Hello Geoff and everyone. I jumped in here a while back before an alpha was launched. I got familiar with the thread again, but it didn't help because I am honestly [more] lost and not sure if this is yet ready for someone like me with no coding skills.

I am using this surface: https://www.roland.com/global/products/v-studio_700/ with the MCU standard with Reaper and it works pretty darn well just as it is. All channel strips work 100% and about 90% of the other buttons can be programmed to actions. I don't really want to change any of that right now.

I'd really like to try this out because this control surface has a section with 12 rotaries and a display, similar to like a C4...but these just don't work as it is for anything, and it would be great to use them for plugs/etc. I have things downloaded/installed and can launch the app, but I almost totally lost after that.

Sorry for the ignorance. It's ok to tell me to come back later when it's ready.
Dave

Hey Dave, like you I'm not a coder either, but what I do know is what you'll want to do first is once you have the CSI up and running in Reaper, enable the "midi in". Then turn each knob on your v700 and jot down the data (if any) that's displayed.
This is then used to allow you to integrate that part of the surface into CSI and further more Reaper.

Hey Freex, I have already mapped all of the buttons early in the year using MidiOx and using Geoff's instructions on formatting. And I have played with the CSI today. What confuses me on this part is that, when I do enable midi in, I see things like faders and button presses provide info, but the pan encoders do not. However, the pan encoders all work already. Same with some buttons, they don't show up in the display for midi in but the buttons work natively. And most importantly for me, the 12 encoders that I am hoping to map, they do not show up in this midi in view....but in MidiOx they do.

Hey Freex, I have already mapped all of the buttons early in the year using MidiOx and using Geoff's instructions on formatting. And I have played with the CSI today. What confuses me on this part is that, when I do enable midi in, I see things like faders and button presses provide info, but the pan encoders do not. However, the pan encoders all work already. Same with some buttons, they don't show up in the display for midi in but the buttons work natively. And most importantly for me, the 12 encoders that I am hoping to map, they do not show up in this midi in view....but in MidiOx they do.

That seems super odd!?!?
Sounds like somethings wrong somewhere.
Alas, I think the reasons and resolution may need to come from Geoff.

Hey Freex, I have already mapped all of the buttons early in the year using MidiOx and using Geoff's instructions on formatting. And I have played with the CSI today. What confuses me on this part is that, when I do enable midi in, I see things like faders and button presses provide info, but the pan encoders do not. However, the pan encoders all work already. Same with some buttons, they don't show up in the display for midi in but the buttons work natively. And most importantly for me, the 12 encoders that I am hoping to map, they do not show up in this midi in view....but in MidiOx they do.

Hey Geoff. I'm not sure. I do still have the mcu standard loaded in osc/control...I have some custom mappings already I don't want to lose. I am not at the studio today but maybe tonight i can post screens. I do know that on the mcu and csi I have only the console selected as input/output.

Also, when I start CSI and configure the first "page", there are green, blue, etc pages already. Then in the surface side, there are green/etc things loaded there. When I add VS700 page to start, and configure a new surface and save it as vs700, I noticed that if I go back into csi the surface was never saved and nothing is there.

Lastly, when I have midi monitoring, all of the values shown come from "green Mix" and a few are "green control".

Hey Geoff. I'm not sure. I do still have the mcu standard loaded in osc/control...I have some custom mappings already I don't want to lose. I am not at the studio today but maybe tonight i can post screens. I do know that on the mcu and csi I have only the console selected as input/output.

Also, when I start CSI and configure the first "page", there are green, blue, etc pages already. Then in the surface side, there are green/etc things loaded there. When I add VS700 page to start, and configure a new surface and save it as vs700, I noticed that if I go back into csi the surface was never saved and nothing is there.

Lastly, when I have midi monitoring, all of the values shown come from "green Mix" and a few are "green control".

Sorry but this is so confusing.

Ah, remove all the Pages you are not using, see if that helps.

I think you will also need to at least put the mcu standard on another set of midi ports, if you cannot remove it altogether.

Check your axt folders, I'll bet you will find 2 .axt files in the same folder with different definitions, it's the kiss of death.

Let me know, methinks we need a redesign of the axt/fxt file structure.

Had a look, can't see anything awry

Do I need to use anything new from the CSI folder (MCUSend notwithstanding)?

If I just change the .dylib and leave everything else the same, the behaviour flips from working normally to broken. The first thing I notice is that the master is no longer pinned (appearing far left).

The working .dylib is the one released immediately before the new one.

I tried a new project and also using the entire contents of the CSI folder from the download, modified to my setup- same result.

Do I need to use anything new from the CSI folder (MCUSend notwithstanding)?

If I just change the .dylib and leave everything else the same, the behaviour flips from working normally to broken. The first thing I notice is that the master is no longer pinned (appearing far left).

The working .dylib is the one released immediately before the new one.

I tried a new project and also using the entire contents of the CSI folder from the download, modified to my setup- same result.

Ahh, got it, will be fixed in next build.

Also going to take the opportunity to change surfaces to use .axt files, instead of directories -- solves the problem in which I caught myself

Hm, I just can't get the CMC-CH working in Windows. CSI does not receive any input from the device. In OSX my other CMC devices work flawlessly. Could it be that there is some device name issue in Windows?

Hm, I just can't get the CMC-CH working in Windows. CSI does not receive any input from the device. In OSX my other CMC devices work flawlessly. Could it be that there is some device name issue in Windows?

You MUST use the new CSI.ini as well as the new folder structure -- The .axt files now mimic the .rst files, folder structure wise.

Hopefully clobbered that nasty SysEx flood

First cut at Sends Page -- see CSI.ini for config examples.

Make sure to set your Sends Page MCU to use MCUSends.axt file -- See MCU for example.

Shift+ChannelLeft = Up
Shift+BankLeft = Down

Volume, Pan, Mute, Send Track name display, Touch shows Send Level.

New build is sweeeeeeeet here

Got rid of the old file structure and added MCUSend.axt and MCUXTSend.axt, mapped Up and Down to the Up/Down nav buttons (I have TrackBank assigned to the Left/Right nav buttons) Added Solo TrackSolo to the MCUSend.axt and MCUXTSend.axt to allow channel solo whilst on the Send Page.

157 track project, 4-5 sends per channel (threw in a couple of 1 and 2 send channels to check the end stop) Spent 10 mins going left,right ,up and down the sends, across the channels in banks of 24 (got another MCUXT), as well as flipping back and forth between the Send Page and the Channel Page. Channels with less than 5 sends stop at the last send on that channel as planned. Send Pan and Mute working AOK.

All good, no crashes and displays working fine.

Couple of minor points. The banking doesn't synchronise between the Channel Page and the Send Page. That is to say, if I switch to the Send page and bank across, then return to the Channel page, the Channel page will be where I left it- it won't have banked with the Send page. This might be desirable in some cases but it would be good to be able to link them.

Also, the rotary push on the 1st channel of my MCU no longer switches between Pan and Width. If I select the channel, pushing the rotary clears the selection. All other rotaries (MCU+XTs) work fine.

Got rid of the old file structure and added MCUSend.axt and MCUXTSend.axt, mapped Up and Down to the Up/Down nav buttons (I have TrackBank assigned to the Left/Right nav buttons) Added Solo TrackSolo to the MCUSend.axt and MCUXTSend.axt to allow channel solo whilst on the Send Page.

157 track project, 4-5 sends per channel (threw in a couple of 1 and 2 send channels to check the end stop) Spent 10 mins going left,right ,up and down the sends, across the channels in banks of 24 (got another MCUXT), as well as flipping back and forth between the Send Page and the Channel Page. Channels with less than 5 sends stop at the last send on that channel as planned. Send Pan and Mute working AOK.

All good, no crashes and displays working fine.

Couple of minor points. The banking doesn't synchronise between the Channel Page and the Send Page. That is to say, if I switch to the Send page and bank across, then return to the Channel page, the Channel page will be where I left it- it won't have banked with the Send page. This might be desirable in some cases but it would be good to be able to link them.

Great, glad we've made some headway.

To Synch banking, just go into Edit Page and check Synch Pages on the pages you'd like to lock together.

Quote:

Originally Posted by MixMonkey

Also, the rotary push on the 1st channel of my MCU no longer switches between Pan and Width. If I select the channel, pushing the rotary clears the selection. All other rotaries (MCU+XTs) work fine.

Sounds like a mapping issue.

The one other thing I'd add is it's a good idea to remove any "clutter" in your files, if something is not used -- comment it out by starting the line with /

That way it won't get read by Reaper but you won't lose it either, just remove the / to get it back.

Is this project the best way to do that - simply - with X32 and Reaper on MacOS? Would it in its current stage be reliable for writing fader automation?

I don't know if the X32 can do MC protocol.
If yes I suppose there is a chance to get it working with CSI in a short time.

If no, you might be in a similar situation as I am with my Behringer XTouch Compact (see above), as very understandably, the CSI first aim is to get MC compatible devices integrated, and other devices (all featuring their own specialties - such as the LEDs in the buttons of the Compact - see above) have lower priority.

This said, it might be a good idea to add an XTouch One to the X32 (I am considering adding an XTouch One to the Compact), as same provides certain features that seem to be important for remote-controlling Reaper. I suppose that getting the One work with CSI should be rather easy.

Documentation should include information on the current state of the configuration dialogue that you reach via the Reaper Prefs/Control/, which appears not to work all that much for changing things. All changes appear to be made in the CSI.ini and the relevant config files.

It took me about 30 minutes to get things going for both the MCU as a main fader box and the MCU as a send control.

I found the "select next page" from the page list defined in the CSI.ini by skimming across the MCU.axt file. This has to be in the documentation as an example. There's no action, there's just a definition in the AXT file.

F1 NextPage

A list of commands, documented is helpful too. Perhaps one of us knows of a good tool to keep documentation like that in a nice editable state where useful PDF files can be produced with the click of a button. For now, the examples are a nice read, but basic procedures for someone who has never seen this stuff, are a requirement to get more testing and usability testing. I almost gave up(for today).

The MCU faders, using MCU.axt and MCU.rst, do not play back automation, even though I see stuff being thrown at it in the midi monitor. Same for send levels. The faders jump back to the previous value after a few seconds. Not usable. Did I miss something ?

The send page has the same problem. The faders just jump back to values which I presume are defined by the static Read/Trim volume level, and not the current volume envelope.

I sure hope I missed something.

I can contribute on the documentation level. I have some experience in that regard, having written the first manual for Audacity a long damn time ago, as well as that for the Monkey's Audio application.

You did say "I have a job coming up in the next few months where I'll definitely need to get my Behringer X32 compact running as a fader control surface".

I'm hoping integrating OSC will take a lot less than a few months.

Perhaps even faster if we have a good tester with a good OSC device, hint hint

That said, of course feel free to search for other solutions.

Haha yes I did say that, but I imagined it could well be next year before OSC work gets done - I have no idea how long these things take!

I'll keep across the thread then and as soon as there's something to test with the X32 and OSC I'll do what I can. Bear in mind you may have to explain how to set it up and test as if talking to a small child 😁

Documentation should include information on the current state of the configuration dialogue that you reach via the Reaper Prefs/Control/, which appears not to work all that much for changing things. All changes appear to be made in the CSI.ini and the relevant config files.

It took me about 30 minutes to get things going for both the MCU as a main fader box and the MCU as a send control.

I found the "select next page" from the page list defined in the CSI.ini by skimming across the MCU.axt file. This has to be in the documentation as an example. There's no action, there's just a definition in the AXT file.

F1 NextPage

A list of commands, documented is helpful too. Perhaps one of us knows of a good tool to keep documentation like that in a nice editable state where useful PDF files can be produced with the click of a button. For now, the examples are a nice read, but basic procedures for someone who has never seen this stuff, are a requirement to get more testing and usability testing. I almost gave up(for today).

The MCU faders, using MCU.axt and MCU.rst, do not play back automation, even though I see stuff being thrown at it in the midi monitor. Same for send levels. The faders jump back to the previous value after a few seconds. Not usable. Did I miss something ?

The send page has the same problem. The faders just jump back to values which I presume are defined by the static Read/Trim volume level, and not the current volume envelope.

I sure hope I missed something.

Thanks for having a look !

Your points are well taken, the documentation is very thin right now.

Yes, automation is quite broken right now.

The software is still at a pre alpha stage, but I would say close to alpha.

Quote:

Originally Posted by airon

I can contribute on the documentation level. I have some experience in that regard, having written the first manual for Audacity a long damn time ago, as well as that for the Monkey's Audio application.