Hi!
To start off with, the system in question here is Mac, Snow Leopard, although this should not be of any concern to be able to reproduce the issue mentioned, and system specs does not really seem relevant either. As for version of Hydra, it's version 1.2 for Mac OS X, downloaded yesterday from my service account. Issue described is the same for both AudioUnit as well as VST versions of the plugin.
I've been mapping up Hydra using Automap, creating a proper layout for editing the sounds, to both get to know Hydra as well as speed up my patch editing whenever there is twiddling to be done.
I know from the manual that the routing mode is not meant to be automated, which is why it is not mapped to any MIDI CC either. But it is available through the automation parameters exposed on the AudioUnit and VST interfaces, which is the way that Automap is hooking into the controls to map them to the faders, rotaries and buttons.
I have found a quite strange behavior when it comes to just the Osc-Routing parameter however, as any value in the range of 0 < 1 switches it over to Routing type A, and value 1 switches it over to Routing type B. Thus, these two routing types are possible to map currently.
Whenever changing it over to Routing Type C using the GUI the value simply stays at 1, and no other parameters are changed either according to the automation recording I'm doing.
If I try to directly set the Osc-Routing value to 1, it jumps to type B, anything lower than 1 (0.99 and all the way down to 0) it jumps to type A.
What I'm asking is simply if it would be possible to make sure that type C is enabled somewhere on that value range as well? It is simply the only thing missing to be able to make a 100% template where you have everything at your fingertips!
A added bonus, on top of the Novation Automap crowd, would be that the same functionality would also work fine Maschine's VST hosting, which also suffers from the same issue today.
Hydra - Routing via automation parameter.Moderators: Christophe, Mark
4 posts
• Page 1 of 1
Re: Hydra - Routing via automation parameter.IIRC it used 0-1-2 as parameter values for the Model switch, which is why it wasn't automatable or supposed to be (then of course automating the model would cause zipper noise anyways).
Admin - Synapse Audio Software
Twitter - www.twitter.com/SynapseAudio Facebook - www.facebook.com/SynapseAudioOfficial
Re: Hydra - Routing via automation parameter.Hi Richard and thank you for the response!
It sounds quite possible that Type C is assigned to the value 2 internally, however the actual parameter interval seems to only go from 0 to 1... However I try (AudioUnit + VST in Live and AudioUnit in Logic), I cannot manage to the the value high enough to tip the Routing over to Type C. As you say, it's not really to be automated, but it would simplify editing the patches through various editing tools (such as Automap and Maschine which helps to map controls to hardware controllers) and I guess also preset managers such as Kore and similar could benefit from being able to read as well as set the value properly...
Re: Hydra - Routing via automation parameter.I've put some info in the other thread I started about Hydra and automap (http://forum.synapse-audio.com/viewtopic.php?f=7&t=8846&p=92113#p92113), but thought I'd leave a easy to follow trail here as well:
Automap template has been made available which is affected by the above restriction (meaning that only Type A and Type B can be selected without clicking in the GUI). In case you were to modify the behavior of the automation parameter, please bump this thread and I'll make sure to update the Automap template to adapt to the changes!
4 posts
• Page 1 of 1
Who is onlineUsers browsing this forum: No registered users and 119 guests |
© 2017 Synapse Audio Software. All Rights Reserved. |