Transport and fader control in cubasis

Hi Nic,
Thanks for redirecting me here. I have an LX49 but it's the same manual as the 61 so everything is pretty much the same.
Everything's working as to the last post.
I'm happy if you want to do the work but I'm also happy that if I can get my head around the language I could do some of it myself.
For example I used BX as Cc's but found that the limit was 79. I'm guessing you need something else to go above this. If you could point me to a guide on sysex that would be useful that would be great as a starter.
Thanks,
Fitz

Hi fitz,

All the 2 character values in the Stream Byter are hexadecimal bytes so range from 00 (decimal 0) to 7F (decimal 127), so that should explain why 79 is OK but 80 is not.

You've got the hang of it, but I think you need to change the second rule also. You just need to change the bolded/red values in each rule to match the relevant slider in Auria and the CC number to match the keyboard:

BX 0C = 90 00 7F +C
BX 0C = B0 0F 00 +D50 +C
BX 0C = B0 2F 40 +D50 +C
BX 0C = B0 00 +D50 +C
BX 0C = B0 20 00 +D50 +C

The controller number (0C above) will go: 0C, 0D, 0E, 0F, 10, 11, 12, 13 for each set of rules the fader number (red 0 above) will go from 0 to 7

Regards, Nic.

Typing those rules in is a pain the butt. Here are the 8 fader rules (generated from a script):

# fader 0
BX 0C = 90 00 7F +C
BX 0C = B0 0F 00 +D50 +C
BX 0C = B0 2F 40 +D50 +C
BX 0C = B0 00 +D50 +C
BX 0C = B0 20 00 +D50 +C

# fader 1
BX 0D = 90 00 7F +C
BX 0D = B0 0F 01 +D50 +C
BX 0D = B0 2F 40 +D50 +C
BX 0D = B0 01 +D50 +C
BX 0D = B0 21 00 +D50 +C

# fader 2
BX 0E = 90 00 7F +C
BX 0E = B0 0F 02 +D50 +C
BX 0E = B0 2F 40 +D50 +C
BX 0E = B0 02 +D50 +C
BX 0E = B0 22 00 +D50 +C

# fader 3
BX 0F = 90 00 7F +C
BX 0F = B0 0F 03 +D50 +C
BX 0F = B0 2F 40 +D50 +C
BX 0F = B0 03 +D50 +C
BX 0F = B0 23 00 +D50 +C

# fader 4
BX 10 = 90 00 7F +C
BX 10 = B0 0F 04 +D50 +C
BX 10 = B0 2F 40 +D50 +C
BX 10 = B0 04 +D50 +C
BX 10 = B0 24 00 +D50 +C

# fader 5
BX 11 = 90 00 7F +C
BX 11 = B0 0F 05 +D50 +C
BX 11 = B0 2F 40 +D50 +C
BX 11 = B0 05 +D50 +C
BX 11 = B0 25 00 +D50 +C

# fader 6
BX 12 = 90 00 7F +C
BX 12 = B0 0F 06 +D50 +C
BX 12 = B0 2F 40 +D50 +C
BX 12 = B0 06 +D50 +C
BX 12 = B0 26 00 +D50 +C

# fader 7
BX 13 = 90 00 7F +C
BX 13 = B0 0F 07 +D50 +C
BX 13 = B0 2F 40 +D50 +C
BX 13 = B0 07 +D50 +C
BX 13 = B0 27 00 +D50 +C

Regards, Nic.

Actually you can control the master fader, by adding extra numbers like this (with 1 track) -

BX 14 = 90 00 7F +C
BX 14 = B0 0F 00 +D50 +C
BX 14 = B0 2F 40 +D50 +C
BX 14 = B0 09 +D50 +C
BX 14 = B0 29 00 +D50 +C

Don't know if this will always work though.

Thanks for typing them out by the way although I've never changed that second value and it seems to work.

Hi fitz,

Yes, the master fader location is dependent upon the number of tracks in the project. Unless you know in advance how many this is (and it is less than 8!) it is not really practical to control master fader in a general sense. That's why I say it is too tricky; Stream Byter not smart enough. Now your questions:



Here is the best guide to understanding MIDI I know of: somascape

The message above:

B - controller message
X - match any channel
6A - yes, controller number in hex
FB = MIDI continue message
+C = clone the message, do not rewrite it.

'Record' is not part of the MIDI spec. It will be a HUI message which is much more complicated.

I will move on to reverse engineering Record and pan at some stage for you!

Regards, Nic.

Hi fitz,

If your research is correct (I dunno - haven't checked myself) then this might just do record:

# might map lx rec to hui record
BX 6B 7F = 90 00 7F +C
BX 6B 7F = B0 0F 0E +D50 +C
BX 6B 7F = B0 2F 45 +D50 +C

(that ports & zones stuff is the HUI protocol)

Regards, Nic.

That doesn't work I'm afraid. I noted that ithe pdf said it should send something different that it receives. I tried this and it didn't work neither.

# might map lx rec to hui record
BX 6B 7F = 90 00 7F +C
BX 6B 7F = B0 0C 0E +D50 +C
BX 6B 7F = B0 2C 45 +D50 +C