MOTUNATION (formerly UnicorNation) is an independent community for discussing Digital Performer and other MOTU audio software and hardware. It is not affiliated with MOTU.
Forum rules
This forum is for most discussion related to the use and optimization of Digital Performer [MacOS] and plug-ins as well as tips and techniques. It is NOT for troubleshooting technical issues, complaints, feature requests, or "Comparative DAW 101."
I'll admit up front, I'm something of a neophyte concerning MIDI since most of my recording experience has been done with audio going straight into the system .. And i recently got the MK2 to take advantage of Arturia's Inst. suite. But I can't figure out how to set it up where One Ch controls One virtual Inst. ONLY ?
They are all sounding together under a single key press even though I have each assigned to a separate MIDI ch ?
I did speak with MOTU support online and they seem to think it's set up correctly ? I'm at a bit of a loss here ?!?
Suggestions appreciated
Attachments
Screenshot 2024-08-11 at 5.11.09 PM-1.jpg (310.08 KiB) Viewed 2644 times
ng62gn wrote: ↑Mon Aug 12, 2024 2:09 am
Make sure your inst. is correctly configured in Audio MIDI Setup (DP Setup menu or Mac Utilities folder)
Running on a Studio M2Max ..
They're all seen ? If I'm not mistaken all the connection happens through USB .. unlike back in the day when you had to pull the connectors to the MTP unit ?
Attachments
Screenshot 2024-08-12 at 1.03.00 PM.png (300.32 KiB) Viewed 2570 times
I'm curious about the appearance of the "DAW" version of your keyboard. It shouldn't matter since you're in Multi and can choose the source, but perhaps there's something about multiple iterations of that device that CoreMIDI can't parse.
stubbsonic wrote: ↑Mon Aug 12, 2024 10:45 am
I'm curious about the appearance of the "DAW" version of your keyboard. It shouldn't matter since you're in Multi and can choose the source, but perhaps there's something about multiple iterations of that device that CoreMIDI can't parse.
Not quite sure what you mean ? .. The MK2 Updater image ?
Can't imagine DP/CoreMIDI would be confused as the Keylab is by no means an oddball controller ?
I'm just wondering why you are using MIDI Multi Record. I always run DP with MIDI Multi record OFF and Audio Multi Record ON.
Unless you want to record multiple performances to multiple VIs simultaneously, I'd just turn MIDI Multi Record off. That way, any and all connected MIDI Controllers will address the current record-enabled VI. You don't have to specify the MIDI Input Source. You can use the Mod Wheel on one keyboard while playing notes on another and manipulating an Expression Pedal connected to a third; all will impact the record-enabled VI.
With this approach, make sure MIDI Controllers are not spitting out notes on multiple MIDI channels; if so you will get doubled MIDI recordings. And working the Mod Wheel on two keyboards at once will give weird, jumpy results!
HC Markus M1 Mac Studio Ultra • 64GB RAM • 828es • macOS 14.73 • DP 11.34 https://rbohemia.com
I think the reason multi was suggested was to troubleshoot the original issue of VI's "all sounding together"
In the image showing the available sources, we see three versions of the KeyLab MkII: DAW, MIDI, and Updater (missing). However, it shows ALL of them under the heading "UNCONFIGURED PORTS".
So that might be a good first step, to go into Audio MIDI Setup (AMS) and double-click device KeyLab MkII. Then in the edit window that opens, switch PROPERTIES to the PORTS tab. It looks like it would (should?) have two ports, one called MIDI, and one called DAW. I'm guessing the MIDI where the KeyLab's 5-pins in/out are treated like a separate port on the same device. And that DAW is the USB feeding the DAW (in). Not sure what the output of DAW does.
In the image showing Audio MIDI Setup, we see the DAW & Updater. I'm tempted to tell you to delete updater, as that just seems like some leftover something. Worst case, if it is needed, you could re-install drivers. The New External Device shows as missing. Do you know what that is? If you don't need it, you can probably get rid of it. Just adding an unnecessary item to the list.
On some of the Arturia keyboards, DAW ports allow you to configure the transport controls as a control surface and the MIDI ports function normally as notes, CCs, etc.
DP 11.34 PT 2024.10.2 Mixbus 11 VEP 7.x with various VIs
NI Komplete Audio 6 on HP Envy 8G i7 Quad Laptop Win11
MOTU 828es ADA8200 MTP-AV on HP Z2 G4 Xeon Workstation Win11
MOTU M4 on MacBook Air M2 2023 Sequoia.4.1
HCMarkus wrote: ↑Mon Aug 12, 2024 11:53 am
I'm just wondering why you are using MIDI Multi Record. I always run DP with MIDI Multi record OFF and Audio Multi Record ON.
Unless you want to record multiple performances to multiple VIs simultaneously, I'd just turn MIDI Multi Record off. That way, any and all connected MIDI Controllers will address the current record-enabled VI. You don't have to specify the MIDI Input Source. You can use the Mod Wheel on one keyboard while playing notes on another and manipulating an Expression Pedal connected to a third; all will impact the record-enabled VI.
With this approach, make sure MIDI Controllers are not spitting out notes on multiple MIDI channels; if so you will get doubled MIDI recordings. And working the Mod Wheel on two keyboards at once will give weird, jumpy results!
It was checked. I think either MOTU or Sweetwater activated that . Can't remember why. I unchecked it and am now able to record a MIDI inst while listening to another MIDI inst. YAY !!
Oh, and are you connected by USB, or MIDI cables? I could never get my KL88mkII to work properly via MIDI. USB is the way to go.
Connected via USB ...
By the way, I went to the page you referenced for the App. Looks great but I can't find the Download link for the Desktop version on the link ?!?
