Analogue-sequencer

-------------- Original message -------------- 

> > 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 ? 
correct.

> 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 ? 
I'm confused. 
"The 'global bar length', GBar, is the number of 16th note steps that the P3 will use as the length of one cycle of the current part." So, if I set gbar to 16, won't the pattern reset well before I want it to without ever reaching step 16? Suppose it actually takes, e.g. 45 16th note steps to reach step # 16, as indicated by the cursor lighting up step 16?

> 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. 
> 
That should be the user's responsibility to make sure that his patterns do what is intended. I think that this should at least be available as an option, say, 'use pattern last step'.
> 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... 
> 
Well, I only argue so strongly proportionally to how much fun I'm having with the P3. So I hope you're taking this in the right spirit. But this just seems so basic to me that part of the concept of using an aux event to control the last step is that you may want to create a much longer evolving pattern. I think that Paul's suggestion of using parts would work - I could (I think - haven't tried part aux events) tell it to move to the next part on step 16, but then, if I wanted to repeat this pattern x times, I'd need x parts...
> Cheers, 
> Colin f 
> 
> 
> 
> 
> 
> 
> Yahoo! Groups Links 
> 
> 
> 
> 
> 

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

> I'm confused. 
> "The 'global bar length', GBar, is the number of 16th note 
> steps that the P3 will use as the length of one cycle of the 
> current part." So, if I set gbar to 16, won't the pattern 
> reset well before I want it to without ever reaching step 16? 
> Suppose it actually takes, e.g. 45 16th note steps to reach 
> step # 16, as indicated by the cursor lighting up step 16?

If you set gbar to 16 it would reset too soon. If you set it to 45, it
wouldn't.
Of course, then your advance to the next part would be synced to the 45
step gbar.

> That should be the user's responsibility to make sure that 
> his patterns do what is intended. I think that this should at 
> least be available as an option, say, 'use pattern last step'.

Let's see if we get any more votes for that option ;-)
I have a feeling it may be rather tricky to implement though...

> But this just seems so basic to me that part of 
> the concept of using an aux event to control the last step is 
> that you may want to create a much longer evolving pattern.

I often use it with a random or threshold mask to decide whether a
pattern will play 8 steps or 16.
In that case, changing the behaviour might cause me to have to think
more about what I'm doing.
Next coding session I have, I'll add a 'set plist hold' event, and see
if it keeps you happy ;-)

Cheers,
Colin f

> From: "Colin f" <colin@colinfraser.com>
> Reply-To: analogue-sequencer@yahoogroups.com
> Date: Wed, 7 Jul 2004 01:04:57 +0100
> To: <analogue-sequencer@yahoogroups.com>
> Subject: RE: [analogue-sequencer] another question: triggering a pattern
> 
>> I'm confused. 
>> "The 'global bar length', GBar, is the number of 16th note
>> steps that the P3 will use as the length of one cycle of the
>> current part." So, if I set gbar to 16, won't the pattern
>> reset well before I want it to without ever reaching step 16?
>> Suppose it actually takes, e.g. 45 16th note steps to reach
>> step # 16, as indicated by the cursor lighting up step 16?
> 
> If you set gbar to 16 it would reset too soon. If you set it to 45, it
> wouldn't.
> Of course, then your advance to the next part would be synced to the 45
> step gbar.
> 

ah - well, I hadn't realize that this parameter could be set higher than 16,
but 16 as a limit would be very low, wouldn't it...Let me see - 256, that's
not so bad, but it is 16 notes...plus, I will definitely be setting up some
patterns using the probability aux events so I won't be quite sure how long
they'll go. It's my goal to exceed any limit that you set...

>> That should be the user's responsibility to make sure that
>> his patterns do what is intended. I think that this should at
>> least be available as an option, say, 'use pattern last step'.
> 
> Let's see if we get any more votes for that option ;-)
> I have a feeling it may be rather tricky to implement though...
> 
>> But this just seems so basic to me that part of
>> the concept of using an aux event to control the last step is
>> that you may want to create a much longer evolving pattern.
> 
> I often use it with a random or threshold mask to decide whether a
> pattern will play 8 steps or 16.
> In that case, changing the behaviour might cause me to have to think
> more about what I'm doing.
> Next coding session I have, I'll add a 'set plist hold' event, and see
> if it keeps you happy ;-)
> 
> Cheers,
> Colin f
> 

Alternatively, maybe you could prescribe a drug that would make me think
that all of my demands have been met...

Now, this 'set plist hold' event would hold the playlist on the same step,
but wouldn't really affect the number of repeats to step 16, as I understand
it...
So, it's not as good as a config option to have the repeat counter simply
look to the pattern last step. In addition this wouldn't use up a valuable
aux event.

But, hell yeah - it will make me happy, although I will pretend not to be.

designing a pattern that has an aux event assigning various probabilities to
aux b, which assigns the last step to the sequence. God, this is fun. Load
pattern with aux events, put controllers on another track. That's the way to
go here.

I need something varying the pitch in the first 5 steps, which is what is
repeating maybe 55% of the time or so. So, there go the other 2 aux events,
I think.

P4 needs 16 aux events per track at least.

Back to play.