Factory reset the unit first then try to load the file. Try another sysex file. If it stops in the same place or the factory reset takes a long time then you may have a flash memory problem. The unit writes to flash and waits for the chip to return from the write process before writing another byte. Faulty flash may be increasing the write time. Flash memory is good because it doesn't need a lithium battery to store the information, but it wears out. The early flash only had about 100,000 writes on average. I'm not sure what the P2k uses but the 100k is an average so there will be some chips that bomb out sooner. You have to be carefully about the sysex in the P2k as it can write directly to the flash RAM and if you are happily changing stuff all the time eventually it will fail. There is an edit buffer in the P2k that is RAM, not flash, that you can write to as many times as you like. Unfortunately I can't find a buffer for the Arpeggiator so when you are changing the User Arps with, say, Prodatum you are writing to the flash. If anyone knows the address of the Arp buffer please let me know. All the best Royce --- In xl7@yahoogroups.com, "Ricard" <ricard2010@...> wrote: > > > It seems that there's either an error in the files, or I'm doing something very wrong. If I reboot the XL-7, it appears to load the patches up until patch 37 (I'm downloading bank 0), then the 'Sysex: too fast' message appears. Apparently this makes the XL-7 confused, because afterwards all patch downloads are met with the 'Sysex: too fast' message. > > Furthermore, the patches don't seem to be correct in that the Sample number is set to 0 = NONE for at least the few that I've tried. > > Strange, I've got a Composer ROM in my XL-7 which I extracted from a P2000, so it should be the correct ROM for these patches. Or have I misunderstood what the patch files are for? >
Message
Re: Sysex too fast?
2013-03-07 by Royce
Attachments
- No local attachments were found for this message.