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

Re: foobar2000 v2.0 bugs Performance

Reply #651
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




Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs

Reply #656
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.

Re: foobar2000 v2.0 bugs

Reply #657
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.

 

Re: foobar2000 v2.0 bugs

Reply #658
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.

Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs

Reply #663
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.

Re: foobar2000 v2.0 bugs

Reply #664
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?


Re: foobar2000 v2.0 bugs

Reply #666
What grimes said.
Email relevant files to peter [at] hydrogenaud.io
Microsoft Windows: We can't script here, this is bat country.

Re: foobar2000 v2.0 bugs

Reply #667
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

Re: foobar2000 v2.0 bugs

Reply #668
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.

Re: foobar2000 v2.0 bugs

Reply #669
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.

Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs

Reply #671
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.

Re: foobar2000 v2.0 bugs

Reply #672
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.



Thanks.
SHURE SRH1840, SENNHEISER HD660S2, SENNHEISER HD 490 PRO, DT 1990 PRO, HiFiMAN Edition XS, Bowers & Wilkins P7, FiiO FT5, 水月雨 (MOONDROP) 空鳴 - VOID, Nakamichi Elite FIVE ANC, SONY WH-ULT900N (ULT WEAR) (made a Upgrade/Balanced Cable by myself)


Re: foobar2000 v2.0 bugs

Reply #674
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.



Thanks.
Classic User Interface 2.0.3 (2023-04-25)
https://www.foobar2000.org/components/view/foo_ui_classic
solved.

Thanks Peter.
SHURE SRH1840, SENNHEISER HD660S2, SENNHEISER HD 490 PRO, DT 1990 PRO, HiFiMAN Edition XS, Bowers & Wilkins P7, FiiO FT5, 水月雨 (MOONDROP) 空鳴 - VOID, Nakamichi Elite FIVE ANC, SONY WH-ULT900N (ULT WEAR) (made a Upgrade/Balanced Cable by myself)