Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Recent Posts
1
Support - (fb2k) / Re: Converting File Bigger Than 4GiB.
Last post by Nick.C -
I checked the option in the converter's "Other" section. The converter reported the same error and the file was still deleted - which suggests it's not a foobar2000 issue.

Understood about WAV over pipes and the --ignore-chunk-sizes option found in encoders. I prefer to use piped encoding as it's much faster (and uses up less of the lifetime write of SSDs).

Further checking, by removing lossyWAV from the command line and piping foobar2000 output to command line FLAC, has also ruled out command line FLAC as the culprit. It seems that my --ignore-chunk-sizes option in lossyWAV is not working as intended.

Many thanks again for taking the time to explain foobar2000's piped output and converter options that I had previously missed. Very much appreciated.
2
Support - (fb2k) / Re: Converting File Bigger Than 4GiB.
Last post by Case -
All decoders in foobar2000 decode to foobar's internal format, in 32-bit foobar2000 that's 32-bit float and in 64-bit foobar2000 it's 64-bit float. The converter recreates the chosen bitdepth integer PCM format from the float data. FLAC library abilities are irrelevant.

In the Converter's 'Other' section there's an option 'Leave partial files for aborted or failed conversions'. Enabling that will stop foobar2000 from deleting the temp files.

So far there hasn't been need to provide option to send anything other than WAVE over pipes, as regular WAV format is the most supported and generally encoders have options to ignore lengths for exactly this purpose.

But if you don't want to work with pipes, the Converter can write Wave64 file directly. Just pick that as the output format and create a temporary file to the disk.
3
Support - (fb2k) / Re: Converting File Bigger Than 4GiB.
Last post by Nick.C -
Thanks very much for the prompt response, Case.

Can you please advise if it is foobar2000 that is deleting the output file (that is very much being created while the processing dialog is active)? If so, what are the conditions for such a deletion.

Given that command line FLAC can be told to output to WAVE64 and RF64, and if it is possible to do so in the FLAC library in use in foobar2000, has any consideration been given to exposing these as an option in the converter?
4
Support - (fb2k) / Re: Foobar2000 v2.* playback sound quality lower than v1.X
Last post by Case -
You don't need a microphone to record the output of your DAC. Just plug cable from the output to input and record.
Though it will be a mostly useless exercise as player can't add jitter. A player can only keep the audio interface's buffers filled, the audio interface is responsible for timing the signal and actually making it audible. If the player fails to keep buffers filled you don't need a specialist to notice it. It will cause very audible glitching.
5
Support - (fb2k) / Re: Converting File Bigger Than 4GiB.
Last post by Case -
The build-in FLAC profile in foobar's converter uses parameters --ignore-chunk-sizes with FLAC. As the name suggests that makes the encoder ignore the short length in WAV header and encode until EOF.
6
Support - (fb2k) / Converting File Bigger Than 4GiB.
Last post by Nick.C -
Good evening,

I'm trying to convert a large FLAC file (a bit over two hours of 24/96 stereo) to lossyFLAC in foobar2000 (v1.6.13) using piped output from foobar2000 to a command line encoder piping output to flac.exe and I experience a failure with the following message:
Code: [Select]
1 out of 1 files converted with major problems.

Source: "H:\Test\Test.flac"
  An error occurred while finalizing the encoding process (Object not found) : "H:\Test\lossyFLAC\Test.flac"
  Conversion failed: Object not found
Dumping chunk sizes from the piped data I get:
Code: [Select]
RIFF; -1
fmt ; 16
data; -1
Noting that command line FLAC terminates with the following error:
Code: [Select]
Test.flac: ERROR: stream is too big to fit in a single WAVE file
I'm wondering if there's anything I'm missing with regard to how files with an uncompressed size of over 4GiB are handled by foobar2000.

Any advice would be very much appreciated.
7
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by pqyt -
v0.8.0.0-beta1, 2024-05-01

* New: Left/Right and Mid/Side level meter.
  * The left/right channel pair is selectable.
* Spectogram
  * New: Vertical scrolling and static spectogram. A special setting is available to align the spectogram with a spectrum bars visualization over or under the spectogram.
  * Improved: Overall polishing and removal of glitches.
* Added: Separate peak and RMS level read outs to the peak meter.
* Fixed: An old color bug in the owner-drawn menu list.

You can only download it from GitHub until the final release.

I'd appreciate any (constructive) feedback about the implementation of the balance and correlation meter and the vertical spectogram.
8
Support - (fb2k) / Re: Foobar2000 v2.* playback sound quality lower than v1.X
Last post by Globares -
Quote from: jarsonic on
...it's also worth noting that the benefit of ASIO is decreased audio latency, not increased sound quality.  If there is a degradation in sound quality with ASIO output, it is either a driver issue or something else in the audio pipeline that is causing an issue.
The ASIO drivers "sound" better, it doesn't mean that the bits are different - I assume that both pipelines are "bit-perfect", but latency, jitter or generally timing is crucial for spatial effect, i.e. the soundstage. They also impact other sound parameters. Windows Audio Mixer is to be avoided. It degrades the sound quality; "exclusive mode" improves things when properly implemented. Generally, no upsampling is much better than a bad one.
The v1 v2 difference is not big, so the question is how may people did A/B comparisons and what did they listen to. Acoustic songs are the best for this. Busy, rock tracks masks this issue, too. Is this Windows-only problem? I have no iOS to test it.
I’ve got no big hopes for a fix. Real-time stream profiling is a tedious task and first a developer (or the Developer 😊, don’t know if there’s a team), needs to reproduce the problem, however there’s a small chance that this “problem report” will trigger some ideas about changes in the data stream processing that could negatively affect the jitter when compared to version 1.X. We’ll see.
10
Lossless / Other Codecs / Re: HALAC (High Availability Lossless Audio Compression)
Last post by Hakan Abbas -
Quote from: Case on
Since there is still no updated decoder DLL I sandboxed the process and added support for 32-bit foobar2000 while at it. Since the DLLs are only 64-bit the 32-bit component won't be able to decode anything unless the OS is also 64-bit.
And I listed the component on my component page: https://foobar.hyv.fi/?view=foo_input_halac
Thank you very much for your interest in the topic and for what you have done. You are great.
I have uploaded the 32-bit compiled versions of the Encoder and Decoder from version 0.2.7 to Github as SSE2 and AVX. The 32-bit version may experience slightly loss of speed during the Encode stage.

I'm trying to prepare the things I get notes for the 0.2.8 DLL version (Windows/Linux). And since the DLL will be independent of the file and the file path, Player will now have multiple language support.

X