Page 1 of 1

[Resolved] Midi show control problem

Posted: Wed Dec 23, 2015 2:20 am
by saitekx830
Hi
I'm trying to control a Zero88 Jester lighting desk(Latest version of firmware installed) using Midi Show control but I'm having no luck.
If we change the output to Midi note I can control the lighting desk faders as it should.
As I have 2 USB to Midi adaptors I have even tried connecting 2 computers together with SCS installed on both.
One setup to send midi and the other to receive with the test midi signal window open and I'm getting nothing when I send the show control command, If I send Midi note controls they appear in the test window.
Have attached 2 screen shots of the production properties and the cue.

With the control cue I have tried it with and without a lighting Q number

Can anyone possibly point me in the right direction.

Re: Midi show control problem

Posted: Thu Dec 24, 2015 5:54 pm
by Mike Daniell
I've run some tests here and MSC is being sent OK. Could you email me a diagnostic file? You can create this file by selecting 'Create Diagnostic File' from the drop-down menu displayed when you click the Help button in the main window. The file will be saved in a folder named "SCS Diagnostics" under "Documents" or "My Documents".

Re: Midi show control problem

Posted: Mon Jan 04, 2016 2:37 pm
by Mike Daniell
Thanks for the diagnostic file. I can't see anything wrong in your cues or in SCS, provided you have the MSC Device Id set correctly. I've extracted your cue file from the diagnostic file and run the MSC cue (Q12) sending the output via a 'loopMIDI' port to MIDI-OX. The input window of MIDI-OX showed:

Code: Select all

TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT               
 00018E51   3  --     F0  Buffer:     7 Bytes   System Exclusive      
 SYSX: F0 7F 01 02 01 01 F7
which is exactly correct for the MSC command supplied in the cue.

Re: Midi show control problem

Posted: Wed Jan 06, 2016 10:09 am
by Mike Daniell
Forum user saitekx830 has advised me:
I have done some more investigations and have found that the problem was caused by my USB to Midi adaptor.

The cheap USB to Midi adaptors that I was using are not able to handle the longer data strings of the System Exclusive commands that MSC uses.

I got hold of a more expensive adaptor and everything worked straight away.