[ddots-l] Re: Strange shutdown behavior in Sonar 5

Gord,    I tried shutting down my MIDI interface before exiting Sonar
and still had the same result.  Perhaps I should have waited longer
between turning off the interface and shutting down Sonar.  Is there a
length of time you wait between these two events?  What else could be
causing this?
K.

-----Original Message-----
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Gordon Kent
Sent: Sunday, October 01, 2006 2:51 PM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: Strange shutdown behavior in Sonar 5


Usually that happens because your midi driver is not letting go.  Turn
off your midi interface and Sonar should shut down.
Gord

----- Original Message ----- 
From: Kevin L. Gibbs <mailto:kevjazz@xxxxxxx>  
To: ddots-l@xxxxxxxxxxxxx 
Sent: Sunday, October 01, 2006 1:21 PM
Subject: [ddots-l] Re: Strange shutdown behavior in Sonar 5

Yes, I've seen that occasionally as well.
K.

-----Original Message-----
From: ddots-l-bounce@xxxxxxxxxxxxx [mailto:ddots-l-bounce@xxxxxxxxxxxxx]
On Behalf Of Phil Muir
Sent: Sunday, October 01, 2006 9:06 AM
To: ddots-l@xxxxxxxxxxxxx
Subject: [ddots-l] Re: Strange shutdown behavior in Sonar 5


Yup, think I have scene that one.  Also scene Sonar refuse to close on
occasion.  When it does that, I can't even kill Sonar off in the task
manager.
 

----- Original Message ----- 
From: Kevin L.  <mailto:kevjazz@xxxxxxx> Gibbs 
To: ddots-l@xxxxxxxxxxxxx 
Sent: Sunday, October 01, 2006 8:31 AM
Subject: [ddots-l] Strange shutdown behavior in Sonar 5


Has anyone noticed the following strange shutdown behavior in Sonar 5?
If I've been working with Sonar 5 PE all day, when I shut it down for
the night, I'll get one of these messages saying that if I choose to end
the program now I will lose any unsaved data.  A progress bar goes
across the screen and, when it is finished I can end the program.  I
know I'm not describing this perfectly.  It's a progress bar I've seen
in other applications which I presume are malfunctioning which causes
that to display.  It's no big deal, just weird.  

Thanks, 
Kevin

Other related posts: