So, I have myself 3rd party driver for mac osx from Synclavier and this Alphatrack manager app allows me to choose:
- AlphaTrack Native
- ProTools (HUI)
- Live (MCU)
- Final Cut Pro (MCU)
- Soundtrack Pro (MCU)
My first thought was,
AS LONG AS I can make Cubase 12 Pro and Alphatrack communicate through Midi ports,
it should work, so I did.
Midi Remote editor read Alphatrack (though its NATIVE driver does not get recognised on mac cubase since original developers have never developed it sadly…)
But when I attempted to assign each keys and buttons and one motorizing fader…
Cubase simply does not recognize it…
Do you think Cubase is not yet ready to fully communicate…?
especially old USB midi controller such as my Alphatrack…?
I am on mac osx mojave 10.14.6.
I have successfully mapped Komplete Kontrol S25, I know when I move each button/key/knobs cubase instantly ‘recognises’ it and then assign every single ones.
But with Alphatrack it just does not work and only cubase recognises is one moving fader.
So, one button for ‘touch’ part, another button for fader value and another one(?) surprisingly cubase mistakes as if it is another on/off button.
PERHAPS… alphatrack’s midi communication is a little complicated…?
- Cubase MIDI remote not yet fully support HUI protocol.
- My Alphatrack HUI driver is not stable.
- This 3rd party driver does not have Cubase implemented driver protocol… so maybe that could be the reason?
Very strange. Only fader is recognized and all other buttons/transport buttons/ knobs do not get ‘added’ onto the custom midi remote editor.