Analogue-sequencer

> firstly, when uploading the firmware via midiOX, with midi-in and -
> out connected to my pc, i got a continual 'BAD DATA' message. i had
> this twice, then i disconnected the midi-out and it worked fine. o i
> just realised this may be because i had 'sysex thru' on in midiOX..

That'll be it. It doesn't like looping sysex, since it ends up in a 'bad
data' loop.

> and secondly i'd like to know how a sysex-dump back to the p3 is
> supposed to end, as i now didn't get anything like a 'done' message.
> it just stopped receiving data and the display read 'abort' over f3.
> i hit abort and it all works fine and all parts & patterns are back
> in place, but it got me kinda nervous..

That's normal behaviour.
The sysex format doesn't have an 'end of file' message - each part and
pattern, and the FTS/bank data are sent as separate blocks. These can be
received in any number, and any order, so there is no end as such.
There are handshaking messages, so when I write the P3 memory manager
utility, it will confirm what's happening, and re-assure you that your
transfer was OK, as well as letting you move patterns between tracks and
banks, and replace individual patterns etc.

Cheers,
Colin f



________________________________________________
Message sent using UebiMiau 2.7.2