I'd like to see how much of the ultra high frequency content is real, rather than harmonic distortion, though a band-limited master would be the best way to check for that.
I can also do that this evening...
Is the taskbar locked? Is foobar maximized in a direction?
Use it in conjunction with foo_uie_mega_panel_splitter.(MPS)
Noticed - on the latest versions, starting with 1.2 scripts are loaded with a delay (50-500ms ..)
As a consequence - I see a white screen sometimes .. And for example with version 1.1.4 - always a quick start ..
Are there some special steps to reproduce this? If I click the minimized foobar's icon or activate it with a keyboard shortcut it restores correctly to maximized size and its window is attached to taskbar and is never beneath it. I can also move taskbar around the screen while foobar2000 is minimized or closed and it opens correctly.
I seem to have trouble making Volumio work to test it. But have you tried 16-bit PCM output from foobar2000? I recall reading about compatibility problems with several devices when 24-bit output is used.
everytime I minimize my foobar and then bring it back to focus, the window goes below the taskbar
this glitch started since I putted the taskbar on the left corner
windows 7 x64, foobar 1.3.15
just reporting this bug, thanks
Spectrum analyzer too, please.
I might as well save a bunch of fcl files for the same reason and then know exactly where the changes were but like I mentioned before I'm not about to do that for every single change, too much a hassle. If, for example, you're working on an excel file, you just do Ctrl S and you have your changes locked. Nobody in their right mind would go about and save different version of the same file which is more or less the method you would need to go about when building a config and testing things out.
So just simply doing save configuration and then letting it crash reverts it back exactly the way you saved it at that point without foo_jesus giving you a version you didn't want beyond the save configuration point or doing it with different files of backups and playing the guess game.
Though foo_jesus doesn't behave exactly as required, it's worth noting that you can set the number of backups to keep, so set it to something like 10. Or 50. Also, you can set how often it autosaves in minutes, so set it to something like 1-5 minutes. Now, you may have to guess which version to restore ("was it 3 minutes ago? 5 minutes ago?), but foo_jesus is not useless in this situation.
No, foo_jesus does not save to 'a' previous state, it goes back to the last previous state. But that's not what OP and I are talking about. Read the thread, we're talking about reverting to x state, not last previous state. If I were to want to revert back to a certain state which is not the last state and I had a component that guarantees to revert to last state then that component is about the last thing I'd want to have.
Simply said, if you're building a config and you want to lock in certain changes and then continue building and test things out before I want to again lock in those changes then a component that would continuously save all changes is something I'd stay away from.