bickieb
Max Output Level: -90 dBFS
- Total Posts : 8
- Joined: 2017/07/12 20:31:41
- Status: offline
Roland DUO-Capture ex UA-22 not working after windows 10 update
Hiya! After checkin what could be the problem, I saw that on the day I couldn't use the duo capture in Sonar there was an update that changed something in the Roland Duo capture. I tried recovering, but that didn't help - so far. Anyone familiar with a problem like this? Hope someone is able to help me.. :o Regards, Rick
post edited by bickieb - 2017/07/13 13:12:31
|
bickieb
Max Output Level: -90 dBFS
- Total Posts : 8
- Joined: 2017/07/12 20:31:41
- Status: offline
Re: External soundcard error
2017/07/12 20:42:36
(permalink)
I see that I can't post links yet (?)
But it says; the following drivers either do not support the current audio format, or are in use by another application.
Please choose whether you want to disable them or use them anyway.
And then it shows: OUT(DUO-capture EX)
IN(DUO-capture EX)
|
bickieb
Max Output Level: -90 dBFS
- Total Posts : 8
- Joined: 2017/07/12 20:31:41
- Status: offline
Re: External soundcard error
2017/07/13 06:58:45
(permalink)
|
tlw
Max Output Level: -49.5 dBFS
- Total Posts : 2567
- Joined: 2008/10/11 22:06:32
- Location: West Midlands, UK
- Status: offline
Re: External soundcard error
2017/07/13 13:08:56
(permalink)
That sounds like another application, or Windows itself, has taken over the device driver and not released it back to Sonar. Sometimes there's another reason, which is that another application or Windows has changed the sample rate to one other than SOnar is set to.
Do you have Window's sounds enabled? If so, turn them all off.
If you have anything open that might use the sound driver - media player, web browser etc., close them before launching Sonar.
There's a setting on Sonar preferences to "share device drivers with other applications". If it's ticked, try unticking it. That should mean Sonar refuses to hand the driver over to anything else. If it isn't ticked, try ticking it and see if that makes a difference.
Sonar Platinum 64bit, Windows 8.1 Pro 64bit, I7 3770K Ivybridge, 16GB Ram, Gigabyte Z77-D3H m/board, ATI 7750 graphics+ 1GB RAM, 2xIntel 520 series 220GB SSDs, 1 TB Samsung F3 + 1 TB WD HDDs, Seasonic fanless 460W psu, RME Fireface UFX, Focusrite Octopre. Assorted real synths, guitars, mandolins, diatonic accordions, percussion, fx and other stuff.
|
bickieb
Max Output Level: -90 dBFS
- Total Posts : 8
- Joined: 2017/07/12 20:31:41
- Status: offline
Re: External soundcard error
2017/07/13 13:14:49
(permalink)
tlw
That sounds like another application, or Windows itself, has taken over the device driver and not released it back to Sonar. Sometimes there's another reason, which is that another application or Windows has changed the sample rate to one other than SOnar is set to.
Do you have Window's sounds enabled? If so, turn them all off.
If you have anything open that might use the sound driver - media player, web browser etc., close them before launching Sonar.
There's a setting on Sonar preferences to "share device drivers with other applications". If it's ticked, try unticking it. That should mean Sonar refuses to hand the driver over to anything else. If it isn't ticked, try ticking it and see if that makes a difference.
Thanks for your reply. I've updated my post, since I think it's a windows update that caused it. Familiar with an annoying windows update that causes this? And since it's an 'essential' update I can not NOT install it =S
|
michheld
Max Output Level: -90 dBFS
- Total Posts : 32
- Joined: 2014/12/20 15:29:05
- Status: offline
Re: External soundcard error
2017/07/13 14:28:03
(permalink)
Hey, just a try: I had to deactivate a programm e.g. found in the systray like "PC Equalizer" to be able to record with my QUAD capture again. Since Win10 these programs takeover the sound channels more exclusively, I guess. Try to close these first, before reinstalling the drivers. And besides: After installing Win10 I had to install the Roland driver updates for QuadCapture. They are normally loaded from the Internet when plugging in the USB-cable...Beware of a domain-WSUS-server, these may prevent the driver from loading.
Best regards
|
bickieb
Max Output Level: -90 dBFS
- Total Posts : 8
- Joined: 2017/07/12 20:31:41
- Status: offline
Re: External soundcard error
2017/07/13 18:36:10
(permalink)
michheld
Hey, just a try: I had to deactivate a programm e.g. found in the systray like "PC Equalizer" to be able to record with my QUAD capture again. Since Win10 these programs takeover the sound channels more exclusively, I guess. Try to close these first, before reinstalling the drivers. And besides: After installing Win10 I had to install the Roland driver updates for QuadCapture. They are normally loaded from the Internet when plugging in the USB-cable...Beware of a domain-WSUS-server, these may prevent the driver from loading.
Best regards
Thanks for your reply. That makes sense and could be it, but how so I see which program uses what in my systray? :p Thanks in advance.
|
bickieb
Max Output Level: -90 dBFS
- Total Posts : 8
- Joined: 2017/07/12 20:31:41
- Status: offline
Re: External soundcard error
2017/07/13 18:45:42
(permalink)
Another thought; maybe I should make a print screen of my systray so you smart people can instantly see which I have to close? :P
|
michheld
Max Output Level: -90 dBFS
- Total Posts : 32
- Joined: 2014/12/20 15:29:05
- Status: offline
Re: External soundcard error
2017/07/13 20:20:42
(permalink)
|
bickieb
Max Output Level: -90 dBFS
- Total Posts : 8
- Joined: 2017/07/12 20:31:41
- Status: offline
Re: External soundcard error
2017/07/14 07:07:42
(permalink)
michheld
Oh, I just was lucky and tried everything in the systray, but maybe this helps for roland driver issues:
Regards
That's a thing I'm going to try as well! Just trail and error.. and hopefully... :D Thanks for your help! :)
|
bickieb
Max Output Level: -90 dBFS
- Total Posts : 8
- Joined: 2017/07/12 20:31:41
- Status: offline
Re: External soundcard error
2017/07/14 07:55:35
(permalink)
Solved. Thank you all for your replies.
I had to disable 'Windows audio' in the msconfig thingie. Thanks again!
|