Hello everybody,

I was wondering whether anybody knew of a good way to hold off a bang until the right conditions have been met.

It's kind of hard to explain, but essentially I have a looping patch. The loop repeats over and over again until a random parameter tells it to stop looping. The problem? The bang that stops the loop doesn't consider where it is stopping in the sample. So I have a tablplay~ that is looping, and suddenly it stops and pops/clicks right in the middle of it. The goal is to create a kind of check that only sends a bang when the sample is done playing.

When a bang is sent at the end of the tabplay~, check whether the spigot object has been opened. If it has, pass through the bang, and stop the playback. If not, WAIT until it has opened, and THEN pass it through. Does anybody have a good idea of doing this?

This is a simplified version of the looper subpatch. Notice a couple of things.

1. Select objects sends a 1 which starts the loop
2. The delay object delays the bang from the end of the tabplay to start the loop all over again (it increases over time actually)
3. Select object sends a 0 (at some random point (we don't know when)) but the bang will go through only when the spigot is open. So the sample needs to have stopped playing when this happens.

The tricky part about all of this is that the looper needs to stop IN BETWEEN the start of the next loop, and the end of the sample.

Help would be tremendously appreciated.

Does this help?

@LiamG The thing is that the tabplay~ is looping indefinitely. If I'm looking at what you wrote correctly, that would stop the playback only after one loop. The looper needs to be ready to stop at any second whenever the indefinite stop bang is sent out.

It looks like I don't fully understand what you're aiming for. I do think though that using the [f] and [sel] objects will help you to get conditional logic right, as this is a way of "checking whether the spigot has been opened".

@LiamG No worries. Simply put, I'm trying to avoid popping and clicking. In my case, it happens when the loop is randomly told to stop playing without verifying that the playback is complete. So I somehow have to find a way to make sure that looping ends only when the playback ends without knowing when the stop looping message arrives.

I've been banging my head against the wall for a while about this. I may just come back to it tomorrow. I think you have a point though that the select and float objects will probably come in handy.

@lunacyfringe said:

I somehow have to find a way to make sure that looping ends only when the playback ends without knowing when the stop looping message arrives.

If that's the case then I think the construction I posted should help. Just connect the second outlet of [sel 1] back into tabplay~ (I forgot to do this in the picture). That way, each time the sample ends, it will either restart the tabplay~ object (0-->bang) or stop it (1-->stop)

@lunacyfringe and @LiamG You can use a spigot if you wish...... no capture and storage of the bang is necessary because [tabplay~] kindly provides the bang when it has finished playing.......
If you do want to immediately stop the sample without clicks then you can use [line~]........ but..... you were nearly there with your patch....... the problem you had was that the bang to fade out was immediately followed by a bang to stop. You needed a delay of say [delay 6] in the string before the stop message so as to allow the fade out to complete before the stop!

David.

Oh yeah, of course that's simpler!