BUG? - Automation of Volt Synth as an AU (maybe some other AUs have this issue too) RESOLVED
Volt Synth exposes all it's parameters - and the 10 macros are already set to 10 Volt parameters - but for some reason NS2 does not control Volt's parameters through either its macros or drawn automation curves. I've had another user confirm the same thing.
By the way - I believe SpaceCraft has the same issue.
I'll try and add any other AUs that have the same problem to this thread as I come across them.
P.s. I've alerted both the Volt and Spacecraft devs to this issue too.
Comments
I have confirmed the problem with AU parameter automation in Volt.
EGSY01 by Elliott Garage also
Oh, it’s worth adding too that VOLT does respond to automation when it’s hosted in AUM. You can bind midi CC’s to Volts parameters using AUMs ‘midi controls’ functionality and that works fine.
Same is true of SpaceCraft when it’s in AUM.
I’ve notified the Elliott Garage dev that he might want to get in touch with Matt. His new app, WaveShaper, is very cool but it also doesn’t respond to NS2 modulation. I did notice that the apps modulations move the knobs that they are assigned to by default so it looks like the MIDI is traveling backwards, from the app to the knob.
At AB forums is discussion about this Volt issue somebody wrote that Spacecraft synth have same issue, and dev of Spacecraft told that it is something which definitely needs to be fixed on his side.
more here: https://forum.audiob.us/discussion/comment/589942#Comment_589942
Elliott Garage synths have been fixed.
Thanks. Have updated the thread on Audiobus Forum with this news.
Volt synth will be fixed in it's next update too..
https://forum.audiob.us/discussion/30396/volt-not-responding-to-automation-in-ns2#latest