Show Cue System

Help!

I been getting the folowing error:

Error -2147417848 Automation error
The object invoked has disconnect4ed from its clients
SCS10.6.1
ProcName = loadDispPanels
NLabel=1210, i=59, j=-1, n=55, p=0
CueFile = C:\Program Files\Sound Cue System9\Shgows\Cindy\Cinderella.scs

Continue with the program?

my choices are yes or no.
I click yes the program continues.

I upgraded to the latest version and I have a hard time getting SCS to start. I get the windows error Asking me if I want to send a report to Microsoft. So I went back to a previous verson and the above error happens every so often after I fire a cue.

I am running WinXP Pro SP3 with 1 Gig.

I have two generic USB audio devices which I use and use MSC with my ETC Express 48/96 to control SCS.

Any Ideas?

Seems odd. Try re-downloading and installing the latest version (10.6.3), and then when you start the program, hold down the Right Control key while you start SCS (it must be the Right Control key, not the Left Control key). This will force SCS to ignore any ASIO devices when it loads. Some ASIO drivers seem to clash with SCS. You can release the key when you see the splash screen.

If that gives the same result, start SCS again but this time hold down the Left Control key while you start the program. This will instruct SCS not to load the last-used cue file when it starts. If SCS loads OK, then open your cue file.

If you still have problems, please email me your cue file (Cinderella.scs).

Mike,

I will try that.

I think I found out what might be the problem.

I looked at the MIDI device and and the Microsoft device was selected not the hardware device. I changed it and the program became more stable.

I was able to update to the latest version and all seems OK.

If we don't get canceled because of the snow storm here in New Jersey I'll let you know how the performance goes and if I have any problems.

Thanks for the quick response!!

Hi Mike,
I also found this bug ages ago but then forgot about it!!

When entering a show on my lappy at home, I tended to forget to plug in my usb midi adaptor (although SCS does remind me)
As I'm editing/entering a show, I don't really need to have the usb/midi plugged in, so SCS defaults to 'blank' for midi out device.
I've found the hard way that if I have anything in the show that calls midi, then SCS becomes unstable, it will randomly crash and sometimes modify the cue file in the process.
I've developed the habit of saving after every edit and also plugging my USB/MIDI adaptor in each time, no more problems, hence I forgot about reporting it!!

I don't know is this still applies in 10.6.3.

Thanks, Boswell. Something that may be significant is that in 10.6.1 there were some changes that were meant to improve the response time on handling incoming MIDI control commands, but those changes unfortunately sometimes crashed the program, possibly in the manner reported by domiii at the start of this topic. So the original MIDI handling code was reinstated in 10.6.2. So by using 10.6.2 or later, that error should be avoided. That doesn't really explain how pluging in the MIDI device corrects the situation, but if you are using MIDI Control (MIDI In) then I strongly recommend using SCS 10.6.2 or later.

I'll try not plugging in my usb/midi adaptor whilst I do some editing and see what happens with 10.6.3

Should be able to let you know by Monday.