By connecting your controller to a Mackie or HUI controls in Cubase Studio Setup, you’re telling Cubase that your controller sends a predefined kind of midi dialect, which uses Notes, CC’s and Pitch bend for all kinds of commands that are not actually notes and pitch bends.īy connecting your controller to the Generic Remote, you’re telling Cubase that you will custom define how to interpret each incoming midi message including the start and stop buttons. This seemed OK initially however when playing the keyboard strange things would happen like tracks being deleted!Ĭubase just sees midi messages. ![]() The keyboard can transmit Mackie, HUI or MIDI (but only one at a time) so I switched it to MIDI & tried creating a mapping using MIDI learn in Generic Remote. I can’t find any info as to how I reassign the buttons. ![]() The centre directional button seems to change the function of the other 4 - when pressed, the up/down now expands or contracts the track display & the left/right don’t do anything. The up/down directional buttons allow cycling through tracks but the left & right buttons are a bit odd as they increase or decrease project window zoom! By assigning a Mackie Control, the PLAY, STOP & RECORD work fine. My issue is the transport controls & “directional buttons” - it has a PLAY, STOP, RECORD & 5 extra buttons. Out of the box the volume slider controls ‘internal’ VST volume but assigning it as a Generic Remote allows it to control track or stereo out volume (plus other parameters) so this isn’t the problem. No specific software or instructions from M-Audio. ![]() Trying to map it to Cubase but struggling.
0 Comments
Leave a Reply. |