Analogue-sequencer

Hi Colin and group!

I finally upgraded to 3.1.006 this past week, practiced on it for a
couple of days and had 2 gigs last night, a solo gig at 7pm and a
TouchXtone gig at 11pm. So wanted to report back...

Installation went very smooth, updated the bootloader first.

Dived in without manual to start and was immediately flumoxed by the
aux selection process. Quickly scanned the manual, figured it out, and
am much happier with the new layout and selection process. Seems very
intuitive. I'm probably going to make a clear label overlay that fits
just under the pattern/track/part selection buttons to remind me what
auxes are on each button. But like that I can select '3' and that
random note is the top of the list. Bravo!

The new layout also motivated me to finally tackle accumulators a bit,
though I still forgot to use them at the gigs. I have a question about
accumulators: I seem to affect the entire pattern using acc rel, even
if I have only selected one note in a pattern to receive the
accumulator aux. Is this normal?

One other quirk I'm trying to track down: I'm having trouble getting
the P3 to set and store a BPM. On some banks, it takes me 2 or 3 times
trying to save the BPM for it to 'stick'. And on one bank, it just
will not set. Any ideas?

So, really nice job. I was just getting comfortable with 3.1.005 and
was a little afraid of the upgrade, but it couldn't have been a
smoother. In fact, the TouchXtone performance last night was amazing,
mostly because of my muse my P3. Tip of the day: Set your P3 tempo to
one half your musical partner's tempo (I was doing 50 bpm to his 100
bpm in Ableton Live).

Jim Combs wrote:
> The new layout also motivated me to finally tackle accumulators a bit,
> though I still forgot to use them at the gigs. I have a question about
> accumulators: I seem to affect the entire pattern using acc rel, even
> if I have only selected one note in a pattern to receive the
> accumulator aux. Is this normal?
>   
You have to protect notes that you don't want to accumulate. Imagine 
you've sent a MIDI Continuous Controller if you like: you send the value 
and this affects all future notes until a new value is sent.
> One other quirk I'm trying to track down: I'm having trouble getting
> the P3 to set and store a BPM. On some banks, it takes me 2 or 3 times
> trying to save the BPM for it to 'stick'. And on one bank, it just
> will not set. Any ideas?
>   
One for Colin - I use this all the time and it's just a matter of 
hitting the softkey for, say, BPM and then adjusting it with the data 
entry. When the value is the tempo you want, save it. This then takes 
over from any current tempo. Apologies if you knew that...

I'm just working with a new minimal setup featuring a P3, Monowave, 
Roland Dimensional Delay and Proteus 2000 and a little keyboard. Sweet 
and very self-contained...

Paul

---
www.softroom.co.uk / www.JointIntelligenceCommittee.com

--- In analogue-sequencer@yahoogroups.com, Paul Nagle <softroom@...>
wrote:
> One for Colin - I use this all the time and it's just a matter of 
> hitting the softkey for, say, BPM and then adjusting it with the data 
> entry. When the value is the tempo you want, save it. This then takes 
> over from any current tempo. Apologies if you knew that...

That is exactly what I'm doing, but for some reason, it acts like it
has saved, returns me to the top page, but it hasn't been saved, moves
of the tempo knob are recognized and nothing stored. The steps I take
are hit softkey, use tempo know to select tempo, hit save softkey,
then the behavior exhibits itself. Some operator error here?

-Jim

> -----Original Message-----
> From: analogue-sequencer@yahoogroups.com 
> [mailto:analogue-sequencer@yahoogroups.com] On Behalf Of Jim Combs
> Sent: 09 July 2006 23:58
> To: analogue-sequencer@yahoogroups.com

> The steps I take
> are hit softkey, use tempo know to select tempo, hit save softkey,
> then the behavior exhibits itself. Some operator error here?

The TEMPO knob always controls the tempo, so the DATA knob is used to set
the bank tempo value.
Otherwise you couldn't set the value without changing the current tempo.

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

Jim wrote:

>The steps I take
>are hit softkey, use tempo know to select tempo, hit save softkey,
>then the behavior exhibits itself. Some operator error here?

Sounds like the same trap I fell into for a while... then realized it was
the _data_ knob that set the tempo!

Cheers,

Mike.



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

> That is exactly what I'm doing, but for some reason, it acts like it
> has saved, returns me to the top page, but it hasn't been saved, moves
> of the tempo knob are recognized and nothing stored. The steps I take
> are hit softkey, use tempo know to select tempo, hit save softkey,
> then the behavior exhibits itself. Some operator error here?
> 
> -Jim

i'm having the exact same issue; if I switch from bank to bank while
the P3 is running it takes the stored tempo setting, but if i've just
started up the P3 it just takes the tempo the tempo-knob indicates,
even though the display shows the stored BPM setting. Also, if I have
the user-config option "lock btempo" set to on, and the tempo
indicated by the tempo knob is different to the stored setting, the
tempo indicated by the tempo knob is locked, and not the stored
setting.. And yes, I know the stored tempo needs to be set with the
data-knob and not with the tempo-knob.

grtz, Chiel

--- In analogue-sequencer@yahoogroups.com, "Colin Fraser" <colin@...>,
Paul, and Mike wrote:
> The TEMPO knob always controls the tempo, so the DATA knob is used
to set
> the bank tempo value.

I knew it had to be something blazingly simple I was missing.

Thanks all!

-Jim

--- In analogue-sequencer@yahoogroups.com, Paul Nagle <softroom@...>
wrote:
> You have to protect notes that you don't want to accumulate.

Do you protect notes by setting those notes to a zero (0) accumulation?

-Jim

Wish I could find a monowave!!

  ----- Original Message ----- 
  From: Paul Nagle 
  To: analogue-sequencer@yahoogroups.com 
  Sent: Sunday, July 09, 2006 1:38 PM
  Subject: Re: [analogue-sequencer] Finally upgraded to 3.1.006c


  Jim Combs wrote:
  > The new layout also motivated me to finally tackle accumulators a bit,
  > though I still forgot to use them at the gigs. I have a question about
  > accumulators: I seem to affect the entire pattern using acc rel, even
  > if I have only selected one note in a pattern to receive the
  > accumulator aux. Is this normal?
  > 
  You have to protect notes that you don't want to accumulate. Imagine 
  you've sent a MIDI Continuous Controller if you like: you send the value 
  and this affects all future notes until a new value is sent.
  > One other quirk I'm trying to track down: I'm having trouble getting
  > the P3 to set and store a BPM. On some banks, it takes me 2 or 3 times
  > trying to save the BPM for it to 'stick'. And on one bank, it just
  > will not set. Any ideas?
  > 
  One for Colin - I use this all the time and it's just a matter of 
  hitting the softkey for, say, BPM and then adjusting it with the data 
  entry. When the value is the tempo you want, save it. This then takes 
  over from any current tempo. Apologies if you knew that...

  I'm just working with a new minimal setup featuring a P3, Monowave, 
  Roland Dimensional Delay and Proteus 2000 and a little keyboard. Sweet 
  and very self-contained...

  Paul

  ---
  www.softroom.co.uk / www.JointIntelligenceCommittee.com 



   

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

> That is exactly what I'm doing, but for some reason, it acts like it
> has saved, returns me to the top page, but it hasn't been saved, moves
> of the tempo knob are recognized and nothing stored. The steps I take
> are hit softkey, use tempo know to select tempo, hit save softkey,
> then the behavior exhibits itself. Some operator error here?

hi,
i'm having a similar issue. When I store a tempo-setting as being the
default tempo using Btempo (setting it using the Data-knob, not the
Tempo-knob), it acts like the tempo has been stored, but when I hit
play it takes the tempo from the tempo knob instead of the stored
tempo, even though the display shows the stored tempo setting. When I
set the "Lock Btempo" setting to on, it locks the tempo indicated by
the tempo knob instead of the setting stored as Btempo. When switching
banks with the P3 running the tempo switches to the the stored setting
for the new bank, like it's supposed to, but when the P3 is stopped
and I hit play it takes the tempo from the tempo knob again. 

grtz, Chiel

> if i've just
> started up the P3 it just takes the tempo the tempo-knob indicates,
> even though the display shows the stored BPM setting. Also, if I have
> the user-config option "lock btempo" set to on, and the tempo
> indicated by the tempo knob is different to the stored setting, the
> tempo indicated by the tempo knob is locked, and not the stored
> setting.. And yes, I know the stored tempo needs to be set with the
> data-knob and not with the tempo-knob.

I'll check that out today...
Sounds like there needs to be an extra check at startup to recall the bank
tempo.

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

On Mon, 10 Jul 2006 13:18:49 -0000, "Jim Combs"
<jwcombs@bellsouth.net> wrote:

>--- In analogue-sequencer@yahoogroups.com, Paul Nagle <softroom@...>
>wrote:
>> You have to protect notes that you don't want to accumulate.
>
>Do you protect notes by setting those notes to a zero (0) accumulation?

No, accumulation affects every subsequent note unless you use the
specific aux event to prevent accumulation or the Xd row which
prevents (pitch) transposition. 

To better understand the accumulators, think of their effect on note
sequences as like a MIDI CC. Imagine you set mod wheel value to zero
on step one of a sequence and a value of 24 on step 8. The first part
of the sequence has no modulation present on *any* notes, even though
you only set the value once. Then for the second half you get a mod
value of 24 for all notes, until the end of the pattern.

In our example, the next time the pattern restarts, modulation is
reset to zero and the same thing is repeated ad infinitum.

To show how accumulators are clever/different, imagine a looping
pattern where you set the accumulator values to 0 and 24 as above. An
accumulator value of zero does nothing so the first half of the
pattern plays as expected. When you reach the value of 24, that step
and any subsequent steps are transposed two octaves. When the pattern
restarts, the zero is ignored again (dumb example eh?) because adding
zero to the accumulator makes no difference. (So all the notes are
still playing 2 octaves above normal. Had this step 1 value been other
than zero, it would be added to the accumulator value at this point).
Naturally, when it now reaches step 8, 24 is added again making *all*
notes now 48 semitones above normal (subject to accumulator behaviour
rules).

You can do groovy things by conditionally masking accumulator values
so that different values are added to the accumulator at different
steps. Or randomising the accumulator value. etc. <g>

Does this help?

Paul


---
Paul Nagle - Joint Intelligence Committee - www.JointIntelligenceCommittee.com
                           SoftRoom Music - www.softroom.co.uk