[Feature Request] Report MIDI 2.0 UMP ports as type 32bit

[symdeb]

Summary

The current JACK API reports any device/port as 8 bits, even it is an MIDI 2.0 UMP device/port. This request is for jack to report UMP ports as 32 bit (since UMP data are 4 bytes each, even some complete UMP MIDI 2.0 messages my require 64 or 128 bits as well). The ALSA API already provides a bit flag to identify an UMP from an legacy port and there are a few more flags that could be useful,. Additionally, a virtual port needs to be able to set such UMP capability flag.

A challenge might be that non-static MIDI 2.0 ports may change their protocol capability on the fly, Even though the use of non-static port may be not used much, if the jack driver could catch notification events and update port capabilities and send an capability_change() event by means of a callback, it would be perfect.

Basic example

Legacy ports
Type: 8 bit raw midi
uuid: 4294969936
UMP Ports:
Type: 32 bit raw midi
uuid: 4294969936

Motivation

When client application are able to differentiate UMP from legacy ports, and knows it capabilities, it knows how to receive and transmit data in UMP format, and as such be able to utilize the JACK API for MIDI 2.0 UMP

For example, an application that sends UMP data via JACK to another -UMP unaware - receiver (virtual application port), results in UMP bytes that such receiver cannot use. A MIDI hardware device does not have issues as the UMP data is translated to MIDI 1.0 UMP or legacy MIDI by the ALSA MIDI driver..