Bc2000 (for the BCF2000 & BCR2000) group photo

Yahoo Groups archive

Bc2000 (for the BCF2000 & BCR2000)

Index last updated: 2026-04-28 23:16 UTC

Message

RE: Re: bcr2000 failed firmware 1-10 upgrade with mac osx, "noOS&qu

2013-11-13 by <rpcfender@...>

I'm not sure you can always blame the Midi interface as Microsoft made their standard driver only able to send /receive 256 bytes. So despite being called a MS compliant driver it is faulty and against the Midi spec and falls over for a large number of Midi devices.

So if the Midi interface doesn't have to install its own driver you are in trouble and you have wasted your money. If the manufacturer has copied the compliant driver then you are still in trouble.

The Roland, Korg, Yamaha & Midisport and I guess quite a few others are OK.

Pity someone doesn't re-write the example Midi driver and make it work like Jamie OConnell who turned a non working MicroSoft C example program into MidiOx

All the best
Royce



---In bc2000@yahoogroups.com, <sote@sbcglobal.net> wrote:

You didn't mention a make or model of MIDI interface so I'll throw this in just in case.

This is the kind of problem people get when they use some of those cheap USB to MIDI cables off eBay. These units are notorious for choking on large amounts of data at once. They work fine for sending note information back and forth from synth or controller to DAW sequencer but throw a sysex at them and they tend to lose their way a quarter or half way thru a 50K file. I suspect these cables were built without buffers.

Not all of these have this problem but there are so many different brands of them (many clones under different brand names) it is hard to distinguish which are good and which aren't.

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.