Yahoo Groups archive

Analogue-sequencer

Index last updated: 2026-04-28 23:15 UTC

Thread

RE: [analogue-sequencer] another question: triggering a pattern

RE: [analogue-sequencer] another question: triggering a pattern

2004-07-06 by implode7@comcast.net

No - that's the whole idea. I want the pattern to reach step 16 for one repeat. If it counts 16 steps, then it would reset even earlier than setting chng = P. 
Show quoted textHide quoted text
-------------- Original message -------------- 

> > Actually, I think that it would be less confusing, but that's 
> > just the way I think... 
> > I am so used to overriding the gbar, I never even thought of 
> > that. If I always override it, I can use it for just these 
> > patterns. Now, having not used the gbar yet 
> > (intentionally...), will it work like I want to ? If I tell 
> > it step 16, will the pattern in question not repeat until it 
> > finally reaches step 16? Or will something more sinister happen? 
> 
> Gbar=16 and chg=B will cause the pattern to reset and 1 repeat to be 
> counted after 16 steps. 
> But maybe you don't want to pattern to reset ? 
> 
> Cheers, 
> Colin f 
> 
> 
> 
> 
> 
> 
> Yahoo! Groups Links 
> 
> 
> 
> 
> 

[Non-text portions of this message have been removed]

RE: [analogue-sequencer] another question: triggering a pattern

2004-07-06 by Colin f

> No - that's the whole idea. I want the pattern to reach step 
> 16 for one repeat. If it counts 16 steps, then it would reset 
> even earlier than setting chng = P. 

Right, I think I understand. You have a pattern that is changing length
under aux control and each time the pattern resets from it's current end
point, that counts as a playlist repeat. But you only want it to count
at step 16 ?
Is the progression of the length of the pattern consistent ? If so, you
could work out how many steps it takes to reach step 16, then set gbar
to that number with chg=B. Then the gbar reset/repeat count will
co-incide with the pattern reaching 16.
Is that any help ?

If I made it work such that a pattern with a dynamically modified length
only counted a playlist repeat when the 'real' last step was reached,
you could end up having playlists getting stuck on a pattern that never
reaches step 16.

However, there might be some aux events I could add that would let you
get this level of control. There is a playlist 'hold' flag, used oddly
enough for playlist hold in ple mode. If you set that 'on' on step 1,
and 'off' on step 16, the playlist would be prevented from advancing
until step 16 was reached. That seems easy enough...

Cheers,
Colin f

Re: [analogue-sequencer] another question: triggering a pattern

2004-07-07 by Paul Nagle

Not wanting to throw a spanner in the works but how would you
determine one pass of a pattern if the direction is "random"? 

Just thinking outloud cos I don't know the answer...

Personally, I'd love to be able to "schedule" some Aux events to
happen based on criteria such as "note x played on any track", "> x
notes played simultaneously", "track x accumulator D > y", "playlist
step x reached", "x passes of gbar executed" and so on. But no, I
don't expect to see these in the P3, except in my strange dreams..

Anyway, it's nice to see all the sequencing passion coming out on this
list. I've been holding back a little and hoping that some of the
detailed stuff isn't frightening for those who haven't delved very
deeply yet. 

Paul

---
Paul Nagle - SoftRoom Music - www.softroom.co.uk
          Bogus Focus Records - www.BogusFocus.com

Re: [analogue-sequencer] another question: triggering a pattern

2004-07-07 by Gene Schwartz

> From: Paul Nagle <softroom@btinternet.com>
> Organization: The Soft Room
> Reply-To: analogue-sequencer@yahoogroups.com
> Date: Wed, 07 Jul 2004 08:27:37 +0100
> To: analogue-sequencer@yahoogroups.com
> Subject: Re: [analogue-sequencer] another question: triggering a pattern
> 
> Not wanting to throw a spanner in the works but how would you
> determine one pass of a pattern if the direction is "random"?
> 
> Just thinking outloud cos I don't know the answer...

Ideally there would be a user option to determine whether to use the pattern
defined last step. But if it were random, then it would eventually arrive at
step 16, and that would be one repeat. It would be 'random' in that case.
> 
> Personally, I'd love to be able to "schedule" some Aux events to
> happen based on criteria such as "note x played on any track", "> x
> notes played simultaneously", "track x accumulator D > y", "playlist
> step x reached", "x passes of gbar executed" and so on. But no, I
> don't expect to see these in the P3, except in my strange dreams..

A config option to 'implement Paul's strange dreams'? Actually those ideas
sound great...
> 
> Anyway, it's nice to see all the sequencing passion coming out on this
> list. I've been holding back a little and hoping that some of the
> detailed stuff isn't frightening for those who haven't delved very
> deeply yet. 
> 

Record that aux events tutorial...actually, I think that a tutorial or two
of setting up some aux events would probably help some people. But the aux
events are where this machine truly gets awesome.

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.