Fire Qlab with Digico Snapshot via OSC

[Damian Clarkson]

Hi,

Can anyone give me any pointers on how to make 'firing next snapshot' fire a cue in qlab via OSC. Documentation on the Digico side seems to be quite minimal with the OSC stuff.

For example, I would like to be firing through my snapshots with a macro button, then when it fires a particular snapshot, that will fire next cue in qlab.

Thanks, Damian 

[Johnny Boy]

Hi Damian,

the easiest way is to just send a MIDI cue Control Change message from Qlab.

Then in the Snapshots section on your Digico, open the Scope and press the Control by midi button.

In the next window you assign the same CC number.

Midi ch 16.

CC numbers can range from 16 to 19.

And the value is whatever you set in the MIDI cue in qlab.

Plus to just toggle up and down the snapshots, use CH16, CC 19, value 126 for fire previous and 127 for fire next.

We use this feature all the time for our shows at Malmö City Theatre in Sweden.

Enjoy!

JC

[Johnny Boy]

I would also add that we have also controlled our SD9 via OSC.

I'm back at work tomorrow and will post the info when I'm at the desk.

Cheers, J

[Damian Clarkson]

Thanks for that. I'm fairly new to the Midi show control world and I think I'm missing something.

I've added a Midi cue 'command' control change, ch 16, control number 60, control value 64 (just the default numbers except ch number).

But I'm not sure exactly how things work on the digico side.

I add my snapshot, then click control by midi, click fire snapshot send MIDI. I can change the numbers 16 to 19, are they referring to MIDI ch numbers? and the number after the comma, is that the CC number? I think I'm a little confused. Thanks for your help. I've attached a screen shot.

Damian 

[Janne Sivonen]

Hi,

The new digico software has an OSC implementation that the ipad remote is using. You should ask your local digico dealer for specifics for the osc details for "other osc". They are not publicly available.

As for digico midi,

the snapshots will be Control Change on MIDI Channel 16 and Control numbers 16-19. Every Control number has 128 available cues. The digico software reading (16,17) stands for (Control number, Control Value). It is not possible to change the Midi channel.

Janne

--
--
Change your preferences or unsubscribe here:
http://groups.google.com/group/qlab
 
Follow Figure 53 on Twitter: http://twitter.com/Figure53

---
You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Janne Sivonen
Yngre ljudmästare, Sound system engineer
janne....@svenskateatern.fi
+358 50 5924362
(+358 50 3716443)

Svenska Teatern
Norra Esplanaden 2
00130 Helsingfors
vaihde (+358) 9616211

[Jarrett Krauss]

Don't use the control by midi section. In the cue list, open up the scope tab, and look for MIDI list. Now in each cue you can assign the midi value, whether it be a control change, program change, note on, whatever. On the QLab side, you are creating a midi trigger for the event, whether it be a group cue or single audio cue or something else. you could do it by hitting capture and then firing the cue on the console or you could type it in. 

In your situation, you would have a bunch of cues that have no midi data attached and then one of the cue would have a midi value. Screenshot attached.

[Andrew Moyer]

On Thursday, August 13, 2015 at 6:15:57 AM UTC-4, Janne Sivonen wrote:

Hi,

The new digico software has an OSC implementation that the ipad remote is using. You should ask your local digico dealer for specifics for the osc details for "other osc". They are not publicly available.

From the Digico SD App User Guide...

 NOTE: In the External Control panel in the images below there are several functions that are not yet implemented –
these are:
HUI Sensing button (not yet implemented) & Add Device – other OSC and MIDI (not yet implemented)

[Damian Clarkson]

Hey. Thanks for that. That makes total sense now. That just made the show I'm planning a whole lot easier.
What purpose would you use the control by midi 'snapshot fires midi' if you can do it the way you've mentioned?

[Jarrett Krauss]

Haven't personally used it, but according to the manual it's for firing console snapshots from incoming MIDI control changes from external sources. Sort of the opposite direction of what you want to do.

[Damian Clarkson]

I'm Actually referring to the 'snapshot fires midi' not 'midi fires snapshot'. Why would you use this if you can set up snapshots to fire midi in the midi list section? Is it the same thing? But a different method..?

[John Conlon]

Sometimes it's justeasier to have all your cues running and fired from the desk. Some people just like using the next button to fire qlab.
For example if you have a snapshot that has an inbaked fader crossfade and then an audio cue that is timed to that, it's easier to just press next and then not have to also fire qlab.

On 21 Aug 2015 04:30, "Damian Clarkson" <damianp...@gmail.com> wrote:

I'm Actually referring to the 'snapshot fires midi' not 'midi fires snapshot'. Why would you use this if you can set up snapshots to fire midi in the midi list section? Is it the same thing? But a different method..?

--
--
Change your preferences or unsubscribe here:
http://groups.google.com/group/qlab

Follow Figure 53 on Twitter: http://twitter.com/Figure53

---

You received this message because you are subscribed to a topic in the Google Groups "QLab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qlab/L9liDZNwsRQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qlab+uns...@googlegroups.com.

[Damian Clarkson]

I understand that. That's exactly what I am doing from the 'MIDI list' settings. Firing an audio cue in qlab when a Digico snapshot is fired. I'm talking about the 'control by midi' section. Where you can select 'midi fires snapshot' or 'snapshot fires midi'. What is the difference between firing midi from the midi list settings or using the snapshot fires MIDI in the control by midi section.

[Jarrett Krauss]

Page 2-22 of the SD_Software_Reference_V2 manual has the answer you're looking for. I think where it says General Purpose Controller it is referring to Midi Control Changes. Don't have a console handy to test it out though.
"

The MIDI Received Fires Snapshots button allows the Snapshot system to respond by default to the following incoming MIDI messages:

General Purpose Controller 16; Values 1 to 127 will fire snapshots 1 to 127
General Purpose Controller 17; Values 0 to 127 will fire snapshots 128 to 255
General Purpose Controller 18; Values 0 to 127 will fire snapshots 256 to 383.
General Purpose Controller 19; Values 0 to 125 will fire snapshots 384 to 509.
General Purpose Controller 19; Value 126 will fire the previous snapshot in list.
General Purpose Controller 19; Value 127 will fire the next snapshot in list.

When active, the Fire Snapshot Sends MIDI button causes the above messages 1 to 509 (or customised versions - see below) to be sent whenever a snapshot button is pressed. Previous and Next buttons do not output MIDI messages of their own."

 

Engaging "MIDI Received Fires Snapshots" allows the Snapshot system to fire cues based on incoming midi. Disengaging it allows you to fire midi into the console and not worry that cues will change. "Fire snapshot sends MIDI" repeats the incoming MIDI CC data back out into the world. I've never used this function, but I suppose if you wanted to sync up two DiGiCo console's snapshots via MIDI, then you can do it this way.

Either way, I don't think this feature is useful to you this time. Scope>MIDI List will send MIDI of any flavor out into the world, including QLab.

One more thing. On the newest version of the SD software, v726, there is a MIDI safe notification somewhere and you can turn MIDI on and off from that window. I use an SD10 still on v685 which doesn't have any visual indication that MIDI safe is on or off. If you're on v685 or earlier, I recommend that you make a macro that turns MIDI safe on and off. Better yet make it 2 separate macros, one with an ON function and with one with an OFF that are triggered from the 'on' and 'off' of a single smart key. Make them two separate colors and voila, your very own homemade midi safe indicator. Test before use.

Jarrett