----- Original Message -----From: rpcfenderSent: Monday, December 03, 2007 12:59 AMSubject: [bc2000] Re: BCR Sysex from DAWHi Art
> With regard to wrapping .tx with $F0 and $F7. I'm still going with my observation that if included they lead to a spurious MIDI message error. Without $F0/$F7, my script does as I expect - which is to send a MIDI note 46 message at 127 velocity. (This is an Ableton Live MCU emulation command that = page minus.) So this is indeed a valid MIDI message, and is shown in MIDIOx as being sent properly when encoder 1 is turned.
Woops. This is why it is good to say what messages you are trying to output at the start.
You only need the sysex bytes if you are sending sysex.
Midi Note on is not sysex
So the error is not the Midi note on ($90) but the sysex header. Boy, did I miss that one. Sorry Art.
$90 43 120 ; note on
$80 43 120 note off
$B0 43 120 ; CC
etc
all channel 1
$F0 43 12 67 ....... 22 $F7 sysex
>
> I'd ask you to actually run this on your BCR, both with and without $F0/$F7, and see what you get. Incidentally, I obtain the same result with multi-message .tx's, including those concluding with an ifn/ifp sequence (again requiring no F7's at all).
>
The format for tx is
.tx Midi message (another Midi message) (another Midi message) (another Midi message) etc
as long as the sum of the Midi messages is less than 125 bytes
The Midi message can be any legitimate Midi message you want
$F0 $41 $10 $00 $6B $12 $10 $00 $20 $1E value checksum $F7 FantomX reverb setting channel 1
$B0 $07 value volume on channel 1
Increase the volume and reverb at the same time
.tx $B0 $07 val $F0 $41 $10 $00 $6B $12 $10 $00 $20 $1E val cks-1 $F7
Note that the BC ignores white space so this is OK with the gaps
What is the message you want to send when you turn it clockwise?
What is the message you want to send when you turn it anticlockwise?
Royce
Message
Re: [bc2000] Re: BCR Sysex from DAW
2007-12-03 by Art Hunkins
Once again, thanks for the great info/response,
Royce.
Actually, I'm having no trouble sending multiple
MIDI messages with .tx; I was just confused about the $F0/$F7 frame. Frankly, I
had (wrongly) considered everything sent via .tx as "sysex". (I've never
strictly sent sysex; never needed to.)
I'd suggest adding to the docs somewhere: ".tx can
send one or mote standard MIDI messages, and/or sysex in the same data stream.
Only the latter is enclosed with the sysex frame $F0 and $F7."
Regarding .easypar and .tx in the same module, I'd
suggest a statement somewhat like this: "In a given module that includes both
.easypar and .tx, .easypar must come first. Also be aware that .easypar resets a
number of parameters, including .showvalue and .mode to off - meaning
you'll get absolutely no visual display unless you specify these
parameters *after* .easypar. With *only* .tx in a module, statement order
is unimportant, as .tx doesn't reset anything."
Art Hunkins