So setting the texture cache too large will influence video playback, other multimedia applications as well as games. Remember that there are multiple other applications that use your GPU and all share its memory. The covers are loaded into GPU memory, so this also the limiting element for your cache. Note: Changes to the multisampling settings will only take effect after the panel is restarted (either hide and show it or restart foobar2000).Įach time you move the display to a new cover, the texture loader makes sure that at least cache size*0.9 covers around the selected cover are loaded. These Settings influence the quality of the generated image. Once the texture cache is filled, the loader sleeps until you move the covers again. This is done in an asynchronous manner (you can see this by scrolling very fast - the covers move faster than the loader can load them -> you see the 'hourglass cover'). The texture loading thread loads the covers from you hard-disk into memory so the renderer can display them. While foobar is minimized or completely hidden behind any windows the renderer will do nothing at all and so also cause no load for your cpu. when you restore the foobar window, new textures have been loaded or an animation is shown. The image will only be rendered when it is needed - eg. The plugin has two threads - one thread to render the image and one thread to cache the cover textures. To understand the effect of the settings in the performance tab it is important to know the basic architecture of the plugin: Chronflow Preferences page showing the 'Performance' tab.

How to install skin foobar2000