MantisBT - Issues

0010398: Keyboard Shortcuts - Plugin GUI Window - Toggle keyboard events button

Sat, 13 Jun 2026 01:03:31 +0000

Currently in plugin GUI windows there is a keyboard icon/button to toggle keyboard events within that plugin, on and off (green/white).

Suggesting to offer a keyboard shortcut that would allow this button to be toggled on/off using your PC keyboard to quickly be able to turn this feature on/off when needed.

Thank You

0010322: Keyboard Shortcuts Dialog - Update search field

Sat, 13 Jun 2026 00:59:59 +0000

I am sure this is going to be worth the time but
This goes with my overall theme of suggesting to make certain specific floating windows within Ardour follow common functionality / behavior as most other applications do.

This is a response to the following post
0010311

Suggesting the following updates which common search/filter fields use....

---------------------------------------------------------------------------------------------------------------------------------------------------------------------

-Use left justified text when English language is used for application because text is read from left to right.
Even if language is not a factor, I have never seen an application use right justify for any fields.

-Magnifying glass icon
Often used/shown on left side of the field, giving user the indication that it is a search field. Typically the text in the field is not right up against the icon because that would be confusing, there should be a couple characters of space in between the icon / text.
(This icon should remain visible all the time, currently it disappears when focus is applied to field which is confusing)
(Also magnifying icons are typically not used as a clear field button, which also does not make sense which I will mention below)

-Field also often contains the "Search..." text within the field as another indicator that it is a search field. (Which Ardour currently does)

-When text is typed into a search field, an "x" icons is often placed at the right side, that when clicked on clears the text from the field.
Currently magnifying glass is programmed to achieve this but it is not expected common behavior. The magnifying glass is also not visible when the field has focus, so cannot clear the field unless you click outside of the pane to then reveal the icon.
Again this is not common behavior.

Hope this was worth the time/effort to create this post.
Thank You

If this is not agreed with, again please regress the fields text back to being "Centered" as it was before all of this occurred.

0010397: Recent Window - Numbers do not sort in sequential order

Sat, 13 Jun 2026 00:56:08 +0000

Found one more instance of non sequential sorting of numbers in Ardour if anyone is interested.

In the session dialog, in the `Recent` tab
If user saves different numbered versions of a project they are working on

Name
Name 1
Name 10
Name 2

Numbers do not sort sequentially.

Thank You

0010396: Bottom Dock - Vertical scroll when closed

Fri, 12 Jun 2026 23:23:06 +0000

(I mentioned this issue in the past)

I view the Bottom Dock as being an overlay, on top of the Editor pane itself.
Therefore to me the Bottom Dock would have interaction with the Editor pane.

However if certain scenarios, when the Bottom Dock is closed, it alters the vertical scroll of the Editor pane.

Based on what I mention above, to me this seems like a bug. Not sure if this is expected behavior?

Thank you to anyone who reads this

0010330: Clicking on group header of invisible group hides all the group's tracks

Fri, 12 Jun 2026 21:28:56 +0000

If a group has been hidden, but tracks in that group are then made visible again, clicking on the group's header in the editor, rather than activating or deactivating the group, hides all of the group's tracks again. I don't think it was always like this, and even if it is like this by design, I don't think it's terribly helpful behaviour.

0010380: Plugin Generic GUI Window - Switches has less height max then Controls

Fri, 12 Jun 2026 18:12:01 +0000

Not sure if this is on purpose?
When you open a plugins generic GUI window
The maximum amount of "Switches" allowed before it breaks into a new column is less then the amount allowed in the "Controls" section.

I think "Switches" column allows for a maximum of 12 in each column before breaking into a new column.
I think "Controls" column allows for maximum of 25 in each column.
This gives the generic GUI window a lot more height, which would give room for more switches in the same column.

Should the maximum amounts be similar?

If the current amounts are expected behavior/not agreed with, then this can post can be closed.

Thank You

0010351: Segfault when importing a MIDI file with "Use MIDI Tempo Map" enabled

Fri, 12 Jun 2026 11:49:52 +0000

Importing the attached .mid file with the "Use MIDI Tempo Map" option checked
crashes Ardour with SIGSEGV. Unchecking that option lets the import complete
normally, so it's specifically the tempo-map path.

Same crash on 9.2 and 9.5 (official linux x86_64 binaries from ardour.org), so
it doesn't look like a 9.5 regression.

The file is a SMF type 1 with 6 tempo events (ranging from 0000069:0000052 to 84 BPM) and
4 time-signature events. The first time signature in the file is 1/4 at tick 0,
followed by 4/4 — that's the most unusual thing about the file and might be
what's tripping the importer up, but I haven't bisected.

0010395: ( Edit in ) Separate window - jumping down in steps

Fri, 12 Jun 2026 11:18:18 +0000

Ardours 9.5 new pianoroll window is jumping down everytime you click in this separate window on the midi region name.
When the window reaches the bottom of the monitor screen it moves a little bit to the right each time you click on the midi region’s name.

* right click on midi region > selected regions > edit in separate window ( pianoroll window opens on left top on the monitor screen ).
* click in this pianoroll window on the name of the midi region, the button right to the active region / all regions.
Per click the window jumps down a little bit until it reaches bottom of the monitor screen.

Before posting on Mantis I want to ask if other users also have this weird behaviour.

Ardour 9.5
Debian 13 Trixie KDE

0010394: Pipewire/Jack Inter-app MIDI/Audio Routing with internal Audio issues

Fri, 12 Jun 2026 09:12:53 +0000

Multiple configurations of routing and engine parameters yield crashes/held notes/connection blocking.

I am trying to play MIDI imported from a custom file, route that to QSynth/FluidSynth and route back audio to master.

Ardour is set to JACK/Pipewire.

With QSynth/FS MIDI engine set to "jack", ambiguous latency is reported. This is somewhat stable, but
it excludes the possibility of internal audio routing. This manifests as Ardour MIDI/VST tracks do not allow
routing (the green circle disappears on connecting to Master).

With QSynth/FS MIDI engine set to "alsa_seq", the ambiguous latency seems resolved, but introduces held-notes issue
(hiccups/xruns introduce note-off misses)

With QSynth/FS AUDIO engine set to pipewire (it's either-or) and MIDI to alsa_seq (I guess if audio is pipewire, MIDI
should NOT be jack) the situation is somewhat stable with regards to audio.

All in all, results in several issues to drive an external "module" routing back to Master in Pipewire mode.

0010393: Clip Cue window: 'Follow Count' is ignored on first started clip

Thu, 11 Jun 2026 18:01:08 +0000

Clips are only played once regardless of the 'Follow Count' setting if the green Letter left from all tracks is clicked.

Tests and screenshots are described here, too:
https://discourse.ardour.org/t/ardour-clip-cue/113380/3

0010392: Product version is actually 8.4

Thu, 11 Jun 2026 17:47:32 +0000

Ardour worked well with Scarlett Solo interface until recent Mint update. Scarlett shows active in system sound settings until
Ardour is launched. Scarlett disappears and re-appears after DAW has shut down. This might not be able to be corrected
on your side since it is apparently a Linux update that caused it.

Have pasted Ardour error log.

0010390: Pinch gesture not responding

Thu, 11 Jun 2026 16:34:42 +0000

Hi, I remember from v8 that it was possible to pinch the Editor, at least horizontally (and in some buggy miraculous occasions vertically).
The resulting behavior was a expansion reduction of :
- the track height vertically (when working)
- the time scale, horizontally.

I found it very useful and I wished both had been working seemlessly.

Now on 9.7, it seems like none of them is working, and yet I kind of remember the horizontal one still working on 9.0.

Is that normal?

0010391: vertical scrollbar for Stylus (or finger) scrolling in the Editor

Thu, 11 Jun 2026 16:23:54 +0000

Hi,
It would be nice to have a scroll bar on either side of the track names, to be able to drag up or down the tracklist of the Editor, when using Windows in Tablet mode, with or without a Stylus.

One of the important sub feature of this scrollbar would be to allow continuous scrolling (meaning : allowing to display tracks in a truncated way) with no magnetic jump from one track to the next when the scroll reaches a threshold.
(this is already a feature that I'd love to see with the trackpad, btw).

Thanks, and keep up the good work.

0010389: Increase allowable Region Envelope Gain to +12db?

Thu, 11 Jun 2026 13:21:08 +0000

Hey guys,

Oftentimes I'm editing drums (for example), and want to use region envelope to manually boost certain hits/transients.
I like using envelope automation for this to ensure a smooth, unnoticeable swings in loudness.
However, occasionally I find that I want to boost the original a little (or a lot) *more* than the current max. +6dB limit.

So, would you ever consider giving us more automation 'headroom' there, to something like max. +10 or +12dB?

Thank you for reading!
-J

0010388: Control Surface menu is completely blank

Thu, 11 Jun 2026 10:42:37 +0000

As per the summary. I cannot see my Nektar panorama P1 at all in this menu . It is however visible as a midi input

0010386: Please add action to nudge playhead with 1 second steps

Tue, 09 Jun 2026 05:41:16 +0000

The generic Mackie control surface nudges the playhead with 1 second steps when using the jogwheel.
There is, however, no user accessible action (https://manual.ardour.org/appendix/menu-actions-list/) that implements this operation. This makes it impossible to bind this operation to other keys/controls.

Suggested names:
"Common/nudge-playhead-forward-1sec"
"Common/nudge-playhead-backward-1sec"

Thanks.

0010387: Inconsistency in automation point levels at -infiity

Mon, 08 Jun 2026 20:45:35 +0000

I've been having trouble while editing automation points, seemingly pointing to the fact that what appears to be -inf dB isn't really. This leads to level inconsistencies if I try to create a fade-in and fade-out in between the two original points.

0010385: User modified surface bindings do not show

Mon, 08 Jun 2026 15:04:44 +0000

With a custom profile for the Mackie surface function keys not all (re)bindings show.

0010384: Custom MIDI map does not show in the list

Sun, 07 Jun 2026 16:12:33 +0000

When I create a custom control surface map (midi map) according to https://manual.ardour.org/using-control-surfaces/generic-midi/midi-binding-maps/#Getting%20Started, it does not appear in the list unless also contains a manufacturer.

I would have expected a map without manifacturer to appear under 'Other' but that isn't the case.

0010383: crash when Midi un-learn

Sun, 07 Jun 2026 10:26:33 +0000

When i click in the Cue Window on:
Midi un-learn

ardour 9.5 crashes:

[New Thread 0x7ffeca7fc6c0 (LWP 3141489)]
[New Thread 0x7ffec9ffb6c0 (LWP 3141490)]

Thread 1 "ArdourGUI" received signal SIGSEGV, Segmentation fault.
0x00007ffff4edd454 in std::_Rb_tree_increment(std::_Rb_tree_node_base*) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(gdb)

0010382: Crash with BadWindow when LV2 UI exits

Wed, 03 Jun 2026 09:13:21 +0000

The UI of an LV2 plugin, the idle() function of the LV2_Idle_Interface may return a non-zero value when the UI has been closed. In the LV2 doc it reads "in which case the host should stop calling idle(), and can either completely destroy the UI, or re-show it and resume calling idle()."

See: https://lv2plug.in/c/html/group__ui.html#structLV2UI__Idle__Interface

In ardour, the value returned from idle() is ignored: see libs/tk/suil/x11_in_gtk2.c, line 457 in suil_x11_wrapper_idle().

Consider this situation:

The UI of an LV2 plugin has and Exit button. The user clicks on it, and the UI destroys its widget (an X11 window)

The UI wrapper window ardour creates hangs empty and eventually ardour crashes with an X11 BadWindow error.

The error I see:

The program 'ardour-9.5.120' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 16061 error_code 3 request_code 25 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)

0010381: Keyboard Shortcuts - Solo based on region or range selection

Tue, 02 Jun 2026 21:36:13 +0000

I might be overlooking something but I noticed that the following action was not available.

If you go into Editor and you select one or more track boxes,
and use the default shortcut ALT+S,
this applies the "Toggle Solo" action.
Which makes sense.

Yet there does not seem to be a way to achieve this by selecting region(s) or range(s) within tracks?

Suggesting that an action/shortcut like this be added to Ardour.

Being that a Track Box and a Region/Range cannot be selected at the same time.
If there would not be any conflicts, I think an even better idea could be to allow the "Toggle Solo" action to achieve this action for selected track boxes, regions and regions within those track boxes.

If this is possible I think this could be something worth adding to Ardour.

Hopefully this makes sense
Thank You

0010378: Plugin Selector - Show highlight in plugin list pane after Up Arrow is applied

Tue, 02 Jun 2026 21:34:28 +0000

-The `Plugin Selector` opens with focus in the search field.
-When you type keyword into search field, the results show up in plugin list pane above
-If you hit your UP ARROW to move the focus up into that plugin list pane, it works, but no visual indication is shown, you have to then hit your UP or DOWN ARROW again, and then the cursor highlight becomes visible at the top of the list.

There might be a reason for this existing behavior, but if possible, I am suggesting to make the first UP ARROW key press, automatically show the cursor highlight in the plugin list pane above, this way user knows that this action worked.
Not all users might assume to hit the UP or DOWN ARROW again.

Thank You

0009909: Allow windows to be centered instead of where mouse cursor is located

Tue, 02 Jun 2026 21:33:47 +0000

I have mentioned this in the past.
Ardour is designed to open up dialogs, windows, plugin GUI windows where your mouse cursor is located.

To me this has always been very confusing and is the only program I have ever seen do anything like this.
Here are just a couple of examples of issues I have experienced with this behavior.

-Sometimes I use "X" or hotkey to close Ardour.
I still get tricked each time because I am looking in the center of my screen and do not see anything, I then think maybe I did not apply hotkey or click on the "X" correctly but then realize that the little "are you sure" dialog is opened somewhere on my screen already.
-Another issue is when in the Mixer when you click on effect button to open effect GUI window for the first time (remembers location for that session after) the effect GUI opens right on top of that mixer channel blocking anything from being seen, prevents the ablity to do things like open up another plugins window or even toggle that window back close if just checking something quickly.

Suggesting to add some options in Preferences - Quirks section :) to allow users to choose how / where these items are opened.
Could get tricky how many settings to add but I will mention some ideas and developers can choose if interested in adding this request.

QUIRKS
-Center dialogs and windows for their first open but remember their location/size after repositiioned
-Center dialogs and windows always (only remembering size adjustements)

Probably will not be considered but could also offer a different set of same settings mentioned above specifically for plugin GUI windows
-Center plugin windows for their first open but remember their location/size after repositiioned
-Center plugin windows always (only remembering size adjustements)

Thank You

0010379: Deleting tracks keeps plugin gui and jack port opened when midi keyboard is connected

Mon, 01 Jun 2026 13:23:23 +0000

After deleting a few tracks together (audio tracks, midi tracks, busses) , a plugin GUI is kept opened, and jack ports are still available.
See screen pictures.

Adding then a new track remove old GUI and ports, except if I try to add a track with same name that a deleted track, JACK reports that port_name is already existing and the old things aren't removed.

When I disconnect the midi keyboard (Novation Launchkey MK4), old GUIs and JACK port are removed immediatly.
If the keyboard is not connected, deleting tracks is OK.

Tested with 9.2 and 9.5