Hi pros,

[Kalman Tarr]

There is an audio cue. There are markers in it. 

When I play it and watch the 'time&Loops' tab, I see that when the play-line step over a marker, the 'add slice' button flashes up. I think this is a generated trigger. How can I get that if I want to use it?

Sincerely,

Kalman

[Chris Ashworth]

Kalman,

With apologies, I don’t really understand what this means, but I don’t think it is something that is related to cue triggers. The “add slice” button is enabled or disabled when the play position is at a time that a slice can or can not be added.  

-C

[Philip Glenn]

If I understand, I believe you just click at the marker (while not playing the cue) in the waveform. But I think they are already slices - right? So the button might actually say “delete slice”. 

Philip Glenn

pgle...@sbcglobal.net

817-781-0237

On Oct 5, 2025, at 1:16 PM, Kalman Tarr <tarr....@gmail.com> wrote:

There is an audio cue. There are markers in it. 

When I play it and watch the 'time&Loops' tab, I see that when the play-line step over a marker, the 'add slice' button flashes up. I think this is a generated trigger. How can I get that if I want to use it?

Sincerely,

Kalman

--
Contact support anytime: sup...@figure53.com
User Group Code of Conduct: https://qlab.app/code-of-conduct/
 
Instagram: https://www.instagram.com/Figure53
TikTok: https://www.tiktok.com/@QLab.app
Bluesky: https://bsky.app/profile/qlab.app
---
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.
To view this discussion visit https://groups.google.com/d/msgid/qlab/1ec9fecd-305a-4f5c-b95e-12296d098ecen%40googlegroups.com.

[Kalman Tarr]

Hi Rich,

You're right, Rich. When the cue runs and reaches the next marker, the "add slice" button flashes. Now I understand that what happens is that the button is enabled or disabled. But when the system disables it, something happens in the program. This should be achieved by the property. According to them, it is not possible. (Again, I'm asking something that is not necessarily in the scope of general use :-( )
I thought that if I could read out whether the button is enabled or disabled. This would obviously include the marker time value. I know I can solve this by running a script. But I wanted to avoid that.
I ran into the woods again!

Thanks

Kalman

[Rich Walsh]

I’m not sure why you’ve invoked my name?

If you want something to happen when a playing Audio Cue crosses a slice marker you can:

1. Put the Audio Cue and a Start Cue targeting the event you want to trigger in a “timeline” Group Cue and then, on the Timeline tab of the Inspector, drag the Start Cue so it snaps to the slice marker in the Audio Cue’s waveform
2. Put the Audio Cue and a Start Cue targeting the event you want to trigger in a “start first” Group Cue, set the Audio Cue to auto-continue and insert a Devamp Cue between them set to “Devamp currently looping slice” and “Start next cue when target reaches the end of the current slice"

Neither of these require a script or access to the internal workings of QLab that change the properties of a UI button…

You might want to read this to understand more about ways of using slice markers to trigger actions: https://qlab.app/cookbook/devamps-demystified/.

Rich

[Kalman Tarr]

That was a Freudian slip, Rich. 

I knew you'd come up with a good idea. And you did. 

Thanks and gratitude.
Best,

Kalman

[Kalman Tarr]

Hi Rich,

Using the first suggested solution, which is very good, there is a problem. 

During rehearsal, when I need to start from a different audio cue, I achieve this by clicking on the group cue timeline. 

What happens is that it displays the previous events (be it the start or midi cue)
Well, how can I prevent of this. By this I mean that only the event generated by the next marker should happen.
Is there a solution for this or do we have to live with this?

Hopefully, the question is clear.

Thanks in advance.

Sincerely,

Kalman

[Rich Walsh]

This is a feature: https://groups.google.com/g/qlab/c/tvgR9OfeD4Q/m/k3Cvd77QAwAJ. The only real workaround is to use timecode instead: https://qlab.app/docs/v5/fundamentals/cue-lists/#the-timecode-tab.

You could, of course, also construct a script to load the Group Cue to a time, temporarily disarm all zero-length child cues before that time, start the cue and then rearm the cues.

There is potentially a slightly convoluted way of tricking this by using MIDI Cues of non-zero length – eg: a control change that fades over 1s – which should only fire the final value when loaded past, but you’d have to do more testing on that. If you can construct your triggered events so that they require a control change of a particular value you may get round this feature by having them fade to a different value over a time short enough that QLab essentially only spits out the start and end values; loading to time after this MIDI Cue should not cause it to send its first value. It would probably work with OSC too, but obviously there is no way of giving a Start Cue a duration to do it that way. I can’t immediately recall if you can set the message rate for MIDI fades; for OSC fades you can get as low as one per second.

It’s a shame you (still?) can't use the same sort of setting as for timecode to NOT send cues you’ve loaded past…

Rich

[Kalman Tarr]

Hi Rich,

My first solution was indeed a timecode-controlled audio playback. This is where I encountered the problem of excluding the retrospective display.
Shame burns my face  that I hadn't paid attention to the 'on start' setting in the cue list timecode tab.
But, that's why you're a pro!

Thanks again your help.

Best

Kalman