|
|
Post by swurveman on Mar 21, 2020 16:03:30 GMT -6
I am running Cubase 10 and am trying to play and monitor my Yamaha ES90 keyboard in Cubase 10 via my RME AES-32 MIDI connection. I have connected the MIDI out of the keyboard to the MIDI "in 1" cable of the RME connection at my RME computer interface. I have created a MIDI track in Cubase and have as my input 2-AES 32 Port 1 In Cubase. I have the monitor button enabled, but I am getting no signal or sound. So, I have no idea how/where to troubleshoot the problem. The S90ES is an old keyboard. So, my suspicion is there, but i can't find anything on the internet to troubleshoot what is wrong. If any of you MIDI experts have thoughts about possible solutions, I would appreciate your advice. Thanks in advance to anybody kind enough to respond!!
|
|
|
|
Post by Tbone81 on Mar 21, 2020 16:08:29 GMT -6
Set the midi input to Omni and see if you get midi input. What do you have the midi routed to? A VSTi? Are you trying to get sounds off the keyboard directly (not sure if you keyboard is just a controller). If so, you need the audio outputs I’d the keyboard routed back into the DAW, and depending on it you have it set to “local off” you’ll also need midi out cable from the interface going back to the keyboard. With “local on” you can skip that step and monitor straight off the keyboard, audio out into DAW.
Make sense ?
|
|
|
|
Post by swurveman on Mar 21, 2020 18:24:18 GMT -6
Set the midi input to Omni and see if you get midi input. What do you have the midi routed to? A VSTi? Are you trying to get sounds off the keyboard directly (not sure if you keyboard is just a controller). If so, you need the audio outputs I’d the keyboard routed back into the DAW, and depending on it you have it set to “local off” you’ll also need midi out cable from the interface going back to the keyboard. With “local on” you can skip that step and monitor straight off the keyboard, audio out into DAW. Make sense ? Thanks for your reply Tbone81! I am trying to get the sound off the keyboard directly, and also use it to control VST's. I have set the MIDI input to “ANY”, which is the same as “OMNI” in Sonar. I'm not sure what you mean by, "If so, you need the audio outputs I’d the keyboard routed back into the DAW." Could you please elaborate? Are you saying that simultaneously with the MIDI input to the MIDI channel, I should be using the stereo audio outputs from the keyboard to record analog in to Cubase? Or are you referring something else? Sorry, I'm a newbie with this and have quit trying to use the MIDI out of the keyboard many times. This time I want to make it work if possible. Thanks again! |
|
|
|
Post by Tbone81 on Mar 21, 2020 19:25:16 GMT -6
Yes that’s exactly what I mean. Midi is only computer code, it carries no audio. So both Midi input and output need to be connected to the midi input/output of your interface. Then, you also need to connect the analog audio outs from the keyboard to your interface.
So it works like this: 1) you press a key and midi is transmitted and recorded into the daw 2) midi recorded to the daw is sent to your keyboard and tells it what to play 3) the associated sounds on your keyboard play and send analog out into your daw
The midi input on your daw channel can be set to “any”, but I forget if Cubase has the same “any” settting in the midis output of a channel. If not, then you need to set it to whatever midi channel your keyboard patch is setup to receive. Midi protocol has 16 channels, and by convention drum sounds are usually defaulted as midi channel 10. You may need to dive into the menu of your keyboard to make sure it’s setup right. Pay attention to the “local” setting. “On” means that when you press a key on the keyboard and sound plays AND midi info is transmitted. “Local off” means that when you strike a key it only sends midi info, but doesn’t trigger its onboard patch.
Hope that helps
|
|
|
|
Post by swurveman on Mar 22, 2020 10:30:41 GMT -6
Yes that’s exactly what I mean. Midi is only computer code, it carries no audio. So both Midi input and output need to be connected to the midi input/output of your interface. Then, you also need to connect the analog audio outs from the keyboard to your interface. So it works like this: 1) you press a key and midi is transmitted and recorded into the daw 2) midi recorded to the daw is sent to your keyboard and tells it what to play 3) the associated sounds on your keyboard play and send analog out into your daw The midi input on your daw channel can be set to “any”, but I forget if Cubase has the same “any” settting in the midis output of a channel. If not, then you need to set it to whatever midi channel your keyboard patch is setup to receive. Midi protocol has 16 channels, and by convention drum sounds are usually defaulted as midi channel 10. You may need to dive into the menu of your keyboard to make sure it’s setup right. Pay attention to the “local” setting. “On” means that when you press a key on the keyboard and sound plays AND midi info is transmitted. “Local off” means that when you strike a key it only sends midi info, but doesn’t trigger its onboard patch. Hope that helps Thanks for clarifying Tbone. Really appreciate it! Question: Since I am going to be connecting my keyboard outputs via my direct boxes and preamps in to my Aurora 16 A/D converter audio, why even use MIDI via my RME computer interface? Am i misunderstanding something? If I didn't like something I played using my keyboard sounds, I could just overdub it via my audio inputs. I do see the value of MIDI for triggering my vst's though. |
|
|
|
Post by damoongo on Mar 22, 2020 11:58:00 GMT -6
Some “advantages” (not always tho!) of taking the midi as well as audio are being able to edit your performance in ways you can’t with audio. (Fixing one note in a chord, quantizing, adding envelopes etc.). Then you can go MIDI out back to midi in of your keyboard and have the computer play your keyboard for you while you twiddle the knobs and filters in real time while recording the audio.
The possibilities are almost limitless, which is usually a problem in my experience.
|
|
