The chord-midi plugin from x42-plugins works when i first create a region in a region of a track.
If i make changes to the notes in the region, like transpose one of them, it randomly can either omit to play one/several of the notes at all, or for some it doesn’t create a chord.
This happens while i “loop” over a region, or several regions.
As discussed in IRC, disabling “chase MIDI” in “preferences” helps a bit, but doesn’t completely solve the problem.
a) I said randomly, and i can’t find a way to reliably make it happen, it really is quite randomly. It can work for a (short) while
b) the described behaviour is also observable in the scroomer/pianoroll of the track
c) duplication the track, the same behaviour can be observed in the dublicated track (as said: randomly)
d) copy the region to a newly created track, midi-chord seems to work again
e) it happens in Ardour9.2 and in 2 nightly builds (215 and 248). midi-chord works reliably in Ardour8
I really wish i could be more detailed, but it is quite randomly, for now i haven’t figured it out (what triggers it and what will happen, omit note or simply don’t create a chord).
I made a short video about the behaviour with a most basic new created session, in case the description was not clear.
In case short on time: the problem is observable minute 0.40ff
Also, side question, how can i link to a video with a preview ?
I made a second short video with ACE-MIDI-monitor enabled, as adviced in IRC. I can’t see anything unusual in midi-monitor, midi seems to toggle between on and off: with-midi-monitor
I don’t know if this is a similar cause but I may have a similar issue with other x42 MIDI plugins. I use x42 Channel Map and Key Range Filter plugins.
I didn’t encounter this problem in Ardour 8.12 but encounter this issue most sessions with Ardour 9.2.
In my case - I have a MIDI keyboard controller connected through Ardour which is connected to an external MIDI synth. What seems to happen is that note-off events are randomly dropped for random notes at random times in a random session. I’ve been meaning to try to troubleshoot further and submit a forum post and bug report - but have not found the time yet. I fix for now by restarting Ardour.
I have found that I encounter the issue the most if I play the Schmitt Op.16 Preparatory Exercises For the Piano. Most times by the time I’m half-way through the exercise book - the problem has presented itself.
I have other MIDI controller issues with Ardour 9.2 with MIDI controllers where my Akai MIDIMIX and Korg NanoKontrol2 are unusable as control surfaces for any automation controllers. I can see the full range of MIDI CC event values being received when a knob or slider is used but the automation is inconsistent and will not progress unless moved at slower than a snails pace no matter what the smoothing value is set to. The control will work reliability if assigned to a channel volume but is unreliable if assigned to an automation control.
I can.
There is a duplicate note-on at 0:13 for Note E2 followed by only a single note-off. Similar at around 0:21 [1], yet at 0:30 two note-on events are followed by two note-off events for Note E2 [2].
Breakage happens when a single C2note-on event is followed by two note-off events.
This is somewhat surprising. The plugin keeps track of received note events and only produces output for the first note-on event. Excess note-off events are ignored.
Anyway it’s clear that something is amiss with MIDI playback in Ardour 9.2. Those duplicate events should not be there. There was already a bug related to MIDI Chase identified and fixed in Arodur 9.2.264, but it looks as if there is more to this.
Is there a way in Ardour to record all MIDI events at different places along the processing chain automatically for the entire time Ardour is running? For example all MIDI events received by Ardour, all events before and after plugins, and all events leaving Ardour. Of course you have the normal MIDI recording function for a channel but trying to identify if my issue is a lost note-off? or multiple note-on’s with a single note-off? or some other issue?
As said, for me it isn’t that easy to troubleshoot it, as there is a certain randomness to it.
In case someone else has the problem and finds this thread, take the ideas to workaround with a grain of salt, but they might be worth a try
the mentioned disabling of midi chase in preferences sure helps a bit
if it happened, saving and closing, then re-opening the session seems to reliably make midi-chord work again.
as far i can tell yet, not moving notes around while looping over the region seems to avoid the problem. So: don’t loop while doing it. Stop the looping, move the notes, start looping again.
More i couldn’t figure out yet. Nightly builds took care of the problem, but as far i can tell didn’t seem to have solved it fully yet (for me it sure is much more difficult to create the problem with nightly build pretty recent version, right now i use version 9.12.304, 26.03.2026, so go for a rather recent version)
