Hello, I'm a new user, currently playing with the demo to find out if SCS is the product for me... Having downloaded the demo, I've been trying to set up a sequence of "midi control send" cues to trigger cues on my lighting desk. The sequence is made up of "whole" cues, rather than being a set of subcues. Each cue auto runs at various timings after the start of cue 1.
At present, the sequence runs fine on my laptop, but only the first "midi control send" cue actually triggers a lighting cue. I have to restart SCS before another cue runs.
Likewise, if I open SCS and go into editor, select a midi cue, and use the "Test Control Send" button, the first time I do this a lighting cue will run fine, but no further cues will run, either using the test button, or by running the cue sequence... again, if I restart SCS, I can again run ONE initial SCS cue, but only one!
Is this a built-in limitation of the demo software? If not, can anyone suggst a solution?
Thanks,
Ben
demo - midi control send problem
-
- Site Admin
- Posts: 3632
- Joined: Sun Jul 24, 2005 8:58 am
- Location: Brisbane, Queensland, Australia. TZ:GMT+10
- Contact:
Re: demo - midi control send problem
That's odd. When you say that only the first lighting cue will run but that no further cues run, do you mean that no further cues of any type run? For example, after activating a lighting cue will an audio cue run?
What type of lighting board are you using? And what MIDI control types are you using (eg Note On)?
What type of lighting board are you using? And what MIDI control types are you using (eg Note On)?
Re: demo - midi control send problem
Hi Mike, Thanks for your reply...
In answer to your questions, I'm just using Midi Show Control cues. I'm sending them to a Strand GSX, via a "Mistar Midilink" USB-Midi 1-In/1-Out cable.
I've done some further experiments, and I'm still confused.
Occasionally, I can open an SCS session and the whole set-up works perfectly, and the SCS control-send cues trigger lighting cues on the GSX, as does the 'test' buttons on the control-send editor page.
Usually, I open SCS and only the first instance of a control-send cue will trigger a cue on the lighting desk (either from running the SCS cues, or from pressing the 'test' button on the editor page. After this first instance, however much I press 'test' or run the SCS cue stack, no further cues are triggered on the GSX. The SCS cues will run on-screen ok, and don't show any "failed to send" error. If I add sound cues into my SCS cue stack, these seem to run fine.
Sometimes, I open SCS and can control send cues/test buttons will never trigger the GSX cues.
I'm not changing any settings (in SCS or elsewhere) between SCS sessions. Sometimes it works, sometimes it doesn't. It's frustrating because when it works, it seems to work smoothly, but then I save my SCS showfile, close and restart SCS (and/or the computer), and it's not working again.
On some occassions, if I go into "Permanent Options", deselect the midi device (so the drop-down menu shows a blank) and press 'apply', and then reselect the midi device, and press 'apply', I'll be up and running again. But not always! Aaargh!
Any advice?
Ben
In answer to your questions, I'm just using Midi Show Control cues. I'm sending them to a Strand GSX, via a "Mistar Midilink" USB-Midi 1-In/1-Out cable.
I've done some further experiments, and I'm still confused.
Occasionally, I can open an SCS session and the whole set-up works perfectly, and the SCS control-send cues trigger lighting cues on the GSX, as does the 'test' buttons on the control-send editor page.
Usually, I open SCS and only the first instance of a control-send cue will trigger a cue on the lighting desk (either from running the SCS cues, or from pressing the 'test' button on the editor page. After this first instance, however much I press 'test' or run the SCS cue stack, no further cues are triggered on the GSX. The SCS cues will run on-screen ok, and don't show any "failed to send" error. If I add sound cues into my SCS cue stack, these seem to run fine.
Sometimes, I open SCS and can control send cues/test buttons will never trigger the GSX cues.
I'm not changing any settings (in SCS or elsewhere) between SCS sessions. Sometimes it works, sometimes it doesn't. It's frustrating because when it works, it seems to work smoothly, but then I save my SCS showfile, close and restart SCS (and/or the computer), and it's not working again.
On some occassions, if I go into "Permanent Options", deselect the midi device (so the drop-down menu shows a blank) and press 'apply', and then reselect the midi device, and press 'apply', I'll be up and running again. But not always! Aaargh!
Any advice?
Ben
-
- Site Admin
- Posts: 3632
- Joined: Sun Jul 24, 2005 8:58 am
- Location: Brisbane, Queensland, Australia. TZ:GMT+10
- Contact:
Re: demo - midi control send problem
Ben,
I've emailed you details of a test I'd like you to run.
I've emailed you details of a test I'd like you to run.