Show Cue System

I have been experimenting with using the SCS interface with the 01v96 to achieve direction with my soundcues, but i have been running into some walls with getting the two to talk. I was wondering if anyone on here had successfully joined the two in order to either change scenes with each cue or have had another way of controlling which outputs are being used with certain cues.

I have downoaded the drivers needed.
I am running on windows 10.
Currently using the USB/Host port.
I receive MIDI messages from the 01v96 when I configure it to MMC, but I don't believe that is what I am looking for.

Thanks for any info!

Andrew

Hi. I use an O1v96 V2 with SCS and I send messages to invoke library changes, channel ON/OFF, direct send ON/OFF and channel volume changes. It works well but you have to work at it to set it up!!

On the O1v96 :
- under DIO/Setup set the receive and transmit ports you will use - I receive via the midi port and send via USB port 1
- under Midi set the channel number (I use ch 1) and also select to receive and transmit the messages you are interested in - Prg. Change (for scene selection), Control Change (for a whole list of programmable events like channel on/off) and Parameter Change (for more "advanced" things like volume changes).
- normally switch Echo off - this would otherwise resend received messages back out which can create a loop . . . .
Having done this then the desk is ready. The Control Change messages are programmed on the O1v96 on another page under midi - the defaults might be enough for you but you can change them to what you want. In the manual for the desk (at the back) there is a full listing of all these midi messages - hard reading but it is there - there is nothing you can't drive by midi.

In SCS :
- define a control send midi device (say O1v96) and assign it to the receive port you have defined on the desk
- create cues or sub-cues of type Control Send and define the message you want - remember to set the midi channel to that set on the desk
- I find it useful to use the new (and wonderful - thanks Mike) callable cues for desk commands - then they are reusable and also if you need to make changes you make them only once. One day I might suggest a development of call cues so that you can pass a parameter (like a program number) into the called cue - would be very useful.

This works just fine. For me though, especially since I sometimes want a dialogue with the desk (eg get me the current volume level of channel 2), I insert another piece of software between SCS and the desk. I use Bome Midi Translator. With this I use a virtual midi connection between SCS and Bome. Then in Bome you can program events. For example when it receives Prg Change 3 on channel 1 from SCS then send a message to the desk to request current channel volume. The desk sends a midi message to Bome which logs the current volume. In that way I can program a second event to raise the volume by 100 units etc. You can't currently do this sort of thing in SCS - and it is a bit specialised!!

Hope that helps - any questions then just ask

Cheers from a wet and windswept France

Richard

Hi,

Set the 01v96 as explained by rborsey.

Then, I SCS I do this:
To load one Scene:
Add a Control Send Cue
Select Control Send Device: MIDI
Select the Message Type: MIDI Program Change (1-128)
Select Channel: 1
Set Program #: “Scene Number”

To change a control (ie. Set channel 1 on):
Add a Control Send Cue
Select Control Send Device: MIDI
Select the Message Type: MIDI Control Change
Select Channel: 1
Set Control #: 64
Set Value: 127

See Owner’s Manual
Appendix C: MIDI
Scene Memory to Program Change Table
Initial Parameter to Control Change Table

Regards,
Lluís