Now that Reaper for Linux has become more official, any chance we will see Linux support some day? I have an X32 in the practice room / studio, and would seriously consider buying an X-touch for home if I knew it could be made to work well.

I'd be more than willing to lend whatever support I could either for porting to Linux and/or improving the X32/X-touch support. I just don't run Windows or OS/X anymore

Yep, I'm pretty much all set, thanks for taking the time to indulge me Is it ok to share the files I'm using with anyone who has a similar setup?

Not indulging you, the MCU/XT/C4 combo is a great testbed for most functionality, especially when added to the Avid Artist Mixes, Control and Softube Console 1 here, makes for a reasonably heterogeneous test sample

Also wanted to make sure folks in general have enough to play around with in a meaningful way, whilst I go off to the OSC Crusades and pray I don't run into the Knights Who Say Nicht !!

Quote:

Originally Posted by MixMonkey

One last thing (pauses for Geoff to stop groaning) Could you put in the piece of code that makes the screen bank in sympathy with the surface (and vice versa)? Then I promise to disappear and leave you in peace

Not sure what you mean here ?

Quote:

Originally Posted by MixMonkey

I don't think so, my C4.axt has just one line- TrackOnSelection MapFXToWidgets, so to make the C4 display the FX on the Send page I just need to include C4.axt in the Send page setup (I don't really need to make C4Send.axt, as it will be identical to C4.axt)

I think you maybe assumed I'd already done this, but I haven't (so carried away with seeing those sends appear on the faders!)

Yes, I did assume that, I was talking about the fxt folder which you would also have to reference, as stated, the same one used on the other Page would be fine, unless you wanted different behaviour.

Now that Reaper for Linux has become more official, any chance we will see Linux support some day? I have an X32 in the practice room / studio, and would seriously consider buying an X-touch for home if I knew it could be made to work well.

I'd be more than willing to lend whatever support I could either for porting to Linux and/or improving the X32/X-touch support. I just don't run Windows or OS/X anymore

A bit down the road, but yes, I hope so, I'm just using the Win/WDL/SWELL stuff, has Justin provided support for that under Linux ?

Also wanted to make sure folks in general have enough to play around with in a meaningful way,

You've certainly provided that

Quote:

Originally Posted by Geoff Waddington

whilst I go off to the OSC Crusades and pray I don't run into the Knights Who Say Nicht !!

They're no longer the knights who say "Ni" they're now the knights who say "Ekke ekke ekke ptang zoo boing" but they still can't bear to hear the word "it", so you should be fine These guys might be good for a shrubbery though....https://dirtdigger.ca/

Quote:

Originally Posted by Geoff Waddington

Not sure what you mean here ?

So that when you select a channel on the surface, the on screen mixer banks to display that channel if it can't already be seen.

In a similar manner, if you select a channel on the on screen mixer that can't be seen on the surface, the surface banks to show the channel.

......."look mate, strange women lying in ponds distributing swords is no basis for a system of government".....

How important is this for your workflow, as you can see it might take an inordinate chunk of time.

MCP only is fine- I wouldn't want the TCP to scroll (personal pref)

Yes to it being a page level option if it doesn't make it harder to implement. Otherwise just have it on all the time- the TCP won't follow and can be used to access functions on unseen tracks if needed.

The lack of it won't stop me getting on with stuff, but I'm pretty sure most people will expect CSI to behave in this way. I was kinda hoping that you could just lift the code from Wadd C4, where this already happens (ignorance is bliss)

Yes to it being a page level option if it doesn't make it harder to implement. Otherwise just have it on all the time- the TCP won't follow and can be used to access functions on unseen tracks if needed.

The lack of it won't stop me getting on with stuff, but I'm pretty sure most people will expect CSI to behave in this way. I was kinda hoping that you could just lift the code from Wadd C4, where this already happens (ignorance is bliss)

Just had a quick look at the old MCU/C4code, looks like it makes sure the selected track is visible on the surface, but doesn't make sure the selected track is visible in Reaper if selected via the surface.

Just had a quick look at the old MCU/C4code, looks like it makes sure the selected track is visible on the surface, but doesn't make sure the selected track is visible in Reaper if selected via the surface.

It's a pity Reaper 40913/Track: Vertical scroll selected tracks into view only scrolls the TCP, otherwise i'd map that to a button and have done with it. That and the code you found and we'd be covered

Select the track on the surface push SomeButton Reaper 40913 and the MCP would scroll the track into view in Reaper. Except only the TCP scrolls

It's a pity Reaper 40913/Track: Vertical scroll selected tracks into view only scrolls the TCP, otherwise i'd map that to a button and have done with it. That and the code you found and we'd be covered

Select the track on the surface push SomeButton Reaper 40913 and the MCP would scroll the track into view in Reaper. Except only the TCP scrolls

I tried a brand new way of doing the MCP scrolling, see if you like it.

Don't quite remember how the other one worked, this one scrolls "just enough" if you are off one edge or the other, so the selected track shows up at the left or right edge of the control surface(s) and the Reaper track control panel.

There is no option to turn it off, but it only works in MCP mode.

Thinking about this, I'm wondering if there really is a good use case for not doing this, that outweighs the damage you can cause be having selected tracks hidden from view.

I agree, now Reaper only "jumps" when selected from surface -- much more intuitive.

This is much better Seems (to me) completely natural.

Just noticed a weird bug (I think it may have been in the previous build as well) When I scroll the screen mixer to a higher numbered track and select it, the surface scroll stops short by 8.

Say I open the session and track one is selected and I can see tracks 1-24 on the surface(s) If I scroll the mixer on screen to see Track 58 and select it, the surface will jump but the far right channel will be Track 50. If I then scroll the screen to see Track 96 and select it, the far right channel will be Track 88.

Now here's the weird thing, going the other way, say scrolling the screen to see Track 46 and selecting it, the surface will jump and put Track 46 far left- exactly what you want.

Banking and selecting tracks from the surface always scrolls the screen correctly- the selected track ends up far left (until the last of the tracks are on the surface, then it doesn't move)

One thing I just discovered is that you can stop the surface banking with the screen by de-selecting "Scroll view when tracks activated" in the menu in the bottom right hand corner of the master fader. With this de-selected you can scroll the TCP and MCP windows and select tracks without the surface moving- v.handy! Think of it a bit like the timeline scrolling, sometimes you want it to scroll, sometimes you don't.

Even with "Scroll view when tracks activated" de-selected, selecting a track on the surface will always scroll both the MCP and TCP. It would be good to be able to disable this temporarily- it's handy to be able to separate the editing window from the mixing surface so you don't 'lose your place' whilst editing tracks if you want to bank the surface and EQ something (which would require a track selection and therefore force the TCP to jump)

I'm less bothered about the MCP following the surface all the time, but options are always good

Still haven't found the time to install Windows 10, but apparently it is working now, somehow. Per default, CSI selected the master track, so no wonder, I couldn't see any change in the other tracks.
However, CSI doesn't seem to follow track selection?

I have to use the "next/previous channel" buttons and enable track coloring to see, which track CSI has currently selected. Did I miss to set some checkbox?

Furthermore, I'm trying to get more functions of the CMC-CH working. The Pan encoder seems a very stubborn guy...

From the specification it says:

Pan
CMC -> PC B0 10 rr
whereas rr: 0x = CW, 4x = CCW, that means, from 00-39 = clockwise, 41-127 = counterclockwise
Is there some way to get this working with CSI?

Still haven't found the time to install Windows 10, but apparently it is working now, somehow. Per default, CSI selected the master track, so no wonder, I couldn't see any change in the other tracks.
However, CSI doesn't seem to follow track selection?

I have to use the "next/previous channel" buttons and enable track coloring to see, which track CSI has currently selected. Did I miss to set some checkbox?

A lot of surfaces have a select button, had a quick look at the CMC-CH, looks more like a Faderport, might need a bit of thought on this to get the best mapping, and will likely help Faderport, AlphaTrack, X Touch One, etc. users at the same time.

Thanks for testing !!

Quote:

Originally Posted by _Stevie_

Furthermore, I'm trying to get more functions of the CMC-CH working. The Pan encoder seems a very stubborn guy...

From the specification it says:

Pan
CMC -> PC B0 10 rr
whereas rr: 0x = CW, 4x = CCW, that means, from 00-39 = clockwise, 41-127 = counterclockwise
Is there some way to get this working with CSI?

Woop, you are a wizard, the Pan encoder works!
The feedback works also, but not quite as expected. When centered, it should be turned off. When left or right, it should gradually get brighter. Not sure, if that's possible?

EDIT: ah so the track selection is an issue, that other users have too. I thought it's only me.

Yes, well... errr.. let's see, maybe not right now, but soon if it doesn't.

The first test cases for the plugins were on the Console 1 and the C4, those are working reasonably well, so right now is a great time to start thinking about how to approach the single channel flavour of controllers.

What would the dream Reaper integration of your your CMC-CH look like ?

....and therein lies the rub.. At the moment it maps all the plugins on the selected track to the surface, so it's best to dedicate certain surface controls to certain FX functions.

For instance, in my system I'm using a Mackie C4 to control plugins (it's an 8x8 endless encoder box with displays) What I'm planning on doing is dedicating A1-A8 (top row) to compressor stuff, B,C and D 1-4 to EQ and B,C and D 5-8 to everything else.

At the present time, there is only one 'layer' available. In my case that means a maximum of 32 rotaries and 32 pushes to cover all the plugins on a channel and I have to be careful that I don't end up with two fx parameters assigned to the same control.

I plan on tearing into the MCU.axt and MCU.rst to get clearer idea of what works and what doesn't when I start assigning Reaper functions to buttons. I'm pretty sure all the Press type buttons will work ok, but the Press FB might be a bit more hit or miss.

For instance, my first choice for the new SetScrollLink was the Solo button on the MCU (handily placed and my Scroll and Zoom buttons don't latch) but this resulted in all the mute and solo buttons on the MCU flickering dimly. When I re-assigned it to GlobalView, it worked fine, including the LED.

One quick question, can the / be used to comment out lines in any of the text files?

I finally got some time to look into this a bit more, I have been slowly reading the entire thread, I am up to about page 30.
I mapped everything on the Spirit 328 that outputs a midi message when in Controller mode, here is the list, these also output midi messages when in mixer mode, but the messages are different, and are used for console automation.

I set up a .rst and .axt file, the transport controls work, but there is no feedback from Reaper, none of the faders, encoders or the mute/solo switches work.
-------------------------------------
Spirit328.rst

Rewind Rewind
FastForward FastForward
Stop Stop
Play Play
Record Record

Fader1 TrackVolume
Pan1 TrackPan
Mute1 TrackMute
Solo1 TrackSolo

Fader2 TrackVolume
Pan2 TrackPan
Mute2 TrackMute
Solo2 TrackSolo

Fader3 TrackVolume
Pan3 TrackPan
Mute3 TrackMute
Solo3 TrackSolo
-------------------------------
Also, when I move a control or push a button in Reaper, the monitor does not show any output.
I am just guessing on the .axt file, I haven't a clue what I am supposed to do there.
Do we have to set any actions in Reaper, or is that done in the .dll?

Yes, well... errr.. let's see, maybe not right now, but soon if it doesn't.

The first test cases for the plugins were on the Console 1 and the C4, those are working reasonably well, so right now is a great time to start thinking about how to approach the single channel flavour of controllers.

What would the dream Reaper integration of your your CMC-CH look like ?

Let's see how easy it is to build !

Oh Geoff, thanks so much for asking this.
Let's see. I'll try to explain it as transparent as possible.

Fader: works
Pan: works now! :P
Mute: works
Solo: works
Read Automation: works
Write Automation: works
Next/Previous Channel: works

"e"-Button: actually opens the Cubase channel strip, not available in Reaper. But I thought, it would be appropriate to open the FX Chain, because all plugins are listed in there. This comes the channel strip very close.
And it would be great, if the button LED would be turned on, if either the FX Chain is opened OR at least one floating plugin window of the selected channel (excluding VST instruments, see below).

Open VST instrument: would be great if this button could open all VST instruments of the selected channel and turn on the LED, when the plugin window is opened.

I plan on tearing into the MCU.axt and MCU.rst to get clearer idea of what works and what doesn't when I start assigning Reaper functions to buttons. I'm pretty sure all the Press type buttons will work ok, but the Press FB might be a bit more hit or miss.

For instance, my first choice for the new SetScrollLink was the Solo button on the MCU (handily placed and my Scroll and Zoom buttons don't latch) but this resulted in all the mute and solo buttons on the MCU flickering dimly. When I re-assigned it to GlobalView, it worked fine, including the LED.

One quick question, can the / be used to comment out lines in any of the text files?

Excellent, let me know what you find !

Yes / works as comment in any of the text files.

Don't forget comments will get clobbered in CSI.ini on the next write though, that's the only one.

....and therein lies the rub.. At the moment it maps all the plugins on the selected track to the surface, so it's best to dedicate certain surface controls to certain FX functions.

For instance, in my system I'm using a Mackie C4 to control plugins (it's an 8x8 endless encoder box with displays) What I'm planning on doing is dedicating A1-A8 (top row) to compressor stuff, B,C and D 1-4 to EQ and B,C and D 5-8 to everything else.

At the present time, there is only one 'layer' available. In my case that means a maximum of 32 rotaries and 32 pushes to cover all the plugins on a channel and I have to be careful that I don't end up with two fx parameters assigned to the same control.

Ah great approach man! I wish, there was still something like that C4 available. 32 rotary knobs with displays sounds absolutely amazing for such a task!

I finally got some time to look into this a bit more, I have been slowly reading the entire thread, I am up to about page 30.
I mapped everything on the Spirit 328 that outputs a midi message when in Controller mode, here is the list, these also output midi messages when in mixer mode, but the messages are different, and are used for console automation.

I set up a .rst and .axt file, the transport controls work, but there is no feedback from Reaper, none of the faders, encoders or the mute/solo switches work.
-------------------------------------
Spirit328.rst

Rewind Rewind
FastForward FastForward
Stop Stop
Play Play
Record Record

Fader1 TrackVolume
Pan1 TrackPan
Mute1 TrackMute
Solo1 TrackSolo

Fader2 TrackVolume
Pan2 TrackPan
Mute2 TrackMute
Solo2 TrackSolo

Fader3 TrackVolume
Pan3 TrackPan
Mute3 TrackMute
Solo3 TrackSolo
-------------------------------
Also, when I move a control or push a button in Reaper, the monitor does not show any output.
I am just guessing on the .axt file, I haven't a clue what I am supposed to do there.
Do we have to set any actions in Reaper, or is that done in the .dll?

Any thoughts?

Ok, first of all, you're working way too hard, channel notation is your friend, instead of:

Definitely something hinkey with some of the PressFB buttons on the MCU.

For instance, if you comment out: Click Reaper 40364 and add Replace Reaper 40364, the Replace button will operate the metronome (as the Click button did) but when the button is in the off state the LED will flicker continuously and a continuous stream of MIDI is being sent from Reaper (presumably causing the LED to flicker)