Analogue-sequencer

Folks,

The new build in files now *REQUIRES THE BOOTLOADER UPDATE*.
This image is bigger than the maximum originally supported, so the 
bootloader must be relocated higher in memory.
The bootloader update is also in files, and is just loaded as a 
normal image, performs the update, and the should be over-written 
with the new main program.
See 'bootloader update.txt' for details.
If you try to apply the firmware image without the later bootloader, 
it should simply show a 'bad block' error when it receives the 
blocks outside the original limit.

The new build now has a separate setting for FTS on the midi thru - 
previously the record mode FTS enable setting applied at all times.
FTS on midi thru is toggled using FUNC+thru, with an 'F' shown in 
front of the thru channel if FTS is active.

The new build adds some aux events:
    set rep*n note+    - sets a note offset for 'rep*n by length'
    set rep*n velo+    - sets a velocity offset for 'rep*n by length'
    set note acc lim   - sets the note accumulator limit
    set velo acc lim   - sets the velocity accumulator limit
    set auxD acc lim   - sets the aux D accumulator limit

There are also variants of the 'mask ???, dAcc>n' events that mask 
on 'n>dAcc', i.e. the opposite condition.

I've also added some extra code to allow me to re-order the aux 
event list without needing to re-assign events in existing patterns.
When you go to select an event you'll find the list is in a more 
logical order.

Cheers,
Colin f

> The new build in files now *REQUIRES THE BOOTLOADER UPDATE*.

Note that if you have got your ready-built P3 from me since September, it
already has the current bootloader.

Cheers,
Colin f

this FTS-on-none-record-midi-through..... does it work on any/all 
channels that happen to be arriving at the p3? are they despatched 
onwards all FTS'ed?

r.m.i. are in the final stages of production of a new album, for 
release by cuneiform early next year. we used the p3 a lot on this 
album, not just for the traditional strings of pulses but also for 
looping keyboard phrases, created using the live track record mode.
has anyone else used the p3 on a commercial release? we might put 
#73's picture in the sleeve somewhere...

d.

> this FTS-on-none-record-midi-through..... does it work on any/all 
> channels that happen to be arriving at the p3? are they despatched 
> onwards all FTS'ed?

If the thru channel is set to 'F-any', all notes will be FTS'd and passed on
their original channel.
This is the same as it was - it was just that the FTS setting for record
mode also applied during play mode.
 
> we might put 
> #73's picture in the sleeve somewhere...

That would be nice ;-)

Cheers,
Colin f

> r.m.i. are in the final stages of production of a new album, for 
> release by cuneiform early next year. we used the p3 a lot on this 
> album, not just for the traditional strings of pulses but also for 
> looping keyboard phrases, created using the live track record mode.
> has anyone else used the p3 on a commercial release? 

welll...not really commercial as we never do more than about 500 
records which remain in the 'underground' circuit mostly and we don't 
really make any profits to speak of, but my track and the combined 
track on KXstarter 2008 are mostly P3-sequenced (check 'em out on 
http://kxstarter.freetekno.nl ). i've got another 12" coming soon on 
a sub-label on which my tracks are mostly P3'ed. 
the method which works best for me is to just record all the midi 
output from the P3's to Cubase in several live sessions of about 15 
minutes, using one bank (1 bank = 1 track in my case). i then cut & 
paste these vertically to build an actual track out of the best bits 
of the sessions. vertical cuts across all tracks only, so i can keep 
the live performance-feel. 

grtz Chiel