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

[Geoff Waddington]

This is the place to discuss/ask about all setup, configuration, help, devices, bug reports, etc. related topics.

The red Wiki link below is another great place to get CSI info related to the above topics.

The CSI Technical Feature Discussion thread will be restricted to technical design considerations.

[mschnell]

Is there already an XTouch Compact file set for it ? (I might finally reconsider to jump in...)
But.... I am heavily using the pre-release "media item fixed lanes" comping, so I suppose I would need this to be supported. (Of course on the long ruin I would be able to make this happen...)
-Michael

[Geoff Waddington]

Originally Posted by mschnell

Is there already an XTouch Compact file set for it ? (I might finally reconsider to jump in...)
But.... I am heavily using the pre-release "media item fixed lanes" comping, so I suppose I would need this to be supported. (Of course on the long ruin I would be able to make this happen...)
-Michael

In the X Touch world we only have X Touch Universal and X Touch One so far.

[mschnell]

I am still not clear if with the Compact it would make more sense to use the Midi or the MC mode...

[Funkybot]

General message to everyone starting off with CSI v3: if you have a device that supports "MCU" of any kind (Behringer, ICON, SSL, etc.), you can probably get up and running quickly with the included X-Touch files from CSI support. There may be some things the X-Touch supports that your hardware doesn't: like changing the display colors and feedback on buttons, but that should be no problem with other hardware that sticks closely to the MCU hardware. Your surface just won't change colors or display feedback, but all features should otherwise work. Hence why it's a great jumping off point until stock MCU files get added.

Just copy the zone folder and rename it for your surface and use that as a jumping off point. The closer your device adheres to MCU, the easier it will be.

Originally Posted by mschnell

I am still not clear if with the Compact it would make more sense to use the Midi or the MC mode...

I'm not an X-Touch Compact owner, but I'd be happy to assist where I can as long as you share any working files.

I recall helping another user out with X-Touch Compact files somewhat recently and there was something really weird about it but I'm blanking on what.

If you want to get up and running quickly my advice would be the same as above:

1. Set the COMPACT up in MCU mode
2. Use the X-Touch files in the CSI support files
3. Copy and rename the zone files to X-Touch Compact
5. Post back here with details if anything doesn't work, doesn't work well, or you'd want to tweak

If we need to try it in MIDI Mode because of strange behavior, I may be able to find an .mst somewhere but try MCU first.

[mschnell]

The thing is, that in MCU mode, some controls of the Compact are disabled. I could imagine to use those (ore anything ) for special purpose.
Unfortunately with the Compact the Faders feature only 7 bit resolution in either mode
Michael

[leejul]

Hi,
I would like to update CSI 3.0 for blind users but I can't find the changes in the Wiki log. Is there a dedicated log page for version 3.0?
Thanks.

[Funkybot]

Originally Posted by leejul

Hi,
I would like to update CSI 3.0 for blind users but I can't find the changes in the Wiki log. Is there a dedicated log page for version 3.0?
Thanks.

Yes, the CSI v3 wiki is at a brand new URL. Here's the change log page:

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

[Nico the kitchen]

hello everyone, since the x touch one single fader is no longer enough for me, i bought the x touch extender to have a few more faders. I use X touch one with CSI and obviously I would like to do the same with the extender but yesterday after half a day I couldn't get it to work. Can anyone help me? (please) thank you

[Funkybot]

Originally Posted by Nico the kitchen

hello everyone, since the x touch one single fader is no longer enough for me, i bought the x touch extender to have a few more faders. I use X touch one with CSI and obviously I would like to do the same with the extender but yesterday after half a day I couldn't get it to work. Can anyone help me? (please) thank you

How did you try setting it up? Which version of CSI are you using? What .mst/.zon folders? What does your CSI.ini look like? Are you sure you set it up for 8 channels in CSI's device preferences? Did you disable the MIDI ports in Reaper?

Does anyone use an XT without the main unit? I'm assuming, like Nico I presume, that the main unit isn't an absolute requirement for the Extender, but I don't know that for a fact.

[MST]

Originally Posted by Funkybot

How did you try setting it up? Which version of CSI are you using? What .mst/.zon folders? What does your CSI.ini look like? Are you sure you set it up for 8 channels in CSI's device preferences? Did you disable the MIDI ports in Reaper?

Does anyone use an XT without the main unit? I'm assuming, like Nico I presume, that the main unit isn't an absolute requirement for the Extender, but I don't know that for a fact.

Yes, my x-touch universal doubles as a x32 mixer controller, and then the extender keeps track of the Reaper channels, and then I switch the x-touch U back to CSI when I need banking or FX parameter control.
Basically the X-touch one, and extender together are a slimmed down x-touch universal, and it makes sense to treat the 2 as such.
But there is no bariere also to treat the extender as a stand alone.

[Funkybot]

Originally Posted by MST

Yes, my x-touch universal doubles as a x32 mixer controller, and then the extender keeps track of the Reaper channels, and then I switch the x-touch U back to CSI when I need banking or FX parameter control.
Basically the X-touch one, and extender together are a slimmed down x-touch universal, and it makes sense to treat the 2 as such.
But there is no bariere also to treat the extender as a stand alone.

I didn't think so, but didn't want to assume having no first-hand experience. Thanks for confirming.

[Nico the kitchen]

Originally Posted by Funkybot

How did you try setting it up? Which version of CSI are you using? What .mst/.zon folders? What does your CSI.ini look like? Are you sure you set it up for 8 channels in CSI's device preferences? Did you disable the MIDI ports in Reaper?

Does anyone use an XT without the main unit? I'm assuming, like Nico I presume, that the main unit isn't an absolute requirement for the Extender, but I don't know that for a fact.

I use a folder that i find in this forum, I install CSI 2 week ago so I think is the latest version, mac m1 ventura,I try Behringerxtouchextender.mst and xtouchxt.mst, Behringerxtouchextender zone folder that I find in this forum, I'm new in CSI programming what you mean whit what does your CSI.ini look like?, I made same things that I do whit x touch one that work perfectly and I set extender surface with 8 track, yes I disable the MIDI port. In behringer site they say that you can use extender stand alone and I presume that are usable like a simple fader MIDI controller! Probably I made something wrong cause as I say I'm new in CSI programming. How I have to edit on reaper preferences the CSI? on surfaces I add x touch one and extender, I add 1 page and I add assignement for x touch one and extender set 1 track on xt1 and 8 on ext, now I'm think that the .zon files doesn't work, maybe it's write only for x touch and doesn't work on xt1

[Geoff Waddington]

Originally Posted by Nico the kitchen

I use a folder that i find in this forum, I install CSI 2 week ago so I think is the latest version, mac m1 ventura,I try Behringerxtouchextender.mst and xtouchxt.mst, Behringerxtouchextender zone folder that I find in this forum, I'm new in CSI programming what you mean whit what does your CSI.ini look like?, I made same things that I do whit x touch one that work perfectly and I set extender surface with 8 track, yes I disable the MIDI port. In behringer site they say that you can use extender stand alone and I presume that are usable like a simple fader MIDI controller! Probably I made something wrong cause as I say I'm new in CSI programming. How I have to edit on reaper preferences the CSI? on surfaces I add x touch one and extender, I add 1 page and I add assignement for x touch one and extender set 1 track on xt1 and 8 on ext, now I'm think that the .zon files doesn't work, maybe it's write only for x touch and doesn't work on xt1

You might want to check that the Extender is set up properly:

Press and hold the Channel 1 SELECT button while powering on the device.
Select the mode and connection type:
Rotate encoder 1 to select the operation mode.
Rotate encoder 2 to select the connection type (USB, MIDI, or Network).
(optional) Use encoders 3 to 7 for network setup.
Rotate encoder 8 to adjust the display contrast.
Press the Channel 1 SELECT button to save and continue.

[Nico the kitchen]

Originally Posted by Geoff Waddington

You might want to check that the Extender is set up properly:

Press and hold the Channel 1 SELECT button while powering on the device.
Select the mode and connection type:
Rotate encoder 1 to select the operation mode.
Rotate encoder 2 to select the connection type (USB, MIDI, or Network).
(optional) Use encoders 3 to 7 for network setup.
Rotate encoder 8 to adjust the display contrast.
Press the Channel 1 SELECT button to save and continue.

yesterday I update the extender with the last firmware and I set up with MC and usb

[ajaym]

Thanks, yes , it does but I think metering will be an issue. The OSC spec is as far as I can see intended to control the mixer as the PC application Yamaha provide does, but while this would programmatically control faders and buttons, etc, it would not as far as I can see do metering nor I think the timecode. That stuff is control surface specific if you see what I mean.
But it sounds like CSI wouldn't be an ideal fit which is fine, I just wanted to get an idea before spending any further time on it. Thanks so much for the help

[Funkybot]

See my reply above your post. Post back here if you need help but CSI includes some .ost files if you need some examples. I'd stay with maybe just one channel and see if you can get that working.

[Cragster]

Trying to gey a handle on the Learn Fx mode. If i learn a param on the C4 to say D1
it gets learned on D1 C1 B1 and A1 ?? I cant figure out what im doing wrong

Heres my LearnFXParams. Is this correct for the C4 ?? Thanks for any help

Zone LearnFXParams
	OnZoneActivation		CheckForExistingLearnZone
		
    RotaryA|            	LearnFXParam
    RotaryPushA|        	LearnFXParam
    DisplayUpperA|      	LearnFXParamNameDisplay
    DisplayLowerA|      	LearnFXParamValueDisplay
	
    RotaryB|            	LearnFXParam
    RotaryPushB|        	LearnFXParam
    DisplayUpperB|      	LearnFXParamNameDisplay
    DisplayLowerB|      	LearnFXParamValueDisplay
	
    RotaryC|            	LearnFXParam
    RotaryPushC|        	LearnFXParam
    DisplayUpperC|      	LearnFXParamNameDisplay
    DisplayLowerC|      	LearnFXParamValueDisplay
    	
    RotaryD|            	LearnFXParam
    RotaryPushD|        	LearnFXParam
    DisplayUpperD|      	LearnFXParamNameDisplay
    DisplayLowerD|      	LearnFXParamValueDisplay

    Control+ChannelLeft SaveLearnedFXParams
    Control+ChannelLeft GoHome
    Option+ChannelLeft EraseLastTouchedControl
ZoneEnd

Do I need to specify RotaryA1 A2 A3 etc in this zone rather then RotaryA| ??

[Cragster]

Scratch that last post. I think I got it sorted. User error haha

[Funkybot]

Originally Posted by Cragster

Scratch that last post. I think I got it sorted. User error haha

Too late. Maybe the above will help someone else. At worst, it'll be a foundation for a wiki page.

[Funkybot]

Originally Posted by Cragster

Trying to gey a handle on the Learn Fx mode. If i learn a param on the C4 to say D1
it gets learned on D1 C1 B1 and A1 ?? I cant figure out what im doing wrong

Do I need to specify RotaryA1 A2 A3 etc in this zone rather then RotaryA| ??

EDIT: as of August 6, 2023 there is information in this post that is already out of date. The learn functionality is still being refined while in the Experimental state/builds.

Hey Cragster, I'll get you setup in no time.

You need a few things to make this work. These zone files I'm including here should "just work" for the C4.

1. A SurfaceFXLayout.zon file. This basically defines the available widget types and some other stuff.

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

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

2. An FXLayouts.zon file. The first set of quotes in each line represents the modifiers you want to use in the zone files (first block has empty quotes to represent: unmodified). The second set of quotes in each line represents the rows (if any). So in the C4, there are 4 rows (D, C, B, A - because MM likes to reverse map them and who am I to argue with MM). In MCU layout, the second set of quotes would be empty.

Zone FXLayouts
    "" "D" 8
    "" "C" 8
    "" "B" 8
    "" "A" 8
    
    "Shift" "D" 8
    "Shift" "C" 8
    "Shift" "B" 8
    "Shift" "A" 8
    
    "Option" "D" 8
    "Option" "C" 8
    "Option" "B" 8
    "Option" "A" 8
    
    "Control" "D" 8
    "Control" "C" 8
    "Control" "B" 8
    "Control" "A" 8
    
    "Alt" "D" 8
    "Alt" "C" 8
    "Alt" "B" 8
    "Alt" "A" 8
ZoneEnd

3. Now, for the LearnFXParams.zon, you don't need any widget-related instructions. Just the Save, Erase, and CheckForExisting actions. So literally just this...

Zone LearnFXParams
    OnZoneActivation	CheckForExistingLearnZone

    ChanStrip           SaveLearnedFXParams
    Function            EraseLastTouchedControl
    
ZoneEnd

4. Don't forget, you need a button to activate the zone. Also shown, a Remap Button.

Zone Buttons
        Marker              RemapAutoZone
        Track               GoAssociatedZone LearnFXParams
...
ZoneEnd

5. Absolute last thing needed: just add LearnFXParams as an AssociatedZone in your home.zon.

Zone Home
        IncludedZones
            Buttons
            SelectedTrackSend
            SelectedTrackReceive 
            SelectedTrackFXMenu          
        IncludedZonesEnd
        AssociatedZones
            LearnFXParams
        AssociatedZonesEnd
ZoneEnd

If you want to automap an FX, just activate the FX via the menu. If you want to learn an FX, just:

1. Press the GoAssociatedZone LearnFXParams button
2. Focus the FX in Reaper
3. Move an FXParam in Reaper with your mouse
4. Touch a control on the surface - now they're linked
5. Repeat steps 3 and 4
6. When you run out of controls, latch your modifier and learn the modified set of controls
7. If you need to delete an assignment because you messed up or change your mind just touch the control on your surface, then press the Erase button
8. When done, press the Save button

That's literally it!

[Cragster]

Originally Posted by Funkybot

Hey Cragster, I'll get you setup in no time.

You need a few things to make this work. These zone files I'm including here should "just work" for the C4.

1. A SurfaceFXLayout.zon file. This basically defines the available widget types and some other stuff.

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

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

2. An FXLayouts.zon file. The first set of quotes in each line represents the modifiers you want to use in the zone files (first block has empty quotes to represent: unmodified). The second set of quotes in each line represents the rows (if any). So in the C4, there are 4 rows (D, C, B, A - because MM likes to reverse map them and who am I to argue with MM). In MCU layout, the second set of quotes would be empty.

Zone FXLayouts
    "" "D" 8
    "" "C" 8
    "" "B" 8
    "" "A" 8
    
    "Shift" "D" 8
    "Shift" "C" 8
    "Shift" "B" 8
    "Shift" "A" 8
    
    "Option" "D" 8
    "Option" "C" 8
    "Option" "B" 8
    "Option" "A" 8
    
    "Control" "D" 8
    "Control" "C" 8
    "Control" "B" 8
    "Control" "A" 8
    
    "Alt" "D" 8
    "Alt" "C" 8
    "Alt" "B" 8
    "Alt" "A" 8
ZoneEnd

3. Now, for the LearnFXParams.zon, you don't need any widget-related instructions. Just the Save, Erase, and CheckForExisting actions. So literally just this...

Zone LearnFXParams
    OnZoneActivation	CheckForExistingLearnZone

    ChanStrip           SaveLearnedFXParams
    Function            EraseLastTouchedControl
    
ZoneEnd

4. Don't forget, you need a button to activate the zone. Also shown, a Remap Button.

Zone Buttons
        Marker              RemapAutoZone
        Track               GoAssociatedZone LearnFXParams
...
ZoneEnd

5. Absolute last thing needed: just add LearnFXParams as an AssociatedZone in your home.zon.

Zone Home
        IncludedZones
            Buttons
            SelectedTrackSend
            SelectedTrackReceive 
            SelectedTrackFXMenu          
        IncludedZonesEnd
        AssociatedZones
            LearnFXParams
        AssociatedZonesEnd
ZoneEnd

If you want to automap an FX, just activate the FX via the menu. If you want to learn an FX, just:

1. Press the GoAssociatedZone LearnFXParams button
2. Focus the FX in Reaper
3. Move an FXParam in Reaper with your mouse
4. Touch a control on the surface - now they're linked
5. Repeat steps 3 and 4
6. When you run out of controls, latch your modifier and learn the modified set of controls
7. If you need to delete an assignment because you messed up or change your mind just touch the control on your surface, then press the Erase button
8. When done, press the Save button

That's literally it!

Hey thank you so much for this. It actually did help ! I was missing some things.I do have one more question though before I go through all the trouble of switching things around. The actions that are tied to buttons to make the learn function go...Can i have them on another surface ? meaning can I call up, save, erase the learn function on the C4 from another surface ?? Right now i have all those actions on a button with modifoers on the C4 because im out of buttons there. Id like to put these actions on my Platform B surface . Great surface for CSI its just a 50 button surface with plenty of room for labels..
So before i go switching am i able to work the learn function on the C4 from another surface ?? Thanks itll save me the trouble of it all if i cant

[georges]

Originally Posted by Funkybot

Hey Cragster, I'll get you setup in no time.

You need a few things to make this work. These zone files I'm including here should "just work" for the C4.

1. A SurfaceFXLayout.zon file. This basically defines the available widget types and some other stuff.

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

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

2. An FXLayouts.zon file. The first set of quotes in each line represents the modifiers you want to use in the zone files (first block has empty quotes to represent: unmodified). The second set of quotes in each line represents the rows (if any). So in the C4, there are 4 rows (D, C, B, A - because MM likes to reverse map them and who am I to argue with MM). In MCU layout, the second set of quotes would be empty.

Zone FXLayouts
    "" "D" 8
    "" "C" 8
    "" "B" 8
    "" "A" 8
    
    "Shift" "D" 8
    "Shift" "C" 8
    "Shift" "B" 8
    "Shift" "A" 8
    
    "Option" "D" 8
    "Option" "C" 8
    "Option" "B" 8
    "Option" "A" 8
    
    "Control" "D" 8
    "Control" "C" 8
    "Control" "B" 8
    "Control" "A" 8
    
    "Alt" "D" 8
    "Alt" "C" 8
    "Alt" "B" 8
    "Alt" "A" 8
ZoneEnd

3. Now, for the LearnFXParams.zon, you don't need any widget-related instructions. Just the Save, Erase, and CheckForExisting actions. So literally just this...

Zone LearnFXParams
    OnZoneActivation	CheckForExistingLearnZone

    ChanStrip           SaveLearnedFXParams
    Function            EraseLastTouchedControl
    
ZoneEnd

4. Don't forget, you need a button to activate the zone. Also shown, a Remap Button.

Zone Buttons
        Marker              RemapAutoZone
        Track               GoAssociatedZone LearnFXParams
...
ZoneEnd

5. Absolute last thing needed: just add LearnFXParams as an AssociatedZone in your home.zon.

Zone Home
        IncludedZones
            Buttons
            SelectedTrackSend
            SelectedTrackReceive 
            SelectedTrackFXMenu          
        IncludedZonesEnd
        AssociatedZones
            LearnFXParams
        AssociatedZonesEnd
ZoneEnd

If you want to automap an FX, just activate the FX via the menu. If you want to learn an FX, just:

1. Press the GoAssociatedZone LearnFXParams button
2. Focus the FX in Reaper
3. Move an FXParam in Reaper with your mouse
4. Touch a control on the surface - now they're linked
5. Repeat steps 3 and 4
6. When you run out of controls, latch your modifier and learn the modified set of controls
7. If you need to delete an assignment because you messed up or change your mind just touch the control on your surface, then press the Erase button
8. When done, press the Save button

That's literally it!

I'm unable to get LearnFXParams to work. I've followed this post and the wiki, created and modified files, but no luck.

I'm curious about the LearnFXParams.zon file. I've tried the file as shown above but wasn't sure about the ChanStrip and Function lines. I'm assuming ChanStrip and Function have to be defined in the Buttons.zon file? I've switched ChanStrip and Function with Left and Right but no change.

In any case in my Bottons.zon file I have the following but pressing the Outputs button does nothing. I'm assuming a dialog box should be shown?

Outputs GoAssociatedZone LearnFXParams

[georges]

I'm trying the latest version of CSI (3.1) with a QCon Pro G2 (set to Mackie control mode using latest firmware) and for the most part the device seems to work well for what I'm using it for, which at this time is to learn "in the box" mixing. I've created two configurations using a copy of the default MCU and X-Touch MST and ZON config files. When testing each configuration, things like banking/channeling, select, mute, solo, un-solo all, seem to work. Mapping function buttons to custom Reaper actions is also working. My issue is this. With a track selected, I hit the plugin/inserts (on the G2) and I can see and channel/bank through all the effects/inserts on the selected track. I can also press the pan button to display and control effect parameters. If I have 10 plugins on a channel, as an example, and I bank so track 1 and 2 display the effect/insert names for insert slot 9 and 10, when I press the pan button on track 1, the effect/insert on slot 1 becomes active, not the effect/insert on slot 9. Hopefully that made sense.

Since I'm getting the same result with two different configurations is it a device problem or is there a CSI tweak I need implement? I went through the MST files and the only buttons that didn't exist on the G2 were, if I recall correctly, aux, busses, output, and user. I don't think that would effect FX banking. Still learning CSI and trying to wrap my head around how everything glues together.

[Funkybot]

Originally Posted by georges

My issue is this. With a track selected, I hit the plugin/inserts (on the G2) and I can see and channel/bank through all the effects/inserts on the selected track. I can also press the pan button to display and control effect parameters.

If I have 10 plugins on a channel, as an example, and I bank so track 1 and 2 display the effect/insert names for insert slot 9 and 10, when I press the pan button on track 1, the effect/insert on slot 1 becomes active, not the effect/insert on slot 9. Hopefully that made sense.

Since I'm getting the same result with two different configurations is it a device problem or is there a CSI tweak I need implement? I went through the MST files and the only buttons that didn't exist on the G2 were, if I recall correctly, aux, busses, output, and user. I don't think that would effect FX banking. Still learning CSI and trying to wrap my head around how everything glues together.

Let me try to rephrase the issue with fewer words (just so I understand - may also help if you reproduce these steps and confirm the results):

1. You've got Track 1 with 10 insert effects
2. You select Track 1
3. You click the Plugin button to enter the SelectedTrackFXMenu

Result: You now see Inserts 1-8 on the surface

4. You click the right button to bank the SelectedTrackFXMenu
5. You now see Insert #9 on channel 8 of the surface
6. You press RotaryPush8

Expected Result: Insert 9 should now be mapped onto the surface.

Actual Result: you're saying Insert 1 is mapped to the surface.

Is that right?

[georges]

Originally Posted by Funkybot

Let me try to rephrase the issue with fewer words (just so I understand - may also help if you reproduce these steps and confirm the results):

1. You've got Track 1 with 10 insert effects
2. You select Track 1
3. You click the Plugin button to enter the SelectedTrackFXMenu

Result: You now see Inserts 1-8 on the surface

4. You click the right button to bank the SelectedTrackFXMenu
5. You now see Insert #9 on channel 8 of the surface
6. You press RotaryPush8

Expected Result: Insert 9 should now be mapped onto the surface.

Actual Result: you're saying Insert 1 is mapped to the surface.

Is that right?

Hey Funkybot,

My actual result is Insert 8 is mapped to the surface.
Even if inset 10 is shown on track 8 display, RotaryPush8 maps to insert 8. No matter what the display shows, RotaryPush1-8 seem to be locked to inserts 1-8.

[Funkybot]

Originally Posted by georges

Hey Funkybot,

My actual result is Insert 8 is mapped to the surface.
Even if inset 10 is shown on track 8 display, RotaryPush8 maps to insert 8. No matter what the display shows, RotaryPush1-8 seem to be locked to inserts 1-8.

Ah ok...that sounds like a bug.

Let me try to reproduce. I don't think I've ever had more than 8 inserts on a track and tried mapping in CSI. I'll check it out in the next day or two and try to confirm.

[georges]

Sounds good. I also wanted to mention I'm able to consistently crash reaper (v6.81) by doing the following. Can you try to repro this too?

1. select a track with inserts
2. press the plugin/inserts button
3. press a rotary button to select the insert
4. press the plugin/inserts button
5. reaper crashes

[Funkybot]

Originally Posted by georges

Hey Funkybot,

My actual result is Insert 8 is mapped to the surface.
Even if inset 10 is shown on track 8 display, RotaryPush8 maps to insert 8. No matter what the display shows, RotaryPush1-8 seem to be locked to inserts 1-8.

Bug confirmed here. I threw 10 different compressors on track 1. Banked to insert #10 on Channel8, which was PSP VintageWarmer 2. Then a RotaryPush8 GoFXSlot action.

Result: Insert FX #8 (Kush Audio's Novatron) was mapped.

Expected Result: Insert FX #10 would be mapped.

Will log this.

EDIT: logged here. Thanks for reporting!

https://github.com/GeoffAWaddington/...stall/issues/3

[Funkybot]

Originally Posted by Funkybot

Bug confirmed here. I threw 10 different compressors on track 1. Banked to insert #10 on Channel8, which was PSP VintageWarmer 2. Then a RotaryPush8 GoFXSlot action.

Result: Insert FX #8 (Kush Audio's Novatron) was mapped.

Expected Result: Insert FX #10 would be mapped.

Will log this.

EDIT: logged here. Thanks for reporting!

https://github.com/GeoffAWaddington/...stall/issues/3

georges,

Update: this doesn't appear to be a CSI bug. I believe this is due to the S&M actions that float the FX. See my post from today about this in the main CSI development thread for more details. This will end up being a feature request methinks!

[MisterGTR]

Anyone using a Frontier Alphatrack?

[Dubhed60]

I Tried to install csi but I’m having an issue somewhere along the line as after dropping the files in reaper resources and user plugs.
I open reaper and disable my midi device.
Options > preferences > Osc > add new > csi >
This is where it goes wrong
I don’t get a homepage like in the you tube videos, come unstuck and thought it best to ask is this a common mistake and if so where have I gone wrong?
Thanks

Windows 11
Akai midimix

[Cragster]

Having some trouble understanding the broadcast/receive. Do all surfaces automatically broadcast but not receive and receive needs to be turned on or do they all broadcast and receive and receive needs to be turned off with the ToggleShouldReceive actions ??
Thanks

[Funkybot]

Originally Posted by Cragster

Having some trouble understanding the broadcast/receive. Do all surfaces automatically broadcast but not receive and receive needs to be turned on or do they all broadcast and receive and receive needs to be turned off with the ToggleShouldReceive actions ??
Thanks

You have to be on the latest experimental billed for the receive functionality to work. Once you have that, the default state of those toggle actions is off. So if you want the receive functionality turned on, you would add those OnInitilization. But you also need to tell it what device to broadcast to via the SetBroadcastGroup action. If you want to surfaces to mirror each other, see my post on the latest page about that.

[Dubhed60]

ref post 861
i got it working thanks

[Cragster]

Originally Posted by Funkybot

You have to be on the latest experimental billed for the receive functionality to work. Once you have that, the default state of those toggle actions is off. So if you want the receive functionality turned on, you would add those OnInitilization. But you also need to tell it what device to broadcast to via the SetBroadcastGroup action. If you want to surfaces to mirror each other, see my post on the latest page about that.

Thank you for the reply and info. Im just going to mess around with it a while and see if I can get the understanding of it.

[georges]

Can someone tell me if the following is possible using CSI 3.2? I have a QCon Pro G2 control surface which is working well with CSI. I purchase a used MPMidi controller (ver. 2A). MPMidi is basically a touchscreen display with 32 endless rotary knobs. I’d like to use the MPMidi knobs to control plugin settings and configure using the new learn feature. To begin, I created a MPMidi.mst file and defined the 32 Rotary encoders as Encoder7Bit which I think is correct based on the CSI documentation and using a midi monitor to view the values the encoders send. I’m confused about which ZON files I would need, and how they would be configured given the unit only has rotary encoders. I’m also assuming I’d have to setup broadcast/receive between the two devices but not sure how this should be configured either.

[Funkybot]

Originally Posted by georges

Can someone tell me if the following is possible using CSI 3.2? I have a QCon Pro G2 control surface which is working well with CSI. I purchase a used MPMidi controller (ver. 2A). MPMidi is basically a touchscreen display with 32 endless rotary knobs. I’d like to use the MPMidi knobs to control plugin settings and configure using the new learn feature. To begin, I created a MPMidi.mst file and defined the 32 Rotary encoders as Encoder7Bit which I think is correct based on the CSI documentation and using a midi monitor to view the values the encoders send. I’m confused about which ZON files I would need, and how they would be configured given the unit only has rotary encoders. I’m also assuming I’d have to setup broadcast/receive between the two devices but not sure how this should be configured either.

That's a cool device. Does it require any special host software or anything for the displays? The displays are my biggest concern about it from a CSI-perspective as if there's anything proprietary happening, it may require new widgets. But let's put aside my display conjecture and pontificating for a moment...

If you just want to assign some FX params to the encoders, that's will be no problem.

• If you intend on using an FXMenu on the QCon to open FX on the MPMidi, that can be setup via broadcast/listen. But that's putting the cart before the horse so let's stick a pin in that.
  
• For now, I'd recommend using FocusedFX mapping on the surface just to get the FX maps working. Then once we've got some working FX zones, then we can loop back to broadcast/listen. The good news is that FocusedFX mapping is on by default. So once you get FX.zon's working, it's just a matter of opening the GUI and they'll just map. Once you get there, you're in a good place for broadcast/listen setup.
  
• Now, how to get the FX things going? We just need to understand the naming convention you used in your .mst. You could do Rotary1-32. Or RotaryA1-A8, B1-B8, C1-C8, D1-D8. Post your .mst and we can then get you setup with the necessary fx files.
  
• If you don't want to wait for us, check the wiki, and look at the FX Mappping, Automapping, Learn page. See if you can make out what's happening and apply it to your own setup: https://github.com/GeoffAWaddington/...d-Remap-Window

[georges]

Originally Posted by Funkybot

That's a cool device. Does it require any special host software or anything for the displays? The displays are my biggest concern about it from a CSI-perspective as if there's anything proprietary happening, it may require new widgets. But let's put aside my display conjecture and pontificating for a moment...

If you just want to assign some FX params to the encoders, that's will be no problem.

• If you intend on using an FXMenu on the QCon to open FX on the MPMidi, that can be setup via broadcast/listen. But that's putting the cart before the horse so let's stick a pin in that.
  
• For now, I'd recommend using FocusedFX mapping on the surface just to get the FX maps working. Then once we've got some working FX zones, then we can loop back to broadcast/listen. The good news is that FocusedFX mapping is on by default. So once you get FX.zon's working, it's just a matter of opening the GUI and they'll just map. Once you get there, you're in a good place for broadcast/listen setup.
  
• Now, how to get the FX things going? We just need to understand the naming convention you used in your .mst. You could do Rotary1-32. Or RotaryA1-A8, B1-B8, C1-C8, D1-D8. Post your .mst and we can then get you setup with the necessary fx files.
  
• If you don't want to wait for us, check the wiki, and look at the FX Mappping, Automapping, Learn page. See if you can make out what's happening and apply it to your own setup: https://github.com/GeoffAWaddington/...d-Remap-Window

Hey Funkybot, thanks for the information. If I understand the controller, it's running software call UPDD damond and UPDD commander along with touchscreen software from Touch Base called MP ControllerByte.

I was able to get some basic mappings going on the QCon so I think that part is working. In the MST file I'm using Rotary1-32 (MST file attached as .TXT).

[Funkybot]

Originally Posted by georges

Hey Funkybot, thanks for the information. If I understand the controller, it's running software call UPDD damond and UPDD commander along with touchscreen software from Touch Base called MP ControllerByte.

I was able to get some basic mappings going on the QCon so I think that part is working. In the MST file I'm using Rotary1-32 (MST file attached as .TXT).

Ok, first question:

Why are you using that...

Widget Rotary1 RotaryWidgetClass
	Encoder7Bit b0 07 7f
	FB_Encoder b0 07 7f
WidgetEnd

...as opposed to this?

Widget Rotary1 RotaryWidgetClass
	Encoder b0 07 7f
	FB_Encoder b0 07 7f
WidgetEnd

Encoder7Bit was created for certain X-Touch devices. Just want to make sure that its use was intentional.

For zone files, create a MP_MIDI folder under CSI zones and add the following:

Home.zon

Zone Home
OnInitialization ToggleEnableFocusedFXMapping   // I'm pretty sure this got changed to off by default in CSI v3.2 so we want to turn it on.
    IncludedZones
        Buttons
    IncludedZonesEnd
    AssociatedZones
        LearnFXParams
    AssociatedZonesEnd
ZoneEnd

Buttons.zon (I'm just doing this so the IncludedZones under home aren't blank - this may not even be necessary).

Zone "Buttons"

// This is just a placeholder zone for now. May not even be needed.

ZoneEnd

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

LearnFXParams

Zone "LearnFXParams"
    SomeButton1          SaveLearnedFXParams

    SomeButton2          EraseLastTouchedControl
ZoneEnd

...That last one won't really do anything for now, but I just want to see if we can get the Auto-map functionality going with the SurfaceFXLayout and FXLayout Zones.

Once you've created those zone files in the MP_MIDI zone folder, just assign that in Reaper and focus an FX. Hopefully it just auomaps. If not, maybe comment out the OnInitialization line in the home.zon and try again.