I´m working with an audio interface from Steinberg, the UR44.
I have very cpu-intensive projects in Ableton and sometimes when I save my project and close Ableton, the audio interface crashes and gets deactivated.
Actually, this shouldn´t be a big deal as I could just re-assign it in the audio settings of Live the next time I open my project, but this is not possible.
I have always to restart Windows 10 because the audio interface cannot be activated during the current WIN 10 session. I can´t select it in Live 10 in the settings (ASIO -> and then choosing the UR44) because it is not listed there.
Has anyone else experinced the same problem? Is this an issue with Steinberg interfaces only?
I can´t find a way to re-activate my interface in WIN10 after a crash without having to reboot my system.
Rebooting windows to be able to re-activate my audio interface
-
- KVRian
- 1286 posts since 7 Dec, 2013 from Earth
Can you still use normal Windows audio (Youtube, Spotify, etc...) after such a crash? I think this problem might be USB related. You could try connecting your UR44 to another USB port.
I also use Windows 10 and a Steinberg UR44 (for about 2 years now) and never had this problem. In fact, this interface works a lot better than my old Focusrite 2i4.
I also use Windows 10 and a Steinberg UR44 (for about 2 years now) and never had this problem. In fact, this interface works a lot better than my old Focusrite 2i4.
-
- KVRian
- 997 posts since 27 Apr, 2005
The more pressing problem to solve would be keeping the interface from crashing to begin with. I don’t think theres any other remedy other than a reboot if it really does crash. I have had this happen with usb midi interfaces in the past, and one thing to try is to disable the windows power saving settings for your USB buses on the motherboard. A lot of advanced USB devices don’t react well to Windows managing the power consumption of the usb bus and crash, so tuning it off could help.
https://helpdesk.flexradio.com/hc/en-us ... ed-Devices
https://helpdesk.flexradio.com/hc/en-us ... ed-Devices
-
- KVRAF
- 5144 posts since 3 Oct, 2013
Roland Duo also knows it I use https://www.vb-audio.com/Voicemeeter/ as middleware ( DAW : virtual ASIO : real ASIO)
"Where we're workarounding, we don't NEED features." - powermat
-
AdvancedFollower AdvancedFollower https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=418780
- KVRian
- 1342 posts since 8 May, 2018 from Sweden
This might not work in your case since the actual audio interface crashes (which it shouldn't, obviously, so I'd look into the root cause of that).
However often it's enough to restart the Windows Audio service rather than the entire PC:
net stop audiosrv
net stop AudioEndpointBuilder
net start audiosrv
Can be put into a Bat file if you have to do it frequently.
However often it's enough to restart the Windows Audio service rather than the entire PC:
net stop audiosrv
net stop AudioEndpointBuilder
net start audiosrv
Can be put into a Bat file if you have to do it frequently.
Take a single oscillator, producing a drone. Send it to the wave shaper, altering the tone.
This can be a triangle, Sawtooth or a square. Modulate the pulse width, nobody will care
This can be a triangle, Sawtooth or a square. Modulate the pulse width, nobody will care
-
- KVRian
- 705 posts since 25 Nov, 2010
Unplug usb cable that is connected to audio interface, and reconnect it 
-
- KVRist
- Topic Starter
- 127 posts since 24 May, 2017
Thanks Everyone for the helpful replies!
Yes, everything else works fine after the crash. I can listen to music, watch videos with sound on YT etc.. It seems that only the ASIO related drivers cannot be reloaded.Reefius wrote: Fri Jan 03, 2020 2:18 pm Can you still use normal Windows audio (Youtube, Spotify, etc...) after such a crash? I think this problem might be USB related. You could try connecting your UR44 to another USB port.
I also use Windows 10 and a Steinberg UR44 (for about 2 years now) and never had this problem. In fact, this interface works a lot better than my old Focusrite 2i4.
-
- KVRist
- Topic Starter
- 127 posts since 24 May, 2017
Done, thanks a lotShawnG wrote: Fri Jan 03, 2020 2:26 pm The more pressing problem to solve would be keeping the interface from crashing to begin with. I don’t think theres any other remedy other than a reboot if it really does crash. I have had this happen with usb midi interfaces in the past, and one thing to try is to disable the windows power saving settings for your USB buses on the motherboard. A lot of advanced USB devices don’t react well to Windows managing the power consumption of the usb bus and crash, so tuning it off could help.
https://helpdesk.flexradio.com/hc/en-us ... ed-Devices
-
- KVRist
- Topic Starter
- 127 posts since 24 May, 2017
Very interesting, thank you very much! This will save me a lot of time if it worksAdvancedFollower wrote: Fri Jan 03, 2020 3:57 pm This might not work in your case since the actual audio interface crashes (which it shouldn't, obviously, so I'd look into the root cause of that).
However often it's enough to restart the Windows Audio service rather than the entire PC:
net stop audiosrv
net stop AudioEndpointBuilder
net start audiosrv
Can be put into a Bat file if you have to do it frequently.
-
- KVRist
- Topic Starter
- 127 posts since 24 May, 2017
This was the first thing I did but it doesn´t work. ASIO is still disabled after reconnectBrokenTrance wrote: Fri Jan 03, 2020 5:23 pm Unplug usb cable that is connected to audio interface, and reconnect it
-
- KVRAF
- 5913 posts since 17 Aug, 2004 from Berlin, Germany
Sometimes when I open a project but do other things outside Cubase, the Asio driver is disabled after a while (I'm not sure if this is a crash?). Anyway, the result is the same, I have to restart Windows because there is no way to reinitialize the Asio driver.
Audio still works, I just can't use the Asio driver and I don't have audio in Cubase.
Is it related to the energy saving mode? I don't think so, as even in "Steinberg Audio Power" energy saving mode selective energy saving is disabled for USB.
I'd say this is a bug in the Steinberg/Yamaha Asio driver (and I haven't found a solution yet)
Audio still works, I just can't use the Asio driver and I don't have audio in Cubase.
Is it related to the energy saving mode? I don't think so, as even in "Steinberg Audio Power" energy saving mode selective energy saving is disabled for USB.
I'd say this is a bug in the Steinberg/Yamaha Asio driver (and I haven't found a solution yet)
| Links-
- KVRian
- 1286 posts since 7 Dec, 2013 from Earth
Is your USB driver up-to-date? Latest version can be found here:
https://www.steinberg.net/en/support/do ... river.html
https://www.steinberg.net/en/support/do ... river.html
-
- KVRist
- Topic Starter
- 127 posts since 24 May, 2017
This is an interface crash of the ASIO drivers, yes. Very annoying, never had a similar issue with my older audio interfaces. I agree that this must be a bug in the Steiberg software. I will drop a mail to their support and report back here.4damind wrote: Fri Jan 03, 2020 7:35 pm Sometimes when I open a project but do other things outside Cubase, the Asio driver is disabled after a while (I'm not sure if this is a crash?). Anyway, the result is the same, I have to restart Windows because there is no way to reinitialize the Asio driver.
Audio still works, I just can't use the Asio driver and I don't have audio in Cubase.
Is it related to the energy saving mode? I don't think so, as even in "Steinberg Audio Power" energy saving mode selective energy saving is disabled for USB.
I'd say this is a bug in the Steinberg/Yamaha Asio driver (and I haven't found a solution yet)
-
- KVRAF
- 10151 posts since 16 Dec, 2002
1) Have you tried disabling and then re-enabling the device when the problem occurs?
2) Have you tried deactivating power saver in both the device properties and under USB controllers?
Both of thbe above under Device Manager.
3) Have you performed tests to check another USB device isnt causing the problems.
Has the device always performed this way or only since recently?
2) Have you tried deactivating power saver in both the device properties and under USB controllers?
Both of thbe above under Device Manager.
3) Have you performed tests to check another USB device isnt causing the problems.
Has the device always performed this way or only since recently?