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.
Topic: foobar2000 Latest preview version (Read 1796 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

foobar2000 Latest preview version

Playback glitched with PGGB-RT (8fS, Extended, Speed) + compressor DSP after updating F2K to the 2024-02-28 version. Please help.

Re: foobar2000 Latest preview version

Reply #1
What outputs have you tried and had problems with? The new preview has changes that can affect output components.

Re: foobar2000 Latest preview version

Reply #2
It is possible that the new CPU usage optimizations don't play nicely with very low output buffer sizes combined with CPU-heavy DSP. The next update will address this.

For now, please try increasing output buffer size in Preferences / Playback / Output.
Microsoft Windows: We can't script here, this is bat country.

Re: foobar2000 Latest preview version

Reply #3
Something weird I'm having here: have two pc's on windows 10, both on latest preview (64-bit) versions, fb2k crashes on both machines when I right click on file, replaygain, scan per track gain, bar goes to around 25% and then crashes on both machines. Also have one Windows 11 machine with the same latest preview, not a single problem to report on that machine. Any idea?

Re: foobar2000 Latest preview version

Reply #4
It is possible that the new CPU usage optimizations don't play nicely with very low output buffer sizes combined with CPU-heavy DSP. The next update will address this.

For now, please try increasing output buffer size in Preferences / Playback / Output.


Temporarily I shifted to the stable version and I always set device buffer at 50ms. My DSPs are CPU heavy (Fabfilter Pro MB and Pro L2).

Re: foobar2000 Latest preview version

Reply #5
v2.2 2024-03-04:

* Minor preexisting aesthetic and performance issue in Keyboard Shortcuts > Action > Filter list:
The search box and the filter list are wonky but work. A char/string typed into the search box is first displayed as a single white space while in the tree, the first entry at the top of the list scrolled to is duplicated three times below itself, followed by a delay, then the replacing of the white space in the search box with the first char entered, and then the rest of the string, if applicable, displayed quicker but not as fast as typing or pasting.

* x86: Only one VST component (foo_dsp_vst3) works. For a second (and so on), the "A configuration window...." message and the window of the VST are not displayed.

* x86 note: The unofficial third-party component foo_out_pulse was helpful to work around stuttery streaming on Wine with PulseAudio. With current fb2k versions, this component is problematic and seems deprecated.

Suggestions:
* DSP Manager: Add a toggle for each active DSP.
* DSP Manager: Add renaming of DSP chain presets: The workaround to save new and delete old is tedious.
* DSP Manager: Alpha sort Available DSPs when third-party components are installed.
* DSP Manager: In the context menu of each DSP in Available DSPs, note the component (for instance, 'Add "Tempo Shift" from Effect DSP').
* Reinstate as an option the behavior from fb2k 1.x to not reset "Title / Artist" and "Artist/album" of URLs when stopping play.
* Enhance update checking (https://hydrogenaud.io/index.php/topic,116509.msg1031404.html#msg1031404)
* Fix URLs displaying "2" for "Title / track artist"? This behavior has been present for awhile (for instance, http://79.120.39.202:9069, http://79.111.14.76:9047). Is this due to fb2k or the server (the value, perhaps, mistakenly being the number of channels?)? A workaround is this custom column: $if($strcmp(%title%,2),%path%,%title%)

Re: foobar2000 Latest preview version

Reply #6
Hi there

Foobar V2.2 2024-03-18 32/64 - crashes when I ReplayGain multiple albums at once. Back in stable foobar2000 v2.1.3 32/64 no problems.

Re: foobar2000 Latest preview version

Reply #7
^I saw someone on reddit with a similar issue. They mentioned it only happens when they disable AVX in their bios. No idea why anyone with a supported CPU would do this but maybe a genuine issue for those with CPUs which really do not support it??

Re: foobar2000 Latest preview version

Reply #8
^I saw someone on reddit with a similar issue. They mentioned it only happens when they disable AVX in their bios. No idea why anyone with a supported CPU would do this but maybe a genuine issue for those with CPUs which really do not support it??

My CPU supports AVX and AVX2 instructions set.

 

Re: foobar2000 Latest preview version

Reply #9
My CPU supports AVX and AVX2 instructions set.

And you're having problems with replay gain scanning like the person I was replying to? You're not making yourself clear given your previous post just up the page is totally unrelated to this issue. :/

edit: just realised this wasn't a generic preview problem thread so twikaros probably shouldn't have posted their unrelated problem here. I guess I need to pay more attention too. :P

Re: foobar2000 Latest preview version

Reply #10
My CPU supports AVX and AVX2 instructions set.

And you're having problems with replay gain scanning like the person I was replying to? You're not making yourself clear given your previous post just up the page is totally unrelated to this issue. :/

edit: just realised this wasn't a generic preview problem thread so twikaros probably shouldn't have posted their unrelated problem here. I guess I need to pay more attention too. :P
Absolutely.

Re: foobar2000 Latest preview version

Reply #11
Foobar V2.2 2024-03-18 32/64 - crashes when I ReplayGain multiple albums at once. Back in stable foobar2000 v2.1.3 32/64 no problems.
I don't see any crashes related to ReplayGain scanning in the crash logger. If you don't post crash logs or share any additional information this is impossible to fix, as ReplayGain scanning any number of albums doesn't generally crash.

My CPU supports AVX and AVX2 instructions set.
Are you saying you still have issues with latest build? You never replied to my question about which output method you use.
PS: you really should consider using longer output buffer than 50 ms. Such short buffer should only be needed if you are monitoring real-time recording.