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 v2.0 bugs (Read 138004 times) previous topic - next topic
0 Members and 8 Guests are viewing this topic.

Re: foobar2000 v2.0 bugs

Reply #600 –
Quote from: Defender on
Seems as if the internal fb2k beta 31 x86 Monkey's audio component is the culprit.
With or without the component?
Monkey's is changing quickly at the moment - sometimes several new versions a day - so from beta 28, fb2k switched to using ffmpeg to decode. But there is a component that tries to stay a bit more up-to-date.

If you didn't use that component - just to play without - then probably it is an ffmpeg issue.
Try the same file with ffplay and see what happens? ffmpeg has chosen to leave a few features completely out of their Monkey's decoder. But, even for "supported" signals, ffmpeg isn't always doing the right thing. (Bug in its WavPack decoder, bug in its MPEG-2 decoder, and ffplay chokes on FLAC files with (stupidly) small block sizes and the dev doesn't care.)

If you did use the component ... try to update it. And/or stay patient, depending on what signal you tried to ape-compress - you cannot expect not-yet-stable codec features to be supported from day one.

Re: foobar2000 v2.0 bugs

Reply #601 –
Quote from: Porcus on
Quote from: Defender on
Seems as if the internal fb2k beta 31 x86 Monkey's audio component is the culprit.
With or without the component?
Monkey's is changing quickly at the moment - sometimes several new versions a day - so from beta 28, fb2k switched to using ffmpeg to decode. But there is a component that tries to stay a bit more up-to-date.

If you didn't use that component - just to play without - then probably it is an ffmpeg issue.
Try the same file with ffplay and see what happens? ffmpeg has chosen to leave a few features completely out of their Monkey's decoder. But, even for "supported" signals, ffmpeg isn't always doing the right thing. (Bug in its WavPack decoder, bug in its MPEG-2 decoder, and ffplay chokes on FLAC files with (stupidly) small block sizes and the dev doesn't care.)

If you did use the component ... try to update it. And/or stay patient, depending on what signal you tried to ape-compress - you cannot expect not-yet-stable codec features to be supported from day one.

I said I got Monkey's Audio 192kHz/24bit (2channel) to work on fb2k beta 31 x86 by installing the external Monkey's Audio component (10.07).

Re: foobar2000 v2.0 bugs

Reply #602 –
Quote from: Defender on
Hi,

fooBar 2.0 beta (until and including) 31 x86 %bitrate% show overall bitrate for MKV instead of the bitrate for the playing audiostream.
fooBar 1,6.16 %bitrate% shows the correct audiostream bitrate.

Is there some other tag for audiostream bitrate in 2.0 beta that I am unaware of?



Did some experimenting with DTS within a MKV container.
On 1.6.16 I need external ffmpeg decoder wrapper to play/list it and everything works as intended (correct codec and bitrate reported).

On fb2k beta 31 x86 things are different. Whether I use the external ffmpeg decoder or not for MKV results are the same.
Upon listing fb2k beta 31 x86 reports the correct codec (DTS in this case) but the overall bitrate of the container MKV.
Upon playing fb2k beta 31 x86 reports the wrong codec (MKV) but the correct bitrate of the playing DTS stream.

Re: foobar2000 v2.0 bugs

Reply #603 –
Bug in v2.0 and v1.6.16 when doing File operations > Move to > Move entire folder content + Remove empty source folders.

After moving folder with cue+flac album, album stays in playlist but when i play album info in status bar is incorrect.
To fix it i have to select all album tracks and do Taging > Reload info from files

@Peter, please make foobar reload info of moved files or folders after File operations > Move to

Re: foobar2000 v2.0 bugs

Reply #604 –
In beta 32 x86, all my keyboard shortcuts for Play / Pause / Stop don't work at all.
I reverted to beta 31 and they started working again.

Re: foobar2000 v2.0 bugs

Reply #605 –
I have noticed that v2.0 X32 Bit version is not playing 192K files correctly (much distortion) when I revert to V2 x64 Bit everything functions normally.

Re: foobar2000 v2.0 bugs

Reply #606 –
Quote from: dore.moni on
Bug in v2.0 and v1.6.16 when doing File operations > Move to > Move entire folder content + Remove empty source folders.

After moving folder with cue+flac album, album stays in playlist but when i play album info in status bar is incorrect.
To fix it i have to select all album tracks and do Taging > Reload info from files

@Peter, please make foobar reload info of moved files or folders after File operations > Move to
Noted, thanks for reporting. At this point I'm fixing only things that broke in 2.0 series, known old bugs will be fixed for version 2.1.

Quote from: frogworth on
In beta 32 x86, all my keyboard shortcuts for Play / Pause / Stop don't work at all.
I reverted to beta 31 and they started working again.
Sorry, can't reproduce, works for me.

Quote from: marktherob2005 on
I have noticed that v2.0 X32 Bit version is not playing 192K files correctly (much distortion) when I revert to V2 x64 Bit everything functions normally.
Sorry, can't reproduce. What kind of files specifically? What format? What settings (output device, DSP, etc)?
Microsoft Windows: We can't script here, this is bat country.

Re: foobar2000 v2.0 bugs

Reply #607 –
Quote from: frogworth on
In beta 32 x86, all my keyboard shortcuts for Play / Pause / Stop don't work at all.
I reverted to beta 31 and they started working again.
while it works for me too like Peter the dev.
what types of Component addons are you perhaps using?
standard install or portable?

Re: foobar2000 v2.0 bugs

Reply #608 –
Bug in File integrity verifier 1.4.2 and integrted version in foobar 2.0: Verbose Accurate rip output option does not work, no changes with on/off checkbox in Advanced options

Re: foobar2000 v2.0 bugs

Reply #609 –
Seems like a bug. I tested Binary Comparator in beta 2.0 and compare it with v1.6.16
There are 2 tracks: 32bit fixed file and the same file converted to 32bit floating.

1. Binary Comparator in beta 2.0 shows that they are different
2. Binary Comparator 2.3.2 when comparing it shows they are the same, No differences in decoded data found.
3. Wavelab 6.0.1 when comparing two files shows they are exactly equal, No differences

I've attached this files for testing. Is there a problem in foobar v2.0 or v1.6.16 with it?

Re: foobar2000 v2.0 bugs

Reply #610 –
Quote from: dore.moni on
Seems like a bug. I tested Binary Comparator in beta 2.0 and compare it with v1.6.16
There are 2 tracks: 32bit fixed file and the same file converted to 32bit floating.

1. Binary Comparator in beta 2.0 shows that they are different
2. Binary Comparator 2.3.2 when comparing it shows they are the same, No differences in decoded data found.
3. Wavelab 6.0.1 when comparing two files shows they are exactly equal, No differences

I've attached this files for testing. Is there a problem in foobar v2.0 or v1.6.16 with it?
The new foobar2000 version (specifically, 64bit foobar2000) reports accurate results. The old version can't possibly report these because it converts int32 to float32 internally before comparing, so it reads the same data from both of these files.
Microsoft Windows: We can't script here, this is bat country.

Re: foobar2000 v2.0 bugs

Reply #612 –
Quote from: Squeller on
Not a bug, but... you get it. Arrows are barely visible in dark mode.
Known but thanks for reminding.
Unfortunately, standard MS control defies my attempts at overriding rendering colors.
I'll look again for version 2.1, at this point I just want 2.0 out with no glaring bugs.
Microsoft Windows: We can't script here, this is bat country.

Re: foobar2000 v2.0 bugs

Reply #613 –
Arrows are barely visible in Album List. Theme is default, not dark, but i use grey background for foobar

Re: foobar2000 v2.0 bugs

Reply #614 –
foobar2000 2.0 beta 32 x86
It seems to have stopped ordering DSP chains by name and reverted to former behavior of ordering by when they were created.
If this was intentional, I need to say that ordering by name is more intuitive and saves time. I renamed all of my chains to have numbers at the beginning so that they would always be in the correct order.

**Edit**
Never mind. Seems closing and reopening is what makes them reorder. No problem here!
Think millionaire, but with cannons.

Re: foobar2000 v2.0 bugs

Reply #615 –
Quote from: Melchior on
while it works for me too like Peter the dev.
what types of Component addons are you perhaps using?
standard install or portable?

Portable install.

OK, I've upgraded again from beta 31 and the problem hasn't appeared. Must have been a random thing - I did restart and test again before reporting last time!
Sorry for the red herring. Thanks for your work 🙏🏼

Re: foobar2000 v2.0 bugs

Reply #616 –
Hi, I'm still receiving the following start error message after the clean installation of v2.0 beta 33 64bit Win 10:



Since version 31 the same error happens also for version 27 - 32.
I'm able to get a functioning Foobar installation with a workaround but I think it would be better to fix this error as I have read that the version 33 is a release candidate build. 

Re: foobar2000 v2.0 bugs

Reply #617 –
@beat8000 - the function uPrintCrashInfo_StartLogging that you are missing is in shared.dll. Do you somehow have an old version of that dll file in the foobar2000 directory? Replacing shared.dll with an old version creates that exact problem.

I'd be curious to know how you created this bugged situation and what your workaround is.
 

Re: foobar2000 v2.0 bugs

Reply #618 –
Hi @Case
For a clean installation I always delete the two indicated Foobar folders during the uninstall.
Therefore the file shared.dll will be newly created but the timestamp is now older (16.04. -19:44) than the one of foobar2000.exe (16.4. - 19.45).

As a workaround I have used the same fix as I have described for the "missing shared.dll error" in my previous post
https://hydrogenaud.io/index.php/topic,122847.msg1021504.html#msg1021504:

During the update e.g. from Version 17-x64 to 24-x64 the optional features must be switched off during the first custom install. Afterwards a second install with activated optional features will complete the install without the shared.dll system error immediately or after the next Foobar start.

Re: foobar2000 v2.0 bugs

Reply #620 –
foobar2000 v2 seems to be missing the options when rightclicking an scrollbar.
Please see images:

foobar2000 v1.6, rightclick options, as expected:


In foobar2000 v2, these rightclick options are missing:


I don't know if it is an intended behavior or an bug?

Re: foobar2000 v2.0 bugs

Reply #622 –
Quote from: TuNk77 on
foobar2000 v2 seems to be missing the options when rightclicking an scrollbar.

I don't know if it is an intended behavior or an bug?

The occasional scrollbar context menu is from the Windows operating system, because here it's in German language. See Screenshot.

Re: foobar2000 v2.0 bugs

Reply #623 –
Can confirm the same on v1.6. Scrollbar menu appears on OS language, even if foobar is set to English.

Re: foobar2000 v2.0 bugs

Reply #624 –
Quote from: beat8000 on
Hi @Case
For a clean installation I always delete the two indicated Foobar folders during the uninstall.
Therefore the file shared.dll will be newly created but the timestamp is now older (16.04. -19:44) than the one of foobar2000.exe (16.4. - 19.45).

As a workaround I have used the same fix as I have described for the "missing shared.dll error" in my previous post
https://hydrogenaud.io/index.php/topic,122847.msg1021504.html#msg1021504
Something weird is going on. The shared.dll file is always updated along with the other core files. Could you log an example installation that reproduces the issue with Process Monitor? Please do not filter out at least anything that touches any file called shared.dll.