27 Aug
2005
27 Aug
'05
9:07 a.m.
On Fri, 2005-08-26 at 19:54 +0200, Pedro Lopez-Cabanillas wrote:
Great!
Now actually running amidi with the firmware update reveals some other
issues possibly related to the linux midi driver?
Midi scenario:
PC out -> controller in/out -> keyboard in/out -> PC in
... where both keyboard and controller are of the merging kind.
The implication is that every SysEx byte send from the PC is also
received by the PC which cannot keep up with the action. This leads to a
corrupted SysEx transfer. Unfortunately Behringer do not include SysEx
documentation, so it is not known wether they issue resend commands or
not.
Disconnecting the PC midi in solves the issue.
TODO: Sanity check my midi-routing :)
mvh // Jens M Andreasen
mvh // Jens M Andreasen
Now, what
would an amidi command look like that guarantees to update
each and every midi-device found with said sysex file?
amidiall.sh
----CUT----
#!/bin/bash
CMD=$(which amidi)
PORTLIST=$($CMD -l|awk '/^hw:/ { print $1 }')
for P in $PORTLIST; do
echo "$CMD --port=$P $*"
$CMD --port=$P $*
done
----CUT----
Usage:
$ amidiall -s myfile.syx
Regards,
Pedro
--