Control Surface Integration (CSI) Technical Feature Discussion

[Geoff Waddington]

Originally Posted by MixMonkey

This seems to work fine also. Hid a bunch of tracks not currently within the scope of the surface banking, from the TCP in Reaper. Then banked the surface to the place where they should be and they were hidden.

So TCP works fine too, just not in realtime ?

If so, we can add ToggleFollowMCPVisibility with the caveats about the realtime behaviour.

[Geoff Waddington]

WARNING BREAKING CHANGES WARNING BREAKING CHANGES

New build is up.

CSI Exp.zip

There is a new Action:

ToggleSynchPageBanking

There is a new CSI.ini file format:

Version 2.0
MidiSurface "XTouch Universal" 12 11 
MidiSurface "SCE24" 11 10
OSCSurface "iPhone" 8000 9000 168.192.2.1
Page "HomePage" 
"SCE24" 1 0 "SCE24.mst" "SCE24_FB"
"XTouch Universal" 8 0 "X-Touch.mst" "X-Touch" 
"iPhone" 0 0 "TouchOSCPhone.ost" "TouchOSCPhone"

I tested Midi but not OSC, so be very careful

Also note, the Config panel GUI DOES NOT WORK !!

I'll tackle that next.

Just thought I'd get this to you folks so you can manually edit CSI.ini and test if Pages now work without all hell breaking loose

[Funkybot]

Will leave it to Puck and MixMonkey to test the page thing, but I can at least verify that once you manually recreate the CSI.ini, everything still works with a single page.

[MixMonkey]

Originally Posted by Geoff Waddington

So TCP works fine too, just not in realtime ?

Umm, as far as I can tell, the surface won't follow the TCP visibility at all.

[Puck]

Originally Posted by Geoff Waddington

WARNING BREAKING CHANGES WARNING BREAKING CHANGES

New build is up.

CSI Exp.zip

Version 2.0
MidiSurface "XTouch Universal" 12 11 
MidiSurface "SCE24" 11 10
OSCSurface "iPhone" 8000 9000 168.192.2.1
Page "HomePage" 
"SCE24" 1 0 "SCE24.mst" "SCE24_FB"
"XTouch Universal" 8 0 "X-Touch.mst" "X-Touch" 
"iPhone" 0 0 "TouchOSCPhone.ost" "TouchOSCPhone"

1. I think we are getting somewhere here

- I no longer lose connection after going to Page2 from my test files. Now on page two I have feedback AND I can control reaper. However, CSI doesn't show input on the log anymore and I can't seem to go back to Page1.

2. And this is just a curiosity that doesn't affect me:

- What's with the numbers after the midisurface entries? I thought it was number of channels and the start position. But your numbers look off for it to be that. Then the numbers show up again in the Page definition but they are different. I feel like I missed something

[Funkybot]

Originally Posted by Puck

2. And this is just a curiosity that doesn't affect me:

- What's with the numbers after the midisurface entries? I thought it was number of channels and the start position. But your numbers look off for it to be that. Then the numbers show up again in the Page definition but they are different. I feel like I missed something

The numbers in the surface section represent the MIDI Device ID for each port. If you go to Reaper's Preferences -> MIDI Devices, you'll see the ID # next to each MIDI device.

The numbers in the "Page" section are the channel count and offset.

Different numbers. Though I suppose it's possible they could be the same.

[MT4U]

Hi there, all. Been digging deeper into the machine, with both the wiki and this forum as my Bibles for the last months. Anyhow I've gotten myself stuck with a couple of ideas where I'm not sure I'm doing things properly, so here I go.

I'm Using an X-Touch with an Extender like this.

Version 2.0
Page "HomePage" FollowTCP NoSynchPages UseScrollLink 
MidiSurface "X-Touch_XT" 12 12 "X-Touch_XT.mst" "XT" 8 0 
MidiSurface "X-Touch" 7 8 "X-Touch.mst" "X-Touch" 8 8

***I'm with the July 2nd. version

I initialize my Home.zon like this on the X-Touch

Zone Home
      OnInitialization ToggleEnableFocusedFXMapping
      OnInitialization Broadcast Home SelectedTrackSend SelectedTrackReceive SelectedTrackFXMenu TrackSend TrackReceive TrackFXMenu
      OnInitialization Receive Home SelectedTrackSend SelectedTrackReceive SelectedTrackFXMenu TrackSend TrackReceive TrackFXMenu
    IncludedZones
        "Buttons"
        "Track"
        "MasterTrack"
    IncludedZonesEnd
    AssociatedZones
       "SelectedTrackSend"
       "SelectedTrackReceive"
       "SelectedTrackFXMenu"
       "TrackSend"
       "TrackReceive"
       "TrackFXMenu"
    AssociatedZonesEnd
ZoneEnd

and the Extender.

Zone "Home"
      OnInitialization ToggleEnableFocusedFXMapping
      OnInitialization Receive Home SelectedTrackSend SelectedTrackReceive SelectedTrackFXMenu TrackSend TrackReceive TrackFXMenu
      OnInitialization Broadcast Home SelectedTrackSend SelectedTrackReceive SelectedTrackFXMenu TrackSend TrackReceive TrackFXMenu
        IncludedZones
            "Track"
        IncludedZonesEnd
        AssociatedZones         
          "SelectedTrackSend"
          "SelectedTrackReceive"
          "SelectedTrackFXMenu"
          "TrackSend"
          "TrackReceive"
          "TrackFXMenu"
        AssociatedZonesEnd
ZoneEnd

1) I add this at the begining of my SelectedTrackFXMenu.zon (on both) but I'm not sure if I need it in other zones besides Home.

    OnInitialization Broadcast Home SelectedTrackSend SelectedTrackReceive SelectedTrackFXMenu TrackSend TrackReceive TrackFXMenu
    OnInitialization Receive Home SelectedTrackSend SelectedTrackReceive SelectedTrackFXMenu TrackSend TrackReceive TrackFXMenu

2) Whenever I map Sends/Receives/FX to the Encoders, they get repeated in both the XT and the Extender. Not sure if it's the default behaviour or I'm missing something.

I map with:

Send                        GoSelectedTrackSend

This is my SelectedTrackSend.zon on both the X-Touch and the Extender.

Zone "SelectedTrackSend"
      DisplayUpper|               TrackSendNameDisplay
      DisplayLower| 		          TrackSendPrePostDisplay
      Fader|Touch+DisplayLower|   TrackSendVolumeDisplay
      Shift+DisplayLower|         TrackSendPanDisplay
      RotaryPush|		              TrackSendPan [ 0.5 ]
      Mute|                       TrackSendMute
      Rotary|                     TrackSendPan
      Fader|                      TrackSendVolume
      Left                        SelectedTrackSendBank -1
      Right                       SelectedTrackSendBank 1
      RecordArm|                  TrackSendPrePost
      Solo|                       NoAction
      Select|                     Reaper "40293"
      Property+Select|            NoFeedback
ZoneEnd

3) After I map my FX Menu with GoSelectedTrackFXMenu I get my FX chain displayed in both surfaces like with the Sends. Once I load an FX, I load different zones in both surfaces and use the 16 rotaries, buttons and displays to control it.

Thus far my evil plans are working to perfection until I hit the button with the LeaveSubZone on the X-Touch and it goes back to the Menu but the Extender stays with the FX mapped.

Is there a GoBackToFXMenu function or something that I am missing?

Thanks Everyone!

[Geoff Waddington]

Originally Posted by MixMonkey

Umm, as far as I can tell, the surface won't follow the TCP visibility at all.

I'm missing something

You posted this "This seems to work fine also. Hid a bunch of tracks not currently within the scope of the surface banking, from the TCP in Reaper. Then banked the surface to the place where they should be and they were hidden."

What do you mean by "from the TCP in Reaper" ?

Do you mean you used the Track Manager to hide the Tracks on the MCP, but you were doing that operation from the TCP ?

[Geoff Waddington]

Originally Posted by Puck

1. I think we are getting somewhere here

- I no longer lose connection after going to Page2 from my test files. Now on page two I have feedback AND I can control reaper. However, CSI doesn't show input on the log anymore and I can't seem to go back to Page1.

Please post your:
CSI.ini
.ost and/or .mst files
your .zon files

As far as input, did you run the Action again for the new Page ?

You shouldn't do that, checked the code here, looks like it should work.

You could also try replacing GoPage "Page1" and GoPage "Page2" with NextPage for both and see what happens.

Originally Posted by Puck

2. And this is just a curiosity that doesn't affect me:

- What's with the numbers after the midisurface entries? I thought it was number of channels and the start position. But your numbers look off for it to be that. Then the numbers show up again in the Page definition but they are different. I feel like I missed something

If you look carefully at an old CSI.ini file like the one above in MT4U's post you will see, as Funkybot pointed out, 2 pairs of numbers, one for the ports and one for the channel count and offset.

Just one more reason why it's better to separate the 2 concepts, it was really easy to miss in the old format

[Geoff Waddington]

Originally Posted by MT4U

Hi there, all. Been digging deeper into the machine, with both the wiki and this forum as my Bibles for the last months. Anyhow I've gotten myself stuck with a couple of ideas where I'm not sure I'm doing things properly, so here I go.

I'm Using an X-Touch with an Extender like this.

Version 2.0
Page "HomePage" FollowTCP NoSynchPages UseScrollLink 
MidiSurface "X-Touch_XT" 12 12 "X-Touch_XT.mst" "XT" 8 0 
MidiSurface "X-Touch" 7 8 "X-Touch.mst" "X-Touch" 8 8

***I'm with the July 2nd. version

I initialize my Home.zon like this on the X-Touch

Zone Home
      OnInitialization ToggleEnableFocusedFXMapping
      OnInitialization Broadcast Home SelectedTrackSend SelectedTrackReceive SelectedTrackFXMenu TrackSend TrackReceive TrackFXMenu
      OnInitialization Receive Home SelectedTrackSend SelectedTrackReceive SelectedTrackFXMenu TrackSend TrackReceive TrackFXMenu
    IncludedZones
        "Buttons"
        "Track"
        "MasterTrack"
    IncludedZonesEnd
    AssociatedZones
       "SelectedTrackSend"
       "SelectedTrackReceive"
       "SelectedTrackFXMenu"
       "TrackSend"
       "TrackReceive"
       "TrackFXMenu"
    AssociatedZonesEnd
ZoneEnd

and the Extender.

Zone "Home"
      OnInitialization ToggleEnableFocusedFXMapping
      OnInitialization Receive Home SelectedTrackSend SelectedTrackReceive SelectedTrackFXMenu TrackSend TrackReceive TrackFXMenu
      OnInitialization Broadcast Home SelectedTrackSend SelectedTrackReceive SelectedTrackFXMenu TrackSend TrackReceive TrackFXMenu
        IncludedZones
            "Track"
        IncludedZonesEnd
        AssociatedZones         
          "SelectedTrackSend"
          "SelectedTrackReceive"
          "SelectedTrackFXMenu"
          "TrackSend"
          "TrackReceive"
          "TrackFXMenu"
        AssociatedZonesEnd
ZoneEnd

1) I add this at the begining of my SelectedTrackFXMenu.zon (on both) but I'm not sure if I need it in other zones besides Home.

    OnInitialization Broadcast Home SelectedTrackSend SelectedTrackReceive SelectedTrackFXMenu TrackSend TrackReceive TrackFXMenu
    OnInitialization Receive Home SelectedTrackSend SelectedTrackReceive SelectedTrackFXMenu TrackSend TrackReceive TrackFXMenu

Remove those lines from SelectedTrackFXMenu, they aren't needed.

Originally Posted by MT4U

2) Whenever I map Sends/Receives/FX to the Encoders, they get repeated in both the XT and the Extender. Not sure if it's the default behaviour or I'm missing something.

I map with:

Send                        GoSelectedTrackSend

This is my SelectedTrackSend.zon on both the X-Touch and the Extender.

Zone "SelectedTrackSend"
      DisplayUpper|               TrackSendNameDisplay
      DisplayLower| 		          TrackSendPrePostDisplay
      Fader|Touch+DisplayLower|   TrackSendVolumeDisplay
      Shift+DisplayLower|         TrackSendPanDisplay
      RotaryPush|		              TrackSendPan [ 0.5 ]
      Mute|                       TrackSendMute
      Rotary|                     TrackSendPan
      Fader|                      TrackSendVolume
      Left                        SelectedTrackSendBank -1
      Right                       SelectedTrackSendBank 1
      RecordArm|                  TrackSendPrePost
      Solo|                       NoAction
      Select|                     Reaper "40293"
      Property+Select|            NoFeedback
ZoneEnd

Yes, that's as per design, you can bank the Sends with TrackSendBank 1, TrackSendBank -1, etc. but you can't span Surfaces like you can with Tracks.

Originally Posted by MT4U

3) After I map my FX Menu with GoSelectedTrackFXMenu I get my FX chain displayed in both surfaces like with the Sends. Once I load an FX, I load different zones in both surfaces and use the 16 rotaries, buttons and displays to control it.

Thus far my evil plans are working to perfection until I hit the button with the LeaveSubZone on the X-Touch and it goes back to the Menu but the Extender stays with the FX mapped.

Is there a GoBackToFXMenu function or something that I am missing?

Thanks Everyone!

Not quite sure what you mean about LeaveSubZone, someone else will likely chime in on that

[MT4U]

Originally Posted by Geoff Waddington

Remove those lines from SelectedTrackFXMenu, they aren't needed.

Not quite sure what you mean about LeaveSubZone, someone else will likely chime in on that

Thanks for your reply!

I use LeaveSubZone from inside the FX Zone and it takes the X-Touch back to the FX Menu, but this does not happen on the Extender which stays inside the FX Zone. I was thinking maybe LeaveSubZone is not the correct function but can't find the best one.

[MixMonkey]

Originally Posted by Geoff Waddington

I'm missing something

You posted this "This seems to work fine also. Hid a bunch of tracks not currently within the scope of the surface banking, from the TCP in Reaper. Then banked the surface to the place where they should be and they were hidden."

What do you mean by "from the TCP in Reaper" ?

I mean I right click on the selected tracks in the TCP and choose "show/hide in MCP"

I agree the terminology is very confusing. To make it more straightforward to describe, I repeated the tests only using the Track Manager to show/hide the tracks. Here are the results:

With the Page set to follow MCP visibility, the surface will only follow the track visibility in the MCP if the mixer is visible on the screen (more specifically, tracks will only hide if the mixer is visible. They can be shown regardless of whether the mixer is visible or not)

With the Page set to follow TCP visibility, I can't find any circumstances where this actually works.

I should point out I'm using OSC for these tests, in case that makes a difference. I'll try it out on MIDI and see if that behaves differently.

[MixMonkey]

Originally Posted by MT4U

I use LeaveSubZone from inside the FX Zone and it takes the X-Touch back to the FX Menu, but this does not happen on the Extender which stays inside the FX Zone. I was thinking maybe LeaveSubZone is not the correct function but can't find the best one.

LeaveSubZone is the correct Action, but I don't believe that it's Broadcast/Received. A workaround could be to put a LeaveSubZone definition in your FX.zon files, so you can return the extender to the FX Menu (probably using a rotary push)

[Geoff Waddington]

Originally Posted by MT4U

Thanks for your reply!

I use LeaveSubZone from inside the FX Zone and it takes the X-Touch back to the FX Menu, but this does not happen on the Extender which stays inside the FX Zone. I was thinking maybe LeaveSubZone is not the correct function but can't find the best one.

Ah, got it.

You are correct, LeaveSubzone is meant only for leaving SubZones. It has unpredictable behaviour when used elsewhere, as you have found out

As MixMonkey says, it does not broadcast.

Try GoSelectedTrackFXMenu, which does broadcast, that should set both surfaces back to SelectedTrackFXMenu.

If not, it is a bug

[Geoff Waddington]

Originally Posted by MixMonkey

I mean I right click on the selected tracks in the TCP and choose "show/hide in MCP"

I agree the terminology is very confusing. To make it more straightforward to describe, I repeated the tests only using the Track Manager to show/hide the tracks. Here are the results:

With the Page set to follow MCP visibility, the surface will only follow the track visibility in the MCP if the mixer is visible on the screen (more specifically, tracks will only hide if the mixer is visible. They can be shown regardless of whether the mixer is visible or not)

With the Page set to follow TCP visibility, I can't find any circumstances where this actually works.

I should point out I'm using OSC for these tests, in case that makes a difference. I'll try it out on MIDI and see if that behaves differently.

Ah, got it now

Ok, so we are back to our original premise -- Pages follow MCP visibility, to the best of their ability

[MixMonkey]

Originally Posted by Geoff Waddington

Ah, got it now

Ok, so we are back to our original premise -- Pages follow MCP visibility, to the best of their ability

Yep, pretty sure that'll be fine Once you know the mixer has to be visible (in some form) it behaves predictably.

[Geoff Waddington]

Originally Posted by MixMonkey

LeaveSubZone is the correct Action, but I don't believe that it's Broadcast/Received. A workaround could be to put a LeaveSubZone definition in your FX.zon files, so you can return the extender to the FX Menu (probably using a rotary push)

Just for clarification, LeaveSubZone isn't really the correct Action to leave FX Zones, although it sorta kinda works

The OP said "until I hit the button with the LeaveSubZone on the X-Touch and it goes back to the Menu but the Extender stays with the FX mapped".

The fact that it goes back to the Menu tells me it is being used to leave an FX Zone, not a SubZone.

[MixMonkey]

Originally Posted by Geoff Waddington

Just for clarification, LeaveSubZone isn't really the correct Action to leave FX Zones, although it sorta kinda works

The OP said "until I hit the button with the LeaveSubZone on the X-Touch and it goes back to the Menu but the Extender stays with the FX mapped".

The fact that it goes back to the Menu tells me it is being used to leave an FX Zone, not a SubZone.

Fair point, although the FXMenu is something of unique case. All the other Associated Zones have a single step to get to their destination. You hit GoSelectedTrackSend and you're at the end of the line, the selected track's sends. With the FXMenu, there's always one more step, to pick an FX from the menu and there may be a further step from there, the SubZone level.

I'm pretty sure you added the LeaveSubZone functionality to this because I whinged that I couldn't return to the FXMenu from an FX without going Home first and then using the GoSelectedTrackFXMenu again.

Interesting that @MT4U has discovered that if you map the SelectedTrackFXMenu to two surfaces you can map two different FX (from the same track) at the same time

What's also possible is to map two different SubZones of the same FX to the surfaces at the same time. This is where the FX SubZone system shows its superiority over using modifiers, where the global nature of modifiers makes doing this impossible.

[Puck]

Originally Posted by Geoff Waddington

Please post your:
CSI.ini
.ost and/or .mst files
your .zon files

That will have to wait until the evening, sorry! (Stupid “real job”)

As far as input, did you run the Action again for the new Page ?

Actually no I just ran it once when i noticed there was a problem.

You could also try replacing GoPage "Page1" and GoPage "Page2" with NextPage for both and see what happens.

I’ll give that a go!

If you look carefully at an old CSI.ini file like the one above in MT4U's post you will see, as Funkybot pointed out, 2 pairs of numbers, one for the ports and one for the channel count and offset.

Just one more reason why it's better to separate the 2 concepts, it was really easy to miss in the old format

Yes I can see clearly now thanks to Funkybot

I did consider the device ID’s were a possibility but then thought it odd that input and output ID’s would be different numbers. I’ve since realized that actually makes sense

[Geoff Waddington]

Originally Posted by MixMonkey

I'm pretty sure you added the LeaveSubZone functionality to this because I whinged that I couldn't return to the FXMenu from an FX without going Home first and then using the GoSelectedTrackFXMenu again.

You should be able to GoSelectedTrackFXMenu directly from an FXSlot without using LeaveSubZone or going Home.

If not, it's a bug

[Funkybot]

Originally Posted by Geoff Waddington

You should be able to GoSelectedTrackFXMenu directly from an FXSlot without using LeaveSubZone or going Home.

If not, it's a bug

I should add this to the wiki. So the "right ways" to unmap FX are either GoSelectedTrackFXMenu/GoTrackFXMenu or GoHome?

EDIT: added to the wiki here...
https://github.com/GeoffAWaddington/...pping-fx-zones

...please let me know if any of that is incorrect or needs changes. I assumed the 're-focusing the same fx' issue still persists in CSI v2 but didn't actually test that out yet.

[MT4U]

Originally Posted by MixMonkey

Interesting that @MT4U has discovered that if you map the SelectedTrackFXMenu to two surfaces you can map two different FX (from the same track) at the same time

What's also possible is to map two different SubZones of the same FX to the surfaces at the same time. This is where the FX SubZone system shows its superiority over using modifiers, where the global nature of modifiers makes doing this impossible.

Actually, what I'm doing is mapping different parameters of the same FX.
Since I have two 8 track surfaces, I reserve my 16th. display to show the FX name on the X-Touch, while the 8 Encoders on the Extender and the first 7 of the X-Touch gimme control over the FX.

Don't really know how to map more than one FX at the same time, though. Sounds interesting, it could be really powerful in some scenarios.

I'm away from the studio right now, but I think the GoSelectedTrackFXMenu by itself didn't go back to the SelectedTrackFXMenu and I ended up doing a GoHome + GoSelectedTrackFXMenu with the subsequent fader shaking.

It was late and I was sleepy, so I will have to check it again an report back with the exact behaviour on both surfaces.

Regarding the MCP following. I can confirm what MixMonkey said about it only synchronizing visible tracks when the MCP is visible, which is really not a deal breaker I believe.

As always, I keep learning from you guys.

[MixMonkey]

Originally Posted by Geoff Waddington

Try GoSelectedTrackFXMenu, which does broadcast, that should set both surfaces back to SelectedTrackFXMenu.

If not, it is a bug

GoSelectedTrackFXMenu only returns the local surface to the FXMenu and from there to Home. Surfaces set to Receive GoSelectedTrackFXMenu follow the Broadcasting surface to the FXMenu and then to GoFXSlot, but don't respond to the Received GoSelectedTrackFXMenu Action to return, either to the FXMenu or to Home.

[chinpou]

Originally Posted by Geoff Waddington

We've had discussions about this.

On the surface (no pun intended ) it looks attractive, but the details, oh the details...

Questions like, should this be two way ?

So, if you hit Shift on the keyboard, does that cause CSI surfaces to be shifted too ?

If you want to modify a mouse action for editing only what hapens to the surface ?

If you modify the surface, what happens to the mouse, does your mouse editing suddenly change ?

What if you want shift on the surface but not Reaper or vice versa ?

Since the overall CSI design philosophy is to reflect the Reaper state, we decided not to do this.

Your approach seems to do a fine job, although perhaps a bit more costly

I was able to achieve mouse button -> midi note -> CSI on macOS 12.4 for free with ControllerMate. This enables me to use my logitech g300 mouse's extra buttons as shift, option, control, and alt modifiers. The extra buttons are laid out like they would be on an MCU.



This allows me to use mouse-click + rotary-turn to do things like item gain adjustment

/ITEM GAIN
    RotaryPush5                       Reaper "41923"    /reset item gain
    Rotary5CW                         Reaper "41925"    /adjust gain 1db
    Rotary5CCW                        Reaper "41924"
    Alt+Rotary5CW                     Reaper "_RS717c8697f22239793e593fa41db5ea359f5b8716" /adjust item gain .1db  
    Alt+Rotary5CCW                    Reaper "_RSad6ba1a0d48b198c4c5aab23b22aca37d1aba975"
    Shift+RotaryPush5                 Reaper "42449"    /reset display peaks
    Shift+Rotary5CW                   Reaper "40155"    /adjust peaks
    Shift+Rotary5CCW                  Reaper "40156"

Or perform detailed item nudging, which I'm finding to be huge for dialog editing.

/NUDGE 1 GRID
    Shift+Rotary7CCW           Reaper "41280"    /adjust left trim 
    Shift+Rotary7CW            Reaper "41276"
    Option+Rotary7CCW          Reaper "41281"    /adjust right trim 
    Option+Rotary7CW           Reaper "41277"      
    Control+Rotary7CCW         Reaper "41291"    /adjust contents 
    Control+Rotary7CW          Reaper "41287"
    Control+Option+Rotary7CCW  Reaper "41282"    /duplicate
    Control+Option+Rotary7CW   Reaper "41278"

Granted, my surface rotary widget definitions have to be a little unorthodox in order to make rotary turns perform actions, rather than adjusting track gain or pan.

Widget Rotary7CCW
	Press b0 16 41
	Press B0 16 42
	Press B0 16 43
	Press B0 16 44
	Press B0 16 45
	Press B0 16 46
	Press B0 16 47
WidgetEnd

Widget Rotary7CW 
	Press b0 16 01
	Press B0 16 02
	Press B0 16 03
	Press B0 16 04
	Press B0 16 05
	Press B0 16 06
	Press B0 16 07
WidgetEnd

I know many CSI programmers use their control surfaces for mixing, to get away from their keyboard and mouse, but with editing, you kinda can't get away from the mouse, unfortunately.

I'd love to see other CSI programmers' setups. Maybe another cockos forum thread is in order? Once I've got mine ironed out, I plan on making a demonstration video.

Thank you all for giving us common Reaper users the power to modify our control surfaces to our liking.

ControllerMate: https://www.orderedbytes.com/controllermate/

[MixMonkey]

I'm afraid I've just discovered a rather nasty bug in the SubZone system.

In an FX.zon containing SubZones, the parameter indexes controlled by the SubZones will always target the plugin in the first slot, rather than the slot containing the plugin you expect to be targeted.

If your SubZone bearing FX is in the first slot, everything works as expected (most of my SubZone bearing FX.zon files are instruments, so always in the first slot) If it's in any other slot, problems...

Apologies for not picking up on this earlier.

[Puck]

Originally Posted by Geoff Waddington

Please post your:
CSI.ini
.ost and/or .mst files
your .zon files

Here they are

NextPage and PrevPage caused the same behavior as GoPage "somePageName"

[Funkybot]

Originally Posted by MixMonkey

I'm afraid I've just discovered a rather nasty bug in the SubZone system.

In an FX.zon containing SubZones, the parameter indexes controlled by the SubZones will always target the plugin in the first slot, rather than the slot containing the plugin you expect to be targeted.

If your SubZone bearing FX is in the first slot, everything works as expected (most of my SubZone bearing FX.zon files are instruments, so always in the first slot) If it's in any other slot, problems...

Apologies for not picking up on this earlier.

Ouch, yeah, that's a bad one. Glad you caught this before 2.0 was declared official! Nice job catching it.

[MixMonkey]

Originally Posted by Funkybot

Ouch, yeah, that's a bad one. Glad you caught this before 2.0 was declared official! Nice job catching it.

As the great Yogi Berra once said:

"it's like deja-vu all over again"

[Geoff Waddington]

Originally Posted by MixMonkey

GoSelectedTrackFXMenu only returns the local surface to the FXMenu and from there to Home.

Are you saying GoSelectedTrackFXMenu returns the local Surface to Home ?

Originally Posted by MixMonkey

Surfaces set to Receive GoSelectedTrackFXMenu follow the Broadcasting surface to the FXMenu and then to GoFXSlot, but don't respond to the Received GoSelectedTrackFXMenu Action to return, either to the FXMenu or to Home.

Ok, that sounds like a bug.

[Geoff Waddington]

Originally Posted by chinpou

I was able to achieve mouse button -> midi note -> CSI on macOS 12.4 for free with ControllerMate. This enables me to use my logitech g300 mouse's extra buttons as shift, option, control, and alt modifiers. The extra buttons are laid out like they would be on an MCU.



This allows me to use mouse-click + rotary-turn to do things like item gain adjustment

/ITEM GAIN
    RotaryPush5                       Reaper "41923"    /reset item gain
    Rotary5CW                         Reaper "41925"    /adjust gain 1db
    Rotary5CCW                        Reaper "41924"
    Alt+Rotary5CW                     Reaper "_RS717c8697f22239793e593fa41db5ea359f5b8716" /adjust item gain .1db  
    Alt+Rotary5CCW                    Reaper "_RSad6ba1a0d48b198c4c5aab23b22aca37d1aba975"
    Shift+RotaryPush5                 Reaper "42449"    /reset display peaks
    Shift+Rotary5CW                   Reaper "40155"    /adjust peaks
    Shift+Rotary5CCW                  Reaper "40156"

Or perform detailed item nudging, which I'm finding to be huge for dialog editing.

/NUDGE 1 GRID
    Shift+Rotary7CCW           Reaper "41280"    /adjust left trim 
    Shift+Rotary7CW            Reaper "41276"
    Option+Rotary7CCW          Reaper "41281"    /adjust right trim 
    Option+Rotary7CW           Reaper "41277"      
    Control+Rotary7CCW         Reaper "41291"    /adjust contents 
    Control+Rotary7CW          Reaper "41287"
    Control+Option+Rotary7CCW  Reaper "41282"    /duplicate
    Control+Option+Rotary7CW   Reaper "41278"

Granted, my surface rotary widget definitions have to be a little unorthodox in order to make rotary turns perform actions, rather than adjusting track gain or pan.

Widget Rotary7CCW
	Press b0 16 41
	Press B0 16 42
	Press B0 16 43
	Press B0 16 44
	Press B0 16 45
	Press B0 16 46
	Press B0 16 47
WidgetEnd

Widget Rotary7CW 
	Press b0 16 01
	Press B0 16 02
	Press B0 16 03
	Press B0 16 04
	Press B0 16 05
	Press B0 16 06
	Press B0 16 07
WidgetEnd

I know many CSI programmers use their control surfaces for mixing, to get away from their keyboard and mouse, but with editing, you kinda can't get away from the mouse, unfortunately.

I'd love to see other CSI programmers' setups. Maybe another cockos forum thread is in order? Once I've got mine ironed out, I plan on making a demonstration video.

Thank you all for giving us common Reaper users the power to modify our control surfaces to our liking.

ControllerMate: https://www.orderedbytes.com/controllermate/

Cool, very creative !

[Geoff Waddington]

Originally Posted by MixMonkey

I'm afraid I've just discovered a rather nasty bug in the SubZone system.

In an FX.zon containing SubZones, the parameter indexes controlled by the SubZones will always target the plugin in the first slot, rather than the slot containing the plugin you expect to be targeted.

If your SubZone bearing FX is in the first slot, everything works as expected (most of my SubZone bearing FX.zon files are instruments, so always in the first slot) If it's in any other slot, problems...

Apologies for not picking up on this earlier.

Thanks, will look into it, as you said, been here before, it's a Yogi thing

[Geoff Waddington]

Originally Posted by Puck

Here they are

NextPage and PrevPage caused the same behavior as GoPage "somePageName"

There is no PrevPage, where did you see that, I need to correct it if it is out there.

I posted "You could also try replacing GoPage "Page1" and GoPage "Page2" with NextPage for both and see what happens."

Try that, NextPage wraps around when it reaches the end.

BOTH Pages should have NextPage.

There is no PrevPage.

Also noticed you have the buttons mapped to the same Action in both Pages.

Suggest maybe mapping them to Rewind and Fast Forward on one Page to ensure things are really changing.

Try that and see what happens.

[MixMonkey]

Originally Posted by Geoff Waddington

Are you saying GoSelectedTrackFXMenu returns the local Surface to Home ?

Yes, if the FXMenu is showing. From there, a further press goes Home. Works nicely, just doesn't broadcast (or maybe get received)

[MixMonkey]

Originally Posted by Geoff Waddington

Thanks, will look into it, as you said, been here before, it's a Yogi thing

"When you arrive at a fork in the road, take it"

[Geoff Waddington]

Originally Posted by MixMonkey

Yes, if the FXMenu is showing. From there, a further press goes Home. Works nicely, just doesn't broadcast (or maybe get received)

Oh, so the GoSelectedTrackFXMenu returns the local Surface to TrackFXMenu ?

That sounds more like it

And then you can press Home to return the local and remote Surfaces to Home ?

[Geoff Waddington]

Originally Posted by MixMonkey

"When you arrive at a fork in the road, take it"

My fav, and I think this one refers to a place the players used to hang, but all the fans caught on, so there was no solitude.

"The place is so crowded no one goes there anymore"

[Puck]

Originally Posted by Geoff Waddington

There is no PrevPage, where did you see that, I need to correct it if it is out there.

I posted "You could also try replacing GoPage "Page1" and GoPage "Page2" with NextPage for both and see what happens."

Try that, NextPage wraps around when it reaches the end.

BOTH Pages should have NextPage.

There is no PrevPage.

Also noticed you have the buttons mapped to the same Action in both Pages.

Suggest maybe mapping them to Rewind and Fast Forward on one Page to ensure things are really changing.

Try that and see what happens.

It appears it’s something I made up. (That’s hilarious)

I can tell things aren’t changing because of the “PageNameDisplay” (that actually exists, I checked! )

But I shall do as you say with the correct action this time and change everything around to check. Will report back in an hour or so.

It’s funny how the mind works sometimes. Well, mine anyways.

[Geoff Waddington]

Originally Posted by Puck

It appears it’s something I made up. (That’s hilarious)

It’s funny how the mind works sometimes. Well, mine anyways.

Mine too, trust me

Originally Posted by Puck

I can tell things aren’t changing because of the “PageNameDisplay” (that actually exists, I checked! )

Well that tests Reaper->Surface.

The other would test Surface->Reaper.

[Geoff Waddington]

New build is up.

CSI Exp.zip

Possible fix for SubZone slot index.

Possible fix for Receive AssociatedZone change.

[MixMonkey]

Originally Posted by Geoff Waddington

Oh, so the GoSelectedTrackFXMenu returns the local Surface to TrackFXMenu ?

That sounds more like it

And then you can press Home to return the local and remote Surfaces to Home ?

No, pressing the same button (GoSelectedTrackFXMenu) again, returns just the local surface Home (you added this, complete with indicator, because it's more natural to press the same button again to leave the sends/receive/FX)

You can, of course, press Home, but these days that's the nuclear option (such is CSI's state of refinement) complete with seismic fader twitch