![]() ![]() I understand that in the context of how people use resolume, the fast "feverishly twisting knobs" is ideal, but for my purposes, I might send a single message every two minutes, triggering a cascade of images which simply MUST happen. So a self-contained system that can error-correct is essential. ![]() A board operator runs the show, who often has no idea what the show is supposed to look like. Of course, if it were me handling this personally, I could just see that the clip isn't playing and take it again, but in the professional opera setting where I work, by union rules I'm not allowed to be the one operating the system. I need to figure out a system which I can rely on 100%.Ĭan you elaborate on how a "?" would work? I took a look at the documentation and see that it returns the active state of something, but I'm not sure how to integrate that into a workflow.įor example, if I trigger a column, causing a sequence of clips to begin playing, is there a way to use "?" to prompt qlab to take it again if the UDP packet is lost? For example, can qlab wait for the response from Resolume and IF it never comes back, retake the cue? Or, if not, is there another show control system that can? It's not so much a big deal in fast paced shows, but when you've got a show with gentle fades on a 2400ft^2 video wall and it suddenly jumps past a transition cue, we're going to have a bad day. Is MIDI or DMX a better call? Or perhaps something more beefy as a show control system? I've heard talk of Vezer? Does anyone have any ideas? Is this a fundamental flaw with OSC? Is there another type of cue delivery system which can audit itself (like with FedEx, I want whatever show control system I use with Resolume to require signature upon delivery, not just leave the package at the doorstep and pray it gets picked up.). Some effects do need to be truly simultaneous. 5 second delay between cues in QLab the problem goes away, but there are moments when even that is unacceptable. Of course, a solution I'm finding is by putting a. This problem has been encountered on two separate occasions, the other was a macbook running QLab3 and a single Resolume server on PC, with a direct adhoc network via Ethernet. All computers are connected via Ethernet, static IPs, isolated network with no internet connection We have had occurrences of the misfire happening both when two simultaneous cues are sent to the same server AND when two simultaneous cues are sent to different servers, making me suspect the problem is not on Resolume's ability to parse two simultaneous signals. There doesn't seem to be any correlation between time between cues and this error, so some kind of network timeout doesn't seem likely Going back (up arrow) in qlab retaking the skipped cue will cause it to successfully trigger. Older MacPro running QLab, two new trashcan MacPros running Resolume In our show of 70 cues (213 total counting autofollows and grouped triggers), a cue will be dropped on average once every other show. For example, a cue triggering Column X on server #1 and an autofollow without a delay to a similar cue on server #2 - It seems to only happen when I have multiple cues tied together. ![]() However, intermittently we have had dropped cues. Due to the large nature of the show we split the composition into one server handing the video wall and one handling front projection. I'm using QLab4 which is sending OSC cues to two separate Resolume servers. Bit of a mind bender here and was wondering if anyone has had encountered a similar situation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |