Apollo Twin USB I/O Matrix
- Thread starter Pixel
- Start date
You still have the virtual, but Windows doesn't route to it the same way Mac does.
Thank you
Is there a way for Windows to show it as an ASIO instead of MME/WDM?
I've looked at the support pages
https://help.uaudio.com/hc/en-us/ar...Windows-WDM-System-Audio-with-Apollo-Twin-USB
I don't see the DAW preferences
Last edited:
As far as I'm aware the ASIO vs WDM is configured in your DAW. Some DAWs can only use ASIO (Cubase, Pro Tools, etc.).
I've never used anything but ASIO with the Twin, so I may not be much further help.
What DAW?
I've never used anything but ASIO with the Twin, so I may not be much further help.
What DAW?
To be clear, the virtual channels are assignable within the DAW (at least under ASIO), but I don't believe they are through Windows.
I tested with Audacity and couldnt select ASIO but the main use is with OBS using their ASIO input source which should detect ASIO devices.
It detected my Asus soundcard which uses Unixonar drivers
(I installed and uninstalled that just to check my other soundcard was being detected and their wasn't a problem with OBS which there wasn't)
The problem is that OBS detects upto 8 channel devices and the Apollo twin is a 22 channel device hence why my only options are:
1) I/O Matrix and create a 2 channel virtual output
2) Show the Apollo Twin as a ASIO device that can be detected in OBS.
Last edited:
A small update for those who also broadcast with OBS. The ASIO third party developers have spent hours with me trying to resolve this issue and broke down the probable causes related to the UAD Windows driver. I passed on the information to UAD Support. This was their response:
then they automatically closed the ticket.
I then passed on the asio plugin developers are willing to collaborate and then received this reply.
I don't like how this customer support representative is insinuating I am a representative of OBS or whether I have some kind of ulterior motive.
Sheesh if this is the response no wonder other streamers/broadcasters/Window users who have this exact same issue gave up and used a virtual audio cable instead.
Regardless I have passed on the developers contact details or requested an email address for them to contact as he is only a "customer support representative" and all the technical information I provided will probably be lost in his hands.
then they automatically closed the ticket.
I then passed on the asio plugin developers are willing to collaborate and then received this reply.
I don't like how this customer support representative is insinuating I am a representative of OBS or whether I have some kind of ulterior motive.
Sheesh if this is the response no wonder other streamers/broadcasters/Window users who have this exact same issue gave up and used a virtual audio cable instead.
Regardless I have passed on the developers contact details or requested an email address for them to contact as he is only a "customer support representative" and all the technical information I provided will probably be lost in his hands.
Well, what was your solution?