Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Recent Posts
11
3rd Party Plugins - (fb2k) / Re: Columns UI
Last post by josemescud -
If you have Foobar2000 v2 (32-bit) installed to obscure the columns titles you just have to select the Dark mode.
Trying that out:
While it makes things 'dark' in general, the header bar of a panel will still not adhere to the colouring you have set for the panel.

Quote
The rest of the problems do not tell you, but I have never had those problems with UI columns and I have installed the 32-bit version and 64-bit.
So to be sure: if you select some files in Windows Explorer, and you select 'open with foobar2000', for you it opens with all the tracks unselected/highlighted?


In Windows Explorer I have marked 2 tracks and in the context menu I have selected "Open in Foobar2000"

Image4:  foobar2000 v2 [64-bit] are loaded on the playlist and the first track is played
Image5:  foobar2000 v2 [32-bit] exactly the same

If in the context menu I selected "Enqueue in Foobar2000" behaves the same except that no track sounds.
12
General - (fb2k) / Re: foobar2000 v2.0 bugs
Last post by Belomor -
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, 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.
17
General - (fb2k) / Re: foobar2000 v2.0 bugs
Last post by Peter -
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.
18
3rd Party Plugins - (fb2k) / Re: Columns UI
Last post by jistme -
If you have Foobar2000 v2 (32-bit) installed to obscure the columns titles you just have to select the Dark mode.
Trying that out:
While it makes things 'dark' in general, the header bar of a panel will still not adhere to the colouring you have set for the panel.

Quote
The rest of the problems do not tell you, but I have never had those problems with UI columns and I have installed the 32-bit version and 64-bit.
So to be sure: if you select some files in Windows Explorer, and you select 'open with foobar2000', for you it opens with all the tracks unselected/highlighted?
19
3rd Party Plugins - (fb2k) / Re: Columns UI
Last post by josemescud -
a big thank you jistme  ;)

1.
"It's about the header bar of the playlist panel.
I managed to make the panel dark, but its header bar remains white:"


If you have Foobar2000 v2 (32-bit) installed to obscure the columns titles you just have to select the Dark mode (Image).

The rest of the problems do not tell you, but I have never had those problems with UI columns and I have installed the 32-bit version and 64-bit.
20
General - (fb2k) / Re: how to disable pop-up balloon/tooltip
Last post by jistme -
I have checked all settings that I could find, and then checked them again.
But it looks like this behaviour is not user configurable.

How can I raise this issue so that it has a chance of getting addressed/resolved?