audition problem

[Kalman Tarr]

Happy Sunday, everyone!

I’ve placed audio and video cues in the workspace and set slice markers on them.
I am creating a series of groups where each group triggers the media files starting from the times defined by the slice markers.
Each group contains the following elements: stop, load, start, and fade (for volume or brightness). I set the timing of the "load" element based on the slice markers so that the groups trigger the media accordingly.
Everything works correctly until I activate "Audition" mode in the workspace.
In this mode, every group starts the media elements (audio/video) from the beginning, regardless of the settings.
I don't understand what is happening differently or what the cause might be.
I checked the settings but didn't find anything unusual—or perhaps I overlooked something.
(I am using the Monterey operating system on a 2017 MacBook Air.)
Could someone help me understand this issue?

Here is a screenshot of the workspace (wsp).

Thanks in advance.

Best,

Kalman

[sftechguy]

First suggestion would be to check in Settings → Audition that the action of each cue type is what you would expect in order for what you're doing in your group cues to work.  Most likely you need to change some that are set to "no output"  to "leave output unchanged".  Be aware, however, that doing so may have unintended consequences when in Audition mode (making it not really "auditioning" in the usual sense).

-s

[micpool]

I can't replicate this.

For me normal playback and audition playback work exactly as expected, regardless of any rerouting in settings/audition

Having said that, I don't understand the relevance of the slice markers in your description. You are using a load cue to load to a specific time. This might be set to the same time as a  slice marker but  beyond them being set the same I can't see that the slice marker is in any way relevant. Or is there some other programming that is hidden in your screenshot?

Mic

[Kalman Tarr]

Hi Mic,

The goal was for the media file to run from one marker to the next and then stop with a gradual fade-out; the whole sequence is wrapped in a group. I am now showing a scenario where there is no group—just the cues themselves—so "Group Mode" doesn't interfere with anything.

I watched your video; Audition is not enabled. It’s just a standard "GO" command.

When Audition is enabled, everything goes wrong. The media starts from the beginning, then fades out and stops somewhere. 

You might ask why this matters. For an audio cue, it really doesn't. 

But when I want to check a video—taking advantage of Audition mode—that’s when it becomes a real problem.
I still don't understand why this error occurs!

I know there is another solution using a "devamp" cue. But with that method, it’s difficult to trigger a fade cue *before* the next marker in such a way that the process—fading and stopping—completes right at that next  marker.

Any new idea?

Best,

Kalman

[micpool]

Kalman,

I think you forgot to post the screenshot without thegroups?

In myscreen recording  the first pass is the normal play mode (indicated by the fact the play arrow is solid in the cue list and the video appears in the monitor window.)

On the second pass I am auditioning the cues using option-space (indicated by the outline bracketed green play arrows in thecue list and that the video appears in the audition window).

Tools Always Audition gives the same result as option space audition

Mic

[Kalman Tarr]

Help me Mic,
I took screenshots of the two situations (normal/listening).
But the files are too large. I converted them to 480p, but the system indicated that they were still too big.

How can I convert them to a smaller size?.

This is the screenshot that was missing.

Sincerely,

Kalman

[micpool]

A screen recording that is small enough to be accepted as an attachment for this, group is normally, about 5-10 seconds in length.

In your case, as the pre wait  on the face  cue is unlikely to affect the outcome, reduce this to 3 seconds and your, file should be small enough!

[Kalman Tarr]

Hi Mic,

I try to send the clips.

[Sam Kusnetz]

Hi Kalman

Try making the order of cues:

• Load cue
• Audio cue
• Fade cue

Does that behave the way you’d like?

Sam

—

Sam Kusnetz (he/him) | Figure 53

s...@figure53.com

On Sep 14, 2026 at 8:50:36 AM, Kalman Tarr <tarr....@gmail.com> wrote:

Hi Mic,

I try to send the clips.

--
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/9ed9828c-9a91-40d3-a313-032283c68872n%40googlegroups.com.

[Kalman Tarr]

Hi Sam,

Your advice worked, Sam. The audio sequence plays correctly from one marker to the next. I don't really understand what's going on.
I hope *you* do! I’m not asking you to fill me in on the technical details. However, to implement this solution, I need to figure out how to write a script that iterates through all the markers step-by-step and sets the "load target time" for the "load cue" and the "pre-wait" time for the "fade cue." I also checked the video cue, and that’s working fine too.
Thanks for the idea.
Sincerely,

Kalman

[micpool]

I'm obviously missing something here.....

In your last video the selected and playhead cue is cue 1.  I assume you are triggering cue 3 with a hotkey trigger? Is this correct? 

If so, I have exactly replicated your cue list, and again, for me, it doesn't matter where the audio cue is, it works identically in normal and audition modes. (screen recording attached).

MIc

[micpool]

Sorry, screen recording this time with audio attached

Mic

[Kalman Tarr]

Hi Mic,

Thanks for the reply! 

I’m curious why your WSP file works, given that it’s structured exactly the same way as mine. I don’t think the issue is related to the macOS or QLab version. It might just be that you got lucky—or perhaps I simply don’t know enough about macOS or QLab.

Sam’s advice is useful, but I want to create a sequence of cues.
Well, I found a solution for this, as shown in the attached images.
I have an audio file containing markers, and I use a script to generate a series of new audio and fade cues.
The audio segments are defined—or rather, delimited—by the markers. This solution works in both normal and audition modes. Since the audio cues are merely references, they don’t place a significant load on the WSP file when running.

Thank you again

Kalman