Interestingly, the LFO problem is present in the stand-alone version of Aparillo on my PC. The presets I've created all load with the LFO rates at minimum, regardless of how they were saved. So it is definitely not just a Mac problem.

You have no problems with the LFO recall in Cubase, but I wonder about other DAWs, especially Reason?

Cubase and Orion.

By 'recall', I don't mean saving a patch and then loading it. I mean having an Aparillo loaded in your DAW (in Reason in my case), tweaking its LFO rates, saving the project (but not saving the patch), and when reopening the project, Aparillo remembers all the parameter settings, just like with every other VST I've ever used in a DAW. In my case, Aparillo remembers all the parameter settings except the LFO rates. Sugar Bytes acknowledges the problem.

By 'recall', I don't mean saving a patch and then loading it. I mean having an Aparillo loaded in your DAW (in Reason in my case), tweaking its LFO rates, saving the project (but not saving the patch), and when reopening the project, Aparillo remembers all the parameter settings, just like with every other VST I've ever used in a DAW. In my case, Aparillo remembers all the parameter settings except the LFO rates. Sugar Bytes acknowledges the problem.

Yes, I know what you were talking about. In Cubase and Orion that is exactly what I did and it worked properly. Obviously you can't do that in the standalone, so it was down to noticing that the LFO rates had not been correctly recalled when I loaded the patch.

By 'recall', I don't mean saving a patch and then loading it. I mean having an Aparillo loaded in your DAW (in Reason in my case), tweaking its LFO rates, saving the project (but not saving the patch), and when reopening the project, Aparillo remembers all the parameter settings, just like with every other VST I've ever used in a DAW. In my case, Aparillo remembers all the parameter settings except the LFO rates. Sugar Bytes acknowledges the problem.

Yes, I know what you were talking about. In Cubase and Orion that is exactly what I did and it worked properly. Obviously you can't do that in the standalone, so it was down to noticing that the LFO rates had not been correctly recalled when I loaded the patch.

we recently uploaded a new Aparillo version (1.0.5) where the described problems are fixed now.
Please download and install again. But before this we recommend to manually delete the Aparillo VST file from:

I keep forgetting to install the update. I'm posting this in the hope that I will see the thread tonight and remember to do it. I am super-keen to start finding spots for Aparillo in our music. I am currently moving a lot of old songs across from Orion to Cubase, which is the perfect opportunity to slip in something new and different.