- Nullsoft tiny is a spectrum vis, exactly like FB's default, and the first 5-10 or so pixels are the exact same slanted gradient pattern as in FB's spectrum window when you start it. It also appears on Stop. No anomalies between songs, though, which is good. This is a feature of the foobar2000 core. The component asks for the spectrum data. If they are not available yet (as they are not computed when no visualisation needs them), it can ask for some kind of "dummy" data to show in the meantime. I can easily just show nothing in that case, if the consensus is that it's better. Actually, I already do it that way in case of oscilloscope data, because it looked bad in the "Classic Spectrum Visualisation" I tested.- Shpeck Tiny shows the same upward streaking as FB's defauls spectrum. It's as if Bob Ross came by with his big brush and brushed gently upwards. I'm not sure how that happens. The plugin does the calculating, not FB. Or does it? Possibly related to issue 1. First, let's see how horrible the Winamp visualisation plugins interface is. They can ask for either the waveform data (oscilloscope), spectrum data, or both. And none of these methods are really realiable. The spectrum data is only 576 values wide, presumably because of some old MP3 optimalization. Now that both limits the resolution considerably, particularly for the fullscreen display, and also makes it difficult to supply, because all normal FFT output has always been sized in powers of 2. (Shpeck just uses the 512 values wide one and stretch it a bit.) Because of how bad the spectrum data are, I noticed the plugins tend to use the waveform data and compute the spectrum itself. But this is not ideal as well - each time, the plugin gets only 576 sample values. To get the precise spectrum for CD Audio, for example, it would need to be called exactly 44100/576=76.5625 times per second, which is not too feasible. Now back to your question: If that plugin uses the spectrum data, there is not much I can do. It's foobar2000 which prepares it. All I could do is to use the 1024 values wide one and shrink it instead of stretching the lower resolution data, but I doubt it will have much impact - as you wrote yourself, the built-in visualisations looks the same, and they are using the data directly and in a perfectly sane way. And if the plugin computes the spectrum itself from the waveform data, I can't do anything at all. Blame it on Nullsoft.- FB keys are disabled. I've mapped Ctrl+Left and Right, and a few others, to Next, Prev, volume up etc., but they don't work in Tiny Fullscreen. It's a bit of a shame because not having keyboard control in fullscreen is half the purpose defeated. I generally have no control over keyboard input in plugins. Or, to be precise, I do in case of plugins running in an embedded window, because they forward the unknown keystrokes to my parent window, but that isn't the case for fullscreen mode and the Tiny Vis.. However, some plugins might also be forwarding the unknown keystrokes to the faked Winamp main window - I don't know if that really happens, but I'll look if it works and include it in the next version if yes. In some plugins, the classic Winamp controls (ZXCVB for prev., play/pause, stop, next or how it is, arrows for seeking/volume, etc.) seems to work at least, but that is unfortunately not the case of the Tiny FS vis you are using.Edit: And of course, you can always use foobar2000 global hotkeys everywhere, including fullscreen.