Yahoo Groups archive

Analogue-sequencer

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

Message

RE: [analogue-sequencer] P3 with a mind of it's own

2004-12-06 by Colin f

> > That sounds more like a hardware problem to me - something 
> causing the
> > memory to get corrupted.
> > Was only the one bank affected, or did others go weird too ?
> >

> No... Playing with them now....

Did you initialise the memory when you first powered your P3 up ?
Just wondering if there might have been random stuff in there that didn't
get deleted...

One point worth noting if it does turn out to be a hardware problem - the P3
pattern data amounts to 48k of RAM.
The notes, velocities, length, delay and gate/tie/skip/X bits are all held
in the lower half, and the auxes in the upper half of the 48k.
The physical memory is divided between two 32k RAM chips, so all 24k of the
note data is held in one chip, and there's an 8k/16k split of the aux data
between the two RAM chips. So if you had a problem with one RAM chip, it
could affect aux data without causing a problem with any of the notes. Was
the underlying note data OK after your incident, with just the auxes
affected ?
I'd take a regular sysex backup for a while, so you could compare the
contents of memory if there is more weirdness.

Cheers,
Colin f

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.