[sdiy] weird poly800...kills patches when any sequencer run
Bob Weigel
sounddoctorin at imt.net
Tue Jan 22 19:55:14 CET 2008
Thanks Dan also. But I found the problem last night. The 'clock' and
other related settings there...parameters 86 and 87 or whatever all...I
think there were three things....had corrupted data in them :-) The
cure involved running the data down. It will only move down.
Eventually you see numbers and when you get to '2' then it will go to 1
and back to 2 if you hit up. Once those values are loaded everthing
works as it should it seems.
The bogus clock value was causing MIDI input to get the processor
totally lost such that it rewrote the SRAM data!
-Bob
George P. Macklin wrote:
> This issue has been there forever. If I remember correctly the only
> work around is to unplug the device prior to Clock Start messages.
> Real big hassle. Someone was recently working on a different OS for
> the Poly800 and this was one of the issues being fixed. I will try to
> hunt down the information.
>
> On Jan 22, 2008 4:19 AM, Bob Weigel <sounddoctorin at imt.net
> <mailto:sounddoctorin at imt.net>> wrote:
>
> internal or MIDI. What in the world is up with that. Just makes
> a big
> noise patch and all the patches have to be reloaded. I asked this a
> while back but will try once more before I start looking at
> signals. -Bob
> _______________________________________________
> Synth-diy mailing list
> Synth-diy at dropmix.xs4all.nl <mailto:Synth-diy at dropmix.xs4all.nl>
> http://dropmix.xs4all.nl/mailman/listinfo/synth-diy
>
>
>
>
> --
> George P. Macklin
> www.granularmatter.com <http://www.granularmatter.com>
> **Please consider the environment before printing this e-mail**
More information about the Synth-diy
mailing list