Control Surface Integration (CSI) Technical Feature Discussion

[Funkybot]

Originally Posted by MixMonkey

Whilst I agree with this in principle, I think it would be better to be able to disable AutoFX Zone generation regardless of the status of the FXMenu. A "ToggleScrollLink" type situation (with LED indicator)

Default it to on (for the newbies and the lazy and the new fx I just bought but haven't mapped yet) then something like this if you want to turn it off...

Zone "Home"
OnInitialization ToggleEnableFocusedFXMapping 
OnInitialization ToggleAutoFXMapping

[Funkybot]

The above has me thinking, should AutoFXMapping and FocusedFXMapping work together?

That would be the ultimate in luxury for new users who don't want to learn to map. But could be annoying for MM.

[MixMonkey]

Originally Posted by Funkybot

Default it to on (for the newbies) then something like this?

Zone "Home"
OnInitialization ToggleEnableFocusedFXMapping 
OnInitialization ToggleAutoFXMapping

Sure, that'll be fine (with LED!) It doesn't take much imagination to see that there will be plugins capable of throwing the whole shebang into chaos

[MixMonkey]

Originally Posted by Funkybot

The above has me thinking, should AutoFXMapping and FocusedFXMapping work together?

That would be the ultimate in luxury for new users who don't want to learn to map. But could be annoying for MM.

Can't help feeling that might not be a great combination, considering the relative unpredictability of FocusedFXMapping but i'm fine with it as long as it can be turned off

[Funkybot]

Originally Posted by MixMonkey

Can't help feeling that might not be a great combination, considering the relative unpredictability of FocusedFXMapping but i'm fine with it as long as it can be turned off

I've been strictly FXMenu for a while, but I feel like FocusedFXMapping worked great except for the one caveat of "CSI doesn't know when the FX has been unfocused". If AutoFXMapping isn't creating instability and could be added to FocusedFXMapping, I could see that providing the ultimate in slick controller behavior out of the box. Honestly, I'd stick to the FXMenu+AutoMap (for plugins I haven't mapped manually yet) approach myself, but I can definitely see a big draw to FocusedFX+AutoMap if that's workable and stable.

Just food for thought.

There are a lot of great doors being opened up by the new functionality.

[MT4U]

Originally Posted by Funkybot

I've been strictly FXMenu for a while, but I feel like FocusedFXMapping worked great except for the one caveat of "CSI doesn't know when the FX has been unfocused".

I've been using FocusedFXMapping a lot for FX Mapping, since whenever I have to do a RefreshAllSurfaces, the FX Zone gets automatically loaded.

That being said, CSI has given me no problems when the FX loses focus. It happens when I have the FX UI focused and I close it with the window close button, or by running a Reaper Action that closes it from CSI.

If, for example, I focus the TCP window first and only then I close the window from the plug-in UI or from CSI, everything is fine, since after focusing the TCP CSI goes back to the track zone.

I tried creating a script that focuses the TCP window and then closes the FX UI, but it won't work. It's as if the Reaper scripts were executed within a Transaction, and here we need to execute one thing at a time with one button.

The same thing happens if I map two consecutive actions in a button in CSI.

Right now, I have two buttons mapped in CSI. The first focuses the TCP and the second closes the FX UI.

Excuse the long post, but I've been around this for days

[MixMonkey]

Originally Posted by MT4U

Excuse the long post, but I've been around this for days

No problem It's why we all end up using the FXMenu

[MixMonkey]

I'm quite taken with the auto-generated FX.zon It strikes me that if you made this:

Zone "VST: TDR Kotelnikov (Tokyo Dawn Labs)" "Kotelnikov"

    FXRotariesA 0 1 2 3 4 5 6 7
    // "Threshold" "Peak Crest" "Soft Knee" "Ratio" "Attack" "Release Peak" "Release RMS" "Makeup"

    FXRotariesB 8 9 10 11 12 13 14 15
    // "Dry Mix" "Dry Wet" "Dry Mix Mode" "Out Gain" "SC HP Freq" "SC HP Slope" "SC Stereo Diff" "Delta"

    FXRotariesC 16 17 18 19 20 21 22 23
    // "Bypass" "Quality" "Mode" "GR Disp Scale" "GR Disp Mode" "Bypass" "Wet" "Delta"
ZoneEnd

...look more like this:

Zone "VST: TDR Kotelnikov (Tokyo Dawn Labs)"
    FXParam 0 "Threshold"
    FXParam 1 "Peak Crest"
    FXParam 2 "Soft Knee"
    FXParam 3 "Ratio"
    FXParam 4 "Attack"
    FXParam 5 "Release Peak"
    FXParam 6 "Release RMS"
    FXParam 7 "Makeup"
    FXParam 8 "Dry Mix"
    FXParam 9 "Dry Wet"
    FXParam 10 "Dry Mix Mode"
    FXParam 11 "Out Gain"
    FXParam 12 "SC HP Freq"
    FXParam 13 "SC HP Slope"
    FXParam 14 "SC Stereo Diff"
    FXParam 15 "Delta"
    FXParam 16 "Bypass"
    FXParam 17 "Quality"
    FXParam 18 "Mode"
    FXParam 19 "GR Disp Scale"
    FXParam 20 "GR Disp Mode"
    FXParam 21 "Bypass"
    FXParam 22 "Wet"
    FXParam 23 "Delta"
ZoneEnd

...then peeps would probably realise pretty quickly what they had to do to the text file to get the map they wanted. If you want an alias, change the name in "". If you want to change the assignment of parameters to controls, change the order of the list. If you want to unassign a control, replace the parameter number with -1.

I appreciate that the TCPFX template method lets you do this within Reaper, and I'm probably biased having edited thousands of these text files, but I think this would almost be easier?

[Funkybot]

Originally Posted by MT4U

Excuse the long post, but I've been around this for days

I wonder if this would work (close the windows first then GoHome):

Zone "Buttons"
F1     Reaper _S&M_WNCLS4     // Closes all(!) FX chain windows
F1     Reaper _S&M_WNCLS3     // Closes all(!) floating FX windows  
F1     GoHome

...sorry if you've already tried that, or that's not really solving the problem. I gave up on FocusedFX for basically the same reason and I don't recall what did and didn't work better.

BTW, MT4U's own CSI FX configurator has really come a long way recently. Within the last few days alone, the Mackie C4 support has really been fleshed out and you can even add colors for toggles on a surface like the Twister. Cool stuff happening everywhere with FX and CSI!

[Geoff Waddington]

Great discussion !

Here's a first cut at a solution to all of this.

Add 2 Actions

ToggleAutoFXMapping
ToggleAutoFocusedFXMapping

One thing we have with FocusedFXMapping is that if we don't have Zones defined for a surface, nothing happens.

With AutoFocusedFXMapping, every surface would light up anytime you focused an FX, CSI would create definitions if they didn't exist.




When you exit Reaper, all auto mapped Zones get deleted.

That way the startup code just has to decide between classic FX Zones and TCPFX Zones, much easier from a coding perspective.

Keeps the ideas coming folks, all good stuff.

[Geoff Waddington]

Originally Posted by MixMonkey

I'm quite taken with the auto-generated FX.zon It strikes me that if you made this:

Zone "VST: TDR Kotelnikov (Tokyo Dawn Labs)" "Kotelnikov"

    FXRotariesA 0 1 2 3 4 5 6 7
    // "Threshold" "Peak Crest" "Soft Knee" "Ratio" "Attack" "Release Peak" "Release RMS" "Makeup"

    FXRotariesB 8 9 10 11 12 13 14 15
    // "Dry Mix" "Dry Wet" "Dry Mix Mode" "Out Gain" "SC HP Freq" "SC HP Slope" "SC Stereo Diff" "Delta"

    FXRotariesC 16 17 18 19 20 21 22 23
    // "Bypass" "Quality" "Mode" "GR Disp Scale" "GR Disp Mode" "Bypass" "Wet" "Delta"
ZoneEnd

...look more like this:

Zone "VST: TDR Kotelnikov (Tokyo Dawn Labs)"
    FXParam 0 "Threshold"
    FXParam 1 "Peak Crest"
    FXParam 2 "Soft Knee"
    FXParam 3 "Ratio"
    FXParam 4 "Attack"
    FXParam 5 "Release Peak"
    FXParam 6 "Release RMS"
    FXParam 7 "Makeup"
    FXParam 8 "Dry Mix"
    FXParam 9 "Dry Wet"
    FXParam 10 "Dry Mix Mode"
    FXParam 11 "Out Gain"
    FXParam 12 "SC HP Freq"
    FXParam 13 "SC HP Slope"
    FXParam 14 "SC Stereo Diff"
    FXParam 15 "Delta"
    FXParam 16 "Bypass"
    FXParam 17 "Quality"
    FXParam 18 "Mode"
    FXParam 19 "GR Disp Scale"
    FXParam 20 "GR Disp Mode"
    FXParam 21 "Bypass"
    FXParam 22 "Wet"
    FXParam 23 "Delta"
ZoneEnd

...then peeps would probably realise pretty quickly what they had to do to the text file to get the map they wanted. If you want an alias, change the name in "". If you want to change the assignment of parameters to controls, change the order of the list. If you want to unassign a control, replace the parameter number with -1.

I appreciate that the TCPFX template method lets you do this within Reaper, and I'm probably biased having edited thousands of these text files, but I think this would almost be easier?

Cool concept !

But the Widget Assignments are missing.

Or are you saying Widget Assignment happens based on the Template Zone ?

Hmmm... pretty damn good idea, let me ponder a bit...

[edit] Or maybe it writes it out longhand, classic FX style, assigning Widgets as it goes...

[Funkybot]

Originally Posted by Geoff Waddington

Great discussion !

Here's a first cut at a solution to all of this.

Add 2 Actions

ToggleAutoFXMapping
ToggleAutoFocusedFXMapping

One thing we have with FocusedFXMapping is that if we don't have Zones defined for a surface, nothing happens.

With AutoFocusedFXMapping, every surface would light up anytime you focused an FX, CSI would create definitions if they didn't exist.




When you exit Reaper, all auto mapped Zones get deleted.

That way the startup code just has to decide between classic FX Zones and TCPFX Zones, much easier from a coding perspective.

Keeps the ideas coming folks, all good stuff.

With AutoFocusedFXMapping, lets say I do want the FX mapped across 3 surfaces (I wouldn't personally, but hypothetically..), would each surface start at FXParam 0 and repeat the mapping? Or would the first surface in the CSI.ini get Param 0 then the remaining would get distributed across multiple? Just trying to poke holes or think about this stuff in advance.

What happens when 2 different surfaces share 1 zone folder? Same mapping for both?

[Geoff Waddington]

Originally Posted by Funkybot

With AutoFocusedFXMapping, lets say I do want the FX mapped across 3 surfaces (I wouldn't personally, but hypothetically..), would each surface start at FXParam 0 and repeat the mapping? Or would the first surface in the CSI.ini get Param 0 then the remaining would get distributed across multiple? Just trying to poke holes or think about this stuff in advance.

What happens when 2 different surfaces share 1 zone folder? Same mapping for both?

It does get ugly fast, doesn't it ?

[Geoff Waddington]

Should we just drop SelectedTrackTCPFX since we have SelectedTrackTCPFXTemplate for permanent mapping, and auto map for temporary.

What real purpose does SelectedTrackTCPFX serve ?

[Geoff Waddington]

Hmmm...

If we do drop SelectedTrackTCPFX, we could make SelectedTrackTCPFXTemplate automatically build as it goes, there would be no need for the BuildSelectedTrackTCPFXZone Action.

[Geoff Waddington]

Should SelectedTrackTCPFXTemplate automatically erase a classic FX Zone ?

We are choosing to define the FX Zone, should that be enough to say "delete any existing Zone, I want to overwrite it" ?

[Funkybot]

Originally Posted by Geoff Waddington

Should we just drop SelectedTrackTCPFX since we have SelectedTrackTCPFXTemplate for permanent mapping, and auto map for temporary.

What real purpose does SelectedTrackTCPFX serve ?

I've gone back and forth on that thought myself. Here's where I land:

SelectedTrackTCPFX is great if you just want to develop workflows within CSI where you always have 8 "Quick Controls" available outside of any other FX mapping. This can build up that "Channel Strip with different plugins" type of workflow, or a Cubase-style "Quick Controls" workflow. I'm saying 8, because I think 4-8 "Quick Controls" is really all you'd ever want on a TCP FX parameter list. I think that's why I just assumed it was limited to 8 earlier today. Benefits: can control multiple FX at once, can automatically refresh as you navigate from track to track as long as those tracks utilize TCP FX.

Whereas, SelectedTrackTCPFXTemplate on the other hand, is the FX Mapping template. It leverages the SelectedTrack TCP if you're rolling your own fx.zon by hand, but doesn't leverage that at all if you're doing an AutoFXMap or AutoFocusedFX map. This is why I think it should ultimately be renamed to just FXMapTempalte or something. The SelectedTrackTCP element of it, is only in 1 of 2 current modes. May be 1 of 3 by the time you're done.

I do see the use-cases for both as being different enough to keep both allowing for multiple workflows.

That said, I'm not married to any of this other than AutoFXMapping, which I think is the bees knees. As a plugin hoarder, that thing is a Godsend (GeoffSend?).

[Funkybot]

Originally Posted by Geoff Waddington

Should SelectedTrackTCPFXTemplate automatically erase a classic FX Zone ?

We are choosing to define the FX Zone, should that be enough to say "delete any existing Zone, I want to overwrite it" ?

Absolutely not. Not ever. Not even a little.

ClassicFX zones should be treated as the gold-standard in all instances IMO.

Here's a half-formed thought...could it be used to remap ClassicFX zones or load the ClassicFX zone as a starting point? Probably not. Scratch that.

[Geoff Waddington]

Originally Posted by Funkybot

I've gone back and forth on that thought myself. Here's where I land:

SelectedTrackTCPFX is great if you just want to develop workflows within CSI where you always have 8 "Quick Controls" available outside of any other FX mapping. This can build up that "Channel Strip with different plugins" type of workflow, or a Cubase-style "Quick Controls" workflow. I'm saying 8, because I think 4-8 "Quick Controls" is really all you'd ever want on a TCP FX parameter list. I think that's why I just assumed it was limited to 8 earlier today. Benefits: can control multiple FX at once, can automatically refresh as you navigate from track to track as long as those tracks utilize TCP FX.

Whereas, SelectedTrackTCPFXTemplate on the other hand, is the FX Mapping template. It leverages the SelectedTrack TCP if you're rolling your own fx.zon by hand, but doesn't leverage that at all if you're doing an AutoFXMap or AutoFocusedFX map. This is why I think it should ultimately be renamed to just FXMapTempalte or something. The SelectedTrackTCP element of it, is only in 1 of 2 current modes. May be 1 of 3 by the time you're done.

I do see the use-cases for both as being different enough to keep both allowing for multiple workflows.

That said, I'm not married to any of this other than AutoFXMapping, which I think is the bees knees. As a plugin hoarder, that thing is a Godsend (GeoffSend?).

Good points all, we'll keep everything.

I agree we have to clean up the nomenclature somehow.

[Geoff Waddington]

Originally Posted by Funkybot

Absolutely not. Not ever. Not even a little.

ClassicFX zones should be treated as the gold-standard in all instances IMO.

That's my feeling too.

The only issue is, what happens the next day when you load an instance of a plugin and you get the classic version, and you remember that yesterday you created a TCPFX map for it ?

[Funkybot]

Originally Posted by Geoff Waddington

That's my feeling too.

The only issue is, what happens the next day when you load an instance of a plugin and you get the classic version, and you remember that yesterday you created a TCPFX map for it ?

Maybe prevent creating a new map if a Classic FX zone already exists. Just load the classic FX zone and don’t allow editing.

[Geoff Waddington]

Originally Posted by Funkybot

Maybe prevent creating a new map if a Classic FX zone already exists. Just load the classic FX zone and don’t allow editing.

That's a great idea !

[Geoff Waddington]

Working through all these proposed changes.

My thinking is that auto mapped FX should be deleted when Reaper closes.

That way there is no possibility of them hanging around and clobbering a classic FX definition that may be authored later.

After all they are temporary by nature, and will always auto map the next time that FX is instantiated, unless a permanent definition (classic or TCPFX) exists.

Those savvy enough can always copy them for later editing while Reaper is still open. We can explain this in the Wiki.



As for classic vs TCPFX:

If a classic Zone exists, mapping via TCPFX will be disabled.

If a TCPFX Zone already exists, you can re edit that via TCPFX.

Make sense ?

[Funkybot]

Makes sense to me!

[MixMonkey]

Originally Posted by Geoff Waddington

Cool concept !

But the Widget Assignments are missing.

Or are you saying Widget Assignment happens based on the Template Zone ?

Yes, exactly. Effectively this:

Zone "VST: TDR Kotelnikov (Tokyo Dawn Labs)"
    RotaryA1    0   "Threshold"
    RotaryA2    1   "Peak Crest"
    RotaryA3    2   "Soft Knee"
    RotaryA4    3   "Ratio"
    RotaryA5    4   "Attack"
    RotaryA6    5   "Release Peak"
    RotaryA7    6   "Release RMS"
    RotaryA8    7   "Makeup"
    RotaryB1    8   "Dry Mix"
    RotaryB2    9   "Dry Wet"
    RotaryB3    10  "Dry Mix Mode"
    RotaryB4    11  "Out Gain"
    RotaryB5    12  "SC HP Freq"
    RotaryB6    13  "SC HP Slope"
    RotaryB7    14  "SC Stereo Diff"
    RotaryB8    15  "Delta"
    RotaryC1    16  "Bypass"
    RotaryC2    17  "Quality"
    RotaryC3    18  "Mode"
    RotaryC4    19  "GR Disp Scale"
    RotaryC5    20  "GR Disp Mode"
    RotaryC6    21  "Bypass"
    RotaryC7    22  "Wet"
    RotaryC8    23  "Delta"
ZoneEnd

[MixMonkey]

Originally Posted by Geoff Waddington

Should we just drop SelectedTrackTCPFX since we have SelectedTrackTCPFXTemplate for permanent mapping, and auto map for temporary.

What real purpose does SelectedTrackTCPFX serve ?

SelectedTrackTCPFX fulfills a different function. It provides an easy way of allowing parameters assigned to track controls (from the same or different plugins) to appear on the surface.

I see this as being unrelated to our automapping adventures, even though the Zones used to acheive the end result are similar.

[MixMonkey]

Originally Posted by Geoff Waddington

Should SelectedTrackTCPFXTemplate automatically erase a classic FX Zone ?

Don't even think about it!

[MixMonkey]

Originally Posted by Geoff Waddington

My thinking is that auto mapped FX should be deleted when Reaper closes.

With regard to my previous posts about maybe changing the format of the auto-generated FX, I'd leave them in the AutoGeneratedFXZones folder after Reaper quits. I'm very much seeing them as a starting point that people will edit to create the Zone of their dreams.

As for classic vs TCPFX:

If a classic Zone exists, mapping via TCPFX will be disabled.

If a TCPFX Zone already exists, you can re edit that via TCPFX.

Make sense ?

This sounds good

[MixMonkey]

Originally Posted by Funkybot

Whereas, SelectedTrackTCPFXTemplate on the other hand, is the FX Mapping template......This is why I think it should ultimately be renamed to just FXMapTemplate or something.

Totally agree with this.

That said, I'm not married to any of this other than AutoFXMapping, which I think is the bees knees. As a plugin hoarder, that thing is a Godsend (GeoffSend?).

Absolutely With a few tweaks to the output format, it's a killer feature!

[Geoff Waddington]

Hmmm...

Maybe it's the manual TCP mapping that goes.

You've turned my thinking on its head

One thing that is particularly obnoxious about manual TCP mapping is the fact that the parameter layout on the TCP GUI may not necessarily, and most likely won't, match the layout on the surface.

It's actually pretty unwieldy, all in all.



So, classic remains.

TCP FX remains for quick mapping, including across multiple plugins.

SelectedTrackTCPFXTemplate manual mapping is history, but not the shorthand template Zone itself, that is is used for auto mapping.

There is a new Zone type that combines the notion of EZFXZone with the expansion characteristics of the | character.

AutoZone "VST: TDR Kotelnikov (Tokyo Dawn Labs)"
    RotaryA1    0   "Threshold"
    RotaryA2    1   "Peak Crest"
    RotaryA3    2   "Soft Knee"
    RotaryA4    3   "Ratio"
    RotaryA5    4   "Attack"
    RotaryA6    5   "Release Peak"
    RotaryA7    6   "Release RMS"
    RotaryA8    7   "Makeup"
    RotaryB1    8   "Dry Mix"
    RotaryB2    9   "Dry Wet"
    RotaryB3    10  "Dry Mix Mode"
    RotaryB4    11  "Out Gain"
    RotaryB5    12  "SC HP Freq"
    RotaryB6    13  "SC HP Slope"
    RotaryB7    14  "SC Stereo Diff"
    RotaryB8    15  "Delta"
    RotaryC1    16  "Bypass"
    RotaryC2    17  "Quality"
    RotaryC3    18  "Mode"
    RotaryC4    19  "GR Disp Scale"
    RotaryC5    20  "GR Disp Mode"
    RotaryC6    21  "Bypass"
    RotaryC7    22  "Wet"
    RotaryC8    23  "Delta"
ZoneEnd

CSI expands this to:

	DisplayUpperA1 		FixedTextDisplay "Threshold"
        DisplayLowerA1       	FXParamValueDisplay 0
        RotaryA1             	FXParam 0

etc.

This format allows for super easy reorganization, and editing in general.

What do you think ?

[Funkybot]

Get in the Zone! AutoZone!!! (If you're in the use, AutoZone is a car parts retailer, get in the zone is their slogan).

Dumb question....but if you can take the FXTemplate zone and build this...

AutoZone "VST: TDR Kotelnikov (Tokyo Dawn Labs)"
    RotaryA1    0   "Threshold"
    RotaryA2    1   "Peak Crest"
    RotaryA3    2   "Soft Knee"
    RotaryA4    3   "Ratio"
    RotaryA5    4   "Attack"
    RotaryA6    5   "Release Peak"
    RotaryA7    6   "Release RMS"
    RotaryA8    7   "Makeup"
ZoneEnd

Then why not just build this?

AutoZone "VST: TDR Kotelnikov (Tokyo Dawn Labs)"
    RotaryA1    FXParam 0   "Threshold"
    RotaryA2    FXParam 1   "Peak Crest"
    RotaryA3    FXParam 2   "Soft Knee"
    RotaryA4    FXParam 3   "Ratio"
    RotaryA5    FXParam 4   "Attack"
    RotaryA6    FXParam 5   "Release Peak"
    RotaryA7    FXParam 6   "Release RMS"
    RotaryA8    FXParam 7   "Makeup"
ZoneEnd

...hey look! It's a classic fx zone syntax just with automatic displays. Could help keep the different types more familiar and portable.

But I dig the direction you're going in. The SelectedTrackTCPFX build process was tedious and slow. Auto mapping would've been my preferred method. If these zones hang out and don't self-destruct as MM recommended, then users should be able to quickly edit and reorder.

Question: could any unassigned FXParams be written to the bottom of the zone and commented out?

AutoZone "VST: TDR Kotelnikov (Tokyo Dawn Labs)"
    RotaryA1    FXParam 0   "Threshold"
    RotaryA2    FXParam 1   "Peak Crest"
    RotaryA3    FXParam 2   "Soft Knee"
    RotaryA4    FXParam 3   "Ratio"
    RotaryA5    FXParam 4   "Attack"
    RotaryA6    FXParam 5   "Release Peak"
    RotaryA7    FXParam 6   "Release RMS"
    RotaryA8    FXParam 7   "Makeup"


/	FXParam 8 "Headroom"
/	FXParam 9 "Power"
/	FXParam 10 "Bypass"
/	FXParam 11 "Wet"
/	FXParam 12 "Delta"

ZoneEnd

...that would help make reassigning easier if everything's in one place. Obvious drawback: Arturia plugins with 3k params taking up disk space.

[MixMonkey]

Originally Posted by Geoff Waddington

What do you think ?

Yep, sounds good!

[MixMonkey]

Originally Posted by Funkybot

AutoZone "VST: TDR Kotelnikov (Tokyo Dawn Labs)"
RotaryA1 FXParam 0 "Threshold"
RotaryA2 FXParam 1 "Peak Crest"
RotaryA3 FXParam 2 "Soft Knee"
RotaryA4 FXParam 3 "Ratio"
RotaryA5 FXParam 4 "Attack"
RotaryA6 FXParam 5 "Release Peak"
RotaryA7 FXParam 6 "Release RMS"
RotaryA8 FXParam 7 "Makeup"
ZoneEnd
[/code]

...hey look! It's a classic fx zone syntax just with automatic displays. Could help keep the different types more familiar and portable.

Do we want to suggest that this AutoZone is akin to the classic method? Will it still allow classic syntax to be tagged on the end?

Question: could any unassigned FXParams be written to the bottom of the zone and commented out?

AutoZone "VST: TDR Kotelnikov (Tokyo Dawn Labs)"
    RotaryA1    FXParam 0   "Threshold"
    RotaryA2    FXParam 1   "Peak Crest"
    RotaryA3    FXParam 2   "Soft Knee"
    RotaryA4    FXParam 3   "Ratio"
    RotaryA5    FXParam 4   "Attack"
    RotaryA6    FXParam 5   "Release Peak"
    RotaryA7    FXParam 6   "Release RMS"
    RotaryA8    FXParam 7   "Makeup"


/	FXParam 8 "Headroom"
/	FXParam 9 "Power"
/	FXParam 10 "Bypass"
/	FXParam 11 "Wet"
/	FXParam 12 "Delta"

ZoneEnd

...that would help make reassigning easier if everything's in one place. Obvious drawback: Arturia plugins with 3k params taking up disk space.

I'd be inclined to print the entire parameter list on the end, commented out. That way, when someone makes a mistake or changes their mind, they have the complete list to refer to, to make repairs

[Funkybot]

Originally Posted by MixMonkey

Do we want to suggest that this AutoZone is akin to the classic method? Will it still allow classic syntax to be tagged on the end?

I was assuming so. You can modify the current-state zones and add rows below to set push states for buttons, add additional displays and widgets, etc. just like ClassicFX zones.

[Geoff Waddington]

Originally Posted by Funkybot

Get in the Zone! AutoZone!!! (If you're in the use, AutoZone is a car parts retailer, get in the zone is their slogan).

I was waiting for someone to do that, figured it would be you

[Geoff Waddington]

Good point on adding things at the end.

That means goodbye AutoZone, and hello this:

Zone "VST: TDR Kotelnikov (Tokyo Dawn Labs)"
    Expand+RotaryA1    FXParam 0   "Threshold"
    Expand+RotaryA2    FXParam 1   "Peak Crest"
    Expand+RotaryA3    FXParam 2   "Soft Knee"
    Expand+RotaryA4    FXParam 3   "Ratio"
    Expand+RotaryA5    FXParam 4   "Attack"
    Expand+RotaryA6    FXParam 5   "Release Peak"
    Expand+RotaryA7    FXParam 6   "Release RMS"
    Expand+RotaryA8    FXParam 7   "Makeup"


/ 8 "Headroom"
/ 9 "Power"
/ 10 "Bypass"
/ 11 "Wet"
/ 12 "Delta"

ZoneEnd

this would allow for adding things at the end, since it is really just a classic Zone with a new modifier.

Better ?

[MixMonkey]

Originally Posted by Geoff Waddington

Good point on adding things at the end.

That means goodbye AutoZone, and hello this:

Zone "VST: TDR Kotelnikov (Tokyo Dawn Labs)"
    Expand+RotaryA1    FXParam 0   "Threshold"
    Expand+RotaryA2    FXParam 1   "Peak Crest"
    Expand+RotaryA3    FXParam 2   "Soft Knee"
    Expand+RotaryA4    FXParam 3   "Ratio"
    Expand+RotaryA5    FXParam 4   "Attack"
    Expand+RotaryA6    FXParam 5   "Release Peak"
    Expand+RotaryA7    FXParam 6   "Release RMS"
    Expand+RotaryA8    FXParam 7   "Makeup"


/ 8 "Headroom"
/ 9 "Power"
/ 10 "Bypass"
/ 11 "Wet"
/ 12 "Delta"

ZoneEnd

this would allow for adding things at the end, since it is really just a classic Zone with a new modifier.

Better ?

I dig!

Thinking about where this might be going, I wonder if we can integrate the RotaryPush into the scheme?

Firstly, by including it in the TCPFXTemplate and secondly by providing an Action that will flip the upper and lower displays from the Rotary to the Push (maybe even use Flip), so that it's easy to see the assignments.

[Funkybot]

Originally Posted by Geoff Waddington

Good point on adding things at the end.

That means goodbye AutoZone, and hello this:

Zone "VST: TDR Kotelnikov (Tokyo Dawn Labs)"
    Expand+RotaryA1    FXParam 0   "Threshold"
    Expand+RotaryA2    FXParam 1   "Peak Crest"
    Expand+RotaryA3    FXParam 2   "Soft Knee"
    Expand+RotaryA4    FXParam 3   "Ratio"
    Expand+RotaryA5    FXParam 4   "Attack"
    Expand+RotaryA6    FXParam 5   "Release Peak"
    Expand+RotaryA7    FXParam 6   "Release RMS"
    Expand+RotaryA8    FXParam 7   "Makeup"


/ 8 "Headroom"
/ 9 "Power"
/ 10 "Bypass"
/ 11 "Wet"
/ 12 "Delta"

ZoneEnd

this would allow for adding things at the end, since it is really just a classic Zone with a new modifier.

Better ?

Me likey.

[MT4U]

Originally Posted by MixMonkey

I dig!

Thinking about where this might be going, I wonder if we can integrate the RotaryPush into the scheme?

Firstly, by including it in the TCPFXTemplate and secondly by providing an Action that will flip the upper and lower displays from the Rotary to the Push (maybe even use Flip), so that it's easy to see the assignments.

Interesting... and what if the ToggleChannel functionality was involved?

[MixMonkey]

Originally Posted by MT4U

Interesting... and what if the ToggleChannel functionality was involved?

ToggleChannel?