Control Surface Integration (CSI) Technical Feature Discussion

[Geoff Waddington]

Originally Posted by Funkybot

One more Eucon issue:

It's no longer working when on a second page. So if I create two CSI pages, "Home" and "Mix," where Home does not include Eucon, but Mix does, then Eucon faders, pans, track displays will not initialize when I go to that second "Mix page." The channel meters move in Eucon, which is interesting, but nothing else is working.

Here's my CSI.ini just so you can see what I'm doing...

Page "Home" FollowTCP NoSynchPages NoScrollLink NoTrackColoring { 0 0 0 }
MidiSurface "X-Touch One" 6 8 "X-Touch_One.mst" "X-Touch_One_Standard" 1 0 0 0 
MidiSurface "MIDI Fighter Twister" 19 21 "MIDIFighterTwisterEncoder.mst" "MFTwisterNoChannels" 0 0 0 0 
MidiSurface "CMC-QC" 9 11 "Stienberg_CMC-QC-2.mst" "CMC-QC-2" 0 0 0 0 

Page "Mix" FollowTCP NoSynchPages NoScrollLink NoTrackColoring { 0 0 0 }
MidiSurface "MIDI Fighter Twister" 19 21 "MIDIFighterTwisterEncoder.mst" "MFTwisterNoChannels" 0 8 0 0 
EuConSurface "EuCon" "EuCon" 8 8 8 2 
MidiSurface "CMC-QC" 9 11 "Stienberg_CMC-QC-2.mst" "CMC-QC-2" 0 0 0 0 
MidiSurface "X-Touch One Selected" 6 8 "X-Touch_One.mst" "X-Touch_One_SelectedTrack" 0 0 0 0

Thanks for the report.

[pwallin]

Hi! Another noobish question. I have mapped some actions on my X-Touch using CSI. Now I have run out of free buttons, so how I program "Shift", "Control" and "Alt" to map a new set of actions? Or is there an example for this already somewhere?

At the moment I am very happy for my workflow using CSI. Thanks all the help so far. I take a deep bow to you all.

-Pasi

[MixMonkey]

Originally Posted by pwallin

I take a deep bow to you all.

....and I curtsey in return

Syntax for Modifiers is simple:

Shift+SomeButton   Reaper "SomeReaperAction"

[pwallin]

Originally Posted by MixMonkey

....and I curtsey in return

Syntax for Modifiers is simple:

Shift+SomeButton   Reaper "SomeReaperAction"

I knew it's something that simple. Thanks again!

[Funkybot]

Originally Posted by pwallin

I knew it's something that simple. Thanks again!

If you run into any trouble, make sure you have release messages in your .mst for all modifier widgets.

[pwallin]

Originally Posted by Funkybot

If you run into any trouble, make sure you have release messages in your .mst for all modifier widgets.

Ok, I managed to do it without trouble. Thanks for the hint anyway.

-Pasi

[MixMonkey]

Originally Posted by pwallin

Ok, I managed to do it without trouble. Thanks for the hint anyway.

-Pasi

...and you know that if you press and release a Modifier quickly, it will latch, right?

At least Behringer had the good sense to put LEDs behind their Modifier buttons, which is more than Mackie did

[tdc]

Wowsers, I have a few days away on a project and this thread goes nuts. :-).

@Geoff: I am back for a bit and happy to do any specific tests you would like.

[cjewellstudios]

Stepped parameters aren't working for me in the new build. Anyone else?

as in:

Rotary13    FXParam 14 "Lo Freq"    	[ (10) 0.0 0.143 0.286 0.429 0.571 0.714 0.857 1.0 ]

For sure worked in the other build. Did I miss a syntax change?

[pwallin]

Originally Posted by MixMonkey

...and you know that if you press and release a Modifier quickly, it will latch, right?

At least Behringer had the good sense to put LEDs behind their Modifier buttons, which is more than Mackie did

Whaaaat? Nice to know.

[pwallin]

Originally Posted by Geoff Waddington

That's only the case if you use FXMenu, you can do it with MapSelectedTrackFXToWidgets, or MapFocusedFXToWidgets and not have to press every time

I still need to find how to actually do that, but meanwhile I just copied "GoFXSlot" command from "RotaryPush" to a "EQ" button on my X-Touch. And I see no problems. Maybe I just do not use these things as elegantly as I could, because I just have only ReaEQ's parameters mapped but my main problem is solved. Still interested to look how your advises actually affect my workflow in future.

Your CSI is awsome!

-Pasi

[Geoff Waddington]

Originally Posted by tdc

Wowsers, I have a few days away on a project and this thread goes nuts. :-).

@Geoff: I am back for a bit and happy to do any specific tests you would like.

Thanks but no need.

With help from Justin, it is now clear what is going on.

When you touch an MCU fader, along with the touch sense message, it also sends out current fader position.

Reaper expects this behaviour.

When you release touch, the envelope and track volume (or whatever envelope you are adjusting) return to previous position.

Meanwhile, CSI's polling loop notices the change and adjusts the EuCon fader accordingly.

What CSI does not currently do is send that new value the next time you touch the fader.

So Reaper is working off the last sent fader move, exactly the behaviour we all see.

I will have to modify EuCon to mimc MCU behaviour and all should be well

However, for other Midi surfaces that don't do what MCU does (Justin mentioned one) we may still have problems.

I guess we'll attempt to handle those on a case by case basis, based on user reports.

[Cragster]

Hey everybody just had a second to read over what's going on . I hear a lot about osc ( which I know absolutely nothing about). Am I correct in thinking that any Android or iPad would work for this? What are some thing you guys do with this in your setups. Just something I would like to try. I have an old android pad that does nothing but sit in a drawer. Saw Geoff using something like this in that cheesy video.
(Which I dont think is cheesy btw).and that touch control thing mixmonkey just posted a few ago. Idk you all know me by now...curious..wanna learn...try the new stuff(well new to me)and a PITA still noobie .so I just get whatever osc software on the pad and throw some files at it from csi ? I dont see anything in the wiki bout osc. Thanks

[MixMonkey]

Originally Posted by cjewellstudios

Stepped parameters aren't working for me in the new build. Anyone else?

as in:

Rotary13    FXParam 14 "Lo Freq"    	[ (10) 0.0 0.143 0.286 0.429 0.571 0.714 0.857 1.0 ]

For sure worked in the other build. Did I miss a syntax change?

I don't think so. At the moment, FX and Sends are essentially 'broken' until Geoff restores them.

I'm still on a version from April for work and only swap out to the new one for testing.

[MixMonkey]

Originally Posted by pwallin

I still need to find how to actually do that, but meanwhile I just copied "GoFXSlot" command from "RotaryPush" to a "EQ" button on my X-Touch.

If it works for you, great. There is no definitive way to use CSI. Everyone has different workflows and everyone has different ideas about what a 'normal' workflow is

For the avoidance of doubt, what follows relates to the older (May and earlier) version of CSI, not the most recent version.

There's nothing to stop you mapping the GoFXSlot commands to other buttons. Just be aware that when the command was in the FXMenu Zone, something like:

Zone "FXMenu|1-8"
    SelectedTrackNavigator
    DisplayUpper|                       FXNameDisplay |
    DisplayLower|                       NoAction
    Rotary|                             NoAction
    RotaryPush|                         GoFXSlot |
ZoneEnd

....the | represents the number of the surface channel. If you take the GoFXSlot command out of the FXMenu Zone, you'll have to provide that number yourself. Something like:

EQButton  GoFXSlot 1

I haven't tried this out so you'll need to experiment for yourself.

If I were you, I'd map another plugin and test things out with 2 FX slots occupied, mapping the second slot to another button. That should give you a clearer idea of whether your setup is solid.

[MixMonkey]

Originally Posted by Cragster

Hey everybody just had a second to read over what's going on . I hear a lot about osc ( which I know absolutely nothing about). Am I correct in thinking that any Android or iPad would work for this?

Well I guess it depends on the OS version, but yes, Touch OSC is available for both and is free.

What are some thing you guys do with this in your setups.

I built a complete mixer/FX controller to use with my laptop when away from the studio. It lets me test out mapping ideas and FX zones without needing the 'big' setup.

If you wanted to use it as an adjunct to your main setup, you could use for things like:
i) Remote transport control (when recording yourself)
ii) Array of labelled buttons assigned to Reaper actions
iii) Separate, dedicated, FX controller

...or all of the above

[Cragster]

Originally Posted by MixMonkey

Well I guess it depends on the OS version, but yes, Touch OSC is available for both and is free.


I built a complete mixer/FX controller to use with my laptop when away from the studio. It lets me test out mapping ideas and FX zones without needing the 'big' setup.

If you wanted to use it as an adjunct to your main setup, you could use for things like:
i) Remote transport control (when recording yourself)
ii) Array of labelled buttons assigned to Reaper actions
iii) Separate, dedicated, FX controller

...or all of the above

Thanks man. I really like that 1st one...recording myself. That could def work. I'll mess with it and see if I can figure it out. Thanks again

[MixMonkey]

Originally Posted by Cragster

Thanks man. I really like that 1st one...recording myself. That could def work. I'll mess with it and see if I can figure it out. Thanks again

Go for it

The way I started was to setup the Zone folder and .ost file structure with a single button (it turned the metronome on and off) just to get it all connected and working, then go from there.

[Geoff Waddington]

New builds are up.

Hopefully have now slain the automation dragon for fader moves.

EuCon users, please verify, make sure you get both dlls/dylibs.

If that works I will tackle the same issue with the rotaries.

[MixMonkey]

Originally Posted by Geoff Waddington

New builds are up.

Hopefully have now slain the automation dragon for fader moves.

EuCon users, please verify, make sure you get both dlls/dylibs.

If that works I will tackle the same issue with the rotaries.

Didn’t want to pile on before, but Touch is broken in OSC as well, but not in the same way. It suffers the ziggy - zaggy, dropping in and out of write when the fader is touched. This happens in the May build as well, but not in the one from April. Sorry to bring more work.

[Geoff Waddington]

Originally Posted by MixMonkey

Didn’t want to pile on before, but Touch is broken in OSC as well, but not in the same way. It suffers the ziggy - zaggy, dropping in and out of write when the fader is touched. This happens in the May build as well, but not in the one from April. Sorry to bring more work.

Hmmm...

It would seem I've lost my touch

[MixMonkey]

Originally Posted by Geoff Waddington

Hmmm...

It would seem I've lost my touch

Aaaaaaaaaaargh......

[Funkybot]

Originally Posted by Geoff Waddington

New builds are up.

Hopefully have now slain the automation dragon for fader moves.

EuCon users, please verify, make sure you get both dlls/dylibs.

If that works I will tackle the same issue with the rotaries.

I'm happy to report the fix is confirmed. Touch mode is working as expected with the faders returning to the initial value after letting go without the weird jumps to the previous touch value. Nice job Geoff (and Justin)!

That's using my Artist Mix.

[Geoff Waddington]

Originally Posted by Funkybot

I'm happy to report the fix is confirmed. Touch mode is working as expected with the faders returning to the initial value after letting go without the weird jumps to the previous touch value. Nice job Geoff (and Justin)!

That's using my Artist Mix.

Excellent news !!

Thanks for testing, now to see how to handle same with rotaries...

[RobinGShore]

I can also confirm that the Eucon touch automation bug is now gone when writing volume automation with the faders, however if I flip the faders and use them to write pan automation instead of volume, the bug still happens with the pan envelope.

Also sends are not working in Eucon on this latest build. When I hit the button to show sends on the controller nothing appears. This was working in the last version.

[pwallin]

Originally Posted by MixMonkey

If it works for you, great. There is no definitive way to use CSI. Everyone has different workflows and everyone has different ideas about what a 'normal' workflow is

For the avoidance of doubt, what follows relates to the older (May and earlier) version of CSI, not the most recent version.

There's nothing to stop you mapping the GoFXSlot commands to other buttons. Just be aware that when the command was in the FXMenu Zone, something like:

Zone "FXMenu|1-8"
    SelectedTrackNavigator
    DisplayUpper|                       FXNameDisplay |
    DisplayLower|                       NoAction
    Rotary|                             NoAction
    RotaryPush|                         GoFXSlot |
ZoneEnd

....the | represents the number of the surface channel. If you take the GoFXSlot command out of the FXMenu Zone, you'll have to provide that number yourself. Something like:

EQButton  GoFXSlot 1

I haven't tried this out so you'll need to experiment for yourself.

If I were you, I'd map another plugin and test things out with 2 FX slots occupied, mapping the second slot to another button. That should give you a clearer idea of whether your setup is solid.

Thanks for explanation. Actually second plugin is my planned next task and now I seem to understand logic behind CSI. But I usually think out of the box, so I may find some unusual way to get things work or find myself unnecessarily frustrated.

[Geoff Waddington]

Originally Posted by RobinGShore

I can also confirm that the Eucon touch automation bug is now gone when writing volume automation with the faders, however if I flip the faders and use them to write pan automation instead of volume, the bug still happens with the pan envelope.

Also sends are not working in Eucon on this latest build. When I hit the button to show sends on the controller nothing appears. This was working in the last version.

Good, glad FaderTouch is working.

Yes, sends are getting reworked right now, they will be back.

Hmmm... on my Mix flip doesn't even work, the fader continues to send Fader moves and FaderTouch and the rotaries continue to send Rotary moves and RotaryTouch.

What surface are you using ?

[Funkybot]

Originally Posted by Geoff Waddington

Good, glad FaderTouch is working.

Hmmm... on my Mix flip doesn't even work, the fader continues to send Fader moves and FaderTouch and the rotaries continue to send Rotary moves and RotaryTouch.

What surface are you using ?

Try this on the Artist Mix...

1. Start with Mix/Pan button lit up on the left
2. Hold the Shift button on the Artist Mix (bottom right)
3. Press the "Flip Chan" button on the left

Result: the fader should now control Pan (if using stereo pan) or PanLeft (if using dual pan). The rotary will control volume.

4. Hit the "Page Right" button to control PanWidth or PanRight.
5. Shift+Flip Chan to get you back into regular fader mode.

[RobinGShore]

Originally Posted by Geoff Waddington

Good, glad FaderTouch is working.

Yes, sends are getting reworked right now, they will be back.

Hmmm... on my Mix flip doesn't even work, the fader continues to send Fader moves and FaderTouch and the rotaries continue to send Rotary moves and RotaryTouch.

What surface are you using ?

I'm using an S1 (https://www.avid.com/products/avid-s1) and a Dock (https://www.avid.com/products/avid-dock), which are basically just updated versions of the artist mix and control. I also have an artist mix gathering dust in my closet that I could pull out for testing if needed, but from my understanding of how eucon works, the specific hardware shouldn't make a difference in sussing out bugs like this.

Anyways, flip works as expected for me. If I have the controller showing pans on the knobs and then I hit the flip button, the faders will now control pan and the knobs will control volume. I'm not certain how it works internally, but I think it could be that the type of messages that get sent out don't actually change, just the parameters that those messages control, so what you're seeing could still make sense. I could be totally be off base though and have no idea what I'm talking about.

[Funkybot]

Originally Posted by RobinGShore

I'm using an S1 (https://www.avid.com/products/avid-s1) and a Dock (https://www.avid.com/products/avid-dock), which are basically just updated versions of the artist mix and control. I also have an artist mix gathering dust in my closet that I could pull out for testing if needed, but from my understanding of how eucon works, the specific hardware shouldn't make a difference in sussing out bugs like this.

Anyways, flip works as expected for me. If I have the controller showing pans on the knobs and then I hit the flip button, the faders will now control pan and the knobs will control volume. I'm not certain how it works internally, but I think it could be that the type of messages that get sent out don't actually change, just the parameters that those messages control, so what you're seeing could still make sense. I could be totally be off base though and have no idea what I'm talking about.

The Flip works on the Artist Mix you just have to hold Shift+Flip Chan. Plus it works with Eucon-mapped FX too.

However, Touch mode doesn't work at all with Eucon-mapped FX at the moment. Which, I doubted they would.

[Geoff Waddington]

Originally Posted by Funkybot

Try this on the Artist Mix...

1. Start with Mix/Pan button lit up on the left
2. Hold the Shift button on the Artist Mix (bottom right)
3. Press the "Flip Chan" button on the left

Result: the fader should now control Pan (if using stereo pan) or PanLeft (if using dual pan). The rotary will control volume.

4. Hit the "Page Right" button to control PanWidth or PanRight.
5. Shift+Flip Chan to get you back into regular fader mode.

Doh, I haven't used flip in so long I forgot to press shift

[Geoff Waddington]

Originally Posted by RobinGShore

I'm using an S1 (https://www.avid.com/products/avid-s1) and a Dock (https://www.avid.com/products/avid-dock), which are basically just updated versions of the artist mix and control. I also have an artist mix gathering dust in my closet that I could pull out for testing if needed, but from my understanding of how eucon works, the specific hardware shouldn't make a difference in sussing out bugs like this.

Anyways, flip works as expected for me. If I have the controller showing pans on the knobs and then I hit the flip button, the faders will now control pan and the knobs will control volume. I'm not certain how it works internally, but I think it could be that the type of messages that get sent out don't actually change, just the parameters that those messages control, so what you're seeing could still make sense. I could be totally be off base though and have no idea what I'm talking about.

Nah, it was me

[Funkybot]

Originally Posted by Geoff Waddington

Doh, I haven't used flip in so long I forgot to press shift

Avid doesn't always make these things obvious.

[Geoff Waddington]

Originally Posted by RobinGShore

I can also confirm that the Eucon touch automation bug is now gone when writing volume automation with the faders, however if I flip the faders and use them to write pan automation instead of volume, the bug still happens with the pan envelope.

Also sends are not working in Eucon on this latest build. When I hit the button to show sends on the controller nothing appears. This was working in the last version.

Yes, I have yet to sort out the bug on the rotary envelope, it's a bit trickier, a bit deeper in the EuCon maze

[Geoff Waddington]

Originally Posted by Funkybot

Avid doesn't always make these things obvious.

It's right there in the small print -- Fiip is above Chan, I just didn't have my reading glasses on

[cjewellstudios]

Directed at MixMonkey

I think I remember you saying something about a mathematical way of figuring out the stepped parameters? Say a param has 6 steps: 0 is the first step and 1 is the last one. Now I know from experience that the rest of the steps are .2 .4 .6 .8.

Previously, I would just take a stepped param and automate it through all of the steps and then look at the envelope to get the correct numbers. However (maybe this came in a Reaper update) that little display on the envelope lane shows the value in the plugin rather than the numerical value between 0 and 1. Makes perfect sense for Reaper but throws a wrench in my stepped param workflow.

My workaround was to do the same thing, then make an automation item and copy it to an airwindows plugin (he typically leaves at least one param in its "0 to 1" state) and then use those values. It's worth it to me to do these extra steps but I feel like maybe theres a better way.

Do you have any advice here, friends?

[Funkybot]

Originally Posted by cjewellstudios

Directed at MixMonkey

I think I remember you saying something about a mathematical way of figuring out the stepped parameters? Say a param has 6 steps: 0 is the first step and 1 is the last one. Now I know from experience that the rest of the steps are .2 .4 .6 .8.

Previously, I would just take a stepped param and automate it through all of the steps and then look at the envelope to get the correct numbers. However (maybe this came in a Reaper update) that little display on the envelope lane shows the value in the plugin rather than the numerical value between 0 and 1. Makes perfect sense for Reaper but throws a wrench in my stepped param workflow.

My workaround was to do the same thing, then make an automation item and copy it to an airwindows plugin (he typically leaves at least one param in its "0 to 1" state) and then use those values. It's worth it to me to do these extra steps but I feel like maybe theres a better way.

Do you have any advice here, friends?

I do this:

([Number of parameter values] - 1) then divide the number 1 by that result.

So let’s say the parameter has 3 values: low, mid, high... so 3 minus 1 is 2. Now take that result and divide 1 by it. That leaves 0.5. That’s your step size.

If it were 4 steps, is the sum of 1 divided by 3, that’s 0.3333. Round up to be safe and you get 0.34.

Math is not my strong suit but that’s my approach.

[cjewellstudios]

Originally Posted by Funkybot

I do this:

([Number of parameter values] - 1) then divide the number 1 by that result.

So let’s say the parameter has 3 values: low, mid, high... so 3 minus 1 is 2. Now take that result and divide 1 by it. That leaves 0.5. That’s your step size.

If it were 4 steps, is the sum of 1 divided by 3, that’s 0.3333. Round up to be safe and you get 0.34.

Math is not my strong suit but that’s my approach.

Makes sense!

It might be helpful to just do the math and make a chart of stepped values up to 10 steps or something of that nature, assuming the math always works out that is. Maybe I'll do that. Having the work you did on the colors for the MFTRGB page on the wiki is so great!

[MixMonkey]

Originally Posted by cjewellstudios

Directed at MixMonkey

I think I remember you saying something about a mathematical way of figuring out the stepped parameters? Say a param has 6 steps: 0 is the first step and 1 is the last one. Now I know from experience that the rest of the steps are .2 .4 .6 .8.

Previously, I would just take a stepped param and automate it through all of the steps and then look at the envelope to get the correct numbers. However (maybe this came in a Reaper update) that little display on the envelope lane shows the value in the plugin rather than the numerical value between 0 and 1. Makes perfect sense for Reaper but throws a wrench in my stepped param workflow.

My workaround was to do the same thing, then make an automation item and copy it to an airwindows plugin (he typically leaves at least one param in its "0 to 1" state) and then use those values. It's worth it to me to do these extra steps but I feel like maybe theres a better way.

Do you have any advice here, friends?

I start with this:

16	[ (4,4,3,2,1) 0.0 0.07 0.13 0.20 0.27 0.33 0.40 0.47 0.53 0.60 0.67 0.73 0.80 0.87 0.93 1.0 ]
15	[ (4,4,3,2,1) 0.0 0.07 0.14 0.21 0.29 0.36 0.43 0.50 0.57 0.64 0.71 0.79 0.86 0.93 1.0 ]
14	[ (4,4,3,2,1) 0.0 0.80 0.15 0.23 0.31 0.38 0.46 0.54 0.62 0.69 0.77 0.85 0.92 1.0 ]
13	[ (4,4,3,2,1) 0.0 0.05 0.13 0.21 0.30 0.38 0.46 0.55 0.63 0.71 0.80 0.88 1.0 ]
12	[ (4,4,3,2,1) 0.0 0.09 0.18 0.27 0.36 0.45 0.55 0.64 0.73 0.82 0.91 1.0 ]
11	[ (4,4,3,2,1) 0.0 0.10 0.20 0.30 0.40 0.50 0.60 0.70 0.80 0.90 1.0 ]
10	[ (4,4,3,2,1) 0.0 0.11 0.22 0.33 0.44 0.55 0.66 0.77 0.88 1.0 ]
9	[ (4,4,3,2,1) 0.0 0.12 0.25 0.37 0.50 0.62 0.75 0.87 1.0 ]
8	[ (4,4,3,2,1) 0.0 0.14 0.29 0.43 0.57 0.71 0.86 1.0 ]
7	[ (4,4,3,2,1) 0.0 0.17 0.33 0.50 0.67 0.83 1.0 ]
6	[ (4,4,3,2,1) 0.0 0.20 0.40 0.60 0.80 1.0 ]
5	[ (4,4,3,2,1) 0.0 0.25 0.50 0.75 1.0 ]
4	[ (4,4,3,2,1) 0.0 0.34 0.67 1.0 ]
3	[ (4,4,3,2,1) 0.0 0.50 1.0 ]

...and just cut'n'paste into the Zone.

For the plugins that don't play fair, I use BlueCat Patchwork (super handy plugin). I put the plugin in Patchwork, assign the parameter to one of its controllers (they run from 0-100%) You can increment them 1% at a time with the up down arrows, so it's easy to see where the steps are.

[cjewellstudios]

Originally Posted by MixMonkey

I start with this:

16	[ (4,4,3,2,1) 0.0 0.07 0.13 0.20 0.27 0.33 0.40 0.47 0.53 0.60 0.67 0.73 0.80 0.87 0.93 1.0 ]
15	[ (4,4,3,2,1) 0.0 0.07 0.14 0.21 0.29 0.36 0.43 0.50 0.57 0.64 0.71 0.79 0.86 0.93 1.0 ]
14	[ (4,4,3,2,1) 0.0 0.80 0.15 0.23 0.31 0.38 0.46 0.54 0.62 0.69 0.77 0.85 0.92 1.0 ]
13	[ (4,4,3,2,1) 0.0 0.05 0.13 0.21 0.30 0.38 0.46 0.55 0.63 0.71 0.80 0.88 1.0 ]
12	[ (4,4,3,2,1) 0.0 0.09 0.18 0.27 0.36 0.45 0.55 0.64 0.73 0.82 0.91 1.0 ]
11	[ (4,4,3,2,1) 0.0 0.10 0.20 0.30 0.40 0.50 0.60 0.70 0.80 0.90 1.0 ]
10	[ (4,4,3,2,1) 0.0 0.11 0.22 0.33 0.44 0.55 0.66 0.77 0.88 1.0 ]
9	[ (4,4,3,2,1) 0.0 0.12 0.25 0.37 0.50 0.62 0.75 0.87 1.0 ]
8	[ (4,4,3,2,1) 0.0 0.14 0.29 0.43 0.57 0.71 0.86 1.0 ]
7	[ (4,4,3,2,1) 0.0 0.17 0.33 0.50 0.67 0.83 1.0 ]
6	[ (4,4,3,2,1) 0.0 0.20 0.40 0.60 0.80 1.0 ]
5	[ (4,4,3,2,1) 0.0 0.25 0.50 0.75 1.0 ]
4	[ (4,4,3,2,1) 0.0 0.34 0.67 1.0 ]
3	[ (4,4,3,2,1) 0.0 0.50 1.0 ]

...and just cut'n'paste into the Zone.

For the plugins that don't play fair, I use BlueCat Patchwork (super handy plugin). I put the plugin in Patchwork, assign the parameter to one of its controllers (they run from 0-100%) You can increment them 1% at a time with the up down arrows, so it's easy to see where the steps are.

Now That's what I'm talkin' 'bout!

Thank you! Oh I also forgot about "acceleration" with the step count, thanks for reminding me!