Author Topic: Coverflow Plugin  (Read 7269 times)

snaphappy7530

  • Newbie
  • *
  • Posts: 2
Ah sadly it looks like once I added roughly 500-1000 songs it would crash no matter what and I had to delete the plugin, a real shame.

phred

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 10272
Ah sadly it looks like once I added roughly 500-1000 songs it would crash no matter what and I had to delete the plugin, a real shame.
I've got 48,000+ tracks and I haven't had any issues. Are you running it embedded in a panel or as a floating panel. I use the floater. Which ever one you're using, try the other.
Download the latest MusicBee v3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Custom Forum Search
Posting screenshots is here

BoringName

  • Sr. Member
  • ****
  • Posts: 916
This is more of a general cover flow thread. There is a specific thread for 3DBee now and any future questions should be directed there.
https://getmusicbee.com/forum/index.php?topic=38740.150

I expect you have "load all covers into memory" checked. As it implies, this will load all your covers into VRAM on the graphics card, if there isn't enough it will crash. Once your library gets large enough, even highend systems will run out of memory. This should only be checked on smaller libraries for most people. The size of the cover files also determines how many will fit in VRAM.

Have a read through the thread I linked above and familiarise yourself with all the settings. I'd suggest unticking "load all covers into memory". Unless you have a very low specced system, you shouldn't get out of memory errors with "load all covers into memory" unchecked. If you are, you can try lowering the "album buffer" setting. The lowest it can go is 20. You can also set it to buffer just a playlist.

Memory management is a juggling act and took me a while to work out. It would be great if all covers could be loaded into VRAM as it performs much better when scrolling and saves constantly loading covers from the disc but unfortunately memory is a finite resource. I know I haven't got it perfect but unless there is something quirky about your hardware, it should work.

I should look at adding an option for specifying an amount of RAM to use as a cache but with how it's all setup, I'm not sure how feasible that will be.