Analogue-sequencer

>  I know I was one of the people asking for all this
> stuff, but I'm having as hard a time keeping up with it as you must be
> having keeping the manual up-to-date.

The general idea is to release an updated manual describing all new feature
at the same time as a beta firmware build becomes a release version. The
current manual is half way through having an index added too, which is a bit
of a pain (much like doing anything in Word...)

> never one to complain about something without proposing a solution,
> here's my solution:
> go through y'r "sent mail" folder & find all the emails you've sent to
> the group about updates. c&p them into a text file & stick it on the
> site instead of/aswell as the revision history.
> then we'd not only know /when/ a function appeared, but we'd know how
> to use it even if we hadn't been paying attention to the list.
> whaddya reckon?

Mr Nagle is pretty good at updating the user guide when something worthwhile
appears, even in a beta.
I could try adding more detail to my revision history. That's the file I
work from when I'm updating the manual.
Keeping more files in sync sounds like yet more work for me.
If I were to update something more often, it would probably be easier to
have a beta manual release to go with the firmware.

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