X1 Not unloading when I shut it down

Does anyone else have this problem? When I have the task manager up when shutting down X1,it keeps using 75 meg of ram, so i have to end process it, even though it appears to be shut down. I have also deleted any instances the Sonitus EQ because it has a memory leak of about 3 meg everytime i stop and start sonar$!@%.

Hi revsnd,

The only time this happens for me is when a MIDI driver hangs. Powering off the MIDI controller allows Sonar to close its process. Do you have anything like that in use on your system?

Unfortunately, Sonar does not behave like a good program should in this regard, and waits indefinitely for an event that will never happen when a driver or some plugins crash. I think any well behaved program should close when I perform an End Process or command line Kill command - alas, Sonar has not done this for many versions. I think I remember sending this in to Cakewalk tech support at some point and the response coming back from Cakewalk was that this was "as intended" behavior, but it sure would be great to have control over programs on my own darn computer.

D

revsnd


I'm using a Tascam DM24 as a control surface, but some projects it shuts down fine, others it hangs up...is that what you mean though?

Thanks again for the help so far!!!

I would guess not, but the only way to be sure is to try to end the Sonar process before and after powering off the DM24. If Sonar closes after powering the unit off, but never before, you can assume the DM24 driver is the culprit. If not, unfortunately you will have to keep searching my friend, as I am not sure what else it would be at the moment.

D

X1 almost never unloads itself from RAM for me when I quit.

I'm usually using about 3.5 gigs of RAM for X1 and maybe 500 megs to 1 gig for BitBridge -- sometimes BitBridge will not shut down at all, or Sonar will start to unload itself from RAM after I shut down and then crash when it has about 600 megs left to unload in RAM.

So in a nutshell, yes. I've had the same problem.

revsnd


It may be my new install of Komplete 7 thats doing it.... i'm testing it like mad now to see where the problem lies. ARGH!!

well the obvious thing that mentioned in 10001 other posts.. you ran the NI stuff standalone FIRST before it was used in sonar ? if not , try that first of all

could be any number of things not having the memory released.. or not being shut down.. but you should list what soundcard it is, mode etc.. then others can say yay / nay they have that problem

I have had this since version 6, many times  i have shut down sonar, to find either its still hogging my Soundcard, or just stopping my Pc from closing as its still running hidden in the background, and the same can be said if sonar crashes, but when i look in my task manager it does not show anything reguarding sonar, unless it is listed with some name i would not know off. 

Well, unlike 10Ten above, I NEVER experienced this problem in any previous version until X1.

This happened almost continuously for the first few days, now it doesn't happen at all.

Go figure.

I have no change in this behavior from 853 to X1a. The only time X1a or 853 (or 7, etc) ever hangs is when it crashes, not responding etc. I guess I am just lucky "again"? This is aknown issue, and as mentioned above, it is mainly the midi drivers or your sound card hanging on and Sonar waits for it. Same as beofre. Never shuts down is definitely "system related".
 

Hmmm... I have tested X1 on 3 separate systems, with various hardware (and so - various drivers), and never encountered the problem mentioned. This included two different processors (AMD/Intel), Windows XP, Windows 7 32bit and Windows 7 64 bit and various sound cards and control hardware (yes I did all that to determine what Hardware/OS/Software was the most advisable to run together with X1).

I think stratman70 is right here..

I had this happen all the time in 8.5.3 and it was either a BitBridge issue or my Alphatrack which caused the issue.

Are you using any Korg controllers (Nano, KontrolPad, etc...)? They are notorious for this. I get it all the time.

 
Yep Ol Pal...
The Korg USB MIDI driver is the culprit in many of these cases.
It's somewhat inert... in that it only happens when closing Sonar (doesn't affect working/saving)
But it's annoying... 

Got to jump in here again on one point,Not to Start major debating mind you,
where as it is related to some Conflicts on the system in relation to X1 and how X1/sonar works, and like i say i have such things since version 6, and something i have had to accept for what sonar is worth, and this is with 3 OSx Setups, various cards etc, and again i have to say, the problem Is alway said to be down/blamed on everything but sonar, even if only running sonar and no otherr vst etc on a clean install of windows updated with all drivers, no other daw behaves like this and no such problem with any other Driver/hardware aspects here, Only with sonar and this is probally the case in  guessing 75% the case for all these unresolved issues over the years, So their for it is with sonar more often than not, Less the odd newbie or clueless person that has not done all the basic checks and driver updates etc or just jumps on the bandwagon, rule these out and what is left.
Its always blamed on everything else But Sonar, I hate that!and more so than ever now X1 has Devastated me yet again 3 years running, and not even a single appolgy from cakewalk to us Users now X1 is riddled  , Fix a few minor bugs as usual, Think that will shut us up, Years down the line it is bound to blow up sooner or later, the way things have been going on, Nothing personnal to you guys/Gals here on the whole, maybe just a little! to those that think the rest of us dont have a clue and they 9/10 time agree its always the driver or some other fualt .
just my view, this is what is Sole destroying About trying to get justifiable Help and support via cakewalk, after we rule things out at our end ,do you think cakewalk will admit or believe Us, then its time for the ignorance as i have encountered, you end up get duplicate answers going back to basics, this is why i get negative with reporting issues becuase its the same on spiel, and hence speaking out a lot over these days, i know the question has to be asked, updating drivers etc, but i just never get here, why no one can admit its down to sonars Dodgy Programme code_Fact more often than not on all unsolved and ongoing issues, under the carpet time, every year  i report lots of these issues and then wait and wait for minor bug fixes then just as you think Cakewalk are persisting to solve things, Bug fix updates stop,
3 is the magic number I feel a de la Sonarul - remix coming on lol)  on a loosing battle.
 

Yes Subjacent - you hate X1 - we know, we know....

Message taken...

Now - the OP luckily has an answer, but it is not constructive to rant on any thread that is describing a problem and asking for help. You did not helped in any way to nail the problem, but only ventilated your anger. I do not think you are helping the OP very much.

I do not say you are not entitled to your opinion, but please lets be a little bit constructive and try not to shoot down every request for help.

If I were to take a guess, I would say I have the issue because I always use tons of RAM (large sample libraries as many instruments, never FROZE).  It seems it happens more frequently depending on how long since my last RE-BOOT. (I am one of those guys who leave the computer on most of the time).

But, no biggie for me just thought I would chime in as well.

Jim

Not directed at you jim, just a thought , i can never figure out, Say for Example all other daws and hardware work fine, and maybe you have used a controller for some time with no problems, and then things go wrong with sonar alone, how come these controllers or hardware devices are fine in the others daws, is that still not down to sonar either trying to be to upfront with technolgy, or just plain getting it wrong, not getting their Programme working, to a good enough Standard, whereas other DAWS seem to get away with it by comparission to sonar, It just confuses the hell out of me this question.

 
 
Let me give you a couple of examples:
 
The original UAD-1 PCI card
The UAD1 was developed before multi-core CPUs existed.
When Sonar became highly optimized for multi-core CPUs (one of the first DAW apps to do so), there were some major issues when using the UAD-1.
At that time, Cubase SX worked very well with the UAD-1 cards.  Guess why... (not highly optimized for multi-core CPUs)
On the surface, one could easily blame Sonar for this problem.
But knowing the underlying issues, the culprit was the driver for the UAD-1.
 
DICE-II chipset (for Firewire audio interfaces)
When it was first released, the DICE-II chipset had all kinds of problems with Sonar.
Dropouts, glitches, crashes, etc...
Note that MOTU and RME Firewire units have always worked extremely well in Sonar (even when running heavy loads at ultra low latency settings).  Clearly there wasn't a blanket problem with Sonar.
As with the UAD-1 example, DICE-II users had more success using apps other than Sonar.
But... like the above example, that doesn't mean that Sonar is the culprit.  Rather, Sonar exposed a problem with the DICE-II implementation.  Note that the drivers for DICE-II have undergone many revisions... and the problems have been ironed out.
Again, on the surface, it would seem like Sonar was the culprit... when in fact the problem was DICE-II and its drivers.
 
As with the above examples... (IMO) the impetus is on Korg to fix their USB MIDI driver.
I've had the "Hang when closing Sonar" issue with numerous Korg units... across many machines.
Note that Yamaha, Roland, Akai, etc... all work just fine.
 
BTW, Just wanted to mention that I know there are legitimate bugs/issues in Sonar (and X1).
I too want to see those addressed.