Greetings!
The day has come to point it out for many that have not come across this problem, yet...
(And I'm glad I'm not the only one) ->
https://forum.cockos.com/showthread.php?t=108596
I'm working on an acousmatic project in REAPER and went ahead making sounds using automation and such like so:
When suddenly, I decided it would be a good idea to increase the buffer size of the driver to spare more CPU, just in case...
However, that affected ALL of the present plugin automation (not volume or pan, since those are sample accurate) and sounds completely different from what is to be expected simply because the automation can only be processed once every X sample of the buffer size (not the case for VST3, if they implemented sample-accurate automation on the plugin).
Here are some audio examples with different buffer lengths affecting the sound that you see being automated from the image to clarify the issue:
https://www.mediafire.com/file/37ut2...es%29.zip/file
Now that it's out of the way, I was thinking if it would be possible to sort this issue out by making the automation independent from the buffer size AND be able to choose which tracks/items are affected by it?
Something in the lines of FL Studio, because it's the only one I know (and I tested) that
doesn't have this issue.
For now, the only solution is to either bounce the tracks on a lower buffer size or to wait and pray for VST3.
Hope this will shed some light for those that haven't experienced this yet.