Yahoo Groups archive

Analogue-sequencer

Index last updated: 2026-04-28 23:15 UTC

Message

Re: [analogue-sequencer] little weirdnesses

2004-06-04 by Colin f

> i've got some strange stuff going on with the BTempo setting; i'm
> basically not able to set it anymore. every time i hit the 'BTempo'-
> softkey and then twist the knob to actually set the initial tempo my
> P3 automatically jumps back to Init tempo = off.

Odd. I'll check the latest fw build on mine and see if it does the same
thing.

> on the subject of tempo: how come the tempo setting jumps per 2 bpm
> above 150 and per 4 above 170? kind of annoying, that, as hardly
> anything i do is below 160..

The tempo knob is scaled to suit the tempo range I use most.
Between the range of 120 to 150 bpm, it actually steps 0.5 bpm per step,
although you can't see this on the display. Towards the little used
extremities, the steps get bigger, as you noticed.
The scaling is held in a lookup table for the 16 bit timer values and
numeric tempo value, so it could be changed easily, but there are only 128
possible tempo settings.
I might be able to produce a firmware patch with an alternative 'nosebleed'
tempo map ;-)
Or if there was a general consensus that less resolution was acceptable at
the extreme ends of the scale, I could adjust the map to extend the 'fine'
region over a larger area.

> another thing; how come the midi-thru and other user-config settings
> aren't stored in a sysex dump? is this because a sysex dump is only
> of the bank/pattern/part/playlist memory and not the actual OS's
> memory, where such stuff is stored?

I could add a block type to support 'general config' settings. It's missing
more due to lack fo time than any other reason. I guess it would be useful
to include the midi channel settings and user config in a dump.

Cheers,
Colin f



________________________________________________
Message sent using UebiMiau 2.7.2

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.