first of all, thanks for letting me join the Beta Group! This is my first Post
I want to report a Problem with the VSTi Sub Phatty Editor regarding Automation of VST Parameters.
This is NOT new to Beta 3 and exists since the first Release Version.
ā The Automation will only be written when touching the Editor Knobs with the Mouse. As soon as I move the Knobs on the Sub Phatty, the DAW (Cubase, or Studio One 3 in my case) will get no āautomation dataā Only workaround is recording MIDI CC Data. Which is in 14bit mode very annoying to editā¦
During my times of working for Steinberg and Presonus, we often had PlugIns with that behavior.
In most cases the āon editā flag was missing or only when using the mouse. Or the Automation stuff was handled in the GUI Thread and not within the processing Thread. Many DAWās will ignore Automation or MIDI generation from within the GUI Threadā¦
If it works in some DAWās, this is more or less a āHackā on the Host Side.
Open the SubPhatty Editor in Cubase Or Studio ONE 3
set the Editor to Automation Write, Touch or Latch
Record some Automation Data e.g Cutoff with the Mouse
Now, simply move the Cutoff Knob on the Sub Phatty.
ā No Automation will be written
This is my personal number 1 Use-Case with the Editor: Recording Automation!!!
I really hope on day we get a working version. Other PlugIn Remotes like the āSoundTower - Prophet 08 Editorā
are working really nice. Jus just turn some Knobs and get āVST Automation Dataā instead of MIDI recordingsā¦
tested VST2 and VST3 within Studio One and Cubase 8.5
RME Multiface @ 64 Samples Latency
Thanks for the feedback. Iām actually surprised because this issue should have been addressed in 2.0.0b2.
it already use the processing thread for notifying DAW about parameters change and I can record VST automation data just fine from hardware knobs (2.0.0b3 VST2 and Cubase 7 x64 under Windows 7 x64)
Will check on Studio one asap but Iām surprised it donāt work for you.
Excuse me if this doesnāt make sense, but when we worked on the Minitaur we were told that the previous installation should be wiped out completely from the OS (in pc CCleaner and mac this one as well as AppTrap, in both making sure the plugin is uninstalled as well) before installing a new version.
Maybe this is why @dudabeats is still getting this bug?
The main issue I am dealing with now (in Cubase) is the automation not being totally reliable and returning the sound back to the original state that it was in at the start of any song. This bug was confirmed by Gil.
