Control Surface Integration (CSI) Technical Feature Discussion

[Geoff Waddington]

New build is up.

Press is no longer

Added MasterTrackNavigator.

Use MasterTrackNavigator in your Master Track Zone -- which now must be an included Zone just like Channel(s) because of the separate navigator.

Removed the Master Track specialty Actions -- MasterTrackVolume, etc.

Modifier latching much improved.

RGB support for the Novation Launchpad.

Mac only in this build -- Edit Launchpad colour in realtime in Learn Mode Window.

[MixMonkey]

Originally Posted by Geoff Waddington

Right now it's hardwired, but yes, acceleration is on the roadmap -- has been for about 2 years or so

No, not acceleration, the opposite, the granularity of the adjustment, how finely a parameter can be adjusted.

Do we have any control over this or is it in the hands of the plugin devs?

[Geoff Waddington]

Originally Posted by MixMonkey

No, not acceleration, the opposite, the granularity of the adjustment, how finely a parameter can be adjusted.

Do we have any control over this or is it in the hands of the plugin devs?

Yeah, that's still acceleration

When you turn slowly it's very fine -- so if you continue to turn very slowly it's still very fine.

If you speed up the jump size increases.

Right now it's hardwired to a constant small value, but acceleration will do what you want when we actually build it

[MixMonkey]

Originally Posted by Geoff Waddington

Yeah, that's still acceleration

When you turn slowly it's very fine -- so if you continue to turn very slowly it's still very fine.

If you speed up the jump size increases.

Right now it's hardwired to a constant small value, but acceleration will do what you want when we actually build it

Ah, I see Could it be hardwired to a smaller value? One "tick" is too big at the moment.

My problem is always lack of fine control, not too many turns to cover the range.

If it could be set in the Zone definition by parameter, that would be awesome

[Geoff Waddington]

Originally Posted by MixMonkey

Ah, I see Could it be hardwired to a smaller value? One "tick" is too big at the moment.

My problem is always lack of fine control, not too many turns to cover the range.

If it could be set in the Zone definition by parameter, that would be awesome

Cool, I cut it in half for the next build, we'll try that.

[MixMonkey]

Originally Posted by Geoff Waddington

Cool, I cut it in half for the next build, we'll try that.

Thanks

[Geoff Waddington]

New build is up.

Encoder adjust amount halved.

On Windows -- Realtime adjustment of Launchpad RGB colours in Learn Mode Window MIGHT work

On Mac -- RGB adjust operational, barely

[MixMonkey]

Originally Posted by Geoff Waddington

New build is up.

Encoder adjust amount halved.

On Windows -- Realtime adjustment of Launchpad RGB colours in Learn Mode Window MIGHT work

On Mac -- RGB adjust operational, barely

New build working nicely

Added Zone MasterTrack to MCU.zon (and added it to IncludedZones):

  
        Zone MasterTrack
		MasterTrackNavigator
		MasterFader TrackVolume
		TrackTouch+MasterFader TrackVolume
		MasterFaderTouch TrackTouch
	ZoneEnd

Touch control on MasterFader doesn't seem to work, but not sure if it ever did

Modifier latching is much better, you now have to do a really quick press to get it to latch, much harder to latch it accidentally.

Encoder resolution improved. On a Send, the minimum adjustment is now ~0.4dB, down from ~0.75dB. On ReaEQ gain minadj is ~0.3dB, down from 0.5dB.

The only side effect I've noticed is I have to turn Pan above a certain speed to shift it off <C>, almost like there was a built in threshold. When Pan is on any other value it behaves normally (minadj~2)

I'd be all for dividing the value you have now by 3 and see what happens. Hopefully, it should give ~0.1 dB minadj on all gain controls

[Geoff Waddington]

Originally Posted by MixMonkey

New build working nicely

Added Zone MasterTrack to MCU.zon (and added it to IncludedZones):

  
        Zone MasterTrack
		MasterTrackNavigator
		MasterFader|  TrackVolume
		TrackTouch+MasterFader|  TrackVolume
		MasterFaderTouch|  TrackTouch
	ZoneEnd

Touch control on MasterFader doesn't seem to work, but not sure if it ever did

Are you using 90 70 7f 90 70 00 for the Master Touch ?

I would remove those | characters, not sure why you have them, seems confusing, as there is no number replacement here, unlike Channels.

Originally Posted by MixMonkey

Modifier latching is much better, you now have to do a really quick press to get it to latch, much harder to latch it accidentally.

Cool, yeah, methinks it's actually usable now

Originally Posted by MixMonkey

Encoder resolution improved. On a Send, the minimum adjustment is now ~0.4dB, down from ~0.75dB. On ReaEQ gain minadj is ~0.3dB, down from 0.5dB.

The only side effect I've noticed is I have to turn Pan above a certain speed to shift it off <C>, almost like there was a built in threshold. When Pan is on any other value it behaves normally (minadj~2)

I'd be all for dividing the value you have now by 3 and see what happens. Hopefully, it should give ~0.1 dB minadj on all gain controls

Ok, see your 3 and and raise it by one to 4

4 x 2 = 8.

The new smallest movement will be 1/8 what it was originally.

We're really looking fo a good value here for acceleration minimum step -- for input to the acceleration design.

Everyone please test this in next build and see if it is too slow to get from min to max.

[MixMonkey]

Originally Posted by Geoff Waddington

Are you using 90 70 7f 90 70 00 for the Master Touch ?

Yep (although it's missing from the default MCU.mst)

I would remove those | characters, not sure why you have them, seems confusing, as there is no number replacement here, unlike Channels.

My bad, lazy cut and paste (I'll delete them from the post). Have removed them but still no joy with Touch.

Ok, see your 3 and and raise it by one to 4

4 x 2 = 8.

The new smallest movement will be 1/8 what it was originally.

We're really looking fo a good value here for acceleration minimum step -- for input to the acceleration design.

Everyone please test this in next build and see if it is too slow to get from min to max.

Sounds good I'm quite happy to do a bit of knob turning in return for finer control.

[poetnprophet]

Originally Posted by Geoff Waddington

New build is up.

Encoder adjust amount halved.

On Windows -- Realtime adjustment of Launchpad RGB colours in Learn Mode Window MIGHT work

On Mac -- RGB adjust operational, barely

Hey Geoff, I'd like to try this today/tomorrow.

Can you describe what you meant about Press being removed/how to modify, and exactly how to setup the master track nav? I see MixMonkey's zone def so I can use that, but not sure exactly how to include the zone or anything else. (I typically just use existing code structures and just modify the names or values....yes even after all this time I still don't get much of the structure on my own)

[mschnell]

A friend of mine (due to my recommendation) will get a Native Instruments Komplete Kontrol A49 for Christmas.

Are there any experiences with using same with CSI ?

-Michael

[Geoff Waddington]

Originally Posted by MixMonkey

Yep (although it's missing from the default MCU.mst)

Yup, will include

OK, sounds like a bug.

[Geoff Waddington]

Originally Posted by poetnprophet

Hey Geoff, I'd like to try this today/tomorrow.

Can you describe what you meant about Press being removed/how to modify, and exactly how to setup the master track nav? I see MixMonkey's zone def so I can use that, but not sure exactly how to include the zone or anything else. (I typically just use existing code structures and just modify the names or values....yes even after all this time I still don't get much of the structure on my own)

If you don't have any Press+SomeButton(s) in any of your Zones, it doesn't affect you.

If you find any, just remove the "Press+".

For Master Channel In your Home Zone

Zone Home
        IncludedZones
                Buttons
                Channel|1-8
                MasterChannel
        IncludedZonesEnd
ZoneEnd

Zone MasterChannel
	MasterTrackNavigator
	MasterFader TrackVolume
	MasterFaderTouch TrackTouch
        ...
ZoneEnd

Also, it's a great idea for everyone to watch your video, and also dig into MalcolmG's wiki, he explains things very well.

[poetnprophet]

Originally Posted by Geoff Waddington

If you don't have any Press+SomeButton(s) in any of your Zones, it doesn't affect you.

If you find any, just remove the "Press+".

For Master Channel In your Home Zone

Zone Home
        IncludedZones
                Buttons
                Channel|1-8
                MasterChannel
        IncludedZonesEnd
ZoneEnd

Zone MasterChannel
	MasterTrackNavigator
	MasterFader TrackVolume
	MasterFaderTouch TrackTouch
        ...
ZoneEnd

Also, it's a great idea for everyone to watch your video, and also dig into MalcolmG's wiki, he explains things very well.

Thank you!

And, I didn't realize that I had my capture settings in low rez! Ahhhh! I'll have to redo that video with higher quality at some point...

[AbbeH]

Originally Posted by CraigGE

Hi AbbeH, I'm really glad you found my original files useful. I know Geoff has already replied to you but I thought you might be interested in a copy of my latest edition mst and zon files. See my signature for the download from the stash - they do work for me but are still a work-in-progress.

Hope this helps.

I just want to say thank you! I had given up all hope on the x-touch mini, but today I gave it another try. At first no success, but after reinstalling a new reaper, doing a factory reset, and reinstalling CSI it finally just worked.

Now I just have to figure out how to change the zon-file to my liking.

[poetnprophet]

confirmed the new build is working with the new master navigator.

Also, I really like the way the rotaries behave now. But like Mix said, when adjusting pan it takes a lot to get past center. Otherwise its really nice!

[AbbeH]

Since I have a non motorized fader that I would like to use for trackvolume on a selected track, I find it annoying that the volume will jump to the setting of the fader. Is there an option for the fader to be soft takeover like there is in reaper if you just map the fader to "set volume on selected tracks" in the actions menu?

[Geoff Waddington]

Originally Posted by poetnprophet

Thank you!

And, I didn't realize that I had my capture settings in low rez! Ahhhh! I'll have to redo that video with higher quality at some point...

Cool, before you redo it, maybe check out MalcolmG's wiki -- I suspect MalcomG is actually a pro technical writer, his explanations are excellent, might answer some questions you had in the video

Also, being nit-picky I would say maybe shorten the .mst description way down, we will probably have a lot available out of the gate and you very rarely change them.

Anyway, all the "action" is in the Zone files:
Actions
Navigators
IncludedZones
FXZones
Modifers

Don't get me wrong, great job, I'm just being the ultra bitchy director

[Geoff Waddington]

Originally Posted by poetnprophet

Also, I really like the way the rotaries behave now. But like Mix said, when adjusting pan it takes a lot to get past center. Otherwise its really nice!

Yeah, next build will be 4 times as sensitive, we're trying to find a good bottom for acceleration.

[Geoff Waddington]

Originally Posted by AbbeH

Since I have a non motorized fader that I would like to use for trackvolume on a selected track, I find it annoying that the volume will jump to the setting of the fader. Is there an option for the fader to be soft takeover like there is in reaper if you just map the fader to "set volume on selected tracks" in the actions menu?

Thanks for reminding me -- will add a "Soft Takeover" checkbox to the Surface config panel.

[Krankykarl]

Will this ever be available in a plug and play sort of format for those of us that don't understand a lot of this technical stuff?
Thanks,Dan

[Geoff Waddington]

Originally Posted by Krankykarl

Will this ever be available in a plug and play sort of format for those of us that don't understand a lot of this technical stuff?
Thanks,Dan

Yes, when we go beta there will be a set of "usual suspects" plug and play available -- more will be added over time ad infinitum -- at least that's the plan

[Krankykarl]

Originally Posted by Geoff Waddington

Yes, when we go beta there will be a set of "usual suspects" plug and play available -- more will be added over time ad infinitum -- at least that's the plan

Thanks Geoff. I spent years on the VS Planet and gained quite an appreciation for the people with the knowledge and the hard work that you guys do to make this all possible.
Dan

[mschnell]

Originally Posted by Krankykarl

Will this ever be available in a plug and play sort of format for those of us that don't understand a lot of this technical stuff?

Obviously only for those who intend to use a (sort of) "standard" device and a (sort of) "standard" workflow. Enhanced demand needs enhanced effort.

-Michael

[MalcolmG]

Originally Posted by Geoff Waddington

Cool, before you redo it, maybe check out MalcolmG's wiki -- I suspect MalcomG is actually a pro technical writer, his explanations are excellent, might answer some questions you had in the video

Haha, definitely not. I just know that in a few weeks when I go back to do something, I will have forgotten, so I'd better spell it out clearly for future me

[Funkybot]

Originally Posted by Geoff Waddington

Yes, when we go beta there will be a set of "usual suspects" plug and play available -- more will be added over time ad infinitum -- at least that's the plan

I'm hoping for a front-end to create the .mst files. For example, something where I:

1. Create a new device, name it
2. Click add to add a parameter, then
3. Move it to learn it, and
4. Maybe right-click the new parameter to designate it as Rotary/Fader, button, etc.

Basically, very similar to setting up a Control Link device in Studio One. Then once that's done, a similar front-end for mapping these things to commands/functions in Reaper from an available list of controls. There's such a wide range of MIDI devices in the world that I think it would make much more sense to concentrate efforts on making it easier for end-users to create the necessary files from a front-end with some kind of Learn functionality so they're never directly editing a script. A GUI-based Learn system would also make it easier to crowd-source more devices, as the barrier to creation would be much smaller.

As of now, my honest opinion is that this is too complex for "ye average end user." I'm pretty used to MIDI and not afraid to dive and learn something new, but after a few hours, just couldn't figure this out and wasn't even sure where to begin troubleshooting. I could be very close or miles away, but I already invested a few hours in trying and don't want spend additional time on something I may not figure out. So when I request things like a front-end, or documentation with practical step-by-step instructions, my requests are purely selfish. I very much like the idea of this and want it to be successful and easy enough for me to use. Anyway, thanks for all your work Geoff. Your Eucon adapter is a total lifesaver, and I appreciate all the time and effort you've invested into control surfaces in Reaper.

[MixMonkey]

Originally Posted by Funkybot

I'm hoping for a front-end to create the .mst files.

What surface are you trying to use?

[Geoff Waddington]

Originally Posted by Funkybot

I'm hoping for a front-end to create the .mst files. For example, something where I:

1. Create a new device, name it
2. Click add to add a parameter, then
3. Move it to learn it, and
4. Maybe right-click the new parameter to designate it as Rotary/Fader, button, etc.

Basically, very similar to setting up a Control Link device in Studio One. Then once that's done, a similar front-end for mapping these things to commands/functions in Reaper from an available list of controls. There's such a wide range of MIDI devices in the world that I think it would make much more sense to concentrate efforts on making it easier for end-users to create the necessary files from a front-end with some kind of Learn functionality so they're never directly editing a script. A GUI-based Learn system would also make it easier to crowd-source more devices, as the barrier to creation would be much smaller.

Well the .mst files are very easy to make if you have a spec, or you can do it the hard way by pressing buttons -- but who wants to ?

We already have a few devices .mst files -- more to come.

There's another reason - naming.

As you know you are free to call your widgets whatever you like -- but -- that has implications -- you can successfully use only Zone files that follow your naming convention.

Because of that alone, I'd like to keep the contributor list as small as possible, and would like to vet all .mst/.ost files here before posting.

On to Zones -- yes -- the Learn Mode Window is coming along, you can now do things in realtime -- it's still very young and will improve with time

I totally get where you are coming from on this.

[Funkybot]

Originally Posted by Geoff Waddington

There's another reason - naming.

As you know you are free to call your widgets whatever you like -- but -- that has implications -- you can successfully use only Zone files that follow your naming convention.

Hi Geoff, that is actually something else I think a front-end for .mst creation can help with. You can force a best-practice naming convention for widgets on the users and get more consistency from user-created .mst files.

Let's imagine a gui-based "Create a Device" screen existed and worked similar to below. So I'm a newbie, setting up a new CSI, and I don't see my device as an .mst file, but there's a "create a device" option/button, which I click...

1. This takes me to the "Create a Device" screen - I've got a blank screen with two buttons, Learn, and Cancel (maybe a greyed out Save button)

2. I hit the Learn button

3. I move a parameter in my hardware

Result: a graphical representation of the learned parameter now appears on screen as a rotary or fader by default. There's a "Widget Name" at the top. The current value is displayed at the bottom. The save button becomes active.

4. I can right click the new Widget on the GUI to change the type of Widget. Example: This is a button, or this is a rotary/fader, this is a jog-wheel, etc.

5. I can click on the name and you give me a couple of naming options based on a set list of conventions (Fader 1, Left or Right Fader 1, Top or Bottom Fader 1, Middle Fader 1, Top-Right or Top-Left Fader 1, etc.).

6. The numbers used in the names would automatically increment each time that type of widget was added.

7. If there were different Press/Release options for a button, I could right-click the visual representation of that widget and set that up here too.

8. I can go on happily/quickly learning parameters/creating widgets.

9. I click save when I'm done - enter the Manufacturer name, enter the product name, and done.

10. Now, once done, I've got a nice clean .mst built behind the scenes adhering to a best practice naming convention. Something any dumb end-user (talking about myself here) could do without needing to so much as crack open a manual. The important thing is, if it's easy to create, it should increase the likelihood of users mapping and sharing more devices.

Anyway, that's been my idea as to how this could be implemented. Studio One's "Control Link" setup works very similar to this and is very intuitive (but not as fully featured or flexible as what you're trying to do here).

[Funkybot]

I should also note: I'm no developer and what I'm describing could very well be a huge work effort. I have no idea. Totally get if that type of thing just has to remain out of scope.

[Freex]

Originally Posted by Funkybot

I should also note: I'm no developer and what I'm describing could very well be a huge work effort. I have no idea. Totally get if that type of thing just has to remain out of scope.

The only thing about a GUI for mst file creation, is it would be ALOT of effort, for something you would use ONCE.

I was daunting to say the least when I tried to get my head around CSI, but really the biggest block, is actually trying it. you then realise that it's all in plain text, not fancy code, Geoff has done an amazing job of making it (pretty much) idiot proof, as I can testify.

Just get it installed, active the show midi IO (really you only need IN) and take note of what some of your control surfaces main controls put out.

You can then look at the MST files that come with CSI and see if any match, moving forward from there it's as easy as loading the closest match finding what works, noting what doesn't and editing those to work.

By the time you've tried all that you'll be hooked and will end up making a template specific to your controller, once you do that, let Geoff know, and he'll add it to CSI (out of the box).

Heck, there might even be someone else working on the mst right now.

[Funkybot]

Originally Posted by Freex

The only thing about a GUI for mst file creation, is it would be ALOT of effort, for something you would use ONCE.

I was daunting to say the least when I tried to get my head around CSI, but really the biggest block, is actually trying it. you then realise that it's all in plain text, not fancy code, Geoff has done an amazing job of making it (pretty much) idiot proof, as I can testify.

Just get it installed, active the show midi IO (really you only need IN) and take note of what some of your control surfaces main controls put out.

You can then look at the MST files that come with CSI and see if any match, moving forward from there it's as easy as loading the closest match finding what works, noting what doesn't and editing those to work.

By the time you've tried all that you'll be hooked and will end up making a template specific to your controller, once you do that, let Geoff know, and he'll add it to CSI (out of the box).

Heck, there might even be someone else working on the mst right now.

That's exactly what I attempted but never got anything working. So I don't know if the error was with the .mst, the pages/zones, the MIDI setup in Reaper itself, or elsewhere.

Anyway, not a big deal. I'll patiently wait until this is further along.

[Freex]

Originally Posted by Funkybot

That's exactly what I attempted but never got anything working. So I don't know if the error was with the .mst, the pages/zones, the MIDI setup in Reaper itself, or elsewhere.

Anyway, not a big deal. I'll patiently wait until this is further along.

Did you get anything showing on the midi In in CSI?
That's a first step check that you have your IOs correct, well your Ins Atleast.
You need to make sure youdont have your device setup in reaper as a midi device. CSI does all that for you

[Funkybot]

Originally Posted by Freex

Did you get anything showing on the midi In in CSI?

Where and how would I see that? I don't see anything in the CSI setup that even looks like it would show me if MIDI was coming in. Note: I'm on Windows.

Originally Posted by Freex

You need to make sure youdont have your device setup in reaper as a midi device. CSI does all that for you

That's counter-intuitive but I did try it both ways with no success. This is also where step-by-stop documentation that assumes no prior knowledge will be key for future success. I'd think "no way Reaper can see the devices unless they're enabled for Control in MIDI Devices."

Here's what I did:

1. Tried to create an .mst file for my Remote Zero SL, which is just a knob/fader box with some transport buttons. Very simple. Just mapped out the parameters. Think it should work. Attached file.

2. Tried to manually create a .zon file. This process seemed way less clear to me. Probably where I'm screwing up. Attached file.

3. Went into Reaper's Preferences > Control Surfaces/OSC

4. Added a CSI

5. Added a "Home" page, set to Mixer Control. Double-clicked it to make it active.

6. Clicked Add MIDI - added a device, selected the .mst and zone files, selected the MIDI input and output ports

7. Clicked OK

8. Opened a project

Result: nothing happened

9. Restarted Reaper

Result: nothing happens

10. Tried the same with those MIDI Devices disabled in Reaper's preferences. No difference.


If anyone feels like digging into the files to see if anything obvious sticks out, they're more than welcome to. I'm at a loss at this point. It's probably the Zone file that's hosed if I had to guess.

NOTE: I changed the file extensions to get them to attach to the board. They were originally Remote Zero SL.mst and Remote Zero SL.zon respectively.

And thanks in advance to everyone for the attempts at help.

[Geoff Waddington]

Originally Posted by Funkybot

Where and how would I see that? I don't see anything in the CSI setup that even looks like it would show me if MIDI was coming in. Note: I'm on Windows.

For now, just run the Reaper Action No-op -- that launches the Learn Mode window -- lower left is monitoring.

Originally Posted by Funkybot

That's counter-intuitive but I did try it both ways with no success. This is also where step-by-stop documentation that assumes no prior knowledge will be key for future success. I'd think "no way Reaper can see the devices unless they're enabled for Control in MIDI Devices."

Yeah, that's a Reaper thing, not specific to CSI.

Originally Posted by Funkybot

Here's what I did:

1. Tried to create an .mst file for my Remote Zero SL, which is just a knob/fader box with some transport buttons. Very simple. Just mapped out the parameters. Think it should work. Attached file.

2. Tried to manually create a .zon file. This process seemed way less clear to me. Probably where I'm screwing up. Attached file.

3. Went into Reaper's Preferences > Control Surfaces/OSC

4. Added a CSI

5. Added a "Home" page, set to Mixer Control. Double-clicked it to make it active.

Don't know what you mean here, please post the contents of your CSI.ini.

Originally Posted by Funkybot

6. Clicked Add MIDI - added a device, selected the .mst and zone files, selected the MIDI input and output ports

The .mst file is a file, but you specify a Zone folder not a file -- all .zon files in that folder and any sub-folders will be loaded by CSI.

Originally Posted by Funkybot

7. Clicked OK

8. Opened a project

Result: nothing happened

9. Restarted Reaper

Result: nothing happens

10. Tried the same with those MIDI Devices disabled in Reaper's preferences. No difference.


If anyone feels like digging into the files to see if anything obvious sticks out, they're more than welcome to. I'm at a loss at this point. It's probably the Zone file that's hosed if I had to guess.

NOTE: I changed the file extensions to get them to attach to the board. They were originally Remote Zero SL.mst and Remote Zero SL.zon respectively.

And thanks in advance to everyone for the attempts at help.

The .mst and .zon files look good at first glance, I suspect a Page definition problem or a Zone folder issue -- the CSI.ini contents will tell.

[WaveTrans]

Hi, after following the blog for a while, I got back to testing and
managed to implement Masterfader control in MCU.mst/.zon files, which quite puzzled me a couple of weeks ago. Was quite straight forward with the post above. Then I failed to achieve rotary control over master pan; the rotary midi code sent is master button independent and does not work on master pan.

Since the Icon platform nano is a single fader controller, I also tried to reduce the multiple channels adressed in the MCU files.
However, when I get rid of the | signs and numbers, the fader control of tracks and pan do not work anymore.
I only get full control over master- and track-faders with the adapted MCU.mst and MCU.zon file including the multiple channels etc.

Could you please help me, to answer these questions, so I can come to the more difficult stuff like Sends, FXmenues and Plugin mapping

[Funkybot]

Originally Posted by Geoff Waddington

For now, just run the Reaper Action No-op -- that launches the Learn Mode window -- lower left is monitoring.



Yeah, that's a Reaper thing, not specific to CSI.



Don't know what you mean here, please post the contents of your CSI.ini.




The .mst file is a file, but you specify a Zone folder not a file -- all .zon files in that folder and any sub-folders will be loaded by CSI.




The .mst and .zon files look good at first glance, I suspect a Page definition problem or a Zone folder issue -- the CSI.ini contents will tell.

Here's what the CSI.ini shows (I've tried different settings):

Page "Home" FollowMCP SynchPages UseScrollLink NoTrackColoring 0 0 0
MidiSurface "RMZL" 0 1 "Remote Zero SL.mst" "Remote Zero SL" UseZoneLink AutoMapSends AutoMapFX AutoMapFXMenu AutoMapFocusedFX

[Geoff Waddington]

First off, did you manage to get the Learn Mode window to launch ?

Originally Posted by Funkybot

Here's what the CSI.ini shows (I've tried different settings):

Page "Home" FollowMCP SynchPages UseScrollLink NoTrackColoring 0 0 0
MidiSurface "RMZL" 0 1 "Remote Zero SL.mst" "Remote Zero SL" UseZoneLink AutoMapSends AutoMapFX AutoMapFXMenu AutoMapFocusedFX

Did you use the config panel to generate this ?

Was the folder "Remote Zero SL" visible in the dropdown ?

The reason I'm asking is -- we are just now adding in support for spaces in filenames and folders -- not sure how the OSs will handle it -- maybe replace the spaces with underscores in the folder name and CSI.ini.

Is your .zon file in the "Remote Zero SL" folder ?

Let me know what happens.

[Funkybot]

Geoff, yes, the files were visible in the dropdown.

Now that I removed the spaces from the file names and the folder name, stuff is now happening. Namely: transport controls work.

And yes, now I can get the no-op action to run. It did nothing before.

I can also see things like Fader and Rotary movements in the Learn window, but I haven't figured out how to actually get the faders to do anything yet. But this is definitely progress.

EDIT: I tried figuring out how to add Fader1 from the left to the Zone to control Channel 1 (things look off) and when I clicked Fader1 then Add to Zone, it crashed Reaper.