Eight exclamation marks before NC starts!

[jss]

When I start NC I now I get the O/S triangular shaped warning dialogbox with exclamation mark in it, - the text just says "Ok" (and nothing else) and clicking gets me the same again. After eight clicks, NC starts as if nothing had happened!
XP sp3
Anyone any idea what's happened here? thanks

[Reinhold H.]

Is there a special scenario when this behaviour comes up?

In version 3 all pop up messages receive an exclamation or question mark but only messages in theones in the playlist area are still from the old shape (triangle plus !). This sounds to me that the issue is caused by an incomplete or corrupted playlist file. Could you please double-check the playlist settings?

Further investigations I recommend to perform those off-line and when all is investigated we will post the findings here. JSS, please send us an email to support@notation.com. A ticket will be opened and we wil determine next steps. Thx.

Reinhold

[jss]

Originally Posted by jss

When I start NC I now I get the O/S triangular shaped warning dialogbox with exclamation mark in it, - the text just says "Ok" (and nothing else) and clicking gets me the same again. After eight clicks, NC starts as if nothing had happened!
XP sp3
Anyone any idea what's happened here? thanks

Hello and thx for the reply
This is bizarre - because I now not cannot reproduce the problem! When it was happening, I could reproduce it - in fact did so a number of times. Looks more like maybe a system/interaction problem. NC was clearly accepting the "ok" to several items - before it started properly. The number of clicks was a constant at 8 times. I will report via support email should it recur.
thank you again
jss

[dj]

Hi, jss, Reinhold:

I'm trying to think back and recall similar instances and I think I recall seeing the exclamation point warning when Composer had been terminated abnormally and was still running in the background.

The cure was to use the Task Manager to get rid of the stalled instance of Composer.

So, jss may have had such an instance a couple of times.

David

[jss]

Hi All,
I think you have id'd the problem David. Thanks.
I remember now - NC took a long time to start up (due to machine load on other software, sound libs etc). I think I may have clicked again (in error) to start it again thinking I had not started it already.

Maybe worth asking whether >1 copy running has any purpose and if not, arrange for it to check for such a situation?
regards
-jss

[Sherry C]

Hi guys,

Composer 3 does check for multiple instances and "kills" any lingering instances from a previous opening before opening up a new instance. That said, there may be "special" circumstances that trip up that safeguard.

If you're able to re-create the situation, please do let us know.

ttfn,
Sherry