[Midi show control from scs to orb]

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

 

Simon

[Midi show control from scs to orb]

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".

[Midi show control from scs to orb]

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

[Midi show control from scs to orb]

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?

[Midi show control from scs to orb]

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) ?