CSI v3 - Now Includes Auto-FX Mapping -- Use this for Setup Help, Bug Reports, etc.

[Funkybot]

Originally Posted by flipotto

Using BCR2000.
Add a new synth on a track click on vst in touchosc (computer)
Dialog for "learn" comes up 3 times.
csi.ini

Version 3.0

OSCSurface "iPad" 8002 9002 192.168.0.37
MidiSurface "BCR2000" 40 38 
OSCSurface "Computer" 8003 9003 127.0.0.1

Page "HomePage" FollowTCP UseScrollLink UseScrollSynch
	"iPad" 8 0 "iPad_BCR2000.ost" "BCR2000_iPad" "FXZones_BCR2000" 
	"BCR2000" 8 0 "BCR2000.mst" "BCR2000_Physical" "FXZones_BCR2000" 
	"Computer" 8 0 "iPad_BCR2000.ost" "BCR2000_Computer" "FXZones_BCR2000" 

	Broadcaster "BCR2000"
		Listener "Computer" "GoHome Sends Receives "
		Listener "BCR2000" "GoHome Sends Receives Learn FXMenu "

	Broadcaster "Computer"
		Listener "iPad" "GoHome Sends Receives FXMenu "
		Listener "BCR2000" "GoHome Sends Receives FXMenu "
		Listener "Computer" "GoHome Sends Receives FXMenu "

It didn't used to do that, before I messed with advanced settings broadcast listener.
I screwed something up, alas.

It'll come up once for each surface. You pick which one you're going to do the learning on. But pick a surface with displays for that.

So that's the expected behavior.

[Funkybot]

Originally Posted by georges

Still nothing. I'm sure it's me. Hopefully the ZIP file uploaded this time. I included a screenshot showing the two devices talking to reaper.

You're correct, I want to treat it as a dumb knob box and avoid using the MP Host Plugin.

Georges, looking at this...



...that looks more like a Fader7Bit message than an endless rotary. We've got values going up and up until we hit a bunch of repeating 7f messages. Does anyone else looking at this disagree? Is there any device configuration on the controller itself to change the knob behavior?

If you turn the knob fully counter-clockwise, are the values 00? And fully clockwise, does it start repeating 7f values? If yes, might need Fader7Bit. I might create an alternative .mst that looks like this just for testing.

MP_MIDI_FADER.mst

Widget Rotary1
     Fader7Bit b0 07 7f
     FB_Fader7Bit b0 07 7f
WidgetEnd

...just the one widget so far (or go crazy and do a Find and Replace and change all). Then try with FocusedFX mapping enabled and see if it works. My goal would be to see if I could get focused FX working with just a single knob for now. Once you get one knob talking, the others just need to follow the same pattern.

Hope this is helpful. It's much easier when the device is in hand or when the .mst grunt work was done by someone else.

I'd also reconsider the naming convention. Maybe not though. If it were me, I'd probably label them something like:

TopRotary1-8
RightRotary1-8
LeftRotary1-8
BottomRotary1-8

or even

RotaryA1-A8
RotaryB1-B8
RotaryC1-C8
RotaryD1-D8

Just in case you ever wanted to take it on a flight or something and have an alternate config where like the bottom row was track volume and the top row was track pan, and right and left were sends/receives. If they follows an 4x8 naming convention, you could do that. But if you're only going to use 32 rotaries for exclusive FX control, then it's not necessary. Just something to think about and make an informed decision on.

[Funkybot]

CSI Support Files have the following updates:

1. Added FaderportClassic files (FreeX, I renamed them to just FaderportClassic and used the CSI native action for toggling input monitoring)

2. Updated BCR2000 files

3. Added BCR2000 iPad files and TouchOSC Layout (note: didn't include the desktop files - let me know if that's an issue for anyone)

Geoff, you're good to release the FaderPortFader addition whenever you're ready. Might as well include the ToggleRestrictTextLength one too since that seems to work.

If anyone else has files for other surfaces they want added, let me know.

[Geoff Waddington]

Version 3.2.1 is now available.

It includes Faderport Classic support and ToggleRestrictTextLength for OSC.

Link is in blue below.

[Funkybot]

And the wiki is now up to 3.2.1.

Updates to the Change Log page, a small one for the ToggleRestrictTextLength action, as well as adding the Faderport Fader widget to the Message Generators and Feedback Processors pages.

[Geoff Waddington]

Originally Posted by Funkybot

And the wiki is now up to 3.2.1.

Updates to the Change Log page, a small one for the ToggleRestrictTextLength action, as well as adding the Faderport Fader widget to the Message Generators and Feedback Processors pages.

Great work as always, thanks !!

[georges]

Originally Posted by Funkybot

Georges, looking at this...



...that looks more like a Fader7Bit message than an endless rotary. We've got values going up and up until we hit a bunch of repeating 7f messages. Does anyone else looking at this disagree? Is there any device configuration on the controller itself to change the knob behavior?

If you turn the knob fully counter-clockwise, are the values 00? And fully clockwise, does it start repeating 7f values? If yes, might need Fader7Bit. I might create an alternative .mst that looks like this just for testing.

MP_MIDI_FADER.mst

Widget Rotary1
     Fader7Bit b0 07 7f
     FB_Fader7Bit b0 07 7f
WidgetEnd

...just the one widget so far (or go crazy and do a Find and Replace and change all). Then try with FocusedFX mapping enabled and see if it works. My goal would be to see if I could get focused FX working with just a single knob for now. Once you get one knob talking, the others just need to follow the same pattern.

Hope this is helpful. It's much easier when the device is in hand or when the .mst grunt work was done by someone else.

I'd also reconsider the naming convention. Maybe not though. If it were me, I'd probably label them something like:

TopRotary1-8
RightRotary1-8
LeftRotary1-8
BottomRotary1-8

or even

RotaryA1-A8
RotaryB1-B8
RotaryC1-C8
RotaryD1-D8

Just in case you ever wanted to take it on a flight or something and have an alternate config where like the bottom row was track volume and the top row was track pan, and right and left were sends/receives. If they follows an 4x8 naming convention, you could do that. But if you're only going to use 32 rotaries for exclusive FX control, then it's not necessary. Just something to think about and make an informed decision on.

I update the MST to use Fader7Bit but get the same result. Also added OnInitialization ToggleEnableFocusedFXMapping to the home.zon and same result.

Should I at least see the AutoGeneratedFXZones folder beting created in the MP_MIDI folder? Or will all the mapping files remain in the QCon config folder? Just to see what would happen I copied the auto generated folder from the Qcon to MP_MIDI and it didn't make a difference.

I'm still trying to learn the details of CSI so this is helpful and I'll keep trying as long as you think theres a shot a getting this working!

[Funkybot]

AutoGeneratedFX zones are surface level. So you'd be expecting to see the folder/FX.zon's get created in the MP_MIDI folder. My guess is that the issue is that we don't have a button on that surface to trigger the automapping. Btton-less surfaces! What will they think of next?

Just want to make sure of a few things: first, did you disable the MP MIDI ports in Reaper's preferences MIDI devices?

Next, set the MP_MIDI device up as 32 channels. Probably not messing anything up as is, but lets see if it changes anything.

Just to experiment, what happens if you add this to the MP_MIDI folder then restart Reaper...

Home.zon

Zone Home
    IncludedZones
        SelectedTrack
        Buttons
    IncludedZonesEnd
    AssociatedZones
	LearnFXParams
    AssociatedZonesEnd
ZoneEnd

SelectedTrack.zon

Zone "SelectedTrack"
    Rotary1    TrackVolume
    Rotary2    TrackPanAutoLeft
    Rotary3    TrackPanAutoRight
ZoneEnd

...create a new track, and with that track selected in Reaper, does Rotary1 control the track volume, and Rotary2 trackpan? If yes, that's a start and means the .mst is good. If no, what happens? Anything? Are the knobs wiggling but not moving or moving too fast?

I want to make sure we get the MP_MIDI device communicating and working doing something simple before we move onto FX and incorporating into the broadcast/listen setup with the QCon.

[AAllali]

Hi,
I am quite new to CSI and Reaper. I use CSI with a X-Touch
I just upgraded from an older version (installed in July 2023) to the latest version of CSI. I did drop the dll file in the resource path.
However, I do not have the new "advanced" window for plug in mapping. It's still the old one.
I surely messed something in the setup... Is it a way to know which version of CSI is running?

Besides, should I change anything in the assignment files to get it to work?

Thanks

[Freex]

Originally Posted by Funkybot

CSI Support Files have the following updates:

1. Added FaderportClassic files (FreeX, I renamed them to just FaderportClassic and used the CSI native action for toggling input monitoring)

You might want to add the info about getting the Faderport back into Native mode, I've found that it sometimes goes into limbo mode,
neither MCU or Native where every button has the same command, and it repeats a 90 ## ## command every couple of seconds.

The only way to put it back into Native mode is by sending it

91 00 64

I tried a few different ways to make that automatic in the .mst but the only way that seemed to work was making a widget (from limbo mode)
and giving it the FB 91 00 64.

But I'm sure there's a more elegant way.

I'm not a fan of the CSI native action for toggling input monitoring, to many presses. I did wonder if the coding order was maybe backwards
or something, or that it could look to see if item monitoring was on first and if not move to track monitoring, rather than toggling thru all the options.
But I'm no coder so I take Geoffs code as gospil, lol.

[georges]

Originally Posted by Funkybot

AutoGeneratedFX zones are surface level. So you'd be expecting to see the folder/FX.zon's get created in the MP_MIDI folder. My guess is that the issue is that we don't have a button on that surface to trigger the automapping. Btton-less surfaces! What will they think of next?

Just want to make sure of a few things: first, did you disable the MP MIDI ports in Reaper's preferences MIDI devices?

Next, set the MP_MIDI device up as 32 channels. Probably not messing anything up as is, but lets see if it changes anything.

Just to experiment, what happens if you add this to the MP_MIDI folder then restart Reaper...

Home.zon

Zone Home
    IncludedZones
        SelectedTrack
        Buttons
    IncludedZonesEnd
    AssociatedZones
	LearnFXParams
    AssociatedZonesEnd
ZoneEnd

SelectedTrack.zon

Zone "SelectedTrack"
    Rotary1    TrackVolume
    Rotary2    TrackPanAutoLeft
    Rotary3    TrackPanAutoRight
ZoneEnd

...create a new track, and with that track selected in Reaper, does Rotary1 control the track volume, and Rotary2 trackpan? If yes, that's a start and means the .mst is good. If no, what happens? Anything? Are the knobs wiggling but not moving or moving too fast?

I want to make sure we get the MP_MIDI device communicating and working doing something simple before we move onto FX and incorporating into the broadcast/listen setup with the QCon.

Progress! After making the latest changes, Rotary1 on the MP_MIDI controls the track volume and Rotary2 controls panning. Not sure if this was causing a problem or not but FXLayouts.zon was showing 32 channels but in the CSI configuration in Reaper it showed 0. I updated this to 32 in the control surface settings in Reaper.

Also confirmed the device was disabled in Reaper.

[Funkybot]

Originally Posted by georges

Progress! After making the latest changes, Rotary1 on the MP_MIDI controls the track volume and Rotary2 controls panning. Not sure if this was causing a problem or not but FXLayouts.zon was showing 32 channels but in the CSI configuration in Reaper it showed 0. I updated this to 32 in the control surface settings in Reaper.

Also confirmed the device was disabled in Reaper.

Awesome news! We can probably forget about most of that stuff now, at least the SelectedTrack zone (unless you wanted to keep it). That was really just me trying to think of the easiest way to know things were talking to each other.

Ok, let's try to get the 2 surfaces talking to each other and see if we can get the FX stuff working. First, check out this page on the wiki:

https://github.com/GeoffAWaddington/...ast-and-listen

What I think you'll need to do:

1. Add your QCon Surface as a Broadcaster
2. Add your MP_MIDI device as a Listener
3. The MP_MIDI device will probably need to "Listen To" the following: GoHome, Learn, AutoMap, FXMenu, FocusedFX (if you wanted to do SelectedTrackFX, you could do that too - probably no harm in checking that box if you're unsure)
4. You'll also likely need to set the QCon up as a Listener in order it for it to listen to itself - so set that up and check the boxes for any zones/actions you use - Broadcaster will broadcast all messages but once setup as broadcasters, actually stop listening to themselves except where told to

Next up, on the QCon, just make sure you have a LearnFXParams zone with Save and Erase buttons. As well as an AutoMapFX action in your buttons zone. See here for more help:

https://github.com/GeoffAWaddington/...d-Remap-Window

...hopefully that can get you going!

[georges]

Originally Posted by Funkybot

Awesome news! We can probably forget about most of that stuff now, at least the SelectedTrack zone (unless you wanted to keep it). That was really just me trying to think of the easiest way to know things were talking to each other.

Ok, let's try to get the 2 surfaces talking to each other and see if we can get the FX stuff working. First, check out this page on the wiki:

https://github.com/GeoffAWaddington/...ast-and-listen

What I think you'll need to do:

1. Add your QCon Surface as a Broadcaster
2. Add your MP_MIDI device as a Listener
3. The MP_MIDI device will probably need to "Listen To" the following: GoHome, Learn, AutoMap, FXMenu, FocusedFX (if you wanted to do SelectedTrackFX, you could do that too - probably no harm in checking that box if you're unsure)
4. You'll also likely need to set the QCon up as a Listener in order it for it to listen to itself - so set that up and check the boxes for any zones/actions you use - Broadcaster will broadcast all messages but once setup as broadcasters, actually stop listening to themselves except where told to

Next up, on the QCon, just make sure you have a LearnFXParams zone with Save and Erase buttons. As well as an AutoMapFX action in your buttons zone. See here for more help:

https://github.com/GeoffAWaddington/...d-Remap-Window

...hopefully that can get you going!

So close... no go with the latest changes. I go into learn mode and the Qcon will learn but not the MP_MIDI. I uploaded a screenshot of the advanced CSI settings and a screenshot of console output. After setting up broadcast/receive, the values being displayed in the output seems to have changed but that's probably expected.

[Funkybot]

Originally Posted by georges

So close... no go with the latest changes. I go into learn mode and the Qcon will learn but not the MP_MIDI. I uploaded a screenshot of the advanced CSI settings and a screenshot of console output. After setting up broadcast/receive, the values being displayed in the output seems to have changed but that's probably expected.

Are you even getting the menu asking if to enter Auto-map or Learn mode for the MP MIDI?


I don't think this will change anything, but just to try it out, what happens if you use this for your SurfaceFXLayout file for MP_MIDI? Does anything change? I know it has no faders and displays.

Zone SurfaceFXLayout
	Rotary FXParam RingStyle=Dot
	DisplayUpper FixedTextDisplay
	DisplayLower FXParamValueDisplay
ZoneEnd

#WidgetTypes Rotary RotaryPush Fader
#RingStyles Dot Fill BoostCut Spread
#DisplayRows DisplayUpper DisplayLower

[Funkybot]

Also, georges, please also try adding dummy display widgets to your .mst. I remember MM reporting that Learn wouldn't work on MIDI surfaces with no displays. So add this and even though they'll do nothing. Just to troubleshoot.

Widget DisplayUpper1
	FB_XTouchDisplayUpper 0
WidgetEnd

Widget DisplayUpper2
	FB_MCUDisplayUpper 1
WidgetEnd

Widget DisplayUpper3
	FB_MCUDisplayUpper 2
WidgetEnd

Widget DisplayUpper4
	FB_MCUDisplayUpper 3
WidgetEnd

Widget DisplayUpper5
	FB_MCUDisplayUpper 4
WidgetEnd

Widget DisplayUpper6
	FB_MCUDisplayUpper 5
WidgetEnd

Widget DisplayUpper7
	FB_MCUDisplayUpper 6
WidgetEnd

Widget DisplayUpper8
	FB_MCUDisplayUpper 7
WidgetEnd

Widget DisplayLower1
	FB_MCUDisplayLower 0
WidgetEnd

Widget DisplayLower2
	FB_MCUDisplayLower 1
WidgetEnd

Widget DisplayLower3
	FB_MCUDisplayLower 2
WidgetEnd

Widget DisplayLower4
	FB_MCUDisplayLower 3
WidgetEnd

Widget DisplayLower5
	FB_MCUDisplayLower 4
WidgetEnd

Widget DisplayLower6
	FB_MCUDisplayLower 5
WidgetEnd

Widget DisplayLower7
	FB_MCUDisplayLower 6
WidgetEnd

Widget DisplayLower8
	FB_MCUDisplayLower 7
WidgetEnd

I know that won't do anything, I just want to see if that makes a difference when combined with the SurfaceFXLayout from the prior post.

Sorry that we're now in the "try out some seemingly random stuff to see what sticks" phase. I hate giving answers like that where I'm not 100% sure.

[georges]

Originally Posted by Funkybot

Are you even getting the menu asking if to enter Auto-map or Learn mode for the MP MIDI?


I don't think this will change anything, but just to try it out, what happens if you use this for your SurfaceFXLayout file for MP_MIDI? Does anything change? I know it has no faders and displays.

Zone SurfaceFXLayout
	Rotary FXParam RingStyle=Dot
	DisplayUpper FixedTextDisplay
	DisplayLower FXParamValueDisplay
ZoneEnd

#WidgetTypes Rotary RotaryPush Fader
#RingStyles Dot Fill BoostCut Spread
#DisplayRows DisplayUpper DisplayLower

I feel I'm getting inconsistent menu promots. Again, I'm sure it's me not fully understanding everything and not doing things in the right order. With a FX focused, if I press Shift+Inst the FX auto maps. Then, with the FX still focused, if I press Inst I get a dialog box "Zone Aleady Exists - ReaComp already exists - Do you want to delete it permanently and go into LearnMode?" From there, I can map as expected (but sometime press Inst does not save the file and if go back and map another FX parameter, press Inst, the file saves.

Before making the latest changes to SurfaceFXLayout.zon, I noticed that a AutoGeneratedFXZones folder was created in the MP_MIDI folder. Progress! I was testing with ReaComp and I see the following file VST__ReaComp__Cockos_.zon

----
Zone "VST: ReaComp (Cockos)" "ReaComp" "Generated by Learn"
OnZoneActivation HideFXSlot

#Begin auto generated section
#End auto generated section
ZoneEnd
----

With the updates to the SurfaceFXLayout.zon applied, no changes noted.

I'm in the Philadelphia area and I see you are in NJ. Given the same timezone, would you be interested in setting up time for a screenshare session? Might save time in the long run.

[georges]

Originally Posted by Funkybot

Also, georges, please also try adding dummy display widgets to your .mst. I remember MM reporting that Learn wouldn't work on MIDI surfaces with no displays. So add this and even though they'll do nothing. Just to troubleshoot.

Widget DisplayUpper1
	FB_XTouchDisplayUpper 0
WidgetEnd

Widget DisplayUpper2
	FB_MCUDisplayUpper 1
WidgetEnd

Widget DisplayUpper3
	FB_MCUDisplayUpper 2
WidgetEnd

Widget DisplayUpper4
	FB_MCUDisplayUpper 3
WidgetEnd

Widget DisplayUpper5
	FB_MCUDisplayUpper 4
WidgetEnd

Widget DisplayUpper6
	FB_MCUDisplayUpper 5
WidgetEnd

Widget DisplayUpper7
	FB_MCUDisplayUpper 6
WidgetEnd

Widget DisplayUpper8
	FB_MCUDisplayUpper 7
WidgetEnd

Widget DisplayLower1
	FB_MCUDisplayLower 0
WidgetEnd

Widget DisplayLower2
	FB_MCUDisplayLower 1
WidgetEnd

Widget DisplayLower3
	FB_MCUDisplayLower 2
WidgetEnd

Widget DisplayLower4
	FB_MCUDisplayLower 3
WidgetEnd

Widget DisplayLower5
	FB_MCUDisplayLower 4
WidgetEnd

Widget DisplayLower6
	FB_MCUDisplayLower 5
WidgetEnd

Widget DisplayLower7
	FB_MCUDisplayLower 6
WidgetEnd

Widget DisplayLower8
	FB_MCUDisplayLower 7
WidgetEnd

I know that won't do anything, I just want to see if that makes a difference when combined with the SurfaceFXLayout from the prior post.

Sorry that we're now in the "try out some seemingly random stuff to see what sticks" phase. I hate giving answers like that where I'm not 100% sure.

No worries at all!!!! Sometimes that phase is part of the fun! I'll wait to try these changes once I see a response to my last post. If the answer is no to screensharing, I'll give this a try and report back.

[Funkybot]

I might be able to hop on a call over the weekend (free time is in short supply these days) but I'd suggest keeping at it. I'm really shooting nearly in the dark here.

In the meantime, for next steps, here's what I'd do:

1. Create an .mst we can just use for experimentation - call it like MP_MIDI_Alt.mst or something.

2. In that .mst add only the first 8 rotaries

3. Add in the DisplayUpper/DisplayLower widgets from my prior post - it may be the case that the Learn process is expecting displays - unsure

4. Setup your device with 8 channels in CSI's settings (I don't think this matters, but just try it out).

5. Go to the FXLayouts.zon and change the 32 in there currently to 8 in order to match. We'll set it back later.

6. See if you can get mapping to work with just the first 8 rotaries with that setup. Your broadcast/listen setup looked fine to me so I don't think the issue is there.

If the above works, it might give us a clue as to what to try next.

[MixR]

Hey Funkybot,

the link to the changelog at
https://github.com/GeoffAWaddington/CSI30Wiki

points to an old version at
https://github.com/GeoffAWaddington/...I-Changelog.md

and not the one in your signature (which has the latest changes).

https://github.com/GeoffAWaddington/.../CSI-Changelog

Would you be able to update the Github Wiki page?

Thank you so much!

[Funkybot]

Originally Posted by MixR

Hey Funkybot,

the link to the changelog at
https://github.com/GeoffAWaddington/CSI30Wiki

points to an old version at
https://github.com/GeoffAWaddington/...I-Changelog.md

and not the one in your signature (which has the latest changes).

https://github.com/GeoffAWaddington/.../CSI-Changelog

Would you be able to update the Github Wiki page?

Thank you so much!

Oh, I have no idea what an .md file is. Might need Geoff on this one.

[Geoff Waddington]

Originally Posted by MixR

Hey Funkybot,

the link to the changelog at
https://github.com/GeoffAWaddington/CSI30Wiki

points to an old version at
https://github.com/GeoffAWaddington/...I-Changelog.md

and not the one in your signature (which has the latest changes).

https://github.com/GeoffAWaddington/.../CSI-Changelog

Would you be able to update the Github Wiki page?

Thank you so much!

Why are you trying to access the Wiki via "Code" instead of "Wiki" ?

Judging by the timestamps, all of the .md files in the "Code" section look hopelessly out of date.

Don't recall how they got there, maybe I used "Code" as a quick and dirty way to transfer the old Wiki pages

FB, .md is just the markdown extension for the Wiki pages.

[georges]

Originally Posted by Funkybot

I might be able to hop on a call over the weekend (free time is in short supply these days) but I'd suggest keeping at it. I'm really shooting nearly in the dark here.

In the meantime, for next steps, here's what I'd do:

1. Create an .mst we can just use for experimentation - call it like MP_MIDI_Alt.mst or something.

2. In that .mst add only the first 8 rotaries

3. Add in the DisplayUpper/DisplayLower widgets from my prior post - it may be the case that the Learn process is expecting displays - unsure

4. Setup your device with 8 channels in CSI's settings (I don't think this matters, but just try it out).

5. Go to the FXLayouts.zon and change the 32 in there currently to 8 in order to match. We'll set it back later.

6. See if you can get mapping to work with just the first 8 rotaries with that setup. Your broadcast/listen setup looked fine to me so I don't think the issue is there.

If the above works, it might give us a clue as to what to try next.

Totally understand regarding your free time comment. I tried the latest updates and no change. I zipped/attached the new MST file, CSI.ini, and MP_Midi folder in case you want to review.

[Funkybot]

Originally Posted by georges

Totally understand regarding your free time comment. I tried the latest updates and no change. I zipped/attached the new MST file, CSI.ini, and MP_Midi folder in case you want to review.

Ok, some file management stuff:

The CSI parser will read all the .zon files in the Zone folder, then it reads the first line of the zone contents to see what kind fo zone it is. You can't have old copies of stuff with the .zon extension because they will still get picked up.

It will also read all subfolders and scan those for any .zon files.

So you shouldn't have both...

SufaceFXLayout.zon
SurfaceFXLayout-org.zon

and...

xSelectedTrack.zon

If you want to keep things in the same folder, I'd rename the file extension to .bak or .old. That will cause the CSI parser not to scan those files.

Same with having an AutoGeneratedFXZones folder and an xAutoGeneratedFXZones folder. CSI will just read both despite the different names. So get rid of one of them.

Best approach might be to just create MP_MIDI_TEST folder.

Do that clean up and try again.

[georges]

Originally Posted by Funkybot

Ok, some file management stuff:

The CSI parser will read all the .zon files in the Zone folder, then it reads the first line of the zone contents to see what kind fo zone it is. You can't have old copies of stuff with the .zon extension because they will still get picked up.

It will also read all subfolders and scan those for any .zon files.

So you shouldn't have both...

SufaceFXLayout.zon
SurfaceFXLayout-org.zon

and...

xSelectedTrack.zon

If you want to keep things in the same folder, I'd rename the file extension to .bak or .old. That will cause the CSI parser not to scan those files.

Same with having an AutoGeneratedFXZones folder and an xAutoGeneratedFXZones folder. CSI will just read both despite the different names. So get rid of one of them.

Best approach might be to just create MP_MIDI_TEST folder.

Do that clean up and try again.

Ah, good to know. Thanks for that. You won't be surprised to hear that things have greatly improved!

I can learn, save, and control fx parameters on the QCon.

I can learn, save, but NOT control fx parameters on the MP_MIDI.

Not sure if this has any effect but I noticed the associate effect zon file "header" is different between the two folders.

MP_MIDI reacomp zon file header:
Zone "VST: ReaComp (Cockos)" "ReaComp" "Generated by Learn"
OnZoneActivation HideFXSlot

QCon reacomp zon file header:
Zone "VST: ReaComp (Cockos)" "ReaComp" "Generated by Learn"
OnZoneActivation SetXTouchDisplayColors Cyan
OnZoneActivation ToggleUseLocalModifiers
OnZoneDeactivation RestoreXTouchDisplayColors
OnZoneDeactivation ToggleUseLocalModifiers
Plugin ClearFXSlot

In the Reaper CSI advanced config, for the MP_MIDI listeners settings I also enabled LocalFXSlot and FocusedFXParam, but that didn't do anything to help adjust the parameter from the device.

[Funkybot]

Originally Posted by georges

Ah, good to know. Thanks for that. You won't be surprised to hear that things have greatly improved!

I can learn, save, and control fx parameters on the QCon.

I can learn, save, but NOT control fx parameters on the MP_MIDI.

Not sure if this has any effect but I noticed the associate effect zon file "header" is different between the two folders.

MP_MIDI reacomp zon file header:
Zone "VST: ReaComp (Cockos)" "ReaComp" "Generated by Learn"
OnZoneActivation HideFXSlot

QCon reacomp zon file header:
Zone "VST: ReaComp (Cockos)" "ReaComp" "Generated by Learn"
OnZoneActivation SetXTouchDisplayColors Cyan
OnZoneActivation ToggleUseLocalModifiers
OnZoneDeactivation RestoreXTouchDisplayColors
OnZoneDeactivation ToggleUseLocalModifiers
Plugin ClearFXSlot

In the Reaper CSI advanced config, for the MP_MIDI listeners settings I also enabled LocalFXSlot and FocusedFXParam, but that didn't do anything to help adjust the parameter from the device.

LocalFXSlot would be if you wanted to use different FX on the QCon and MP_MIDI device simultaneously. FocusedFXParam would be if you wanted to use like the Master fader on the QCon to control the focused fx parameter in Reaper. Neither really apply to your setup.

What I would do, now that you kind of have things working, is try to go back to the display-less setup, with 32 channels, and see if you can get things working there.

Maybe try this next...

Go back to the original Rotary1-32.mst

Then use these zone files...
Home.zon

Zone Home
OnInitialization ToggleEnableFocusedFXMapping   // we're turning this off, use the FXMenu on the QCon to active fx on the MP_MIDI
    IncludedZones
        Buttons
    IncludedZonesEnd
ZoneEnd

Go back to this...

SurfaceFXLayout.zon

Zone SurfaceFXLayout
	Rotary FXParam RingStyl=Dot
ZoneEnd

#WidgetTypes Rotary
#RingStyles Dot Fill BoostCut Spread

FXLayouts.zon

Zone FXLayouts
     "" "" 32
     "Shift" "" 32
     "Option" "" 32
     "Control" "" 32
     "Alt" "" 32
     "Shift+Option" 32
     "Shift+Control" "" 32
     "Shift+Alt" "" 32
ZoneEnd

FXPrologue.zon

Zone FXPrologue
	OnZoneActivation	HideFXSlot
ZoneEnd

Can you get things working playing around with the above? If not, I'm thinking I can create an OSC surface to try to mimic your setup but I won't have time to try that out for next few days.

[tommoh]

Hi all. Still at it, trying to get the Icon Platform Nano to play nicely with CSI. Two things first, The Icon does not send out a Sysex message when you press the “Master” track selector, rather it changes the CC number of the fader. Is there a way to get Reaper to switch to the master track when this happens?
Secondly, whenever I switch from Reaper to, say, ah Internet browse the Icon send to lose connection with Reaper and needs to be refreshed (Alt+F1) to get it back on track. Why could this be and how can I rectify it?
Thanks in advance

[Funkybot]

Originally Posted by tommoh

Hi all. Still at it, trying to get the Icon Platform Nano to play nicely with CSI. Two things first, The Icon does not send out a Sysex message when you press the “Master” track selector, rather it changes the CC number of the fader. Is there a way to get Reaper to switch to the master track when this happens?

It sounds like the Platform Nano is just following the MCU spec, which is 8 channel faders plus 1 master. So just add your MasterTrack zone as an included zone in Home.

I can't emphasize this enough as a general tip: if you're using an MCU surface, start with the stock MCU files or at least reference them regularly to see how they work.

Originally Posted by tommoh

Secondly, whenever I switch from Reaper to, say, ah Internet browse the Icon send to lose connection with Reaper and needs to be refreshed (Alt+F1) to get it back on track. Why could this be and how can I rectify it?
Thanks in advance

Go to Repaer's Preferences > Control/OSC/Web. Do you have the box checked that says, "Close control surface devices when stopped and not active application?" If yes, uncheck that.

[melostalker]

Hi at all,
Anybody here have problems with the Remap window?
I’ve updated to the latest CSI version and now the remap window don’t show me the FX params.
The window is empty. I can remap them but I don’t se the parameter names.

I’m on Mac with latest reaper Version

[Geoff Waddington]

Originally Posted by melostalker

Hi at all,
Anybody here have problems with the Remap window?
I’ve updated to the latest CSI version and now the remap window don’t show me the FX params.
The window is empty. I can remap them but I don’t se the parameter names.

I’m on Mac with latest reaper Version

The auto generated FX Zone format changed, you might have to remap.

As a test, just delete one of your old auto generated FX Zones, then let CSI auto map it, and then check to see if Remap works on that Zone.

[GeckoLikesMartini]

Originally Posted by Funkybot

Yes. That just got released yesterday. It's called Auto-Map.

See here:
https://github.com/GeoffAWaddington/.../CSI-Changelog

But even more importantly, here:
https://github.com/GeoffAWaddington/...d-Remap-Window

...all the details about how to setup auto-mapping are on that latter page.

Thanks for the links - is there a solution to just completely disable the auto map function ? I prefer to not get any dialogue window when clicking on an empty fx slot or an unmapped plugin.

Regards, mj

[Geoff Waddington]

Originally Posted by GeckoLikesMartini

Thanks for the links - is there a solution to just completely disable the auto map function ? I prefer to not get any dialogue window when clicking on an empty fx slot or an unmapped plugin.

Regards, mj

Just had a quick look at the code, looks like I need to add a feature request

[melostalker]

Originally Posted by Geoff Waddington

The auto generated FX Zone format changed, you might have to remap.

As a test, just delete one of your old auto generated FX Zones, then let CSI auto map it, and then check to see if Remap works on that Zone.

Thanks, now it's working. My fxlayout.zon had some issue

[Geoff Waddington]

Originally Posted by GeckoLikesMartini

Thanks for the links - is there a solution to just completely disable the auto map function ? I prefer to not get any dialogue window when clicking on an empty fx slot or an unmapped plugin.

Regards, mj

Been thinking about this a bit more.

Agree GoFXSlot for an empty slot should do nothing.

However, what do you think should happen for an FX that has no map ?

Doing nothing doesn't seem right.

[georges]

Originally Posted by Funkybot

LocalFXSlot would be if you wanted to use different FX on the QCon and MP_MIDI device simultaneously. FocusedFXParam would be if you wanted to use like the Master fader on the QCon to control the focused fx parameter in Reaper. Neither really apply to your setup.

What I would do, now that you kind of have things working, is try to go back to the display-less setup, with 32 channels, and see if you can get things working there.

Maybe try this next...

Go back to the original Rotary1-32.mst

Then use these zone files...
Home.zon

Zone Home
OnInitialization ToggleEnableFocusedFXMapping   // we're turning this off, use the FXMenu on the QCon to active fx on the MP_MIDI
    IncludedZones
        Buttons
    IncludedZonesEnd
ZoneEnd

Go back to this...

SurfaceFXLayout.zon

Zone SurfaceFXLayout
	Rotary FXParam RingStyl=Dot
ZoneEnd

#WidgetTypes Rotary
#RingStyles Dot Fill BoostCut Spread

FXLayouts.zon

Zone FXLayouts
     "" "" 32
     "Shift" "" 32
     "Option" "" 32
     "Control" "" 32
     "Alt" "" 32
     "Shift+Option" 32
     "Shift+Control" "" 32
     "Shift+Alt" "" 32
ZoneEnd

FXPrologue.zon

Zone FXPrologue
	OnZoneActivation	HideFXSlot
ZoneEnd

Can you get things working playing around with the above? If not, I'm thinking I can create an OSC surface to try to mimic your setup but I won't have time to try that out for next few days.

With these changes back to nothing happening on the MP_MIDI side. AutoGeneratedFXZones folder not being created. Once I added that back and after adding LearnFXParams as an associated zone. Auto folder created and a zon file with only OnZoneActivation HideFXSlot.

I really appreciate all of your help and time with this. I'll keep trying on my end and look for an update in a few days once you try OSC (territory I'm totally unfamiliar with)

[Funkybot]

Originally Posted by georges

With these changes back to nothing happening on the MP_MIDI side. AutoGeneratedFXZones folder not being created. Once I added that back and after adding LearnFXParams as an associated zone. Auto folder created and a zon file with only OnZoneActivation HideFXSlot.

I really appreciate all of your help and time with this. I'll keep trying on my end and look for an update in a few days once you try OSC (territory I'm totally unfamiliar with)

Oh sorry, yeah, that LearnFXParams definitely needs to be an AssociatedZone. My apologies.

We'll get there. Might just take a bit more trial and error. Feel free to keep at it or just wait a bit more and I'll see if I can get an OSC version together over the weekend and test on that.

[Geoff Waddington]

Version 3.2.2 is now available.

CSI no longer presents dialog if FX slot is empty.

Link is in blue below.

[Funkybot]

Hi Geoff, a few questions as I try to help get george's MPMIDI controller working as an FX knob Box he can launch from his QCon. A few of these things might be a bit unique to his setup and understanding how CSI works around these would help get him up and running:

1. Are there any bare minimum requirements for IncludedZones in a Home.zon? For instance, can a Home zone have no included zones and just an LearnFXParams AssociatedZone? I'm thinking that should be no problem, but wanted to confirm as it's atypical. He just wants the surface to be dormant until he launches FX on it from his QCon or Focuses them in Reaper.

2. SaveLearnFXParams and EraseLastTouched can now be broadcast from one surface to another via the LearnFXParams ListenTo option right? He doesn't need physical buttons on the MPMIDI for these and can stick them on the QCon right?

3. Are there any bare minimum WidgetTypes requirements for Learn to work? For instance, I recall early on MM saying Learn would only work on surfaces with displays. Is that the case? It sounds like george's setup would use the device as a knob box only. If displays are a requirement for Learn, we would need to add in Dummy Display widgets.

4. Also, can the WidgetTypes in the SurfaceFXLayout.zon just be Rotary only? He's got no buttons on the surface and no faders and no displays. I'd think it should be flexible enough to work with just one, but again, very atypical.

[Geoff Waddington]

Originally Posted by Funkybot

Hi Geoff, a few questions as I try to help get george's MPMIDI controller working as an FX knob Box he can launch from his QCon. A few of these things might be a bit unique to his setup and understanding how CSI works around these would help get him up and running:

1. Are there any bare minimum requirements for IncludedZones in a Home.zon? For instance, can a Home zone have no included zones and just an LearnFXParams AssociatedZone? I'm thinking that should be no problem, but wanted to confirm as it's atypical. He just wants the surface to be dormant until he launches FX on it from his QCon or Focuses them in Reaper.

2. SaveLearnFXParams and EraseLastTouched can now be broadcast from one surface to another via the LearnFXParams ListenTo option right? He doesn't need physical buttons on the MPMIDI for these and can stick them on the QCon right?

Yes, you should be fine.

Originally Posted by Funkybot

3. Are there any bare minimum WidgetTypes requirements for Learn to work? For instance, I recall early on MM saying Learn would only work on surfaces with displays. Is that the case? It sounds like george's setup would use the device as a knob box only. If displays are a requirement for Learn, we would need to add in Dummy Display widgets.

I would define some Dummy Display Widgets, just to get things going, then try removing them and see what happens.

Originally Posted by Funkybot

4. Also, can the WidgetTypes in the SurfaceFXLayout.zon just be Rotary only? He's got no buttons on the surface and no faders and no displays. I'd think it should be flexible enough to work with just one, but again, very atypical.

Yes, you should be fine here as well, aside from the display caveat mentioned above.

[MixMonkey]

Originally Posted by Funkybot

2. SaveLearnFXParams and EraseLastTouched can now be broadcast from one surface to another via the LearnFXParams ListenTo option right?

Whilst SaveLearnFXParams definitely broadcasts, I didn't have any luck with EraseLastTouchedControl and had to include it in the LearnFXParams Zone for each XT (RecordArm8). I would much rather put it on the MCU and have it broadcast.
That said, please corroborate that EraseLastTouchedControl doesn't broadcast, second opinions derived from different circumstances are the key to effective troubleshooting

The same goes regarding the need for display definitions in the .mst in order for Learn to operate.

[Geoff Waddington]

Originally Posted by MixMonkey

Whilst SaveLearnFXParams definitely broadcasts, I didn't have any luck with EraseLastTouchedControl and had to include it in the LearnFXParams Zone for each XT (RecordArm8). I would much rather put it on the MCU and have it broadcast.
That said, please corroborate that EraseLastTouchedControl doesn't broadcast, second opinions derived from different circumstances are the key to effective troubleshooting

Oops, right you are, EraseLastTouchedControl needs the surface context in order to know which Zone control to erase, that's why Broadcast makes no sense for EraseLastTouchedControl.

Originally Posted by MixMonkey

The same goes regarding the need for display definitions in the .mst in order for Learn to operate.

Yes, as I said, define some Dummy Display Widgets as a startiing point, then, when things work, try removing them.