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.1 bugs (Read 16822 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: foobar2000 v2.1 bugs

Reply #25 –
Nevermind, I had made an error in the advanced settings to the Properties dialog. Sorry.

Re: foobar2000 v2.1 bugs

Reply #26 –
Quote from: augustoriodosul on
Hi guys. Listening to 44.1K x 16bit, switching to new music 96K x24bit range, strange noise comes along. It only ceases after closing Foobar2000 v. 2.1 release 05.06.2023 and opening it again. Thanks.
Thanks, that was the issue pawel_na_a was trying to report. Noises with exclusive mode + smooth fader when audio stream format changes.

Edit: things should be fixed in the preview released today.

Re: foobar2000 v2.1 bugs

Reply #28 –
Problem with stuttering sound solved in latest preview (2023-06-07)

Re: foobar2000 v2.1 bugs

Reply #29 –
After updating to v2.1x64 Preview-2023-06-07 over 2.0x64 Final, I find that when using "check for updated components" I will occasionally receive the message "Could not check for updates: The specified data could not be decrypted."  The message appears immediately, without the usual "progress bar."

Usually, checking again immediately afterwards results in a normal response.  The problem is the most reproducible when newly starting 2.1, doing a "Check for new foobar2000 versions" (always works), then right after that the "Check for updated components."  I would say the frequency of the occurence that way is about 50%.  This was never observed in 2.0 Final x64.

Windows 10 x64 22H2.

Re: foobar2000 v2.1 bugs

Reply #30 –
The latest version of foobar2000 (v2.X) doesn't obey High Contrast settings in WIndows 10. It appears to apply to all windows (main window, options, console, ect., ect.) within the program. The old (v1.X.X) versions prior to (v2.X) don't have this problem.

What's happening is that (v2.X) is using "dark mode" colors rather than the High Contrast colors.

Re: foobar2000 v2.1 bugs

Reply #31 –
Hi, I get crashes on playback error when trying to play HLS radio (v2.1 preview 2023-06-07)

The radio stations are:
https://www.maxradio.ca/UHD/MaxRadio/384k/Max.m3u8 (384k AAC-LC Stereo)
https://www.maxradio.ca/UHD/MaxRadio/FLAC/Max.m3u8 (FLAC)
both work just fine in VLC

one crash report is for AAC, another for FLAC

Re: foobar2000 v2.1 bugs

Reply #32 –
@iGom, the crash logs show that foo_input_vgmstream is for some reason involved and looks like it is the cause.

Re: foobar2000 v2.1 bugs

Reply #33 –
Quote from: Case on
@iGom, the crash logs show that foo_input_vgmstream is for some reason involved and looks like it is the cause.

Still crashes after removing foo_input_vgmstream

Re: foobar2000 v2.1 bugs

Reply #34 –
Of sorry, I didn't read the crash logs properly so I missed an important bit. You have enabled the advanced preferences option to crash when playback fails, and those streams are unrecognized by foobar2000.

Re: foobar2000 v2.1 bugs

Reply #35 –
Quote from: Case on
Of sorry, I didn't read the crash logs properly so I missed an important bit. You have enabled the advanced preferences option to crash when playback fails, and those streams are unrecognized by foobar2000.

yeah, but e.g. this station works just fine http://as-hls-ww-live.akamaized.net/pool_904/live/ww/bbc_radio_fourfm/bbc_radio_fourfm.isml/bbc_radio_fourfm-audio=96000.norewind.m3u8

Anyway, I got the previous stations to work with this component https://www.foobar2000.org/components/view/foo_input_ffmpeg, so I'll stick with this for now

Re: foobar2000 v2.1 bugs

Reply #36 –
Windows 11 22H2, foobar2000 v2.1 2023-06-07

It seems that the ReplayGain scan/playback is broken for xHE-AAC files when Windows Media Foundation is used for decoding. The values are much lower then they should be, for example I have a flac file which has track gain -6.94 dB and track peak 0.98 but the encoded file (preset 3, ~96kbps) shows track gain -1.83 dB and track peak 0.75 (the encoded files are RG re-scanned).

I also tried re-scanning the same file previously made (which has the correct RG values) and I get the incorrect (lower) values again. However when I play the file which has the correct RG, the volume is too low, but sounds OK (volume wise) when using the incorrect RG values.

Re: foobar2000 v2.1 bugs

Reply #37 –
Maybe DRC is enabled by default in WMF decoder.

Re: foobar2000 v2.1 bugs

Reply #38 –
V2.0 [x86] / W10

When foobar2000 restored down to any window size other than fully maximized, neither
- Album list filtering in the component
nor
- Properties dialog dropdown of autocomplete fields
Work correctly.

Album list sometimes won't draw and autocomplete suggestions can't be selected via down / up arrow on keyboard
 
Neither an audiophile, nor album snob. Why do ratings threads always have someone saying they don't believe in rating music?
Record Label Icons: 600x600 pngs appropriate for any color background:
freeimage.host/johnbuck/?list=images&sort=name_asc&page=1

Re: foobar2000 v2.1 bugs

Reply #40 –
I get inusual 0db series in meter.

Re: foobar2000 v2.1 bugs

Reply #41 –
64-Bit latest preview. Bug in Refacets filtering?

Full PATH to example file: "M:\Musik\Devices\Pop\exm\2021. 3xBACH\01. prelude 3.m4a"

This single filter is being used:

Code: [Select]
((%path% HAS \Reference\) OR (%path% HAS \Klassik\)) AND (%path% NOT HAS \VLevel\)

The tracks in above folder are included in the filter. Refacets shows a lot of folders from my Pop folder and I don't see why. Usually lists just very few tracks.

Screenshot related.

Re: foobar2000 v2.1 bugs

Reply #43 –
As Porcus said, your filter is invalid. You can fix it by changing the last part to (NOT %path% HAS \VLevel\).

Hint: you can test a filter easily with Library -> Search dialog. It will give instant feedback about syntax errors.

Re: foobar2000 v2.1 bugs

Reply #44 –
Quote from: Forfit on
I get inusual 0db series in meter.
Is this under Wine perhaps? You know Peter's time is limited. There's a higher chance of getting any bug fixed if more details are given how they are triggered.

Re: foobar2000 v2.1 bugs

Reply #46 –
Quote from: iGom on
Hi, I get crashes on playback error when trying to play HLS radio (v2.1 preview 2023-06-07)

The radio stations are:
https://www.maxradio.ca/UHD/MaxRadio/384k/Max.m3u8 (384k AAC-LC Stereo)
https://www.maxradio.ca/UHD/MaxRadio/FLAC/Max.m3u8 (FLAC)
both work just fine in VLC

one crash report is for AAC, another for FLAC


Thanks for the links, this has been most helpful to me.
Relevant functionality (play multi segment MP4 DASH) was missing in my code and has just been added for the next build.

For correct rendering of these stream, the application must be able to deal with:
  • Multi-segment MP4 DASH
  • FLAC in MP4 container
  • ID3 tags in MP4 container, in legit MP4 chunks, as if other MP4 tagging specs didn't exist.

It just happens that I can deal with all of this by connecting multiple pieces of own technology together. But implementing this in anything less modular is a giant pain.

Also, it's the 2020s and clowns still add ID3v2 to new file formats.
Microsoft Windows: We can't script here, this is bat country.

Re: foobar2000 v2.1 bugs

Reply #47 –
Greart
Quote from: Peter on
Quote from: iGom on
Hi, I get crashes on playback error when trying to play HLS radio (v2.1 preview 2023-06-07)

The radio stations are:
https://www.maxradio.ca/UHD/MaxRadio/384k/Max.m3u8 (384k AAC-LC Stereo)
https://www.maxradio.ca/UHD/MaxRadio/FLAC/Max.m3u8 (FLAC)
both work just fine in VLC

one crash report is for AAC, another for FLAC


Thanks for the links, this has been most helpful to me.
Relevant functionality (play multi segment MP4 DASH) was missing in my code and has just been added for the next build.

For correct rendering of these stream, the application must be able to deal with:
  • Multi-segment MP4 DASH
  • FLAC in MP4 container
  • ID3 tags in MP4 container, in legit MP4 chunks, as if other MP4 tagging specs didn't exist.

It just happens that I can deal with all of this by connecting multiple pieces of own technology together. But implementing this in anything less modular is a giant pain.

Also, it's the 2020s and clowns still add ID3v2 to new file formats.

Great to hear that, thanks! Just in case there are also multi-channels and xHE-AAC stations if that would be helpful. kinda surprised to hear about ID3 in the MP4 container

512k AAC-LC Surround
https://www.maxradio.ca/UHD/LG73Surround/512k/LG73.m3u8
https://www.maxradio.ca/UHD/MaxRadioSurround/512k/Max.m3u8
https://www.maxradio.ca/UHD/NewWestRockSurround/512k/NewWestRock.m3u8
https://www.maxradio.ca/UHD/UptownSurround/512k/Uptown.m3u8

48k xHE-AAC Stereo
https://www.maxradio.ca/UHD/LG73/48k/LG73.m3u8
https://www.maxradio.ca/UHD/MaxRadio/48k/Max.m3u8
https://www.maxradio.ca/UHD/NewWestRock/48k/NewWestRock.m3u8
https://www.maxradio.ca/UHD/UptownRadio/48k/Uptown.m3u8   

Re: foobar2000 v2.1 bugs

Reply #48 –
Not a bug per se, but the Quick Tigger dialog window (initiated through the context menu Tagging > Quick Tagger > ... > More...) doesn't use dark mode.

Re: foobar2000 v2.1 bugs

Reply #49 –
Hi, using the x86 version on windows 10 22H2 on a i7 with 16 Gig RAM