Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: foobar2000 v2.0 bugs (Read 138021 times) previous topic - next topic
0 Members and 5 Guests are viewing this topic.

Re: foobar2000 v2.0 bugs

Reply #725 –
Version 2 does not show the total time of selected tracks properly:

Re: foobar2000 v2.0 bugs

Reply #726 –
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!

Re: foobar2000 v2.0 bugs

Reply #727 –
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.

Re: foobar2000 v2.0 bugs

Reply #728 –
"Bring to front when adding new files" does not work (Win7).

Re: foobar2000 v2.0 bugs

Reply #729 –
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? 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?

Re: foobar2000 v2.0 bugs

Reply #730 –
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?

Re: foobar2000 v2.0 bugs

Reply #731 –
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.

Re: foobar2000 v2.0 bugs

Reply #732 –
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.

Re: foobar2000 v2.0 bugs

Reply #733 –
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.
 

Re: foobar2000 v2.0 bugs

Reply #735 –
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.

Re: foobar2000 v2.0 bugs

Reply #737 –
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

Re: foobar2000 v2.0 bugs

Reply #738 –
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

Re: foobar2000 v2.0 bugs

Reply #739 –
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:

Re: foobar2000 v2.0 bugs

Reply #740 –
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?

Re: foobar2000 v2.0 bugs

Reply #741 –
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.

Re: foobar2000 v2.0 bugs

Reply #742 –
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?

Re: foobar2000 v2.0 bugs

Reply #745 –
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".

Re: foobar2000 v2.0 bugs

Reply #746 –
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.

Re: foobar2000 v2.0 bugs

Reply #747 –
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.

Re: foobar2000 v2.0 bugs

Reply #748 –
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.

Re: foobar2000 v2.0 bugs

Reply #749 –
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.