Rev. 1224 midi messages received bug

[dasfaker]

Hi Atom

In rev. 1224, all midi messages received in the panel have size 0.

[Stoner]

I know he is working on this issue as I was on chat with him when I was getting it.  I cannot say ALL messages received are zero, but I can confirm that cc midi messages appear to work while the sysex ones do not.  Can you confirm that behaviour dasfaker?

Stoner

[atom]

Yeah i’ve seen this reported. I can’t reproduce this, the binary i built on my Windows 8 runs fine (the size of a CC show up as 3 bytes). I did a rebuild 1225 (added a getMidiMessageType() as an alias to getType(), didn’t do anything else). Try it if that still doesn’t work then there is something very much broken.

[Stoner]

Atom, if you looked at my reply to this you will note that I get 3 bytes also on cc messages from my knobs on the Minitaur when I turn them.  What I do not get is SysEx messages when I inquire to the Minitaur about the firmware version or ask for parch information.

Stoner

[dasfaker]

Yes, your are correct Stoner. Cc’s are working fine, but sysex not. I’m working on a panel that works only with sysex so I didn’t tested cc messages.

[Stoner]

Thanks dsafaker.  Atom, 1225 has fixed the getMidiMessageType and it now shows that type 5 returns zero length items.  I am guessing that type 5 means SysEx, is that true???  Anyway, the SysEx messages are still not working.

Stoner

[atom]

Yes 5 is SysEx, it’s defined in LUA, you can do comparison like so

myMethod = function(midi)
	if midi:getType() == CtrlrMidiMessage.SysEx then
		console ("midi size="..midi:getSize())
		console ("raw:")
		console (midi:toString())
	end
end

[atom]

NOT ALL damn 🙂 i thought all was broken, just SysEx. Now i found the problem. A fix will be there asap.

[Stoner]

Resolved in 1228 and all tests out okay.  Thanks so much Atom.

Stoner

[Author]

Posts