SOLVED: No audio from VSTIs with MOTU UltraLite mk3

[didierb]

Hello, folks,

I recently upgraded to a MOTU UltraLite mk3 audio interface and I can't get any sound from VSTIs in Cubase 4.5.2. I suspect it's an output routing issue, but I can't figure out where the link is broken. Here's the setup:

1/ Korg Triton Extreme connected to the UltraLite via MIDI and analog inputs 7-8.
2/ Powered monitors connected to the UltraLite via Main Outs 1-2.

In Windows XP Home (SP3), I can play iTunes, play my keyboard, etc., and hear everything just fine. Strangely, though, the Sounds and Audio Devices control panel lists NO AUDIO DEVICE under the volume tab. The audio tab, on the other hand, lists MOTU Main Out 1-2 as the default device for sound playback and UltraLite mk3 as the default MIDI playback device.

OK, on to Cubase 4.5.2.
Here, MIDI tracks triggering the Triton play just fine but instrument tracks linked to software synths make no sound -- that's none of Cubase's built-in VSTIs and Spectrasonics' Trilogy, Stylus RMX and Omnisphere. Meters for those instrument tracks light up, indicating that sound is being produced but I can't hear it.

Cubase's VST Connections window is set up as follows:
INPUTS
Stereo In
Left: Analog 7
Right: Analog 8

OUTPUTS
Stero Out
Left: Main Out 1-2 - 1
Right: Main Out 1-2 - 2

STUDIO
Monitor 1
Left: Main Out 1-2 - 1
Right: Main Out 1-2 -2

If anybody has any suggestions on how to solve this mystery, I'd greatly appreciate it. Thanks in advance.

Cheers,

-- D
_________________
Intel E8400 @ 3GHz; 4 GB PC 8500 Mushkin RAM; Gigabyte GA-X48-DS4 mobo; Maxtor 640GB HD x2 (RAID 0); XP Home SP3; Cubase 4.5.2; MOTU UltraLite mk3 audio interface; Korg Triton Extreme; Spectrasonic Stylus RMX; Trilogy; Omnisphere

[TheRealRoach]

In Cubase 4, you should leave the "outputs" in VST Connections disconnected if you are using the control room. You should read the chapter on the Control Room.

Just make sure your VSTi's outputs are routed to the Stereo Out.

Also make sure your MOTU device is selected in "Device Setup...".

Can you get any sound out of Cubase? or are you just having problems with VSTi?

[didierb]

Thanks for the tip about Control Room, RealRoach. I turned it off.

Yes, all the VSTi's outputs are routed to Stereo Out and the MOTU is selected under Device Setup. I'm not getting any audio out of Cubase, except from my MIDI-triggered Korg Triton. The meters in the instrument tracks do peak, though, so Cubase is generating an audio signal; it's just not sounding it out. I can bounce the track and listen to the recording on iTunes, but not from within Cubase. Weird -- and unpractical.

What puzzles me, too, is Windows XP's Sound control panel, which says "NO AUDIO DEVICE" under the volume tab. The audio tab, on the other hand, lists MOTU Main Out 1-2 as the default device for sound playback. Is this normal? I would have thought the UtralLite would show under all tabs, too. (In Vista 64-bit Home Premium, the device is listed under all tabs.)

Thanks again for your input.

Cheers,

D.

[TheRealRoach]

This is unusual indeed.

The only times this has every happened to me were when:
- Cubase crashed and didn't release the audio driver properly. A reboot solved the problem
- The buffer setting is set so low that your system will flat our refuse to send any audio at all to the audio driver. A larger buffer setting solves this.

The Windows Audio/Sounds Properties shouldn't make much of a difference because when Cubase loads, it initiates the audio driver, and when it exits, it releases the audio driver. Each application loads the audio driver as it loads.

Since your exported/bounced audio plays back in a different app then I would say there is something wrong with the installation of the MOTU drivers. Maybe it was an incomplete/partial installation. Weirder things have happened.

You could try uninstalling all of the MOTU stuff and then reinstalling it. Before you do that though, could you post a screen shot of your VST Connections -> Output window, as well as your device setup windows (the part that tells you what your input and output latency is).

[didierb]

Hello, again,

I've re-installed the drivers several times with no luck. I've played around with the settings in CueMix -- monitor on, monitor off, etc. ... -- but no go. In Cubase, I've even deleted all the buses and recreated them, turned off ASIO and re-enabled it, but no luck whatsoever. I've tried the UltraLite with a MacBook Pro and I got sound out of it. Granted, it stutters like crazy even at really high buffer rates, but at least the VSTs were playing. Anyway, here is a bunch of screenshots. Maybe you can spot the culprit.

I took the "VST Audio System" screenshot without a project opened; that's why it shows a sample rate of 44 Khz.







This screenshot was taken simply from Windows, not from Cubase. I work at 48 Khz, so that's what it shows there.
















Thanks a lot for your help, RealRoach. I'm about ready to pack this thing up and return it. I've had the worst luck with audio interfaces. The only one that worked reliably was the PCI-based Echo Gina 3G. I stupidly sold it because I wanted something that would work on my PC and my new MacBook Pro. I tried an M-Audio unit before the MOTU and didn't even get any sound at all from that one. ... I'm starting to think my music is cursed.

[didierb]

Here's an interesting bit. I switched outputs, connecting the monitors to Analog Outs 1-2, instead of Main Outs 1-2, and voila, everything is sounding out as it should. Kinda makes me wonder what's the purpose of the Main Outs plugs. I've got a Tech Note posted on MOTU's Web site. It should be interesting to hear what their tech guys have to say.

[didierb]

OK, according to Mike at MOTU, the fault lies with the drivers. Here is his answer to my question:

Unfortunately, this is a known issue with the latest Firewire/USB 2 drivers. When utilizing the ASIO drivers, each output is offset by one stereo pair. We expect to address this behavior with a future update. All updates and news items are posted at http://www.motu.com, so check back periodically or subscribe to our news feed. In the meantime, I recommend connecting your monitoring system to the next highest output pair.

In other words, use a different output until the next update. I'm just glad I've got sound and that my UltraLite is not broken.

[TheRealRoach]

Yeah they majorly busted that driver. It's pretty well documented in a few other threads around here.

Glad it's sorted out!