However here's the bug report.
A VST parameter with enabled "preset" input but disabled "auto" input messes with Cubase automation parameters.
In a nutshell: Not only the disabled parameter is filtered but also one additional parameter which is NOT disabled at the SM VST prim. I found the following rule:
The disabled parameter is filtered by cubase. All following parameters are moving up one position in the automation parameter list. Now Cubase additionally filters out the position where the disabled parameter would usually appear. But due to the first filtering there's not the disabled parameter itself but the next one which filled that slot. Sounds a bit complicated - so here's an example which can be verified with my example osm.
We have these parameters:
0 1 2 3 4 5 6 and disable parameter 0 and 2 for automation. Which should result in:
1 3 4 5 6. That is what shows up e.g in Reaper. But Cubase does this: We disabled position 0 and 2. These are now filled with parameter 1 and 4. So what appears is just:
3 5 6.
It would be very kind if some Cubase owner could verify that because i stumbled over that shortly before my next release. And this is yet another showstopper.
So here's the osm.
autotest.osm- (8.77 KiB) Downloaded 103 times
