Arturia Logic Pro X

[Mickie Bottiglieri]

Howeverit requires (quite) some time, until things are assembled. A special role plays unexpected behavior of the Cubase software, which kicks in here and there. E.g. it does keep faders assigned, if changing projects.

I went through this intense exercise over the last couple of weeks while connecting a (hardware modified) Yamaha 01x as a Mackie Control. As a side effect, I learned Midi inside-out. Not sure, how close I am already to be an expert.

Thank you for your insight. It sure helps.

You confirm the solution I also had in my mind. (which is to create a generic controller setup for one of the 2 controllers.)

Unfortunately, I lack the time to do this now.

Nevertheless, thanks for your feedback.

It would make more sense to set up the Keylab as a Generic Remote, as the displays on the X-Touch will not work if it is set up as a Generic Remote.

This is the sort of situation where I would be tempted to write something that goes in between Cubase and the hardware using MIDI loopback ports and something like Max, Pure Data or Bome MIDI Translator Pro. I think Plogue Bidule could also be used, but I have no experience with it. This article discusses the approach and gives an example.

I think you will need a Generic Remote in Cubase for one device (likely the Keylab) no matter what - from memory, Cubase will always try to treat two Mackie Controls as making one combined control surface with 16 channels plus a master. Generic Remote is how you define user configurable controls. Tha advantage of putting Max or similar between the device and Cubase is that you can implement things that you cannot implement directly in Cubase, such as banks of controls. It also gives you the opportunity to manipulate return data from Cubase into what the controller expects.

I hope MIDI 2.0 will bring more standardisation to controllers and control surfaces but MIDI 2.0 standardisation, let alone software and hardware supporting MIDI 2.0, are still some way off. When MIDI 2.0 is here, there will still be a requirement to support legacy MIDI controllers.

From having re-read the posts here, I think there is a key problem of the two controllers to co-exist as Macki Controllers. Especially the two sets of faders may bite each other as they are sending absolute data.

Background is, tthat the Xtouch with its motor faders would respond (theoretically) to when the Arturia faders are moved. But the Arturia, which has no motor faders, does not follow the changes of its sister fader in the XTouch. So the problem occurs as soon as two corresponding faders (try to) send different values. However, this view may be incorrect given what Davidw stated. Read on.

Easier said than done for me due to a neurological condition that has made learning tragically hard for at least 10 years now. In the past I have known how to solve issues like this. Back in the 90sI had been really whizzy on all of this stuff (Cubase, MIDI, problem solving) . Back then I honestly knew it inside out for work. Alas the years and the Neuro stuff mean that it all seems like it has faded away.

3a8082e126