By the way, when you encounter issues or problems like this, we
encourage you to open an issue via Microsoft's support channels.
Customers with a Premier contract should contact their account
manager, and others can follow instructions on
http://support.microsoft.com to contact Microsoft.
While we are on the topic of the inbox USB MIDI class driver, is
anyone on this list aware of other issues (defects or functionality)
in this driver that prevent it from being more generally useful?
Regards,
Frank Yerrace
Microsoft
-----Original Message-----
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Tom Duffy
Sent: Friday, November 8, 2013 4:08 PM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: New information about multi-port USB MIDI
devices
I seem to remember the problem being triggered when you split a SysEx
message into multiple packets. If you always keep the SysEx in a
single call to the MIDI subsystem, the problem doesn't occur.
Our product has up to 7 MIDI ports in a USB stream, one of
those is dedicated to SysEx control. We had to keep the
Sysex size at 512 bytes to avoid problems on XP and 7.
This was developed back in 2003/2004, so my memory of the details are
a little hazy now.
We may have been aware of the hotfix, but it's difficult to get
permission to redistribute those to end users, and besides, they are
using all the different language versions and variations that are
available in the world. No way to keep track of it.
Tom.
Matthew van Eerde wrote:
This is indeed a bug with USBAudio.sys on devices that have multiple
jacks on a single MIDI pipe. I would suggest calling Microsoft and
requesting a hotfix rather than writing a driver.
*From:*wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] *On Behalf Of *Timothy
Knudtson
*Sent:* Friday, November 8, 2013 1:00 PM
*To:* wdmaudiodev@xxxxxxxxxxxxx
*Subject:* [wdmaudiodev] New information about multi-port USB MIDI
devices
I have done some further research on the multi-port USB MIDI problem
that I have been encountering with the default USBAudio.sys driver.
The driver will accept the first few MIDI events (SYSEX Messages, notes,
etc...) then will stop working for a few more messages, then will
start working again for all messages after that.
I was able to reproduce the issue using a third party MIDI device
that has multiple MIDI ports for a single USB device. The third party
MIDI controller created their own USBAudio.sys driver to compensate
for this short coming in the default driver.
My question is what steps should I take to create my own USBAudio.sys
driver? Is there a sample driver that is recommend I start with?
Timothy Knudtson
iConnectivity
******************
WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
Unsubscribe:
mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
URL to WDMAUDIODEV page:
http://www.wdmaudiodev.com/
******************
WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
Unsubscribe:
mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx
URL to WDMAUDIODEV page:
http://www.wdmaudiodev.com/
