Analogue-sequencer

I get a Bad Block Error when trying to receive SysEx data, I'm
assuming I have the wrong setup with the sending program. 

My setup from sending program is as follows: 
Midi Block Size 1024, Count 64, Delay 200

Ive set the delay to 200 as the manual states that the flash needs
100ms to write each sysex block however can someone advise the correct
block/count sizes.

Thanks
Roger

Colin,

> First thing to check is that you don't have a midi loop.
> If the 'ack' from P3 is looped back round to P3, it'll give a bad block
> message.

I only have a cable into the input midi connection, so Im not sure
what you mean by 'ack' loop?

> > My setup from sending program is as follows: 
> > Midi Block Size 1024, Count 64, Delay 200
> 
> I'm not sure what those parameters mean. Is your program putting a 200ms

Yes, it does appear insert a 200ms delay, I dont know what the other
params are either - just trying to find a solution? For what its worth
the Bad Block X! message appears immediatly the message starts

Thanks
Roger

--- In analogue-sequencer@yahoogroups.com, "Colin f" <colin@c...> wrote:

> Roger,
>  
> > I get a Bad Block Error when trying to receive SysEx data, I'm
> > assuming I have the wrong setup with the sending program. 
> 
> First thing to check is that you don't have a midi loop.
> If the 'ack' from P3 is looped back round to P3, it'll give a bad block
> message.
>  
> > My setup from sending program is as follows: 
> > Midi Block Size 1024, Count 64, Delay 200
> 
> I'm not sure what those parameters mean. Is your program putting a 200ms
> delay after every F7 ?
> 
> Cheers,
> Colin f

Roger,
 
> I get a Bad Block Error when trying to receive SysEx data, I'm
> assuming I have the wrong setup with the sending program. 

First thing to check is that you don't have a midi loop.
If the 'ack' from P3 is looped back round to P3, it'll give a bad block
message.
 
> My setup from sending program is as follows: 
> Midi Block Size 1024, Count 64, Delay 200

I'm not sure what those parameters mean. Is your program putting a 200ms
delay after every F7 ?

Cheers,
Colin f

Paul,

I recently completed construction of my P3 and I was intending to
learn more of it operationally by loading your sysex demo file!

However, in an effort to troubleshoot, when I got the bad block
message (trying to load the demo file) i did a sysex dump from the P3
then I was trying to reload that sysex dump but I get the same Bad
Block message.

Very confused
Roger

--- In analogue-sequencer@yahoogroups.com, Paul Nagle <softroom@b...>
wrote:
> On Thu, 14 Apr 2005 15:59:48 -0000, "makedosh" <makedosh@y...>
> wrote:
> 
> >Yes, it does appear insert a 200ms delay, I dont know what the other
> >params are either - just trying to find a solution? For what its worth
> >the Bad Block X! message appears immediatly the message starts
> 
> What sort of sysex data is it - a backup of some of your own
> sequences? I could try it here if you like.
> 
> Paul
> 
> ---
> Paul Nagle / Soft Room Music
>  www.softroom.co.uk
>  www.BogusFocus.com
> 
> ** Binar's Project Poltergeist and Headshock's MFPE available direct
from the Bogus site NOW. **

On Thu, 14 Apr 2005 15:59:48 -0000, "makedosh" <makedosh@yahoo.com>
wrote:

>Yes, it does appear insert a 200ms delay, I dont know what the other
>params are either - just trying to find a solution? For what its worth
>the Bad Block X! message appears immediatly the message starts

What sort of sysex data is it - a backup of some of your own
sequences? I could try it here if you like.

Paul

---
Paul Nagle / Soft Room Music
 www.softroom.co.uk
 www.BogusFocus.com

** Binar's Project Poltergeist and Headshock's MFPE available direct from the Bogus site NOW. **

On Thu, 14 Apr 2005 17:09:20 -0000, "makedosh" <makedosh@yahoo.com>
wrote:

>I recently completed construction of my P3 and I was intending to
>learn more of it operationally by loading your sysex demo file!

Ah, well I'm told it can equally lead to bewilderment.

>However, in an effort to troubleshoot, when I got the bad block
>message (trying to load the demo file) i did a sysex dump from the P3
>then I was trying to reload that sysex dump but I get the same Bad
>Block message.

Hmmmm, one for cleverer people than me to solve I guess. 

Paul
---
Paul Nagle / Soft Room Music
 www.softroom.co.uk
 www.BogusFocus.com

** Binar's Project Poltergeist and Headshock's MFPE available direct from the Bogus site NOW. **

> I only have a cable into the input midi connection, so Im not sure
> what you mean by 'ack' loop?

That rules out a loop.

Can your P3 receive midi sync or note messages OK ?
Try setting the midi thru on to pass notes and check the input is working.
Which type of opto-isolator did you use ?

Cheers,
Colin f

> Can your P3 receive midi sync or note messages OK ?
> Try setting the midi thru on to pass notes and check the input is
working.
Yes, midi in works ok

> Which type of opto-isolator did you use ?
6N137

Thanks
Roger

Roger wrote:

> I get a Bad Block Error when trying to receive SysEx data, I'm
> assuming I have the wrong setup with the sending program. 
> 
> My setup from sending program is as follows: 
> Midi Block Size 1024, Count 64, Delay 200
> 
> Ive set the delay to 200 as the manual states that the flash needs
> 100ms to write each sysex block however can someone advise the 
correct
> block/count sizes.

This was down to the librarian program Roger is using - ChangeIt.
An otherwise decent bit of freeware, but it doesn't put gaps after 
F7, just between blocks, and the block sizes aren't too granular.

Cheers,
Colin f