One Week Later !!!!!!! SOLVED!!!!!!!!

when I adjust the asio buffer size, and then hit the apply button, it comes up with a box and it says, device currently used by another application

ba_midi

jwh


Hi Guys,
I've tried just about everything including the registry cleaner, if only there was a way to find out (device currently used by another application) what that device was switch it off and get back on track!!!! is this looking at it too simply ?
And NoKey give me a break here, I'm trying to get my system to work, if you need to know anything start a new thread, Idon't say this in a nasty way but this is now really frustrating!!!!!

John

John,
I think you mentioned you have a V-20 there as well as the UA card?   I'm not sure, but maybe it has something to do with that?
 
Hi Billy,
I bought the V-20 thinking this would solve my problem of this error,but the thing is still there,so I am now using the V-20, all this happened a week ago, when I downloaded the upgrade for Dim Pro, and I even deleted Dim Pro to see if that got rid of the prolem,but again no,have you ever heard of this before ?
 
John 

ba_midi

Hi Billy, I bought the V-20 thinking this would solve my problem of this error,but the thing is still there,so I am now using the V-20, all this happened a week ago, when I downloaded the upgrade for Dim Pro, and I even deleted Dim Pro to see if that got rid of the prolem,but again no,have you ever heard of this before ? John

 
John,
I have seen others have this problem, yes.  And - more often than not, it was a 'driver sharing' problem (which is usually solved by checking the "Share Drivers" option in Sonar).
 
However, computers can be finicky as we all know ;)   And, with the move to 64bit still in its infancy, I think there are a lot of 'extra' issues -- especially with the drivers for hardware, and of course software.
 
So it's possible you've hit an extraordinary situation (one we may all learn from if/when solved).
 
An example of this is a recent thread where someone went through a lot of the "usual" recommendations for getting rid of clicks/pops/dropouts -- none of which worked.  I suggested (based on someone else's experience) adjusting their power settings to maximum -- and that solved the problem.
 
So I think continuing to work this through, as you are trying to do, is helpful to everyone along with you.
 
The message you've gotten is probably true -- in the sense it's telling you there is some conflict with another device; so tracking that down may take some more deductive measures.
For example ... if you disconnect any one thing that may be a conflicting device, what is the result?   That's what I mean be being deductive.  Trying one thing at a time, seeing the result.
 
Also - making sure you have the latest "known to work with your setup/OS" drivers has to be checked.  Though I suspect you've done that.
 
When I don't have a good answer, I try to be suggestive.  IOW, get the user to think, and be deductive in approach.  Something may shake out.
 
And, keeping those of us watching this thread informed can help.  Any one thing you say MAY shake out another idea toward solution.
 
 

ba_midi

Billy, Would it make any sense to delete my recent work on Sonar (I obviously have the material on my external drive) un-install Sonar and then re-install it ? John

 
Normally I don't recommend the uninstall/reinstall approach until at least enough other approaches have been explored.
 
But, sometimes it really is the only option left.   This MAY be the case in your situation.
 
I would do a full backup first, of course, at least of your OS drive (normally drive C:, where Sonar and the OS is installed) as a precaution.
 
Then I would do a full uninstall of Sonar.  Reboot.  Then reinstall.  And reboot once after the initial install.
 
You may also wish to do a "custom" install (it's an option during the install procedure) rather than the "normal/basic".  If you select custom, most of the options are already checked like a normal install, but I would then go through the list to make sure the ones you want ARE checked.   Some will be unchecked and generally can be left unchecked (some of the older plugins, for example, which aren't really useful and most wont' work on 64bit anyway).
 
But you can always do a normal install just to get going too.
 
IF you discover you have the same problem after all that - then it at least deduces that it's not Sonar that has the problem, but rather it's probably one of the device drivers (audio is highly suspect) or a Windows driver (might also be audio).
 
 

NoKey

jwh


And NoKey give me a break here, I'm trying to get my system to work, if you need to know anything start a new thread, Idon't say this in a nasty way but this is now really frustrating!!!!!

jwh,

I questioned the statement in concern for your own self-interest that the problem be solved, not because I wanted to know anything as you suppose, or distract interest from your issue.

I believe that if something is contributed that is not based on fact, it can lead astray. I don't happen to have the problem that you do have, and I hope it gets resolved.

Bitflipper, I don't find this statement to be correct...I have various applications use the same ASIO driver simultaneously. Do you have any documentation that supports what you state?