1
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.
2
3rd Party Plugins - (fb2k) / Re: foo_vis_spectrum_analyzer
Last post by Defender -Great to see new functionality.
Unfortunately total gauge gap calculation with different windows scaling than 100%, 200%, 300% is still bugged and thus bars are calculated and displayed too small.
Did you miss my bug report?
https://hydrogenaud.io/index.php/topic,125031.msg1043230.html#msg1043230
3
3rd Party Plugins - (fb2k) / Re: request: 64bit rss reader (for podcasts)
Last post by UELong -4
Support - (fb2k) / Re: Foobar2000 v2.* playback sound quality lower than v1.X
Last post by Gabriel Schwartz -I have not run into this issue, and have not heard of anyone else running into a similar issue during the entire development of foobar2000 2.x. One thing to note is that ASIO tends to bypass Windows Audio Mixer settings, so make sure that the max volume levels for fb2k in the mixer are at the same level (100%) for both installations. Also ensure that you have the latest audio drivers for your system.
If you use ASIO why would you need audio drivers for?
Everything is converted in your DAC specially if you output via USB.
5
FLAC / Re: FLAC-git Releases (Code Base v1.4.x)
Last post by itisljar -These binaries are for Linux. They won't work on Windows.
Of course. You didn't do anything, I didn't read properly LOL
Thanks for Windows binaries.
6
Support - (fb2k) / Re: Converting File Bigger Than 4GiB.
Last post by Nick.C -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.
7
Support - (fb2k) / Re: Converting File Bigger Than 4GiB.
Last post by Case -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.
8
Support - (fb2k) / Re: Converting File Bigger Than 4GiB.
Last post by Nick.C -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?
9
Support - (fb2k) / Re: Foobar2000 v2.* playback sound quality lower than v1.X
Last post by Case -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.
10