I’m coming up against a really annoying issue with a very heavily populated Hallion Live Hi Hat instrument that has a series of sublayers containing round robin groups.
I have a fully operational selector script that feeds back to GUI control and a text output box, displaying the name of the sublayer currently selected. This allows me to create one Hallion instrument but have a whole collection of converted EXS 24 round robin patches selectable from the macro page
The downside is this creates an extraordinary amount of zones
From the GUI Designer I can attach an (unscaled) knob to the sound parameters by adding this kind of thing in the Knob’s ‘Value’ Box :
@type:Layer/@type:Zone/@id:140002
This addresses every single possible zone. There is no lag on the GUI control. This parameter is changed instantly.
Certain things, though I need to scale. For example, the velocity to filter cutoff has a parameter range of -200% all the way to +200%. I need a GUI Knob to address only 0% to + 100%
It appears the zone control for this is Filter.VelocityToFilter but when building scripts that recursively search through the layers to address the zone, even though I can correctly address the parameter - it’s incredibly laggy it can take half a second for the GUI control to become responsive again
I’m pretty new to this and fully understand that Halion is way more complex than Kontakt given
Is there any way to apply the parameter to the sub layers as shown above instead of the zones ? - I’m basically looking for the scripting equivalent of this function in script:
@type:Layer/@type:Zone/@id:140002