Hi there,
I've bought an SSL2+. I've installed the drivers and updated the SSL and it works, if I (re-)start my PC (Win 10) and Cubase 13 with the interface plugged in. But if I plug it in with win or cubase already running it kind of freezes projects in Cubase - as if I had tons of plugins and minimal buffer. Restart the pc -the SSL works (in the same project). I checked Sample Rate. I don't have similar problems with the babyface, antelope orion 32+ gen 3 or focurite interfaces. Those all work plug and play if i switch asio drivers in cubase. Any ideas?

- also - but comparativley smaller issue: the SSL shows 4 potential Asio drivers which is kind of anoying if you switch interfaces dayily like I do working in different places. The list of asio choices gets overly long. I bought the SSL specifically for one place so I don't have to carry the babyface around all the time. RME: I did not have one single dropout in 20 years. Why is it that other companies aren't able to programm decent drivers or virtual mixers like total mix. sigh...
Best
Hannes

Hmmm I have a 2+ and don't even remember installing software for it, although must have done.

What I would do it make sure the WIN 10 is never looking for the SSL for its sounds. Just have an ASIO driver running in Cubase. Let Win 10 carry on with laptop speakers or whatever. A lot of Win sounds and web pages will confuse the, ahem, out of a sound interface by sending different sample rates of material. Bad idea.

Plugging it when Cubase is running is probably not a great idea either as the software engine relies on the info it gets on booting.

Otherwise SSL 2+ is best for the money at the price point. I quite like it. I have a lot more expensive things too.

Hi AVSC,
thanks for your advice. I'll try so next time I am using it.

What on earth are you doing?

Your post gave me a headache.

Swapping interface while daw is running? wth