I'm sure these poorer studios aren't the main demographic/market for the Apollo Twin so it's understandable that the issue could go un-noticed but I can confirm, at least on my system, every DAW except Cubase 5 and earlier doesn't see the Apollo Twin Thunderbolt drivers. I don't mind saying that since I own Cubase 10.5 which also gives me a license for Cubase 5. I have quite a few first generation immigrant African clients that just want to track vocals in my studio and have a cheap producer/studio do the music for them back home and all they want it tracked in Cubase 5.

Now you would think that would not be often and it isn't too often but once you start working with studios in Africa and poorer countries, it is extremely often since Cubase 5 was the last version to be cracked. Something is going on with Cubase 5 and earlier not seeing the UAD driver.Ĭubase 6 and onwards broke backwards compatibility with lanes and comping with Cubase 5 so anytime someone sends me a session to collab, co-produce, add session vocals to, I have to use Cubase 5. The Apollo Thunderbolt ASIO driver shows up in all modern 64 bit DAWs on the same Maschine though, Cubase 10.5, FL Studio, Maschine, Kontakt, Pro Tools 12, even Adobe Premiere. My internal laptop speakers work fine with ASIO4ALL though in Cubase 5. ASIO4ALL seems to work though but the Latency is terrible and if you use it with the Universal Audio WDM Driver it seems to cause clocking issues and the sample rate doesn't lock to the DAW and is off. I don't have this issue with my Apogee Duet 2, older Tascam FW-1884 interface, older Line 6 interface and my Aphex interface. I never really noticed until today, Cubase 5 32 bit can't see the Apollo Thunderbolt drivers on Windows 10. I have some older versions of Cubase installed on my system for compatibility with other studios.

Can i update cubase 5