Skip to main content

MIDI Forum

Atsushi
Atsushi
Active Member
Joined: Mar 10, 2019
Last seen: Aug 20, 2024
Topics: 3 / Replies: 8
Reply
RE: MIDI 2.0 Why can a function block only have one "MIDI1" port ?

A UMP endpoint does cover multiple legacy ports (most of real world MIDI 1.0 devices would have at least one input and one output). Note that one Fu...

10 months ago
Reply
RE: Legacy MIDI to MIDI 2.0 Registered and Assignable messages

Regarding [2], the UMP specification says (at P.104): > MIDI 1.0 Protocol Increment (CC 96) and Decrement (CC 97) messages are translated to ...

10 months ago
Reply
RE: Why is UMP MIDI2 controller limited to a 7 bits index (UMP spec 7.4.6 MIDI 2.0 Control Change Message)

I support the current specification and the overall strategy that the specification implements regarding backward compatibility in CC index. DAWs do n...

10 months ago
Reply
RE: MIDI 2.0 Why can a function block only have one "MIDI1" port ?

I guess you are taking the mentioned number differently. "The Number of Groups Spanned" is not the number of MIDI 1.0 ports. The number of spanned gro...

10 months ago
Reply
RE: Processing concurrent MIDI Message Reports

It is good to know that my Q is not kind of dumb 😉 > If the Device supports ChCtrlLIst/AllCtrlList PE messages then you could compare the incom...

1 year ago
Reply
RE: MIDI-CI Property Exchange: adding new element to a JSON array in partial updates

Hi, Could you please elaborate on this - > for simplicity and interoperability reasons. I do not see any particular need for interoperability...

1 year ago
Reply

Hello, Thanks Andrew for all the verification and Mike for the status updates. I will wait for the revised updates and apply changes to my implemen...

2 years ago
Reply

I did (do) have some implementation code for a UMP-based SMF alternative format in my MIDI 2.0 library, and it is also based on big endian.br /> It...

2 years ago