Text only | Text with Images

HydrogenAudio

Hosted Forums => foobar2000 => General - (fb2k) => Topic started by: Chibisteven on 2022-08-31 05:26:22

Title: foobar2000 v2.0 bugs
Post by: Chibisteven on 2022-08-31 05:26:22
The bugs I found so far appear to be GUI related.

Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2022-09-01 12:54:18
Noted, thanks for reporting.
Title: Re: foobar2000 v2.0 bugs
Post by: Lesmo16 on 2022-09-01 13:08:09
ReFacets isn't shown in the list of installed media library viewers.
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-09-01 13:33:39
How did you manage that? It's not optional and is installed for everyone.

If you have multiple installs of v1 and v2, check you launched the right one???
Title: Re: foobar2000 v2.0 bugs
Post by: DJ FRANK G. on 2022-09-01 13:39:05
Portable install: the config does't save in portable folder.
Title: Re: foobar2000 v2.0 bugs
Post by: Brand on 2022-09-01 13:41:56
This is probably a known issue, but I didn't see it mentioned.
The built in dark color themes (in Quick Setup) have poor visibility of the "arrows" in the media library. They're often not visible unless you hover over them with the mouse pointer:

X

It looks fine if "Dark Mode" is enabled, however.

EDIT: In dark mode, the light colored themes have worse visibility:

X
Title: Re: foobar2000 v2.0 bugs
Post by: Lesmo16 on 2022-09-01 13:46:16
Quote from: marc2k3 on
How did you manage that? It's not optional and is installed for everyone.
I made a clean portable install of v2 and the list entry doesn't appear. ReFacets works anyway.

Quote from: marc2k3 on
If you have multiple installs of v1 and v2, check you launched the right one???
It was the right one.
Title: Re: foobar2000 v2.0 bugs
Post by: arch21 on 2022-09-01 13:50:35
Open menu shows Add files on the title, Add files shows Open on title. they work as they should.

Quote from: marc2k3 on
How did you manage that? It's not optional and is installed for everyone.

If you have multiple installs of v1 and v2, check you launched the right one???

I guess he expected ReFacets to be listed there
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-09-01 13:53:25
Quote from: arch21 on
I guess he expected ReFacets to be listed there

That would be it. :D
Title: Re: foobar2000 v2.0 bugs
Post by: Lesmo16 on 2022-09-01 13:55:15
It is.  :D
Title: Re: foobar2000 v2.0 bugs
Post by: Brand on 2022-09-01 13:55:33
Quote from: DJ FRANK G. on
Portable install: the config does't save in portable folder.
It does here. Maybe you didn't notice, but a fresh portable install now has a "profile" folder. 1.6 didn't have it.
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-09-01 14:02:09
Quote from: Brand on
It does here. Maybe you didn't notice, but a fresh portable install now has a "profile" folder. 1.6 didn't have it.

The profile folder for portable installs was introduced with 1.6. It's always there for clean installs.

If you didn't have one, it's because you upgraded from an older version.
Title: Re: foobar2000 v2.0 bugs
Post by: Bogozo on 2022-09-01 15:57:18
Beta 3.

Console UI element doesn't use color settings from "DUI->Colors and Fonts" anymore. Is this intended?

Converter's presets that use *.bat files don't work anymore.
Example of preset:
(https://i.imgur.com/6Xkc3qo.png)
(https://i.imgur.com/9wbhTTl.png)
(https://i.imgur.com/JukmMNq.png)
Text of bat file:
Code: [Select]
START "sox" /D "C:\Program Files\sox\" /HIGH /WAIT sox.exe %1 -n spectrogram -x 1600 -Y 1200 -o "C:\temp\foo_temp\Image.png"
mspaint.exe "C:\temp\foo_temp\Image.png"
In 1.6.12 it works as expected: creates spectrogram and opens it in MS Paint.
Title: Re: foobar2000 v2.0 bugs/toggle album art
Post by: Dalnorge42 on 2022-09-01 17:10:41
Is there a way to toggle album art? I used to be able to just mouse click the area and it would switch between front and back covers.
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-09-01 17:33:00
Columns UI does that. Not sure if DUI did but I've been wrong a few times today so who knows.  :P
Title: Re: foobar2000 v2.0 bugs
Post by: sasalasa on 2022-09-01 17:59:29
reFACET in foobar2.0 doesn't show me my folders even I choose the folder colums...
Title: Re: foobar2000 v2.0 bugs
Post by: MaCs on 2022-09-01 18:45:42
Quote from: sasalasa on
reFACET in foobar2.0 doesn't show me my folders even I choose the folder colums...
By "folder", you mean "album art"? ReFacets doesn't do that... yet. It shows folder names.
Title: Re: foobar2000 v2.0 bugs
Post by: Dalnorge42 on 2022-09-01 18:57:49
Quote from: marc2k3 on
Columns UI does that. Not sure if DUI did but I've been wrong a few times today so who knows.  :P
I would be happy with a key command to toggle album art (assign to mouse button).
Title: Layout Editing Mode
Post by: Lesmo16 on 2022-09-01 19:41:21
The Layout Editing Mode can't be finished completely.
After switching it off the blue splitters indeed turn to grey ...
but even locked (the new method) splitters stay movable.
Title: Re: foobar2000 v2.0 bugs
Post by: demirkoray on 2022-09-01 21:53:52
In Preferences > Output, Enable smooth seeking, pause and volume changes under Fading.

And then, play a stereo track after a mono track --> Gapless playback does not work!

Play a stereo track after a stereo track --> Gapless playback works.

Title: Re: foobar2000 v2.0 bugs
Post by: Fabcore on 2022-09-02 00:34:36
BUG:
When it drop a file from windows explorer to a playlist with many files and the playlist is focused on any file (the scrollbar is up or down), the scrollbar centers, losing the focus where i was.
Title: Re: foobar2000 v2.0 bugs
Post by: Forfit on 2022-09-02 02:29:32
In V1 I restore fb2k from notification bar with one click.
In VW I restore fb2k from notification bar with TWO click.

e.c.
I not know because, but now it work.
Title: Re: foobar2000 v2.0 bugs
Post by: demirkoray on 2022-09-02 10:20:36
Gapless playback does not work, if you play a stereo song right after a mono song through ASIO.
Title: Re: foobar2000 v2.0 bugs
Post by: IWSNX on 2022-09-02 19:36:31
Beta 3, 32-bit:

search term "IS" doesn't work.
My Autoplaylist "5 star rating"
%rating IS 5%
doesn't get any results or just music files which have been added today.

%rating HAS 5% is working.
Title: Re: foobar2000 v2.0 bugs
Post by: Porcus on 2022-09-02 19:48:29
Sure you put the rightmost percent sign where it should?
Title: Re: foobar2000 v2.0 bugs
Post by: IWSNX on 2022-09-02 20:10:55
Yes, as you can see there is only 1 file found. Take a look at the screenshot.

(https://i.imgur.com/aqOiFET.png)
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-09-02 20:13:05
You need to update it to

Code: [Select]
rating IS 5

Without the %%, it uses metadata directly from your files.

With fb2k v2, it has playback statistics built in (previously foo_playcount) and this takes over %rating% for its own internal database.
Title: Re: foobar2000 v2.0 bugs
Post by: IWSNX on 2022-09-02 20:17:15
Thanks for clarification, it works!
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-09-02 20:25:16
Also, if you used to display %rating% in any playlist column / display panel, it now needs updating to use $meta(rating).
Title: Re: foobar2000 v2.0 bugs
Post by: josemescud on 2022-09-02 20:30:14
Help. Error in the Media Library.

I have updated to version 2.0 Betta 3, 32bits and something that had never happened to me has happened to me since Foobar, more than 10 years ago.

If I open Foobar without having connected the external hard drive my music offers me at the Album List Panel all my music and in the Library View when I select an artist offers me all the albumes of her. And the following occurs:
- The first time offers albumes correctly
- Change to another artist and when I return to the previous one, all the tracks of all the albums have doubled.
- If I do this operation 10 times I double them 10 times, if I do 50 I duplicate them 50.

The attached image reflects the problem.

As the tracks duplicate, it takes more to respond to all actions.

The only solution is to click the hard drive and wait for monitoring (8 TB hard drive).

It has also happened to me with the connected hard drive, after using Re-Facets. Logically, it has been slowed in such a way that it did not respond and I had to stop the process. But when Foobar launched again, he did not respond and had to disconnect the hard drive to load the foobar and monitor the hard drive.
Title: Re: foobar2000 v2.0 bugs
Post by: josemescud on 2022-09-02 20:41:01
I just realized that after being without using Foobar, he has continued to double every track with which he has become so slow that he hardly responds.
Title: Re: foobar2000 v2.0 bugs
Post by: Snowknight26 on 2022-09-04 00:43:59
Time to add to the list. Found these using beta 3, 64-bit. Will update as I find more.

Title: Re: foobar2000 v2.0 bugs
Post by: pulbitz on 2022-09-04 06:46:34
Deleted about ~10 files in Autoplaylist (about 400,000 items). (File Operations - Delete file)
Until I noticed (about 5-10 minutes) fb2k 2.0 beta 3 was using 100% CPU(1 core) and was constantly writing disks to a specific .tmp file. (loop)
It looks like there is something wrong with sqlite processing.
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-09-04 11:36:02
Quote from: Snowknight26 on
  • Artwork panel flickers when resizing

I'm sure this will be fixed soon enough but I might as well pimp my album art replacement while I can.

It doesn't flicker
Uses the same preferences.
Shows tooltips with size/path info...

(https://i.imgur.com/tuQkmC6.png)

Customisable double click action and other bits available on the menu...

(https://i.imgur.com/ADiuFq5.png)

Like the new DUI panel, it uses WIC for handling exotic image formats (ignore if you have no idea what this is) and can also display album art from certain radio streams.

One thing it does not do is display library viewer selections. That was a conscious choice by me as I don't like it. It tracks playlist items only - preferring the playing item if playing, selected item if not. Can be configured to always track the selected item if you want.

JScript Panel 3, link in sig. 32bit/64bit available. Add to layout as usual, right click>Configure. Click the Samples button>Album Art.
Title: Re: foobar2000 v2.0 bugs
Post by: marktherob2005 on 2022-09-04 15:24:35
Class not registered for aif files

I installed v2 32bit beta 3
when using aif files I get class not registered
then i'm back at 1.6.12 it handles .aif files normally

i'm on Windows 10 64bit build 19041
Title: Re: foobar2000 v2.0 bugs
Post by: Case on 2022-09-04 17:09:20
I think a little bit more info is needed. AIFF is a container and can contain data compressed with several different methods. A sample file would be great but telling what type of compression is used may be minimum requirement.
Title: Re: foobar2000 v2.0 bugs
Post by: Erratic on 2022-09-05 03:46:44
1) Some items when selected in Preferences turn the whole preferences window into "Light" mode even when the system is running in "dark" mode. Selecting unaffected options return the window to dark mode.

Notable examples in the the whole "Columns UI" section and sub-options below it, others option do it also including options added by some plugins.

2) Selecting the Advanced preference and typing something into the filter will often (but not always) cause foobar to CTD a few seconds after finishing typing.  Doing this while a track is playing seems to increase the chance (but again not always).
 

This is on 32 bit version of v2 beta 3.

Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-09-05 06:52:15
Components with preference pages are entirely responsible for rendering the area marked with the rectangle. fb2k can't take it over and automagically apply dark mode.

(https://i.imgur.com/EFDWC5J.png)

fb2k renders the rest and components have to advertise they are dark mode capable. This is because many components will never be updated.

If fb2k assumed all components were dark mode capable and rendered the bits it is responsible in dark mode while the components themselves are not updated, you'd end up with a terrible situation like this...

(https://i.imgur.com/nfTWq8m.png)

This is why the whole window changes to match what the component is capable of.

And just because the entire CUI layout/playlist/panels supports dark mode, it doesn't mean the preferences are dark mode capable (yet). We'll have to wait. Remember CUI 2.0 is still marked as alpha.

Just for fun, components can update their own area but not tell fb2k they are dark mode capable and this happens...

(https://i.imgur.com/ajouzgz.png)

I assume there is a special place in hell for anyone who released a component abusing these options.  :))

Title: Re: foobar2000 v2.0 bugs
Post by: RetBaron on 2022-09-05 13:06:13
Hello, thank you for 2.0 version, Peter.

32-bit version works well with my portable DarkOne installation which I have backed up on 1.6 version. Then foo_input_monkey and foo_playcount remained and caused error and were uninstallable - uninstall option faded out. I returned to backed up 1.6 version and uninstalled these two, then upgraded without any error, everything is running well - skin, playback, all settings and playlist too.

One note though. There should be some speed up coming from used SQlite DB. I can't confirm that. Foobar start is significantly longer, pasting folders from explorer, sorting playlist and removing duplicates is taking up more time too and now I have faded out window with hourglass and waiting time about 15s even when switching between playlists, which was under one second in 1.6. I don't use library or watched folder at all, only one huge whole collection playlist consisting of 11TB and almost half million tracks from my NAS and one temporary playlist for converting etc.

I also hoped for native .webp cover art, but it's not so important.
Title: Re: foobar2000 v2.0 bugs
Post by: Case on 2022-09-05 15:45:59
About .webp cover art support, foobar2000 v2.0 uses Windows Imaging Component interface that allows it to support all image formats that your OS supports. You can for example download HEIC and WEBP support codecs from the Microsoft Store to get them working instantly.

I see that portable install using the old way without "profile" subdirectory causes the component uninstall to be disabled.

All the slow operations you talk about point that you have pre-2.0 UI components active that do some heavy metadata displaying or processing. For reference over here v1.6.12 console reports "Startup time : 0:00.306176" and v2.0 beta 3 reports "Startup time : 0:00.125752". Autoplaylists or library monitoring are not supposed to be a problem, the player is meant to start practically instantly.
Perhaps keeping compatibility with the old components was a mistake.
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-09-05 15:52:10
For windows store averse people or those on windows 7/8.1, you can get webp working by installing this...

https://storage.googleapis.com/downloads.webmproject.org/releases/webp/WebpCodecSetup.exe

edit: not sure that first part made sense. webp is bundled for 10/11 users. You have to go out of your way to remove it.
Title: Re: foobar2000 v2.0 bugs
Post by: watcherhd on 2022-09-06 13:36:40
Album art showing covers is inconsistent - there are times - that it shows not cover or front jpg - it shows random picture

(https://i.imgur.com/W86GPbJ.png)

I think it just uses the first picture in folder.
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-09-06 14:05:08
^ got any more pixels bro? Not sure what you're trying to show us. But check File>Preferences>Display>Album Art>Front. Remove any patterns that don't match your own images or move your to the top. Also, it might help if you said it was the playlist or album art panel??

---

Beta 4 is out...


Quote
    MP4 tagging: do not set Various Artists if itunescompilation is present but set to 0.
    Crash bugs fixed.
    Made installer refuse to upgrade old non-portable installs containing profile data in application folder, which is no longer supported.
    Fixed metadb lock up with large queryInfoMulti() batches.
    Fixed library search by rating not working.
    Added ReFacets to library viewers list.
    Fixed missing double click to fullscreen in Default UI visualisations.
    Fixed disappearing live playback info on playback statistics update.
    Fixed longer-than-necessary gap when reopening exclusive-mode output on format change.
    Fixed seekbar & visualisation glitches when playing very short audio tracks with exclusive-mode output.

https://www.foobar2000.org/download
Title: Re: foobar2000 v2.0 bugs
Post by: watcherhd on 2022-09-06 14:22:03

(https://i.imgur.com/wNfwurw.png)
left only front.* and cover.*  ande removed all other files from the folder - it just doesnt load nor in the playlist nor in album art
(https://i.imgur.com/VMggDtz.png)



Title: Re: foobar2000 v2.0 bugs
Post by: watcherhd on 2022-09-06 14:42:04
found something - front.* works and folder* shows black squares until put first in list. on 1.16.12 it used to work even with folder.* listed as last in settings
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-09-06 14:43:22
I presume this displayed fine on v1.6.1.2? There have been changes in image handling with v2 where the windows imaging component (WIC) is used for loading images. If you could put the image inside a zip and attach it, I could test it with other components.

Just to be clear, I can't do anything about it. I'm just curious.
Title: Re: foobar2000 v2.0 bugs
Post by: watcherhd on 2022-09-06 14:50:18
Quote from: marc2k3 on
I presume this displayed fine on v1.6.1.2? There have been changes in image handling with v2 where the windows imaging component (WIC) is used for loading images. If you could put the image inside a zip and attach it, I could test it with other components.


Just to be clear, I can't do anything about it. I'm just curious.

Thank you for an explanation!
Title: Re: foobar2000 v2.0 bugs
Post by: watcherhd on 2022-09-06 15:03:58
zip attached
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-09-06 15:22:32
Looks like Beta 4 has the album art column removed from the playlist view??

But I tested Beta3 and it displays just fine. (edit: I must be high, my console is showing Beta4 - I have another Beta4 install with no album art columns. I need a lie down :/ )

(https://i.imgur.com/ou09Pu5.png)

Sorry (not sorry) about the girly pop music.  ;D

another edit: no columns.

(https://i.imgur.com/wgv9C59.png)
Title: Re: foobar2000 v2.0 bugs
Post by: josemescud on 2022-09-07 11:58:07
The performance of version 2.0 is inadmissible. I don't know if it will be a problem of Columns UI or Foobar.

The problem appears when you have an external hard drive connected by USB. Mine has 5 tb of music

- If I have the external hard drive off and open foobar the tracks multiply continuously in the Playlist View (see image) and you cannot get well because it takes a long time to respond as the tracks multiply. You change to another artist and continue to multiply. In the Album List Panel the tracks appear correctly without multiplication.

- You have no choice but to plug the hard drive that had already been monitored the previous day. It takes to monitor 50 minutes. And until the monitoring ends any album that you put new on the hard disk the album list panel does not recognize it.

I have also experienced this problem in my wife's portatile and fails the same. So I think it's not difficult to check the problem by developers.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2022-09-07 13:36:41
@marc2k3 Not here.
Title: Re: foobar2000 v2.0 bugs
Post by: Brazil2 on 2022-09-07 13:43:04
Quote from: marc2k3 on
For windows store averse people or those on windows 7/8.1, you can get webp working by installing this...
https://storage.googleapis.com/downloads.webmproject.org/releases/webp/WebpCodecSetup.exe
Is there any similar link for HEIC ?
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-09-07 13:51:15
Quote from: grimes on
@marc2k3 Not here.

Yeah, like I said in my post, I had 2 installs running. One was fine, the other was not. I think somehow I inadvertently selected "Default Playlist" from the "Layout>Quick setup" dialog - I don't consciously remember doing it but choosing "Album art in playlist" restored the columns again. Odd.

I think the columns should be selectable regardless of which quick setup option you choose.
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-09-07 13:53:24
Quote from: Brazil2 on
Is there any similar link for HEIC ?

I don't think so. webp is very much a Google thing so that's why they've provided that for many years. HEIC support only comes in windows 10 and later via the store. Someone may correct me on that.

edit: I just googled "heic wic windows 7" and found this....

https://winaero.com/heif-heic-images-windows-10/

which links to this...

https://www.copytrans.net/copytransheic/

I'm not testing though.
Title: Re: foobar2000 v2.0 bugs
Post by: Brazil2 on 2022-09-07 14:10:01
Quote from: marc2k3 on
https://www.copytrans.net/copytransheic/
Yes, I've found the same. It's free for personal use and it seems to do the job for Windows HEIC integrated support.
Title: Re: foobar2000 v2.0 bugs
Post by: cheatfreak47 on 2022-09-07 17:08:05
Not 100% sure, but I seem to get crashes when moving around or resizing items on the toolbar, especially if I have toolbar visualizations are enabled. (specifically I usually use spectrum and oscilloscope).

I've pressed "send report" on such crashes a few times. Happened while remaking my usual layout on a fresh install, for now I've had to leave my toolbar visualizations disabled, but I figured I'd report it here in case it's not an issue that's been noticed.

on fb2k 2.0, 32-bit
Title: Re: foobar2000 v2.0 bugs
Post by: Bogozo on 2022-09-08 17:55:45
Lossless DTS files that aren't packed in Matroska are not playable with new built-in DTS decoder.
Title: Re: foobar2000 v2.0 bugs
Post by: metal_termite on 2022-09-09 04:54:57
I can't even get beta 3 or beta 4 running. Both crash immediately after the import process :/
Title: Re: foobar2000 v2.0 bugs
Post by: pulbitz on 2022-09-09 06:42:55
fb2k 2.0 UI responsive too slow.
I have about 400,000 items in my playlist, and from 260,000 onwards, pressing and holding the up/down arrow keys will teleport without seeing movement.
It also uses too much CPU.
Look at the captured video file.
My CPU has 12 threads so 8.3% utilization equals 100%.

2.0 beta 4 x64.mp4
https://file.io/AVC8SVxBKQYb

1.6.12.mp4
https://file.io/1th89wg8aSde
Title: Re: foobar2000 v2.0 bugs
Post by: varezhka on 2022-09-09 07:18:41
the design of the new spectrum in full-screen mode has become worse, the bars have become more unpleasantly blurry, the visual part has suffered!

fb2k v1.6.12: https://ic.pics.livejournal.com/serezhik_18/14264802/351148/351148_original.png
fb2k v2.0.b4 x64: https://ic.pics.livejournal.com/serezhik_18/14264802/351368/351368_original.png

Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-09-09 12:02:15
Beta 5 https://www.foobar2000.org/download
Quote
    Fixed various crash bugs.
    Improved rendering performance of very large playlists with grouping & album art enabled.
    Made ReFacets sorting remembered.
    Fixed inverted titles of "Add Files" vs "Open" dialogs.
    Reduced output reopen delay when input format (channel count etc) changes.
    Improved dark mode rendering of checkboxes.
    Suppressed library error log lines about folder.jpg etc inside archive files.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2022-09-09 12:10:47
Glitch in cover art in DUI playlist view: different size. fb2k 2.0 beta 5 (x64).
Title: Re: foobar2000 v2.0 bugs
Post by: AndreaT on 2022-09-09 12:56:36
About CPU usage increase of V2 beta 4 compared to FB 1.6 and V2 Alpha

Hello, the following notes just to seek for feedbacks / share my data in case others may have noticed the same CPU usage increase.

As I started testing FB v2 Alpha I did NOT notice any relevant CPU usage increase vs. previous v1.6.
Over the time I did not performe other comparison because I was not having performance problem, thereof I believe the CPU usage remained quite same until Beta 4.

As I installed Beta 4 I started noticing some CPU resource issue (to know that I am running a 32bit Win 10 old PC ... 2GHz 2 cores).
However, last time I made CPU check with v2 Alpha, with regular FLAC audio, I recorded 50% of CPU usage, while yesterday, with Bet 4, I had to record 80% of CPU usage.

Is it only me or also others have noticed this CPU usage increase?

Regards, Andrea
Title: Re: foobar2000 v2.0 bugs
Post by: The Link on 2022-09-09 13:00:04
Please test beta 5 which has fixes for high cpu usage.
Title: Re: foobar2000 v2.0 bugs
Post by: Chibisteven on 2022-09-09 13:31:57
Quote from: AndreaT on
Is it only me or also others have noticed this CPU usage increase?

I've noticed that 2.0 can stutter and struggle if the CPU is under a heavier load like running Stereo Tool in VST Wrapper being one of the more extreme things you can do.  I haven't observed any increases in CPU usages though as it remains about the same.  In lighter CPU loads remains about the same as before as well.

1,6.12 handles the same heavy CPU load being generated just fine without stutters or struggles.
Title: Re: foobar2000 v2.0 bugs
Post by: AndreaT on 2022-09-09 14:54:30
Quote from: The Link on
Please test beta 5 which has fixes for high cpu usage.

Thanks. I tested the new Beta 6 and it is somehow better than the Beta 4: approximatively 10% less CPU usage.
But I am still having big problems... I cannot play SACD anymore because running out of CPU power.

I have to investigate because no such kind of issues until recently (from Beta 4)...

All the best, Andrea
Title: Re: foobar2000 v2.0 bugs
Post by: cheatfreak47 on 2022-09-09 23:15:28
Quote from: cheatfreak47 on
Not 100% sure, but I seem to get crashes when moving around or resizing items on the toolbar, especially if I have toolbar visualizations are enabled. (specifically I usually use spectrum and oscilloscope).

I've pressed "send report" on such crashes a few times. Happened while remaking my usual layout on a fresh install, for now I've had to leave my toolbar visualizations disabled, but I figured I'd report it here in case it's not an issue that's been noticed.

on fb2k 2.0, 32-bit

Update on this problem, turns out these issues are likely due to MSI Afterburner and RivaTunerStatisticsServer trying to hook into the the program- so users of MSI Afterburner and RivaTuner, to fix this, you need to open RivaTuner's GUI and add foobar2000.exe to the application profile list, and set detection for it to "None" to prevent it from trying to hook into foobar2000s video buffers, which is what was leading to all of the crashes for whatever reason.

I probably should've noticed this sooner, but it just didn't occur to me that RivaTuner would be trying to hook Foobar2000 at all, since it never did before, I assume this is due to the shift from software to hardware rendering for the visualizations. I only caught onto it being a RivaTuner thing due to a random crash I had not even opening the foobar error reporter and instead dumping the error into Windows Reliability History, with the faulting module being "dxgi.dll" in Windows.
Title: Re: foobar2000 v2.0 bugs
Post by: anamorphic on 2022-09-10 04:05:23
Quote from: Snowknight26 on
  • Layout splitters can't be locked anymore (to prevent accidental panel resizing) in layout editing mode
    • 1.6 menu (https://www.stfcc.org/pics/i/ec8e395cc44de13d7951a9d746f63149.png)
    • 2.0 menu (https://www.stfcc.org/pics/i/adf67f6c20c04fb9c19b0289c4f78c54.png)
Man this one is a real nuisance. I hope this is not intended... because previously in another thread @Case wrote -

Quote from: Case on
Size locking is still there, see the various scale options. But you can't lock all sizes anymore, you have to pick which side of a splitter remains resizable.
The problem is the middle ones are not locked, they stay resizable. The "Scale left/right/top/bottom" options are fine in terms of not moving the splitters when the window dimensions change (I like that), but the splitter bars themselves can still be accidentally resized. And even worse with lots of splitters in play, rolling the mouse over the layout changes the mouse cursor to arrows constantly. <argh>

A single "Lock splitter" option (edit: to lock all panes at once) could still work together with the "Scale left/right/top/bottom" options - simply preventing the mouse cursor changing and accidental resizing. (It could be dimmed out with "Scale proportionally")

Please for the love of gods consider bringing back the option, Peter. Or Case, whisper in his ear. :D
Title: Re: foobar2000 v2.0 bugs
Post by: mudlord on 2022-09-10 09:49:51
Quote from: cheatfreak47 on
Quote from: cheatfreak47 on
Not 100% sure, but I seem to get crashes when moving around or resizing items on the toolbar, especially if I have toolbar visualizations are enabled. (specifically I usually use spectrum and oscilloscope).

I've pressed "send report" on such crashes a few times. Happened while remaking my usual layout on a fresh install, for now I've had to leave my toolbar visualizations disabled, but I figured I'd report it here in case it's not an issue that's been noticed.

on fb2k 2.0, 32-bit

Update on this problem, turns out these issues are likely due to MSI Afterburner and RivaTunerStatisticsServer trying to hook into the the program- so users of MSI Afterburner and RivaTuner, to fix this, you need to open RivaTuner's GUI and add foobar2000.exe to the application profile list, and set detection for it to "None" to prevent it from trying to hook into foobar2000s video buffers, which is what was leading to all of the crashes for whatever reason.

I probably should've noticed this sooner, but it just didn't occur to me that RivaTuner would be trying to hook Foobar2000 at all, since it never did before, I assume this is due to the shift from software to hardware rendering for the visualizations. I only caught onto it being a RivaTuner thing due to a random crash I had not even opening the foobar error reporter and instead dumping the error into Windows Reliability History, with the faulting module being "dxgi.dll" in Windows.

Visualizations now use Direct2D, which is in turn, built on DX10 infrastructure, such as dxgi.dll which exports functions needed to build the D2D instance.

Funny, I would have thought with a name associated with game cheating would know all about DLL hooking........
Title: Re: foobar2000 v2.0 bugs
Post by: killchain on 2022-09-10 13:33:07
Beta 6. Status bar appears empty - only volume icon is seen.

Tried removing the formatting, but it's still the same.
Title: Re: foobar2000 v2.0 bugs
Post by: johnhopfensperger on 2022-09-10 14:39:44
Beta2 through Beta6. I enter an exact song name into the search bar, but it finds no results.
Title: Re: foobar2000 v2.0 bugs
Post by: Squeller on 2022-09-10 16:33:29
Beta6 x64: Album Art in playlist forgets "Padding" and "Border" state after restart. Playlist columns forget their width.
Title: Re: foobar2000 v2.0 bugs
Post by: Brazil2 on 2022-09-10 17:16:33
In Defaut User Interface, System notification area options are gone ? Why ?
Minimize to notification area is a must have ;)
Title: Re: foobar2000 v2.0 bugs
Post by: fbuser on 2022-09-10 17:31:03
Quote from: Brazil2 on
In Defaut User Interface, System notification area options are gone ?
No.
Title: Re: foobar2000 v2.0 bugs
Post by: Vicas on 2022-09-10 19:26:36
Beta 6

Default User Interface - if an splitter with tabs is resized enough to appear horizontal scrollbar it is displayed in white color.
Title: Re: foobar2000 v2.0 bugs
Post by: Nordfinn on 2022-09-10 19:59:27
Don't know if this is a glitch or deliberate, but: Every 2.0 update has deleted some old components' .dll files (e.g., dolbyhph), even from the x86 components folder.  Have had to hunt them down and reload.   N.
Title: Re: foobar2000 v2.0 bugs
Post by: Brazil2 on 2022-09-11 01:42:15
Quote from: fbuser on
No.
https://hydrogenaud.io/index.php?action=dlattach;topic=122847.0;attach=23297;image
Thanks, I missed this submenu :-[
Title: Re: foobar2000 v2.0 bugs
Post by: cheatfreak47 on 2022-09-11 04:13:34
Quote from: mudlord on
Quote from: cheatfreak47 on
Quote from: cheatfreak47 on
Not 100% sure, but I seem to get crashes when moving around or resizing items on the toolbar, especially if I have toolbar visualizations are enabled. (specifically I usually use spectrum and oscilloscope).

I've pressed "send report" on such crashes a few times. Happened while remaking my usual layout on a fresh install, for now I've had to leave my toolbar visualizations disabled, but I figured I'd report it here in case it's not an issue that's been noticed.

on fb2k 2.0, 32-bit

Update on this problem, turns out these issues are likely due to MSI Afterburner and RivaTunerStatisticsServer trying to hook into the the program- so users of MSI Afterburner and RivaTuner, to fix this, you need to open RivaTuner's GUI and add foobar2000.exe to the application profile list, and set detection for it to "None" to prevent it from trying to hook into foobar2000s video buffers, which is what was leading to all of the crashes for whatever reason.

I probably should've noticed this sooner, but it just didn't occur to me that RivaTuner would be trying to hook Foobar2000 at all, since it never did before, I assume this is due to the shift from software to hardware rendering for the visualizations. I only caught onto it being a RivaTuner thing due to a random crash I had not even opening the foobar error reporter and instead dumping the error into Windows Reliability History, with the faulting module being "dxgi.dll" in Windows.

Visualizations now use Direct2D, which is in turn, built on DX10 infrastructure, such as dxgi.dll which exports functions needed to build the D2D instance.

Funny, I would have thought with a name associated with game cheating would know all about DLL hooking........

Ha, it's exactly that knowledge that tipped me off that it was RivaTuner, it was just surprising, because RivaTuner very rarely causes any problems just by it's hooking action on it's own, I think the actual cause is RivaTuner hooking every individual visualization on the main window and constantly rapidly rotating between them until it somehow corrupts the memory of the program or something like that.

I guess that's a worthwhile note though, Foobar2000 2.0+ and RivaTuner will not play nice with eachother.
Title: Re: foobar2000 v2.0 bugs
Post by: Chibisteven on 2022-09-11 05:24:30
Quote from: cheatfreak47 on
Quote from: mudlord on
Quote from: cheatfreak47 on
Quote from: cheatfreak47 on
Not 100% sure, but I seem to get crashes when moving around or resizing items on the toolbar, especially if I have toolbar visualizations are enabled. (specifically I usually use spectrum and oscilloscope).

I've pressed "send report" on such crashes a few times. Happened while remaking my usual layout on a fresh install, for now I've had to leave my toolbar visualizations disabled, but I figured I'd report it here in case it's not an issue that's been noticed.

on fb2k 2.0, 32-bit

Update on this problem, turns out these issues are likely due to MSI Afterburner and RivaTunerStatisticsServer trying to hook into the the program- so users of MSI Afterburner and RivaTuner, to fix this, you need to open RivaTuner's GUI and add foobar2000.exe to the application profile list, and set detection for it to "None" to prevent it from trying to hook into foobar2000s video buffers, which is what was leading to all of the crashes for whatever reason.

I probably should've noticed this sooner, but it just didn't occur to me that RivaTuner would be trying to hook Foobar2000 at all, since it never did before, I assume this is due to the shift from software to hardware rendering for the visualizations. I only caught onto it being a RivaTuner thing due to a random crash I had not even opening the foobar error reporter and instead dumping the error into Windows Reliability History, with the faulting module being "dxgi.dll" in Windows.

Visualizations now use Direct2D, which is in turn, built on DX10 infrastructure, such as dxgi.dll which exports functions needed to build the D2D instance.

Funny, I would have thought with a name associated with game cheating would know all about DLL hooking........

Ha, it's exactly that knowledge that tipped me off that it was RivaTuner, it was just surprising, because RivaTuner very rarely causes any problems just by it's hooking action on it's own, I think the actual cause is RivaTuner hooking every individual visualization on the main window and constantly rapidly rotating between them until it somehow corrupts the memory of the program or something like that.

I guess that's a worthwhile note though, Foobar2000 2.0+ and RivaTuner will not play nice with eachother.

"RivaTuner" sounds like a nice little program to give you that VAC ban you'll always wanted to have playing a Steam game (and those are delayed).  Please don't complain on the Counter-Strike forums either.  See enough of that stuff already.
Title: Re: foobar2000 v2.0 bugs
Post by: Sohl on 2022-09-11 06:04:09
Quote from: Chibisteven on
"RivaTuner" sounds like a nice little program to give you that VAC ban
Good thing Valve doesn't ban accounts for using hardware monitoring software.
Title: Re: foobar2000 v2.0 bugs
Post by: Case on 2022-09-11 06:19:20
Quote from: killchain on
Beta 6. Status bar appears empty - only volume icon is seen.
Your status bar appears bugged otherwise too. There should be numerical volume level after the volume icon. Do you perhaps run ui_hacks component or have you modified the bundled files?
If you can reproduce such issue on a clean portable install, then it's worth reporting. Or it might be worth reporting if you spend the time to figure out what component in your install causes it.
Title: Re: foobar2000 v2.0 bugs
Post by: Case on 2022-09-11 06:24:59
Quote from: johnhopfensperger on
Beta2 through Beta6. I enter an exact song name into the search bar, but it finds no results.
Can't replicate. Are the files you try to search in Media Library? What "search bar"? ReFacets' search, Library Search and Playlist Search all appear to function properly here.
Title: Re: foobar2000 v2.0 bugs
Post by: Case on 2022-09-11 06:26:56
Quote from: Nordfinn on
Don't know if this is a glitch or deliberate, but: Every 2.0 update has deleted some old components' .dll files (e.g., dolbyhph), even from the x86 components folder.  Have had to hunt them down and reload.
foobar2000 v2.0 nukes incorrectly installed components without questions. The 'components' directory inside main install dir is only for the bundled first party components. Nothing else has business being there and it will be nuked clean on each install or update.
Title: Re: foobar2000 v2.0 bugs
Post by: pulbitz on 2022-09-11 08:13:45
UI responsiveness in v2 is too slow, is this level originally expected?
I'm curious as I don't have any feedback regarding this.

https://hydrogenaud.io/index.php/topic,122857.0.html
https://hydrogenaud.io/index.php/topic,122847.msg1015262.html#msg1015262

It's too slow compared to v1, so it's inconvenient to use.

https://www.mediafire.com/file/fnr8qbwnowydld6/fb2k_1.6.12.mp4/file
https://www.mediafire.com/file/rr58m53apf36n9t/fb2k_2.0_beta_6.mp4/file
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-09-11 10:58:35
Quote from: Vicas on
Beta 6

Default User Interface - if an splitter with tabs is resized enough to appear horizontal scrollbar it is displayed in white color.

musicmusic has the same issue with Columns UI...

https://github.com/reupen/columns_ui/issues/544

I guess there's no official way to style them and no hacky workaround has been found either.

edit: seems like using windows 11 *might* fix it but it's a hateful piece of **** I cannot use.  :))
Title: Re: foobar2000 v2.0 bugs
Post by: pawel_na_a on 2022-09-11 17:34:34
Customize Buttons dialog is always in light mode.
Title: Re: foobar2000 v2.0 bugs
Post by: metal_termite on 2022-09-12 04:33:00
Menus (drop-down and context) have these odd white squares on the bottom corners. See attached image.
Title: Re: foobar2000 v2.0 bugs
Post by: metal_termite on 2022-09-12 04:55:02
Not a bug per se, but it would be nice if the tag sanitizer imported the user settings from the legacy version which it disables. I went to sanitize some tags and almost didn't notice it reset list of fields to retain.
Title: Re: foobar2000 v2.0 bugs
Post by: Nordfinn on 2022-09-13 13:19:01
f
Title: Re: foobar2000 v2.0 bugs
Post by: Nordfinn on 2022-09-13 13:21:57
Quote from: Case on
foobar2000 v2.0 nukes incorrectly installed components without questions. The 'components' directory inside main install dir is only for the bundled first party components. Nothing else has business being there and it will be nuked clean on each install or update.

Ok, but I confess I can't guess why that's necessary.  Even a simple, benign component like Timebomb (used all the time), which is still listed as an official component? What does "incorrectly installed"
 mean?
Title: Re: foobar2000 v2.0 bugs
Post by: Case on 2022-09-13 13:47:18
It has nothing to do with component simplicity. The components directory has been reserved for bundled components at least since foobar2000 v1.1.
I suppose you have never seen https://wiki.hydrogenaud.io/index.php?title=Foobar2000:How_to_install_a_component (https://wiki.hydrogenaud.io/index.php?title=Foobar2000:How_to_install_a_component). And with installed foobar2000 instance things are even simpler. Just double click the .fb2k-component file.
Title: Re: foobar2000 v2.0 bugs
Post by: Case on 2022-09-13 14:24:59
Quote from: pulbitz on
UI responsiveness in v2 is too slow, is this level originally expected?
I'm curious as I don't have any feedback regarding this.
Sorry, at least I initially assumed your bug reports are related to running old 1.0 components that are known to be slow. With the added details the issue was confirmed and fixed in beta 7.
Title: Re: foobar2000 v2.0 bugs
Post by: Alexander Ostuni on 2022-09-13 15:03:21
I don't know if that is related.
In Foobar 1.6 when I chose a genre in the first column in Facets all 6 following columns are updated in a fraction of a second.
In Foobar 2 b7 and all previous betas and using only reFacets when I chose a genre with many albums it takes nearly a second until the remaining columns are updated with the right entries.

32 bit portable install.
Title: Re: foobar2000 v2.0 bugs [playback-statitics]
Post by: BeLu on 2022-09-13 15:18:48
Maybe not a bug -   but an unpleasant feature:
As far as I see you can't switch off the newly integrated Playback Statistics functionality. So each time you play a file the the '%last-modified%' field is set to the LAST_PLAYED_TIMESTAMP - unless you generally activate "preserve creation/modification-time when retagging" (since vers 1.5). That makes no sense (playing a file should not count as a full-fledged modification of its tags). For me  playback statitics should be only an option - or statistics-retagging should not affect  modification time.
Title: Re: foobar2000 v2.0 bugs
Post by: pulbitz on 2022-09-13 17:27:51
Quote from: Case on
Quote from: pulbitz on
UI responsiveness in v2 is too slow, is this level originally expected?
I'm curious as I don't have any feedback regarding this.
Sorry, at least I initially assumed your bug reports are related to running old 1.0 components that are known to be slow. With the added details the issue was confirmed and fixed in beta 7.

Thanks! Fixed in beta 7.
Title: Re: foobar2000 v2.0 bugs
Post by: pulbitz on 2022-09-13 17:32:19
The process of creating playlists in v2.0 seems to be very inefficient.

Create playlist-*.fplite.new.tmp file -> change to playlist-*.fplite file

It seems to repeat this behavior over and over again. The problem is that there is a lot of writing to disk because this process repeats every few seconds until it's finished.

I tried adding 407,705 items to the playlist(media library rescan), and the created playlist file(.fplite) was only 31.2 MB, but 12.6 GB of disk write operation occurred during processing.
(This is my observation. This excludes .sqlite file writes performed by the system process by foobar2000. Only .fplite file writes performed by the foobar2000.exe process are counted.)
Title: Re: foobar2000 v2.0 bugs
Post by: Air KEN on 2022-09-14 04:55:40
foobar2000 v2.0 beta 7 32bit 64bit
Album List is case insensitive.
But when I send  to "Playlist Manager" it's not.
Case-sensitive Track items.

Thanks.
Title: Re: foobar2000 v2.0 bugs
Post by: Aliaksandr_by on 2022-09-14 06:50:56
foobar2000x64_beta7
the album list does not have all files
e.g. *.dfs (with plugin for playing)

the file
E:\MUSIC\Dire Straits\Dire Straits - Brothers In Arms - 1985(2021),(USA),DSF(tracks),(OC-9XMLf+MF(115)avb+Pio)\C1 Why Worry.dsf

was not viewed in the album list; but if I add by hand it will play

Title: Re: foobar2000 v2.0 bugs
Post by: Air KEN on 2022-09-14 07:49:18
Quote from: Air KEN on
foobar2000 v2.0 beta 7 32bit 64bit
Album List is case insensitive.
But when I send  to "Playlist Manager" it's not.
Case-sensitive Track items.

Thanks.
Media Library not working properly.
Album List and Playlist Manager not displaying correctly.
Title: Re: foobar2000 v2.0 bugs
Post by: AndreaT on 2022-09-14 20:04:58
FB v2 Beta 7, 32bit version, strange crashes

Hello, just to report to you these 2 cases:
1) After 4-5 minutes of a regular 44kHz 16bit FLAC the CPU usage went up to 99%, FB Beta 7 crashes, disappeared from the running task, but eventually CPU resources were not released: CPU usage remained 99%. I had to reboot the PC. Crash report generated and sent as usual.
2) After having paused Beta 7 for some time (almost 1h), on restart audio had problem, not smooth play, cuts, high CPU usage and, most strange thing, Foobar entry disappeared from the Task Manager list of running applications.
Putting FB on pause again, it popped-up again among the running tasks. Restarting it, it disappeared again. PC rebooted again. No crash report generated.
Regards, Andrea
Title: Re: foobar2000 v2.0 bugs
Post by: AndreaT on 2022-09-14 20:08:29
How to configure/customize Album Art View as it was in FB 1.6.x?

Hello, I am sorry, I cannot find anymore the option to customize/configure the Album Art View component.
In FB 1.6.x I was able to configure the front, back, cd and so on search file order and location (subfolder) using, e.g., "..\front.*".

How can do that with FB v2 ?

Thanks and regards, Andrea
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-09-14 20:53:15
File>Preferences>Display>Album art.  << original confusing answer

File>Preferences>Display. Look under Album Art in the right hand pane. It's not changed at all.
Title: Re: foobar2000 v2.0 bugs
Post by: AndreaT on 2022-09-14 21:11:30
Quote from: marc2k3 on
File>Preferences>Display>Album art. It's not changed at all.

Hi @marc2k3 , ... well... the problem is that I do NOT have that entry. Please give a look to the attached screenshot I took.
Thanks, Andrea
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-09-14 21:13:35
Sorry if the > was misleading implying it was a node. Just highlight Display.

(https://i.imgur.com/9fmwiJf.png)
Title: Re: foobar2000 v2.0 bugs
Post by: AndreaT on 2022-09-14 21:19:47
Hi @marc2k3 , thank you so much! I got it and, sorry, I was completely blind.
Regards, Andrea
Title: Re: foobar2000 v2.0 bugs
Post by: johnhopfensperger on 2022-09-14 23:25:43
Quote from: Case on
Quote from: johnhopfensperger on
Beta2 through Beta6. I enter an exact song name into the search bar, but it finds no results.
Can't replicate. Are the files you try to search in Media Library? What "search bar"? ReFacets' search, Library Search and Playlist Search all appear to function properly here.

I'm talking about Library Search.
I found out what's going on: The file has no title metadata, so its filename appears in foobar as the title.
It seems the old version of foobar could find the track by filename, but the new version cannot.
Title: Re: foobar2000 v2.0 bugs
Post by: Air KEN on 2022-09-15 10:54:34
Quote from: Air KEN on
foobar2000 v2.0 beta 7 32bit 64bit
Album List is case insensitive.
But when I send  to "Playlist Manager" it's not.
Case-sensitive Track items.

Thanks.

foobar2000 beta 8 x32/x64:
the problem is not solved yet.
correct is 91 (ReFacets)

https://i.imgur.com/wxTZwaW.png
https://i.imgur.com/Thx5Vsc.png
https://i.imgur.com/vas2Olo.png

Thanks.
Title: Re: foobar2000 v2.0 bugs
Post by: Akczht on 2022-09-15 12:08:47
Can we have a better Unicode alias for '/' , right now it's like this 'Fate⁄Stay Night' as you can see the alias for '/' covers the name of the album a little , recommendations - '/'   'Ⳇ'  '〳'  '᜵'   '∕ '   '⧸'
Title: Re: foobar2000 v2.0 bugs
Post by: Lesmo16 on 2022-09-15 12:23:41
Quote from: Lesmo16 on
The Layout Editing Mode can't be finished completely.
After switching it off the blue splitters indeed turn to grey ...
but even locked (the new method) splitters stay movable.
Since this isn't corrected until beta 8: Isn't this a bug?  :o
Title: Re: foobar2000 v2.0 bugs
Post by: Case on 2022-09-15 13:48:57
Quote from: Air KEN on
foobar2000 beta 8 x32/x64:
the problem is not solved yet.
correct is 91 (ReFacets)

https://i.imgur.com/wxTZwaW.png
https://i.imgur.com/Thx5Vsc.png
https://i.imgur.com/vas2Olo.png
I atleast do not understand what your problem report tries to say.

Quote from: Lesmo16 on
Quote from: Lesmo16 on
The Layout Editing Mode can't be finished completely.
After switching it off the blue splitters indeed turn to grey ...
but even locked (the new method) splitters stay movable.
Since this isn't corrected until beta 8: Isn't this a bug?  :o
That has nothing to do with layout editing mode. You can move the splitters even if you skip that part. That is how they currently work, Peter is aware of the request to restore old locking behavior. I can't comment if things will change.
Title: Re: foobar2000 v2.0 bugs
Post by: Case on 2022-09-15 14:09:47
Quote from: Akczht on
Can we have a better Unicode alias for '/' , right now it's like this 'Fate⁄Stay Night' as you can see the alias for '/' covers the name of the album a little , recommendations - '/'   'Ⳇ'  '〳'  '᜵'   '∕ '   '⧸'
It's only that way on Segoe UI as far as I can tell. The first replacement character you suggest is the actual forward slash that the replacement character replaces. That is an illegal character on Windows filesystems and can't be used.
Out of the suggestions '∕' is ok. It's actually a slash, the others are not and depending on the font they don't either show up at all or don't look like a slash.
Title: Re: foobar2000 v2.0 bugs
Post by: Air KEN on 2022-09-15 14:12:25
> I atleast do not understand what your problem report tries to say.
hahaha. sorry.

"Album List" is case insensitive (normal).
Sending to "Playlist Manager" displayed the combined number of uppercase and lowercase letters.
Not normal since Beta 7.

I have artistname "Taeyeon" and TAEYEON.
91 in total. Only uppercase numbers are displayed (20).
https://i.imgur.com/wxTZwaW.png
https://i.imgur.com/Thx5Vsc.png
https://i.imgur.com/vas2Olo.png
Title: Re: foobar2000 v2.0 bugs
Post by: Akczht on 2022-09-15 14:32:14
Quote from: Case on
Quote from: Akczht on
Can we have a better Unicode alias for '/' , right now it's like this 'Fate⁄Stay Night' as you can see the alias for '/' covers the name of the album a little , recommendations - '/'   'Ⳇ'  '〳'  '᜵'   '∕ '   '⧸'
It's only that way on Segoe UI as far as I can tell. The first replacement character you suggest is the actual forward slash that the replacement character replaces. That is an illegal character on Windows filesystems and can't be used.
Out of the suggestions '∕' is ok. It's actually a slash, the others are not and depending on the font they don't either show up at all or don't look like a slash.
I'm on an iPhone now , so the one you said was fine was the one that is in the current foobar2000 , I think this also looks 'Ⳇ' good , I am not to decide what is correct , so anything goes .
Title: Re: foobar2000 v2.0 bugs
Post by: Air KEN on 2022-09-15 16:51:30
"Album List" is case insensitive (normal).
Sending to "Playlist Manager" displayed the combined number of uppercase and lowercase letters.
Not normal since Beta 7.

I have artistname "Taeyeon" and TAEYEON.
91 in total. Only uppercase numbers are displayed (20).

https://i.imgur.com/wxTZwaW.png
https://i.imgur.com/Thx5Vsc.png
https://i.imgur.com/vas2Olo.png
--------
Prerferences > Media Library > Album List > Actions
Duble-click action: Send to New Playlist
Middle button action: Create Autoplaylist
The number sent to "Playlist Manager" is different.
Is this the default?

Not from foobar2000 v2.0 beta 7.
I don't know when.

Thanks,
Title: Re: foobar2000 v2.0 bugs
Post by: Akczht on 2022-09-15 17:23:14
a full width SOlidus "／" would be the best thing that should replace the current solidus

edit : just saw how it actually looks in windows 11 , the current selection of the lookalike for Solidus '/' , is all fine
Title: Re: foobar2000 v2.0 bugs
Post by: AndreaT on 2022-09-15 17:42:16
FB v2 Beta 8 not appearing in Task Manager among the running applications

Hello, I don't know if relevant, but in my Windows 10, 32bit, with all the new patches available as of today, as I updated from Beta 7 to Beta 8, FB v2 started running, and even played for over 1h but no "trace" of it in the Task Manager among the running applications (while it is playing audio).

Browsing all the items listed in Task Manager, no reference found for Foobar while it is really playing audio.
Stopping the audio stream / stopping Foobar play, then the Task Manager shows-up Foobar entry...

Anyway, no crash had. It is still working so... if you need a memory dump, let me know quickly

Cheers, Andrea
Title: Re: foobar2000 v2.0 bugs
Post by: sfman on 2022-09-15 17:44:15
Tags: Foobar doesn't see the difference between values "ALBUM ARTIST" and ALBUMARTIST.
When adding some value to ALBUMARTIST tag its appended to "ALBUM ARTIST" and ALBUMARTIST stays empty
Tag scheme I use: APE+ID3v1
Title: Re: foobar2000 v2.0 bugs
Post by: papavlos on 2022-09-15 18:55:02
beta 8, 32-bit, on Linux under wine:
Standard default Tabs "Playlists" and "Properties" are properly colored, according to currently selected colors scheme in View > Layout > Quick setup.
But additional UI Elements "Library" and "Console" do not follow the color scheme.
Title: Re: foobar2000 v2.0 bugs
Post by: Bogozo on 2022-09-15 19:44:22
Quote from: papavlos on
beta 8, 32-bit, on Linux under wine
Quote from: papavlos on
"Console" is always painted with system colors regardless of color scheme currently selected
On windows 7 it is the same.

Library tree also doesn't seem to look OK on windows 7.
(https://i.imgur.com/hWzyWjz.png)
Title: Re: foobar2000 v2.0 bugs
Post by: metal_termite on 2022-09-16 01:30:11
Beta 8 32-bit is yet another version that crashes after installation every time I try to start version 2. Again, deleting my playlist folder seems to solve the issue. Crash report has been submitted again.
Title: Re: foobar2000 v2.0 bugs
Post by: Lesmo16 on 2022-09-16 11:11:21
Quote from: Case on
Quote from: Lesmo16 on
Quote from: Lesmo16 on
The Layout Editing Mode can't be finished completely.
After switching it off the blue splitters indeed turn to grey ...
but even locked (the new method) splitters stay movable.
Since this isn't corrected until beta 8: Isn't this a bug?  :o
That has nothing to do with layout editing mode. You can move the splitters even if you skip that part. That is how they currently work, Peter is aware of the request to restore old locking behavior. I can't comment if things will change.
I support this request!
Title: dB on right edge truncated
Post by: Lesmo16 on 2022-09-16 11:15:45
Playback visualizations Spectrum, VU Meter and Peak Meter show the B of dB on the right edge truncated.
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-09-17 05:15:00
I'm not suggesting this for everyone but if anyone already uses scripting components like WSH panel mod, Spider Monkey Panel or JScript Panel, they can lock splitters by adding code inside a panel like this...

Code: [Select]
window.MinWidth = window.MaxWidth = 400;

Now I can't drag at all...

(https://i.imgur.com/9qsma9E.gif)
Title: Re: foobar2000 v2.0 bugs
Post by: pawel_na_a on 2022-09-17 12:18:20
[beta 8, Default UI, groups and album cover column enabled]
Unwanted scrolling when changing content (deleting items) of the playlist
Title: Re: foobar2000 v2.0 bugs
Post by: AndreaT on 2022-09-17 18:21:43
"Album Art View" not scanning sub-folders for images

Hello, in FB v1.6.x and older I was used to have Album Art View fetching images (like "folder.jpg" and the like) also from any subfolder of the played audio parent directory.

Now, in FB v2 I cannot have this. I tried and re-tried, but no way (for me) to have the subfolder scanned and the wanted images displayed (in my case I am searching for front.jpg and back.jpg.

Does anyone know how to fix my problem?

Thanks and regards, Andrea
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-09-17 19:14:30
It won't look there by default. You have to tell it. No change in behaviour.

(https://i.imgur.com/A29OcBc.png)
Title: Re: foobar2000 v2.0 bugs
Post by: Vicas on 2022-09-17 19:19:58
Quote from: AndreaT on
"Album Art View" not scanning sub-folders for images

Hello, in FB v1.6.x and older I was used to have Album Art View fetching images (like "folder.jpg" and the like) also from any subfolder of the played audio parent directory.

Now, in FB v2 I cannot have this. I tried and re-tried, but no way (for me) to have the subfolder scanned and the wanted images displayed (in my case I am searching for front.jpg and back.jpg.

Does anyone know how to fix my problem?

Thanks and regards, Andrea

Not a bug as it works for me.

To include sub-folder, in your case you should use ..\front.jpg and ..\back.jpg at front and back artwork configuration respectfully at Preferences / Display

Edit: This is for up folder
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-09-17 19:21:42
Quote from: Vicas on
To include sub-folder, in your case you should use ..\front.jpg and ..\back.jpg at front and back artwork configuration respectfully at Preferences / Display

You're going up a level - the complete opposite of a subfolder. ;D

edit: I'm doubting myself now. I was right, 2 periods goes up a folder.
Title: Re: foobar2000 v2.0 bugs
Post by: Vicas on 2022-09-17 19:43:06
Quote from: marc2k3 on

You're going up a level - the complete opposite of a subfolder. ;D

edit: I'm doubting myself now. I was right, 2 periods goes up a folder.


Indeed, I though sub but wrote for up folder. :D

Anyway it is not a bug just needs to be specified in artwork preferences.
Title: Re: foobar2000 v2.0 bugs
Post by: AndreaT on 2022-09-17 19:53:25
Hi @marc2k3 and all,

my big big big problem is that all the images are in subfolders having different names (:->), so I cannot specify a subfolder in the setting.

I tried with *\front.jpg and also with *.*\front.jpg and the like, but they were not working.

However, I remember well, 100% sure (even because I used FB 1.6 for over 10 years!) I was able to display all well with the v.1.6 of Album Art View.

I cannot believe to be only one having Album Arts in subfolders...
Anyone else here is having my same problem?

Thanks and regards, Andrea
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-09-17 20:10:05
I never knew wildcards were supported in folder names so that's something new I've learned today.

And this works in fb2k v2...

Code: [Select]
*\*.*

No image alongside the audio tracks but inside a random folder...

(https://i.imgur.com/pUb4qzC.png)

Note: Because of fb2k always caching album art for its own panel/playlist, you always have to restart after changing settings.
Title: Re: foobar2000 v2.0 bugs
Post by: Vicas on 2022-09-17 20:19:58
I have just tried and it worked for me too. Definitely not a bug.
For covers in sub folder I used *\front.jpg and *\back.jpg
Title: Re: foobar2000 v2.0 bugs
Post by: AndreaT on 2022-09-17 21:03:24
Hi @marc2k3 and @Vicas ,
I confirm that, now it works also for me (after a FB restart).
I don't know why it didn't work the first time... it may be it was requiring a restart
Thank you for your support. Kind regards, Andrea
Title: Re: foobar2000 v2.0 bugs
Post by: shalivan on 2022-09-17 22:11:12
Hi. I have problems with rating. Cannot set ratings for my library.
'edit properties' - with new tag: <RATING> set to '5' - dont show any stars in 'playlist view'
Title: Re: foobar2000 v2.0 bugs
Post by: metal_termite on 2022-09-17 23:02:03
Reinstalled beta 8, but deleted v1.6.x playlist folder first so foobar2000 v2 would not crash on importing the playlists.

Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-09-18 00:48:55
Quote from: shalivan on
Hi. I have problems with rating. Cannot set ratings for my library.
'edit properties' - with new tag: <RATING> set to '5' - dont show any stars in 'playlist view'

You'll need update any custom column to use $meta(rating) instead of %rating%.

Pretty sure the new clickable rating column is for playback statistics only, not file tags.
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-09-18 00:55:26
Quote from: metal_termite on
  • Beta 8 did not import any playback stats at all.

I'd assume you can export from a working 1.6 setup via the Library menu to an XML file and import the file via the Library menu in v2.

If you don't have a backup of your 1.6 install, look inside your profile folder for a folder named index-data - this contains playback stats from 1.6 (assuming it survived the upgrade??). You should be able to transfer that to a portable 1.6 install to get the data.
Title: Re: foobar2000 v2.0 bugs
Post by: windfr on 2022-09-18 08:24:25
Hi, I don't if it's a bug; 
With  version1.6 ,  with  Search  command,  when putting a  directory name, it was possible to get all the albums and tracks included in the directory and sub-directories.

It's not possible with version 2 .  Do we have to modifiy some script to get them ?
Title: Re: foobar2000 v2.0 bugs
Post by: ASopH on 2022-09-18 08:27:27
Hi,

I've tested %file_attributes% but there's nothing shown!
Title: Re: foobar2000 v2.0 bugs
Post by: stijneman on 2022-09-18 21:14:39
Thank you for rebuilding Facets, much appreciated! I'd like to share a few pieces of feedback.

Two potential bugs:

1. The ReFacets checkbox option "Start playback when sending selection to playlist" doesn't work in combination with ReFacets' Double-click action "Add to current playlist".

If I use those two together, the selection does get added to the playlist, but it doesn't start playing; I expect it to (it's actually how I prefer to use Foobar). The checkbox option does does work in combination with "Send to current playlist (default)" though.

2. In Preferences>Display, set Selection Viewers to "Prefer current selection". Then, in ReFacets, with the selection also present in the current playlist (let's say one album), click on a song with the left mouse button to select it. Nothing happens in the playlist.

Expected behavior: like in Facets, if I do those same actions, the active selection in the playlist follows what I select in Facets.

Aesthetics:

3. I can't unlock the toolbar (same as mentioned above).

4. ReFacets' search bar, compared to Facets, has an additional and unnecessary black/white 1px (?) border around it. See attached screenshot. It turns blue (same color as the volume switch) when searching something.

5. Refacts' buttons in the UI ("Library", "Filters") appear to be uncentered vertically, or otherwise need some more spacing below the strings. See attached screenshot.

6. The X-button to clear a search is very small, making it a bit harder to click compared to in Facets. See attached screenshot.

7. When mouse-hovering the X-button to clear a search, the mouse-hover animation is a white square.

No playlist related mods installed, portable fresh Foobar 2000 v2 b8 install.

Looking forward to using ReFacets for years to come! :) Hope this helps.
Title: Re: foobar2000 v2.0 bugs
Post by: stijneman on 2022-09-19 12:28:40
Quote from: stijneman on
(...)
Oops I forgot the attachment - can't seem to edit the post, here it is after all.
Title: Re: foobar2000 v2.0 bugs
Post by: ASopH on 2022-09-20 09:07:37
Hi,
Perhaps not a bug!
When searching the music folders, all files from unavailable drives are logged - wouldn't it be better to skip and not to record unavailable drives?
Title: Re: foobar2000 v2.0 bugs
Post by: ASopH on 2022-09-20 10:07:50
Hi, once again!

It happens, when scan is incomplete and foobar ist closed. Next open, all not scanned files are logged as error.
Title: Re: foobar2000 v2.0 bugs
Post by: metal_termite on 2022-09-22 17:09:52
Beta 9 fixed the crashing when importing v1.4 playlists.

Foobar2000 2.0 beta 9 x32
Windows 11 22H2 (22621.521)

foo_quicktagger 1.1 (2022-09-16)
- Preferences window doesn't completely honor Windows dark mode (See attached screenshot)

Properties dialog window
- Not sure if this is a bug per se but the font size on the tabs is larger than the other default font sizes in the rest of the ui. See attached screenshot for comparison between the tab font sizes on the foobar2000 properties dialog window and stock Windows 11 22H2 properties window.

Windows 11 (22H2) notification area
- There's a visual glitch. I'm not sure what text is supposed to be displayed in this area, but I doubt it's a path to the foobar2000.exe file. (See attached screenshot)
- The playback buttons do nothing when pressed
Title: Re: foobar2000 v2.0 bugs
Post by: metal_termite on 2022-09-22 20:37:41
Foobar2000 2.0 beta 9 32bit

Playback statistics

1. %rating_stars%. %rating_stars% displays the correct rating (solid stars) but an additional empty star is displayed. See below example where %rating% is 2. The left column displays the built-in playlist view rating, the right column displays [%rating_stars%].

(https://i.imgur.com/xsU0w4L.png)

However, this issue goes away if you update the track's %rating%.

2. Import statistics from file tags. This correctly imports playback statistics from tags, but where those statistics do not exist as tags, the database playback stats get reset. This is not how the feature worked in version 1.6. In 1.6 if the stats were not present in the tags, the database playback stats would not be reset.

3. %play_count%. %play_count% does not get incremented at all after a track is listened to.
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2022-09-22 20:54:36
Thanks for all the bug reports.

I read everything, just haven't had time to properly investigate all of them yet. All reported issues will be looked into before the final release. There are no deadlines here, the final version will be out when I'm confident that all annoying issues/regressions have been fixed.

Also, Quick Tagger = fixed.
Title: Re: foobar2000 v2.0 bugs
Post by: Valetos2 on 2022-09-22 21:06:02
Tried to update to v2.0 (x86 so far). The installer says that since the install directory contains configuration data, but foobar2000 is not using portable mode, this is no longer supported in v2.0.

I've checked the Roaming folder -- it doesn't have anything newer than 2015. Seems someday I managed to keep both program, plugins and configs in the same folder somehow, which was probably useful.

What should I move to %appdata%\roaming\foobar2000 to make it "unportable" but still working with all configs?

X
Title: Re: foobar2000 v2.0 bugs
Post by: pawel_na_a on 2022-09-22 21:15:06
(beta 9)
Title: Re: foobar2000 v2.0 bugs
Post by: metal_termite on 2022-09-22 21:50:35
Foobar2000 2.0 beta 9 32bit

Playlist view
1. Custom column sizes and positions for views marked remember layout for this playlist are not persistent between sessions, nor when switching between playlists. The column sizes/positions will just reset.

2. The built-in clickable rating stars that essentially display %rating_stars_fixed% are visually difficult to discern. There isn't much contrast between the solid stars (★) and outlined stars (☆) so the rating column just looks like a massive block of stars and the actual ratings are difficult to distinguish. I'd strongly suggest making the outlined stars (☆) a dimmer color than the solid stars (★) as foo_simplaylist did, such as <<<☆>>> or add the ability to let the end-user customize the colors for solid and outlined stars.

foo_plorg
Obviously not a core Foobar2000 issue, but the playlist often auto-scrolls up or down whenever focus leaves the component and there's mouse movement  on another component 🥴. I would put up with the lack of dark mode but it's just not as usable on fb2k v2 with this auto-scrolling glitch unfortunately. I'm sure this third-party component is now abandoned, and I'm only mentioning it because it would be great if the maintained DUI playlist manager incorporated the use of custom nodes/leafs with drag-and-drop sorting of nodes/playlists for better organization of playlists.
Title: Re: foobar2000 v2.0 bugs
Post by: Chibisteven on 2022-09-22 21:57:13
Quote from: Valetos2 on
Tried to update to v2.0 (x86 so far). The installer says that since the install directory contains configuration data, but foobar2000 is not using portable mode, this is no longer supported in v2.0.

I've checked the Roaming folder -- it doesn't have anything newer than 2015. Seems someday I managed to keep both program, plugins and configs in the same folder somehow, which was probably useful.

What should I move to %appdata%\roaming\foobar2000 to make it "unportable" but still working with all configs?

[attach type=image]23418[/attach]
Move these to "%appdata%\roaming\foobar2000"
Folders: "AccurateRip", "configuration", "index-data", "library", "playlists", "playlists-v1.3", "playlists-v1.4", "user-components"
Files: "LargeFieldsConfig.txt", "theme.fth", "version.txt"

Make sure you have no nonbundled components installed in the "components" folder.  You can run an older installer such as 1.6.12 and have it move components for you.  However you may lose some components that the installer won't move, it will list them so you can attempt to manually move them, once you hit "OK" it'll delate those if you haven't move them.  You can manually move components the installer doesn't like into "user-components" directory by using the name of said component as the folder name and dropping the component and all of it's dependencies in it.  It's tedious process but one that isn't too difficult to do.
Title: Re: foobar2000 v2.0 bugs
Post by: fmcuu on 2022-09-23 07:13:55
Comparing with 1.6 - version 2.0 can not add multiple folders using "Add folder..."
Dunno if this was said before, or may be there is another way to add more than one folder at once?
Title: Re: foobar2000 v2.0 bugs
Post by: ASopH on 2022-09-23 14:42:39
Hi, The Music CD Writer Component:
A little confused
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2022-09-23 15:04:38
foobar2000 v2.0 beta 9 (x64): Visualization Spectrogram interrupted after 1 min (Playback Statistics).
Is this normal? What can I do?


Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-09-23 17:16:13
If playback stats is set to write file tags at the same time, it's probably normal. I wouldn't expect it if just using the internal DB.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2022-09-23 17:27:13
Same problem after deactivating save to file tags.
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-09-23 17:39:49
Cannot reproduce. I tested just now and there was no gap. Maybe you've messed with your buffer settings? The default is 1000ms under Preferences>Playback>Output.
Title: Re: foobar2000 v2.0 bugs
Post by: TuNk77 on 2022-09-23 18:09:36
Exporting playback statistics from foobar2000 v2 and then importing to foobar2000 v 1.6.12 does not work, I just get the following error:
Playback statistics import failure: Unsupported format or corrupted file
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-09-23 18:44:59
It's expected as the data is now bound to file path in v2. With foo_playcount, it was a combination of tags. They are not compatible.
Title: Re: foobar2000 v2.0 bugs
Post by: TuNk77 on 2022-09-23 20:08:38
Thank you for clarifying, marc2k3  :)

I think I found a bug in the albumlist, used in DUI, I have music on two separate HDD's, when I type "D:\" in the searchfilter, I get zero results, but in foobar2000 1.6.12, it works as expected
Title: Re: foobar2000 v2.0 bugs
Post by: Newron on 2022-09-23 20:43:11
beta 10

@ReFacets:

Added multiple albums and noticed that sorting in playlist is mixed up (albums torn apart) and does not reflect ReFacets sorting.
("Works" with Library Viewer and Drag & Drop)

Seems like files are added to playlist sorted by file creation date.

On a side note:
Is implementation of cover art planned for ReFacets? (Maybe after 2.0 is out?)
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2022-09-23 21:57:02
Problem solved with removing JS Smooth Browser (JScript Panel 3.1.0).
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-09-23 22:08:27
Quote from: grimes on
Problem solved with removing JS Smooth Browser (JScript Panel 3.1.0).

Yeah, it sees DB updates the same as tag updates which isn't right. I can fix that but it will take component changes in the next release.

edit: this might be trickier than I first thought. There is a callback for library items being changed too which isn't as easy to suppress. I'll look in to it.
Title: Re: foobar2000 v2.0 bugs
Post by: Sashka78 on 2022-09-24 13:09:33
1. Auto-scale Columns with Window Size doesn't work in the Default User Interface.
2. Columns size changes in Properties (if it's a tab in a Default User Interface element) are not remembered when changing tracks.
Title: Re: foobar2000 v2.0 bugs
Post by: metal_termite on 2022-09-24 20:39:12
Beta 10 32-bit on Windows 11 22H2

My DUI fonts are all the default settings. It's not unusual that when applying edits in Layout Editing Mode the font is changed. Unfortunately I cannot find a pattern to duplicate this issue on-demand. Changing the font in the preferences dialog and then resetting the fonts fixes the issue.
Title: Re: foobar2000 v2.0 bugs
Post by: hamybal on 2022-09-25 00:05:48
Foobar v2 32-bit beta 10
Foobar v2 portable and default installation on startup is taking up to 15-25 seconds before fully loaded where as v1 takes 4-10 seconds and in general everything goes slower but can't really give anything about it because there's nothing in the console about it.

Replacing a comma with semicolon in %artist% is instead of showing a comma in playlist view it's showing a semicolon, while if you mannually replace it it will change into a comma in playlist view. It can be do with mp3tag but prefer it with foobar

Refacets
Most of the time it's just not working or it takes 30+ seconds upon using search, with a smaller library it ofcourse goes a bit faster but still not optimal, both default and portable.
In fb v1 facets you could right click enable/disable "library, filters, source, help" would like to see that again.
Would also like album art view to make a comeback.

Not a bug
with fb v1 you could lock left/rights borders in DUI layout editing which is really usefull because you lock some while still be able to move others, hopefully this makes a comeback aswell.

File operation/Move to/... replacing characters in filenames
Could it be made possible to be able to replace these "| /" to "│ ／, the replacements can be done manually but not through foobar.
But these ": ? < > " for some reason can be replaced to "꞉ ？ ＜ ＞" while it should be having the same problem.

Thanks to all developers for all your efforts in creating an even better foobar it's really appreciated, have a wonderful day/night!
Title: Re: foobar2000 v2.0 bugs
Post by: metal_termite on 2022-09-25 00:14:35
Quote from: metal_termite on
1. %rating_stars%. %rating_stars% displays the correct rating (solid stars) but an additional empty star is displayed. See below example where %rating% is 2. The left column displays the built-in playlist view rating, the right column displays [%rating_stars%].

Just playing around with the beta again. More insight here into the above issue. All tracks that were imported from version 1.6.x now have a fractional %rating% except if the %rating% was 5. See the table below.

Playback statistics %rating% before and after installing version 2 beta:
v1.6.xv2
11.5
22.5
33.5
44.5
55
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2022-09-25 17:25:36
Beta 10, Win 11: Crash after component installation during restart. Crash report submitted.
Title: Re: foobar2000 v2.0 bugs
Post by: edogawaconan on 2022-09-26 12:46:23
Beta 10: Media Library Search of "NOT somefield IS 1 AND NOT someotherfield IS 1" now gives empty result. The logical equivalent "NOT (somefield IS 1 OR someotherfield IS 1)" works as expected.

Doesn't happen on Beta 8. Playlist search also not affected.

I played around a bit more and it looks like the resulting logic is "somefield IS 1 AND someotherfield IS 1" (which in my previous test happened to match nothing)

(https://s.myconan.tk/2022-09/foobar2000_2022-09-26_21-00-27.png)
Title: Re: foobar2000 v2.0 bugs
Post by: RetroComp on 2022-09-26 21:14:15
There appears to be a freezing problem with the "Album List" UI Element... when I add my library on my desktop it always freezes the entire UI when the Album list tries to update after some time. music keeps playing, at least for a little bit. and it continues to scan and read the network? but even leaving it like this for a day it does not fix itself. (I have about 300,000 tracks living on network storage, fwiw)

if I cut the element out, add in my library, let it scan, and add the element back in, all is fine. but it seems like there's possibly some race condition I am encountering from the initial add
Title: Re: foobar2000 v2.0 bugs
Post by: ASopH on 2022-09-27 17:27:46
Hi,

I've been missing SUBITEMS from Statistics (facets)  in ReFacets - any chance to implement it?  ;)
Title: Re: foobar2000 v2.0 bugs
Post by: xsdaver on 2022-09-27 19:54:06
Folders with dsf files do not show up in the album list.  So if you have the same album in redbook as flac and DSD as dsf files in two separate directories only the redbook directory shows up in the album list.  The dsf files play fine when dragged into the playlist from Windows Explorer.  I do have foo_input_sacd installed, which I assume is required for the files to play.
Title: Re: foobar2000 v2.0 bugs
Post by: edogawaconan on 2022-09-27 20:34:17
I don't know if it's intended, in 1.6.x I can ctrl-f (on playlist) -> type thing -> press enter to play the first hit but I can't do that anymore in beta 10.
Title: Re: foobar2000 v2.0 bugs
Post by: xsdaver on 2022-09-28 13:07:44
I have (at least) one album that verifies accurate with AccurateRip but when checked with verify integrity it fails.  The 32 bit version says the files are OK if I verify integrity.
Title: Re: foobar2000 v2.0 bugs
Post by: Squeller on 2022-09-28 13:35:46
Beta 10 crash when ext. CUE points to non-existing file.
Title: Re: foobar2000 v2.0 bugs
Post by: xsdaver on 2022-09-28 13:49:41
I use a script to group files with the word Classical in the genre tag by composer.  In the 32 bit version of foobar it looks like this:

(https://www.lakeb.com/images/bruch32.jpg)

In the 64 bit version of foobar it looks like this:

(https://www.lakeb.com/images/bruch64.jpg)

Exact same script (Note:  I put certain classical albums that are a pain in the a** to tag in a tree names Classical - PITA, subd is a tag I created to put some works by some composers in to sub categories):

Code: [Select]
$ifgreater($strstr(%path%,'PITA'),0,,__$ifgreater($strstr(%genre%,'Classical'),0,___|___$puts(comp3,)___$ifgreater($strchr(%composer%,','),0,____$puts(comp,$left(%composer%,$sub($strstr(%composer%,', '),1)))____$puts(comp2,' +' $trim($right(%composer%,$sub($len(%composer%),$strstr(%composer%,', ')))))____$puts(comp3,' '), ____$ifgreater($strchr(%composer%,'&'),0,_____$puts(comp,$left(%composer%,$sub($strstr(%composer%,' & '),1)))_____$puts(comp2,' & ' $trim($right(%composer%,$sub($len(%composer%),$strstr(%composer%,'&'))))),_____$puts(comp,%composer%)_____$puts(comp2,' ')))____$ifgreater($strchr($get(comp2),'+'),0,____$get(comp3) $left($right($get(comp),$sub($len($get(comp)),$strrchr($get(comp),' '))),1) ' 3 Or More Names',____$get(comp3) $left($right($get(comp),$sub($len($get(comp)),$strrchr($get(comp),' '))),1))___|___$trim($right($get(comp),$sub($len($get(comp)),$strrchr($get(comp),' '))))', '$trim($left($get(comp),$sub($strrchr($get(comp),' '),1)))___$get(comp2)___|___$if($meta_test(subd),____> $meta(subd)|)___$if($greater($strstr(%title%,' - '),0),$trim($substr(%title%,1,$sub($strstr(%title%,' - '),1))),%title%)|%artist% > %album%|%track% - %title%,)__)
Title: Re: foobar2000 v2.0 bugs
Post by: InverseDecay on 2022-09-28 19:44:52
beta8 and beta10 (at least) will no longer search the filepath in media library search by default, you now need to specify "%path% HAS .."
Title: Re: foobar2000 v2.0 bugs
Post by: AndreaT on 2022-09-29 12:56:55
External HDDs are disconnected quite often

Hello, I don't know if a bug or my only problem, but I have noted that with the last betas of FB v2, my external HDDs (4 USB 3.0 units) are quite often disconnected.
Time to time it also happens that a disconnected unit is not automatically re-connected: I have then to manually remove and re-attach the USB cable.
Regards, Andrea
Title: Re: foobar2000 v2.0 bugs
Post by: Slayer Moon on 2022-09-29 17:08:30
I think those are not have to have such a big font?
Title: Re: foobar2000 v2.0 bugs
Post by: josemescud on 2022-10-01 10:41:29
Quote from: Slayer Moon on
I think those are not have to have such a big font?


If you mean the titles you indicate in red I think they cannot be modified.
You can only modify the source for metadata.

Title: Re: foobar2000 v2.0 bugs
Post by: Slayer Moon on 2022-10-01 13:32:02
Quote from: josemescud
If you mean the titles you indicate in red I think they cannot be modified.
You can only modify the source for metadata.
Yep this is what i meant. Weird we can't modify the size of this dont. Why it is suppose to be a bigger than other fonts?
Title: Re: foobar2000 v2.0 bugs
Post by: NorthGraves on 2022-10-03 00:39:15
Beta 10:
Selecting several files in Directory Opus and hitting Enter briefly shows them in the playlist one by one, and only retains the very last file and start playing it.

1.6.12 - works fine - selecting several files in Directory Opus and hitting Enter shows them all in foobar2000 and starts playing the very first one.

If instead of hitting Enter - right clicking and selecting "Open in foobar2000" in the context menu - works fine in beta 10 - shows them all in foobar2000 and starts playing the very first one.
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2022-10-06 13:07:53
Note about beta 11,

I wasn't even going to make a new beta this week, but I figured out a solution for a random shutdown crash issue that gets auto-reported a lot, I really want to know if the solution works.

Beta 11 doesn't address all issues known to me at the moment. Expect a thorough cleanup of remaining issues sometime next month. Until then, keep the reports coming and thanks for all the feedback so far.
Title: Re: foobar2000 v2.0 bugs
Post by: metal_termite on 2022-10-08 01:55:41
Can anyone else confirm if the playback statistics' %rating% values are misreported after installing version 2 (now beta 11)? Or is this just happening to me?

In the case that it might be a bug specific to me I am including two attachments. The XML playback statistics export of the same track from v1.6.12 and from v2b11. On v1.6 the %rating% is 3, and on v2b11 the %rating% is reported as 3.5.
Title: Re: foobar2000 v2.0 bugs
Post by: pulbitz on 2022-10-09 07:37:52
When I open the console window, I often get a "database is locked" error. It occurs when foobar2000 is loaded. And while I can't be specific, it often happens when I try to play a particular file.
There seems to be a delay in the operation of foobar2000 when this DB error occurs.

Code: [Select]
Components loaded in: 0:00.011037
Configuration read in: 0:00.001171
foobar2000 v2.0 beta 11+log x64 [standard]
Playlist #0 loaded in 0:00.159534
User Interface initialized in: 0:00.386367
FFmpeg version: 5.1
Loading foo_discogger
foo_discogger: http_client service ready
Startup time : 0:00.478256
Watching: D:\Music
Library initialized after 0:02.441319
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid, playCount, dateAdded, lastPlayed, firstPlayed, rating FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid, playCount, dateAdded, lastPlayed, firstPlayed, rating FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid, playCount, dateAdded, lastPlayed, firstPlayed, rating FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid, playCount, dateAdded, lastPlayed, firstPlayed, rating FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid, playCount, dateAdded, lastPlayed, firstPlayed, rating FROM metadb WHERE name = ?
database is locked
Title: Re: foobar2000 v2.0 bugs
Post by: Squeller on 2022-10-09 09:43:13
Album List. View is "By folder structure". In a folder, which has many single files, every file with its own embedded art. Folder holds no art file. Clicking the first file, it shows its art in playlist view. On clicking subsequent files, it does not refresh art. Screenshot related. fb2k2x64 beta 11
X

Quote from: Slayer Moon on
Yep this is what i meant. Weird we can't modify the size of this dont. Why it is suppose to be a bigger than other fonts?

Noticed it as well.
Title: Re: foobar2000 v2.0 bugs
Post by: AndreaT on 2022-10-12 19:24:14
Beta 12 - High CPU usage on my old 32bit Windows 10 fully patched

Hello, I am sorry I didn't extensively tested beta 11, however, this new Beta 12 along with the last Windows 10 updates (I don't know which one is the main responsible) make my old 32bit Windows 10 PC unusable.
Over 80% of CPU usage reported and continuous audio cuts and whistles (also updated Behringer UMC ASIO driver).

Regards, Andrea

Title: Re: foobar2000 v2.0 bugs
Post by: Gus. on 2022-10-12 19:56:32
Quote from: AndreaT on
Beta 12 - High CPU usage on my old 32bit Windows 10 fully patched

Hello, I am sorry I didn't extensively tested beta 11, however, this new Beta 12 along with the last Windows 10 updates (I don't know which one is the main responsible) make my old 32bit Windows 10 PC unusable.
Over 80% of CPU usage reported and continuous audio cuts and whistles (also updated Behringer UMC ASIO driver).

Regards, Andrea


If you are using ASIO as output, first try these 3 components:
Official: https://www.foobar2000.org/components/view/foo_out_asio
Unofficial: https://sourceforge.net/projects/sacddecoder/files/foo_out_asio%2Bdsd/
Unofficial: https://sourceforge.net/projects/foobar2000-wasap2-output/files/
It could be a driver or output issue. Have you also tried the Default outputs (WASAPI shared and exclusive)?
Title: Re: foobar2000 v2.0 bugs
Post by: imeric on 2022-10-13 00:55:54
SACD DSD files did not get imported on upgrade
Title: Re: foobar2000 v2.0 bugs
Post by: Chibisteven on 2022-10-13 02:12:00
Quote from: AndreaT on
Beta 12 - High CPU usage on my old 32bit Windows 10 fully patched

Hello, I am sorry I didn't extensively tested beta 11, however, this new Beta 12 along with the last Windows 10 updates (I don't know which one is the main responsible) make my old 32bit Windows 10 PC unusable.
Over 80% of CPU usage reported and continuous audio cuts and whistles (also updated Behringer UMC ASIO driver).

Regards, Andrea

What CPU does your computer use?

The 32-bit build of foobaf2000 v2.0 runs fine for me on my Windows 10 Professional x64 machine using my Intel Core i5 7500.  CPU usage is about 0% average playing FLAC with about spike to about 1-3% from time-to-time.  WavPack being slightly more demanding at 0.5% average.  All considered normal on my end.  And that's with the normal DSP usage for me as well.
Title: Re: foobar2000 v2.0 bugs
Post by: AndreaT on 2022-10-13 18:17:19
Quote from: AndreaT on
Beta 12 - High CPU usage on my old 32bit Windows 10 fully patched

Hello, I am sorry I didn't extensively tested beta 11, however, this new Beta 12 along with the last Windows 10 updates (I don't know which one is the main responsible) make my old 32bit Windows 10 PC unusable.
Over 80% of CPU usage reported and continuous audio cuts and whistles (also updated Behringer UMC ASIO driver).

Regards, Andrea




Hello @Gus., @Chibisteven , I think the problem was not completely due to Foobar v2.
I rebooted the PC and the CPU load went down by itself. Probably something was leftover from the previous MS Win update.

Moreover, I found that my buffering settings were all 0. Thereof I set these to my so far used sizes (see attached).

Doing so, Foobar v2 can now play smoothly comparable with previous v1.6.
Due to my quite demanding audio setup and relatively low performance 32bit PC, the CPU usage is so:
- 44kHz 16bit FLAC => 50% CPU
- SACD ISO => 70% CPU
This is fine for me now. I can play anything.

If anyone has / knows a better/optimal Buffer setting, please let me know.

Thanks for your support
Regards, Andrea
Title: Re: foobar2000 v2.0 bugs
Post by: Chibisteven on 2022-10-14 07:00:45
Quote from: AndreaT on
Quote from: AndreaT on
Beta 12 - High CPU usage on my old 32bit Windows 10 fully patched

Hello, I am sorry I didn't extensively tested beta 11, however, this new Beta 12 along with the last Windows 10 updates (I don't know which one is the main responsible) make my old 32bit Windows 10 PC unusable.
Over 80% of CPU usage reported and continuous audio cuts and whistles (also updated Behringer UMC ASIO driver).

Regards, Andrea




Hello @Gus., @Chibisteven , I think the problem was not completely due to Foobar v2.
I rebooted the PC and the CPU load went down by itself. Probably something was leftover from the previous MS Win update.

Moreover, I found that my buffering settings were all 0. Thereof I set these to my so far used sizes (see attached).

Doing so, Foobar v2 can now play smoothly comparable with previous v1.6.
Due to my quite demanding audio setup and relatively low performance 32bit PC, the CPU usage is so:
- 44kHz 16bit FLAC => 50% CPU
- SACD ISO => 70% CPU
This is fine for me now. I can play anything.

If anyone has / knows a better/optimal Buffer setting, please let me know.

Thanks for your support
Regards, Andrea

I find that leaving the file buffering at defaults is best.  Output buffer usually has more impact against drop outs as everything has time to be fully processed through the whole foobar2000 chain, especially on really old, slow computers, on more modern, faster ones like mine it makes no difference at all where things are set but can provide some protection if a mechanical hard drive is put under a continuous heavy load.

The network buffering might be fine to adjust if your internet connection isn't very stable but I leave the file buffering at it's defaults.

I switch between 1 and 30 seconds depending on what I'm doing.  If I'm playing a whole playlist nonstop then exclusive mode works best so I set it to 30 seconds and leave it running.  Otherwise I use shared mode with 1 second as it's much more responsive when making changes in the DSP area for example as I don't have to wait long for changes to take effect.

As for your settings: Change your full file buffering to 0 KB.  500 MB will put a huge load on your CPU and consume a large amount of RAM.  Instead adjust only the read ahead until it plays smoothly or increase the output buffer.
Title: Re: foobar2000 v2.0 bugs
Post by: chicky on 2022-10-14 07:15:24
still can't search any songs in playlist
Title: Re: foobar2000 v2.0 bugs
Post by: AndreaT on 2022-10-14 20:42:43
Beta 12 - Cannot play (certain) WMA files

Hello, thanking all who supported me with my others issues, I am here again reporting that I have problems with certain WMA files.

I get the error "Unable to open item for playback (24-bit WMA Lossless decoding is broken on Windows 10, use foo_input_ffmpeg to decode this file): "xxxx.wma"

Now, the problem is that even with foo_input_ffmpeg these files cannot be played, while other players like the same Windows 10 Groove and JRiver MC29 can play without problems.

In my FB v2 I have installed obviously also the default FFmpeg decoder foo_input_std v5.1

Regards, Andrea
Title: Re: foobar2000 v2.0 bugs
Post by: Bogozo on 2022-10-14 20:58:09
Quote from: AndreaT on
Now, the problem is that even with foo_input_ffmpeg these files cannot be played
And what exactly is happening when you try to play them with foo_input_ffmpeg? Also, show your foo_input_ffmpeg settings.
Title: Re: foobar2000 v2.0 bugs
Post by: AndreaT on 2022-10-14 21:05:06
Quote from: Bogozo on
Quote from: AndreaT on
Now, the problem is that even with foo_input_ffmpeg these files cannot be played
And what exactly is happening when you try to play them with foo_input_ffmpeg? Also, show your foo_input_ffmpeg settings.

Hello @Bogozo , I did not configure foo_input_ffmpeg, I am sorry, I do not have any "external" decoder. I just tryed to install to check if it was just the matter to have it missing. In the past I never used it.

So, I relly do not know why FB v2 doesn't play my WMA.

If you have suggestion/instruction to use foo_input_ffmpeg, please give me step-by-step direction.

Thanks and regards, Andrea
Title: Re: foobar2000 v2.0 bugs
Post by: Gus. on 2022-10-14 21:06:45
Did you put ffmpeg.exe and ffprobe.exe in the root of the foobar folder?
https://github.com/GyanD/codexffmpeg/releases

The other players use DirectShow and Windows Media Foundation, which foobar does not.
Title: Re: foobar2000 v2.0 bugs
Post by: AndreaT on 2022-10-14 21:31:26
Quote from: Gus. on
Did you put ffmpeg.exe and ffprobe.exe in the root of the foobar folder?
https://github.com/GyanD/codexffmpeg/releases/tag/5.1.2

The other players use DirectShow and Windows Media Foundation, which foobar does not.

Hello @Gus., I downloaded both full_build and full_build_shared. Copied in ProgramFiles, then set FB v2 FFmpeg config to point to these directory (one at a time), ticked also WMA association.

Nothing out. FB v2 reoports "Unable to open item for playback (Could not start the decoder: could not start the worker process):..."

In attachment my FFmpeg configuration.

Kind regards, Andrea
Title: Re: foobar2000 v2.0 bugs
Post by: Gus. on 2022-10-14 21:39:09
I'm guessing FFMPEG doesn't support the format because no one uses it, even Microsoft, and maybe because of the license. Either way, I've never come across a sample to check if it plays or how.
Title: Re: foobar2000 v2.0 bugs
Post by: sveakul on 2022-10-14 22:20:55
I tried converting a 16-bit FLAC to a 24-bit WMA Lossless using WMAEncode64.exe with the options:

--silent --codec lossless --out-bitdepth 24 - %d

The resulting file will not play in either Foobar v1 or v2 resulting in the same error message as AndreaT about needing foo_input_ffmpeg.  I did not add that plugin to try, but noted that the file will play fine in both MusicBee and AIMP which use the bass_wma.dll as a plugin.  Forcing both to use system codecs resulted in no-play.  Windows 10 21H2 x64.

Edit:  forgot to add that Window Media Payer is not "activated" on my system, which may explain the no-plays when AIMP and MusicBee were forced to use system codecs.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2022-10-14 22:59:47
Ratings are not displayed properly. Track shows 4, context menu 5 and Properties 4.5. 4.5 was the result of conversion from 1.6.12 to 2.0, should be 4
Title: Re: foobar2000 v2.0 bugs
Post by: Bogozo on 2022-10-15 00:08:44
Quote from: AndreaT on
FB v2 reoports "Unable to open item for playback (Could not start the decoder: could not start the worker process):..."
Maybe your windows is blocking ffmpeg.exe/ffprobe.exe somehow. You know, there is such thing in windows: "This File Came From Another Computer And Might be Blocked to help protect this computer"

Quote from: Gus. on
I'm guessing FFMPEG doesn't support the format
Your guess is wrong.

For those who forgot why fb2k on windows 10 refuses to play wma lossless by default - https://hydrogenaud.io/index.php/topic,117275.0.html , https://hydrogenaud.io/index.php/topic,117578.0.html
Title: Re: foobar2000 v2.0 bugs
Post by: Gus. on 2022-10-15 00:57:09
OK, now that I have a WMA Lossless sample from @Case https://hydrogenaud.io/index.php/topic,117578.0.html
It does play with the FFMPEG Wrapper/latest FFMPEG 5.1.2
Foobar 2.0 x64 beta 12 portable in latest version Win10 Pro x64 "Downloads" folder.
Title: Re: foobar2000 v2.0 bugs
Post by: AndreaT on 2022-10-15 08:20:47
Quote from: Bogozo on
Quote from: AndreaT on
FB v2 reoports "Unable to open item for playback (Could not start the decoder: could not start the worker process):..."
Maybe your windows is blocking ffmpeg.exe/ffprobe.exe somehow. You know, there is such thing in windows: "This File Came From Another Computer And Might be Blocked to help protect this computer"

Quote from: Gus. on
I'm guessing FFMPEG doesn't support the format
Your guess is wrong.

For those who forgot why fb2k on windows 10 refuses to play wma lossless by default - https://hydrogenaud.io/index.php/topic,117275.0.html , https://hydrogenaud.io/index.php/topic,117578.0.html

Hello @gus. and @Bogozo , thanks a lot for your kind and prompt follow-up on my reported issue.
Well, if I have correctly understood, there is no solution right now available for Foobar (please correct me if I am wrong).

Thant's not a big issue for me, I have just a few WMA files and I can use other players.
At this point, do you recommend me to remove FFmpeg wrapper (foo_imput_FFmpeg)?
I will keep only the default foo_input_std.

Thanks again and kind regards, Andrea
Title: Re: foobar2000 v2.0 bugs
Post by: Porcus on 2022-10-15 10:38:03
The problem about WMAL playback is that ... it isn't lossless if the output signal isn't correct.
And for an application that is often used for lossless conversion, it does not really make sense to take responsibility for converting that. With WMAL being a dying format, people would be tempted to convert their WMAL files to something better, and with the output possibly being broken ... one should at least be warned from here to Hades. Don't throw away the original.

I suppose you want to do the following.
(1) Convert them "as losslessly as seems possible". I guess you would try those different decoders that are around? (You can try to bitcompare afterwards.)
(2) Stuff your WMALs away in a backup.
(3) Tag those converted files, or keep them in a way that distinguish them. (Say, using a different codec/setting than you would otherwise use.)

Microsoft was about to scrap WMAL already with Vista , https://answers.microsoft.com/en-us/windows/forum/all/how-do-you-convert-wma-lossless-to-wav/15dabe00-ef24-4f7e-811f-a4ae4855b916 - I don't know if the XP decoding "is known as reliable" nor whether it is available without firing up an old XP. (And even then ... how?)
Title: Re: foobar2000 v2.0 bugs
Post by: Bogozo on 2022-10-15 12:50:45
Quote from: AndreaT on
if I have correctly understood, there is no solution right now available for Foobar (please correct me if I am wrong).
@AndreaT  Solution is to use foo_input_ffmpeg. Why there is problem with running ffmpeg binaries on your system, this is another question.
Is your windows 32-bit or 64-bit ? If it is 32-bit, you need 32-bit ffmpeg, not 64-bit that @Gus. gave link to. 32-bit ffmpeg can be downloaded from here - https://github.com/sudo-nautilus/FFmpeg-Builds-Win32/releases/download/latest/ffmpeg-master-latest-win32-gpl.zip
Title: Re: foobar2000 v2.0 bugs
Post by: zK on 2022-10-15 12:53:15
Quote from: Lesmo16 on
Quote from: Case on
Quote from: Lesmo16 on
Quote from: Lesmo16 on
The Layout Editing Mode can't be finished completely.
After switching it off the blue splitters indeed turn to grey ...
but even locked (the new method) splitters stay movable.
Since this isn't corrected until beta 8: Isn't this a bug?  :o
That has nothing to do with layout editing mode. You can move the splitters even if you skip that part. That is how they currently work, Peter is aware of the request to restore old locking behavior. I can't comment if things will change.
I support this request!
+1 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Title: Re: foobar2000 v2.0 bugs
Post by: metal_termite on 2022-10-15 19:15:55
Re: Playlist view > right click a column header > columns

If one has many custom columns that cannot all be displayed within the context menu, an up button and down button appear respectively.

1. It doesn't look like the aforementioned buttons don't respect dark mode (see attached image)
2. Using these buttons actually becomes very cumbersome when repeatedly clicking the down button to navigate to the bottom of the context menu. I think it would be a lot more elegant to replace this behaviour with a scrollbar on the context menu when it's required.
Title: Re: foobar2000 v2.0 bugs
Post by: Chibisteven on 2022-10-15 23:01:32
Quote from: AndreaT on
Quote from: Bogozo on
Quote from: AndreaT on
FB v2 reoports "Unable to open item for playback (Could not start the decoder: could not start the worker process):..."
Maybe your windows is blocking ffmpeg.exe/ffprobe.exe somehow. You know, there is such thing in windows: "This File Came From Another Computer And Might be Blocked to help protect this computer"

Quote from: Gus. on
I'm guessing FFMPEG doesn't support the format
Your guess is wrong.

For those who forgot why fb2k on windows 10 refuses to play wma lossless by default - https://hydrogenaud.io/index.php/topic,117275.0.html , https://hydrogenaud.io/index.php/topic,117578.0.html

Hello @gus. and @Bogozo , thanks a lot for your kind and prompt follow-up on my reported issue.
Well, if I have correctly understood, there is no solution right now available for Foobar (please correct me if I am wrong).

Thant's not a big issue for me, I have just a few WMA files and I can use other players.
At this point, do you recommend me to remove FFmpeg wrapper (foo_imput_FFmpeg)?
I will keep only the default foo_input_std.

Thanks again and kind regards, Andrea


I keep both FFMPEG Wrapper and FFMPEG up to date.  I have both of those but I seldom use them.  Usually when an operating system is blocking something it's that something is too new and antivirus doesn't like it.  You can try whitelisting stuff antivirus don't like.  I have a fair amount trust in both foobar2000's developer and FFMPEG's developer to know their stuff is safe and reputable.  WMA sucks overall mainly because it's maker, Microsoft more or less abandoned it.  If you have the original sources somewhere else such as a CD you ripped it from, you can re-encode it to a different format.
Title: Re: foobar2000 v2.0 bugs
Post by: pulbitz on 2022-10-16 15:01:02
I'm using Windows with Loudness Equalization turned on.
foobar2000 2.0 beta 12 x64 uses Playback - Output - Device: Primary Sound Driver.
If you check Fading (Enable smooth seeking, pause and volume changes) option, Loudness Equalization DSP is used normally.
By the way, if it is unchecked, the volume will be reduced as if Loudness Equalization is not used.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2022-10-17 12:12:58
[v2 beta 12] Play count isn't updated, if the track is never played (play_count 0).

EDIT: Never mind. There went something wrong during update to v2. Problem solved with new installation.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2022-10-17 20:28:22
Glitch: Windows 11 integration displays path to foobar2000.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2022-10-18 12:26:26
Glitches: DUI

Title: Re: foobar2000 v2.0 bugs
Post by: imeric on 2022-10-18 20:08:36
Quote from: imeric on
SACD DSD files did not get imported on upgrade
Anybody else experiencing this issue? Is it due to the SACD plugin (which is working fine in 1.16)?
The .dsf files will play in v2 beta 12 but are not visible in my library anymore.
If I add the folder manually playstats are still intact (ie Dated added is good, playcount etc...)
Thx
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2022-10-19 03:57:08
Bug: Terrible Memory leaks in Visualization panels. From 200MB to 1000MB in an hour! More then one visualization is effected.

EDIT: Removed Coverflow Mod: no increase in Memory consumption. (See Screenshot 2)
Title: Re: foobar2000 v2.0 bugs
Post by: imeric on 2022-10-20 18:00:09
Quote from: imeric on
Quote from: imeric on
SACD DSD files did not get imported on upgrade
Anybody else experiencing this issue? Is it due to the SACD plugin (which is working fine in 1.16)?
The .dsf files will play in v2 beta 12 but are not visible in my library anymore.
If I add the folder manually playstats are still intact (ie Dated added is good, playcount etc...)
Thx
Never mind this was probably due to installing the 64bit version then reinstalling 32bit afterwards due to missing components. I clean reinstalled with a backup of my library and everything worked fine.

I have to say so far so good with v2 I love the new covert art addtion in playlist view and the fluid spectrum visualization with HW acceleration it's a lot smoother.  Now I'd love to be able to modify ratings using stars while writing to tag in the playlist view instead of needing a right click with quicktagger...
Title: Re: foobar2000 v2.0 bugs
Post by: AndreaT on 2022-10-20 18:13:54
FOUND SOLUTION FOR PLAYING 24bit WMA on Foobar 32bit

Thanks @Gus.  @Bogozo @Chibisteven , I have finally been able to play those 24bit WMA on my 32bit Foobar V2 using the following ffmpeg decoders package:  https://github.com/sudo-nautilus/FFmpeg-Builds-Win32/releases/tag/latest

Regards, Andrea
Title: Re: foobar2000 v2.0 bugs
Post by: Gus. on 2022-10-20 18:21:51
Quote from: AndreaT on
FOUND SOLUTION FOR PLAYING 24bit WMA on Foobar 32bit

Thanks @Gus.  @Bogozo @Chibisteven , I have finally been able to play those 24bit WMA on my 32bit Foobar V2 using the following ffmpeg decoders package:  https://github.com/sudo-nautilus/FFmpeg-Builds-Win32/releases/tag/latest

Regards, Andrea

Great! If you're running a 32-bit OS, then yes, you'll need 32-bit builds of ffmpeg, most builds nowadays are 64-bit only.
Title: Re: foobar2000 v2.0 bugs
Post by: ASopH on 2022-10-22 14:27:15
Hi,

An existing Converter-Preset can't be saved (Portable Mode).
I've changed my Destination-Setting and after I clicked BACK and SAVE there's no request to really SAVE and CONVERT don't run.
Title: Re: foobar2000 v2.0 bugs
Post by: InchPerfect on 2022-10-23 20:48:18
[Repeat of this post (https://hydrogenaud.io/index.php/topic,123229.new.html) I made a couple of days ago. Maybe this thread is the best place to post it?]

I can't use search when a filter including "NOT" is applied.

I use default UI and facets.

When I've got a filter like "NOT %genre% HAS Live" active, as soon as I type anything in the search box (even just "a"), nothing shows up. All the facets panels go completely blank.

It looks like this only happens when the filter includes "NOT".

I have two filters:

1. Live: %genre% HAS Live
and
2. Not Live: NOT %genre% HAS Live.

The first one works as expected (search is possible when the filter is applied) but the second one returns nothing when anything is typed in the search box.

It's the same in v2 beta 11 and v2 beta 12. But the issue doesn't exist in v1.

I presume this is a (major) bug but perhaps I'm doing something wrong?

Thanks.
Title: Re: foobar2000 v2.0 bugs
Post by: Monno on 2022-10-24 14:15:01
Quote from: InchPerfect on
[Repeat of this post (https://hydrogenaud.io/index.php/topic,123229.new.html) I made a couple of days ago. Maybe this thread is the best place to post it?]

I can't use search when a filter including "NOT" is applied.

I use default UI and facets.

When I've got a filter like "NOT %genre% HAS Live" active, as soon as I type anything in the search box (even just "a"), nothing shows up. All the facets panels go completely blank.

It looks like this only happens when the filter includes "NOT".

I have two filters:

1. Live: %genre% HAS Live
and
2. Not Live: NOT %genre% HAS Live.

The first one works as expected (search is possible when the filter is applied) but the second one returns nothing when anything is typed in the search box.

It's the same in v2 beta 11 and v2 beta 12. But the issue doesn't exist in v1.

I presume this is a (major) bug but perhaps I'm doing something wrong?

Thanks.

I've been messing around with filters trying to replicate the bug you experienced and haven't been able to do it.
Everything seems to be working for me. Here was my working query...
NOT %genre% HAS soundtrack

Weird issue.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2022-10-24 14:25:33
Apply filter and add for example "a" in search. This should show all filter results with an "a", but it shows nothing.
Title: Re: foobar2000 v2.0 bugs
Post by: suisei on 2022-10-24 23:09:25
Statistics such as rating is now hard linked to the file path, which means if the file is moved, the rating is loss.

Please add an option to use the old Playback Statistics (foo_playcount) behavior. While this may not be as accurate, it is good enough for me.

If not, please allow the use of the old foo_playcount component, and recompile it for 64 bit.

Thank you.
Title: Re: foobar2000 v2.0 bugs
Post by: Squeller on 2022-10-25 08:45:29
Beta 12 32bit: After I delete files via "File Operations, Dele Files" - my autoplaylists still keep those entries. I.e., they aren't removed from the database. Tracks disappear after manual refresh of database. Is that intended? Can't fb2k, even if library is set to manual refresh only, delete entries if files are deleted via fb2k's UI?
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2022-10-25 10:46:16
Quote from: suisei on
Statistics such as rating is now hard linked to the file path, which means if the file is moved, the rating is loss.

Please add an option to use the old Playback Statistics (foo_playcount) behavior. While this may not be as accurate, it is good enough for me.

If not, please allow the use of the old foo_playcount component, and recompile it for 64 bit.

Thank you.
That's not true. Beside the Playback Statistics database, the data (rating etc.) can be written to file tags. This can be done automatically by store playback statistics in file tags in Preferences or manually by Write statistics to file tags in context menu. If you loose the playback statistics database, restore it with Import statistics from file tags in context menu.
Title: Re: foobar2000 v2.0 bugs
Post by: WhameWhame on 2022-10-25 15:00:49
Quote from: grimes on
[v2 beta 12] Play count isn't updated, if the track is never played (play_count 0).

EDIT: Never mind. There went something wrong during update to v2. Problem solved with new installation.

Any idea what exactly the problem was? Am having the same problem - if the track is played for the first time play count isn't updating! Reinstalling didn't solve.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2022-10-25 16:01:46
No idea, but did you delete the sqlite database files and reread the media library?
Title: Re: foobar2000 v2.0 bugs
Post by: suisei on 2022-10-25 22:39:33
Quote from: grimes on
That's not true. Beside the Playback Statistics database, the data (rating etc.) can be written to file tags. This can be done automatically by store playback statistics in file tags in Preferences or manually by Write statistics to file tags in context menu. If you loose the playback statistics database, restore it with Import statistics from file tags in context menu.

You can try it yourself, just add a random song file, rate it, move it to a different folder, add that song again, you can see that the rating is lost. The rating is tied to the original location so the rating is only for that exact location. The old foo_playcount does't have this issue.

I do not want to write anything to tag.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2022-10-25 23:10:12
From: https://wiki.hydrogenaud.io/index.php?title=Foobar2000:File_Operations_(foo_fileops) (https://wiki.hydrogenaud.io/index.php?title=Foobar2000:File_Operations_(foo_fileops))
Quote
Data from the official playback statistics component is preserved when moving files.
Note: If the files are moved to a folder which is not monitored by the Media Library, they will be removed from the Media Library and playback statistics will also be lost.
Title: Re: foobar2000 v2.0 bugs
Post by: suisei on 2022-10-25 23:35:35
Quote from: grimes on
From: https://wiki.hydrogenaud.io/index.php?title=Foobar2000:File_Operations_(foo_fileops)
Quote
Data from the official playback statistics component is preserved when moving files.
Note: If the files are moved to a folder which is not monitored by the Media Library, they will be removed from the Media Library and playback statistics will also be lost.

The old foo_playcount can rate and preserve data for song not in the library as well, and if the file is moved, whether it is monitored or not, the data is still there for it.

The one in 2.0 cannot do any of that, even for song in the folder monitored by the library.

If this is really not a bug, I hope the old foo_playcount will be allowed to function again because it has exactly what I need.
Title: Re: foobar2000 v2.0 bugs
Post by: WhameWhame on 2022-10-26 15:41:56
Quote from: grimes on
No idea, but did you delete the sqlite database files and reread the media library?

I didn't, no - reinstalling without deleting AppData didn't fix the problem for me, but deleting AppData did. So the problem must have been somewhere in there...
Title: Re: foobar2000 v2.0 bugs
Post by: imeric on 2022-10-27 16:23:58
Quote from: Chibisteven on
Quote from: AndreaT on
Quote from: AndreaT on
Beta 12 - High CPU usage on my old 32bit Windows 10 fully patched

Hello, I am sorry I didn't extensively tested beta 11, however, this new Beta 12 along with the last Windows 10 updates (I don't know which one is the main responsible) make my old 32bit Windows 10 PC unusable.
Over 80% of CPU usage reported and continuous audio cuts and whistles (also updated Behringer UMC ASIO driver).

Regards, Andrea




Hello @Gus., @Chibisteven , I think the problem was not completely due to Foobar v2.
I rebooted the PC and the CPU load went down by itself. Probably something was leftover from the previous MS Win update.

Moreover, I found that my buffering settings were all 0. Thereof I set these to my so far used sizes (see attached).

Doing so, Foobar v2 can now play smoothly comparable with previous v1.6.
Due to my quite demanding audio setup and relatively low performance 32bit PC, the CPU usage is so:
- 44kHz 16bit FLAC => 50% CPU
- SACD ISO => 70% CPU
This is fine for me now. I can play anything.

If anyone has / knows a better/optimal Buffer setting, please let me know.

Thanks for your support
Regards, Andrea

I find that leaving the file buffering at defaults is best.  Output buffer usually has more impact against drop outs as everything has time to be fully processed through the whole foobar2000 chain, especially on really old, slow computers, on more modern, faster ones like mine it makes no difference at all where things are set but can provide some protection if a mechanical hard drive is put under a continuous heavy load.

The network buffering might be fine to adjust if your internet connection isn't very stable but I leave the file buffering at it's defaults.

I switch between 1 and 30 seconds depending on what I'm doing.  If I'm playing a whole playlist nonstop then exclusive mode works best so I set it to 30 seconds and leave it running.  Otherwise I use shared mode with 1 second as it's much more responsive when making changes in the DSP area for example as I don't have to wait long for changes to take effect.

As for your settings: Change your full file buffering to 0 KB.  500 MB will put a huge load on your CPU and consume a large amount of RAM.  Instead adjust only the read ahead until it plays smoothly or increase the output buffer.

I had stutter issues on an old Intel Core 2 Quad Q660/P5Q Mobo with Wasapi, ASIO and ASIO+DSD.  I need ASIO for my Exasound DAC which doesn't support WASAPI.  I'm still using an Old M-Audio 192 and resolved WASAPI stutter on this one by changing the Hardware buffer to 50ms as per pic below.  For ASIO thx to Andrea and Chibisteven the Read-Ahead increase for local files was mostly the culprit in my case.  I had a very large full file buffering and not sure why this should be left at zero if I have plenty of RAM on the PC...Anyway still playing with this but so far so good.  For casual listening while working I resample everything with Sox to 384 KHz and use the old continuator DSP as I have all kinds of files (lossy,redbook, Hi-Res and DSD)... Usually works fine but has been a bit of a challenge on this Old PC but makes me see where the bottlenecks are!!
Title: Re: foobar2000 v2.0 bugs
Post by: imeric on 2022-10-27 18:20:02
Quote from: imeric on
Quote from: Chibisteven on
Quote from: AndreaT on
Quote from: AndreaT on
Beta 12 - High CPU usage on my old 32bit Windows 10 fully patched

Hello, I am sorry I didn't extensively tested beta 11, however, this new Beta 12 along with the last Windows 10 updates (I don't know which one is the main responsible) make my old 32bit Windows 10 PC unusable.
Over 80% of CPU usage reported and continuous audio cuts and whistles (also updated Behringer UMC ASIO driver).

Regards, Andrea




Hello @Gus., @Chibisteven , I think the problem was not completely due to Foobar v2.
I rebooted the PC and the CPU load went down by itself. Probably something was leftover from the previous MS Win update.

Moreover, I found that my buffering settings were all 0. Thereof I set these to my so far used sizes (see attached).

Doing so, Foobar v2 can now play smoothly comparable with previous v1.6.
Due to my quite demanding audio setup and relatively low performance 32bit PC, the CPU usage is so:
- 44kHz 16bit FLAC => 50% CPU
- SACD ISO => 70% CPU
This is fine for me now. I can play anything.

If anyone has / knows a better/optimal Buffer setting, please let me know.

Thanks for your support
Regards, Andrea

I find that leaving the file buffering at defaults is best.  Output buffer usually has more impact against drop outs as everything has time to be fully processed through the whole foobar2000 chain, especially on really old, slow computers, on more modern, faster ones like mine it makes no difference at all where things are set but can provide some protection if a mechanical hard drive is put under a continuous heavy load.

The network buffering might be fine to adjust if your internet connection isn't very stable but I leave the file buffering at it's defaults.

I switch between 1 and 30 seconds depending on what I'm doing.  If I'm playing a whole playlist nonstop then exclusive mode works best so I set it to 30 seconds and leave it running.  Otherwise I use shared mode with 1 second as it's much more responsive when making changes in the DSP area for example as I don't have to wait long for changes to take effect.

As for your settings: Change your full file buffering to 0 KB.  500 MB will put a huge load on your CPU and consume a large amount of RAM.  Instead adjust only the read ahead until it plays smoothly or increase the output buffer.

I had stutter issues on an old Intel Core 2 Quad Q660/P5Q Mobo with Wasapi, ASIO and ASIO+DSD.  I need ASIO for my Exasound DAC which doesn't support WASAPI.  I'm still using an Old M-Audio 192 and resolved WASAPI stutter on this one by changing the Hardware buffer to 50ms as per pic below.  For ASIO thx to Andrea and Chibisteven the Read-Ahead increase for local files was mostly the culprit in my case.  I had a very large full file buffering and not sure why this should be left at zero if I have plenty of RAM on the PC...Anyway still playing with this but so far so good.  For casual listening while working I resample everything with Sox to 384 KHz and use the old continuator DSP as I have all kinds of files (lossy,redbook, Hi-Res and DSD)... Usually works fine but has been a bit of a challenge on this Old PC but makes me see where the bottlenecks are!!
Still stutters no matter what parameters I use with ASIO or ASIO+DSD...Works just fine with my other player
Title: Re: foobar2000 v2.0 bugs
Post by: Chibisteven on 2022-10-28 03:17:11
Quote from: imeric on
Quote from: imeric on
I had stutter issues on an old Intel Core 2 Quad Q660/P5Q Mobo with Wasapi, ASIO and ASIO+DSD.  I need ASIO for my Exasound DAC which doesn't support WASAPI.  I'm still using an Old M-Audio 192 and resolved WASAPI stutter on this one by changing the Hardware buffer to 50ms as per pic below.  For ASIO thx to Andrea and Chibisteven the Read-Ahead increase for local files was mostly the culprit in my case.  I had a very large full file buffering and not sure why this should be left at zero if I have plenty of RAM on the PC...Anyway still playing with this but so far so good.  For casual listening while working I resample everything with Sox to 384 KHz and use the old continuator DSP as I have all kinds of files (lossy,redbook, Hi-Res and DSD)... Usually works fine but has been a bit of a challenge on this Old PC but makes me see where the bottlenecks are!!
Still stutters no matter what parameters I use with ASIO or ASIO+DSD...Works just fine with my other player

It's the age of CPU probably.  That CPU is Q1 2007 (https://www.intel.com/content/www/us/en/products/sku/29765/intel-core2-quad-processor-q6600-8m-cache-2-40-ghz-1066-mhz-fsb/specifications.html).  So it's quite old.   It's an XP / Vista era CPU.  It's going to struggle with modern applications.
Title: Re: foobar2000 v2.0 bugs
Post by: iridescentaudio on 2022-10-28 11:37:22
I'm also getting extremely high CPU usage on occasion, no clues as to why. Granted I also have an older processor (Core i3 2100), but I am not used to seeing foobar2000 using 70% CPU while idle/monitoring, I'm used to seeing single figures even with my admittedly bloated setup ~ a large library (six figures) and a lot of playlists, some of which I could dispense with, minibar, rainbow spectrum visible at all times, and I'm also using JS Smooth Browser which to be honest hasn't been working well ever since upgrading either, with regular crashes especially with larger playlists, so I may just give it the bum's rush since I rarely use it anyway.

On the plus side, memory use actually seems to have gone down. May just make a few adjustments to see if I can improve performance.
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-10-28 11:58:49
Quote from: iridescentaudio on
I'm also using JS Smooth Browser which to be honest hasn't been working well ever since upgrading either, with regular crashes especially with larger playlists, so I may just give it the bum's rush since I rarely use it anyway.

Well that's nonsensical. Smooth Browser is a library viewer. The size of your playlists will have zero affect on it

 (edit: i guess you could be using older versions with playlist supprt but they were buggy as hell and should be avoided - and I'd assume most playlists are going to be smaller than an entire library??)

BTW, the latest version JScript Panel 3 is optimised for fb2k v2 and has lots of performance tweaks and fixes for the included smooth scripts. Performance still might suck for large collections but I would fix any errors if there were reported.

Anyone using SMP versions should seriously consider switching or not using. They haven't been updated in years and are unlikely to be,
Title: Re: foobar2000 v2.0 bugs
Post by: iridescentaudio on 2022-10-28 13:42:19
I'm merely telling you what I'm experiencing, marc. I promise you I am not making it up!
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-10-28 14:10:25
I didn't say you were making it up. I just suggested using the latest version and reporting bugs as you encounter them. Common sense is not so common these days.
Title: Re: foobar2000 v2.0 bugs
Post by: imeric on 2022-10-28 14:37:27
Quote from: Chibisteven on
Quote from: imeric on
Quote from: imeric on
I had stutter issues on an old Intel Core 2 Quad Q660/P5Q Mobo with Wasapi, ASIO and ASIO+DSD.  I need ASIO for my Exasound DAC which doesn't support WASAPI.  I'm still using an Old M-Audio 192 and resolved WASAPI stutter on this one by changing the Hardware buffer to 50ms as per pic below.  For ASIO thx to Andrea and Chibisteven the Read-Ahead increase for local files was mostly the culprit in my case.  I had a very large full file buffering and not sure why this should be left at zero if I have plenty of RAM on the PC...Anyway still playing with this but so far so good.  For casual listening while working I resample everything with Sox to 384 KHz and use the old continuator DSP as I have all kinds of files (lossy,redbook, Hi-Res and DSD)... Usually works fine but has been a bit of a challenge on this Old PC but makes me see where the bottlenecks are!!
Still stutters no matter what parameters I use with ASIO or ASIO+DSD...Works just fine with my other player

It's the age of CPU probably.  That CPU is Q1 2007 (https://www.intel.com/content/www/us/en/products/sku/29765/intel-core2-quad-processor-q6600-8m-cache-2-40-ghz-1066-mhz-fsb/specifications.html).  So it's quite old.   It's an XP / Vista era CPU.  It's going to struggle with modern applications.
True...But it's OC'd from 2.4 to 3.2GHz, has been stable like this for years and working just fine however yes the P5Q Mobo, memory etc... may come at play here too...And I'm running W11 on it so I'm pushing my luck!!

But back to my point, if I can make it play just fine with my other Player it should also play fine with Foobar ASIO?... Any thoughts on my parameters? CPU usage of Foobar V2 is always below 5-10 percent with memory usage of around 100 to 300 MB depending on the file played.
Title: Re: foobar2000 v2.0 bugs
Post by: Chibisteven on 2022-10-28 15:52:35
Quote from: imeric on
True...But it's OC'd from 2.4 to 3.2GHz, has been stable like this for years and working just fine however yes the P5Q Mobo, memory etc... may come at play here too...And I'm running W11 on it so I'm pushing my luck!!

But back to my point, if I can make it play just fine with my other Player it should also play fine with Foobar ASIO?... Any thoughts on my parameters? CPU usage of Foobar V2 is always below 5-10 percent with memory usage of around 100 to 300 MB depending on the file played.

Maybe your luck ran out?  Running Windows 11 on an unsupported CPU that is really too old, I mean what on Earth could go wrong there?  Honestly it be a waste of my time to figure out exactly what is going wrong here because you have all the red flags of a very risky and potentially very problematic system configuration.  Just because other applications are running fine at the moment doesn't mean that they'll continue to do so in the future.
Title: Re: foobar2000 v2.0 bugs
Post by: Gus. on 2022-10-28 17:04:35
There are 3 ASIO output components that I know of:
https://www.foobar2000.org/components/view/foo_out_asio
https://sourceforge.net/projects/sacddecoder/files/foo_out_asio%2Bdsd/
https://sourceforge.net/projects/foobar2000-wasap2-output/
If none of them are working properly with high buffers, maybe you should consider trying alternative ASIO drivers:
https://github.com/dechamps/FlexASIO
https://www.asio4all.org/
Also try the Thread Priority settings in Foobar, maybe disable MMCSS...
Title: Re: foobar2000 v2.0 bugs
Post by: Execucucu on 2022-10-29 00:07:51
Tried the latest Beta 12.

Bug 1: Media Library "Simple Search" is a bit broken.
Simple search was supposed to search matching text among metadata OR FILEPATH. Now the FILEPATH part doesn't work.

Bug 2: Refacet's search textbox size limits how many characters you can type per search??
If the textbox (searchbox? Just the place where I type search keywords) is too small, you can only type a few characters at max.
This bug only happens with Refacet searchbox. (The Facets search box isn't having this problem.)

Imagine trying to walk around Bug 1 by searching "%path% HAS whatiwant" instead of "whatiwant", only to encounter bug 2 which prevents me from typing this many characters in one search.

Not a bug 3: The sort by name behavior changed.
In 2.0 Beta 12, names start with numbers (eg. 1,2,3) is sorted before names start with [.
Back in 1.x version, [, and even 【 (which is a 2 byte character) is sorted before numbers.
Now in 2.0 Beta 12, 【, as well as all other 2 byte characters, are sorted after all 1 byte characters.
Title: Re: foobar2000 v2.0 bugs
Post by: glong on 2022-10-29 07:54:08
V2 bugs noticed

Apply to 32 bit version since supporting components for the following don't seem to be supported

All ISO files will play etc when file>open but none of them appear in FB album or folder listings and wont be found with text searches

Quick Tagger occasionally  will tag a file but mostly it does nothing
Title: Re: foobar2000 v2.0 bugs
Post by: iridescentaudio on 2022-10-29 11:13:04
Quote from: marc2k3 on
I didn't say you were making it up. I just suggested using the latest version and reporting bugs as you encounter them. Common sense is not so common these days.

I'm not using J Script Panel 3, I am using Spider Monkey Panel. I say "using", I'm not really using it/can live without it. If I needed to switch to this component that is news to me. In any case, it is very likely unrelated to the main issue I'm struggling with - foobar spiking to and then idling at over 70% CPU usage and staying there indefinitely. It's basically unusable software until I can figure out what is causing this or what's happening. I'm keeping my task manager open while using foobar to try and find any rhyme or reason. It'd be good if there was some way I could see what internal processes are active in foobar because I am left completely guessing at it.
Title: Re: foobar2000 v2.0 bugs
Post by: anamorphic on 2022-10-29 12:17:05
Just a reminder from the release notes (https://wiki.hydrogenaud.io/index.php?title=Foobar2000:Version_2.0_Release_Notes#Before_reporting_bugs...) ...

Quote
Before reporting bugs...
Please verify that any bugs can be recreated WITHOUT ANY COMPONENTS first. ESPECIALLY without any components that have not yet been specifically updated for foobar2000 v2.0. Due to design changes, many components will suffer from performance issues until refactored for the new database system.
Title: Re: foobar2000 v2.0 bugs
Post by: AndreaT on 2022-10-29 15:04:15
UI Element "Tabs" related

Hi All, I just noticed that UI elements associated to tabs are usig significant CPU resources also wheno not in focus (not the active tab).

To be more precise, let me give you a real case on my 32bit Windows 10 running FB v2 beta 12:

Case 1 (optimal):
- FB setup as per my baseline config
- Added a UI Tabs having only 1 tab associated with the UI element Console (all time in focuse / visible)
- Overal CPU usage playing a regular FLAC 44kHz 16bit => 25%

Case 2 (the bad case):
- FB setup as per my baseline config
- Added a UI Tabs having 3 tabs associated with the UI elements Console, Peak Meter, Spectrum
- Overal CPU usage playing a regular FLAC 44kHz 16bit:
     - having focus on Console tab (the only visible) => 47%
     - having focus on Spectrum tab (the only visible) => 65%
     - having focus on Feak meter tab (the only visible) => 55%

Is it normal this behavior? I mean, is it by design?
I would expect that UI elements in the backgroud (not in focus) should not use so much CPU resource.

All the best, Andrea
Title: Re: foobar2000 v2.0 bugs
Post by: AndreaT on 2022-10-29 15:42:15
Strange "error loading" reported at Console output on startup (only):

User Interface initialized in: 0:02.384614
[foo_acfu] error loading cache entry 19EECCD4-18C6-40AE-94BC-B0631D77E38D: unregistered source: 19EECCD4-18C6-40AE-94BC-B0631D77E38D
[foo_acfu] error loading cache entry 5D818F39-C68C-4522-BF43-D9CF2FF72010: unregistered source: 5D818F39-C68C-4522-BF43-D9CF2FF72010
[foo_acfu] error loading cache entry 61368423-3FDC-44DA-9924-984480BA15B5: unregistered source: 61368423-3FDC-44DA-9924-984480BA15B5
[foo_acfu] error loading cache entry 94974E25-6AA2-418D-927D-41093087A6D2: unregistered source: 94974E25-6AA2-418D-927D-41093087A6D2
[foo_acfu] error loading cache entry C5F5D92C-482B-4938-83AC-B672BC3687E8: unregistered source: C5F5D92C-482B-4938-83AC-B672BC3687E8

Hi All, any idea why I am having this?
FB v2 beta 12 looks anyway working quite fine.

Regards, Andrea
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-10-29 15:47:14
foo_acfu is a 3rd party component so ask the developer. This thread is the last place you should be asking about it.
Title: Re: foobar2000 v2.0 bugs
Post by: AndreaT on 2022-10-29 18:04:10
Quote from: marc2k3 on
foo_acfu is a 3rd party component so ask the developer. This thread is the last place you should be asking about it.

Thanks @marc2k3 , I was not aware of that or I forgot it. I will search for the appropriate thread...
Title: Re: foobar2000 v2.0 bugs
Post by: AndreaT on 2022-10-29 18:07:56
FB v2 Beta 12 - BUG: False "file corrupted error" reported on restart from long pause

Hi All, I think this is a bug because never seen before with FB v1.6

Anytime I put on pause any audio file for at least 30minutes, then on restart the audio stream works fine for 10-20 seconds and then stops reporting something like "corrupted file".

It is a false error becaure file verifier reports file OK and also because replaying it again it plays perfectly until its end.

Regards, Andrea
Title: Re: foobar2000 v2.0 bugs
Post by: imeric on 2022-11-01 13:49:53
Quote from: glong on
All ISO files will play etc when file>open but none of them appear in FB album or folder listings and wont be found with text searches
I had the same issue after upgrading to the 64 bit version. I rolled back to v2 32 bit but needed to delete all V2 %appdata% folders so it would reimport and update the database from version 1.16 and that fixed this issue for me.
Title: Re: foobar2000 v2.0 bugs
Post by: Belomor on 2022-11-01 19:12:19
2.0 Beta 12 fails to read my windows network share where my media library resides. The error text is "Unable to open item for playback (I/O error (win32 #24)):". Neither mounted drive nor UNC path works.
It has always worked fine with 1.x versions.
Title: Re: foobar2000 v2.0 bugs
Post by: mudlord on 2022-11-05 01:16:39
"Works for me" *shrug*

Though thats about as useful as "there is no such thing as world hunger because I have a sandwich"....
Title: Re: foobar2000 v2.0 bugs
Post by: medp7060 on 2022-11-05 20:37:37
On Windows 10 PE:

v1.x works, but v2.0 beta 12 portable has this error: "The remote procedure call failed"
Title: Re: foobar2000 v2.0 bugs
Post by: InchPerfect on 2022-11-06 08:42:02
I'm not sure exactly how to describe this but ratings in v2 beta just don't seem to work properly.

When I filter by the built-in "Top rated" (i.e. %rating% IS 5) I get a random selection of tracks with different ratings from 0 to 5.

Is this a but or am I doing something wrong?

In Settings>Advanced>Display>Properties dialog>Standard fields I have: Track title=TITLE;Album title=ALBUM;Artist name=ARTIST;Album artist=ALBUM ARTIST;Date=DATE;Orig year=ORIGINAL RELEASE DATE;Genre=GENRE;Composer=COMPOSER;Performer=PERFORMER;Track Number=TRACKNUMBER;Total Tracks=TOTALTRACKS;Disc Number=DISCNUMBER;Total Discs=TOTALDISCS;Comment=COMMENT;Rating=RATING;Copyright=COPYRIGHT;

I use Quick tagger to set the rating: https://i.imgur.com/2dxkzNK.png

And in Preferences>Display>Default User Interface>Playlist View I have this custom column: Name = Rating Pattern= $pad($repeat(★,$meta(rating)), 5,) so I can display the ratings as stars.

Am I writing to the wrong field or something?

I'd really like to be able to filter by rating. Please can someone help? Thanks.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2022-11-06 10:46:19
The rating are stored in an own database and in the tags. With Quicktagger you are writing in the tags.. The metadata has to be transferred to the database with Import statistics from file tags or use $meta(rating).
Normal procedure is, to create ratings with context menu playlist | Playback Statistics | Rating | 1-5 and activate the checkbox Store playback statistics in file tags in Preferences.
Title: Re: foobar2000 v2.0 bugs
Post by: InchPerfect on 2022-11-06 14:59:00
Quote from: grimes on
The rating are stored in an own database and in the tags. With Quicktagger you are writing in the tags.. The metadata has to be transferred to the database with Import statistics from file tags or use $meta(rating).
Normal procedure is, to create ratings with context menu playlist | Playback Statistics | Rating | 1-5 and activate the checkbox Store playback statistics in file tags in Preferences.

Thanks very much, grimes.

But I'm still horribly confused lol.

OK. I've checked the box Store playback statistics in file tags in Preferences.

But I don't know how to rate the tracks without doing context menu playlist | Playback Statistics | Rating | 1-5.

I've made shortcut keys to rate tracks. Ctrl+2 for a 2 rating, for example. But when I then right click the track (that has been rated 2), in context menu playlist | Playback Statistics | Rating it says the rating is 5 (screenshot: https://i.imgur.com/grFyE6h.png) even though in Properties it says the Rating is 2.

And if I right click a track that I haven't rated, it says that it's rated 5. Screenshot: https://i.imgur.com/TD3lzX4.png There's no rating for that track in Properties. Screenshot: https://i.imgur.com/OA6TOeu.png

And I thought I was using $meta(rating). In Preferences>Display>Default User Interface>Playlist View I have this custom column: Name = Rating Pattern= $pad($repeat(★,$meta(rating)), 5,)

And when I use the shortcut keys to rate songs, the rating shows up fine in Properties, it just doesn't seem to be understood by fb2k.

I don't really know what checking the box Store playback statistics in file tags in Preferences is doing, to be honest. And I don't understand why tracks that I haven't rated have this hidden 5 rating when I look in the context menu but nothing shows up in Properties.

And if I choose a track with no rating and do context menu playlist | Playback Statistics | Rating and click on Write statistics to file tags the hidden 5 rating gets put into my Rating column. It's clearly using the same field as I'm already using when I use the shortcut keys to rate tracks, as you can see here: https://i.imgur.com/DCj8bSP.png Also, why does it add that ADDED TIMESTAMP field to the tag when I do that?

I'm really bewildered! Can you help me more please. I'd really appreciate it.

EDIT:
Quote from: grimes on
The metadata has to be transferred to the database with Import statistics from file tags or use $meta(rating).
How do I do Import statistics from file tags? And do I want to? I've spent a lot of time rating tracks and I'd cry if they got overwritten by the hidden 5 ratings that I've only just found out about. What does Import statistics from file tags do?
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2022-11-06 15:53:11
%rating% displays the database value 5, $meta(rating) the tag value 2.

Backup your database with Library | Playback Statistics | Export Statistics
Import statistics from file tags overwrites your statistics database with the tag values.

What I don't understand: You set the database to 5, so immediately the tag value should update to 5

Your keyboard shortcut doesn't work. (See attachment)


Title: Re: foobar2000 v2.0 bugs
Post by: InchPerfect on 2022-11-06 16:06:50
Thanks again.

I'm still not quite getting it. But a quick question while I try and get to grips with what your saying ...

Are you saying my rating shortcut is wrong (see attached)?

Oh and where is "Import statistics from file tags"?
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2022-11-06 16:13:22
I recommend to use Playback Statistics to set ratings, not the tagger. The tagger writes the tag only and not the database and the tag. That's the cause for your confusion.
Title: Re: foobar2000 v2.0 bugs
Post by: InchPerfect on 2022-11-06 16:15:17
Can I transfer the ratings I've already done to the database?
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2022-11-06 16:18:39
Check first the ratings in your database with %rating% (because you think there are wrong "hidden" 5).
Title: Re: foobar2000 v2.0 bugs
Post by: InchPerfect on 2022-11-06 16:19:47
How do I do that? Sorry.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2022-11-06 16:21:22
 Add a column to playlist viewer with %rating%.
Title: Re: foobar2000 v2.0 bugs
Post by: InchPerfect on 2022-11-06 16:41:34
Getting there.

1. How do I set the Playback statistics rating to 0 or not rated?

When I try to change it to not rated, it stays the same.

So I tried changing all my unrated tracks to a 1 rating and then doing Rating - (minus) but again it stayed the same.

Then I tried deleting the rating from Properties but again they all still say 1 in my new %rating% column.

EDIT: And setting the rating to 0 in Properties doesn't change the rating either.

2. And, by the way, is my Rating field in Properties wrong? I have it as Rating=RATING in Preferences. But as I say, I've just made that field empty via Properties but the %rating% column says they are all rated 1.

Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2022-11-06 16:48:29
Rating 0 or -1 doesn't exist. To remove rating, use context menu playlist | Playback Statistics | Rating | <not set>

Rating=RATING works here.
Title: Re: foobar2000 v2.0 bugs
Post by: InchPerfect on 2022-11-06 17:00:34
As I said, I tried that but it doesn't work.

It has a dot next to "not set" in the context menu thing but it still says 1 in the %rating% column. This may be a bug I suppose?

EDIT; Here's a couple of screenshots. Before and after. They're the same (except that when I set it to "not set", one star gets added to my $pad($repeat(★,$meta(rating)), 5,) column - strangely).
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2022-11-06 17:21:08
I guess, there went something wrong during conversion to v2. Try it with a new installation of v2 (I know its a lot of work).
Title: Re: foobar2000 v2.0 bugs
Post by: InchPerfect on 2022-11-07 03:27:52
OK, grimes, my old friend. I had to take a break but here's an update.

I did a completely fresh install of fb2k v2 beta 12 (portable).

When I use context menu playlist | Playback Statistics | Rating | <not set> on fewer than 100 tracks (that are currently tagged with one star), it works fine. The rating gets removed.

When I do it on 100 tracks or more, it doesn't work.

I've tried it on several amounts between 1 and 99 and it always works fine. Any number I've tried over 99, it always fails.

All my tracks are mp3s with only ID3v2.3 tags.

My best guess is that fb2k wants to send me a warning that I'm about to tag 100 tracks or more, but there's a bug which doesn't throw up the warning and therefore fb2k doesn't run the task.

Hope that helps.
Title: Re: foobar2000 v2.0 bugs
Post by: InchPerfect on 2022-11-07 04:00:40
Rather than edit my previous post, I'll put this here because I think it's a separate issue.

I wanted to save time changing my 1-star ratings to "not set". So rather than doing them 99 tracks at a time, I did a fresh install of v1 latest.

I installed Facets (because I couldn't work out how to get the Playlist viewer to populate with all my tracks without it) and installed Playlist statistics (to set the ratings).

But then, when I added a Rating column (%rating%), all my tracks have a question mark in that column. It's infuriating lol!

Attached is a screenshot of one track that is rated 4 as you can see in Properties on the left, but shows a question mark in the Rating column on the right.

As a reminder, I rated the tracks using context menu playlist | Playback Statistics | Rating | <not set> in v2 beta 12 as suggested by you, so the ratings should be in the database and the tags, I believe.

What's going on? Why don't the ratings show up in the rating column?

Thanks yet again. So sorry to bother you with this rather trivial stuff.
Title: Re: foobar2000 v2.0 bugs
Post by: InchPerfect on 2022-11-07 05:51:52
Quote from: grimes on
Ratings are not displayed properly. Track shows 4, context menu 5 and Properties 4.5. 4.5 was the result of conversion from 1.6.12 to 2.0, should be 4
On another note. Not sure if this is related ...

Why do the ratings (which hopefully I've done right now* as per our discussion above) not show up in mp3tag?

I have more than a thousand rated tracks but only 34 have ratings according to mp3tag. (All my tracks have ID3v2.3 tags.)

*[I now have a custom column using $pad($repeat(★,%rating%), 5,) and my keyboard shortcuts use  Playback Statistics>Rating instead of Quick Tagger.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2022-11-07 07:40:44
Limit 99 tracks: There is no 3 digits limit in foobar2000. Don't know whats wrong.

?: ? indicates that the rating is MISSING (not set).

mp3tag: I don't know.

Verify integrity of your MP3's. There seems to be some of them corrupt.
Title: Re: foobar2000 v2.0 bugs
Post by: InchPerfect on 2022-11-07 07:50:28
Quote from: grimes on
?: ? indicates that the rating is MISSING (not set).
That's what I mean. They are rated. I used Playback statistics to do it properly but they show ? in v1.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2022-11-07 07:55:12
Priority is to fix your faulty files in your media library. This is the prerequisite for a working rating system.

Mark all tracks in playlist | rightclick | Utilities | Verify integrity
Title: Re: foobar2000 v2.0 bugs
Post by: InchPerfect on 2022-11-07 08:05:00
Quote from: grimes on
Limit 99 tracks: There is no 3 digits limit in foobar2000. Don't know what's wrong.
So I'm reporting a bug: You can't set more than 99 tracks to <not set> in v2.
Title: Re: foobar2000 v2.0 bugs
Post by: InchPerfect on 2022-11-07 08:13:00
Quote from: grimes on
Priority is to fix your faulty files in your media library. This is the prerequisite for a working rating system.

Mark all tracks in Media library | rightclick | Utilities | Verify integity
Yeah, I was just doing that already.

The vast majority are OK.

23 items could not be correctly decoded.
237 items decoded with minor problems.

I quite sure that is not the problem.

I've rated many hundreds of tracks and none of them show a rating in v1. And only 34 show a rating in mp3tag.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2022-11-07 08:17:38
Fix the MP3's: Fix VBR MP3 header or Rebuild MP3 stream.
Title: Re: foobar2000 v2.0 bugs
Post by: Porcus on 2022-11-07 13:20:54
I don't do that as long as they play fine - since the files are kinda not-totally-well, I would rather not touch them if they behave nice and gapless.
Of course some that display lengths that are way off ... too tempting not to fix.
Title: Re: foobar2000 v2.0 bugs
Post by: InchPerfect on 2022-11-12 06:18:44
This fairly simple query (I created a Filter) doesn't seem to work in v2 but does work in v1.

(NOT %genre% HAS Compilation) AND (album artist HAS Various)

Is it a bug or am I doing something wrong? Thanks.

[Also, I don't understand whether I should be writing %genre% or genre, and %album artist% or album artist? (but, as I say, this works as it is in v1. I'd just like to know for future reference please. I couldn't work it out by reading this page: https://wiki.hydrogenaud.io/index.php?title=Foobar2000:Query_syntax)]

[Also, there doesn't seem to be any mention of %play_count% on this page: https://wiki.hydrogenaud.io/index.php?title=Foobar2000:Title_Formatting_Reference. It's used in the built-in Filters like %play_count% MISSING. Is that just because it's still in beta?]
Title: Re: foobar2000 v2.0 bugs
Post by: Porcus on 2022-11-12 09:06:41
TAK md5 sum not shown; a query for %__md5sum% MISSING returns all TAK files.
It was like that in 1.6 as well, but 2.0 is supposed to support TAK out-of-the-box, so now it isn't a component issue.

takc -fi gives information comparable to WavPack codec profile and version. Like this:
Code: [Select]
  Encoder:                 V 2.3.2, -p4m
  Codec:                   4 Integer 24 bit MC (TAK 2.2)
  Wave file meta data:     Not available
  MD5:                     2204d09a890b8211f0d1329adc1daa8a

... so maybe a suggestion or two:
* What is, say <WAVPACK_VERSION> = 5, make it <FORMAT_VERSION> = WavPack 5. What for .ape is <VERSION> (say 3.99), make it <FORMAT_VERSION> too. Report <FORMAT_VERSION> TAK 2.2 or something for the above.
(I don't know if the <FLAGS> in .ape is used for anything?! Could it be other than 0?)
* %__md5% be remapped to look for MD5 and if "missing", DSD audio MD5.
It does already returns Monkey's checksum on encode, which is something else - so then maybe even consider to include audiomd5 tags as written by the foo_audiomd5 external component (https://foobar.hyv.fi/2.0/?view=foo_audiomd5), since they are computed either the same way as the ape or on the PCM.
* Oh, and WavPack hybrid should be reported as hybrid lossless or hybrid lossy, and transcoding warnings be fixed (https://hydrogenaud.io/index.php/topic,123325.0.html).

Title: Re: foobar2000 v2.0 bugs
Post by: iangk on 2022-11-12 12:15:36
Quote from: InchPerfect on
This fairly simple query (I created a Filter) doesn't seem to work in v2 but does work in v1.

(NOT %genre% HAS Compilation) AND (album artist HAS Various)

Is it a bug or am I doing something wrong? Thanks.

[Also, I don't understand whether I should be writing %genre% or genre, and %album artist% or album artist? (but, as I say, this works as it is in v1. I'd just like to know for future reference please. I couldn't work it out by reading this page: https://wiki.hydrogenaud.io/index.php?title=Foobar2000:Query_syntax)]

[Also, there doesn't seem to be any mention of %play_count% on this page: https://wiki.hydrogenaud.io/index.php?title=Foobar2000:Title_Formatting_Reference. It's used in the built-in Filters like %play_count% MISSING. Is that just because it's still in beta?]

Same for me. It seems to be the first part of the string i.e. 'NOT %genre% HAS Compilation' that's causing the issue. It seems to be the NOT that's failing - '%genre% HAS Compilation' works.
Interestingly substituting IS for HAS doesn't cause the same problem, so 'NOT %genre% IS Compilation' works.
It's a different query of course, but is seems to be the combination of NOT and HAS. Works as expected in v 1.6.13
Title: Re: foobar2000 v2.0 bugs
Post by: Porcus on 2022-11-12 13:08:21
Must be a bug.
Returns nothing: album MISSING AND NOT album HAS e
Returns nothing: %album% MISSING AND NOT album HAS e
Works as should: album MISSING AND NOT %album% HAS e
Works as should: %album% MISSING AND NOT %album% HAS e


Title: Re: foobar2000 v2.0 bugs
Post by: pqyt on 2022-11-16 19:06:43
foobar2000 2.0 beta 13 installer (but the older versions had the same problem)

- The suggested installation location defaults to "Desktop" but when you start to browse for another location it somehow remembers the previous location of the portable installation and shows that.

Suggested fix: if there is a previous portable installation, default to that location.
Title: Re: foobar2000 v2.0 bugs
Post by: pqyt on 2022-11-16 20:32:35
foobar2000 2.0 beta 13:

- The GDI rendering of the standard Spectrum Analyzer visualization component is plain awful on Windows 11: A lot of stuttering

Beta 12 performed very smoothly.
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-11-16 20:35:19
Erm....

Quote
Reverted visualisations to GDI rendering by default. Use advanced preferences toggle to enable D2D. Too many systems fail at D2D rendering.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2022-11-16 21:11:16
This? Use hardware acceleration
Title: Re: foobar2000 v2.0 bugs
Post by: pqyt on 2022-11-17 05:49:13
I know. I changed the setting. I'm just reporting the observed behavior.
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-11-17 06:11:53
Quote from: pqyt on
I know. I changed the setting. I'm just reporting the observed behavior.

Why did you mention Beta12 performing very smoothly when gdi rendering wasn't available. It was hardware accelerated with no choice. You're not making any sense.
Title: Re: foobar2000 v2.0 bugs
Post by: Belomor on 2022-11-17 09:45:05
Still unable to access my network shares with Beta 13.

Quote from: Belomor on
2.0 Beta 12 fails to read my windows network share where my media library resides. The error text is "Unable to open item for playback (I/O error (win32 #24)):". Neither mounted drive nor UNC path works.
It has always worked fine with 1.x versions.
Title: Re: foobar2000 v2.0 bugs
Post by: paregistrase on 2022-11-17 17:59:40
Good news in the linux-wine front.

High CPU usage with visualizations is gone.

Upgrading 1.16 installation with v2.13 without missing files or crashes.

Thanks devs

Title: Re: foobar2000 v2.0 bugs
Post by: Akczht on 2022-11-20 09:41:31
Alright , I know I've brought it up before also but I would like to add something , "⁄" & "∕" , are the current replacement for the solidus foobar2000 , which looks absolute dogwater imho on all mainstream operating systems out of the box , I would like to present two suggestions "⧸" (Big Solidus) and  "／" (Full-width Solidus) , full width solidus looks amazing on all apple devices but looks not so amazing on windows and the big solidus is good everywhere , a replacement that could make the ":" (Colon) look a little better is "：" (Full-Width Colon) it also looks good on most devices , current replacement is "∶" . Please! implement anything except the current replacements.
Title: Re: foobar2000 v2.0 bugs
Post by: Bogozo on 2022-11-20 17:45:51
Is remembering volume level per-device a bug or feature? If it is feature, could it be made optional?
Title: Re: foobar2000 v2.0 bugs
Post by: InverseDecay on 2022-11-25 01:29:47
Quote from: grimes on
Quote from: suisei on
Statistics such as rating is now hard linked to the file path, which means if the file is moved, the rating is loss.

Please add an option to use the old Playback Statistics (foo_playcount) behavior. While this may not be as accurate, it is good enough for me.

If not, please allow the use of the old foo_playcount component, and recompile it for 64 bit.

Thank you.
That's not true. Beside the Playback Statistics database, the data (rating etc.) can be written to file tags. This can be done automatically by store playback statistics in file tags in Preferences or manually by Write statistics to file tags in context menu. If you loose the playback statistics database, restore it with Import statistics from file tags in context menu.

I can only repeat what the other user said. It IS broken. I experienced this issue with music in a zip archive in beta12. In an old playlist with the old path the statistics were there, but in a new playlist with the new zip path, they were missing. Upgrading to latest beta13 still shows the same error. It also happens with normal files. I'm actually surprised I haven't noticed it before. The "View Report" function in the Playback Statistics settings page also tracks them per-path.

Other problems that exist since at least beta8: File path search is broken in Media Library Search and Playlist Search.

Not to diminish the work of the developers, but if I would have known that this "beta" is still so unpolished and doesn't receive fixes for reported bugs for months, I would have not switched. Even with the enticing dark mode..

I guess there is no way for me to go back to the old version without having to redo all my config changes and statistics changes that happened in the meantime, right? Writing statistics to file tags is not a realistic option..
Title: Re: foobar2000 v2.0 bugs
Post by: Thegreen16 on 2022-11-25 02:15:17
Does anyone know if WASAPI will be returning for x64?
Title: Re: foobar2000 v2.0 bugs
Post by: sveakul on 2022-11-25 03:23:19
Quote from: Thegreen16 on
Does anyone know if WASAPI will be returning for x64?
The "Default" output device for v2 x64 IS Wasapi, man.  You can choose "Default...[exclusive]" or just "Default.." which is shared.
Title: Re: foobar2000 v2.0 bugs
Post by: InverseDecay on 2022-11-27 06:52:16
OK, it gets even better, the whole rating statistics are completely broken. There are "hidden" x.5 ratings, seemingly the ones that got imported from fb2k 1.6. This was also already reported by @metal_termite . It gets even more ridiculous if you play around with this a bit. The sqlite database is very strange with apparently two places with rating saved? Once is normal, but also with these x.5 values, and another is a percentage(?!). This weirdness is also present if you export the stats to xml.

A track matching %rating% IS "1"     becomes RatingPercent="20" Rating="1"
A track matching %rating% IS "1.5"  becomes RatingPercent="30" Rating="2" (gets rounded up)

I can't trust this software anymore. There must be a very lax development process present with a seemingly unfinished software design for v2.0 and numerous undocumented, but conscious, changes. It's grossly irresponsible to release this as "beta"-quality software.
Title: Re: foobar2000 v2.0 bugs
Post by: Chibisteven on 2022-11-27 08:59:32
Quote from: InverseDecay on
Not to diminish the work of the developers, but if I would have known that this "beta" is still so unpolished and doesn't receive fixes for reported bugs for months, I would have not switched. Even with the enticing dark mode..

I guess there is no way for me to go back to the old version without having to redo all my config changes and statistics changes that happened in the meantime, right? Writing statistics to file tags is not a realistic option.

Quote from: InverseDecay on
I can't trust this software anymore. There must be a very lax development process present with a seemingly unfinished software design for v2.0 and numerous undocumented, but conscious, changes. It's grossly irresponsible to release this as "beta"-quality software.

It's beta software.  Exercise some common sense here.  It's for testing purposes, not for regular everyday use.  I'm still using 1.6.14 at the moment as that's the last stable version of the software for regular everyday use.  Only using 2.0 for testing and finding bugs at the moment because it's in beta.  Software can be in beta for months, it's a lot more common than you think it is.
Title: RATING empty in column
Post by: Forfit on 2022-11-28 05:26:25
When I add a "RATING" tag to a mp3, it not show in "Rating" column of DUI, also if I rescan media library.
It show only old "RATING".
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2022-11-30 13:56:37
Quote from: Belomor on
2.0 Beta 12 fails to read my windows network share where my media library resides. The error text is "Unable to open item for playback (I/O error (win32 #24)):". Neither mounted drive nor UNC path works.
It has always worked fine with 1.x versions.
What Windows version and what kind of network shares (hosted on what machine)?
Which version of foobar2000, 32-bit or 64-bit? Does the other version work?
Error 24 is ERROR_BAD_LENGTH (https://learn.microsoft.com/en-us/windows/win32/debug/system-error-codes--0-499-), sounds like a bug in my code, but can't quite figure out what it is and it doesn't seem to happen for anyone else.
Title: Re: foobar2000 v2.0 bugs
Post by: Peti on 2022-11-30 18:34:00
In Beta 14 this query is not working anymore: %path% HAS music\singles SORT BY %added% DESCENDING
it seems that if the path value has a slash and there is a space after the value the query is not returning any result
it was working fine till b13
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2022-11-30 20:45:50
Search index now includes paths by default. Unfortunately this seems to have introduced some quirks. You can turn it off: Advanced Preferences / Tools / Search / Index file paths. This will make %path% behave exactly as before.
Will investigate for next beta.

Edit: This is a valid bug affecting other queries not just path, thanks for reporting. Will be fixed soon.
Title: Re: foobar2000 v2.0 bugs
Post by: Belomor on 2022-11-30 21:31:14
Quote from: Peter on
Quote from: Belomor on
2.0 Beta 12 fails to read my windows network share where my media library resides. The error text is "Unable to open item for playback (I/O error (win32 #24)):". Neither mounted drive nor UNC path works.
It has always worked fine with 1.x versions.
What Windows version and what kind of network shares (hosted on what machine)?
Which version of foobar2000, 32-bit or 64-bit? Does the other version work?
Error 24 is ERROR_BAD_LENGTH (https://learn.microsoft.com/en-us/windows/win32/debug/system-error-codes--0-499-), sounds like a bug in my code, but can't quite figure out what it is and it doesn't seem to happen for anyone else.
foobar2000: 64-bit
Windows 10 21H2 with SMB/CIFS 1.0 compatibility package installed
The shares are hosted on a linux router, mounted read-only (can't tell the sort of the smb server, it's closed source, yet works ok with any windows app). Edit: R/W mount doesn't work either.
Didn't test it in foobar 32-bit.Edit: Foobar 32-bit fails with the same error.
Title: Re: foobar2000 v2.0 bugs
Post by: Squeller on 2022-12-01 09:09:49
Quote from: Peter on
Edit: This is a valid bug affecting other queries not just path, thanks for reporting. Will be fixed soon.
Oh thx! I have a lot of %path% filtering not working now.
%path% as part of the search index, what does it mean, why, what's the advantage, what can we use it for?
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2022-12-01 14:45:08
Quote from: Squeller on
%path% as part of the search index, what does it mean, why, what's the advantage, what can we use it for?
It means that plaintext searches (ones without expressions/operators) scan file paths.

It also means faster searches including %path%, using full text index instead of testing one-by-one if each track in the library passes criteria. Your search query is internally translated to actual SQL expression if not using anything not supported by search index. Watch console output when performing search to see some basic feedback on library index operations.
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2022-12-01 14:57:30
Beta 15 posted.

Status:
Search bugs = fixed.
Playback statistics bugs = acknowledged, pending for next update.
Network share = please get beta 15, it will crash encountering this error and generate a bug report. Auto submit the report and I'll have a better idea what's going on.

Thanks.
Title: Re: foobar2000 v2.0 bugs
Post by: Squeller on 2022-12-01 17:10:57
Quote from: Peter on
Search bugs = fixed.

OK, I have enabled the new path/index advanced option now. Still problems with paths - in playlist:

- I've got a big playlist with tracks somewhere in "M:\Music\Klassik\Blah..."
- I've got ReFacets set to "Playlist" and this filter:

Code: [Select]
%path% HAS \Klassik\

Filter shows no entries in the Refacets. If I turn the filter off, all attributes of playlist entries appear.

Do I need to re-index maybe? (EDIT: No, no change)
Title: Re: foobar2000 v2.0 bugs
Post by: papavlos on 2022-12-02 17:18:22
When on Linux / wine some components miss foobar color scheme and are using system default.
See attached: "Selection Properties" and "Playlist Manager" properly use Blue color scheme whereas "Console" and "Album List" are not properly painted. The "Album List" seems to have texts properly colored, only the background unused by text remains white.
Same behavior in both 32- and 64-bit versions.
The bug is present in all betas (15 is the last tested).
Title: Re: foobar2000 v2.0 bugs
Post by: djdron on 2022-12-02 19:01:45
I have 7z/rar's with .wma's inside which are not appeared in Album List in "by folder structure" view.
Also I have .zip's with many zxtune-associated file types. They also not appeared in Album List at all (in different view modes).
If I unpack them from .zip - all fine.
Also I have playlists from foobar 1.6 32 bit with parsed files from that .zip's - they played OK.
Tested on latest beta 15 - same.
Title: Re: foobar2000 v2.0 bugs
Post by: djdron on 2022-12-02 19:06:04
Also I noticed big font in track properties tabs.
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2022-12-03 14:26:15
Beta 16 out

Change log (https://wiki.hydrogenaud.io/index.php?title=Foobar2000:Version_2.0_Beta_Change_Log)

I'll skip change log copypasting and just say what is still pending investigation:
If there's something else important that I missed, mentioned earlier in this thread, please repost.

I added splitter locking, but I'm not sure that's what some of you people are after. The ability to lock width/height of stuff was a bit of a side effect of old splitter implementation, I can add some other way to do this, without having to add splitter.
Title: Re: foobar2000 v2.0 bugs
Post by: djdron on 2022-12-03 21:36:29
Peter
Seems files from zip/7z/rar archives fixed in Album List in "by folder structure" view in beta 16.
But not for file types registered in zxtune plugin.

When I do File->Add files.../Add folder... - zxtune-registered file types successfully added to playlist.
Title: Re: foobar2000 v2.0 bugs
Post by: Belomor on 2022-12-04 06:59:04
Quote from: Peter on
Beta 16 out

Now it works (the network issue is gone). Thanks a lot!
Title: Re: foobar2000 v2.0 bugs
Post by: InverseDecay on 2022-12-04 15:12:05
Thanks for these fixes, Peter!

Quote from: Peter on
Playback statistics bugs = acknowledged, pending for next update.
Do you plan to go back to non path-bound playback statistics? The new system is very inflexible. You can't move folders or files outside of foobar2k. And tracks in archives can't even be moved with the internal tool.
Title: Re: foobar2000 v2.0 bugs
Post by: Squeller on 2022-12-04 15:45:49
Many thanks!
- B16 has fixed my issues about filtering by path.
- Welcome change of the properties column font. I also didn't like the big one.
Title: Re: foobar2000 v2.0 bugs
Post by: NorthGraves on 2022-12-05 00:37:21
Foobar2000 2.0 Beta 16 - still the same bug in Directory Opus:

Selecting multiple audio files and hitting Enter in Directory Opus makes foobar2000 2.0 go through the audio files one by one and only playing the last one.

No such problem in foobar2000 1.6.
Title: Re: foobar2000 v2.0 bugs
Post by: anamorphic on 2022-12-05 04:42:52
Thanks Peter. The locked splitters work fine that way. I can live with it, though I would point out the new method has disadvantages when resizing the window. i.e. Say you previously had 3x3 element layout, and wanted to lock the outside elements (to say 50px), with only the middle element scaling - this is no longer possible. On resizing / maximizing they all "scale proportionally" whereas previously the locked elements would keep a fixed width / height. (A minor issue I can live with like I said, but the old saying "if it ain't broke, don't fix it" kind of comes to mind ;) )

A few ReFacets remaining issues (aside from extra feature requests) -

I believe there needs to be a "Default sort order" option box in Preferences > Media Library > ReFacets (like Facets) - column library viewers need a way to sort the playlist. If user wants to auto- sort playlist by %date% for example, this is currently not possible. (Several mentions in ReFacets (https://hydrogenaud.io/index.php/topic,122835.0.html) topic). ->
Quote from: iangk on
Are there plans to add the "Default sort order" option from Facets to Refacets so that the playlist view can be automatically sorted?

Toolbar buttons have black drop arrows. ->
Quote from: LordWarlock on
UI glitch: In dark mode the Library and Filters dropdown uses black (=invisible) arrows.

Toolbar does not expand and locked toolbar reverts position on restart. ->
Quote from: iangk on
A toolbar glitch: The filter dropdown, selecting a new filter which has a longer character length doesn't increase the size of the box, so the dropdown selector gets hidden. If the width is manually increased (moving the search bar to the right), that's OK until FB2K is restarted, then it reverts back to the width of the currently displayed filter. Locking the toolbar doesn't help, it just makes it impossible to expand the dropdown.

Finally an old curiosity / glitch I noticed - there appear to be two styles of Album List? ... In View > Layout > Quick Setup, clicking through the "Main Layout" options, one Album List has grey background, while the other has white background. Also, add an Album List to a blank splitter = grey. Then use Replace UI Element on it with Tabs = white.
Title: Re: foobar2000 v2.0 bugs
Post by: danielgwan on 2022-12-06 04:42:40
Quote from: InverseDecay on
Thanks for these fixes, Peter!

Quote from: Peter on
Playback statistics bugs = acknowledged, pending for next update.
Do you plan to go back to non path-bound playback statistics? The new system is very inflexible. You can't move folders or files outside of foobar2k. And tracks in archives can't even be moved with the internal tool.

Vote for non path-bounding playback statistics. And I really don't want write ratings to the file.

Yesterday I changed folder name, and found all my song ratings in the folder were lost. Thousands of ratings were made by effort during these years, that was not Foobar2000 1.6 behavior. Please consider undo that.

As to saving ratings to the file tag, that's not a good choice for me at least. I would like foobar2000 to handle my playback statistics, not writing the file tag and change the file everytime I play it or rate it. Otherwise it would brings big trouble for me to do the file incremental backup, the file will be re-backup every it is modified, that's really silly. Please consider.
Title: Re: foobar2000 v2.0 bugs
Post by: Porcus on 2022-12-06 06:28:06
Quote from: danielgwan on
As to saving ratings to the file tag, that's not a good choice for me at least. I would like foobar2000 to handle my playback statistics, not writing the file tag and change the file everytime I play it or rate it. Otherwise it would brings big trouble for me to do the file incremental backup, the file will be re-backup every it is modified, that's really silly. Please consider.

foo_external_tags might be a thing for you? Tags in a database or in files in the same folder. Gives an opportunity to back up tags only.
https://foobar.hyv.fi/2.0/?view=foo_external_tags
Title: Re: foobar2000 v2.0 bugs
Post by: danielgwan on 2022-12-06 07:26:11
Quote from: Porcus on
Quote from: danielgwan on
As to saving ratings to the file tag, that's not a good choice for me at least. I would like foobar2000 to handle my playback statistics, not writing the file tag and change the file everytime I play it or rate it. Otherwise it would brings big trouble for me to do the file incremental backup, the file will be re-backup every it is modified, that's really silly. Please consider.

foo_external_tags might be a thing for you? Tags in a database or in files in the same folder. Gives an opportunity to back up tags only.
https://foobar.hyv.fi/2.0/?view=foo_external_tags

Thanks for the recommendation. I'll try it out. Still, it would be better if foobar2000 2.0 could undo that change.
Title: Re: foobar2000 v2.0 bugs
Post by: iridescentaudio on 2022-12-06 14:07:40
Is there any news/update on the situation of ratings from previous installations being imported with decimals like 1.5, 2.5, 3.5 etc.? Is a fix coming or is the expectation that users re-apply all track ratings manually to fix it?

Also +1 for external tags, great component, my backup strategy would be a nightmare without it since I store stats in tags (for peace of mind.)

Thanks.
Title: Re: foobar2000 v2.0 bugs
Post by: Bogozo on 2022-12-06 16:12:48
@Peter
No automatically reloading info from files when re-adding them into playlist (behavior no presented in 1.6.x) - https://hydrogenaud.io/index.php/topic,122970.0.html

Inconsistent appearance of Album List tree - https://hydrogenaud.io/index.php/topic,123169.0.html

Console UI element doesn't use theme color setting for background unless in dark mode.

I don't insist those are problems, but i would like to know if this is intended behavior.
Title: Re: foobar2000 v2.0 bugs
Post by: stefanhuber on 2022-12-06 23:30:10
Hello,

sorry if this has already been covered here. I have happily been using foobar2000 for many years. Unfortunately with the update to v.1.6.14 I was experiencing constant crahes. I have thus decided to upgrade to v2.0 beta16.

It seems if the problem with crashes is now gone, but most of my playback history is gone. I still have a copy of the v.1.6.14 installation. Should I try to install v2.0 again? Is there something I should keep in mind to successfully migrate the playback data to the new version or is this a known issue that will be resolved in future releases?
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2022-12-08 21:19:50
Quote from: NorthGraves on
Foobar2000 2.0 Beta 16 - still the same bug in Directory Opus:

Selecting multiple audio files and hitting Enter in Directory Opus makes foobar2000 2.0 go through the audio files one by one and only playing the last one.

No such problem in foobar2000 1.6.
Right click, "Open in foobar2000" with multi selection = good behavior, my shell extension is invoked once with multiple files.
Hitting enter with multi selection = bad behavior, my shell extension is invoked multiple times with single files.
I'd have to wait for more files instead of starting playback instantly. Sounds to me like it's their bug not mine?
Title: Re: foobar2000 v2.0 bugs
Post by: NorthGraves on 2022-12-08 23:04:43
Quote from: Peter on
Quote from: NorthGraves on
Foobar2000 2.0 Beta 16 - still the same bug in Directory Opus:

Selecting multiple audio files and hitting Enter in Directory Opus makes foobar2000 2.0 go through the audio files one by one and only playing the last one.

No such problem in foobar2000 1.6.
Right click, "Open in foobar2000" with multi selection = good behavior, my shell extension is invoked once with multiple files.
Hitting enter with multi selection = bad behavior, my shell extension is invoked multiple times with single files.
I'd have to wait for more files instead of starting playback instantly. Sounds to me like it's their bug not mine?

Very possible, but "their bug" is not present if using Foobar2000 1.6.

Hence something must have changed in Foobar2000 2.0 that specifically results in this "Hitting enter with multi selection = bad behavior, my shell extension is invoked multiple times with single files".
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2022-12-09 11:28:05
Quote from: NorthGraves on
Very possible, but "their bug" is not present if using Foobar2000 1.6.

Hence something must have changed in Foobar2000 2.0 that specifically results in this "Hitting enter with multi selection = bad behavior, my shell extension is invoked multiple times with single files".
I rewrote the whole shell extension in v2.0, so the shell now talks to foobar2000 using a different protocol: IExecuteCommand instead of IContextMenu. This has many advantages, most importantly avoids unnecessary loading of our code into Explorer.exe and every other app invoking these shell ops.

Mitigation on my side is possible, at cost of degraded performance (wait for more files before taking action).

I already use such workaround when adding files from command-line: foobar2000.exe <path-to-file>. The whole point of implementing the shell extension is being able to reliably send multiple files without hacks or delays.

While Directory Opus is awesome technology, this really looks like their bug. By convention, pressing enter or doubleclicking should perform the same action as the bold command in the context menu, no? Here it clearly does something different.
Title: SPLIT: Re: foobar2000 v2.0"Could not negotiate VST audio format" [split]
Post by: Peter on 2022-12-09 11:29:39
One or more of the messages of this topic have been moved to General - (fb2k) (https://hydrogenaud.io/index.php?board=27.0) - https://hydrogenaud.io/index.php?topic=123426.0
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2022-12-09 13:49:44
Beta 17 out.

Rating 0.5 issue = fixed: importing old database now produces correct results, first of beta 17 fixes badly imported values.
Title: Re: foobar2000 v2.0 bugs
Post by: NorthGraves on 2022-12-09 14:29:52
Quote from: Peter on
Quote from: NorthGraves on
Very possible, but "their bug" is not present if using Foobar2000 1.6.

Hence something must have changed in Foobar2000 2.0 that specifically results in this "Hitting enter with multi selection = bad behavior, my shell extension is invoked multiple times with single files".
I rewrote the whole shell extension in v2.0, so the shell now talks to foobar2000 using a different protocol: IExecuteCommand instead of IContextMenu. This has many advantages, most importantly avoids unnecessary loading of our code into Explorer.exe and every other app invoking these shell ops.

Mitigation on my side is possible, at cost of degraded performance (wait for more files before taking action).

I already use such workaround when adding files from command-line: foobar2000.exe <path-to-file>. The whole point of implementing the shell extension is being able to reliably send multiple files without hacks or delays.

While Directory Opus is awesome technology, this really looks like their bug. By convention, pressing enter or doubleclicking should perform the same action as the bold command in the context menu, no? Here it clearly does something different.

Thanks, I passed your answer to the Directory Opus developers.

I guess for now (for me) the options are what they are.
Stop using Directory Opus or back to foobar2000 1.6.
Title: Re: RATING empty in column
Post by: Forfit on 2022-12-09 22:50:35
Quote from: Forfit on
When I add a "RATING" tag to a mp3, it not show in "Rating" column of DUI, also if I rescan media library.
It show only old "RATING".
Solved in 2.0 beta 16.
Title: Re: foobar2000 v2.0 bugs
Post by: Snowknight26 on 2022-12-10 01:31:36
Quote from: Snowknight26 on
Time to add to the list. Found these using beta 3, 64-bit. Will update as I find more.

[...]

Didn't realize we couldn't edit posts. Beta 17 still has at least the following problems:


Additional things I've noticed:
Title: Re: foobar2000 v2.0 bugs
Post by: iridescentaudio on 2022-12-11 15:26:50
Quote from: Peter on
Beta 17 out.

Rating 0.5 issue = fixed: importing old database now produces correct results, first of beta 17 fixes badly imported values.

All seems well, thank you!
Title: Re: foobar2000 v2.0 bugs
Post by: GoodEnoughGear on 2022-12-13 07:01:22
Hi folks,

Beta 17 32 bit here on Win11 Pro, with the new VST component,  Resampler-V, UPNP, Playlist Attributes and ProjectM vizualizer.

I output to Virtual Audio Cable, and I've discovered that using Default output to the virtual line in is fine, no under or overruns and clear audio, but if I use the Default (Exclusive) I get on the order of about 150 underruns per second and the output is badly distorted. Event mode on or off does not make a difference, though having event mode on in earlier versions (separate WASAPI component) had the same effect. Maybe event mode is hardwired into exclusive Default and it doesn't follow the flag in advanced settings.

<<Update - Found the issue>>
OK, this is probably just a bit of poor UI, you need to check the "Exclusive Output Overrides" checkbox for the "Use event" checkbox to function - clearing this and checking override sorts out the underruns. On uncheck of "Exclusive Output Overrides" the child UI should gray out.

Anyway, thanks for all the hard work, loving this new version!
Title: Re: foobar2000 v2.0 bugs
Post by: acetone on 2022-12-14 00:25:12
This problem is not important, but lost a part of metadata on editing.

https://hydrogenaud.io/index.php/topic,123222.0.html

Not resolved both with 2.0 beta 17 and 1.6.14.
Title: Re: foobar2000 v2.0 bugs
Post by: Fabcore on 2022-12-14 17:38:17
When open a .fpl then close and open (restart the program), the playlist previously created by opening .fpl is gone, so i have to open again the fpl.

My bad day.
Title: Re: foobar2000 v2.0 bugs
Post by: MordredKLB on 2022-12-16 04:32:09
Upgrading to Beta 17 from 1.6.11 did not import any of my playback statistics. My Library paths were automatically set, but none of my playcount data was transferred over, it had to discover all the files again, and everything has a date added date of today. Not sure what could have gone wrong, but it's pretty bad and I don't know how to fix it.
Title: Re: foobar2000 v2.0 bugs
Post by: beat8000 on 2022-12-16 13:04:27
According to my test it's not possible to play first a DSD128 track and after that a PCM 96 kHz track with Beta 17-64bit, because the playing stops at the beginning of the second track.

However it works perfectly with Beta 17-32bit
Title: Re: foobar2000 v2.0 bugs
Post by: djdron on 2022-12-17 21:09:52
Quote from: djdron on
Peter
Seems files from zip/7z/rar archives fixed in Album List in "by folder structure" view in beta 16.
But not for file types registered in zxtune plugin.
Seems I fugured out how to fix this.
After renaming directory with this archives and then renaming back, zxtune-supported files appeared in Album List view.
Rescan folder in library did not work.
Seems some bug with db info from previous version of foobar2000 (was upgraded from 1.6).
Title: Re: foobar2000 v2.0 bugs
Post by: papavlos on 2022-12-18 11:40:16
Quote from: papavlos on
When on Linux / wine some components miss foobar color scheme and are using system default.
See attached: "Selection Properties" and "Playlist Manager" properly use Blue color scheme whereas "Console" and "Album List" are not properly painted. The "Album List" seems to have texts properly colored, only the background unused by text remains white.
Same behavior in both 32- and 64-bit versions.
The bug is present in all betas (15 is the last tested).
Version 17 fixes proper "Console" coloring, both in 32- and 64-bit versions.
The "Album List" UI Element waiting to be fixed.
Title: Re: foobar2000 v2.0 bugs
Post by: danielgwan on 2022-12-18 14:31:21
Found another problem for myself because of the "path bound playback statistics".

Due to my car USB's only-mp3-playable limitation, I keep all my songs in both 2 formats: one Apple Lossless and one MP3 format (MP3 files were kept on another harddisk, converted from the lossless files, so as to have the same tag info).

Before, I listened to and rated lossless songs on PC. Then from time to time I draged my whole MP3 format songs into foobar2000, they would show the same rating-stars which lossless songs had, so that I could easily use foobar2000's build-in File Operation-Copy To... function to copy the 5 star MP3 files to my USB disk for my car.

Now I can't do the same workflow, pity.
Title: Re: foobar2000 v2.0 bugs
Post by: Squeller on 2022-12-21 10:47:01
I've rescanned library, it now includes, as expected, a track with:
%added%: 2022-12-03 17:25:51

But a search "%added% DURING LAST 1 DAYS" does not find it.

Why is this?

Recent fb2k v2 beta, components up to date, 32 bit version. It's a portable instance operating on relative library paths, if that is important.
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-12-21 11:08:48
Quote from: Squeller on
%added%: 2022-12-03 17:25:51

But a search "%added% DURING LAST 1 DAYS" does not find it.

Today is the 21st. The 3rd was 18 days ago. 18 is more than 1. That's the reason it's not returned in the search results.

Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2022-12-21 21:50:42
Beta 18 out.

foo_playcount is usable again, internal playback statistics feature has been dropped.
First run of new foo_playcount imports old v2.0 beta database back to its own.

Also, I have rewritten playlist & library search cache/indexing.
IF you can find a case where the new search is still slower than foobar2000 v1.x series, please let me know.
Title: Re: foobar2000 v2.0 bugs
Post by: pqyt on 2022-12-21 22:08:57
Quote from: Peter on
Beta 18 out.

foo_playcount is usable again, internal playback statistics feature has been dropped.
First run of new foo_playcount imports old v2.0 beta database back to its own.

Also, I have rewritten playlist & library search cache/indexing.
IF you can find a case where the new search is still slower than foobar2000 v1.x series, please let me know.

Portable install crashes as soon as it starts. I removed all user-components from my profile and it keeps crashing.  Crash report was sent.
Title: Re: foobar2000 v2.0 bugs
Post by: ejp2472 on 2022-12-22 08:31:23
By my 18 simply hangs during start.
After removing the Library and Playlist folder under the profile (it could start)
And the library works when restarting.

But when i add a playlist it again hangs during start.
Removing the playlist folder makes it start again.
Title: Re: foobar2000 v2.0 bugs
Post by: MaFred on 2022-12-22 10:51:14
After Beta 18, the rating column in the playlists is empty. I went back to Beta 17, everything is OK.
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-12-22 11:05:41
https://wiki.hydrogenaud.io/index.php?title=Foobar2000:Version_2.0_Beta_Change_Log#Beta_18

Quote
Removed internal playback statistics, made Playback Statistics component (foo_playcount) operational again. First run of new foo_playcount imports foobar2000 v2.0 beta database back.

Obviously an updated version of foo_playcount with 32bit/64bit support has been released at the same time...

https://www.foobar2000.org/components/view/foo_playcount

Title: Re: foobar2000 v2.0 bugs
Post by: MaFred on 2022-12-22 12:03:00
Thank you, that worked.
Title: Re: foobar2000 v2.0 bugs
Post by: InchPerfect on 2022-12-22 12:13:28
Quote from: marc2k3 on
https://wiki.hydrogenaud.io/index.php?title=Foobar2000:Version_2.0_Beta_Change_Log#Beta_18

Quote
Removed internal playback statistics, made Playback Statistics component (foo_playcount) operational again. First run of new foo_playcount imports foobar2000 v2.0 beta database back.

Obviously an updated version of foo_playcount with 32bit/64bit support has been released at the same time...

https://www.foobar2000.org/components/view/foo_playcount


This wiki page should be updated, I think. https://wiki.hydrogenaud.io/index.php?title=Foobar2000:Components/Playback_Statistics_v3.x_(foo_playcount)

Screenshot attached.
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2022-12-22 13:13:51
Crash regression fixed in beta 19, thanks for the sent reports.
Title: Re: foobar2000 v2.0 bugs
Post by: Monno on 2022-12-22 15:45:47
beta 19 did not import my playlist statistics for most of my library. I was able to recover 95% from a back up. Wishing I would have backed up the stats before installing the update.
Title: Re: foobar2000 v2.0 bugs
Post by: Mrakobes on 2022-12-23 06:17:36
beta 19 does not start. in the 18th beta, a problem appeared, stopped running, while the database in the root folder with the discography and ratings disappeared. I installed cheat 19 and moved the profile folder, but it does not start
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2022-12-23 11:47:09
Quote from: Monno on
beta 19 did not import my playlist statistics for most of my library. I was able to recover 95% from a back up. Wishing I would have backed up the stats before installing the update.
Note that old foobar2000 v2.0 beta playback statistics are *not* being deleted.
If you go back to beta 17, it will show your old playback statistics again. Though import/export format is incompatible between the two systems for now. (But please back your profile up before downgrading for good measure)
Quote from: Mrakobes on
beta 19 does not start. in the 18th beta, a problem appeared, stopped running, while the database in the root folder with the discography and ratings disappeared. I installed cheat 19 and moved the profile folder, but it does not start
Please auto submit crash reports from the latest version. It will make figuring the cause out much easier for me.
Title: Re: foobar2000 v2.0 bugs
Post by: iangk on 2022-12-23 14:33:26
I updated from beta 17 to 19 (portable, windows 10 x64), and installed foo playcount 3.1, but it didn't import the playback statistics from beta 17. Every track shows added today.
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2022-12-23 14:56:28
Problem acknowledged.
Please don't worry, nothing is actually erased from the database.
Reverting to beta 17 will make your stats visible again-
https://www.foobar2000.org/getfile/foobar2000_v2.0_beta_17.exe
https://www.foobar2000.org/getfile/foobar2000-x64_v2.0_beta_17.exe

Problem is being investigated and will be autocorrected if possible.
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2022-12-23 15:05:43
Disregard that, I fail at coding.

foo_playcount update in a moment, will fix this mess automatically and recover your data.
Title: Re: foobar2000 v2.0 bugs
Post by: ApacheReal on 2022-12-24 06:55:50
Hello.

I point out that in the conversion phase the file name formatting option is not stored and a space is added at the end.

https://ibb.co/WscsYdH

https://ibb.co/PwnfHzJ

foobar2000 v2 32bit beta19



Title: Re: foobar2000 v2.0 bugs
Post by: metal_termite on 2022-12-25 07:11:47
foobar2000 v2.0 beta 19 32-bit [Windows 11]

I've noticed item counts for auto-playlists, displayed by foo_plorg, do not update after metadata is changed unless I change the playback state of a track. For instance, an autoplaylist with the query "genre IS synthwave" has an item count of 100. If I delete "synthwave" from the genre of 1 track, the item count will remain 100 until I play a track, stop a track, or change a track.

I've never noticed this behavior before with prior beta versions, and I have skipped the last several.
Title: Re: foobar2000 v2.0 bugs
Post by: ghf_50 on 2022-12-25 14:14:51
foobar2000 v2.0 x64 beta 19 on Windows 11
There are two Peak Meter in the toolbar's right click menu.
Title: Re: foobar2000 v2.0 bugs
Post by: oberon0470 on 2022-12-26 03:26:56
I don't know if this is a bug but when playing a cue sheet in v2 both 32 bit & 64 bit there is a pause between tracks that is not there in the 1.6 versions. It seems to reset before playing the next track. In the task bar using CUI it says 'Opening' for about a second before beginning to play. In 1.6 it flashes so quick I can't read 'Opening'

When converting to a multi track file from a cue you can see the converter speed drop to zero between tracks. On 1.6 the speed drops a little (ex. from 64x to 59x) but not close to zero.
Title: Re: foobar2000 v2.0 bugs
Post by: alpha_zzz on 2022-12-27 13:11:28
When string includes specific keywords, the last word (or character) becomes omitted on tooltip.

Example string: "foobar 3rd 123 456 789.mp3"
Tooltip: "foobar 3rd 123 456"
In this case, the string is file name and the keyword is "3rd" then "789" is not show on tooltip.

The tooltip will be shown when you mouse over the string which is partially hidden. I saw such tooltips in file name field as well as playlist name field.
I found several keywords which cause above bug. For example they are "3rd", "4th" and others. In other words, they are lower case substring "rd" following "3", or "th" following any number. ("1st" and "2nd" are no problem.)
Therefore below file name and playlist name also can reproduce this bug.
"foobar2000theme.mp3" -> "foobar2000them"
"foobar2000the best playlist" -> "foobar2000the best"
Title: Re: foobar2000 v2.0 bugs
Post by: Monno on 2022-12-27 16:02:20
Quote from: Peter on
Quote from: Monno on
beta 19 did not import my playlist statistics for most of my library. I was able to recover 95% from a back up. Wishing I would have backed up the stats before installing the update.
Note that old foobar2000 v2.0 beta playback statistics are *not* being deleted.
If you go back to beta 17, it will show your old playback statistics again. Though import/export format is incompatible between the two systems for now. (But please back your profile up before downgrading for good measure)
Quote from: Mrakobes on
beta 19 does not start. in the 18th beta, a problem appeared, stopped running, while the database in the root folder with the discography and ratings disappeared. I installed cheat 19 and moved the profile folder, but it does not start
Please auto submit crash reports from the latest version. It will make figuring the cause out much easier for me.

I have the latest updates and something I'm noticing with foo_stats is that some albums have multiple %added%. I know what the timestamp for the date added should be for the entire album, but i am unable to update it. Resetting stats and importing from file tags or from a .xml file does not correct the date added field.
I even tried to mess with meta data from .sqlite file with no luck. Not sure that to think about this. Thoughts?

[Update]
Something to note with my issue is that albums added to my library before foobarV2 have this issue. Albums (Like the albums I got for Christmas) do not.
Title: Re: foobar2000 v2.0 bugs
Post by: Mrakobes on 2022-12-27 18:08:37
I am very sorry that I switched to 2.0 so early, I am surprised that the product is so raw. I really love this player, statistics and rating are very important to me, while I'm on 1.6, let users younger than me test
Title: Re: foobar2000 v2.0 bugs
Post by: neothe0ne on 2022-12-27 23:55:15
I see in the 2.0 change log that,
Quote
First run performs import of old configuration data (playlists, library).

However, I installed 2.0 beta 19 over a copy of my 1.6.15 folder, and after several minutes before foobar2000 2.0 finished loading, I can see my playlists, but my autoplaylists and my library are empty.  My library is setup as the relative path "..\Music\", where my foobar2000 folder is at the same level as my Music folder.  Is this expected behavior?

If I right-click that Music folder entry and rescan, then things start appearing, but I would have expected the 2.0 import/first load procedure to have already found the files.
Title: Re: foobar2000 v2.0 bugs
Post by: MaFred on 2022-12-28 10:47:01
Since foobar V2, I very often get the error "Unsupported format or corrupted file" when loading an fpl playlist (saved with V2).
The playlist is then not complete.
This happens with an existing playlist, a new playlist and with an Album list generated playlist. No console error message.
I attach a m3u playlist as an attachment.
If this m3u playlist is loaded, then saved as an fpl playlist, and the fpl playlist is then loaded again, I get the above error message.
fpl playlists from foobar1.6 can be loaded once without any problems.
Title: Re: foobar2000 v2.0 bugs
Post by: Air KEN on 2022-12-29 15:27:58
Hi :)

foobar2000 v2.0 beta 20 32bit (Default UI, Columns UI 2.0.0-alpha.5)
・Clicking (manipulating) ReFacets freezes.

no problem:
-foobar2000 v2.0 beta 20 64bit Default UI, Columns UI 2.0.0-alpha.5
-foobar2000 v2.0 beta 19 32bit + Columns UI 2.0.0-alpha.5

Start Up Consol
https://mega.nz/file/gDEFQQIQ#uUXeEfQfJSQshNSdxQjwokpgHlWQGL5W6hBwnTA7UFs

ReFacets Filters
https://i.imgur.com/HTTCeRm.png

Anyone have the same symptoms?
Title: Re: foobar2000 v2.0 bugs
Post by: dypsis on 2022-12-30 04:13:59
I run a fairly standard setup, but I couldn't get the v2.0 Beta 20 configuration to look anything like I had with v1.6.14.
I've gone back to v1.6.14 for now.
Title: Re: foobar2000 v2.0 bugs
Post by: demirkoray on 2022-12-30 20:23:41
v2.0_beta_16 can play my 24 bit files.
v2.0_beta_20 says: Unsupported stream format: 96000 Hz / 24-bit / 2 channels (0x17700)

All settings are identical. I just update the version, and then I cannot play my 24 bit files anymore.
Title: Re: foobar2000 v2.0 bugs
Post by: sveakul on 2022-12-30 22:47:54
Quote from: demirkoray on
v2.0_beta_16 can play my 24 bit files.
v2.0_beta_20 says: Unsupported stream format: 96000 Hz / 24-bit / 2 channels (0x17700)

All settings are identical. I just update the version, and then I cannot play my 24 bit files anymore.
My v2_beta_20, 64-bits, can play the 24bit 96kHz FLAC file downloads from here (legal) without problems: https://www.3delite.hu/MP4%20Stream%20Editor/music.html (https://www.3delite.hu/MP4%20Stream%20Editor/music.html)
Title: Re: foobar2000 v2.0 bugs
Post by: Porcus on 2022-12-31 01:06:30
Quote from: demirkoray on
v2.0_beta_16 can play my 24 bit files.
v2.0_beta_20 says: Unsupported stream format: 96000 Hz / 24-bit / 2 channels (0x17700)

All settings are identical. I just update the version, and then I cannot play my 24 bit files anymore.
Are you sure that the output is set not only to the same device, but to the same as far as "Exclusive mode" is selected or not?
Title: Re: foobar2000 v2.0 bugs
Post by: JohnBuckWLD on 2022-12-31 05:56:42
More of an oversight (or perhaps intentional) as opposed to a bug, but with foobar's five standard embedded art options since the reworked properties dialog window (and Tagging > Attach Pictures > shortcut), the new added album art in DUI playlist view feature omits (5) Icon images, and is only enabled for (1) Album / Front cover, (2) (Album) Back cover, (3) Artist picture, and (4) Disc / Media picture.

Given the obsolescence of ESPlaylist (https://hydrogenaud.io/index.php/topic,79030.msg1018870.html#msg1018870), which was the only canned (non-scripted /  WSH panel) playlist that supported Icon artwork, it would be great if support for icon artwork was incorporated into V2
Title: Re: foobar2000 v2.0 bugs
Post by: Mrakobes on 2022-12-31 06:23:49
Maybe I was swearing at 2.0 in vain, I've been suffering for days, once again I did a clean install and first of all I installed the damn foo_jscript_panel3-3.2.0 and the player stopped starting! The process does not want to be deleted by regular methods, I had to kill the process through a third-party program, I apply a crash log
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-12-31 07:50:33
If you remove JScript Panel 3 and fb2k starts normally then the bug is not with fb2k and you're posting in the wrong thread about it.

Title: Re: foobar2000 v2.0 bugs
Post by: Mrakobes on 2022-12-31 13:55:54
Quote from: marc2k3 on
If you remove JScript Panel 3 and fb2k starts normally then the bug is not with fb2k and you're posting in the wrong thread about it.

I just apologized to the developer 2.0 and warned users about the incompatibility of your software with the jscriptpanel, so that they would not think that this is a bug of the player
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2022-12-31 22:04:22
This line in your crash report...

Code: [Select]
JScript Panel 3.2.0 (Thumbs by marc2003): initialised in 21359 ms

is suspect. Taking that long means you're trying to load far too many images or stupidly high resolution ones that are causing a 32bit process to run out of memory. I'll see if I can handle it better but that may be beyond my limited skills. Maybe checking the total file size of all image paths and aborting if it's too much will be the easy way out.
Title: Re: foobar2000 v2.0 bugs
Post by: RonnChyran on 2023-01-03 03:15:02
Going from beta 17 to beta 20 breaks my autoplaylists with the following query: `(%last_played% DURING LAST 1 WEEK) OR (%added% DURING LAST 4 WEEKS) SORT DESCENDING BY %last_played%`. Trying similar searches also fails.
Title: Re: foobar2000 v2.0 bugs
Post by: Air KEN on 2023-01-03 07:43:05
@ RonnChyran

You need Playback Statistics (foo_playcount) .

Playback Statistics (foo_playcount) v3.1.2 (022-12-29)
https://www.foobar2000.org/components/view/foo_playcount

Releases of Playback Statistics
> 3.1 released on: 2022-12-21
> foobar2000 v2.0 support (beta 18 or newer required)
> First run imports existing database from old foobar2000 v2.0 betas.

Foobar2000:Version 2.0 Beta Change Log
https://wiki.hydrogenaud.io/index.php?title=Foobar2000:Version_2.0_Beta_Change_Log#Beta_18
Beta 18
> Removed internal playback statistics, made Playback Statistics component (foo_playcount) operational again. First run of new foo_playcount imports foobar2000 v2.0 beta database back.


Title: Re: foobar2000 v2.0 bugs
Post by: oberon0470 on 2023-01-05 01:06:03
Two things I have noticed in Playback Statistics 3.12.

If I change the title tag in Properties I lose playback info for that file. It shows added date as today's date.

Also if I import an XML written by old foobar2000 v2.0 betas the info is properly imported but I get an error box saying incorrect or corrupted file.
Title: Re: foobar2000 v2.0 bugs
Post by: wolterstorff on 2023-01-05 07:23:02
Quote from: oberon0470 on
If I change the title tag in Properties I lose playback info for that file. It shows added date as today's date.

confirmed, same here (Foobar 2000 beta 20_x86 & PlaybackStatistics 3.1.2)
Title: Re: foobar2000 v2.0 bugs
Post by: wolterstorff on 2023-01-05 07:35:45
[x86] something which was working in beta 17 but not in beta 20 (i skipped beta 18 & 19 because it didn't start); therefore i post this here:

Changes in/with Playlists (creating new ones, deleting old ones, renaming playlists) in Playlist Organizier-Panel (foo_plorg, Version 2.6) only have affect at restart.

Ingo
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2023-01-07 13:51:15
Quote from: ApacheReal on
I point out that in the conversion phase the file name formatting option is not stored and a space is added at the end.
Noted, but can't repro. What exactly do you do to get this?

Quote from: Air KEN on
foobar2000 v2.0 beta 20 32bit (Default UI, Columns UI 2.0.0-alpha.5)
・Clicking (manipulating) ReFacets freezes.
Noted, investigating.
Quote from: demirkoray on
v2.0_beta_16 can play my 24 bit files.
v2.0_beta_20 says: Unsupported stream format: 96000 Hz / 24-bit / 2 channels (0x17700)

All settings are identical. I just update the version, and then I cannot play my 24 bit files anymore.
Thanks for reporting. This is actual valid bug, nonsensical channel mask is being passed around. Fixed for beta 21.

Quote from: JohnBuckWLD on
More of an oversight (or perhaps intentional) as opposed to a bug, but with foobar's five standard embedded art options since the reworked properties dialog window (and Tagging > Attach Pictures > shortcut), the new added album art in DUI playlist view feature omits (5) Icon images, and is only enabled for (1) Album / Front cover, (2) (Album) Back cover, (3) Artist picture, and (4) Disc / Media picture.
Icon column added for beta 21, thanks for pointing out.
Quote from: Mrakobes on
Maybe I was swearing at 2.0 in vain, I've been suffering for days, once again I did a clean install and first of all I installed the damn foo_jscript_panel3-3.2.0 and the player stopped starting! The process does not want to be deleted by regular methods, I had to kill the process through a third-party program, I apply a crash log

Note that 'bad allocation' crashes with huge library and 32-bit foobar2000 often mean running out of 32-bit address space.
Quote from: RonnChyran on
Going from beta 17 to beta 20 breaks my autoplaylists with the following query: `(%last_played% DURING LAST 1 WEEK) OR (%added% DURING LAST 4 WEEKS) SORT DESCENDING BY %last_played%`. Trying similar searches also fails.
Noted. Are you sure that you have foo_playcount (https://www.foobar2000.org/components/view/foo_playcount) installed? It's now required for this functionality.
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2023-01-07 13:58:53
Quote from: MaFred on
Since foobar V2, I very often get the error "Unsupported format or corrupted file" when loading an fpl playlist (saved with V2).
The playlist is then not complete.
This happens with an existing playlist, a new playlist and with an Album list generated playlist. No console error message.
I attach a m3u playlist as an attachment.
If this m3u playlist is loaded, then saved as an fpl playlist, and the fpl playlist is then loaded again, I get the above error message.
fpl playlists from foobar1.6 can be loaded once without any problems.

Thanks for the report. I'd like a sample of actual FPL that fails to load. FPL format also saves cached tags, loading M3U and saving to FPL on my system will not produce same results as on yours as my foobar2000 does not know the tags of references files. I could not create a failing FPL this way.

Quote from: neothe0ne on
I see in the 2.0 change log that,
Quote
First run performs import of old configuration data (playlists, library).

However, I installed 2.0 beta 19 over a copy of my 1.6.15 folder, and after several minutes before foobar2000 2.0 finished loading, I can see my playlists, but my autoplaylists and my library are empty.  My library is setup as the relative path "..\Music\", where my foobar2000 folder is at the same level as my Music folder.  Is this expected behavior?
Certainly not the expected behavior, will check again, probably a problem with importing of ..\ paths.
Quote from: oberon0470 on
Two things I have noticed in Playback Statistics 3.12.

If I change the title tag in Properties I lose playback info for that file. It shows added date as today's date.

Also if I import an XML written by old foobar2000 v2.0 betas the info is properly imported but I get an error box saying incorrect or corrupted file.
I'd like a sample of offending XML that shows error messages, even if it actually imports fine.
Changing tag in Properties - there's a pretty old loophole in foo_playcount logic that results in exactly this in the following scenario:
foo_playcount gets told that file got edited from state B to C, but stats remain pinned to A.
I'm addressing this for the next update.
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2023-01-07 13:59:40
Quote from: ghf_50 on
foobar2000 v2.0 x64 beta 19 on Windows 11
There are two Peak Meter in the toolbar's right click menu.
Wow, accidental Twin Peaks.
Fixed for beta 21, thanks for reporting.
Title: Re: foobar2000 v2.0 bugs
Post by: MaFred on 2023-01-07 15:46:07
Quote from: MaFred on 2022-12-28 10:47:01

    Since foobar V2, I very often get the error "Unsupported format or corrupted file" when loading an fpl playlist (saved with V2).
    The playlist is then not complete.
    This happens with an existing playlist, a new playlist and with an Album list generated playlist. No console error message.
    I attach a m3u playlist as an attachment.
    If this m3u playlist is loaded, then saved as an fpl playlist, and the fpl playlist is then loaded again, I get the above error message.
    fpl playlists from foobar1.6 can be loaded once without any problems.
Quote
Quote from: Peter on 2023-01-07 13:58

Thanks for the report. I'd like a sample of actual FPL that fails to load. FPL format also saves cached tags, loading M3U and saving to FPL on my system will not produce same results as on yours as my foobar2000 does not know the tags of references files. I could not create a failing FPL this way.

Attached is a corrupted fpl playlist
Title: Re: foobar2000 v2.0 bugs
Post by: pawel_na_a on 2023-01-07 19:39:54
small flaw: total time played isn't remembered anymore (beta 20, 21; 1.6.14 works well)
Title: Re: foobar2000 v2.0 bugs
Post by: GoodEnoughGear on 2023-01-08 12:44:14
Cross-posted on the Beta20 thread, but I have some updates and it seems this is the better trafficked thread.

On Beta 20 and 21 VST config is not retained. No changes made in the VST UI is persisted, and there is no audible effect of real-time changes. DMG plugins show signal passing and show effect of changes in the GUI on signal but there are no audible changes. I can drop gain to zero in TrackControl and meters all drop, but there is no effect to the audio being played, gain does not change.

Upon closing and re-opening the VST GUI, it has reverted back to default. I am using the built-in DMG defaults to get around this - whatever is default in the VST does work, just no other changes have any effect.

I have verified the same behavior using Blue Cat Audio's PatchWork product as well, so my correlation with an update applied to the DMG products is by chance. I rolled back my DMG installs to no avail as well.

I have also tried clean install of FB2K 2.0 Beta 21 with the same results.

Thanks!
Title: Re: foobar2000 v2.0 bugs
Post by: amatala on 2023-01-08 13:23:23
I have recently upgraded from beta 16 to beta 20 & 21 32-bit version on Windows 11 and after the upgrade Foobar is just closing without any error. The next time I try to start, it asks to go to safe mode which is working fine, but trying to start Foobar normally again keeps on failing. I couldn't find any error log anywhere with more info, so I just went back to beta 16 again which is running fine. I am not sure if this is a known problem yet, so I guess I'll have to try again in a few versions...
Title: Re: foobar2000 v2.0 bugs
Post by: Air KEN on 2023-01-08 14:57:59
Hi :)

Version 2.0 Beta Change Log - Beta 21:
https://wiki.hydrogenaud.io/index.php?title=Foobar2000:Version_2.0_Beta_Change_Log#Beta_21

> Added 'icon' column in default playlist view.

Lossless file image cannot be embedded with Properties.
High Resolution was fine.

https://i.imgur.com/vzClOyg.png


Thanks.
Title: Re: foobar2000 v2.0 bugs
Post by: bayousam on 2023-01-08 17:32:10
Hi Guys,
I thought you might like to know that Panda AV is preventing installation of V2.0 Beta20 and Beta21 32-bit on my Windows 10 64-bit installation (Suspicious file neutralized, on running installation).
Best regards, Sam
Title: Re: foobar2000 v2.0 bugs
Post by: Fabcore on 2023-01-09 01:20:56
From Beta 20,
"Playlist group layout optimizations reverted (no more scrollbar jumping around stupidly), unless in the new low memory mode."

Now beta 21,
there's still the jumping scrollbar issue when in the playlist has a lot of groups and the behavior is triggered by:
1. Drop audio files from explorer
2. undo some changes
3. ... i think, no more.

Regards.
Title: Re: foobar2000 v2.0 bugs
Post by: NetRanger on 2023-01-09 05:02:29
Quote from: bayousam on
Hi Guys,
I thought you might like to know that Panda AV is preventing installation of V2.0 Beta20 and Beta21 32-bit on my Windows 10 64-bit installation (Suspicious file neutralized, on running installation).
Best regards, Sam

Report that to Panda as a False Positive
Title: Re: foobar2000 v2.0 bugs
Post by: Air KEN on 2023-01-10 15:52:26
Quote from: Air KEN on
Hi :)

Version 2.0 Beta Change Log - Beta 21:
https://wiki.hydrogenaud.io/index.php?title=Foobar2000:Version_2.0_Beta_Change_Log#Beta_21

> Added 'icon' column in default playlist view.

Lossless file image cannot be embedded with Properties.
High Resolution was fine.

https://i.imgur.com/vzClOyg.png


Thanks.
foobar2000 v2.0 beta 22 32bit/64bit

There are File Types that still cannot embed images (*.jpg, *.png, *.ico).
Monkey's Audio, TAK, WavPack ...

https://i.imgur.com/VwJ8gsC.png

Thanks.
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2023-01-11 03:15:42
So it's any format that uses APEv2.

And it would only be a bug if it crashed or failed silently. I get a popup dialog with a very specific message....

(https://i.imgur.com/H0pkk5R.png)





Title: Re: foobar2000 v2.0 bugs
Post by: Air KEN on 2023-01-11 07:05:39
Hi :) marc2k3
thanks for the response.

> So it's any format that uses APEv2.
I think so too

don't crash, Unable to embed image in properties.
"Icon" only.
Title: Re: foobar2000 v2.0 bugs
Post by: RetBaron on 2023-01-11 12:08:50
Automatically fill values in tag editting has different (wrong) logic now. When using commas it fills values before the last comma instead of value before first comma. You can easily try it for yourself in 1.6 and latest 2.0 beta.

Folder name: Dire Straits - 1998 - Best Of, Sultans Of Swing {UK,Rock,Blues} (Vertigo,UK,558 658-2,CD,Comp) [FLAC]
Source: Other / %directoryname%
Used syntax for automatic tag filling: %artist% - %date% - %album% {%artistcountry%,%genre%} (%label%,%releasecountry%,%discnumber%,%releasetype%)
Title: Re: foobar2000 v2.0 bugs
Post by: MirrorMan on 2023-01-11 12:16:11
Greetings from Kyiv!
Сompared the sounds of the beta version 22 [x64] with 21 - my subjective impression is that the new version sounds too clean and emotionless, as if the dynamic range is cut at low frequencies and the sound seems quieter because of this.
Compared on the tracks (flac):
Chromeo - Night by Night
Ketil Bjornstad - Remembrance II.

I have been using the player for almost 17 years - many thanks to the developer for this!
Title: Re: foobar2000 v2.0 bugs
Post by: GoodEnoughGear on 2023-01-12 08:58:49
This issue sorted out now with the update of the VST2/3 package. Thanks!.

Quote from: GoodEnoughGear on
Cross-posted on the Beta20 thread, but I have some updates and it seems this is the better trafficked thread.

On Beta 20 and 21 VST config is not retained. No changes made in the VST UI is persisted, and there is no audible effect of real-time changes. DMG plugins show signal passing and show effect of changes in the GUI on signal but there are no audible changes. I can drop gain to zero in TrackControl and meters all drop, but there is no effect to the audio being played, gain does not change.

Upon closing and re-opening the VST GUI, it has reverted back to default. I am using the built-in DMG defaults to get around this - whatever is default in the VST does work, just no other changes have any effect.

I have verified the same behavior using Blue Cat Audio's PatchWork product as well, so my correlation with an update applied to the DMG products is by chance. I rolled back my DMG installs to no avail as well.

I have also tried clean install of FB2K 2.0 Beta 21 with the same results.

Thanks!
Title: Re: foobar2000 v2.0 bugs
Post by: Cannonaire on 2023-01-12 12:14:20
foobar 2.0 beta 22 x86
*EDIT* I confirmed these bugs are not present with the same DSPs in foobar 2.0 beta 20 x86, nor in 1.16.10.

I'm now noticing popping sounds at the beginning of tracks when I skip to next track. It isn't every time, but it is very frequent. I seem to have narrowed it to two different DSPs. With either of them active, I get popping. I don't know when this issue was introduced.

Loud popping (click sound) basically every manual track change:
foo_dsp_stereoconv
Copyright 2007 Eric Larson
http://people.bu.edu/edlarson/

Quiet popping (bloop sound) randomly on manual track change:
MathAudio Headphone EQ for Foobar2000
(C) 2014-2022  MathAudio.com
https://MathAudio.com

I need both of these DSPs. I don't even know if the stereo convolver is still supported, but I would love to be able to use it on the x64 version since it has a huge impact on my headphone listening - I consider the stereo convolver impulses I use to be the crown jewel of my headphone listening setup for the difference they make.
Title: Re: foobar2000 v2.0 bugs
Post by: AndreaT on 2023-01-12 12:21:36
FB v2 Beta 22 x86 32bit crashes on "freedb tagging"

Hello, I noticed that the new Beta 22 frequently crashes on tagging using freedb option.

Regards,
Andrea
Title: Re: foobar2000 v2.0 bugs
Post by: AndreaT on 2023-01-12 12:36:02
FB v2 Beta 22 x86 32bit has problems also with "MusicBrainz tagging"

Hello, using MusicBrainz option for tagging, the first use works, but from the second and following it reports "Network Error".
I then have to restart Foobar to have it working one-time again.

Regards, Andrea
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2023-01-13 11:27:59
Regarding DSP changes-
For performance reasons, I made DSPs receive a 'flush' event when cycling tracks instead of total reinit.
This should be the same behavior as when seeking. If some DSPs handle this badly, they also handle seeking badly as far as I know.
Please report this as a bug to DSP authors. If the problem persists, I'll investigate reverting to the old behavior.

Regarding freedb / musicbrainz,
No bug here, please autosubmit any crash reports, I have not been able to find any on the tracker.
Title: Re: foobar2000 v2.0 bugs
Post by: MirrorMan on 2023-01-13 17:53:41
Quote from: MirrorMan on
Greetings from Kyiv!
Сompared the sounds of the beta version 22 [x64] with 21 - my subjective impression is that the new version sounds too clean and emotionless, as if the dynamic range is cut at low frequencies and the sound seems quieter because of this.
Compared on the tracks (flac):
Chromeo - Night by Night
Ketil Bjornstad - Remembrance II.

I have been using the player for almost 17 years - many thanks to the developer for this!
Peter, thanks for the beta 23, the low frequency range is beautiful. I compared it with the two previous versions - 23 sounds great!
Title: Re: foobar2000 v2.0 bugs
Post by: sveakul on 2023-01-13 18:41:44
Quote from: Peter on
Regarding DSP changes-
For performance reasons, I made DSPs receive a 'flush' event when cycling tracks instead of total reinit.
Could this have anything to do with the VST plugins behaviour when the DSP chain is changed and new tracks played in v2 64-bit VST adapter .10.1?(https://hydrogenaud.io/index.php/topic,123342.msg1021139.html#msg1021139 (https://hydrogenaud.io/index.php/topic,123342.msg1021139.html#msg1021139))?
Title: Re: foobar2000 v2.0 bugs
Post by: Raznurok on 2023-01-13 20:42:57
Not sure if this has been reported but the seekbar seems to visually refresh (glitch, if you will) if you drag the blue indicator bar along it. It doesn't do this in the stable release. Thanks!
Title: Re: foobar2000 v2.0 bugs
Post by: Cannonaire on 2023-01-13 22:48:56
Quote from: Peter on
Regarding DSP changes-
For performance reasons, I made DSPs receive a 'flush' event when cycling tracks instead of total reinit.
This should be the same behavior as when seeking. If some DSPs handle this badly, they also handle seeking badly as far as I know.
Please report this as a bug to DSP authors. If the problem persists, I'll investigate reverting to the old behavior.
For MathAudio, that's a frequently used plugin and I will try to contact the author when I am able.

However, I don't think the other author still supports the Stereo Convolution plugin. The link in the about section is dead. If the new DSP behavior is here to stay, that means I'm effectively stuck on beta 20 forever since the plugin is essential to me.

Regardless, thank you so much for your hard work. I appreciate and value everything you have done to create and support foobar2000.
Title: Re: foobar2000 v2.0 bugs
Post by: Bogozo on 2023-01-14 12:24:53
Quote from: Cannonaire on
I don't think the other author still supports the Stereo Convolution plugin.
foo_dsp_stereoconv was recently recompiled by Case for fb2k v2 - https://foobar.hyv.fi/2.0/?view=foo_dsp_stereoconv
Title: Re: foobar2000 v2.0 bugs
Post by: Cannonaire on 2023-01-14 13:34:12
Quote from: Bogozo on
Quote from: Cannonaire on
I don't think the other author still supports the Stereo Convolution plugin.
foo_dsp_stereoconv was recently recompiled by Case for fb2k v2 - https://foobar.hyv.fi/2.0/?view=foo_dsp_stereoconv
Whoa! I had no idea! Thank you! :D

It looks like it still has the popping problem with v2.0 beta 23 as expected, but I will contact CASE when I am able to see if they can solve the issue.
Additional information: Seeking shows no signs of popping with it in beta 20.
Title: Re: foobar2000 v2.0 bugs
Post by: sveakul on 2023-01-14 20:46:00
@Peter: will v2 32 & 64 bit also be receiving the option to not apply the new DSP flushing action when changing tracks, as you have now done for 1.6.16 (and thank you for that!)?
Title: Re: foobar2000 v2.0 bugs
Post by: redrose on 2023-01-15 13:47:08
Quote from: Raznurok on
Not sure if this has been reported but the seekbar seems to visually refresh (glitch, if you will) if you drag the blue indicator bar along it. It doesn't do this in the stable release. Thanks!
Yes, I can confirm, this happens here too.
Beta 23, Windows 10, AMD cpu and dgpu.
Title: Re: foobar2000 v2.0 bugs
Post by: Air KEN on 2023-01-15 14:10:22
foobar2000 v2 beta23
Ubuntu 22.04.1

Last modified (edited) and Created are equal.
Media Library is broken.
Title: Re: foobar2000 v2.0 bugs
Post by: ASopH on 2023-01-15 15:53:52
Hi,
fb2k v2.0 beta 23 64bit Win 10

no full start of foobar - no music where be shown, fb2k not fully loaded - no error.log

media library is broken (content.sqlite is greater 50MB) from external drive
after deleting this file foobar starts normally.
After re-reading and external drive is off:
no full start of foobar - no music where be shown, fb2k not fully loaded - no error.log
Title: Re: foobar2000 v2.0 bugs
Post by: Raznurok on 2023-01-17 10:55:02
Has anyone else noticed an issue with seek speed in 2.0? Not seen this happen in the stable version but beta 23 (at least) sometimes has a noticeable pause whilst seeking. A restart sometimes fixes this but not always. Not sure what triggers this as it'll sometimes go away on its own, and it happens with both local files and files on a network drive.
Title: Re: foobar2000 v2.0 bugs
Post by: beat8000 on 2023-01-17 16:43:49
Hi, I'm receiving an error message after the clean installation of v2.0 beta 23 64bit Win 10 because the file shared.dll could not be found during the start of foobar.
With Beta 17 and less it is working. I have recognized that this version uses the timestamp 09.12.2022 14:13 for shared.dll and 09.12.2022 14:14 for foobar2000.exe which means that the file shared.dll is older.

With Beta 23 both files are using the timestamp 13.01.23 12:36

Title: Re: foobar2000 v2.0 bugs
Post by: Fabcore on 2023-01-18 01:00:51
1. playlist: groups; Abrupt jumps by changing something that affects the said group's text.
2. On low memory mode editing tags doesn't do at first, must has try again to actually applies its tags.

Regards
Title: Re: foobar2000 v2.0 bugs
Post by: Fabcore on 2023-01-18 17:14:10
Beta 24 and still have this annoyance.
whenever i change the text on the groups, the playlist jumps to whatever position losing completely the tracking where i was.

edit reason: typo on beta number.
Title: Re: foobar2000 v2.0 bugs
Post by: beat8000 on 2023-01-18 17:37:16
Quote from: beat8000 on

With Beta 17 and less it is working. I have recognized that this version uses the timestamp 09.12.2022 14:13 for shared.dll and 09.12.2022 14:14 for foobar2000.exe which means that the file shared.dll is older.


I have just changed the timestamp of the file shared.dll after the Beta 24-x64 installation to 18.01.23 15:25 but I'm still receiving the same system error "... shared.dll missing..." in German.
I assume that there is another error because the file obviously is existing.
Title: Re: foobar2000 v2.0 bugs
Post by: beat8000 on 2023-01-22 17:19:21
Quote from: beat8000 on
Quote from: beat8000 on

With Beta 17 and less it is working. I have recognized that this version uses the timestamp 09.12.2022 14:13 for shared.dll and 09.12.2022 14:14 for foobar2000.exe which means that the file shared.dll is older.


I have just changed the timestamp of the file shared.dll after the Beta 24-x64 installation to 18.01.23 15:25 but I'm still receiving the same system error "... shared.dll missing..." in German.
I assume that there is another error because the file obviously is existing.
I have just found a workaround for this system error.
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.
Title: Re: foobar2000 v2.0 bugs
Post by: Takaji on 2023-01-28 20:21:56
Crossposting this possible bug report to this thread, as this may have been the better place to put it:

Quote from: Takaji on
I'm not exactly sure when this behaviour started (possibly when I switched to foobar2000 v2.0?), but I've noticed that if I modify the %album% tag of an album, then %added% also changes to the date that I modified the tags - I assume because the database sees this as a new entry. Is there a way to disable/fix this?

I thought maybe the playback statistics database would've relied on another way of identifying a track/album instead of by the tags - perhaps by a hash or something like this?

I noticed a typo in an album title, and now %added% shows that the album was added to my library today, instead of back in 2018. I have an autoplaylist which organises my music by %added%, and this then gets messed up.

Quote from: Takaji on
I can confirm that this is happening with 2.0 beta 24 and foo_playcount 3.1.3.

Steps to reproduce:
1. Change the title of an album (%album%) in the media library (in this case I added "(Test)" to the end of the album name)
2. Playback Statistics field will show an Added date that reflects when you changed the album name.

Changing the album name back to its original value restores the correct playback statistics.
Title: Re: foobar2000 v2.0 bugs
Post by: burgundio on 2023-01-29 09:30:21
I am not an expert user but apparently updating foobar to 2.0 I lost the ability to play.iso dsd files that i could previously play and convert - despite my trying I cannot get the grayed out components to play again. Any help?
Thanks
Burgundio
Title: Re: foobar2000 v2.0 bugs
Post by: Gus. on 2023-01-29 15:59:23
Quote from: burgundio on
I am not an expert user but apparently updating foobar to 2.0 I lost the ability to play.iso dsd files that i could previously play and convert - despite my trying I cannot get the grayed out components to play again. Any help?
Thanks
Burgundio
Are you using components from here: https://sourceforge.net/projects/sacddecoder/
Title: Re: foobar2000 v2.0 bugs
Post by: Porcus on 2023-01-31 10:30:33
At the end of a big move job, fb2k (edit: x64 beta 24) will for hours and hours stay "unresponsive" but not completely:

* In the alt-tab cycle the main window shows up, but I cannot select it.
* I mouseover the icon in the taskbar it shows that there is a (edit:) File Operations Setup window that I cannot access.
* CPU usage stays at 12 to 15 percent; I have 8 threads, so I can only guess that it occupies one thread doing its thing and then a little bit on something else

But after fighting the task bar a little bit, I get
* this blank "window"-alike thing (to the left in the picture)
* and then to play music! And skip tracks and ... (to the right)

(https://i.imgur.com/tvLPJxg.png)

Title: Re: foobar2000 v2.0 bugs
Post by: Pinstripe on 2023-01-31 14:04:38
Hi, I want to report a bug (x64 Beta 24):

The option "Save playback state when closing foobar2000 and resume on next startup" doesn't work. Whenever I play a track, close foobar, reopen it, the track starts from the beginning again.
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2023-01-31 14:23:29
No issues here??

(https://i.imgur.com/KxdkJBb.gif)

Using the same version/x64.
Title: Re: foobar2000 v2.0 bugs
Post by: Pinstripe on 2023-01-31 14:37:19
I just noticed it *does* work if I launch foobar2000.exe, rather than the mp3 file directly. I thought the latter should work, too. My mistake I guess.
Title: Re: foobar2000 v2.0 bugs
Post by: Porcus on 2023-02-01 10:43:37
Bug with TAK files: MD5 are not detected or shown.

x64 beta 24.
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2023-02-01 11:01:23
I'd assume foo_input_tak would support that. Case updated it for fb2k 2.0.

https://foobar.hyv.fi/2.0/?view=foo_input_tak


Title: Re: foobar2000 v2.0 bugs
Post by: Porcus on 2023-02-04 12:51:31
Another MD5 issue, with WavPack calculating it in the same endianness as the source file. It seems that foobar2000 - like FLAC - calculates it little-endian, and so fails to verify these WavPack files.
The problem has been around ever since WavPack got CAF support, but the combination foobar2000, CAF, WavPack and MD5 is scarce. Now with WavPack supporting AIFF, it could happen more often - indeed this is an issue I discovered upon verifying some of my encodes - some artist gave me something that was in AIFF - not thinking it up first and trying to provoke it (although I should have!).

foobar2000 does handle how FLAC and WavPack differ in MD5 for unsigned signals (that is, 8-bit WAVE), so I guess it is intended to verify the files that are indeed OK.


As for TAK: foo_input_tak makes MD5 show, after reloading tags - and I can then remove the component as long as I don't reload tags from files once again.
Title: Re: foobar2000 v2.0 bugs
Post by: funkyblue on 2023-02-05 10:15:56
Hello
I searched and searched and finally found a thread for Foobar2000 2.0 beta. I forgot to backup and then updated from the 1.6.1 stable version to 2.0 beta 24.
I've lost my last played and play count numbers. Are there issues with Foobar2000 v2 beta 24?
Can anyone help?
Kind Regards
funkyblue and a member since 2001.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-02-05 12:49:44
Maybe update foo_playcount (https://www.foobar2000.org/components/view/foo_playcount)
Title: Re: foobar2000 v2.0 bugs
Post by: iridescentaudio on 2023-02-06 14:56:20
I'm using 2.0 beta 17 and probably ought to update, but this once again has implications for playback statistics. Should I reinstall the Playback Statistics component before updating to a new beta, or after? I want to make sure this goes as smoothly as possible, noting some issues people have experienced.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-02-06 15:17:12
I've installed newest version of foo_playcount after 2.0 beta 24. Without foo_playcount the rating and playcount columns in playlist view showed errors. The Playback Statistics database remains intact.
Title: Re: foobar2000 v2.0 bugs
Post by: regor on 2023-02-06 15:46:51
Quote from: grimes on
I've installed newest version of foo_playcount after 2.0 beta 24. Without foo_playcount the rating and playcount columns in playlist view showed errors. The Playback Statistics database remains intact.
That seems right. Statistics was removed on beta 18 (?). So anything after that should not retrieve rating or playcount, unless you have the plugin. Correct me if i'm wrong.
https://wiki.hydrogenaud.io/index.php?title=Foobar2000:Version_2.0_Beta_Change_Log#Beta_24

Although I think the plugin should be simply integrated into foobar at this point, with the current behavior (not the one linked to paths). It would put an end to all these problems with ratings, statistics disappearing, mixed versions, tag remaps, etc. And the same for the $meta(), %RATING% inconsistencies... lets simply add a new tag remap called %RATING_FILE% which points to "ratin" tags on files, if it exists, and done. Or just a single setting to either use database or read from files. And all tags pointing to that. Much cleaner.

In any case at least it should be installed by default (and opt-out setting).
Title: Re: foobar2000 v2.0 bugs
Post by: funkyblue on 2023-02-07 01:20:42
Quote from: grimes on
Maybe update foo_playcount (https://www.foobar2000.org/components/view/foo_playcount)

Thanks. That was it :)

My other question, is I've installed a heap of plugins over the years and not really used them. Is there a simply way to clean my directory and remove anything unused?

Quote from: regor on
Quote from: grimes on
I've installed newest version of foo_playcount after 2.0 beta 24. Without foo_playcount the rating and playcount columns in playlist view showed errors. The Playback Statistics database remains intact.
That seems right. Statistics was removed on beta 18 (?). So anything after that should not retrieve rating or playcount, unless you have the plugin. Correct me if i'm wrong.
https://wiki.hydrogenaud.io/index.php?title=Foobar2000:Version_2.0_Beta_Change_Log#Beta_24

Although I think the plugin should be simply integrated into foobar at this point, with the current behavior (not the one linked to paths). It would put an end to all these problems with ratings, statistics disappearing, mixed versions, tag remaps, etc. And the same for the $meta(), %RATING% inconsistencies... lets simply add a new tag remap called %RATING_FILE% which points to "ratin" tags on files, if it exists, and done. Or just a single setting to either use database or read from files. And all tags pointing to that. Much cleaner.

In any case at least it should be installed by default (and opt-out setting).

I'd have to agree. It should be in the default installation. I do not use much apart from the default plugins.
Title: Re: foobar2000 v2.0 bugs
Post by: sveakul on 2023-02-07 05:23:33
Quote from: funkyblue on
My other question, is I've installed a heap of plugins over the years and not really used them. Is there a simply way to clean my directory and remove anything unused?
In the Installed Components window, right-click the ones you don't use and choose "remove."  Then, in the Profile folder, open the Configuration subfolder and delete any existing .cfg files that correspond to the removed plugins.
Title: Re: foobar2000 v2.0 bugs
Post by: Bogozo on 2023-02-12 13:56:31
Built-in DTS decoder doesn't report lossless profile of DTSHDMA nor its bitdepth if it is in *.dts container and thus, when using conversion to other lossless, bitdepth is truncated to 16 bits (unless manually set to 24 bits) even if source DTSHDMA is 24 bit.
Title: Re: foobar2000 v2.0 bugs
Post by: varezhka on 2023-02-12 20:35:22
For some reason, FPS drops noticeably in games if you run Foobar version 2.0 beta 24 at the same time as the game. With version 1.16.16 and earlier there are no such problems.
Title: Re: foobar2000 v2.0 bugs
Post by: funkyblue on 2023-02-13 00:16:27
Quote from: sveakul on
Quote from: funkyblue on
My other question, is I've installed a heap of plugins over the years and not really used them. Is there a simply way to clean my directory and remove anything unused?
In the Installed Components window, right-click the ones you don't use and choose "remove."  Then, in the Profile folder, open the Configuration subfolder and delete any existing .cfg files that correspond to the removed plugins.

There are lots in folders in the plugin directory that aren't used and aren't listed. Do I just delete?
Title: Re: foobar2000 v2.0 bugs
Post by: sveakul on 2023-02-13 05:07:47
Quote from: funkyblue on
There are lots in folders in the plugin directory that aren't used and aren't listed. Do I just delete?
You mean the "user-components" directory, right?  If the component folder name is not listed in Preference/Installed Components, I assume that means it is not compatible with v2.0 beta 24 since your upgrade from "1.6.1."  To be on the safe side, why not just move those to some temp folder outside of Foobar and see if Foobar continues to work the way you expect.  If so, you could go ahead and delete them.
Title: Re: foobar2000 v2.0 bugs
Post by: Execucucu on 2023-02-13 07:34:37
The behavior was painful when using nothing but "Refacets + PlaylistView".

Assuming I already selected and was already playing some track, which shows in the PlaylistView.

Correct behavior (when using the old Facets + PlaylistView):

Whenever my current selection in Facets panel changed (by clicking another item in the Facets list, or by searching)...
1. It will switch the PlaylistView to the list with my selection (or search) results. PlaylistView reflects the change, by automatically switch to the playlist called "Library selection".
2. The current playling list will move to the playlist "Library selection (playing)". So I can go back to it anytime.
3. When double clicking an item in Facets, it sends all corresponding tracks to the playlist, and play from the first track.

Problematic behavior (when using Refacets + PlaylistView):

1. When using the Refacet search box. It won't automatically send the search results to the playlist called "Library selection", and activate it. (Selecting an item in the Refacets list works properly, though.)
2. Refacets will never move my current playing list to the playlist "Library selection (playing)". So I can't go back to it by double clicking the status bar. Even worse, the current playing track won't repeat, even if I set the playback order to "Repeat (track)", since it's not in the playlist anymore.
3. When double clicking an item in Facets, it sends all corresponding tracks to the playlist, and... selects all of them??

Suggestions on how to fix Refacets:
1. You basically need to recreate the "Selection action: Send to selection playlist, keep playing playlist" feature in the old Facets. And the "Play" feature right next to it as well. Currently there's only a "Send to selection playlist" option which really couldn't get the job done.
2. Also make sure searching in the searchbox also performs the selection action.

(What version am I using: Was using beta 12, recently updated to beta 24, problem remains the same. I should have reported it back then.)
Title: Re: foobar2000 v2.0 bugs
Post by: valiant8086 on 2023-02-14 01:41:49
beta24, 32bit portable.

Since at least Beta17, if I double click or press enter on files in explorer there is a 1.5 second or so lag before Foobar starts playing it. I have it configured not to bring to front, and I usually run Foobar closed out to the tray. Since I'm in the habit of playing many short sounds in sound libraries, this lag every time I do so is pretty huge. Definitely didn't experience this with 1.6.x. I think the only difference is this is installed portable and I used the open with and set it to always open the file type in Foobar with this portable version.

I notice that the current playing sound doesn't stop playing immediately either. It's as though Foobar doesn't start to do anything for at least 1.5 seconds.

If I use the play command while a file was already loaded, it is instantaneous.

I did not upgrade from 1.6, this was a fresh upgrade as of version 2.0beta6 or so iirc.
Title: Re: foobar2000 v2.0 bugs
Post by: PeterMac on 2023-02-15 15:48:14
Maybe someone know how to fix "SimPlaylist" to be also in dark mod ?.
If not possible, does default "Playlist View" can display track time like on screenshot ?

Thank you.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-02-15 16:23:40
"Playlist view" doesn't accept context-specific fields like %playback_time%.
Title: Re: foobar2000 v2.0 bugs
Post by: PeterMac on 2023-02-15 18:02:23
Right, not work with Playlist View :( 
SimPlaylist is old component and not work in dark mode to match nice :'(
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-02-15 18:33:03
I've %playback_time%[ / -%playback_time_remaining% / %length%] in statusbar.
Title: Re: foobar2000 v2.0 bugs
Post by: PeterMac on 2023-02-15 22:25:51
not work
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2023-02-15 22:54:59
Your screenshot a few posts up is already showing the playback time / length in the status bar.  :o
Title: Re: foobar2000 v2.0 bugs
Post by: PeterMac on 2023-02-15 23:03:27
but I want this also in playlist
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2023-02-15 23:13:32
It had already been established in your conversation with grimes that it was not possible. Then he posted...

Quote
I've %playback_time%[ / -%playback_time_remaining% / %length%] in statusbar.

If you post "not work" in response to that, how do you think it makes you look?
Title: Re: foobar2000 v2.0 bugs
Post by: PeterMac on 2023-02-16 11:51:07
It was not establishedi in conversation at all, because grimes paste some code for statusbar and not clear say where to use it, and I thought to use it for playlist, and I answered not work.
If we have foobar2000 v2, would be nice to improve add this to default playlist, also add color text highlight for playing element on playlist. Thank you.
Title: Re: foobar2000 v2.0 bugs
Post by: anamorphic on 2023-02-16 12:52:44
I second request for %playback_time% (etc) - strange to not have it when every other playlist does. Maybe two decades ago it made sense to only have status bar updates, but nowadays...? (I know however this is the bug reporting thread, not the wishlist (https://hydrogenaud.io/index.php/topic,116509.msg1022483.html#new) thread!)

"Highlighting" has always been there - see wiki (https://wiki.hydrogenaud.io/index.php?title=Foobar2000:Preferences:Default_User_Interface:Playlist_View#Dimming_and_Highlighting_Text) or here (https://hydrogenaud.io/index.php/topic,123610.msg1021792.html#msg1021792) for an example.
Title: Re: foobar2000 v2.0 bugs
Post by: always.beta on 2023-02-17 05:50:37
fb2k beta24+foo_playcount v3.1.3, the song rating is 4, after modifying the album date, the song rating disappeared.
Title: Re: foobar2000 v2.0 bugs
Post by: MordredKLB on 2023-02-17 06:37:17
Quote from: always.beta on
fb2k beta24+foo_playcount v3.1.3, the song rating is 4, after modifying the album date, the song rating disappeared.
Ratings and all playcount data is lost if you use any program other than the currently running fb2k instance to change: Date, Title, Artist, or Album Name.

However if inside foobar you change say the Date back to what it was before you changed it externally, the ratings and playcounts will return to what they were (so long as you do this within 4 weeks of the last time foobar saw the file). Then you can change the Date back to what it should and the ratings and playcounts will not be lost.

Nevermind, just repro'd this by changing the date from inside foobar too. Oddly it does stick after the first edit, so you can change date from:
2022 -> 2021 playcounts lost
2021 -> 2022 playcounts return
2022 -> 2021 playcounts stick

Only seems to effect foo_playcount's metadb hash though as foo_enhanced_playcount data isn't lost. Definitely appears to be a bug in that component as opposed to foobar itself.
Title: Re: foobar2000 v2.0 bugs
Post by: always.beta on 2023-02-17 08:04:40
Quote from: MordredKLB on
Nevermind, just repro'd this by changing the date from inside foobar too.
I modified the album date with fb2k's own attribute function.
Title: Re: foobar2000 v2.0 bugs
Post by: Squeller on 2023-02-17 08:05:20
Is that a bug or drastic misunderstanding on my side?

In ReFacets, I have a column with simply:
Code: [Select]
if2(%work%,%album%)
But there will be no entries listed which don't have %work%, but have %album%. Those (album names) are still in the "Missing tag" listing, as if I just used "%work%"

Latest beta.
Title: Re: foobar2000 v2.0 bugs
Post by: regor on 2023-02-17 10:51:23
The preferences window does not support ctrl + backspace to delete the current text, although such behavior is present on the rest of panels, windows, popups, etc. On CUI and DUI. Applies to foobar V1 too.

See here:
https://github.com/reupen/columns_ui/issues/572
Title: Re: foobar2000 v2.0 bugs
Post by: always.beta on 2023-02-18 03:34:16
beta24，In the dark theme mode, 1, the toolbar font is not uniform; 2, when the tabs are crowded, the tab switching is white.
Title: Re: foobar2000 v2.0 bugs
Post by: always.beta on 2023-02-18 03:44:57
Bug: An animation demonstration of level data loss after editing music tags inside fb2k.
https://imgur.com/a/bRqmBIh
(https://imgur.com/a/bRqmBIh)
Title: Re: foobar2000 v2.0 bugs
Post by: Porcus on 2023-02-19 09:58:50
To follow up on the below, it seems that for lossless sources including uncompressed, the verifier component calculates and displays audio MD5s - but apparently only 16 bit and 24 bit, not 8 nor 32 (nor float32/float64).
Quote from: Porcus on
Another MD5 issue, with WavPack calculating it in the same endianness as the source file. It seems that foobar2000 - like FLAC - calculates it little-endian, and so fails to verify these WavPack files.

Also a wishlist item on the verifier output: yes I can sort by columns (I would have wanted filename with extension) and select, but:
Once there is an option to add to playback queue, surely it should be feasible to send to new playlist?
Title: Re: foobar2000 v2.0 bugs
Post by: ApacheReal on 2023-02-20 16:48:51
I have a 192000Hz/24bit 1.7gb flac file.
With foobar vers. 1.5.8 runs fine, with vers. 2.0 beta 24 tells me that the file is corrupt or unsupported format. reference libFLAC 1.2.1 20070917.

I don't know if some flac library needs to be updated.
Title: Re: foobar2000 v2.0 bugs
Post by: Porcus on 2023-02-20 16:53:56
@ApacheReal : The FLAC library has been updated to one that detects much more errors. There have been a lot of such threads here, the most recent being this: https://hydrogenaud.io/index.php/topic,123715.0.html

What does the verification say? In v2 it is built-in, the old needs this component: https://www.foobar2000.org/components/view/foo_verifier
Are do they report same MD5s?


I wonder if Peter could save himself many quite a lot of questions by including an older FLAC version and whenever a .flac throws an error, run it through the old version to see if the errors are the same, and report an explanation if not.
Title: Re: foobar2000 v2.0 bugs
Post by: ApacheReal on 2023-02-20 18:15:42
What I can say that the flac file is not corrupted.

I converted the flac file to wav 24/192 with foobar2000 vers. 1.5.8

Put the wav files in foobar2000 v2.0 beta24 and verified that they were read I proceeded to convert them back to flac 24/192

I don't know more.

I reported the problem, because I think there is something wrong.
Title: Re: foobar2000 v2.0 bugs
Post by: Porcus on 2023-02-20 20:50:04
Which file did come out corrupted? The one before conversion to WAVE or the one after?

Most of these files that now give errors or warnings, have had ID3 tags written to them by EAC, but this is a high resolution.

Edit: Just because conversion with 1.5.8 does not lead to any objections, it doesn't mean the file is OK - because 1.5.8 uses a FLAC version that does less checks. If you look at https://hydrogenaud.io/index.php/topic,123219.msg1017891.html#msg1017891 you will see a file that was supposed to be 16 bits, but when you decode it, it turns out one channel needs 18 bits and the other needs even more.
Title: Re: foobar2000 v2.0 bugs
Post by: demirkoray on 2023-02-23 10:09:24
foobar2000 v2.0 beta24: In Playlist Organizer, right click on a folder, using the popped up context menu, create a new playlist --> Bug. Here is a video of it: https://www.dropbox.com/s/z7gjs08iqo70p4c/Video.mp4?dl=0
Title: Re: foobar2000 v2.0 bugs
Post by: regor on 2023-02-23 10:27:15
XD I love the infinite amount of reports with Playlist Organizer these days, even when people warned this would happen and the component has been reported to be broken since years.

But there it is, at the components list, without a warning. Keep sending reports please, it's really funny. Wonder when we will change the current components model, instead of talking about the philosophy of software.

Quote from: demirkoray on
foobar2000 v2.0 beta24: In Playlist Organizer, right click on a folder, using the popped up context menu, create a new playlist --> Bug. Here is a video of it: https://www.dropbox.com/s/z7gjs08iqo70p4c/Video.mp4?dl=0

Just to be clear in case 3 reports (https://hydrogenaud.io/index.php/topic,80705.msg1020868.html#msg1020868) in a year about the component being broken since 2015 is not clear enough. (it's also broken on V1)
IT WILL NOT BE UPDATED; PEOPLE PLEASE STOP USING IT AND REPORTING BUGS.
Title: Re: foobar2000 v2.0 bugs
Post by: pulbitz on 2023-02-24 09:17:13
I'm still having the same problem with beta 25.

metadb, library, playlists.
https://www.mediafire.com/file/bjib5yl93i0fxp9/beta25-playlist-db.7z/file

Code: [Select]
Components loaded in: 0:00.006179
Configuration read in: 0:00.000461
foobar2000 v2.0 beta 25 x64 [standard]
Playlist #0 loaded in 0:00.118938
User Interface initialized in: 0:00.255285
Loading foo_discogger
foo_discogger: http_client service ready
FFmpeg version: 5.1
Startup time : 0:00.306408
Watching: D:\Music
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
Library initialized after 0:00.744459
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked

Quote from: pulbitz on
When I open the console window, I often get a "database is locked" error. It occurs when foobar2000 is loaded. And while I can't be specific, it often happens when I try to play a particular file.
There seems to be a delay in the operation of foobar2000 when this DB error occurs.

Code: [Select]
Components loaded in: 0:00.011037
Configuration read in: 0:00.001171
foobar2000 v2.0 beta 11+log x64 [standard]
Playlist #0 loaded in 0:00.159534
User Interface initialized in: 0:00.386367
FFmpeg version: 5.1
Loading foo_discogger
foo_discogger: http_client service ready
Startup time : 0:00.478256
Watching: D:\Music
Library initialized after 0:02.441319
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid, playCount, dateAdded, lastPlayed, firstPlayed, rating FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid, playCount, dateAdded, lastPlayed, firstPlayed, rating FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid, playCount, dateAdded, lastPlayed, firstPlayed, rating FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid, playCount, dateAdded, lastPlayed, firstPlayed, rating FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid, playCount, dateAdded, lastPlayed, firstPlayed, rating FROM metadb WHERE name = ?
database is locked
Title: Re: foobar2000 v2.0 bugs
Post by: djanssen on 2023-02-24 19:05:49
Quote from: Chibisteven on
The bugs I found so far appear to be GUI related.

  • Double clicking on a visualization doesn't go to full screen mode.
  • Double clicking with a full screen visualization doesn't exit full screen mode.
  • Exiting full screen mode with a visualization causes it to reshape to the size of the screen and not remember the size and position of where it was last at.
  • Before the open file box pops up (shortcut CTRL + O) any highlighted items in the playlist disappear completely for a brief second before reappearing.

Would Autoplaylist fit here? Also, compatibility with the remote tool?
Title: Re: foobar2000 v2.0 bugs
Post by: Elric on 2023-02-25 10:15:30
Hi,
have a Problem with Beta 25-x64 / Win10 Pro.
When I edit Tags via Properties-Dialog (FLAC FIles) and then save it, Foobar gets unresponsive with 1 Core runs at 100%.
Must kill it with the Taskmanager.
Tags are written.
Title: Re: foobar2000 v2.0 bugs
Post by: Elric on 2023-02-26 12:19:40
Yesterday I haven't time to present more Information.

If I edit the Tags on Files which are in my Media Library Path, after saving them, the Properties Dialog don't close and Foobar gets unresponsive.

1 Core gets up to 100%.
Here is a Stacktrace.

Code: [Select]
ntdll.dll!NtdllDialogWndProc_W+0x100
ntdll.dll!NtClose+0x14
KERNELBASE.dll!CloseHandle+0x45
windows.storage.dll!Ordinal815+0x1319c
windows.storage.dll!SHGetKnownFolderIDList_Internal+0x3887
windows.storage.dll!SHGetKnownFolderIDList_Internal+0x2944
windows.storage.dll!SHGetKnownFolderIDList_Internal+0x282d
windows.storage.dll!SHGetFolderPathEx+0xc3c
windows.storage.dll!SHGetKnownFolderIDList_Internal+0x3043
windows.storage.dll!SHGetKnownFolderIDList_Internal+0x723
windows.storage.dll!SHGetKnownFolderIDList_Internal+0x157
windows.storage.dll!SHGetKnownFolderIDList_Internal+0x6e
windows.storage.dll!SHGetKnownFolderItem+0x2d
windows.storage.dll!IsLibraryCreatedByPolicy+0x2532
shared.dll!uEvalKnownFolder+0x60
foobar2000.exe+0x172b2d
foobar2000.exe+0xa34ae
foobar2000.exe+0xa3711
foobar2000.exe+0x28c8c4
foobar2000.exe+0x161391
foobar2000.exe+0x1e3a79
foobar2000.exe+0x24367c
foobar2000.exe+0x67004
foobar2000.exe+0x242f9b
foobar2000.exe+0x243af7
ucrtbase.dll!configthreadlocale+0x92
KERNEL32.DLL!BaseThreadInitThunk+0x14
ntdll.dll!RtlUserThreadStart+0x21
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2023-02-27 12:20:06
Quote from: Elric on
Hi,
have a Problem with Beta 25-x64 / Win10 Pro.
When I edit Tags via Properties-Dialog (FLAC FIles) and then save it, Foobar gets unresponsive with 1 Core runs at 100%.
Must kill it with the Taskmanager.
Tags are written.
Problem fixed for the next update, thanks for reporting.
Title: Re: foobar2000 v2.0 bugs
Post by: kamild1996 on 2023-02-27 19:45:52
A minor bug, but it seems like the "Visualisation update interval" setting no longer works when the visualiser is put on fullscreen mode. Unfortunately, I'm unable to tell which beta update may have caused the change.
Title: Re: foobar2000 v2.0 bugs
Post by: hubo on 2023-02-27 21:42:32
Visualization is offset (probably 2px to the left).
Title: Re: foobar2000 v2.0 bugs
Post by: GeoffW on 2023-02-28 14:30:50
Cue file (multiple tracks onto single FLAC) hangs for ages before playing. Running over a network from a USB2 drive so it's not the fastest but it worked better on the previous version (although that had its own issues in that it paused between tracks - even when playing from the same FLAC - which was why I tried the beta...)

Status bar just shows "Starting playback...", and nothing on the console other than

Opening track for playback: "\\netpath\\Music\StayTheFunkAtHome5.cue" / index: 1

Playing the FLAC file on its own doesn't have nearly as bad a startup time (2 minutes vs <5s). Is FB2k trying to scan every file in the cue before it starts, and doing it multiple times on the same file?

Edit: same pause if I make the mistake of jumping to another track in the cue (so still within the same flac), so it's not just that it's pre-caching some data.

Edit 2: oh, it does it between tracks too.
Title: Re: foobar2000 v2.0 bugs
Post by: kor5n on 2023-03-01 08:06:03
Hi. I've a bug with foobar2000 beta 26-x86 on Win11 Pro.
When the UAC window opens asking for administrator rights, the player crashes if the main window is not minimized (if it is minimized, crashes happen every other time).
I will attach the last four dumps.
Code: [Select]
Illegal operation:
Code: C0000005h, flags: 00000000h, address: 5E25256Ah
Access violation, operation: read, address: 00000000h

Call path:
app_mainloop

Code bytes (5E25256Ah):
5E25252Ah:  CC CC CC CC CC CC 55 8B EC 83 E4 F8 56 8B F1 57
5E25253Ah:  8B 86 D0 01 00 00 8B 78 14 8B 46 64 8B 80 50 01
5E25254Ah:  00 00 F6 40 5B 01 74 27 8B 46 0C C6 86 D5 01 00
5E25255Ah:  00 01 57 8B 80 50 01 00 00 80 48 18 02 8B 4E 0C
5E25256Ah:  FF 37 8B 89 50 01 00 00 E8 D9 96 EE FF EB 07 C6
5E25257Ah:  86 D5 01 00 00 00 8B 07 39 B8 DC 11 00 00 74 06
5E25258Ah:  89 B8 DC 11 00 00 8B 8E D0 01 00 00 FF 75 08 8B
5E25259Ah:  49 0C E8 9F A8 10 00 5F 5E 8B E5 5D C2 04 00 CC

Stack (00AFEC2Ch):
00AFEC0Ch:  087E3AE0 10000000 00000000 03E36FB0
00AFEC1Ch:  03C1F970 15A3B820 80000000 00000000
00AFEC2Ch:  00000000 00000032 00AFEF18 00AFEC58
00AFEC3Ch:  00AFEC54 5E245431 00000200 15988900
00AFEC4Ch:  15D49000 01216758 00AFF0D8 5E302BDC
00AFEC5Ch:  00000200 00000000 00000000 000001AB
00AFEC6Ch:  00000090 00000000 00000000 000001AB
00AFEC7Ch:  00000090 01215350 5E301EE0 006C6C64
00AFEC8Ch:  65747379 5C32336D 00000144 159886A0
00AFEC9Ch:  05651710 0551F880 6F706552 03E36FB0
00AFECACh:  15988900 0563C5E8 00AFF250 00006E69
00AFECBCh:  00000000 00000000 34653766 66343865
00AFECCCh:  38353032 6E5C6331 75646C76 00000000
00AFECDCh:  15D49000 00000010 00000000 00000000
00AFECECh:  00000000 00000000 00000000 00000000
00AFECFCh:  00000090 000001AB 00000000 00000090
00AFED0Ch:  00000000 03D2FF00 00000000 056D0A70
00AFED1Ch:  00000000 00000000 00000000 00000000
00AFED2Ch:  00000000 00000000 00000000 000001AB
00AFED3Ch:  00000090 00000000 00000000 000001AB

Registers:
EAX: 0866DB60, EBX: 0563C5E8, ECX: 03C1F420, EDX: 5F608640
ESI: 0563C5E8, EDI: 00000000, EBP: 00AFEC3C, ESP: 00AFEC2C

Crash location:
Module: nvd3dum
Offset: 108256Ah

Loaded modules:
foobar2000                       loaded at 00CB0000h - 01001000h
ntdll                            loaded at 77BF0000h - 77D9F000h
KERNEL32                         loaded at 76900000h - 769F0000h
KERNELBASE                       loaded at 76150000h - 763BA000h
SHLWAPI                          loaded at 76CE0000h - 76D2B000h
msvcrt                           loaded at 76E40000h - 76F04000h
COMCTL32                         loaded at 6F480000h - 6F6A4000h
WINMM                            loaded at 758E0000h - 75911000h
GDI32                            loaded at 772D0000h - 772F2000h
USER32                           loaded at 773E0000h - 77587000h
ucrtbase                         loaded at 76A70000h - 76B82000h
UxTheme                          loaded at 746C0000h - 7473F000h
win32u                           loaded at 77300000h - 7731A000h
combase                          loaded at 777F0000h - 77A6B000h
gdi32full                        loaded at 763C0000h - 7649E000h
RPCRT4                           loaded at 77730000h - 777E9000h
ADVAPI32                         loaded at 75920000h - 7599C000h
msvcp_win                        loaded at 769F0000h - 76A69000h
dbghelp                          loaded at 74FD0000h - 751A2000h
sechost                          loaded at 776A0000h - 77722000h
OLEAUT32                         loaded at 76D30000h - 76DCC000h
SHELL32                          loaded at 75A70000h - 760D2000h
ole32                            loaded at 77120000h - 7726D000h
CRYPT32                          loaded at 77590000h - 77693000h
shared                           loaded at 6EA50000h - 6EA71000h
zlib1                            loaded at 63AA0000h - 63AB7000h
sqlite3                          loaded at 639D0000h - 63A9B000h
MSVCP140                         loaded at 63960000h - 639CD000h
imagehlp                         loaded at 764A0000h - 764BB000h
COMDLG32                         loaded at 76B90000h - 76C40000h
shcore                           loaded at 77320000h - 773E0000h
MSIMG32                          loaded at 6EA40000h - 6EA46000h
OLEACC                           loaded at 6F420000h - 6F474000h
WINHTTP                          loaded at 6F340000h - 6F416000h
gdiplus                          loaded at 71180000h - 712ED000h
VCRUNTIME140                     loaded at 63940000h - 63955000h
Secur32                          loaded at 753C0000h - 753CA000h
dbgcore                          loaded at 74EE0000h - 74F09000h
SSPICLI                          loaded at 75370000h - 75395000h
IMM32                            loaded at 76C40000h - 76C65000h
kernel.appcore                   loaded at 753F0000h - 75403000h
bcryptPrimitives                 loaded at 76C70000h - 76CD2000h
windows.storage                  loaded at 74810000h - 74EDE000h
wintypes                         loaded at 74740000h - 74807000h
MSCTF                            loaded at 77A70000h - 77B4B000h
foo_bpm                          loaded at 638F0000h - 63931000h
foo_discord_rich                 loaded at 63840000h - 638EC000h
foo_musical_spectrum             loaded at 10000000h - 1001C000h
foo_vis_oscilloscope_d2d         loaded at 63810000h - 6383C000h
d2d1                             loaded at 63320000h - 6380B000h
foo_vis_projectM                 loaded at 63190000h - 6331A000h
OPENGL32                         loaded at 67220000h - 67300000h
GLU32                            loaded at 671D0000h - 67212000h
dxcore                           loaded at 704D0000h - 704FD000h
foo_converter                    loaded at 630F0000h - 63185000h
foo_wave_minibar_mod             loaded at 630A0000h - 630E1000h
foo_ui_std                       loaded at 62EF0000h - 6309C000h
dwmapi                           loaded at 67300000h - 67324000h
foo_input_std                    loaded at 62D30000h - 62EE9000h
avcodec-fb2k-59                  loaded at 62B00000h - 62D21000h
avformat-fb2k-59                 loaded at 62AD0000h - 62AFB000h
avutil-fb2k-57                   loaded at 62910000h - 62ACA000h
MSACM32                          loaded at 628F0000h - 62909000h
bcrypt                           loaded at 74020000h - 7403A000h
foo_dsp_std                      loaded at 628B0000h - 628EB000h
foo_dsp_eq                       loaded at 62840000h - 628AD000h
foo_dsp_crossmix                 loaded at 62830000h - 6283F000h
foo_headphone_eq                 loaded at 033D0000h - 0347A000h
foo_openmpt54                    loaded at 62800000h - 6282E000h
libopenmpt                       loaded at 62660000h - 627FD000h
openmpt-zlib                     loaded at 62590000h - 625A8000h
openmpt-vorbis                   loaded at 625B0000h - 6265B000h
openmpt-mpg123                   loaded at 62550000h - 62589000h
openmpt-ogg                      loaded at 62540000h - 6254B000h
foo_gep                          loaded at 62150000h - 6253A000h
foo_midi                         loaded at 61E40000h - 6214D000h
bass                             loaded at 61DF0000h - 61E3D000h
bassmidi                         loaded at 61D60000h - 61DE1000h
foo_freedb2                      loaded at 61D20000h - 61D53000h
foo_room_eq                      loaded at 03630000h - 03863000h
foo_dsp_vocal_exciter            loaded at 61CF0000h - 61D14000h
foo_vis_vumeter                  loaded at 61C40000h - 61CE5000h
foo_openlyrics                   loaded at 61B00000h - 61C40000h
foo_dsp_vst3                     loaded at 61AA0000h - 61AFC000h
WS2_32                           loaded at 760F0000h - 7614F000h
foo_dsp_effect                   loaded at 03920000h - 03989000h
foo_dsp_utility                  loaded at 61A70000h - 61A92000h
foo_input_ffmpeg                 loaded at 61A30000h - 61A63000h
foo_enhanced_spectrum_analyzer   loaded at 039D0000h - 03A13000h
foo_unpack                       loaded at 619B0000h - 61A29000h
foo_fileops                      loaded at 61950000h - 619AD000h
clbcatq                          loaded at 77B50000h - 77BD2000h
atlthunk                         loaded at 61940000h - 6194E000h
WindowsCodecs                    loaded at 6E8E0000h - 6EA40000h
dataexchange                     loaded at 6ECA0000h - 6ECEC000h
twinapi.appcore                  loaded at 6EAD0000h - 6EC9F000h
TextShaping                      loaded at 6EDC0000h - 6EE55000h
MMDevApi                         loaded at 618C0000h - 6193C000h
DEVOBJ                           loaded at 74260000h - 74284000h
CFGMGR32                         loaded at 744B0000h - 744ED000h
d3d9                             loaded at 67330000h - 674A1000h
VERSION                          loaded at 74F20000h - 74F28000h
directxdatabasehelper            loaded at 6F8E0000h - 6F91C000h
nvldumd                          loaded at 5FD60000h - 5FDF6000h
msasn1                           loaded at 742E0000h - 742EE000h
cryptnet                         loaded at 74610000h - 74637000h
drvstore                         loaded at 74500000h - 74609000h
wldp                             loaded at 74210000h - 74252000h
cryptbase                        loaded at 74F10000h - 74F1B000h
WINTRUST                         loaded at 77270000h - 772C8000h
CRYPTSP                          loaded at 74400000h - 74415000h
rsaenh                           loaded at 743D0000h - 74400000h
nvd3dum                          loaded at 5D1D0000h - 5FD58000h
nvspcap                          loaded at 61690000h - 618BA000h
profapi                          loaded at 753D0000h - 753E9000h
ntmarta                          loaded at 74340000h - 74369000h
gpapi                            loaded at 741E0000h - 74201000h
DWrite                           loaded at 64350000h - 64568000h
textinputframework               loaded at 646C0000h - 647A4000h
CoreMessaging                    loaded at 6F920000h - 6F9ED000h
CoreUIComponents                 loaded at 60740000h - 609D0000h
aticfx32                         loaded at 61500000h - 61684000h
POWRPROF                         loaded at 742F0000h - 74336000h
UMPDC                            loaded at 74370000h - 7437E000h
amdihk32                         loaded at 609D0000h - 609F7000h
sud                              loaded at 60710000h - 60735000h
PROPSYS                          loaded at 710B0000h - 71176000h
ADVPACK                          loaded at 606E0000h - 6070F000h
SETUPAPI                         loaded at 764C0000h - 768FD000h
DUI70                            loaded at 60570000h - 606D2000h
PP-UWP-Interop                   loaded at 60560000h - 6056A000h
vccorlib140                      loaded at 60510000h - 60552000h
Windows.Media.Playback.Backgrou  loaded at 60450000h - 6050E000h
MFPlat                           loaded at 602B0000h - 60446000h
RTWorkQ                          loaded at 60280000h - 602AD000h
Windows.Media.MediaControl       loaded at 60200000h - 60275000h
MFMediaEngine                    loaded at 5FE70000h - 601FE000h
XmlLite                          loaded at 5FE40000h - 5FE6B000h
AUDIOSES                         loaded at 5C240000h - 5C3CA000h
Windows.UI                       loaded at 5C130000h - 5C23A000h
Windows.Media.Devices            loaded at 5C0B0000h - 5C124000h
Windows.Media.Playback.ProxyStu  loaded at 5FE30000h - 5FE3D000h
OneCoreUAPCommonProxyStub        loaded at 5BE30000h - 5C0A9000h
explorerframe                    loaded at 5BC50000h - 5BE24000h
dxgi                             loaded at 70750000h - 7081A000h
d3d11                            loaded at 5BA10000h - 5BC47000h
nvwgf2um                         loaded at 58170000h - 5BA03000h
atiuxpag                         loaded at 5FE00000h - 5FE2E000h
atidxx32                         loaded at 56720000h - 58169000h
avrt                             loaded at 56710000h - 56719000h
resourcepolicyclient             loaded at 56700000h - 56710000h
dsdmo                            loaded at 566C0000h - 566F1000h
msdmo                            loaded at 566B0000h - 566B9000h
atiu9pag                         loaded at 614D0000h - 614FA000h
atiumdag                         loaded at 60A00000h - 614C1000h
atiumdva                         loaded at 5C3D0000h - 5D1C5000h

Stack dump analysis:
Address: 5E245431h (nvd3dum+1075431h)
Address: 5E302BDCh (nvd3dum+1132BDCh)
Address: 5E301EE0h (nvd3dum+1131EE0h)
Address: 5C32336Dh (AUDIOSES+E336Dh), symbol: "Ordinal5" (+348EDh)
Address: 7626C9E8h (KERNELBASE+11C9E8h), symbol: "CloseHandle" (+58h)
Address: 673E1470h (d3d9+B1470h), symbol: "DebugSetLevel" (+1EA0h)
Address: 769163F1h (KERNEL32+163F1h), symbol: "GlobalFindAtomW" (+E1h)
Address: 769163B4h (KERNEL32+163B4h), symbol: "GlobalFindAtomW" (+A4h)
Address: 673053B0h (dwmapi+53B0h), symbol: "DwmExtendFrameIntoClientArea" (+C00h)
Address: 773058FCh (win32u+58FCh), symbol: "NtUserHwndQueryRedirectionInfo" (+Ch)
Address: 7745DB6Dh (USER32+7DB6Dh), symbol: "DwmGetDxSharedSurface" (+4Dh)
Address: 67306422h (dwmapi+6422h), symbol: "DwmpDxGetWindowSharedSurface" (+292h)
Address: 673068FFh (dwmapi+68FFh), symbol: "DwmpDxGetWindowSharedSurface" (+76Fh)
Address: 01000000h (foobar2000+350000h)
Address: 6737A666h (d3d9+4A666h)
Address: 673BF8E7h (d3d9+8F8E7h), symbol: "Direct3DCreate9On12Ex" (+C077h)
Address: 673BF922h (d3d9+8F922h), symbol: "Direct3DCreate9On12Ex" (+C0B2h)
Address: 67379B30h (d3d9+49B30h)
Address: 5E1CBA65h (nvd3dum+FFBA65h)
Address: 00D4B838h (foobar2000+9B838h)
Address: 5E2CBDC7h (nvd3dum+10FBDC7h)
Address: 5E2CE242h (nvd3dum+10FE242h)
Address: 5E2D1824h (nvd3dum+1101824h)
Address: 5E1B8CA3h (nvd3dum+FE8CA3h)
Address: 5E2E35F8h (nvd3dum+11135F8h)
Address: 5E2EDAC4h (nvd3dum+111DAC4h)
Address: 5E35CD48h (nvd3dum+118CD48h), symbol: "QueryOglResource" (+53428h)
Address: 5E35CE4Fh (nvd3dum+118CE4Fh), symbol: "QueryOglResource" (+5352Fh)
Address: 5E35CD48h (nvd3dum+118CD48h), symbol: "QueryOglResource" (+53428h)
Address: 67373C74h (d3d9+43C74h)
Address: 67373C79h (d3d9+43C79h)
Address: 673AEA60h (d3d9+7EA60h), symbol: "Direct3DCreate9" (+3E0h)
Address: 673B79FCh (d3d9+879FCh), symbol: "Direct3DCreate9On12Ex" (+418Ch)
Address: 67372815h (d3d9+42815h)
Address: 00E36FB0h (foobar2000+186FB0h)
Address: 67467240h (d3d9+137240h), symbol: "Direct3DShaderValidatorCreate9" (+41DA0h)
Address: 67392970h (d3d9+62970h), symbol: "Direct3DCreate9Ex" (+A250h)
Address: 673A6A96h (d3d9+76A96h), symbol: "Direct3DCreate9Ex" (+1E376h)
Address: 673A6A50h (d3d9+76A50h), symbol: "Direct3DCreate9Ex" (+1E330h)
Address: 5E2F8A0Ah (nvd3dum+1128A0Ah)
Address: 5E2F8990h (nvd3dum+1128990h)
Address: 674537F1h (d3d9+1237F1h), symbol: "Direct3DShaderValidatorCreate9" (+2E351h)
Address: 67390E07h (d3d9+60E07h), symbol: "Direct3DCreate9Ex" (+86E7h)
Address: 67390DC0h (d3d9+60DC0h), symbol: "Direct3DCreate9Ex" (+86A0h)
Address: 6740B70Bh (d3d9+DB70Bh), symbol: "Ordinal23" (+1E56Bh)
Address: 6740B5ABh (d3d9+DB5ABh), symbol: "Ordinal23" (+1E40Bh)
Address: 61C576D2h (foo_vis_vumeter+176D2h), symbol: "foobar2000_get_interface" (+C636h)
Address: 61C578A4h (foo_vis_vumeter+178A4h), symbol: "foobar2000_get_interface" (+C808h)
Address: 61C57D1Eh (foo_vis_vumeter+17D1Eh), symbol: "foobar2000_get_interface" (+CC82h)
Address: 61C4A47Dh (foo_vis_vumeter+A47Dh)
Address: 61C56437h (foo_vis_vumeter+16437h), symbol: "foobar2000_get_interface" (+B39Bh)
Address: 61C48E2Eh (foo_vis_vumeter+8E2Eh)
Address: 774123E3h (USER32+323E3h), symbol: "Ordinal2713" (+6B3h)
Address: 774030E6h (USER32+230E6h), symbol: "CallWindowProcW" (+716h)
Address: 77402D9Ah (USER32+22D9Ah), symbol: "CallWindowProcW" (+3CAh)
Address: 7740D8E9h (USER32+2D8E9h), symbol: "GetWindowThreadProcessId" (+2A9h)
Address: 707CF590h (dxgi+7F590h), symbol: "DXGIGetDebugInterface1" (+E7B0h)
Address: 77C6870Dh (ntdll+7870Dh), symbol: "KiUserCallbackDispatcher" (+4Dh)
Address: 77414EB0h (USER32+34EB0h), symbol: "WindowFromPoint" (+F40h)
Address: 77402B6Ah (USER32+22B6Ah), symbol: "CallWindowProcW" (+19Ah)
Address: 77C87B80h (ntdll+97B80h), symbol: "NtdllDialogWndProc_W" (+160h)
Address: 707CF590h (dxgi+7F590h), symbol: "DXGIGetDebugInterface1" (+E7B0h)
Address: 77414EB0h (USER32+34EB0h), symbol: "WindowFromPoint" (+F40h)
Address: 7740CADFh (USER32+2CADFh), symbol: "GetPropW" (+FFh)
Address: 707CF6E3h (dxgi+7F6E3h), symbol: "DXGIGetDebugInterface1" (+E903h)
Address: 7740EABFh (USER32+2EABFh), symbol: "TranslateMessage" (+15Fh)
Address: 77C6870Dh (ntdll+7870Dh), symbol: "KiUserCallbackDispatcher" (+4Dh)
Address: 77C68640h (ntdll+78640h), symbol: "KiUserApcDispatcher" (+70h)
Address: 77C87B80h (ntdll+97B80h), symbol: "NtdllDialogWndProc_W" (+160h)
Address: 773013ACh (win32u+13ACh), symbol: "NtUserDispatchMessage" (+Ch)
Address: 77401AE4h (USER32+21AE4h), symbol: "DispatchMessageW" (+604h)
Address: 77C6614Ch (ntdll+7614Ch), symbol: "ZwCallbackReturn" (+Ch)
Address: 7740D834h (USER32+2D834h), symbol: "GetWindowThreadProcessId" (+1F4h)
Address: 77414EB0h (USER32+34EB0h), symbol: "WindowFromPoint" (+F40h)
Address: 77403A44h (USER32+23A44h), symbol: "IsDialogMessageW" (+854h)
Address: 62FC3FBDh (foo_ui_std+D3FBDh)
Address: 00D7BCFFh (foobar2000+CBCFFh)
Address: 00F8F094h (foobar2000+2DF094h)
Address: 00EE806Ch (foobar2000+23806Ch)
Address: 00F77E68h (foobar2000+2C7E68h)
Address: 00D7BE19h (foobar2000+CBE19h)
Address: 00D7D25Dh (foobar2000+CD25Dh)
Address: 00F16414h (foobar2000+266414h)
Address: 00D7D0F1h (foobar2000+CD0F1h)
Address: 76AA989Dh (ucrtbase+3989Dh), symbol: "crt_atexit" (+3Dh)
Address: 00F16414h (foobar2000+266414h)
Address: 00D7D0F1h (foobar2000+CD0F1h)
Address: 76B7571Ch (ucrtbase+10571Ch), symbol: "mbcasemap" (+16Ch)
Address: 00F9157Ch (foobar2000+2E157Ch)
Address: 00ED737Bh (foobar2000+22737Bh)
Address: 00EE82D5h (foobar2000+2382D5h)
Address: 00ED6F98h (foobar2000+226F98h)
Address: 00ED701Ch (foobar2000+22701Ch)
Address: 00ED701Ch (foobar2000+22701Ch)
Address: 00ED69FEh (foobar2000+2269FEh)
Address: 76917D69h (KERNEL32+17D69h), symbol: "BaseThreadInitThunk" (+19h)
Address: 76917D50h (KERNEL32+17D50h), symbol: "BaseThreadInitThunk" (+0h)
Address: 77C5B74Bh (ntdll+6B74Bh), symbol: "RtlInitializeExceptionChain" (+6Bh)
Address: 77C6E8B0h (ntdll+7E8B0h), symbol: "wcstombs" (+70h)
Address: 77C5B6CFh (ntdll+6B6CFh), symbol: "RtlClearBits" (+BFh)
Address: 77C88674h (ntdll+98674h), symbol: "RtlCaptureContext" (+F4h)
Address: 00ED701Ch (foobar2000+22701Ch)
P.S.: nvd3dum.... I assumed that this is due to the included visualizers (and specifically the oscilloscope), but my assumption turned out to be wrong. I do not know what to do.
P.P.S.: My computer has two video adapters, and the player runs on a weaker video adapter. I can't say exactly what version the problems started with, but the first dump was created on January 18th. Then I did not pay attention to it.
Title: Re: foobar2000 v2.0 bugs
Post by: umnin on 2023-03-01 09:29:12
I have 2.0 beta 26 x64. But I didn't found any consistency in crashes except open foobar2000, wait 5+ min, do any action with it =< crash. I have sent 5 reports already. Had no problems with previous installed beta 24.
Title: Re: foobar2000 v2.0 bugs
Post by: kor5n on 2023-03-02 14:05:56
Quote from: kor5n on
Hi. I've a bug with foobar2000 beta 26-x86 on Win11 Pro.
When the UAC window opens asking for administrator rights, the player crashes if the main window is not minimized (if it is minimized, crashes happen every other time).
Moreover, the player crashed after I left the game (closed the application). Both applications are rendered on the same monitor, but through different video accelerators. If necessary, I will send a dump (the program offered to send the report, and I did it).
Title: Re: foobar2000 v2.0 bugs
Post by: ApacheReal on 2023-03-05 16:49:21
Problem whit plugin ZXTune Player and foobar2000 v2.0

The .dsf file don't start.

Drag and Drop in playlist don't work.

Loop processed file.

Removed the plugin the .dsf files worked again.

.dsf = Direct Stream Digital (DSD) not Sega Dreamcast format (DSF)
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2023-03-05 23:54:26
When you have multiple inputs able to play different file types with the same extension, you can set the priority of one over the other under File>Preferences>Playback>Decoding.
Title: Re: foobar2000 v2.0 bugs
Post by: paregistrase on 2023-03-06 02:43:22
Using the dark theme the status bar fonts sometimes have artifacts in maximized state

(https://i.imgur.com/eGpSAqY.png)

Getting out of maximized, make it return to normal

(https://i.imgur.com/u1cNGSU.png)

With "use system setting" didn't happen.

One way to trigger it is to select Dark mode, maximize the window and open properties dialog.
Title: Re: foobar2000 v2.0 bugs
Post by: ApacheReal on 2023-03-06 05:45:47
Quote from: marc2k3 on
When you have multiple inputs able to play different file types with the same extension, you can set the priority of one over the other under File>Preferences>Playback>Decoding.
Thank you.

I didn't know about this option.
Title: Re: foobar2000 v2.0 bugs
Post by: Porcus on 2023-03-06 11:27:00
@ApacheReal: Although you have gotten an answer on how to prioritize the playback chain, your DSD files can be losslessly compressed with WavPack. You cannot use a player like fb2k (nor ffmpeg) to do that, but you can drag and drop it onto wavpack.exe .

Tip: If you prefer drag+drop over command-line, then rename the executable first; this suggestion by the developer will get you better compression, verification, and tags imported:
https://hydrogenaud.io/index.php/topic,122626.msg1012159.html#msg1012159
Another option like {--allow-huge-tags} might be necessary if it has biggg album art. ID3v2.4 is at test version stage with an executable posted here: https://hydrogenaud.io/index.php/topic,123684.0.html

(WavPack will reject DST-compressed DSDIFF files - already compressed heavier than WavPack can - as well as the .wsd file format.)
Title: Re: foobar2000 v2.0 bugs
Post by: orangefx on 2023-03-08 16:00:30
i run win10 in dark mode on uhd screen scaled 125%. the visibility of everything is worse readable (for me) in v.2 vs. v.1.6.
is there an option to scale up and colour the fonts, also for submenus and preferences? also it would be nice to be able to resize the preferences window when working with advanced options.
Title: Re: foobar2000 v2.0 bugs
Post by: ApacheReal on 2023-03-08 17:47:17
Problems of runtime error after installing the plugin ZXTune Player 0.0.9 whit foobar2000 v2.0 beta 26

Manually removed the plugin the problem does not recur.
Title: Re: foobar2000 v2.0 bugs
Post by: SleepShadowWeb on 2023-03-10 03:14:58
not open the link https://stream.friskyradio.com/
It plays in my browser, it plays in Aimp, but doesn't open in foobar2000
Title: Re: foobar2000 v2.0 bugs
Post by: NetRanger on 2023-03-10 04:45:52
Quote from: SleepShadowWeb on
not open the link https://stream.friskyradio.com/
It plays in my browser, it plays in Aimp, but doesn't open in foobar2000

No problems here with adding the URL through File->Add Location
Title: Re: foobar2000 v2.0 bugs
Post by: sharpedge on 2023-03-11 08:41:17
When I use 2.0 an dalter any tags, the playback statistics component does not act as expected:
The "date added" info gets updated with the date and time of the tag alteration.

In foobar 1.x, the date added field is not changed.

I use latest versions in both 1 and 2 but will stop using 2 even though I love it...
I really want to keep my original date added info
Title: Re: foobar2000 v2.0 bugs
Post by: ASopH on 2023-03-11 10:43:30
Hi,
refacets config is not exported by "export-theme" in defaultUI and converter config cannot exported as well.
Title: Re: foobar2000 v2.0 bugs
Post by: SleepShadowWeb on 2023-03-11 10:51:57
Quote from: NetRanger on
Quote from: SleepShadowWeb on
not open the link https://stream.friskyradio.com/
It plays in my browser, it plays in Aimp, but doesn't open in foobar2000

No problems here with adding the URL through File->Add Location

I add the address, and I get a message in response:
The following error(s) occurred during loading of the location(s)

personally you add, music plays?
Title: Re: foobar2000 v2.0 bugs
Post by: Gus. on 2023-03-11 21:47:13
Quote from: SleepShadowWeb on
not open the link https://stream.friskyradio.com/
It plays in my browser, it plays in Aimp, but doesn't open in foobar2000

Plays fine for me as well:
https://stream.frisky.friskyradio.com/mp3_low (96kbps)
https://stream.frisky.friskyradio.com/mp3_high (320kbps)
https://stream.deep.friskyradio.com/mp3_low
https://stream.deep.friskyradio.com/mp3_high
https://stream.chill.friskyradio.com/mp3_low
https://stream.chill.friskyradio.com/mp3_high
Title: Re: foobar2000 v2.0 bugs
Post by: paregistrase on 2023-03-12 00:40:02
Quote from: Gus. on
Quote from: SleepShadowWeb on
not open the link https://stream.friskyradio.com/
It plays in my browser, it plays in Aimp, but doesn't open in foobar2000

Plays fine for me as well:
https://stream.frisky.friskyradio.com/mp3_low (96kbps)
https://stream.frisky.friskyradio.com/mp3_high (320kbps)
https://stream.deep.friskyradio.com/mp3_low
https://stream.deep.friskyradio.com/mp3_high
https://stream.chill.friskyradio.com/mp3_low
https://stream.chill.friskyradio.com/mp3_high

I tried the first two

Start to play but few seconds later foobar crashes completely.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-03-12 01:34:27
Plays fine for me, no crash. foobar2000 v2.0 beta 26.
Title: Re: foobar2000 v2.0 bugs
Post by: Gus. on 2023-03-12 01:34:42
I suspect server-side problems with the streams, sometimes they take very long to connect. There's also128kbps:
https://stream.frisky.friskyradio.com/mp3_mid
I've been trying them in foobar2000 beta26  x64,  no  crashes...
Title: Re: foobar2000 v2.0 bugs
Post by: paregistrase on 2023-03-12 02:16:37
Beta 26 too., never reach to 30 seconds. Hard crash, no logs or dump (empty files)

:(
Title: Re: foobar2000 v2.0 bugs
Post by: Vicas on 2023-03-12 18:49:00
Beta 26 x32 plays fine every link, no crashes at all
Title: Re: foobar2000 v2.0 bugs
Post by: papavlos on 2023-03-16 19:47:05
Beta27 x32 and x64 under WINE/Linux - the only GUI bug I can observe is the Library view in dark mode:
Title: Re: foobar2000 v2.0 bugs
Post by: paregistrase on 2023-03-17 08:09:38
Quote from: papavlos on
Beta27 x32 and x64 under WINE/Linux - the only GUI bug I can observe is the Library view in dark mode:

I don't know if It is foobar2000 fault or simply lack of wine support for dark themes but without tweaking the default look of foobar dark mode has some odd looking zones, but my Album List didn't look as bad as yours

(https://i.imgur.com/CQvqRxF.png)

Some can be changed with the winecfg tool, but others like the active tab doesn't obey any of it and the gray background with black text is very hard to read. If someone knows how modified, it will be much appreciated.

One thing that seems like a bug is the status bars (from main window, properties, etc.) that gets all blurry.

(https://i.imgur.com/OX3z2DP.png)

(https://i.imgur.com/FwYA96o.png)


but at the end doesn't look so bad

(https://i.imgur.com/5cJNXn4.png)

Title: Re: foobar2000 v2.0 bugs
Post by: umnin on 2023-03-17 09:02:20
Beta27x64 still have random crashes.
Open foobar, leave minimized 5+ min. Click play. Crash.
Open foobar, start play immediately play 2 tracks, on 3rd try to delete file via global hotkey. Crash.

So once again I go back to beta24 without crashes.
Also question. Can I disable annoying "this version is over 8 weeks old"?
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2023-03-17 09:54:43
Quote from: umnin on
Beta27x64 still have random crashes.
Open foobar, leave minimized 5+ min. Click play. Crash.
Open foobar, start play immediately play 2 tracks, on 3rd try to delete file via global hotkey. Crash.
Looked into matching crash report data, looks like your config.sqlite in foobar2000 profile is corrupted, please make a backup and delete.
A future version will recover from this automatically.
Quote
So once again I go back to beta24 without crashes.
Also question. Can I disable annoying "this version is over 8 weeks old"?
Request noted.
Title: Re: foobar2000 v2.0 bugs
Post by: umnin on 2023-03-17 20:27:00
Quote from: Peter on
Looked into matching crash report data, looks like your config.sqlite in foobar2000 profile is corrupted, please make a backup and delete.

Looks like you were right. Deleted config.sqlite, set settings from scratch (and manually set total time played from old config) and so far no crashes. Will update if something changes in next few days.
Do devs need my old config.sqlite that provokes crashes?
Title: Re: foobar2000 v2.0 bugs
Post by: Ibanezz on 2023-03-18 23:41:11
Hello
I believe this is an actual bug in foobar's asio audio routing, but if i have worng you can move it to proper section.
I want to use foobar as upnp renderer/player because Jriver is sometimes resource heavy if you want to surf and listen to music at the same time, it starts to lag both the music and the webbrowser.
I am using dephonica as crossover with my 8-ch dac. But foobar asio wont show all channels, it only shows 6 out of 8 channels.
This crossover is a freeeware now, so the full version is the one we get with all eight channels to use.
But foobar asio messes up all audio routing, it routs all channels wrong, and some channels aren't even there, and some channels dosent even play at all, or some channels play to same channel, this with Dephonica.
And this also applies to asio4all, messed up audio routing, even if all channels are there and plying, but in the wrong order, a little better, but i shouldn't be forced to totally reconfigure Dephonica to use foobar.
It works all correct in all other applications that uses asio. Like Jriver for example.
in dephonica CH-CH2 is used for headphones on Dac CH1-CH2, so no crosseover there.
But here it it all mesed up and actually not really routable eihter, just nameable of what channel it is.
And in dephonica it is channel based from 1-8, and why is foobars channels totally messed up comparing to all other routing programs out there?, i can switch to other programs that uses asio and link to dephonica and it just works as the crossover is preconfigured with slopes on channels 3-8 to an 3-way active setup, but with foobar this seems impossible. Because of wrong channel order and no real way to actually reroute the channel (tested with asio4all, and it just gave it an name, not an actual reroute).

Also tested to downmix 7.1 / 5.1 to stereo, but to no luck, so i am stuck.

My config
Asus Strix X570e-gaming
3600mhz corsair SL Pro 32 GB
EVGA 750 G2 PSU

Windows 11 64bit
Foobar latest 2.x X64
Latest asio+dsd in foorbar
Latest Asio driver from Okto
Foobar > Dephonica > USB >Dac > 6 Amps
Title: Re: foobar2000 v2.0 bugs
Post by: papavlos on 2023-03-19 22:08:33
@paregistrase 
I think you have selected a dark theme at you Desktop Environment (DE) level and it looks like foobar is following it.
I have something different: a light theme at my DE and have selected "Dark Blue" colors set in "View > Layout > Quick setup" in foobar directly.
Please try to change your color set in foobar to something different than your DE and check if all foobar elements are painted consistently, differently than the rest of your DE.

A nice view setup, BTW. Everything under control in one screen.
Title: Re: foobar2000 v2.0 bugs
Post by: paregistrase on 2023-03-20 03:30:20
Quote from: papavlos on
@paregistrase 
I think you have selected a dark theme at you Desktop Environment (DE) level and it looks like foobar is following it.
I have something different: a light theme at my DE and have selected "Dark Blue" colors set in "View > Layout > Quick setup" in foobar directly.
Please try to change your color set in foobar to something different than your DE and check if all foobar elements are painted consistently, differently than the rest of your DE.

A nice view setup, BTW. Everything under control in one screen.

I wish it did. Yes I have a Dark theme in Desktop and I want a Dark foobar, but I'm on Linux, running foobar through wine, and it didn't detect if I have a dark or light theme in my desktop. Selecting "use system setting" only give the old fashion XP style default wine theme. If I want dark foobar I must set Dark mode and here is when not all elements are themed. The same happens with the light foobar theme.

I don't think that it was foobar fault, it searches for one condition that is not meet in my case (no dark theme support in wine). All the correction must be set in wine itself, so in fact, foobar has his own color, independent of my desktop selection.

Will be cool that foobar will gives more customization elements, but I supposed that it is not necessary on Windows.
Title: Re: foobar2000 v2.0 bugs
Post by: dore.moni on 2023-03-20 10:53:24
Hello.

Latest foobar2000 v1.6.16 and foobar2000 v2.0 still can't output 32bit files properly. It playback ok, status bar shows that it is 32bit, but my DAC internal test shows that it is 24bit instead of 32bit. When i test the same files with JRiver Media Center, DAC screen shows it as 32bit.

I use ASIO Output 2.1.2 and my DAC is RME ADI-2 Pro FS. The testing files i use are special wav files for testing bit-perfect playback of RME  ADI-2 Pro FS

Can someone else check if it is possible to output 32bit files properly?
Title: Re: foobar2000 v2.0 bugs
Post by: wojak on 2023-03-20 13:26:32
Quote from: dore.moni on
Hello.

Latest foobar2000 v1.6.16 and foobar2000 v2.0 still can't output 32bit files properly. It playback ok, status bar shows that it is 32bit, but my DAC internal test shows that it is 24bit instead of 32bit. When i test the same files with JRiver Media Center, DAC screen shows it as 32bit.

I use ASIO Output 2.1.2 and my DAC is RME ADI-2 Pro FS. The testing files i use are special wav files for testing bit-perfect playback of RME  ADI-2 Pro FS

Can someone else check if it is possible to output 32bit files properly?

I can't answer your question, but some time ago I checked that Foobar still can't losslessly convert 32 bit file into 32 bit files. If it is still the same.....most probably it also can't play such files losslessly.
Title: Re: foobar2000 v2.0 bugs
Post by: Porcus on 2023-03-20 15:58:20
fb2k 1.x operates with 32-bit float internally, and so it cannot do 32-bit integer in a lossless manner.

Version 2 is still at beta stage, so I'd be patient. It can verify 32-bit integer FLAC files, but I have no idea what it can output.
(For DACing it doesn't matter, there is still nothing that can deliver the 25th bit, had it even been audible. There is a chip that boasts 140 dB dynamic range (in mono only!) - but in real measured environments it doesn't fully hit 20 bits: http://archimago.blogspot.com/2017/06/measurements-oppo-sonica-dac-ess-sabre.html )
Title: Re: foobar2000 v2.0 bugs
Post by: Cannonaire on 2023-03-20 19:23:26
I'm on Beta 27 now and it seems like there is a regression - the popping and lingering audio from the previous track upon manually changing tracks is back even though I have "Fast DSP reset when cycling tracks manually" off.
Title: Re: foobar2000 v2.0 bugs
Post by: mudlord on 2023-03-20 20:46:02
Quote from: dore.moni on
Hello.

Latest foobar2000 v1.6.16 and foobar2000 v2.0 still can't output 32bit files properly. It playback ok, status bar shows that it is 32bit, but my DAC internal test shows that it is 24bit instead of 32bit. When i test the same files with JRiver Media Center, DAC screen shows it as 32bit.

I use ASIO Output 2.1.2 and my DAC is RME ADI-2 Pro FS. The testing files i use are special wav files for testing bit-perfect playback of RME  ADI-2 Pro FS

Can someone else check if it is possible to output 32bit files properly?

I have to question why you sent a DM to me personally about this when really its not my concern. I find that exceptionally irritating.

Porcus has your answer, anyway.
Title: Re: foobar2000 v2.0 bugs
Post by: dore.moni on 2023-03-21 05:22:56
Sorry for that. I asked you personally because you are professional developer and can diagnose this problem.
Porcus is incorrect. When volume in foobar is at max 0dB, foobar does not do internal processing and must output bits as they are in file. (if the intput of dac can accept it)

When  volume in foobar is at max 0dB and the file is 24bit it outputs bit-perfect as in file.
But if the file is 32bit integer foobar outputs it as 24bit simply by trunkating last 8bits. And the output is not bitperfect then.
So my question why it is so?

JRiver Media Center outputs 32bit integer as is at 32bit.
Title: Re: foobar2000 v2.0 bugs
Post by: Forfit on 2023-03-21 10:11:17
When I pause Fb2k b27 the working set RAM grows impressively over time.
Title: Re: foobar2000 v2.0 bugs
Post by: Chibisteven on 2023-03-22 06:13:56
Quote from: dore.moni on
Sorry for that. I asked you personally because you are professional developer and can diagnose this problem.
Porcus is incorrect. When volume in foobar is at max 0dB, foobar does not do internal processing and must output bits as they are in file. (if the intput of dac can accept it)

When  volume in foobar is at max 0dB and the file is 24bit it outputs bit-perfect as in file.
But if the file is 32bit integer foobar outputs it as 24bit simply by trunkating last 8bits. And the output is not bitperfect then.
So my question why it is so?

JRiver Media Center outputs 32bit integer as is at 32bit.


Porcus is correct, you're wrong.  foobar2000 converts everything to 32-bit floating point in 32-bit versions of the application where 64-bit versions (2.0 or newer) convert everything to 64-bit floating point.  foobar2000 does internal processing at all times regardless of the volume setting.  It's just at 0 dB that this processing is simply a lossless passthrough of sorts for most formats up to 24-bit integers (i.e. reversible) in 32-bit versions.  I know I'm repeating what has been said, but maybe you need to hear it from somebody else.
Title: Re: foobar2000 v2.0 bugs
Post by: Forfit on 2023-03-22 06:40:29
Quote from: Forfit on
When I pause Fb2k b27 the working set RAM grows impressively over time.
Playlist in a Virtual Disk.
Gif Screenshot:
(https://interno.altervista.org/temp/fb2kPause.gif)
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-03-22 07:18:48
Any problematic components?
Title: Re: foobar2000 v2.0 bugs
Post by: Forfit on 2023-03-22 08:05:33
Quote from: grimes on
Any problematic components?
Same when I remove all components.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-03-22 09:24:48
This memory leak happened to me? https://hydrogenaud.io/index.php/topic,122847.msg1017848.html#msg1017848
Title: Re: foobar2000 v2.0 bugs
Post by: wojak on 2023-03-22 09:29:28
Quote from: Chibisteven on
Quote from: dore.moni on
Sorry for that. I asked you personally because you are professional developer and can diagnose this problem.
Porcus is incorrect. When volume in foobar is at max 0dB, foobar does not do internal processing and must output bits as they are in file. (if the intput of dac can accept it)

When  volume in foobar is at max 0dB and the file is 24bit it outputs bit-perfect as in file.
But if the file is 32bit integer foobar outputs it as 24bit simply by trunkating last 8bits. And the output is not bitperfect then.
So my question why it is so?

JRiver Media Center outputs 32bit integer as is at 32bit.


Porcus is correct, you're wrong.  foobar2000 converts everything to 32-bit floating point in 32-bit versions of the application where 64-bit versions (2.0 or newer) convert everything to 64-bit floating point.  foobar2000 does internal processing at all times regardless of the volume setting.  It's just at 0 dB that this processing is simply a lossless passthrough of sorts for most formats up to 24-bit integers (i.e. reversible) in 32-bit versions.  I know I'm repeating what has been said, but maybe you need to hear it from somebody else.

32 bit foobar operates in 32 float so can't losslessly convert or play 32 integers - understandable. But why 64 bit foobar (which operates in 64 float) can't losslesly play or convert 32 integers?
Title: Re: foobar2000 v2.0 bugs
Post by: Porcus on 2023-03-22 10:17:00
Quote from: wojak on
why 64 bit foobar (which operates in 64 float) can't losslesly play or convert 32 integers?
Because v2 is not done yet, you are still testing a development version?
Title: Re: foobar2000 v2.0 bugs
Post by: toprobroy on 2023-03-22 10:37:41
Hi. I've just joined as I have a problem and I'm not sure if it's a bug?

I tried FOO about 7 months ago and I'm now running V 1.6.16. I'm running it on my laptop.
Originally I had it look for folders in 2 locations. One was on my C Drive and the other an external drive that I would switch on before running it and it found data from both sources.
Recently I decided to put all the music on the External Drive and moved the stuff off my C Drive as I wanted to free a bit of space.

It works fine but it's still looking for files from my C Drive. "Unable to open item for playback (Object not found):"

I only have the one set of folders configured and all the music is stored in Sub Folders and again that all works fine as I like random mode a lot and just listen whilst I work.

Why is it still looking for the C Drive as well though. That's what I can figure out. It just skips them when it's randomly looking around, but still looking at C. Can this be fixed, or is it a bug?

Thanks
Title: Re: foobar2000 v2.0 bugs
Post by: Porcus on 2023-03-22 10:39:34
Quote from: toprobroy on
Why is it still looking for the C Drive as well though.
Preferences -> Media Library, what folders do you have?
Title: Re: foobar2000 v2.0 bugs
Post by: toprobroy on 2023-03-22 10:41:14
E:/Music
Title: Re: foobar2000 v2.0 bugs
Post by: DotNoir on 2023-03-22 11:21:50
Quote from: toprobroy on
Hi. I've just joined as I have a problem and I'm not sure if it's a bug?

I tried FOO about 7 months ago and I'm now running V 1.6.16. I'm running it on my laptop.
Originally I had it look for folders in 2 locations. One was on my C Drive and the other an external drive that I would switch on before running it and it found data from both sources.
Recently I decided to put all the music on the External Drive and moved the stuff off my C Drive as I wanted to free a bit of space.

It works fine but it's still looking for files from my C Drive. "Unable to open item for playback (Object not found):"

I only have the one set of folders configured and all the music is stored in Sub Folders and again that all works fine as I like random mode a lot and just listen whilst I work.

Why is it still looking for the C Drive as well though. That's what I can figure out. It just skips them when it's randomly looking around, but still looking at C. Can this be fixed, or is it a bug?

Thanks


To me this sounds like you are talking about playlists and not media library. If you had configured an autoplaylist, it would update the playlist with only active files, but most apparently you have just put all your music from your media library as a regular playlist. Go to Edit->Remove dead items.

To have all your library in an autoplaylist go to Library->Album List and right click on your "All Music" and click "Create Autoplaylist" that way your playlist has all your songs from your library and it will update when your library updates.
Title: Re: foobar2000 v2.0 bugs
Post by: toprobroy on 2023-03-22 11:26:54
Ah. thanks for that. The Dead Items seems to have worked. If not I'll let you know.
I already that playlist set up as you said.

Thanks to all for the help. :))
Title: Re: foobar2000 v2.0 bugs
Post by: dore.moni on 2023-03-22 19:18:49
Quote from: Chibisteven on
Quote from: dore.moni on
Sorry for that. I asked you personally because you are professional developer and can diagnose this problem.
Porcus is incorrect. When volume in foobar is at max 0dB, foobar does not do internal processing and must output bits as they are in file. (if the intput of dac can accept it)

When  volume in foobar is at max 0dB and the file is 24bit it outputs bit-perfect as in file.
But if the file is 32bit integer foobar outputs it as 24bit simply by trunkating last 8bits. And the output is not bitperfect then.
So my question why it is so?

JRiver Media Center outputs 32bit integer as is at 32bit.


Porcus is correct, you're wrong.  foobar2000 converts everything to 32-bit floating point in 32-bit versions of the application where 64-bit versions (2.0 or newer) convert everything to 64-bit floating point.  foobar2000 does internal processing at all times regardless of the volume setting.  It's just at 0 dB that this processing is simply a lossless passthrough of sorts for most formats up to 24-bit integers (i.e. reversible) in 32-bit versions.  I know I'm repeating what has been said, but maybe you need to hear it from somebody else.

I understand that internal processing is 32-bit floating point or 64-bit floating point. But the input of my DAC is 32bit. So after processing foobar have to convert the data from 32-bit floating point to 32bit integer. Or to 24bit integer for DAC with 24bit inputs. There is even an option "Output data format" 16/24/32bit to choose.

So i have 3 questions:

1. Why foobar outputs data in 24bit, even if i choose Output data format as 32bit? (My DAC internal test indicates that it is 24bit)
2. If the volume is changed and not 0dB, foobar will process and convert the data from 32-bit floating point to 32bit integer or to 24bit integer?
3. How can i play in foobar 32bit files on a 32bit DAC bit-perfect? Other programs can do this a long ago.

Title: Re: foobar2000 v2.0 bugs
Post by: phunkydizco on 2023-03-23 06:33:01
I don't know if this has been mentioned before, but all custom album list views are gone, after update from 1.6.16 to beta 27.

Edit: I have to say, I have not updated directly. I installed beta 27 as portable version in a new folder and imported my saved default ui theme. Are the album list views part of themes at all?
Title: Re: foobar2000 v2.0 bugs
Post by: Porcus on 2023-03-23 09:56:48
Quote from: dore.moni on
3. How can i play in foobar 32bit files on a 32bit DAC bit-perfect? Other programs can do this a long ago.
Get yourself a version 0.8.3 (http://www.oldversion.com/windows/foobar2000-0-8-3) while you wait for 2.0 to be done?
Title: Re: foobar2000 v2.0 bugs
Post by: Air KEN on 2023-03-23 10:21:19
Monkey's Audio Decoder (foo_input_monkey) v10.07 2023-03-23 (https://www.foobar2000.org/components/view/foo_input_monkey)
foobar2000 v2.0 beta 27 32bit 64bit

error:
Failed to load DLL: foo_input_monkey.dll
Reason: Obsolete component; please remove.
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2023-03-23 10:28:50
Quote from: Air KEN on
Monkey's Audio Decoder (foo_input_monkey) v10.07 2023-03-23 (https://www.foobar2000.org/components/view/foo_input_monkey)
foobar2000 v2.0 beta 27 32bit 64bit

error:
Failed to load DLL: foo_input_monkey.dll
Reason: Obsolete component; please remove.
Component meant for the next foobar2000 v2.0 beta.
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2023-03-23 10:33:06
Quote from: dore.moni on
Hello.

Latest foobar2000 v1.6.16 and foobar2000 v2.0 still can't output 32bit files properly. It playback ok, status bar shows that it is 32bit, but my DAC internal test shows that it is 24bit instead of 32bit. When i test the same files with JRiver Media Center, DAC screen shows it as 32bit.

I use ASIO Output 2.1.2 and my DAC is RME ADI-2 Pro FS. The testing files i use are special wav files for testing bit-perfect playback of RME  ADI-2 Pro FS

Can someone else check if it is possible to output 32bit files properly?
It's been mentioned a few times but I'll say it again:

You need 64-bit foobar2000 v2.0 to do what you ask for.

You haven't explicitly said so but from your post I conclude that you're running the 32bit version, because that's the only way you can possibly use ASIO Output v2.1.2, rather than v2.2 with 64bit support.
The reason for this is that ALL components must be rebuilt to operate on 64bit floatingpoint data, I can't just add it without breaking all components, so I decided to introduce it along with another change that requires new builds of all components.
If you're running 64-bit foobar2000 with latest ASIO output and still getting bad behavior, please say so and I'll investigate.
Title: Re: foobar2000 v2.0 bugs
Post by: Porcus on 2023-03-23 10:47:35
OK, so 64-bit beta now does 64-bit signal path - "no matter what" output? (Presuming that you don't pass it to a Windows 32-bit audio mixer.)
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2023-03-23 14:08:36
Signal path is hardcoded. audio_sample type is defined to float32 for 32bit foobar2000, 64bit for foobar2000. It can't be changed at runtime.

In 64-bit foobar2000:
All decoders output float64 audio.
All DSPs take and produce float64 audio (what they use internally is another story).
All outputs take float64 audio (though all have to downconvert it as no real life device accepts float64 data).

If I changed these audio_sample definitions, it would produce a foobar2000 build that can't run any existing components, because audio_sample format is an essential part of all audio related component interfaces.
That is why I chose to change it for foobar2000 64-bit, since all components needed rebuilding anyway. I'm not entirely sure if it makes sense, but I'll never have a chance to change it again.
Title: Re: foobar2000 v2.0 bugs
Post by: dore.moni on 2023-03-23 15:08:46
I've tested latest beta foobar v2.0 x64 with ASIO driver 2.2 x64
At last foobar can output 32bit files correct and bit-perfect!!!

There is only one problem, there is no option to choose 32bit ASIO devices now. Only 64bit ASIO drivers supported.
On v1.6.16 there was support for both driver versions. And we have to wait for all plugins to be updated to x64. It will take a long time i think.

As far as i remember long ago there was foobar2000 0.8.3 with 64bit internal processing and 32bit ASIO output with Otachan plugin. And foobar2000 0.8.3 was a 32bit prorgam. It was fenomenal for that time! Thank you Peter.

Is it possible to implement 64bit internal processing for 32bit versions v1.6.x and v2.0 too? (at least just for volume control)
Title: Re: foobar2000 v2.0 bugs
Post by: wojak on 2023-03-23 15:28:27
Quote from: Peter on
Signal path is hardcoded. audio_sample type is defined to float32 for 32bit foobar2000, 64bit for foobar2000. It can't be changed at runtime.

In 64-bit foobar2000:
All decoders output float64 audio.
All DSPs take and produce float64 audio (what they use internally is another story).
All outputs take float64 audio (though all have to downconvert it as no real life device accepts float64 data).

If I changed these audio_sample definitions, it would produce a foobar2000 build that can't run any existing components, because audio_sample format is an essential part of all audio related component interfaces.
That is why I chose to change it for foobar2000 64-bit, since all components needed rebuilding anyway. I'm not entirely sure if it makes sense, but I'll never have a chance to change it again.

Hi @Peter,
I just tested foobar 2 beta 27 64bit and tried to convert 32 bit integer wavpack and flac to flac or wav or wavpack and I got either error or 32 bit float. So is it possible to convert to 32 integer, if so how, if not will it be in the future?
I tried flac 1.4.2, ffmpeg6.0 and wavpack 5.6. Errors or 32 floats.
DBpoweramp does it, foobar does not.
Title: Re: foobar2000 v2.0 bugs
Post by: Cannonaire on 2023-03-23 19:21:55
Quote from: Cannonaire on
I'm on Beta 27 now and it seems like there is a regression - the popping and lingering audio from the previous track upon manually changing tracks is back even though I have "Fast DSP reset when cycling tracks manually" off.
The issue persists in Beta 28.

**Edit**
The issue seems to go away when I turn off "Enable smooth seeking, pause and volume changes". This is a really nice feature though, and I would really prefer to leave it on.
Title: Re: foobar2000 v2.0 bugs
Post by: Cannonaire on 2023-03-23 21:04:34
I just verified that v2.0 beta 24 doesn't exhibit this behavior. I am using 32-bit Portable, if that matters.
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2023-03-24 12:20:37
Quote from: Cannonaire on
I just verified that v2.0 beta 24 doesn't exhibit this behavior. I am using 32-bit Portable, if that matters.
Thanks, looking into it, though I can't recreate it so far.

What about beta 25 and 26?
https://www.foobar2000.org/getfile/foobar2000_v2.0_beta_25.exe
https://www.foobar2000.org/getfile/foobar2000_v2.0_beta_26.exe

What exact audio device are you using?
ASIO etc perhaps?
Title: Re: foobar2000 v2.0 bugs
Post by: dore.moni on 2023-03-24 19:24:58
I've tested foobar v2.0 for bitperfect playback. RME ADI-2 Pro FS DAC has a special internal test for it, and it shows on display if the output of player is correct or not. All settings are default. Volume is 0dB. I checked all possible combinations with 3 different DACS i have
Maybe it will be useful for somebody.
Title: Re: foobar2000 v2.0 bugs
Post by: dore.moni on 2023-03-24 19:28:05
Default: Primay Sound Driver - not bit perfect at all !
Default: RME DAC - not bit perfect at all !
Default: RME DAC (exclusive) - Exclusive output overrides=off Use event=on in Advanced menu (Default foobar options) - very distorted audio!!!
Default: RME DAC (exclusive) - Exclusive output overrides=off Use event=off in Advanced menu - very distorted audio!!!
Default: RME DAC (exclusive) - Exclusive output overrides=on Use event=on in Advanced menu - very distorted audio!!!
Default: RME DAC (exclusive) - Exclusive output overrides=on Use event=off in Advanced menu  16bit output 16bit file - bit perfect 16bit
Default: RME DAC (exclusive) - Exclusive output overrides=on Use event=off in Advanced menu  16bit output 24bit file - bit perfect (but 16bit)
Default: RME DAC (exclusive) - Exclusive output overrides=on Use event=off in Advanced menu  24bit output 24bit file - bit perfect 24bit
Default: RME DAC (exclusive) - Exclusive output overrides=on Use event=off in Advanced menu  24bit output 32bit file - bit perfect (16bit, not 24bit)

Default: RME DAC (exclusive) - Exclusive output overrides=on Use event=off in Advanced menu  32bit output 32bit file - bit perfect 32bit
ASIO: RME DAC - bit perfect (with all samling rates and bitrates)

So there is only 2 good options:
1. ASIO output
2. WASAPI (exclusive) with special settings: 32bit output, Exclusive output overrides=on, Use event=off in Advanced menu


Peter, if it is impossible to fix all exclusive modes, maybe just set my settings in Advanced menu by default in foobar?
Title: Re: foobar2000 v2.0 bugs
Post by: Bogozo on 2023-03-24 20:22:28
Quote from: dore.moni on
fix all exclusive modes, maybe just set my settings in Advanced menu by default in foobar?
Default settings are default because they work for most cases. Bu not for all cases. And this is why these settings are allowed to be changed by user.
Title: Re: foobar2000 v2.0 bugs
Post by: dore.moni on 2023-03-24 21:18:41
Quote from: Bogozo on
Quote from: dore.moni on
fix all exclusive modes, maybe just set my settings in Advanced menu by default in foobar?
Default settings are default because they work for most cases. Bu not for all cases. And this is why these settings are allowed to be changed by user.

I mean not to use WASAPI exlcusive output by default, but to change it default settings in Advanced menu to working ones.

You write that the default WASAPI exlusive settings in foobar work for most cases. I've tested many souncards and DACs with them, and none of them are usable. The settings that i recommend are useable for most cases.

WASAPI (exclusive) settings: Exclusive output overrides=on, Use event=off in Advanced menu
Title: Re: foobar2000 v2.0 bugs
Post by: Melchior on 2023-03-25 00:14:53
Quote from: dore.moni on
Quote from: Bogozo on
Quote from: dore.moni on
fix all exclusive modes, maybe just set my settings in Advanced menu by default in foobar?
Default settings are default because they work for most cases. Bu not for all cases. And this is why these settings are allowed to be changed by user.

I mean not to use WASAPI exlcusive output by default, but to change it default settings in Advanced menu to working ones.

You write that the default WASAPI exlusive settings in foobar work for most cases. I've tested many souncards and DACs with them, and none of them are usable. The settings that i recommend are useable for most cases.

WASAPI (exclusive) settings: Exclusive output overrides=on, Use event=off in Advanced menu

hmm..
 I have Realtek UAD driver v6.0.9492.1 for said audio chipset..
- Realtek® ALC1220A 8-Channel High Definition Audio CODEC for my ASUS PRIME x570-PRO latest BIOS v4602.
for devices I always point to my Realtek (speakers) output and never use the exclusive mode... hmm...
never had any issues as far as I can tell...
but best of luck figuring this out,, or a bug fix..

but my point is, is your drivers up to date?
Title: Re: foobar2000 v2.0 bugs
Post by: dore.moni on 2023-03-25 04:25:13
I've showed with my tests, that the benefit of using WASAPI exclusive or ASIO is only if you want to have bi-perfect playback, i.e. ideal quality as it was recorded.

The default mode that everyone and you uses is all purpose for everething in Windows. But it is not bit-perfect. And of cource this default mode can't switch the sample rate of your souncard. By default windows configure every souncard samplerate at 48kHz and it is fixed for every program that you use. But if you play music files from foobar wich are mostly 44.1kHz, then windows will resamle it from 44.1kHz to default 48kHz, and so the sound will become even worse.

WASAPI exclusive mode in foobar can change this samplerate, and the sound didn't change and that's why it is perfect.
You can check it in settings of your soundcard during playback
Title: Re: foobar2000 v2.0 bugs
Post by: Cannonaire on 2023-03-25 04:59:56
I will test and possibly zip my portable install for you when I'm able. Thanks.
Title: Re: foobar2000 v2.0 bugs
Post by: Cannonaire on 2023-03-28 02:03:20
Quote from: Peter on
Quote from: Cannonaire on
I just verified that v2.0 beta 24 doesn't exhibit this behavior. I am using 32-bit Portable, if that matters.
Thanks, looking into it, though I can't recreate it so far.

What about beta 25 and 26?
https://www.foobar2000.org/getfile/foobar2000_v2.0_beta_25.exe
https://www.foobar2000.org/getfile/foobar2000_v2.0_beta_26.exe

What exact audio device are you using?
ASIO etc perhaps?

Sorry for the delay. Difficult days. Anyway...
Same settings were used in all cases. I verified that the behavior only happens with "Enable smooth seeking, pause and volume changes" on (50ms for all except 0ms for fade in on manual track change) in conjunction with certain DSPs (Stereo Convolver and/or MathAudio Headphone EQ will each cause the bug). Audio devices were a Schiit Modius in exclusive mode 24-bit and also my onboard realtek device non-exclusive. Both devices exhibited the behavior. If you want, I can 7z archive my foobar portable install and send it to you with sample tracks which tend to make the bug very audible.

*Edit*
Just did some more tests. Checked and made sure some more settings were the same.
Behavior is there in 24, 25, 26, 27, and 28.
I guess that means I need to test with older versions.
Title: Re: foobar2000 v2.0 bugs
Post by: Cannonaire on 2023-03-28 02:17:00
More testing. The bug is present even in beta 20. Same rules apply - turning off "Enable smooth seeking, pause and volume changes" will make it stop, or removing the identified DSPs.
One more test for now. The bug is there even in v1.6.10. I guess it's not a new bug, but a bad interaction between the identified DSPs and smooth seeking.

*Final edit*
I believe my confusion came from the audio devices with "DEFAULT" at the beginning automatically disabling smooth seeking, which prevented the bug in some cases.

Thank you.

*Even more final edit*
On a whim, I decided to also test with 0ms for both fade in and fade out on manual track change, and also 50ms for both. The bug persists in both cases.
Title: Re: foobar2000 v2.0 bugs
Post by: Cannonaire on 2023-03-28 04:19:20
I tried a fresh installation, and it didn't have the bug until I also installed and added foo_dsp_stereoconv and Resampler (SRC).

To reproduce the bug:

1. Install foobar2000 beta 28 portable (or really any version even as far back as 1.6.10. I've only tried with portable.)

2. Install these components
Stereo Convolver (linked) (MathAudio Headphone EQ seems to work as well, but I haven't tested it as thoroughly)
https://foobar.hyv.fi/2.0/?view=foo_dsp_stereoconv
Resampler SRC:
https://www.foobar2000.org/components/view/foo_dsp_src_resampler

3. Add the two DSPs in order (screenshot included)
Stereo Convolver
Resampler (SRC)

4. Configure Resampler (SRC) with target "Upsample 4x" and Mode "Best Sinc Interpolator". Stereo Convolver can use the default settings and still reproduce the bug, though I normally use different impulses.
*note - My test tracks were both 44100Hz 16-bit and very loud (almost reaching -0dB)

5. Turn On "Enable smooth seeking, pause and volume changes" (I use 50ms for all except fade in on manual track change, but it doesn't seem to matter)

6. Manually change between tracks.

The bug doesn't happen on every manual track change, but it is fairly frequent, and it occurs much more often - almost every time - when more DSPs are added. I realize this is pretty specific and these components are not yours (Peter), but it is a real setup I use, and it still only causes the bug when smooth seeking is enabled. Thank you for reading.
Title: Re: foobar2000 v2.0 bugs
Post by: dore.moni on 2023-03-28 04:28:14
Converter in foobar v2.0 have 3 issues:

1. I have playlist with 32bit int files in wav or flac. If i want to export it to 32bit int wav without bitdepth change, just format conversion, there is no such option. Only 32bit, but it's floating. So the bits in files will be changed. Maybe it's wise to add such an option to choose 32bit or 32bit-float?
2. Even if i press convert, converter doesn't remind of lossy bits operation. I checked foobar v1.6.16, it does remind
3. After conversion there is annoying window 'Converter output'. And there is no option to disable it
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2023-03-28 12:54:53
Quote from: Cannonaire on
I tried a fresh installation, and it didn't have the bug until I also installed and added foo_dsp_stereoconv and Resampler (SRC).

(...)
Thanks for the details, I'm investigating mitigation techniques for this.

Possible workarounds:
Please report if either of the above helps.
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2023-03-28 12:56:18
Quote from: dore.moni on
Peter, if it is impossible to fix all exclusive modes, maybe just set my settings in Advanced menu by default in foobar?
Is the device name exactly spelled "RME DAC" ?
I'll add it to internal workarounds list so you no longer need to change advanced settings.
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2023-03-28 13:50:45
Quote from: dore.moni on
Converter in foobar v2.0 have 3 issues:

1. I have playlist with 32bit int files in wav or flac. If i want to export it to 32bit int wav without bitdepth change, just format conversion, there is no such option. Only 32bit, but it's floating. So the bits in files will be changed. Maybe it's wise to add such an option to choose 32bit or 32bit-float?
2. Even if i press convert, converter doesn't remind of lossy bits operation. I checked foobar v1.6.16, it does remind
3. After conversion there is annoying window 'Converter output'. And there is no option to disable it
1 + 2, looks like an oversight, fixing. Thanks for reporting.
3. Checkbox for this is shown in conversion progress dialog, I guess it's hard to see or click if conversion finishes near instantly.
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2023-03-28 14:11:33
PS
I'm still waiting for someone to enlighten me about legitimate purposes of 32bit integer audio. I can't think of any.
Title: Re: foobar2000 v2.0 bugs
Post by: Cannonaire on 2023-03-29 07:15:54
Quote from: Peter on
Possible workarounds:
  • Increase output buffer length - smooth mode starts playing after 1/4th of the buffer is ready, that would be 250ms with defaults; if more audio audio doesn't arrive in time after that, glitch happens. Try 5000ms output buffer instead of the default 1000ms please.
  • Change automatic resampling behavior - by default, SSRC is used to resample played audio to match Windows Mixer sample rate. SSRC which isn't very CPU efficient, you can set Advanced Preferences / Tools / Automatic Resampling to "Resampler (RetroArch)", without the quotation marks, or to any other name of DSP which you wish to be used for implicit resampling.
Please report if either of the above helps.
They didn't help. Buffer length didn't seem to affect it at all.
Regarding the resampler I've been using - I've been upsampling to 176400Hz for final output because I recall seeing graphs which showed the DAC handled it more cleanly, however I can't claim that for certain because I can't find said graphs anymore and I don't think I could tell a difference either way. I think for now I'm just going to remove that resampler from the DSP chain and listen at 44100Hz. It's also important to note that this DAC was in exclusive mode, so I don't think the automatic resampler would have been activated during my tests except on the other audio device. Oddly, I use the same resampler earlier in the chain and it never causes a problem unless it comes after the Stereo Convolver or other offending component.
Title: Re: foobar2000 v2.0 bugs
Post by: Porcus on 2023-03-29 10:52:37
Not sure if this is bug of feature or neither, but anyway:

* Fair enough: If I make changes to a file outside fb2k - keeping time stamp - fb2k does not "see" the change unless I instruct to reload info.
* But: If I even play the file, fb2k does not update. Any reason not to? Obviously it has to read the file (and the files in question are FLAC, with metadata at the beginning.)
Title: Re: foobar2000 v2.0 bugs
Post by: wojak on 2023-03-29 14:08:04
Quote from: Peter on
PS
I'm still waiting for someone to enlighten me about legitimate purposes of 32bit integer audio. I can't think of any.

There are 32 bit int audio files (maybe not many but still there are) so some people want to use them. If we can play and convert 16bit and 24 bit files properly why make it impossible to play and convert 32 bit int files properly? It was "technically" impossible in 32 bit FB but in 64 bit FB it should be normal - out-of-the-box thing. To be honest I thought that this is the main reason to implement 64 bit FB. I do not need to know how many people and why want to use it. If it will be implemented I surely will use it. Someone said earlier that his DAC can "see" 32bit int file so why not to let him use this feature (and again: I do not need to know why he needs it or does it make any audible difference, it just is possible and FB2.0 64 bit can do it technically, so why not?) If there is any reason to deliberately block such a feature why not also block 24 bit or 16 bit? Or anything else? I do not want to offend you (I am really grateful for your hard work on this program) and I do not know anything about programming - maybe it is very hard to implement such a feature - if so, probably most users will understand why it is not implemented but if it is just a matter of "justification" of someones need to use 32 bit int then I still hope that one day you will implement, even without legitimate purpose.  Especcially that another program of yours can do it already. Once again - big thankyou for your program.
Title: Re: foobar2000 v2.0 bugs
Post by: Porcus on 2023-03-29 14:12:09
Quote from: wojak on
If there is any reason to deliberately block such a feature
I don't think "looks like an oversight, fixing" looks like it was deliberate.

Apart from that, I'd say you are right.
Stupid: 32-bit integer
Bad: Violating the "lossless is lossless" maxime.

Others are providing "Stupid", fb2k need not behave "Bad". And it looks like it will be fixed.
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2023-03-29 15:04:14
Regarding Converter vs 32bit fixed-point,
I obviously meant to do it properly, but I seem to have lost my train of thought there sometime last year, took warnings off but never implemented & validated encoding. Fixing this properly now.

Quote from: wojak on
There are 32 bit int audio files (maybe not many but still there are) so some people want to use them. If we can play and convert 16bit and 24 bit files properly why make it impossible to play and convert 32 bit int files properly? It was "technically" impossible in 32 bit FB but in 64 bit FB it should be normal - out-of-the-box thing. To be honest I thought that this is the main reason to implement 64 bit FB. I do not need to know how many people and why want to use it. If it will be implemented I surely will use it. Someone said earlier that his DAC can "see" 32bit int file so why not to let him use this feature (and again: I do not need to know why he needs it or does it make any audible difference, it just is possible and FB2.0 64 bit can do it technically, so why not?) If there is any reason to deliberately block such a feature why not also block 24 bit or 16 bit? Or anything else? I do not want to offend you (I am really grateful for your hard work on this program) and I do not know anything about programming - maybe it is very hard to implement such a feature - if so, probably most users will understand why it is not implemented but if it is just a matter of "justification" of someones need to use 32 bit int then I still hope that one day you will implement, even without legitimate purpose.  Especcially that another program of yours can do it already. Once again - big thankyou for your program.
32bit fixedpoint audio only makes sense in DAC design - handling unpadded 24bit data is generally more complex than handling the same data padded to 32bit. However, you're never actually going to hear or measure differences in last 8 bits in analog signal coming out of your DAC.

So, playback of 32bit fixedpoint was working well enough in past foobar2000 versions already - as you can never possibly hear or measure the difference in analog output.

That said, I'm not actively blocking anything, current behavior of Converter is an oversight that is being corrected.
Title: Re: foobar2000 v2.0 bugs
Post by: 0x00000ed on 2023-03-29 16:21:09
Just noticed that the beta versions do not save the current player state if you restart (or shutdown) the computer without turning off the player itself. Instead of loading last player state the last saved one is started. Checked with blank profile on beta 28. In stable version 1.6.16 with blank profile everything works fine. Only player and all the standard components are installed. Win10 x64 21H1.

updated
I have tested all previous versions, the latest working one is beta 24.
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2023-03-29 20:53:07
Quote from: 0x00000ed on
Just noticed that the beta versions do not save the current player state if you restart (or shutdown) the computer without turning off the player itself. Instead of loading last player state the last saved one is started. Checked with blank profile on beta 28. In stable version 1.6.16 with blank profile everything works fine. Only player and all the standard components are installed. Win10 x64 21H1.

updated
I have tested all previous versions, the latest working one is beta 24.
Good find, fixed for the next build, thanks for reporting.
Title: Re: foobar2000 v2.0 bugs
Post by: dore.moni on 2023-03-30 04:02:48
Quote from: Peter on
Quote from: dore.moni on
Peter, if it is impossible to fix all exclusive modes, maybe just set my settings in Advanced menu by default in foobar?
Is the device name exactly spelled "RME DAC" ?
I'll add it to internal workarounds list so you no longer need to change advanced settings.

1. The device name is RME ADI-2 Pro FS, but in foobar its name is different for different RME outputs.

Please see my attachment. By the way i will suggest to rename all exlusive outputs from 'Default: Souncard name [exclusive]' to 'Exclusive: Souncard name'. Because WASAPI exclusive output is not a default in Windows and will confuse some users what to choose. And maybe it's possible to display group of the same cards 'RME ADI-2 Pro' first and the name of its output after, so that they will be in correct alphabetical order. I mean like this:

Default: RME ADI-2 Pro: AES
Default: RME ADI-2 Pro: Analog (1+2)
Default: RME ADI-2 Pro: Phones

Exclusive: RME ADI-2 Pro: AES
Exclusive: RME ADI-2 Pro: Analog (1+2)
Exclusive: RME ADI-2 Pro: Phones



2. I have many other different players and DACs, and almost all of them works correct for WASAPI exclusive output with the settings i found.
Exclusive output overrides=on Use event=off in Advanced menu
That's why i thought maybe this settings will be optimal as default for everyone (if one prefer to use WASAPI exclusive output).


3. My third question is why 3 other combination of exclusive output settings don't work?
RME drivers are known to be one of the best and reference among professional DACs and souncards.

Title: Re: foobar2000 v2.0 bugs
Post by: dore.moni on 2023-03-30 04:17:39
Quote from: Peter on
Quote from: dore.moni on
Converter in foobar v2.0 have 3 issues:

1. I have playlist with 32bit int files in wav or flac. If i want to export it to 32bit int wav without bitdepth change, just format conversion, there is no such option. Only 32bit, but it's floating. So the bits in files will be changed. Maybe it's wise to add such an option to choose 32bit or 32bit-float?
2. Even if i press convert, converter doesn't remind of lossy bits operation. I checked foobar v1.6.16, it does remind
3. After conversion there is annoying window 'Converter output'. And there is no option to disable it
1 + 2, looks like an oversight, fixing. Thanks for reporting.
3. Checkbox for this is shown in conversion progress dialog, I guess it's hard to see or click if conversion finishes near instantly.


3. It was hard to find at first. Maybe a good idea to move this checkbox option to the other 'Settings >When done'? Like the same setting 'Show full status report'
Title: Re: foobar2000 v2.0 bugs
Post by: dore.moni on 2023-03-30 05:02:00
Quote from: Peter on
PS
I'm still waiting for someone to enlighten me about legitimate purposes of 32bit integer audio. I can't think of any.

The difference in 24bit files and 32bit is unnoticeable for human hearing. But only if there is no processing done with bits. I mean No volume change and resampling in foobar, no digital volume change in DAC.

But if for example you play 24bit file in foobar and change volume -12 or -24 dB, foobar will convert 32bit floating output to 24bit int without dithring, and there will remain only 20bits of data, 4 MSB bits will be lost. The DAC has its own processor and if volume is changed in DAC some information will be lost further.

If foobar will convert 64bit floating output to 32bit int and DAC has 32bit input, then all original 24bits will be preserved and DAC will receive them all, even if foobar change volume down to -48dB (wich is -8bits). Then DAC will process volume control in 42bits internaly, then it will make conversion to final 32bits with special dithering. After that DAC chip will do 16x resampling with full 24bits (not 20bits like in first examle). RME claims that in such a way their digital volume control is one of the best and is even better than analog volume control


Most modern good quality DACs have 32bit input and 32bit D/A chip.

P.S. I've found a link with another good comment about this 32 bit int problem in foobar:
https://hydrogenaud.io/index.php/topic,121171.msg999315.html#msg999315
Title: Re: foobar2000 v2.0 bugs
Post by: dore.moni on 2023-03-30 07:42:36
This is RME manual (see attachement pages 89-90)

34.20 Digital Volume Control

The ADI-2 Pro deliberately avoids an analog level adjustment by means of a potentiometer. Its
digital version surpasses an analog one in practically every conceivable point. Typical
disadvantages of setting with potentiometers:
• Synchronicity errors lead to panoramic shifts and significant volume deviations left / right, in
particular near the end points of the adjustment range.
• In the middle setting range, there is an increased crosstalk and changes in the frequency
response. Changes in the frequency response also occur at the end regions of the
adjustment path.
• The setting range for optimum volume adjustment is often too small, or at the lower or
upper end of the potentiometer's adjustment range.
• Non-reproducible settings (except 0 and 11).
• Higher THD/THD+N. A point well known to measurement technicians. As soon as an
analog potentiometer is in the signal path, the unstable contact between wiper and resistive
track causes noise, which contains both THD (distortion) and N (noise), even in the
stationary state. Thus the -110 dB of a DAC quickly gets reduced to for example -80 or -70
dB.

Special volume ICs, which activate different resistance values by means of numerous electronic
switches, avoid some of the above mentioned points. Unfortunately, even the best of these ICs
do not achieve either THD or dynamics of the DACs used in the ADI-2 Pro, thus would affect its
analog output signal.

However, none of this is an issue with RME's digital volume control!
In fact an analog volume control has a (theoretical) advantage in only one point, namely the
maximum signal to noise ratio at a higher level reduction. In reality, current circuitry overturns
the theory, and the SNR at the output of such a device is no better than that of a digitally controlled
one. This is even more true the better the DA converter works and the less noise it has -
just like the ADI-2 Pro, which provides the maximum noise ratio over a wide level range of 20
dB, thanks to its four reference levels realized in the analog domain.

The most often cited issue of a digital volume control is an alleged loss of resolution at higher
attenuation. An example: 117 dB dynamic roughly equals 19 bit resolution. A volume attenuation
of 48 dB (8 bit) leaves 11 bit of resolution. Such a simple, but important details omitting
argumentation, usually ends with: the music must sound distorted in quieter parts, and the signal
to noise ratio is down to a useless 69 dB.

The former is simply wrong, the latter irrelevant in practice. Indeed there is a reduced signal to
noise ratio, but it doesn't matter, as the noise was not audible before (below the hearing threshold),
and is still not audible after lowering the level. And the reduced SNR also applies to
devices with potentiometers, since the potentiometer is never placed at the output, but in the
middle of the circuit, followed by further electronics which also add some basic noise.
The quality of the ADI-2 Pro's digital volume control is best shown by measurements. Hard
times coming up for convinced supporters of the analog control, because here it is very clear
that the disadvantages of a digital volume adjustment, such as roughness and distortions at
higher attenuation, simply do not exist - at least with RME.

The following measurement shows a digital full-scale sine of 1 kHz, 16 bits without dither, which
is reduced in level by 40 dB. Also shown are a full-scale sine of 1 kHz with 24 bit, at 60 dB and
96.3 dB level attenuation, which is the lowest volume setting the ADI-2 Pro offers.
A high-resolution FFT like HpW Works makes it possible to disassemble the signal into
individual frequencies, and to identify unwanted components down to a level of -190 dBFS. The
measurement shows that the undithered 16 bit signal does not produce any distortion or other
tones above -170 dBFS. So at a volume setting of -40 dB the measurable THD is -130 dB. At 24
bit a volume setting of -60 dB also achieves -130 dB without distortion. And at a volume setting
of -96.3 dB there are still -93 dB THD measurable.

These results clearly show that distortion products of the digital volume control are not drowned
by the DAC's noise, but are not generated at all. It works perfectly even with an undithered 16
bit signal, no detectable distortion products are produced.

If the volume control is measured at the analog output, the demonstrable THD is reduced to
around -100 dB at a volume setting of -60 dB, by the self-noise of the DAC (SNR 117 dB RMS
unweighted). In the above measurement that would be seen as straight noise floor at -160
dBFS. The digital volume control of the ADI-2 Pro therefore works much more precisely and
cleaner than required for current top-level DACs.

In summary:
RME's digital volume control in 42 bit TotalMix technology avoids all the disadvantages of
analog level control via pots, is easy to use, offers reproducible settings, and the highest sound
quality.
Title: Re: foobar2000 v2.0 bugs
Post by: Erich_2 on 2023-03-30 16:18:53
ReFacets Folder = $directory(%path%)
doesn’t work anymore, shows pointless or a mix of folders and albums!  :(

In Facets I used Folder = $directory(%path%)
I use two ore sometimes three times „Folder“ and then Album and so on...
The first 2 (or even 3) columns show perfectly my folder structure:

What’s going on with ReFacets?
And yes, simple Genre - Artist - Album - etc. works.

I went back to Facets.

Erich

Title: Re: foobar2000 v2.0 bugs
Post by: iangk on 2023-03-30 16:58:31
Beta 29 x64, portable.
Upon opening FB2K window is not maximized. If I maximize the window, exit, restart, the window is not maximized again. Does not happen in Beta 27 (haven't tested Beta 28).
Title: Re: foobar2000 v2.0 bugs
Post by: Pradesh on 2023-03-30 17:28:36
Probably a false alarm, but Trojan:Win32/Bearfoos.A!ml was detected in Beta 29 64bits by Defender.
Title: Re: foobar2000 v2.0 bugs
Post by: sveakul on 2023-03-30 19:01:31
Quote from: iangk on
Beta 29 x64, portable.
Upon opening FB2K window is not maximized. If I maximize the window, exit, restart, the window is not maximized again. Does not happen in Beta 27 (haven't tested Beta 28).
This is also the case here, please fix.  Does not happen in Beta 28.
Title: Re: foobar2000 v2.0 bugs
Post by: Pradesh on 2023-03-30 19:29:55
Quote from: Pradesh on
Probably a false alarm, but Trojan:Win32/Bearfoos.A!ml was detected in Beta 29 64bits by Defender.
2 hours later it is no longer :)
Title: Re: foobar2000 v2.0 bugs
Post by: Chibisteven on 2023-03-31 02:41:31
New bug in Beta 29: foobar2000 no longer remembers if it's main window was maximized.

Easy to reproduce:
1. Run foobar2000 and maximize window.
2. Close foobar2000.
3. Run foobar2000 again.
Title: Re: foobar2000 v2.0 bugs
Post by: Melchior on 2023-03-31 02:44:39
Quote from: Chibisteven on
New bug in Beta 29: foobar2000 no longer remembers if it's main window was maximized.

Easy to reproduce:
1. Run foobar2000 and maximize window.
2. Close foobar2000.
3. Run foobar2000 again.

yup, same with me on Windows 11 Pro.
using Nvidia display driver v431.41
and a EVGA/Nvidia RTX 3070 Ti 8GB gfx card.
Title: Re: foobar2000 v2.0 bugs
Post by: Fabcore on 2023-03-31 03:57:32
F2K v2.0 beta 29
Two playlist annoyances:
-it does still have those abrupt jumps to anywhere when changing something that can alter the name of the group.
-it's very slow switch from tab to tab that it has a lot of content (more than 500 items and up), and the situation gets worse the more number of items.
Title: Re: foobar2000 v2.0 bugs
Post by: 0x00000ed on 2023-03-31 06:06:24
Quote from: iangk on
Beta 29 x64, portable.
Upon opening FB2K window is not maximized. If I maximize the window, exit, restart, the window is not maximized again. Does not happen in Beta 27 (haven't tested Beta 28).
29 too.

Quote from: Fabcore on
F2K v2.0 beta 29
Two playlist annoyances:
-it does still have those abrupt jumps to anywhere when changing something that can alter the name of the group.
-it's very slow switch from tab to tab that it has a lot of content (more than 500 items and up), and the situation gets worse the more number of items.
Tested on 100k tracks in multiple tabs, everything works for me.
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2023-03-31 11:47:48
Thanks for the bug reports. Making a new build addressing the maximized window regression.

Quote from: Fabcore on
F2K v2.0 beta 29
Two playlist annoyances:
-it does still have those abrupt jumps to anywhere when changing something that can alter the name of the group.
-it's very slow switch from tab to tab that it has a lot of content (more than 500 items and up), and the situation gets worse the more number of items.
More details please.
Components installed?
Album covers in playlist enabled?
Columns used in playlist? Grouping pattern?
Does getting rid of grouping or covers improve?
Title: Re: foobar2000 v2.0 bugs
Post by: Andy Foo on 2023-03-31 13:00:21
Maybe this is reported before, but I did not find it:

In Foobar2000 V2.0 beta 30 64 bits version: On a large library when right clicking in the Album List (Folder view) on a large folder or the root folder Foobar freezes (gets unresponsive) for several minutes before showing the context menu,

In the  V2 beta 30 32 bits version the context menu appears much quicker, but is still slower than in Foobar 1.6.

I noticed this problem since (around) V2.0 beta 26.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-03-31 14:35:19
Do you have a corrupted Media Library?
Title: Re: foobar2000 v2.0 bugs
Post by: MaFred on 2023-03-31 16:50:46
When trying to download Beta30.exe, "Trojan:Win32/Wacatac.B!ml" is detected!?
Title: Re: foobar2000 v2.0 bugs
Post by: Andy Foo on 2023-03-31 17:24:29
Quote from: grimes on
Do you have a corrupted Media Library?

Thanks for the suggestion.
I will try to remove and rebuild the library in the 64 bits version. In all other versions of Foobar (1.6 and v2 32 bits) it works fine with the same source files.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-03-31 17:34:10
Title: Re: foobar2000 v2.0 bugs
Post by: Andy Foo on 2023-03-31 17:53:16
Quote from: grimes on
  • Save metadb.sqlite
  • remove metadb.sqlite
  • Remove music folders in Preferences|Media Library
  • Add music folders

Thanks. Will do and let you know.
Title: Re: foobar2000 v2.0 bugs
Post by: Andy Foo on 2023-03-31 18:44:52
Quote from: Andy Foo on
Quote from: grimes on
  • Save metadb.sqlite
  • remove metadb.sqlite
  • Remove music folders in Preferences|Media Library
  • Add music folders

Thanks. Will do and let you know.

- deleted the metadb.sqlite file
- removed the music folders in Preferences|Media libray
- Added them again
- Pressed Apply and waited until Foobar was completely ready with scanning the library

Still the same problem. Right clicking in the Album list on the root folder (large library around 9000 albums) freezes V2 64 bits for several minutes (none responding) before showing the context menu.
I have a portable install of all Foobars (V2 64 and 32bit and V1.6) on a NUC with internal M.2 Samsung SSD. As said, no problem with the V2 32 bit version and no problem with the 1.6 version. All use the same source folders.

It almost seems if the 64 bit version is doing an unindexed search in the database for all the properties before showing the context menu. If I right click in the Album List on a folder with fewer albums the context menu appears quicker. It seems directly related to the number of albums/tracks. As said; V2 32 bits and V1.6 work fine.
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2023-03-31 18:52:26
Maybe a component is to blame? Third parties can be responsible for showing/hiding/greying out their own menu items depending on the properties of selection. Can you try another 64bit install without components?
Title: Re: foobar2000 v2.0 bugs
Post by: Andy Foo on 2023-03-31 19:15:21
Quote from: marc2k3 on
Maybe a component is to blame? Third parties can be responsible for showing/hiding/greying out their own menu items depending on the properties of selection. Can you try another 64bit install without components?

Thanks for the response. I will try your suggestion.
As I understand now this is not a common problem or bug in the V2 beta version, but more an individual problem on my side.

I must say I have exactly the same components installed in the 32 bits and 64 bits version, but I will remove them from the 64 bit version and see what happens.
Title: Re: foobar2000 v2.0 bugs
Post by: Andy Foo on 2023-03-31 19:22:38
Quote from: Andy Foo on
Quote from: marc2k3 on
Maybe a component is to blame? Third parties can be responsible for showing/hiding/greying out their own menu items depending on the properties of selection. Can you try another 64bit install without components?

Thanks for the response. I will try your suggestion.
As I understand now this is not a common problem or bug in the V2 beta version, but more an individual problem on my side.

I must say I have exactly the same components installed in the 32 bits and 64 bits version, but I will remove them from the 64 bit version and see what happens.

I removed all the components from the 64 bit version and indeed the problem is gone! Thank you. Now I am going to put them back one by one to see which one is the culprit. Thanks for your suggestion!
Title: Re: foobar2000 v2.0 bugs
Post by: Andy Foo on 2023-03-31 19:32:38
Quote from: MaFred on
When trying to download Beta30.exe, "Trojan:Win32/Wacatac.B!ml" is detected!?
I can concur. If I download the 32 bits version with Edge I always had to choose 'run anyway' because of a smartscreen warning, but now it won't download at all ('Can not download. Virus detected'). This is coming from the standard Windows Defender. No other anti virus programs installed.

On the 64 bits version the download is fine.
Title: Re: foobar2000 v2.0 bugs
Post by: darkalex on 2023-04-01 00:19:12
Quote from: MaFred on
When trying to download Beta30.exe, "Trojan:Win32/Wacatac.B!ml" is detected!?

Now this is a newer Trojan:Win32/Wacatac.B!ml virus compared to the  Trojan:Win32/Bearfoos.A!ml in Beta 29

What the hell is going on here? I mean sure defender can make one false alarm, but that's two different trojans in 2 setups and unless something drastic was done to the program, it is practically impossible to detect a whole new trojan, unless it's actually there...

Could the dev please take a look at the malware protection on their build PC? and maybe add MD5 checksums, Virus Total with the download links now?

I'm not downloading this version or running the newer Beta 29/30 now, I'm backing up my settings, scan them to ensure 0 malware, and downgrading the program until this situation is responded properly and solved.

2 different trojans in 2 consecutive builds with minor changes... something's off...

Please look this up dev, thank you very much
Title: Re: foobar2000 v2.0 bugs
Post by: Fabcore on 2023-04-01 03:09:41
Quote from: Peter on
Thanks for the bug reports. Making a new build addressing the maximized window regression.

Quote from: Fabcore on
F2K v2.0 beta 29
Two playlist annoyances:
-it does still have those abrupt jumps to anywhere when changing something that can alter the name of the group.
-it's very slow switch from tab to tab that it has a lot of content (more than 500 items and up), and the situation gets worse the more number of items.
More details please.
Components installed?
Album covers in playlist enabled?
Columns used in playlist? Grouping pattern?
Does getting rid of grouping or covers improve?
yes, it needs to be updated. However i never had a problem with it.
edit: wrong response cause wrong thread.

1. The abrupt changes is mostly triggered when there's a lot of groups in a scroll-able playlist
X

2. For the bad performance on playlist tabs, just simply switch from one to another playlist tab in which at least one of them has more than x00 elements, but you can test it for  better proof with more than 3000 elements with or without the "cover" columns in it.
It's like some recalculations is done behind the scenes every time the tab is showed.
I had the old stable version too (v1.6.14) with the (almost) same columns and tabs with the (again almost) same number of items in it, and i hadn't those issues.
on the changelog, in the beta 20 there's a mention that it was fixed but is partial
Playlist group layout optimizations reverted (no more scrollbar jumping around stupidly), unless in the new low memory mode.
and
Fixed playlist layout glitch causing unwanted scrolling during certain events. on beta 27
that's a partial solution, i understand, it's a beta yet.
For people that use this program, have you seen this bug?

Regards.
Title: Re: foobar2000 v2.0 bugs
Post by: darkalex on 2023-04-01 07:23:55
I got the Beta installer removed from Microsoft Defender's malware definitions!

Here's their response:

User Opinion: Incorrect detection

Analyst comments:

At this time, the submitted files do not meet our criteria for malware or potentially unwanted applications. The detection has been removed. Please follow the steps below to clear cached detections and obtain the latest malware definitions.

1. Open command prompt as administrator and change directory to c:\Program Files\Windows Defender
2. Run “MpCmdRun.exe -removedefinitions -dynamicsignatures”
3. Run "MpCmdRun.exe -SignatureUpdate"

Alternatively, the latest definition is available for download here: https://docs.microsoft.com/microsoft-365/security/defender-endpoint/manage-updates-baselines-microsoft-defender-antivirus

Thank you for contacting Microsoft.

 ;)
Title: Re: foobar2000 v2.0 bugs
Post by: MaFred on 2023-04-01 11:48:21
After updating the malware definitions for Defender, no Trojan is detected anymore!
Title: Re: foobar2000 v2.0 bugs
Post by: Bogozo on 2023-04-01 18:30:28
Beta 29 always starts not in fullscreen mode. No such problem with beta 28. Windows 7 32 bit.Fixed in beta 30.
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2023-04-01 21:47:31
Here's a bug with the File operations dialog in dark mode. Switching between Rename and Move turns one of the checkbox labels black.

(https://i.imgur.com/0Pe9wfq.gif)
Title: Re: foobar2000 v2.0 bugs
Post by: dore.moni on 2023-04-02 06:50:02
File Integrity Verifier 1.4.2 and integrted version in foobar 2.0 has a bug:
When using "Verify album with acurate rip" shows that disc is not acurate if the whole disc or some of the tracks are HDCD and foo_hdcd.dll is installed
If i remove foo_hdcd.dll, then "Verify album with acurate rip" shows that disc is acurate.
The same problem is when CD is tagged as Pre-emphasis and foo_deemph.dll 0.1.1 is installed, "Verify album with acurate rip" shows that disc is not acurate

So i think File Integrity Verifier must ignore all postprocessing decoders, like foo_hdcd.dll, foo_deemph.dll and others


@Peter, why there is no option in foobar to temporary disable installed postprocessors, like the checkbox options in 'Playback > Decoding' menu?
Title: Re: foobar2000 v2.0 bugs
Post by: darkalex on 2023-04-02 23:52:31
Version 2, Beta 30 x64

Bug in Converter, showing the output preferences for FLAC/PCM whenever using a lossy encoder.

Image attached from Converter dialog, showing "Output 24 bit" but the output is AAC. I checked my preset settings too, they're normal.

Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2023-04-03 14:36:55
Quote from: dore.moni on
File Integrity Verifier 1.4.2 and integrted version in foobar 2.0 has a bug:
When using "Verify album with acurate rip" shows that disc is not acurate if the whole disc or some of the tracks are HDCD and foo_hdcd.dll is installed
If i remove foo_hdcd.dll, then "Verify album with acurate rip" shows that disc is acurate.
The same problem is when CD is tagged as Pre-emphasis and foo_deemph.dll 0.1.1 is installed, "Verify album with acurate rip" shows that disc is not acurate

So i think File Integrity Verifier must ignore all postprocessing decoders, like foo_hdcd.dll, foo_deemph.dll and others


@Peter, why there is no option in foobar to temporary disable installed postprocessors, like the checkbox options in 'Playback > Decoding' menu?
Bug acknowledged and fixed for the next update, normal Verifier suppresses postprocessing, I forgot to do this for AccurateRip checking.
I don't think a global switch for it is feasible, it's something negotiated between decoders and frontends.
Though individual postprocessing components could implement their own switches.
Quote from: darkalex on
Version 2, Beta 30 x64

Bug in Converter, showing the output preferences for FLAC/PCM whenever using a lossy encoder.

Image attached from Converter dialog, showing "Output 24 bit" but the output is AAC. I checked my preset settings too, they're normal.
Acknowledged, thanks for reporting.
Quote from: marc2k3 on
Here's a bug with the File operations dialog in dark mode. Switching between Rename and Move turns one of the checkbox labels black.
Acknowledged, thanks for reporting.
Title: Re: foobar2000 v2.0 bugs
Post by: elcosomalo on 2023-04-03 17:01:06
Clickable rating stars: NOT CLICKEABLE and not appearing by default in default user interface.

Title: Re: foobar2000 v2.0 bugs
Post by: phunkydizco on 2023-04-04 07:31:20
In beta 30 (32-bit) the maximized state of the picture viewer window is not saved.
Title: Re: foobar2000 v2.0 bugs
Post by: dore.moni on 2023-04-04 09:49:09
Quote from: Peter on
Quote from: dore.moni on

@Peter, why there is no option in foobar to temporary disable installed postprocessors, like the checkbox options in 'Playback > Decoding' menu?
I don't think a global switch for it is feasible, it's something negotiated between decoders and frontends.
Though individual postprocessing components could implement their own switches.


Some discs play incorrect with HDCD decoder, some with De-emphasis. And to check it or playback without errors i have to completely uninstall this foobar components. And then install them again for normal discs. It's unconvinient.

1. I will suggest to add checkboxes in 'Preferences: Installed components' menu to enable or disable any component without uninstalling.
2. Or add a checkboxes in 'Preferences: Playback > Postprocessors' menu with all installed postprocessors in it.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-04-04 10:41:53
DUI statusbar highlight glitch: >>>%tag%<<< at the end of the statusbar syntax causes "total duration of selected tracks" and  "count of selected tracks" to be highlighted. Adding a space after >>>%tag%<<< prevents this glitch.
Title: Re: foobar2000 v2.0 bugs
Post by: iridescentaudio on 2023-04-04 14:05:23
Any chance of taking another look at the Playback Statistics issue of tag writes interrupting playback (https://hydrogenaud.io/index.php/topic,122553.0.html)? IIRC changes were made in the first 2.0 beta so that tag writes didn't apply until track stop or change (perfect), but AFAIK they were rolled back when the component was separated out again. Possibly an oversight?

(sorry if this is in the wrong place, there isn't a Playback Statistics thread listed on the component repository (https://www.foobar2000.org/components/view/foo_playcount).)
Title: Re: foobar2000 v2.0 bugs
Post by: Belomor on 2023-04-05 14:17:34
Foobar2k 2.0 beta 30 x64, it prints a few lines in the console while scanning my media library, like:
Code: [Select]
Invalid cuesheet - index outside allowed range
Invalid cuesheet - index outside allowed range
Invalid cuesheet - index outside allowed range
Multiple ID3v2 tags encountered
Multiple ID3v2 tags encountered
Multiple ID3v2 tags encountered
How do I find the problem .cue or .flac file so that I could correct it?
Title: Re: foobar2000 v2.0 bugs
Post by: dore.moni on 2023-04-07 12:15:56
File integrity verifier: Verbose Accurate rip output option does not work, no changes with on/off checkbox in Advanced options.
Foobar v1.6.16 the same issue
Title: Re: foobar2000 v2.0 bugs
Post by: ASopH on 2023-04-08 08:25:22
Hi,

little glitch in TABS - the left/right buttons in dark mode are light :-)
Title: fooBar v2.0 - bitrate AC3/DTS embedded in MKV bug
Post by: Defender on 2023-04-08 09:32:29
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?

Title: Re: foobar2000 v2.0 bugs
Post by: marktherob2005 on 2023-04-08 21:47:47
Foobar V2.0 all betas for X32 are playing back 192K bitrate garbled however X64 are playing correctly.
Title: Re: foobar2000 v2.0 bugs
Post by: josemescud on 2023-04-09 12:45:42
I would like, if possible, that the "Batch attach pictures" option of the Masstagger component in dark mode is not blank.
Title: Re: foobar2000 v2.0 bugs
Post by: beat8000 on 2023-04-09 14:08:54
Hi, I'm receiving the following error message after the clean installation of v2.0 beta 31 64bit Win 10:

(https://www.dropbox.com/s/qdhninszqefwi5h/Capture.PNG?dl=1)

Since then the same error happens also for version 27 - 30. I think there might be an issue in the registry now.
Title: Re: foobar2000 v2.0 bugs
Post by: Defender on 2023-04-10 11:29:13
Quote from: marktherob2005 on
Foobar V2.0 all betas for X32 are playing back 192K bitrate garbled however X64 are playing correctly.

I had the same experience that in the middle of some songs I had just noise. Songs work fine in 1.6.16.
I converted the container (Monkey's audio) to Flac. Resulting flac play fine on fb2k beta 31 x86.
I installed Monkey's audio component 10.07 to fb2k x86 and now also the original Monkey's audio files play fine.

Seems as if the internal fb2k beta 31 x86 Monkey's audio component is the culprit.
Title: Re: foobar2000 v2.0 bugs
Post by: Porcus on 2023-04-10 13:03:42
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 (https://hydrogenaud.io/index.php/topic,122810), bug in its MPEG-2 decoder (https://hydrogenaud.io/index.php/topic,123198.0.html), and ffplay chokes on FLAC files with (stupidly) small block sizes and the dev doesn't care (https://hydrogenaud.io/index.php/topic,121478.msg1020251.html#msg1020251).)

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.
Title: Re: foobar2000 v2.0 bugs
Post by: Defender on 2023-04-10 13:44:06
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 (https://hydrogenaud.io/index.php/topic,122810), bug in its MPEG-2 decoder (https://hydrogenaud.io/index.php/topic,123198.0.html), and ffplay chokes on FLAC files with (stupidly) small block sizes and the dev doesn't care (https://hydrogenaud.io/index.php/topic,121478.msg1020251.html#msg1020251).)

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).
Title: Re: foobar2000 v2.0 bugs
Post by: Defender on 2023-04-10 14:09:05
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.
Title: Re: foobar2000 v2.0 bugs
Post by: dore.moni on 2023-04-10 14:24:08
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
Title: Re: foobar2000 v2.0 bugs
Post by: frogworth on 2023-04-12 15:16:35
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.
Title: Re: foobar2000 v2.0 bugs
Post by: marktherob2005 on 2023-04-12 16:56:21
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.
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2023-04-12 18:03:36
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)?
Title: Re: foobar2000 v2.0 bugs
Post by: Melchior on 2023-04-12 18:37:13
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?
Title: Re: foobar2000 v2.0 bugs
Post by: dore.moni on 2023-04-13 06:49:39
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
Title: Re: foobar2000 v2.0 bugs
Post by: dore.moni on 2023-04-13 06:53:02
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?
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2023-04-13 08:14:32
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.
Title: Re: foobar2000 v2.0 bugs
Post by: Squeller on 2023-04-13 09:14:50
Not a bug, but... you get it. Arrows are barely visible in dark mode.
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2023-04-13 10:25:36
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.
Title: Re: foobar2000 v2.0 bugs
Post by: dore.moni on 2023-04-13 13:11:08
Arrows are barely visible in Album List. Theme is default, not dark, but i use grey background for foobar
Title: Re: foobar2000 v2.0 bugs
Post by: Cannonaire on 2023-04-15 23:05:29
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!
Title: Re: foobar2000 v2.0 bugs
Post by: frogworth on 2023-04-16 04:09:11
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 🙏🏼
Title: Re: foobar2000 v2.0 bugs
Post by: beat8000 on 2023-04-17 01:29:35
Hi, I'm still receiving the following start error message after the clean installation of v2.0 beta 33 64bit Win 10:

(https://www.dropbox.com/s/qdhninszqefwi5h/Capture.PNG?dl=1)

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. 
Title: Re: foobar2000 v2.0 bugs
Post by: Case on 2023-04-17 06:41:19
@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.
Title: Re: foobar2000 v2.0 bugs
Post by: beat8000 on 2023-04-17 11:53:41
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.
Title: Re: foobar2000 v2.0 bugs
Post by: marktherob2005 on 2023-04-17 18:21:34
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.
This bug has been fixed in Beta 33
Title: Re: foobar2000 v2.0 bugs
Post by: TuNk77 on 2023-04-17 21:55:00
foobar2000 v2 seems to be missing the options when rightclicking an scrollbar.
Please see images:

foobar2000 v1.6, rightclick options, as expected:
(http://i.imgur.com/cVhPX9Wh.png) (https://imgur.com/cVhPX9W)

In foobar2000 v2, these rightclick options are missing:
(https://i.imgur.com/SJIfAEKh.png)

I don't know if it is an intended behavior or an bug?
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-04-17 22:06:09
Playlist Switcher: Scrollbar not in Dark Mode.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-04-18 09:13:46
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.
Title: Re: foobar2000 v2.0 bugs
Post by: regor on 2023-04-18 09:43:35
Can confirm the same on v1.6. Scrollbar menu appears on OS language, even if foobar is set to English.
Title: Re: foobar2000 v2.0 bugs
Post by: Case on 2023-04-18 09:54:11
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 (https://learn.microsoft.com/en-us/sysinternals/downloads/procmon)? Please do not filter out at least anything that touches any file called shared.dll.
Title: Re: foobar2000 v2.0 bugs
Post by: mp5 on 2023-04-18 15:11:04
1. foobar can not remember a window with a playlist view that is less than 8 rows long. I set it to one row only to get foobar window as little as possible, but when I restart it, it goes to a default of 8 rows.
2. On columns ribbon the letters are light gray on white, so I can not see anything.

Title: Re: foobar2000 v2.0 bugs
Post by: poldar on 2023-04-18 15:25:01
Hello,
I use Foobar 2000 V2 beta 31 (32 bits).
I use an auto playlist to select classic tracks not yet played
My filter pattern is:
genre LESS "8" AND ((%play_count% LESS 1) OR ((%play_count% LESS 2) AND (%last_played%  DURING LAST 1 HOURS))) AND %discnumber% LESS 6000 AND NOT %rating% IS 1
Comment:
Genre less “8” = tracks of classical music
A track read for the first time must disappear from the auto playlist after one hour
Tracks with rating=1 do not appear in the playlist

Since the installation of Foobar 2000 V2 this auto-playlist is no longer updated in real time.

To force the update you must either relaunch foobar or revalidate the filter pattern.

According to my tests:
Field-based auto-playlists update in real time when the value of the field is changed.
The auto-playlist based on time criteria does not update in real time when time criterion is checked.

thanks for your help
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-04-18 16:23:40
Your filter pattern doesn't make sense.
Title: Re: foobar2000 v2.0 bugs
Post by: seomanakasimon on 2023-04-18 16:40:59
I have build A new system and i'm running W11
How do i get exclusive output on my HDMI output without craks and extreme distortion.
Whithout exclusive it all seems to work without distortion but then the output does not switch from stereo to surround and vise versa

Now i'm running the 32 bit V2.0 beta 33
I'm running the 32bit version because 1 plugin is not willing to go 64 bit.

I hav tried some of the advanced settings in foobar. 
Advanced > Playback > exclusive  output overrides on and off with diffent values. (can not go higher 100ms ??)
Advanced > Playback > Buffering some diffeent values

I tried: In Windows running the Foobar2000.exe in realtime priority ( helped in win 7 and 8 with asio ticks and pops)

Anyone any trick op there sleeves?

(PS noticed same beaviour on a laptop with W11)

-Asus Prime H610M-R D4
-Intel I5 13400T
-32GB dr4
Title: Re: foobar2000 v2.0 bugs
Post by: poldar on 2023-04-18 17:32:33
Quote from: grimes on
Your filter pattern doesn't make sense.

Why?
This filter has been working perfectly for years.
I just have a real-time refresh problem since Foobar v2.

Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-04-18 17:48:13
You can test this with a simple filter autoplaylist.
Title: Re: foobar2000 v2.0 bugs
Post by: beat8000 on 2023-04-18 17:57:34
Quote from: Case on
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 (https://learn.microsoft.com/en-us/sysinternals/downloads/procmon)? Please do not filter out at least anything that touches any file called shared.dll.
Hi @Case
I think it was an issue in the Windows registry because some Volume7 and Volume8 Foobar2000 keys were locked in the registry and couldn't be deleted anymore. Therefore I have made a save of this probably invalid system and I have restored one of my valid system images.

Now the clean install is working again and I can also update the version 26-x64 with all my settings to 33-x64.
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2023-04-18 18:00:28
re: time based queries...

The easiest thing to test with is the Library menu>Playback statistics>Show recently played. This opens a library search window. Now click the button on the extreme right with 3 dots>Create autoplaylist.

Now listen as normal and find tracks getting added as you listen. Works for me (tm).
Title: Re: foobar2000 v2.0 bugs
Post by: poldar on 2023-04-19 10:40:09
Quote from: grimes on
You can test this with a simple filter autoplaylist.
Quote from: grimes on
You can test this with a simple filter autoplaylist.
Quote from: marc2k3 on
re: time based queries...

The easiest thing to test with is the Library menu>Playback statistics>Show recently played. This opens a library search window. Now click the button on the extreme right with 3 dots>Create autoplaylist.

Now listen as normal and find tracks getting added as you listen. Works for me (tm).

thank you for your answers.
Here is a simpler example:

Query pattern:
%last_played% DURING LAST 5 MINUTES

On the screenshots below we see:
At 10:19 am we see that the playlist is well updated and real time according to the tracks played
But it is not updated to remove tracks read more than 5 minutes ago (it still contains tracks read from 9h20).

At 10;20 I revalidated the filter manually which causes the expected result

The playlist with the filter pattern
genre LESS "8" AND ((%play_count% LESS 1) OR ((%play_count% LESS 2) AND (%last_played%  DURING LAST 1 HOURS))) AND %discnumber% LESS 6000 AND NOT %rating% IS 1
cited in my first post is intended to contain unread classic tracks.
(tracks read must disappear with a one-hour latency to allow full playback before erasing).
With the V1 this mechanism worked correctly, since the V2 the tracks read for more than an hour no longer disappear in real time.

Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-04-19 12:04:41
Can't reproduce. last played track is removed after 5 min from Search panel and from the created autoplaylist.
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2023-04-19 12:19:23
Thanks for all reports.
The timed refresh bug was quite hard to reproduce reliably and depended on order of other events. Should be gone in beta 34.
Also fixed scroll bar context menus, nice find.
Title: Re: foobar2000 v2.0 bugs
Post by: poldar on 2023-04-19 12:43:35
Quote from: grimes on
Can't reproduce. last played track is removed after 5 min from Search panel and from the created autoplaylist.
Quote from: grimes on
Can't reproduce. last played track is removed after 5 min from Search panel and from the created autoplaylist.

Interesting

When the search window is opened it updates in real time and the playlist too.
When the search window is closed the playlist does not update in real time.

My configuration

Windows 7 64 bits
Foobar 2000.V2.0 beta 31(x86) 32 bits
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-04-19 12:50:22
Thanks Peter, you forgot Playlist History's scrollbar context menu. See Screenshot.
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2023-04-19 12:52:58
Is that part of fb2k itself? I think not.  :o  :))
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2023-04-19 13:24:31
Quote from: poldar on
Interesting

When the search window is opened it updates in real time and the playlist too.
When the search window is closed the playlist does not update in real time.

My configuration

Windows 7 64 bits
Foobar 2000.V2.0 beta 31(x86) 32 bits
Exactly that should be fixed in beta 34. Please update.
Title: Re: foobar2000 v2.0 bugs
Post by: Air KEN on 2023-04-19 15:06:38
foobar2000 v2.0 beta 34 64bit Default UI (only)
Context Menu > "Run seavice" is not displayed.

Preferences > Context Menu > "Run seavice" ON

foobar2000 v2.0 beta 34 64bit Columns UI: OK
foobar2000 v2.0 beta 34 32bit Default UI/Columns UI: OK

foobar2000 v2.0 beta 33 32bit/64bit Default UI/Columns UI: OK

(https://i.imgur.com/GvS6szX.png)

(https://i.imgur.com/rrvzoh1.png)
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-04-19 15:18:30
Don't have that problem. Do you have latest version 0.4.5, released on 2022-09-19?
Title: Re: foobar2000 v2.0 bugs
Post by: Air KEN on 2023-04-19 15:29:34
Yes, Run services 0.4.5 (2022-09-19).
No problem up to foobar2000 v2.0 beta 33.

Installed components:
Spoiler (click to show/hide)
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-04-19 15:48:14
Do you have Preferences | Tools | Run services?
Title: Re: foobar2000 v2.0 bugs
Post by: Air KEN on 2023-04-19 22:11:50
@grimes

Bingo!
Broken Runservice Setting for 4 foobars.
When I replaced "foo_run.dll.cfg", it returned to the original.

Many thanks.
Title: Re: foobar2000 v2.0 bugs
Post by: dore.moni on 2023-04-19 23:58:41
Quote from: seomanakasimon on
I have build A new system and i'm running W11
How do i get exclusive output on my HDMI output without craks and extreme distortion.
Whithout exclusive it all seems to work without distortion but then the output does not switch from stereo to surround and vise versa

Now i'm running the 32 bit V2.0 beta 33
I'm running the 32bit version because 1 plugin is not willing to go 64 bit.

I hav tried some of the advanced settings in foobar. 
Advanced > Playback > exclusive  output overrides on and off with diffent values. (can not go higher 100ms ??)
Advanced > Playback > Buffering some diffeent values

I tried: In Windows running the Foobar2000.exe in realtime priority ( helped in win 7 and 8 with asio ticks and pops)

Anyone any trick op there sleeves?

(PS noticed same beaviour on a laptop with W11)

-Asus Prime H610M-R D4
-Intel I5 13400T
-32GB dr4

I had the same issue. This settings solve my problem with distorsion on exclusive outpur:

Exclusive output overrides=on, Use event=off in Advanced menu
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-04-22 13:36:52
DUI, playlist view: column "Playing" is not sortable for Queue indicator ("(1)", "(2)", etc.).
Title: Re: foobar2000 v2.0 bugs
Post by: Newron on 2023-04-23 13:13:47
Hi Peter,

Re-Facets freezes foobar on start-up, if Re-Facets mode is set to Library and a search query is present (like "%style% HAS rock"). Freeze eats no CPU.

My config:
- beta 34, 64bit
- 40.000+ tracks
- 8 facets, 4 of them multi-value: language, genre, style, mood (a lot to compute/filter^^")

Workaround:
Setting Re-Facets mode to Playlist.

Related observation:
While updating, Re-Facet is blocking other operations. Re-Facets is very slow compared to old (in-memory) Facets. A query on my machine takes roughly 1 sec per 10k items, while old one updates almost instantly.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-04-23 15:29:31
A problem with the Media Library? Any errors in Preferences | Media Library | Show errors?
Title: Re: foobar2000 v2.0 bugs
Post by: Newron on 2023-04-23 17:32:43
Hi Grimes,

"Show errors" listed 14 file not found errors (guess they were from early beta, when I accidentally used 1.6 foobar to move some folders).

I cleared that error list. No new errors after restarting foobar. Button greyed out.

Forgot to mention that the freeze bug appeared in previous betas as well.

Sometimes the start-up freeze did not happen with new betas, but eventually reappeared, as my collection grew or changed my re-facets setup
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-04-23 17:38:16
Had problems with a corrupted Media Library myself, could fix it with: https://hydrogenaud.io/index.php/topic,122847.msg1024429.html#msg1024429
Title: Re: foobar2000 v2.0 bugs Performance
Post by: poldar on 2023-04-23 19:15:58
Hi Peter,

First congratulations for your fantastic audio player and your constant work to continuously improve it. I use it daily to automatically choose the tracks to listen according to multicriteria (rating, playback history and so on...) among my 75,000 classical music tracks.

Since the upgrade to V2.0 the boot time has changed from 15 s to 1mn 30s.
By analysing the activity of the computer with the resource monitor (see attachment 1) we see that the slowdown is caused by very high disk activity on the system disk that contains the profile file of foobar and on the disk Z: which contains my music library.
The main disk activity takes place on the playlist files in the profile folder (...Appdata/roaming/foobar2000-v2).
I use many playlists, the largest of which contains 59,000 tracks.

Apart from this small problem during cold start, I have no other problem with response time.
The most complicated requests are executed at lightning speed.

I also noticed a spike in CPU activity every minute when foobar is running (already present with v1) (see attachment 2).
May be caused by the refresh of playlists depending on time parameter.
If so, I would have a suggestion: allow users to define the refresh period of each playlists (for some of my playlists a refresh of an hour or even a day would be enough).
Thank you for your attention
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-04-23 19:26:46
Hi poldar,
please post your console output (View | Console) after startup of foobar2000.

(23.000 tracks: startup < 5s)
Title: Re: foobar2000 v2.0 bugs
Post by: Newron on 2023-04-23 20:14:23
Quote from: grimes on
Had problems with a corrupted Media Library myself, could fix it with: https://hydrogenaud.io/index.php/topic,122847.msg1024429.html#msg1024429

Rebuilding media library did not help, foobar still freezes on start-up with my way of using re-facets.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-04-23 20:24:29
I don't think it's a problem with the ML viewer, but with the ML.
Next try: All Music playlist | Select all tracks | context menu | Utilities | Verify integrity
Title: Re: foobar2000 v2.0 bugs
Post by: Cannonaire on 2023-04-24 05:08:28
Scroll bar is wrong in dark mode in the DSP dropdown in the top toolbar. 2.0 Beta 34 x86. I don't know if this pertains to foobar itself or ColumnsUI. I'm using ColumnsUI.
Title: Re: foobar2000 v2.0 bugs
Post by: poldar on 2023-04-24 08:45:41
Quote from: grimes on
Hi poldar,
please post your console output (View | Console) after startup of foobar2000.

(23.000 tracks: startup < 5s)

Hi Grimes,
Thanks , I had never used the console view. It contains insightful information (in particular: a corrupt file, an unexpected resampling on one of my output devices).
Attached are two console views:
one for the first foobar boot (cold boot)
the other for a foobar restart (stop and restart of foobar). (warm boot).
Warm boot is very fast because the data of the files are still present in the cache.

In my previous post I forgot to specify that all my playlists are auto playlists.
The purpose of my post was to report a slower start in V2 than in V1.  The difference is even greater because I have a large dicotheque and I use a lot of playlists.
This is not a critical issue as it only happens once a day when foobar starts cold.
Title: Re: foobar2000 v2.0 bugs
Post by: Porcus on 2023-04-24 09:12:40
Highlight color doesn't work, I think? With reservation for user error.

Discovered because "it randomly worked" when I hit a ReFacets selection. Then, when I went into Preferences -> Colors and fonts, I noticed that I had once upon a time set it to something bright. But what it actually shows, is some grey tint (that, when I look at it, is hardly useful in dark mode).
Except that random instance. Which I cannot reproduce. Grey is back.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-04-24 09:13:53
Startup seems to be fine, except Library. Please remove that corrupt Ravel FLAC from Media Library, the loading may be time-consuming. Just move the file to a directory not monitored by Media Library.
Additional you can do my recommendations for Newron's problem, a few posts above: Rebuild Library and File Integrity check.
Then post again Console output (cold/warm).

(I have 80 playlists)

The construction architecture of the Media Library has changed fundamentally from v1 to v2.
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2023-04-24 11:22:20
Quote from: poldar on
one for the first foobar boot (cold boot)
the other for a foobar restart (stop and restart of foobar). (warm boot).
Warm boot is very fast because the data of the files are still present in the cache.
Thanks for the problem report.
Can you please post specifications of your computer? Most importantly, is your operating system (and foobar2000 profile) on a spinning hard disk drive, or a solid state drive?
If it's a hard disk drive, I can add mitigations for this exact case (ordered database read might help here), but you really but really want to get upgrade to *any* solid state drive, even a 10 years old one.
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2023-04-24 11:26:12
Quote from: Porcus on
Highlight color doesn't work, I think? With reservation for user error.

Discovered because "it randomly worked" when I hit a ReFacets selection. Then, when I went into Preferences -> Colors and fonts, I noticed that I had once upon a time set it to something bright. But what it actually shows, is some grey tint (that, when I look at it, is hardly useful in dark mode).
Except that random instance. Which I cannot reproduce. Grey is back.
Note that there is highlight color and selection color. The former in fact rarely used, mainly by visualisations; definitely not used in ReFacets.
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2023-04-24 11:26:39
Quote from: Cannonaire on
Scroll bar is wrong in dark mode in the DSP dropdown in the top toolbar. 2.0 Beta 34 x86. I don't know if this pertains to foobar itself or ColumnsUI. I'm using ColumnsUI.
Noted, thanks.
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2023-04-24 11:29:34
Quote from: Newron on
Hi Peter,
Re-Facets freezes foobar on start-up, if Re-Facets mode is set to Library and a search query is present (like "%style% HAS rock"). Freeze eats no CPU.
Thanks for the bug report.
I made a special component to turn these into crash reports:
https://www.foobar2000.org/components/view/foo_crash
Please use its deadlock troubleshooting tool to produce and submit crash reports, I'll look into them.

Edit: I just updated the component so the feature can be used even if foobar2000 locks up during early startup before you can get to relevant menu.
Title: Re: foobar2000 v2.0 bugs
Post by: Porcus on 2023-04-24 12:16:42
Quote from: Peter on
Quote from: Porcus on
Highlight color doesn't work, I think? With reservation for user error.

Discovered because "it randomly worked" when I hit a ReFacets selection. Then, when I went into Preferences -> Colors and fonts, I noticed that I had once upon a time set it to something bright. But what it actually shows, is some grey tint (that, when I look at it, is hardly useful in dark mode).
Except that random instance. Which I cannot reproduce. Grey is back.
Note that there is highlight color and selection color. The former in fact rarely used, mainly by visualisations; definitely not used in ReFacets.

Hm ... tested more, and got closer to the bug - I am fairly sure it is. It is Selection:
I actually got the Selection colour "working" in ReFacets by changing it "from blue to a different blue"; I think the blue it was was the default-if-checkboxed. The "highlighting" was by doing the following:
* A ReFacets search in Playlist,
* then click "all".
In the playlist I then see "stripes" for the ones matched. Now they are "a different blue", but for months they have been grey. Certainly visible in light mode, not in dark mode. But then for sudden it turned blue, and by changing the blue tint ... blue it is.
By reverting to default (and closing playlist and reopening blah blah blah) and checking the Selection box to get up the "default blue" ... grey reproduced. And it is a darker grey than when Selection wasn't checked! So checking off the Selection
* should have turned it blue,
but
* does turn it to a different grey.
Title: Re: foobar2000 v2.0 bugs
Post by: Newron on 2023-04-24 17:11:29
Quote from: Peter on
Thanks for the bug report.
I made a special component to turn these into crash reports:
https://www.foobar2000.org/components/view/foo_crash
Please use its deadlock troubleshooting tool to produce and submit crash reports, I'll look into them.

Edit: I just updated the component so the feature can be used even if foobar2000 locks up during early startup before you can get to relevant menu.

My computer running foobar is not connected to the internet. How do I (preferably not publically) submit the crash report?
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-04-24 17:25:09
In configuration folder of foobar2000 is a folder "crash report" with a txt and a dmp file.
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2023-04-24 18:42:15
What grimes said.
Email relevant files to peter [at] hydrogenaud.io
Title: Re: foobar2000 v2.0 bugs
Post by: poldar on 2023-04-24 23:46:10
Quote from: grimes on
Startup seems to be fine, except Library. Please remove that corrupt Ravel FLAC from Media Library, the loading may be time-consuming.
The construction architecture of the Media Library has changed fundamentally from v1 to v2.
Hi
Thank you for your answer.
- I replaced the corrupted file with a healthy version that brings a gain of nearly 40s to start-up time!
- I reinstalled V1.6.16 to observe the console view.

Cold starts
With V1 the Start-up time is identical to that of the V2.
But the global startup time in V1 is shorter because the playlists initialize during the start-up
while with V2 the initialization of the library continues after the startup phase
Global startup time: V2 48s vs V1 22s

Warm start V2 1s

See console views attached
Title: Re: foobar2000 v2.0 bugs
Post by: poldar on 2023-04-25 00:02:08
Quote from: Peter on
Can you please post specifications of your computer? Most importantly, is your operating system (and foobar2000 profile) on a spinning hard disk drive, or a solid state drive?
If it's a hard disk drive, I can add mitigations for this exact case (ordered database read might help here), but you really but really want to get upgrade to *any* solid state drive, even a 10 years old one.

My configuration:
Windows Home Premium edition SP1 64bits
Processor Intel Core is-3450 3.10GHz
Windows Performance Index:
CPU: 7.5
Memory:7.6
Transfer rate of the system: 5.9 (hard Disk)

My system hard Disk is the weak point of my configuration.

After fixing the corrupted track, the cold boot time of the V2 is significantly reduced. See my answer to Grimes above.
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2023-04-25 00:04:49
Have you tried without foo_upnp? I seem to recall @regor grumbling about it being really slow on earlier fb2k betas. This may have been resolved by the metadata caching changes way back in Beta18 but I honestly have no idea.
Title: Re: foobar2000 v2.0 bugs
Post by: Cannonaire on 2023-04-25 00:31:15
Quote from: Peter on
Quote from: Cannonaire on
Scroll bar is wrong in dark mode in the DSP dropdown in the top toolbar. 2.0 Beta 34 x86. I don't know if this pertains to foobar itself or ColumnsUI. I'm using ColumnsUI.
Noted, thanks.
Looks like most or all of the dropdowns on the toolbar have light mode highlight and scrollbar.
Title: Re: foobar2000 v2.0 bugs
Post by: regor on 2023-04-25 01:57:56
Quote
Have you tried without foo_upnp? I seem to recall @regor grumbling about it being really slow on earlier fb2k betas. This may have been resolved by the metadata caching changes way back in Beta18 but I honestly have no idea.
- V2 beta 8 with foo_upnp 70K tracks: 120 secs. + Startup time : 0:45 = 3 min total of startup (unresponsive UI full time)
- V2 beta 34 with foo_upnp 70K tracks: 88 secs + Startup time : 0:23 = 1:40 min  total of startup (unresponsive UI full time)
- V1.6 with foo_upnp 70K tracks: 10 secs + Startup time : 0:26 = 30 secs total of startup (but UI is responsive at ~20 s)

An improvement, but really far from v1.6 performance.
Title: Re: foobar2000 v2.0 bugs
Post by: Air KEN on 2023-04-25 09:48:12
Hi :)
Classic Playlist View (Classic User Interface 2.0.2 (foo_ui_classic))
foobar2000 v2.0 beta 34 64bit

Scrollbar is black when foobar is minimized and restored. Click the scrollbar to fix.
When used in the Classic User Interface, Default UI element and Columns UI Panel.

(https://i.imgur.com/5rRA01L.png)

Thanks.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-04-25 10:36:24
@poldar CPU Spikes: Did you check your S.M.A.R.T. parameters for your drive?
Title: Re: foobar2000 v2.0 bugs
Post by: Air KEN on 2023-04-25 12:48:21
Quote from: Air KEN on
Hi :)
Classic Playlist View (Classic User Interface 2.0.2 (foo_ui_classic))
foobar2000 v2.0 beta 34 64bit

Scrollbar is black when foobar is minimized and restored. Click the scrollbar to fix.
When used in the Classic User Interface, Default UI element and Columns UI Panel.

(https://i.imgur.com/5rRA01L.png)

Thanks.
Classic User Interface 2.0.3 (2023-04-25)
https://www.foobar2000.org/components/view/foo_ui_classic
solved.

Thanks Peter.
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2023-04-25 13:12:21
Beta 35 out.
Startup lockup with ReFacets filters has been addressed.
I'm really hoping to go 2.0 final by the end of this week.
If issues that you're running into persist, don't worry, preview builds of the next version will be available shortly after. At this point I want 2.0 stable done without usage-ruining bugs.
Title: Re: foobar2000 v2.0 bugs
Post by: poldar on 2023-04-25 13:24:38
Quote from: grimes on
@poldar CPU Spikes: Did you check your S.M.A.R.T. parameters for your drive?

Attached the results of the scan for my System disk
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-04-25 14:12:14
This is ok. Additionally you could try in foobar2000's Advanced Preferences Playback | Prevent hard disk sleep while playing.
Title: Re: foobar2000 v2.0 bugs
Post by: poldar on 2023-04-25 16:33:24
Quote from: grimes on
This is ok. Additionally you could try in foobar2000's Advanced Preferences Playback | Prevent hard disk sleep while playing.
It’s done.
But I don’t understand how this change could improve Foobar’s startup time
nor the CPU peak seen every minute when foobar is active because this peak occurs even if there is no playback in progress
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-04-25 16:55:51
Thanks for the information. Then the option is useless for you. I thought, that the spin-up of the hard disc causes the spikes. Are these spikes only with foobar2000? Possible is also a processor defect. Are these spikes really at 80% CPU? Unusable! Your computer is 13 years old. I recommend a new computer with SSD.
Title: Re: foobar2000 v2.0 bugs
Post by: Defender on 2023-04-25 18:11:39
Quote from: Defender on
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.

Things improved a lot in beta 35 x86. The correct kbps is reported.

Bit weird that in case of lossless DTS-HD the correct __bitspersample is reported which is not available in lossy DTS (16/20/24 bit).
I would also prefer that in codec or codec_profile the difference between DTS and DTS-HD would be reported.

Maybe beta 36 :-) ?
Title: Re: foobar2000 v2.0 bugs
Post by: Bogozo on 2023-04-25 18:24:03
Quote from: Defender on
Bit weird that in case of lossless DTS-HD the correct __bitspersample is reported which is not available in lossy DTS (16/20/24 bit).
Lossy DTS (just like mp3, aac and so on) doesn't have any bitdeph.
Title: Re: foobar2000 v2.0 bugs
Post by: Defender on 2023-04-26 12:33:25
Quote from: Bogozo on
Quote from: Defender on
Bit weird that in case of lossless DTS-HD the correct __bitspersample is reported which is not available in lossy DTS (16/20/24 bit).
Lossy DTS (just like mp3, aac and so on) doesn't have any bitdeph.

Ha, thanks for pointing that out.

Apparently only the lossy DTS 96/24 format is actuallly 96kHz / 24bit on compatible devices and has an embedded fallback core of 48/16 on non compatible devices.
Is that correct?

Everything below checked on beta 35.

Analogue to this E-AC3 also reports (windows/mediainfo) having a bitdepth of 32 (which doesn't show in foobar). Is this also incorrect since it is a lossy format?

About codec field within foobar (container MKV):
Sometimes foobar properties have %codec% E-AC3 and sometimes %codec%  EAC3.
In case of lossless DTS:X the %codec% field is not set (%video codec% is set correctly to H.265).
Title: Re: foobar2000 v2.0 bugs
Post by: Peter on 2023-04-26 12:45:08
Quote from: Porcus on
Hm ... tested more, and got closer to the bug - I am fairly sure it is. It is Selection:
I actually got the Selection colour "working" in ReFacets by changing it "from blue to a different blue"; I think the blue it was was the default-if-checkboxed. The "highlighting" was by doing the following:
* A ReFacets search in Playlist,
* then click "all".
In the playlist I then see "stripes" for the ones matched. Now they are "a different blue", but for months they have been grey. Certainly visible in light mode, not in dark mode. But then for sudden it turned blue, and by changing the blue tint ... blue it is.
By reverting to default (and closing playlist and reopening blah blah blah) and checking the Selection box to get up the "default blue" ... grey reproduced. And it is a darker grey than when Selection wasn't checked! So checking off the Selection
* should have turned it blue,
but
* does turn it to a different grey.

Weird behavior noted, thanks.
Selection color behaviors are indeed nonsensical, will be looked into for the next update after 2.0.
Title: Re: foobar2000 v2.0 bugs
Post by: Porcus on 2023-04-26 13:08:07
Quote from: Peter on
Quote from: Porcus on
Hm ... tested more, and got closer to the bug - I am fairly sure it is. It is Selection:
I actually got the Selection colour "working" in ReFacets by changing it "from blue to a different blue"; I think the blue it was was the default-if-checkboxed. The "highlighting" was by doing the following:
* A ReFacets search in Playlist,
* then click "all".
In the playlist I then see "stripes" for the ones matched. Now they are "a different blue", but for months they have been grey. Certainly visible in light mode, not in dark mode. But then for sudden it turned blue, and by changing the blue tint ... blue it is.
By reverting to default (and closing playlist and reopening blah blah blah) and checking the Selection box to get up the "default blue" ... grey reproduced. And it is a darker grey than when Selection wasn't checked! So checking off the Selection
* should have turned it blue,
but
* does turn it to a different grey.

Weird behavior noted, thanks.
Selection color behaviors are indeed nonsensical, will be looked into for the next update after 2.0.

Update, anyway, because I upgraded to beta 35 yesterday.
But first, I had reset the page at Preferences -> Display -> Default User Interface -> Colors and Fonts.
Then upgrade to beta 35.
And grey works as should. Every time!
Then, right now I see how I could trigger the behaviour:
Just enter the same page and hit the "Selection" checkbox. Grey goes "wrong grey instead of blue".
How to fix it? As above: On the page, click on the blue and drag the slider ever so slightly, changing the colour to something different.
How to break it? Reset page again and hit the "Selection" checkbox.
Title: Re: foobar2000 v2.0 bugs
Post by: BingoMan on 2023-04-26 17:16:46
In the light theme, as soon as you click on a track in the "Libraly Viewer Selection" window, the album or track selection in the Album List window disappears, and when there is a selection, for some reason it is dark blue and its color cannot be changed. It's very inconvenient, you can't see from which album the track is playing, in 1.6.16... everything is fine, the gray selection darkens a little but remains gray. In a dark theme, the gray selection remains at least a little bit visible, but in a light one, you can’t see what is playing at all.
The GIF video shows what it looks like.
Title: Re: foobar2000 v2.0 bugs
Post by: The Link on 2023-04-26 17:32:17
Just wanted to mention that foobar2000 v2.0 is released. 🥳
Title: Re: foobar2000 v2.0 bugs
Post by: cvac999 on 2023-04-26 19:36:27
I just tried updating. It wiped out my theme and all my components. Not happy. What's the easiest way to get back to the previous version? I don't know what happened here. I'm on Windows 10.
Title: Re: foobar2000 v2.0 bugs
Post by: esa372 on 2023-04-27 00:12:48
...same as above.
 :'(
Title: Re: foobar2000 v2.0 bugs
Post by: Cannonaire on 2023-04-27 03:02:00
Remember to always back up your settings before doing an in-place update. :(
Title: Re: foobar2000 v2.0 bugs
Post by: esa372 on 2023-04-27 03:09:00
Quote from: Cannonaire on
Remember to always back up your settings before doing an in-place update. :(
In my case, I did.  I am now back to v1.6.16  ...but, I would like to know how I can update to v2.0 while keeping my settings, layout, and components.

Any advice out there?
Title: Re: foobar2000 v2.0 bugs
Post by: Cannonaire on 2023-04-27 03:36:44
I'm sure someone here will be able to help. I could try, but I don't know where settings are stored. I've always used a Portable install. I know Columns UI has a button to export your settings - there might be other options like that.
Title: Re: foobar2000 v2.0 bugs
Post by: Gus. on 2023-04-27 03:43:56
I also use portable installs, there's a folder called "profile" inside the root "foobar2000" folder, which I think stores user data/settings/themes/components etc. (so keep a copy of that entire folder).
For me there's nothing foobar related in C:\Users\User\AppData
Title: Re: foobar2000 v2.0 bugs
Post by: Chibisteven on 2023-04-27 03:54:29
Quote from: esa372 on
Quote from: Cannonaire on
Remember to always back up your settings before doing an in-place update. :(
In my case, I did.  I am now back to v1.6.16  ...but, I would like to know how I can update to v2.0 while keeping my settings, layout, and components.

Any advice out there?

1. Run the 1.6.16 installer and have it move all user components to the correct place.  For ones it refuses to move, manually move them as well as their dependencies.
2. Now create a separate portable install of 1.6.16 of that same configuration and setup and use that to test your 2.0 upgrades on.  Once you get things working you can convert back to a system install of 2.0.

TIP: If you want to test system installs, use the Windows Sandbox feature if your version of Windows supports it.  Alternately, you can use a virtual machine or a different computer to test system installs.

Be sure you have "view hidden files" enabled:
For 1.6 system installs your configuration and users components will be at "C:\Users\-USER NAME HERE-\AppData\Roaming\foobar2000\"
For 2.0 system installs your configuration and users components will be at "C:\Users\-USER NAME HERE-\AppData\Roaming\foobar2000-v2\"
For portable installs it's always "ROOT FOLDER\profile\".  If you're missing a "profile" folder don't upgrade, run the 1.6.16 installer to migrate stuff to the correct place then upgrade.
Title: Re: foobar2000 v2.0 bugs
Post by: esa372 on 2023-04-27 04:50:24
Thanks, all, for the input.

Quote from: Chibisteven on
1. Run the 1.6.16 installer and have it move all user components to the correct place.  For ones it refuses to move, manually move them as well as their dependencies.
I made sure that all the components are in "...\AppData\Roaming\foobar2000", but I don't know how to check the relative dependencies.  (I did not see any option from the installer to move anything.)

Quote from: Chibisteven on
2. Now create a separate portable install of 1.6.16 of that same configuration and setup...
I am able create a portable install of v1.6.16 with my config, but when I upgrade to v2.0, all settings and components are again lost.

(btw, the portable install defaulted to "Desktop"; I'm using Windows 10, and Columns UI.)

Maybe the problem lies in the dependencies you mentioned, but if everything works fine as a portable install for v1.6 on the desktop, why wouldn't a portable install of v2.0 into the same folder carry over all the settings?

Thanks, again!
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2023-04-27 05:12:09
You are upgrading to 32bit 2.0 right? 64bit is never going to work. A 64bit install loads components from user-components-x64 and will ignore anything in the old user-components folder.

This is not a foobar2000 limitation, just general computing. Just like you cannot upgrade 32bit windows to 64bit without zapping your entire OS partition and starting again from scratch.

edit: I've not tested this but it might be possible to retain settings going from 32bit -> 64bit if you try this...

-Install 64bit portable in a pristine brand new folder.
-Do not attempt to use it as such or make any configuration changes.
-Go and acquire 64bit versions of all your components, assuming they are available. There is no alternative to finding and installing them manually. Do it the usual way via the components dialog in fb2k.
-Once you're happy the contents of the user-components-x64 folder in this new portable install match the contents of your old user-components folder, close the new fb2k 64bit instance.
-Now browse the profile and delete everything EXCEPT the user-components-x64 folder.
-Now browse your old 32bit profile and copy all the contents to the 64bit profile.
-Run and see what happens....  :P
Title: Re: foobar2000 v2.0 bugs
Post by: esa372 on 2023-04-27 06:33:12
Quote from: marc2k3 on
You are upgrading to 32bit 2.0 right? 64bit is never going to work. A 64bit install loads components from user-components-x64 and will ignore anything in the old user-components folder.
D'oh!! 

Thank you, marc2k3!  The 32-bit install worked perfectly.
(Sometimes, I forget to engage the ol' noodle!)

I don't have time tonight, but I will try your untested 32- to 64-bit experiment tomorrow.

Thanks for the tips, everyone!
Title: Re: foobar2000 v2.0 bugs
Post by: Dave.L on 2023-04-27 12:23:38
Hi.
Where is "Output format" in f2k v2.0 ?
Spoiler (click to show/hide)
f2k v2.0 automatically understands 16-24-32 bit, etc. ?

P.S.
Many thanks for major release, x64 bit, and native dark theme.

P.S.S.
According to the magazine "Time", person of the year — Peter Pawlowski.
✌️
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-04-27 12:27:09
Quote
New audio output device management features - unwanted devices can be disabled, bit depth and DSP can be configured per-device.
Title: Re: foobar2000 v2.0 bugs
Post by: pulbitz on 2023-04-27 12:54:20
I reported the "database is locked" issue a few times during the beta, but didn't get any feedback, so I just waited.
After installing the 2.0 final version, I deleted all my media libraries, playlists and rebuilt them.
The problem still occurs.

I'm attaching the console log and the metadb, library, playlists files.
https://www.mediafire.com/file/hppudd7v1j7ghnu/fb2k2.0-db-playlist.7z/file
Code: [Select]
Components loaded in: 0:00.006447
Configuration read in: 0:00.000487
foobar2000 v2.0 x64 [standard]
Playlist #0 loaded in 0:00.132494
User Interface initialized in: 0:00.255920
FFmpeg version: 6.0
Loading foo_discogger
foo_discogger: http_client service ready
Startup time : 0:00.308187
Watching: D:\Music
Library initialized after 0:00.897691
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-04-27 13:05:21
Did you remove the metadb.sqlite file?
Title: Re: foobar2000 v2.0 bugs
Post by: pulbitz on 2023-04-27 13:17:25
I deleted metadb.sqlite, \library-v2.0\*, \playlists-v2.0\*
Title: Re: foobar2000 v2.0 bugs
Post by: Case on 2023-04-27 13:34:29
@pulbitz, care to create a Process Monitor log showing what goes on over there? It's highly unlikely that foobar2000 locks the database form itself, I'd suspect that is done by some other application. But just in case it is locked by foobar2000 process you may want to share some configuration details. Perhaps there is some component out there that can do it.
Title: Re: foobar2000 v2.0 bugs
Post by: pulbitz on 2023-04-27 14:02:17
There are only two additional components that I install and use.
Masstagger 1.9 https://www.foobar2000.org/components/view/foo_masstag
Discogger 1.0.17.1 https://github.com/ghDaYuYu/foo_discogs/releases/tag/v1.0.17.1

And I have attached the config.sqlite and Process Monitor log files.
https://www.mediafire.com/file/1y2y3wjaeroi4ca/config.sqlite/file
https://www.mediafire.com/file/d7xb9eubtdb1apd/Logfile.PML.7z/file
Title: Re: foobar2000 v2.0 bugs
Post by: marktherob2005 on 2023-04-27 14:19:53
`new to report V2.0 Final X32 is not playing 192K Bit files properly. X64 pays correctly.
Title: Re: foobar2000 v2.0 bugs
Post by: Case on 2023-04-27 14:57:01
Thanks @pulbitz. I could replicate the error messages in the console by using your config files, but only with foo_discogger installed. It seems to do some SQLite accessing of its own too.

@marktherob2005 - If you want to be helpful, post a sample file or at the very least tell what file format your file has. Your issue sounds like the Monkey's Audio playback problem, but it should be gone now.
Title: Re: foobar2000 v2.0 bugs
Post by: pulbitz on 2023-04-27 19:10:52
Thanks for the test.
However, I found it odd that uninstalling foo_discogger didn't fix the problem, so I tested again.

I deleted the foobar2000-v2 folder in its entirety, so it was completely defaulted.
I then recreated just the media library and playlists and tested them.
This didn't cause any problems.

However, if I change the "Playback | Order | Default" to "Shuffle (albums)", I get the "database is locked" issue!
Title: Re: foobar2000 v2.0 bugs
Post by: da yuyu on 2023-04-27 19:47:15
Hi @pulbitz @case

IMHO it would be useful to clone the fb2k installation, reducing the library size (maybe by halfs) checking if the log still reports the same error.
Title: Re: foobar2000 v2.0 bugs
Post by: pulbitz on 2023-04-28 00:53:07
From what I've been able to test, the problem is not related to foo_discogger.
It happens even with a clean foobar2000.
I've written down my tests below to make it more clear.

1. Run a completely clean foobar2000 (%APPDATA%foobar2000-v2 folder doesn't exist)
2. Close foobar2000 (%APPDATA%foobar2000-v2 folder created)

3. Unpack and copy the attached library-v2.0.7z file to %APPDATA%foobar2000-v2 folder
https://www.mediafire.com/file/s8aewprg8xjn4h4/library-v2.0.7z/file

4. Once again, run foobar2000
5. Library - Album List, Right-click on "All Music" and click "Create Autoplaylist"

Up to this point, everything is fine.

6. Playback - Order - Shuffle (albums) or Shuffle (folders)

View - Console, The "database is locked" message is repeating.
Code: [Select]
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
Title: Re: foobar2000 v2.0 bugs
Post by: LeVvE on 2023-04-28 06:34:05
One thing I noticed with 2.0 is that the album list doesn't swap between light/dark font when text is highlighted based on how dark your background color is?

This is how it used to look: https://i.imgur.com/vTFDDkc.png
This is how it looks now: https://i.imgur.com/wElxea4.png

If I make the background any darker it's really hard to read the text in the album list because it's black instead of white, also when anything is clicked in the playlist the highlight color is removed and turns black so it's black on black and I can't read it at all.
Title: Re: foobar2000 v2.0 bugs
Post by: BingoMan on 2023-04-28 15:42:16
LeVvE
Yes, the color of the selection is not adjustable, and on a black background in the "Album List" window, the selection is not visible at all, in all beta versions it is, everything was waiting for it to be fixed, but not yet.
Title: Re: foobar2000 v2.0 bugs
Post by: wojak on 2023-04-28 16:18:09
Hi,
probably not a bug per se but: I have FB1.16 - normal install and FB2x64 normal install. I checked shell integration and all associations, context menus and all in FB2 and unchecked all of those in 1.16. The Enquenue and play with show wher I right click...but the files and folders play or que in old FB1.16 instead of FB2. I already checked the registry entries and they show the path to FB2.0 (Program files not ProgramFiles(86)). So the context menu does work but with wrong version of FB. How to fix this???
Title: Re: foobar2000 v2.0 bugs
Post by: Xin-Hong on 2023-04-28 18:56:35
Thank you for the 2.0 !

After a clean install of the x64 version I had a very minor ui issue:
Title: Re: foobar2000 v2.0 bugs
Post by: paregistrase on 2023-04-29 07:47:19
I have a strange bug with this chain of characters
Code: [Select]
Extra Prince, His Majesty Prince, P. Rince, Princ, Prince & Prince, Prince Jackson, Princes, Принс, פרינס, プリンス, 普林斯, 王子, 프린스

In some cases, foobar display it right and in other show squares.

For example, in properties main window show squares

(https://i.imgur.com/q3gKgOr.png)

but in the edit window is shown fine

(https://i.imgur.com/7FrTEXJ.png)

Also in the display text component (foo_textdisplay) have a weird behavior. If it is displayed in the same line show squares

(https://i.imgur.com/CEa8Zpk.png)

But in different lines, the characters in the new line show fine

(https://i.imgur.com/chuQPQQ.png)

Removing

Code: [Select]
פרינס

make the chain shows right in all scenarios

(https://i.imgur.com/tN2DtJz.png)

(https://i.imgur.com/Agol80H.png)

(https://i.imgur.com/NkZxsAw.png)


Can someone confirm if this happens also in windows and is not a wine bug?




Title: Re: foobar2000 v2.0 bugs
Post by: BThing on 2023-04-29 16:42:06
I really like the possibility that you can convert and save files in 64 bit floating point but I have a case of when I convert a 6 channel 24 bit 48 KHz WAV-file into a stereo 64 bit floating point 48 KHz WAV-file the resulting max amplitude becomes infinite (VERY) large. There is no problem when I convert it in 32 bit floating point. How can that happen and will you please correct that issue? It could potentially damage electronics and loudspeakers...! If you have a file-hotel, I could send you the original 6 channel file.

Always check the result before you play it on your sound system! Regards Brian.
Title: Re: foobar2000 v2.0 bugs
Post by: VitorMach on 2023-04-29 17:07:55
Hello!
I have one problem since I have installed fb2k 2.0 (32-bit), my media library is not being populated with files using other extensions such as s3m, vgm, mid, etc...
I have the extensions installed and up-to-date.
Does anyone know what the problem could be?

EDIT: Apparently setting the "restrict to" option to *.* instead of the original * fixes it.
Title: Re: foobar2000 v2.0 bugs
Post by: bnnm on 2023-04-30 00:29:30
Not 100% sure, but 2.0 64-bit may not be able to handle components using windows "\" style paths (incorrectly unpacked into {settings dir}/user-components-x64).

This has x64/*.dll and works: https://www.foobar2000.org/getcomponent/7e6c5ce77cd445493206b263f9b9697c/foo_input_vgmstream.fb2k-component

While this has x64\*.dll and doesn't: https://github.com/vgmstream/vgmstream-releases/releases/download/nightly/foo_input_vgmstream.fb2k-component

If I re-compress the later with 7-zip (that creates linux "/" style paths) works fine. Powershell creates win style paths so it's a bit inconvenient foobar can't handle them (since it's the only default win cmd tool that can make zips).
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2023-04-30 02:48:52
If you're using github actions to upload artifacts/releases, The 7zip command line tool (7z) is included on the windows runners. I use it...

https://github.com/marc2k3/foo_queue_viewer/blob/1ec65ec995c9d20b7a67810d63800f21bcbd0d6a/.github/workflows/build.yml#L59

Title: Re: foobar2000 v2.0 bugs
Post by: anamorphic on 2023-04-30 04:31:38
ReFacets bug? -

Double-click action: 'Send to new playlist' + 'Start playback when sending selection to playlist', does not start playback. Then, Middle-click action: 'Add to current playlist', playback starts, and continued middle-clicks start the new track.

(Typically the reverse in previous years, 'Send' actions can start playback while 'Add' actions do not)
Title: Re: foobar2000 v2.0 bugs
Post by: jarjuk on 2023-04-30 07:36:29
Hello,

I have raised an issue  https://github.com/mmtrt/foobar2000/issues/4 regarding change in CUE sheet functionality in foobar2000 V2.0, where foobar2000 v2.0 does not understand CUE sheets, which in v1.16.1 worked just fine.

I'll cross post it the into this 'upstream' site.

Hello,

(Sorry for my bad English)

Today I noticed that my foobar2000 cue sheets did not work in my Ubuntu 22.02 system after snap forced installation to version 2.0. I was able to resume cue sheet functionality by reverting back to v1.16.1 and disabling snap updates for foobar2000.

My use case: I have used cue sheet to index a number FLAC files converted from old recordings in reel tape, C-casette and MD-disks formats. Some of the FLAC file content is not of interest, and I have been able to (ab)use foobar2000 cue sheets to skip irrelevant sections in these FLAC files by assigning non-interesting sections to track 99. In v1.16.1, only last of the number 99 tracks (very short one) was present in the playlist loaded for the cue - effectively dropping non-interesting sections in the FLAC files.

Is it possible to have v2.0 re-implement the functionality, which we had in v1.16.1?

Thank You for this wonderful player - I have been using it I think over 10 years!

Best Regards Jukka

Below is an example for one of my cue sheets

Code: [Select]
TITLE   "Md-24"
FILE "..\Md-24/Md-24.flac" FLAC
  TRACK 1 AUDIO
       Performer "Freija"
      TITLE "Sä muistatko metsätien"
     INDEX 01 0:22:64
      REM REPLAYGAIN_TRACK_GAIN  4.17 dB
      REM REPLAYGAIN_TRACK_PEAK 0.521851
    TRACK 99 AUDIO
     TITLE "Loppu"
       Performer "5.7.2021-30.6.2022"
     INDEX 01 4:29:65


  TRACK 2 AUDIO
       Performer "Reijo Haapaniemi"
      TITLE "Anjushka"
     INDEX 01 4:36:5
      REM REPLAYGAIN_TRACK_GAIN  0.55 dB
      REM REPLAYGAIN_TRACK_PEAK 0.679321
    TRACK 99 AUDIO
     TITLE "Loppu"
       Performer "5.7.2021-30.6.2022"
     INDEX 01 7:8:15


  TRACK 3 AUDIO
       Performer "Johann Hermann Schein"
      TITLE "Banchetto musicale"
     INDEX 01 7:14:46
      REM REPLAYGAIN_TRACK_GAIN  +2.81 dB
      REM REPLAYGAIN_TRACK_PEAK 0.516998
    TRACK 99 AUDIO
     TITLE "Loppu"
       Performer "5.7.2021-30.6.2022"
     INDEX 01 9:28:19


  TRACK 4 AUDIO
       Performer "Nikolas Papazoglu"
      TITLE "Kaneis edo den tragouda"
     INDEX 01 9:39:27
      REM REPLAYGAIN_TRACK_GAIN  13.11 dB
      REM REPLAYGAIN_TRACK_PEAK 0.142517
    TRACK 99 AUDIO
     TITLE "Loppu"
       Performer "5.7.2021-30.6.2022"
     INDEX 01 12:43:53


  TRACK 5 AUDIO
       Performer "Järviradio"
      TITLE "Jingle"
     INDEX 01 13:9:49
      REM REPLAYGAIN_TRACK_GAIN  -7.59 dB
      REM REPLAYGAIN_TRACK_PEAK 1.000000

  TRACK 6 AUDIO
       Performer "Järviradio"
      TITLE "Grammari jingle"
     INDEX 01 13:15:14
      REM REPLAYGAIN_TRACK_GAIN  -0.18 dB
      REM REPLAYGAIN_TRACK_PEAK 0.972626
    TRACK 99 AUDIO
     TITLE "Loppu"
       Performer "5.7.2021-30.6.2022"
     INDEX 01 13:43:17


  TRACK 7 AUDIO
       Performer "Heikki Mikael"
      TITLE "Hiljaa pyyntösi sun kuulen"
     INDEX 01 13:46:69
      REM REPLAYGAIN_TRACK_GAIN  -6.06 dB
      REM REPLAYGAIN_TRACK_PEAK 1.000000
    TRACK 99 AUDIO
     TITLE "Loppu"
       Performer "5.7.2021-30.6.2022"
     INDEX 01 17:37:70


  TRACK 8 AUDIO
       Performer "Rhonda Vincent"
      TITLE "Ashes of Mt. Augustine"
     INDEX 01 17:44:13
      REM REPLAYGAIN_TRACK_GAIN  +3.81 dB
      REM REPLAYGAIN_TRACK_PEAK 0.345947
    TRACK 99 AUDIO
     TITLE "Loppu"
       Performer "5.7.2021-30.6.2022"
     INDEX 01 21:9:53


  TRACK 9 AUDIO
       Performer "Fairport Convention"
      TITLE "Fortheringay"
     INDEX 01 21:20:40
      REM REPLAYGAIN_TRACK_GAIN  +5.56 dB
      REM REPLAYGAIN_TRACK_PEAK 0.317230

  TRACK 10 AUDIO
       Performer "Kaseva"
      TITLE "Syksy"
     INDEX 01 24:28:22
      REM REPLAYGAIN_TRACK_GAIN  +2.56 dB
      REM REPLAYGAIN_TRACK_PEAK 0.547607

  TRACK 11 AUDIO
       Performer "Danny"
      TITLE "Keskiyöllä"
     INDEX 01 29:23:6
      REM REPLAYGAIN_TRACK_GAIN  +9.53 dB
      REM REPLAYGAIN_TRACK_PEAK 0.239563
    TRACK 99 AUDIO
     TITLE "Loppu"
       Performer "5.7.2021-30.6.2022"
     INDEX 01 32:23:52


  TRACK 12 AUDIO
       Performer "Vivaldi & Topi Lehtipuu"
      TITLE "Deh ti piega, deh consenti"
     INDEX 01 32:31:55
      REM REPLAYGAIN_TRACK_GAIN  +9.05 dB
      REM REPLAYGAIN_TRACK_PEAK 0.357697
    TRACK 99 AUDIO
     TITLE "Loppu"
       Performer "5.7.2021-30.6.2022"
     INDEX 01 41:38:16


  TRACK 13 AUDIO
       Performer "Radion kamarikuoro"
      TITLE "Virsi 558"
     INDEX 01 41:41:2
      REM REPLAYGAIN_TRACK_GAIN  -4.50 dB
      REM REPLAYGAIN_TRACK_PEAK 0.934723
    TRACK 99 AUDIO
     TITLE "Loppu"
       Performer "5.7.2021-30.6.2022"
     INDEX 01 42:47:17


  TRACK 14 AUDIO
       Performer "YLE"
      TITLE "Iltavirren esittely"
     INDEX 01 42:52:30
      REM REPLAYGAIN_TRACK_GAIN  -2.01 dB
      REM REPLAYGAIN_TRACK_PEAK 0.585938
    TRACK 99 AUDIO
     TITLE "Loppu"
       Performer "5.7.2021-30.6.2022"
     INDEX 01 43:0:33


  TRACK 15 AUDIO
       Performer "Mantovani"
      TITLE "Mentyä yön"
     INDEX 01 43:2:8
      REM REPLAYGAIN_TRACK_GAIN  -6.15 dB
      REM REPLAYGAIN_TRACK_PEAK 1.000000
    TRACK 99 AUDIO
     TITLE "Loppu"
       Performer "5.7.2021-30.6.2022"
     INDEX 01 45:15:7


  TRACK 16 AUDIO
       Performer "Danny"
      TITLE "Anak (Lapselleni)"
     INDEX 01 45:18:51
      REM REPLAYGAIN_TRACK_GAIN  -6.92 dB
      REM REPLAYGAIN_TRACK_PEAK 1.000000
    TRACK 99 AUDIO
     TITLE "Loppu"
       Performer "5.7.2021-30.6.2022"
     INDEX 01 48:16:4


  TRACK 17 AUDIO
       Performer "Gabriels"
      TITLE "Blame"
     INDEX 01 48:32:62
      REM REPLAYGAIN_TRACK_GAIN  +7.02 dB
      REM REPLAYGAIN_TRACK_PEAK 0.289276
    TRACK 99 AUDIO
     TITLE "Loppu"
       Performer "5.7.2021-30.6.2022"
     INDEX 01 51:16:19


  TRACK 18 AUDIO
       Performer "Reisijärven kristillisen opiston kuoro"
      TITLE "Pieni iltarukous"
     INDEX 01 51:27:34
      REM REPLAYGAIN_TRACK_GAIN  +0.70 dB
      REM REPLAYGAIN_TRACK_PEAK 0.454041
    TRACK 99 AUDIO
     TITLE "Loppu"
       Performer "5.7.2021-30.6.2022"
     INDEX 01 52:19:40


  TRACK 19 AUDIO
       Performer "YLE"
      TITLE "Iltavirren esittely"
     INDEX 01 52:21:51
      REM REPLAYGAIN_TRACK_GAIN  -6.14 dB
      REM REPLAYGAIN_TRACK_PEAK 0.826508

  TRACK 20 AUDIO
       Performer "Chveneburebi & Lela Nakeuri"
      TITLE "Vardis Shto (Rose branch)"
     INDEX 01 52:35:15
      REM REPLAYGAIN_TRACK_GAIN  +8.96 dB
      REM REPLAYGAIN_TRACK_PEAK 0.411316
    TRACK 99 AUDIO
     TITLE "Loppu"
       Performer "5.7.2021-30.6.2022"
     INDEX 01 55:41:67


  TRACK 21 AUDIO
       Performer "Lea Laven"
      TITLE "Keskikesän valssi"
     INDEX 01 55:46:49
      REM REPLAYGAIN_TRACK_GAIN  +8.17 dB
      REM REPLAYGAIN_TRACK_PEAK 0.296722
    TRACK 99 AUDIO
     TITLE "Loppu"
       Performer "5.7.2021-30.6.2022"
     INDEX 01 59:17:55




  TRACK 22 AUDIO
       Performer "Pihasoittajat"
      TITLE "Astelin kaunista kangasta"
     INDEX 01 59:49:36
      REM REPLAYGAIN_TRACK_GAIN  11.28 dB
      REM REPLAYGAIN_TRACK_PEAK 0.236359
    TRACK 99 AUDIO
     TITLE "Loppu"
       Performer "5.7.2021-30.6.2022"
     INDEX 01 62:36:73


  TRACK 23 AUDIO
       Performer "YLE"
      TITLE "Afro Blue esittelyi"
     INDEX 01 63:10:71
      REM REPLAYGAIN_TRACK_GAIN  4.66 dB
      REM REPLAYGAIN_TRACK_PEAK 0.290771

  TRACK 24 AUDIO
       Performer "Abbey Lincoln"
      TITLE "Afro Blue"
     INDEX 01 63:19:18
      REM REPLAYGAIN_TRACK_GAIN  5.13 dB
      REM REPLAYGAIN_TRACK_PEAK 0.431183
    TRACK 99 AUDIO
     TITLE "Loppu"
       Performer "5.7.2021-30.6.2022"
     INDEX 01 66:38:18


  TRACK 25 AUDIO
       Performer "Gjallarhorn"
      TITLE "I riden så"
     INDEX 01 66:48:57
      REM REPLAYGAIN_TRACK_GAIN  13.87 dB
      REM REPLAYGAIN_TRACK_PEAK 0.142029
    TRACK 99 AUDIO
     TITLE "Loppu"
       Performer "5.7.2021-30.6.2022"
     INDEX 01 71:24:39


  TRACK 26 AUDIO
       Performer "Kate Burge, Ruth Hazleton & Luke Plumb"
      TITLE "The Newgate Stone"
     INDEX 01 71:50:14
      REM REPLAYGAIN_TRACK_GAIN  10.96 dB
      REM REPLAYGAIN_TRACK_PEAK 0.238464
    TRACK 99 AUDIO
     TITLE "Loppu"
       Performer "5.7.2021-30.6.2022"
     INDEX 01 74:43:38


MOD Edit: Move CUE to CODE box
MOD Note: CUE-Sheet Syntax: All track numbers must be between 1 and 99 inclusive. The first track number can be greater than one, but all track numbers after the first must be sequential (e.g. 10, 11, 12...). 1, 99, 2, 99, 3... is not valid track order syntax.
Title: Re: foobar2000 v2.0 bugs
Post by: bnnm on 2023-04-30 09:21:02
Quote from: marc2k3 on
If you're using github actions to upload artifacts/releases, The 7zip command line tool (7z) is included on the windows runners. I use it...

https://github.com/marc2k3/foo_queue_viewer/blob/1ec65ec995c9d20b7a67810d63800f21bcbd0d6a/.github/workflows/build.yml#L59
True that I can change the build scripts/tools around this (though this powershell powershell script is mainly for local builds), but seems like an unintended behavior, that other devs may encounter sooner or later. Or if \ paths aren't supported some error would be helpful (got me stumped for a while...).
Title: Re: foobar2000 v2.0 bugs
Post by: pqyt on 2023-04-30 16:18:23
My title formatting code for the Album List in 1.6.16 contained CR/LF's to make it easier to edit them in an external editor. They get imported in 2.0 and converted to two underscore ('_') characters.

Not a biggy but it took me a few moments to determine why underscores appeared and removed them from the 2.0 code.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-04-30 22:05:36
I have had a deadlock of foobar2000 using ReFacets. I clicked first item of a column. Playlist view was flickering. No bad shutdown menu, no crash report. Adding "running" file and starting foobar2000 in safe mode didn't solve the problem. Had to replace configuration folder with a backup. Can't reproduce the bug anymore.
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2023-04-30 22:22:17
The graphical glitches in the first image suggest you've got a gdi handle leak. It could be refacets or it could be something else entirely that was to blame. IIRC, there is a per app limit of 10,000 and it could have been interacting with refacets pushed it over the edge.

You can enable a gdi object column in task manager in the details tab or use Process Explorer to check if it happens again.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-04-30 22:57:14
I made a backup of the corrupt configuration folder. I replaced the intact configuration folder with the corrupt one. Deadlock again! Ran Taskmanager, its not a problem with gdi objects.
Title: Re: foobar2000 v2.0 bugs
Post by: TuNk77 on 2023-05-01 00:19:24
Version 2 does not show the total time of selected tracks properly:

(https://i.imgur.com/DzgVlki.png)
Title: Re: foobar2000 v2.0 bugs
Post by: fubar2000 on 2023-05-01 10:29:45
having v2 play issues where streaming from laptop on LAN to oppo udb203 does not play more than the buffer amount of time - if set buffer bigger it plays longer then stops after that time, and shorter gets the same stop...

could not possible be firewall / equipment related I'd thought? Anyone else has similar problem? it stops playing for multiple FLAC files on local SSD... very puzzling!
Title: Re: foobar2000 v2.0 bugs
Post by: wojak on 2023-05-01 15:54:28
Hi,
Windows 10, Foobar2.0x64
two bugs:
 1. when switching stream using new swithcer the audio stream changes but the display on bottom bar and in colums remains unchanged. When changed using old method (right click...) everything changes instantly.
2. Sometimes (in fact quite often) when manually closing foobar everything seems ok but can't restart (reopen) it. After PC restart I get something like "foobar closed with error last time - open in safe mode or normally or ignore" It also appies to 32bit version. Never happened in 1.6.16.
Title: Re: foobar2000 v2.0 bugs
Post by: tor11 on 2023-05-01 21:51:04
"Bring to front when adding new files" does not work (Win7).
Title: Re: foobar2000 v2.0 bugs
Post by: iridescentaudio on 2023-05-02 09:58:49
I just noticed 2.0 being out of beta today. Congrats! Just wondering if this Playback Statistics issue could be investigated?

Quote from: iridescentaudio on
Any chance of taking another look at the Playback Statistics issue of tag writes interrupting playback (https://hydrogenaud.io/index.php/topic,122553.0.html)? IIRC changes were made in the first 2.0 beta so that tag writes didn't apply until track stop or change (perfect), but AFAIK they were rolled back when the component was separated out again. Possibly an oversight?
Title: Re: foobar2000 v2.0 bugs
Post by: wojak on 2023-05-02 21:17:28
Hi, I use FB2.0x64 on Windows10 and lately foobar lost control of its own components - I cant just click on a componet to install it because it lost association and connectong it to Foobar.exe or foobarshell...exe does not work. So the only way to install/update component is manually from the library/components/install. How to fix the association?
Title: Re: foobar2000 v2.0 bugs
Post by: pulbitz on 2023-05-03 13:16:55
I am reporting a bug related to keyboard focus.

1. Copy music files from explorer (Ctrl+C)

2. Paste into foobar2000's playlist window (Ctrl+V)

3. Invoke context menu (Shift+F10) -> The context menu is invoked as if the keyboard focus is on the playlist tab title. In beta versions prior to the 2.0 final version, the context menu was invoked from the playlist.
Title: Re: foobar2000 v2.0 bugs
Post by: BingoMan on 2023-05-03 17:37:30
wojak
Right-click on the fb2k-component file, "Open with" select foobar2000, check "Always open this application for fb2k-component", or Find another application on this computer, find foobar2000.exe open in it. Everything must open, the association must be preserved.
Title: Re: foobar2000 v2.0 bugs
Post by: wojak on 2023-05-03 18:14:00
Quote from: BingoMan on
wojak
Right-click on the fb2k-component file, "Open with" select foobar2000, check "Always open this application for fb2k-component", or Find another application on this computer, find foobar2000.exe open in it. Everything must open, the association must be preserved.
No, it does not. That way foobar puts a component in a playlist and says it can't play it (because it is not an audio file). It does not treat it as a component and does not try to install it.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-05-03 18:34:07
See also: https://hydrogenaud.io/index.php/topic,124091.msg1026476.html#msg1026476
Title: Re: foobar2000 v2.0 bugs
Post by: wojak on 2023-05-03 18:52:35
Quote from: grimes on
See also: https://hydrogenaud.io/index.php/topic,124091.msg1026476.html#msg1026476
Yes, I know how to install component from the library/componets..... but it used to work by just doubleclicking on a component...not it does not. That is why I reported a bug in FB2.0. I hope it was not deliberately changed because it was easier to just click on sometimes many new components than soing it all the long way.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-05-03 19:01:22
Yes, seems to be a bug.
Title: Re: foobar2000 v2.0 bugs
Post by: tommitytom on 2023-05-04 02:14:09
New Facets UI seems to completey lock up the UI when returning a large amount of search results.  Also seems to happen with the regular media search but not to the same extent as this.  Collection is roughly 1.26tb, 82k tracks.  32bit version.  I recorded a gif, added a visualizer so you can see it lock up:
https://imgur.com/a/KmEh37v
Title: Re: foobar2000 v2.0 bugs
Post by: Case on 2023-05-04 06:50:36
Quote from: wojak on
Hi, I use FB2.0x64 on Windows10 and lately foobar lost control of its own components - I cant just click on a componet to install it because it lost association and connectong it to Foobar.exe or foobarshell...exe does not work. So the only way to install/update component is manually from the library/components/install. How to fix the association?

The component installation from shell by double click requires special parameters to foobar2000. I suspect people having problems with it have used portable foobar2000 installations and have manually tried to associate .fb2k-component. Doing that writes invalid registry keys that prevent the proper parameters from getting passed to the player. I'll try to make future foobar2000 installer able to fix the registration automatically.

But for now you should be able to fix it manually with Registry Editor (regedit.exe) by deleting the following registry keys:
HKEY_CURRENT_USER\SOFTWARE\Classes\.fb2k-component
HKEY_CURRENT_USER\SOFTWARE\Classes\fb2k-component_auto_file
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.fb2k-component
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-05-04 07:49:49
Quote from: grimes on
I have had a deadlock of foobar2000 using ReFacets. I clicked first item of a column. Playlist view was flickering. No bad shutdown menu, no crash report. Adding "running" file and starting foobar2000 in safe mode didn't solve the problem. Had to replace configuration folder with a backup. Can't reproduce the bug anymore.
Further investigation: Seems to be a problem after resizing Album cover column in playlist viewer.

Here is a video during resizing Album cover column in playlist viewer:

Title: Re: foobar2000 v2.0 bugs
Post by: wojak on 2023-05-04 15:55:40
Quote from: Case on
Quote from: wojak on
Hi, I use FB2.0x64 on Windows10 and lately foobar lost control of its own components - I cant just click on a componet to install it because it lost association and connectong it to Foobar.exe or foobarshell...exe does not work. So the only way to install/update component is manually from the library/components/install. How to fix the association?

The component installation from shell by double click requires special parameters to foobar2000. I suspect people having problems with it have used portable foobar2000 installations and have manually tried to associate .fb2k-component. Doing that writes invalid registry keys that prevent the proper parameters from getting passed to the player. I'll try to make future foobar2000 installer able to fix the registration automatically.

But for now you should be able to fix it manually with Registry Editor (regedit.exe) by deleting the following registry keys:
HKEY_CURRENT_USER\SOFTWARE\Classes\.fb2k-component
HKEY_CURRENT_USER\SOFTWARE\Classes\fb2k-component_auto_file
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.fb2k-component


Hi,
I deleted those 3 keys and now the components are not associated with anything. If I double-click on a component Windows asks to choose a program to open it. What should I do next to make foobar-component-updater use it automatically?
Title: Re: foobar2000 v2.0 bugs
Post by: Case on 2023-05-05 06:25:55
Do you not have standard installation of foobar2000? The installer writes association keys to HKEY_LOCAL_MACHINE and the existing associations should now be used when the incorrect values from current user's keys are gone.
Run the installer and just install the player again. That will recreate the associations.
Title: Re: foobar2000 v2.0 bugs
Post by: alekssmitt on 2023-05-05 07:11:43
The foobar2000-x64_v2.0 version does not work with the minilyrics plugin "foo_ui_minilyrics.dll" because the latter is only for the x32 system.
Is there any way to reconcile them?
Title: Re: foobar2000 v2.0 bugs
Post by: manudevil on 2023-05-05 09:58:18
Have you tried foo_openlyrics?
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-05-05 10:48:34
Or ESLyric: https://hydrogenaud.io/index.php/topic,122571.0.html
Title: Re: foobar2000 v2.0 bugs
Post by: wojak on 2023-05-05 15:14:55
Quote from: Case on
Do you not have standard installation of foobar2000? The installer writes association keys to HKEY_LOCAL_MACHINE and the existing associations should now be used when the incorrect values from current user's keys are gone.
Run the installer and just install the player again. That will recreate the associations.
Thanks, reinstalling FB2x64 fixed the "plugin association".
Title: Re: foobar2000 v2.0 bugs
Post by: smokowir on 2023-05-06 09:41:53
after installing version 2.0, foobar shuts down when trying to connect via the Foobar Con pro app that is on the Android phone. no problem so far. I sent the report.
Title: Re: foobar2000 v2.0 bugs
Post by: watcherhd on 2023-05-06 15:48:10
Foobar 2.0 x64 - just noticed that volume gets considerably lower after forwarding a track at the seekbar - checked with RG on and off, with ASIO and WASAPI exclusive outputs - same effect - just touch the seekbar - volume goes down.
Checked on two different output devices, on 1.6.16 everything is OK.
Title: Re: foobar2000 v2.0 bugs
Post by: Melchior on 2023-05-06 16:05:47
Quote from: watcherhd on
Foobar 2.0 x64 - just noticed that volume gets considerably lower after forwarding a track at the seekbar - checked with RG on and off, with ASIO and WASAPI exclusive outputs - same effect - just touch the seekbar - volume goes down.
Checked on two different output devices, on 1.6.16 everything is OK.
I tried what you said with v2 x86_32bit and it works fine as far as I could try..
so it would be a x86_64bit issue.
Title: Re: foobar2000 v2.0 bugs
Post by: watcherhd on 2023-05-06 18:04:39
Quote from: Melchior on
I tried what you said with v2 x86_32bit and it works fine as far as I could try..
so it would be a x86_64bit issue.

I'll wait for someone to confirm or totally decline this - if my case is local - I will try and reinstall the player again from scratch (this one is updated from beta versions).
Also forgot to mention - Windows 11 64-bit.
Title: Re: foobar2000 v2.0 bugs
Post by: Fabcore on 2023-05-06 22:04:40
Hi, i think there's a graphic (fonts) bug with the memory when handling quite a lot of files (like 4000 items and more approx) in a playlist after some long period of passed time like a couple of days or so.
It's a visual thing, the fonts change from some selected to the "system font" like the old times in PC with programs with very limited RAM and speeds...

I'm on windows 10 22h2.

Here in the pic of the glitch
Title: Re: foobar2000 v2.0 bugs
Post by: watcherhd on 2023-05-07 00:38:40
Quote from: watcherhd on
Quote from: Melchior on
I tried what you said with v2 x86_32bit and it works fine as far as I could try..
so it would be a x86_64bit issue.

I'll wait for someone to confirm or totally decline this - if my case is local - I will try and reinstall the player again from scratch (this one is updated from beta versions).
Also forgot to mention - Windows 11 64-bit.

Switching between outputs restores the volume until seekbar is touched.
Title: Re: foobar2000 v2.0 bugs
Post by: sveakul on 2023-05-07 03:52:41
Quote from: watcherhd on
Switching between outputs restores the volume until seekbar is touched.
In Preferences/Playback/Output, under "Fading" is there anything enabled for "Seek"?  If so, zero it out, or uncheck the "Enable" box altogether.
Title: Re: foobar2000 v2.0 bugs
Post by: watcherhd on 2023-05-07 11:04:17
Quote from: sveakul on
Quote from: watcherhd on
Switching between outputs restores the volume until seekbar is touched.
In Preferences/Playback/Output, under "Fading" is there anything enabled for "Seek"?  If so, zero it out, or uncheck the "Enable" box altogether.

No - fading is off an volume goes down and not coming back until you switch output device and back (or maybe the next track is playing - I should check)
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-05-07 11:37:48
Is a DSP set for one of the output devices?
Title: Re: foobar2000 v2.0 bugs
Post by: Case on 2023-05-07 11:43:14
@watcherhd - this is random but you don't happen to use some loudness-enhancing VSTs? In other threads people have complained that seeking causes VST to get bypassed.
Title: Re: foobar2000 v2.0 bugs
Post by: watcherhd on 2023-05-07 12:09:24
del
Title: Re: foobar2000 v2.0 bugs
Post by: watcherhd on 2023-05-07 12:10:53
Quote from: Case on
@watcherhd - this is random but you don't happen to use some loudness-enhancing VSTs? In other threads people have complained that seeking causes VST to get bypassed.

@Case, you are right - it's VST EasyQ_v10.07 connected with new VST adapter plugin by Peter that seeking causes to get bypassed.

Too bad - on 1.6.16 with very old VST 2.4 adapter - © 2011 Yegor Petrov it doesn't happen.

But at least we know that it's not new Foobar's poblem.
Title: Re: foobar2000 v2.0 bugs
Post by: un autre moi on 2023-05-07 12:32:18
Unfortunately I had to return to v1.6.16 as v2.0 never loaded my whole music library, even after several attempts to rescan, the status of my drive F remained “Reading tags…”, actually I haven’t noticed this status in the previous versions of foobar2000, this might be a culprit.
Title: Re: foobar2000 v2.0 bugs
Post by: watcherhd on 2023-05-07 12:49:39
@grimes - it was VST - but not in device list - just in general DSP chain :)
Title: Re: foobar2000 v2.0 bugs
Post by: Erich_2 on 2023-05-07 18:22:05
What’s going on with ReFacets "Folder"?

ReFacets "Folder" = $directory(%path%)
doesn’t work anymore like Facets, shows pointless or a mix of folders and albums!  :(
All tests were made with clean installed portable installations (V.2 32bit on Win11).
I restructured, used fewer folders, the result was always a mess.

ReFacets "Genre" works perfect. But this is unusable for me because there are hundreds or maybe thousand of different genres.

I have about 100000 song titles sorted into Albums.  Is that too much for V.2.0? It was from the beginning, has affected all beta versions until V. 2.0.
X
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2023-05-07 18:42:52
The folder columns in original facets never used title formatting. You won't find a preference where you can edit them.

It's just like you can't edit the folder structure view in album list either. A special API for getting the relative path of a track which discards your watched folder(s) from the beginning is used and there is no title formatting equivalent to this. You can probably hack around with $replace and $substr and maybe achieve something similar.

edit: as an example this works for the first folder column where my watched folder is E:\Music

Code: [Select]
$puts(relative_path,$replace(%path%,E:\Music\,))$substr($get(relative_path),0,$sub($strstr($get(relative_path),\),1))

Now you figure out the code for the 2nd column and so on....
Title: Re: foobar2000 v2.0 bugs
Post by: Erich_2 on 2023-05-07 19:55:36
@marc2k3
Thanks, Ok, I did it for the first folder column where my watched folder is D:\Musikbibliothek.
Code: [Select]
$puts(relative_path,$replace(%path%,D:\Musikbiliothek\,))$substr($get(relative_path),0,$sub($strstr($get(relative_path),\),1))
But when I go to a folder, only the name of the same folder minus 1 letter appears in the second folder column.
Code: [Select]
$puts(relative_path,$replace(%path%,D:\Musikbiliothek\,))$substr($get(relative_path),0,$sub($strstr($get(relative_path),\),2))
And in the third folder column only the name of the same folder minus 2 letters appears.
Code: [Select]
$puts(relative_path,$replace(%path%,D:\Musikbiliothek\,))$substr($get(relative_path),0,$sub($strstr($get(relative_path),\),3))
X

What can I do? For a normal user this is a horror code. I only can copy and paste. ;-)
This Facets-Folder-Thing is the only reason why I use Foobar2000 since 15 years  :-((((

I just can't imagine being the only one who sorts by at least 2 or 3 folders.
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2023-05-07 21:25:16
Yeah, you'll never figure it out when you don't even understand what the code does. First it has to discard the watched folder path. It then had to look for the first \ in the resulting string and then that has to be discarded by subtracting 1 from its position.

The 2nd pane has to discard the watched folder and the entire folder name displayed in the first pane And then of course you have to find the next slash and discard the text after it. I can hardly blame anyone for not knowing how to do this. It's not easy.

But it does highlight the vast difference between the super-magic folder columns in original facets compared to title formatting. I feel I've made that point.  :))
Title: Re: foobar2000 v2.0 bugs
Post by: sacdman on 2023-05-08 04:07:20
Having my own issues with foobar... some plugins won't work with the 64bit v2.0 like WSH panel mod, I have included an image of my layout. i use DUI and would really appreciate this kind of simpler look and feel. Don't really need anything more advanced than this. I am also attaching the list of plugins I use. Thanks. I have attempted to use 2.0 32 bit as well and get some odd behavior with the items listed in my library. Others have noted this as well. Thanks.
Title: Re: foobar2000 v2.0 bugs
Post by: seomanakasimon on 2023-05-08 05:56:59
Quote from: un autre moi on
Unfortunately I had to return to v1.6.16 as v2.0 never loaded my whole music library, even after several attempts to rescan, the status of my drive F remained “Reading tags…”, actually I haven’t noticed this status in the previous versions of foobar2000, this might be a culprit.

My sacd 5.1 map only became visible when I put it in a extra folder.
Ie; f:\sacd\sacd 5.1
Title: Re: foobar2000 v2.0 bugs
Post by: Erich_2 on 2023-05-08 08:57:33
Quote from: marc2k3 on
Yeah, you'll never figure it out when you don't even understand what the code does. First it has to discard the watched folder path. It then had to look for the first \ in the resulting string and then that has to be discarded by subtracting 1 from its position.

The 2nd pane has to discard the watched folder and the entire folder name displayed in the first pane And then of course you have to find the next slash and discard the text after it. I can hardly blame anyone for not knowing how to do this. It's not easy.

But it does highlight the vast difference between the super-magic folder columns in original facets compared to title formatting. I feel I've made that point.  :))

Thanks for the explanation, too bad.., back to Facets...
But why is there in ReFacets: Folder=$directory(%path%)?
Title: Re: foobar2000 v2.0 bugs
Post by: Case on 2023-05-09 06:24:40
I wonder if I'm missing something, but you should be able to achieve what you are after quite easily with ReFacets, @Erich_2.

The pre-existing Folder definition "$directory(%path%)" gives just the exact folder name the track is in. To get the name of the folder higher up in the path tree, you can use string "$directory(%path%,2)". And to get the parent folder of that, use "$directory(%path%,3)", and so on. Just define as many folder depths as you need.

As an example if you have the following file:
Code: [Select]
D:\Musikbiliothek\Neue Deutsche Welle\Falco\1985\Falco 3\01. Rock Me Amadeus.flac
$directory(%path%) will return "Falco 3"
$directory(%path%,2) will return "1985"
$directory(%path%,3) will return "Falco"
$directory(%path%,4) will return "Neue Deutsche Welle"
$directory(%path%,5) will return "Musikbiliothek"
$directory(%path%,6) would return "Missing tag" as you are out of folders.
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2023-05-09 07:23:30
Quote from: Case on
I wonder if I'm missing something

That could work but walking up the path from right to left does depend on the folder structure being X folders deep for every single track in the library otherwise it's going to break down.
Title: Re: foobar2000 v2.0 bugs
Post by: Erich_2 on 2023-05-09 08:56:12
Till beta 26 ReFacets I used Folders with „SpecialFolder“ as a workaround: N= 2,3,4,5,6 or 7
SpecialFolder = $directory(%path%,$sub($len(%path%),$len($replace(%path%,\,,|,,/,)),N))
From Beta 27 on it didn't work anymore.

$directory(%path%) - $directory(%path%,2) - $directory(%path%,x) etc. also brings a confusion.
The only thing what really works, is (only in the first column):
$puts(relative_path,$replace(%path%,D:\Musikbiliothek\,))$substr($get(relative_path),0,$sub($strstr($get(relative_path),\),1))

But like Mick Jagger sings: I can't get no Satisfaction.
There is a Path in "Media Library". Putting this path back into a formula is not acceptable to the user.





Title: Re: foobar2000 v2.0 bugs
Post by: a3aan on 2023-05-10 17:12:09
This works for me: $directory(%path%,$sub($sub($len(%path%),$len($replace(%path%,\,))),N)).
Title: Re: foobar2000 v2.0 bugs
Post by: Erich_2 on 2023-05-10 21:47:28
Quote from: a3aan on
This works for me: $directory(%path%,$sub($sub($len(%path%),$len($replace(%path%,\,))),N)).

Great! Good workaround!
Thank you Sir!
Title: Re: foobar2000 v2.0 bugs
Post by: CSwa913102 on 2023-05-11 04:53:01
"Dark mode not supported on this system"

Edition   Windows 10 Home
Version   22H2
Title: Re: foobar2000 v2.0 bugs
Post by: lender1257 on 2023-05-13 11:43:12
v2, 32-bit

how to change the font-size in peter's playlist search.
the setting will not be applied when switching to v2.

thanks
Title: Re: foobar2000 v2.0 bugs
Post by: Case on 2023-05-13 13:29:34
Quote from: CSwa913102 on
"Dark mode not supported on this system"
Have you perhaps changed foobar2000 to be run under compatibility mode of some older OS version?
Title: Re: foobar2000 v2.0 bugs
Post by: lender1257 on 2023-05-13 16:45:38
Quote from: lender1257 on
v2, 32-bit

how to change the font-size in peter's playlist search.
the setting will not be applied when switching to v2.

thanks
setting of the font size found.
but cannot be changed. Bug.
Title: Re: foobar2000 v2.0 bugs
Post by: Irama on 2023-05-13 17:32:54
Using v. 2.0 (stable) or 2.1 beta (64 bits), interface is temporarily freezing on my side when I update tags, while music is still playing flawlessly. It can last from a few seconds (if I update tags of a single album) to a few minutes (for a bunch of albums using masstager) and everything will be fine again after all operations are completed. Meanwhile CPU usage is somewhere between 20 and 50 %. Same thing happens while new music is being downloaded and automatically scanned for being added in media library. My computer is "a bit" old (see specs below) and music library quite big.

This didn't happen with previous versions. I don't know anything about computing, but I guess this has something to do with foobar now being unable to forget new tag updates after crash (which is nice) and that this is not a bug but a consequence of choices made. Hence I'd like to know if there were ways to shorten this temporary freeze for old computers ran by old people like me... Any help appreciated!

Of course I use some components, mostly JScript Panel samples, but I guess they affect RAM more than CPU, and problems were similar without them installed.

Here's my configuration:

CPU   Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz   3.60 GHz
RAM   16,0 Go
Foobar on SDD
Music library (over 18,000 albums; 8 TB data) on 3 different supposedly healthy HDD
Windows 10

Title: Re: foobar2000 v2.0 bugs
Post by: Majestyk on 2023-05-16 10:50:32
I'm not sure if this has been mentioned, but the music folder path (with V2.0 in portable mode) becomes corrupt if you move the FB2K folder to another directory. It will say "The system cannot find the path specified." 

My music folder is in D:\Music but it actually added another folder to the path when I moved FB2K. So the path became D:\Darkone\Music.

Title: Re: foobar2000 v2.0 bugs
Post by: Majestyk on 2023-05-17 00:05:46
Ok, it turns out the problem might be my end and I can't figure out why. Something is corrupting the path of one of my portable themes, whenever I move the FB2K portable folder to another directory. Even if I copy it and paste it in the same dir, it becomes corrupt.  But it doesn't do this on the older Foobar (V1.6.16). Only V2.

So all my themes are fine on both 32Bit versions of FB2K when moving them  But one theme does not on V2.0, only.

I don't know how I'm going to begin trouble shooting this.

Update: Ok, so I made a fresh portable install of V2 32 bit and copied the profile files of my 'tainted' theme to the new install. (I did not copy files like playlists-v2.0). And now it works fine when moving around.  I'm still going to play around with the 'tainted' version and see why it's doing that.

Update 2: I spoke to soon. It's doing it again.
Title: Re: foobar2000 v2.0 bugs
Post by: Majestyk on 2023-05-17 01:15:28
One more update. The "bug" seems to happen randomly. When it happens , the path shows up as "...\...\Music Files". When it doesn't, the path shows up as "D:\Music Files". I don't think it has anything to do with my theme (IE: components).



Title: Re: foobar2000 v2.0 bugs
Post by: josemescud on 2023-05-19 20:18:04
I use Foobar 64-bit
I need to know in Masstagger how to import.
I click on the "Import From File" button and mark an .mts file but nothing happens (Image1).
I also need to know if it is possible to sort the scripts. (Image2)
Title: Re: foobar2000 v2.0 bugs
Post by: josemescud on 2023-05-23 12:50:21
I want to do a Query search that will list the tracks whose title contains " (double quotation mark)

I write this script:

Code: [Select]
%title% HAS "
but it doesn't work and it lists the complete library
I guess it must be a reserved character that requires a special syntax
Title: Re: foobar2000 v2.0 bugs
Post by: Porcus on 2023-05-23 13:23:12
Quote from: josemescud on
I guess it must be a reserved character that requires a special syntax
... and should not be posted in a thread about bugs. It even warns you with a bubble saying "Invalid filter expression".
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-05-23 13:55:38
You can replace " with ' in title tag: Masstagger | Format values from other fields
(Please check output preview)

TITLE
Code: [Select]
$replace(%title%,'"','')
Title: Re: foobar2000 v2.0 bugs
Post by: Irama on 2023-05-23 19:54:41
Quote from: Irama on
Using v. 2.0 (stable) or 2.1 beta (64 bits), interface is temporarily freezing on my side when I update tags, while music is still playing flawlessly. It can last from a few seconds (if I update tags of a single album) to a few minutes (for a bunch of albums using masstager) and everything will be fine again after all operations are completed. Meanwhile CPU usage is somewhere between 20 and 50 %. Same thing happens while new music is being downloaded and automatically scanned for being added in media library. My computer is "a bit" old (see specs below) and music library quite big.

This didn't happen with previous versions. I don't know anything about computing, but I guess this has something to do with foobar now being unable to forget new tag updates after crash (which is nice) and that this is not a bug but a consequence of choices made. Hence I'd like to know if there were ways to shorten this temporary freeze for old computers ran by old people like me... Any help appreciated!

Of course I use some components, mostly JScript Panel samples, but I guess they affect RAM more than CPU, and problems were similar without them installed.

Here's my configuration:

CPU   Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz   3.60 GHz
RAM   16,0 Go
Foobar on SDD
Music library (over 18,000 albums; 8 TB data) on 3 different supposedly healthy HDD
Windows 10

Coming back on this... It seems that foobar is rebuilding the entire library each time I make any change on the metadatas or doing anything else that could affect the library (adding an album for instance). It is pretty annoying since heavy changes can freeze the program for tenth of minutes. Tasks manager tells me that foobar uses up to 40 % of CPU ressources (usually 25-30 % and less than 1 % in normal use). I tried everything I could with Windows, such as giving foobar "real time access" with no results. I'm a bit desperate about this...
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-05-23 20:25:34
Did you try a fresh portable foobar2000 2.0/2.1 installation and read in Media Library (8TB, that will take some time).
Title: Re: foobar2000 v2.0 bugs
Post by: Irama on 2023-05-23 20:54:21
I did with 2.0 32 bits version with no results. Will try again tonight with 2.1 64 bits.
Title: Re: foobar2000 v2.0 bugs
Post by: Irama on 2023-05-24 12:56:58
Did a perfectly clean portable install of v. 2.1. Library scan has been quite fast (maybe 20-30 minutes) but problem remains the same: foobar freezes after editing tags, adding albums, etc...

I also notice that RAM use is quite high... 1200 to 2300 MB but that might be because I use Smooth Browser.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-05-24 13:06:45
Do you have error messages in console? View | Console.
Title: Re: foobar2000 v2.0 bugs
Post by: Irama on 2023-05-24 13:24:56
No errors and everything seems to load quite fast, including library.
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-05-24 13:28:44
Do you have errors in Preferences | Media Library | Show errors?
Title: Re: foobar2000 v2.0 bugs
Post by: Irama on 2023-05-24 13:35:08
No error neither...
Title: Re: foobar2000 v2.0 bugs
Post by: grimes on 2023-05-24 13:41:15
Sorry, that I can't help you. You could try to read in parts of the Media Library (one drive for example) and test. But that's a lot of work. Maybe its a bug in foobar2000. I don't know.
Title: Re: foobar2000 v2.0 bugs
Post by: Irama on 2023-05-24 14:47:02
Thanks for trying to help anyway, I appreciate! Trying to read one drive at a time is not a bad idea, I'll do it when I have time.
Title: Re: foobar2000 v2.0 bugs
Post by: Tortie on 2023-05-25 07:54:58
FB2K 2.0 is missing the option to specify push or event for exclusive mode. Push was useful for use with older asynchronous DAC processors.

Overall, my view of 2.0 is that it lacks polish and has a unattractive GUI. It looks like a step backwards for Foobar development. Not sure what the goal of 2.0 or what purpose the project's existence serves. I hope version 1.0 continues to see updates. 2.0 should be shelved for now.
Title: Re: foobar2000 v2.0 bugs
Post by: Air KEN on 2023-05-25 13:54:07
@Tortie

not a bug.

foobar2000 change log
https://www.foobar2000.org/changelog

foobar2000 v1.6（2020-09-02）
> Default output mode is now WASAPI shared.

Output: default

foobar2000 v1.6.7 (2021-05-20)
> Built-in WASAPI exclusive output.

Output: device [exclusive]
------
Different people have different tastes in UI.
I have been using Default UI.
It's been a text editor style UI for a long time.
I like Windows 11 + foobar2000 v2.0 32bit 64bit.

Title: Re: foobar2000 v2.0 bugs
Post by: anamorphic on 2023-05-25 14:37:17
Quote from: Tortie on
FB2K 2.0 is missing the option to specify push or event for exclusive mode.
File > Preferences > Advanced > Playback > enable 'Exclusive output overrides' > disable 'Use event'. = Push
Title: Re: foobar2000 v2.0 bugs
Post by: Remedial Sound on 2023-05-25 21:18:21
There is a feature (Default UI, Playlist View) from 1.X that's gone missing as far as I can tell.

In 1.6.16 and earlier, if I drag a playlist selection to the column header bar (as in the attached screenshot), it will remove the selected tracks from their position in the playlist and drop them at the end of the playlist.  I'd very much like to see this functionality return, it is super useful in curating playlists - e.g., after having just listened to an album and deciding you want to keep it "on rotation."
Title: Re: foobar2000 v2.0 bugs
Post by: zhouy@outlook.com on 2023-05-26 03:27:32
Was there any change with how foobar deals with relative file paths in the fpl files with v2.0?  I always keep my foobar2000.exe in the root directory of my music folder, this way I could just sync my music with OneDrive between computers.  Once I upgraded to v2.0, when I try to add the .\ path to the monitoring folders it always just fills in an absolute path.
Title: Re: foobar2000 v2.0 bugs Quicksearch
Post by: JCKeanu on 2023-05-26 12:34:10
Hi,
i update to V2.0x32 portable
then i missing Library - Quicksearch, i update to 1.0.6
but its still missing in Installed media library viewers
in v1.6.8 its called Quick Seach Toolbar - foo_quicksearch v3.4
in v2.0 its called Qsearch - foo_qsearch v1.06
thx
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2023-05-26 14:19:24
qsearch is not a replacement for quicksearch. Since you're using 32bit, you can continue to use the original component.
Title: Re: foobar2000 v2.0 bugs
Post by: Irama on 2023-05-29 14:04:26
Quote from: Irama on
Quote from: Irama on
Using v. 2.0 (stable) or 2.1 beta (64 bits), interface is temporarily freezing on my side when I update tags, while music is still playing flawlessly. It can last from a few seconds (if I update tags of a single album) to a few minutes (for a bunch of albums using masstager) and everything will be fine again after all operations are completed. Meanwhile CPU usage is somewhere between 20 and 50 %. Same thing happens while new music is being downloaded and automatically scanned for being added in media library. My computer is "a bit" old (see specs below) and music library quite big.

This didn't happen with previous versions. I don't know anything about computing, but I guess this has something to do with foobar now being unable to forget new tag updates after crash (which is nice) and that this is not a bug but a consequence of choices made. Hence I'd like to know if there were ways to shorten this temporary freeze for old computers ran by old people like me... Any help appreciated!

Of course I use some components, mostly JScript Panel samples, but I guess they affect RAM more than CPU, and problems were similar without them installed.

Here's my configuration:

CPU   Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz   3.60 GHz
RAM   16,0 Go
Foobar on SDD
Music library (over 18,000 albums; 8 TB data) on 3 different supposedly healthy HDD
Windows 10

Coming back on this... It seems that foobar is rebuilding the entire library each time I make any change on the metadatas or doing anything else that could affect the library (adding an album for instance). It is pretty annoying since heavy changes can freeze the program for tenth of minutes. Tasks manager tells me that foobar uses up to 40 % of CPU ressources (usually 25-30 % and less than 1 % in normal use). I tried everything I could with Windows, such as giving foobar "real time access" with no results. I'm a bit desperate about this...

Coming back again on this, just to let you know that I found the culprit: Smooth Browser (JScript Panel script). Removed it and everything is now working fine, except relatively high RAM use.
Title: Re: foobar2000 v2.0 bugs
Post by: ironmine on 2023-05-30 03:29:54
I have Windows 7 (64-bit).

I upgraded Foobar to 2.1 (64-bit) from 1.16.

Foobar cannot load now George Yohng's VST Wrapper (http://www.yohng.com/software/foobarvst.html).
The error message says: "Failed to load DLL: foo_dsp_vstwrap.dll.  Reason: Not a valid Win32 application."

What should I do? How to make this VST wrapper compatible with the newest version of Foobar? I need this plugin very much as I used it to connect to a VST host program in which I used lots of VST plugins.

Thank you for any advice.

PS: I wish Foobar had a way to connect to VST plugins as one of its standard features to harness the power of a multitude of VST plugins that are out there...

Title: Re: foobar2000 v2.0 bugs
Post by: Gus. on 2023-05-30 04:01:33
That VST Wrapper is 32-bit, try it on a 32-bit version of foobar2000.
Also try this component: https://www.foobar2000.org/components/view/foo_dsp_vst3
Allows VST effects to be used as DSPs in foobar2000. Supported processor architectures: x86 32-bit, x86 64-bit.
Title: Re: foobar2000 v2.0 bugs
Post by: sveakul on 2023-05-30 04:51:03
Get the new VST host plugin linked to by Gus, it blows the old Yohng one out of the water.  Written by Peter, can host 32 or 64-bit VST2/3 plugins independent of the player architecture, etc.  Basically uncrashable.
Title: Re: foobar2000 v2.0 bugs
Post by: Jinse on 2023-05-30 08:09:45
2.0, 2.1 have problems with the support of the tak format, the older tak format cannot be properly decoded with the built-in ffmpeg, but it can be played correctly using the tak decoder plugin (the same is true for other media players that use ffmpeg, such as mpv)
Title: Re: foobar2000 v2.0 bugs
Post by: Porcus on 2023-05-30 08:42:47
Quote from: Jinse on
2.0, 2.1 have problems with the support of the tak format, the older tak format cannot be properly decoded with the built-in ffmpeg, but it can be played correctly using the tak decoder plugin (the same is true for other media players that use ffmpeg, such as mpv)
Does it give the proper error message?
(If you want to use TAK, why not convert to new TAK?)
Title: Re: foobar2000 v2.0 bugs
Post by: Bogozo on 2023-05-30 16:32:59
Quote from: Jinse on
the older tak format
What version exactly?
It would be good idea to submit bug to ffmpeg.
Title: Re: foobar2000 v2.0 bugs
Post by: XTplank on 2023-06-02 05:17:05
i don't know if this is a bug or intentional but updating to 2.0 64 bit stable appears to leave the old 1.6.x version folders/shortcuts/etc. intact though you can no longer uninstall it from windows' app list. is it safe to delete the old folders or best to just leave them alone? i guess future releases will clear them eventually?
Title: Re: foobar2000 v2.0 bugs
Post by: Case on 2023-06-02 11:03:23
The 64-bit foobar2000 installer intentionally doesn't touch the 32-bit installation. Though shortcut icons obviously get overwritten by the latest installation.

It would be best to uninstall the 32-bit version before installing the 64-bit player. But you can still do it later. Unfortunately I learned too late that the modern side "Apps and Features" doesn't list both bitness variants, but the "Programs and Features" option in Control Panel can do it just fine.
Alternatively you can enter the old directory under Program Files and manually launch the uninstall.exe from there.
Do not just delete the directory, otherwise the registry will be left with unwanted and invalid entries.
Title: Re: foobar2000 v2.0 bugs
Post by: XTplank on 2023-06-02 12:38:48
Quote from: Case on
The 64-bit foobar2000 installer intentionally doesn't touch the 32-bit installation. Though shortcut icons obviously get overwritten by the latest installation.

It would be best to uninstall the 32-bit version before installing the 64-bit player. But you can still do it later. Unfortunately I learned too late that the modern side "Apps and Features" doesn't list both bitness variants, but the "Programs and Features" option in Control Panel can do it just fine.
Alternatively you can enter the old directory under Program Files and manually launch the uninstall.exe from there.
Do not just delete the directory, otherwise the registry will be left with unwanted and invalid entries.
ah, that's why. i forgot the original control panel shows a more complete list. I can confirm this works, 1.6 is removed and the 64-bit 2.0 version is unaffected. I also realized the separate installs would help some people with 32-bit only plugins, not realizing the 64-bit version don't work with them, and can promptly revert versions. I installed the 64-bit version even while the old version was still installed because it was recommended to do so by the official wiki and the change log implied it didn't really matter. and also it would save time by being able to import settings, keyboard shortcuts and playlists. just glad i don't have to wrangle regedit and figure out how to clean things there again

thanks a lot
Title: Re: foobar2000 v2.0 bugs
Post by: Melchior on 2023-06-02 13:30:36
Quote from: Case on
The 64-bit foobar2000 installer intentionally doesn't touch the 32-bit installation. Though shortcut icons obviously get overwritten by the latest installation.

It would be best to uninstall the 32-bit version before installing the 64-bit player. But you can still do it later. Unfortunately I learned too late that the modern side "Apps and Features" doesn't list both bitness variants, but the "Programs and Features" option in Control Panel can do it just fine.
Alternatively you can enter the old directory under Program Files and manually launch the uninstall.exe from there.
Do not just delete the directory, otherwise the registry will be left with unwanted and invalid entries.
hmm.. I use a portable style install for easier backups...
if Peter can get the few Kode54 components I use up to speed for 64bit I will upgrade to it.
he did so for foo_gep renaming it to

I intend to install right over the 32bit version if possible,
to keep all my playlists and components intact but for components I will have to do that reinstall and hope it takes the 64bit versions this time...
Title: Re: foobar2000 v2.0 bugs
Post by: kutuzof on 2023-06-03 06:32:20
"Toggle Full-Screen Mode" - does not return the visualization window size.
Title: Re: foobar2000 v2.0 bugs
Post by: Kurayuri on 2023-06-07 16:59:25
Unable to display cover normally after opening .cue in UTF-8.
Given a .cue file and a .flac with embedded cover, if I play .flac directly or play .cue in UTF-8 with BOM, the cover is displayed normally. However, I play .cue in UTF-8 without BOM, the cover won't be displayed, and it will hint "no image".
Title: Re: foobar2000 v2.0 bugs
Post by: vitamusic on 2023-06-07 18:20:13
Do not work with Anubis ASIO Driver
https://www.merging.com/uploads/assets/Installers/25th_Anniversary_HotFix4/RAVENNA_ASIO_13.0.7/MergingRavennaASIODriver_13.0.7_HotFix_Build9134_x64.exe
Merging Technology Support referenced to you for this problem.

Title: Re: foobar2000 v2.0 bugs
Post by: MeMow on 2023-06-08 05:11:13
Issue with streaming DSF AND WAV files over ftp servers
  - Providing a network stream ftp://, a .DSF will play with distorted sound
  - Providing a network stream http:// or https://, a .DSF will play fine
  - DFF files will stream fine over ftp and http/s
  - Providing a network stream ftp://, a .WAV will play as static sound
  - Providing a network stream http:// or https://, a .WAV will play fine
  - FLAC files will stream over ftp or http/s and play fine
There are likely more codecs that have this issue, these are just the ones I have come across and compared.
I can provide examples for clarification...
Title: Re: foobar2000 v2.0 bugs
Post by: Tortie on 2023-06-13 08:58:23
Quote from: anamorphic on
Quote from: Tortie on
FB2K 2.0 is missing the option to specify push or event for exclusive mode.
File > Preferences > Advanced > Playback > enable 'Exclusive output overrides' > disable 'Use event'. = Push

Thank you for the tip!


Quote from: Air KEN on
@Tortie

not a bug.

foobar2000 change log
https://www.foobar2000.org/changelog

foobar2000 v1.6（2020-09-02）
> Default output mode is now WASAPI shared.

Output: default

foobar2000 v1.6.7 (2021-05-20)
> Built-in WASAPI exclusive output.

Output: device [exclusive]
------
Different people have different tastes in UI.
I have been using Default UI.
It's been a text editor style UI for a long time.
I like Windows 11 + foobar2000 v2.0 32bit 64bit.



Understood. In 1.1.16 and earlier versions Foobar provided more granular control of the WASAPI output type in File > Preferences >  Playback > Output > Devices as the below screenshot shows. I was thrown for a loop when those push/event options disappeared in version 2.0.

X
Title: Re: foobar2000 v2.0 bugs
Post by: Defender on 2023-06-15 13:43:26
Please make sure that $char(65279) ZERO-WIDTH SPACE can NOT end up in tags (like %artist%).

Happens with some streams ... example https://playerservices.streamtheworld.com/api/livestream-redirect/SUBLIME_FUNK_DISCO.mp3

Thx
Title: Re: foobar2000 v2.0 bugs
Post by: perdido34 on 2023-06-15 15:45:48
I installed 2.0 (Windows 10) over the previous version. Unlike prior updates, 2.0 did not install over the older version. Instead, I ended up with two separate installations of foobar2000, and 2.0 didn't retain preferences and settings from the prior version, including the ASIO driver and SACD settings.   How about warning users in advance when an update is going to cause this situation?
Title: Re: foobar2000 v2.0 bugs
Post by: Porcus on 2023-06-16 11:47:33
Quote from: Defender on
Please make sure that $char(65279) ZERO-WIDTH SPACE can NOT end up in tags (like %artist%).
Kinda ... why? What is so special about that one that you call it a bug?
Title: Re: foobar2000 v2.0 bugs
Post by: anamorphic on 2023-06-16 12:42:57
^ Also... no thanks. Zero Width Space is useful for tagging same named artists/albums so they get differentiated in the library and get their own Playback Statistics.

Quote from: Defender on
Happens with some streams ...

(Perhaps contact the streamer and ask them to fix their stream? Rather than a foobar fix...)
Title: Re: foobar2000 v2.0 bugs
Post by: Defender on 2023-06-16 14:03:47
Quote from: Porcus on
Quote from: Defender on
Please make sure that $char(65279) ZERO-WIDTH SPACE can NOT end up in tags (like %artist%).
Kinda ... why? What is so special about that one that you call it a bug?

You don't consider a zero-width space character an illegal character in tags? (You cannot even see it's there).
Same as Character Right-To-Left Override and Character Left-To-Right Override.

IMO it should be stripped on the lowest level (foobar itself), so it does not have to be done in all (third party) plugins and your own code.
Title: Re: foobar2000 v2.0 bugs
Post by: Porcus on 2023-06-16 18:34:41
Just because a particular user (like yourself) don't see the need for a particular character (like zero-width space), does not make it anything close to "illegal". Stop whining bug about something that isn't.
Title: Re: foobar2000 v2.0 bugs
Post by: Defender on 2023-06-16 21:12:07
Quote from: Porcus on
Just because a particular user (like yourself) don't see the need for a particular character (like zero-width space), does not make it anything close to "illegal". Stop whining bug about something that isn't.

Whatever :-) Let's just say we disagree
Title: Re: foobar2000 v2.0 bugs
Post by: pulbitz on 2023-07-30 09:11:48
Quote from: pulbitz on
From what I've been able to test, the problem is not related to foo_discogger.
It happens even with a clean foobar2000.
I've written down my tests below to make it more clear.

1. Run a completely clean foobar2000 (%APPDATA%foobar2000-v2 folder doesn't exist)
2. Close foobar2000 (%APPDATA%foobar2000-v2 folder created)

3. Unpack and copy the attached library-v2.0.7z file to %APPDATA%foobar2000-v2 folder
https://www.mediafire.com/file/s8aewprg8xjn4h4/library-v2.0.7z/file

4. Once again, run foobar2000
5. Library - Album List, Right-click on "All Music" and click "Create Autoplaylist"

Up to this point, everything is fine.

6. Playback - Order - Shuffle (albums) or Shuffle (folders)

View - Console, The "database is locked" message is repeating.
Code: [Select]
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked

bump

The bug is still there.
I reduced about 100,000 songs from the media library.
I also cleaned up a lot of tags in the files (deleted lyrics, cue data, etc.)
I deleted the existing files. Below are the newly created metadb and playlist files.
https://www.mediafire.com/file/bzqd2osxm3p4xcb/foobar2000-v2.7z/file

There seems to be something that the foobar2000 v2 DB can't handle and is causing errors.
file name too long?
some unicode it can't handle?
I have my suspicions, but there's nothing more I can do in the real world.

Code: [Select]
Components loaded in: 0:00.006330
Configuration read in: 0:00.000473
foobar2000 v2.1 preview 2023-07-27 x64 [standard]
Playlist #0 loaded in 0:00.108934
User Interface initialized in: 0:00.225828
Loading foo_discogger
foo_discogger: a previous foo_discogger.cfg.db file version was found
foo_discogger: http_client service ready
FFmpeg version: 6.0
Startup time : 0:00.270997
Watching: D:\Music
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
Library initialized after 0:00.718363
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
could not compile SQL:
SELECT info, infoBrowse, size, lastModified, infoBrowseTime, created, attribs, attribsValid FROM metadb WHERE name = ?
database is locked
Title: Re: foobar2000 v2.0 bugs
Post by: josemescud on 2023-09-10 13:17:02
I want to warn that the following Actions are interchanged:

Playback / Volume / Up (instead of UP it lowers the volume).

Playback / Volume / Down (instead of DOWN turn up the volume)
Title: Re: foobar2000 v2.0 bugs
Post by: Case on 2023-09-10 14:01:39
How did you reach that conclusion? The actions work exactly as they should here both in foobar2000 v2.0 and in the latest 2.1 preview. Both in 32-bit and 64-bit versions.
Title: Re: foobar2000 v2.0 bugs
Post by: Case on 2023-09-10 18:49:21
@josemescud - Have you perhaps edited the "Volume step (dB)" setting found under Preferences -> Advanced -> Playback? It currently doesn't prevent you from entering negative values. If you enter a negative value there that will reverse the adjustment direction.
Title: Re: foobar2000 v2.0 bugs
Post by: josemescud on 2023-09-10 19:09:26
Quote from: Case on
@josemescud - Have you perhaps edited the "Volume step (dB)" setting found under Preferences -> Advanced -> Playback? It currently doesn't prevent you from entering negative values. If you enter a negative value there that will reverse the adjustment direction.

Thank you very much for your help.

You were right. The Volume Step value I don't think I ever modified it. The current value was -5. I changed it = 2 and the keyboard shortcuts for volume up and volume down work perfectly.
Title: Re: foobar2000 v2.0 bugs
Post by: edogawaconan on 2023-09-15 10:22:01
Quote from: edogawaconan on
I don't know if it's intended, in 1.6.x I can ctrl-f (on playlist) -> type thing -> press enter to play the first hit but I can't do that anymore in beta 10.
just want to report that this is still the case in 2.0 🥲
at least I can work it around by closing the find window first (by pressing esc) and then press enter.
Title: Re: foobar2000 v2.0 bugs
Post by: felix23 on 2023-09-16 12:45:01
Dear Community, I like to report that iPod manager 0.7.2 does not work properly with foobar v. 2.0. The device is recognized but "send playlist" leads to "foobar2000 afcfileref open" error which states that the divice is locked. Uninstall foobar v.2 and restinstall v.1.6.16 fixed the problem.
Title: Re: foobar2000 v2.0 bugs
Post by: Air KEN on 2023-09-16 14:12:37
@felix23
I can use it without any problems

iPod nano 6th x2, 7th x1
iPod shuffle 2nd x1, 4th x2

foobar2000 v2.1 preview 2023-09-14 32-bit
iPod manager 0.7.2
iTunes 12.12.10.1 x64
Windows 10, 11 Home

I want it to be compatible with 64bit.

(https://i.imgur.com/Dt8K3ZA.png)

(https://i.imgur.com/HjJGyIY.png)

You should move to this thread.
iPod manager: https://hydrogenaud.io/index.php/topic,45160.4200.html
Title: Re: foobar2000 v2.0 bugs
Post by: Bruce-in-Philly on 2023-10-10 21:48:56
Sorry if this was posted....

Library not showing DFF or DSF (DSD) files.  In WIndows, I set the file type to be foobar and foobar icon shows in windows explorer.   Win 11 all updates.  Had to move back to 1.6.17...  Both 2.0 and beta has issue.

Otherwise, a great build... thanx... I love the hide devices... I switch devices all the time... just great.

Bruce in Philly
Title: Re: foobar2000 v2.0 bugs
Post by: sveakul on 2023-10-11 01:07:30
Quote from: Bruce-in-Philly on
Library not showing DFF or DSF (DSD) files.
Try adding the component foo_input_sacd, download here: https://sourceforge.net/projects/sacddecoder/files/foo_input_sacd/ (https://sourceforge.net/projects/sacddecoder/files/foo_input_sacd/)
Title: Re: foobar2000 v2.0 bugs
Post by: Bruce-in-Philly on 2023-10-11 03:24:08
I did, nothing...

Yea, I saw that on some other forum... didn't work.   Of course I could have done something wrong but I don't think so... are you sure that will work?  If you are sure, I will re-load 2.0 and try it again... but I am 99% sure I did.

Peace
Bruce in Philly
Title: Re: foobar2000 v2.0 bugs
Post by: Belomor on 2023-10-11 03:51:28
Quote from: Bruce-in-Philly on
are you sure that will work?
I got it working in foobar 2.0:

(https://i122.fastpic.org/big/2023/1011/6e/1e633d97ba4eb1057196121111093c6e.png)
Title: Re: foobar2000 v2.0 bugs
Post by: Bruce-in-Philly on 2023-10-11 20:36:25
Quote from: Belomor on
Quote from: Bruce-in-Philly on
are you sure that will work?
I got it working in foobar 2.0:

(https://i122.fastpic.org/big/2023/1011/6e/1e633d97ba4eb1057196121111093c6e.png)


Cool, how did you get it work?

Bruce
Title: Re: foobar2000 v2.0 bugs
Post by: Porcus on 2023-10-11 20:59:52
Obligatory "If you want to play DSD, then WavPack can compress them losslessly as long as you use the WavPack executable rather than conversion by a player" comment. (Oh and DST packed are not supported.)
Title: Re: foobar2000 v2.0 bugs
Post by: Bruce-in-Philly on 2023-10-11 21:35:00
Quote from: Porcus on
Obligatory "If you want to play DSD, then WavPack can compress them losslessly as long as you use the WavPack executable rather than conversion by a player" comment. (Oh and DST packed are not supported.)

I just ensured that another PC I have in my home has Foobar 2.0 and has the foo_input_sacd compoent installed.... no go... not picking it up in the library.   So that is two machines, one with Win 10 and other 11 that wont see DSF or DFF files.  Again, I these file types assigned in windows to foobar.

Thanx,
 Bruce in Philly
Title: Re: foobar2000 v2.0 bugs
Post by: Bruce-in-Philly on 2023-10-12 02:53:37
Quote from: Porcus on
Obligatory "If you want to play DSD, then WavPack can compress them losslessly as long as you use the WavPack executable rather than conversion by a player" comment. (Oh and DST packed are not supported.)

I just re-read your post....  The issue isn't playing these files, it is just that Foobar doesn't recognize their existence.  I don't want them converted or "played", just passed through to my DAC bit-for-bit.   The bug in Foobar is a library issue.

Peace
Bruce in Philly
Title: Re: foobar2000 v2.0 bugs
Post by: felix23 on 2023-10-12 13:35:41
@Air Ken

I guess my wired setup might be the reason but it worked for several years. I use an ipod touch 2G and I love the playlist features which help me to teach my sport lessons. I know that sounds strange but I do not like the idea of streaming. I own the music and I can use it when I want to use it. Anyway

when I connect my ipod touch 2G it will be recognized by win11 under usb-devices (apple mobile device usb composite device). In this state I cannot use the ipod manager 0.7.2 because the device can not be found. It is every time the same procedure. Now I need to uninstall the apple mobile device usb composite device driver and also set unistall driver. After that I need to rediscover all changed devices. Now the ipod touch 2G is recognized as USB-Controller device (apple mobile device usb driver ver 6.0.9999.67 from 18.05.2015). In this state ipod manger 0.7.2. finds my ipod touch 2G and can be synced. I know it sounds rediclious but this worked for me several years since the 2.0 update appeared. What I am looking for is a configuration without the whole itunes package, just the drivers to get foobar running. I spended so my hours in the past to get it running and I really fear the effort again to set it up working. May you or others had the same issue and can provide a setup that is foolproof.

Many thanks.
Title: Re: foobar2000 v2.0 bugs
Post by: Air KEN on 2023-10-12 14:28:01
@felix23

I own two iPod touch 7th 32GB.
iPod touch is not supported.
I was thinking how much I wish I could use it.
Currently, it is connected to foobar2000 v2.0 32bit as foobar2000 mobile iOS.
Or as a device controller...
MonkeyMote for foobar2000
https://www.monkeymote.com/home
------------
hahaha...
I didn't know there was such a trick.
But this can't be helped.
This is not a bug in foobar2000 v2.0.
We can use any supported iPod, so it's not a bug.
Title: Re: foobar2000 v2.0 bugs
Post by: Case on 2023-10-12 15:57:25
Quote from: Bruce-in-Philly on
I just re-read your post....  The issue isn't playing these files, it is just that Foobar doesn't recognize their existence.  I don't want them converted or "played", just passed through to my DAC bit-for-bit.   The bug in Foobar is a library issue.
Did you perhaps add your DSD collection path to media library before you installed foo_input_sacd component? It seems foobar2000 v2.x remembers all the files it sees when library is initialized and it will keep ignoring all old files it didn't recognize during initial scan even if you later add components that can handle them.
You should be able to work aroud this issue by removing the media library path from Media Library configuration, restart foobar2000, then add the path back.
Title: Re: foobar2000 v2.0 bugs
Post by: felix23 on 2023-10-12 16:10:11
@Air Ken

In my humble opinion there has to be any connection with the new version. I reinstalled foobar2000_v2.0 (32bit) in a different directory and ran it. The ipod touch 2g is support (https://wiki.yuo.be/dop:start at least for my software version) and was recognized. I used File->iPod->manage contents, where a window appeard, curiously since some update in the past "genius playlists" appeard several time on my device, but I don't want to complain about it, if the whole device still syncs. Now I tried to remove some old playlist and all of these genius playlists. Finally I hit "save and close" and following error appeard

I/O Error: AFCFileRefOpen returned: 2 Path was: /com.apple.itunes.lock_sync

So I closed foobar2.0 and reopened directly the old version 1.6.16 and did the same steps above, but this time it worked. So in my humble opinion something is not right aligned between these two versions. Does anybody has any ideas about it?

Many thanks.
Title: Re: foobar2000 v2.0 bugs
Post by: Bruce-in-Philly on 2023-10-12 16:57:08
Quote from: Case on
Quote from: Bruce-in-Philly on
I just re-read your post....  The issue isn't playing these files, it is just that Foobar doesn't recognize their existence.  I don't want them converted or "played", just passed through to my DAC bit-for-bit.   The bug in Foobar is a library issue.
Did you perhaps add your DSD collection path to media library before you installed foo_input_sacd component? It seems foobar2000 v2.x remembers all the files it sees when library is initialized and it will keep ignoring all old files it didn't recognize during initial scan even if you later add components that can handle them.
You should be able to work aroud this issue by removing the media library path from Media Library configuration, restart foobar2000, then add the path back.

I did this... no go.   BTW, if one should need to do this, then what happens when you copy new DFF files to the music directory?  Delete and restart again?  No, 1.x versions worked fine... no hoops to jump through.  Foobar has always been great... i have just one directory (and only one path in foobar) on a NAS called Music.  Under that is a folder for each band or artist, under that a folder for each album, and under that, the tunes.   Always worked really well and pretty fast too.  When I buy new files, I just copy, via Windows, to the music folder.   If Foobar is running, it finds it almost immediately... if not running, it will maybe 5 - 10 minutes after firing it up (I have a huge library).  It just worked.  Been using it for what... now over 20 years or so???  I dunno for ever...

Peace
Bruce in Philly
Title: Re: foobar2000 v2.0 bugs
Post by: Case on 2023-10-12 20:11:34
That initial scan issue is the absolutely only problem I can trigger. And it is a bug. But even if you suffered from that problem any new added files would be visible just like with the old foobar.
Note that this issue is super easy to avoid for you: once you install foobar2000 v2.x, install foo_input_sacd first. After it is installed, configure media library paths.

Are you certain you restarted foobar2000 after you removed the configured media library paths? Without this step the previously ignored entries will not be cleared.
Perhaps I should suggest you to remove the "library-v2.0" directory under the foobar's profile path. That will achieve the same plus it will reset the exclude filter to default.

PS: this thread is scarily titled foobar2000 v2.0 bugs. Everyone should be using the v2.1 previews as that is where all the recent developments and fixes have happened. The 2.0 "stable" is half a year behind on fixes.
Title: Re: foobar2000 v2.0 bugs
Post by: Bruce-in-Philly on 2023-10-12 20:19:02
Ok, here is what I am about to do....

I am going to download and run 2.1 (have 2.0 on my test machine).  Then I will ensure foo_input_sacd is active... it should as it is already there.   Then I will delete the path to my music folder.   Then I will shut down foobar... reopen.. then initialize the path to the folder and I will report what happens.

Update:   OK.... did the deeds.... now waiting for library to build.....

Update: WOOOHOO!!! it worked.  Thanx so much.  Yep a bug, but now I am back in business.

Peace
Bruce in Philly
Title: Re: foobar2000 v2.0 bugs
Post by: Air KEN on 2023-10-13 03:04:05
@felix23
Oops.
Your older iPod touch is on the list of supported models.
https://wiki.yuo.be/dop:start#supported_models

You should go to the iPod thread.
iPod manager: https://hydrogenaud.io/index.php/topic,45160.4200.html
Title: Re: foobar2000 v2.0 bugs
Post by: gfxnow on 2023-10-17 19:31:34
Quote from: Case on
PS: this thread is scarily titled foobar2000 v2.0 bugs. Everyone should be using the v2.1 previews as that is where all the recent developments and fixes have happened. The 2.0 "stable" is half a year behind on fixes.

Yes the latest 2.1 preview is actually more stable than the 2.0 "stable" release. I think Peter has specific issues in his backlog that he wants to fix before releasing 2.1
Title: Re: foobar2000 v2.0 bugs
Post by: LeVvE on 2023-12-21 10:01:54
Quote from: LeVvE on
One thing I noticed with 2.0 is that the album list doesn't swap between light/dark font when text is highlighted based on how dark your background color is?

This is how it used to look: https://i.imgur.com/vTFDDkc.png
This is how it looks now: https://i.imgur.com/wElxea4.png

If I make the background any darker it's really hard to read the text in the album list because it's black instead of white, also when anything is clicked in the playlist the highlight color is removed and turns black so it's black on black and I can't read it at all.
Just installed the new 2.1 release, I really like the new radio interface stuff. Internet Radio looks the same as the playlist with correct? highlight and text color.

Internet radio white text on blue selection: https://i.imgur.com/ium2Oh8.png

Album list still shows weird colors with dark selection/highlight color and black instead of white text, the "box" around the text also has rounded edges compared to everywhere else: https://i.imgur.com/ePKIKZf.png

Thanks.
Title: Re: foobar2000 v2.0 bugs
Post by: marc2k3 on 2023-12-21 10:32:06
Album list being borked has been reported many times but nothing has been done (yet). :P

It seems like it's because windows theming APIs are being used but they should not be when custom colours are active.

https://hydrogenaud.io/index.php/topic,124779.msg1036518.html#msg1036518
Title: Re: foobar2000 v2.0 bugs
Post by: Case on 2023-12-21 12:51:03
The color issue was noted but Peter didn't want to start making any heavy last minute changes before 2.1 release.

There's a newer thread for foobar2000 v2.1 bugs: https://hydrogenaud.io/index.php/topic,124137.0.html (https://hydrogenaud.io/index.php/topic,124137.0.html).
Title: Re: foobar2000 v2.0 bugs
Post by: Despair on 2023-12-22 20:56:35
Semi off topic, but can someone tell me the color codes for the default dark theme in 2.1? I'd like to use them in 1.6.17 as well, but selecting Dark Mode doesn't display the individual colors anywhere.
Title: Re: foobar2000 v2.0 bugs
Post by: A_Man_Eating_Duck on 2023-12-23 21:29:16
Maybe take a screenshot of Foobar2000 and paste it in to a paint program and use the colour picker to find the colour codes?
Title: Re: foobar2000 v2.0 bugs
Post by: Otvinta on 2023-12-24 05:17:47
v2.1
Drag & drop cover art in file properties cause window scrolling by mouse movement.
Title: Re: foobar2000 v2.0 bugs
Post by: orangefx on 2024-03-13 19:44:17
Quote from: orangefx on
i run win10 in dark mode on uhd screen scaled 125%. the visibility of everything is worse readable (for me) in v.2 vs. v.1.6.
is there an option to scale up and colour the fonts, also for submenus and preferences? also it would be nice to be able to resize the preferences window when working with advanced options.
one year later the gui scales + views ok, but preferences window still shows in 100% only. running v.2.1.2. unusable for bad eyeview.
Text only | Text with Images