MantisBT - Issues

0010412: Region Envelope shows only when interaction occurs

Tue, 14 Jul 2026 08:04:22 +0000

Something I've noticed over the years but never mentioned...

After first opening a project, Region Envelope is only initially displayed once your mouse 'interacts' with the region (-by hovering over it). (--> See gif 1.)
Moreover, expanding and shrinking vertical track height makes envelope automation disappear and reappear seemingly randomly. (--> See gif 2.)

Suggestion:
It would be nice if region envelope *always* showed. : )

Thanks,
-Joe

[PS: Is this another macOS-specific graphics thing? o___o]

0010435: Import Window - Replace Search field with filter field and show all the time

Tue, 14 Jul 2026 08:03:33 +0000

I have many observations/suggestions to share about the current layout/behavior of the Import Window.

First off, do not care what this is called Search/Find/Filter, just concerned about its functionality. For this post I am going to refer to this as a Filter field.

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

ISSUES NOTICED
-When the Search field has focus, the common behavior is to be able to hit ESCAPE key to close the `Search` field, but I am suggesting to always be shown so not valid. The next option is to clear the field (which is what Keyboard Shortcuts dialog does).
Currently the `Import` window in general uses ESCAPE as a close shortcut, which then closes the `IW`.
Constantly do this out of habit, closing the `IW`.
`Plugin Selector` field does the same, closes the window when hit ESCAPE in filter field.
To me this is unexpected behavior.

-`Search` is an actual item at the top of `Places` sidebar.
If a user is using keyboard to navigate in this sidebar, a common behavior is to hit HOME key to bring cursor to the top.
When this is done in this sidebar, it applies focus to the `Search` entry at the top which then opens and applies the focus out of the sidebar and into the `Search` field.
To me this is unexpected behavior.

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

SUGGESTIONS
-Suggesting to remove the `Search` entry from the left sidebar "Places".

-Suggesting to replace the `Search` field with a filter field instead.

-Suggesting to make this `Filter` field be visible all the time.
(To get idea what this will look like, click on "Type A Name" button. Instead of "Location" it will be a Filter field.)

-You may say, well where would the "Location:" field go?
For the answer to this question please see the following post
https://tracker.ardour.org/view.php?id=10434

-This field would get common layout that all Filter fields do in Ardour (other then the odd layout used in Keyboard Shortcuts dialog search field)
Magnifying glass on the left side / then filter field / then button-icon to clear the field on the right side / recursive button at end of right side.

-Recursive button when applied will allow filter field to also display results within subfolders of current path, turning this field into a Search.

-Add common shortcut CTRL+F to apply focus into the Filter field.

-If this field already contains text, when focus is applied back into this field, that text will highlight automatically so user can just type over it with a new keyword.

-When Filter field has focus, hitting DOWN ARROW would bring the focus into the results shown in the file pane below.

-Not relevant to this post but do not want to make a new post about this.
Align the bottom of the left sidebar with the bottom of the file pane.
Currently the file pane is slightly shorter.

Thank you to anyone who reads this post

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

Tue, 14 Jul 2026 07:59:28 +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.

0010433: Option to append "mixer scene" name to filename during export

Mon, 13 Jul 2026 18:40:20 +0000

USE CASE
I use Ardour for producing practice tracks for a choir.
Each practice track has a different mix depending on which section/use it is for. e.g. Tenor with their part louder.
All of these audio files are produced from the same midi/audio tracks in the session.
I use the "Mixer scenes" to save the mix should I need to re-export due to changes (wrong notes etc). I can usually have 6 mixer scenes for one song.
To export each mix I have to type the mix name into the "label" field in the export screen to generate the right filename for the mix.

FEATURE REQUEST
It would be really useful to have an option on the export screen to append the currently selected "mixer scene" name onto the file name.
I realise this is a very specific use for the "Mixer scene" function but I could be used effectively for other cases where specific revisions are being exported for a client.
Having the name automatically appended would reduce typing, reduce the chance of misnaming an export, enable a user to export a new mix with the right file name in 3 clicks.

0010438: Unlocking Fun: A Beginner's Guide to Block Blast

Mon, 13 Jul 2026 02:56:55 +0000

Sometimes, all you need is a simple yet engaging puzzle to unwind. Forget complex narratives or intense action; the pure satisfaction of fitting shapes together can be incredibly therapeutic. And if you’re looking for a game that perfectly encapsulates this feeling, look no further than Block Blast. This delightful puzzle game offers a surprisingly deep and endlessly replayable experience, making it a perfect companion for a quiet evening or a short break.

https://blockblasts.io/

What is Block Blast?

At its core, Block Blast is a classic block-fitting puzzle game with a modern twist. The objective is straightforward: you're presented with a 10x10 grid and a continuous stream of different-shaped blocks. Your goal is to strategically place these blocks to form complete lines, either horizontally or vertically, which then clear from the board. The more lines you clear, the higher your score, and the longer you can keep playing. What makes Block Blast so compelling is its simplicity - there are no timers, no pressure, just the soothing challenge of making every move count. You can experience the game for yourself at Block Blast.

How to Play (or Master) Block Blast

Playing Block Blast is intuitive, but mastering it requires a bit of foresight and strategic thinking. You'll always have three blocks available at a time, giving you some flexibility in your choices.

Observe the Shapes: Before placing any block, take a moment to look at all three available shapes. Consider how they might fit together, not just for the current move, but for future possibilities.
Prioritize Line Clearing: Your main objective is to clear lines. Don't be afraid to sacrifice a perfectly placed block if it leads to clearing multiple lines simultaneously, which often results in higher scores and more space.
Think Ahead: This is where Block Blast truly shines. Unlike some other block games, new blocks don't appear randomly after each move. You know what three blocks are coming next, so plan your placements accordingly. Try to create "pockets" or areas where certain shapes will fit perfectly.
Avoid Crowding Corners: It's easy to fill up the edges of the board. While this can sometimes be useful, be mindful not to create unfillable gaps in the corners, as these can quickly lead to a "game over."
Embrace the Challenge: Don't get discouraged if your board fills up. Each game is a new opportunity to learn and improve your strategy.
Tips for a Better Block Blast Experience
Take Your Time: There’s no rush! This isn't a race against the clock. Think through your moves carefully.
Look for Combos: Clearing multiple lines with a single block placement (a "combo") is incredibly satisfying and boosts your score significantly.
Practice Makes Perfect: The more you play, the better you'll become at recognizing patterns and anticipating future moves.
Experiment with Strategies: There's no single "right" way to play. Try different approaches to see what works best for you. Sometimes, a seemingly awkward placement can open up a brilliant opportunity later on.

Conclusion

Block Blast is more than just a simple puzzle game; it's a wonderfully relaxing and mentally stimulating experience. Its straightforward mechanics hide a surprising depth of strategy, making it a game you can easily pick up but will keep coming back to. So, if you're looking for a delightful way to challenge your mind and unwind, give Block Blast a try. You might just find your new favorite way to relax.

0010437: Quantize window no longer appears

Sun, 12 Jul 2026 07:37:47 +0000

Quantize window no longer appears via shortcut, main menu nor right-click menu, as of version 9.7
(release, latest debug, local build all tested)

Works in 9.4

0010436: Import Window - Issues with Places being Bookmark

Fri, 10 Jul 2026 21:19:27 +0000

The `Import` Window (`IW`) has a `Places` sidebar on its left side.
This sidebar is mainly based on "Bookmarks" which I feel can lead to some issues/has limitations.

LIMITATIONS
-There is no way that the user can clean up this sidebar
-Many "Places" shown will not be used by user/Ardour
-Unused "Places" cannot be hidden
-Unused "Places" cannot be removed because they are "Bookmarks" and this will remove them from the users system, not just in Ardour.
-One of the main functions of the `IW` will be for audio samples.
If a user wanted to create entries for their audio sample folders, they get created as "Bookmarks".
This means that now those sample library based "Bookmarks" will have to appear throughout that users system (Desktop Environment based File Managers, Open file picker dialogs, etc.)
Which is not desired.
-And because of this, user will also not be able to sort these "Bookmarks" as desired for use in Ardour, because would then translate through system components that show/use "Bookmarks"

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

SUGGESTION APPROACH 1 - TWO SIDEBAR OPTIONS
-Existing "Bookmarks" based sidebar can remain for users who prefer this approach.
-Offer a secondary sidebar that is only Ardour based, not system "Bookmarks" based.
-Users can then setup their own desired "Places" links
-Users can manually sort this list of "Places" to their preferences
-Maybe these both could each be offered as their own "tabs"
Could be two different tabs in the current location of the "Places" header text is located.
Or if that is not agreed with then maybe an entirely new tab for this in the existing tab bar at the top of the `IW` window.

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

SUGGESTION APPROACH 2 - UPDATE EXISTING SIDEBAR
If above suggestion is not agreed with then maybe can make updates to existing sidebar
-Allow "Bookmarks" and any other entries that Ardour provides to be hidden. Can make them show up in a context menu with check boxes that user can choose which items to show?
This would just hide "Bookmarks" so they would not get literally removed.
-Could allow another "line separated" section that could allow user to add "Places" that would only be seen/used by Ardour.
(Basically a little version of the SUGGESTION 1 mentioned above)
-User would be allow to choose where this "new section" would appear. (Top, in between current "line separated" sections, bottom)

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

Not sure how much more time to put into this post, so I will stop here.

Thank you to anyone who reads this post

0010434: Import Window - Make breadcrumb address bar become text when button applied

Fri, 10 Jul 2026 21:16:15 +0000

Currently the `Import Window` shows a "breadcrumb" style address bar at the top.
There is a "Type A Name" button to its left that opens up a "Location:" field when applied.

Suggesting that when this button is clicked on, to just make the field show up in place of the "breadcrumb" style address bar.
This is common practice in most file managers.

I cannot edit this post to add a link, but I plan on making a post after this about replacing the space used by "Location:" field with Search/Filter/Find field.

0010135: Play Range-Selection plays beginning of non selected regions after

Fri, 10 Jul 2026 21:14:47 +0000

`Play Range/Selection` transport button / shortcut issue

Instead of stopping the playing at the end of a selected region, if there are any regions right after (edges align) you will notice it plays a short amount of the beginning of that next region.

Thank you to anyone who reads this

0010424: Ardour9.7.56 crashing on selecting an empty midi slot in cue grid that is supposed to open piano roll.

Wed, 08 Jul 2026 06:46:50 +0000

Ardour9.7.56 crashing on selecting an empty midi slot in cue grid and printing the following report:

Set cursor set to default
locate to 0 took 123 usecs for 1 tracks = 123 per track
ardour-9.7.56: ../libs/midi++2/midi++/midnam_patch.h:394: const std::string& MIDI::Name::CustomDeviceMode::channel_name_set_name_by_channel(uint8_t): Assertion `channel <= 15' failed.
Aborted ardour9

This happens most of the time on first start. If the crash doesn't happen on first attempt to open a piano roll of the cue, the following attempts after that don't cause the program to crash.
This crash happens to me about 90% of the time. The few times it does work (doesn't crash) I can not find out why.

0010431: Regions - When moving allow Escape key to cancel

Mon, 06 Jul 2026 20:34:43 +0000

`Grab` mode requires the holding down of LMB and dragging to perform a move action of a Region.
While holding down LMB and dragging Region away from its original location, if user decides to change their mind on the move, there is currently no way to cancel this action.
Suggesting to allow ESCAPE key to cancel move action.

Thank You

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

Mon, 06 Jul 2026 20:33:48 +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

0010430: Import Audio Midi Window - Window width adjusts when highlight stereo files

Mon, 06 Jul 2026 20:33:18 +0000

Must have `Auto play` check box "on" to experience this behavior.
Meter on the right shows single meter for mono files and splits into two meters to show stereo files.
When this occurs it increases the width of the actual Import window a little, slightly animating the window.

If you have a folder that contains both mono and stereo files,
as you navigate through those files, the window width keeps adjusting which is sickening :)

Suggesting to prevent Stereo files/meters from adjusting the Import windows width.

Thank You

0010375: Desktop Environment font size increases button size

Mon, 06 Jul 2026 20:31:18 +0000

I mentioned this on forum a while ago
https://discourse.ardour.org/t/desktop-environment-font-size-increases-button-size/110472

If user increases their Desktop Environments default font size, this causes Ardour to increase the size of its buttons shown in its `Application Bar`, but the text size itself does not increase.
This just causes more space to be used by the `Application Bar`.
In forum post linked above, this was said to be a possible bug that the text size does not increase.

Even if this did work, then this would also mean that it should increase the Menu Bar font size as well, etc.

I understand the thought of trying to make Ardour function like other applications in this way, but as it has been said Ardour is more of a unique application.
For example, in one of my recent posts I asked about setting to adjust font size without the need to scale the GUI and it was said that it is not possible.
So being that Ardour achieves font size/button size increases through a scaling method, to me it seems that this DE + Ardour connection should be removed.
(GUI scaling increase + this issue = even bigger buttons)

GTK
Also if user wanted to override/prevent a specific application from being affected by a DE setting such as font size, they would be able to achieve this through GTK. Now that Ardour has "absorbed" GTK2 as its own toolkit, I do not think this method is available any longer to the user?

So I am suggesting to remove this connection between DE and Ardour GUI
or
Provide some sort of way for user to prevent this from happening.

Thank You

0010429: Mackie Control: "single fader follows selection" only works for the first 8 stripables (X-Touch One)

Sat, 04 Jul 2026 20:30:36 +0000

On devices using (e.g. the Behringer X-Touch One), the fader only follows GUI track selection for stripables within the first n_strips() (8) positions of the session.
Selecting any track/bus beyond that: the fader drops to -inf and the scribble strip goes blank.

This matches an older unresolved forum report:
https://discourse.ardour.org/t/behringer-x-touch-one-channel-banking-issue/107252

Cause :
In MackieControlProtocol::stripable_selection_changed()
(libs/surfaces/mackie/mackie_control_protocol.cc), the loop that collects selected stripables increments 'added' for every stripable
SCANNED instead of every stripable MAPPED, so the search never looks past the first n_strips() entries of the sorted list:

for (; r != sorted.end() && added < (*si)->n_strips (false); ++r, ++added) {
if ((*r)->is_selected()) {
stripables.push_back (*r);
}
}

If the selected stripable sits beyond position 8, 'stripables' stays
empty and map_stripables() nulls every strip.

Fix

Only count stripables actually retained, so the scan covers the whole session while still mapping at most n_strips() per surface:

for (; r != sorted.end() && added < (*si)->n_strips (false); ++r) {
if ((*r)->is_selected()) {
stripables.push_back (*r);
++added;
}
}

Tested with an X-Touch One (MC standard mode, "X-Touch One" device file):
selection following now works for any track/bus in a session with
more than 8 stripables.

0010428: Horizontal scrolling could be smooth?

Fri, 03 Jul 2026 18:26:32 +0000

I've read about the vertical scrolling discussions on the ardour forum. Now i found, that i can use my second mousewheel to scroll through the timeline in ardour.
When doing that i get lost quite often, especially when i zoomed in a lot. I think that is because the image is jumping instead of gliding, so i loose track of the direction the view is moving.
When scrolling horizontally there could be a smooth scrolling, right? It seems to me there are no half track-issues or similar things.

0007144: Ardour's Pitch Shift doesn't work

Wed, 01 Jul 2026 03:11:31 +0000

I can't get any sound from a clip that I apply a pitch shift to. Watch the level meters in this clip.
https://youtu.be/vX2OeohMK5A

0010423: Ardour gives errors for a new session started from a template

Tue, 30 Jun 2026 18:37:58 +0000

Ubuntu Pipewire 24.04, but using regular Jack.

After going through the steps below Ardour will not play the recorded music except in very slow
spurts. Sometimes the playback head goes forward and then backward. The other
menus and buttons respond, but slowly, and only when a spurt happens.
Reopening the file gives the same behavior. Reloading the session does the
same thing. After reloading in safe mode the recordings will play, but the logic
fail errors keep flashing on the screen. This message (or one like it) is repeatedly
printed to the screen with a short time between the errors:

LOGIC FAIL sc @ 101720:224 using 117 1/4 notes per minute (144738462 sc-per-1/4) P@20639687778066/244320:0/61081|1|0
-- Stacktrace Thread: ArdourGUI
PBD::stacktrace(std::ostream&, int, unsigned long)
Temporal::TempoPoint::superclock_at(Temporal::Beats const&) const
Temporal::TempoMap::superclock_at(Temporal::Beats const&) const
Temporal::timepos_t::_superclocks() const
/opt/Ardour-9.7.0/bin/ardour-9.7.0(+0xc7cbf1) [0x62f8cc632bf1]
CairoWidget::on_expose_event(_GdkEventExpose*)
Gtk::Widget_Class::expose_event_callback(_GtkWidget*, _GdkEventExpose*)
_gtk_marshal_BOOLEAN__BOXED
g_closure_invoke
/opt/Ardour-9.7.0/lib/libgobject-2.0.so.0(+0x21e29) [0x70f6a29a3e29]
g_signal_emit_valist
g_signal_emit
/opt/Ardour-9.7.0/lib/libytk.so.2(+0x2c4814) [0x70f6a2ec4814]
gtk_main_do_event
_gdk_window_process_updates_recurse
_gdk_window_process_updates_recurse
_gdk_window_process_updates_recurse
_gdk_window_process_updates_recurse
/opt/Ardour-9.7.0/lib/libydk.so.2(+0x5306d) [0x70f6a317e06d]

LOGIC FAIL sc @ 101721:1020 using 117 1/4 notes per minute (144738462 sc-per-1/4) P@20639687778066/244320:0/61081|1|0
-- Stacktrace Thread: ArdourGUI
PBD::stacktrace(std::ostream&, int, unsigned long)
Temporal::TempoPoint::superclock_at(Temporal::Beats const&) const
Temporal::TempoMap::superclock_at(Temporal::Beats const&) const
Temporal::timepos_t::_superclocks() const
/opt/Ardour-9.7.0/bin/ardour-9.7.0(+0xc7cbf1) [0x62f8cc632bf1]
CairoWidget::on_expose_event(_GdkEventExpose*)
Gtk::Widget_Class::expose_event_callback(_GtkWidget*, _GdkEventExpose*)
_gtk_marshal_BOOLEAN__BOXED
g_closure_invoke
/opt/Ardour-9.7.0/lib/libgobject-2.0.so.0(+0x21e29) [0x70f6a29a3e29]
g_signal_emit_valist
g_signal_emit
/opt/Ardour-9.7.0/lib/libytk.so.2(+0x2c4814) [0x70f6a2ec4814]
gtk_main_do_event
_gdk_window_process_updates_recurse
_gdk_window_process_updates_recurse
_gdk_window_process_updates_recurse
_gdk_window_process_updates_recurse
/opt/Ardour-9.7.0/lib/libydk.so.2(+0x5306d) [0x70f6a317e06d]

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

Tue, 30 Jun 2026 05:58:39 +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.

0010421: trying to access the Control Protocol Settings from usb connected Shuttlepro2, causes Ardour to crash.

Sun, 28 Jun 2026 20:19:21 +0000

When clicking on the shuttle pro checkbox trying to enable the settings, the sound stops and ardour crashes.
It’s not possible to adjust the shuttle pro2’s settings inside ardours active surfaces.

0010419: Audio Export Timespan Display Range

Sun, 28 Jun 2026 14:31:37 +0000

When I export audio as a range the very first time (regardless if quick audio or stem export) within a recording session, my range does not appear. I have to close the export dialog box and reopen for the range to appear.
Been happening for me since 9.0

macos Ventura 13.7.8
Ardour 9.7

0010422: Working with Inserts could be much faster.

Sun, 28 Jun 2026 12:12:12 +0000

I think working with inserts could be much faster. Here is how i would save on mouseclicks:

1. When creating an insert automaticaly make the routing window open. There is no use for a insert if it's not routed immediately. This would save one click.
2. The default tab to open when a new insert is made could be "Hardware". This would save one more click before routing. (Inserts are mainly used for outboard gear, right?)
3. There could be a way to store typical routings. In example saving the compressor in and output as one bundle to choose and load from a dropdown menu. This would be much more comfortable in my opinion. Like this you would not even have to route in and out seperately.
4. Inserts could be copyable accros tracks. I know it prevents from mixing signals on outboardgear and getting a doubled mix back. Still i think, that when a user copys an insert there is probably an intention behind that. For example quickly copying the routing of an insert to another track. Maybe a good option would be to only allow one active insert of the same routing?

0009373: Add possibility to collapse / expand a group (aka "folder track")

Sat, 27 Jun 2026 02:56:14 +0000

Please make a feature in Ardour to enable collapse/expand a tracks group - something like a "folder track" known from other DAWs.
If you have a plugin (eg. virtual drums) that fans out into 16 or more separate tracks, this would be desired to collapse all these tracks and keep edit area organized and clear.
Thanks!

0010420: Crash when expanding the boundary of a split region in the pianoroll

Fri, 26 Jun 2026 16:19:06 +0000

After splitting a long MIDI region, deleting the left-hand part, and moving the remaining region to the beginning of the timeline, an empty area is still visible on the left side when the region is opened in the pianoroll.
Attempting to expand the region boundary into this empty area causes Ardour to crash with the following assertion:

ardour-9.7.90: ../libs/ardour/location.cc:344: int ARDOUR::Location::set_start(const Temporal::timepos_t&, bool): Assertion `_start.is_positive() || _start.is_zero()' failed.
Aborted

I believe it's related to 0010136 as the root issue seems to be the same.

0010348: MIDI Chase Playback causes note at beginning of region to drone

Fri, 26 Jun 2026 07:14:32 +0000

When 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.