Control Surface Integration (CSI) Technical Feature Discussion

[Geoff Waddington]

Originally Posted by Funkybot

Just want to add: I think the key to this request is that this is with an X-Touch One, using I'm assuming a "SelectedTrack" zone.

Correct me if I'm wrong, but I think the ask here is:

1. I select multiple tracks in Reaper
2. I move the fader with my mouse - it creates a quick group and moves all faders

CSI should work the same way with the SelectedTrack zones but instead, all faders go to zero.

This is by design.

Selected Track means exactly one Selected Track in CSI.

Discussion indicated that it was too risky to do it any other way, given the small size of most Surfaces, especially one Fader Surfaces, a user could affect Tracks they weren't even aware of, Selected Tracks that where way out of view of the Surface.

So, it seemed the logical way to go was to have CSI define SelectedTrack as a uniquely Selected Track.

[UNdark]

Originally Posted by Funkybot

Nice job on the fix Geoff! And MixMonkey on the assist!

One for the CSI v3 feature request list that occurred to me today while updating the old Reapinger BCF-2000 CSI files in another thread...

SomeButton    SelectTracksNamed "Drums"
SomeButton    SelectTracksNamed "Kick*"
SomeButton    SelectTracksNamed "Snare*"
SomeButton    SelectTracksNamed "Tom*"

The intent would be that CSI would locate any tracks in Reaper with the names in the quotation marks and select them. The idea being that people could combine those with other actions to create macro actions to only show the drums, or only show vocal tracks, etc. without having to use a Folder workflow which can be detrimental for CPU use. Why not just use existing scripts that do that? Not portable from a CSI perspective. The * would be a wildcard to pick up Kick In and Kick Out tracks.

Obviously there are other priorities and this isn't super important by any means but wanted to suggest it before I forgot!

Thats exactly how i use reaper, then CSI follows suite to a button. It takes a teeny bit of work inside reaper but if CSI could do it all the better!!

[leejul]

Originally Posted by MixMonkey

ZIP up your CSI folder and post it, I’ll take a look

Here is the download link:
thanks a lot for your help.
https://1drv.ms/u/s!AldObfqUjgIth50D...ScDTA?e=OrmfHW

[Geoff Waddington]

Funkybot, do you have a reliable, repeatable, test case of a plugin that crashes auto map ?

[luiza177]

Some questions/feature requests EDIT: just realized these things were just being talked about a few posts earlier... Sorry about that.

a) For one-fader devices, is there a way to have the one fader control all selected track? Similar to the default behavior with a mouse.

b) Is it possible to go from one Zone to another's SubZone with one button press? I tried stacking the lines like this, but that doesn't seem to work.

[Funkybot]

Originally Posted by Geoff Waddington

Funkybot, do you have a reliable, repeatable, test case of a plugin that crashes auto map ?

It was anything with over 48 automation parameters. I had 48 params in my SelectedTrackTCPFXTemplate.zon file. Anything less than that # was working.

Here's the Mac download for Arturia's Tube-STA plugin (seems like it would be up your alley). They have bonkers # of automation params so that will probably be a good stress test for the auto-map:
https://dl.arturia.net/products/comp...1_5_0_4061.pkg

...other than the insane automation param thing, it's quite a fine plugin.

If you need me to rollback to the crashy build to find something else, I can. It was a Visual C++ Runtime crash each time, so it's possible it's Windows only.

[Funkybot]

Originally Posted by Geoff Waddington

This is by design.

Selected Track means exactly one Selected Track in CSI.

Discussion indicated that it was too risky to do it any other way, given the small size of most Surfaces, especially one Fader Surfaces, a user could affect Tracks they weren't even aware of, Selected Tracks that where way out of view of the Surface.

So, it seemed the logical way to go was to have CSI define SelectedTrack as a uniquely Selected Track.

I agree with this BTW, but there's been two or three recent requests to change that now. That said, I totally understand the idea of "just make it work like the quick groups in Reaper". So I can see it both ways (the current "play it safe" vs the "quick groups"). Worst case as an end-user, you screw up multiple tracks and just have to Undo one or more times when you notice. One to contemplate for the v3 Feature Request list.

[MT4U]

I found this strange behavior in the SelectedTrackFXMenu.

Scenario: X-Touch + X-Touch Extender (Win10).

1) On the X-Touch, I press a button mapped to GoSelectedTrackFXMenu.
2) Both surfaces show the SelectedTrackFXMenu, everything works as expected.
3) I press again GoSelectedTrackFXMenu.
4) The Extender goes back to the track zone, X-Touch stays put.
5) I press again GoSelectedTrackFXMenu.
4) The X-Touch goes back to the track zone.

EDIT: The same occurs with GoSelectedTrackSend

[Geoff Waddington]

Originally Posted by MT4U

I found this strange behavior in the SelectedTrackFXMenu.

Scenario: X-Touch + X-Touch Extender (Win10).

1) On the X-Touch, I press a button mapped to GoSelectedTrackFXMenu.
2) Both surfaces show the SelectedTrackFXMenu, everything works as expected.
3) I press again GoSelectedTrackFXMenu.
4) The Extender goes back to the track zone, X-Touch stays put.
5) I press again GoSelectedTrackFXMenu.
4) The X-Touch goes back to the track zone.

EDIT: The same occurs with GoSelectedTrackSend

Seems like it might be related to Broadcast/Receive.

Please post the Home Zones for both devices.

[Funkybot]

Originally Posted by Geoff Waddington

Seems like it might be related to Broadcast/Receive.

Please post the Home Zones for both devices.

Hi Geoff, any thoughts with my Broadcast/Receive issues from last night? Am I doing something wrong? Potential bug? Can do some more testing tonight.

[Geoff Waddington]

Originally Posted by Funkybot

Hi Geoff, any thoughts with my Broadcast/Receive issues from last night? Am I doing something wrong? Potential bug? Can do some more testing tonight.

Not sure, didn't see anything obvious.

[Geoff Waddington]

New build is up.

CSI Exp.zip

Possible fix for auto map crash.

[Funkybot]

Originally Posted by Geoff Waddington

New build is up.

CSI Exp.zip

Possible fix for auto map crash.

Some good news. This produced with no crashing...

Zone "VST3i: UADx Waterfall B3 Organ (Universal Audio (UADx))" ""

	FXRotariesA 0 1 2 3 4 5 6 7
	// "Upper 16" "Upper 5 1/3" "Upper 8" "Upper 4" "Upper 2 2/3" "Upper 2" "Upper 1 3/5" "Upper 1 1/3"

	FXRotariesB 8 9 10 11 12 13 14 15
	// "Upper 1" "Lower 16" "Lower 5 1/3" "Lower 8" "Lower 4" "Lower 2 2/3" "Lower 2" "Lower 1 3/5"

	FXRotariesAShift 16 17 18 19 20 21 22 23
	// "Lower 1 1/3" "Lower 1" "Pedal 16" "Pedal 8" "Upper MIDI Ch" "Lower MIDI Ch" "Pedals MIDI Ch" "Split"

	FXRotariesBShift 24 25 26 27 28 29 30 31
	// "Split Swap" "Split Key" "Lower Transpose" "Upper Transpose" "Vol Switch" "Vib Upper" "Vib Lower" "Vibrato-Chorus"

	FXRotariesAOption 32 33 34 35 36 37 38 39
	// "Perc On/Off" "Perc Vol" "Perc Decay" "Perc Harm" "Swell Pedal" "Preamp Tone" "Reverb" "Rotary Enable"

	FXRotariesBOption 40 41 42 43 44 45 46 47
	// "Rotary Speed" "CC64 Function" "Rotary Volume" "Rotary Drive" "Rotary Mic Level" "Mic Balance" "Drum Mic" "Drum Position"
ZoneEnd

...first thing that stuck out: the FXMenuName alias is a blank string in line 1. That's happening on multiple AutoFXMap zones in this build. Used to work reliably. Now that part is inconsistent.

...second thing with that particular zone: OSC works. MIDI does not. I think that's because most, if not all, are stepped params. If yes, we can table that part for now.

Next, I tried this, but it crashed upon GoFXSlot...

Zone "VSTi: Strobe2 (FXpansion)" ""

	FXRotariesA 0 1 2 3 4 5 6 7
	// "Perf1" "Perf2" "PerfX" "PerfY" "Perf3" "Cutoff" "Res" "CtffEnv"

	FXRotariesB 8 9 10 11 12 13 14 15
	// "ModA" "ModD" "ModS" "ModR" "Saw" "Pls" "SubSin" "SubTri"

	FXRotariesAShift 16 17 18 19 20 21 22 23
	// "SubPls" "SubSaw" "Noise" "Pw" "AmpA" "AmpD" "AmpS" "AmpR"

	FXRotariesBShift 24 25 26 27 28 29 30 31
	// "FltDrv" "Amp" "CtffKy" "CtffLf" "LfoMode" "LfoRate" "LfoSync" "LfoPhas"

	FXRotariesAOption 32 33 34 35 36 37 38 39
	// "LfoPw" "LfoSwin" "PwEnv" "PwLfo" "PwKey" "Pitch" "PitchEn" "PitchLf"

	FXRotariesBOption 40 41 42 43 44 45 46 47
	// "PitchKe" "Level" "BendUp" "BendDn" "GldMd" "Legato" "Rtrggr" "Priorit"

Notice that it did the mapping but it's missing the ZoneEnd row. Otherwise, it's all good!

But along the way, I learned something: I loaded this on a track but never actually hit the GoFXSlot to map it...

Zone "VSTi: Cypher (FXpansion)" ""
	FXRotariesA 0 1 2 3 4 5 6 7
ZoneEnd

...so it creates an AutoMap for the first 8 params on load, but doesn't build the larger maps until you GoFXSlot. That was interesting. No idea if it's meaningful though.

This did not crash and produced the alias...

Zone "VST: Dist COLDFIRE (Arturia)" "Dist COLDFIRE"

	FXRotariesA 0 1 2 3 4 5 6 7
	// "On/Off" "Input Volume" "Output Volume" "Mix" "Color" "Routing Balance" "Routing Band Split" "Distortion A Output Level"

	FXRotariesB 8 9 10 11 12 13 14 15
	// "Distortion A Dry/Wet" "Distortion A Slot Bypass" "Distortion A Pre Filter Bypass" "Distortion A Pre Filter Freq" "Distortion A Comb Filter Freq" "Distortion A Pre Filter Q" "Distortion A Post Filter Bypass " "Distortion A Post Filter HP Freq"

	FXRotariesAShift 16 17 18 19 20 21 22 23
	// "Distortion A Post Filter LP Freq" "Distortion A Distortion Bypass" "Distortion A Module Type" "Distortion A Drive" "Distortion A Bitcrusher Frequenc" "Distortion A Bitcrusher Jitter" "Distortion A Bitcrusher Aliasing" "Distortion A Bit Inverter Bit 1 "

	FXRotariesBShift 24 25 26 27 28 29 30 31
	// "Distortion A Bit Inverter Bit 2 " "Distortion A Bit Inverter Bit 3 " "Distortion A Bit Inverter Bit 4 " "Distortion A Bit Inverter Bit 5 " "Distortion A Bit Inverter Bit 6 " "Distortion A Bit Inverter Bit 7 " "Distortion A Bit Inverter Bit 8 " "Distortion A Rectifier Center"

	FXRotariesAOption 32 33 34 35 36 37 38 39
	// "Distortion A Tube Profile" "Distortion B Output Level" "Distortion B Dry/Wet" "Distortion B Slot Bypass" "Distortion B Pre Filter Bypass" "Distortion B Pre Filter Freq" "Distortion B Comb Filter Freq" "Distortion B Pre Filter Q"

	FXRotariesBOption 40 41 42 43 44 45 46 47
	// "Distortion B Post Filter Bypass " "Distortion B Post Filter HP Freq" "Distortion B Post Filter LP Freq" "Distortion B Distortion Bypass" "Distortion B Module Type" "Distortion B Drive" "Distortion B Bitcrusher Frequenc" "Distortion B Bitcrusher Jitter"
ZoneEnd

...and the Encoder knobs worked, but the knob behavior was like some messed up stepped param that went between 0 and some random value. Even on continuous params. Very odd. I suspect this is because of the billion automation parameters Arturia uses for every plugin (about 3,000 in reality).

This zone worked like a champ (UA for the win again)...

Zone "VST3: UADx Galaxy Tape Echo (Universal Audio (UADx))" "Galaxy Tape Echo"

	FXRotariesA 0 1 2 3 4 5 6 7
	// "Echo Pan" "Rev Pan" "Input Vol" "Input Send" "Head Sel" "Bass" "Treble" "Rev Vol"

	FXRotariesB 8 9 10 11 12 13 14 15
	// "Sync" "Echo Rate ms" "Echo Rate Note" "Feedback" "Echo Vol" "Loop Age" "Loop Splice" "Wet Solo"

	FXRotariesAShift 16 17 18 19 20 21 -1 -1
	// "Output Vol" "Power" "Master Bypass" "Bypass" "Wet" "Delta" "NoAction" "NoAction"

	FXRotariesBShift -1 -1 -1 -1 -1 -1 -1 -1
	// "NoAction" "NoAction" "NoAction" "NoAction" "NoAction" "NoAction" "NoAction" "NoAction"

	FXRotariesAOption -1 -1 -1 -1 -1 -1 -1 -1
	// "NoAction" "NoAction" "NoAction" "NoAction" "NoAction" "NoAction" "NoAction" "NoAction"

	FXRotariesBOption -1 -1 -1 -1 -1 -1 -1 -1
	// "NoAction" "NoAction" "NoAction" "NoAction" "NoAction" "NoAction" "NoAction" "NoAction"
ZoneEnd

...notice that the alias is there and this has less than 48 params.

I'm not sure if any of this is helpful. If there's a specific test or set of tests or specific plugins you want me to try, let me know.

[MT4U]

Originally Posted by Geoff Waddington

Please post the Home Zones for both devices.

X-Touch

Zone Home
    OnInitialization ToggleEnableFocusedFX
    OnInitialization Broadcast Home SelectedTrackFXMenu TrackSend TrackReceive TrackFXMenu SelectedTrackSend SelectedTrackReceive TCPFX VCA Folder FXSlot SelectedTrackFXMenuBank ToggleEnableFocusedFXMapping SelectedTrackSendBank SelectedTrackReceiveBank
    OnInitialization Receive Home SelectedTrackFXMenu TrackSend TrackReceive TrackFXMenu SelectedTrackSend SelectedTrackReceive TCPFX VCA Folder FXSlot
//
    IncludedZones
       Buttons
       Track
       MasterTrack
    IncludedZonesEnd
    AssociatedZones
       SelectedTrackSend
       SelectedTrackReceive
       SelectedTrackFXMenu
       TrackSend
       TrackReceive
       TrackFXMenu
       VCA
       Folder
       SelectedTrackTCPFX
    AssociatedZonesEnd
ZoneEnd

Extender:

Zone "Home"
    OnInitialization Receive Home SelectedTrackFXMenu TrackSend TrackReceive TrackFXMenu SelectedTrackSend SelectedTrackReceive TCPFX VCA Folder FXSlot SelectedTrackFXMenuBank ToggleEnableFocusedFXMapping SelectedTrackSendBank SelectedTrackReceiveBank 
    OnInitialization Broadcast Home SelectedTrackFXMenu TrackSend TrackReceive TrackFXMenu SelectedTrackSend SelectedTrackReceive TCPFX VCA Folder FXSlot
//
        IncludedZones
          Track
        IncludedZonesEnd
//        
        AssociatedZones
          SelectedTrackSend
          SelectedTrackReceive
          SelectedTrackFXMenu
          TrackSend
          TrackReceive
          TrackFXMenu
          VCA
          Folder
          SelectedTrackTCPFX
        AssociatedZonesEnd
ZoneEnd

I think I may have a couple of Broadcasts that are no more...

[Funkybot]

Originally Posted by Geoff Waddington

Not sure, didn't see anything obvious.

Me neither. Just feels like Home isn't being broadcast/received properly.

At some point this week, I'll see if I can dig further. Maybe if two surfaces share a zone and then a third does not, broadcast/receive doesn't work between the odd one out? Will play around.

[Funkybot]

I should add: I did just create 11 AutoMaps from 11 different vendors without major issue (aside from the occasional missing alias). Including many plugins with >48 params. So the crashing isn't an all the time thing nor are the missing aliases.

[Geoff Waddington]

New build is up.

CSI Exp.zip

Funkybot, please re run the tests from your previous post and report what happens.

[edit] Take a look at the step sizes file, you will immediately see why COLDFIRE is such a dog's breakfast

We'll have to painstakingly go through the whole step sizes file and clean out the junk

Since you provided all of Arturia ones, I'll leave them up to you.

Seriously, I'll have a go at that file tomorrow, eliminating any sketchy ones.

[Funkybot]

Originally Posted by Geoff Waddington

New build is up.

CSI Exp.zip

Funkybot, please re run the tests from your previous post and report what happens.

[edit] Take a look at the step sizes file, you will immediately see why COLDFIRE is such a dog's breakfast

We'll have to painstakingly go through the whole step sizes file and clean out the junk

Since you provided all of Arturia ones, I'll leave them up to you.

Seriously, I'll have a go at that file tomorrow, eliminating any sketchy ones.

Yes, let's remove anything with the word Arturia in the row.

I honestly thought COLDFIRE was only released after I created the ZoneStepSizes, but I guess my memory is getting corrupt.

About to commence retesting.

[Funkybot]

Ok, the new build works great. No alias problems. No crashing.

Nice one Geoff!

[Geoff Waddington]

Originally Posted by Funkybot

Ok, the new build works great. No alias problems. No crashing.

Nice one Geoff!

Great news, thanks for all the effort !

I'll clean up the step sizes file tomorrow.

[claytownproductions]

Originally Posted by Funkybot

Just want to add: I think the key to this request is that this is with an X-Touch One, using I'm assuming a "SelectedTrack" zone.

Correct me if I'm wrong, but I think the ask here is:

1. I select multiple tracks in Reaper
2. I move the fader with my mouse - it creates a quick group and moves all faders

CSI should work the same way with the SelectedTrack zones but instead, all faders go to zero.

You are correct, good sir. Thank you helping me articulate that

[Geoff Waddington]

New build is up.

CSI Support Files.zip

CSI Exp.zip

First pass at cleaning up the step size file.

Arturia was the worst, followed closely by izotope, with Fuse and Acon running a distant 3rd and 4th.

Please report any others you have trouble with and I'll investigate.

Also added the auto map fixes to the TCPFX build, although you are much less likely to hit issues there, as the process is manual.

[Freex]

Originally Posted by Geoff Waddington

New build is up.

CSI Support Files.zip

CSI Exp.zip

First pass at cleaning up the step size file.

Arturia was the worst, followed closely by izotope, with Fuse and Acon running a distant 3rd and 4th.

Please report any others you have trouble with and I'll investigate.

Also added the auto map fixes to the TCPFX build, although you are much less likely to hit issues there, as the process is manual.

While we're on the autostepsize subject, what why does it work, obviously i have zones already created to deal with some issues, but going forward?

[Geoff Waddington]

Originally Posted by Freex

While we're on the autostepsize subject, what why does it work, obviously i have zones already created to deal with some issues, but going forward?

It's simply a list of about 1000 or so plugins and all their step values so that you don't have to do this:

    SomeControl  FXParam 6 [ 0.0 0.5 1.0 ]

It just automatically uses the values from the step size list if available.

[MixMonkey]

Originally Posted by leejul

Here is the download link:
thanks a lot for your help.
https://1drv.ms/u/s!AldObfqUjgIth50D...ScDTA?e=OrmfHW

Ok, a few things here

Firstly SubZones can't have SubZones; your Automation Zone has a SubZone AutomationHelp, but is itself a SubZone of Buttons. You've included AutomationHelp as a SubZone of Buttons, so I think you get this, just get rid of the extra SubZone definition in Automation.

I would be inclined to put all your SubZone definitions into Buttons unless you specifically need the Navigator action of a particular Zone (Track, for instance) You've pretty much done this already, and it's a good policy.

Pick a single button on the surface and define it as GoHome in the Buttons Zone. Don't redefine that button in any other Zones and don't use any other buttons to GoHome. Your sanity will thank you for it

I think the reason your Automation SubZone (in Buttons) doesn't work properly in the SelectedTrackFXMenu Zone is because the inputs button you've used to GoSubZone appears in the SelectedTrackFXMenu Zone without an Action attached; and in the Automation SubZone, the returning action is GoHome, not LeaveSubZone. This means you'll exit the SelectedTrackFXMenu when you exit the Automation SubZone, as everything is going home.

You're building quite a complicated web of Zones and SubZones here and you'll probably make your life easier if you don't change your main Zone navigation button definitions from Zone to Zone ie keep MidiTracks, Inputs, AudioTracks, AudioInstrument, Aux, Busses, Outputs and User the same in every Zone. Use the same button to LeaveSubZone as you did to GoSubZone.

[MixMonkey]

Could I have some clarification on the (current) purpose of these three Zone types please? Thanks

SelectedTrackTCPFX
SelectedTrackTCPFXTemplate
RotaryFXMapTemplate

[Funkybot]

Originally Posted by MixMonkey

Could I have some clarification on the (current) purpose of these three Zone types please? Thanks

SelectedTrackTCPFX
SelectedTrackTCPFXTemplate
RotaryFXMapTemplate

SelectedTrackTCPFX - this is used for mapping widgets to the TCP controls of the selected track. This is like the "Cubase Quick Controls" style workflow.

SelectedTrackTCPFXTemplate - this is used for creating fx.zon files using the TCP controls as the mapping utility. Maybe needs a better name?

RotaryFXMapTemplate - I suspect that's just a holdover in the Support Files from a prior iteration of the above.

[MixMonkey]

Thanks @funkybot

Originally Posted by Funkybot

SelectedTrackTCPFX - this is used for mapping widgets to the TCP controls of the selected track. This is like the "Cubase Quick Controls" style workflow.

Does this accomodate more than 8 controls? I'm trying it out on the iPad and I have A1 - D8 in the SelectedTrackTCPFX Zone, but all I get is the first 8 parameters repeated across B,C and D.

SelectedTrackTCPFXTemplate - this is used for creating fx.zon files using the TCP controls as the mapping utility. Maybe needs a better name?

How does this differ from SelectedTrackTCPFX?

RotaryFXMapTemplate - I suspect that's just a holdover in the Support Files.

I'll ignore this for now.

[Funkybot]

Originally Posted by MixMonkey

Does this accomodate more than 8 controls? I'm trying it out on the iPad and I have A1 - D8 in the SelectedTrackTCPFX Zone, but all I get is the first 8 parameters repeated across B,C and D.

This is all real new, so take all of this with a grain of salt, and Geoff can chime in and correct anything that's wrong...

I think SelectedTrackTCPFX are just really meant for "Quick Controls" and may indeed be limited to just 8.

SelectedTrackTCPFXTemplate uses a different syntax and can map multiple rows. It's also used for the Auto Mapping functionality.

For the C4, you'd set it up as such if you wanted to use rows A-D and then also have Shift for more options....

Zone "SelectedTrackTCPFXTemplate"

	FXRotariesATemplate 8
	FXRotariesBTemplate 8
	FXRotariesCTemplate 8
	FXRotariesDTemplate 8
	FXRotariesAShiftTemplate 8
	FXRotariesBShiftTemplate 8
	FXRotariesCShiftTemplate 8
	FXRotariesDShiftTemplate 8
ZoneEnd

It does beg the question: couldn't SelectedTrackTCP just use the template and map similarly? That's one for Mr. Waddington.

[Funkybot]

I should add, the auto-mapping is killer BTW.

Load up any FX you don't have a map for into the FX Menu, then GoFXSlot, and boom, map created! It usually just works. Minus some plugins with wonky stepped params and whatenot.

[MixMonkey]

Originally Posted by Funkybot

This is all real new, so take all of this with a grain of salt, and Geoff can chime in and correct anything that's wrong...

Cool, thanks for getting me on the same page!

I think SelectedTrackTCPFX are just really meant for "Quick Controls" and may indeed be limited to just 8.

Makes sense, I'll trim it down to 8.

SelectedTrackTCPFXTemplate uses a different syntax and can map multiple rows. It's also used for the Auto Mapping functionality.

For the C4, you'd set it up as such if you wanted to use rows A-D and then also have Shift for more options....

Zone "SelectedTrackTCPFXTemplate"

	FXRotariesATemplate 8
	FXRotariesBTemplate 8
	FXRotariesCTemplate 8
	FXRotariesDTemplate 8
	FXRotariesAShiftTemplate 8
	FXRotariesBShiftTemplate 8
	FXRotariesCShiftTemplate 8
	FXRotariesDShiftTemplate 8
ZoneEnd

Thanks, I'll give it a try

[Geoff Waddington]

Originally Posted by MixMonkey

Makes sense, I'll trim it down to 8.

SelectedTrackTCPFX is not limited to 8, it is based on your SelectedTrackTCPFX.zon defintion.

Funkybot is right, RotaryFXMapTemplate is a holdover, will remove it.

//  View Buttons
 
    GlobalView                  Global
    MidiTracks                  GoSelectedTrackTCPFX
    Inputs                      GoSelectedTrackTCPFXTemplate
    AudioTracks                 NoAction
    AudioInstrument             NoAction
    Aux                         NoAction
    Busses                      NoAction
    Outputs                     AddBlankTCPFXParam
    User                        BuildSelectedTrackTCPFXZone

[Funkybot]

Thanks for clarifying Geoff. Would it make sense to rename SelectedTrackTCPFXTemplate to something more generic like FXMappingTemplate since it's used to create FX maps via the TCP but also auto-fx maps? Might also help differentiate it from SelectedTrackTCPFX zones.

[MixMonkey]

Originally Posted by Geoff Waddington

SelectedTrackTCPFX is not limited to 8, it is based on your SelectedTrackTCPFX.zon defintion.

Yup, working now, my silly mistake

[Geoff Waddington]

Originally Posted by Funkybot

Thanks for clarifying Geoff. Would it make sense to rename SelectedTrackTCPFXTemplate to something more generic like FXMappingTemplate since it's used to create FX maps via the TCP but also auto-fx maps? Might also help differentiate it from SelectedTrackTCPFX zones.

I hear ya', the thing is, in order to map you use GoSelectedTrackTCPFXTemplate in order to reinforce that it requires SelectedTrack, uses the TCPFX mechanism, and the TCPFXTemplate.

Tricky bit of nuance, open to suggestions that convey as much info as possible.

[MixMonkey]

I think I'm making a mistake here

I have SelectedTrackTCPFXTemplate as an AssociatedZone in the Home Zone, but it seems to auto generate an FX.zon (in the AutoGeneratedFXZones folder) when I insert an FX (for which I don't already have an FX.zon) without any intervention from me other than having the track selected before insert the FX.

Could you run me through the process one time?

I was expecting to maybe go to the SelectedTrackTCPFXTemplate Zone, maybe change some aliases and then hit BuildSelectedTrackTCPFXZone.

[Geoff Waddington]

Originally Posted by MixMonkey

I think I'm making a mistake here

I have SelectedTrackTCPFXTemplate as an AssociatedZone in the Home Zone, but it seems to auto generate an FX.zon (in the AutoGeneratedFXZones folder) when I insert an FX (for which I don't already have an FX.zon) without any intervention from me other than having the track selected before insert the FX.

Could you run me through the process one time?

I was expecting to maybe go to the SelectedTrackTCPFXTemplate Zone, maybe change some aliases and then hit BuildSelectedTrackTCPFXZone.

The auto generate works in the FXMenu context, so if that is active, you will get an auto generated Zone before you get a chance to start defining the Zone as you expect.

Haven't really thought through how to design efficient, effective workflows with all this yet, just providing the building blocks at this point

[MixMonkey]

Originally Posted by Geoff Waddington

The auto generate works in the FXMenu context, so if that is active, you will get an auto generated Zone before you get a chance to start defining the Zone as you expect.

Ah! That makes perfect sense on my setups. On both the new version of the MM_iPad_Mixer and the Mackie setup with the C4s in the studio, the SelectedTrackFXMenu is continuously active.

Haven't really thought through how to design efficient, effective workflows with all this yet, just providing the building blocks at this point

No probs, I'll de-activate the SelectedTrackFXMenu and try out the other features. Very impressive so far!

[Funkybot]

If there's a priority, as has been indicated, it should probably be: 1) Classic FX Zones, 2) SelectedTrackTCPFX zones, then down at the bottom 3) Auto-generated.

This way a user that keeps their FX Menu always on and ends up with an auto-generated zone as a result could still enter GoSelectedTrackTCPFXTemplate and build a custom zone. Which, once complete, would cause CSI to ignore the auto-generated zone.

[MixMonkey]

Originally Posted by Funkybot

If there's a priority, as has been indicated, it should probably be: 1) Classic FX Zones, 2) SelectedTrackTCPFX zones, then down at the bottom 3) Auto-generated.

This way a user that keeps their FX Menu always on and ends up with an auto-generated zone as a result could still enter GoSelectedTrackTCPFXTemplate and build a custom zone. Which, once complete, would cause CSI to ignore the auto-generated zone.

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)