Devamp Cues being skipped???

[Nicholas Drashner]

Hi there,

I'm using Devamp cues and slices to trigger MSC messages to a click track.  I have a click track with about 10 slices, and I want each one to trigger a consecutive MSC message.  To do this, I have a group following the click track with alternating Dvamp and MIDI message cues (example: Devamp Slice 1, Midi message 1, Dvamp Slice 2, Midi message 2, ect.)  All of these are auto followed. 

The problem I'm having is that Qlab is at times skipping some of the Dvamp cues - like it is triggering 5 and 6 simultaneously when is should only trigger 5 and wait for 6.  It seems as if the calculated wait time isn't able to insert before it just goes on to trigger the next cue.   And the error is happening at various times when I play the whole song - each time is different.

any ideas?

thanks,
Nick

[Nicholas Drashner]

I may have solved this right after posting.  I'm not putting a 0.1 second wait time after each MIDI message, which gives the following Devamp cue time to calculate its own wait time before being triggered.

[micpool]

That should do it. I'd be more inclined to put it as a pre wait on the devamp cue.

The pre wait can be as long as you like as long as the revamp happens before the next slice is reached

Mic

[Chris Ashworth]

Hi Nicholas,

Another thing to check is that you’re using the most recent version of QLab; a recent update resolved some bugs related to this.

[micpool]

On Tuesday, May 6, 2014 2:27:09 AM UTC+1, Christopher Ashworth wrote:

Hi Nicholas,

Another thing to check is that you’re using the most recent version of QLab; a recent update resolved some bugs related to this.

I can replicate Nicholas' problem

Not surprisingly, it's related to the speed of the mac.

I couldn't replicate it on a MacBookPro, but it skips on devamps consistently on my mac mini.

Video attached with both machines running identical workspaces (5 fps so counters update jerkily)  wav is 6 channels

Mic

[micpool]

Whoops

Scrub my last post, what I had actually replicated was  Chris's solution!

The cuelist called Slow Mac was in fact running 3.0.16. Updating that Mac to Qlab 3.0.18 solves the problem and the 2 machines execute the cue lists identically.

Mic