All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Henningsson <david.henningsson@canonical.com>
To: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Fwd: USB MIDI Specification Update Proposal
Date: Sun, 20 Jul 2014 20:52:34 +0200	[thread overview]
Message-ID: <53CC0FF2.8000702@canonical.com> (raw)
In-Reply-To: <20140715234123.11232.qmail@vps-1011917-539.manage.myhosting.com>

Forwarding this in case anyone is interested in influencing this 
standard somehow, to make sure they don't do anything problematic for 
us...? Are we interested?

// David

-------- Original Message --------
Subject: 	USB MIDI Specification Update Proposal
Date: 	15 Jul 2014 19:41:23 -0400
From: 	MMA/IASIG Announcements <info@midi.org>
To: 	



July 15, 2014

Greetings,

The MIDI Manufacturers Association ("MMA") Technical Standards Board
("TSB") has formed a working group to update the USB Class Specification
for MIDI Devices.

The original version 1.0 specification was published in 1999 by the USB
Implementors Forum (USB-IF). It has been implemented in hundreds
(thousands?) of devices from many different manufacturers, and all of
the major operating systems include "class drivers" that allow MIDI
devices to connect by USB without the user needing to install a driver.

Meanwhile, the technology and the environment around MIDI and USB have
changed:

   * Processors are faster, and USB itself is faster
   * Many music devices are equipped with USB ports for MIDI, and some of
     those can operate at faster than MIDI-DIN speed (typically via
     custom USB drivers)
   * Popular mobile systems now also support MIDI via USB, but do not
     allow manufacturers to install custom drivers
   * Mobile has low power requirements

Given all of these factors, we think the USB-MIDI Specification could
benefit from an update. We do not propose a major overhaul or any change
of basic architecture, but rather a minor update that we expect to label
as a version 1.1. The update will be done in collaboration with the
USB-IF. Components of the proposed Version 1.1 Update that we plan to
discuss include:

   * Additional Device Attributes
   * Bandwidth Descriptors
   * Add Interrupt Mode
   * Transfer Non-MIDI Data / Meta Event
   * Product Identification (Logos)

We would like all commercial manufacturers of USB MIDI hardware and
software to join us in this effort. If you would like to comment, ask
questions, voice an opinion or suggestion, or simply have early access
to the specification, please join the MMA and subscribe to the working
group email mailing list.

Regards,

Mike Kent, WG Chair (Roland Corp.)
Tom White, President/CEO, MMA



------------------------------------------------------------------------

(C) 2014 MIDI Manufacturers Association Incorporated.

       reply	other threads:[~2014-07-20 18:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140715234123.11232.qmail@vps-1011917-539.manage.myhosting.com>
2014-07-20 18:52 ` David Henningsson [this message]
2014-07-21  8:17   ` Fwd: USB MIDI Specification Update Proposal Clemens Ladisch
2014-07-21  8:21     ` David Henningsson
2014-07-21 12:48       ` Clemens Ladisch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53CC0FF2.8000702@canonical.com \
    --to=david.henningsson@canonical.com \
    --cc=alsa-devel@alsa-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.