In principle my vote goes to $7F $7F as well, for the reasons Art gives. (And in totally practical terms: I only have one BCR at the moment, so I could never get any mixups anyway.) However, people with more than one B-Control on the same physical MIDI output device (seen from the computer) do get into trouble with $7F $7F, because ALL BCs respond. For instance, this is the case in the U-4 setup described in the manual, where the first BC is connected to the computer via USB, and the second BC to the first BC via standard MIDI. And one could argue with the point about "responsibility where it belongs", for a particular, technical reason: If you use Device=$7F and Model=$7F fot the MIDI messages transmitting the script lines, then every BCF and every BCR always responds to every script line it receives by sending back a reply message (which states whether the message was correct, and if not, the error type). So if both a BCF and a BCR are connected to the same physical MIDI output device, they will then BOTH respond to every script line you send, EVEN if the script has started with "$rev F1" or "$rev R1". So this may cause a lot of unnecessary MIDI traffic; this might not be serious, but still... The advantage of using specific Device and Model IDs is that the BCs then do NOT respond to script lines meant for other devices or models. Mark. --- In bc2000@yahoogroups.com, "abhunkin" <abhunkin@...> wrote: > I vote for 7F 7F for various reasons. Primarily because it *is* all > inclusive and covers all bases for the programmer. It leaves > responsibility right where it belongs: the choice of $rev F1 or $rev R1 > by the *script writer*. > > Art Hunkins > > --- In bc2000@yahoogroups.com, "rpcfender" <rpcfender@...> wrote: >> Thanks for the info Mark. I'll include it in the docs. >> I'll change the program to include the universal setting. >> Does anyone want this to be selectable or should I just output $7f > $7f >> (all device ids + any type of unit) ?? >> >> Royce
Message
Re: BCF/BCR Sysex requests
2007-07-15 by Mark van den Berg
Attachments
- No local attachments were found for this message.