Hi all
 
Just new to this forum and ready to learn the magic of X3. Have been working with X3 a few weeks now, and made some improvements.
 
Since a few days however I encounter an issue that after opening X3 once, I cannot open it again after closing, or after I have put my laptop to hybernate. I need to restart and then it is working ok, but once only. I checked the task manager and there is no program remnant left to close.
 
My laptop is an HP EliteBook with an Intel i7 2.60 GHz, with 4Gb RAM, 64bit
 
What could be the issue?
 
Thanks in advance for your advice

Ad
 
 

that usually means it hasn't exited cleanly - after closing sonar, run task manager - can you still see sonar in the list of processes? if so, sonar hasn't released the audio driver (for whatever reason) - -what soundcard/driver are you using?

lawp
that usually means it hasn't exited cleanly - after closing sonar, run task manager - can you still see sonar in the list of processes? if so, sonar hasn't released the audio driver (for whatever reason) - -what soundcard/driver are you using?

Thanks for responding.
In the task-manager is nothing left of Sonar's applications, so that can't be the issue I believe.
 
Standalone (where the problems appears) I'm using the ASIO4ALL driver.
Connected to my gear I use a Roland Octa-Capture, but I haven't checked if the problem appears then also.

that's the process list (not application list) in task manager?

This used to happen to people frequently with some M-Audio interfaces (wouldn't let go of the driver as lawp pointed out). I'm assuming it probably has something to do with ASIO4All which is not recommended for Sonar (or pretty much any pro level audio). Honestly you should just try to use the interface if at all possible or snag a small simple interface when you go portable. I'm sure you could pick something up for under $100 that is good enough to monitor with and handle audio while fiddling around with Sonar and small enough to not be a pain to lug around.
 
Otherwise if that is the only problem you are having with ASIO4All it's a pretty darned minor one. I'd just try not to close Sonar or not worry about having to reboot.
 
As far as hibernate... don't let your computer do that. In fact turn off all power saving features and "sleep" type functions. That stuff is notorious for screwing up DAWs. Even manually putting it in hibernate is no good because it kicks the audio driver(s) offline. Just manage the system manually.
 
For now make sure you have the latest patch for Sonar (X3e) and the most recent version of ASIO4all (or google for problems and try to use the version with the least trouble reports).
 
And if your laptop is one that came preinstalled with Windows and a bunch of other gack remove as much bloatware as you can or do a fresh install of Windows if possible.
 
Cheers.

are you using any midi drivers from m audio ? (keyboard)
sometimes these drivers will not release and thus holds the program hostage until the driver decides to let go.

Thanks for the info
 
No I'm not using any M-Audio drivers.
Sounds probably like an Asio4All issue. Will try to find an alternative or live with it..

Yup kill ASIO4All and don't look back.

ASIO4ALL works for some folks most of the time, some of the time for most folks, and not at all for some.
 
I have had flaky issues with it on my system in the past, and nuked it quite a long while back and have never once considered using it ever again.
 
You can get an inexpensive but decent new interface for around $135 from Guitar Center, and there are some cheaper options - really basic new ones or used but decent ones from around $99 or so.
 
Bob Bone
 

SOLVED!
 
My windows7 Task Manager does not list the processes anymore, as previous versions did, but you can still get the processes by:
open a command prompt
(run) tasklist
In there I saw that after closing Sonar (X3 Production), sonarpdr.exe is still listed as active process
 
Can be killed by running the following at the command prompt:
tskill sonarpdr
 
After that, I could start Sonar again, working as normal
 
So at least for this issue, Asio4All might cause this issue, but it can be overcome, and Sonar works now normally
 
Thanks for all your suggestions