Control Surface Integration (CSI) Technical Feature Discussion

[Geoff Waddington]

New build is (finally) up:
https://stash.reaper.fm/v/33037/CSI%20pre%20alpha.zip

It's actually a bit less functional than the last one:
Touch doesn't work
Cycle actions don't work
Automation is incomplete

However, this represents the architecture we will be using going forward, unless there is a big problem with it.

So have at 'er, and let me know.

Make sure you use the new CSI.ini, .rst, .axt, and .fxt files, there have been changes.

Don't forget to read the new CSI ReadMe, it has changed substantially.

[mschnell]

Originally Posted by studer58

Good to know, thanks Geoff. Only Achilles Heel seems to be lack of effects control for plugins

I suppose with CSI this should be able to be mended.

-Michael

[mschnell]

Originally Posted by Geoff Waddington

New build is (finally) up...

GREAT !!! Thanks a lot !

Do you think it makes sense to try it with XTouch Compact ?

-Michael

[Geoff Waddington]

Originally Posted by mschnell

GREAT !!! Thanks a lot !

Do you think it makes sense to try it with XTouch Compact ?

-Michael

Of course !!

Let me know what happens.

[barold]

Will try this with X-Touch Mini.

Excited that I might be able to use this unit, as truthfully it doesn't do what I need in any of my host applications. I envisioned something useful, and after a lot of farting around only came up with something quirky

[Nakedcityuk]

Ive got an M-Audio Projectmix
Is there anyway I can get the (flying) faders and pan to work with Reaper?

Im not much of a computer person, more a musician that just wants to record and mix (hence loving Reaper!)

Any help of the 'click here' variety would be VERY appreciated!

Groover

[Geoff Waddington]

Originally Posted by Nakedcityuk

Ive got an M-Audio Projectmix
Is there anyway I can get the (flying) faders and pan to work with Reaper?

Im not much of a computer person, more a musician that just wants to record and mix (hence loving Reaper!)

Any help of the 'click here' variety would be VERY appreciated!

Groover

With the unit off, hold down the Aux 2 button.

While still holding down Aux 2, power the unit up.

You should see it come up on Cubase mode, aka Mackie Control.

Now, you can install the CSI software and select MCU for the protocol.

[mschnell]

Originally Posted by Geoff Waddington

Of course !!
Let me know what happens.

For now I was able to successfully install it and successfully add "control Surface Integrator" to Reaper's "Control Surfaces" config menu, and use "Edit" on same

To find out how to use it, I edited a "Real Surface" and a "Page", and a "Virtual Surface" to the "MCU" options avilable, and will try it with the XControl in MCU mode.

I found that in the CSI "ReadMe.pdf" provided you use an Xcontrol Comnpact as an example picture

Anyway, up till now, I fail to understand the exact meaning of "page" in the pre-alpha manual.

OK: I suppose, finally, a page is a collection of settings which virtual control any control element of the real surface is to move (and is to be moved by with e.g. motor faders). And this (and the page switching "actions" is defined in the various initialization files.)

I suppose, as I right now defined just a single page in the edit menu, there will be no switching between pages yet.

....

OK. I put the XControl in "MC" mode (the MC LED is lit and the Motor faders return to zero when I move them), connected it to the PC via USB and started Reaper.

I now could set "Midi Input" and "Midi Output" of the "Real Surface" to "X-TOUCH-COMPACT" (and set the "template" to "MCU.rst" and enabled all monitoring).

When I now move a fader in Reaper the CSI Monitor Window pops up and shows Midi messages, but nothing happens on the XTouch (the MIDI IN" LED of the XTOUCH does not flash). When I move a fader of the XTOUCH I don't see midi messages in the Monitor window.

-Michael

[Geoff Waddington]

Originally Posted by mschnell

For now I was able to successfully install it and successfully add "control Surface Integrator" to Reaper's "Control Surfaces" config menu, and use "Edit" on same

To find out how to use it, I edited a "Real Surface" and a "Page", and a "Virtual Surface" to the "MCU" options avilable, and will try it with the XControl in MCU mode.

I found that in the CSI "ReadMe.pdf" provided you use an Xcontrol Comnpact as an example picture

Anyway, up till now, I fail to understand the exact meaning of "page" in the pre-alpha manual.

OK: I suppose, finally, a page is a collection of settings which virtual control any control element of the real surface is to move (and is to be moved by with e.g. motor faders). And this (and the page switching "actions" is defined in the various initialization files.)

I suppose, as I right now defined just a single page in the edit menu, there will be no switching between pages yet.

....

OK. I put the XControl in "MC" mode (the MC LED is lit and the Motor faders return to zero when I move them), connected it to the PC via USB and started Reaper.

I now could set "Midi Input" and "Midi Output" of the "Real Surface" to "X-TOUCH-COMPACT" (and set the "template" to "MCU.rst" and enabled all monitoring).

When I now move a fader in Reaper the CSI Monitor Window pops up and shows Midi messages, but nothing happens on the XTouch (the MIDI IN" LED of the XTOUCH does not flash). When I move a fader of the XTOUCH I don't see midi messages in the Monitor window.

-Michael

Looks like midi I/O problems.

Like you say moving a fader should show as an OUT midi message (it does) and the X-Touch midi in LED should probably light up (it doesn't).

You should also see midi IN messages when you activate X-Touch controls.

Is there more than one X-Touch midi choice in the dropdown ?

[mschnell]

Originally Posted by Geoff Waddington

Is there more than one X-Touch midi choice in the dropdown ?

Nope.

With Midi in: none but the single "X-TOUCH COMPACT",
With Midi-Out: Just "X-TOUCH COMPACT" and Microsoft Wavetable Synth.

I verified that when trying to record midi from the XTouch in a track I get recorded Midi messages, and playing back the track moves the faders appropriately.

In the CSI.ini file there is no mentioning of the XTouch, even though it is shown in the "Real Surfaces" window (I just removed the others, but no change).

Could it be that the name of the "X-TOUCH COMPACT" midi device (featuring hyphens) introduces the problem ? I seem to remember that I once had such a problem with some other device and some other software.

-Michael

[Geoff Waddington]

Originally Posted by mschnell

Nope.

With Midi in: none but the single "X-TOUCH COMPACT",
With Midi-Out: Just "X-TOUCH COMPACT" and Microsoft Wavetable Synth.

I verified that when trying to record midi from the XTouch in a track I get recorded Midi messages, and playing back the track moves the faders appropriately.

In the CSI.ini file there is no mentioning of the XTouch, even though it is shown in the "Real Surfaces" window (I just removed the others, but no change).

Could it be that the name of the "X-TOUCH COMPACT" midi device (featuring hyphens) introduces the problem ? I seem to remember that I once had such a problem with some other device and some other software.

-Michael

Ok looks like the unit is sending midi fine.

Could you post the contents of your CSI.ini file.

[mschnell]

CSI.ini:

MidiInMonitor On
MidiOutMonitor On
VSTMonitor On

RealSurface Mix1TestMCU_RealSurface 8 1 3 4 MCU.rst

Page Page1 Yes
VirtualSurface Mix1TestMCU_RealSurface MCU MCU

[Geoff Waddington]

Originally Posted by mschnell

CSI.ini:

MidiInMonitor On
MidiOutMonitor On
VSTMonitor On

RealSurface Mix1TestMCU_RealSurface 8 1 3 4 MCU.rst

Page Page1 Yes
VirtualSurface Mix1TestMCU_RealSurface MCU MCU

This says you have a real surface named "Mix1TestMCU_RealSurface".

Is this what you see in the CSI Real Surfaces and Virtual Surfaces windows ?

Can you post the contents of the MCU.rst file and the contents of the MCU.axt file in the axt/MCU folder.

[mschnell]

Originally Posted by Geoff Waddington

This says you have a real surface named "Mix1TestMCU_RealSurface".

Is this what you see in the CSI Real Surfaces and Virtual Surfaces windows ?

Yep. I renamed "Mix1" to Mix1TestMCU in that window and (finally) deleted the others. Am I not supposed to do this ?

When I start Reaper the CSI log window sais:

OUT -> Mix1TestMCU_RealSurface e6  00  00 
OUT -> Mix1TestMCU_RealSurface 90  06  00 
OUT -> Mix1TestMCU_RealSurface 90  0e  00 
OUT -> Mix1TestMCU_RealSurface 90  16  00 
OUT -> Mix1TestMCU_RealSurface 90  1e  00 
OUT -> Mix1TestMCU_RealSurface 90  6f  00 
OUT -> Mix1TestMCU_RealSurface b0  37  01 
OUT -> Mix1TestMCU_RealSurface e7  00  00 
OUT -> Mix1TestMCU_RealSurface 90  07  00 
OUT -> Mix1TestMCU_RealSurface 90  0f  00 
OUT -> Mix1TestMCU_RealSurface 90  17  00 
OUT -> Mix1TestMCU_RealSurface 90  1f  00

Originally Posted by Geoff Waddington

Can you post the contents of the MCU.rst file and the contents of the MCU.axt file in the axt/MCU folder.

The date of both shows that they are not modified after installing from the ZIP.

MCU.rst
Track Button 90 28 00 7f
Send Button 90 29 00 7f
Pan Button 90 2a 00 7f
Plugin Button 90 2b 00 7f
EQ Button 90 2c 00 7f
Instrument Button 90 2d 00 7f

BankLeft Button 90 2E 00 7f
BankRight Button 90 2F 00 7f
ChannelLeft Button 90 30 00 7f
ChannelRight Button 90 31 00 7f
Flip Button 90 32 00 7f
GlobalView Button 90 33 00 7f

nameValue Button 90 34 00 7f
smpteBeats Button 90 35 00 7f

F1 Button 90 36 00 7f
F2 Button 90 37 00 7f
F3 Button 90 38 00 7f
F4 Button 90 39 00 7f
F5 Button 90 3a 00 7f
F6 Button 90 3b 00 7f
F7 Button 90 3c 00 7f
F8 Button 90 3d 00 7f

MidiTracks Button 90 3E 00 7f
Inputs Button 90 3F 00 7f
AudioTracks	Button 90 40 00 7f
AudioInstruments Button 90 41 00 7f    
Aux Button 90 42 00 7f
Busses Button 90 43 00 7f    
Outputs Button 90 44 00 7f
User Button 90 45 00 7f

Shift ButtonWithRelease 90 46 00 7f
Option ButtonWithRelease 90 47 00 7f
Control ButtonWithRelease 90 48 00 7f
Alt ButtonWithRelease 90 49 00 7f

Read Button 90 4a 00 7f
Write Button 90 4b 00 7f
Trim Button 90 4c 00 7f
Touch Button 90 4d 00 7f
Latch Button 90 4e 00 7f
Group Button 90 4f 00 7f

Save Button 90 50 00 7f
Undo Button 90 51 00 7f
Cancel Button 90 52 00 7f
Enter Button 90 53 00 7f

Marker Button 90 54 00 7f
Nudge Button 90 55 00 7f

Cycle Button 90 56 00 7f
Drop Button 90 57 00 7f
Replace Button 90 58 00 7f
Click Button 90 59 00 7f
Solo Button 90 5a 00 7f

Rewind Button 90 5b 00 7f
FastForward Button 90 5c 00 7f
Stop Button 90 5d 00 7f
Play Button 90 5e 00 7f
Record Button 90 5f 00 7f

Up Button 90 60 00 7f
Down Button 90 61 00 7f
Left Button 90 62 00 7f
Right Button 90 63 00 7f

Zoom Button 90 64 00 7f
Scrub Button 90 65 00 7f

MasterChannelFaderTouch ButtonWithRelease 90 70 00 7f
MasterChannelFader Fader14Bit -72.0 12.0 e8 00 7f 00 7f

JogWheelRotary Encoder b0 3c 00 7f
 
Channel
ChannelFaderTouch ButtonWithRelease 90 68 00 7f
ChannelRotaryPush ButtonCycler 90 20 00 7f
ChannelRotary Encoder b0 10 00 7f
ChannelDisplayUpper DisplayUpper
ChannelDisplayLower DisplayLower
ChannelFader Fader14Bit -72.0 12.0 e0 00 7f 00 7f
ChannelRecordArm Button 90 00 00 7f
ChannelSolo Button 90 08 00 7f
ChannelMute Button 90 10 00 7f
ChannelSelect Button 90 18 00 7f
ChannelEnd

MCU.axt:
ChannelLeft TrackBank 1
ChannelRight TrackBank -1
BankLeft TrackBank 20
BankRight TrackBank -20
Rewind Rewind
FastForward FastForward
Stop Stop
Play Play
Record Record
F1 NextLayout
F7 PinSelectedTracks
F8 UnpinSelectedTracks
Shift Shift
Option Option
Control Control
Alt Alt
Read TrackAutoMode 1
Write TrackAutoMode 3
Trim TrackAutoMode 0
Touch TrackAutoMode 2
Latch TrackAutoMode 4
Group TrackAutoMode 5
Shift+Read GlobalAutoMode 1
Shift+Write GlobalAutoMode 3
Shift+Trim GlobalAutoMode 0
Shift+Touch GlobalAutoMode 2
Shift+Latch GlobalAutoMode 4
Shift+Group GlobalAutoMode 5
Save Reaper 40026
Shift+Save Reaper 40022
Undo Reaper 40029
Shift+Undo Reaper 40030
Marker Reaper 40172
Shift+Marker Reaper 40157
Option+Marker Reaper 40174
Nudge Reaper 40173
Cycle CycleTimeline
Click Reaper 40364
Zoom LatchedZoom
Scrub LatchedScrub

ChannelDisplayUpper TrackNameDisplay
ChannelDisplayLower TrackTouchControlled TrackVolumeDisplay
ChannelFader TrackVolume
ChannelFaderTouch TrackTouch
ChannelRotary TrackPan
ChannelDisplayLower TrackPanDisplay
ChannelSelect TrackUniqueSelect
Shift+ChannelSelect TrackRangeSelect
Control+ChannelSelect TrackSelect
ChannelRecordArm TrackRecordArm
ChannelMute TrackMute
ChannelSolo TrackSolo

[Geoff Waddington]

Originally Posted by mschnell

Yep. I renamed "Mix1" to Mix1TestMCU in that window and (finally) deleted the others. Am I not supposed to do this ?

No, you're fine.

I tested here with 1 surface and it worked as expected.

Does the midi port list in Audio->Midi Devices agree with what you see in the CSI Real Surface midi port dropdown lists?

[mschnell]

Originally Posted by Geoff Waddington

Does the midi port list in Audio->Midi Devices agree with what you see in the CSI Real Surface midi port dropdown lists?

Yes
Both read exactly:

X-TOUCH COMPACT

I.e. not with two hyphens, as I once suggested before, but with a blank. I do suppose that this in fact is the problem, as elements in many kinds of lists are separated by blank.

-Michael

[Geoff Waddington]

Originally Posted by mschnell

Yes
Both read exactly:

X-TOUCH COMPACT

I.e. not with two hyphens, as I once suggested before, but with a blank. I do suppose that this in fact is the problem, as elements in many kinds of lists are separated by blank.

-Michael

Hmmm...

Can you post screen shots of the midi in/out dropdowns in CSi config and also screenshots of the MIDI devices windows ?

[Geoff Waddington]

New build is up:
https://stash.reaper.fm/v/33037/CSI%20pre%20alpha.zip

Cycle Actions are back with a slightly different syntax:

ChannelRotary TrackCycle ChannelRotaryPush TrackPan TrackPanWidth

[mschnell]

Originally Posted by Geoff Waddington

Can you post screen shots of the midi in/out dropdowns in CSi config and also screenshots of the MIDI devices windows ?

Here you are..
-Michael

[mschnell]

+ this

[Geoff Waddington]

Originally Posted by mschnell

+ this

Don't know if it matters, but on my setup, in the MIDI Devices panel I have all of my CSI devices set to disabled.

Also, what version of Reaper are you using ?

[Freex]

Originally Posted by Geoff Waddington

Don't know if it matters, but on my setup, in the MIDI Devices panel I have all of my CSI devices set to disabled.

That's what jumped out at me too, My devices are disabled also.

[mschnell]

Originally Posted by Geoff Waddington

Don't know if it matters, but on my setup, in the MIDI Devices panel I have all of my CSI devices set to disabled.

I did try both settings: no difference.

Originally Posted by Geoff Waddington

Also, what version of Reaper are you using ?

I always use the newest release, so right now it's 5.90.

-Michael

[Geoff Waddington]

Originally Posted by mschnell

I did try both settings: no difference.



I always use the newest release, so right now it's 5.90.

-Michael

Hmmm...

RealSurface Mix1TestMCU_RealSurface 8 1 3 4 MCU.rst

Try manually changing 3 4 in CSI.ini

I would try:
0 1
1 2
2 3
3 4 -- already proven not to work
4 5
5 6
6 7
7 8
8 9

etc., just to see if we can anything to work.

[mschnell]

Extremely funny:

I started
0 1
1 2
2 3
3 4

And now it works

I did not change anything but editing the ini file (to and fro) and starting Reaper several times.

Really puzzled....

-Michael

[mschnell]

Seems to go on working for now.

So details....

The Reaper Master fader is mapped to the left most fader of the XControl Track 1 to fader 2, ...track 7 to fader 8 and the "Main" fader seems not to be assigned to a Reaper control.

Supposedly I can easily sort this out in the config files.

For the "track" faders Volume, Pan, Select, Mute, and Solo works correctly including light and fader remote moving. Maybe Mute and Solo should be swapped, as the position on the surface is reversed.

-Michael

[Geoff Waddington]

Originally Posted by mschnell

Seems to go on working for now.

So details....

The Reaper Master fader is mapped to the left most fader of the XControl Track 1 to fader 2, ...track 7 to fader 8 and the "Main" fader seems not to be assigned to a Reaper control.

Supposedly I can easily sort this out in the config files.

The Master is not working because you told CSI there are only 8 faders

Change this:
RealSurface Mix1TestMCU_RealSurface 8 1 3 4 MCU.rst

to this:
RealSurface Mix1TestMCU_RealSurface 9 1 3 4 MCU.rst

Originally Posted by mschnell

For the "track" faders Volume, Pan, Select, Mute, and Solo works correctly including light and fader remote moving. Maybe Mute and Solo should be swapped, as the position on the surface is reversed.l

You can do this by making your own .axt files for the X Touch Compact.

Just go into the CSI/axt folder and make a new folder (e.g XTouchCompact)

Copy the CSI/axt/MCU/MCU.axt file to CSI/axt/XTouchCompact/MCU.axt.

Probably a good idea to rename it, say XTouchCompact.axt.

Now you can change the following:
ChannelMute TrackMute
ChannelSolo TrackSolo

to :

ChannelMute TrackSolo
ChannelSolo TrackMute

Now go into CSI config and change Virtual Surface to point to XTouchCompact folder.

Voila you've now got a custom axt for your surface that swaps the Mute and Solo buttons !

However, this only affects those buttons within this Page definition.

Another Page could have entirely different behaviour.

If you want to do this globally, perform the equivalent steps with the .rst files and change the buttons there.

If you use that approach, the Mute and Solo will be swapped for all pages.

Glad things have started working, let me know if you need any help with the customization.

[mschnell]

I could recreate the problem and it got ever weirder.

I opened the CSI "Real Surface" edit menu and set the "Midi Out" to "Wavetable Synth" (there is only one Midi In device)

Of course it does not work.

Changed it back to "X-Touch Compact"

Still not working (Error like yesterday)

Edited CSI.ini to ... 0 1 ...

Works ?!?!?!?!?!? (Other than yesterday. Supposedly wrong device numbers ?!?!?! )

Edited CSI.ini to ... 3 4 ...

Works (supposedly correct device numbers ? )

Verified that setting Midi out to "WaveTable" modified CSI.ini to ... 3 0 ...

Seemingly sometimes device specs are taken not from CSI.ini, but from elsewhere .

Edited the channel count to 9, which is reflected in CSI.ini.

Not working and right now the "edit CVSI.ini somehow" does not work any more.

-Michael

[Freex]

Originally Posted by mschnell

I could recreate the problem and it got ever weirder.

I opened the CSI "Real Surface" edit menu and set the "Midi Out" to "Wavetable Synth" (there is only one Midi In device)

Of course it does not work.

Changed it back to "X-Touch Compact"

Still not working (Error like yesterday)

Edited CSI.ini to ... 0 1 ...

Works ?!?!?!?!?!? (Other than yesterday. Supposedly wrong device numbers ?!?!?! )

Edited CSI.ini to ... 3 4 ...

Works (supposedly correct device numbers ? )

Verified that setting Midi out to "WaveTable" modified CSI.ini to ... 3 0 ...

Seemingly sometimes device specs are taken not from CSI.ini, but from elsewhere .

Edited the channel count to 9, which is reflected in CSI.ini.

Not working and right now the "edit CVSI.ini somehow" does not work any more.

-Michael

Not sure how the new alpha plays, but the old one used to hang if you went back into the settings.
Restart reaper and don't go back into the CSI. Does that work?

When you set the count to 9 you then need to "Pin" the Master Strip on surface to the master fader in reaper.

[mschnell]

Originally Posted by Freex

Not sure how the new alpha plays, but the old one used to hang if you went back into the settings.
Restart reaper and don't go back into the CSI. Does that work?

No.
It never hang for me.
I always stopped Reaper for manually editing CSI.ini and restarted,

Originally Posted by Freex

When you set the count to 9 you then need to "Pin" the Master Strip on surface to the master fader in reaper.

I did suppose something like this, but right now I don't thoroughly understand these options.

Anyway, I suppose that setting the channel count to 9 should not deactivate the Midi transport altogether, or should it ?

-Michael

[mschnell]

DFoing the "exteded edit CSI.ini" trick got it working again:

Trying all settings one after the other: 0/1, 1/2, 2/3, 3/4

now the line reads:

RealSurface Mix1TestMCU_RealSurface 9 1 3 4 MCU.rst

I suppose meaning:

9 channels
1 ???
3 Midi In device #
4 Midi out device #

-Michael

[mschnell]

Now all nine faders ork.

Of course I need to set fader 9 to "Master" and shift the channels down, as the "Compact" does not feature the "select", "Mute", and "Solo" buttons with the ninth fader.

Before starting this endeavor:

Right Now the "Control Surface Mode" is set "Control Surface Integrator". Should I stay with this, or can/should I do a "X-Touch Compact MC" selection here (supposedly by creating an appropriate file) ?

-Michael

[Geoff Waddington]

Originally Posted by mschnell

DFoing the "exteded edit CSI.ini" trick got it working again:

Trying all settings one after the other: 0/1, 1/2, 2/3, 3/4

now the line reads:

RealSurface Mix1TestMCU_RealSurface 9 1 3 4 MCU.rst

I suppose meaning:

9 channels
1 ???
3 Midi In device #
4 Midi out device #

-Michael

9 channels
1 Bankable -- 1 = yes, 0 = no, usually set to 1, except for Console 1, Mackie C4, etc.
3 Midi In device #
4 Midi out device #

[Geoff Waddington]

Originally Posted by mschnell

Now all nine faders ork.

Of course I need to set fader 9 to "Master" and shift the channels down, as the "Compact" does not feature the "select", "Mute", and "Solo" buttons with the ninth fader.

Yes, as Freex said, you should probably Pin the Master to Channel 9.

Originally Posted by mschnell

Before starting this endeavor:

Right Now the "Control Surface Mode" is set "Control Surface Integrator". Should I stay with this, or can/should I do a "X-Touch Compact MC" selection here (supposedly by creating an appropriate file) ?

-Michael

The "Control Surface Mode" should always be "Control Surface Integrator".

[mschnell]

Originally Posted by Geoff Waddington

Just go into the CSI/axt folder and make a new folder (e.g XTouchCompact)

Copy the CSI/axt/MCU/MCU.axt file to CSI/axt/XTouchCompact/MCU.axt.

Probably a good idea to rename it, say XTouchCompact.axt.

Did so. and then selected this for "Page1"

But after that tapping buttons at the surface has no effect any more (but the messages showing in the Midi Log Window), while the faders still work as expected, and the lights in the buttons still follow the actions done in Reaper.

Edit:

Deleting the recently used "Real Surface" in the menu and by that selecting the newly created one, got rid of this effect. Now the buttons are working again. (Weird again )

-Michael

[mschnell]

Originally Posted by Geoff Waddington

Now you can change the following:
ChannelMute TrackMute
ChannelSolo TrackSolo

to :

ChannelMute TrackSolo
ChannelSolo TrackMute

Works. But is this really appropriate ? Would it not be better to edit the midi messages (supposedly defined in some other file) ?

Anyway, the buttons on the X-Touch are not labeled.

-Michael

[mschnell]

Originally Posted by Freex

When you set the count to 9 you then need to "Pin" the Master Strip on surface to the master fader in reaper.

Yep. But no idea how to do that.

-Michael

[Freex]

Originally Posted by mschnell

Yep. But no idea how to do that.

-Michael

bank across once so that first channel (MASTER) on control surface is active on strip 9 (your master strip)
Then hit F7 (I think it's F7 PIN F8 UNPIN)
Then bank back and you should find the Reaper_master_fader in now pinned to your control_surface_master_Strip.

This is on a pre-project basis. So if you make a new project you need to set it up.
It's 2 secs of prep once you get used to it.

[mschnell]

Originally Posted by Freex

bank across once so that first channel (MASTER) on control surface is active on strip 9 (your master strip)

What is "bank" and even "bank across" ?

-Michael

[mschnell]

Originally Posted by Freex

This is on a per-project basis. So if you make a new project you need to set it up.

Supposedly not really a problem, but anyway, Is it uncommon that a surface has the Master fader in the right-most position ? Close to all Mixers are crafted that way.

-Michael