From the original SynthMaker forum (2004–2014), with its members’ names and dates.
1-2-Many ·
Having issues with this - when triggering it to send 1 syx patch, the midi LED on my hardware unit just hangs, until I press a key on my midi keyboard. The patch doesn't load either. I have a sneaky feeling that it's sending the data out too fast for my hardware to recognize it? (Yes protect is OFF).
Any way to slow it down?
EDIT - Confirmed from the User Manual -
Notice: If the transmission interval is shorter than 25ms, the device cannot receive data correctly. Please make enough interval between transmission.
infuzion ·
I'm assuming you are sending more than Sysex data string in a row?
Ticker -> Tigger Div -> StrSysex trigger input
or use my Heartbeat system; it is slightly more accurate for 40-10 triggers/second.
1-2-Many ·
I found the source of my woes. It's a StrSysex BUG. It thinks it needs to correct internal F0 & F7s, which is wrong since it's SYX it should all be left alone - just send the data!
Left is the original String - Right is what it spits out (recaptured via SysexStr)
infuzion ·
1-2-Many wrote: I found the source of my woes. It's a StrSysex BUG.
Good sluthing! Post a bug in the Bugs forum! Also post the OSM there or send to [email removed]
DigitalWhiteByte ·
1-2-Many wrote: I found the source of my woes. It's a StrSysex BUG (recaptured via SysexStr)
I would like to ask you how did you test?
virtual midi loopback did you use? aka: midi-ox - midi yoke - LoopBe
The driver midi-yoke, seems to have some bugs on sysex, when used with midi-ox.
The driver LoopBe, seems to support better sysex and beyond is 64-bit.
If the test, you did it using the midi ports to an external device and then in your hardware,
There may be various problems.
I also note that the primitive SYSEX, has a maximum buffer of 1000 hexadecimal numbers.
try to post the string in question, because I can not reproduce the bug.
infuzion ·
DigitalWhiteByte wrote: try to post the string in question, because I can not reproduce the bug.
or OSM is better
1-2-Many ·
DigitalWhiteByte wrote: I would like to ask you how did you test?
virtual midi loopback did you use? aka: midi-ox - midi yoke - LoopBe
The driver midi-yoke, seems to have some bugs on sysex, when used with midi-ox.
The driver LoopBe, seems to support better sysex and beyond is 64-bit.
If the test, you did it using the midi ports to an external device and then in your hardware,
There may be various problems.
I also note that the primitive SYSEX, has a maximum buffer of 1000 hexadecimal numbers.
try to post the string in question, because I can not reproduce the bug.
No, this is all internal SM - no midi loopbacks, not passing through any exernal devices.
Here is an example with the bug - done in SM 2.0.5 Free version. Just push the trigger button to see the bug on the output
chrispal ·
Value F7 representing end of transmission, and maybe it can exist only on last byte, SM shrinking F to 7, probably this is the point.
F0 is a start of transmission, F7 is the end, values between them can be from 00 to 7F only i guess.
1-2-Many ·
chrispal wrote: Value F7 representing end of transmission, and maybe it can exist only on last byte, SM shrinking F to 7, probably this is the point.
F0 is a start of transmission, F7 is the end, values between them can be from 00 to 7F only i guess.
Yeah - sure.
SM should not care or tamper with Syx data is the point. Syx data is machine specific info that doesn't always adhere to the SOT/EOT format. There are hardware devices that chunk their data into packets for per one syx send operation, as my preset example shows (it contains three F0-F7 packets per preset, required since each packet addresses a different memory location and the address info is part of the syx header).
The StrSysex primative should not try to guess what it means or mess with it in any way - period.
chrispal ·
You can split your string into 3 complete packets with String to String Array, and then send them to StrSysex one by one using String Array Get At...
1-2-Many ·
chrispal wrote: You can split your string into 3 complete packets with String to String Array, and then send them to StrSysex one by one using String Array Get At...
Yes, thanks, I've done that (err something like that) and it works. Still this behavior is odd and should be fixed IMO.
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker