Well, if you're not feeling like testing this thing, you can still throw me a bone or two.
Remember, it's a different implementation now. I am aware that the previous version could screw up high-LPB automation - my bad.
Also, I was not aware of any difference between OSX and Windows. This is obviously important to know, as the API is supposed to work similarly across platforms.
Sounds like I need to boot my Mac up and run some tests after all.
Now, for the bone: can you give me an example of a plugin where you experience problems with rounding/feedback? Preferably a cross-platform, non-commercial one.
If I'm lucky I might be able to make some parameter feedback ** cue ugly teeth smiley **
OK, I will try, but currently have no time to deep dive here again. Will test your new version,too.
Would be nice if you could setup a decent macos testing system to get a better view of the problems (u can ask me about setting up hackintosh if you like).
If you really think it is related to realtiming of the midi events (I still wonder how lua does not add a delay here), then a vst parameter observation should run in realtime, too.
From conceptional view, I would suggest that automation reading of a parameter is completely disabled while recording. So like an "arming" mechanism. Even on overwrite, the already existing data should not be read. Imagine a motorized fader, how annoying overwrite works then. Such a mechanism is missing Completly, AFAIK.
Or from API, something like parameter.automation_reading = false / parameter.automation_writing = true
Edited by ffx, 11 May 2017 - 08:39.