Yahoo Groups archive

Analogue-sequencer

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

Message

Re: [analogue-sequencer] AUX D acc. start value?

2004-07-07 by Colin f

> i've been playing around with masks combined with the AUX D acc, and
> i've come up with some questions i can't find answers to in the
> manual. does the AUX D accumulator value start at 0 by default?

Yes - aux D acc is reset to 0 when a new pattern is selected.

> so secondly, is the
> AUX D acc. independant from the AUX D track if no value is set there?

The aux D acc is added to the value for aux D, but when it's being used for
thresholds and masks, the accumulator value is used by itself - the value of
aux D is not included.

> and it looks like the 'mask aux B, Dacc > n' & 'mask aux C, Dacc > n'
> events only work if they're in a track above the aux B or C track
> they're trying to manipulate..i.e. on AUX track A or B.

The auxes are processed in series order - A, B, C, D
So there's no point masking aux B from aux C since aux B will already have
been processed before aux C can turn it off. That's why there's no mask aux
A - there's no aux before A to assign it to.

> would it be possible to copy just the AUX steps of a track?

Potentially, but if you bear in mind the above conditions in future you
shouldn't need to, and I can use the limited remaining space for something
else.

> and another thing i'd like to see; the possibility to set a 'loop
> start point' for playlists, kind of like on the MPC's. so you could
> make a playlist that starts at its first step, plays completely
> through and then loops back to the second step instead of the first
> one..being able to dynamically change the loop point with an aux
> event would be really cool. but that's probably P4 stuff, right?

Sounds complicated... it might scare more people than it pleases ;-)

Cheers,
Colin f



________________________________________________
Message sent using UebiMiau 2.7.2

Attachments

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.