Analogue-sequencer

> Is this the prototype? (got any spares?;-)

It is a prototype.
The step board is likely to be final, but I may decide to alter the layout
or number of keys on either side of the display.

> It looks small, I expected it bigger.

Guid gear gangs in sma bulk.

> Those rotary encoders look very
> professional.  Maybe you could post a high res pic?

I'll post some more once the case is complete.
It doesn't even have its tempo and A/B control knobs yet, or labels on the
upper UI area.
The step knobs are indeed encoders, 30-indent ALPS units, with centre push.

> Do you have a current "function' list?

At the moment, it is running a ported version of P3 OS v4.5, which is
essentially the same as v4.0, but with a free pool of patterns for each bank
instead of a fixed relationship between patterns and part/track locations.
The cirklon build also has a fundamental change in the way the tempo is
generated, which greatly increases the usable range, makes multiple
simultaneous tempi easy to do, and allows events to be scheduled based on
tempo or linear time references, or both. e.g. track offset in steps of ms,
step repeats in divisions of tempo, or units of time.
There is quite a list of further changes and additions still to be made.
Functions may come and go based on user testing, so I'd rather not give an
exhaustive list yet.
Hopefully it'll be a bit further on by the time I take it to Cambridge for
Synth DIY.

The main hardware platform is certainly final.
It's running on a ST Cortex-M3 processor by ARM, a 72MHz 32-bit
microcontroller, with multiple hardware UARTS (4 of which are usable), USB,
SD-card support, and all sorts of other nice things that make programming
for the MCS81 seem like a bad dream.

> And most important, when will it be available and at what 
> price. (I'll start
> saving now!)

At the moment I'm considering whether to do a small pre-production run, for
adventurous beta testing types.
The timescale to availability depends on when I decide I'm happy enough with
the OS to be able to sell production units as 'complete'.
OS testing and debugging goes a lot more quickly with other people
stress-testing things.
I don't want to be selling them on the basis of promised features, so a
pre-production run would be sold on the understanding that the OS wont be
feature complete, and there may be a fair amount of debugging to be done.
But of course, as a beta tester, you'd have a greater say in how the final
product might turn out.

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