View Single Post
Old 07-31-2019, 03:37 PM   #3485
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,183
Default

Quote:
Originally Posted by MixMonkey View Post
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
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com

Last edited by Geoff Waddington; 07-31-2019 at 03:45 PM.
Geoff Waddington is offline   Reply With Quote