Chronflow is probably the best cover flow plugin for foobar2000. The only problem is that it throws “Can’t set pixel format” and “Img texture leak error 2” on certain video cards, mine included. I used foo_bubble_coverflow because of that for quite a while, but then i decided to give Chronflow another try, and to my greatest surprise it worked without problem. At least until i had to restart foobar. (For those who have the “Previous submission still in progress” problem with the foo_audioscrobbler plugin, stopping playback and restarting foobar solves the problem every time, the cache then can be submitted manually (as i usually do), but i guess it’ll be submitted anyway with the next track.) But now that i knew it can work, i didn’t give up. And i figured out the solution. It’s not a real solution, just a quick workaround, annoying but works, for me at least.

So here’s The Way: install both Chronflow and bubble coverflow. When putting together the layout/skin for foobar, the best idea is to put a splitter for spaceholder where the coverflow will have to be. Put Chronflow in it, and use it. Whenever it throws that pixel format / texture leak error, remove it from the layout and put bubble coverflow in its place. For me, if i do this, bubble coverflow will throw a pixel format error as well at first. But don’t worry about that, restart foobar, and the bubble flow will be all right where it’s supposed to be, and it’ll work fine. Then the only thing left is to put Chronflow back in bubble flow’s place, and that’ll work as well without problem–at least until the next restart.

Since it’s quite troublesome, the best choice is not to shutdown foobar ever (then if once running, these errors won’t come out). I usually hibernate my computer, so the only time i have to restart foobar is when the scrobbler plugin screws up because of my connection lagging.

If you have to restart it, and you know, then the best choice is to change Chronflow to bubble coverflow before quitting, and changing it back when restarted foobar. It will work. (At least it should.)

I hope this will be useful, i really looked around all the foobar-o-sphere, but couldn’t find a solution before. Also, i don’t know if there’s and recent version of Chronflow. When i was forced to change computer and these errors started coming up, after a while i contacted Chronial to ask about this problem and whether there’ll be further updates to Chronflow, but no reply arrived since august last year…