|
|
|
02-22-2021, 10:30 AM
|
#12521
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 6,027
|
Quote:
Originally Posted by Grotteko
Ok, so I've set it up like you described (I think...) but it still behaves a little wierd. The selection is working. So when I select a channel the sends are mapped to that channel. But all the knobs are still connected to one send. And that send corresponds to the number of sends I put in when setting up the controller. So if I put in 8 sends, all knobs will control send 8 on the selected channel. If i select 2 sends all of them will control number 2 etc.
|
Ok, do this...
1. In your mst, rename Rotary2 from RotaryB to RotaryB1
2. Rename RotaryC to RotaryB2
3. Rename RotaryD to RotaryB3, etc.
4. Do the same for the Push Messages (RotaryPushB becomes RotaryPushB1)
So you should have RotaryB1 through RotaryB7 and RotaryPushB1 through RotaryPushB7. Once you do, change the send section of your .zon file to look like this...
Code:
Zone "Send"
SendNavigator
RotaryB| TrackSendVolume
RotaryPushB| TrackSendPrePost
ZoneEnd
That says RotaryB1-RotaryB7 control TrackSendVolume1-7. That's the proper syntax for what you're trying to do. Don't use RotaryB, RotaryC, RotaryD, because it won't work.
Also, since Pan is hard coded to the one Rotary, you technically only have 7 sends.
|
|
|
02-22-2021, 12:16 PM
|
#12522
|
Human being with feelings
Join Date: Mar 2020
Location: IJsselstein, Netherlands
Posts: 435
|
Reapinger BCF new version (v0.1.1)
I just released a new version of the Reapinger BCF2000 CSI files.
Version 1 of CSI is now supported. Also made some minor improvements.
This version can be found here: https://stash.reaper.fm/v/39995/reap...000-v0.0.3.zip
|
|
|
02-22-2021, 01:35 PM
|
#12523
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,251
|
Quote:
Originally Posted by Navelpluisje
|
Thanks for this effort !
Will be included in next build.
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
|
|
|
02-23-2021, 12:21 AM
|
#12524
|
Human being with feelings
Join Date: Mar 2020
Location: IJsselstein, Netherlands
Posts: 435
|
Quote:
Originally Posted by Geoff Waddington
Thanks for this effort !
|
You're welcome
Quote:
Originally Posted by Geoff Waddington
Will be included in next build.
|
Thanx, sounds great
|
|
|
02-23-2021, 04:58 AM
|
#12525
|
Human being with feelings
Join Date: Oct 2019
Location: Örebro, Sweden
Posts: 12
|
Quote:
Originally Posted by Funkybot
Ok, do this...
1. In your mst, rename Rotary2 from RotaryB to RotaryB1
2. Rename RotaryC to RotaryB2
3. Rename RotaryD to RotaryB3, etc.
4. Do the same for the Push Messages (RotaryPushB becomes RotaryPushB1)
So you should have RotaryB1 through RotaryB7 and RotaryPushB1 through RotaryPushB7. Once you do, change the send section of your .zon file to look like this...
Code:
Zone "Send"
SendNavigator
RotaryB| TrackSendVolume
RotaryPushB| TrackSendPrePost
ZoneEnd
That says RotaryB1-RotaryB7 control TrackSendVolume1-7. That's the proper syntax for what you're trying to do. Don't use RotaryB, RotaryC, RotaryD, because it won't work.
Also, since Pan is hard coded to the one Rotary, you technically only have 7 sends.
|
Thank you, I understand a bit more how it works now. I read the documentation on the | sign and got it up and running with the code you provided.
I have one final thing that would make it work a little better. The display is currently showing track name and pan which is how i want it. What would be great though would be to se the send name and pre/post state for the send knob i turn. I'm a little confused though how to solve it. I started out by using the go zone command to trigger a zone with those display elements in it. I get it to work for the first channel. So when i turn a a knob it show info on send number 1 but not the other sends. I also don't know how to get out of the zone and back to the original state correctly.
How would I go about this? This is my code as of now:
Code:
Zone "Send"
SendNavigator
RotaryB| TrackSendVolume
RotaryPushB| TrackSendPrePost
RotaryB| GoZone Display
ZoneEnd
Zone "Display"
DisplayUpper| TrackSendNameDisplay
DisplayLower| TrackSendVolumeDisplay
Cancel GoZone Home
ZoneEnd
|
|
|
02-23-2021, 05:09 AM
|
#12526
|
Human being with feelings
Join Date: Jun 2013
Location: Krefeld, Germany
Posts: 14,784
|
@Geoff, just to let you know...
There seems to be a general compatibility problem with the OSC implementation by Behringer (e.g. X32 and XR18)
see -> https://forum.cockos.com/showthread....13#post2409813
-Michael
|
|
|
02-25-2021, 10:31 PM
|
#12527
|
Human being with feelings
Join Date: Aug 2006
Location: Berlin
Posts: 11,818
|
Send related question
I have a send zone setup on the Faderport 16 that looks like this:
Code:
Zone "Send"
SendNavigator
FPDisplayA| FixedTextDisplay "Send"
FPDisplayB| TrackSendVolumeDisplay
FPDisplayC| TrackSendNameDisplay // only displays 4-6 characters
Fader| TrackSendVolume
Mute| TrackSendMute // only works with trim/read send mutes, not the automatable ones
BankLeft TrackSendBank "-16"
BankRight TrackSendBank "16"
ZoneEnd
It is accessed through this
Code:
Send MapSelectedTrackSendsToWidgets
This gives me all sends of the selected track.
Now I'd like to do a zone that gives me Send 1 or 2 or 3 etc. , of the currently displayed tracks.
Thus if tracks 10-25 are currently displayed and I access that new send zone, it should display send 1 of each track on the corresponding fader. Banking with a button or dial, would bank to send 2,3,etc. Or I could setup SELECT buttons to access those sends for all tracks.
Is this possible ?
And is this possible and still have the standard send zone available as well as described at the top of this post ?
My current approach to this would be to have one zone per send. I'll try to set this up today, but perhaps someone can enlighten me and save a little time .
I'm presuming this may require the track navigator.
|
|
|
02-26-2021, 06:15 AM
|
#12529
|
Human being with feelings
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 11,251
|
Quote:
Originally Posted by airon
|
Thanks, will investigate, but I seem to recall looking at this before and coming to the conclusion that on/off automation params are not supported in the exposed Reaper API used to control such things.
__________________
To install you need the CSI Software and Support Files
For installation instructions and documentation see the Wiki
Donate -- via PayPal to waddingtongeoff@gmail.com
|
|
|
02-26-2021, 08:38 AM
|
#12530
|
Human being with feelings
Join Date: Aug 2006
Location: Berlin
Posts: 11,818
|
Well, go and give Justin and Schwa a slap on the ass.
The Reaper actions can handle this so it's just an API thing if anything. They may be able to find a solution in an afternoon.
That said, the send mutes are not exposed via OSC either in Reapers own OSC csurf either. I use actions there too.
Time to crack a whip. It's an oversight. That's my guess.
|
|
|
02-28-2021, 02:46 PM
|
#12531
|
Human being with feelings
Join Date: Jun 2010
Location: UK
Posts: 412
|
EDIT: ignore, got it.
I'm just implementing the encoder feedback for X-Touch XCtrl mode (time display is done). Are the different pan display modes still used? "TrackPan <x>" doesn't seem to change anything:
Quote:
Originally Posted by Geoff Waddington
TrackPan "0" means display Track Pan using MCU display mode 0.
The display modes --
0 = line (e.g. pan)
1 = boost/cut (e.g. eq)
2 = fill from right (e.g. level)
3 = center fill (e.g. Q)
|
Last edited by DeBased; 02-28-2021 at 02:53 PM.
|
|
|
03-03-2021, 12:42 AM
|
#12532
|
Human being with feelings
Join Date: Aug 2012
Location: Riga Latvia
Posts: 194
|
FX Zone for JSFX
I'm trying to do my first babysteps in CSI world. I have an Behringer Xtouch mini and have success with making/customising .zon files for plugins like ReaEQ, TDR VOS SlickEQ. I just make ZoneRawFXFile with action "CSI Toggle Write Params to /CSI/Zones/ZoneRawFXFiles when FX inserted" and there it goes.
I have no success with trying to do same thing for JSFX plugins like SonicAnomaly S.LA.X, Mrelwood's Sky. JSFX's controls doesn't correspond to rotary moves. When controls is moved by mouse, hardware rotary leds chaotically tries to catch these moves.
Reaper "bypass" and "wet" controls works as expected.
Is there any workarounds? In whitch direction i must dig deeper?
This is very basic .zon file for S.LA.X made by me.
Code:
Zone "JS: S.LA.X"
SelectedTrackNavigator
Rotary1 FXParam 0 "Peak"
Rotary8 FXParam 1 "Gain"
Rotary7 FXParam 2 "Comp/Lim"
Rotary2 FXParam 3 "Emphasis"
UpperButton8 FXParam 4 "Mode"
LowerButton8 FXParam 5 "Bypass"
Fader FXParam 6 "Wet"
ZoneEnd
Last edited by jazznfunk; 03-03-2021 at 02:00 PM.
Reason: typo & format
|
|
|
03-03-2021, 02:32 AM
|
#12533
|
Human being with feelings
Join Date: Sep 2017
Posts: 998
|
Quote:
Originally Posted by jazznfunk
I'm trying to do my first babysteps in CSI world. I have an Behringer Xtouch mini and have success with making/customising .zon files for plugins like ReaEQ, TDR VOS SlickEQ. I just make ZoneRawFXFile with "CSI Toggle Write Params to /CSI/Zones/ZoneRawFXFiles when FX inserted" and there it goes.
I have no success with trying to do same ting for JSFX plugins like SonicAnomaly S.LA.X, Mrelwood's Sky. JSFX's controls doesn't correspond to rotary moves. When controls is moved by mouse, hardware rotary leds chaotically tries to catch these moves.
Reaper "bypass" and "wet" controls works as expected.
Is there any workarounds? In whitch direction i must dig deeper?
This is very basic .zon file for S.LA.X made by me.
Zone "JS: S.LA.X"
SelectedTrackNavigator
Rotary1 FXParam 0 "Peak"
Rotary8 FXParam 1 "Gain"
Rotary7 FXParam 2 "Comp/Lim"
Rotary2 FXParam 3 "Emphasis"
UpperButton8 FXParam 4 "Mode"
LowerButton8 FXParam 5 "Bypass"
Fader FXParam 6 "Wet"
ZoneEnd
|
All VST parameters have a range of 0 to 1 regardless of what the GUI says. JS plugins do not work like that, the parameters have ranges of whatever the developer would like. To figure this out, you can hit the edit button on the GUI of the JSFX. Doing that on S.LA.X and you'll see this section near the top:
Code:
slider1:0<0,10,0.1>-Peak
slider2:0<0,10,0.1>-Gain
slider3:5<0,10,0.1>-Comp/Lim
slider4:10<0,10,0.1>-Emphasis
slider5:1<0,2,1{Flat,Fat 1,Fat 2}>-Mode
The numbers on each line between the <> is the information you want to know.
<low number of range, high number of range, step size>
In CSI you can define the range of a parameter like this:
Code:
Rotary1 FXParam 0 "Peak" [ 0.0>10.0 ]
With the mode parameter on the button, you'll want to define a range and then use stepped parameters like this:
Code:
UpperButton8 FXParam 4 "Mode" [ 0.0>2.0 0.0 1.0 2.0 ]
The encoder LEDs will still act as you see them when you move the GUI with the mouse because CSI does not yet interpolate the results on the feedback processors when a range of a parameter is outside the normal 0 to 1.
See down the page a bit here for more cool stuff: https://github.com/GeoffAWaddington/.../wiki/Encoders
In particular, if the x-touch mini has acceleration, you're going to want to set that up because that takes controlling plugins to another level.
|
|
|
03-03-2021, 02:51 AM
|
#12534
|
Human being with feelings
Join Date: Aug 2012
Location: Riga Latvia
Posts: 194
|
cjewellstudios, thank You very much for clarification, can't wait evening to try it out @home!
Last edited by jazznfunk; 03-04-2021 at 12:20 AM.
|
|
|
03-03-2021, 04:10 PM
|
#12535
|
Human being with feelings
Join Date: Mar 2021
Posts: 6
|
Making a new OSC surface for IGNITE QUICbox
Thanks to Geoff for this very fascinating addition to Reaper.
I have several of these interesting IGNITE QUICbox desks:
https://www.jlcooper.com/_images/_ga.../oem_00100.jpg
Quite nice, well made with 16 motorised faders, lots of LEDS, LCD screen backlit
buttons with 64 colours, 2x40 character VFD display etc.
I want to use them as a control surface with Reaper.
I have worked out the TCP/IP protocol they talk, and I have written an interface program that
converts (in a pretty hardwired way) between its TCP commands and OSC.
It works fine against Reaper, using the builtin
Reaper OSC support and using Reapers default config Default.ReaperOSC. So far so good.
But I would like to make it work with Geoffs CSI interface via OSC, because
of the flexibility that would bring. I can invent and define whatever OSC interface I
like for this device, and have made some progress at making it interoperate with CSI over OSC.
But some issues remain, that I think are mainly due to the young age of the CSI OSC support:
1. Looking at the source, it appears there are only 3 things supported inside an OSC Widget:
Control
Touch
FB_Processor
- Control: seems to work fine with any fader or button. Faders are normalised
floats and buttons send as 0.0 or 1.1. I can use this to control Reaper faders and buttons like Mute, Solo, etc
- Touch: Dont really know what this is for. Can anyone enlighten me?
- FB_Processor seems to be able to handle feedback of any normalised float or text based Action that works with OSC.
I can use it to set track titles, fixed text, move faders, turn LEDS on and off etc.
Is there more needed or planned?
2. When I have a TrackNavigator zone set up and a fader configured to work with a
Widget in CSI and thus control a Reaper TrackVolume,
the fader does indeed change the track volume in Reaper and the changing the track volume in reaper moves the fader. BUT...
when I move the fader, CSI is continually sending back fader FB_Processor feedback from recently
received fader Control messages back to the originating Widget,
and which by then is slightly out of date. The result is that the fader keeps 'kicking' under your fingers and often wont
stay where you left it.
I know that when you use the native OSC support in Reaper, when you update a track volume from an OSC surface,
Reaper politely does NOT feed that motion back to the originating OSC surface, so your fader stops where you leave it.
Perhaps this has something to do with Touch above?
3. It appears that TimeDisplay action is not yet implemented for OSC (it seems to be for EuCon), so there is no way for me
to get the time/beats/etc into the VFD display. Using this:
Widget VFD
FB_PRocessor /vfd
WidgetEnd
...
Zone "Buttons"
VFD TimeDisplay
....
only results in empty strings being sent by OSC to path /vfd
(I _can_ send FixedText to VFD and it works)
Seems to be because of:
in control_surface_Reaper_actions.h:
...
class TimeDisplay : public Action
...
virtual void RequestUpdate(ActionContext* context) override
{
context->UpdateWidgetValue(0);
}
ie its not actually implemented yet.
Is it possible that might change soon?
4. I sort of think that I might like to do some initialisation and configuration of the
surface when CSI starts up, by sending some canned OSC messages to my program, maybe cause it to reinit
or to set some button icons and colours etc,
and I see there is an OnInitialization virtual widget, but it seems that it can only
trigger Reaper actions and cannot FB_PRocessor act on my real Widgets, and forcing them to send OSC to my surface.
Or do I misunderstand?
|
|
|
03-03-2021, 04:39 PM
|
#12536
|
Human being with feelings
Join Date: Sep 2017
Posts: 998
|
@mikemccauley
These are some wonderful questions. Most of which I believe are questions for Geoff.
That's a beautiful control surface. Why go through OSC? Just curious
I'm super interested in the answers to these questions because I'm currently looking into Open Stage Control because I'm having crazy issues with TouchOSC. I have a sneaky suspicion I may run into trouble and need some more OSC support from CSI, but I'm not too sure yet it's super new to me.
|
|
|
03-03-2021, 05:22 PM
|
#12537
|
Human being with feelings
Join Date: Jun 2010
Location: UK
Posts: 412
|
Quote:
Originally Posted by mikemccauley
I have several of these interesting IGNITE QUICbox desks:
|
wow cool. expensive?
Quote:
- Touch: Dont really know what this is for. Can anyone enlighten me?
|
Do you have touch-sensitive faders? if so, that . ie. the faders (and I guess knobs too) may be conductive, so they can sense when they are touched. important with motorized faders so you can grab them mid-flight and the motor will disengage and not fight you. also can be used to select tracks etc.
Can't help with the rest due to a) being new to CSI (also programming for it right now) and b) haven't used OSC for anything yet (over to Geoff).
|
|
|
03-03-2021, 06:35 PM
|
#12538
|
Human being with feelings
Join Date: Mar 2021
Posts: 6
|
Quote:
Originally Posted by cjewellstudios
@mikemccauley
These are some wonderful questions. Most of which I believe are questions for Geoff.
That's a beautiful control surface. Why go through OSC? Just curious
I'm super interested in the answers to these questions because I'm currently looking into Open Stage Control because I'm having crazy issues with TouchOSC. I have a sneaky suspicion I may run into trouble and need some more OSC support from CSI, but I'm not too sure yet it's super new to me.
|
This QUICbox does not support MIDI, just its native TCP/IP message protocol. So the only way I can see to use with Reaper is to make a translation program between OSC and its native protocol. Then I can put say a RPi or similar between them and talk to it by OSC.
|
|
|
03-03-2021, 06:39 PM
|
#12539
|
Human being with feelings
Join Date: Mar 2021
Posts: 6
|
Quote:
Originally Posted by DeBased
wow cool. expensive?
Do you have touch-sensitive faders? if so, that . ie. the faders (and I guess knobs too) may be conductive, so they can sense when they are touched. important with motorized faders so you can grab them mid-flight and the motor will disengage and not fight you. also can be used to select tracks etc.
Can't help with the rest due to a) being new to CSI (also programming for it right now) and b) haven't used OSC for anything yet (over to Geoff).
|
Yes, the faders send a message when the fader starts and end the move, and I can engineer an OSC message to be sent when those event occur. Is that what the Touch entry in a widget is supposed to work with? Cant find any doc about what Touch is in CSI nor how to work with it. Anyone know?
|
|
|
03-03-2021, 07:40 PM
|
#12540
|
Human being with feelings
Join Date: Mar 2021
Posts: 6
|
Quote:
Originally Posted by DeBased
wow cool. expensive?
|
They are not current products: a few years old, but Ive seen them on ebay for a few hundred dollars. OEM'd from JLCooper, so nicely made.
|
|
|
03-03-2021, 08:16 PM
|
#12541
|
Human being with feelings
Join Date: Mar 2021
Posts: 6
|
Quote:
Originally Posted by mikemccauley
Yes, the faders send a message when the fader starts and end the move, and I can engineer an OSC message to be sent when those event occur. Is that what the Touch entry in a widget is supposed to work with? Cant find any doc about what Touch is in CSI nor how to work with it. Anyone know?
|
OK, so after looking at the code and experimenting, I see that Touch is indeed intended to detect that the user is manually moving a fader (OSC message value 1.0), and CSI will stop sending updates to that fader until the Touch off (OSC value 0.0) is received.
Also these faders only generate touch events when you press down on the top of the fader button (ie towards the surface). Its not sufficient to just move the fader by pressing up or down against the side of the knob.
On this QUICbox, the touch detection on the faders is a bit flakey and unreliable :-(, hence still get some kickbacks from time to time. So I think that the native Reaper OSC implementation is a bit superior in this case, in that it never echoes fader moves back to the originating surface.
Anyay I now OSC faders with Touch working OK with a Widget like this in my .ost:
Widget Fader1
Control /fader/1/move
Touch /fader/1/touch
FB_Processor /fader/1/move
WidgetEnd
|
|
|
03-03-2021, 10:07 PM
|
#12542
|
Human being with feelings
Join Date: Mar 2021
Posts: 6
|
Quote:
Originally Posted by DeBased
Do you have touch-sensitive faders? if so, that . ie. the faders (and I guess knobs too) may be conductive, so they can sense when they are touched. important with motorized faders so you can grab them mid-flight and the motor will disengage and not fight you. also can be used to select tracks etc.
|
Quite right, it turns out these faders are touch sensitive, prob capacitive, and only work reasonably reliably if you are touching the housing of the QUICbox as well as touching the fader knob with your fingertip (not fingernail)
|
|
|
03-03-2021, 11:33 PM
|
#12543
|
Human being with feelings
Join Date: Jun 2013
Location: Krefeld, Germany
Posts: 14,784
|
Quote:
Originally Posted by mikemccauley
So the only way I can see to use with Reaper is to make a translation program between OSC and its native protocol.
|
I feel Midi instead of OSC would be easier with CSI. And of course OSCIIBot can do this just as well (you would need LoopMidi, additionally). But I do see that you initially wanted to do "native" Reaper support.
-Michael
|
|
|
03-04-2021, 12:22 AM
|
#12544
|
Human being with feelings
Join Date: Aug 2012
Location: Riga Latvia
Posts: 194
|
Quote:
Originally Posted by cjewellstudios
All VST parameters have a range of 0 to 1 regardless of what the GUI says. JS plugins do not work like that, the parameters have ranges of whatever the developer would like. To figure this out, you can hit the edit button on the GUI of the JSFX. Doing that on S.LA.X and you'll see this section near the top:
Code:
slider1:0<0,10,0.1>-Peak
slider2:0<0,10,0.1>-Gain
slider3:5<0,10,0.1>-Comp/Lim
slider4:10<0,10,0.1>-Emphasis
slider5:1<0,2,1{Flat,Fat 1,Fat 2}>-Mode
|
This Parameter works as expected:
Code:
UpperButton8 FXParam 4 "Mode" [ 0.0>2.0 0.0 1.0 2.0 ]
Still no luck with:
Code:
Rotary1 FXParam 0 "Peak" [ 0.0>10.0 ]
but S.LA.X's "Peak" knob steps between 0 of 10 and 1 of 10 on dial, when i put this in brackets: (like for stepped controls)
Code:
Rotary1 FXParam 0 "Peak" [ 0.0 1.0 ]
If i understand correctly, do i miss something like a multiplier/divider to match up CSI and JSFX parameter ranges?
|
|
|
03-04-2021, 04:18 AM
|
#12545
|
Human being with feelings
Join Date: Jun 2010
Location: UK
Posts: 412
|
Quote:
Originally Posted by mikemccauley
Quite right, it turns out these faders are touch sensitive, prob capacitive, and only work reasonably reliably if you are touching the housing of the QUICbox as well as touching the fader knob with your fingertip (not fingernail)
|
that's annoying. if you can find a service manual or open one up, there may be a touch sensitivity adjustment somewhere.
|
|
|
03-04-2021, 12:18 PM
|
#12546
|
Human being with feelings
Join Date: Jun 2018
Posts: 4
|
I must be missing something
I'm getting my feet wet with CSI and my FaderPort 16. I am trying to just get one button working.
Code:
Widget SoloClear
Press 90 01 7f
WidgetEnd
and just to perform the most basic action
Code:
Zone "Solo Clear"
SoloClear Play
ZoneEnd
When I hit the Solo Clear button it should start the transport. I have verified the midi data with MIDI monitor. I edit it with Reaper exited. Can I assume if I edit, the next time reaper runs both the ZON and MST get reloaded? I also can't see where the physical button is defined in the widget.
|
|
|
03-04-2021, 01:52 PM
|
#12547
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 6,027
|
Quote:
Originally Posted by jgourd
I'm getting my feet wet with CSI and my FaderPort 16. I am trying to just get one button working.
Code:
Widget SoloClear
Press 90 01 7f
WidgetEnd
and just to perform the most basic action
Code:
Zone "Solo Clear"
SoloClear Play
ZoneEnd
When I hit the Solo Clear button it should start the transport. I have verified the midi data with MIDI monitor. I edit it with Reaper exited. Can I assume if I edit, the next time reaper runs both the ZON and MST get reloaded? I also can't see where the physical button is defined in the widget.
|
Are you missing the "Home" zone? Try this...
Code:
Zone "Home"
IncludedZones
"Buttons"
IncludedZonesEnd
ZoneEnd
Zone "Buttons"
SoloClear Play
ZoneEnd
|
|
|
03-04-2021, 01:54 PM
|
#12548
|
Human being with feelings
Join Date: Aug 2015
Posts: 5
|
Gotta say, this thing is amazing!
I recently got a novation launchkey mini Mk3 and the CSI is making it a really great controller.
Also props to the WIKI... I wouldn't have got anywhere near as far as I did without that reference.
I do have a question, and it may just be me being silly...
Is there a way (action) to allow the midi data to passthrough the CSI and directly to reaper?
If not
Is there an action that can send midi back to the device?
Let me explain;
One of the launchkey's features is a drum mode, which when selected turns all the pads to midi notes (technically the pads are notes in "session" mode too but since I am linking them to actions, the midi data doesn't matter past the mst file).
When the launchkey is set to "DAW control", this drum mode sends the same data but through midi2 port (the one that it uses as control data and the one I have linked to CSI)... It does this so that the DAW can send it pad light feedback, but now I can't find a way to get these 16 notes out of CSI and back into reaper.
My first idea was to make a background lua script and pass it data from CSI (so hitting pad 1 would send that script a "1" or whatever) and translate that to note hits on the virtual keyboard. But I couldn't find a way for CSI to pass the midi (or arbitrary number) to the script.
Then I realised I was probably complicating it and just needed to pass certain midi through as if it was a normal reaper midi device (I can't enable it as a normal midi input device in reaper because then of course it will pass ALL the data through)
Alternatively I could just send the launchkey a midi message (same port used for feedback) when I hit the button to go into this drum mode (it sends out a CC message but sets up the pads internally) to go back to "normal control" and then it will output to the midi1 port, no issue. and then I can just press another button and enter the "DAW control" mode again.
The only issue with this mode is that I'm not sure how to send a message back to the launchkey through CSI. The reason I trick it into "DAW control" to begin with is having a dummy widget with a FB_TwoState feedback and send the same control to both states of this widget, so it just loads up like this when CSI initialises.
Sorry for the wall of text. I didn't expect my bad explanations to be this long.
|
|
|
03-04-2021, 03:03 PM
|
#12549
|
Human being with feelings
Join Date: Jun 2010
Location: UK
Posts: 412
|
Quote:
Originally Posted by jgourd
Can I assume if I edit, the next time reaper runs both the ZON and MST get reloaded?
|
yep but there's a quicker way, search reaper Actions for 'Refresh all Control Surfaces' (IIRC), that reloads everything on the fly.
|
|
|
03-05-2021, 03:10 AM
|
#12550
|
Human being with feelings
Join Date: Aug 2006
Location: Berlin
Posts: 11,818
|
Quote:
Originally Posted by jazznfunk
This Parameter works as expected:
Code:
UpperButton8 FXParam 4 "Mode" [ 0.0>2.0 0.0 1.0 2.0 ]
Still no luck with:
Code:
Rotary1 FXParam 0 "Peak" [ 0.0>10.0 ]
but S.LA.X's "Peak" knob steps between 0 of 10 and 1 of 10 on dial, when i put this in brackets: (like for stepped controls)
Code:
Rotary1 FXParam 0 "Peak" [ 0.0 1.0 ]
If i understand correctly, do i miss something like a multiplier/divider to match up CSI and JSFX parameter ranges?
|
If in doubt, record some automation with the parameter controls of the plugin, and then take a look at the Reaper session in a text editor. You'll get your parameter range there.
Quote:
Originally Posted by jgourd
I'm getting my feet wet with CSI and my FaderPort 16. I am trying to just get one button working.
Code:
Widget SoloClear
Press 90 01 7f
WidgetEnd
and just to perform the most basic action
Code:
Zone "Solo Clear"
SoloClear Play
ZoneEnd
When I hit the Solo Clear button it should start the transport. I have verified the midi data with MIDI monitor. I edit it with Reaper exited. Can I assume if I edit, the next time reaper runs both the ZON and MST get reloaded? I also can't see where the physical button is defined in the widget.
|
Have you had a look at the Faderport 16 MST and ZONE files that come with CSI ?
The MST at least is a good starting point, and the main zone file offers hints at where to start if you want to customize the unit to your liking. I wrote and use it everyday.
Quote:
Originally Posted by DeBased
yep but there's a quicker way, search reaper Actions for 'Refresh all Control Surfaces' (IIRC), that reloads everything on the fly.
|
The other method is to keep the Preferences / Control/OSC/web window open, select the "Control Surface Integrator" entry and hit the EDIT button button below. Hit the OK button on the window that pops up and CSI will reload.
|
|
|
03-05-2021, 05:43 AM
|
#12551
|
Human being with feelings
Join Date: Dec 2019
Posts: 193
|
First of all, I gotta say this is an amazing addition to Reaper, so a big thanks to everyone involved!
Second, I just got an Avid S1, and it's working great with the Eucon module + CSI.
I was wondering if it's possible to add support for track colors.
When working with Pro Tools / Cubase or any other native Eucon app, the bottom row of colors correspond to the track colors.
I know it's a bit nitpicky, but the colors really help locating oneself within the session.
Any chance of implementing it? Or maybe there's some configuration I should be doing to get it to work?
|
|
|
03-06-2021, 11:26 AM
|
#12552
|
Human being with feelings
Join Date: Jan 2018
Posts: 1,651
|
hey all, long time no talk hope everyone has been well. As usual, CSI is working flawlessly for me.
Just wondering, any breaking updates since Sept 2020? Breaking as in both new and could possibly "break" if I don't change some syntax somewhere?
cheers!
|
|
|
03-06-2021, 11:30 AM
|
#12553
|
Human being with feelings
Join Date: Jul 2007
Location: New Joisey
Posts: 6,027
|
Quote:
Originally Posted by poetnprophet
hey all, long time no talk hope everyone has been well. As usual, CSI is working flawlessly for me.
Just wondering, any breaking updates since Sept 2020? Breaking as in both new and could possibly "break" if I don't change some syntax somewhere?
cheers!
|
September 2020 was already the 1.x builds right? I don't think there have been any breaking changes since then.
|
|
|
03-07-2021, 09:20 AM
|
#12554
|
Human being with feelings
Join Date: Jul 2007
Location: London, UK
Posts: 1,217
|
Could anyone please confirm if this is the current expected with the X Touch One? If I press one of the CHANNEL SELECT buttons (either left or right), the unit shows the name of the name on the control surface but doesn't actually select it so the buttons are actually still active to the previously selected track.
This was not the way it used to work before CSI v1.0 was released and it is a massive step backwards if this is the case. I would like to use the current version but have the same functionality as before - in other words, when I press either of the CHANNEL <> buttons, the unit should move to the next track and automatically select it ("TrackUniqueSelect" maybe?).
Any info would be much appreciated.
|
|
|
03-07-2021, 10:10 AM
|
#12555
|
Human being with feelings
Join Date: Aug 2015
Posts: 5
|
Quote:
Originally Posted by susbemol
Could anyone please confirm if this is the current expected with the X Touch One? If I press one of the CHANNEL SELECT buttons (either left or right), the unit shows the name of the name on the control surface but doesn't actually select it so the buttons are actually still active to the previously selected track.
This was not the way it used to work before CSI v1.0 was released and it is a massive step backwards if this is the case. I would like to use the current version but have the same functionality as before - in other words, when I press either of the CHANNEL <> buttons, the unit should move to the next track and automatically select it ("TrackUniqueSelect" maybe?).
Any info would be much appreciated.
|
Not a X Touch One user, but perhaps the other zone file for this control surface is what you are looking for?
There is a;
X-Touch_One_Standard
and a;
X-Touch_One_SelectedTrack
The latter looks like it will fit your needs perhaps (as the Channel left and right buttons switch tracks, not CSI banks)
|
|
|
03-07-2021, 10:19 AM
|
#12556
|
Human being with feelings
Join Date: Jul 2007
Location: London, UK
Posts: 1,217
|
Quote:
Originally Posted by chriswinter
Not a X Touch One user, but perhaps the other zone file for this control surface is what you are looking for?
There is a;
X-Touch_One_Standard
and a;
X-Touch_One_SelectedTrack
The latter looks like it will fit your needs perhaps (as the Channel left and right buttons switch tracks, not CSI banks)
|
I was under the impression that I had tried this initially but clearly that wasn't the case as it works! Thanks so much for that, I can't believe I failed to notice this but I think I'm all sorted for now.
|
|
|
03-07-2021, 10:26 AM
|
#12557
|
Human being with feelings
Join Date: Aug 2015
Posts: 5
|
Quote:
Originally Posted by chriswinter
I could just send the launchkey a midi message (same port used for feedback) when I hit the button to go into this drum mode (it sends out a CC message but sets up the pads internally) to go back to "normal control" and then it will output to the midi1 port, no issue. and then I can just press another button and enter the "DAW control" mode again.
|
I finally got this way working with a bit of duct tape.
For potential future reference if anybody else gets a similar situation...
Code:
Zone "Home"
IncludedZones
"Normal"
IncludedZonesEnd
ZoneEnd
Zone "DAW"
// NoAction = button off, so switches DAW mode on
ButtonModeDrum NoAction
// When pressed will go to normal zone which will turn DAW mode off
ButtonModeCustom GoZone Normal
ZoneEnd
Zone "Normal"
// When press drum mode, switch off DAW mode by turning Normal mode on
ButtonModeDrum Reaper _RS68f37bf856bd88df8dd1087f1840c07e1a46e3b7 //Custom Action: Toggle state Always on
ButtonModeDrum GoZone DAW
ZoneEnd
And then in my .mst file I have twostate feedback on both ButtonModeDrum and ButtonModeCustom that switches DAW mode off when in the off state, and DAW mode on when in the on state.
So I now have it working, not the way it's probably ever intended to be used but hey... works for me.
That being said a action of "send to control surface" would be very useful and I'm sure not just for me either. Something along the lines of...
Code:
ButtonPress1 SendFeedback {99 24 7f}
Nothing fancy, just a 7bit thing will do (since you could technically string them together in a "macro" for a lot of information)
|
|
|
03-08-2021, 04:24 AM
|
#12558
|
Human being with feelings
Join Date: Apr 2018
Posts: 11
|
Hi everyone,
It is possible to set up Behringer X-Touch mini? After several tries, I failed. If this question has already been discussed here, I apologize. I couldn't find it.
|
|
|
03-08-2021, 05:00 AM
|
#12559
|
Human being with feelings
Join Date: Sep 2017
Posts: 998
|
Quote:
Originally Posted by losj8
Hi everyone,
It is possible to set up Behringer X-Touch mini? After several tries, I failed. If this question has already been discussed here, I apologize. I couldn't find it.
|
It definitely should be possible. I do believe someone here uses one.
How far have you gotten?
Is the x-touch mini disabled in Reaper preferences? (It should be)
Search the action list for CSI and "toggle input from surfaces" and move a knob and see if you get any action there.
The other thing that maybe tripping you up is it looks like theres an MCU mode and a user mode with two layers. They both should technically work. It's just the right mst file and zone need to be used.
Some more details of what you've done so far and where you're at in the process will help us nail down what we need to do next.
|
|
|
03-08-2021, 02:40 PM
|
#12560
|
Human being with feelings
Join Date: Apr 2018
Posts: 11
|
Quote:
Originally Posted by cjewellstudios
It definitely should be possible. I do believe someone here uses one.
How far have you gotten?
Is the x-touch mini disabled in Reaper preferences? (It should be)
Search the action list for CSI and "toggle input from surfaces" and move a knob and see if you get any action there.
The other thing that maybe tripping you up is it looks like theres an MCU mode and a user mode with two layers. They both should technically work. It's just the right mst file and zone need to be used.
Some more details of what you've done so far and where you're at in the process will help us nail down what we need to do next.
|
I made some progress and was able to get the MC mode to work. But I would like to configure the controller more for managing plugins, and this is exactly what I can't do. I switched the controller to normal mode and changed the mst and zon in the settings and it seems that there is a connection. The solo buttons that are configured by default work, but when I try to configure the ReaComp, nothing doesn't work. Maybe I'm doing something wrong. I created a file in the zones folder with the following content:
Code:
Zone "VST: ReaComp (Cockos)" ReaComp
SelectedTrackNavigator
RotaryA1 FXParam 0 "Thresh"
FaderA FXParam 1 "Ratio"
RotaryPushA1 FXParam 16 "AutoRel"
ZoneEnd
Last edited by losj8; 03-09-2021 at 02:35 AM.
|
|
|
Thread Tools |
|
Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 02:11 PM.
|