How do I set up midi so i can record in Cubase
hi
simplest routing should be something like this:
Hardware:
Keyboard MIDI OUT to Creamware IN (cable)
Scope routing:
Creamware MIDI A source to sequencer MIDI dest (via a synth if wanted)
Cubase:
In > Creamware midi IN/OUT
When a track is recorded, i do remove this IN routing on the cubase track to avoid midi "feedback"
simplest routing should be something like this:
Hardware:
Keyboard MIDI OUT to Creamware IN (cable)
Scope routing:
Creamware MIDI A source to sequencer MIDI dest (via a synth if wanted)
Cubase:
In > Creamware midi IN/OUT
When a track is recorded, i do remove this IN routing on the cubase track to avoid midi "feedback"
try this, bigger guys in the forum might agree.
creamware midi source>sequencer midi dest
from the midi channel in cubase, as arela said, use only creamware midi in and not out at the same time when recording.
if it is a creamware synth it is better to connect the synth at creamware midi source as well.(creawares midi source can give to many devices) so you listen it connected to scopes mixer. this makes scope independent of what you are doing in cubase. you play the synth and with rec botton in midi channel you record.
now when you want to listen the midi playback connected to scopes synth, from scopes routing window disconnect the synth from scopes midi source and connect it to sequencer midi source. in that case the midi channel in cubase must be set to "nothing in" and "creamware midi out".
it is much simpler when recording vsts, you set midi channel in cubase at "creamware in" and "out" the vst you want to play or record.
try this as well. disable direct monitoring in cubase. in that case you can have an audio channel in cubase receiving the sound of a scopes synth(set "audio in" at the same channel the synth is connected to scopes mixer).
ex: synth connected to channel 2 in scopes mixer. then put an audio channel in cubase set to audio 2 in. then send it out to channel 3(or whatever) which means you get it at scopes mixer to channel 3. in that case and with direct monitoring disabled you can pass the audio singal of a scopes synth through a vst effect realtime loaded in inserts of audio channel.
if you want to listen only to singal passed through cubase, then untick the green(mix) button of channel 2 in scopes mixer.
make sure you have set scope to the best ully latency you can achieve.
absolutelly necessary is to set vst connections busses of asio in cubase.
i do not know your system but i will tell you the way i work as an example even if it seems exagerated(i have 20dsps)
i use stm 4896 mixer.
asio2 32bit flt, 64 asio2 source in mixer and 64 asio2 out of mixer.
my busses in vst connections settings in nuendo(same with cubase) are set to 32 stereo asio in and 32 stereo asio out.(saved as a preset for quick use)
you can offcourse use as many asios as you like(max 32stereo), and you can also use a smaller scopes mixer i would prefer stm2448.
depends on needs and power you have.
it is nice and convenient to make a good match to scopes mixer channels and cubase channels.
i hope this gives an idea.
creamware midi source>sequencer midi dest
from the midi channel in cubase, as arela said, use only creamware midi in and not out at the same time when recording.
if it is a creamware synth it is better to connect the synth at creamware midi source as well.(creawares midi source can give to many devices) so you listen it connected to scopes mixer. this makes scope independent of what you are doing in cubase. you play the synth and with rec botton in midi channel you record.
now when you want to listen the midi playback connected to scopes synth, from scopes routing window disconnect the synth from scopes midi source and connect it to sequencer midi source. in that case the midi channel in cubase must be set to "nothing in" and "creamware midi out".
it is much simpler when recording vsts, you set midi channel in cubase at "creamware in" and "out" the vst you want to play or record.
try this as well. disable direct monitoring in cubase. in that case you can have an audio channel in cubase receiving the sound of a scopes synth(set "audio in" at the same channel the synth is connected to scopes mixer).
ex: synth connected to channel 2 in scopes mixer. then put an audio channel in cubase set to audio 2 in. then send it out to channel 3(or whatever) which means you get it at scopes mixer to channel 3. in that case and with direct monitoring disabled you can pass the audio singal of a scopes synth through a vst effect realtime loaded in inserts of audio channel.
if you want to listen only to singal passed through cubase, then untick the green(mix) button of channel 2 in scopes mixer.
make sure you have set scope to the best ully latency you can achieve.
absolutelly necessary is to set vst connections busses of asio in cubase.
i do not know your system but i will tell you the way i work as an example even if it seems exagerated(i have 20dsps)
i use stm 4896 mixer.
asio2 32bit flt, 64 asio2 source in mixer and 64 asio2 out of mixer.
my busses in vst connections settings in nuendo(same with cubase) are set to 32 stereo asio in and 32 stereo asio out.(saved as a preset for quick use)
you can offcourse use as many asios as you like(max 32stereo), and you can also use a smaller scopes mixer i would prefer stm2448.
depends on needs and power you have.
it is nice and convenient to make a good match to scopes mixer channels and cubase channels.
i hope this gives an idea.
-
hubird
maybe the obvious now:
to avoid midi loops, you can choose unable Midi-Thru per midi channel, see Midi settings menu.
The Virus hardware synth has a menu to choose between Midi internal, internal+Midi, or Midi, this makes another way of working possible.
In general, I always use selecting the right Midi track in Cubase to send the Midi info to the right destination (be it inside Cubase, be it Creamware internal).
to avoid midi loops, you can choose unable Midi-Thru per midi channel, see Midi settings menu.
The Virus hardware synth has a menu to choose between Midi internal, internal+Midi, or Midi, this makes another way of working possible.
In general, I always use selecting the right Midi track in Cubase to send the Midi info to the right destination (be it inside Cubase, be it Creamware internal).