I’m having the same issue. Unmixing a song with high quality causes only silence. Other quality settings work. I’m using it as a ARA extension in Cubase 14 Pro, windows 11, AMD GPU.
Hi @Joza
can you specify which GPU exactly?
AMD Radeon RX 6800 as GPU and AMD Ryzen 9 3900X as CPU
1 Like
@Jonas2021 Same issue in the standalone app, but changing AI Processing Device from Auto to CPU solves the issue.
This thread also describes that despite switching to lower settings and rendering with GPU, only the CPU is used.
I have this on high settings trying WAV or FLAC.
I tried numerous songs and the stems show they have split but no play back and black screen.
I tried it on normal settings and it worked.
I tried SL 11 on high and it worked but sounded as good as normal settings on SP12.
Quite disappointed, I even sent a ticket and had no response as of yet.
I am on Window 11 Pro 24H2 latest build.
Asus Crosshair Extreme x870e latest BIOS.
CPU-9950x3D.
64gb Dual Channel 6000mtps Corsair Dominator Ram on Expo.
GPU-9070xt
Main Drive - Samsung 9100 Pro Gen 5 - 2tb
Windows and drivers are fully up to date.
All software is legit and up to date.
Really would like a fix for this 
1 Like
Same problem on Ryzen 5950X, RX 6800xt. HIGH results in black screen standalone or in Cubase but works on Balanced or Fast. High sometimes causes Cubase to crash but only about 25% of the time.
It is essential that @Robin_Lobel do more thorough testing on AMD CPUs and GPUs. Come on, Robin, I love your work man, but you really need to buy and test more AMD stuff in-house. I do NOT use nVidia anymore for any of my many DAWs, due to other issues I’ve had, so this AMD situation is not good to see.
It is essential that Steinberg pay attention to this too, and make sure the QC process includes more AMD CPUs and GPUs.
Please, Steinberg, don’t release things without a more strenuous QC process. It is NOT enough to say that the beta team missed it and that once you launch it into the wild, you’ll find more issues. Of COURSE you’ll find more issues once it’s out in the wild, but this one is too obvious, hitting too many users with obvious similarities of hardware. Clearly, people on the QC team are NOT putting this through its paces on AMD hardware, and you shouldn’t have to rely on the beta team to catch this kind of thing.
Again, I love Robin’s work, no disrespect intended with this post, and I can’t wait to use SL12, but this needed more time in beta, with a more diverse set of hardware, and more people at Steinberg running quality checks with AMD in-house. If that takes more time, so be it. If that costs $10 more per license, so be it. I KNOW you can’t cover every possibility, but this one is pretty obvious.
Let’s go! Please get this patched up and let’s move on, and not let it happen again.
Sincerely, and with respect,
A long-time Steinberg customer
3 Likes