[Fix 11.8.2] Division by zero error

[Trogwold]

Hi,

Using SCS 11.8.1.2.

4 screens in total, 3 for display and one for control.

We've been battling this all day with just simple test image cues. The images are put on what SCS numbers as screens 2, 3 & 4. Everything will seem to be ok but then, out of nowhere, we get a Division By Zero error when opening the cue file. We've learnt that we can get round it by changing the file path to the images in Windows, after which SCS will say that it can't find them but it will then open the file. The trick is then to change any cues sent to screen 2 to (a non-existent) screen 5. Save, reset the image file path back to normal, and the cue file is then usable again....until some indeterminate time later when it informs us that, actually, there is no screen 5. At this point we have to change 5 back to 2, re-save, and all will be well for another while...until the dreaded Divide By Zero error returns and round we go again.

The video drivers page shows some random screens and splits which don't relate in the slightest to anything that we actually have connected. I can't see any way to clear these.

I know a log file will help but I'm away from the theatre at the moment. I can get one tomorrow.

Would a factory reset help do you think? Would the audio cues (which are now complete for this show) be harmed in any way?

Thanks in advance,
Rob

[Mike Daniell]

A factory reset probably won't help, but it won't affect your cue file either. Basically a factory reset clears everything in the 'preferences' file (which is where option settings are saved), apart from the list of recent files and favorite files. What will be helpful is the log from a run in which the 'division by zero' error occurred.

[Trogwold]

Thanks Mike. I'll get one over to you as soon as I can.

[Mike Daniell]

Rob, another user has reported the same bug and has provided me with a log file. The bug occurs under some conditions if you minimize the editor window and subsequently double-click on a cue in the main window. I've emailed you a new version of SCS that fixes this error.

[blt]

Mike,

Rob (Trogwold) is one of our system users and has asked me to send the log file for the problem - attached in case further confirmation of solution is needed.

When using a new set up of screens/projectors for a new production, SCS seems to remember the previous set up and retains spurious screens (in this case, I think it is based on prior use of a Matrox TripleHead2Go). Is there some way to clear the (non-control) screens and allow the system to then identify the configuration as connected for the present show.

I THINK I have overcome the problem by disconnecting all display screens, rebooting PC, opening a new cue file, closing down again, reconnecting and switching on screens, restarting PC and again opening a blank cue file before going back to the show file. Tested several times without it failing but still holding breath.

Thanks for sending the new version to Rob. I will see how it goes and hope to be able to breathe again soon.

[Mike Daniell]

When using a new set up of screens/projectors for a new production, SCS seems to remember the previous set up and retains spurious screens (in this case, I think it is based on prior use of a Matrox TripleHead2Go). Is there some way to clear the (non-control) screens and allow the system to then identify the configuration as connected for the present show.

Changes in 11.8.1 included: "Saved window positions, sizes and splitter bar settings are now saved separately for different display configurations, eg separately for having one screen or two screens connected. This test also takes into consideration display scaling and sizes." If you have some 'spurious' screen setting restored, please email me a log from that run and explain what's wrong. If necessary, you can always use the 'Special Start' facility and select 'Clear saved window positions and sizes'. See Problem starting SCS in the Help file.

[Trogwold]

Hi Mike,

After Keith's judicious fiddling (above) everything worked last night with just a couple of test image cues.

This morning, trying to open the same cue file, the same error was back. I cleared the window positions and tried opening the cue file again but with the same result, and then again after installing the 'as' version you sent me; still the same result.

I'll email the log file over.

Rob