Bc2000 (for the BCF2000 & BCR2000)

>
> Just to let you all know. Anyone fortunate enough to own a Kawai K4, can now control their synth, in real time, using their BCR2000. This is thanks to the delightfully crafted presets written by Royce.
> 
> For anyone who doesn't have a K4 or K4r, they can be picked up for peanuts on a certain internet auction site and are certainly more interesting to play with than your average soft synth.
> 
> Royce actually wrote these way back in May and I've had them for testing and forgot to post them till now. So apologies for that.
> 
> Presets, templates and read me are all now in the files section.
> 
> Thanks,
> Alan
>

>
> --- In bc2000@yahoogroups.com, "Rainer" <klorisk@> wrote:
> > Unfortunately, the file "Kawai K4_1.syx" does not seem to work properly, both in BC Manager and in BCR Edit it can't be imported, while the 2nd can be.
> > 
> > The BC Manager gives the following error when importing:
> > Error: MIDI system exclusive error
> > No Exclusive status
> > 
> > Could you perhaps check the file and perhaps re-export it from your setup, and re-upload it?
> 
> Since you mentioned BC Manager, I got curious, out of a sense of responsibility - just to check the error message wasn't caused by some kind of bug in BC Manager...
> 
> I found that what's wrong with the file is that the last 4 bytes ('end' plus F7) of the last SysEx message are inexplicably repeated:
> F0 ... 65 6E 64 F7 65 6E 64 F7
> So the second 'e' (65) occurs where a new SysEx message should start, i.e. where F0 is expected: this is what BC Manager means by "No Exclusive status".
> 
> So I'm a bit curious how this file was generated; was there a bug in the generating program?
> 
> In any case, it is very simple to fix this specific file: just remove the last four bytes.
> You can use a generic hexadecimal editor for this.
> Alternatively, you can use BC Manager's File -> Convert -> "Syx to txt/bc2" (from the main menu): BC Manager then produces an error message "Stream read error", but still creates the txt file correctly, which you can then simply open normally in BC Manager (and convert back to a syx file, if you wish).
> 
> Hope this helps,
> Mark.
>

>
> --- In bc2000@yahoogroups.com, "Rainer" <klorisk@> wrote:
> > Unfortunately, the file "Kawai K4_1.syx" does not seem to work properly, both in BC Manager and in BCR Edit it can't be imported, while the 2nd can be.
> > 
> > The BC Manager gives the following error when importing:
> > Error: MIDI system exclusive error
> > No Exclusive status
> > 
> > Could you perhaps check the file and perhaps re-export it from your setup, and re-upload it?
> 
> Since you mentioned BC Manager, I got curious, out of a sense of responsibility - just to check the error message wasn't caused by some kind of bug in BC Manager...
> 
> I found that what's wrong with the file is that the last 4 bytes ('end' plus F7) of the last SysEx message are inexplicably repeated:
> F0 ... 65 6E 64 F7 65 6E 64 F7
> So the second 'e' (65) occurs where a new SysEx message should start, i.e. where F0 is expected: this is what BC Manager means by "No Exclusive status".
> 
> So I'm a bit curious how this file was generated; was there a bug in the generating program?
> 
> In any case, it is very simple to fix this specific file: just remove the last four bytes.
> You can use a generic hexadecimal editor for this.
> Alternatively, you can use BC Manager's File -> Convert -> "Syx to txt/bc2" (from the main menu): BC Manager then produces an error message "Stream read error", but still creates the txt file correctly, which you can then simply open normally in BC Manager (and convert back to a syx file, if you wish).
> 
> Hope this helps,
> Mark.
>

>
> Thanks for that  Mark.
> 
> It is not in my original so perhaps Alan could check his version (he up loaded it ) and see if there is a problem in his version.
> 
> All the best
> Royce
> 
> --- In bc2000@yahoogroups.com, "Mark" <markwinvdb@> wrote:
> >
> > --- In bc2000@yahoogroups.com, "Rainer" <klorisk@> wrote:
> > > Unfortunately, the file "Kawai K4_1.syx" does not seem to work properly, both in BC Manager and in BCR Edit it can't be imported, while the 2nd can be.
> > > 
> > > The BC Manager gives the following error when importing:
> > > Error: MIDI system exclusive error
> > > No Exclusive status
> > > 
> > > Could you perhaps check the file and perhaps re-export it from your setup, and re-upload it?
> > 
> > Since you mentioned BC Manager, I got curious, out of a sense of responsibility - just to check the error message wasn't caused by some kind of bug in BC Manager...
> > 
> > I found that what's wrong with the file is that the last 4 bytes ('end' plus F7) of the last SysEx message are inexplicably repeated:
> > F0 ... 65 6E 64 F7 65 6E 64 F7
> > So the second 'e' (65) occurs where a new SysEx message should start, i.e. where F0 is expected: this is what BC Manager means by "No Exclusive status".
> > 
> > So I'm a bit curious how this file was generated; was there a bug in the generating program?
> > 
> > In any case, it is very simple to fix this specific file: just remove the last four bytes.
> > You can use a generic hexadecimal editor for this.
> > Alternatively, you can use BC Manager's File -> Convert -> "Syx to txt/bc2" (from the main menu): BC Manager then produces an error message "Stream read error", but still creates the txt file correctly, which you can then simply open normally in BC Manager (and convert back to a syx file, if you wish).
> > 
> > Hope this helps,
> > Mark.
> >
>

>
> --- In bc2000@yahoogroups.com, "Alan" <alan@> wrote:
> > No, I could find no problem in my copy. I've not made any changes to the preset as Royce wrote it, I wouldn't know how, so I don't know what's happened there.
> 
> So that seems to leave us with an uploading error. Still very strange.
> (I think we can exclude a storage error at Yahoo or a downloading error.)
> 
> In any case: the invalid version currently in the Files section at Yahoo has a size of 18,392 bytes, so the correct version should have 18,388 bytes.
> You might try uploading the correct version and then checking how big it is when you download it again.
> 
> Best wishes,
> Mark.
>