Alsa-Devel Archive on lore.kernel.org
 help / color / Atom feed
* [alsa-devel] MIDI 2.0 universal packet protocol
       [not found] <1578973497459815979-webhooks-bot@alsa-project.org>
@ 2020-01-14  3:45 ` GitHub issues - edited
  0 siblings, 0 replies; 3+ messages in thread
From: GitHub issues - edited @ 2020-01-14  3:45 UTC (permalink / raw)
  To: alsa-devel

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 ? Reference for packet format : [https://www.midi.org/articles-old/details-about-midi-2-0-midi-ci-profiles-and-property-exchange](url)

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [alsa-devel] MIDI 2.0 universal packet protocol
       [not found] <1578973876973015070-webhooks-bot@alsa-project.org>
@ 2020-01-14  3:51 ` GitHub issues - edited
  0 siblings, 0 replies; 3+ messages in thread
From: GitHub issues - edited @ 2020-01-14  3:51 UTC (permalink / raw)
  To: alsa-devel

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [alsa-devel] MIDI 2.0 universal packet protocol
       [not found] <1578970828615752935-webhooks-bot@alsa-project.org>
@ 2020-01-14  3:00 ` GitHub issues - opened
  0 siblings, 0 replies; 3+ messages in thread
From: GitHub issues - opened @ 2020-01-14  3:00 UTC (permalink / raw)
  To: alsa-devel

alsa-project/alsa-lib issue #24 was opened from symdeb:

Since MIDI 2.0 only support USB and non MIDI 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 ? Reference for packet format : [https://www.midi.org/articles-old/details-about-midi-2-0-midi-ci-profiles-and-property-exchange](url)

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, back to index

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [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] <1578973876973015070-webhooks-bot@alsa-project.org>
2020-01-14  3:51 ` GitHub issues - edited
     [not found] <1578970828615752935-webhooks-bot@alsa-project.org>
2020-01-14  3:00 ` GitHub issues - opened

Alsa-Devel Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/alsa-devel/0 alsa-devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 alsa-devel alsa-devel/ https://lore.kernel.org/alsa-devel \
		alsa-devel@alsa-project.org
	public-inbox-index alsa-devel

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.alsa-project.alsa-devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git