Control Surface Integration (CSI) Technical Feature Discussion

[Geoff Waddington]

Originally Posted by jacksoonbrowne

What definition should be removed?

[EDIT]
Will try the exp source you posted a few hours ago.
And the new Xtouch support files

Yup, get the new Exp version, and the support files I just posted a minute ago.

[Geoff Waddington]

New Support files are up.

CSI Support Files.zip.

[Geoff Waddington]

New build is up

CSI v2_0.zip

Brings version 2.0 to Exp level.

Gets rid of any nasty flickering caused by recent changes.

[Funkybot]

Wiki updated! Change Log and the Widget Mode pages.

[jacksoonbrowne]

Originally Posted by Geoff Waddington

New build is up

CSI v2_0.zip

Brings version 2.0 to Exp level.

Gets rid of any nasty flickering caused by recent changes.

Confirmed, X-Touch nasty flickering gone

[ivanmihaljevic]

Not sure if anything was done about SelectedTrackReceive banking, but it's still not working on my end.
Also, I noticed one more peculiar thing. I have a footswitch hooked up to my X Touch and it's doing this:

Footswitch1             Reaper 40044 //Transport:Play-stop
Hold+Footswitch1	Record

In CSI 1, this worked great. However, in v 2.0 it always starts recording even if I let go of the pedal immediately. I also noticed that if I remove the Hold+Footswitch1 line it only starts playing once I let go of the pedal while before it would start playing the moment I press the pedal. The pedal I'm using doesn't have a polarity inverse switch, so it's not that.
Any ideas?

[Funkybot]

Originally Posted by ivanmihaljevic

Not sure if anything was done about SelectedTrackReceive banking, but it's still not working on my end.
Also, I noticed one more peculiar thing. I have a footswitch hooked up to my X Touch and it's doing this:

Footswitch1             Reaper 40044 //Transport:Play-stop
Hold+Footswitch1	Record

In CSI 1, this worked great. However, in v 2.0 it always starts recording even if I let go of the pedal immediately. I also noticed that if I remove the Hold+Footswitch1 line it only starts playing once I let go of the pedal while before it would start playing the moment I press the pedal. The pedal I'm using doesn't have a polarity inverse switch, so it's not that.
Any ideas?

The SelectedTrackReceiveBank action not working is something Geoff said last night is next on the to-do list.

Regarding the footswitch: what values does your footswitch actually send when pressed? For Hold to work, it needs to send a press message and a release message. What your describing sounds like it only sends one.

When you run the "CSI Toggle Show Raw Input from Surfaces" action, do you see this with each footswitch press and release?

Footswitch1 90 66 7F 
Footswitch1 90 66 00

[ivanmihaljevic]

Originally Posted by Funkybot

The SelectedTrackReceiveBank action not working is something Geoff said last night is next on the to-do list.

Regarding the footswitch: what values does your footswitch actually send when pressed? For Hold to work, it needs to send a press message and a release message. What your describing sounds like it only sends one.

When you run the "CSI Toggle Show Raw Input from Surfaces" action, do you see this with each footswitch press and release?

Footswitch1 90 66 7F 
Footswitch1 90 66 00

Awesome to hear about receive banking!

Yup! Those are the values I'm seeing. The timing is right too, I see the 7F message the moment I press it and the 00 message the moment I release.
And the mst definition is:

Widget Footswitch1
  Press 90 66 7F 90 66 00
WidgetEnd

The same mst definition and the same actions in the Zone file worked for CSI v1.

[Funkybot]

Originally Posted by ivanmihaljevic

Awesome to hear about receive banking!

Yup! Those are the values I'm seeing. The timing is right too, I see the 7F message the moment I press it and the 00 message the moment I release.
And the mst definition is:

Widget Footswitch1
  Press 90 66 7F 90 66 00
WidgetEnd

The same mst definition and the same actions in the Zone file worked for CSI v1.

Maybe it's a timing issue. Have you tried very fast press and releases? I'm not sure what the actual timing is for a hold message but feet aren't as fast as fingers, so I'm thinking maybe that's where the issue lies.

[ivanmihaljevic]

Originally Posted by Funkybot

Maybe it's a timing issue. Have you tried very fast press and releases? I'm not sure what the actual timing is for a hold message but feet aren't as fast as fingers, so I'm thinking maybe that's where the issue lies.

I did try! And I'm quite sure that it's not a timing thing. Because I press it and release it and the recording (which is the hold+ command) starts about a second after I let go of the pedal. Interestingly it also only starts playing right after I let go of the pedal and it used to play when I pressed it and then started recording a second after if I don't release it.

[Geoff Waddington]

Originally Posted by ivanmihaljevic

I did try! And I'm quite sure that it's not a timing thing. Because I press it and release it and the recording (which is the hold+ command) starts about a second after I let go of the pedal. Interestingly it also only starts playing right after I let go of the pedal and it used to play when I pressed it and then started recording a second after if I don't release it.

What happens if you do this instead:

Footswitch1             Play
Hold+Footswitch1	Record

[MT4U]

Originally Posted by Geoff Waddington

New build is up

CSI v2_0.zip

Brings version 2.0 to Exp level.

Gets rid of any nasty flickering caused by recent changes.

Great. I just noticed something else.

I had these "Dummy" reaper action that I map on buttons to turn the lights on when the "real" action does not (GoSubZone i.e.), so that I know there's an action mapped, but it stopped working after the last build. Is there any other way to accomplish this?

Thanks!

[Funkybot]

Originally Posted by MT4U

Great. I just noticed something else.

I had these "Dummy" reaper action that I map on buttons to turn the lights on when the "real" action does not (GoSubZone i.e.), so that I know there's an action mapped, but it stopped working after the last build. Is there any other way to accomplish this?

Thanks!

What action? There are some Dummy Toggles in SWS, I think those correctly report their state and should still work. If anything post the action.

[MT4U]

Originally Posted by Funkybot

What action? There are some Dummy Toggles in SWS, I think those correctly report their state and should still work. If anything post the action.

I've been mapping FX Zones on the X-Touch based on SubZone menus that list the names of the SubZones (i.e.: OSC / AMP / FILTER / ETC) and load the different SubZones by pressing the Select buttons.

Since CSI did not turn the LEDs on when I mapped "GoSubZone..." on a button, I was adding first a line with reaper action 2008 (Action: Wait 0.1 seconds before next action) which did nothing, but turned my LEDs on indicating that there was something mapped to the button.

  .....
  Select1 Reaper 2008
  Select1 GoSubZone "VST3: ValhallaSupermassive (Valhalla DSP, LLC)-1"
  .....

Well... I know it is a little weird, but worked fine for me up to the previous build. It stopped working with last build, I believe it maybe related to the feedback changes, but in the end I solved it by just doing this instead:

  .....
  InvertFB+Select1 GoSubZone "VST3: ValhallaSupermassive (Valhalla DSP, LLC)-1"
  .....

I believe this may be closer to the "proper" way of doing it

Thanks FunkyBot, your reply led me in the right direction.

[ivanmihaljevic]

Originally Posted by Geoff Waddington

What happens if you do this instead:

Footswitch1             Play
Hold+Footswitch1	Record

I don't like that option because it does Play/Pause and I want Play/Stop, but I'll see if it changes anything about triggering the hold behavior even when I'm not holding the footswitch pressed.

[ivanmihaljevic]

Originally Posted by Geoff Waddington

What happens if you do this instead:

Footswitch1             Play
Hold+Footswitch1	Record

Tried now, still the same issue!

[ivanmihaljevic]

Originally Posted by Funkybot

The SelectedTrackReceiveBank action not working is something Geoff said last night is next on the to-do list.

Regarding the footswitch: what values does your footswitch actually send when pressed? For Hold to work, it needs to send a press message and a release message. What your describing sounds like it only sends one.

When you run the "CSI Toggle Show Raw Input from Surfaces" action, do you see this with each footswitch press and release?

Footswitch1 90 66 7F 
Footswitch1 90 66 00

Oh wait... I just realized something! The footswitch I'm using is sending these messages in reverse! Just tried a different pedal and everything works as it should. It seems the pedal somehow changed the polarity even though there's no switch for it.
Anyway, it's not a CSI issue, but a hardware issue it seems.

UPDATE: I opened up the pedal and there are no polarity switches on the inside either and everything looks good. It's a very simple pedal and all the connections seem fine. I cleaned everything with contact cleaner, put it back together and the same issue still persisted. So... I decided to just switch the 7F and 00 values in the MST and now it works as I want it to. It's really weird that a pedal would just change the polarity like that, but I managed to solve it and that's what matters

[RattlesnakeLodge]

I had another thought as far as new and potentially very powerful features, hopefully easy to implement...

Custom exclusive global modifiers. By exclusive, I mean activating one, deactivates all other custom modifiers. Perhaps modifier is not the right name for it, but it could essentially be the same mechanism under the hood. For example, let's say there are 100 of these custom modifiers. For the purposes of not mistaking these for pre-named conventional modifiers, I will call this "ParamBank"...

"
Select1 ParamBank1
Select2 ParamBank2
Select3 ParamBank3
Select4 ParamBank4
"

...and so on.

"
ParamBank1+RotaryA1 SomeAction
ParamBank2+RotaryA1 AnotherAction
"

Again, I would suggest these custom modifiers, or "ParamBank"s are exclusive. Meaning, one gets activated, it turns the rest off. Not the pre-named modifiers like Shift, Options, Control, Alt, etc, just the proposed custom ones.

They should also be global, just like Shift, Option, Control, and Alt.

What I'm personally trying to solve is how to get a control action from one surface to change the mapped actions of another surface. For example, I would like to hit a button on my X-Touch Universal, which defines what specific band of EQ or multiband compression my Midi Fighter Twister is controlling. Without Broadcast/Receive support for SubZones, and a limited number of pre-named global modifiers that can be repurposed, it is pretty difficult.

This is just one example of how these custom modifiers could benefit users. But it is also would I can't currently think of, some extra room for customization, that may make this requested feature very powerful.

Cheers!

[MT4U]

Originally Posted by RattlesnakeLodge

What I'm personally trying to solve is how to get a control action from one surface to change the mapped actions of another surface. For example, I would like to hit a button on my X-Touch Universal, which defines what specific band of EQ or multiband compression my Midi Fighter Twister is controlling. Without Broadcast/Receive support for SubZones, and a limited number of pre-named global modifiers that can be repurposed, it is pretty difficult.

This is just one example of how these custom modifiers could benefit users. But it is also would I can't currently think of, some extra room for customization, that may make this requested feature very powerful.

Cheers!

Interesting. I still think that SubZone broadcasting with a declaration of "SubZoneReceive On/Off" on zone activation for the Zones in other surfaces would suffice though.

[iNX]

Hello,

I've a problem with my xtouch when I want to change bank, and channel. In fact I've set on the same page 3 configuration of MCU on my elgato streamdeck to show all tracks and select it easily, but when I do this, my xtouch is fixed on the 8 first track and I can't navigate on other track on the xtouch. Is it normal for you?

[Manwë]

I haven't seen this mentioned before so sorry if I'm repeating an idea!!

This is just a simple way to keep track of the currently active zone using the SWS Image Resources and the docked image window.



Using the SWS Image Resources menu, you can add a "SWS/S&M: Resources - Show image, slot _" action with the corresponding button for switching between specific zones.

By default, Show image 1-4 is available in the actions menu.

You can extend this by changing the line "S&M_SHOW_IMG=___" line in your S&M.ini file, located in your Reaper resources path, to however many you'll need.

Make a PNG template for your zones on pixlr.com and add them to your Images resources in your SWS Extensions menu.

Add your images in SWS Extensions, add the CMD ID's to your CSI zone activation buttons and that's it!

Hopefully someone can find this useful!

[Funkybot]

Brilliant! Haven't seen anyone do that. Thanks for sharing.

[Geoff Waddington]

Originally Posted by Manwë

I haven't seen this mentioned before so sorry if I'm repeating an idea!!

This is just a simple way to keep track of the currently active zone using the SWS Image Resources and the docked image window.



Using the SWS Image Resources menu, you can add a "SWS/S&M: Resources - Show image, slot _" action with the corresponding button for switching between specific zones.

By default, Show image 1-4 is available in the actions menu.

You can extend this by changing the line "S&M_SHOW_IMG=___" line in your S&M.ini file, located in your Reaper resources path, to however many you'll need.

Make a PNG template for your zones on pixlr.com and add them to your Images resources in your SWS Extensions menu.

Add your images in SWS Extensions, add the CMD ID's to your CSI zone activation buttons and that's it!

Hopefully someone can find this useful!

Impressive !

The creativity of CSI users never ceases to amaze me, as does the power and flexibility of Reaper itself.

[Manwë]

This could work as an equivalent function to the Projection option in ReaLearn, as well!

I used another SWS Extension to combine the Zone Image above with a SWS Cycle Action to show the Projection image just in case your forget a mapping!



Make 2 new custom actions for the 2 images you want to use for the selected zone like the following:

///First custom action for the Surface mapping image. I named mine "CSI HOME MAPPING--> UNDOCK"

SWS/S&M: Resources - Show image, slot __
Dock/undock currently focused window

///Second custom action to return to the docked CSI zone image. I named mine "CSI HOME ZONE-->DOCK"

SWS/S&M: Resources - Show image, slot __
Dock/undock currently focused window

Then a SWS Cycle Action with toggle enabled like the following:

(custom action command ID)          Custom: CSI HOME MAPPING-->UNDOCK
!                                   -----Step-----
(custom action command ID)          Custom: CSI HOME ZONE-->DOCK

Dock your Zone image where you'd like it, map your Cycle Action to a surface button in your zone and press, resize/locate your Mapping image where you'd like it and done!

The only downside is you would need to have the Zone image docked before activating another zone. Otherwise the Zone image and projection image are swapped. Quick fix though!

You can skip all the docking options too if you have a separate monitor!

[MixMonkey]

Originally Posted by Manwë

This could work as an equivalent function to the Projection option in ReaLearn, as well!

I used another SWS Extension to combine the Zone Image above with a SWS Cycle Action to show the Projection image just in case your forget a mapping!



Make 2 new custom actions for the 2 images you want to use for the selected zone like the following:

///First custom action for the Surface mapping image. I named mine "CSI HOME MAPPING--> UNDOCK"

SWS/S&M: Resources - Show image, slot __
Dock/undock currently focused window

///Second custom action to return to the docked CSI zone image. I named mine "CSI HOME ZONE-->DOCK"

SWS/S&M: Resources - Show image, slot __
Dock/undock currently focused window

Then a SWS Cycle Action with toggle enabled like the following:

(custom action command ID)          Custom: CSI HOME MAPPING-->UNDOCK
!                                   -----Step-----
(custom action command ID)          Custom: CSI HOME ZONE-->DOCK

Dock your Zone image where you'd like it, map your Cycle Action to a surface button in your zone and press, resize/locate your Mapping image where you'd like it and done!

The only downside is you would need to have the Zone image docked before activating another zone. Otherwise the Zone image and projection image are swapped. Quick fix though!

You can skip all the docking options too if you have a separate monitor!

I wonder if this could be adapted to show the control mapping in an active FX.zon? Then all those surfaces that don't have displays would become a lot more user friendly without the need for an additional iPad to display the mapping

[Manwë]

Originally Posted by MixMonkey

I wonder if this could be adapted to show the control mapping in an active FX.zon? Then all those surfaces that don't have displays would become a lot more user friendly without the need for an additional iPad to display the mapping

I'm sure there is a way to implement this!

I've included the PNG files for the zone images if anyone is interested as well!

[Funkybot]

Manwë, I assume you don't mind, but I added this great tip to the Wiki in the Tips and Tricks section, including the .png's and .gif's.

https://github.com/GeoffAWaddington/...ping-in-reaper

Please review and let me know if anything needs to be changed.

[Manwë]

Originally Posted by Funkybot

Manwë, I assume you don't mind, but I added this great tip to the Wiki in the Tips and Tricks section, including the .png's and .gif's.

https://github.com/GeoffAWaddington/...ping-in-reaper

Please review and let me know if anything needs to be changed.

Of course! Very happy this was useful enough to include in the Wiki!

Looks great, certainly more thorough than my walkthrough!

[rmusmeci]

Dear CSI developers,

I very much appreciate your work. I really think the CSIs have great potential under the hood and will always get better with time.

Unfortunately I'm facing an annoying issue with the time display of my IconNano. When the measure indicator overtook a digit, this will not be erased when the time cursor goes back. For exampple, having a project with 110 measures, when the cursor reaches the measure say 107, when going back to the measure 25, the display will show 125 (as if the hundreds digit will become permanent).

The only way to reset the stuck digit is to reinitializing the CSI plugin opening the preferences or restarting Reaper.

Is there someone else facing this issue? Is there some workaround?

Thank a lot

[MikeMcK]

Probably not a big deal, but I believe I found a typo in Buttons.zon. I'm sure "Nidge" below should be "Nudge".

Also, please let me know if there's a better place to report this kind of thing.

    Nudge+Up                    Reaper 41925                // Item: Nudge items volume +1dB
    Nudge+Down                  Reaper 41924                // Item: Nudge items volume -1dB
    Nidge+Left                  Reaper 41279                // Item edit: Nudge left by saved nudge dialog settings 1
    Nudge+Right                 Reaper 41275                // Item edit: Nudge right by saved nudge dialog settings 1

[Geoff Waddington]

Originally Posted by MikeMcK

Probably not a big deal, but I believe I found a typo in Buttons.zon. I'm sure "Nidge" below should be "Nudge".

Also, please let me know if there's a better place to report this kind of thing.

    Nudge+Up                    Reaper 41925                // Item: Nudge items volume +1dB
    Nudge+Down                  Reaper 41924                // Item: Nudge items volume -1dB
    Nidge+Left                  Reaper 41279                // Item edit: Nudge left by saved nudge dialog settings 1
    Nudge+Right                 Reaper 41275                // Item edit: Nudge right by saved nudge dialog settings 1

Thanks, fixed, and updated CSI Support Files.zip

[MT4U]

I've been testing the latest Feedback changes and I tried this:

  RecordArm8  FXParam 351 [ 0.0 1.0 ] Feedback=No

but I always get feedback on the LED.

X-Touch Extender, latest build.

[jacksoonbrowne]

"TrackFolderParentDisplay" action doesn't appear in Wiki ?

[Funkybot]

Originally Posted by MT4U

I've been testing the latest Feedback changes and I tried this:

  RecordArm8  FXParam 351 [ 0.0 1.0 ] Feedback=No

but I always get feedback on the LED.

X-Touch Extender, latest build.

This probably won't make a difference (90% sure it won't) but have you tried it this way too?

  RecordArm8  FXParam 351 Feedback=No [ 0.0 1.0 ]

[Funkybot]

Originally Posted by jacksoonbrowne

"TrackFolderParentDisplay" action doesn't appear in Wiki ?

I don't think I realized that existed but I see it in the X-Touch folder.zon file. Will add it tomorrow. Thanks for the call-out Roy!

[MT4U]

Originally Posted by Funkybot

This probably won't make a difference (90% sure it won't) but have you tried it this way too?

  RecordArm8  FXParam 351 Feedback=No [ 0.0 1.0 ]

First thing I did

[ivanv]

hey all,
long time admirer, first time poster
i wanted to know if anyone has come up with a workflow for using CSI to address reaper's track controls?
(the ones that we can make show up in the reaper mixer for plugin paramaters we select)
what i'm looking to do is have it such that my control surface (mackie control + c4) has some controls that map on to whatever track controls may be present on the selected track.
any suggestions would be greatly appreciated!

and, my apologies if this has been covered, i've scoured the documentation and this thread and couldn't find a solution.

[MT4U]

Originally Posted by ivanv

hey all,
long time admirer, first time poster
i wanted to know if anyone has come up with a workflow for using CSI to address reaper's track controls?
(the ones that we can make show up in the reaper mixer for plugin paramaters we select)
what i'm looking to do is have it such that my control surface (mackie control + c4) has some controls that map on to whatever track controls may be present on the selected track.
any suggestions would be greatly appreciated!

and, my apologies if this has been covered, i've scoured the documentation and this thread and couldn't find a solution.

Hi there, welcome to the forum!

If I understand correctly, you mean the Track Controls in the TCP (not the Mixer).

As far as I know, you will have to create FX SubZones for every plug-in on the track and control them independently... dunno if the wizzards here have another suggestion.

[Funkybot]

Originally Posted by ivanv

hey all,
long time admirer, first time poster
i wanted to know if anyone has come up with a workflow for using CSI to address reaper's track controls?
(the ones that we can make show up in the reaper mixer for plugin paramaters we select)
what i'm looking to do is have it such that my control surface (mackie control + c4) has some controls that map on to whatever track controls may be present on the selected track.
any suggestions would be greatly appreciated!

and, my apologies if this has been covered, i've scoured the documentation and this thread and couldn't find a solution.

That's what I call the "Console One workflow". That can absolutely be done in CSI, but as pointed out by MT4U, not at the Track Controls-level but rather at the plugin-level. So let's say you had a surface with 16 rotaries, you could have the first always be mapped to a HP filter, followed by some EQ bands, you could have rotary 9 always mapped to compressor theshold, etc. and then activate those multiple FX maps when you click on a track. But it would be up to you to create the mappings for any plugins like that, and you'd want to be careful to make sure the mappings didn't conflict.

Step 1 is creating the FX maps...

https://github.com/GeoffAWaddington/...rument-Mapping

Then you'd have to activate the FX (see SelectedTrackFX):

https://github.com/GeoffAWaddington/...electedTrackFX)

Then you'd create a command that essentially says, "whenever a track is selected in Reaper, map the FX..."

https://github.com/GeoffAWaddington/...electedtrackfx

[Geoff Waddington]

Originally Posted by ivanv

hey all,
long time admirer, first time poster
i wanted to know if anyone has come up with a workflow for using CSI to address reaper's track controls?
(the ones that we can make show up in the reaper mixer for plugin paramaters we select)
what i'm looking to do is have it such that my control surface (mackie control + c4) has some controls that map on to whatever track controls may be present on the selected track.
any suggestions would be greatly appreciated!

and, my apologies if this has been covered, i've scoured the documentation and this thread and couldn't find a solution.

Funkybot has provided some great resources to get you going, hopefully MixMonkey will also chime in as he has Mackie Control(s) and a C4, so he might have something that will work right out of the box.

And welcome to the forum !