EOS and QLab

P

Patch29

Member
Hi so I have two questions but first let me tell you where I am at.

So I just finished programming and running two dance shows. Both of them I ran from my Dell laptop via nomad and audio was run from a mac book pro on Q-Lab. A few years ago I ran qlab off an Ion but I am wondering if I can do it in reverse.

1) Instead of having to watch the time code on qlab for when to go to the next que, is there a way to trigger my nomad from qlab but with specific parts in the song triggering different ques? If so how?

2) How do I link the mac with pc especially without being able to do this via midi time code? I remember we did use the OSCrouter but I did not configure it and that was with the old version of Q-lab.



Thanks
 
Ion can be triggered from QLab via timecode, OSC, MSC, MIDI note, and probably via UDP strings if you want to get creative with scripting. Of these, it sounds like OSC is the better option for your application.

  1. Configure an OSC send port and an Ion receive port: use 3032 for TCP. Hunt up the manuals or tutorials that are readily available on ETC's site or Figure53's site, since Eos/QLab is a very common configuration.
  2. Create a group cue that contains your audio cue and several OSC network cues.
  3. Set the delay time on the OSC cues to whenever you want them to happen in the song.
  4. Execute the group cue and see what happens.
So what should your OSC strings look like? That depends a lot on how you have programmed the Ion. If all you want to do is go to the next cue then /eos/key/go wil do it for you. A somewhat safer approach would be to trigger explicit cues or isolate each song into it's own cue list and load that cue list on the main fader as one of the first actions in your OSC group cue. To fire an explicit cue the message is /eos/cue/#/fire for the master fader or #/# for an alternate cue list/cue number.

If all that sounds like greek then you might want to look for some YouTube videos.
 
sk8rsdad said:
Ion can be triggered from QLab via timecode, OSC, MSC, MIDI note, and probably via UDP strings if you want to get creative with scripting. Of these, it sounds like OSC is the better option for your application.

  1. Configure an OSC send port and an Ion receive port: use 3032 for TCP. Hunt up the manuals or tutorials that are readily available on ETC's site or Figure53's site, since Eos/QLab is a very common configuration.
  2. Create a group cue that contains your audio cue and several OSC network cues.
  3. Set the delay time on the OSC cues to whenever you want them to happen in the song.
  4. Execute the group cue and see what happens.
So what should your OSC strings look like? That depends a lot on how you have programmed the Ion. If all you want to do is go to the next cue then /eos/key/go wil do it for you. A somewhat safer approach would be to trigger explicit cues or isolate each song into it's own cue list and load that cue list on the main fader as one of the first actions in your OSC group cue. To fire an explicit cue the message is /eos/cue/#/fire for the master fader or #/# for an alternate cue list/cue number.

If all that sounds like greek then you might want to look for some YouTube videos.
Click to expand...

Im actually on nomad and using two different computers with two different operating systems.
 
You must log in or register to reply here.

Similar threads

Herr_Sprecker
QLab 4 Scripting Control for an Eiki LC-XL100 Projector
Replies
9
Views
873
TimMc
TimMc
Timeradiant
EOS Qlab osc networking issue
Replies
0
Views
311
Timeradiant
Timeradiant
NickVon
another one of those "Best laptop for" threads
Replies
1
Views
197
dbaxter
dbaxter
Ken Porter
Sound f/x custom hardware for ergonomic programming of QLab?
Replies
6
Views
1K
Sam Kusnetz
Sam Kusnetz
A
Triggering StageTracks w/ QLab
Replies
2
Views
3K
Malabaristo
M

Users who are viewing this thread

Total: 1 (members: 0, guests: 1)
Back