Hello!
I have brand new UR22-C, and I can’t get get stable audio playback through the device.
According to ASIO driver status, the dreaded “Audio Interruption due to USB error is detected” message appears in Steinberg USB driver settings, as soon as I try to play any longer audio stream, in addition to audio drops. This makes working with the device impossible. These drops appear only when audio output is loaded, when recording or when playing back with loopback there are no problems.
I am working with different PCs, one is a laptop, with Core i7-1235U CPU, which has integrated Intel USB chipset, and Windows 10 Pro 22H2.
Second is desktop PC, also with Windows 10 22H2, with integrated Intel W790 chipset USB, but I also tried PCI-Express add-on cards, with Renesas USB 3.0 controller, Diodes USB 2.0 to PCIe bridge, ASMedia 3242 PCIe controller (20 Gb/s) and Fresco 3.0 controller. Every single one of these have the same issue.
On the laptop dropouts are much more frequent, and can happen even twice in a second, and generally I haven’t got more than 10 seconds of uninterrupted sound.
On the desktop it’s less frequent, happens usually at most 4-5 seconds apart, and often times I can get 2-3 minutes of uninterrupted audio out of it. I gave up on laptop. I can’t set anything in its BIOS anyway.
I have already done my research in other places, and checked following:
UR22-C has newest firmware, and I have newest available software.
BIOS, firmwares on everything on the motherboard is up to date. Windows update is regularly ran and all devices - onboard and off-board have their drivers installed.
Windows is installed on GPT layout, and boots in UEFI mode. SecureBoot is on, set to Windows OS.
Windows boot disk is NOT encrypted.
I have ECC RAM, and I ran memtest on it, there weren’t any errors
ALL PCI-Express ASPM and power saving features are turned off in BIOS.
Power to USB in S5 (soft-off) state is disabled
ALL USB power saving features are turned off in OS.
Experiments I ran:
XMP is required for this PC to work, but I removed all but one RAM modules, and checked without it anyway - for all of the testing.
Turbo Boost is required for this PC to be usable (or it stays in 1.2 GHz clock all cores), but for the sake of test, I also disabled it - for all of the testing.
I checked USB ports only directly, without any USB hubs (I don’t have any anyway).
I checked both powered with USB-C, and with external micro USB power, using high quality power brick and high quality portable USB power bank.
I installed one after another all of the USB controllers listed above
I checked obviously both 3.1 and 2.0 modes, all modes (Low Latency, Standard and Stable) and 128/512/2048 values.
I talked with my retailer’s support staff, and they agreed to lend me second UR22-C device, it behaved exactly the same.
I grabbed another SSD and installed Windows 10 from scratch.
I replaced cables with high quality ones - USB-A to USB-C, and USB-C to USB-C, the latter included PD 3.0 certified cables.
I haven’t noticed any of these having any impact on the issue.
Although I own and use many strange USB devices, none of them ever gave my any issues.
I don’t have any more ideas. Is there anything else I can do?
Wow! You seem to have a stubborn issue here!
I was tempted to suggest an exorcism… but let’s try other options first.
The error message suggested this could be a hardware issue and you did a great job investigating this track.
One last hardware test I can think of is to make sure you use the external power supply (and not the usb-c power) and set the “Power Source” slider in the back accordingly.
Then let’s look into the software side…
Open Task Manager and close/disable/stop all non-critical applications running in the background. I suggest the bulldozer approach where you kill a “large” number of processes and services (take notes) until the error message disappears, then reboot and try by disabling only half of your previous test, until the error shows up again. Then disable half this list, etc. Take a pen and paper to take notes and avoid going nuts.
Let me think about it if I get other ideas… hopefully others here will have seen that issue before and provide a quicker fix.
Very bizarre…
As a first order of business, I completely reinstalled my OS from scratch, switching to Windows Server 2022, my reasoning being there is far fewer background stuff going on, and most programs need to politely ask to be run, instead of treating autostart as their home turf. Sadly, to no avail.
I suggest the bulldozer approach where you kill a “large” number of processes and services (take notes) until the error message disappears
You see… the problem is the error never goers away. It wasn’t an issue that started happening, it was present from day 0.
One last hardware test I can think of is to make sure you use the external power supply (and not the usb-c power) and set the “Power Source” slider in the back accordingly.
I already did that test, with truly decent power brick, but I repeated test with laboratory power supply I borrowed from my workplace. Also it didn’t help.
In another news I lent the device to my friend, who uses Focusrite 2i2 (we switched for a few days). He said, that on his PC (AM4 based PC and Windows 11) he had the error pop up few times, but only on USB extender (he has optical USB extension as his PC in different room), when plugged directly to the PC there was not a single problem.
So if no one else has any ideas… I will probably try some other device. It pains my heart, as UR22 has absolutely everything I want, including built-in effects, which drastically reduce software clutter and my work.
Hi there
Have you seen this? A whole list of tweaks that might help.
Although it didn’t worked for me. Im still looking for a solution to my case. Still have some days before I wont be able to return mu UR44C so I will dig deeper and try to work it out.
Please write here when you will have some news on your case.
Got my UR824 in 2018. After a Windows 10 update to 20H2 (in 2021) this Audio issue occurred. I have never been able to use this unit as Master since then, and none of the current or past Software, provided by YAMAHA makes any difference.
It has never been addressed on the software side of thing’s, and fear this will continue.
If I am to be whole heartedly honest in my opinion, I would advise you to return it. The Driver seems to be a very poor performer in certain Windows environments. Folk have been expressing their frustrations for years, still, no change.
Hello!
Yes, this post was one of the first I stumbled upon, and I have tried this in every Windows system I used. I spent little more time trying to pin this down, and arrived at conclusion, that simply nothing can be done.
This device is simply incompatible with my computers.
I have two PCs now - a Intel Gen12 (Alderlake) based laptop, made by Clevo, which has no controls over USB and power settings in BIOS, so I can’t really do anything. It’s running Windows 10 Pro, and stutters on output (and displayes the error message) every 30 or 40 seconds. But in addition to this, it also interrupts effects run on host PC (I am using IK’s Amplitube, as I have full license, and never had this issue).
Second PC is Xeon W7 based desktop, on ASUS W790-Ace motherboard. It’s basically a server in an ATX PC form factor, and it has very different architecture. Power controls, and USB routing were of lower priority in this hardware than in your typical desktop PC, and USB is hanging off of PCI-Express, instead of chipset or CPU/SoC. It’s running currently Windows Server 2022. It doesn’t help that there is a GPU and two dozen SSDs. The audio drops every 4-5 seconds.
I do not plan to put together another dedicated to audio input only PC. So this is the end of the road for me with Steinberg. I am eyeing some cheaper Behringer unit like UMC202HD, since I won’t get full 100% refund on UR22C.
I must add that I have been unsuccessful with Windows 10, intel 6th gen and Windows 11, intel 11th gen.
I personally doubt that trying an older version of Windows, ie:10, will heed a more positive result. Just maybe in Windows 7, but the activation server for W7 is not active anymore.
The YSUSB Driver is a poorly written piece of software for Windows (IMHO) in comparison to the other 5 audio interfaces software that I own.
Some find workarounds and are happy, other’s (like me) do not see why we should be performing PC Acrobatics to get the YSUSB Driver to perform as it should. Simple tweaks are ok, but diving into the BIOS /UEFI to do this and that, is a bridge too far, personally.
thank you for covering that. You saved me a Sunday evening
But Lets be honest - Steinberg needs to officially address this.
It’s clear that it’s their fault, either in driver or in hardware. I have tried Behringer, SSL, Focusrite, and some even random cheap DAC/Guitar interface combo from AliExpress. None have same issues, and work on same hardware. Do they really want to hear “Avoid at all costs, doesn’t work” in product reviews, and comments?
And since the product package contains software keys, resell and/or returns are highly problematic.
The YSUSB Driver is actually supplied by YAMAHA, they are the ones who need to address this problem.
I feel confident that Steinberg has informed YAMAHA of the problems some of us are facing, but I do not believe YAMAHA view this as an urgent issue, since nothing they have released since 2021 has made any improvement on the YSUSB Driver’s performance, on W10 or 11.
I also believe that time will eventually catch up with YAMAHA/Steinberg audio interfaces on Windows, with more and more people starting to have issues. If not immediately, then at some stage down the line.
I’d like to know the exact specs for the Windows PC build, they use on testing, that makes YAMAHA so confident in releasing these abysmal YSUSB drivers for Windows. I just don’t get it.
Well I must say that indeed it is a disappointing that Steinberg has these flaws and by studying this forum and other sources it seems that there is not much going on from their side to get better. I was hoping to make my dream come true by buying this satisfy-all-my-needs- interface (UR44C) but ended in second week of struggle to make it work
Good that we have this community where people can share their feedback and important infos. It is very helpful for me.
Another good side that I see in this bad situation that these Steinberg issues are with us for some time now which allowed us to accumulate large volumes of info and nad solutions gathered by poor customers who are (stil) struggling to find a fix by trial and errors. Great job to us!
So having said all that It seems that I have found some cure to my issue "Audio Interruption due to USB error"
I have performed as much as I was able to from the “Great List Of Solutions” provided by @dondawell in his thread (linked few posts above). Thanks Dondawell for your input!
Mainly updating everything that was to update (using manufacturer site and three different standalone apps to find different drivers that needed update). Experimenting with ports, cables, uninstalling/disabling everything related to audio that could interfere with YamahaSteinbergUSB driver, even tweaking Registry Editor and BIOS… finally I got my self to a place where I still got this error once in a while in Yamaha Driver Panel, but there is no more audio cuts off (drop outs) during playback or recording. Im testing it second day and so far so good
I might decide to keep this interface
Just I will never get back those long days wasted for fixing something that should work from the start
Steinberg and Yamaha - please do something about this
My problems started with the Windows 10, OS update to 20H2 and has carried over to Windows 11.
The tweek I got from @dondawell, setting the XHCI mode in the UEFI to Manual, cured the problem for a few months, only to return. I just gave up after that.
Well I was somehow prepared. Before buying this interface I did a upgrade from win 10 to 11 j I wanted to rule out the situation that I will run it with no issues on 10 and then one day - months, years after purchase when I will finally (and inevitably) go to win 11 and face this nightmare after the return policy is over. And now I have these issue but I also have 30 days to test it.
Yes risky, but the battle is not over - I still have some tweaks that I leave for later in case that issue will return. And there is still hope that Steinberg+Yamaha will finally one day release an updated and healed driver
This interface is exactly what I need right now and a truly upgrade to my home studio - its worth the struggle.
Two weeks left until end of my return period.
If you have any suggestion what tests I could perform to provoke the issues than write now!
In my case it nothing helped from any of the other help threads. My drivers and firmwares are always up to date. Only noticeable difference I have observed during troubleshooting is switching to stable/2048 configuration, which grants some time, a minute or so, before the interruptions happen. Shorter buffer / Low Latency mode allows for immediate problems. This in my humble opinion points to a bug in driver.
Steinberg makes the device, but the support contact is indeed with Yamaha Music (in my case Yamaha Music GMbH).
Device is supported, so lets drop them some email.
Community support forum is one thing, but at some point manufacturer should step in.
Yamaha has pretty good track record when it comes to support of keyboards from my experience, we will see how it goes with USB Audio interface.
When I initially contacted Steinberg Support back in 2021, and implemented all the advice given, the very last suggestion was a clean install of Windows 10, needless to say, made no difference.
I didn’t contact YAMAHA about the issue, but will certainly do so, now. Who knows?
I must say that the list of what one can do and change in PC/laptop is long. These steps listed by @dondawell is something more universal (except some BIOS tweaks) but each machine is different and has its own programs, drivers, processes and services.
For me for instance from the things that I had to discover for my self was uninstalling one audio software that I was using as my windows EQ, deleting Realtek ASIO driver from Regestry, disabling audio driver for my monitor (I use a adapter from VGA to HDMI that supports audio). Uninstalling my driver for my previous audio interface. Disabling in Device Manager all devices that may interfere with YSUSB driver.
Other thing was to make my laptop more light and save CPU resources for DAW by stoping and disabling many system services, uninstalling some programs that I found useful, but used rather rarely. I dont haver that powerful machine, so I need every drop of CPU for make playback and recording smooth and thus decrease the audio drop outs.
So I encourage everyone who is determined enough to make own research and dig deeper.
Hi All,
Just to chime in. I have the same problems with my UR24C device connected to a W11 Dell Precision 7740 system.
I am getting not only drop outs but apparently some kind of driver reboot with 1-2 secs (!) audio interruption.
The driver panel is reporting an error: “Audio interruption due to USB error is detected…”.
Reading thru a few posts about Yamaha driver issues it seams like the drivers are just crap. Is there anyone out there who could report that their UR*C device are working just fine with no drop outs even with low buffer sizes?
I feel like I have to cut my losses, toss my UR22C and buy a competitor, like UA Apollo or RME Babyface interfaces. They are supposed to have stellar drivers …
I don’t want to waste my time reinstalling windows, disabling bunch of drivers etc… I just dont have the time nor the nerves to do it …
Sorry, I thought I bought decent HW that I expect to work flawlessly with their Cubase SW which I also bought.
Frustrating …
