🔥 Lifetime deal! Get Control Surface Studio for Just £67 👉 Click Here To Get It
Time left... mailtimers.com
⚠️ Lifetime licenses are ending soon, get yours before they're gone ⚠️
Your shopping cart is empty.

Remote script 2 controllers of the same

Submitted by piloadami on Mon, 10/24/2022 - 12:36
piloadami
Control Surface Studio User

Hi everybody, been working on this for a while with no avail so would appreciate any help!

Setup:

2 controllers of the same brand: Novation Launcontrol XL
VST: PS-20 by cherry audio

Launch-control has 24 knobs and 8 faders. With both units I would like to have in total 48 knobs/16 faders doing different things in the same plugin/device.

Is this possible and if so how?

My initial thought was to change controller 2 MIDI CC info output for the knobs/faders which I have done in Launchcontrol XL components midi mapping software. In order for me to run a different MIDI cc info I have to run the controller in user mode (not factory, both buttons accessible on top right of the controller).

I can then confirm that different midi info is sent out by controller 2 as seeing on Control Surface studio MIDI monitor pop up box.

So on Control Surface studio I create a Scrip named: Launch Control XL
mode/track selector/device selector
Parameter Bank 1 and 2
Parameter Bank 1 has 24 knobs
Parameter Bank 2 has 24 knobs

The idea is that parameter bank 1 controls knobs 1 till 24 with it’s own midi CC
Then parameter bank 2 controls knobs 1 till 24 again with it's own midi CC

On Ableton midi preferences I have:
Control surface
1 - css launch control xl
2 - css launch control xl
(Same script 2 separate controllers?)

Input
1 - launch control xl
2 - launch control xl #2

Output
1- launch control xl
2-launch control xl #2

I can control the vst with controller 1, no problem.

However when I try and control the vst with controller 2 Ableton sees an incoming midi yellow light signal but not the blue light. I’m not entirely sure on what the lights mean however I’m assuming that Ableton recognises the hardware as a controller connected to it but not midi CC info is being passed?!

2 things I'm finding confusing:

1. Upon investigating the MIDI CC relationship between controller 1 (on launch control xl midi software) and Control Surface studio here’s what I get:

Launch control xl components default:

MIDI CC 13
MIDI channel 1

Control Surface sees on:

MIDI Value 13
MIDI channel 9

How is it possible that on novation midi CC info the midi channel is 1 however Control Surface studio recognises the knobs/faders on MIDI channel 9? I can still use and control the parameters in Ableton no probs but I wonder if that is causing the confusion in between controller number 2?

2. Again for controller 1 the VST (PS-20 cherry audio) receives midi CC out from controls surface (13) into 21. Is this common practice for different platforms send/receive different midi CC messages and still work?

Topic Category: 

4 Responses

Comments

piloadami
Control Surface Studio User
#1

Edit/Update:

If I change controller 2 MIDI channel to 9 (instead of default 1) and midi CC to 3 (unused midi info by controller 1) control surface studio sees it no probs.

On Ableton I can make it communicate with the VST by going inside the VST and manually midi mapping each new knob to it's relevant midi CC (CV control 1 is now on knob 1 of controller 2 pulling midi CC info 3/channel 9). The slightly annoying thing is that now when I expand the VST view to be able to see sliders moving (right arrow top plugin) I can't see the parameter moving even after adding it to the list).

piloadami
Control Surface Studio User
#2

Anybody?!

JohnC
Forum Admin
#3

It sounds like there is a bug somewhere along the line, but not necessarily with CSS.
Maybe you could try running the 2 controllers through a usb hub of some kind so that Ableton classes them as 1 controller, then attach that 1 controller to the css script.

clatyonc
Control Surface Studio User
#4

i actually just posted up a question on this as i am also using two launch control XLs. ive only just downloaded remotify today so still trying to conceptualise how this would work. Im thinking that each LCXL should have its own midi channel and its own script. Im going to do some testing so will let you know how i go. Im also running two launch controls as well so another level of complication!

would be good to hear if you sorted anything out since you last posted an update.