From: GitHub issues - edited <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: [alsa-devel] MIDI 2.0 universal packet protocol
Date: Tue, 14 Jan 2020 04:51:21 +0100 (CET) [thread overview]
Message-ID: <20200114035123.DBA18F8014E@alsa1.perex.cz> (raw)
In-Reply-To: <1578973876973015070-webhooks-bot@alsa-project.org>
alsa-project/alsa-lib issue #24 was edited from symdeb:
Since MIDI 2.0 only support USB and not over DIN (for now), will MIDI 2.0 need a new or updated OS class driver for the 32/64 bit universal packet interface and device descriptor for devices ? Page 16 of the USB MIDI class driver spec defines support for 1,2 or 3 bytes transfers only, How will this have to be implemented by MIDI USB device manufacturers and well as on the Linux OSes side ? How will this impact Linux ALSA ? Would the first byte of the message with b7=0 not confuse the driver of running status ?
Link universal packet format
https://www.midi.org/articles-old/details-about-midi-2-0-midi-ci-profiles-and-property-exchange)
Link first MIDI 2.0 Ready product: Roland A-88MKII
https://www.midi.org/articles-old/roland-announces
Issue URL : https://github.com/alsa-project/alsa-lib/issues/24
Repository URL: https://github.com/alsa-project/alsa-lib
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next parent reply other threads:[~2020-01-14 13:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1578973876973015070-webhooks-bot@alsa-project.org>
2020-01-14 3:51 ` GitHub issues - edited [this message]
[not found] <1578973497459815979-webhooks-bot@alsa-project.org>
2020-01-14 3:45 ` [alsa-devel] MIDI 2.0 universal packet protocol GitHub issues - edited
[not found] <1578970828615752935-webhooks-bot@alsa-project.org>
2020-01-14 3:00 ` GitHub issues - opened
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=20200114035123.DBA18F8014E@alsa1.perex.cz \
--to=github@alsa-project.org \
--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.