Show Cue System

are you using the built in (automatic) MSC transmission functionality or are you using the MIDI_Raw feature to transmit MSC strings? and do you have any way of knowing if any strings are received whenever there should be an MSC string? i mean can you determine if nothing is being received by SCS or if it's being received but not interpreted?

I've tried both built in and MIDI raw.  The SCS program has a MIDI monitor that shows me it's getting strings.

Built in sends F0 7F 01 02 3X 00 31 F7 where the X is the cue number.  The SCS sees this but I cannot find a setting that will interpret this string.

Sending MIDI raw of F0 7F 01 02 10 01 3X F7 which is format that SCS documentation wants for a go on specific cue is received as F0 7F 01 02 10 3X F7.  The missing 01 before the cue number is the go command.

I've looked at MIDI raw using MIDI OX and OX sees the raw string as it was sent.

SCS  MIDI Show Control Messages shows format the program is expecting.

Tom

Tom

Where are you located.  It sounds like a setup thing.  Best advise is to call your local ETC support office for troubleshooting. 

while i don't know why there's a 01 missing, there are two things to note:

- you can check what MIDI strings Eos is sending in the Diagnostics tab (Displays > Browser > Utilities > Diagnostics)

- SCS seems by default to be listening to Command Format 10hex, that's Sound Devices, but Eos sends to 01hex. from the phrase "by default" in their online help i conclude that it can be changed somewhere. you will have to do that.

already with built in MSC there seem to be some parts of the midi command that go missing: you say SCS shows that it's receiving F0 7F 01 02 3X 00 31 F7, but i think Eos should be sending F0 7F 01 02 01 01 3X 00 31 F7...

I'm in Florida.  ETC is looking at problem.

I've been looking at MIDI sends at the PC using MIDI OX but will take a look at Diagnostics.

Today I tried using a macro to send MIDI raw F0 7F 01 02 10 01 31 F7

When I hit [macro] 1 [enter], MIDI OX displayed to strings

F0 7F 01 02 01 01 F7 (probably because MSC was enabled)

and F0 7F 01 02 10 31 F7 (missing the 01 GO command)

I've sent this info and show file on to ETC for help

The SCS software has a setting to make it respond to lighting control messages.

I use Show Cue (currently using V 11.2.3) all the time triggering audio cues from my ION (2.0.1 BETA 37) via MIDI show control to a Behringer BCF2000 to a PC via USB.

My set up is as follows:

In ION Show control settings

MSC transmit = enabled

MSC transmit channel = 1

ACN MIDI transmit ID = 1

In Show Cue/Editor/Production/Properties/Devices/Cue Control Devices

C1 Device Type = MIDI In

Physical Device = BDF2000

Active = Checked

Setting in Device:

MIDI in Port = BCF2000

Control Method = MIDI Show Control (MSC)

Device ID = 1 01H

MSC Command Format = 01H Lighting (General)

Go Button Macro # = 1 01H

This set-up works for me every time.

John

Hey, 

We have set up scs to trigger the Lx , in tech it had a few issues in triggering multiple cues withing a second of each other , so I just made follow cues. But now it seems not to listen to the signal Everytime, and inconsistent. It fired all cues  last night but not this morning. Does anyone know what the issue might be?

Any help appreciated. 

This all could be be possibly an scs problem but after opening  the diagnostics on the Ion while firing the cues on scs I can see that its registering on the desk as recieved but not firing. Possibly the string that's sent is wrong but scs produces and adjusts when you tell it what the cue number is. If I can forward any images to help along please just ask. 

Set up is SCS - focusrite - midi controller - Ion xe