Go Back   Cockos Incorporated Forums > REAPER Forums > MIDI Hardware, Control Surfaces, and OSC

Reply
 
Thread Tools Display Modes
Old 11-28-2020, 06:04 AM   #11841
Funkybot
Human being with feelings
 
Join Date: Jul 2007
Posts: 2,011
Default

Quote:
Originally Posted by spkr4thdd View Post
Hi guys,

I’ve been away with RL work for the past 2-3 months and have come back to a whole new world of V1 CSI!!

Is there a list somewhere of any major changes which I’ll need to know before diving straight back in??

Also, does anyone know who this guy is? I want to find out how he has his FX set up and how he has the buttons mapped...

https://youtu.be/QD1o0JenoNE
There were some pretty minor syntax changes outlined here:

https://forum.cockos.com/showpost.ph...ostcount=11490
Funkybot is online now   Reply With Quote
Old 11-28-2020, 10:26 AM   #11842
kevrose
Human being with feelings
 
Join Date: Dec 2009
Location: That London they have now
Posts: 93
Default

Quote:
Originally Posted by MixMonkey View Post
Doh! You know, I might change this to just dump the completed Zone on the Desktop! (everyone has a desktop) The saving and loading is so convoluted because of the way VBA is implemented on the Mac. The load folder (ZoneRawFXFiles) will be there because it's where CSI outputs the RawParameter file.

Sure thing:
Code:
Zone "VST: TDR VOS SlickEQ (Tokyo Dawn Labs)" "VOS_EQ"
SelectedTrackNavigator
/
/
DisplayUpperA1 FXParamNameDisplay 22 "VOS_EQ"
DisplayLowerA1 FXParamValueDisplay 22  
RotaryA1 FXParam 22 [ (0.001,0.005,0.025,0.05,0.1) ]
RotaryPushA1 FXParam 21 [ 0.0 1.0 ]
/   
DisplayUpperA2 NoAction  
DisplayLowerA2 NoAction  
RotaryA2 NoAction  
RotaryPushA2 NoAction  
/   
DisplayUpperA3 NoAction  
DisplayLowerA3 NoAction  
RotaryA3 NoAction  
RotaryPushA3 NoAction  
/   
DisplayUpperA4 FXParamNameDisplay 20 "Qual"
DisplayLowerA4 FXParamValueDisplay 20  
RotaryA4 FXParam 20 [ (0.001,0.005,0.025,0.05,0.1) ]
RotaryPushA4 FXParam 20 [ 0.0 1.0 ]
/   
DisplayUpperA5 FXParamNameDisplay 9 "Sat"
DisplayLowerA5 FXParamValueDisplay 9  
RotaryA5 FXParam 9 [ (0.001,0.005,0.025,0.05,0.1) ]
RotaryPushA5 FXParam 9 [ 0.0 1.0 ]
/   
DisplayUpperA6 FXParamNameDisplay 15 "Mode"
DisplayLowerA6 FXParamValueDisplay 15  
RotaryA6 FXParam 15 [ (4,4,3,2,1) 0.0 0.20 0.40 0.60 0.80 1.0 ]
RotaryPushA6 FXParam 15 [ 0.0 0.20 0.40 0.60 0.80 1.0 ]  
/   
DisplayUpperA7 NoAction  
DisplayLowerA7 NoAction  
RotaryA7 NoAction  
RotaryPushA7 NoAction  
/   
DisplayUpperA8 NoAction  
DisplayLowerA8 NoAction  
RotaryA8 NoAction  
RotaryPushA8 NoAction  
/   
DisplayUpperB1 FXParamNameDisplay 2 "Shape"
DisplayLowerB1 FXParamValueDisplay 2  
RotaryB1 FXParam 2 [ (0.001,0.005,0.025,0.05,0.1) ]
RotaryPushB1 FXParam 2 [ 0.0 1.0 ]
/   
DisplayUpperB2 FXParamNameDisplay 8 "Model"
DisplayLowerB2 FXParamValueDisplay 8  
RotaryB2 FXParam 8 [ (0.001,0.005,0.025,0.05,0.1) ]
RotaryPushB2 FXParam 8 [ 0.0 0.34 0.67 1.0 ]
/   
DisplayUpperB3 FXParamNameDisplay 7 "Shape"
DisplayLowerB3 FXParamValueDisplay 7  
RotaryB3 FXParam 7 [ (0.001,0.005,0.025,0.05,0.1) ]
RotaryPushB3 FXParam 7 [ 0.0 1.0 ]
/   
DisplayUpperB4 NoAction  
DisplayLowerB4 NoAction  
RotaryB4 NoAction  
RotaryPushB4 NoAction  
/   
DisplayUpperB5 NoAction  
DisplayLowerB5 NoAction  
RotaryB5 NoAction  
RotaryPushB5 NoAction  
/   
DisplayUpperB6 NoAction  
DisplayLowerB6 NoAction  
RotaryB6 NoAction  
RotaryPushB6 NoAction  
/   
DisplayUpperB7 NoAction  
DisplayLowerB7 NoAction  
RotaryB7 NoAction  
RotaryPushB7 NoAction  
/   
DisplayUpperB8 NoAction  
DisplayLowerB8 NoAction  
RotaryB8 NoAction  
RotaryPushB8 NoAction  
/   
DisplayUpperC1 FXParamNameDisplay 1 "LF"
DisplayLowerC1 FXParamValueDisplay 1  
RotaryC1 FXParam 1 [ (0.001,0.005,0.025,0.05,0.1) ]
RotaryPushC1 NoAction  
/   
DisplayUpperC2 FXParamNameDisplay 4 "MF"
DisplayLowerC2 FXParamValueDisplay 4  
RotaryC2 FXParam 4 [ (0.001,0.005,0.025,0.05,0.1) ]
RotaryPushC2 NoAction  
/   
DisplayUpperC3 FXParamNameDisplay 6 "HF"
DisplayLowerC3 FXParamValueDisplay 6  
RotaryC3 FXParam 6 [ (0.001,0.005,0.025,0.05,0.1) ]
RotaryPushC3 NoAction  
/   
DisplayUpperC4 NoAction  
DisplayLowerC4 NoAction  
RotaryC4 NoAction  
RotaryPushC4 NoAction  
/   
DisplayUpperC5 FXParamNameDisplay 11 "Stage"
DisplayLowerC5 FXParamValueDisplay 11  
RotaryC5 FXParam 11 [ 0.0 0.25 0.50 0.75 1.0 ]
RotaryPushC5 FXParam 11 [ 0.0 0.25 0.50 0.75 1.0 ]
/   
DisplayUpperC6 FXParamNameDisplay 12 "Drive"
DisplayLowerC6 FXParamValueDisplay 12  
RotaryC6 FXParam 12 [ (0.001,0.005,0.025,0.05,0.1) ]
RotaryPushC6 NoAction  
/   
DisplayUpperC7 NoAction  
DisplayLowerC7 NoAction  
RotaryC7 NoAction  
RotaryPushC7 NoAction  
/   
DisplayUpperC8 NoAction  
DisplayLowerC8 NoAction  
RotaryC8 NoAction  
RotaryPushC8 NoAction  
/   
DisplayUpperD1 FXParamNameDisplay 0 "Gain"
DisplayLowerD1 FXParamValueDisplay 0  
RotaryD1 FXParam 0  
RotaryPushD1 FXParam 16 [ 0.0 1.0 ]
/   
DisplayUpperD2 FXParamNameDisplay 3 "Gain"
DisplayLowerD2 FXParamValueDisplay 3  
RotaryD2 FXParam 3 [ (0.001,0.005,0.025,0.05,0.1) ]
RotaryPushD2 FXParam 17 [ 0.0 1.0 ]
/   
DisplayUpperD3 FXParamNameDisplay 5 "Gain"
DisplayLowerD3 FXParamValueDisplay 5  
RotaryD3 FXParam 5 [ (0.001,0.005,0.025,0.05,0.1) ]
RotaryPushD3 FXParam 18 [ 0.0 1.0 ]
/   
DisplayUpperD4 NoAction  
DisplayLowerD4 NoAction  
RotaryD4 NoAction  
RotaryPushD4 NoAction  
/   
DisplayUpperD5 FXParamNameDisplay 10 "HPF"
DisplayLowerD5 FXParamValueDisplay 10  
RotaryD5 FXParam 10 [ (0.001,0.005,0.025,0.05,0.1) ]
RotaryPushD5 NoAction  
/   
DisplayUpperD6 FXParamNameDisplay 13 "Gain"
DisplayLowerD6 FXParamValueDisplay 13  
RotaryD6 FXParam 13 [ (0.001,0.005,0.025,0.05,0.1) ]
RotaryPushD6 FXParam 19 [ 0.0 1.0 ]
/   
DisplayUpperD7 NoAction  
DisplayLowerD7 NoAction  
RotaryD7 NoAction  
RotaryPushD7 NoAction  
/   
DisplayUpperD8 NoAction  
DisplayLowerD8 NoAction  
RotaryD8 NoAction  
RotaryPushD8 NoAction  
/
ZoneEnd
Thanks so much for this, didn't reply sooner as the prospect of having a fully integrated control surface made me take my studio apart and rearrange/rewire it all!

Have started going through all my .zon files and making the changes. CSI is just great...
kevrose is offline   Reply With Quote
Old 11-28-2020, 02:34 PM   #11843
spkr4thdd
Human being with feelings
 
Join Date: Apr 2020
Location: Scotland
Posts: 74
Default

Thanks for the response, great to have that quick reference. I do have a couple of questions while I dive in...

Quote:
Originally Posted by Funkybot View Post
2. TrackTouch (widgets/actions) and/or FaderTouch (modifiers) are gone.

Remove any "touch" messages (e.g. anything looks like this) from any existing zone....
Code:
	TrackTouch+DisplayLower| 	TrackVolumeDisplay
	FaderTouch|  			TrackTouch
Remove "FaderTouch" from your surface.mst files and add a new line to your fader widgets. So this (old)...
Code:
Widget FaderTouch1
	Press 90 68 7f 90 68 00
WidgetEnd

Widget Fader1
	Fader14Bit e0 7f 7f
	FB_Fader14Bit e0 7f 7f
WidgetEnd
Gets consolidated down to this (new)...
Code:
Widget Fader1
	Fader14Bit e0 7f 7f
	FB_Fader14Bit e0 7f 7f
	Touch 90 68 7f 90 68 00
WidgetEnd
OK, I get that, but now how do I tell CSI to display the volume level in the corresponding lower display when I touch a fader?

I used to use

Code:
	TrackTouch+DisplayLower| 		TrackVolumeDisplay
Is there a new way to do that?

Quote:
Originally Posted by Funkybot View Post
4. FXMenu and Send zones have new syntax...

Replace your old Send and FXMenu zoness with this (new)...
Code:
Zone "Send"
    SendNavigator
    DisplayUpper|               TrackSendNameDisplay
    DisplayLower|               TrackSendVolumeDisplay
    Mute|                       TrackSendMute
    Fader|                      TrackSendVolume
ZoneEnd 

Zone "FXMenu"
    FXMenuNavigator
    DisplayUpper|               FXMenuNameDisplay
    DisplayLower|               NoAction
    Rotary|                     NoAction
    RotaryPush|                 GoFXSlot
ZoneEnd
I think I've got the FX. I'll play around to make sure.

Quote:
Originally Posted by Funkybot View Post
5. Toggle and Press modifiers are gone. Replaced with...

If you were using toggle and/or press modifiers in previous builds to make buttons do things, they no longer exist. Press just works. Toggles have changed.

Press (old)...
Code:
Press+SomeButton     SomeAction
New...
Code:
SomeButton     SomeAction
Toggle (old)...
Code:
Toggle+SomeButton      SomeAction
Toggle (new) (same syntax as stepped parameters, which is what they basically are)....
Code:
SomeButton      SomeAction [ 0.0 1.0 ]
Is this the case for the built in ones like 'MapSelectedTrackFX' etc?
__________________
Slainté, Grae
Mac Pro 5,1 | OSX 10.13.6 | Reaper 6.16(64) | CSI (Latest) & DBM4R (Latest) | Behringer X-Touch (1.15)
spkr4thdd is offline   Reply With Quote
Old 11-28-2020, 02:46 PM   #11844
Funkybot
Human being with feelings
 
Join Date: Jul 2007
Posts: 2,011
Default

Quote:
Originally Posted by spkr4thdd View Post
Thanks for the response, great to have that quick reference. I do have a couple of questions while I dive in...



OK, I get that, but now how do I tell CSI to display the volume level in the corresponding lower display when I touch a fader?

I used to use

Code:
	TrackTouch+DisplayLower| 		TrackVolumeDisplay
Is there a new way to do that?
FaderTouch on the displays is unfortunately gone in the current-state version of 1.0 but is planned to make a comeback in the future. Geoff has said there will eventually be some "Override" actions (Example: TrackVolumeOverride) that will take over the display upon receiving touch much messages.

Quote:
Originally Posted by spkr4thdd View Post
Is this the case for the built in ones like 'MapSelectedTrackFX' etc?
No, adding the [ 0.0 1.0 ] is unnecessary on any CSI actions that toggle.

Good luck and please post in the new CSI Device Setup thread if you have additional questions or run into trouble:

https://forum.cockos.com/showthread.php?t=245280
Funkybot is online now   Reply With Quote
Old 11-28-2020, 04:42 PM   #11845
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 5,818
Default

Quote:
Originally Posted by Funkybot View Post
FaderTouch on the displays is unfortunately gone in the current-state version of 1.0 but is planned to make a comeback in the future. Geoff has said there will eventually be some "Override" actions (Example: TrackVolumeOverride) that will take over the display upon receiving touch much messages.
Actually it will be a bit different, touch will not be involved, it is now reserved for automation:

Code:
    DisplayLower| MCUTrackPanDisplay
    Takeover+DisplayLower|  TrackVolumeDisplay
    Takeover+DisplayLower|  TrackSendVolumeDisplay
This means if you change Track Volume it will temporarily take over the Lower Display to show the Track Volume.

Similarly for Track Send Volume.

After a period of no adjustment -- likely 1.5 - 2 seconds or so -- the display will revert back to Track Pan Display
Geoff Waddington is offline   Reply With Quote
Old 11-28-2020, 05:02 PM   #11846
Funkybot
Human being with feelings
 
Join Date: Jul 2007
Posts: 2,011
Default

Seems nice and simple.
Funkybot is online now   Reply With Quote
Old 11-28-2020, 05:19 PM   #11847
Mistik
Human being with feelings
 
Join Date: Nov 2018
Posts: 13
Default

Quote:
Originally Posted by Geoff Waddington View Post
Actually it will be a bit different, touch will not be involved, it is now reserved for automation:

Code:
    DisplayLower| MCUTrackPanDisplay
    Takeover+DisplayLower|  TrackVolumeDisplay
    Takeover+DisplayLower|  TrackSendVolumeDisplay
This means if you change Track Volume it will temporarily take over the Lower Display to show the Track Volume.

Similarly for Track Send Volume.

After a period of no adjustment -- likely 1.5 - 2 seconds or so -- the display will revert back to Track Pan Display
Awesome! will this work for touched FX parameters too?
__________________
IconPlatformNano v1.1, update - WORKING - tested with CSI 1.0 (2020-12-04), nano firmware v1.14
Download here: http://e.pc.cd/NWhotalK
Mistik is offline   Reply With Quote
Old 11-28-2020, 05:52 PM   #11848
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 5,818
Default

Quote:
Originally Posted by Mistik View Post
Awesome! will this work for touched FX parameters too?
Yes any parameter that can be displayed.
Geoff Waddington is offline   Reply With Quote
Old 11-28-2020, 06:16 PM   #11849
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 1,856
Default

Quote:
Originally Posted by kevrose View Post
Thanks so much for this, didn't reply sooner as the prospect of having a fully integrated control surface made me take my studio apart and rearrange/rewire it all!

Have started going through all my .zon files and making the changes. CSI is just great...
Glad it's working for you!

Here's a shiny new version that supports steps and acceleration properly (scroll right) 'Open Zone' is now working again ( I should point out it will only open FX zones that it created. The Zone format it creates is very strict, so be careful if you dive in and edit things by hand, chances are it won't load back in!)

I left the save/load unchanged, so make sure you have the ZoneRawFXFiles and ZoneFXFiles folders present in the CSI folder.

If you open a Configurator created Zone from another (live) folder, you can edit it and when you hit 'Create Zone', it will save the edited Zone back to the same location (over the original). I strongly suggest you make a backup copy of your FX Zones if you intend to edit them 'on the fly' like this.

Give it a try and let me know how you get on.

EDIT: Large zones can take >10seconds to load, be patient!

Last edited by MixMonkey; 12-13-2020 at 06:03 PM.
MixMonkey is offline   Reply With Quote
Old 11-29-2020, 03:29 AM   #11850
Petzi
Human being with feelings
 
Join Date: Jan 2009
Location: Belgium
Posts: 33
Default

Team,

I finally got myself a better surface (Behringer X-Touch), and will keep my QconLite only for mobile needs.

The X-Touch works really well, except I can't get a few things working in the FX zones.

First, I can assign the rotary push to an action in an FX, but it's one way, not acting as a switch :

For instance, in my SSL E Channel, I have the following :

Code:
    RotaryPush4     FXParam 26 "HF Type"
This should toggle on or off the bell shape for the high frequency, but it only sets it on, and leaves it like that

Same for the "Bypass" parameter. I can bypass on/off using "_S&M_FXBYPSEL", but
Code:
Mute1  FXParam 18 "Bypass"
also goes one way Am I missing something ?

Also, I'm trying to configure "Monark" from Native Instruments. I mapped a rotary button to one of the rotary switches that have 6 fixed values (triangle, pulse, ...). If I set the value in the GUI, I see the LED ring show the right position. But if I turn the rotary button, it only goes down (from right to left, but never from left to right). The rotary is configued as

Code:
Widget Rotary1
	Encoder b0 10 7f	
	FB_Encoder  b0 10 7f
WidgetEnd
Faders and rotary in other situations work just perfectly
__________________
Reaper/Pro Tools running on an overclocked ZX81. Presonus Scarlett. Guitars. Greasy fingers.
Petzi is offline   Reply With Quote
Old 11-29-2020, 05:57 AM   #11851
ramses
Human being with feelings
 
Join Date: Jul 2009
Posts: 872
Default

Quote:
Originally Posted by Geoff Waddington View Post
Actually it will be a bit different, touch will not be involved, it is now reserved for automation
So, I guess there's no way of using the touch part of faders to perform other duties as it is? I would like to have touching the fader selecting the track, but I guess this can't be done presently?
ramses is offline   Reply With Quote
Old 11-29-2020, 06:39 AM   #11852
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 1,856
Default

Quote:
Originally Posted by Petzi View Post
First, I can assign the rotary push to an action in an FX, but it's one way, not acting as a switch :

For instance, in my SSL E Channel, I have the following :

Code:
    RotaryPush4     FXParam 26 "HF Type"
You need to add the two values for 'on' and 'off':
Code:
RotaryPush4     FXParam 26 [ 0.0 1.0 ] "HF Type"
If you ever wanted to do a three way switch it would be like this:
Code:
 SomeButton SomeFXParameter [ 0.0 0.5 1.0 ]
Get the idea?
MixMonkey is offline   Reply With Quote
Old 11-29-2020, 07:26 AM   #11853
Petzi
Human being with feelings
 
Join Date: Jan 2009
Location: Belgium
Posts: 33
Default

Quote:
Originally Posted by MixMonkey View Post
You need to add the two values for 'on' and 'off':
Code:
RotaryPush4     FXParam 26 [ 0.0 1.0 ] "HF Type"
If you ever wanted to do a three way switch it would be like this:
Code:
 SomeButton SomeFXParameter [ 0.0 0.5 1.0 ]
Get the idea?
Thanks a lot, I think I get it now I've got it working for the On/Off switches !

But it still doesn't work on the encoder :

Code:
    Rotary1         FXParam 10 [0.0 0.2 0.4 0.6 0.8 1.0] "Osc1Wave"
    Fader1         FXParam 10 [0.0 0.2 0.4 0.6 0.8 1.0] "Osc1Wave"
The rotary and fader both control the same 6-way switch. With this config, the fader changes the switch values just fine, but not the rotary. And to ensure it wasn't a typo, I've exchanged Rotary1/Fader1 in the .ZON file, but still the same behaviour.
__________________
Reaper/Pro Tools running on an overclocked ZX81. Presonus Scarlett. Guitars. Greasy fingers.
Petzi is offline   Reply With Quote
Old 11-29-2020, 07:34 AM   #11854
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 1,856
Default

Quote:
Originally Posted by Petzi View Post
Code:
    Rotary1         FXParam 10 [0.0 0.2 0.4 0.6 0.8 1.0] "Osc1Wave"
    Fader1         FXParam 10 [0.0 0.2 0.4 0.6 0.8 1.0] "Osc1Wave"
Try this:
Code:
    Rotary1         FXParam 10 [ 0.0 0.2 0.4 0.6 0.8 1.0 ] "Osc1Wave"
    Fader1         FXParam 10 [ 0.0 0.2 0.4 0.6 0.8 1.0 ] "Osc1Wave"
..I added spaces after and before the brackets.
MixMonkey is offline   Reply With Quote
Old 11-29-2020, 08:09 AM   #11855
Petzi
Human being with feelings
 
Join Date: Jan 2009
Location: Belgium
Posts: 33
Default

Quote:
Originally Posted by MixMonkey View Post
Try this:

..I added spaces after and before the brackets.

Works (nearly) ! Faders was working fine without the space, but at least now the rotary is a bit better.

Downward is perfect, upwards requires turning the rotary a lot ! The same encoder value of +/- 0.007937 is sent from the surface, but negative values work fine (one notch, one switch position), while positive values just ... don't

Code:
    Rotary1         FXParam 10 [ 0.0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1.0 ] "Osc1Wave"
Tried various values (finer, coarser) to see if it helps, but no luck.
__________________
Reaper/Pro Tools running on an overclocked ZX81. Presonus Scarlett. Guitars. Greasy fingers.
Petzi is offline   Reply With Quote
Old 11-29-2020, 08:35 AM   #11856
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 5,818
Default

Quote:
Originally Posted by ramses View Post
So, I guess there's no way of using the touch part of faders to perform other duties as it is? I would like to have touching the fader selecting the track, but I guess this can't be done presently?
Yes, that's correct.

Do you not have a select switch for each channel ?

Just trying to understand the use case here...
Geoff Waddington is offline   Reply With Quote
Old 11-29-2020, 08:36 AM   #11857
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 5,818
Default

Quote:
Originally Posted by Petzi View Post
Works (nearly) ! Faders was working fine without the space, but at least now the rotary is a bit better.

Downward is perfect, upwards requires turning the rotary a lot ! The same encoder value of +/- 0.007937 is sent from the surface, but negative values work fine (one notch, one switch position), while positive values just ... don't

Code:
    Rotary1         FXParam 10 [ 0.0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1.0 ] "Osc1Wave"
Tried various values (finer, coarser) to see if it helps, but no luck.
Try using input monitor and turning the encoder, is it putting out "clean" values, that is, are they moving smoothly upward, or are they jumping around a lot ?
Geoff Waddington is offline   Reply With Quote
Old 11-29-2020, 09:05 AM   #11858
ramses
Human being with feelings
 
Join Date: Jul 2009
Posts: 872
Smile

Quote:
Originally Posted by Geoff Waddington View Post
Yes, that's correct.

Do you not have a select switch for each channel ?

Just trying to understand the use case here...
By now I'm fairly used to working "blind", that is, I have a small OSC script (toggleable) that projects a completely black window overlay for me across all my monitors. It's a device set up to force me to disregard visual distractions.

I have select switches. But it's an additional step, and its slower. It's more intuitive and quicker to just touch the fader and have the channel selected immediately. Also, there's less risk of forgetting what channel is selected, and having to get back to the screens for visual confirmation.

By now, it's the way I'm used to working with Fader 1, and I have grown to depend on it for mixing quickly and efficiently.
ramses is offline   Reply With Quote
Old 11-29-2020, 09:25 AM   #11859
Petzi
Human being with feelings
 
Join Date: Jan 2009
Location: Belgium
Posts: 33
Default

Quote:
Originally Posted by Geoff Waddington View Post
Try using input monitor and turning the encoder, is it putting out "clean" values, that is, are they moving smoothly upward, or are they jumping around a lot ?
It works smoothly - no erratic jumps - and gives the same value (except the sign) whether I move the rotary left of right. Looking at the slides in the UI view of the plugin, I see downwards value moving the slider for that control to the left, while upward values having a hard time moving the slider to the right.

But I start suspecting the plugin implementation (Monark from Native Instruments) because other NI plugins with a three-way switch work just fine.
__________________
Reaper/Pro Tools running on an overclocked ZX81. Presonus Scarlett. Guitars. Greasy fingers.
Petzi is offline   Reply With Quote
Old 11-29-2020, 09:34 AM   #11860
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 5,818
Default

Quote:
Originally Posted by ramses View Post
By now I'm fairly used to working "blind", that is, I have a small OSC script (toggleable) that projects a completely black window overlay for me across all my monitors. It's a device set up to force me to disregard visual distractions.

I have select switches. But it's an additional step, and its slower. It's more intuitive and quicker to just touch the fader and have the channel selected immediately. Also, there's less risk of forgetting what channel is selected, and having to get back to the screens for visual confirmation.

By now, it's the way I'm used to working with Fader 1, and I have grown to depend on it for mixing quickly and efficiently.
Fair points all.

I think I have a way we can have our cake and eat it too

As I'm sure you know touching a fader often moves it ever so slightly.

Say you were in automation Touch mode and you wanted to select a Track.

It would be very difficult to ensure that you didn't accidentally write automation as well.

However, if you are willing to accept that, you could also define the Touch separately and then map it directly to select in the Zone file:

Code:
Widget FaderTouch1
     Press 90 68 7f
WidgetEnd
and in the Zone:

Code:
    FaderTouch| TrackUniqueSelect

However, there is another, perhaps better way depending on your workflow.


You could have 2 Pages:

One where the .mst was changed and the Touch definitions were removed from the Fader definitions, and explicit FaderTouch definitions were added.

You could then do the mapping as above and all would be good.

The caveat would be that automation touch would not work -- either accidentally or on purpose on that Page

So, just another option to think about...
Geoff Waddington is offline   Reply With Quote
Old 11-29-2020, 09:36 AM   #11861
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 5,818
Default

Quote:
Originally Posted by Petzi View Post
It works smoothly - no erratic jumps - and gives the same value (except the sign) whether I move the rotary left of right. Looking at the slides in the UI view of the plugin, I see downwards value moving the slider for that control to the left, while upward values having a hard time moving the slider to the right.

But I start suspecting the plugin implementation (Monark from Native Instruments) because other NI plugins with a three-way switch work just fine.
Yeah, there are a lot of sloppy VST implementations out there, not saying Monark is one of them, but they are far too prevalent in my view
Geoff Waddington is offline   Reply With Quote
Old 11-29-2020, 09:53 AM   #11862
Funkybot
Human being with feelings
 
Join Date: Jul 2007
Posts: 2,011
Default

Quote:
Originally Posted by Geoff Waddington View Post
Yeah, there are a lot of sloppy VST implementations out there, not saying Monark is one of them, but they are far too prevalent in my view
Yeah, having spent almost all week mapping plugins to encoders, this is very obvious. Some vendors will let you assign encoders no sweat, others use stepped parameters with some very odd values and are a complete nightmare to map to encoders. You really come to appreciate the companies that handle this in a no nonsense manner. Keeping it simple is the one advantage of configuring my twister I’m Fader7Bit mode: mapping was much much easier but you lose resolution. I’d totally understand someone making the tradeoff.
Funkybot is online now   Reply With Quote
Old 11-29-2020, 10:48 AM   #11863
norbury brook
Human being with feelings
 
norbury brook's Avatar
 
Join Date: Mar 2007
Location: London UK
Posts: 1,987
Default

@Funkybot and @geoffwaddington.


My mistake, I was putting the .dll's and the CSI folder in the reaper program files folder NOT in the reaper resources path folder.

Works like a charm now.

thanks

M
__________________
https://www.marcuscliffe.com/
norbury brook is offline   Reply With Quote
Old 11-29-2020, 11:06 AM   #11864
Funkybot
Human being with feelings
 
Join Date: Jul 2007
Posts: 2,011
Default

Quote:
Originally Posted by ramses View Post
So, I guess there's no way of using the touch part of faders to perform other duties as it is? I would like to have touching the fader selecting the track, but I guess this can't be done presently?
What if you’re touching multiple tracks because you’re moving two or more channels simultaneously? Wouldn’t you run the risk of the selection jumping all over the place?
Funkybot is online now   Reply With Quote
Old 11-29-2020, 12:32 PM   #11865
ramses
Human being with feelings
 
Join Date: Jul 2009
Posts: 872
Default

Quote:
Originally Posted by Geoff Waddington View Post
Fair points all.

I think I have a way we can have our cake and eat it too

As I'm sure you know touching a fader often moves it ever so slightly.

Say you were in automation Touch mode and you wanted to select a Track.

It would be very difficult to ensure that you didn't accidentally write automation as well.

However, if you are willing to accept that, you could also define the Touch separately and then map it directly to select in the Zone file:

Code:
Widget FaderTouch1
     Press 90 68 7f
WidgetEnd
and in the Zone:

Code:
    FaderTouch| TrackUniqueSelect

However, there is another, perhaps better way depending on your workflow.


You could have 2 Pages:

One where the .mst was changed and the Touch definitions were removed from the Fader definitions, and explicit FaderTouch definitions were added.

You could then do the mapping as above and all would be good.

The caveat would be that automation touch would not work -- either accidentally or on purpose on that Page

So, just another option to think about...
Thanks for thinking about this, I think I'll try the second option for now.
ramses is offline   Reply With Quote
Old 11-29-2020, 12:34 PM   #11866
ramses
Human being with feelings
 
Join Date: Jul 2009
Posts: 872
Default

Quote:
Originally Posted by Funkybot View Post
What if you’re touching multiple tracks because you’re moving two or more channels simultaneously? Wouldn’t you run the risk of the selection jumping all over the place?
True. But as long as selection stays with the last touched track, it shouldn't be too much of an issue. I'll do the implementation and report back.
ramses is offline   Reply With Quote
Old 11-29-2020, 08:05 PM   #11867
cjewellstudios
Human being with feelings
 
Join Date: Sep 2017
Posts: 554
Default

It seems the majority of you have figured this out but:
Code:
TrackBank "+8"
Does not work. While

Code:
TrackBank "8"
does.

It's like that in the Wiki, so that should be changed.

I have this elaborate setup where I show and hide tracks all the time so I hardly ever need to bank.
cjewellstudios is offline   Reply With Quote
Old 11-29-2020, 08:49 PM   #11868
Funkybot
Human being with feelings
 
Join Date: Jul 2007
Posts: 2,011
Thumbs up

Quote:
Originally Posted by cjewellstudios View Post
It's like that in the Wiki, so that should be changed.
Done. Thanks for pointing that out!
Funkybot is online now   Reply With Quote
Old 11-30-2020, 06:06 AM   #11869
ramses
Human being with feelings
 
Join Date: Jul 2009
Posts: 872
Default

Fader Touch works brilliantly now! Just like I'm used to. Thanks.

I've decided to go with the first suggested implementation for now, since I don't use touch automation that often anyway.

This is what I use in the *.mst:

Code:
Widget Fader1 
    Fader7Bit b0 64 7f
    FB_Fader7Bit b0 64 7f
WidgetEnd  

Widget FaderTouch1
	AnyPress b0 0a 7f
WidgetEnd

...
and in the channel *.zon:

Code:
FaderTouch|  TrackUniqueSelect

Last edited by ramses; 11-30-2020 at 06:12 AM.
ramses is offline   Reply With Quote
Old 11-30-2020, 07:34 AM   #11870
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 1,856
Default

Just noticed that the Mackie C4.mst in the DL is missing its Rotary acceleration values. If it could be swapped with the attached one, that'd be great.

Last edited by MixMonkey; 12-13-2020 at 06:03 PM.
MixMonkey is offline   Reply With Quote
Old 11-30-2020, 07:55 AM   #11871
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 5,818
Default

Quote:
Originally Posted by MixMonkey View Post
Just noticed that the Mackie C4.mst in the DL is missing its Rotary acceleration values. If it could be swapped with the attached one, that'd be great.
Done.

Will be in next build post.
Geoff Waddington is offline   Reply With Quote
Old 11-30-2020, 07:55 AM   #11872
Geoff Waddington
Human being with feelings
 
Geoff Waddington's Avatar
 
Join Date: Mar 2009
Location: Dartmouth, Nova Scotia
Posts: 5,818
Default

Quote:
Originally Posted by ramses View Post
Fader Touch works brilliantly now! Just like I'm used to. Thanks.

I've decided to go with the first suggested implementation for now, since I don't use touch automation that often anyway.

This is what I use in the *.mst:

Code:
Widget Fader1 
    Fader7Bit b0 64 7f
    FB_Fader7Bit b0 64 7f
WidgetEnd  

Widget FaderTouch1
	AnyPress b0 0a 7f
WidgetEnd

...
and in the channel *.zon:

Code:
FaderTouch|  TrackUniqueSelect
Cool, glad you got it working.
Geoff Waddington is offline   Reply With Quote
Old 11-30-2020, 07:37 PM   #11873
cjewellstudios
Human being with feelings
 
Join Date: Sep 2017
Posts: 554
Default

So I've been messing around with Scroll Link. I like what it does quite a bit! Sorry about posting in both threads about it but this one is more of a philosophy thing.

Scroll link, as I understand it, takes the selected track and puts it in channel one of your surface.

However, when I ForceScrollLink when any one of tracks 2-8 are selected (I'm talking the first set of 8 tracks in a project) it doesn't put the selected track as channel 1 on my surface. Tracks 9 and above work fine, and incidentally, if you work your way back from 9 back to 1 with ForceScrollLink or ToggleScrollLink engaged, the selected track maintains its position as channel one on the surface.

I'm not sure if this is intentional and I have a feature request, or if I'm reporting a bug

While we are on the Scroll link talk: Is there a way I can set ToggleScrollLink to be toggled on to start?
cjewellstudios is offline   Reply With Quote
Old 11-30-2020, 07:49 PM   #11874
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 1,856
Default

Quote:
Originally Posted by cjewellstudios View Post
While we are on the Scroll link talk: Is there a way I can set ToggleScrollLink to be toggled on to start?
Check 'Reaper follows surfaces' in Prefs/Pages/Edit.

See if ScrollLink works properly with the box ticked in the prefs, ForceScrollLink might not work as expected, I haven't used it in a while.
MixMonkey is offline   Reply With Quote
Old 11-30-2020, 08:02 PM   #11875
cjewellstudios
Human being with feelings
 
Join Date: Sep 2017
Posts: 554
Default

Quote:
Originally Posted by MixMonkey View Post
Check 'Reaper follows surfaces' in Prefs/Pages/Edit.

See if ScrollLink works properly with the box ticked in the prefs, ForceScrollLink might not work as expected, I haven't used it in a while.
[Edit] I'm deft, sorry. Yes that makes togglescrollLink start toggled on! Thank you! [/Edit]

Thanks for your reply. I actually didn't have that checked, however I get the same behavior.

It only doesn't do what I expect it to when the first visible track of the project is channel 1 of my surface. From there, selecting any channel in that bank of 8 tracks and hitting ToggleScrollLink or ForceScrollLink, it doesn't move the selected track to channel 1.

Last edited by cjewellstudios; 11-30-2020 at 08:08 PM.
cjewellstudios is offline   Reply With Quote
Old 12-01-2020, 02:26 AM   #11876
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 1,856
Default

Quote:
Originally Posted by cjewellstudios View Post
[Edit] I'm deft, sorry. Yes that makes togglescrollLink start toggled on! Thank you! [/Edit]

Thanks for your reply. I actually didn't have that checked, however I get the same behavior.

It only doesn't do what I expect it to when the first visible track of the project is channel 1 of my surface. From there, selecting any channel in that bank of 8 tracks and hitting ToggleScrollLink or ForceScrollLink, it doesn't move the selected track to channel 1.
It won’t scroll if the track is already visible on the surface(s).
MixMonkey is offline   Reply With Quote
Old 12-01-2020, 06:22 AM   #11877
cjewellstudios
Human being with feelings
 
Join Date: Sep 2017
Posts: 554
Default

Quote:
Originally Posted by MixMonkey View Post
It won’t scroll if the track is already visible on the surface(s).
Right, ok so that is the way it's supposed to work then. I understand that not having your surface jump around is preferable but there are times when I would prefer that it does. I propose:

Firstly, I'm sorry if I'm just not thinking clearly but, do we need Forcescrolllink AND ToggleScrollLink? It seems perhaps redundant to me, especially since you can choose to have Scroll Link start on or off in your page edit window (thanks MixMonkey!) And subsequently toggle it on or off.

With that in mind, I'm thinking we should make the ForceScrollLink action behave as a one time "take the selected track and make it channel one" action.

Personal use case:

Say I have 8 guitar tracks (rock on!) And I've hidden everything else except for those 8 tracks, the guitar buss, stereo buss, and maybe some other buss as well. So I have 11 tracks visible in Reaper, and I actually want the 4th on channel 1 on my surface. I would like to be able to selected the track and Forcescrolllink and have the 4th track as channel one.

I have thought about this and I could also just TrackUniqueSelect and bank by 1 until I get there. Which is totally fine with me, but I felt like the scroll link discussion was still worth having since it does seem redundant and the new functionality would potentially save me a few button presses every now and again
cjewellstudios is offline   Reply With Quote
Old 12-01-2020, 06:31 AM   #11878
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 1,856
Default

Quote:
Originally Posted by cjewellstudios View Post
With that in mind, I'm thinking we should make the ForceScrollLink action behave as a one time "take the selected track and make it channel one" action.
I think this is a good idea, if it's not to difficult to implement. I asked Geoff to create ForceScrollLink ages ago as a way of having the surfaces scroll after some scripts I had written had run (previously I'd just been toggling off and on again to make it scroll)

If we could have:

Code:
 SomeButton ForceScrollLink SomeChannelNumber
... that would be even better
MixMonkey is offline   Reply With Quote
Old 12-01-2020, 08:05 AM   #11879
Mistik
Human being with feelings
 
Join Date: Nov 2018
Posts: 13
Default

Hey guys probably very noob question, but is it at all possible to use a MIDI device at the same time both with CSI as a control surface (some buttons and rotaries) and as a MIDI input to trigger MIDI notes on a channel (keys or pads for example).

I just bought a Presonus Atom pad controller and am looking at the best way to integrate it with reaper. Atom has drum pads, buttons and rotaries. I would love to use the pads for triggering drum samples and all the other controls as I define them in CSI.

I tried to have Atom enabled both as a MIDI input and in CSI with no effect.

Is there a way for CSI to transmit MIDI notes to the selected track?

Thanks for your help.
__________________
IconPlatformNano v1.1, update - WORKING - tested with CSI 1.0 (2020-12-04), nano firmware v1.14
Download here: http://e.pc.cd/NWhotalK
Mistik is offline   Reply With Quote
Old 12-01-2020, 08:39 AM   #11880
MixMonkey
Human being with feelings
 
MixMonkey's Avatar
 
Join Date: Sep 2017
Location: London, England.
Posts: 1,856
Default

Quote:
Originally Posted by Mistik View Post
Hey guys probably very noob question, but is it at all possible to use a MIDI device at the same time both with CSI as a control surface (some buttons and rotaries) and as a MIDI input to trigger MIDI notes on a channel (keys or pads for example).

I just bought a Presonus Atom pad controller and am looking at the best way to integrate it with reaper. Atom has drum pads, buttons and rotaries. I would love to use the pads for triggering drum samples and all the other controls as I define them in CSI.

I tried to have Atom enabled both as a MIDI input and in CSI with no effect.

Is there a way for CSI to transmit MIDI notes to the selected track?

Thanks for your help.
Sorry, but I think you're out of luck here. The only way this can made to work is with controllers that have 2 discrete, virtual connections to the host.

I have an Akai MPK249 and it appears in the computer as USB_A and USB_B. I have USB_A enabled in the Reaper MIDI settings and route the keyboard and pads to this output.

USB_B is disabled in the MIDI settings, but used in CSI. I route the faders and knobs to this output.
MixMonkey is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 10:28 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, vBulletin Solutions Inc.