Changed Interface (and thus drivers); MIDI Instruments Now Not Working

**Cerebrate42** · 06-03-2012, 02:31 PM

I normally use a Tascam US-1641 for tracking, but I was using an M-Audio Fast Track Pro temporarily, while I had my Tascam at a friend's studio. When I tried to open a previous project that had MIDI instruments in it, even after changing the audio driver, doing the proper device setup, and choosing the correct VST connections, the MIDI instruments wouldn't sound. I messed around for like 15 minutes. Nothing.
The weird thing is, the output on the channel for each track registers; the digital LED lights are lighting up on the digital VU meter; it's indeed "playing back," if you will. This just doesn't come through the "Audio Activity" VU meters, and, hence, I hear nothing. I'm almost positive, however, that the VST connections and such are set up correctly, because the tracks I actually recorded (i.e., guitars, bass, and vocals) do indeed sound.

So, I figured it was just the M-Audio. Now that I have my Tascam back, I have everything set-up per usual, and I open up the same project... and, again, no luck. I can't hear the MIDI instruments.

Why is this? I'm only using Kontakt 4 and Synlenth for this project. In Kontakt 4, the output and midi channel are set up correctly... I just CAN'T figure it out. It's so frustrating.

(Specs:
Win 7 64 bit
Cubase 5)

Thanks!

**Cerebrate42** · 06-03-2012, 02:37 PM

I forgot to mention that, if I create a new instrument track, and copy and paste the MIDI information from the original into the new track, the new one does indeed work.
Why is this?!

Thanks again

**Cerebrate42** · 06-03-2012, 02:57 PM

I was messing around again, and I noticed the metronome does not sound at all either. (And I use it on Audio Click, not on MIDI click.)

**Cerebrate42** · 06-03-2012, 03:45 PM

All right, this is frustrating the H**L out of me. I've been playing around with it more, and come to the conclusion that is definitely has something to do with the Device Setup or VST Connections or something. I restarted Cubase, and tried again, and, upon reopening the project, got a warning saying that the previous outputs were no longer connected. So, I went back into Device Setup, chose the correct device (i.e., the Tascam) in the ASIO4ALL driver, and turned off "High Definition Audio Device" in the WDM Device List; changed the outputs to the Tascam stereo bus in VST Connections; and, TRACK BY TRACK, changed the output routing of each actually recorded (again, guitars, bass, and vox) to that stereo output.

However, now the MIDI instrument tracks I made anew, that were sounding, are SILENT AGAIN! Ahhhh...

What's the problem here?

I restarted Cubase once more, and the problem didn't reoccur (i.e., the guitars, etc., still sound; the MIDI instruments are still silent), so I figured it was something weird I had done with the output in Device Setup last time, before I closed it.

Thanks again!

**the evil** · 06-03-2012, 04:26 PM

what version of cubase? what is in your device setup for your midi instruments? what is the I/O for the midi?

**brandondrury** · 06-03-2012, 04:37 PM

. I restarted Cubase, and tried again, and, upon reopening the project, got a warning saying that the previous outputs were no longer connected. So, I went back into Device Setup, chose the correct device (i.e., the Tascam) in the ASIO4ALL driver, and turned off "High Definition Audio Device" in the WDM Device List; changed the outputs to the Tascam stereo bus in VST Connections; and, TRACK BY TRACK, changed the output routing of each

It sounds like your stereo bus fried. I know I've done this where I simply pressed F4 and changed the output of the 2bus to whatever the new interface is. Sometimes it does delete the old one and leaves all tracks and buses unrouted.

However, now the MIDI instrument tracks I made anew, that were sounding, are SILENT AGAIN! Ahhhh...

What's the problem here?

Sometimes when doing a lot of frustrating rerouting it's easy to screw through basic troubleshooting.

First, I'd look at the first MIDI track. I'd make sure it's output is routed correctly with the correct channel # (at least for Kontakt). Then I'd look for visual feedback that Kontakt is getting the MIDI data, the instruments are there as they should and the audio meters in Kontakt look like they are working. From there Kontakt will flow to channels in Cubase. (It is possible that these can be set wrong as well.) You should see the meters in Cubase doing their thing. From there, they need to be routed to your new 2bus as well.

Let us know at which stage they are breaking.

Brandon

**Cerebrate42** · 06-03-2012, 04:43 PM

Originally Posted by the evil

what version of cubase? what is in your device setup for your midi instruments? what is the I/O for the midi?

Cubase 5

For device setup and VST connections, I've attached pics.

As for I/O, the MIDI files are already recorded. (And these are all technically instrument tracks, and not MIDI tracks.) So the I for each is just All MIDI Inputs; the O is Kontakt 4 (and Sylenth).

**Cerebrate42** · 06-03-2012, 04:50 PM

Originally Posted by brandondrury

First, I'd look at the first MIDI track. I'd make sure it's output is routed correctly with the correct channel # (at least for Kontakt). Then I'd look for visual feedback that Kontakt is getting the MIDI data, the instruments are there as they should and the audio meters in Kontakt look like they are working. From there Kontakt will flow to channels in Cubase. (It is possible that these can be set wrong as well.) You should see the meters in Cubase doing their thing. From there, they need to be routed to your new 2bus as well.

Let us know at which stage they are breaking.

Brandon

Thanks for the response Brandon.

So I've attached a pic of Kontakt 4. As you can see, for MIDI ch., I always just go for omni. In this project, I'm using 13 MIDI tracks, so channels could get messy and annoying really fast. For Output, there's only one option anyway: st. 1.

And, as you said, the meter in Kontakt is definitely registering.

I don't know what other parameters I can change...

Kontakt.jpg

**Cerebrate42** · 06-03-2012, 04:52 PM

Also, I keep conflating the language; so, to be clear: these are instrument tracks not midi tracks. They're using MIDI data, of course, though.

**tacman7** · 06-04-2012, 08:15 AM

Just wondering, why you don't use the real drivers?

Are you doing tests using audio files to make sure you have audio?

Sometimes there can be a volume control that gets turned off on a midi track, I guess instrument tracks can do that too.

I'm new to instrument tracks and am having trouble understanding what it is they do and how they work.

**Cerebrate42** · 06-04-2012, 08:45 AM

Originally Posted by tacman7

Just wondering, why you don't use the real drivers?

That's a good question. I'm pretty sure a read somewhere a few years back that ASIO4ALL was just a better choice than the Tascam US-1641. If this isn't true, I certainly could just use the Tascam drivers. Although I haven't had any problems with ASIO4ALL really. I've only just had this problem from changing between interfaces.

Originally Posted by tacman7

Are you doing tests using audio files to make sure you have audio?

Yes, and I do.

Thanks!