Quote:
Originally Posted by
liquidsonics
I generally agree, but presented with the choice of overhauling the presets management system and breaking backwards compatibility for 10 years of Reverberate 1/2 users vs improving presets management capability for the next generation I went for the former because I know in time Reverberate 1/2 will begin to stop working as operating systems and plug-in formats march on and gradually break the old versions. Always a difficult decision.
Hi Matt, and thanks a lot for your answer.
I can perfectly understand the choice of not breaking backward compatibility. And (because I don't know nothing about coding plugins) I don't know the kind of time and work involved in creating a backward compatible preset system.
But at the same time, my point was that to me the preset system is quite difficult to use (at the moment, I still didn't figure exactly how to create my own presets) and doesn't look exactly like a preset system.
EDIT : I know about the manual. I just find the procedure described there very "convoluted" (sorry for the joke) and not practical at all.
The most confusing is that a convolution reverb is of course based on IRs, but to me the Reverberate folder system doesn't seem to make any difference between an IR and a preset (but maybe I'm missing something).
IMHO, the best way would be a file management system where you could load an IR located in a bank, and then save your tweaks of this IR in a preset.
So you would have two folders/banks : IRs and presets.
Specially than in Reverberate, you can load 2 different IRs in the same preset, but the whole bank folder and recalling presets system is still organized around what I see as IRs.
Anyway, I'm amazed by the sound quality of your plugin, and this is the most important (even if workflow is important too).
Maybe it's just a way of thinking I'm not accustomed to (or I didn't understand yet).