Report next Controller - port and channel issue

[Oortone]

Minor issue.

This is tried with two USB controllers
Evolution UC33 (very old)
Novation Summit (quite new)

"MIDI>Report Next Controller MIDI" does not give any name (Summit) or "Unknown" (UC33) in it's report window although the correct names are given in the "Change MIDI" dialog. Also the midi channel given starts at 0 instead of 1 which is not according to standard. A device sending att midi channel 6 will be reported sending at 5 e.t.c.

Mapping seems to work ok.

I used the Blofeld profile.
macOS 14.6.1

[eclab]

All Report Next Controller MIDI is doing is reporting MIDI that's arriving at whatever device you specified was the controller device. At the stage that it receives this information to report it, it no longer has access to the device itself. I *might* be able to get it to at least report whether it's Controller 1 or Controller 2, would that be enough? Otherwise it'd be more work. Getting the MIDI channel dealt with should be easy.

…

On Jan 7, 2026, at 1:32 PM, Oortone ***@***.***> wrote: Oortone created an issue (eclab/edisyn#103) Minor issue. This is tried with two USB controllers Evolution UC33 (very old) Novation Summit (quite new) "MIDI>Report Next Controller MIDI" does not give any name (Summit) or "Unknown" (UC33) in it's report window although the correct names are given in the "Change MIDI" dialog. Also the midi channel given starts at 0 instead of 1 which is not according to standard. A device sending att midi channel 6 will be reported sending at 5 e.t.c. Mapping seems to work ok. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.

[Oortone]

It's just a report in case it was not known. For me personally it's minor. But I've seen similar behavior in other MIDI applications on Mac. Sysex Librarian for instance has no name for some devices in the Speed menu. cheers, Tor Den ons 7 jan. 2026 kl 19:41 skrev Evolutionary Computation Laboratory < ***@***.***>:

…

*eclab* left a comment (eclab/edisyn#103) <#103 (comment)> All Report Next Controller MIDI is doing is reporting MIDI that's arriving at whatever device you specified was the controller device. At the stage that it receives this information to report it, it no longer has access to the device itself. I *might* be able to get it to at least report whether it's Controller 1 or Controller 2, would that be enough? Otherwise it'd be more work. Getting the MIDI channel dealt with should be easy. > On Jan 7, 2026, at 1:32 PM, Oortone ***@***.***> wrote: > > > Oortone > created an issue > (eclab/edisyn#103) > Minor issue. > > This is tried with two USB controllers > Evolution UC33 (very old) > Novation Summit (quite new) > > "MIDI>Report Next Controller MIDI" does not give any name (Summit) or "Unknown" (UC33) in it's report window although the correct names are given in the "Change MIDI" dialog. Also the midi channel given starts at 0 instead of 1 which is not according to standard. A device sending att midi channel 6 will be reported sending at 5 e.t.c. > > Mapping seems to work ok. > > — > Reply to this email directly, view it on GitHub, or unsubscribe. > You are receiving this because you are subscribed to this thread. > — Reply to this email directly, view it on GitHub <#103 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIYIRYFN73BU2OCMSUF6ABL4FVHL5AVCNFSM6AAAAACQ7IJD3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMRQGIZTCMJSGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>