Analogue-sequencer

Folks,

P3 v3.89 beta is in the files section.
This version needs a sysex backup/restore before/after installation 
as I had to move some of the pattern data around to fit things in.

It adds a new sub-menu to configure the accumulators per pattern.
You'll find the 'Acc conf' option on the last pattern edit page, 
next to 'Apply FTS'.
The accumulators are probably due a bit more explanation by now...

There are 3 accumulators per track - for note, velocity and aux D.
Each time a new pattern is selected, or the sequencer is restarted, 
all three accumulators are reset to zero.

The accumulator values are added to the note, velocity or aux D 
values before each note or cc message is sent.
So unless you modify the value of the accumulators with an aux 
event, they have no effect.
If this sounds complicated, feel free to give up now.

The aux events used to modify the accumulators are the
 'offset abs ...'
and
 'offset rel ...'
events.
'offset abs ...' sets an accumulator to a specific value in the 
range 0 to 127.
'offset rel ...' allows you to add a value in the range -64 to +63 
to the current accumulator value.
So if you have 'offset velo rel', with a value of +1 on each step, 
the accumulator value will increase by one as each step plays - 
offsetting the stored values of velocity transmitted on each step as 
it does.

But things get a bit more complicated... ;-)
There are 3 options that control the behaviour of the accumulator.
The first of these is 'limit', which has a range of 0 to 127.
This sets the maximum *absolute* value the accumulator can reach.
Each accumulator can have a positive or negative value between plus 
and minus 'limit'. If you apply a negative offset to an accumulator 
that is already 0, it will become negative - so the resulting value 
of note, velo or aux D sent will be lower than the stored value.
When the accumulator reaches 'limit', what it does next will depend 
on the 'accumulator limit behaviour'. This option (shown as 'A:' in 
the UI) can take the following settings:

 rtz  = return to zero
 clip = stop at the limit and go no further
 rvrs = rebound from the limit and reverse direction

Reverse has the added effect that any future offsets to the 
accumulator will be inverted until the limit is reached again 
(typically the limit at the opposite end of the accumulator travel).

The final option is the 'result behaviour' (shown as 'R:' in the UI).
This can be set to 'clip' or 'wrap'.
This option defines what happens when the *result* of the stored 
value plus the accumulator value is out of range - e.g. if the total 
velocity is greater than 127 or less than 0.
A setting of 'clip' limits the result to the valid range.
A setting of 'wrap' folds the value back into the other end of the 
valid range.

So, here's a quick example, which may makes things a bit clearer:

Set up a note pattern as usual.
Then configure aux A to 'offset note rel'.
Set a value on step 1 of the pattern for aux A of +12.
Go to the 'acc conf' menu - on entry it will display the note 
accumulator settings for the pattern.
You can access the settings for the other two accumulators using the 
PAGE key.
Use the DATA knob to set the note acc limit to 24.
Use F1 to select A:rtz, and F2 to select R:clip if they are not 
already set. Then press F3 to confirm the settings.
Now start the pattern.

Intially the note accumulator value will be 0, but on the first 
step, it will have +12 added.
So the pattern will play transposed up by 12 semitones, then 24.
At the next offset of +12, the limit of 24 is exceeded.
Since 'A:' is set to rtz, this means the accumulator will reset to 0.

So, as the pattern loops, it will play transposed by 12, 24, 0, 12, 
24, 0, ... and so on.
If you now enter 'acc conf' again, and change A: to 'clip', the 
accumulator will rise to 24, then stick there until a different 
pattern is selected, or playback is restarted.
Setting A: to 'rvrs' will cause the accumulator to oscillate around 
0.
The transpose of each loop of the pattern will be:
+12, +24, +12, 0, -12, -24, -12, 0, +12, ... and so on.

If you're feeling experimental, give it a try and let me know how 
you get on ;-)

Cheers,
Colin f

> the one thing that confuses me about this is the duration of 
> the effect...
> in your example, the pattern is transposed +/-12 each time it 
> plays... so
> in the above example if all stored vel values are 100, does 
> it progress
> like: 101, 102, 103... 116? or does it just change the velocity to 101
> each time? i imagine "rel" would increase each step and "abs" 
> would just
> add the value to the *stored* value, with no "accumulation". is that
> accurate?

That's right. 'abs' seems to be somewhat redundant - but there are uses
for it I'll spare you the details of until you get a hang of the basics
;-)
Once the value in an accumulator is set, it will be added to it's
associated value in all following steps.
So on every step (where X is not set, and ignoring result wrap/clip):

transmitted note number = force to scale ( step note number + part Xpos
+ playlist step xpos + note accumulator )

transmitted velocity = step velocity + velocity accumulator

transmitted aux D value = step aux D value + aux D accumulator

Note that if you have aux D set to an aux event rather than a midi
controller, the accumulator will modify the operand of that event. So
for example, you might grab notes from other tracks with aux D, using
aux C to sweep aux D back and forth across the other tracks by
offsetting the aux D accumulator. While simultaneously arpeggiating the
result with the note accumulator. And sweeping the filter like a clock
synced LFO using the velocity accumulator.

Cheers,
Colin f

On Tue, 2 Mar 2004, colinfraser_com wrote:

> So if you have 'offset velo rel', with a value of +1 on each step,
> the accumulator value will increase by one as each step plays -
> offsetting the stored values of velocity transmitted on each step as
> it does.

the one thing that confuses me about this is the duration of the effect...
in your example, the pattern is transposed +/-12 each time it plays... so
in the above example if all stored vel values are 100, does it progress
like: 101, 102, 103... 116? or does it just change the velocity to 101
each time? i imagine "rel" would increase each step and "abs" would just
add the value to the *stored* value, with no "accumulation". is that
accurate?

bleep.
out.

---
http://leichenfeld.iuma.com
http://thirdwavecollective.com

Colin,

> The aux events used to modify the accumulators are the
>  'offset abs ...'
> and
>  'offset rel ...'
> events.
> 'offset abs ...' sets an accumulator to a specific value in the 
> range 0 to 127.
> 'offset rel ...' allows you to add a value in the range -64 to +63 
> to the current accumulator value.

blimey, you trying to turn everyone into assembly language programmers?

Paul

On Tue, 2 Mar 2004 15:13:33 -0600 (CST), blip <bleep@waste.org> wrote:

>the one thing that confuses me about this is the duration of the effect...
>in your example, the pattern is transposed +/-12 each time it plays... so
>in the above example if all stored vel values are 100, does it progress
>like: 101, 102, 103... 116? or does it just change the velocity to 101
>each time? i imagine "rel" would increase each step and "abs" would just
>add the value to the *stored* value, with no "accumulation". is that
>accurate?

The accumulator is increased/decreased each time it is called. So if
you have a pattern that is 4 steps long and step one is a rel
transpose of +1, each time the pattern plays it will transpose by a
semitone. If you put a transpose of +1 on step 3 also, it will go up
at that point in addition to the previous increase.

Try masking the transpose events, perhaps by randomness, and see how
interesting it can get. Remember each step can transpose positive or
negative in the same pattern and you can use X to prevent
transposition of certain steps. Tip: if you do everything with FTS
active, it might be a good idea to apply the FTS to the pattern data
so that when you choose the steps to X you don't get stuff that's out
of tune.

Nurses, gimme nurses...

Paul

---
Paul Nagle / Soft Room Music
Email: paul@softroom.co.uk www.softroom.co.uk
                           www.BogusFocus.com

> blimey, you trying to turn everyone into assembly language 
> programmers?

Not quite. It does all tend to sound a bit programmatic, but it gives
you a lot of scope.
With any luck Paul N will waste his holidays coming up with some mind
addling examples ;-)

Cheers,
Colin f

On Tuesday 02 March 2004 23:33, Paul Maddox (Mail Lists) 
wrote:
> Colin,
>
> > The aux events used to modify the accumulators are the
> >  'offset abs ...'
> > and
> >  'offset rel ...'
> > events.
> > 'offset abs ...' sets an accumulator to a specific
> > value in the range 0 to 127.
> > 'offset rel ...' allows you to add a value in the range
> > -64 to +63 to the current accumulator value.
>
> blimey, you trying to turn everyone into assembly
> language programmers?

LOL! :)
Reading over Colin's blurb again, I gotta admit that this 
looks like an excerpt of my old 6502 manual. :))

- Robert

On Wednesday 03 March 2004 00:22, Colin f wrote:
> > blimey, you trying to turn everyone into assembly
> > language programmers?
>
> Not quite. It does all tend to sound a bit programmatic,
> but it gives you a lot of scope.
> With any luck Paul N will waste his holidays coming up
> with some mind addling examples ;-)

I'm *sure* it will sound great Colin. With the introduction 
of the aux events, the P3 has changed into a very, very 
powerful and unique tool. 

Now I want a 32 track version, with 2 MIDI outputs, heh.

- Robert

On Tue, 2 Mar 2004 23:22:33 -0000, "Colin f" <colin@colinfraser.com>
wrote:

>With any luck Paul N will waste his holidays coming up with some mind
>addling examples ;-)

There's luck but is it good? A couple of new examples in the usual
place showing simple note accumulation and controller accumulation.

Number 31 feaures about 6 tracks with some kind of accumulation on
most of them, also switching to different patterns in a playlist, each
pattern having different accumulation settings. Practially impossible
to tell, of course <g> - this piece is the short version cos I got
really self-indulgent later (no, really).

Number 32 features just one synth - with simple note accumulation and
also an accumulated variation in its VCA envelope decay time. Should
be a little easier to appreciate what's going on in this one.... 

Simple pleasures...

Paul
---
Paul Nagle / Soft Room Music
Email: paul@softroom.co.uk www.softroom.co.uk
                           www.BogusFocus.com

--- In analogue-sequencer@yahoogroups.com, "colinfraser_com"
<colin@c...> wrote:
> Folks,
> 
> P3 v3.89 beta is in the files section.
> This version needs a sysex backup/restore before/after installation 
> as I had to move some of the pattern data around to fit things in.
> 
Sorry my silly Question, but what do you mean exactly with:
"sysex backup/restore before/after installation" ???
Do you mean that i should make sysex dump of my existing os before i
dump the new one to it, then dump the new one back to the computer and
back again? Hääh??? 
Sorry again, what sall i do?
Don't laugh to loud...., folks.
Stefan

Thanks, uups, now i got it. I was thinking that it was something much
deeper thatn that. Shame on me, and thanks again.
Stefan

--- In analogue-sequencer@yahoogroups.com, Robert van der Kamp
<robnet@w...> wrote:

> On Wednesday 03 March 2004 19:06, privat_joy wrote:
> > --- In analogue-sequencer@yahoogroups.com,
> > "colinfraser_com"
> >
> > <colin@c...> wrote:
> > > Folks,
> > >
> > > P3 v3.89 beta is in the files section.
> > > This version needs a sysex backup/restore before/after
> > > installation as I had to move some of the pattern data
> > > around to fit things in.
> >
> > Sorry my silly Question, but what do you mean exactly
> > with: "sysex backup/restore before/after installation"
> > ??? Do you mean that i should make sysex dump of my
> > existing os before i dump the new one to it, then dump
> > the new one back to the computer and back again? Hääh???
> > Sorry again, what sall i do?
> > Don't laugh to loud...., folks.
> > Stefan
> 
> If you want to keep your song data, you have to backup it 
> before you upgrade the OS, and restore it afterwards. The 
> procedure is described in the manual, IIRC.
> 
> - Robert

> If you want to keep your song data, you have to backup it 
> before you upgrade the OS, and restore it afterwards. The 
> procedure is described in the manual, IIRC.

I try to avoid requiring this if I can - but in the last update, I've
moved the pattern length data to a new location.

Cheers,
Colin f

On Wednesday 03 March 2004 19:06, privat_joy wrote:
> --- In analogue-sequencer@yahoogroups.com,
> "colinfraser_com"
>
> <colin@c...> wrote:
> > Folks,
> >
> > P3 v3.89 beta is in the files section.
> > This version needs a sysex backup/restore before/after
> > installation as I had to move some of the pattern data
> > around to fit things in.
>
> Sorry my silly Question, but what do you mean exactly
> with: "sysex backup/restore before/after installation"
> ??? Do you mean that i should make sysex dump of my
> existing os before i dump the new one to it, then dump
> the new one back to the computer and back again? Hääh???
> Sorry again, what sall i do?
> Don't laugh to loud...., folks.
> Stefan

If you want to keep your song data, you have to backup it 
before you upgrade the OS, and restore it afterwards. The 
procedure is described in the manual, IIRC.

- Robert

Hi Colin,

OK, some weird sh*t going on here!

I just loaded V3.89, and did a data clear.

Selecting pattern edit mode, page 2, which should be the pattern direction page, the 
menu indicates CC#8, where the pattern direction should be. Incrementing with F2 
increases the cc number up to 127, then starts into the accumulator menu (note grab 
etc).

Whilst in this menu, the pattern is only 1 step long regardless of where edit last is set. 
F1 decreases the CC value down to cc#0, then to brownian from where the track then 
works normally and pattern direction can now be selected.

This is the same for every track.

As I said, I did take the precaution of wiping all data both before and after loading 
V3.89.

I also reloaded the OS. Checksum is CA0B.

Reverting back to V3.88 appears OK

<paranoid>

Is it just happening to me??

/<paranoid>

Thanks

Andy
--
Andy Wilson
http://www.techman.synth.net
mailto:andy@techman.synth.net

> I just loaded V3.89, and did a data clear.
> 
> Selecting pattern edit mode, page 2, which should be the 
> pattern direction page, the 
> menu indicates CC#8, where the pattern direction should be. 
> Incrementing with F2 
> increases the cc number up to 127, then starts into the 
> accumulator menu (note grab 
> etc).

Sounds like a f#cked up string pointer. I no longer have that build, so
I can't confirm or deny it, but the version I'm currently at doesn't do
this, so I'll upload it now.

Cheers,
Colin f

Hi Colin

> Sounds like a f#cked up string pointer. I no longer have that build, so
> I can't confirm or deny it, but the version I'm currently at doesn't do
> this, so I'll upload it now.
> 

Thanks. Loaded V3.892.
Well at least I don't see CC# anymore, but entering the pattern edit page 2 menu 
comes up with Grab nte+A trk n and F1& F2 step through the aux functions. It's not 
until I see a legitimate direction that the track works properly :-<

All the best

Andy

--
Andy Wilson
http://www.techman.synth.net
mailto:andy@techman.synth.net

> Well at least I don't see CC# anymore, but entering the 
> pattern edit page 2 menu 
> comes up with Grab nte+A trk n and F1& F2 step through the 
> aux functions. It's not 
> until I see a legitimate direction that the track works properly :-<

Aha. I think I know what the trouble is. You must have direction values
that are out of range.
How they got to be out of range, I can't tell.
I'll need to check an old dump from mine to see if it's the sysex load
that's doing it.

Cheers,
Colin f

> > Well at least I don't see CC# anymore, but entering the 
> > pattern edit page 2 menu 
> > comes up with Grab nte+A trk n and F1& F2 step through the 
> > aux functions. It's not 
> > until I see a legitimate direction that the track works properly :-<

Well, I can't repeat this effect here. Anyone else getting this ?
Andy, what version were you on before ?
Did you do the sysex dump, then the firmware upgrade, then a wipe, then
a sysex re-load ?
Or some other order ?

BTW The aux event name strings are defined in memory after the direction
names - so the reason you are seeing aux event names is because a
direction string array entry larger than the number of directions will
show an aux event name.

Cheers,
Colin f

> this is the only PLED display i found in the states... none 
> of the major
> distributors seem to carry them. i'm curious as to whether 
> this will work,
> because i can't find the model colin recommends on the farnell site...
> 
http://www.onestopdisplays.net/1%20page%20Specs%20(OSD)/OSD1602%20rev091
103.pdf

That looks very similar to the Farnell part, so it should be fine.
I'll check the dimensions out properly just to make sure it will mount
in the same case layout, but the key thing from the electronic point of
view is the HD44780 compatibility.

Cheers,
Colin f

i think great britain is pulling some colonial strings because for some
reason things are more available there than here in her big-ass colony...

anyway...

this is the only PLED display i found in the states... none of the major
distributors seem to carry them. i'm curious as to whether this will work,
because i can't find the model colin recommends on the farnell site...

http://www.onestopdisplays.net/1%20page%20Specs%20(OSD)/OSD1602%20rev091103.pdf

bleep.
out.

---
http://leichenfeld.iuma.com
http://thirdwavecollective.com

> I'll check the dimensions out properly just to make sure it will 
mount
> in the same case layout

Physical dimensions on the datasheets are identical too, so this 
part looks ideal.

Cheers,
Colin f

On Wed, 3 Mar 2004 21:51:46 -0000, "Colin f" <colin@colinfraser.com>
wrote:

>Well, I can't repeat this effect here. Anyone else getting this ?

Fine here - been giving it some hammer for much of the day without a
hiccup.

Paul


---
Paul Nagle / Soft Room Music
Email: paul@softroom.co.uk www.softroom.co.uk
                           www.BogusFocus.com

> Fine here - been giving it some hammer for much of the day without a
> hiccup.


same here; nothing weird happening that's not supposed to be 
happening...

grtz Chiel

Hi Colin,

Sorry, had to go and do something else last night, so went offline.

> Andy, what version were you on before ?

I was running V3.88

> Did you do the sysex dump, then the firmware upgrade, then a 
wipe, then
> a sysex re-load ?
> Or some other order ?

I had nothing worth keeping at that time, so I just loaded V3.89 over 
3.88 then did a memory wipe.

That's when the problem first appeared. Reloading V3.88 seemed to 
work fine. When you posted V3.892, I first did a memory wipe on 
V3.88, loaded 3.892 OS, then did another memory wipe.

When I loaded 3.892, over I first did a memory wipe.

I'm wondering if there is still some crapola in the RAM somewhere 
which isn't being cleared by the memory wipe. Tonight I will remove 
the battery back up and reload the latest OS. I'll keep you posted on 
what I find.

All the best

Andy
---

Andy Wilson
http://www.techman.synth.net
andy@techman.synth.net

On Wed, 3 Mar 2004, colinfraser_com wrote:

> > I'll check the dimensions out properly just to make sure it will
> mount
> > in the same case layout
>
> Physical dimensions on the datasheets are identical too, so this
> part looks ideal.

i contacted their sales dept. via email yesterday asking about a single
display, but haven't heard back. if any US builders are interested in
using this display, please send me an email. i'd be willing to buy
displays for everyone in the US, have them shipped to me, then ship
them out to all of you. maybe they'll listen better when i want to
buy a lot of them...

bleep.
out.

---
http://leichenfeld.iuma.com
http://thirdwavecollective.com

At 09:14 AM 3/4/04 -0600, you wrote:

>i contacted their sales dept. via email yesterday asking about a single
>display, but haven't heard back. if any US builders are interested in
>using this display, please send me an email. i'd be willing to buy
>displays for everyone in the US, have them shipped to me, then ship
>them out to all of you. maybe they'll listen better when i want to
>buy a lot of them...


I'd be interested in buying one.  Email me off-list so we can discuss the
details. 

Dave Magnuson
resfreq@hoohahrecords.com

Resonant Frequency:
resfreq@hoohahrecords.com
http://www.hoohahrecords.com/resfreq/index.html

  ----------


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.598 / Virus Database: 380 - Release Date: 2/28/04


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