Garbage MIDI Data (MIDI FX, Logic Pro, Mac M1)

Audio Plugins
#1

Hi,
my sequencer outputs MIDI data to Logic Pro on M1 Macs that is not generated by the plugin itself. This leads to unpredictable behavior, such as notes that hang permanently, and makes it impossible to work with. My plugin only generates Note-On and -Off messages, which are always output on MIDI channel 1. However, many other commands appear in the MIDI log that are neither generated by me nor have any relation to generated MIDI data (see Scripter Logs below).
I am aware of the problem that existed with Logic Pro and 3rd party MIDI FX on M1 Macs. I also thought it was fixed since 10.7.4. However, this problem occurs with 10.7.4.
The problem only occurs on M1 Mac.
Intel works fine.
The VST3 version works fine on both M1 and Intel Macs in other hosts.
JUCE version is 6.1.6.
The AU is compiled as MIDI FX & Universal.
Does anyone have any ideas?

Faulty output (Bold & Italic = garbage data):

[NoteOn channel:1 pitch:36 [C1] velocity:100]
[NoteOff channel:1 pitch:36 [C1] velocity:0]
[NoteOn channel:1 pitch:38 [D1] velocity:100]
[NoteOff channel:1 pitch:38 [D1] velocity:0]
Error: send() called with malformed MIDI event
[PolyAftertouch channel:4 pitch:119 [B7] value:1]
[Aftertouch channel:1 value:0]
[NoteOn channel:5 pitch:111 [D#7] velocity:1]
[NoteOff channel:5 pitch:197 [F14] velocity:0]
[NoteOff channel:2 pitch:1 [C#-2] velocity:0]
[NoteOff channel:1 pitch:0 [C-2] velocity:0]
[PolyAftertouch channel:10 pitch:52 [E2] value:1]
[PolyAftertouch channel:10 pitch:52 [E2] value:1]
[PolyAftertouch channel:10 pitch:52 [E2] value:1]
[PolyAftertouch channel:11 pitch:1 [C#-2] value:0]
Error: send() called with malformed MIDI event
[PolyAftertouch channel:4 pitch:119 [B7] value:1]
[Aftertouch channel:1 value:0]
[NoteOn channel:5 pitch:111 [D#7] velocity:1]
[NoteOff channel:5 pitch:197 [F14] velocity:0]
[NoteOff channel:2 pitch:1 [C#-2] velocity:0]
[NoteOff channel:1 pitch:0 [C-2] velocity:0]
[PolyAftertouch channel:10 pitch:52 [E2] value:1]
[PolyAftertouch channel:10 pitch:52 [E2] value:1]
[PolyAftertouch channel:10 pitch:52 [E2] value:1]
[ControlChange channel:1 number:1 [Modulation] value:0]

Correct output (e.g. Intel Mac)

[ControlChange channel:1 number:100 [Reg.Par. LSB] value:4]
[NoteOff channel:1 pitch:48 [C2] velocity:0]
[NoteOn channel:1 pitch:48 [C2] velocity:100]
[NoteOff channel:1 pitch:48 [C2] velocity:0]
[NoteOn channel:1 pitch:48 [C2] velocity:100]
[ControlChange channel:1 number:123 [All Notes Off] value:0]

Issues with MidiBuffer in JUCE 7 on macOS in RELEASE build
Bugs in M1 Logic Pro Itself
#2
#3

Thanks for the cross reference. I’ve already read every thread here about Logic Pro/M1/MIDI FX. And after an Apple employee posted here and Apple addressed the problem as “fixed” in the release notes of 10.7.4, I assumed it was. Since then, no new reports have appeared here that there are still problems with this constellation. That’s what I’m wondering about.

I analyzed the problem over the weekend and am now sure that it is somehow related to M1/Silicon. Because when Logic Pro is launched on M1 in Rosetta mode, the problem no longer occurs.

#4

There is a message from @adamwilson in that thread saying that there are still MIDI issues with 10.7.4.

#5

My bad, I somehow confused this thread with another one. Really though I read everything about this topic, but oviously didn’t.
Thanks for clearing it up!

#6

Just to confirm, I still have weird issues with my MIDI plugin Entonal Studio, in Logic Pro, including random notes being generated.

#7

I can confirm to experience similar (if not the exact same) issues on an M2 when building for release, both VST3 and standalone: Issues with MidiBuffer in JUCE 7 on macOS in RELEASE build.

#8

I think the issue you linked to is different from the one in this thread; I have zero issues in other hosts, this one is a Logic Pro on Apple Silicon issue AFAIK

1 Like
#9

Okay, good to know. Thanks!