Control Surface Integration (CSI) Technical Feature Discussion

[Geoff Waddington]

New build is up.

CSI Exp.zip


FXParamStepValuesCache.txt now automatically generated, just turn a knob.



FXParamAliasesCache.txt now generated by doing this:

Define a SelectedTrackTCPFX Zone, and a means to navigate to it.

The key is mapping a display to TCPFXParamNameDisplay.

Insert the FX for which you wish to name an alias on the SelectedTrack.

Hit the button mapped to GoSelectedTrackTCPFX.

Define the alias using the Reaper method.

Close Reaper - no need to save.

The alias gets written to FXParamAliasesCache.txt and is available for all instances of that FX from now on, until you change it or remove it from the Cache.

[MixMonkey]

Originally Posted by Geoff Waddington

New build is up.

CSI Exp.zip


FXParamStepValuesCache.txt now automatically generated, just turn a knob.



FXParamAliasesCache.txt now generated by doing this:

Define a SelectedTrackTCPFX Zone, and a means to navigate to it.

The key is mapping a display to TCPFXParamNameDisplay.

Insert the FX for which you wish to name an alias on the SelectedTrack.

Hit the button mapped to GoSelectedTrackTCPFX.

Define the alias using the Reaper method.

Close Reaper - no need to save.

The alias gets written to FXParamAliasesCache.txt and is available for all instances of that FX from now on, until you change it or remove it from the Cache.

Got it halfway working here The alias is correctly saved to the cache, but not picked up by new instances of the same plugin.

Excellent stuff though! I'm just putting together a page for my new iPad mixer that uses it.

[Geoff Waddington]

Originally Posted by MixMonkey

Got it halfway working here The alias is correctly saved to the cache, but not picked up by new instances of the same plugin.

Excellent stuff though! I'm just putting together a page for my new iPad mixer that uses it.

Hmmm...

Working fine here.

Are you sure you have the display mapped to FXParamNameDisplay on said plugins ?

I had mine initially mapped to FixedText, had to change it.

[Funkybot]

Originally Posted by Geoff Waddington

Hmmm...

Working fine here.

Are you sure you have the display mapped to FXParamNameDisplay on said plugins ?

I had mine initially mapped to FixedText, had to change it.

I think what MixMonkey is experiencing is this:

1. Create an Alias for a TCPFXParam
2. Don't save that as a track template or anything yet
3. Exit Reaper and restart
4. Reload that FX
5. Add that param as a TCPFXParam again

Result: Reaper does not read the alias file (I don't expect it to) so the TCPFXParamName reads as the default name from Reaper. Not the aliased name from the file. The two are in sync. If it read the name from the file here without Reaper also reading the same file name, then the two names would be out of sync. Not sure how you get around that.

However, what does work is this:

1. Create an Alias for a TCPFXParam
2. Exit Reaper and restart
3. Load a new instance of that FX
4. Map the FX the traditional way (e.g. FX Menu or Focused)

Result: the param alias appears as expected.

[Funkybot]

FXParamStepValuesCache.txt on the other hand is not doing what I expect at all. Some questions:

1. Do I have to create a map first?
2. Or do I have to add it to TCPFX then move the knob for this to be right?
3. It's supposed to look like a ZoneStep file right with all step sizes? Right now, I just see step 1: 0.0000000

Not clear on this process at all at the moment.

This definitely isn't right for example:

"VST: Sonsig Rev-A (Relab Development)" 0 0.000000
"VST: Sonsig Rev-A (Relab Development)" 5 0.000000
"VST: Sonsig Rev-A (Relab Development)" 15 0.000000
"VST: ValhallaVintageVerb (Valhalla DSP, LLC)" 0 0.000000
"VST: ValhallaVintageVerb (Valhalla DSP, LLC)" 2 0.000000

The Relab plugin has a lot of stepped parameters with a lot of steps and I moved them all.

When I try to do that with a plugin I don't have a map for already, I get nada.

[Geoff Waddington]

Originally Posted by Funkybot

I think what MixMonkey is experiencing is this:

1. Create an Alias for a TCPFXParam
2. Don't save that as a track template or anything yet
3. Exit Reaper and restart
4. Reload that FX
5. Add that param as a TCPFXParam again

Result: Reaper does not read the alias file (I don't expect it to) so the TCPFXParamName reads as the default name from Reaper. Not the aliased name from the file. The two are in sync. If it read the name from the file here without Reaper also reading the same file name, then the two names would be out of sync. Not sure how you get around that.

However, what does work is this:

1. Create an Alias for a TCPFXParam
2. Exit Reaper and restart
3. Load a new instance of that FX
4. Map the FX the traditional way (e.g. FX Menu or Focused)

Result: the param alias appears as expected.

Ah yes, now I see.

Best to think of it this way.

Use TCPFXParam as the editor for aliases.

As you say, then you can use the aliases for "traditional" Zones.

[Geoff Waddington]

Originally Posted by Funkybot

FXParamStepValuesCache.txt on the other hand is not doing what I expect at all. Some questions:

1. Do I have to create a map first?
2. Or do I have to add it to TCPFX then move the knob for this to be right?
3. It's supposed to look like a ZoneStep file right with all step sizes? Right now, I just see step 1: 0.0000000

Not clear on this process at all at the moment.

This definitely isn't right for example:

"VST: Sonsig Rev-A (Relab Development)" 0 0.000000
"VST: Sonsig Rev-A (Relab Development)" 5 0.000000
"VST: Sonsig Rev-A (Relab Development)" 15 0.000000
"VST: ValhallaVintageVerb (Valhalla DSP, LLC)" 0 0.000000
"VST: ValhallaVintageVerb (Valhalla DSP, LLC)" 2 0.000000

The Relab plugin has a lot of stepped parameters with a lot of steps and I moved them all.

When I try to do that with a plugin I don't have a map for already, I get nada.

I shouldn't have built these at the same time

FXParamStepValuesCache.txt has nothing to do with TCPFX

Here's what I used to test:

Zone "VST: UAD Fairchild 660 (Universal Audio, Inc.)" "Fair660"
	DisplayUpper1		FXParamNameDisplay 9
 	DisplayLower1		FXParamValueDisplay 9
	Rotary1 		FXParam 9 	

	DisplayUpper2		FXParamNameDisplay 1
 	DisplayLower2		FXParamValueDisplay 1
	Rotary2 		FXParam 1 	

	DisplayUpper3		FXParamNameDisplay 2
 	DisplayLower3		FXParamValueDisplay 2
	Rotary3 		FXParam 2 	

	DisplayUpper4		FXParamNameDisplay 3
 	DisplayLower4		FXParamValueDisplay 3
	Rotary4 		FXParam 3 	

	DisplayUpper5		FXParamNameDisplay 6
 	DisplayLower5		FXParamValueDisplay 6
	Rotary5 		FXParam 6 	

	DisplayUpper6		FXParamNameDisplay 7
 	DisplayLower6		FXParamValueDisplay 7
	Rotary6 		FXParam 7 	

	DisplayUpper7		FXParamNameDisplay 0
 	DisplayLower7		FXParamValueDisplay 0
	Rotary7 		FXParam 0 	

	DisplayUpper8		FXParamNameDisplay 8
 	DisplayLower8		FXParamValueDisplay 8
	Rotary8 		FXParam 8 	
ZoneEnd

I just activated it using FXMenu, moved some knobs a tiny bit, and voila:

"VST: UAD Fairchild 660 (Universal Audio, Inc.)" 0 0.000000 0.500000 1.000000
"VST: UAD Fairchild 660 (Universal Audio, Inc.)" 1 0.000000 0.050000 0.100000 0.150000 0.200000 0.250000 0.300000 0.350000 0.400000 0.450000 0.500000 0.550000 0.600000 0.650000 0.700000 0.750000 0.800000 0.850000 0.900000 0.950000 1.000000
"VST: UAD Fairchild 660 (Universal Audio, Inc.)" 2 0.000000
"VST: UAD Fairchild 660 (Universal Audio, Inc.)" 3 0.000000 0.200000 0.400000 0.600000 0.800000 1.000000
"VST: UAD Fairchild 660 (Universal Audio, Inc.)" 6 0.000000
"VST: UAD Fairchild 660 (Universal Audio, Inc.)" 7 0.000000
"VST: UAD Fairchild 660 (Universal Audio, Inc.)" 8 0.000000
"VST: UAD Fairchild 660 (Universal Audio, Inc.)" 9 0.000000 0.166667 0.333333 0.500000 0.666667 0.833333 1.000000

Worth pointing put that a single step value of 0.000000 indicates a continuous (non stepped) parameter.

I've set it so that a delta of 0.02 or less means continuous -- that's 50 steps.

[Funkybot]

Originally Posted by Geoff Waddington

I shouldn't have built these at the same time

FXParamStepValuesCache.txt has nothing to do with TCPFX

...

I just activated it using FXMenu, moved some knobs a tiny bit, and voila:

"VST: UAD Fairchild 660 (Universal Audio, Inc.)" 0 0.000000 0.500000 1.000000
"VST: UAD Fairchild 660 (Universal Audio, Inc.)" 1 0.000000 0.050000 0.100000 0.150000 0.200000 0.250000 0.300000 0.350000 0.400000 0.450000 0.500000 0.550000 0.600000 0.650000 0.700000 0.750000 0.800000 0.850000 0.900000 0.950000 1.000000
"VST: UAD Fairchild 660 (Universal Audio, Inc.)" 2 0.000000
"VST: UAD Fairchild 660 (Universal Audio, Inc.)" 3 0.000000 0.200000 0.400000 0.600000 0.800000 1.000000
"VST: UAD Fairchild 660 (Universal Audio, Inc.)" 6 0.000000
"VST: UAD Fairchild 660 (Universal Audio, Inc.)" 7 0.000000
"VST: UAD Fairchild 660 (Universal Audio, Inc.)" 8 0.000000
"VST: UAD Fairchild 660 (Universal Audio, Inc.)" 9 0.000000 0.166667 0.333333 0.500000 0.666667 0.833333 1.000000

Worth pointing put that a single step value of 0.000000 indicates a continuous (non stepped) parameter.

I've set it so that a delta of 0.02 means continuous -- that's 50 steps.

Ok, that worked! I didn't even need to do anything else to map all the steps, it was transparent.

Does it not do anything by design if you already have the steps in your .zon file?

Loading this up did not write the values...

Zone "VST: Sonsig Rev-A (Relab Development)" "Sonsig Rev-A"

DisplayUpperA1 FXParamNameDisplay 0 "Time"
DisplayLowerA1 FXParamValueDisplay 0 
RotaryA1 FXParam 0 [ (0.001,0.002,0.003,0.004,0.005,0.006,0.0075,0.01,0.02,0.035,0.05) ]
DisplayRotaryPushA1 FXParamNameDisplay 1 "Freeze"
RotaryPushA1 FXParam 1 [ 0.0 1.0 ] { 90 255 0 255 50 0 }
DisplayUpperShiftA1 NoAction 
DisplayLowerShiftA1 NoAction 
ShiftRotaryA1 NoAction 
/  
DisplayUpperA2 FXParamNameDisplay 2 "Size"
DisplayLowerA2 FXParamValueDisplay 2 
RotaryA2 FXParam 2 [ 0.0 0.111 0.222 0.333 0.444 0.556 0.667 0.778 0.889 1.0 ]
DisplayRotaryPushA2 NoAction 
RotaryPushA2 NoAction 
DisplayUpperShiftA2 NoAction 
DisplayLowerShiftA2 NoAction 
ShiftRotaryA2 NoAction 
/  
DisplayUpperA3 FXParamNameDisplay 3 "Character"
DisplayLowerA3 FXParamValueDisplay 3 
RotaryA3 FXParam 3 [ (30) 0.0 0.5 1.0 ]
DisplayRotaryPushA3 NoAction 
RotaryPushA3 NoAction 
DisplayUpperShiftA3 NoAction 
DisplayLowerShiftA3 NoAction 
ShiftRotaryA3 NoAction 
/  
DisplayUpperA4 FXParamNameDisplay 4 "Ensemble"
DisplayLowerA4 FXParamValueDisplay 4 
RotaryA4 FXParam 4 [ (15) 0.0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1.0 ]
DisplayRotaryPushA4 NoAction 
RotaryPushA4 NoAction 
DisplayUpperShiftA4 NoAction 
DisplayLowerShiftA4 NoAction 
ShiftRotaryA4 NoAction 
/  
DisplayUpperA5 FXParamNameDisplay 5 "Pre Delay"
DisplayLowerA5 FXParamValueDisplay 5 
RotaryA5 FXParam 5 [ (0.001,0.002,0.003,0.004,0.005,0.006,0.0075,0.01,0.02,0.035,0.05) ]
DisplayRotaryPushA5 NoAction
RotaryPushA5 NoAction
DisplayUpperShiftA5 FXParamNameDisplay 6 "PreDelay Sync"
DisplayLowerShiftA5 FXparamValueDisplay 
ShiftRotaryA5 FXParam 6 [ (15) 0.0 0.05 0.1 0.15 0.2 0.25 0.3 0.35 0.4 0.45 0.5 0.55 0.6 0.65 0.7 0.75 0.8 0.85 0.9 0.95 1.0 ]

...I know they're already in the zone, but might be a good idea to write anyway so that can be leveraged for other surfaces in the future.

[Geoff Waddington]

Originally Posted by Funkybot

Ok, that worked! I didn't even need to do anything else to map all the steps, it was transparent.

Yup, effortless

Originally Posted by Funkybot

Does it not do anything by design if you already have the steps in your .zon file?

Correct, it only works if you haven't overridden the auto generate by manually defining steps.

[Funkybot]

And just to document for anyone playing at home, the step size bit works like this:

1. Create an FX.zon for your plugin - you don't need to do anything special for toggles or stepped params in the zone creation process

2. Activate the FX.zon map like you normally would (Focused FX, SelectedTrackFX, FX Menu)

3. Move a stepped param

Result: the stepped param values get written.

Geoff, one last question: does it write the stepped param values for the entire plugin or just each param that gets moved on a moved-param-by-moved-param basis?

[Geoff Waddington]

Originally Posted by Funkybot

And just to document for anyone playing at home, the step size bit works like this:

1. Create an FX.zon for your plugin - you don't need to do anything special for toggles or stepped params in the zone creation process

2. Activate the FX.zon map like you normally would (Focused FX, SelectedTrackFX, FX Menu)

3. Move a stepped param

Result: the stepped param values get written.

Geoff, one last question: does it write the stepped param values for the entire plugin or just each param that gets moved on a moved-param-by-moved-param basis?

It only writes for ones that get moved.

I thought of writing the entire plugin, but then recalled those monstrous ones you have, and decided to do it on an as needed basis.

Don't forget, as soon as you turn a knob, it uses the previously created map if present, and only maps if necessary.

That seemed to be the most efficient approach.

[Funkybot]

Originally Posted by Geoff Waddington

It only writes for ones that get moved.

I thought of writing the entire plugin, but then recalled those monstrous ones you have, and decided to do it on an as needed basis.

Don't forget, as soon as you turn a knob, it uses the previously created map if present, and only maps if necessary.

That seemed to be the mose efficient approach.

Makes sense to me. Especially since it just "picks up" the stepped params with no effort. So doing it on an as-needed basis only is definitely the way to go.

Those monstrous Arturia plugins were going to be on my testing list for tomorrow. Just wanted to kick the tires on this before heading out tonight.

I'm not sure if you've seen MixMonkey's recent FX Configurator, but you basically just made the entire right half of it obsolete today. I'm sure he won't mind at all.

Happy new year to you all!

[Geoff Waddington]

Originally Posted by Funkybot

Makes sense to me. Especially since it just "picks up" the stepped params with no effort. So doing it on an as-needed basis only is definitely the way to go.

Those monstrous Arturia plugins were going to be on my testing list for tomorrow. Just wanted to kick the tires on this before heading out tonight.

I'm not sure if you've seen MixMonkey's recent FX Configurator, but you basically just made the entire right half of it obsolete today. I'm sure he won't mind at all.

Happy new year to you all!

Yeah, I can't see using anything but auto now, except in the extremely rare case where you want to specifically leave out a certain step or steps.

Oh yeah, and Happy New Year everyone !!

[MixMonkey]

Originally Posted by Funkybot

I think what MixMonkey is experiencing is this:

1. Create an Alias for a TCPFXParam
2. Don't save that as a track template or anything yet
3. Exit Reaper and restart
4. Reload that FX
5. Add that param as a TCPFXParam again

Result: Reaper does not read the alias file (I don't expect it to) so the TCPFXParamName reads as the default name from Reaper. Not the aliased name from the file. The two are in sync. If it read the name from the file here without Reaper also reading the same file name, then the two names would be out of sync. Not sure how you get around that.

However, what does work is this:

1. Create an Alias for a TCPFXParam
2. Exit Reaper and restart
3. Load a new instance of that FX
4. Map the FX the traditional way (e.g. FX Menu or Focused)

Result: the param alias appears as expected.

Ah, yes This is exactly it. I was expecting the aliases that were generated to be used in TCPFX plugins. I didn't get it was a way to generate aliases for the FX.zon method. No probs

TCPFX working fine then! I'll finish my iPadMixer page.

[MixMonkey]

Originally Posted by Funkybot

I'm not sure if you've seen MixMonkey's recent FX Configurator, but you basically just made the entire right half of it obsolete today. I'm sure he won't mind at all.

Don't mind at all With a bit more work I'm sure the entire left half can be made obsolete too

Happy New Year All!!

[Geoff Waddington]

Originally Posted by Funkybot

However, what does work is this:

1. Create an Alias for a TCPFXParam
2. Exit Reaper and restart
3. Load a new instance of that FX
4. Map the FX the traditional way (e.g. FX Menu or Focused)

Result: the param alias appears as expected.

Actually, you can leave out step 2, as soon as you create the alias it is available.

[Geoff Waddington]

New build is up.

CSI Support Files.zip

CSI Exp.zip

Implemented first draft of FXRotaries and FXFaders for super easy Zone definitions.

This only works for surfaces that have Rotary1, Rotary2, DisplayUpper1, DisplayUpper2, DisplayLower1, DisplayLower2, etc.

So, for those who have that type of surface it's this easy:

Zone "VST: UAD Fairchild 660 (Universal Audio, Inc.)" "Fair660"
	FXRotaries 9 1 2 3 6 7 0 8
ZoneEnd

Now, to start the year off right, you can see how the aforementioned FXRotaries can be leveraged to provide... wait for it... yup, primitive start but...

Implemented primitive auto map for FXMenu.

When you GoTrackFXMenu and there is a plugin with no map, it now gets a primitive auto generated one.

It is placed in you Zone folder in a new subfolder named AutoGenerated.

If the AutoGenerated folder does not exist, it will be created.



Happy New Year !!



It doesn't take much imagination to see what's coming next

There will be a new Action named AutoGenFromSelectedTrackTCPFX, used like this

You will just insert an FX that you wish to map on the SelectedTrack.

Then you will do the magic of choosing the params you want included in your new Zone.

Next, name aliases as needed for parameters, perhaps even including an alias for the Zone itself.

Finally, press the button you have mapped to AutoGenFromSelectedTrackTCPFX.

Voila !!

I would say that is sufficiently close to a midi learn type approach, for now at least.

Meanwhile, I'm taking the rest of the day off for some New Year's day NFL enjoyment.

[722]

Hallo and thank you very much for this wonderful project!

Just finished upgrading my CSI configuration of SSL UF8 to the CSI version 2.0 syntax.

On my UF8, there are eight buttons labeled [1], [2], [3] etc. which I used to jump to a specific send slot with a single button press. My original Buttons.zon (before 2.0) included these lines and it worked:

    Send1	SendSlotBank -7
    Send1	MapTrackSendsSlotToWidgets
    Send2	SendSlotBank -7
    Send2	SendSlotBank 1
    Send2	MapTrackSendsSlotToWidgets
    Send3	SendSlotBank -7
    Send3	SendSlotBank 2
    Send3	MapTrackSendsSlotToWidgets
    Send4	SendSlotBank -7
    Send4	SendSlotBank 3
    Send4	MapTrackSendsSlotToWidgets
    Send5	SendSlotBank -7
    Send5	SendSlotBank 4
    Send5	MapTrackSendsSlotToWidgets
    Send6	SendSlotBank -7
    Send6	SendSlotBank 5
    Send6	MapTrackSendsSlotToWidgets
    Send7	SendSlotBank -7
    Send7	SendSlotBank 6
    Send7	MapTrackSendsSlotToWidgets
    Send8	SendSlotBank -7
    Send8	SendSlotBank 7
    Send8	MapTrackSendsSlotToWidgets

No, as I transition to CSI 2.0 I adjusted the commands to the following:

    Send1	TrackSendBank -7
    Send1	GoTrackSend
    Send2	TrackSendBank -7
    Send2	TrackSendBank 1
    Send2	GoTrackSend
    Send3	TrackSendBank -7
    Send3	TrackSendBank 2
    Send3	GoTrackSend
    Send4	TrackSendBank -7
    Send4	TrackSendBank 3
    Send4	GoTrackSend
    Send5	TrackSendBank -7
    Send5	TrackSendBank 4
    Send5	GoTrackSend
    Send6	TrackSendBank -7
    Send6	TrackSendBank 5
    Send6	GoTrackSend
    Send7	TrackSendBank -7
    Send7	TrackSendBank 6
    Send7	GoTrackSend
    Send8	TrackSendBank -7
    Send8	TrackSendBank 7
    Send8	GoTrackSend

... but it doesn't work.🙈 The TrackSendBank commands don't seem to work inside the Buttons.zon before calling the GoTrackSend. However, they seem to do the job inside the TrackSend.zon, where for example:

    Send2	TrackSendBank -7
    Send2	TrackSendBank 1

makes pressing the button [2] (Send2) bank directly to the second bank of sends. But only when already inside the TrackSend.zon.

The result for now: Pressing any number jumps to sends bank 1. Once inside the sends view, I can use the number buttons to jump to a specific bank directly, but not earlier from the Buttons.zon.

Maybe someone would have an idea what I am missing?

Many thanks in advance and best wishes,

Jakub

[Funkybot]

Enjoy the football! I've got the Giants game on in the background as I kick the tires on this.

It's working here if I modify my MFTwister.mst to follow the MCU-style naming convention (e.g. replace RotaryA1-A8 with just Rotary1-8, DisplayUpperA1 with DisplayUpper1). Was just messing with the .mst for testing purposes. As expected, it created the fx.zon's just mapping the first 8 params in order. Worked well.

I use a similar naming convention to the C4 in my .mst for the Twister, so if you build a C4/SCE24 variation that allowed for A1-A8, B1-B8, C1-C8, that would probably cover the Twister.

One potential bug: after activating the new AutoGenerated fx maps, they don't appear to update and write to the FXParamStepValuesCache.txt file.

Also, it might be verbose, but I think "AutoGeneratedFXZones" or "AutoFXZones" might be a better name for the folder. Just something there to specifically call out to newbies "hey, these are fx zones".

Very cool stuff!

[Geoff Waddington]

New build is up.

CSI Exp.zip

Added FXRotariesA, FXRotariesB, FXRotariesC, FXRotariesD.

Renamed AutoGenerated to AutoGeneratedFXZones.

Funkybot, AutoGenerated FX maps update the FXParamStepValuesCache.txt file just fine here.

[MixMonkey]

Originally Posted by Geoff Waddington

New build is up.

CSI Exp.zip

Added FXRotariesA, FXRotariesB, FXRotariesC, FXRotariesD.

I get an FX.zon generated, but no parameter assignment.

Zone "VST: TDR VOS SlickEQ (Tokyo Dawn Labs)" "VOS SlickEQ (Tokyo Dawn Labs)"
	FXRotaries
ZoneEnd

[Funkybot]

Originally Posted by Geoff Waddington

New build is up.

CSI Exp.zip

Added FXRotariesA, FXRotariesB, FXRotariesC, FXRotariesD.

Renamed AutoGenerated to AutoGeneratedFXZones.

Funkybot, AutoGenerated FX maps update the FXParamStepValuesCache.txt file just fine here.

Hi Geoff, on first test, it's not working yet. I suspect it's something in the .mst/.ost files. The files get generated but with no values.

How is this working behind the scenes? I suspect something in my .mst/.ost is confusing it. Might help me troubleshoot.

Here is an excerpt of my modified .mst (I removed a bunch of other widgets in case they were interfering).

StepSize
    RotaryWidgetClass 0.001
StepSizeEnd

AccelerationValues
    RotaryWidgetClass Dec 3f     3e    3d    3c    3b    3a    39     38    36    33    2f      
    RotaryWidgetClass Inc 41     42    43    44    45    46    47     48    4a    4d    51
    RotaryWidgetClass Val 0.001  0.002 0.003 0.004 0.005 0.006 0.0075 0.01  0.02  0.03  0.04
AccelerationValuesEnd

Widget RotaryPushA1
    Press b1 00 7f b1 00 00
    FB_MFT_RGB b1 00 7f
WidgetEnd

Widget RotaryA1 RotaryWidgetClass
    Encoder b0 00 7f
    FB_Fader7Bit b0 00 00
WidgetEnd

...

Widget RotaryB1 RotaryWidgetClass
    Encoder b0 08 7f
    FB_Fader7Bit b0 08 00
WidgetEnd

Widget RotaryPushB1
    Press b1 08 7f b1 08 00
    FB_MFT_RGB b1 08 7f
WidgetEnd

And here's the .ost with the displays...

Widget DisplayUpperA1
FB_Processor /DisplayUpperA1
WidgetEnd

Widget DisplayLowerA1
FB_Processor /DisplayLowerA1
WidgetEnd

Widget RotaryA1
Control /RotaryA1
FB_Processor /RotaryA1
WidgetEnd

Widget RotaryPushA1
Control /RotaryPushA1
FB_Processor /RotaryPushA1
WidgetEnd

...

Widget DisplayUpperB1
FB_Processor /DisplayUpperB1
WidgetEnd

Widget DisplayLowerB1
FB_Processor /DisplayLowerB1
WidgetEnd

Widget RotaryB1
Control /RotaryB1
FB_Processor /RotaryB1
WidgetEnd

Widget RotaryPushB1
Control /RotaryPushB1
FB_Processor /RotaryPushB1
WidgetEnd

EDIT: just saw MixMonkey's post. Not just me at least.

[Funkybot]

Oh, and this EXP build is missing the 64 in the Windows .dll filename again. I manually renamed it before testing.

[MixMonkey]

Originally Posted by Funkybot

just saw MixMonkey's post. Not just me at least.

Do we need to change anything in the .mst? I tried Widget to EWidget but it made no difference.

[Funkybot]

Originally Posted by MixMonkey

Do we need to change anything in the .mst? I tried Widget to EWidget but it made no difference.

I don't think any .mst changes are required.

My standard MFTWister .mst/.ost files have widgets called things like "ShiftRotaryA1", "RotaryPushDisplayA1", "DisplayUpperShiftA1", "DisplayLowerShiftA1". So I created a modified version without those in case they were the problem. But that made no change.

When I used the standard Rotary1, Rotary2, convention using the same syntax, it worked earlier without additional changes.

[Geoff Waddington]

Originally Posted by MixMonkey

I get an FX.zon generated, but no parameter assignment.

Zone "VST: TDR VOS SlickEQ (Tokyo Dawn Labs)" "VOS SlickEQ (Tokyo Dawn Labs)"
	FXRotaries
ZoneEnd

I'm not communicating well at all today

Should have said "Added FXRotariesA, FXRotariesB, FXRotariesC, FXRotariesD, but not for auto generation, just the shorthand Zone definition method"

You can tell by the presence of "FXRotaries" in the Zone file, not "FXRotariesA".

CSI can do a little sleuthing in the auto generation algorithm.

How about this ?

If CSI finds Rotary1, etc., it uses those.

If that fails it then tries the A, B, C, variants.

[Geoff Waddington]

Originally Posted by Funkybot

Oh, and this EXP build is missing the 64 in the Windows .dll filename again. I manually renamed it before testing.

Thanks, obviously still getting used to the new build environment

[Funkybot]

Originally Posted by Geoff Waddington

CSI can do a little sleuthing in the auto generation algorithm.

How about this ?

If CSI finds Rotary1, etc., it uses those.

If that fails it then tries the A, B, C, variants.

That makes sense! Will it stop at RotaryD? I personally wouldn't want it to map all the banks on the Twister (which would go up to RotaryH8). But if it did, so be it! If it stops at RotaryD8, then that would be a-ok with me too. Preferred even.

[Geoff Waddington]

Originally Posted by Funkybot

That makes sense! Will it stop at RotaryD? I personally wouldn't want it to map all the banks on the Twister (which would go up to RotaryH8). But if it did, so be it! If it stops at RotaryD8, then that would be a-ok with me too. Preferred even.

I meant it would try Rotary1, then RotaryA1, then RotaryB1, then RotaryC1, then RotaryD1, until it finds a match.

What you propose makes sense, but for a first iteration it will stop when it finds a row that works.

We can refine things later, once it all works.

[Funkybot]

Originally Posted by Geoff Waddington

I meant it would try Rotary1, then RotaryA1, then RotaryB1, then RotaryC1, then RotaryD1, until it finds a match.

What you propose makes sense, but for a first iteration it will stop when it finds a row that works.

We can refine things later, once it all works.

Ah, ok. Understood. I don't think anyone would even have a B1 if there wasn't an A1, but as you say, mapping multiple rows can come later.

[Geoff Waddington]

New build is up.

CSI Exp.zip

Auto generate now supports A, B, C, D (I hope)

[Funkybot]

Originally Posted by Geoff Waddington

New build is up.

CSI Exp.zip

Auto generate now supports A, B, C, D (I hope)

This is a weird one: it's working to create the map, the map works on my iPad without issue, but it's not working on the MFTwister hardware. GoFXSlot from the Twister will activate the zone, it's just once in the zone, the param feedback doesn't light up, nor does turning the rotary do anything.

I double checked against other pre-existing FX maps in the same session, and the encoders work as expected. So the Twister is there and talking both ways. CSI Input Monitoring showed RotaryA1 moving as expected when turned. The widgets are just standard Encoder widgets with Feedback7Bit. But the MIDI control just wasn't communicating with this fx zone type.

Widget RotaryA1 RotaryWidgetClass
    Encoder b0 00 7f
    FB_Fader7Bit b0 00 00
WidgetEnd

[Funkybot]

Also, feature request for later on if I may: you're already stripping out the plugin prefix for the alias field. Please also strip out any text in parenthesis.

So this...
"VST3: UADx Brigade Chorus (Universal Audio (UADx))" "Brigade Chorus"

Instead of this...
"VST3: UADx Brigade Chorus (Universal Audio (UADx))" "Brigade Chorus (Universal Audio (UADx))"

[Geoff Waddington]

Originally Posted by Funkybot

This is a weird one: it's working to create the map, the map works on my iPad without issue, but it's not working on the MFTwister hardware. GoFXSlot from the Twister will activate the zone, it's just once in the zone, the param feedback doesn't light up, nor does turning the rotary do anything.

I double checked against other pre-existing FX maps in the same session, and the encoders work as expected. So the Twister is there and talking both ways. CSI Input Monitoring showed RotaryA1 moving as expected when turned. The widgets are just standard Encoder widgets with Feedback7Bit. But the MIDI control just wasn't communicating with this fx zone type.

Widget RotaryA1 RotaryWidgetClass
    Encoder b0 00 7f
    FB_Fader7Bit b0 00 00
WidgetEnd

Can you post both the Zones that are generated in the MFT folder/AutoGeneratedFXZones as well as the Zones that are working correctly ?

[Geoff Waddington]

Originally Posted by Funkybot

Also, feature request for later on if I may: you're already stripping out the plugin prefix for the alias field. Please also strip out any text in parenthesis.

So this...
"VST3: UADx Brigade Chorus (Universal Audio (UADx))" "Brigade Chorus"

Instead of this...
"VST3: UADx Brigade Chorus (Universal Audio (UADx))" "Brigade Chorus (Universal Audio (UADx))"

Great idea !!

Will do.

[Geoff Waddington]

New build is up

CSI Exp.zip

Improved auto generated FX Zone alias naming.

[Geoff Waddington]

Originally Posted by Funkybot

This is a weird one: it's working to create the map, the map works on my iPad without issue, but it's not working on the MFTwister hardware. GoFXSlot from the Twister will activate the zone, it's just once in the zone, the param feedback doesn't light up, nor does turning the rotary do anything.

I double checked against other pre-existing FX maps in the same session, and the encoders work as expected. So the Twister is there and talking both ways. CSI Input Monitoring showed RotaryA1 moving as expected when turned. The widgets are just standard Encoder widgets with Feedback7Bit. But the MIDI control just wasn't communicating with this fx zone type.

Widget RotaryA1 RotaryWidgetClass
    Encoder b0 00 7f
    FB_Fader7Bit b0 00 00
WidgetEnd

Just remembered, the MFT doesn't have Upper and Lower Displays does it ?

That means no Zones will be created, you should not be able to find any in the MFT Zone folder.

[Funkybot]

Originally Posted by Geoff Waddington

Just remembered, the MFT doesn't have Upper and Lower Displays does it ?

That means no Zones will be created, you should not be able to find any in the MFT Zone folder.

I use my MFTwister with an OSC tablet and they both share a zone folder. The displays are in the .ost and exist in the zone folder. The file generated and the zone activates and works on the iPad. This is supposed to be mirrored on the Twister but isn't. Kind of like it's Broadcasting the zone activation from Twister to iPad but the Twister is supposed to change with it and isn't.

Here's the auto-generated file:

Zone "VST3: UADx Brigade Chorus (Universal Audio (UADx))" "Brigade Chorus"
	FXRotariesA 0 1 2 3 4 5 6 7
ZoneEnd

Here's a pre-existing FX.zon where you can see the displays.

Zone "VST3: ValhallaVintageVerb (Valhalla DSP, LLC)" "VintageVerb"

/
MainDisplay1 FXNameDisplay
MainDisplay2 TrackNameDisplay
/
DisplayUpperA1 FXParamNameDisplay 1 "PreDelay"
DisplayLowerA1 FXParamValueDisplay 1 
RotaryA1 FXParam 1 [ (0.001,0.002,0.003,0.004,0.005,0.006,0.0075,0.01,0.02,0.035,0.05) ]
DisplayRotaryPushA1 NoAction 
RotaryPushA1 NoAction 
DisplayUpperShiftA1 NoAction 
DisplayLowerShiftA1 NoAction 
ShiftRotaryA1 NoAction

[Geoff Waddington]

Originally Posted by Funkybot

I use my MFTwister with an OSC tablet and they both share a zone folder. The displays are in the .ost and exist in the zone folder. The file generated and the zone activates and works on the iPad. This is supposed to be mirrored on the Twister but isn't. Kind of like it's Broadcasting the zone activation from Twister to iPad but the Twister is supposed to change with it and isn't.

Aha, now I see, the shared folder is the key.

The OSC tablet must also have Rotaries defined in the .ost.

Currently CSI checks to ensure all three conditions (Rotary, Upper, Lower) are met before generating a Zone as well as before loading a Zone defined with the new shorthand.

It looks like the OSC device is causing the Zone generation, and it will load just fine.

However, the lack of Upper and Lower displays on the MFT prevent the Zone from loading.

Maybe we should relax that constraint.

What do you think ?

Do you envision any downside to that approach ?

[Funkybot]

Originally Posted by Geoff Waddington

Aha, now I see, the shared folder is the key.

The OSC tablet must also have Rotaries defined in the .ost.

Currently CSI checks to ensure all three conditions (Rotary, Upper, Lower) are met before generating a Zone as well as before loading a Zone defined with the new shorthand.

It looks like the OSC device is causing the Zone generation, and it will load just fine.

However, the lack of Upper and Lower displays on the MFT prevent the Zone from loading.

Maybe we should relax that constraint.

What do you think ?

Do you envision any downside to that approach ?

I don't see any apparent downsides to that approach.