- From: <bugzilla@jessica.w3.org>
- Date: Wed, 03 Oct 2012 23:24:31 +0000
- To: public-audio@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18992 --- Comment #8 from Florian Bomers <w3c_bugz@bome.com> 2012-10-03 23:24:30 UTC --- (In reply to comment #7) > Yamaha's request was that short MIDIMessages be complete messages - i.e., that > they not require additional state to be maintained from message to message > (aside from long messages that could be broken in multiple parts; they weren't > happy about that, but were okay with it.) That seems like a logical request; > and with your current system, what does the Windows/Mac API give you for your > drum computer? On reception (drum computer to host), the Windows and Mac API's undo running status, so I receive a series of complete MIDI messages. I only know that the drum computer is using running status from the old DOS days. However, I have been able to send multiple messages at once WITH running status (on Windows, with midiOutLongMsg() ), and it works fine. I just assume that the bytes are sent "as is" on the MIDI transport. But it's hard to verify these days... -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Wednesday, 3 October 2012 23:24:32 UTC