04-10-2022, 02:30 PM
(This post was last modified: 04-10-2022, 02:34 PM by kindredlost.)
I have tried for a week or two to learn how to route midi signals to their instrument destinations and to my DAW for separate midi track data. I have read the manual many times and once I finally set it up it all seemed quite simple. I will say it isn't exactly intuitive but once you get the idea of virtual ports then it really hits home.
My setup includes the NDLR, a bunch of hardware synths and Cubase on an iMac. My intent was to route the four parts from the NDLR to the instruments and to separate track in Cubase for real time recording and later playback (if needed). I like this strategy for a number of reasons - mostly though in case of a later reworking of the music idea with different voices or in case of recording errors with levels etc..
It worked great when I finally got a model of the virtual port idea in my head. Using the NDLR usb cable directly to the usb A and each "part" from the NDLR set up for usb 1 - 4 in matching with midi channels 1 - 4. So the Drone is output from the NDLR in midi channel 1 and correspondingly usb #1. The Motif-1 is midi channel 2 and usb #2, etc.. Then picking up the synth output channel for each usb port as well as PC port #9 - 12. Then setting each midi recording track in Cubase for the midi channel number and port from the MRCC was the next task. Once these and the audio channels for the synths were set up in Cubase I just hit record and played everything. Once finished I set up Cubase midi channels for return to the MRCC in the same virtual ports with each corresponding synth picked on the MRCC as well.
What kept giving me trouble was the idea of how to use the ports and midi channels as discrete routs to and from the NDLR and PC. I was picking up all midi channels on each of the four midi tracks in Cubase until I paired each port to the corresponding midi channel and it snapped into place. Sort of an epiphany once it happened. I doubt I'll forget the idea of the virtual port after that.
Anyway, regardless of preaching to the choir I am proud of myself for sticking with it long enough to make it happen. Here is a short 3 minute piece demonstrating the session.
My setup includes the NDLR, a bunch of hardware synths and Cubase on an iMac. My intent was to route the four parts from the NDLR to the instruments and to separate track in Cubase for real time recording and later playback (if needed). I like this strategy for a number of reasons - mostly though in case of a later reworking of the music idea with different voices or in case of recording errors with levels etc..
It worked great when I finally got a model of the virtual port idea in my head. Using the NDLR usb cable directly to the usb A and each "part" from the NDLR set up for usb 1 - 4 in matching with midi channels 1 - 4. So the Drone is output from the NDLR in midi channel 1 and correspondingly usb #1. The Motif-1 is midi channel 2 and usb #2, etc.. Then picking up the synth output channel for each usb port as well as PC port #9 - 12. Then setting each midi recording track in Cubase for the midi channel number and port from the MRCC was the next task. Once these and the audio channels for the synths were set up in Cubase I just hit record and played everything. Once finished I set up Cubase midi channels for return to the MRCC in the same virtual ports with each corresponding synth picked on the MRCC as well.
What kept giving me trouble was the idea of how to use the ports and midi channels as discrete routs to and from the NDLR and PC. I was picking up all midi channels on each of the four midi tracks in Cubase until I paired each port to the corresponding midi channel and it snapped into place. Sort of an epiphany once it happened. I doubt I'll forget the idea of the virtual port after that.
Anyway, regardless of preaching to the choir I am proud of myself for sticking with it long enough to make it happen. Here is a short 3 minute piece demonstrating the session.
