Originally Posted by David Rick ➡️

If Windows is not detecting your Lyra, but it still works fine in your DAW's, that's a blessing in my book! I went out of my way to arrange that by uninstalling the WME drivers so the OS can't send full-scale status beeps and bloops through my expensive studio monitors or deafen me when I'm editing something on headphones. Who wants an extra, unspecified mixer app or sample rate conversion inline when making critical choices about mastering levels and dither? I use my motherboard's audio system as a decoy and only route it through my monitor controller only when I'm watching a YouTube video.

Originally Posted by David Rick ➡️

If Windows is not detecting your Lyra, but it still works fine in your DAW's, that's a blessing in my book! I went out of my way to arrange that by uninstalling the WME drivers so the OS can't send full-scale status beeps and bloops through my expensive studio monitors or deafen me when I'm editing something on headphones. Who wants an extra, unspecified mixer app or sample rate conversion inline when making critical choices about mastering levels and dither? I use my motherboard's audio system as a decoy and only route it through my monitor controller only when I'm watching a YouTube video.

Originally Posted by David Rick ➡️

@ Riothood : My Orpheus converters have been working fine under Windows 10 for some time now. I explained upthread what I had to do in terms of using the legacy Firewire driver, etc. There are some reports that isn't necessary anymore, maybe in Windows 11. The "decoy" strategy to keep Windows from using my interface for "junk" applications is what I've been doing for years. You can set the default audio device to Realtek or whatever explicitly, or you can simply not install a WME driver for the Orpheus.

Originally Posted by bpackard ➡️

TL;DR
I'm seriously considering ditching Prism for RME, because drivers.

Since getting a new Lyra 2 in 2019, it's been a love hate relationship. Love the sound, hate the uncertainty of their drivers. I read the glowing reviews and ignored the occasional mention of poor drivers. I think I biff'd it.

I'm a Studio One user. (yeah, I know... Hush lol). It's what I learned, and what I like.

Budget interfaces prior to the Prism, even Behringer, we're stable and performed quite well with Studio One. I was ready to upgrade.

I chose the Prism Lyra 2 because it had well reviewed and praised conversion, preamps, and the I/O I needed for my small producer studio. On paper, it made sense to go "all in" on what many consider the best. What I didn't pay attention to was the random mentions of bad drivers. I had no idea...

2019. Day one with the interface, Studio One's ASIO support glitches with dropouts (garbled audio) every time I mixdown or bounce. Sometimes Studio One would straight crash. Curious, I plugged in my old UCM202, reinstalled the driver, Studio One works great again. As the good IT guy I am, I know the last change I made is likely the issue, but I had to be sure. So I tried the Lyra on a different, "known good" PC, same issue. I contacted Presonus support as well as Prism.

Presonus support, well... They have fingers and love to point them at everyone else, but eventuality the ticket got elevated so they could see through a remote session what was happening (even though the debug reports all point to prism's driver). This was due diligence on my part to eliminate the DAW as the causing issue.

In Prism's defense, they were WAY more responsive and willing to help than most companies. They provided firmware and drivers that captured diagnostics and it really seems they care. I still believe that.

Unfortunately, it took a while for them to send me new drivers to test. They managed to fix the crashing issue, but the dropouts after bounce/mixdown persisted. In fact, since having the Lyra 2 I've had to change buffer size on the interface EVERY time I did any processing of audio. Bounces, mixdown, stems, freezing tracks, processing Melodyne, etc. It wasn't a show stopper, but man it's annoying to do extra steps just to get audio to play properly. Especially after almost 5 years.

When Studio One updated to 4.6, new issues arose, all dealing with Prism's ASIO driver (WDM works just fine). I was able to work around them but it just added to the annoyance. When S1v5 came out, I waited for a year to see if Prism would put out a new driver. Luckily they did and the new issues from 4.6 went away leaving only the annoying mixdown dropout issue. It's sad that THAT'S what normal is for me.

The release of Studio One v6 caused no new issues with the Lyra 2. Then v6.5 comes out.
It has some great new features I was eager to try. ATMOS support, new reverb plug, etc. So, I updated. Big no-no. The Lyra 2 doesn't even interact with the software making Studio One v6.5 unusable. Show stopper.

Once again I am in ticket limbo while Prism and Presonus duke it out. I'm sooo done. What's the point of having the Mercedes of conversion if the hardware sh*ts the bed every time a DAW updates?

So, here I am 5 years later seriously considering downgrading to the RME UCX 2 simply because of their renown drivers. I've held my Prism loyalty for too long. I'm done being nervous if minor DAW updates break my interface. That shouldn't happen.

So, my question: If you own any RME product, has it ever sh*t the bed like Prism?

I've read many reviews, read a lot of forum threads, and I haven't seen much negativity at all with their products and "in house driver development" sounds pretty dang good right about now.

Thanks!

Originally Posted by snoskit ➡️

Use the Lyra as a converter hooked upto the UCX2 using ADAT.
Routing may need to be setup first in the Lyra.
Select RME as ASIO unit.
In Totalmix:
ADAT in 1+2 will be Lyra inputs.
ADAT outs 1 - 4 will be Lyra outputs 1 - 4.
ADAT outs 5+6 will be Lyra headphone out.

manual

Originally Posted by snoskit ➡️

Sorry been a bit busy.

optical cables 2x (in and out) needed.
In Cubase audio setup you need to enable UCXII ADAT 1 + 2 and 3 + 4.
In Cubase set your outputs to use these channels (normally that'd be master group channel).
In Total Mix you can set main outs as ADAT 1+2, or 3+4.
In UCXII settings I'd set the clock to internal
In Lyra settings I'd set clock source to ADAT.
In Lyra I'd set it to ADAT mode ADAT4