Control Surface Integration (CSI) Technical Feature Discussion - Page 240

cemark · 06-22-2020, 01:40 PM

I want them to work on one and the same channel -- not the selected one but the one that goes with TrackNavigator.

The weird thing is that focus jumps: First time I press Arm it operates on track 1. But when I press it agian, it operates on the selected channel. Werird, huh?

Funkybot · 06-22-2020, 01:48 PM

Quote:

Originally Posted by cemark

I want them to work on one and the same channel -- not the selected one but the one that goes with TrackNavigator.

The weird thing is that focus jumps: First time I press Arm it operates on track 1. But when I press it agian, it operates on the selected channel. Werird, huh?

Can you post your Faderport.mst file?

cemark · 06-22-2020, 01:50 PM

Code:

/ *************************************************************
/ Author: Johan Steensland
/ Reaper forum alias: Cemark
/
/ Filename: FPv2.mst
/ Date: June 2020, v1
/
/ Purpose: mst file that defines the capabilities of the
/          surface Faderport v2
/
/
/ Use: You may use this file for all purposes except commercial
/
/ Comment: Make sure your surface is set to Studio One mode.
/ **************************************************************

/ ********** Upper section
/ **************************
Widget Solo1
	Press 90 08 7f
	FB_TwoState 90 08 7f 90 08 00
WidgetEnd

Widget Mute1
	Press 90 10 7f
	FB_TwoState 90 10 7f 90 10 00
WidgetEnd

Widget Arm1
	Press 90 00 7f
	FB_TwoState 90 00 7f 90 00 00
WidgetEnd

Widget Shift
	Press 90 46 7f 90 46 00
WidgetEnd


Widget Bypass1
	Press 90 03 7f
	FB_TwoState 90 03 7f 90 03 00
WidgetEnd

Widget Touch
	Press 90 4d 7f
	FB_TwoState 90 4d 7f 90 4d 00
WidgetEnd

Widget Write
	Press 90 4b 7f
	FB_TwoState 90 4b 7f 90 4b 00
WidgetEnd

Widget Read
	Press 90 4a 7f
	FB_TwoState 90 4a 7f 90 4a 00
WidgetEnd



/ ************** Middle section
/ *******************************
Widget Prev
	Press 90 2E 7f
WidgetEnd

Widget Next
	Press 90 2F 7f
WidgetEnd

Widget RotaryPress1
	Press 90 20 7f 90 20 00
WidgetEnd

Widget Rotary1
	Encoder b0 10 7f [ < 41 > 01 ]
	FB_Encoder b0 10 7f
WidgetEnd



/ ************** Lower section
/ *******************************

Widget Link
	Press 90 05 7f
	FB_TwoState 90 05 7f 90 05 00
WidgetEnd

Widget Pan
	Press 90 2a 7f
	FB_TwoState 90 2a 7f 90 2a 00
WidgetEnd

Widget Channel
	Press 90 36 7f
	FB_TwoState 90 36 7f 90 36 00
WidgetEnd

Widget Scroll
	Press 90 38 7f
	FB_TwoState 90 38 7f 90 38 00
WidgetEnd


Widget Master
	Press 90 3a 7f
	FB_TwoState 90 3a 7f 90 3a 00
WidgetEnd

Widget Click
	Press 90 3b 7f
	FB_TwoState 90 3b 7f 90 3b 00
WidgetEnd

Widget Section
	Press 90 3c 7f
	FB_TwoState 90 3c 7f 90 3c 00
WidgetEnd

Widget Marker
	Press 90 3d 7f
	FB_TwoState 90 3d 7f 90 3d 00
WidgetEnd



/ ***************** Transport
/ ****************************
Widget Rewind
	Press 90 5b 7f
	FB_TwoState 90 5b 7f 90 5b 00
WidgetEnd

Widget FastForward
	Press 90 5c 7f
	FB_TwoState 90 5c 7f 90 5c 00
WidgetEnd

Widget Stop
	Press 90 5d 7f
	FB_TwoState 90 5d 7f 90 5d 00
WidgetEnd

Widget Play
	Press 90 5e 7f
	FB_TwoState 90 5e 7f 90 5e 00
WidgetEnd

Widget Record
	Press 90 5f 7f
	FB_TwoState 90 5f 7f 90 5f 00
WidgetEnd

Widget Cycle
	Press 90 56 7f
	FB_TwoState 90 56 7f 90 56 00
WidgetEnd




/ ***************** Fader
/ ****************************

Widget Fader1
	Fader14Bit e0 7f 7f
	FB_Fader14Bit e0 7f 7f
WidgetEnd

Widget FaderTouch1
	Press 90 68 7f 90 68 00
WidgetEnd

Funkybot · 06-22-2020, 02:18 PM

Code:

Zone Home
	IncludedZones
		"Track Control|1-1"
	IncludedZonesEnd
ZoneEnd

/ **********************
/ Track Control handles everything about a track
/ ***********************
Zone "Track Control|1-1"
	TrackNavigator
	Arm|  				TrackRecordArm
	Solo|  				TrackSolo
	Mute|				TrackMute
	Fader|	  			TrackVolume
	FaderTouch|  			TrackTouch	
	Rotary|				TrackPan

ZoneEnd

Look at the strikethrough text and remove it in your .zon file. The 1-1 gets declared once in the home zone/included zones. Shouldn't be declared again in the actual zone. Try that.

cemark · 06-22-2020, 09:49 PM

Tried that -- no difference.

First press on Arm: Track 1 gets armed.

Second press: The selected track gets armed. This also move fader focus to this track.

Third press: The selected track gets un-armed.

Funny thing is: If I start with SOLO instead of Arm, it does not jump to the selected track. Focus stays on track 1.

Also, the rotary does not work at all :-(

cemark · 06-22-2020, 10:11 PM

Working in parallel on getting the encoder to work (Reaper is ignoring it). This is from the wiki (turns out I have the same code):

Code:

Widget Rotary1
	Encoder b0 10 7f [ < 41 > 01 ]
	FB_Encoder b0 10 7f
WidgetEnd

Coppla questions here.

1. My rotary actually outputs accelleration. However, as long as I turn the knob slowly with just 1 tick at the time, it acts like a simple rotary and outputs exactly what is described in the text on the wiki. In principle, my rotary should work with this code?

2. What is the hex 7f in the example? My rotary does not output that (and I get the impression from the example on the wiki that it really shouldn't). Can it be something else for my rotary?

3. How can I detect exactly what accelleration codes my rotary outputs? I turn the knob and look at MIDI OX and see a bunch of numbers. For CW they seem to be between 01 and 3f. But does it skip numbers? Is 3f really the largest number etc?

Thanks!

cemark · 06-23-2020, 12:18 AM

OK, baby steps forward ...

I got the rotary to work, by strippiong the code down to:

Code:

Widget Rotary1
	Encoder b0 10 7f
WidgetEnd

However, question #3 above still remains: How do I determine exactly what my rotary outputs? Of course I want to use its full capabilities.

cemark · 06-23-2020, 12:24 AM

Quote:

Originally Posted by cemark

Tried that -- no difference.

First press on Arm: Track 1 gets armed.

Second press: The selected track gets armed. This also move fader focus to this track.

Third press: The selected track gets un-armed.

Funny thing is: If I start with SOLO instead of Arm, it does not jump to the selected track. Focus stays on track 1.

Also, the rotary does not work at all :-(

OK, the focus-jump only occurs with the button Arm. Solo, Mute, fader and pan does NOT cause a jump to the selected track.

What's up with Arm???

Here's how it's defined:

Code:

Widget Arm1
	Press 90 00 7f
	FB_TwoState 90 00 7f 90 00 00
WidgetEnd

And here's the zone:

Code:

Zone "Track Control|"
	TrackNavigator
	Arm|  				TrackRecordArm
	Solo|  				TrackSolo
	Mute|				TrackMute
	Fader|	  			TrackVolume
	FaderTouch|  			TrackTouch	
	Rotary|				TrackPan

ZoneEnd

spkr4thdd · 06-23-2020, 05:36 AM

Quote:

Originally Posted by cemark

OK, baby steps forward ...

I got the rotary to work, by strippiong the code down to:

Code:

Widget Rotary1
	Encoder b0 10 7f
WidgetEnd

However, question #3 above still remains: How do I determine exactly what my rotary outputs? Of course I want to use its full capabilities.

There was a whole load of work done by FunkyBot, MixMonkey, Geoff and others about this some time ago. I think they used MidiOX and similar tools to record the MIDI messages and translate it into something CSI can use in a simple format.

The discussion was somewhere around this point in the thread.

Lomeos · 06-23-2020, 05:38 AM

Hi all,

I've been trying to work with csi / x-touch one for a while now. I notice some serious audio issues after a while when having many tracks. This is probably a performance issue - my laptop is quite a few years old.

After a while, crackling noise becomes louder through my audio interface. When I unplug and plug the audio interface, it is gone for a while. If I set the latency a bit higher, it is gone for a wile, but it always returns.

If I don't connect the x-touch one, no issues at all.
If I connect the x-touch one like Behringer suggests (setting the device to Reaper), also no problem, apart from that most things don't work as I would like. (the reason I switched to CSI)

So I guess that more or less narrows it down to some performance issues with CSI on my setup.

I really like the way CSI allows me to customize the device, but with the noise issues it now functions mostly as a paper weight.

I updated all the drivers for the audio interface and have the latest firmware on the X-touch.

Anyone else have these issues and maybe a solution?

Cheers

Edit: updated with computer specs.

Laptop: HP Envy, Core i7-4700MQ @ 2.4Ghz. 8Gb ram, 500Gb SSD harddrive
Os: Windows 10. Reaper is always the latest.

spkr4thdd · 06-23-2020, 05:44 AM

Quote:

Originally Posted by Lomeos

Hi all,

I've been trying to work with csi / x-touch one for a while now. I notice some serious audio issues after a while when having many tracks. This is probably a performance issue - my laptop is quite a few years old.

After a while, crackling noise becomes louder through my audio interface. When I unplug and plug the audio interface, it is gone for a while. If I set the latency a bit higher, it is gone for a wile, but it always returns.

If I don't connect the x-touch one, no issues at all.
If I connect the x-touch one like Behringer suggests (setting the device to Reaper), also no problem, apart from that most things don't work as I would like. (the reason I switched to CSI)

So I guess that more or less narrows it down to some performance issues with CSI on my setup.

I really like the way CSI allows me to customize the device, but with the noise issues it now functions mostly as a paper weight.

I updated all the drivers for the audio interface and have the latest firmware on the X-touch.

Anyone else have these issues and maybe a solution?

Cheers

It would help to know what kind of laptop/spec you're running, OS, Reaper versions, RAM, etc... It seems odd that CSI would cause performance issues, it's a really 'light' extension to Reaper?

Lomeos · 06-23-2020, 05:53 AM

Quote:

Originally Posted by spkr4thdd

It would help to know what kind of laptop/spec you're running, OS, Reaper versions, RAM, etc... It seems odd that CSI would cause performance issues, it's a really 'light' extension to Reaper?

Ah yes:
Laptop: HP Envy, Core i7-4700MQ @ 2.4Ghz. 8Gb ram, 500Gb SSD harddrive
Os: Windows 10. Reaper is always the latest.

My typical projects have between 20 and 40 tracks

spkr4thdd · 06-23-2020, 06:04 AM

Quote:

Originally Posted by Lomeos

Ah yes:
Laptop: HP Envy, Core i7-4700MQ @ 2.4Ghz. 8Gb ram, 500Gb SSD harddrive
Os: Windows 10. Reaper is always the latest.

My typical projects have between 20 and 40 tracks

That seems odd tbh? What audio interface are you using?

It sounds more like it's a possible conflict with USB devices rather than CSI itself? The other options use the standard MIDI config of Reaper whereas CSI 'takes over' that and manages it internally (or that's how I see it? Geoff might correct me).

Funkybot · 06-23-2020, 07:37 AM

Quote:

Originally Posted by cemark

OK, baby steps forward ...

I got the rotary to work, by strippiong the code down to:

Code:

Widget Rotary1
	Encoder b0 10 7f
WidgetEnd

However, question #3 above still remains: How do I determine exactly what my rotary outputs? Of course I want to use its full capabilities.

Read the encoders section of the wiki:

https://github.com/malcolmgroves/rea.../wiki/Encoders

There are 4 flavors of encoders:

1. MCU
2. MCU, No Acceleration
3. Encoders with Discrete steps
4. Encoders with Continuous steps

Your best bet to figure out which will work is:

1. Open a MIDI logger like MIDI OX
2. Open the device, turn on logging
3. Turn the encoder clockwise really slow

What's the value?

4. Turn the encoder clockwise really fast

Did the values change? If yes, you have either type 3 or 4. If no, you have type 1 or 2.

If type 1 or 2 (values don't change), start with type 1. If it works. Stop there. If not try type 2. If your surface transmits 41 when decreasing and 01 when increasing then add this to your widget. Encoder b0 10 7f [ < 41 > 01 ]. If that doesn't work, stick to type 1.

If type 3 or 4, then you should create a list* of all the unique encoder steps when turning clockwise, and another list of all the encoder steps when turning counter-clockwise. If there are gaps in the values transmitted (like say value 48 is missing), then you have an encoder with discrete steps. If no gaps, you have an encoder with continuous steps. Use the appropriate syntax in your widget (see Wiki).

*What I found works is doing a bunch clockwise of turns at many different speeds. Get a HUGE list of MIDI values. Copy and paste those into Excel. Using a combination of Text to Columns and Remove Duplicates clean up the list then perform a Sort on what remains. What's left over are the unique values. Will be easy to spot if there are any missing values. Then repeat the process for counterclockwise values.

Funkybot · 06-23-2020, 07:40 AM

Quote:

Originally Posted by cemark

OK, the focus-jump only occurs with the button Arm. Solo, Mute, fader and pan does NOT cause a jump to the selected track.

What's up with Arm???

Here's how it's defined:

Code:

Widget Arm1
	Press 90 00 7f
	FB_TwoState 90 00 7f 90 00 00
WidgetEnd

And here's the zone:

Code:

Zone "Track Control|"
	TrackNavigator
	Arm|  				TrackRecordArm
	Solo|  				TrackSolo
	Mute|				TrackMute
	Fader|	  			TrackVolume
	FaderTouch|  			TrackTouch	
	Rotary|				TrackPan

ZoneEnd

I have no idea why Arm wouldn't work based on that example. Are you sure you don't have a second version of Arm assigned somewhere else in the .zon file? I'd look for a double assignment or something like that. Can you post the full .zon contents?

cemark · 06-23-2020, 07:55 AM

Quote:

Originally Posted by Funkybot

*What I found works is doing a bunch clockwise of turns at many different speeds. Get a HUGE list of MIDI values. Copy and paste those into Excel. Using a combination of Text to Columns and Remove Duplicates clean up the list then perform a Sort on what remains. What's left over are the unique values. Will be easy to spot if there are any missing values. Then repeat the process for counterclockwise values.

THIS! I have done everything else on your list. I know it has accelleration and I also know between which values. What I don't know is what values it skips. And since the range is huge, it's very hard to eyeball it. But I'll try with Excel.

cemark · 06-23-2020, 07:57 AM

Funkybot, here's mu zon-file (Arm is NOT double defined):

Code:

/ *************************************************************
/ Author: Johan Steensland
/ Reaper forum alias: Cemark
/
/ Filename: FPv2.zon
/ Date: June 2020, v1
/
/ Purpose: Zone file that defines my personal CSI bindings for
/          my surface Faderport v2
/
/ Uses: Bindings for my favorite plugins can be found in the
/       files "fx_plugin.zon"
/
/ Use: You may use this file for all purposes except commercial
/
/ Comment: This Zone file follows the syntax/semantics defined in 
/          the CSI Beta build xxx
/
/ Comment: After edit, use Reaper action: 
/		Control surface: Refresh all surfaces 41743
/ **************************************************************


Zone Home
	Shift 	Shift
	Prev	TrackBank  "-1"
	Next	TrackBank  "+1"
	IncludedZones
		"Extended Transport|"
		"Track Control|1-1"
	IncludedZonesEnd
ZoneEnd

/ **********************
/ Extended Transport handles transport, markers, regions, zoom and scroll
/ ***********************
Zone "Extended Transport|"
	Rewind 		Rewind
	FastForward	FastForward
	Stop 		Stop
	Play 		Play
	Record 		Record
	Cycle		Reaper "1068" // Toggle Repeat
/ The lines below are copied from a previous version, created by forum member Airon
/ The ID:s are checked against my Reaper/PC!
	Section		Reaper "40174" //Markers: Insert region from time selection, OK
	Shift+Section	Reaper "40306" //Markers: Insert region from time selection and edit..., OK
	Marker 		Reaper "40157" //Insert marker, OK
	Shift+Marker 	Reaper "40171" //insert marker and edit, OK
	Click 		Reaper 	"40364" // Toggle metronome, OK
/ Back to my code
	Scroll		GoZone	"Zoom|"
	Zoom		GoZone	"Zoom Vertically"
ZoneEnd

/ **********************
/ The following two zones just map the rotary to horizontal/vertical zoom
/ ***********************
Zone "Zoom|"
	Rotary1		Reaper	"990" // Standard Reaper mousewheel zoom
	Zoom		GoZone Home
ZoneEnd

Zone "Vertical Zoom"
	Rotary1		Reaper	"991" // Zoom vertically
	Zoom		GoZone Home
	Shift+Zoom	GoZone Home
ZoneEnd

/ **********************
/ Track Control handles everything about a track
/ ***********************
Zone "Track Control|"
	TrackNavigator
	Arm|  				TrackRecordArm
	Solo|  				TrackSolo
	Mute|				TrackMute
	Fader|	  			TrackVolume
	FaderTouch|  			TrackTouch	
	Rotary|				TrackPan // This works ...
/	Rotary|		Reaper	"990" // Standard Reaper mousewheel zoom. ... while this does not.
ZoneEnd


/ **********************
/ Master just maps the fader to the master in Reaper
/ ***********************
Zone "Master|"
	MasterTrackNavigator
	Fader 	TrackVolume
	Master	GoZone Home
ZoneEnd

dr_After · 06-23-2020, 08:16 AM

How can I toggle button light (in my case: Instrument on Behringer X-Touch)? I assigned an action and it works ok but the button is lit all the time.

Funkybot · 06-23-2020, 08:23 AM

Quote:

Originally Posted by cemark

Funkybot, here's mu zon-file (Arm is NOT double defined):

Code:

/ *************************************************************
/ Author: Johan Steensland
/ Reaper forum alias: Cemark
/
/ Filename: FPv2.zon
/ Date: June 2020, v1
/
/ Purpose: Zone file that defines my personal CSI bindings for
/          my surface Faderport v2
/
/ Uses: Bindings for my favorite plugins can be found in the
/       files "fx_plugin.zon"
/
/ Use: You may use this file for all purposes except commercial
/
/ Comment: This Zone file follows the syntax/semantics defined in 
/          the CSI Beta build xxx
/
/ Comment: After edit, use Reaper action: 
/		Control surface: Refresh all surfaces 41743
/ **************************************************************


Zone Home
	Shift 	Shift
	Prev	TrackBank  "-1"
	Next	TrackBank  "+1"
	IncludedZones
		"Extended Transport|"
		"Track Control|1-1"
	IncludedZonesEnd
ZoneEnd

/ **********************
/ Extended Transport handles transport, markers, regions, zoom and scroll
/ ***********************
Zone "Extended Transport|"
	Rewind 		Rewind
	FastForward	FastForward
	Stop 		Stop
	Play 		Play
	Record 		Record
	Cycle		Reaper "1068" // Toggle Repeat
/ The lines below are copied from a previous version, created by forum member Airon
/ The ID:s are checked against my Reaper/PC!
	Section		Reaper "40174" //Markers: Insert region from time selection, OK
	Shift+Section	Reaper "40306" //Markers: Insert region from time selection and edit..., OK
	Marker 		Reaper "40157" //Insert marker, OK
	Shift+Marker 	Reaper "40171" //insert marker and edit, OK
	Click 		Reaper 	"40364" // Toggle metronome, OK
/ Back to my code
	Scroll		GoZone	"Zoom|"
	Zoom		GoZone	"Zoom Vertically"
ZoneEnd

/ **********************
/ The following two zones just map the rotary to horizontal/vertical zoom
/ ***********************
Zone "Zoom|"
	Rotary1		Reaper	"990" // Standard Reaper mousewheel zoom
	Zoom		GoZone Home
ZoneEnd

Zone "Vertical Zoom"
	Rotary1		Reaper	"991" // Zoom vertically
	Zoom		GoZone Home
	Shift+Zoom	GoZone Home
ZoneEnd

/ **********************
/ Track Control handles everything about a track
/ ***********************
Zone "Track Control|"
	TrackNavigator
	Arm|  				TrackRecordArm
	Solo|  				TrackSolo
	Mute|				TrackMute
	Fader|	  			TrackVolume
	FaderTouch|  			TrackTouch	
	Rotary|				TrackPan // This works ...
/	Rotary|		Reaper	"990" // Standard Reaper mousewheel zoom. ... while this does not.
ZoneEnd


/ **********************
/ Master just maps the fader to the master in Reaper
/ ***********************
Zone "Master|"
	MasterTrackNavigator
	Fader 	TrackVolume
	Master	GoZone Home
ZoneEnd

I honestly have no idea why you're seeing such strange behavior with Arm. Nothing sticks out to me as incorrect there.

Let's try this:

1. Open MIDIOx
2. Hit Arm a few times

Does it output the same message each time? Maybe StudioOne mode does something weird wtih Arm? Does the message change with each press?

Otherwise...and I fully expect this will NOT make a difference, try renaming your widget from Arm1 to RecordArm1. Don't think that'll change anything but who knows.

Funkybot · 06-23-2020, 08:25 AM

Quote:

Originally Posted by dr_After

How can I toggle button light (in my case: Instrument on Behringer X-Touch)? I assigned an action and it works ok but the button is lit all the time.

This depends entirely on how Reaper reports the state of that particular action. If Reaper reports On/Off, the button will follow suit. If Reaper does not, the light will stay on.

In my X-TouchOne.mst I just ended up commenting out the FB line for those buttons to keep the lights in a constant off state versus a constant on state.

cemark · 06-23-2020, 08:29 AM

Funky, thanks for sticking with me!

The button output is stable (constant).

I tried renaming, but the jump is still there ... :-(

dr_After · 06-23-2020, 08:34 AM

Quote:

Originally Posted by Funkybot

This depends entirely on how Reaper reports the state of that particular action. If Reaper reports On/Off, the button will follow suit. If Reaper does not, the light will stay on.

In my X-TouchOne.mst I just ended up commenting out the FB line for those buttons to keep the lights in a constant off state versus a constant on state.

Thank you for a quick answer!

Funkybot · 06-23-2020, 09:12 AM

Cemark,

Let's keep things in this thread to consolidate. Backup your current .zon file as to not lose it then try out this zone...what works what doesn't?

Code:

Zone Home
	IncludedZones
		"Global|"
		"Track Control|1-1"
	IncludedZonesEnd
ZoneEnd

Zone "Global|"
	Shift 		Shift
	Prev		TrackBank  "-1"
	Next		TrackBank  "+1"
	Rewind 		Rewind
	FastForward	FastForward
	Stop 		Stop
	Play 		Play
	Record 		Record
	Cycle		Reaper "1068" 	// Toggle Repeat
	Section		Reaper "40174" 	//Markers: Insert region from time selection, OK
	Shift+Section	Reaper "40306" 	//Markers: Insert region from time selection and edit..., OK
	Marker 		Reaper "40157"	//Insert marker, OK
	Shift+Marker 	Reaper "40171" 	//insert marker and edit, OK
	Click 		Reaper 	"40364" // Toggle metronome, OK
	Master		GoZone 	"Master"
ZoneEnd

Zone "Track Control|"
	TrackNavigator
	Arm| 		TrackRecordArm
	Solo|  		TrackSolo
	Mute|		TrackMute
	Fader|	  	TrackVolume
	FaderTouch|  	TrackTouch	
	Rotary|		TrackPan
	Scroll		GoZone	"Zoom"
	Zoom		GoZone	"Vertical Zoom"
ZoneEnd

Zone "Master"
	MasterTrackNavigator
	Fader1 		TrackVolume
	Master		GoZone Home
ZoneEnd

Zone "Zoom"
	Rotary1		Reaper	"990" // Standard Reaper mousewheel zoom
	Scroll		GoZone Home
ZoneEnd

Zone "Vertical Zoom"
	Rotary1		Reaper	"991" // Zoom vertically
	Zoom		GoZone Home
ZoneEnd

I noticed a few things in your .zon that stuck out as odd or incorrect:

1. You didn't seem to have a way to enter the Master .zon. I don't know how the unit works, but if you're using Fader1 for MasterFader, then how would CSI know to replace Fader1 with the selected track with the master track.

2. You had one zone named "Vertical Zoom" in the GoZone command, but the zone was actually named "Zoom Vertically." You need to be consistent.

3. You used Scroll to enter the "Zoom" zone, but then used the Zoom button to go "Home" but the Zoom button may be assigned to something else. I used Scroll go return Home from the Zoom zone.

4. I cleaned up the actions that you said weren't working. Let's start small...

5. I renamed one of the zones and put the trackbank buttons and other buttons there, rather than having them directly in the Home zone.

6. I moved the GoZone Zoom into the TrackControl zone. The reason? Whenever using PanWidth in the MCU.zon, the GoZone action to enter PanWidth was always in the same zone as the Pan.

And note: I mess things up in CSI .zon files all the time so I'm not saying everything here will work 100%. In fact, I kind of suspect things won't work in this. But lets use this as a starting point for troubleshooting.

Pompeysie · 06-23-2020, 09:12 AM

[apologies for the terrible pun].

Can anyone tell me why this code for controlling a fader, specified on the wiki doesn't work:

Widget Fader
Fader14Bit e0 7f 7f e0 00 00
WidgetEnd

But this does:

Widget Fader
Fader14Bit e0 7f 7f
FB_Fader14Bit e0 7f 7f
WidgetEnd

Also, even those the second piece of code above works, there is a discrepancy between the position of the fader in Reaper and my surface fader (FaderPort V2)?

Funkybot · 06-23-2020, 09:26 AM

Quote:

Originally Posted by Pompeysie

[apologies for the terrible pun].

Can anyone tell me why this code for controlling a fader, specified on the wiki doesn't work:

Widget Fader
Fader14Bit e0 7f 7f e0 00 00
WidgetEnd

But this does:

Widget Fader
Fader14Bit e0 7f 7f
FB_Fader14Bit e0 7f 7f
WidgetEnd

Also, even those the second piece of code above works, there is a discrepancy between the position of the fader in Reaper and my surface fader (FaderPort V2)?

My guess? Maybe the syntax changed.

Geoff, if yes, please confirm and I'll update the Wiki. I haven't been using the second half in my faders and they work.

Thanks for pointing this out Pompeysie!

cemark · 06-23-2020, 09:42 AM

Quote:

Originally Posted by Funkybot

Cemark,

Let's keep things in this thread to consolidate. Backup your current .zon file as to not lose it then try out this zone...what works what doesn't?

Code:

Zone Home
	IncludedZones
		"Global|"
		"Track Control|1-1"
	IncludedZonesEnd
ZoneEnd

Zone "Global|"
	Shift 		Shift
	Prev		TrackBank  "-1"
	Next		TrackBank  "+1"
	Rewind 		Rewind
	FastForward	FastForward
	Stop 		Stop
	Play 		Play
	Record 		Record
	Cycle		Reaper "1068" 	// Toggle Repeat
	Section		Reaper "40174" 	//Markers: Insert region from time selection, OK
	Shift+Section	Reaper "40306" 	//Markers: Insert region from time selection and edit..., OK
	Marker 		Reaper "40157"	//Insert marker, OK
	Shift+Marker 	Reaper "40171" 	//insert marker and edit, OK
	Click 		Reaper 	"40364" // Toggle metronome, OK
	Master		GoZone 	"Master"
ZoneEnd

Zone "Track Control|"
	TrackNavigator
	Arm| 		TrackRecordArm
	Solo|  		TrackSolo
	Mute|		TrackMute
	Fader|	  	TrackVolume
	FaderTouch|  	TrackTouch	
	Rotary|		TrackPan
	Scroll		GoZone	"Zoom"
	Zoom		GoZone	"Vertical Zoom"
ZoneEnd

Zone "Master"
	MasterTrackNavigator
	Fader1 		TrackVolume
	Master		GoZone Home
ZoneEnd

Zone "Zoom"
	Rotary1		Reaper	"990" // Standard Reaper mousewheel zoom
	Scroll		GoZone Home
ZoneEnd

Zone "Vertical Zoom"
	Rotary1		Reaper	"991" // Zoom vertically
	Zoom		GoZone Home
ZoneEnd

I noticed a few things in your .zon that stuck out as odd or incorrect:

1. You didn't seem to have a way to enter the Master .zon. I don't know how the unit works, but if you're using Fader1 for MasterFader, then how would CSI know to replace Fader1 with the selected track with the master track.

2. You had one zone named "Vertical Zoom" in the GoZone command, but the zone was actually named "Zoom Vertically." You need to be consistent.

3. You used Scroll to enter the "Zoom" zone, but then used the Zoom button to go "Home" but the Zoom button may be assigned to something else. I used Scroll go return Home from the Zoom zone.

4. I cleaned up the actions that you said weren't working. Let's start small...

5. I renamed one of the zones and put the trackbank buttons and other buttons there, rather than having them directly in the Home zone.

6. I moved the GoZone Zoom into the TrackControl zone. The reason? Whenever using PanWidth in the MCU.zon, the GoZone action to enter PanWidth was always in the same zone as the Pan.

And note: I mess things up in CSI .zon files all the time so I'm not saying everything here will work 100%. In fact, I kind of suspect things won't work in this. But lets use this as a starting point for troubleshooting.

1. No, I had cut that part out because it did not work, and I was testing stuff.

2. Oooops

3. Yes, I noticed the inconsistancies. I was changing buttons ...

4. I REALLY appreciate your help, and I'm trying everything you suggest. But it this would make a difference, something is very wrong ...

Don't be afraid to mess up -- we're debugging!

Oh, and your file made no difference whatsoever :-(

Pompeysie · 06-23-2020, 09:46 AM

Quote:

Originally Posted by Funkybot

My guess? Maybe the syntax changed.

Geoff, if yes, please confirm and I'll update the Wiki. I haven't been using the second half in my faders and they work.

Thanks for pointing this out Pompeysie!

Ahh, ok, thanks.

Any thoughts on the mismatch between unity on the fader in Reaper and on the surface?

Funkybot · 06-23-2020, 09:51 AM

Quote:

Originally Posted by cemark

Oh, and your file made no difference whatsoever :-(

Ok, so what still works and what doesn't? Let's summarize and keep it short like...

Works:
Fader
Pan
Most Buttons

Doesn't Work (and what happens):
Arm (works on first press, second press Arms selected track?)
etc...

Funkybot · 06-23-2020, 09:54 AM

Quote:

Originally Posted by Pompeysie

Ahh, ok, thanks.

Any thoughts on the mismatch between unity on the fader in Reaper and on the surface?

I **believe** I remember this coming up in the past. If I recall correctly, Reaper lets you configure the maximum fader volume. Example: +12db. But different surfaces use different max fader volumes. Example: the Avid Artist Mix is +12db, the X-Touch One is +10db.

Locate the Reaper preference and adjust it to match your surface. Does that fix it?

cemark · 06-23-2020, 09:55 AM

Quote:

Originally Posted by Funkybot

Ok, so what still works and what doesn't? Let's keep it short...

Works:
Fader
Pan
Most Buttons

Doesn't Work (and what happens):
Arm (works on first press, second press Arms selected track?)
etc...

Works: Fader, pan, solo, mute, next/prev track, transport, markers and regions.

NO go: Arm (jumps as described), zoom, scroll

I have double checked with the CSI edit mode: Arm sends the same msg, but the second time pressed, weget the famous jump.

cemark · 06-23-2020, 09:58 AM

Oh, and Master suddenly has come to life!

So, I was wrong: Your file DID make a difference for the better

Funkybot · 06-23-2020, 10:03 AM

Quote:

Originally Posted by cemark

Works: Fader, pan, solo, mute, next/prev track, transport, markers and regions.

NO go: Arm (jumps as described), zoom, scroll

I have double checked with the CSI edit mode: Arm sends the same msg, but the second time pressed, weget the famous jump.

Do me a favor and humor me...go into MCU mode on the surface. Double check the widget used for Arm. Does it work?

I can't emphasize this enough...CSI supports MCU, MIDI, OSC, and EuCon. If "Studio One mode" on the FaderPort is using anything proprietary....then it's just not officially supported by CSI. I wouldn't be surprised if this causes weird behavior. That's why I keep recommending MCU mode. Frankly, I just feel like your barking up the wrong tree from the get-go. I know you said MCU mode is weird...but I'd rather troubleshoot those issues than deal with any potentially proprietary modes.

I believe you said you don't want to use MCU mode because button assignments change. That may be totally normal. Here's how MCU mode works on the X-Touch One - it simulates 8 virtual tracks. So Fader1 exists, and then you hit NexTrack and you're on widget Fader2, which has a different assignment. The Mute buttons go from Mute1 up to Mute8 with different assignments, same for Solo, TrackArm, FaderTouch, Rotary, etc.

So my advice at this point: try MCU mode out. Use the MCU.mst, update your .zon, and we'll try to get you sorted out in that mode. The one we know **should** work.

poetnprophet · 06-23-2020, 10:05 AM

Hello everyone. I took a forum hiatus since March. Whew!

Ok, what did I miss here in CSI? Any cool new features in the last few months?

Hope everyone is doing ok

Funkybot · 06-23-2020, 10:11 AM

Quote:

Originally Posted by cemark

Oh, and Master suddenly has come to life!

So, I was wrong: Your file DID make a difference for the better

Closer!

cemark · 06-23-2020, 10:12 AM

There are three MCU modes: Logic, Live and Cubase. Which one should I choose?

cemark · 06-23-2020, 10:18 AM

Just tested Cubase MCU mode. The jumping still occurs.

Funkybot · 06-23-2020, 10:18 AM

Quote:

Originally Posted by cemark

There are three MCU modes: Logic, Live and Cubase. Which one should I choose?

Let's use Cubase mode. There are a few buttons that have no function in Logic and Live mode that look like they work in Cubase mode.

Funkybot · 06-23-2020, 10:38 AM

Quote:

Originally Posted by cemark

Just tested Cubase MCU mode. The jumping still occurs.

That's ok, this is at least a starting point. MCU is a well documented and established standard. So if the FaderPort truly works with MCU, I'm confident that we can sort through the issues. With "Studio One Mode" I'm way less confident. Remember: there are dozens of us who frequent this forum using many MCU devices and they work with CSI. We'll get it sorted.

So for trouble-shooting, we're almost starting from scratch (but not quite):

1. Backup your current .mst and .zon files (we can always go back)
2. Create a new .mst file called "FaderPort2MCU.mst" or something - paste the contents of the MCU.mst into that new .mst file
3. Create a new file called FaderPort2MCU.zon (or something like that)
4. Paste the below .zon file in there...

Code:

Zone Home
	OnTrackSelection MapSelectedTrackSendsToWidgets
	IncludedZones
		"Buttons|"
		"Channel|1-1"
		"MasterChannel|"
	IncludedZonesEnd
ZoneEnd

Zone "Global|"
	Shift 		Shift
	Prev		TrackBank  "-1"
	Next		TrackBank  "+1"
	Rewind 		Rewind
	FastForward	FastForward
	Stop 		Stop
	Play 		Play
	Record 		Record
	Cycle		Reaper "1068" 	// Toggle Repeat
	Section		Reaper "40174" 	//Markers: Insert region from time selection, OK
	Shift+Section	Reaper "40306" 	//Markers: Insert region from time selection and edit..., OK
	Marker 		Reaper "40157"	//Insert marker, OK
	Shift+Marker 	Reaper "40171" 	//insert marker and edit, OK
	Click 		Reaper 	"40364" // Toggle metronome, OK
	Zoom		GoZone	"Vertical Zoom"
	Master		GoZone 	"Master"
ZoneEnd

Zone "Channel|"
	TrackNavigator
	RecordArm| 	TrackRecordArm
	Solo|  		TrackSolo
	Mute|		TrackMute
	Fader|	  	TrackVolume
	FaderTouch|  	TrackTouch	
	Rotary|		TrackPan
	RotaryPush| 	GoZone "PanWidth|"
ZoneEnd

Zone "Master|"
	MasterTrackNavigator
	MasterFader 	TrackVolume
	Master		GoZone Home
ZoneEnd

Zone "Pan|1-8"
	TrackNavigator
	Rotary| 	TrackPan "0"
	RotaryPush| 	GoZone PanWidth|
ZoneEnd

Zone "PanWidth|1-8"
	TrackNavigator
	Rotary| 	TrackPanWidth "1"
	RotaryPush| 	GoZone Pan|
ZoneEnd

Now, before we even launch Reaper, let's figure out what's going on in MCU Mode...

5. Open MIDI Ox
6. Open up the FaderPort2 in MCU mode and enable logging
7. Move fader 1 and note the address, do the same for Solo, Mute, etc.
8. On the surface, press the button to select the next channel and move the fader again. Did the fader address change? Did Solo and Mute addresses also change? Do these correspond to Solo1, Solo2, Fader1, Fader2, Mute1, Mute2 in the .mst file?

If yes, that's good. That means it works like the X-Touch One and Icon surfaces where it simulates 8 full MCU channels. This is expected. The MasterFader should also have a dedicated virtual fader in this mode with it's own unique address.

If no, report back on the messages you receive.

9. Now, hit the buttons on the FaderPort2. Locate the MIDI address in the MCU.mst file and note the widget name. Example: there's no MCU widget called scroll. So maybe that's mapped to F6 or something in the FaderPort's MCU implementation. So figure that out. What's the "Scroll" button's address? Does that address exist in the MCU.mst? If yes, make note of the widget name (you can even edit the Widget name in your .mst ). Maybe it makes sense to rename the widget in the .mst file to "Scroll" to help make zone creation easier.

Now you should be in a position to configure your surface.

cemark · 06-23-2020, 10:41 AM

I have tried all MCU modes and the behavior is the same.

Not so strange since they send the same midi msg. I get what you are saying about potential proprietary messages, but I think all modes output standard midi messages. Even if they were sending something else, Reaper/CSI is configured to listen to the midi?

I'm not trying to be unreasonable here or single minded. Working with the Studio One mode is the only choice that make sense, if your goal is to customize the surface. In MCU-mode I get access to less than half the functionality. For example, Shift outputs nothing, and Shift +ANYButton outputs nothing. There goes half the functionality. The remaining functionality will be hard to map out, because you really need to test all (or many) combinations and create widgets for all of them. From there to a zone file also feels a bit too much work for my taste.

So please, don't take my choice for Mode like I am stubborn or unreasoable, I just want to be able to get the best use of my unit.

poetnprophet · 06-23-2020, 10:45 AM

Quote:

Originally Posted by Funkybot

Let's use Cubase mode. There are a few buttons that have no function in Logic and Live mode that look like they work in Cubase mode.

I believe Logic Mode should be the "MCU" Mode, as Logic developed the MCU protocol originally.

One of my surfaces said that in the documentation, I forget which one.