"radio" play of tracks in a group

[TECNICA PERMAR]

Hi!

I would like to play 2 tracks in a group in the way that every time a hit go to that group only one track play once and the other skip on next go the first track skips and play the second.

I've tried with arm/disarm and nesting group but I didn't find a solution..

maybe a script that on first go play one track and disarm the second and next go disarm the first track and play the second track and so on?

thank you!

Luca

[micpool]

Put the tracks in a separate cue list and target the cue list with a start cue. That way you can have any number of audio cues in any number of “radio” playlists. Use a reset cue targeting the cue list to set it back to the top. If you want a radio playlist to loop, auto continue  the last cue to a goto cue targeting the first cue in the list. You can pop a playlist out as a separate window so you can see the progress, through the playlist.  Your main cue list could be a cart with buttons to start each playlist.

Mic

[TECNICA PERMAR]

hi Mic!

a cart and a playlist is what i’ve done..

but is not the result i would like to have..

i would like that every time i fire the same group only one clip plays and in this order:

go 1 - clip 1

go 2 - clip 2

go 3 - clip 1

go 4 - clip 2

and so on

the routine you wrote do that? In this case i think i don’t understand your suggestion (probably my english is not giod enough..)

thank you for your precious help!

luca

[micpool]

Here's a classic toggle group

The critical thing is delaying the arm/disarm cues otherwise both audio cues will play and the toggle will remain unchanged

Workspace and Screen recording attached

Mic

[Rich Walsh]

I think you can use the “Fade & stop peers” setting here: if the clips are set to stop peers then the cue list steps through the clips one at a time and loops round.

Rich

On 2 Mar 2023, at 10:57, micpool <m...@micpool.com> wrote:

Here's a classic toggle group

--
Contact support anytime: sup...@figure53.com
Follow QLab on Twitter: https://twitter.com/QLabApp
User Group Code of Conduct: https://qlab.app/code-of-conduct/
---
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 on the web visit https://groups.google.com/d/msgid/qlab/5e82eaac-1640-4c5a-8137-f049477c5833n%40googlegroups.com.
<Screenshot 2023-03-02 at 10.52.25.png><Classic toggle.zip><Screen Recording 2023-03-02 at 10.51.28.mov>

[micpool]

And here's  2 playlists triggered by a cart when you want more than 2  items in your playlist

[micpool]

On Thursday, March 2, 2023 at 11:08:51 AM UTC Rich Walsh wrote:

I think you can use the “Fade & stop peers” setting here: if the clips are set to stop peers then the cue list steps through the clips one at a time and loops round.

 I'm not clear how to implement your suggestion. Isn't the only group type  or cue list, that will repeat in order, a QLab 5 playlist (which will not  not allow trigger actions inside them) Or have I misunderstood?

[Rich Walsh]

Does this make sense? It’s very rough…

I can’t see how to put a “cue list” into “playlist” mode at the moment? I’ve not poked around with playlists very much yet; doesn’t just a traditional cue list play the cues in order when triggered – and then you just add a GoTo at the end to loop?

Rich

--
Contact support anytime: sup...@figure53.com
Follow QLab on Twitter: https://twitter.com/QLabApp
User Group Code of Conduct: https://qlab.app/code-of-conduct/
---
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 on the web visit https://groups.google.com/d/msgid/qlab/4cc35fbd-1f3c-49cb-9074-c6488896cae8n%40googlegroups.com.

[Chris Ashworth]

That’s true that a cue list can’t (currently?) be set to playlist mode — that’s a neat idea, though.

Is the original request about having two cues that play one after another in a loop, and only one is allowed to play at a time?  (If not, then I have misunderstood, and apologize for the noise.)

If that’s true, my initial thought was “create a cue list with one looping playlist group inside it, and put the two cues inside the playlist”

I am probably missing something though!

-C

[micpool]

Hi Rich

Yes that works., It's basically a 2 cue  version of  my 2nd example , which used short cues as stings. I agree, if you were using long cues, or loops,  and only wanted one to play at a time  that fade and stop peers would achieve this.

Mic

[Rich Walsh]

This thread’s gotten a bit confusing as “cue list” and “playlist” have been used interchangeably, rather than using “playlist” only to mean the specific mode of a Group Cue that (amongst other things) disables the trigger actions of the cues within it.

I think a “playlist” mode Group Cue is not useful for this request as triggering it causes it to restart the cue that is currently playing, not stop it and start the next. A vanilla cue list however, does do this – with the appropriate trigger actions. I think a cue list is superior to a Group Cue for this task as it has the concept of an independent playhead within it, that can step through the cues. (You have to manually loop it, which seems to be the only useful thing – in this context – that a “playlist” mode Group Cue adds to cue list.)

My understanding is that we’re trying to make a round-robin cart machine, where each time you fire a “cart” you get the next sound in the list _on its own_.

Does that help?

Rich

[Ed Boos]

Place all tracks in a group with mode "start random child and go to next cue".

Use a cart to start the group.

Every time you start the group you will play a different track, until all tracks have been played.

If only two tracks are in the group, they will alternate with each start. 
Ed

[micpool]

The random group method won't produce a toggle behaviour, because the round robin only works per cycle. After 2 random cues have been fired (if there are 2 children in the random group) there is a 50/50 chance of the next cue fired being the same as the last.

Mic

[Chris Ashworth]

Hum, I’m not sure I’m following. I’ve attached an example workspace of the cues I’m imagining.

The key pieces of this workspace are:

 - Two cues in a playlist

 - The playlist is set to loop

 - In the Triggers tab, the playlist has the setting “if running, a second trigger [plays next]”

In this way, triggering the playlist will go back and forth between the two cues inside. (Or would play through many cues if it had more than two.)

One key piece of this is using the Triggers setting to “play next" — which is something I missed when I was first trying to figure it out.

Does this match the spec?

-C

[micpool]

I've completely lost the plot!I think we need to remind ourselves of the original question

I would like to play 2 tracks in a group in the way that every time a hit go to that group only one track play once and the other skip on next go the first track skips and play the second.

i would like that every time i fire the same group only one clip plays and in this order:

go 1 - clip 1
go 2 - clip 2
go 3 - clip 1
go 4 - clip 2
and so on

Unless I'm missing something, the playlist group  solution just repeats 1 2 1 2 1 2 forever until it is stopped.  If it gets another start with the triggers set as Chris describes it will skip early to the next track, but it doesn't play alternate cues, on each start targeting the playlist group.

I think the solutions that work, are the  'classic toggle arm disarm' in post 2 of this thread, and the  separate cue list method described, with and without a fade and stop peers option, in posts 3, 4 +5 which has the advantage of being expandable to any number of cues.

[Chris Ashworth]

Oh blah, I see what I missed — my solution works fine for cues that have an infinite duration, such as a still image or text cue with duration set to zero.  In that case, it just waits on each cue until the next trigger comes in.

So if you have, say, still images, my solution works, but it doesn’t work if you have cues with a finite duration, such as an audio cue.

[micpool]

On Friday, March 3, 2023 at 4:31:35 PM UTC ch...@figure53.com wrote:

Oh blah, I see what I missed — my solution works fine for cues that have an infinite duration, such as a still image or text cue with duration set to zero.  In that case, it just waits on each cue until the next trigger comes in

Which is probably  what you had in mind when you wrote the tip text in the inspector.

Shouldn't  'Play one  cue at a time sequentially, actually be play all cues sequentially?'

The option to do either is probably where this is heading.....

What control would need to be added to the playlist inspector to make finite length cues behave the same as infinite length cues? This would add a cycle round robin facility to complement the random round robin capability of the random group cue. This is often the preferred method for samplers because it ensures that you can't get an identical sample occurring consecutively, which is often the only giveaway that sample playback is the source of a sound.

Mic

[Sam Kusnetz]

Chris got us almost all the way there, inspiring me to make this solution:

The Text cues are routed to a stage which goes to an (unused) NDI output. The Playlist group is set to loop, and also set to play next on a second trigger.

When you start the Playlist group, the first song plays, completes, and follows to the Text cue which plays invisibly to the unused NDI output.

When you start the Playlist again, it advances to the second song. When that song concludes, it follows to the second Text cue.

Repeat as much as you need.

There is, however, a dramatically simpler solution. Create a second cue list and set it up like this:

Give the cue list a hotkey or MIDI trigger, or put a bunch of Start cues which target this list in the main cue list.

Every time the cue list is triggered, it will either play the first song, or play the second song and then return the playhead to the first song. This solution can also, clearly, work with any number of songs, not just two.

Shouldn't  'Play one  cue at a time sequentially, actually be play all cues sequentially?'

Because language is flexible, I can see the distinction you’re drawing here but I do not believe that “play one cue at a time, sequentially” is a fundamentally inaccurate description of Playlist group behavior.

Best

Sam

—

Sam Kusnetz (he/him) | Figure 53

s...@figure53.com

[micpool]

Perhaps using a 'pseudo infinite WAIT a year cue ' is better than the text to NDI  cue, as it doesn't require a video licence and its function is clearer.

However, there is a major flaw in the use of any infinite length cue method.. What if the first cue hasn't finished? The infinite length  cue plays not the intended toggle cue.

The second post in this thread already contained  the simpler separate cue list solution.which is obviously the best, as it is universal, expandable, and fully adaptable, but if you do want a 2 item  toggle, visible in the main  cue list, the  classic arm disarm toggle group in post 4 of this thread fit's the bill.

There is a shorter (less cues) toggle  with a  'changing  targets'  group structure , but that does not give quite such obvious visual feedback as the arm disarm method.

Mic