Jump to content


Photo

Midi show control from scs to orb


  • Please log in to reply
14 replies to this topic

#1 Paul Finch

Paul Finch
  • Members
  • 5 posts
  • Gender:Male

Posted 26 May 2017 - 10:46 PM

Hi

I am trying to get SCS (show cue system) to trigger go on on the orb using midi shoe control. Has anyone tried this ?

#2 Edward

Edward
  • Trained on FLX
  • 115 posts
  • Gender:Male
  • Location:Pontypridd
  • Interests:Lighting and Drumming

Posted 26 May 2017 - 10:57 PM

No I haven't. My first question would be what MIDI interface are you using? Does it have any sort of LED indicator on it to show it is receiving MIDI from your PC.

Edward

#3 Paul Finch

Paul Finch
  • Members
  • 5 posts
  • Gender:Male

Posted 27 May 2017 - 07:44 AM

Hi there. I have tried a emu USB to midi lead and that has a led on it that flashes when receiving midi. I have also tried a scarlet audio interface with a midi output and USB in from laptop
I am wondering if I have a setting wrong on the orb as it says at the bottom of the cue stack midi not detected

#4 Edward

Edward
  • Trained on FLX
  • 115 posts
  • Gender:Male
  • Location:Pontypridd
  • Interests:Lighting and Drumming

Posted 27 May 2017 - 10:03 AM

Hi Paul,

 

If all is good with your MIDI interface and the LED is lighting when a trigger is sent, ensre on the ORB in SETUP -> Inputs & Outputs -> MSC Enable -> Set device ID.

 

This will then control Playback 0 in 7.9.2.

 

Just be wary if you are using a cheap MIDI interface...

http://www.arvydas.c...ay-be-required/

 

Edward



#5 SJWicks

SJWicks
  • Members
  • 5 posts

Posted 27 May 2017 - 01:46 PM

To support Paul Finch's request,  if Midi Show Control is enabled in SETUP -> Inputs & Outputs -> MSC Enable and the Device ID is set, why would the cues stack screen still indicate that "midi not detected" (at the bottom of the screen) ?



#6 Edward

Edward
  • Trained on FLX
  • 115 posts
  • Gender:Male
  • Location:Pontypridd
  • Interests:Lighting and Drumming

Posted 27 May 2017 - 02:13 PM

This would mean that there was no MIDI signal present coming from the interface to the MIDI In port on the console.

Edward

#7 SJWicks

SJWicks
  • Members
  • 5 posts

Posted 27 May 2017 - 07:33 PM

OK.  Paul and I were trying to get MSC to trigger the orb last night with no success.  This was the setup; laptop 1 sending MSC (lighting Go) via midi to laptop 2 using Focusrite Scarlett interface.

 

Laptop 2 - Showcue systems software  "listening" for MSC lighting "go" which will trigger a sample sound cue.  When tested the music cue triggered as expected, thus demonstrating that both midi signal and MSC commands were being transmitted and received.

 

Connecting midi from the Scarlet interface to the orb (using Midi in socket), the orb did not trigger a lighting cue in playback 0.  We noticed that "midi not detected" was visible on the screen.  Using the Midi thru midi port, we connected laptop 2 to the orb.  We then send the MSC command from laptop 1 to the Orb .. the orb did not trigger but Laptop 2 DID trigger as it did the first time.

 

This test demonstrated that midi was still being transmitted and received, however the Orb screen still showed that "midi not detected".

 

So ... is the midi In port always enabled?  and if so ... our test might indicate that there's a fault with the midi in connector and the orb board.

 

would you make the same assessment?



#8 Edward

Edward
  • Trained on FLX
  • 115 posts
  • Gender:Male
  • Location:Pontypridd
  • Interests:Lighting and Drumming

Posted 28 May 2017 - 05:27 PM

Hmmm interesting.

Do the device IDs match on the Orb and the Laptop 1 MSC trigger?

 

Edward



#9 SJWicks

SJWicks
  • Members
  • 5 posts

Posted 28 May 2017 - 06:53 PM

Yes they did. Both set to device ID 1 and the second laptop also set to ID 1.



#10 Edward

Edward
  • Trained on FLX
  • 115 posts
  • Gender:Male
  • Location:Pontypridd
  • Interests:Lighting and Drumming

Posted 30 May 2017 - 11:20 PM

Hmm that is strange that the MSC signal is passing straight through the console without the console detecting it.
We'll have to wait to see what Jon can suggest, I'm a bit flummoxed by this one!

Edward

#11 SJWicks

SJWicks
  • Members
  • 5 posts

Posted 31 May 2017 - 08:04 AM

We  are equally "at a loss".  However we are able to borrow another orb and will do another series of tests on that desk.  If we can get the second orb desk to read the Midi, we can then "compare and contrast". 



#12 Edward

Edward
  • Trained on FLX
  • 115 posts
  • Gender:Male
  • Location:Pontypridd
  • Interests:Lighting and Drumming

Posted 31 May 2017 - 09:36 AM

Yes that will be a good next step in the trouble shooting, be interested to hear the results!

 

Edward



#13 Jon Hole

Jon Hole

    Product Manager

  • Zero 88 Admin
  • 1,762 posts
  • Gender:Male
  • Location:Cwmbran, Wales

Posted 01 June 2017 - 03:20 PM

Hi Paul and SJWicks,

 

We've found an issue in the latest software version that affects some hardware variants which causes MIDI to (try and) be read at the wrong baud rate. We're getting it fixed asap and will get a beta out tomorrow. If you would like to be part of the Beta Test group to access this, drop me an email (jonhole@eaton.com) and I'll add you to the group.

 

Jon


Jon Hole
Product Manager, Entertainment Lighting Controls


#14 SJWicks

SJWicks
  • Members
  • 5 posts

Posted 01 June 2017 - 10:26 PM

Thanks Jon.  That would explain a great deal. I believe Paul is hoping to test the beta version tomorrow.

 

Simon



#15 Paul Finch

Paul Finch
  • Members
  • 5 posts
  • Gender:Male

Posted 02 June 2017 - 06:15 PM

Hi All

 

Yes i have the beta version on my desk now and it works!! MSC working fab using a usb midi cable and Show Cue Systems.  Thanks for your help Edward and Jon.  






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users