Tincture wrote:I saw the mention of "Revert" for the browser and thought "hurray, hurray, hurray!". But now I think I have read somewhere that it "reloads" the patch used before browsing, rather than actually just going back to its previous state. Can anyone confirm/deny please?
The reason it matters to me is that I quite often tweak patches quite a bit after loading them and so "reloading" the patch wouldn't take me back to where I was before browsing :/
It can work exactly as you describe if you understand HOW it works and you approach it like the "old" version.
If you browse and tweak WHILE browsing (not possible to do in previous versions), it will not work as expected, which is logical IMO because the idea of Revert is to take you back to the "pre-browsing" state.
But if you browse, then leave browse mode to tweak a patch, then when you begin browsing again, revert will return you to your tweaked patch (not the stored "preset" you started with).
This is exactly what you want, you just have to "tell" it when you want to keep the patch by ending your browse session. This worked automatically in the old version, fwiw because you had was no other option!
Reverting, BTW, takes you OUT of browse mode, so you'll have to "browse" again to re-activate the feature. Again this is how it used to work, except the browser is not now "modal" which causes the confusion IMO. But it was pretty easy to learn the new workflow for me.
Remember that Revert takes you back to the state of the instrument when you ENTERED browse mode, not the preset stored on disk - sometimes these are the same thing, like if you created a device loaded with a factory patch, then loaded a second patch, then hit revert you would be returned to the factory patch. But not because it's the one on disk but because it was the one LOADED into the device when you began browsing.
I probably could have stated this more clearly - hope this helps!