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 137955 times) previous topic - next topic
0 Members and 3 Guests are viewing this topic.

Re: foobar2000 v2.0 bugs

Reply #675 –
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.
Microsoft Windows: We can't script here, this is bat country.

Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs

Reply #680 –
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 :-) ?

Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs

Reply #683 –
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.
Microsoft Windows: We can't script here, this is bat country.

Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs

Reply #686 –
Just wanted to mention that foobar2000 v2.0 is released. 🥳

Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs

Reply #688 –
...same as above.
 :'(

Re: foobar2000 v2.0 bugs

Reply #689 –
Remember to always back up your settings before doing an in-place update. :(
Think millionaire, but with cannons.

Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs

Reply #691 –
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.
Think millionaire, but with cannons.

Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs

Reply #697 –
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.
✌️

Re: foobar2000 v2.0 bugs

Reply #698 –
Quote
New audio output device management features - unwanted devices can be disabled, bit depth and DSP can be configured per-device.

Re: foobar2000 v2.0 bugs

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