I love this software, Problems with Cue's
Posted: Fri Oct 20, 2006 12:57 pm
My Tech director and I just bought SCS Pro, and I love it. I took me 3 hours from zero to having all the cues (30 or so) input and setup for out production of Arcadia. The ability to automate cross fades and which speaker each cue plays is really nice.
I have been having a stability problem that seems to occur while I am editing cues. After editing the cue list and saving it other cues in the list get corrupted and will generate an error message when the cue is run. This error results in SCS crashing. This happens randomly and there doesn’t seem to be a pattern at all to the corruption. Deleting the offending cue(s) and recreating it solves the problem, sometimes its 2-3 cues and they are usually all in the same order. I don’t have the text of the error (I know not too helpful!) but it is long and seems to represent the database entry for that particular cue. (It has a string of what seems to cue parameters.) I will try to do a screen cap the next time it blows up.
Once I fix the offending cues, the program is quite stable, so the only real inconvenience is that I have to go through the entire cue list prior to a performance or rehearsal if I have made any changes. This is a little tiresome since the dynamic nature of the program and the ability to edit on the fly is really one of the more powerful aspects of the system.
Some details on my setup....
Computer is a tower PC running a Pentium 4 3.0Ghz processor and 1GB of ram. This machine is dedicated to running sound Cues and interfacing with my Mackie TT24 (The most badass digital console for under US $10K)
I am running SCS 9.1.5a (only version ever installed)
Any insight?
I have been having a stability problem that seems to occur while I am editing cues. After editing the cue list and saving it other cues in the list get corrupted and will generate an error message when the cue is run. This error results in SCS crashing. This happens randomly and there doesn’t seem to be a pattern at all to the corruption. Deleting the offending cue(s) and recreating it solves the problem, sometimes its 2-3 cues and they are usually all in the same order. I don’t have the text of the error (I know not too helpful!) but it is long and seems to represent the database entry for that particular cue. (It has a string of what seems to cue parameters.) I will try to do a screen cap the next time it blows up.
Once I fix the offending cues, the program is quite stable, so the only real inconvenience is that I have to go through the entire cue list prior to a performance or rehearsal if I have made any changes. This is a little tiresome since the dynamic nature of the program and the ability to edit on the fly is really one of the more powerful aspects of the system.
Some details on my setup....
Computer is a tower PC running a Pentium 4 3.0Ghz processor and 1GB of ram. This machine is dedicated to running sound Cues and interfacing with my Mackie TT24 (The most badass digital console for under US $10K)
I am running SCS 9.1.5a (only version ever installed)
Any insight?