Catch 22 on start up if Cue Control declared but not attached

[PhilVale]

Not sure if this is a bug but I can't find a way out of it.

There seems to be a catch 22 if:

1) Cue Control device is declared and used
2) SCS is started without the Cue Control device attached

You can go to the Device mapping at start up - but then can't delete the Control Cue device because it's used by a cue. But you can't go and delete or deactivate the cue because you can't get off the Device mapping page becuasde it wants the Cue Control device to be present. Try saving the device map and it then complaibns there's no cue control device.

I can't see a way to effectively disable the cue control device abnd move forward so have to close SCS from the Task Manager which I never like doing because nover know what else might get not tidied up.

[dee99]

Thanks Phil we will look into it.

[PhilVale]

Thanks Dee,

It may just be the way it is but let me know if you need abnytghibng further.

Phil.

[Mike Daniell]

I sometimes have a similar situation and the solution is to assign a dummy device to the affected devices. When you apply the changes you should be asked if you want to save the changes as a new device map, so select 'Save as new device map' and then enter the name for the new device map. For example, I use MIDI Control Sends and MIDI Cue Control using my A&H Qu-16, but the Qu-16 is not always with me at rehearsals, so I have two device maps that I've named 'Production' and 'No Qu-16'. From the main window, you can switch device maps if required by selecting the required device map via the 'Device Maps' toolbar button.

If this doesn't help, then please email us the SCS log file from a run in which your 'Catch 22' happens. Log files are created and saved in a folder named "SCS Logs" under "Documents", and the name of each file includes a time-stamp indicating when the log started. Email the file to support@showcuesystems.com.