Quote:
Originally Posted by MixMonkey
Yep, top in the FX Chain window (or top position in the mixer channel)
|
OK, got it.
Reaper uses fxIndex not name to access params
When CSI maps the "Top" Zone it sets the index, so Zone "VST3: Oxford Dynamics (Sonnox)" and Zone "VST3: bx_digital V3 (Plugin Alliance)" are fine, they get fxIndex 0, and 1, respectively.
So far so good.
But...
The subzones never get their index set, so they always use the default, which is 0.
That's why they act so weird, unless they are in the first slot -- slot 0 -- the default is perfect here.
So, what we need is a way to tie SubZones such that when the parent index gets set, the subZones do too.
Let's toss some syntax ideas around...
Code:
Zone MainFX
BindIndex SubMainFX1
BindIndex SubMainFX2
....
ZoneEnd
Zone SubMainFX1
....
ZoneEnd
Zone SubMainFX2
....
ZoneEnd
Pretty clunky, how about we bring back the notion of SubZone, only now it has nothing to do with stacks, etc., it just means it has the same properties (e.g. index) as another Zone.
Code:
Zone MainFX
SubZone SubMainFX1
SubZone SubMainFX2
....
ZoneEnd
Zone SubMainFX1
....
ZoneEnd
Zone SubMainFX2
....
ZoneEnd
That looks better...
Anyone think of a better one, please chime in !!!
[edit]
Just thought of a much better one, both from a clarity and implementation perspective:
Code:
Zone MainFX
....
ZoneEnd
Zone SubMainFX1
ParentZone MainFX
....
ZoneEnd
Zone SubMainFX2
ParentZone MainFX
....
ZoneEnd