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

Re: foobar2000 v2.0 bugs

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


Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs

Reply #84
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.  :))

Re: foobar2000 v2.0 bugs

Reply #85
Customize Buttons dialog is always in light mode.


Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs

Reply #88
f

Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs

Reply #90
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. And with installed foobar2000 instance things are even simpler. Just double click the .fb2k-component file.

Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs [playback-statitics]

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

Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs

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

Re: foobar2000 v2.0 bugs

Reply #96
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.
SHURE SRH1840, SENNHEISER HD660S2, SENNHEISER HD620S, SENNHEISER HD 490 Pro Plus, beyerdynamic 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 #97
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


Re: foobar2000 v2.0 bugs

Reply #98
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.
SHURE SRH1840, SENNHEISER HD660S2, SENNHEISER HD620S, SENNHEISER HD 490 Pro Plus, beyerdynamic 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 #99
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