Analogue-sequencer

I've owned my P3 for about 18 months now, but am only starting to get 
into the D accumulator.  The song I'm working on right now has me 
skipping across cables to mute tracks, falling on delays, splitting my 
skull to switch parts... for a fairly simple tune.

So I've figured out how to configure an Aux event (on Aux B) to unmute 
a track which I'm pretty sure I already knew how to do.  I'd like to 
unmute the track after pattern 1, track 1, plays 12 times.  

So I set up Aux D with the event to unmask Aux B when n > AccD.  But 
there is no difference from when xD <= n. I set the number on the Aux = 
12, enable the aux event.  Every time I hit run, track 3 is unmuted.

I'm missing something very nooby, but I can't figure out what it is.  
AuxB (unmuting the track) happens on the every retrigger of pattern 1.  

Thoughts?

cheers,
eric f

ach_gott wrote:

> So I've figured out how to configure an Aux event (on Aux B) to unmute 
> a track which I'm pretty sure I already knew how to do.  I'd like to 
> unmute the track after pattern 1, track 1, plays 12 times.  

Using V4 (not sure if you are?), the absolute easiest way to do this is 
to have bar 1 play 12 times and have bar 2 contain your track unmute 
event. No need of accumulators.

> So I set up Aux D with the event to unmask Aux B when n > AccD.  But 
> there is no difference from when xD <= n. I set the number on the Aux = 
> 12, enable the aux event.  Every time I hit run, track 3 is unmuted.

The thing about accumulators is that they run from 0-127 but some of the 
events you are manipulating have other scales. So there are 8 tracks for 
example and you have to divide 128 by 8 to get the appropriate chunk (16 
in this case) so that each addition to the accumulator is equivalent to 
a track. Assuming that's what you want. I'm not totally sure what your 
above example looks like, could you say what each aux row is set to, 
what the values are, I'll try to recreate it. Or try the simpler example 
above. :)
Final thoughts: make sure the accumulator limit is set to the full range 
and its behaviour is what you want too. I think that stuff is well 
covered in the manual. The accumulator is a simple counter really but 
enormously useful because of the masking events and behavioural controls.

Hope this helps.

-- 
Paul
---
"Effectus super absolutionem"
http://www.JointIntelligenceCommittee.com
http://www.myspace.com/jointintelligencecommittee

Cool, thanks!  I'm using V3 still... one of these days I'll move up to V4 (and install my memory expansion). 
   
  So, as you might imagine, I'm conserving the patterns on my track... there are other ways to go about it, sure, but I'm also trying to get my head around combining the D accumulator with other events for use in the future.  I like the idea of timing global events, having a portion of a piece be a sequenced improvisation, that sort of thing.
   
  I appreciate Paul's help, but can anyone else advise.  To review (with a correction):
  =Track 3 is muted
  =Track 1 has Aux B = Unmute track 3.  Enabled on step 1.
  =Track 1 has Aux C = offset Dacc rel = +1.  Enabled on step 1.
  =Track 1, Aux D has Mask xB, Dacc >= n.  n=12.  Enabled on step 1
  But the track is unmuted regardless, in fact, I can .  As far as I understand it, the scaling Paul mentions doesn't apply to this type of event, correct?
   
  This is driving me mad!
   
  cheers,
  eric f

Softroom <softroom@btinternet.com> wrote:
  ach_gott wrote:

> So I've figured out how to configure an Aux event (on Aux B) to unmute 
> a track which I'm pretty sure I already knew how to do. I'd like to 
> unmute the track after pattern 1, track 1, plays 12 times. 

Using V4 (not sure if you are?), the absolute easiest way to do this is 
to have bar 1 play 12 times and have bar 2 contain your track unmute 
event. No need of accumulators.

> So I set up Aux D with the event to unmask Aux B when n > AccD. But 
> there is no difference from when xD <= n. I set the number on the Aux = 
> 12, enable the aux event. Every time I hit run, track 3 is unmuted.

The thing about accumulators is that they run from 0-127 but some of the 
events you are manipulating have other scales. So there are 8 tracks for 
example and you have to divide 128 by 8 to get the appropriate chunk (16 
in this case) so that each addition to the accumulator is equivalent to 
a track. Assuming that's what you want. I'm not totally sure what your 
above example looks like, could you say what each aux row is set to, 
what the values are, I'll try to recreate it. Or try the simpler example 
above. :)
Final thoughts: make sure the accumulator limit is set to the full range 
and its behaviour is what you want too. I think that stuff is well 
covered in the manual. The accumulator is a simple counter really but 
enormously useful because of the masking events and behavioural controls.

Hope this helps.

-- 
Paul
---
"Effectus super absolutionem"
http://www.JointIntelligenceCommittee.com
http://www.myspace.com/jointintelligencecommittee



------------------------------------

Yahoo! Groups Links






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

>   I appreciate Paul's help, but can anyone else advise.  To 
> review (with a correction):
>   =Track 3 is muted
>   =Track 1 has Aux B = Unmute track 3.  Enabled on step 1.
>   =Track 1 has Aux C = offset Dacc rel = +1.  Enabled on step 1.
>   =Track 1, Aux D has Mask xB, Dacc >= n.  n=12.  Enabled on step 1
>   But the track is unmuted regardless, in fact, I can .  As 
> far as I understand it, the scaling Paul mentions doesn't 
> apply to this type of event, correct?

The problem here is that you are trying to mask aux B using aux D.
The auxes are processed in order, so aux B has already taken effect when aux
D disables it.
You should use aux A to do the Mask xB.

It may be confusing that you are using the aux D accumulator, but not aux D.
The aux D accumulator value is added to the value for aux D unless it is
'disconnected' using the xDAcD option.
But the aux D accumulator value is *also* used in any threshold events, such
as 'Mask xB, Dacc>=n'.

Hope that helps.

Best regards,
Colin Fraser
Sequentix Music Systems Ltd
http://www.sequentix.com