Mackie Control emulation for Bome Midi Translator Pro

  • Q&A Forum
  • Mackie Control emulation for Bome Midi Translator Pro
0
0

I’ve been using Midi Translator Pro for years and, although I can get my X-touch compact to send pitchbend for fader and note # for touch, I can’t get the touch to work properly in Cubase. When I use a mouse and touch a fader, automation is only written while I touch but when I use the X-Touch automation (in midi mode), writing continues after I release touch. If I look at the midi information, pitchhbend is transmitted and note on is transmitted until I lift my finger. It’s weird because if I run my X-Touch in Mackie Control Mode in my X-Touch, automation works as it should. To be clear, I have the correct pitchbend and note settings (that correspond to mackie control).
Any ideas would me much appreciated!

Marked as spam
Posted by (Q&A Forum: 1, Answers: 3)
April 8, 2019 12:08 am
65 views

I assume you are still running Cubase in Mackie mode but you are using Bome MIDI Translator for translating CC messages to pitch bend message for the faders, right? Are you also translating the touch CC’s to note on and note off to let Cubase know you are touching and releasing the faders? It is difficult to see what you are doing without a posted project file and perhaps a log to show the MIDI going in and out.

The only other different could be in how your controller response to fader movement messages you make with your mouse and whether it is honoring the mouse taking over control when it wants to. To me it sounds like since the writing continues after you release touch, you might not be translating your release message back to Cubase correctly.

In summary, please post your project file and a create a log (choosing MIDI IN MIDI OUT Incoming and Outgoing). This way we can see what is happening.

Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz

( at April 8, 2019 1:28 am)
0
Private answer

Progress, Yes!

I turns out if you add a second note off command (actually “note on” with a velocity of 0) the fader releases when you lift your finger (as in mc mode)!

 

Here’s my (very cool) setup.

I use a x-Touch Compact because it’s programmable.

I use translators in BMT  (Bome Midi Translator) to change cc messages (both fader and touch) to pitchbend  (channel 1) and note # (G#7). I’m actually using a Frontier Designs “Alphatrack” in Cubase because it assigns the fader (9th fader on X-Touch in my case) to the selected channel, much more intuitive than MC (mackie control) where you have to bank to find the track and I usually work on 1 channel at a time anyway. The other faders are assigned to FX sends 1-8 with on/off buttons below and Cubase Quick controls in bank B.

Then I found out a very cool feature in the X-Touch Compact that lets you change from Standard Midi mode to MC mode via cc# 127 on the global channel. So I programmed a button on the X-Touch (in my case the far right  top of three) to change back and forth from midi to MC modes, Very cool!

In BMT I created a midi router from the X-Touch midi in/out to 2 virtual midi ports (I use LoopBe30 for creating 24 virtual midi ports) so that I can setup a MC in Cubase  (as well as a generic remote).

This means I can use both MC and standard midi (with 2 banks, a and b) on the X-touch in Cubase!

This makes this controller extremely versatile.

Marked as spam
Posted by (Q&A Forum: 1, Answers: 3)
April 11, 2019 9:34 pm
Yes, cool. I found about the CC 127 on my X-touch MIDI. You can do the same with that so I have set it up so I can use Layer A, Layer B and Mackie Mode, on the fly. Glad you got it working! Steve PS. Hmm if it is working. can you mark this thread as resolved.
( at April 11, 2019 9:47 pm)
0
Private answer

Hi,

The attached is an example of Moving Fader 1 Layer A on your X-Touch Compact and emulating Mackie fader 1.

It has 3 translators

Touch Fader 1 – This sends the Mackie Touch Message when you touch the fader. It also sets the variable ga as a flag to the software to know it has been touched. This flag is used later to suppress multiple touch messages until the fader is released and to suppress fader movement messages. It sends a note-on (touch message) to the application to let it know the fader is being manipulated. Some applications require this before they will move the faders in Mackie Mode

Release Fader 1 – Sets the value ga back to 0 and sends a note-off message to the application to notify the fader has been release.

Move Fader 1 – The converts the fader movement from CC to pitch bend which is what Mackie protocol recognizes as a fader movement.

I also set up a feedback preset to send controls back to the device. Without this, motorized faders on some devices will jump back to zero when you release the fader.

Finally I set up a path for translating from Mackie to CC so that if you move the fader on your application, the Motorized fader on your X-touch Compact should also move.

 

Let me know how it works as I didn’t fully test it.

Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz

 

 

Marked as spam
Posted by (Q&A Forum: 38, Answers: 3196)
April 8, 2019 3:53 pm

Thanks for this Steve.
Unfortunately, it didn’t help.
I tried without Midi Translator as well…
I set up the X-Control with the EXACT same midi message as it sends in Mackie Control mode, .(PitchBend at Channel 9 for the Master Fader value and E7 for the touch of the 9th fader) and then I setup a Mackie Control remote (in Cubase) for X-Touch. When the X-Touch is in MC mode (with a mackie control in Cubase), I press a fader and automation is written until I release (as it should be). When the X-Touch is in Midi mode ( also with a mackie control in Cubase), I press a fader and automation is written until I press STOP.
This is baffling, I’ve even recorded the midi from X-Control in MC mode and X-control in Midi mode and the midi information is identical, (PitchBend at Channel 9 for the Master Fader value and E7 for the touch of the 9th fader).
Putting the X-Contol into MC mode must do something else, I just can’t figure out what.

( at April 8, 2019 9:09 pm)
Hi, I only programmed fader 1. Each fader will have its own touch and release message. Could you try with fader 1 only? Also, perhaps you can send me your project file and show me the log of messages. Steve Caldwell Bome Q and A Moderator and Independent Bome Consultant/Specialist bome@sniz.biz
( at April 8, 2019 10:27 pm)

Steve:
I only used 1 fader, I just changed the values to reflect the master fader. I also tried with fader 1 as in your original template. I’ll send a log in a bit.

( at April 9, 2019 7:18 pm)

OK, it would help also to see your project file. If you don’t feel like sharing it publicly, you can always mail it to me and if there is an issue we I can comment and advise here.

Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz

( at April 9, 2019 7:24 pm)

Any progress, Peter?

( at April 11, 2019 1:54 pm)