View Issue Details

IDProjectCategoryView StatusLast Update
0010348ardourbugspublic2026-05-25 12:25
Reportergfontanilla Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status newResolutionopen 
PlatformGNUOSLinuxOS Version(any)
Product Version9.2 
Summary0010348: MIDI Chase Playback causes note at beginning of region to drone
DescriptionWhen a MIDI note is drawn at the start of a region, and the playhead is at the start of the region, playback causes the note to drone until the playback ends. When moving the playhead elsewhere (snap is off), playback proceeds as expected.
Steps To Reproduce1. Create a MIDI track using an instrument plugin or external synth
2. With snap on, draw a region whose start is aligned to the grid
3. With snap on, draw a MIDI note at the start of the region
4. With snap on, locate the playhead to the start of the region
5. Hit play
TagsNo tags attached.

Activities

gfontanilla

2026-05-18 16:51

reporter   ~0030399

File attachment didn't seem to work, so: https://www.youtube.com/watch?v=1BrDpH1Kv-U

jean-emmanuel

2026-05-19 18:15

updater   ~0030408

I believe this is fixed in 9.5.

gfontanilla

2026-05-19 18:37

reporter   ~0030409

Unfortunately, it still occurs in 9.5 (as well as builds from master during the past few days).

jean-emmanuel

2026-05-22 06:53

updater   ~0030414

I can't seem to reproduce this one though, would you mind uploading a session the exbibits the issue ?

gfontanilla

2026-05-23 17:00

reporter   ~0030417

This is the same session as the one in the video: https://drive.google.com/drive/folders/1hew4VGEL-6ANJgYC6EIA3KWWu8W9nk4x

jean-emmanuel

2026-05-24 02:18

updater   ~0030423

The note stops normally here using provided session (using a different synth because I don't have the one in use).

gfontanilla

2026-05-24 04:08

reporter   ~0030425

I just tried the same session on my MacBook M1 and was able to reproduce it. My MacBook didn't have the "JX10" plugin so I replaced it with "MDA JX10" and selected the "Monosynth" preset to get the same sound in the video. I noticed if I select a non-looping synth preset like "Hard Lead", the issue isn't as obvious (but still there).

I'm digging into this again and possibly have identified the root cause. I'll post an update and perhaps another video once I get all the details.

gfontanilla

2026-05-24 17:19

reporter   ~0030431

Can you try reproducing again? The same session should be fine as long as the synth present is the kind that loops infinitely.

Furthermore, I found out that the note doesn't have to be at the beginning of a region. It could be anywhere in a region as long as the playhead and note start are exactly aligned. It's also easier to reproduce if "Return to last playback start when stopped" is enabled (as it does in the video). Another way to reproduce is by starting playback -- and before it ends, relocating the playhead to playback start by (repeatedly) clicking the area with snap enabled.

Good news is I have fix. I'll submit a PR after a good night's sleep just to be sure :)

The not so good news is I found another bug. It's similar but the root cause is different (dragging the region), so I believe a separate bug report is warranted. I'll create one tomorrow as well.

jean-emmanuel

2026-05-24 19:46

updater   ~0030432

I did try with a looping synth (surge xt, default preset) to make sure I'd hear a stuck note. Still no issue here with and without Auto Return enabled. I also tried removing my config folder just in case. (using build from master branch on Linux).

gfontanilla

2026-05-25 04:26

reporter   ~0030433

Apologies. After trying to reproduce the issue again, it seems the issue only happens on specific presets in specific synths. I couldn't reproduce it with x42's "General MIDI Synth" that ships with Ardour, but I was able to using Dexed (LV2) specifically with presets "26. -WOBBLE 1-" and "9. SAW EM UP" (among others) in the default bank/cartridge. Here is a session that uses Dexed created on macOS with Ardour 9.5 (release) that I also tried on a Debian-based distro: https://drive.google.com/drive/folders/1ghedj25LNI-tXI7Ki-v4GLIhshxzwxd2

For some additional context, I first noticed this issue using an external synth. I guess it was luck that I chose the "JX10" plugin when I attempted to reproduce it. It also occurs regardless of the audio engine (ALSA, PulseAudio, JACK, CoreAudio on macOS).

jean-emmanuel

2026-05-25 11:35

updater   ~0030437

Ok I manage to reproduce it: two NOTE_ON messages are emitted instead of one because Ardour attempts to resume the note errouneously , not all synths exhibit the issue (many will only need one NOTE_OFF to shut the note down regardless of how many NOTE_ON were received). Thank you for your patience !

gfontanilla

2026-05-25 12:25

reporter   ~0030438

Glad you were able to reproduce! Thank your for taking the time.

And yes, two MIDI_CMD_NOTE_ON are indeed being emitted as I found out, though I didn't know synths behave differently when it came to that. I opened a PR and tagged you in it: https://github.com/Ardour/ardour/pull/1115 :)

Issue History

Date Modified Username Field Change
2026-05-18 16:43 gfontanilla New Issue
2026-05-18 16:51 gfontanilla Note Added: 0030399
2026-05-19 18:15 jean-emmanuel Note Added: 0030408
2026-05-19 18:37 gfontanilla Note Added: 0030409
2026-05-22 06:53 jean-emmanuel Note Added: 0030414
2026-05-23 17:00 gfontanilla Note Added: 0030417
2026-05-24 02:18 jean-emmanuel Note Added: 0030423
2026-05-24 04:08 gfontanilla Note Added: 0030425
2026-05-24 17:19 gfontanilla Note Added: 0030431
2026-05-24 19:46 jean-emmanuel Note Added: 0030432
2026-05-25 04:26 gfontanilla Note Added: 0030433
2026-05-25 11:35 jean-emmanuel Note Added: 0030437
2026-05-25 12:25 gfontanilla Note Added: 0030438