Apollo Twin Duo USB Asio Driver does not work in DAW

Werner_K

New Member
Hi Folks,

I have a weird situation.

I first used my Apollo Twin Duo USB on a Asus P8Z77 V-Premium with a I7 3770K (1155) (Win 7 64 Bit) and it worked very well.

I have changed MB and CPU to I7 K6850 (6 Processors) with a Asus X99 Deluxe II on Win 7 64 Bit and I am not able to record with Apollo on any DAW.

I have Cubase 9 Pro and Studio One 3.

I can hear Music normally with any Audio Player.

However, when I start Studio One 3 it recognizes Apollo and a USB Asio Driver for it but it stops loading and states: Apollo... cannot be initialized and cannot start.

On Cubase 9 Pro it does not even recognize the Asio USB Driver of Apollo.

I uninstalled Driver of UA and reinstalled. I used all USB 3.0 ports. I unplugged all usb 3.0 ports and solely plugged in Apollo. No DAW recording possible.

I am out of any idea.

Is there a possibility to only download Drivers (without the 2 GB plugins) and install them separately?

Has anyone the same experience or any idea to solve this problem?

I really need to record with Apollo....

You help would be really appreciated

Thank You

Werner
 

Toxteth

Active Member
Hi and welcome to this forum. Do you know that certain usb3 controllers will cause problems.

from UAD's support pages:
Motherboards and PCIe to USB 3 adapter cards that use USB 3 controller chips from the following manufacturers are are not recommended for use with Apollo Twin USB:

Texas Instruments
Etron
Fresco Logic
ASMedia

Not saying that's your problem, but something to look at...
 

Werner_K

New Member
Thank you.

I was aware of that. Just surfed the Forum.

I used the Intel USB 3.0 Connection (mid board) of the MB and I have purchased the KT4005 with the NEC Chip. Didn't help.

Uninstalled UA newest 9.1 and switched back to original Driver which came with the Apollo (8.5.2.63) also did not help.

To be honest I do not like to uninstall several usb Drivers to get a single USB device running. That's not my imagination of plug and play.

The System is quite new set. Simply a Music machine.

Win 7 64 bit, Norton Security AV, Steinberg Cubase 9.0 Pro, Studio One 3, Steinberg Absolute 3, Native Instruments Complete 11, Toontrack, Focusrite 18i8 second Gen, Adobe Premiere and several Asio Driver of Music Instruments (E-Drums by Roland, Korg PX4, Roland GR-55, Line 6 POD HD 500x). That's all.

I know Focusrite might be the Problem.

Uninstalled Focusrite. No Change. Apollo ist not working properly.

Help...
 

Werner_K

New Member
Thanks for asking, Yes, also not work when Norton is disabled.

Changed a few things in the PC

Now I got the message "Apollo Twin USB cannot be initialized" when starting Studio One V3 Pro...

:-(
 

T11

Member
How did it go Werner?

These are the steps I would go through:

- Contact UAD support

- Install the new 9.2

- Download Korg USB-MIDI Driver Tools and choose:
"Uninstall Korg USB-MIDI Device"

(This little tool will list all your USB Midi-ports and show which ones are inactive/corrupted, after which you can delete those you might think may cause issues or simply just those you know you wont use again.)

- For Win 7/8.1: Downloads | minilogue - KORG USB-MIDI Driver (for Windows 7/8.1) | KORG (USA)

- For Windows 10: Downloads | minilogue - KORG USB-MIDI Driver (for Windows 10) | KORG (USA)

- Upgrade BIOS

- Check if I'd installed any screen capture program, VoiceMeeter or some other program which might try to put itself first in line in the computers audio chain.

If none of that would help then I'd consider to:
1. Uninstall Norton (and maybe replace it with MSE)
2. Upgrade to a later Win-version
 

UniversalAudio

Official UA Representative
Thanks for asking, Yes, also not work when Norton is disabled.

Changed a few things in the PC

Now I got the message "Apollo Twin USB cannot be initialized" when starting Studio One V3 Pro...

:-(
Hi Werner_K,

You should contact UA Customer Support directly for help with this. They can step through your setup and possibly screen share with you.

Please let us know how it goes!

Best,

-GK
Gannon Kashiwa
 

Werner_K

New Member
Thank you all for your kind support.

This is getting really weird.

I have tried 4 (!!) different PCIe USB 3.0 Extension Cards on a PCIe x16 Slot which has nor splitting of IRQ or bandwidth lanes with other on-board devices (I have a 40 lane cpu).

NEC Chip, Renesas Chip, VIA Chip

The Twin Duo now is plugged to a on-board Intel USB 3.0 slot.

I have tried de-installing Korg USB-Midi Driver, de-installing Norton Internet Security. No Antiviruis Program installed. Changing to Kasperky Internet Security.

Nothing helps... I have not one single entrance in the error protocols of windows (programs or system). Device manager tells me all system work. no error.

I can hear Music over the Twin Audio and it is recognized in the Sound Manager.

But dam... no DAW recognizes the ASIO Driver.

Studio One 3 Pro does recognize the Twin Audio but it not able to initialize or start it.

Cubase Pro 9 is not even recognizing the UAD USB Asio Driver. It only recognizes UAD Thunderbolt and UAD Firewire (although I have no device with either of the connections).

I am not inexperienced in soft and hardware since I assemble all my PCs (over 10 in the last years) by myself and install all.

That has never happened before. I am absolutely without any clue...

Win 7 64bit. All drivers and windows up do date. Driver UAD 9.2 installed (de-installed prior version before installing 9.2 with shut down, no restart)

Only MS office 365, DAWs, Anti Virus and music software (some instrumental usb drivers Roland etc.) nothing else on the Music PC.

Twin Duo worked proper on P8Z77 and X99 deluxe (version 1) not on X99 Deluxe II from Asus.

All chipset driver, USB driver and system driver are up-to-date. Focusrite 18i8 2nd gen. working also properly. This is off down when I try to work with Apollo twin. But is has parallel worked before on the P8Z77 with both Focusrite and Apollo Twin Duo.

I really do not want to change to Win 10 because of the spying and forced updates. I do not like to have a handy system on a PC with massive more power. I also read Win10 is not that stable and do not work with all daws or software properly. And I hate tiles...

What can I do?

Your help would be really appreciated.

best

Werner
 

T11

Member
Sorry to hear that Werner. Your best bet is probably to contact UAD support so they can help you find the cause of problem.

(Don't think u have to be too afraid of Win10. It's stable and works great, at least better than my prev Win7. When u install it you can click 'No Thanks' to all report-to-MS-stuff. Also you can control the updates. There are plenty of guides out there for both of these things.)

I hope that UAD will help u back on track. Good luck and hopefully u can report back the solution in this thread.
 

Raw_DSP

Active Member
Hi Folks,

I have a weird situation.

I first used my Apollo Twin Duo USB on a Asus P8Z77 V-Premium with a I7 3770K (1155) (Win 7 64 Bit) and it worked very well.

I have changed MB and CPU to I7 K6850 (6 Processors) with a Asus X99 Deluxe II on Win 7 64 Bit and I am not able to record with Apollo on any DAW.

I have Cubase 9 Pro and Studio One 3.

I can hear Music normally with any Audio Player.

However, when I start Studio One 3 it recognizes Apollo and a USB Asio Driver for it but it stops loading and states: Apollo... cannot be initialized and cannot start.

On Cubase 9 Pro it does not even recognize the Asio USB Driver of Apollo.

I uninstalled Driver of UA and reinstalled. I used all USB 3.0 ports. I unplugged all usb 3.0 ports and solely plugged in Apollo. No DAW recording possible.

I am out of any idea.

Is there a possibility to only download Drivers (without the 2 GB plugins) and install them separately?

Has anyone the same experience or any idea to solve this problem?

I really need to record with Apollo....

You help would be really appreciated

Thank You

Werner

Every latest Z/XX Asus MB uses the ASMedia controller for usb 3.0, i'm pretty sure that what uad claims on his page is intended as "only motherboard without native chipset helped by an external adapter WITH these controllers are subject to issues" By the way sounds like a driver/software mismatch to me.

- Have you changed MB and Chipset. Good. Have You installed from scratch drivers,asus suite, .inf files too? If not, almost certainly your OS will be a mess.
- Update Bios if available, install tipical asus stuff like Lan, SATA, Audio driver. For now avoid and disconnect from MB any unnecessary device like card reader, wi fi, external box often with additional USB2.0/3.0 ports

For the USB 3.0 starts with the oldest one, install a daw, download and install the UAD software (the whole package with their ordinary reboot!), check the multimedia sounds setting. Try to assign for multimedia streaming (web pages, you tube...) the internal asus audio card, at least for now, Just to be sure that the driver's resource are not occupied by any other applications. Try to use Cubase with ASIO driver, if it works update to latest usb 3.0 driver.
 

Matt Hepworth

Master of the UADiverse
Forum Admin
Moderator
If you've tried multiple UAD versions you may have the same mismatch thing I experienced.

-->Do you guys see any red error text when you launch the UAD Meter/Control Panel (the small rectangular window with the blue UAD-2 button on the left side)?

CAUSE
I had this issue trying to after Windows 10 update to Creators update, then trying a newer UAD version after. Though the cause of my issue was more of a worst case scenario, the symptoms are the same as you describe. It may be a mismatch.

After rolling back to Anniversary Update I was also no longer able to install or uninstall UAD software (missing system-xxbit.msi).

Post Creators Update UAD was 9.2. After rollback it was not really 9.1 or 9.2 and errored on uninstall or install.

The behaviour was as you describe, though.

SYMPTOMS
Console would load fine. Apollo seemed to be working, but was not recognized by the DAW. The clincher, though, was a red text error in the UAD meter/control panel.

SOLUTION
I was able to resolve by manually deleting all UA files from Program Files, ProgramData, and delete some references in regedit. I was then able to run a reinstall with 9.1. 9.2 still gave a missing system msi error.

That solved the issues for my side. The UAD Meter/Control panel was how I knew there was a mismatch somewhere.
 
UAD Bundle Month
Top