APPLICATION ERROR #804

Profile not found.

Please use the "Back" button in your web browser to return to the previous page. There you can correct whatever problems were identified in this error or select another action. You can also click an option from the menu bar to go directly to a new section.
Previous non-fatal errors occurred. Page contents follow.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8973 [ardour] features tweak always 2022-09-27 10:17 2022-09-29 11:56
Reporter: johne53 Platform: Microsoft  
Assigned To: OS: Windows  
Priority: normal OS Version: 10  
Status: new Product Version: Mixbus 8.x  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Inconsistent Snap options
Description: In Mixbus's Editor window, just above the rulers, there's a button saying 'Snap' and to the right of it there's another button offering the various Grid options. And the Edit menu (Edit->Snap & Grid) also contains a list of Grid options. For the most part, selecting an option in one menu will reflect the same option in the other.

Unfortunately though... the two menus offer different options so sometimes, selecting an option in one menu will leave the other menu showing no selection. Is that intentional or do the two menus need to be brought into sync?

Or maybe one of them isn't needed any more ?
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0026590)
johne53   
2022-09-29 11:56   
I found this early return in 'gtk2_ardour/editor.cc' which I thought might be causing the problem:-

bool
Editor::grid_type_is_musical(GridType gt) const
{
    switch (gt) {
    case GridTypeBeatDiv32:
    case GridTypeBeatDiv28:
    case GridTypeBeatDiv24:
    case GridTypeBeatDiv20:
    case GridTypeBeatDiv16:
    case GridTypeBeatDiv14:
    case GridTypeBeatDiv12:
    case GridTypeBeatDiv10:
    case GridTypeBeatDiv8:
    case GridTypeBeatDiv7:
    case GridTypeBeatDiv6:
    case GridTypeBeatDiv5:
    case GridTypeBeatDiv4:
    case GridTypeBeatDiv3:
    case GridTypeBeatDiv2:
    case GridTypeBeat:
    case GridTypeBar:
        return true; // <--- returns early !!!
    case GridTypeNone:
    case GridTypeTimecode:
    case GridTypeMinSec:
    case GridTypeCDFrame:
        return false;
    }
    return false;
}

However, I rebuilt with that line commented out but it didn't change anything. I've also discovered that this affects both Mixbus and Ardour but the bit I'm not sure about is whether it's intentional.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8964 [ardour] bugs minor always 2022-09-19 21:37 2022-09-26 08:38
Reporter: Mitsch Platform: Ubuntu Studio  
Assigned To: OS: Linux  
Priority: normal OS Version: 04.22  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Aux Send reaction on mouse scrolling is slow
Description: There is principally a good mechanism in ardour using the scroll wheel on faders:
* Just scroll wheel: fast
* Scroll wheel with Ctrl pressed: slow
* Scroll wheel with Ctrl+Alt pressed: very slow

There is an exception of this rule. When using the scroll wheel on auxiliary sends, it goes:
* Just scroll wheel: slow
* Scroll wheel with Ctrl pressed: very slow
* Scroll wheel with Ctrl+Alt pressed: slightly before "no move at all"

I wonder if this is intended. If not, I'd love to see this behavior changed to one I experienced on other faders.
Tags:
Steps To Reproduce: Use a channel strip with an auxiliary send, set the pointer over it and scroll.
Additional Information:
System Description
Attached Files:
Notes
(0026581)
x42   
2022-09-19 22:41   
This is mysterious. There should be no difference and scroll-wheel works exactly the same (also the small inline fader).

Do you have a mouse with a latching (clicking) scroll-wheel, or do you use a touch-pad (or middle-click scroll emulation)?
I'm asking because the inline fader reacts to both horizontal and vertical scroll, with a touch-pad, a diagonal scroll can cancel out any changes.

I cannot reproduce the issue here (nor can other users I've just asked on IRC).
(0026582)
Mitsch   
2022-09-20 21:08   
Yes, I do have a latching scroll wheel. My preferred input device is a wired "Logitech Track Man Wheel" trackball. But I have mice with which I had the same result.
To be more precise I show you the dB change I'm getting delivered.

Faders (edit window or main fader of mixer window), count from 0.0 dB:
* Scroll wheel only: -5.7 dB / (+)4.7 dB for 5 scroll events from latch to latch.
* with CTRL: -0.1 dB / (+)0.1 dB for each scroll event.
* with CTRL and Alt, you need 10 events to scroll +/-0.1dB

This is totally okay for me. A very good experience.

Auxiliary Sends, count from 0.0 dB:
* Scroll wheel only: -5.69 dB / (+)4.71 dB for 5 scroll events. (Seems to be identical with the faders behavior. My fault! I had this wrong in my mind when writing the bug report!)
* with CTRL, I need between 3 and 5 scroll events to get +/-0.01 dB (I mean 0.01, not 0.1!)
* with CTRL and Alt, you need 45 scroll events to get +/-0.01 dB

Just in case, you're still getting other results: I'm using german locales. In rare cases, some programs can't deal with this or showing strange behaviors like this… But of course, it can also relate to Ubuntu's build options…
(0026589)
Mitsch   
2022-09-26 08:38   
Can this behavior be reproduced?


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8972 [ardour] bugs major always 2022-09-24 22:46 2022-09-25 00:23
Reporter: yurivict Platform: GNU  
Assigned To: OS: Linux  
Priority: high OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Splash screen never disappears with the "Indexing Plugins ..." message
Description: I have several packages of LV2 plugins installed installed:
gxplugins-lv2-0.9 Set of LV2 plugins from the guitarix project
infamous-plugins-lv2-0.3.0.7 LV2 plugins for various sound effects
invada-studio-plugins-lv2-1.2.0 Set of LV2 audio effect plugins, ported from VST
lv2-1.18.4 Open standard for audio plugins (successor to LADSPA)
x42-plugins-lv2-20220714 Collection of LV2 plugins (submodules)

The Ardour splash screen never disappears.



clang-14
FreeBSD 13.1
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0026586)
x42   
2022-09-24 23:12   
Which desktop environment do you use?

Some (like KDE) do not follow freedesktop.org specs, in Ardour you can work around this via Preferences > Appearance > Quirks > Show/hide splash screen instead of setting z-axis order.

You can launch Ardour with --no-splash option as well.
(0026587)
x42   
2022-09-24 23:13   
Then again this may be a different issue, related to LV2 scanning (not a splash screen issue after all. Does `lv2ls` work and list all plugins?
(0026588)
yurivict   
2022-09-25 00:23   
I use xfce4 DE.

lv2ls lists all LV2 plugins instantly.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8971 [ardour] bugs major always 2022-09-23 11:16 2022-09-24 20:29
Reporter: thebutant Platform: Ubuntu  
Assigned To: paul OS: Linux  
Priority: high OS Version: (any)  
Status: resolved Product Version: Mixbus 8.x  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Opaque/transparent audio regions destroys other regions when placed on top
Description: When placing an opaque region on top of some other audio region, anything that's under the opaque region is destroyed.
Tags:
Steps To Reproduce: Have 2 audio regions.
Make one of them opaque / transparent.
Place the opaque one on top of the other region.
In my case, this destroys whatever's under the opaque region.
Additional Information:
System Description
Attached Files:
Notes
(0026583)
paul   
2022-09-23 20:55   
What does "destroy" actually mean here?
(0026584)
thebutant   
2022-09-24 05:19   
In my case, placing the opaque region over another region makes this other region disappear completely in the range of the opaque region.
That's what "destroys" means.

I cannot stack regions, because the one underneath is completely eaten og digested by the opaque region.
(0026585)
paul   
2022-09-24 20:29   
This was a bug introduced during recent-ish development. Thanks for noticing. It has been fixed in the Ardour codebase, and the fix will appear in a future Mixbus minor release.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8965 [ardour] features minor always 2022-09-19 22:13 2022-09-19 22:13
Reporter: Mitsch Platform: Ubuntu Studio  
Assigned To: OS: Linux  
Priority: normal OS Version: 04.22  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: automation mode "touch" blocks direct value editing and editing via scrolling
Description: I'd prefer to directly write values with the keyboard or using the scroll wheel to edit automation, but unfortunately, in the edit window both seem to be blocked in "touch" mode. You can only edit if you click and hold the fader and move it.

This could be intended, but I can't see the point.
Tags:
Steps To Reproduce: In the edit window, start f.e. a "Trim"-automation with "write" mode in a channel strip. Stop transport, so automation automatically switches to "touch". Go ahead with transport and stop it again, after some time. Double click on the fader, it changes to an input dialog where you can change the value to a desired one and hit enter: Nothing changes. It should have switched to the desired value and set a new automation point.

In the edit window, start f.e. a "Trim"-automation with "write" mode in a channel strip. Stop transport, so automation automatically switches to "touch". Go ahead with transport and stop it again, after some time. Hold shift and use the scroll wheel over the fader that should be changed: Nothing happens. But it should like using the fader in "manual" mode and set a new automation point.
Additional Information:
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8962 [ardour] bugs crash always 2022-09-19 04:23 2022-09-19 04:23
Reporter: Revelations11 Platform: Microsoft  
Assigned To: OS: Windows  
Priority: high OS Version: 10  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Problema Rejilla y plugins
Description: Saludos equipo de Ardour.

Mi problema es que cuando intento configurar la rejilla a 1/16 no realiza nada, solamente funciona hasta 1/8 note, pero de 1/16 en adelante no sirve, tampoco veo para configurarla a 1/2 note, por otro lado, inserto un plugin llamado Total EQ de Hornet Plugins y esta en formato VST 3 y no funciona, no hace nada, instale su VST 2 y este sale como error, abro otro DAW y funciona el plugin, pero en Ardour no funciona, no hace nada, espero me puedan brindar y dar una solucion a estos problemas. Agradezco de antemano la pronta respuesta y solucion muchas gracias.
Tags: grid, plugin
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8961 [ardour] bugs major always 2022-09-14 00:19 2022-09-14 01:25
Reporter: graymon Platform: Microsoft  
Assigned To: x42 OS: Windows  
Priority: normal OS Version: 10  
Status: resolved Product Version: 6.9  
Product Build: Resolution: no change required  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: ACE Fluid Synth Cannot Play SF2 Soundfonts in Windows
Description: ACE Fluid Synth Cannot Play SF2 Soundfonts in Windows.

Tags:
Steps To Reproduce: Create Midi Track using ACE Fluid Synth
Apply sf2 sound font by browsing file system
Attempt to play virtual keyboard notes.

Successful:
Install sforzando from https://www.plogue.com/products/sforzando.html
Reload plugins
Create Midi Track using sforzando
Apply sf2 sound font by browsing file system
Attempt to play virtual keyboard works as expected.
Additional Information: Downloaded Bass soundfonts from here:
https://www.producerfeed.com/files/soundfonts/21-bass-sf.rar


The project was created in Linux and the filesystem copies over to Windows, but it failed when using a brand new session.
System Description
Attached Files:
Notes
(0026578)
x42   
2022-09-14 00:39   
Which .sf2 file are you using?

After unpacking the rar there are 22 files. I have tested`Bass/1276-FReTLeZzz.sf2` `Bass/336-ACBass.sf2` and `Bass/336-Squierbass.sf2` and they work just fine with a quick test.
(0026579)
graymon   
2022-09-14 01:21   
I turned off Ardour - started another new project and all the sound fonts are working now. I guess that's good news, but I feel stupid. I even loaded up the apps that were started in Linux, and now adding a new midi track with the Fluid Synth works also. I can no longer duplicate the problem. Please close this one out. If it happens again, I'll try to figure out what is different in my setup. Thanks for checking this for me, and sorry for the misreporting.
(0026580)
x42   
2022-09-14 01:25   
No problem. I thought perhaps you have loaded the .rar file directly.. but if you can reproduce it again, please let us know. perhaps there's a detail we have missed.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8926 [ardour] features feature always 2022-06-15 18:48 2022-09-13 17:25
Reporter: mrmrrs Platform: Debian GNU  
Assigned To: OS: Linux  
Priority: high OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: MIDI learn without middle mouse button (using a trackball)
Description: Hello. :)

Is there a way to assign a different mouse button for mapping a parameter to a MIDI controller?

As Ardour awaits a middle mouse click on a parameter, to map it to a MIDI controller and I use a trackball ("Kensington Orbit"), that has no middle mouse button, it would absolutely make sense to be able to specify other buttons for MIDI mapping. I know, that many people use trackballs in studios, as they are more practical in terms of space requirement on a mixing desk. However, the Kensington Orbit has buttons for left click, right click and a scroll wheel (non-clickable). The ball is also non-clickable.

The most practical way would be a right click (on any parameter), while pressing the left "ALT" key on the keyboard, as this combination has no particular function in this context.

Have I overlooked an option or is this really not a feature? If the latter is true, please, add this. :))
I don't want to produce e-waste, by just buying a three-button mouse. As the trackball is fully working.
It is also more ergonomical and less likely to cause carpal tunnel syndrome.

Thank you in advance. Namaste.
Best regards,
Philip
Tags: Accessibility, automation, control, feature request, feature-request midi, features, GUI, hotkey, improvements
Steps To Reproduce: Using a two-button mouse or trackball and trying to use the third button. :D
Additional Information:
System Description
Attached Files:
Notes
(0026482)
x42   
2022-06-15 19:26   
This is currently not configurable (but may become so in future versions).

On Linux/X11 a common solution to use "Evdev Middle Button Emulation" press left+right mouse button emulates a middle-mouse button press.
(0026577)
mrmrrs   
2022-09-13 17:21   
Thanks! I am absolutely looking forward to it. :)

In the meanwhile I have successfully set up the emulation.
Somehow it seems to work everywhere else but within Ardour.

For example:
Firefox acknowledges such a button press and reacts accordingly by opening an URL as a new tab or closing a tab etc..
Nautilus also reacts, as expected, by opening a folder as a new tab.
Ardour either does nothing or only acknowledges one of the two buttons.

And I have tried to exactly time the simulatneous press of these buttons.
But as all other applications correctly recognize the emulation as a third button press,
I presume Ardour ignores the time window set for the press or the whole emulation itself.

Is there a need to modify the file "/home/"username"/.config/ardour6/ui_scripts"?
And if so, could you please share a piece of code to be put in there to enable Ardour to recognize the evdev emulation?

If you need some log file or screenshot in this regard, please, let me know.

Thanks in advance. Namaste.

Best regards,
Philip


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8777 [ardour] features minor have not tried 2021-07-18 15:43 2022-09-12 12:51
Reporter: unfa Platform:  
Assigned To: x42 OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 6.8  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: LUFS normalisation for audio regions
Description: Right now the audio region normalization can be done based on Peak and Peak RMS measurements.
What is missing is LUFS Integrated.

The only sensible way to perform LUFS normalization at this moment is to perform loudness analysis, write down the LUFS value, do math in your head and apply gain manually.
Since the Analysis dialog is blocking access to the rest of Ardour, this is extra tedious to do, especially if you need to normalize multiple regions (like for example: mastering an album and doing quick loudness normalization after importing your mixes to get in the ballpark before doing manual loudness matching.

Another way would be to import regions, then mark them all with ranges on the timeline and export them using loudness normalization, then import them again.
As you can imagine, neither of these solutions is optimal.

Since LUFS normalization is already present in the export process in Ardour, I hope it shouldn't be too hard to add in here as well.
What do you think?
Tags: audio, loudness, LUFS, normalisation
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0026057)
x42   
2021-07-18 16:12   
(Last edited: 2021-07-18 16:12)
When is this useful?

Can you think of any workflow that should encourage normalizing to perceived loudness when you later mix or master the the result, which significantly changes the perceived loudness?

(0026058)
unfa   
2021-07-18 18:32   
As I've written above - a rough level matching for album mastering is the main use-case for me but I believe I also needed this when working with sound effects, can't remember what it was though. Since EBU-R128 is the best perceived loudness model we have, it makes sense for me to use that instead of peak RMS which is in my mind an inferior solution for the same problem (unlike peak or true peak - these ensure no clipping).
(0026063)
x42   
2021-07-20 02:57   
implemented in Ardour 6.8-186-gf457225d08 -- feedback is welcome.
(0026064)
unfa   
2021-07-20 07:59   
Awesome, thank you! I will test it and give feedback.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8960 [ardour] bugs crash always 2022-09-11 18:59 2022-09-11 18:59
Reporter: secke Platform: x86_64  
Assigned To: OS: Ubuntu  
Priority: normal OS Version: 20.04  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ardour-6.9 with Presonus Faderport V2 segfaults on Section->Next
Description: Using a Presonus Faderport V2, when I'm in "Section" mode and hit "Next", Ardour reliably crashes.

Also happens in other circumstances, but this is easiest way to reproduce.

It seems that the "Next" button or turning the dial right is part of the misbehaviour in most cases.

Also note that in "Channel" mode (after hitting the button "Channel", when it is lit) the "Prev" button works as expected (selecting the previous track) while "Next" has no discernable effect.

Most other controls seem to work as expected.
Tags: control surface, crash
Steps To Reproduce: * Start Ardour
> bin/ardour6 -n
* Create new session
* Choose "Empty Template"
* Audio setup:
    - Audio System: ALSA
    - MIDI System: ALSA raw devices
* Start
* Configure control surface:
    - Edit -> Preferences -> Control Surfaces -> PreSonus FaderPort2
    - -> Show Protocol Setting: select Faderport MIDI connectors (Faderport device reacts)
* Close dialogs
* On the Fadeport device:
    - Hit "Master"
    - Hit "Section"
    - Hit "Next"

After a few moments, Ardour crashes.

Instead of the crash, I'd expect Ardour to do-the-right-thing™ (e.g. select next region), show an error dialog ("you can't do that here") or do nothing except writing a log entry.
Additional Information: On Ubuntu 20.04 (kernel: Linux 5.4.0-125-generic 0000141-Ubuntu SMP Wed Aug 10 13:42:03 UTC 2022 x86_64)
Presonus Faderport V2 attached via USB
Focusrite Scarlett 2i2 soundcard attached via USB (crash also happens with other soundcards)

Ardour version:
> secke@Dobrindt:~$ /opt/Ardour-6.9.0/bin/ardour6 --version
> Ardour6.9.0 (built using 6.9 and GCC version 6.3.0 20170516)

Attached files:
* ardour-log_2022-09-11_003 -> contents of the Ardour log until BEFORE the crash
* ardour-out_2022-09-11_003.txt -> shell output of the Ardour process
* _opt_Ardour-6.9.0_bin_ardour-6.9.0.1000.crash.head -> first part of created crash file, without actual core dump (too big to upload)
* Faderport-Test.tar.gz -> tarball of created session, saved just before triggering the crash

----

MIDI events

In Ardour's MIDI tracer, pressing "Next" in "Channel" mode is reported like this:
> 39566314 NoteOn chn 1 19 7f
> 39566314 NoteOn chn 1 19 00

(Note that in "Channel" mode pressing "Next" does NOT cause a crash, but merely does nothing.)

Using an external MIDI tracer, I see that in "Section" mode, "Prev" and "Next" generate the following MIDI events:
> Controller, Channel 1 | Controller: 60 - Control 28 LSB, Value: 65 # "Section"/"Prev"
> Controller, Channel 1 | Controller: 60 - Control 28 LSB, Value: 1 # "Section"/"Next" (causing the crash)

For comparison, these are "Prev" and "Next" in "Channel" mode:
> Note On, Channel 1 | Note: 46 (A#2), Velocity: 127 # "Channel"/"Prev" (selects previous channel)
> Note Off, Channel 1 | Note: 46 (A#2), Velocity: 64
> Note On, Channel 1 | Note: 25 (C#1), Velocity: 127 # "Channel"/"Next" (does nothing in Ardour)
> Note Off, Channel 1 | Note: 25 (C#1), Velocity: 64
System Description
Attached Files: ardour-log_2022-09-11_003 (2,326 bytes) 2022-09-11 18:59
https://tracker.ardour.org/file_download.php?file_id=4214&type=bug
ardour-out_2022-09-11_003.txt (2,122 bytes) 2022-09-11 18:59
https://tracker.ardour.org/file_download.php?file_id=4215&type=bug
_opt_Ardour-6.9.0_bin_ardour-6.9.0.1000.crash.head (101,788 bytes) 2022-09-11 18:59
https://tracker.ardour.org/file_download.php?file_id=4216&type=bug
Faderport-Test.tar.gz (3,550 bytes) 2022-09-11 18:59
https://tracker.ardour.org/file_download.php?file_id=4217&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
5579 [ardour] bugs text always 2013-07-12 05:31 2022-09-11 00:03
Reporter: dbolton Platform:  
Assigned To: x42 OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 3.0  
Product Build: Resolution: duplicate  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Disable "Opaque" option in MIDI regions context menu
Description: Currently all MIDI regions act "transparently" when stacked/overlaid. However context menu shows a checkmark next to "[region name] > Edit > Opaque".

Expected behavior: The "Opaque" menu option should not have a checkmark (since the region acts transparently). Additionally the menu item should be grayed out to indicate that Ardour doesn't support opaque MIDI regions.

Discussion: According to las on IRC, opaque MIDI regions would "present some very, very difficult logic to implement. We would have to synthesize note on and note off events". Since the feature is unlikely to be implemented, the UI should to be updated to reflect this fact.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0026575)
x42   
2022-09-11 00:03   
9 years later.. and this has just been implemented.

I'm closing this, please provide feedback at 0005100


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
5100 [ardour] features major have not tried 2012-09-10 15:33 2022-09-11 00:01
Reporter: colinf Platform:  
Assigned To: x42 OS:  
Priority: normal OS Version:  
Status: feedback Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 3.X  
Summary: MIDI regions are always transparent
Description: When two or more MIDI regions overlap, notes from all overlapping regions play, regardless of the opacity of the upper regions.

I think that:
 (a) the opacity of MIDI regions should be choosable
 (b) they should be opaque by default

This would make them behave just like audio regions, which I think would be much less confusing.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0014081)
paul   
2012-10-17 22:26   
this is a very deep problem.
(0014553)
colinf   
2013-01-22 11:58   
I know this is unlikely to be implemented before 3.0.

However, I'd request that for the moment, MIDI regions be explicitly marked as transparent (and maybe not allowed to be made opaque).

That way, if some future version of A3 does allow opaque MIDI regions, sessions containing overlapping MIDI regions will continue to sound the same when loaded.
(0020615)
colinf   
2019-03-20 23:14   
This still bugs me, six years later...
(0024326)
inFlowiaLab   
2020-05-31 18:17   
The problem is still relevant. Without its solution, working with MIDI takes is very unproductive. You have to mute every take except for the active one. This is slow, and it is completely different from recording takes of ordinary non-MIDI sound.
(0024327)
paul   
2020-05-31 18:45   
I wonder why I said this was so deep.
(0024328)
paul   
2020-05-31 18:52   
Oh, I see why.

The earliest/leftmost boundary of a currently-topmost MIDI region has to act as an "all notes off" for every note currently on.

This is trivial if every region completely covers all the ones below it. But if they are "staggered", then this becomes quite challenging. There is also the question of what happens to notes in a lower region that span the entire length of the upper region.

so yeah, inFlowiaLab, I understand why this is tricky for your workflow. But its quite hard to solve for the general case, and when we don't do that, people will run into those scenarios very often. In your case, since you appear to be completely "covering" one take with another, I would just delete the existing region (it isn't deleted from the session or disk) or switch to a new playlist.
(0024329)
inFlowiaLab   
2020-05-31 19:20   
> "There is also the question of what happens to notes in a lower region that span the entire length of the upper region."

It should sound until the upper region begins. Then she must shut up forever.

> "In your case, since you appear to be completely "covering" one take with another, I would just delete the existing region (it isn't deleted from the session or disk) or switch to a new playlist."

But I do not want to delete the recorded duplicates until I decided which one suits me. I record several takes, listen to them several times, choose the best one and leave it. And while I choose with MIDI clips, I have to drown out all the duplicates except one, listen to it, then drown it out, turn on another, listen to it, drown it out to turn on another and so on. With AUDIO thoughts, everything is simpler - I listen to the upper double, then I select another and raise it up - and it already sounds, I do not need to drown out all the doubles. Just pick the one you want and go up.

I'm not sure if using playlists to record takes is a good idea. Is there really a way to record duplicates in a loop, automatically placing each in its own separate playlist, and then quickly switch between playlists when choosing the best take? (As fast as this can be done with layers of AUDIO clips.)
(0026573)
colinf   
2022-09-09 22:51   
Looks like this is now implemented in edd78000 (& preceding), though I haven't tried it yet...
(0026574)
x42   
2022-09-11 00:01   
As of Ardour 7.0-pre0-3455-g38c5ae4237 layered obscured MIDI regions is now fully implemented.

At the start of an opaque region above a lower region, pitch-bend and CCs values that were modified by a lower regions are either reset or restored to the the prior state (if available).
The main motivation here is to provide an easy way to loop-record and comp with consistency.

Please test.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8947 [ardour] other minor always 2022-07-26 14:46 2022-09-05 10:30
Reporter: johne53 Platform: Microsoft  
Assigned To: OS: Windows  
Priority: normal OS Version: 10  
Status: new Product Version: Mixbus 8.x  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: File size creepage even though nothing's changed
Description: I've discovered this in Mixbus though I'm not sure if it's intentional or a bug... basically, each session file contains a GUIObjectState section looking like this:-

      <GUIObjectState>
        <Object id="rtav 7" height="68" visible="1"/>
        <Object id="automation 68" height="68" visible="0"/>
        <Object id="automation 70" height="68" visible="0"/>
        <Object id="automation 7 12/0/0" height="68" visible="0"/>
        <Object id="automation 83" height="68" visible="0"/>
        <Object id="automation 87" height="68" visible="0"/>
        <Object id="rtav 19" height="68" visible="1"/>
        <Object id="automation 106" height="68" visible="0"/>
        <Object id="automation 108" height="68" visible="0"/>
        <Object id="automation 19 12/0/0" height="68" visible="0"/>
        <Object id="automation 121" height="68" visible="0"/>
        <Object id="automation 125" height="68" visible="0"/>
        <Object id="strip 7" visible="1" strip-width="Wide">
          <Object id="processor 94"/>
        </Object>
        <Object id="strip 19" visible="1">
          <Object id="processor 132"/>
        </Object>

       // rest of the object

        <Object id="automation 10108" height="98" visible="0"/>
        <Object id="automation 10110" height="98" visible="0"/>
      </GUIObjectState>

Near the 'rtav' objects, each number after the word 'automation' corresponds to an object id somewhere else in the file (typically an automation control / pan control / trim control or whatever). But towards the end of GUIObjectState there's usually a long list of orphaned objects whose 'automation' value doesn't correspond to any value elsewhere in the file. And each time the user presses 'Session->Save' another of these objects gets created and stored. So the file size creeps gradually upwards, even if nothing changed between this save and the last save. Is this behaviour intentional or a bug?
Tags:
Steps To Reproduce: Simply press Session->save with an existing session (without changing anything else)
Additional Information:  It seems to be present in files having ver 6000 or ver 7000 but I don't see it in earlier files.
System Description
Attached Files:
Notes
(0026567)
johne53   
2022-08-16 07:55   
This is still present here in both Ardour and Mixbus - though in Ardour's case it doesn't seem to affect every session. Maybe someone could try it on Linux or Mac?
(0026572)
johne53   
2022-09-05 10:30   
I'm still not sure if I've found a bug or if this gradual 'creepage' is intentional... but FWIW I booted into Linux this morning and I'm seeing exactly the same effect here in Linux.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8958 [ardour] bugs minor have not tried 2022-09-01 18:15 2022-09-01 18:15
Reporter: danx64 Platform: Microsoft  
Assigned To: OS: Windows  
Priority: normal OS Version: 10  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Plugins LV2 failed
Description: Plugins LV2 fallan al ser cargados y no se muestra su GUI respectivamente generan clicks en el audio
Tags: Ardour, audio, GUI, PLugins
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8957 [ardour] bugs minor sometimes 2022-08-29 08:57 2022-08-30 18:50
Reporter: raoul86 Platform: Arch  
Assigned To: OS: Linux  
Priority: low OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Problem with Ardour plugin GUIs
Description: problem with some pluggins (drumgizmo, setbfree, x42eq...) impossible to edit with double click...
it seem to be this issue which work :

"I found suil 0.10.16-2 has a different issue where plugins can only open once in Ardour, best solution is to downgrade back to suil 0.10.12-1.

sudo pacman -U https://archive.archlinux.org/packages/s/suil/suil-0.10.12-2-x86_64.pkg.tar.zst"
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8956 [ardour] bugs major always 2022-08-27 11:15 2022-08-27 20:57
Reporter: lucienkacrofts Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: urgent OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Scrubber audittion function not working
Description: Selected the quick edit Scrubber option for listening to a section of a waveform (cursor changes to a small speaker symbol) then hold left mouse button and scan back and forward over wave form. This should produce audio at whatever speed / direction you move the mouse. On left click the speaker symbol disappears, the play head marker jumps to the position of the cursor but does not move, the counter does not move and no audio is produced. After many attempts i got an error message saying 'memory pool full recompile with larger amounts'. This audition function worked in Ardour 5.12 from the ubuntu 20.04 repo but no longer works in Ardour 6 +.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0026571)
lucienkacrofts   
2022-08-27 20:57   
Just installed Ardour 6.9 on Windows 10 64bit and the same problem as with the Linux version.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8907 [ardour] bugs major always 2022-04-24 02:34 2022-08-25 19:50
Reporter: johnthebard Platform: Debian GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Click in audio at 41 bars audible with various distortion plugins.
Description: There's a click at 41 bars which is inaudible without distortion but consistent with distortion. The click stays regardless of where the audio lines up with 41 bars.
Tags:
Steps To Reproduce: Enable either ZynDistortion or GxAmplifier-Stereo-X one at a time, and play the audio so that the playhead passes 41 bars.

Moving the audio around has no effect on the click happening at 41 bars.
Additional Information: Project file was sent via email to paul
System Description
Attached Files:
Notes
(0026557)
paul   
2022-08-12 13:29   
I think I fixed this? Do you recall?
(0026570)
johnthebard   
2022-08-25 19:50   
Yes, it turns out it was an issue with plugins and I just so happened to use several plugins in a row to test that have that issue. The 41 bar location was where a loop marker was which was (if I remember correctly) causing some kind of buffer reset the plugins responded poorly to.

We talked about it in IRC and I forgot to mention here/close this when we figured it out.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8955 [ardour] bugs block always 2022-08-23 12:48 2022-08-23 13:54
Reporter: Kilgharrah Platform: Microsoft  
Assigned To: OS: Windows  
Priority: low OS Version: 10  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: VST Gui not opening (6.9 demo)
Description: After adding a Vst3 instrument(produced with st4 and synister) to a project, the gui does not open.
Tags: GUI, VST
Steps To Reproduce: Attempting to load a vst plugin in the demo 6.9 ardour(windows 10) with
"edit->references->plugins->Automatically open the plugin gui when adding a new plugin" enabled.
and "edit->preferences->plugins->Don't automatically open the plugin GUI when the plugin has an inline display mode" DISABLED.
Additional Information: Trying to demo ardour to determing if its right for me. since my vsts arent configurable(which they have to be) i cannot do that, and i dont event think the retail version of ardour will support it.

I want to enjoy and use ardour, i really do.
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8848 [ardour] features minor N/A 2022-01-02 20:02 2022-08-18 15:28
Reporter: colinf Platform: Debian GNU  
Assigned To: paul OS: Linux  
Priority: normal OS Version: (any)  
Status: resolved Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Improve MIDI region unlinking behaviour
Description: Presently, there's no way to unlink multiple linked regions but have them remain linked to each other.

It might be useful in some cases, when unlinking multiple selected regions all at once, to preserve the links within the region selection rather than creating a new source for every region.

E.g.: if we have a set of linked MIDI regions A, A, A, A, it could be useful to be able to select (say) the last two and unlink them, and end up with A, A, A', A', where the regions A' are still linked.
Tags:
Steps To Reproduce:  
Additional Information:
System Description
Attached Files: 0001-gtk2_ardour-implement-Unlink-from-unselected-for-MID.patch (10,231 bytes) 2022-07-11 21:36
https://tracker.ardour.org/file_download.php?file_id=4195&type=bug
Notes
(0026500)
colinf   
2022-07-11 21:36   
Path attached: plenty of room for improvement, but it Works for Me.
(0026569)
paul   
2022-08-18 15:28   
applied and pushed, thanks!


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8419 [ardour] features minor have not tried 2020-09-22 15:44 2022-08-16 18:06
Reporter: cooltehno_bugs Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.3  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Rude Automation HIDE/SHOW button
Description: Proposal is to add a Rude button to hide all/ Show all existing automation.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files: toggle-existing-automation.gif (571,608 bytes) 2022-08-16 18:06
https://tracker.ardour.org/file_download.php?file_id=4213&type=bug
Notes
(0025051)
cooltehno_bugs   
2020-09-22 15:52   
or may be this could have a shortcut...
(0026568)
cooltehno_bugs   
2022-08-16 18:06   
Recently I've found the View > Automation > "Toggle All Existing Automation"/ - That's super. I've just assigned a shortcut through the Keyboard Shortcuts dialog Alt-K - and got the desired function. I don't understand why nobody didn't know this...?


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8953 [ardour] bugs major random 2022-08-12 14:24 2022-08-15 21:50
Reporter: FabienB Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ardour is randomly crashing with Jack server (segmentation fault)
Description: When used with Jack server, Ardour is randomly crashing whatever the complexity of the current session (can happen with a simple audio track). It can happen a few seconds after the opening of a session or half an hour later during playback without a particular interaction. Run in a terminal, I have a "Segmentation fault" output for each crash. Here is a gdb backtrace (a part of, I can add the full BT if needed):

--Type <RET> for more, q to quit, c to continue without paging--

Thread 26 "audioengine" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffcc19f700 (LWP 3050)]
0x00007ffff7454e1b in ARDOUR::PortManager::run_input_meters(unsigned int, long)
    () from /opt/Ardour-6.9.0/lib/libardour.so.3
(gdb) thread apply all bt

[…]

Thread 26 (Thread 0x7fffcc19f700 (LWP 3050)):
#0 0x00007ffff7454e1b in ARDOUR::PortManager::run_input_meters(unsigned int, long) () from /opt/Ardour-6.9.0/lib/libardour.so.3
0000001 0x00007ffff745762b in ARDOUR::PortManager::cycle_start(unsigned int, ARDOUR::Session*) () from /opt/Ardour-6.9.0/lib/libardour.so.3
#2 0x00007ffff7057722 in ARDOUR::AudioEngine::process_callback(unsigned int) () from /opt/Ardour-6.9.0/lib/libardour.so.3
#3 0x00007fffcf4592fb in ARDOUR::JACKAudioBackend::process_thread() () from /opt/Ardour-6.9.0/lib/backends/libjack_audiobackend.so
0000004 0x00007fffd80491f2 in ?? () from /lib/x86_64-linux-gnu/libjack.so.0
0000005 0x00007fffd8062280 in ?? () from /lib/x86_64-linux-gnu/libjack.so.0
#6 0x00007ffff0892609 in start_thread (arg=<optimized out>) at pthread_create.c:477
#7 0x00007fffee48b133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

[…]

Tested on Ubuntu 20.04.4 LTS and Ardour 6.9.0 (Official build), Jack is provided by KXStudio repository (jackd version 1.9.12).
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0026561)
x42   
2022-08-12 14:42   
This could have a number of causes. The backtrace is from an optimized version of Ardour (without line-numbers) so we cannot tell. A few that come to mind:

* If you have any MIDI devices and hotplug them after starting Ardour, this is a known issue and fixed for upcoming Ardour 7.0. Meanwhile connect them before starting Ardour
* you have manually disabled `work-around-jack-no-copy-optimization` in the config
* an issue with jack 1.9.12 which is from 2017 is rather old at this point and has some known bugs that can also cause this

PS. Unless you have a specific need for JACK, prefer Ardour's ALSA backend
(0026566)
FabienB   
2022-08-15 21:50   
Thank you for your answers. I have checked the two first points and still have the problem. I do use ALSA backend for "in-the-box" projects but need sometimes Jack for bridging VCV Rack for example (VCV VST plugin does not work yet in Ardour). I will try with Ardour 7 and an updated Jack server.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8939 [ardour] bugs major always 2022-07-09 20:27 2022-08-12 19:14
Reporter: Nonlinear Platform: Microsoft  
Assigned To: OS: Windows  
Priority: normal OS Version: 10  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Some VST3 plugins produce no output - ALL VST3 plugins show I/O error in plugin manager
Description: Every VST3 plugin I have checked in Ardour's plugin manager shows the following errors:

[Info]: VST3: \ error getting busInfo for bus: 0 rv: 0, got type: kMain
[Info]: VST3: \ error getting busInfo for bus: 0 rv: 0, got type: kMain

Some VST3 plugins work properly while others receive input but produce no output back to the DAW - like they are perpetually bypassed. They LOOK like they are working (their meters move, etc.) but the processed sound is not returned to the DAW.

VST2 versions of the same plugins work properly.
Tags:
Steps To Reproduce: 0000001) Scan plugin in plugin manager and view report. (All VST3 plugins report I/O bus errors.)
#2) Insert VST3 plugin in any track or bus and listen for output change when turning knobs, etc. (Some plugins work, some don't.)
Additional Information:
System Description
Attached Files: Ardour VST3 errors.png (165,978 bytes) 2022-08-12 19:14
https://tracker.ardour.org/file_download.php?file_id=4212&type=bug
Notes
(0026499)
Nonlinear   
2022-07-09 20:34   
There appears to be no way to edit my post so I will add info here. This issue is with regard to 3rd party VST3 plugins - of all brands. Some work some don't but ALL report the I/O error. The reason I marked this "major" is because a user can inadvertently think the plugin is working when it is in fact not affecting the audio at all.
(0026559)
x42   
2022-08-12 13:45   
At this point it time Ardour's VST3 host supports only "one main bus, and one aux-bus. Also an optional aux-bus by itself is currently N/A.
(0026560)
x42   
2022-08-12 13:47   
Which plugin(s) are affected by this?
(0026563)
Nonlinear   
2022-08-12 17:50   
>>At this point it time Ardour's VST3 host supports only "one main bus, and one aux-bus. Also an optional aux-bus by itself is currently N/A
The error I am reporting here is shown for all VST3 plugins including 2in/2out plugins. Every VST3 plugin I have checked in plugin scan shows this error "[Info]: VST3: \ error getting busInfo for bus: 0 rv: 0, got type: kMain". Some VST3 plugins produce audio output while others simply pass the signal thru unaffected.

>>Which plugin(s) are affected by this?
It's not specific to any particular plugin brand or plugin title - and those plugins that don't work in Ardour work fine in all other DAWs. Therefore, there appears to be a VST3 interface issue in Ardour.

If others users have noticed this issue they probably blame it on the plugin(s) and move along. Please do some checking on your own and don't take my word for it!
(0026564)
x42   
2022-08-12 17:58   
Yes, as I said above it is not a plugin issue, but missing support for specific VST3 configurations in Ardour

I am curious if you have a VST3 that has more than one output bus or announces an output bus as main out, and hence does not currently work correctly in Ardour.
So far the only one I know is Addictive Drums in multi-out mode.
(0026565)
Nonlinear   
2022-08-12 19:14   
To be clear, there are two problems here:

1) EVERY VST3 plugin shows up in the Plugin Manager as having I/O bus errors - including major brands like Fabfilter, Izotope and Waves. Please see attached screenshots. This is not due to a "specific VST3 configuration".

2) Some plugins, even those with only stereo I/O (no aux buses) - do not process the audio and pass it through unaffected. AFAIK, all plugins announce their main I/O bus as "Main". That is the Steinberg VST3 default labeling for main pins regardless of any aux pins. I cannot explain why some plugins work and others don't.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8759 [ardour] bugs minor always 2021-06-23 07:36 2022-08-12 16:44
Reporter: CTS Platform: Arch  
Assigned To: paul OS: Linux  
Priority: normal OS Version: (any)  
Status: assigned Product Version: 6.7  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: MIDI learn does not have any effect
Description: When using the MIDI learn (ctrl-middle click) feature, parameters appear to acknowledge incoming MIDI when mapping but the controller fails to have any effect on the parameter value itself.

I noticed this when I was testing issue 0008756, in an earlier commit there was usually at least "some" sporadic movement of the parameter in response to the controller movements. In the most recent commit I tested (8ad1405cf5e83a31017d88ee6706c819b484a37c) parameters appear entirely unresponsive.
Tags:
Steps To Reproduce: 1. Start Ardour
2. Enable Generic MIDI under preferences -> control surfaces. Select your controller for Incoming MIDI.
3. Create an audio track
4. Ctrl - middle click on a fader, see pop-up "operate controller now"
5. Move a control knob or something on your controller, see that the MIDI control message is acknowledged as the popup disappears
6. Continue moving your controller and observe that the mapped parameter does not respond to the incoming messages (i.e. nothin happens!)
Additional Information:
System Description
Attached Files:
Notes
(0026395)
paul   
2022-04-16 00:52   
There are several possibilties.

One is that your controller is using encoders and not "real knobs". These send just "+1" and "-1" messages, and cannot be used with MIDI learn.

Another is that you may need to sweep the knob through the whole range in order to "engage" with the parameter under control.
(0026558)
paul   
2022-08-12 13:29   
status?
(0026562)
CTS   
2022-08-12 16:44   
Hey Paul, it looks to be largely fixed in Ardour7 (commit b03e9b4). Still broken in Ardour6.9. I am just testing by trying to map one of the virtual dials on the virtual keyboard to a track fader. Thank you!


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8952 [ardour] bugs minor always 2022-08-12 14:08 2022-08-12 14:08
Reporter: FabienB Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: low OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: "Clear all xruns" is not working
Description: In the Ruler, Location Markers, right-click menu proposes "Clear all xruns" option which is not working. "Clear all locations" is working and delete markers and xruns as well.

Tested on Ubuntu 20.04.4 LTS and Ardour 6.9.0 (Official build).
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8855 [ardour] bugs minor always 2022-01-08 20:41 2022-08-12 13:44
Reporter: magnetophon Platform: Linux  
Assigned To: OS: NixOS  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: No audio inputs for Surge VST3
Description: The VST3 version of both 1.9 and XT don't have audio inputs when used in Ardour.
According to baconpaul it's not a Surge issu but an ardour one: ihttps://github.com/surge-synthesizer/surge/issues/5743#issuecomment-1008144854
The LV2 and standalone work fine.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0026292)
x42   
2022-01-08 21:13   
Yes, it's not just surge, but applies to other VST3s as well.
At this point it time Ardour's VST3 host supports only "one main bus, and one aux-bus. Also an optional aux-bus by itself is currently N/A.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8920 [ardour] features minor have not tried 2022-06-01 11:34 2022-08-12 13:44
Reporter: johne53 Platform:  
Assigned To: OS:  
Priority: low OS Version:  
Status: new Product Version: Mixbus 8.x  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: VST plugin issue with multi-output plugins
Description: Sorry if I'm duplicating an entry here. AFAICT it isn't possible to search the entries using text. You need to search for a specific bug ID number (is that just me misunderstanding something..?) Anyway...

Over on the Mixbus forum there've been reports about VST3 plugins not working if they offer multiple outputs (more than 2 presumably...) The older VST2 plugins support multiple outputs okay apparently.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0026478)
x42   
2022-06-02 01:15   
Probably not a duplicate, but currently expected behavior, which is also documented in the manual.

Ardour only supports one optional bus for VST3 plugins (usually side-chain input), and does not support variable I/o for VST3 plugins. Addressing this is on the long-term ToDo list.

(VST2 does not support variable I/O, an instrument with multi-channel output will always have all those outputs)
(0026479)
x42   
2022-06-02 01:18   
This is not a Windows specific issue, but Ardour/VST3 related.

Conceptually VST3 bussing is at odds with how Ardour internally handles variable-i/o (which is heavily inspired by audio unit). Solving this will require a major internal overhaul.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8923 [ardour] other major always 2022-06-08 00:01 2022-08-12 13:24
Reporter: BluesInGMusic Platform: Debian GNU  
Assigned To: paul OS: Linux  
Priority: normal OS Version: (any)  
Status: feedback Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: it will not completely download. At least thats what my computer says.
Description: When i tried to use the system, I get a notice my "text writer1"will not be able to "complete the download"' I have 1 TB of memory, at least, available, so space isn't a problem. My computer system is 22.04 LTS Jammy Jellyfish. I already paid $4 before the download. I do not know what is going on. I know $4 is not a lot of money, but I'm on the hook for $4 a month now. Granted I am new to computers, but I haven't been able to access the download. Don't know what to do. thanks.
Tags:
Steps To Reproduce: I have tried for hours, to "complete the download". It's the same thing every time.
Additional Information: tried to get info from Ubuntu but not much luck, there.
System Description
Attached Files:
Notes
(0026556)
paul   
2022-08-12 13:24   
This is a bug tracker about errors in Ardour itself.

Issues with downloading should go to help@ardour.org or our IRC channel or our forums.

Did you ever manage to download the software? If not, were you able to cancel your subscription?


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8951 [ardour] bugs major always 2022-08-10 13:04 2022-08-11 21:29
Reporter: thebutant Platform: Ubuntu  
Assigned To: paul OS: Linux  
Priority: high OS Version: (any)  
Status: acknowledged Product Version: Mixbus 8.x  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Unable to copy and paste modwheel automation
Description: When editing modwheel automation, I'm mostly unable to copy and edit nodes from one place to another.
Sometimes I can actually copy and paste, but then they appear in random places and not where I asked to.
Tags:
Steps To Reproduce: Make a midi region with modwheel automation.
Try to copy and paste automation nodes. See it the appear where you'd think they should, or if they appear somewhere at all.
Additional Information:
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8022 [ardour] features minor always 2020-04-19 10:16 2022-08-11 20:00
Reporter: sonnie Platform: Some Other Linux  
Assigned To: paul OS: Some Other Linux  
Priority: normal OS Version: unknown  
Status: feedback Product Version: 6.0-pre1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Tint background color of Mixer- and Editor-Channel (Header)
Description: I love to have a fast overview. For years other DAWs can optinally tint background color of the mixer strips for faster overview. I'd love to see this in Ardour.
Tags: color, mixer
Steps To Reproduce: -
Additional Information: -
System Description
Attached Files: ardour editor.jpg (89,762 bytes) 2020-04-21 07:39
https://tracker.ardour.org/file_download.php?file_id=3597&type=bug
reaper editor mixer.jpg (212,734 bytes) 2020-04-21 07:39
https://tracker.ardour.org/file_download.php?file_id=3598&type=bug
ardour mixer.jpg (266,377 bytes) 2020-04-21 07:39
https://tracker.ardour.org/file_download.php?file_id=3599&type=bug
ardour mixer track color.jpg (538,888 bytes) 2020-04-22 17:11
https://tracker.ardour.org/file_download.php?file_id=3605&type=bug
ardour mixer track color-2.jpg (538,888 bytes) 2020-04-22 17:11
https://tracker.ardour.org/file_download.php?file_id=3606&type=bug
ProotoolsMixer.jpg (322,299 bytes) 2020-04-22 17:45
https://tracker.ardour.org/file_download.php?file_id=3607&type=bug
ardour-mixer-colored.png (222,630 bytes) 2022-07-19 18:11
https://tracker.ardour.org/file_download.php?file_id=4200&type=bug
colored_mixer.png (115,964 bytes) 2022-08-10 01:27
https://tracker.ardour.org/file_download.php?file_id=4205&type=bug
aug10.png (167,158 bytes) 2022-08-11 04:19
https://tracker.ardour.org/file_download.php?file_id=4206&type=bug
grafik.png (26,633 bytes) 2022-08-11 05:56
https://tracker.ardour.org/file_download.php?file_id=4207&type=bug
aug10-2.png (173,815 bytes) 2022-08-11 06:28
https://tracker.ardour.org/file_download.php?file_id=4208&type=bug
aug-11-m.png (167,571 bytes) 2022-08-11 14:47
https://tracker.ardour.org/file_download.php?file_id=4209&type=bug
aug-11-e.png (163,956 bytes) 2022-08-11 14:47
https://tracker.ardour.org/file_download.php?file_id=4210&type=bug
grafik-2.png (14,374 bytes) 2022-08-11 19:49
https://tracker.ardour.org/file_download.php?file_id=4211&type=bug
Notes
(0021397)
paul   
2020-04-19 13:47   
Please explain more clearly what you mean by this. Do you mean "use the track color as the background of the mixer strip for that track" ?
(0023838)
sonnie   
2020-04-21 07:16   
use the track color as the background of the mixer strip for that track. I use pretty big screens and its hard go get an overview without the "coloured backgrounds" in mixer (or editor in track headers - where solo/mute and volume is located) just with the group bars above.

Maybe its more reasonable with some pics.
(0023848)
ahellquist   
2020-04-21 23:34   
This is really a much needed feature IMHO. I tend to scroll in larger project while trying to read the labels of the tracks.. If there are 19 vocal tracks in a row it is hard to find what I am looking for. It really doesn't help to use a small screen for that matter.. Having Colors like above would make things quite convenient.

Or in a shorter form:
+1
(0023862)
paul   
2020-04-22 16:45   
@sonnie: those are not track colors at all, but group colors.
(0023863)
sonnie   
2020-04-22 17:11   
@paul: Yes. Is there a different way to color the tracks (not the audio/MIDI items). These are way better for my eyes for a fast overview than these small track color bubbles. (see pic attached)
I run sessions with 50-100 tracks+ and its very, very hard to see fast, what track is what type.
(0023866)
ahellquist   
2020-04-22 17:45   
Plain old Protools has this appearance which is quite handy if you are looking for one of the two dark green tracks and are in a hurry.
(0023867)
itsmonika   
2020-04-22 18:22   
Ok this make some sence
(0023868)
paul   
2020-04-22 19:48   
I should be clear here: I welcome an option to color mixer strip backgrounds.

But there's a lot of language appearing here about "track colors", whereas what is shown in the screenshots from other DAWs are not individual track colors, but group colors.
(0023871)
sonnie   
2020-04-23 07:22   
"whereas what is shown in the screenshots from other DAWs are not individual track colors, but group colors. "

No, in Reaper and Pro Tools it's called "Track Colors". But nevermind, we now know, what I initially meant. Thanks for your help. :)
(0026176)
sonnie   
2021-10-06 09:18   
Will this be a feature of Ardour 7? :)
(0026517)
tanjeffmoos   
2022-07-19 18:11   
I also vote for this feature.

In Ardour, each track in the mixer has a little color bubble on the top. It would be great if that color was more appearent on the whole mixer strip. I gimped an example of how it might look like :)

I'm well aware that implementing this is harder than using Gimp.
(0026539)
paul   
2022-08-09 22:20   
Now in git master via commit bfedf7168e
(0026543)
x42   
2022-08-10 01:27   
I do like at @tanjeffmoos mockup, but the current state of coloring the whole strip incl faceplace of the fader and meter is not helpful and introduces visual clutter in my opinion.
Also the master-bus be exempt but VCAs should also have an outline (like tracks). The faders should not default to blue but the fader/meter area get colored depending on track type (again).

For those who cannot compile from git, the current state looks like :
(0026544)
tanjeffmoos   
2022-08-10 06:00   
I agree with x42 that the current version looks distracting, because there is too much color in the fader/meter area. Or maybe it is just too much contrast between the bright background color and the dark fader/meter.

Coloring the fader and meter (as x42 proposed) would reduce contrast. But I think that recoloring the meter is non-trivial, because it uses multiple colors (white and red ticks, green/yellow/red bars) which need to work with any background color the user chooses. Also, there are other meters with other tick colors (e.g. K20).

I suppose that you mainly colored the background of the strip. Are fader and meter grouped using a box widget? If so, it might help to change the background of that box back to gray (this would look more like my mockup). It might be simpler to implement.
(0026545)
x42   
2022-08-10 12:15   
> Coloring the fader and meter (as x42 proposed) would reduce contrast.

I proposed to revert that that area to how it was before. The box with the fader and meter should just be boring gray (for busses), boring blue-gray (for Audio tracks), and green-gray (for MIDI tracks), like it is when not using track-color. Like in your screenshot above (https://tracker.ardour.org/view.php?id=8022#c26517)

More nitpicking: Currently the brightness of the track color is increased. IMHO, that is also not the correct approach. The color should be used as is.
If this is an issue with the "flat & boxy" theme (the track header button is not distinguishable), increasing saturation would be my choice. Alternatively make it darker with a dark theme and brighter with a bright theme.

--

PS. Harrison Mixbus has an entirely different approach to this: the mixer-strip itself is not colored, the background remains unchanged, only the Fader itself is colored.
(0026546)
paul   
2022-08-11 04:19   
new approach underway. feedback welcomed.
(0026547)
tanjeffmoos   
2022-08-11 05:56   
I like the approach, it looks very clean.

But there is a corner case: It a fader is all the way down, almost no color will be visible. My suggestions are:
- Colorize the "comment" button. Its color does not indicate any status, hence a new color won't do any harm.
- Add a colored horizontal ruler below the fader/meter and above the "group" button, just do indicate the strips color.
- Colorize the fader background with a darker (or brighter?) version of the strip color.

Here are two examples of how a ruler could look like.
(0026548)
paul   
2022-08-11 06:27   
the name button at the *top* is already colored
(0026549)
paul   
2022-08-11 06:28   
here's a corresponding view of the editor view
(0026550)
paul   
2022-08-11 14:47   
OK, here are two screenshots of the current state of play (similar to above but master bus is uncolored, and fader bgs are correct)

Again, any feedback is welcome
(0026551)
tanjeffmoos   
2022-08-11 18:53   
> the name button at the *top* is already colored
Yes, but it is far away from the bottom :-)

The current approach looks professional. Even the 0,0-markers are colored, I love such details!
(0026552)
paul   
2022-08-11 19:26   
"0,0-markers" ??
(0026554)
tanjeffmoos   
2022-08-11 19:49   
This line. How it is named correctly?
(0026555)
x42   
2022-08-11 20:00   
I think "unity position marker" -- although in different contexts (faders for plugin automation) it's the "default value marker"


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8950 [ardour] bugs major always 2022-08-10 12:52 2022-08-11 19:39
Reporter: thebutant Platform: Ubuntu  
Assigned To: paul OS: Linux  
Priority: normal OS Version: (any)  
Status: resolved Product Version: Mixbus 8.x  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Modwheel nodes become unavailable/difficult to edit after splitting a midi region.
Description: When recording a miditrack with modwheel, it's useful to edit the modwheel automation afterwards (if something was a bit off).
In Mixbus 8.1 this is still possible, but not after dividing/splitting the recorded miditrack.
I can still edit the modwheel nodes as usual in the first, original midi region, but not in the new part, the one that was split off. In this new region I cannot select more nodes than one at the time (or if I press ctrl, I can pick one and one and one and one).
If I undo and the region is one whole again, I can select several modwheel nodes and edit them as I wish, but as soon as the region is split, this new region (the second one) will not let me select more than one modwheel node at the time.
Tags:
Steps To Reproduce: Record a midi region with modwheel automation.
Divide the midi region.
Try to select several automation nodes in the second region (in edit mode).
At least for me I can not drag my mouse and select them anymore, I have to pick one at the time (but I can select several if I press ctrl and pick one at the time, however this is rather time consuming).
Undo, so the region becomes one whole again, and you can drag your mouse and select multiple nodes.
Additional Information:
System Description
Attached Files:
Notes
(0026553)
paul   
2022-08-11 19:39   
This is now fixed in git master and will be in the 7.0 release of Ardour. It may or may not be in the next release of Mixbus, due to release schedules.

BTW, the bug applied to any MIDI automation at all, not just modwheel or bender.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8232 [ardour] features minor have not tried 2020-06-14 12:42 2022-08-09 23:56
Reporter: unfa Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 6.0  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: We really need a vertical scroll bar
Description: If you'd rather listen to me talking about this and show you what I mean, here's a quickly made video:
https://youtu.be/8Lmq9TRblXw

If you prefer to read, here goes:

My Ardour sessions tend to have a lot of tracks.

I scroll the sessios a lot trying to find the stuff I need.

And I realized there's a very simple, but missing component in Ardour.

A scroll bar.

Why?

A scroll bar clearly shows the user how much stuff there is , and what portion of the stuff they are currently looking at.
It may also allow to quickly jump to a different place, if the user knows what he's looking for.

I can't tell you how much time I'm wasting simply scrolling up and down trying to find that one track. The lack of a scroll bar makes it very hard for me to create a mental image of the vertical space in my session. And even if I had one, I can't immediately jump to that part.

A very basic scroll bar (like the horizontal one in the Mixer view) would do, but Ardour could go a step further and make the scroll bar actually represent the session contents to make the navigation easier.

What if the scroll bar shown colored horizontal bars representing the tracks buses and VCAs? What about vertical lines showing groups?
This could make the vertical navigation of the session so much better. it is terribly inefficient right now.

Unless there's some secret techniques I haven't discovered yet.

Yes, there's the Tracks & Busses side bar. I probably should start using that more. The problem is - for this to be useful I need to give it at least 200 pixels in width, which takes away from the precious editor space. And if I give it less space it's gonna be very easy to misclick and disable a track. It's a sharp tool, so I need to be careful not to cut myself.

What I'm thinking of would not need more than 32 pixels of width, and it would be used *only* to navigate - no data entry allowed (so you can't screw anything up).

The horizontal session navigation is very good - the "Overview" allows me to clearly see what is there, and what part of it I am looking at as well as allowing me to jump places quickly.
But there is no such thing for vertical navigation.

I think once in the past the "summary" on the bottom served for vertical navigation as well, but not any more. Even when it did - the amount of pixels vertically was just not enough to make it useful. A vertical scroll bar needs to be tall.

What do you think?
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: Mockup.png (159,460 bytes) 2020-07-03 10:04
https://tracker.ardour.org/file_download.php?file_id=3750&type=bug
MeterBridge.png (32,909 bytes) 2020-07-03 10:56
https://tracker.ardour.org/file_download.php?file_id=3752&type=bug
Screenshot_20200703_140046.png (105,320 bytes) 2020-07-03 12:01
https://tracker.ardour.org/file_download.php?file_id=3753&type=bug
Screenshot_20220810_004558-1.png (79,102 bytes) 2022-08-09 23:00
https://tracker.ardour.org/file_download.php?file_id=4204&type=bug
Notes
(0024465)
muzikermammoth   
2020-06-15 04:15   
What i do is, i open the panel on the right, and select the tracks and busses tab. In that tab, there is a list of all the tracks and the various switches such as record, mute, active, viewable. Clicking on the names gets ardour to focus on the track in the editor panel. I can even select multiple tracks on this list and ardour will display those. The hot key 'z' will also maximise and focus ardour on selected tracks. Used in conjunction with 'shift - z', which undoes this view, I can zoom focus on one view, and undo to return back to a previous view.

Hope that helps
(0024466)
mhartzel   
2020-06-15 05:06   
I agree that a vertical scrollbar is a simple but valuable tool and I really miss it. It may be easy enough to navigate without it when you have 10 tracks, but not anymore when you have 50. Also as unfa mentioned it also lets you see your vertical position in the track list and the size of the scroll bar shows your vertical "zoom" level also. This helps you create a mental image of your position when you move around. So when we lost the scroll bar we lost three functionalities.
(0024467)
muzikermammoth   
2020-06-15 05:57   
The workflow which i described really comes into its own when trying to align clips within multiple tracks. By selecting tracks to focus on, and pressing 'z', only these tracks are displayed by ardour. In this way the editor view with the tracks becomes a fluid changing interface. Though i do see why the lack of a scrollbar to be a strange omission in any widget that displays content as a list.
(0024473)
mhartzel   
2020-06-15 15:43   
I tried the workaround and I agree this is helpful. You can fit 35 - 40 track names there and focus on single or multiple tracks. I didn't know this feature existed :)
(0024539)
paul   
2020-07-01 16:14   
"The horizontal session navigation is very good - the "Overview" allows me to clearly see what is there, and what part of it I am looking at as well as allowing me to jump places quickly.
But there is no such thing for vertical navigation."

It shows the whole session vertically also.
(0024550)
unfa   
2020-07-01 16:33   
Paul - that's not enough though. You can't see much with 60 pixels of height in the summary panel. You also can't scroll vertically using it.

Have you read my report or watched the video?
(0024551)
paul   
2020-07-01 16:48   
Sorry, my mistake. It once allowed for vertical scrolling.
(0024552)
paul   
2020-07-01 16:49   
(side note: the summary panel can be resized).
(0024556)
unfa   
2020-07-01 18:58   
Yes, vertical scrolling was possible at some time, but even then it was quite limited due to the vertical space available.

(no problem)

Right now the summary panel doesn't visualize what vertical part of the session the user is currently looking at - so it's not helping to build a mental image of the session contents in that dimension. I honestly liked that function, but it wasn't still ideal, as to have any decent precision in vertical scrolling, one had to make the pane quite large, stealing precious space from the track contents themselves.

I think a narrow vertical scroll bar could do a great job with a relatively small pixel cost.

The summary can be resized, true - but for sessions with 50+ tracks, it'd need to be quite big to be of any use (IMO), and it'd use up a lot of pixels for that, while a narrow vertical bar could be much more efficient with it.

I could try and prepare a mock-up to show you what I imagine it could look like if you're interested.
(0024566)
x42   
2020-07-02 20:03   
"...And even if I had one, I can't immediately jump to that part..."
As you mentioned yourself, click on the track in the editor's sidebar, that moves the track into view and selects it.

There are various issues with a vertical scrollbar. Firstly there is no good place to put it. Left of the editor's sidebar is no good place, it's hard to hit it with the mouse.
The bar in the scroller changes its size every time a track's height is resized (which is very common when using "F" and visual-undo), it also snaps in intervals that are not even (due to different track heights and automation lanes). The scrollbar was removed a few versions back because it was pretty much useless due to those issues (and more).
(0024594)
unfa   
2020-07-03 09:14   
x42:

> As you mentioned yourself, click on the track in the editor's sidebar, that moves the track into view and selects it.

That is true, though because there's a bunch of active controls and the track names are very small it's really hard to do.
I think that it could be modified or extended with a different mode to facilitate the problems I'm having with the current design.

> There are various issues with a vertical scrollbar. Firstly there is no good place to put it. Left of the editor's sidebar is no good place, it's hard to hit it with the mouse.

Well, I'm not sure what you mean - a default place virtually all software use is the right edge of the container the scoll bar affects. I think it would make sense between the timeline and an extra panel opened.

> The bar in the scroller changes its size every time a track's height is resized (which is very common when using "F" and visual-undo), it also snaps in intervals that are not even (due to different track heights and automation lanes).

I didn't think about this - but I think it could be solved. The scroll bar should represent a scaled down version of the track, bus, lane and VCA layout and reflect the size of these elements (to help the user connect that with what he sees in the timeline canvas to build a mental image of the session. I think that the snapping shouldn't be that much of a problem.

> The scrollbar was removed a few versions back because it was pretty much useless due to those issues (and more).

Ah I see. I don't remember when I last saw it, but I think I used it, and suddenly I realized I'm missing something.

Maybe then the Tracklist tab could be extended to ease vertical navigation?
I think it'd need three things:

- Give an option to hide the toggles so users can't disable or hide track by misclicking
- Hilight tracks currently visible on the screen to show the user what he's looking at.
- Add a search box so user can quickly filter the tracks and jump to a place of his interest

However I'd still want to give a mini-map scroll bar a try - I'll make a mockup. It would be very useful even if it was non-interactive and only provided visual feedback. However I don't think allowing the user to click and drag to scroll or jump should be that big of a problem once the basics are there. What do you think?
(0024595)
unfa   
2020-07-03 09:38   
Maybe I'll show you one of the session I'm currently working on:

https://unfa.xyz/random/big_ardour_session.png

This session has all sound effects for a small video game.
Being able to have them all in one session is very convenient and allows me to make corrections quickly.

But the session is large so navigating it becomes clunky. But I believe a few simple tools in Ardour could greatly aid with that, because there's not muhc otehr problems with such large sessions (maybe high RAM and CPU usage even when no sound is being produced).

Open the file, set the scale to 100% and scroll. I've joined screenshots from Ardour to make this.

During the process I had no idea how much work is left, because there is simply no visual indication of what part of my session (vertically) am I currently looking at.
Even something like hilighting currently visible tracks in the Summary panel would help - I'd have at least a very rough indication of where am I.

But what would be excellent IMO would be a 24-pixel wide vertical mini-map showing only headers, track types, states and groups. I can't manually prepare a complete mockup, but I'll draw a basic one to show you what I mean.
(0024596)
unfa   
2020-07-03 10:04   
Here's a mockup of a minimap-scrollbar I have in mind.

As you can see this shows:

Master Bus, Tracks, Buses, VCAs (I forgot to add one), automation lanes - all in scale to the "real world" session size.

Groups with their colors and if they're active or not

Record / Mute / Solo status on each track.

Hilights the currently visible area.

It's a little bit ugly, but I hope you get the idea.

Because everything is a simple square, this should scale up pretty well.

I believe if I had this kind of a navigational aid, I could spend much less time scrollign back and forth never finding what I want.

What do you think?
(0024598)
unfa   
2020-07-03 10:44   
Also: if we could integrate a simple level indicator ( a bar changing color from black to green to clipping red) to each track and bus - that'd be absolutely insane In such big sessions I'm spending a lot of time trying to find which tracks produce sound in any given part of the timeline. I haven't added that in the mockup, but that'd be like extra 2-3 pixels vertically to the right of the Rec / Mute / Solo indicators.

What do you think?
(0024599)
mhartzel   
2020-07-03 10:56   
Just for the record, the MeterBridge is far more handy for hunting down what channels are playing. Just open it with: alt + b and drag it open as it might only show a couple of tracks at first. Then you can just open and close it when needed with alt + b. In the screenshot below only channel 7 is outputting audio in a 50 channel session. Pretty easy to spot it, isn't it.
(0024600)
unfa   
2020-07-03 12:01   
mhartzel:

Thanks! Though without a scroll bar or an option to search tracks y name this really doesn't help if I have a really large session - have you seen the stiched screenshot I linked before?
https://unfa.xyz/random/big_ardour_session.png

Here's how the meterbridge looks here:
(0024601)
unfa   
2020-07-03 12:03   
If the meterbridge allowed to jump the editor to a selected track/bus - it'd be at least somewhat helpful, but it doesn't :D
(0026485)
Alkukoira   
2022-06-19 16:02   
I've been missing this feature as well. What's the status? No dice?

I use the up and down keys to scroll between tracks vertically (sometimes the keys work for this, other times they seem to be "occupied" - still unsure what contributes to the keys' different behaviors). 'Page up' and 'page down' can obviously speed up vertical scrolling as well, yet a more robust way to vertically scroll would be of benefit. If there's still an issue with placing the scroll bar, Unfa's suggestion is still good, and an invisible scroll bar could work, too. "Invisible...": say; clicking and dragging on a track (In EDITOR: under its name) would scroll vertically.
(0026536)
paul   
2022-08-09 19:55   
1. scroll bars require mouse motion to place the pointer in the scroll bar. This is almost always a time-waster and is generally considered non-ergonomic.

2. Do none of you have mice with a scrollwheel?

3. @unfa I do not understand your mockup image at all. Can you explain it?
(0026540)
unfa   
2022-08-09 23:00   
@paul

1. Scroll bars provide a clear immediate visual indication of "you are here" and "this is how much stuff is out there".
With very large Ardour sessions (dozens and dozens of tracks many with half a dozen automation lanes open) I often find myself lost scrolling tracks up and down endlessly, trying to find that one track. Having a scroll bar would give me some more spatial awareness about where am I currently.

2. My issue is not about not being able to scroll up and down, it;s about how hard it is to find yourself. The "scroll bar" could not even be a scroll bar, just a visual indicator of which tracks are currently visible on my screen and how many tracks are above and below what I'm currently looking at.

3. I think my mockup is not that great. Let me use a working example instead. I am attaching a screenshot fro a popular text editor Kate.
   1. This is the editing area - it's what the timeline is in Ardour
   2. This is the "mini map" which also functions as a scroll bar.
   3. This is a highlighted part of the mini-map that represents what portion of the edited document is currently visible on screen.

When you have a huge Ardour project with a hunderd tracks - it's as if you'd be editing a source file so large you cannot remember everything that is in it (say 50 various functions), while having no scroll bar, no mini-map, no line numbers, no method list, no code block folding and no search function. That's how it feels to me when I have 100+ tracks in Ardour in a project I've been working on for months.

In software development one can (and probably should) break a huge source file up into smaller ones, making things easier to manage - in Ardour that's not possible. Surely a tiny part of Ardour's userbase is going to be making projects this big, but even smaller ones would greatly benefit from navigational improvements.

Did I explain the problem better?
(0026541)
paul   
2022-08-09 23:09   
OK, so I understand the issue, but the mini-map idea is dead on arrival, at least for me. In the text editing case, generating this is relatively trivial (its the same contents, with "automatically" scaled down text. There's no trival way of doing this for region/track displays. In addition, the start of tracks (which is all you would likely see (as in Kate, where only the start of lines is visible), unlike some text, will not do much to identify where you are.

You might like the track-color-as-bg-color commit that I just pushed recently., (see 0008022) It doesn't really address things in the way a scroll bar would, but could offer you visual guidance via color.
(0026542)
unfa   
2022-08-09 23:56   
@paul In Kate the mini-map works in 2 dimensions - it shows each line of text with it's start and end. That's not what I'd imagine for this feature, as it would be too complex and also hard to read visually if the minimap represented track clips. What I imagine is having full-width horizontal rectangles representing track/bus/automation lanes. Their color would indicate type (track, bus, automation lane, VCA) or a custom color if provided. So we don't care at all about regions on tracks or data on automation lanes, just tracks and lanes themselves. An important part is showing a rectangle that highlights what is currently seen on screen.
I am not sure if using proportional track height in the mini-map (or scrollbar preview? vertical preview?) would be a good idea - on one end it'd help users visually correlate the timeline and the scrollbar preview, but it could also make things a but more cluttered. It could be helpful though. Otherwise the "visible window" highlight would also need to change size.

One important function would be to scroll the timeline vertically immediately to chosen position after clicking on the scrollbar/minimap - this is how it works in Kate, and I think that's great..

That track-color-as-bg-color seems like a step in the right direction - and having such custom track colors be reflected on the minimap / scrollbar preview would greatly help users orient themselves in a huge session.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8940 [ardour] bugs crash always 2022-07-15 23:30 2022-08-09 20:09
Reporter: rw_bowman Platform: Ubuntu  
Assigned To: paul OS: Linux  
Priority: normal OS Version: (any)  
Status: resolved Product Version: 6.9  
Product Build: Resolution: no change required  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: crash using pipewire jack
Description:  ardour crashes with latest pipewire update, when trying to use jack on ubuntu 22.04
Tags:
Steps To Reproduce: open ardour, choose jack on selection screen. or jack is preselected from previous session. GUI for ardour will load and crash a few seconds in, choosing alsa or pulseaudio seems to work fine. timeshifted back before last pipewire update and works fine. no other installs other than pipewire update., adjusting jack parameters, quantum, etc to no avail.
Additional Information:
System Description
Attached Files: Text File.txt (53,575 bytes) 2022-07-15 23:30
https://tracker.ardour.org/file_download.php?file_id=4199&type=bug
Notes
(0026506)
x42   
2022-07-17 15:33   
The crash happens in `pipewire-0.3/jack/libjack.so.0` -- nothing we can do about here on our side.

Pipewire is still under heavy development. I suggest to use Ardour's ALSA backend, or jackd.
(0026507)
rw_bowman   
2022-07-18 08:42   
Yep, reported issue to the pipewire git, and timeshifted back to working version of pipewire so all good for now.
(0026538)
paul   
2022-08-09 20:09   
pipewire issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8088 [ardour] bugs minor always 2020-05-05 00:19 2022-08-09 20:07
Reporter: serdeman Platform: Intel i3 laptop  
Assigned To: paul OS: Linux  
Priority: normal OS Version: Mint 19 Cinnamon  
Status: resolved Product Version: 6.0-pre1  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ardour 6rc1.176 - Exporting does not work correctly
Description: When exporting a mixdown to an audio file, I notice that trying to export a WAV 44.1, 32but (non-float) file does not work correctly. When creating a new export profile, hitting SAVE populates the log with this kind of line:

2020-04-28T23:27:30 [ERROR]: XML error: failed to load external entity "/home/steve/.config/ardour6/export/BWAV 32float Export (copy).format"

Continuing on with setting up the export settings, the popup box does some weird things in the section regarding dither type. (ref. the two screen captures please). After first selected 32bit, all the dither types seem to be available (in white text). But if you click to 16bit, then back to 32bit, all the dither types, except NONE, turn RED.

The resulting export more often than not turns out to be 32bit float. I have not figured out how to, with confidence, make a non-float 32bit file.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files: Ardour 6rc1.176 gdb output (77,397 bytes) 2020-05-05 00:19
https://tracker.ardour.org/file_download.php?file_id=3660&type=bug
Export_Box_After.png (147,446 bytes) 2020-05-05 00:19
https://tracker.ardour.org/file_download.php?file_id=3661&type=bug
Export_Box_Before.png (145,642 bytes) 2020-05-05 00:19
https://tracker.ardour.org/file_download.php?file_id=3662&type=bug
Notes
(0024068)
serdeman   
2020-05-05 00:24   
I forgot to mention, during the export, most of the time I end up with two files. One, with all the naming conventions I chose, and an identical file, with a generic name and the tag I placed for the export settings. For example, "session_WAV_441_32bit".
(0026537)
paul   
2022-08-09 20:07   
6.0 is more than 2 years and 8 versions old at this point. Not believed to be an issue in the most recent 6.x release nor in 7.0


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8943 [ardour] bugs major always 2022-07-21 06:31 2022-08-09 19:50
Reporter: johne53 Platform: Microsoft  
Assigned To: paul OS: Windows  
Priority: urgent OS Version: 10  
Status: resolved Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Strange pointer usage in 'libs'ardour'triggerbox.cc'
Description: I'm repeatedly seeing crashes here when using the Cue Marker lane (in the Edit window). These translate to assertions if I make a Debug build here (with MSVC). I haven't tracked down all the problems but at least part of it is coming from code like this inside 'TriggerBox::fast_forward ()' :-

    CueEvents::const_iterator nxt_cue = c; ++nxt_cue;

    // Then statements like this (further down)
    c = nxt_cue;
    pos = c->time;

As you can see, there's no check to validate the 'c' object. It can easily be pointing to cues.end()
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0026518)
johne53   
2022-07-21 06:40   
Sorry - one other thing... it's likely just something I'm not understanding but what's the significance of tests like this

    if (c->cue == INT32_MAX)

AFAICT we never set it to INT32_MAX so what would cause it to be set like that?
(0026535)
paul   
2022-08-09 19:50   
INT32_MAX == CueRecord::stop_all

code has been changed.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8827 [ardour] bugs minor always 2021-11-26 07:59 2022-08-09 19:50
Reporter: bobbus Platform: Redhat  
Assigned To: paul OS: Linux  
Priority: normal OS Version: (any)  
Status: feedback Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ardour 6.6.9 crashes on Fedora 35
Description: Description of problem:
Ardour6.6.9 is broken in Fedora 35. I upgraded from 34 and Ardour is no longer working properly.
Installed a clean Fedora Jam 35 in a VM to replicate the issue, and it's exactly the same.

I'm very aware this might be a Fedora packaging issue, but since Fedora 35 pulled in a lot of the most recent libraries, this might be related.

Actions taken:
Started ardour6 from CLI
Opened existing project or started new project
Do anything in the GUI, like starting a playback, clicking in the timeline, ...
Ardour freezes.

When starting a project or opening an existing project, a ton of error messages are dropped on the CLI (see attached).


Version-Release number of selected component (if applicable):
6.6.9

How reproducible:
Always
Tags:
Steps To Reproduce: Steps to Reproduce:
1.Start Ardour6 on Fedora 35
2.open new or existing project
3.check STDOUT output

Actual results:
Ardour hangs
Additional Information:
System Description
Attached Files: ardour-error-log.txt (21,218 bytes) 2021-11-26 07:59
https://tracker.ardour.org/file_download.php?file_id=4141&type=bug
Notes
(0026247)
bobbus   
2021-11-26 08:13   
removed lv2-klaviatur, klaviatur_gtk and lv2-newtonator and functionally Ardour is now OK.
All the funky lilv_plugin errors in the output remain however!
For completeness: Jack backend emulated by pipewire.
(0026248)
bobbus   
2021-11-26 09:10   
ignore previous comment - Ardour not working despite the removal of broken plugins.
(0026250)
x42   
2021-11-26 14:26   
Does it work if you don't use pipewire? Can you test with Ardour's ALSA backend (no JACK, no PW)?
(0026251)
rohanlean   
2021-11-28 09:43   
Not exactly the answer to Robin's question, but the flatpak from flathub works with pipewire via JACK on Fedora 35 without freezing in the way described.
(0026252)
bobbus   
2021-11-28 12:45   
Switched to jack without PW, but that gave issues starting jack (resources likely claimed by PW).
So I switched to ALSA backend for Ardour6. Doesn't freeze as before, but playback is not consistent and then hangs.

Not the same behavior as with pipewire-jack but also problematic and unusable.
Tried the Fedora 35 live CD and starting Ardour6 from CLI throws the same errors as on my pc.

Flatpaks... I rather don't.
(0026534)
paul   
2022-08-09 19:50   
is this still happening? It is almost certainly a pipewire issue. Will mark resolved in 1 week if no response.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8945 [ardour] bugs crash always 2022-07-23 23:20 2022-08-09 19:17
Reporter: levalithan Platform: Arch  
Assigned To: paul OS: Linux  
Priority: high OS Version: (any)  
Status: resolved Product Version: 6.9  
Product Build: Resolution: unable to reproduce  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Immediate crashing when trying to export
Description: Title. I've finished a track, i go to export and, no matter where i export it, how i export it, or in what format i export it, it doesn't work and will crash immediately with no dialogues or anything. Just an immediate close
Tags:
Steps To Reproduce: Open ardour project, try to export audio
Additional Information: i've attached a file with logs that the "debugging ardour" asked me to grab, if that helps
System Description
Attached Files: ardourcrashlog.txt (65,041 bytes) 2022-07-23 23:20
https://tracker.ardour.org/file_download.php?file_id=4203&type=bug
Notes
(0026520)
levalithan   
2022-07-23 23:27   
nevermind, did it first thing after a reboot with no other programs open, and it worked, i think something with discord and ardour broke as discord didn't have any audio after the initial crash
(0026533)
paul   
2022-08-09 19:17   
Not actionable as-is.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8900 [ardour] bugs minor always 2022-04-14 11:26 2022-08-09 19:14
Reporter: johne53 Platform: Microsoft  
Assigned To: OS: Windows  
Priority: normal OS Version: 10  
Status: new Product Version: Mixbus 8.x  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Crashing bug with RubberBandStretcher
Description: I've been following up a bug report on the MB forum. It's a very reproducible crash on Windows (both for my MSVC build and also Robin's gcc build) but I haven't had a chance yet to try it with Ardour. Also, it probably needs testing with the other platforms.
Tags:
Steps To Reproduce: 1) In the Cues page, select any clip and enable its 'Stretch' mode.
2) Press its "/2" button more than twice.
3) Attempting to replay the clip now causes Mixbus to crash.
Additional Information: I tracked the crash down to some code in librubberband. Intentionally or otherwise, it seems like RubberBandStretcher must have a limit on how much a clip can be speeded up. Double speed works okay and x4 works okay but x8 will crash MB in about 80% of cases.
System Description
Attached Files:
Notes
(0026426)
johne53   
2022-05-02 06:57   
Steps to reproduce:
1) In the Cues page, select any clip and enable its 'Stretch' mode.
2) Press its "/2" button more than twice.
3) Attempting to replay the clip now causes Mixbus to crash.

Additional Information:
it seems like RubberBandStretcher must have a limit on how much a clip can be speeded up.

If this can't be fixed, maybe there could be an upper limit on the maximum speed? (i.e. an upper limit on the number of '/2' presses...)
(0026437)
johne53   
2022-05-07 11:37   
FWIW I can reproduce the same crash in Linux but with a couple of minor differences... on Linux, the speeded-up clip will attempt to play for a second or so (apparently at the last known working speed) and then I see the same crash. And so far in Linux, the crash rate is 100%.
(0026486)
johne53   
2022-06-20 09:56   
Does anyone know this got fixed? I haven't tried Linux yet but I can't reproduce it in Mixbus Windows any more...
(0026487)
lerni   
2022-06-21 05:58   
Dunno but just happen to stumble over https://github.com/Ardour/ardour/commit/fcbe6aab494bf4e13b9ad3d4d5e0ff60ce65626c recently and it sounds related enough.
(0026488)
johne53   
2022-06-21 11:01   
Something's definitely improved this because it used to crash with any clip - but now, I can only find one clip that crashes, namely:-

Under Goldbaby Audio Loops->Loops->PercAndDrums

and it's the clip called "HandsAndFeet1.flac"
(0026532)
paul   
2022-08-09 19:14   
This no longer seems to be reproduceable (here, at least).


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8946 [ardour] bugs minor always 2022-07-24 19:31 2022-08-09 19:11
Reporter: oml65 Platform: Arch  
Assigned To: paul OS: Linux  
Priority: normal OS Version: (any)  
Status: resolved Product Version: 6.9  
Product Build: Resolution: no change required  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ardour 6.9.0 hangs when closing with JACK setup (not with RtAudio setup or jackd not started)
Description: When closing ardour6 it hangs when is setup with JACK.

Ardour 6.9.0
"After Bach"
(rev 6.9)
Intel 64-bit
Tags: closing, hangs, jack
Steps To Reproduce: Open gnome-terminal and run ardour6.
Close ardour.
Hangs and does not return to login prompt. I need to press CTRL+C.
Additional Information: Config:

Build documentation: False
Debuggable build: False
Export all symbols (backtrace): False
Install prefix: /usr
Strict compiler flags: []
Internal Shared Libraries: True
Use External Libraries: True
Library exports hidden: True
Free/Demo copy: False

ALSA DBus Reservation: True
Architecture flags: None
ARM NEON support: False
Aubio: True
AudioUnits: False
Build target: x86_64
Canvas Test UI: False
Beatbox test app: False
CoreAudio: False
CoreAudio 10.5 compat: False
Debug RT allocations: False
Debug Symbols: False
Denormal exceptions: False
Dr. Mingw: False
FLAC: True
FPU optimization: True
FPU AVX/FMA support: True
Freedesktop files: True
Libjack linking: link
Libjack metadata: True
Lua Binding Doc: False
Lua Commandline Tool: True
LV2 UI embedding: True
LV2 support: True
LV2 extensions: True
LXVST support: True
Mac VST support: False
NI-Maschine: False
OGG: True
Phone home: False
Process thread timing: False
Program name: Ardour
Samplerate: True
PT format: True
PTW32 Semaphore: False
Threaded WaveViews: True
Translation: True
Unit tests: False
Use LLD linker: False
VST3 support: True
Windows VST support: False
Wiimote support: False
Windows key: Mod4><Super

PortAudio Backend: False
CoreAudio/Midi Backend: False
ALSA Backend: True
Dummy backend: True
JACK Backend: True
Pulseaudio Backend: True

Buildstack: -system-
Mac i386 Architecture: False
Mac ppc Architecture: False
Mac arm64 Architecture: False

C compiler flags: ['-I/build/ardour/src/ardour', '-march=x86-64', '-mtune=generic', '-O2', '-pipe', '-fno-plt', '-fexceptions', '-Wp,-D_FORTIFY_SOURCE=2', '-Wformat', '-Werror=format-security', '-fstack-clash-protection', '-fcf-protection', '-g', '-fvar-tracking-assignments', '-fdebug-prefix-map=/build/ardour/src=/usr/src/debug', '-flto', '-DHAVE_RF64_RIFF', '-DWAF_BUILD', '-DNDEBUG', '-fshow-column', '-O3', '-fomit-frame-pointer', '-ffast-math', '-fstrength-reduce', '-pipe', '-DARCH_X86', '-mmmx', '-msse', '-mfpmath=sse', '-DUSE_XMMINTRIN', '-DBUILD_SSE_OPTIMIZATIONS', '-DLXVST_64BIT', '-Wall', '-Wpointer-arith', '-Wcast-qual', '-Wcast-align', '-Wno-unused-parameter', '-DBOOST_SYSTEM_NO_DEPRECATED', '-D_ISOC9X_SOURCE', '-D_LARGEFILE64_SOURCE', '-D_FILE_OFFSET_BITS=64', '-DPROGRAM_NAME="Ardour"', '-DPROGRAM_VERSION="6"', '-Wstrict-prototypes', '-Wmissing-prototypes']
C++ compiler flags: ['-I/build/ardour/src/ardour', '-march=x86-64', '-mtune=generic', '-O2', '-pipe', '-fno-plt', '-fexceptions', '-Wp,-D_FORTIFY_SOURCE=2', '-Wformat', '-Werror=format-security', '-fstack-clash-protection', '-fcf-protection', '-Wp,-D_GLIBCXX_ASSERTIONS', '-g', '-fvar-tracking-assignments', '-fdebug-prefix-map=/build/ardour/src=/usr/src/debug', '-flto', '-DHAVE_RF64_RIFF', '-DWAF_BUILD', '-DNDEBUG', '-fshow-column', '-O3', '-fomit-frame-pointer', '-ffast-math', '-fstrength-reduce', '-pipe', '-DARCH_X86', '-mmmx', '-msse', '-mfpmath=sse', '-DUSE_XMMINTRIN', '-DBUILD_SSE_OPTIMIZATIONS', '-DLXVST_64BIT', '-Wall', '-Wpointer-arith', '-Wcast-qual', '-Wcast-align', '-Wno-unused-parameter', '-DBOOST_SYSTEM_NO_DEPRECATED', '-D_ISOC9X_SOURCE', '-D_LARGEFILE64_SOURCE', '-D_FILE_OFFSET_BITS=64', '-DPROGRAM_NAME="Ardour"', '-DPROGRAM_VERSION="6"', '-std=c++11', '-DBOOST_NO_AUTO_PTR', '-DBOOST_BIND_GLOBAL_PLACEHOLDERS', '-Woverloaded-virtual', '-Wno-unused-local-typedefs', '-D__STDC_LIMIT_MACROS', '-D__STDC_FORMAT_MACROS', '-DCANVAS_COMPATIBILITY', '-DCANVAS_DEBUG', '-DBOOST_ERROR_CODE_HEADER_ONLY']
Linker flags: ['-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now', '-flto']

$ LC_ALL=C ardour6 --gdb
GNU gdb (GDB) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/ardour6/ardour-6.9.0...
(No debugging symbols found in /usr/lib/ardour6/ardour-6.9.0)
(gdb) run
Starting program: /usr/lib/ardour6/ardour-6.9.0
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Ardour6.9.0 (built using 6.9 and GCC version 11.2.0)
Ardour: [INFO]: Your system is configured to limit Ardour to 524288 open files
Ardour: [INFO]: Loading system configuration file /etc/ardour6/system_config
Ardour: [INFO]: Loading user configuration file /home/user/.config/ardour6/config
[New Thread 0x7ffff0de6640 (LWP 9742)]
Ardour: [INFO]: CPU vendor: AuthenticAMD
Ardour: [INFO]: AVX-capable processor
Ardour: [INFO]: AVX with FMA capable processor
Ardour: [INFO]: CPU brand: AMD Ryzen 9 5900X 12-Core Processor
Ardour: [INFO]: Using AVX and FMA optimized routines
[New Thread 0x7fffebfff640 (LWP 9743)]
[New Thread 0x7fffe3fff640 (LWP 9744)]
[New Thread 0x7fffeb7fe640 (LWP 9745)]
Ardour: [INFO]: Loading plugin meta data file /usr/share/ardour6/plugin_metadata/plugin_tags
Ardour: [INFO]: Loading plugin statistics file /home/user/.config/ardour6/plugin_metadata/plugin_stats
[New Thread 0x7fffeaffd640 (LWP 9746)]
[Thread 0x7fffeaffd640 (LWP 9746) exited]
[New Thread 0x7fffeaffd640 (LWP 9747)]
[New Thread 0x7fffea572640 (LWP 9748)]
[New Thread 0x7fffe9c48640 (LWP 9749)]
Ardour: [INFO]: Loading default ui configuration file /etc/ardour6/default_ui_config
Ardour: [INFO]: Loading user ui configuration file /home/user/.config/ardour6/ui_config
Ardour: [INFO]: Loading 452 MIDI patches from /usr/share/ardour6/patchfiles
[New Thread 0x7fffe93ce640 (LWP 9750)]
[Thread 0x7fffe93ce640 (LWP 9750) exited]
[New Thread 0x7fffe93ce640 (LWP 9751)]
[New Thread 0x7fffe8bcd640 (LWP 9752)]
[Thread 0x7fffe93ce640 (LWP 9751) exited]
[New Thread 0x7fffe93ce640 (LWP 9753)]
[New Thread 0x7fffe37fe640 (LWP 9754)]
[Thread 0x7fffe8bcd640 (LWP 9752) exited]
[Thread 0x7fffe93ce640 (LWP 9753) exited]
[Thread 0x7fffe37fe640 (LWP 9754) exited]
[New Thread 0x7fffe37fe640 (LWP 9755)]
[New Thread 0x7fffe93ce640 (LWP 9756)]
[Thread 0x7fffe37fe640 (LWP 9755) exited]
[Thread 0x7fffe93ce640 (LWP 9756) exited]
Ardour: [INFO]: Loading color file /usr/share/ardour6/themes/dark-ardour.colors
Ardour: [INFO]: Loading ui configuration file /etc/ardour6/clearlooks.rc
[New Thread 0x7fffe93ce640 (LWP 9757)]
[New Thread 0x7fffe37fe640 (LWP 9758)]
[Thread 0x7fffe93ce640 (LWP 9757) exited]
[New Thread 0x7fffe93ce640 (LWP 9759)]
[New Thread 0x7fffe8bcd640 (LWP 9760)]
[Thread 0x7fffe37fe640 (LWP 9758) exited]
[Thread 0x7fffe93ce640 (LWP 9759) exited]
[New Thread 0x7fffe93ce640 (LWP 9761)]
[New Thread 0x7fffe37fe640 (LWP 9762)]
[Thread 0x7fffe8bcd640 (LWP 9760) exited]
[Thread 0x7fffe93ce640 (LWP 9761) exited]
[New Thread 0x7fffe93ce640 (LWP 9763)]
[New Thread 0x7fffe8bcd640 (LWP 9764)]
[Thread 0x7fffe37fe640 (LWP 9762) exited]
[Thread 0x7fffe93ce640 (LWP 9763) exited]
[Thread 0x7fffe8bcd640 (LWP 9764) exited]
Ardour: [INFO]: Loading bindings from /etc/ardour6/ardour.keys
Loading ui configuration file /etc/ardour6/clearlooks.rc
[New Thread 0x7fffe8bcd640 (LWP 9765)]
[New Thread 0x7fffe93ce640 (LWP 9766)]
[Thread 0x7fffe8bcd640 (LWP 9765) exited]
[New Thread 0x7fffe8bcd640 (LWP 9767)]
[New Thread 0x7fffe37fe640 (LWP 9768)]
[Thread 0x7fffe8bcd640 (LWP 9767) exited]
[Thread 0x7fffe93ce640 (LWP 9766) exited]
[Thread 0x7fffe37fe640 (LWP 9768) exited]
[New Thread 0x7fffe37fe640 (LWP 9769)]
[New Thread 0x7fffe93ce640 (LWP 9770)]
[Thread 0x7fffe37fe640 (LWP 9769) exited]
[Thread 0x7fffe93ce640 (LWP 9770) exited]
[New Thread 0x7fffe8238640 (LWP 9771)]
[New Thread 0x7fffe2ffd640 (LWP 9772)]
[Thread 0x7fffe2ffd640 (LWP 9772) exited]
[Thread 0x7fffe8238640 (LWP 9771) exited]
[New Thread 0x7fffe8238640 (LWP 9773)]
[New Thread 0x7fffe2ffd640 (LWP 9774)]
[Thread 0x7fffe2ffd640 (LWP 9774) exited]
[Thread 0x7fffe8238640 (LWP 9773) exited]
[New Thread 0x7fffe93ce640 (LWP 9775)]
[New Thread 0x7fffe37fe640 (LWP 9776)]
[Thread 0x7fffe93ce640 (LWP 9775) exited]
[New Thread 0x7fffe93ce640 (LWP 9777)]
[New Thread 0x7fffe8bcd640 (LWP 9778)]
[Thread 0x7fffe37fe640 (LWP 9776) exited]
[Thread 0x7fffe93ce640 (LWP 9777) exited]
[Thread 0x7fffe8bcd640 (LWP 9778) exited]
[New Thread 0x7fffe8bcd640 (LWP 9779)]
[New Thread 0x7fffe93ce640 (LWP 9780)]
[Thread 0x7fffe8bcd640 (LWP 9779) exited]
[New Thread 0x7fffe8bcd640 (LWP 9781)]
[Thread 0x7fffe93ce640 (LWP 9780) exited]
[New Thread 0x7fffe93ce640 (LWP 9782)]
[Thread 0x7fffe8bcd640 (LWP 9781) exited]
[Thread 0x7fffe93ce640 (LWP 9782) exited]
[New Thread 0x7fffe93ce640 (LWP 9783)]
[New Thread 0x7fffe8bcd640 (LWP 9784)]
[New Thread 0x7fffe37fe640 (LWP 9785)]
[New Thread 0x7fffe2eda640 (LWP 9786)]
[New Thread 0x7fffe26d9640 (LWP 9787)]
[New Thread 0x7fffe1ed8640 (LWP 9788)]
[New Thread 0x7fffe16d7640 (LWP 9789)]
[New Thread 0x7fffe0ed6640 (LWP 9790)]
[New Thread 0x7fffabfff640 (LWP 9791)]
[New Thread 0x7fffab7fe640 (LWP 9792)]
Found nothing along /home/user/.config/ardour6/templates:/usr/share/ardour6/templates
[New Thread 0x7fffaaffd640 (LWP 9793)]
[New Thread 0x7fffaa7fc640 (LWP 9794)]
[Thread 0x7fffaaffd640 (LWP 9793) exited]
[Thread 0x7fffaa7fc640 (LWP 9794) exited]
[New Thread 0x7fffaa7fc640 (LWP 9795)]
[New Thread 0x7fffaaffd640 (LWP 9796)]
[Thread 0x7fffaa7fc640 (LWP 9795) exited]
[Thread 0x7fffaaffd640 (LWP 9796) exited]
[New Thread 0x7fffaaffd640 (LWP 9797)]
[Thread 0x7fffe9c48640 (LWP 9749) exited]
[Thread 0x7fffe0ed6640 (LWP 9790) exited]
[Thread 0x7fffe1ed8640 (LWP 9788) exited]
[Thread 0x7fffe26d9640 (LWP 9787) exited]
[Thread 0x7fffabfff640 (LWP 9791) exited]
[Thread 0x7fffe37fe640 (LWP 9785) exited]
[Thread 0x7fffab7fe640 (LWP 9792) exited]
[Thread 0x7fffe16d7640 (LWP 9789) exited]
[New Thread 0x7fffe16d7640 (LWP 9798)]
[New Thread 0x7fffe8238640 (LWP 9799)]
[New Thread 0x7fffe2573640 (LWP 9800)]
[New Thread 0x7fffe2235640 (LWP 9801)]
[Thread 0x7fffe2eda640 (LWP 9786) exited]
Scanning folders for bundled LV2s: /usr/lib/ardour6/LV2
[New Thread 0x7fffe2eda640 (LWP 9802)]
[New Thread 0x7fffab7fe640 (LWP 9803)]
[New Thread 0x7fffe37fe640 (LWP 9804)]
[New Thread 0x7fffabfff640 (LWP 9805)]
[New Thread 0x7fffe0ed6640 (LWP 9806)]
[New Thread 0x7fffaa7fc640 (LWP 9807)]
[New Thread 0x7fffa9ffb640 (LWP 9808)]
[New Thread 0x7fffa97fa640 (LWP 9809)]
[New Thread 0x7fffa8ff9640 (LWP 9810)]
[New Thread 0x7fff819a0640 (LWP 9811)]
[New Thread 0x7fff8119f640 (LWP 9812)]
[Thread 0x7fff819a0640 (LWP 9811) exited]
[Thread 0x7fff8119f640 (LWP 9812) exited]
Set cursor set to default
[New Thread 0x7fff8119f640 (LWP 9813)]
[New Thread 0x7fff819a0640 (LWP 9814)]
[Thread 0x7fff8119f640 (LWP 9813) exited]
[New Thread 0x7fff8119f640 (LWP 9815)]
[New Thread 0x7fff8099e640 (LWP 9816)]
[Thread 0x7fff819a0640 (LWP 9814) exited]
[Thread 0x7fff8119f640 (LWP 9815) exited]
[Thread 0x7fff8099e640 (LWP 9816) exited]
[New Thread 0x7fff8099e640 (LWP 9817)]
[New Thread 0x7fff8119f640 (LWP 9818)]
[Thread 0x7fff8099e640 (LWP 9817) exited]
[Thread 0x7fff8119f640 (LWP 9818) exited]
[New Thread 0x7fff8119f640 (LWP 9819)]
[New Thread 0x7fff8099e640 (LWP 9820)]
[Thread 0x7fff8119f640 (LWP 9819) exited]
[New Thread 0x7fff8119f640 (LWP 9821)]
[New Thread 0x7fff819a0640 (LWP 9822)]
[Thread 0x7fff8119f640 (LWP 9821) exited]
[Thread 0x7fff8099e640 (LWP 9820) exited]
[Thread 0x7fff819a0640 (LWP 9822) exited]
[New Thread 0x7fff819a0640 (LWP 9823)]
[New Thread 0x7fff8099e640 (LWP 9824)]
[Thread 0x7fff819a0640 (LWP 9823) exited]
[New Thread 0x7fff819a0640 (LWP 9825)]
[New Thread 0x7fff8119f640 (LWP 9826)]
[Thread 0x7fff8099e640 (LWP 9824) exited]
[Thread 0x7fff819a0640 (LWP 9825) exited]
[Thread 0x7fff8119f640 (LWP 9826) exited]
[New Thread 0x7fff8119f640 (LWP 9827)]
[New Thread 0x7fff819a0640 (LWP 9828)]
[Thread 0x7fff8119f640 (LWP 9827) exited]
[Thread 0x7fff819a0640 (LWP 9828) exited]
[New Thread 0x7fff819a0640 (LWP 9829)]
[New Thread 0x7fff8119f640 (LWP 9830)]
[Thread 0x7fff819a0640 (LWP 9829) exited]
[Thread 0x7fff8119f640 (LWP 9830) exited]
[New Thread 0x7fffe179fa00 (LWP 9831)]
[New Thread 0x7fffe1793a00 (LWP 9832)]
[New Thread 0x7fffe1787a00 (LWP 9833)]
[New Thread 0x7fffe177ba00 (LWP 9834)]
[New Thread 0x7fffe176fa00 (LWP 9835)]
[New Thread 0x7fffe1763a00 (LWP 9836)]
[New Thread 0x7fffe1757a00 (LWP 9837)]
[New Thread 0x7fffe174ba00 (LWP 9838)]
[New Thread 0x7fffe173fa00 (LWP 9839)]
[New Thread 0x7fffe1733a00 (LWP 9840)]
[New Thread 0x7fffe1727a00 (LWP 9841)]
[New Thread 0x7fffe171ba00 (LWP 9842)]
[New Thread 0x7fffe170fa00 (LWP 9843)]
[New Thread 0x7fffe1703a00 (LWP 9844)]
[New Thread 0x7fffe16f7a00 (LWP 9845)]
[New Thread 0x7fffe16eba00 (LWP 9846)]
[New Thread 0x7fffe066aa00 (LWP 9847)]
[New Thread 0x7fffe065ea00 (LWP 9848)]
[New Thread 0x7fffe0652a00 (LWP 9849)]
[New Thread 0x7fffe0646a00 (LWP 9850)]
[New Thread 0x7fffe063aa00 (LWP 9851)]
[New Thread 0x7fffe062ea00 (LWP 9852)]
[New Thread 0x7fffe0622a00 (LWP 9853)]
[New Thread 0x7fffe0617640 (LWP 9854)]
[New Thread 0x7fffe0596640 (LWP 9855)]
[New Thread 0x7fffe0515640 (LWP 9856)]
[New Thread 0x7fffe0494640 (LWP 9857)]
[New Thread 0x7fffe0413640 (LWP 9858)]
[New Thread 0x7fffe0392640 (LWP 9859)]
[New Thread 0x7fffe0311640 (LWP 9860)]
[New Thread 0x7fffe0290640 (LWP 9861)]
[New Thread 0x7fffe020f640 (LWP 9862)]
[New Thread 0x7fffe018e640 (LWP 9863)]
[New Thread 0x7fffe010d640 (LWP 9864)]
[New Thread 0x7fffe008c640 (LWP 9865)]
[New Thread 0x7fffa87f8640 (LWP 9866)]
[New Thread 0x7fffa8777640 (LWP 9867)]
[New Thread 0x7fffa86f6640 (LWP 9868)]
[New Thread 0x7fffa8675640 (LWP 9869)]
[New Thread 0x7fffa85f4640 (LWP 9870)]
[New Thread 0x7fffa8573640 (LWP 9871)]
[New Thread 0x7fffa84f2640 (LWP 9872)]
[New Thread 0x7fffa8471640 (LWP 9873)]
[New Thread 0x7fffa83f0640 (LWP 9874)]
[New Thread 0x7fffa836f640 (LWP 9875)]
[New Thread 0x7fffa82ee640 (LWP 9876)]
[New Thread 0x7fff8119f640 (LWP 9877)]
[New Thread 0x7fff819a0640 (LWP 9878)]
[Thread 0x7fff8119f640 (LWP 9877) exited]
[New Thread 0x7fff8119f640 (LWP 9879)]
[New Thread 0x7fff8099e640 (LWP 9880)]
[Thread 0x7fff8119f640 (LWP 9879) exited]
[Thread 0x7fff819a0640 (LWP 9878) exited]
[Thread 0x7fff8099e640 (LWP 9880) exited]
[New Thread 0x7fff8099e640 (LWP 9881)]
[New Thread 0x7fff819a0640 (LWP 9882)]
[Thread 0x7fff8099e640 (LWP 9881) exited]
[Thread 0x7fff819a0640 (LWP 9882) exited]
[New Thread 0x7fff819a0640 (LWP 9883)]
[New Thread 0x7fff8099e640 (LWP 9884)]
[Thread 0x7fff819a0640 (LWP 9883) exited]
[Thread 0x7fff8099e640 (LWP 9884) exited]
[New Thread 0x7fffa80df640 (LWP 9885)]
[New Thread 0x7fff8099e640 (LWP 9886)]
[Thread 0x7fffa8ff9640 (LWP 9810) exited]
[Thread 0x7fffe0ed6640 (LWP 9806) exited]
[Thread 0x7fffa9ffb640 (LWP 9808) exited]
[Thread 0x7fffe2eda640 (LWP 9802) exited]
[Thread 0x7fffe37fe640 (LWP 9804) exited]
[Thread 0x7fffaa7fc640 (LWP 9807) exited]
[Thread 0x7fffabfff640 (LWP 9805) exited]
[Thread 0x7fffab7fe640 (LWP 9803) exited]
[Thread 0x7fffe16d7640 (LWP 9798) exited]
[New Thread 0x7fffe16d7640 (LWP 9887)]
[New Thread 0x7fffab7fe640 (LWP 9888)]
[New Thread 0x7fffabfff640 (LWP 9889)]
[New Thread 0x7fffaa7fc640 (LWP 9890)]
[New Thread 0x7fffe2eda640 (LWP 9891)]
[Thread 0x7fffaa7fc640 (LWP 9890) exited]
[Thread 0x7fffe2eda640 (LWP 9891) exited]
[New Thread 0x7fffe2eda640 (LWP 9892)]
[New Thread 0x7fffaa7fc640 (LWP 9893)]
[Thread 0x7fffe2eda640 (LWP 9892) exited]
[Thread 0x7fffaa7fc640 (LWP 9893) exited]
[New Thread 0x7fffaa7fc640 (LWP 9894)]
[New Thread 0x7fffe2eda640 (LWP 9895)]
[Thread 0x7fffaa7fc640 (LWP 9894) exited]
[Thread 0x7fffe2eda640 (LWP 9895) exited]
[New Thread 0x7fffe2eda640 (LWP 9896)]
[New Thread 0x7fffaa7fc640 (LWP 9897)]
[Thread 0x7fffe2eda640 (LWP 9896) exited]
[New Thread 0x7fffe2eda640 (LWP 9898)]
[New Thread 0x7fffe0ed6640 (LWP 9899)]
[Thread 0x7fffe2eda640 (LWP 9898) exited]
[Thread 0x7fffaa7fc640 (LWP 9897) exited]
[Thread 0x7fffe0ed6640 (LWP 9899) exited]
[New Thread 0x7fffe0ed6640 (LWP 9900)]
[New Thread 0x7fffaa7fc640 (LWP 9901)]
[Thread 0x7fffe0ed6640 (LWP 9900) exited]
[Thread 0x7fffaa7fc640 (LWP 9901) exited]
[New Thread 0x7fffaa7fc640 (LWP 9902)]
[New Thread 0x7fffe0ed6640 (LWP 9903)]
[Thread 0x7fffaa7fc640 (LWP 9902) exited]
[New Thread 0x7fffaa7fc640 (LWP 9904)]
[New Thread 0x7fffe2eda640 (LWP 9905)]
[Thread 0x7fffe0ed6640 (LWP 9903) exited]
[Thread 0x7fffaa7fc640 (LWP 9904) exited]
[Thread 0x7fffe2eda640 (LWP 9905) exited]
[New Thread 0x7fffe2eda640 (LWP 9906)]
[New Thread 0x7fffaa7fc640 (LWP 9907)]
[New Thread 0x7fffe0ed6640 (LWP 9908)]
[New Thread 0x7fffa8ff9640 (LWP 9909)]
[New Thread 0x7fff819a0640 (LWP 9910)]
[New Thread 0x7fff8119f640 (LWP 9911)]
[New Thread 0x7ffeb27fc640 (LWP 9912)]
[New Thread 0x7ffeb1ffb640 (LWP 9913)]
[Thread 0x7fffab7fe640 (LWP 9888) exited]
Butler drops pool trash
[Thread 0x7fffa80df640 (LWP 9885) exited]
[Thread 0x7ffeb1ffb640 (LWP 9913) exited]
[Thread 0x7ffeb27fc640 (LWP 9912) exited]
[Thread 0x7fff8119f640 (LWP 9911) exited]
[Thread 0x7fff819a0640 (LWP 9910) exited]
[Thread 0x7fffa8ff9640 (LWP 9909) exited]
[Thread 0x7fffe0ed6640 (LWP 9908) exited]
[Thread 0x7fffaa7fc640 (LWP 9907) exited]
[Thread 0x7fffe2eda640 (LWP 9906) exited]
[Thread 0x7fffa82ee640 (LWP 9876) exited]
[Thread 0x7fffa836f640 (LWP 9875) exited]
[Thread 0x7fffa83f0640 (LWP 9874) exited]
[Thread 0x7fffa8471640 (LWP 9873) exited]
[Thread 0x7fffa84f2640 (LWP 9872) exited]
[Thread 0x7fffa8573640 (LWP 9871) exited]
[Thread 0x7fffa85f4640 (LWP 9870) exited]
[Thread 0x7fffa8675640 (LWP 9869) exited]
[Thread 0x7fffa86f6640 (LWP 9868) exited]
[Thread 0x7fffa8777640 (LWP 9867) exited]
[Thread 0x7fffa87f8640 (LWP 9866) exited]
[Thread 0x7fffe008c640 (LWP 9865) exited]
[Thread 0x7fffe010d640 (LWP 9864) exited]
[Thread 0x7fffe018e640 (LWP 9863) exited]
[Thread 0x7fffe020f640 (LWP 9862) exited]
[Thread 0x7fffe0290640 (LWP 9861) exited]
[Thread 0x7fffe0311640 (LWP 9860) exited]
[Thread 0x7fffe0392640 (LWP 9859) exited]
[Thread 0x7fffe0413640 (LWP 9858) exited]
[Thread 0x7fffe0494640 (LWP 9857) exited]
[Thread 0x7fffe0515640 (LWP 9856) exited]
[Thread 0x7fffe0596640 (LWP 9855) exited]
[Thread 0x7fffe0617640 (LWP 9854) exited]
[Thread 0x7fffabfff640 (LWP 9889) exited]
[Thread 0x7fffe16d7640 (LWP 9887) exited]
[Thread 0x7fff8099e640 (LWP 9886) exited]
[Thread 0x7fffe170fa00 (LWP 9843) exited]
[Thread 0x7fffe16f7a00 (LWP 9845) exited]
[Thread 0x7fffe0622a00 (LWP 9853) exited]
[Thread 0x7fffe062ea00 (LWP 9852) exited]
[Thread 0x7fffe063aa00 (LWP 9851) exited]
[Thread 0x7fffe0646a00 (LWP 9850) exited]
[Thread 0x7fffe0652a00 (LWP 9849) exited]
[Thread 0x7fffe065ea00 (LWP 9848) exited]
[Thread 0x7fffe066aa00 (LWP 9847) exited]
[Thread 0x7fffe16eba00 (LWP 9846) exited]
[Thread 0x7fffe1703a00 (LWP 9844) exited]
[Thread 0x7fffe171ba00 (LWP 9842) exited]
[Thread 0x7fffe1727a00 (LWP 9841) exited]
[Thread 0x7fffe1733a00 (LWP 9840) exited]
[Thread 0x7fffe173fa00 (LWP 9839) exited]
[Thread 0x7fffe174ba00 (LWP 9838) exited]
[Thread 0x7fffe1757a00 (LWP 9837) exited]
[Thread 0x7fffe1763a00 (LWP 9836) exited]
[Thread 0x7fffe176fa00 (LWP 9835) exited]
[Thread 0x7fffe177ba00 (LWP 9834) exited]
[Thread 0x7fffe1787a00 (LWP 9833) exited]
[Thread 0x7fffe1793a00 (LWP 9832) exited]
[Thread 0x7fffe179fa00 (LWP 9831) exited]
[Thread 0x7fffa97fa640 (LWP 9809) exited]
^C
Thread 1 "ArdourGUI" received signal SIGINT, Interrupt.
0x00007ffff5689119 in ?? () from /usr/lib/libc.so.6
(gdb) bt
#0 0x00007ffff5689119 in () at /usr/lib/libc.so.6
0000001 0x00007ffff568e113 in () at /usr/lib/libc.so.6
#2 0x00007ffff3f2b326 in () at /usr/lib/libjack.so.0
#3 0x00007ffff3f0b23c in () at /usr/lib/libjack.so.0
0000004 0x00007ffff3f0a149 in () at /usr/lib/libjack.so.0
0000005 0x00007ffff3f2ed75 in jack_client_close () at /usr/lib/libjack.so.0
#6 0x00007fffe9cabe70 in ARDOUR::JackConnection::close() () at /usr/lib/ardour6/backends/libjack_audiobackend.so
#7 0x00007fffe9cac23b in ARDOUR::JACKAudioBackend::stop() () at /usr/lib/ardour6/backends/libjack_audiobackend.so
0000008 0x00007ffff77264ee in ARDOUR::AudioEngine::stop(bool) () at /usr/lib/ardour6/libardour.so.3
0000009 0x00005555559b87f7 in ()
0000010 0x00005555559ee138 in ()
0000011 0x00007ffff70c59e6 in () at /usr/lib/libglibmm-2.4.so.1
0000012 0x00007ffff6f27c6b in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
0000013 0x00007ffff6f7e001 in () at /usr/lib/libglib-2.0.so.0
0000014 0x00007ffff6f271cf in g_main_loop_run () at /usr/lib/libglib-2.0.so.0
#15 0x00007ffff6b339fe in gtk_main () at /usr/lib/libgtk-x11-2.0.so.0
0000016 0x00007ffff7241d5d in Gtkmm2ext::UI::run(Receiver&) () at /usr/lib/ardour6/libgtkmm2ext.so.0
#17 0x000055555597b8f3 in main ()
(gdb) exit
A debugging session is active.

        Inferior 1 [process 9739] will be killed.

Quit anyway? (y or n) y
$
System Description
Attached Files:
Notes
(0026521)
oml65   
2022-07-24 19:32   
$ uname -a
Linux my_pc 5.18.13-arch1-1 0000001 SMP PREEMPT_DYNAMIC Fri, 22 Jul 2022 13:05:04 +0000 x86_64 GNU/Linux
$
(0026522)
oml65   
2022-07-24 20:44   
Neither Wafeform12 nor Waveform11 nor reaper have this issue.
(0026523)
x42   
2022-07-25 13:36   
This is likely the same issue as https://discourse.ardour.org/t/ardour-hanging-at-shutdown/107260/22?u=x42

Ardour delegates background processing to JACK, and those those threads cannot be stopped due to a recent bug in glibc that arch ships.
It s already fixed upstream: https://sourceware.org/bugzilla/show_bug.cgi?id=29214#c6

meanwhile you could downgrade glibc (as mentioned in the forum thread).
(0026531)
paul   
2022-08-09 19:11   
glibc bug.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8589 [ardour] features minor have not tried 2021-02-26 10:45 2022-07-28 07:49
Reporter: unfa Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Allow panning the timeline in X/Y using middle mouse button
Description: In many programs that feature any form of canvas, the middle mouse button can be held down on empty space to pan the canvas.

I think Ardour would also benefit from such a feature.

How would it work:

When the user hold down MMB while not hovering over any region, the horizontal mouse movement translates to panning the timeline horizontally.
The vertical movement has a dead zone and some increment before it shifts the view vertically, to avoid crazy track scrolling.

On conjunction with the mouse wheel zoom this would greatly improve user's options of quickly navigating the timeline.

Alternatively, a modifier key could be used to alter MMB's function to allow using pan even if the mouse is hovering over an object, as that'd be much less error-prone,
Though I'd personally use panning much more often, so it'd make more sense to me to have pan be default, and moving regions vertically require a modifier key (Shift for example).

What do you think?
Tags: ui, usability, UX
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0025558)
x42   
2021-02-26 11:41   
tl;dr: Configure your OS or Hardware to do that.

Thinkpads do this unconditionally. Mac Systems likewise offer X/Y scrolling OOTB via magic-mouse or their touchpad.

This is not something application developers should do. Efficient use it depends on the mouse or interface you have.
Furthermore there are additional preferences (natural scrolling), or with some multi-button trackballs you may prefer buttons other than middle-click.
(0026332)
Thovthe   
2022-02-18 03:31   
I agree with the original poster.

Navigating the canvas with come combination of middle-mouse and a key (personally `ctrl+mmb`) becomes natural for anyone who uses 2D or 3D graphics/cad programs. It should be more than one to one mouse movement to canvas movement (1.5 or 3) particularly in the x direction, might make sense for y to be a lower amount though. I find myself trying desperately to drag around before I end up zooming in and out a bunch just to move over a bit.

On windows a different method of interaction that fulfills the same function would probably be covered by the standard middle-mouse-click action but on other platforms this would be a good feature.
(0026524)
acollsen   
2022-07-26 19:24   
I would love this feature. So far this is the hardest thing for me to get used to, to not have this feature.
(0026525)
unfa   
2022-07-26 22:18   
@x42 I don't know of applications that rely on special hardware or OS configurations to do this kind of scrolling.
The grand majority of creative software that has a 2D canvas of some kind I have used (both open-source and proprietary) has this basic feature of panning the canvas by dragging it with a mouse.
Some of the tools are: Inkscape, Blender, GIMP, Krita, Carla, Bespoke Synth, Natron, Godot, Adobe Substance Designer, Adobe Substance Painter, Corel Draw,

It seems strange to me to dismiss that need. Maybe in an alternate reality programs don't need to do that and OS can handle it, I have never witnessed that in action.
(0026526)
x42   
2022-07-26 22:48   
I'm not really opposed to adding this feature, but since there is a better solution, that should be preferred:

On GNU/Linux X11 provides this

xinput set-prop $deviceId "libinput Button Scrolling Button" 2 # Using middle button.
xinput set-prop $deviceId "libinput Natural Scrolling Enabled" 1 # for natural scrolling.

You can get the deviceID via `xinput list`

Chances are that your desktop's mouse configuration tool also allows to configure it. Search for "Auto Scroll".
This will then work consistently for all UI applications! e.g. Chromium/Chrome doesn't support this by default, and in Firefox it's an option.
(0026527)
paul   
2022-07-27 15:12   
@x42 not sure that's an equivalent "solution". I think what is being asked for here is not changing the default scroll button, but adding h-scroll behavior from a middle-button drag.
(0026528)
paul   
2022-07-27 15:13   
@acollsen, @unfa: do you not have scroll wheels with horizontal scroll behavior?
(0026530)
acollsen   
2022-07-28 07:49   
For example: If I click and hold the middle mouse button on the editor canvas I would love for the canvas to stick to the mouse pointer so i could drag the canvas around with the mouse without any delay or smooth scrolling. The Firefox auto-scroll is NOT what I mean.

Try opening Inkscape for example and middle click and drag on the canvas. Blender uses Shift+middle-click I think.

Thanks.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
7741 [ardour] features minor always 2019-03-20 23:22 2022-07-23 22:27
Reporter: colinf Platform:  
Assigned To: x42 OS:  
Priority: normal OS Version:  
Status: feedback Product Version: 5.X git (version in description)  
Product Build: Resolution: reopened  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Group gain sharing should never happen for groups where it's not enabled
Description: If I want a group to have gain sharing (either absolute or relative), I'll enable it in the group's properties. If I don't want a group to have gain sharing by default, I certainly don't want it to have gain sharing when I <Shift>+Click on any of the groups faders. There are more use cases for groups without gain sharing than with it, in my experience, especially now that we have VCAs, which do all that group gain sharing could and more.
Tags:
Steps To Reproduce:
Additional Information: I have a vague memory of making this report before, but I can't find it now...
Attached Files: grouped-fader-shift-click.ods (11,974 bytes) 2022-05-22 13:56
https://tracker.ardour.org/file_download.php?file_id=4189&type=bug
0001-gtk2_ardour-only-allow-shift-click-to-disengage-fade.patch (1,219 bytes) 2022-05-22 17:58
https://tracker.ardour.org/file_download.php?file_id=4190&type=bug
0001-gtk2_ardour-only-allow-shift-click-to-disengage-fade-2.patch (1,213 bytes) 2022-07-15 16:41
https://tracker.ardour.org/file_download.php?file_id=4198&type=bug
0002-gtk2_ardour-disable-reset-to-default-on-shift-click-.patch (1,275 bytes) 2022-07-23 14:58
https://tracker.ardour.org/file_download.php?file_id=4201&type=bug
0001-libs-widgets-allow-fader-to-opt-out-of-shift-click-r.patch (1,553 bytes) 2022-07-23 14:58
https://tracker.ardour.org/file_download.php?file_id=4202&type=bug
Notes
(0020925)
colinf   
2020-01-22 12:34   
This still bothers me. I might have just grouped some tracks to record-enable them together more easily, or even just to make them all the same colour - I really never want gain-sharing for such a group, shift pressed or not.

I do find <shift>+click on faders to reset them occasionally useful, but if I accidentally<shift>+click a grouped fader it'll reset all the faders of the group, regardless of what the group is for. Worse, it doesn't even do it consistently: it depends on the setting of the group's 'Relative' gain tick box (which isn't even enabled if 'Gain' is unticked) as to whether the other faders in the group will all reset to 0dB, or keep their gains relative to the 0dB level of the <shift>+clicked fader. Worse still, even if 'Relative' is ticked, faders that would have gone above +6dB are clamped to +6dB, and even the relative balance of the group faders is lost.
(0020930)
bluebones   
2020-01-25 13:27   
+1

Would be nice to have the handy shift+click gain reset back affecting just one track, given that Gain is unticked on group settings.
(0020931)
bluebones   
2020-01-25 13:39   
I'd add that this happens even with group's side label deactivated, which actually makes me think of it as a bug rather than a feature request.
(0020937)
colinf   
2020-01-27 19:30   
And it's no less inconsistent when a group has 'gain' sharing enabled: in that case, <shift>+click on a grouped fader resets just that fader to 0dB, except if the group itself is disabled, in which case it resets all the faders, relatively or absolutely according to the 'relative' setting.
(0020938)
colinf   
2020-01-27 19:34   
I believe that <shift> was originally supposed to invert the enabled status of a group when clicking on elements of tracks with that group, but even that doesn't seem consistent: some mixer strip controls (e.g. record arm) treat <ctrl > in that way instead.
(0026433)
johne53   
2022-05-05 09:20   
This relates to a bug we've been discussing on the Mixbus forum. Mixbus has a few problems of its own but AFAICT, when the Shift key is being pressed, neither Mixbus nor Ardour take any notice of a group's Gain Sharing status :-(

Surely this can't be difficult to fix ?
(0026453)
x42   
2022-05-21 21:13   
This is intended behavior. Holding down the primary modifier key inverts group behavior: `InverseGroup` (enable disabled groups, disable enabled groups or group-settings)
(0026454)
johne53   
2022-05-22 10:46   
Hi Robin - the problem is that different controls exhibit different behaviours. Mixbus has some additional issues (controls on the Mixer don't always behave like they do in the Editor) but let's just concentrate on Ardour for now...

1) Add 2 tracks to a group and then edit the group to remove the gain control.
2) Each fader behaves (correctly) as though it's not part of the group. And using Shift+ inverts that behaviour (correctly, as we now know...)
3) Now try removing some buttons from the group (let's say the Muting button)
4) Each Mute button now behaves (correctly) as if it's not part of the group - BUT... using Shift+ makes no difference (i.e. it doesn't invert the behaviour)
(0026455)
colinf   
2022-05-22 13:56   
I made a spreadsheet (I know, sorry) enumerating the the <Shift>+click fader behaviour for all the possible states of group enabled/gain sharing/relative to see if it made any more sense seeing it in a table like that. Here it is: is this really all intended behaviour?
(0026456)
colinf   
2022-05-22 14:01   
Incidentally, there's also this comment in gtk2_ardour/gain_meter.cc:586

        // XXX hack allow to override group
        // (this breaks group'ed shift+click reset)

I'd argue that breaking <shift>+click reset to 0dB is rather a steep price to pay to allow three different ways to override disabling group gain sharing to exist.
(0026457)
colinf   
2022-05-22 14:06   
Also, it seems perverse to me that a disabled (greyed-out) tick box in the group properties should affect the behaviour of the group.
(0026458)
colinf   
2022-05-22 17:58   
Attached a (trivial) patch to only allow <shift>+click to disable gain sharing if it's enabled in the active group's properties, and not to enable it if it's disabled. I personally think this is better: if the behaviour of enabling gain sharing in a disabled group is also required I really do believe something rather more clever is required than the current code.
(0026505)
colinf   
2022-07-15 16:41   
Updated patch to fix merge conflict after 6089ae93 attached. I still find it hard to believe that the behaviour of <shift>+click on faders of channels in disabled groups without this patch is either intended or desirable.
(0026519)
colinf   
2022-07-23 14:58   
An alternative approach, if the <Shift> override to enable gain sharing is really deemed more important than <Shift>+click to reset to 0dB could be disabling the reset to 0dB behaviour for grouped tracks. I don't like it, but at least it removes the "Oops, I just set all these faders and I don't know how to put them back" on <Shift>+click behaviour, which was my original motivation for this report.

Alternative hacky patches attached (001-libs-widgets-allow-fader-to-opt-out-of-shift-click-r.patch & 0002-gtk2_ardour-disable-reset-to-default-on-shift-click-.patch) to do this, in case anyone's interested.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8942 [ardour] bugs major always 2022-07-18 10:03 2022-07-18 13:50
Reporter: KottV Platform: GNU  
Assigned To: x42 OS: Linux  
Priority: normal OS Version: (any)  
Status: resolved Product Version: 6.9  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ardour LV2 host doesn't provide boundedBlockLength in features array
Description: Hi,

Information is from here https://forum.juce.com/t/juce7-technical-preview-branch/50866/87

For the Ardour issue: JUCE plugins need to know their maximum processing block size, so JUCE LV2 plugins declare bufs:boundedBlockSize as an lv2:requiredFeature. If a plugin requires features that cannot be supplied by the host, the host should not attempt to instantiate the plugin. If the host does supply the feature, then it should include the feature in the array of features passed to the plugin during instantiation. For that assertion to fire, one of the following must be true:

   *The host cannot supply the boundedBlockLength feature, but attempts to instantiate the plugin anyway. The host should not attempt to instantiate the plugin in this case.
    *The host can supply the boundedBlockLength feature, but does not include it in the features data array. In this case, the host should be updated to include boundedBlockLength in its features array.
Tags:
Steps To Reproduce: Compile any JUCE plugin with LV2 support.
Install plugin in LV2 path.
Scan for the new plugins in Ardour.
Add new plugin.
Additional Information:
System Description
Attached Files:
Notes
(0026508)
x42   
2022-07-18 12:52   
It's a feature that plugins can require (lv2:requiredFeature), and the host in turn implements and provides
http://lv2plug.in/ns/ext/buf-size#minBlockLength
http://lv2plug.in/ns/ext/buf-size#maxBlockLength

In case of Ardour both are set, minBlockLength is 1 and maxBlockLength 8192. This has been implemented since 2015.

Compare to other plugins that use it (ZynAddSubFX.lv2, KlangFalter.lv2, Pianoteq 6.lv2, moony.lv2 etc)
(0026509)
KottV   
2022-07-18 13:03   
thnx, forwarded to juce forum
(0026510)
KottV   
2022-07-18 13:16   
BTW I haven't such issue in the jalv, Muse, Reaper, Carla
(0026511)
x42   
2022-07-18 13:20   
Odd the same person who wrote jalv (and the LV2 spec) also wrote Ardour's implementation.
(0026512)
KottV   
2022-07-18 13:23   
I know :)
Could you take a look at JUCE implementation, please? Or give a point?
(0026513)
x42   
2022-07-18 13:24   
Reading the source, it looks like the feature is indeed not explicitly announced to the plugin, but the min/max options are set.
(0026514)
reuk   
2022-07-18 13:32   
When a host supports an `lv2:requiredFeature`, the host MUST pass the feature's URI and any additional data to the plugin in LV2_Descriptor::instantiate(), and the plugin MUST fail to instantiate if a required feature is not supported by the host. (See http://lv2plug.in/ns/lv2core#requiredFeature).

I believe that the JUCE implementation is adhering to the spec by failing to instantiate, given that the host is not reporting boundedBlockLength as supported. Plugins that declare boundedBlockLength as a requiredFeature, but which don't check that the host provides this feature, do not adhere to the spec.

If there's some provision in the spec that means 'data-only' features don't need to be included in the LV2_Feature array, please provide a link to this provision so that I can reference it in a change to JUCE.

If there's no such provision, then I believe the wording in the spec is unambiguous, and Ardour must add boundedBlockLength to its array of supported features in order to declare support.
(0026515)
x42   
2022-07-18 13:46   
It is redundant, so it seems plugins just read the options (if present), regardless of the host announcing the feature.
It makes lot more sense the other way around. A host that does not provide the options should refuse plugins that require the feature.

Anyway fixed now in Ardour 7.0-pre0-3175-g79f8606b2d -- Thanks for the heads up.
(0026516)
reuk   
2022-07-18 13:50   
Great, thanks!


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8941 [ardour] bugs crash always 2022-07-16 00:01 2022-07-16 00:01
Reporter: tc69 Platform: Arch  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ardour crashes if you try to remove ZynReverb plugin from a midi track.
Description: The plugin itself works fine while it's added to the midi track.
The crash happens with all other synths I've tested it, except for when it's used with ZynAddSubFX.
Tags:
Steps To Reproduce: 1. Create a midi track
2. Add ZynReverb
3. Remove ZynReverb from the track
Additional Information: Ardour terminal output when crash happens:

GLib (gthread-posix.c): Unexpected error from C library during 'pthread_setspecific': Invalid argument. Aborting.
Aborted (core dumped)
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8823 [ardour] bugs minor always 2021-11-19 17:59 2022-07-14 02:12
Reporter: rohanlean Platform: GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: MIDI automation causes repeated messages to be sent for constant values
Description: While trying out the Salamander Grand Piano with sfizz I noticed that if the sustain pedal (CC64) is automated, then if the pedal is fully disengaged or fully engaged, the pedal sound is triggered all the time. Presumably Ardour sends control messages all the time. I have submitted a pull request for the Salamander piano that changes the pedal noise values to trigger just before the endpoints instead of at them, but I am not sure if that is the right approach. Even with that fix, the pedal noise triggers multiple times instead of just once if the pedal is moved slowly.

I think it might be best if Ardour did not send repeat messages if the previous value is unchanged.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files: MIDI-CC-playback.png (17,406 bytes) 2021-11-20 11:41
https://tracker.ardour.org/file_download.php?file_id=4136&type=bug
sustain_pedal-2021-11-22.zip (33,203 bytes) 2021-11-22 19:48
https://tracker.ardour.org/file_download.php?file_id=4139&type=bug
no_mode.png (5,963 bytes) 2021-11-22 19:48
https://tracker.ardour.org/file_download.php?file_id=4140&type=bug
Notes
(0026219)
x42   
2021-11-20 11:41   
Could you provide an Arodur session or .mid file that causes this?

I cannot explain this, nor reproduce it. CC parameter changes are only sent when there is a value change (see ACE MIDI Monitor)
(0026220)
rohanlean   
2021-11-20 13:13   
My setup is as follows:

Ardour 6.9 (flathub, commit 0bdbac43f4bfcdacb69bc5f61d8dbd0ffa01e4ef893553be676877b00147351f),
sfizz 1.1.1 (flathub, runtime 21.08, commit a7bc503d34572af978b163d9f6f6fb04c95790622936f06a2fa9b0884e6a1d83),
Salamander Grand Piano ( https://github.com/sfzinstruments/SalamanderGrandPiano , commit f974189f4d12c99f4f214aadfb4538faf7e7f54f)

New Ardour session, new MIDI track with sfizz, Salamander loaded in sfizz; add an automation lane for controller 64.

Simply witching the automation lane from Manual to Play (no need to start playback) causes
the track to emit constant low level noise, and for sfizz to show 32-37 voices playing at once.

Increasing the the trigger level for the pedal noise from 0 to 1, as here: https://github.com/sfzinstruments/SalamanderGrandPiano/pull/3/files
resolves this.

Oddly enough for me the ACE MIDI Monitor shows no MIDI messages from the automation lane at all. I am probably using it wrong.
(0026224)
paul   
2021-11-22 18:06   
could you check what the mode selection for the CC lane (right click on the CC track header) ?
(0026225)
rohanlean   
2021-11-22 18:47   
On the previous automation track, which I had added through

  Automation > Processor automation > sfizz > Parameters 65-96 > Controller 64

I see no mode selection. But I have now noticed that there is also

  Automation > Controllers > 64: Sus Pedal > Channel 1

which shows discrete mode, only has states Off and Play, and **does not have this problem**.

Does that mean this is a bug in sfizz?
(0026226)
paul   
2021-11-22 19:08   
Right click on automation track header. A menu will appear that has "Mode" at the bottom.
(0026227)
x42   
2021-11-22 19:32   
> Does that mean this is a bug in sfizz?
We have too little information, and also some imprecise info on the subject.

Could you create a session that produces the problem. save and .zip it up and share it? That would be helpful.

Does anyone else also have this issue? Have sfizz authors been able to reduce it?
(0026228)
rohanlean   
2021-11-22 19:48   
I thought that after my last post the instructions for reproduction were unambiguous, but I have attached a project per your request;
also a screenshot which shows that no "Mode" entry appears in the menu for me.
(0026229)
paul   
2021-11-22 21:21   
I have now debugged this with sfizz and salamander from current git, and I'm extremely certain that it's a bug in sfizz. Ardour does not send repeat messages, and sfizz' behavior is not replicated by other synths that are sustain-pedal aware (e.g. Pianoteq with a piano model that has a loud pedal noise).
(0026230)
paul   
2021-11-22 21:24   
I also just tested this using an actual sustain pedal. If the pedal is held down, the pedal "noise" (i used an amplifier to hear it more clearly) plays continuously until I release the pedal.
(0026231)
rohanlean   
2021-11-22 22:03   
Thank you. I will raise the issue with the sfizz developers.

Just to help my understanding, if such questions are appropriate here:

The Automation > Controllers lane is part of the MIDI data and generates messages in a standardised way,
whereas the Automation > Processor automation lane is separate and sends floating point numbers to
sfizz via some plugin interface, generating the floating point numbers by linearly interpolating (time, value)
pairs and sending an update to sfizz every frame (?) where the floating point value compares unequal to the last one?
(0026232)
paul   
2021-11-22 23:41   
(Last edited: 2021-11-22 23:42)
When the CC lane is in Mode > Discrete there is zero interpolation at all. Ardour simply sends individual CC events, the same ones displayed as control points in the lane display. It sends no data that was not recorded or explicitly drawn for the CC track.

When the CC lane is in Mode > Linear, Ardour will interpolate between the points (linear interpolation) and sends a new (potentially interpolated) value periodically. It will not resend the same value, ever.

In both cses, no floating point numbers are involved. The CC track display/represents actual CC messages, and Ardour delivers CC messages to the plugin as MIDI data. This is quite different from generalized plugin automation (which is not CC data, and is presented as floating point).

I do not know why your version of Ardour does not show the Mode option in that context menu. My impression is that it's not an official Ardour build, which makes it harder to offer support for issues like that.

(0026233)
x42   
2021-11-23 15:52   
@paul : the label is "sfizz Controller 064" which is a plugin parameter (and hence float). Also note the automation label "Manual"

MIDI CC lanes show "Damper Pedal" (depending on MIDNAM) but neither track or plugin label. That also explains why there is "Manual" (and not "Off").
(0026234)
x42   
2021-11-23 15:54   
One explanation would be an internal conflict in sfizz. Plugin-parameter (Controller 064) vs. MIDI data CC64.
A plugin must only ever expose one, otherwise there can be ambiguities.
(0026235)
paulfd   
2021-11-24 13:22   
So this is a plugin parameter automation track and not a MIDI one is that it? In this case, does Ardour send the current parameter value in each block for example? Does the same thing happen if you actually automate the CC64 track?

The underlying behavior is that you can have a voice play when receiving a CC message with value in a certain range. This is typically used by piano libraries for sustain pedal noises.

Robin is probably onto something however. Since sfizz allows user-defined parameters beyond the actual number of CCs in the midi spec, and with higher-than-7-bit resolution, these are advertised as plugins parameters, and the first 127 are bound to midi in the VST3 plugin, and (should be) marked with `midi:binding` in the LV2 spec. However the latter has proven problematic because if the host doesn't support the `midi:binding` annotation, you have the terrible UX of having your sustain pedal basically do nothing until you manually bind "plugin parameter 64" to "input midi CC 64". If this is the issue, I'll just remove the first 127 parameters from the LV2 until the binding is more common.
(0026236)
paul   
2021-11-24 16:05   
I've described what happens with the "actual" MIDI CC 64 controller, both via automation in ardour and also when using a physical sustain pedal.

When I get a chance, I'll check the sfizz "exported" Controller064 parameter.
(0026237)
x42   
2021-11-25 18:59   
> In this case, does Ardour send the current parameter value in each block for example?

In case of VST3 automation playback: Yes, implicit curve points at the end of each cycle are always queued explicitly.

This applied to the dashed circles in the diagram:
https://developer.steinberg.help/display/VST/Parameters+and+Automation#ParametersandAutomation-AutomationPlayback

This is something on our long list of VST3 things to tweak. Since one can do arbitrary locations or change the loop-point while looping, the only sane way
to determine if implicit points have to be transmitted is compare the value with a the most recently sent value (and unset it if automation playback mode changed).
Since a plugin will have to do this anyway internally in order to dezipper control parameters, I opted to not implement the discrimination logic in the host, assuming no harm is done my making the curve explicit.
(0026238)
rohanlean   
2021-11-25 20:45   
A somewhat off topic observation here is that Ardour seems to continually pass arguments even while playback is paused. In general I have noticed that Ardour uses more resources than necessary while "idle". I understand that things could happen even then, and that because Ardour does not know what plugins are up to it may be difficult to determine just when nothing is happening. So maybe this issue cannot be solved completely, but any improvements would be nice. Then one does not have to worry so much about leaving Ardour running in the background, especially on a mobile device.

One example I noticed is that simply adding some MIDI tracks without any plugins seems to increase idle resource usage significantly, and I see absolutely no reason for that.

I can open a new issue about idle resource usage if you want.
(0026239)
x42   
2021-11-25 21:00   
> One example I noticed is that simply adding some MIDI tracks without any plugins seems to increase idle resource usage significantly, and I see absolutely no reason for that.

That should not be the case, at least there should not be any significant DSP load increase after the first track.
But yes, by design Ardour's mixer is never idle and constantly processes, like a hardware mixer would. One benefit of that is that the load is constant.

> A somewhat off topic observation here is that Ardour seems to continually pass arguments even while playback is paused.

Not arguments, only port parameters.
The MIDI event-list is sparse and those are discrete events. The plugin should really use MIDI CCs and not expose a control port for those.
I know VST3 makes this complicated and many plugin-devs despise Steinberg's implementation, but at least conceptually it's sound.
(0026240)
paulfd   
2021-11-25 21:22   
> I opted to not implement the discrimination logic in the host, assuming no harm is done my making the curve explicit

Another fix would be for sfizz to disregard controller events that match the current controller state. I'll check if this is indeed what happens in other SFZ implementations and do so if necessary.

> The plugin should really use MIDI CCs and not expose a control port for those.

Technically it's an LV2 parameter :)

> I know VST3 makes this complicated and many plugin-devs despise Steinberg's implementation, but at least conceptually it's sound.

I've come to like it because it avoid such headaches to be honest. If anything, I'd like to be able to capture all channels at once for a given controller.
Anyway I think we can agree the fixes are probably more on sfizz's side so I'll get back to you guys if needed, thanks for your time!
(0026241)
rohanlean   
2021-11-25 21:27   
> One benefit of that is that the load is constant.

That may be true for Ardour itself, but for some popular plugins at least it appears to be false. So I do not think one can reliably judge if the hardware can handle a particular setup just by looking at idle usage, in which case I see only two direct user-facing benefits to any significant idle usage at all: potentially better latency and less overhead under load. Of course users may indirectly benefit from a simpler implementation in other ways.
(0026242)
x42   
2021-11-25 21:32   
> Technically it's an LV2 parameter :)

In this case Ardour will *not* repeat the parameter change.
This is only done for VST3, because the spec demands the value to be sent at the end of each cycle so a plugin can internally interpolate.
(0026243)
x42   
2021-11-25 21:49   
> but for some popular plugins at least it appears to be false.

sadly, yes. This is where pro-audio plugin vendors go to great length to make difference. When live on stage, for FOH mixes, or during a recording-session with a client reliability is key.

> I see only two direct user-facing benefits to any significant idle usage at all: potentially better latency and less overhead under load.

Latency is not affected by this at all. -- Well, if the load is lower, you could use a smaller block-size. But as soon as the system is not idle anymore that is no longer an option.

In case of Ardour, the "overhead" is only to do metering and apply gain (trim and fader). There is dedicated asm code for both of those operations, and one can easily use 1000 tracks without significant DSP load (unless you use the debug version, not an optimized build, which might explain what you're seeing).

Anyway, this is not something that can be changed. This was an early design decision that is deeply ingrained in Ardour's processing engine.
(0026249)
rohanlean   
2021-11-26 12:13   
> unless you use the debug version, not an optimized build, which might explain what you're seeing

I have just checked. The relevant flags that I could see in the Waf output were `-O3 -g -DNDEBUG`, so I am using an optimised build. The DSP load as reported by Ardour indeed does not increase, but adding 8 MIDI tracks to an empty project roughly doubles the CPU use of Ardour reported by `top` (the value is fluctuating in both cases), independently of whether the Ardour windows are visible or not.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8903 [ardour] features minor N/A 2022-04-22 15:40 2022-07-11 21:41
Reporter: colinf Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Allow creation of source markers in regions currently being recorded
Description: I quite often want to place markers whilst recording to note something or other - it'd be nice if those markers could be source markers for the regions currently being recorded.

Unfortunately, the regions currently being recorded don't actually exist as regions until recording is stopped, so implementing this requires special-casing source marker creation while recording to add the marker location & name to a list that can be applied to the newly-created regions after recording ends.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: 0002-gtk2_ardour-set-region-marks-into-currently-recordin.patch (1,670 bytes) 2022-07-11 21:41
https://tracker.ardour.org/file_download.php?file_id=4196&type=bug
0001-libs-ardour-allow-creating-region-source-markers-whi.patch (3,301 bytes) 2022-07-11 21:41
https://tracker.ardour.org/file_download.php?file_id=4197&type=bug
Notes
(0026501)
colinf   
2022-07-11 21:41   
Patches attached.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8885 [ardour] bugs minor always 2022-02-27 22:49 2022-07-08 16:22
Reporter: mtemmerm Platform: Debian GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: AKAI MPK249 midi map not working as expected (new maps included)
Description: There are some issues with the current midi map (e.g. switches need to be pressed twice to toggle solo on/off). I made new ones, one that uses the switches to toggle solo on/off, one that toggles mute on/off (my preference).
Tags: control surface
Steps To Reproduce: When using the current AKAI MPK249 midi map, press a switch twice to toggle solo on/off, this is not as it should be.
Additional Information: Changed clt to ctl-toggle in the midi map, and also set the Master fader to the Modwheel on the controller instead of the last fader in bank C. It's a bit of a hack, but I find it better this way.
System Description
Attached Files: AKAI_MPK249-mute.map (4,975 bytes) 2022-02-27 22:49
https://tracker.ardour.org/file_download.php?file_id=4163&type=bug
AKAI_MPK249-solo.map (4,975 bytes) 2022-02-27 22:49
https://tracker.ardour.org/file_download.php?file_id=4164&type=bug
AKAI_MPK249-mute-2.map (5,068 bytes) 2022-02-28 15:08
https://tracker.ardour.org/file_download.php?file_id=4165&type=bug
AKAI_MPK249-solo-2.map (5,068 bytes) 2022-02-28 15:08
https://tracker.ardour.org/file_download.php?file_id=4166&type=bug
Notes
(0026338)
mtemmerm   
2022-02-28 15:08   
Updated the midi maps: these have strip 8 on bank C as the master control strip, using the modwheel for volume will conflict and was dumb of me.
(0026497)
x42   
2022-07-08 11:50   
The solo-2.map seem to be identical to the the existing map, but changes "ctl" to "ctl-toggle" for the solo toggles.
Does it supersede the existing AKAI_MPK249.map ?
(0026498)
mtemmerm   
2022-07-08 16:22   
Hi x42! I set it to ctl-toggle so I don't have to press it twice, that was mostly what it did 'wrong' IMO. I'm afraid I don't know quite how to answer your question though... it supersedes it on my computer, as I overwrote the file, but I'm not a dev, just a Linux-using musician :).


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8925 [ardour] features feature N/A 2022-06-14 23:09 2022-07-06 08:38
Reporter: nika.hrlyn Platform: Arch  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: save and restore plugin views
Description: i would like to be able to open and close groups of plugins with a shortcut. like all my analyser plugins organized on my second screen. or all the related bus EQ. or the two bus plugin chain. all in the neat positions that i arranged when i saved the plugin view.similar maybe to saving editor views
Tags: plugin, preset, safe view, workflow
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0026494)
x42   
2022-07-05 15:16   
Ardour already remembers the position of plugin windows.

Is this about having multiple arrangements, rather than a single position information for plugins?

Or do you simply want to open/close the UIs in groups? e.g. show/HIde all EQs, or Show all plugins of selected tracks(s)?
(0026495)
nika.hrlyn   
2022-07-06 08:38   
I simply want to open/close the UIs in groups.
But if there are multiple arrangements that could be interesting also.
For example in one plugin view I open all the Plugins on the 2Bus and there the Spectrum analyzer is in the bottom right.. but in a second view, in which I have all my EQ open, the spectrum analyzer fills half of the screen.

But honestly that would go beyond my expectaions.. for now id just like to be able to open/close in groups :)


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
7768 [ardour] features minor N/A 2019-06-22 02:10 2022-07-04 04:22
Reporter: jeffbrown Platform: Some Other Linux  
Assigned To: OS: Some Other Linux  
Priority: normal OS Version: unknown  
Status: new Product Version: 5.12  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: MIDI warp: linearly stretch the timing of MIDI events in a region
Description: # Linear MIDI warping

In Ableton Live you can "warp" audio -- you might take a 2 second clip of sound, and stretch it so that what used to be the first half of the clip occupies the first 90%, and what used to be the second half occupies the remaining 10%.

Doing that with audio seems hard, and I'm not asking for it. But similarly warping MIDI is dead simple, at least mathematically (see below). And surprisingly, Ableton do not offer it.

This feature would let the user add "warp marks" to a point in the MIDI timeline, and then drag them around. Dragging a warp mark causes a linear stretching of the events around it, while keeping the other warp marks fixed.


## One reason you might want to do this

Suppose you record without a metronome, and your left hand always slams down a particular chord X at the start of the beat. If you stuck a warp mark at the start of each X, you could then drag those marks around to change the tempo of what you played locally, while preserving the rhythm.

Among other possibilities, this lets you add a click track after you've recorded without one. That's valuable because many players find it easier to be more creative without a click track.


## The math

Suppose the user has drawn three warp marks, at times `a`, `b0` and `c`, where `a < b0 < c`. Suppose the user then drags the middle marker from the old time `b0` to the new time `b1`.

No MIDI events before `a` or after `c` will be affected by the move. (For warp purposes, the start and end of a note are treated as two separate MIDI events.)

Consider a MIDI event which, before `b0` is warped to `b1`, occurs at time `t0`, where `a < t0 < b0`. After warping, this event will occur at time `t1`, where
```
t1 = (t0 - a) * (b1 - a) / (b0 - a) + a
```

Similarly, if `b0 < t0 < c`, then after `b0` is warped to `b1`, an event which used to occur at time `t0` will now occur at time `t1`, where
```
t1 = c - (c - t0) * (c - b1) / (c - b0)
```

Those formulas work regardless of whether the middle marker is dragged forward or backward.
Tags: Midi
Steps To Reproduce:
Additional Information: If my description is not clear, I could try making some animations and upload them to Youtube.
System Description
Attached Files:
Notes
(0020806)
x42   
2019-11-01 01:16   
Thanks for the elaborate suggestion. The description is clear, but it's not something that can be implemented in the near future.

The problem here is at a different level: "t" in your case is just some abstract continuous time unit.

Ardour's engine handles currently uses a ratio for audio time (when events actually are played to the soundcard): N / sample-rate.
While music-time (bar/beat/ticks) and a tempo-map is currently use double-precision floating point value (mainly for the benefit of exponential tempo-ramps).
GUI Edits can happen at independent music-time units (e.g. move one bar forward, and backwards) and should be lossless.

The problem is that there is no bijective map between the different time-domains, mainly due to rounding issues.

There are some plans to move to a common high-precision time-base ratio ("superclock") to return to some sane state of linear algebra. There are also some thoughts how to represent music-time: https://ardour.org/timing.html but this is a deep change and will likely not happen before Ardour7.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8932 [ardour] bugs minor always 2022-06-29 16:49 2022-06-29 16:58
Reporter: afranke Platform: GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: midnam Values not taken into account for automation ranges
Description: On a MIDI track, I set it to Novation A Station and add an automation on controller 3 (Arp Pattern). I then get a slider that goes from 0 to 127.

Looking at the matching MIDNAM file (shipped with Ardour), I see that the values are supposed to be between 0 and 5. Ardour ignores that range.

The 6 values also have names in a ValueNameList, but those aren’t displayed anywhere, as far I can see. Is this also ignored?
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0026491)
x42   
2022-06-29 16:58   
Ardour only uses Midnam for annotation, not to constrain parameter-ranges.
Looking at the source-code, the value-names should be displayed in the verbose cursor (when hovering over an automation point).

I agree that the value-names should ideally also be displayed on the Fader-Control itself.

I am unsure about constraining the range (and showing it as dropdown). One can change the name-document on the fly and CCs range is not really constrained.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8931 [ardour] features feature N/A 2022-06-24 17:23 2022-06-28 06:09
Reporter: tmu Platform: Debian GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Lock Position of everything Audio
Description: Would it be possible to lock the position of audio (and MIDI) but have anything else (region boundaries, automation, ...) movable?

I could imagine a second Lock Mode ("Lock Audio"?) or some checkboxes somewhere to select which items to lock in Lock Mode.
Tags: editing, lock
Steps To Reproduce:
Additional Information: My usual work with Ardour/Mixbus is editing live recordings. So there’s no Grid and none of the Audio should ever move, once it is in place. A lot of the editing is deleting the parts where the instrument on the specific channel doesn't play: Noone needs to hear the drumset over the Backing Vocals SM58 all the time. This means a lot of selecting, splitting and moving the region boundaries.

But often the regions move a tiny bit when I only want to select them. Of course, that doesn’t happen in Lock Mode, but then I cannot move anything.
System Description
Attached Files:
Notes
(0026489)
chance_favre   
2022-06-26 11:36   
I agree, for the same reasons -- editing live recordings. Thanks.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8930 [ardour] features minor always 2022-06-19 15:18 2022-06-19 15:18
Reporter: Alkukoira Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: In Blueberry Milk "color theme" the grid is off kilter (+ color tuning)
Description: In Blueberry Milk (which I love)-- thanks for the light layout-- the grid emphasizes off beats (in basic quarter note division). The grid lines for 1.5, 2.5, 3.5 are thicker than, say, 1.2.0, 1.3.0, 1.4.0.

It's a very feminine approach to emphasize the off-beats (reggae springs to mind), and as a custom setup such a grid division can be usable, however, is it intentional (or intuitive (to Ardour's largely male user-base)?

Also, using, say ACE Delay in Blueberry Milk, the sync button (among others) gets swallowed up in the color setup, so finetuning the color themes with this mind, and also the purity of colours, would be a great advance for Ardour and its users.

Thanks, and namaste.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8893 [ardour] bugs minor always 2022-03-26 14:03 2022-06-18 12:40
Reporter: johne53 Platform: Microsoft  
Assigned To: OS: Windows  
Priority: normal OS Version: 10  
Status: new Product Version: Mixbus 8.x  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Cue page crash when monitoring changes
Description: Mixbus v8 can be made to crash quite easily in the new Cues page...
Tags:
Steps To Reproduce: - Select a clip in the new Cues page (preferably one that's 20 secs length or more)
- Click on "/2" to change its BPM
- Click on the icon to start playback
- Pressing the "Master" button a few times will cause MB to crash (disappear from the screen)

If the crash doesn't happen, press "x2" or "/2" again. It'll usually happen very soon.
Additional Information: Has only been found on Windows so far.
System Description
Attached Files: Mixbus32C-8.0.17-crash-1648312824.txt (7,180 bytes) 2022-03-26 16:53
https://tracker.ardour.org/file_download.php?file_id=4173&type=bug
Notes
(0026361)
x42   
2022-03-26 16:27   
Is there a file in %localappdata%\Mixbus8\CrashLog\ ?
(0026362)
johne53   
2022-03-26 16:53   
I just recreated the crash here and yes, it generated a crash log (attached). It looks like the problem is in 'RubberBand::RingBuffer<float>::write<float>'

Possibly a problem with buffer size or alignment? It doesn't happen if I don't keep assigning and unassigning 'Mstr'.

BTW - the issue was initially reported by user PBuryk over on the Mixbus forum.
(0026484)
johne53   
2022-06-18 12:40   
Am I right in thinking this got fixed (I can't reproduce it now...)


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8927 [ardour] other minor always 2022-06-15 22:47 2022-06-15 22:47
Reporter: prokoudine Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: MIDI markers and region markers have different look and function
Description: MIDI markers and region markers serve pretty much the same purpose. However, they differ in their location, rendering style, and ability to be edited. It could be worth revisiting them to see if all that needs a unification of sorts, in both form and function.

Also, since audio files can have built-in markers too, the checkbox in the importing dialog should probably named in a more general way?
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8924 [ardour] documentation text always 2022-06-12 14:29 2022-06-15 13:33
Reporter: jkbd Platform: Arch  
Assigned To: x42 OS: Linux  
Priority: low OS Version: (any)  
Status: resolved Product Version: 6.9  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: "Print Bindings (to you webbrowser)" contains wrong bindings
Description: The HTML contains for example:

```
{ --------------------------Set Punch from Selection
{ --------------------------Set Loop from Selection
```

which mismatches the true bindings:

```
[ --------------------------Set Punch from Selection
] --------------------------Set Loop from Selection
```

I have not checked all the other bindings.
Tags:
Steps To Reproduce: Hit Alt-K. Click on the "Print Bindings" button and look into the Editor Window section.
Additional Information: This is independent from the local language. I tried English and German.
System Description
Attached Files:
Notes
(0026481)
x42   
2022-06-15 13:33   
Fixed in 7.0-pre0-2973-g047296060f


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8832 [ardour] bugs minor always 2021-12-02 17:58 2022-06-09 16:36
Reporter: rohanlean Platform: GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Crash when percussive MIDI note is placed at end of region
Description: Selecting "Note Mode > Percussive" on a MIDI track and then placing a note at the very end of a region (using grid snapping) crashes Ardour.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files: ardour_midi_backtrace.txt (6,416 bytes) 2022-06-09 16:36
https://tracker.ardour.org/file_download.php?file_id=4194&type=bug
Notes
(0026389)
paul   
2022-04-16 00:39   
Please read http://ardour.org/debugging_ardour and try to provide a backtrace for this crash.
(0026480)
rohanlean   
2022-06-09 16:36   
Apologies for the belated response. I have attached a backtrace.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8922 [ardour] bugs major always 2022-06-07 14:15 2022-06-07 14:15
Reporter: xav Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Beginning of the recording is missing when using Jack transport
Description: When recording a Hydrogen stereo drums track using Jack transport, the recording start is delayed by 55ms (see picture).
Tags: jack, recording
Steps To Reproduce: Create a stereo "Drums" track
Connect this track with the stereo output of Hydrogen
Enable JACK transport in Ardour.
Set Ardour as JACK master.
Enable JACK transport in Hydrogen ("J. TRANS" icon).
In Ardour, set the timeline to the beginning.
Make the recording.
Additional Information: Jack 1.9.20
Hydrogen 1.1.1
System Description
Attached Files: ardour_bug.png (80,525 bytes) 2022-06-07 14:15
https://tracker.ardour.org/file_download.php?file_id=4193&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8916 [ardour] bugs major always 2022-05-29 17:31 2022-05-31 19:13
Reporter: rpatros Platform: Arch  
Assigned To: x42 OS: Linux  
Priority: normal OS Version: (any)  
Status: resolved Product Version: 6.9  
Product Build: Resolution: no change required  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ardour 6.9 not able to close when closing the program
Description: Unable to close Ardour 6.9 when closing the program. It just hangs and does not close and then after some time, I get a warning message saying:

This window might be busy and is not responding. Do you want to terminate the application?

Ardour 6.9 not able to close when closing the program.
Tags: GUI, unable to close ardour
Steps To Reproduce: Running Arch linux running Kernel 5.15.41-1-lts

1. I have a project that I have 2 audio tracks, 1 midi track and 2 buses.
2. My problem is that when trying to close Ardour program, it just hangs and does not close and then after some time, I get a warning message saying:

This window might be busy and is not responding. Do you want to terminate the application?

3. Started jack without Realtime and then started ardour in gdb using the following command:

ardour6 --gdb
Additional Information: gdb output when the project was opened and after attempting to close the application:

[rpatros@patros-pc tmp]$ ardour6 --gdb
GNU gdb (GDB) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/ardour6/ardour-6.9.0...
(No debugging symbols found in /usr/lib/ardour6/ardour-6.9.0)
(gdb)
(gdb) run
Starting program: /usr/lib/ardour6/ardour-6.9.0
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Ardour6.9.0 (built using 6.9 and GCC version 11.2.0)
Ardour: [INFO]: Your system is configured to limit Ardour to 524288 open files
Ardour: [INFO]: Loading system configuration file /etc/ardour6/system_config
Ardour: [INFO]: Loading user configuration file /home/rpatros/.config/ardour6/config
[New Thread 0x7ffff0afe640 (LWP 111540)]
Ardour: [INFO]: CPU vendor: GenuineIntel
Ardour: [INFO]: AVX-capable processor
Ardour: [INFO]: CPU brand: Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz
Ardour: [INFO]: Using AVX optimized routines
[New Thread 0x7fffebfff640 (LWP 111541)]
[New Thread 0x7fffe3fff640 (LWP 111542)]
[New Thread 0x7fffeb7fe640 (LWP 111543)]
Ardour: [INFO]: Loading plugin meta data file /usr/share/ardour6/plugin_metadata/plugin_tags
Ardour: [INFO]: Loading plugin statistics file /home/rpatros/.config/ardour6/plugin_metadata/plugin_stats
[New Thread 0x7fffeaffd640 (LWP 111544)]
[Thread 0x7fffeaffd640 (LWP 111544) exited]
[New Thread 0x7fffeaffd640 (LWP 111545)]
[New Thread 0x7fffea2a9640 (LWP 111546)]
[New Thread 0x7fffe9993640 (LWP 111547)]
Ardour: [INFO]: Loading default ui configuration file /etc/ardour6/default_ui_config
Ardour: [INFO]: Loading user ui configuration file /home/rpatros/.config/ardour6/ui_config
Ardour: [INFO]: Loading 452 MIDI patches from /usr/share/ardour6/patchfiles
[New Thread 0x7fffe9121640 (LWP 111548)]
[Thread 0x7fffe9121640 (LWP 111548) exited]
[New Thread 0x7fffe9121640 (LWP 111549)]
[New Thread 0x7fffe8920640 (LWP 111550)]
[Thread 0x7fffe9121640 (LWP 111549) exited]
[New Thread 0x7fffe9121640 (LWP 111551)]
[New Thread 0x7fffe36f6640 (LWP 111552)]
[Thread 0x7fffe36f6640 (LWP 111552) exited]
[Thread 0x7fffe9121640 (LWP 111551) exited]
[Thread 0x7fffe8920640 (LWP 111550) exited]
[New Thread 0x7fffe8920640 (LWP 111553)]
[New Thread 0x7fffe36f6640 (LWP 111554)]
[New Thread 0x7fffe9121640 (LWP 111555)]
[New Thread 0x7fffe2ef5640 (LWP 111556)]
[Thread 0x7fffe2ef5640 (LWP 111556) exited]
[New Thread 0x7fffe2ef5640 (LWP 111557)]
Ardour: [INFO]: Loading color file /usr/share/ardour6/themes/dark-ardour.colors
[Thread 0x7fffe2ef5640 (LWP 111557) exited]
Ardour: [INFO]: Loading ui configuration file /etc/ardour6/clearlooks.rc
[New Thread 0x7fffe2ef5640 (LWP 111558)]
[New Thread 0x7fffe2647640 (LWP 111559)]
[Thread 0x7fffe2ef5640 (LWP 111558) exited]
[New Thread 0x7fffe2ef5640 (LWP 111560)]
[New Thread 0x7fffe1e46640 (LWP 111561)]
[Thread 0x7fffe2ef5640 (LWP 111560) exited]
[New Thread 0x7fffe2ef5640 (LWP 111562)]
[New Thread 0x7fffe1645640 (LWP 111563)]
[Thread 0x7fffe2647640 (LWP 111559) exited]
[New Thread 0x7fffe2647640 (LWP 111564)]
[Thread 0x7fffe2ef5640 (LWP 111562) exited]
[New Thread 0x7fffe2ef5640 (LWP 111565)]
[Thread 0x7fffe1e46640 (LWP 111561) exited]
Ardour: [INFO]: Loading bindings from /etc/ardour6/ardour.keys
Loading ui configuration file /etc/ardour6/clearlooks.rc
[Thread 0x7fffe1645640 (LWP 111563) exited]
[Thread 0x7fffe2647640 (LWP 111564) exited]
[Thread 0x7fffe2ef5640 (LWP 111565) exited]
[New Thread 0x7fffe2ef5640 (LWP 111566)]
[New Thread 0x7fffe2647640 (LWP 111567)]
[Thread 0x7fffe2ef5640 (LWP 111566) exited]
[New Thread 0x7fffe2ef5640 (LWP 111568)]
[New Thread 0x7fffe1645640 (LWP 111569)]
[Thread 0x7fffe2ef5640 (LWP 111568) exited]
[New Thread 0x7fffe2ef5640 (LWP 111570)]
[New Thread 0x7fffe1e46640 (LWP 111571)]
[Thread 0x7fffe2ef5640 (LWP 111570) exited]
[Thread 0x7fffe2647640 (LWP 111567) exited]
[Thread 0x7fffe1645640 (LWP 111569) exited]
[New Thread 0x7fffe0e44640 (LWP 111572)]
[New Thread 0x7fffe0c45640 (LWP 111573)]
[Thread 0x7fffe1e46640 (LWP 111571) exited]
[Thread 0x7fffe0c45640 (LWP 111573) exited]
[Thread 0x7fffe0e44640 (LWP 111572) exited]
[New Thread 0x7fffe0e44640 (LWP 111574)]
[New Thread 0x7fffe0c45640 (LWP 111575)]
[Thread 0x7fffe0c45640 (LWP 111575) exited]
[Thread 0x7fffe0e44640 (LWP 111574) exited]
[New Thread 0x7fffe1e46640 (LWP 111576)]
[New Thread 0x7fffe1645640 (LWP 111577)]
[Thread 0x7fffe1e46640 (LWP 111576) exited]
[New Thread 0x7fffe1e46640 (LWP 111578)]
[Thread 0x7fffe1e46640 (LWP 111578) exited]
[Thread 0x7fffe1645640 (LWP 111577) exited]
[New Thread 0x7fffe1645640 (LWP 111579)]
[New Thread 0x7fffe1e46640 (LWP 111580)]
[Thread 0x7fffe1645640 (LWP 111579) exited]
[Thread 0x7fffe1e46640 (LWP 111580) exited]
[New Thread 0x7fffe1e46640 (LWP 111581)]
[New Thread 0x7fffe1645640 (LWP 111582)]
[New Thread 0x7fffe2ef5640 (LWP 111583)]
[Thread 0x7fffe1645640 (LWP 111582) exited]
[Thread 0x7fffe1e46640 (LWP 111581) exited]
[Thread 0x7fffe2ef5640 (LWP 111583) exited]
[New Thread 0x7fffe2ef5640 (LWP 111584)]
[New Thread 0x7fffe1e46640 (LWP 111585)]
[New Thread 0x7fffe1645640 (LWP 111586)]
[New Thread 0x7fffe2647640 (LWP 111587)]
[Thread 0x7fffe1645640 (LWP 111586) exited]
[New Thread 0x7fffe1645640 (LWP 111588)]
[New Thread 0x7fffb3fff640 (LWP 111589)]
[Thread 0x7fffe1645640 (LWP 111588) exited]
[Thread 0x7fffe2647640 (LWP 111587) exited]
[Thread 0x7fffb3fff640 (LWP 111589) exited]
[Thread 0x7fffe9121640 (LWP 111555) exited]
[Thread 0x7fffe2ef5640 (LWP 111584) exited]
[Thread 0x7fffe9993640 (LWP 111547) exited]
[New Thread 0x7fffe1645640 (LWP 111590)]
[New Thread 0x7fffe1446640 (LWP 111591)]
[New Thread 0x7fffe13c5640 (LWP 111592)]
Scanning folders for bundled LV2s: /usr/lib/ardour6/LV2
[New Thread 0x7fffe2ef5640 (LWP 111593)]
[New Thread 0x7fffe9121640 (LWP 111594)]
[New Thread 0x7fffb3fff640 (LWP 111595)]
[Thread 0x7fffe9121640 (LWP 111594) exited]
[Thread 0x7fffb3fff640 (LWP 111595) exited]
Set cursor set to default
[New Thread 0x7fffb3fff640 (LWP 111596)]
[New Thread 0x7fffe9121640 (LWP 111597)]
[Thread 0x7fffb3fff640 (LWP 111596) exited]
[New Thread 0x7fffb3fff640 (LWP 111598)]
[New Thread 0x7fffe2647640 (LWP 111599)]
[Thread 0x7fffb3fff640 (LWP 111598) exited]
[Thread 0x7fffe9121640 (LWP 111597) exited]
[Thread 0x7fffe2647640 (LWP 111599) exited]
[New Thread 0x7fffe2647640 (LWP 111600)]
[New Thread 0x7fffe9121640 (LWP 111601)]
[Thread 0x7fffe2647640 (LWP 111600) exited]
[Thread 0x7fffe9121640 (LWP 111601) exited]
[New Thread 0x7fffe9121640 (LWP 111602)]
[New Thread 0x7fffe2647640 (LWP 111603)]
[Thread 0x7fffe9121640 (LWP 111602) exited]
[New Thread 0x7fffe9121640 (LWP 111604)]
[New Thread 0x7fffb3fff640 (LWP 111605)]
[Thread 0x7fffe9121640 (LWP 111604) exited]
[Thread 0x7fffe2647640 (LWP 111603) exited]
[Thread 0x7fffb3fff640 (LWP 111605) exited]
[Thread 0x7fffe2ef5640 (LWP 111593) exited]
[New Thread 0x7fffe2ef5640 (LWP 111606)]
[New Thread 0x7fffb3fff640 (LWP 111607)]
[Thread 0x7fffe2ef5640 (LWP 111606) exited]
[New Thread 0x7fffe2ef5640 (LWP 111608)]
[New Thread 0x7fffe9121640 (LWP 111609)]
[Thread 0x7fffb3fff640 (LWP 111607) exited]
[Thread 0x7fffe2ef5640 (LWP 111608) exited]
[Thread 0x7fffe9121640 (LWP 111609) exited]
[New Thread 0x7fffe9121640 (LWP 111610)]
[New Thread 0x7fffe2ef5640 (LWP 111611)]
[Thread 0x7fffe9121640 (LWP 111610) exited]
[Thread 0x7fffe2ef5640 (LWP 111611) exited]
[New Thread 0x7fffe2ef5640 (LWP 111612)]
[New Thread 0x7fffe9121640 (LWP 111613)]
[Thread 0x7fffe2ef5640 (LWP 111612) exited]
[Thread 0x7fffe9121640 (LWP 111613) exited]
[New Thread 0x7fffe0f85a00 (LWP 111614)]
[New Thread 0x7fffe0f79a00 (LWP 111615)]
[New Thread 0x7fffe0f6da00 (LWP 111616)]
[New Thread 0x7fffe0f62640 (LWP 111617)]
[New Thread 0x7fffe0ee1640 (LWP 111618)]
[New Thread 0x7fffe0e60640 (LWP 111619)]
[New Thread 0x7fffe9121640 (LWP 111620)]
[New Thread 0x7fffe2ef5640 (LWP 111621)]
[Thread 0x7fffe9121640 (LWP 111620) exited]
[New Thread 0x7fffe9121640 (LWP 111622)]
[New Thread 0x7fffb3fff640 (LWP 111623)]
[Thread 0x7fffe2ef5640 (LWP 111621) exited]
[Thread 0x7fffe9121640 (LWP 111622) exited]
[New Thread 0x7fffe9121640 (LWP 111624)]
[New Thread 0x7fffe2ef5640 (LWP 111625)]
[Thread 0x7fffb3fff640 (LWP 111623) exited]
[Thread 0x7fffe9121640 (LWP 111624) exited]
[New Thread 0x7fffe9121640 (LWP 111626)]
[New Thread 0x7fffb3fff640 (LWP 111627)]
[Thread 0x7fffe2ef5640 (LWP 111625) exited]
[Thread 0x7fffe9121640 (LWP 111626) exited]
[Thread 0x7fffb3fff640 (LWP 111627) exited]
[New Thread 0x7fffb2c74640 (LWP 111628)]
[New Thread 0x7fffb3fff640 (LWP 111629)]
[New Thread 0x7fffe9121640 (LWP 111630)]
ALSA lib pcm_dsnoop.c:601:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dmix.c:1032:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.hdmi.0:CARD=0,AES0=4,AES1=130,AES2=0,AES3=2'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM hdmi
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.hdmi.0:CARD=0,AES0=4,AES1=130,AES2=0,AES3=2'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM hdmi
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline:CARD=0,DEV=0
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline:CARD=0,DEV=0
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM phoneline
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM phoneline
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
ALSA lib pcm_dmix.c:1032:(snd_pcm_dmix_open) unable to open slave
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
[New Thread 0x7fffa559f640 (LWP 111631)]
[New Thread 0x7fffa551e640 (LWP 111632)]
[Thread 0x7fffa551e640 (LWP 111632) exited]
[Thread 0x7fffa559f640 (LWP 111631) exited]
ALSA lib pcm_dsnoop.c:601:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dmix.c:1032:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.hdmi.0:CARD=0,AES0=4,AES1=130,AES2=0,AES3=2'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM hdmi
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.hdmi.0:CARD=0,AES0=4,AES1=130,AES2=0,AES3=2'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM hdmi
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline:CARD=0,DEV=0
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline:CARD=0,DEV=0
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM phoneline
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM phoneline
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
ALSA lib pcm_dmix.c:1032:(snd_pcm_dmix_open) unable to open slave
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
[New Thread 0x7fffa559f640 (LWP 111633)]
[New Thread 0x7fffa551e640 (LWP 111634)]
[Thread 0x7fffa551e640 (LWP 111634) exited]
[Thread 0x7fffa559f640 (LWP 111633) exited]
Creating a blank synth
ALSA lib pcm_dsnoop.c:601:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dmix.c:1032:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.hdmi.0:CARD=0,AES0=4,AES1=130,AES2=0,AES3=2'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM hdmi
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.hdmi.0:CARD=0,AES0=4,AES1=130,AES2=0,AES3=2'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM hdmi
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline:CARD=0,DEV=0
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline:CARD=0,DEV=0
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM phoneline
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM phoneline
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
ALSA lib pcm_dmix.c:1032:(snd_pcm_dmix_open) unable to open slave
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
[New Thread 0x7fffa559f640 (LWP 111635)]
[New Thread 0x7fffa551e640 (LWP 111636)]
[Thread 0x7fffa551e640 (LWP 111636) exited]
[Thread 0x7fffa559f640 (LWP 111635) exited]
Calling configure on soundfont
Loading /home/rpatros/Music/SoundFonts2/SF2/25-piano-sf/25 Piano Soundfonts/Motif ES6 Concert Piano.SF2
ALSA lib pcm_dsnoop.c:601:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dmix.c:1032:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.hdmi.0:CARD=0,AES0=4,AES1=130,AES2=0,AES3=2'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM hdmi
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.hdmi.0:CARD=0,AES0=4,AES1=130,AES2=0,AES3=2'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM hdmi
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline:CARD=0,DEV=0
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline:CARD=0,DEV=0
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM phoneline
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM phoneline
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
ALSA lib pcm_dmix.c:1032:(snd_pcm_dmix_open) unable to open slave
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
[New Thread 0x7fffa559f640 (LWP 111637)]
[New Thread 0x7fffa551e640 (LWP 111638)]
[Thread 0x7fffa551e640 (LWP 111638) exited]
[Thread 0x7fffa559f640 (LWP 111637) exited]
[New Thread 0x7fffe2ef5640 (LWP 111639)]
[New Thread 0x7fffe2647640 (LWP 111640)]
[New Thread 0x7fff87fff640 (LWP 111641)]
fluidsynth: warning: No preset found on channel 9 [bank=128 prog=0]
sid=1
Calling configure on preset_key_set
Calling configure on preset_key_set2
Calling configure on preset_key_set3
Calling configure on preset_key_set4
Calling configure on preset_key_set5
Calling configure on preset_key_set6
Calling configure on preset_key_set7
Calling configure on preset_key_set8
Calling configure on preset_key_set9
Calling configure on preset_key_set10
Calling configure on preset_key_set11
Calling configure on preset_key_set12
Calling configure on preset_key_set13
Calling configure on preset_key_set14
Calling configure on preset_key_set15
Calling configure on preset_key_set16
[New Thread 0x7fff85105640 (LWP 111642)]
[New Thread 0x7fff84904640 (LWP 111643)]
fluidsynth: warning: Instrument not found on channel 0 [bank=0 prog=14], substituted [bank=0 prog=0]
[New Thread 0x7fff73fff640 (LWP 111644)]
[New Thread 0x7fff73745640 (LWP 111645)]
[New Thread 0x7fff72f44640 (LWP 111646)]
[Thread 0x7fff73745640 (LWP 111645) exited]
[Thread 0x7fff72f44640 (LWP 111646) exited]
Reading player:ACE Fluid Synth took 5006 microseconds, final size = 9662
[New Thread 0x7fff72f44640 (LWP 111647)]
[New Thread 0x7fff73745640 (LWP 111648)]
[Thread 0x7fff72f44640 (LWP 111647) exited]
[Thread 0x7fff73745640 (LWP 111648) exited]
[New Thread 0x7fff73745640 (LWP 111649)]
[New Thread 0x7fff72f44640 (LWP 111650)]
[Thread 0x7fff73745640 (LWP 111649) exited]
[New Thread 0x7fff73745640 (LWP 111651)]
[New Thread 0x7fff72743640 (LWP 111652)]
[Thread 0x7fff72f44640 (LWP 111650) exited]
[Thread 0x7fff73745640 (LWP 111651) exited]
[New Thread 0x7fff73745640 (LWP 111653)]
[Thread 0x7fff72743640 (LWP 111652) exited]
[New Thread 0x7fff72743640 (LWP 111654)]
[Thread 0x7fff73745640 (LWP 111653) exited]
[New Thread 0x7fff73745640 (LWP 111655)]
[New Thread 0x7fff72f44640 (LWP 111656)]
[Thread 0x7fff73745640 (LWP 111655) exited]
[Thread 0x7fff72743640 (LWP 111654) exited]
[Thread 0x7fff72f44640 (LWP 111656) exited]
[New Thread 0x7fff72f44640 (LWP 111657)]
[New Thread 0x7fff72743640 (LWP 111658)]
[Thread 0x7fff72f44640 (LWP 111657) exited]
[New Thread 0x7fff72f44640 (LWP 111659)]
[New Thread 0x7fff73745640 (LWP 111660)]
[Thread 0x7fff72f44640 (LWP 111659) exited]
[Thread 0x7fff72743640 (LWP 111658) exited]
[Thread 0x7fff73745640 (LWP 111660) exited]
[New Thread 0x7fff73745640 (LWP 111661)]
[New Thread 0x7fff72743640 (LWP 111662)]
[New Thread 0x7fff72f44640 (LWP 111663)]
[Thread 0x7fffe1e46640 (LWP 111585) exited]
CALF DEBUG: instance 0x55555c3f3610 data 0x55555bc56ef8
CALF DEBUG: calf 0x7fffb12e6630 cpi 0x7fffb0aebd60
CALF DEBUG: instance 0x55555b73d400 data 0x55555905db58
CALF DEBUG: calf 0x7fffb12e6630 cpi 0x7fffb0aebd60
CALF DEBUG: instance 0x5555595d8320 data 0x555558eac428
CALF DEBUG: calf 0x7fffb12e6690 cpi 0x7fffb0aebbb0
[New Thread 0x7fffe1e46640 (LWP 111685)]
[New Thread 0x7fff71a8a640 (LWP 111686)]
[Thread 0x7fffe1e46640 (LWP 111685) exited]
[New Thread 0x7fffe1e46640 (LWP 111687)]
[New Thread 0x7fff71289640 (LWP 111688)]
[Thread 0x7fff71a8a640 (LWP 111686) exited]
[Thread 0x7fffe1e46640 (LWP 111687) exited]
[New Thread 0x7fffe1e46640 (LWP 111689)]
[New Thread 0x7fff71a8a640 (LWP 111690)]
[Thread 0x7fff71289640 (LWP 111688) exited]
[Thread 0x7fffe1e46640 (LWP 111689) exited]
[New Thread 0x7fffe1e46640 (LWP 111691)]
[New Thread 0x7fff71289640 (LWP 111692)]
[Thread 0x7fff71a8a640 (LWP 111690) exited]
[Thread 0x7fffe1e46640 (LWP 111691) exited]
[New Thread 0x7fffe1e46640 (LWP 111693)]
[New Thread 0x7fff71a8a640 (LWP 111694)]
[Thread 0x7fffe1e46640 (LWP 111693) exited]
[Thread 0x7fff71289640 (LWP 111692) exited]
[Thread 0x7fff71a8a640 (LWP 111694) exited]
[New Thread 0x7fff71a8a640 (LWP 111695)]
[New Thread 0x7fffe1e46640 (LWP 111696)]
[New Thread 0x7fff71289640 (LWP 111697)]
[New Thread 0x7fff4f430640 (LWP 111698)]
[Thread 0x7fff71289640 (LWP 111697) exited]
[New Thread 0x7fff71289640 (LWP 111699)]
[New Thread 0x7fff4ec2f640 (LWP 111700)]
[Thread 0x7fff4f430640 (LWP 111698) exited]
[Thread 0x7fff71289640 (LWP 111699) exited]
[Thread 0x7fff4ec2f640 (LWP 111700) exited]
[New Thread 0x7fff4ec2f640 (LWP 111701)]
[New Thread 0x7fff71289640 (LWP 111702)]
[Thread 0x7fff4ec2f640 (LWP 111701) exited]
[Thread 0x7fff71289640 (LWP 111702) exited]
[Thread 0x7fffe1e46640 (LWP 111696) exited]
[Thread 0x7fff71a8a640 (LWP 111695) exited]
[New Thread 0x7fff71a8a640 (LWP 111712)]
[New Thread 0x7fffe1e46640 (LWP 111713)]
[Thread 0x7fff71a8a640 (LWP 111712) exited]
[New Thread 0x7fff71a8a640 (LWP 111714)]
[New Thread 0x7fff71289640 (LWP 111715)]
[Thread 0x7fffe1e46640 (LWP 111713) exited]
[Thread 0x7fff71a8a640 (LWP 111714) exited]
[Thread 0x7fff71289640 (LWP 111715) exited]
[Thread 0x7fff84904640 (LWP 111643) exited]
Butler drops pool trash
[Thread 0x7fffb2c74640 (LWP 111628) exited]
[Thread 0x7fffe0e60640 (LWP 111619) exited]
[Thread 0x7fffe0ee1640 (LWP 111618) exited]
[Thread 0x7fffe0f62640 (LWP 111617) exited]
[Thread 0x7fff72f44640 (LWP 111663) exited]
[Thread 0x7fff72743640 (LWP 111662) exited]
[Thread 0x7fff73745640 (LWP 111661) exited]
[Thread 0x7fff73fff640 (LWP 111644) exited]
[Thread 0x7fff85105640 (LWP 111642) exited]
[Thread 0x7fffb3fff640 (LWP 111629) exited]
[Thread 0x7fffe0f6da00 (LWP 111616) exited]
[Thread 0x7fffe0f79a00 (LWP 111615) exited]
[Thread 0x7fffe0f85a00 (LWP 111614) exited]
[Thread 0x7fffe9121640 (LWP 111630) exited]
[Thread 0x7fff87fff640 (LWP 111641) exited]
[Thread 0x7fffe2647640 (LWP 111640) exited]
[Thread 0x7fffe13c5640 (LWP 111592) exited]
[Thread 0x7fffe1446640 (LWP 111591) exited]
[Thread 0x7fffe1645640 (LWP 111590) exited]
[Thread 0x7fffe36f6640 (LWP 111554) exited]
[Thread 0x7fffe8920640 (LWP 111553) exited]
[Thread 0x7fffea2a9640 (LWP 111546) exited]
[Thread 0x7fffe2ef5640 (LWP 111639) exited]
[Thread 0x7fffeaffd640 (LWP 111545) exited]
[Thread 0x7fffeb7fe640 (LWP 111543) exited]
[Thread 0x7fffe3fff640 (LWP 111542) exited]
[Thread 0x7fffebfff640 (LWP 111541) exited]
[Thread 0x7ffff106ea00 (LWP 111537) exited]
[Thread 0x7ffff0afe640 (LWP 111540) exited]
[New process 111537]

Program terminated with signal SIGKILL, Killed.
The program no longer exists.
(gdb)
System Description
Attached Files: ardour_error.png (182,535 bytes) 2022-05-29 17:34
https://tracker.ardour.org/file_download.php?file_id=4191&type=bug
gdb.zip (4,159 bytes) 2022-05-30 15:28
https://tracker.ardour.org/file_download.php?file_id=4192&type=bug
Notes
(0026463)
rpatros   
2022-05-29 17:34   
Here is the error received
(0026464)
x42   
2022-05-29 17:39   
```
Program terminated with signal SIGKILL, Killed.
The program no longer exists.
(gdb)
```

How was this killed?

Can you instead get a backtrace from when Ardour hangs, as described at https://discourse.ardour.org/t/ardour-hanging-at-shutdown/107260/11
Thanks
(0026465)
rpatros   
2022-05-29 18:08   
Hello x42,

Thank you for the quick reply, here is the bt:


[rpatros@patros-pc tmp]$ ardour6 --gdb
GNU gdb (GDB) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/ardour6/ardour-6.9.0...
(No debugging symbols found in /usr/lib/ardour6/ardour-6.9.0)
(gdb) run
Starting program: /usr/lib/ardour6/ardour-6.9.0
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Ardour6.9.0 (built using 6.9 and GCC version 11.2.0)
Ardour: [INFO]: Your system is configured to limit Ardour to 524288 open files
Ardour: [INFO]: Loading system configuration file /etc/ardour6/system_config
Ardour: [INFO]: Loading user configuration file /home/rpatros/.config/ardour6/config
[New Thread 0x7ffff0afe640 (LWP 119202)]
Ardour: [INFO]: CPU vendor: GenuineIntel
Ardour: [INFO]: AVX-capable processor
Ardour: [INFO]: CPU brand: Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz
Ardour: [INFO]: Using AVX optimized routines
[New Thread 0x7fffebfff640 (LWP 119203)]
[New Thread 0x7fffeb7fe640 (LWP 119204)]
[New Thread 0x7fffeaffd640 (LWP 119205)]
Ardour: [INFO]: Loading plugin meta data file /usr/share/ardour6/plugin_metadata/plugin_tags
Ardour: [INFO]: Loading plugin statistics file /home/rpatros/.config/ardour6/plugin_metadata/plugin_stats
[New Thread 0x7fffea7fc640 (LWP 119206)]
[Thread 0x7fffea7fc640 (LWP 119206) exited]
[New Thread 0x7fffea7fc640 (LWP 119207)]
[New Thread 0x7fffe9aa8640 (LWP 119208)]
[New Thread 0x7fffe9192640 (LWP 119209)]
Ardour: [INFO]: Loading default ui configuration file /etc/ardour6/default_ui_config
Ardour: [INFO]: Loading user ui configuration file /home/rpatros/.config/ardour6/ui_config
Ardour: [INFO]: Loading 452 MIDI patches from /usr/share/ardour6/patchfiles
[New Thread 0x7fffe8920640 (LWP 119210)]
[Thread 0x7fffe8920640 (LWP 119210) exited]
[New Thread 0x7fffe8920640 (LWP 119211)]
[New Thread 0x7fffcbfff640 (LWP 119212)]
[Thread 0x7fffe8920640 (LWP 119211) exited]
[New Thread 0x7fffe8920640 (LWP 119213)]
[New Thread 0x7fffcb6f6640 (LWP 119214)]
[Thread 0x7fffe8920640 (LWP 119213) exited]
[Thread 0x7fffcb6f6640 (LWP 119214) exited]
[Thread 0x7fffcbfff640 (LWP 119212) exited]
[New Thread 0x7fffcbfff640 (LWP 119215)]
[New Thread 0x7fffcb6f6640 (LWP 119216)]
[New Thread 0x7fffe8920640 (LWP 119217)]
[New Thread 0x7fffcadd2640 (LWP 119218)]
[Thread 0x7fffcadd2640 (LWP 119218) exited]
[New Thread 0x7fffcadd2640 (LWP 119219)]
Ardour: [INFO]: Loading color file /usr/share/ardour6/themes/dark-ardour.colors
[Thread 0x7fffcadd2640 (LWP 119219) exited]
Ardour: [INFO]: Loading ui configuration file /etc/ardour6/clearlooks.rc
[New Thread 0x7fffcadd2640 (LWP 119220)]
[New Thread 0x7fffca5d1640 (LWP 119221)]
[Thread 0x7fffcadd2640 (LWP 119220) exited]
[New Thread 0x7fffcadd2640 (LWP 119222)]
[New Thread 0x7fffc9dd0640 (LWP 119223)]
[Thread 0x7fffcadd2640 (LWP 119222) exited]
[New Thread 0x7fffcadd2640 (LWP 119224)]
[New Thread 0x7fffc95cf640 (LWP 119225)]
[Thread 0x7fffca5d1640 (LWP 119221) exited]
[Thread 0x7fffcadd2640 (LWP 119224) exited]
[New Thread 0x7fffcadd2640 (LWP 119226)]
[New Thread 0x7fffca5d1640 (LWP 119227)]
[Thread 0x7fffc9dd0640 (LWP 119223) exited]
[Thread 0x7fffcadd2640 (LWP 119226) exited]
Ardour: [INFO]: Loading bindings from /etc/ardour6/ardour.keys
Loading ui configuration file /etc/ardour6/clearlooks.rc
[Thread 0x7fffc95cf640 (LWP 119225) exited]
[New Thread 0x7fffc95cf640 (LWP 119228)]
[New Thread 0x7fffcadd2640 (LWP 119229)]
[Thread 0x7fffca5d1640 (LWP 119227) exited]
[Thread 0x7fffc95cf640 (LWP 119228) exited]
[New Thread 0x7fffc95cf640 (LWP 119230)]
[New Thread 0x7fffca5d1640 (LWP 119231)]
[Thread 0x7fffcadd2640 (LWP 119229) exited]
[Thread 0x7fffc95cf640 (LWP 119230) exited]
[New Thread 0x7fffc95cf640 (LWP 119232)]
[New Thread 0x7fffcadd2640 (LWP 119233)]
[Thread 0x7fffca5d1640 (LWP 119231) exited]
[Thread 0x7fffc95cf640 (LWP 119232) exited]
[Thread 0x7fffcadd2640 (LWP 119233) exited]
[New Thread 0x7fffc8dce640 (LWP 119234)]
[New Thread 0x7fffc8c09640 (LWP 119235)]
[Thread 0x7fffc8c09640 (LWP 119235) exited]
[Thread 0x7fffc8dce640 (LWP 119234) exited]
[New Thread 0x7fffc8dce640 (LWP 119236)]
[New Thread 0x7fffc8c09640 (LWP 119237)]
[Thread 0x7fffc8c09640 (LWP 119237) exited]
[Thread 0x7fffc8dce640 (LWP 119236) exited]
[New Thread 0x7fffcadd2640 (LWP 119238)]
[New Thread 0x7fffc95cf640 (LWP 119239)]
[Thread 0x7fffcadd2640 (LWP 119238) exited]
[New Thread 0x7fffcadd2640 (LWP 119240)]
[New Thread 0x7fffca5d1640 (LWP 119241)]
[Thread 0x7fffcadd2640 (LWP 119240) exited]
[Thread 0x7fffc95cf640 (LWP 119239) exited]
[New Thread 0x7fffc95cf640 (LWP 119242)]
[New Thread 0x7fffcadd2640 (LWP 119243)]
[Thread 0x7fffca5d1640 (LWP 119241) exited]
[Thread 0x7fffc95cf640 (LWP 119242) exited]
[New Thread 0x7fffc95cf640 (LWP 119244)]
[New Thread 0x7fffca5d1640 (LWP 119245)]
[Thread 0x7fffc95cf640 (LWP 119244) exited]
[Thread 0x7fffcadd2640 (LWP 119243) exited]
[Thread 0x7fffca5d1640 (LWP 119245) exited]
[New Thread 0x7fffca5d1640 (LWP 119246)]
[New Thread 0x7fffcadd2640 (LWP 119247)]
[New Thread 0x7fffc95cf640 (LWP 119248)]
[New Thread 0x7fffc9dd0640 (LWP 119249)]
[Thread 0x7fffc95cf640 (LWP 119248) exited]
[New Thread 0x7fffc95cf640 (LWP 119250)]
[New Thread 0x7fffb3fff640 (LWP 119251)]
[Thread 0x7fffc95cf640 (LWP 119250) exited]
[Thread 0x7fffc9dd0640 (LWP 119249) exited]
[Thread 0x7fffb3fff640 (LWP 119251) exited]
[Thread 0x7fffe8920640 (LWP 119217) exited]
[Thread 0x7fffca5d1640 (LWP 119246) exited]
[Thread 0x7fffe9192640 (LWP 119209) exited]
[New Thread 0x7fffc95cf640 (LWP 119252)]
[New Thread 0x7fffc93d0640 (LWP 119253)]
[New Thread 0x7fffc934f640 (LWP 119254)]
Scanning folders for bundled LV2s: /usr/lib/ardour6/LV2
[New Thread 0x7fffca5d1640 (LWP 119255)]
[New Thread 0x7fffe8920640 (LWP 119256)]
[New Thread 0x7fffb3fff640 (LWP 119257)]
[Thread 0x7fffe8920640 (LWP 119256) exited]
[Thread 0x7fffb3fff640 (LWP 119257) exited]
Set cursor set to default
[New Thread 0x7fffb3fff640 (LWP 119258)]
[New Thread 0x7fffe8920640 (LWP 119259)]
[Thread 0x7fffb3fff640 (LWP 119258) exited]
[New Thread 0x7fffb3fff640 (LWP 119260)]
[New Thread 0x7fffc9dd0640 (LWP 119261)]
[Thread 0x7fffb3fff640 (LWP 119260) exited]
[Thread 0x7fffe8920640 (LWP 119259) exited]
[Thread 0x7fffc9dd0640 (LWP 119261) exited]
[New Thread 0x7fffc9dd0640 (LWP 119262)]
[New Thread 0x7fffe8920640 (LWP 119263)]
[Thread 0x7fffc9dd0640 (LWP 119262) exited]
[Thread 0x7fffe8920640 (LWP 119263) exited]
[New Thread 0x7fffe8920640 (LWP 119264)]
[New Thread 0x7fffc9dd0640 (LWP 119265)]
[Thread 0x7fffe8920640 (LWP 119264) exited]
[New Thread 0x7fffe8920640 (LWP 119266)]
[New Thread 0x7fffb3fff640 (LWP 119267)]
[Thread 0x7fffc9dd0640 (LWP 119265) exited]
[Thread 0x7fffe8920640 (LWP 119266) exited]
[Thread 0x7fffb3fff640 (LWP 119267) exited]
[Thread 0x7fffcadd2640 (LWP 119247) exited]
[New Thread 0x7fffcadd2640 (LWP 119268)]
[New Thread 0x7fffb3fff640 (LWP 119269)]
[Thread 0x7fffcadd2640 (LWP 119268) exited]
[New Thread 0x7fffcadd2640 (LWP 119270)]
[New Thread 0x7fffe8920640 (LWP 119271)]
[Thread 0x7fffcadd2640 (LWP 119270) exited]
[Thread 0x7fffb3fff640 (LWP 119269) exited]
[New Thread 0x7fffb3fff640 (LWP 119272)]
[New Thread 0x7fffcadd2640 (LWP 119273)]
[Thread 0x7fffe8920640 (LWP 119271) exited]
[Thread 0x7fffb3fff640 (LWP 119272) exited]
[Thread 0x7fffcadd2640 (LWP 119273) exited]
[New Thread 0x7fffcadd2640 (LWP 119274)]
[New Thread 0x7fffb3fff640 (LWP 119275)]
[Thread 0x7fffcadd2640 (LWP 119274) exited]
[Thread 0x7fffb3fff640 (LWP 119275) exited]
[New Thread 0x7fffc8f2ca00 (LWP 119276)]
[New Thread 0x7fffc8f20a00 (LWP 119277)]
[New Thread 0x7fffc8f14a00 (LWP 119278)]
[New Thread 0x7fffc8f09640 (LWP 119279)]
[New Thread 0x7fffc8e88640 (LWP 119280)]
[New Thread 0x7fffc8e07640 (LWP 119281)]
[New Thread 0x7fffb3fff640 (LWP 119282)]
[New Thread 0x7fffcadd2640 (LWP 119283)]
[Thread 0x7fffb3fff640 (LWP 119282) exited]
[New Thread 0x7fffb3fff640 (LWP 119284)]
[New Thread 0x7fffe8920640 (LWP 119285)]
[Thread 0x7fffcadd2640 (LWP 119283) exited]
[New Thread 0x7fffb3fff640 (LWP 119286)]
[Thread 0x7fffb3fff640 (LWP 119284) exited]
[New Thread 0x7fffcadd2640 (LWP 119287)]
[Thread 0x7fffe8920640 (LWP 119285) exited]
[Thread 0x7fffb3fff640 (LWP 119286) exited]
[New Thread 0x7fffb3fff640 (LWP 119288)]
[New Thread 0x7fffe8920640 (LWP 119289)]
[Thread 0x7fffcadd2640 (LWP 119287) exited]
[Thread 0x7fffb3fff640 (LWP 119288) exited]
[Thread 0x7fffe8920640 (LWP 119289) exited]
[New Thread 0x7fffb2d75640 (LWP 119290)]
[New Thread 0x7fffe8920640 (LWP 119291)]
[WRN] Found standard VST 2.x chunk header (bank)
[New Thread 0x7fffb3fff640 (LWP 119292)]
ALSA lib pcm_dsnoop.c:601:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dmix.c:1032:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.hdmi.0:CARD=0,AES0=4,AES1=130,AES2=0,AES3=2'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM hdmi
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.hdmi.0:CARD=0,AES0=4,AES1=130,AES2=0,AES3=2'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM hdmi
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline:CARD=0,DEV=0
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline:CARD=0,DEV=0
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM phoneline
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM phoneline
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
ALSA lib pcm_dmix.c:1032:(snd_pcm_dmix_open) unable to open slave
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
[New Thread 0x7fffa1040640 (LWP 119293)]
[New Thread 0x7fffa0fbf640 (LWP 119294)]
[Thread 0x7fffa0fbf640 (LWP 119294) exited]
[Thread 0x7fffa1040640 (LWP 119293) exited]
ALSA lib pcm_dsnoop.c:601:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dmix.c:1032:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.hdmi.0:CARD=0,AES0=4,AES1=130,AES2=0,AES3=2'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM hdmi
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.hdmi.0:CARD=0,AES0=4,AES1=130,AES2=0,AES3=2'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM hdmi
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline:CARD=0,DEV=0
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline:CARD=0,DEV=0
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM phoneline
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM phoneline
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
ALSA lib pcm_dmix.c:1032:(snd_pcm_dmix_open) unable to open slave
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
[New Thread 0x7fffa1040640 (LWP 119295)]
[New Thread 0x7fffa0fbf640 (LWP 119296)]
[Thread 0x7fffa0fbf640 (LWP 119296) exited]
[Thread 0x7fffa1040640 (LWP 119295) exited]
Creating a blank synth
ALSA lib pcm_dsnoop.c:601:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dmix.c:1032:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.hdmi.0:CARD=0,AES0=4,AES1=130,AES2=0,AES3=2'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM hdmi
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.hdmi.0:CARD=0,AES0=4,AES1=130,AES2=0,AES3=2'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM hdmi
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline:CARD=0,DEV=0
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline:CARD=0,DEV=0
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM phoneline
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM phoneline
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
ALSA lib pcm_dmix.c:1032:(snd_pcm_dmix_open) unable to open slave
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
[New Thread 0x7fffa1040640 (LWP 119297)]
[New Thread 0x7fffa0fbf640 (LWP 119298)]
[Thread 0x7fffa0fbf640 (LWP 119298) exited]
[Thread 0x7fffa1040640 (LWP 119297) exited]
Calling configure on soundfont
Loading /home/rpatros/Music/SoundFonts2/SF2/25-piano-sf/25 Piano Soundfonts/Motif ES6 Concert Piano.SF2
ALSA lib pcm_dsnoop.c:601:(snd_pcm_dsnoop_open) unable to open slave
ALSA lib pcm_dmix.c:1032:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.hdmi.0:CARD=0,AES0=4,AES1=130,AES2=0,AES3=2'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM hdmi
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.hdmi.0:CARD=0,AES0=4,AES1=130,AES2=0,AES3=2'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM hdmi
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline:CARD=0,DEV=0
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline:CARD=0,DEV=0
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM phoneline
ALSA lib confmisc.c:1369:(snd_func_refer) Unable to find definition 'cards.0.pcm.modem.0:CARD=0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM phoneline
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
ALSA lib pcm_dmix.c:1032:(snd_pcm_dmix_open) unable to open slave
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library libasound_module_pcm_pulse.so (/usr/lib/alsa-lib/libasound_module_pcm_pulse.so: cannot open shared object file: No such file or directory)
[New Thread 0x7fffa1040640 (LWP 119299)]
[New Thread 0x7fffa0fbf640 (LWP 119300)]
[Thread 0x7fffa0fbf640 (LWP 119300) exited]
[Thread 0x7fffa1040640 (LWP 119299) exited]
[New Thread 0x7fffcadd2640 (LWP 119301)]
[New Thread 0x7fffc9dd0640 (LWP 119302)]
[New Thread 0x7fff83fff640 (LWP 119303)]
fluidsynth: warning: No preset found on channel 9 [bank=128 prog=0]
sid=1
Calling configure on preset_key_set
Calling configure on preset_key_set2
Calling configure on preset_key_set3
Calling configure on preset_key_set4
Calling configure on preset_key_set5
Calling configure on preset_key_set6
Calling configure on preset_key_set7
Calling configure on preset_key_set8
Calling configure on preset_key_set9
Calling configure on preset_key_set10
Calling configure on preset_key_set11
Calling configure on preset_key_set12
Calling configure on preset_key_set13
Calling configure on preset_key_set14
Calling configure on preset_key_set15
Calling configure on preset_key_set16
[New Thread 0x7fff837fe640 (LWP 119304)]
[New Thread 0x7fff82ffd640 (LWP 119305)]
[New Thread 0x7fff827fc640 (LWP 119306)]
[New Thread 0x7fff81ffb640 (LWP 119307)]
[New Thread 0x7fff817fa640 (LWP 119308)]
fluidsynth: warning: Instrument not found on channel 0 [bank=0 prog=14], substituted [bank=0 prog=0]
[Thread 0x7fff81ffb640 (LWP 119307) exited]
restarting Session::update_latency. # of send changes: 8 iteration: 1
[Thread 0x7fff817fa640 (LWP 119308) exited]
Reading player:ACE Fluid Synth took 5869 microseconds, final size = 9662
[New Thread 0x7fff817fa640 (LWP 119309)]
[New Thread 0x7fff81ffb640 (LWP 119310)]
[Thread 0x7fff817fa640 (LWP 119309) exited]
[Thread 0x7fff81ffb640 (LWP 119310) exited]
[New Thread 0x7fff81ffb640 (LWP 119311)]
[New Thread 0x7fff817fa640 (LWP 119312)]
[Thread 0x7fff81ffb640 (LWP 119311) exited]
[New Thread 0x7fff81ffb640 (LWP 119313)]
[New Thread 0x7fff80ff9640 (LWP 119314)]
[Thread 0x7fff81ffb640 (LWP 119313) exited]
[Thread 0x7fff817fa640 (LWP 119312) exited]
[New Thread 0x7fff817fa640 (LWP 119315)]
[New Thread 0x7fff81ffb640 (LWP 119316)]
[Thread 0x7fff817fa640 (LWP 119315) exited]
[Thread 0x7fff80ff9640 (LWP 119314) exited]
[New Thread 0x7fff80ff9640 (LWP 119317)]
[New Thread 0x7fff817fa640 (LWP 119318)]
[Thread 0x7fff80ff9640 (LWP 119317) exited]
[Thread 0x7fff81ffb640 (LWP 119316) exited]
[Thread 0x7fff817fa640 (LWP 119318) exited]
[New Thread 0x7fff817fa640 (LWP 119319)]
[New Thread 0x7fff81ffb640 (LWP 119320)]
[Thread 0x7fff817fa640 (LWP 119319) exited]
[New Thread 0x7fff817fa640 (LWP 119321)]
[New Thread 0x7fff80ff9640 (LWP 119322)]
[Thread 0x7fff81ffb640 (LWP 119320) exited]
[Thread 0x7fff817fa640 (LWP 119321) exited]
[Thread 0x7fff80ff9640 (LWP 119322) exited]
[New Thread 0x7fff80ff9640 (LWP 119323)]
[New Thread 0x7fff817fa640 (LWP 119324)]
[New Thread 0x7fff81ffb640 (LWP 119325)]
[New Thread 0x7fff63fff640 (LWP 119327)]
[New Thread 0x7fff637fe640 (LWP 119328)]
[Thread 0x7fff63fff640 (LWP 119327) exited]
[New Thread 0x7fff63fff640 (LWP 119329)]
[New Thread 0x7fff62ffd640 (LWP 119330)]
[Thread 0x7fff637fe640 (LWP 119328) exited]
[Thread 0x7fff63fff640 (LWP 119329) exited]
[Thread 0x7fff62ffd640 (LWP 119330) exited]
[Thread 0x7fffca5d1640 (LWP 119255) exited]
[Thread 0x7fff82ffd640 (LWP 119305) exited]
Butler drops pool trash
[Thread 0x7fffb2d75640 (LWP 119290) exited]
[Thread 0x7fff827fc640 (LWP 119306) exited]
[Thread 0x7fffc8e07640 (LWP 119281) exited]
[Thread 0x7fffc8e88640 (LWP 119280) exited]
[Thread 0x7fffc8f09640 (LWP 119279) exited]
[Thread 0x7fff81ffb640 (LWP 119325) exited]
[Thread 0x7fff817fa640 (LWP 119324) exited]
[Thread 0x7fff80ff9640 (LWP 119323) exited]
[Thread 0x7fff837fe640 (LWP 119304) exited]
[Thread 0x7fffe8920640 (LWP 119291) exited]
[Thread 0x7fffc8f14a00 (LWP 119278) exited]
[Thread 0x7fffc8f20a00 (LWP 119277) exited]
[Thread 0x7fffc8f2ca00 (LWP 119276) exited]
[Thread 0x7fffb3fff640 (LWP 119292) exited]
^C
Thread 1 "ArdourGUI" received signal SIGINT, Interrupt.
0x00007ffff571a119 in ?? () from /usr/lib/libc.so.6
(gdb) bt
#0 0x00007ffff571a119 in () at /usr/lib/libc.so.6
0000001 0x00007ffff571f113 in () at /usr/lib/libc.so.6
#2 0x00007ffff3d18326 in () at /usr/lib/libjack.so.0
#3 0x00007ffff3cf823c in () at /usr/lib/libjack.so.0
0000004 0x00007ffff3cf7149 in () at /usr/lib/libjack.so.0
0000005 0x00007ffff3d1bd75 in jack_client_close () at /usr/lib/libjack.so.0
#6 0x00007fffe91a8e70 in ARDOUR::JackConnection::close() () at /usr/lib/ardour6/backends/libjack_audiobackend.so
#7 0x00007fffe91a923b in ARDOUR::JACKAudioBackend::stop() () at /usr/lib/ardour6/backends/libjack_audiobackend.so
0000008 0x00007ffff77e64ee in ARDOUR::AudioEngine::stop(bool) () at /usr/lib/ardour6/libardour.so.3
0000009 0x00005555559b87f7 in ()
0000010 0x00005555559ee138 in ()
0000011 0x00007ffff70d59e6 in () at /usr/lib/libglibmm-2.4.so.1
0000012 0x00007ffff6f37163 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
0000013 0x00007ffff6f8d9e9 in () at /usr/lib/libglib-2.0.so.0
0000014 0x00007ffff6f366a3 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0
#15 0x00007ffff6bb09fe in gtk_main () at /usr/lib/libgtk-x11-2.0.so.0
0000016 0x00007ffff7251d5d in Gtkmm2ext::UI::run(Receiver&) () at /usr/lib/ardour6/libgtkmm2ext.so.0
#17 0x000055555597b8f3 in main ()
(gdb)
(0026466)
rpatros   
2022-05-29 18:45   
I also want to share that when using ALSA as the backend engine for Ardour, the application can be closed without any issues but with Jack as the backend, I encounter the issue. I am hoping that the backtrace gathered is helpful enough to identify the root cause.
(0026467)
x42   
2022-05-30 13:22   
Thank you. It seems to be an issue with jack. The application hangs calling jack_client_close().

Which version of jack are you using?
(0026468)
x42   
2022-05-30 13:42   
Also do you start jackd before starting Ardour, or does Ardour start jackd for you?
(0026469)
x42   
2022-05-30 14:00   
Since the hang is effectively in libc.so.6 it could also be indirectly caused by a glibc update. Which libc version do you have installed?
(0026470)
Daniele1971   
2022-05-30 15:28   
Here openSUSE TW, glibc-2.35
gdb output generated with ardour-7.pre0.2870-debug, attacched.

Duet to some connection issue, did not dowload the debuinfo packages. Let me know if I have to do it again with debuginfo packages installed.
(0026471)
rpatros   
2022-05-30 15:53   
x42, to answer the questions:

1. Version of Jack is jack2:

[rpatros@patros-pc ~]$ jackd --version
jackdmp version 1.9.21 tmpdir /dev/shm protocol 9

2. Yes I do start jack before starting ardour.

3. The glibc version that I am running is 2.35-5

[rpatros@patros-pc ~]$ sudo pacman -Q | grep glibc
glibc 2.35-5
lib32-glibc 2.35-5

Hope this helps.
(0026472)
rpatros   
2022-05-30 16:12   
x42,

Here is a simple screen sharing that I took yesterday, where you can see that first I started ardour using ALSA and it was able to close the app, then I switch to jack, then attempted to close the app and it hangs:

https://odysee.com/@rpatros:4/Ardour69_bug_upon_closure:d
(0026474)
thomastommySpammer   
2022-05-31 07:18   
good
(0026475)
paul   
2022-05-31 14:21   
confirmed as caused by changes in glibc.
(0026476)
x42   
2022-05-31 18:14   
upstream bug https://sourceware.org/bugzilla/show_bug.cgi?id=29214
libjack is affected by this -- Ardour itself is not.
The glibc release 2.35.0 is not affected, but current git 2.35.xx as currently shipped by some bleeding edge distros has this issue.
(0026477)
x42   
2022-05-31 19:13   
Fix is available upstream at glibc.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8606 [ardour] bugs minor always 2021-03-05 11:38 2022-05-30 18:46
Reporter: gaurangarora Platform: Ubuntu  
Assigned To: x42 OS: Linux  
Priority: normal OS Version: (any)  
Status: resolved Product Version: 6.6  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: 'Consolidate Range with/without Processing' on a FLAC session plays processed clip in silence
Description: When the 'Audio File Format' of a session is set to FLAC, and a 'Consolidate Range with Processing' command is given, the resulting clip plays in silence. But closing the session and relaunching resolves the issue.
Tags:
Steps To Reproduce: 1. Change Session Audio File format to 'FLAC'
2. Select a range in a track with the 'Range Mode' tool
3. Right click on the selected range and select 'Consolidate Range' or 'Consolidate Range with Processing'
4. Playback the newly processed range. No audio is heard.
Additional Information:
System Description
Attached Files:
Notes
(0026024)
gaurangarora   
2021-07-02 19:34   
Bug persists in version 6.8
(0026025)
gaurangarora   
2021-07-02 19:53   
Bug is reproducible on Mac OS version as well.
(0026473)
x42   
2022-05-30 18:46   
Fixed in Ardour 7.0-pre0-2871 ce7d8ed8a1


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
5846 [ardour] features feature N/A 2014-01-30 18:09 2022-05-26 21:55
Reporter: bruno Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.0  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Filter freesound search results by license
Description: The idea is to be able to filter search results in the Freesound tab by type of license (for example, "show me Public Domain files only", "show me CC-BY only", etc).
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0026462)
colinf   
2022-05-26 21:55   
I've had a go at implementing this in eae1673f: scope for improvement still, but at least it's a start...


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
7449 [ardour] bugs minor always 2017-08-16 14:11 2022-05-23 14:14
Reporter: magnetophon Platform: linux  
Assigned To: OS: NixOS  
Priority: normal OS Version: 17.09pre  
Status: new Product Version: 5.10  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: shift click fader in group reverses link behavior
Description: When I shift click on a fader to reset its gain to 0dB, it messes up:
if the group is enabled, the other faders in the group stay where they are, if the group is disabled the gains are linked.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
6493 [ardour] bugs major always 2015-07-31 10:41 2022-05-21 21:03
Reporter: dlp Platform:  
Assigned To: x42 OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 4.X git (version in description)  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Freesound import broken
Description: Common search terms - e.g. drums, loop. techno, etc - return nothing in the Freesound import dialog. Verified on repetition.
Tags:
Steps To Reproduce:
Additional Information: Ardour4.1.446 (built using 4.1-465-g67c75c5 and GCC version 4.8.3 20140911 (Red Hat 4.8.3-7))
Attached Files:
Notes
(0026449)
colinf   
2022-05-20 13:44   
Freesound APIv2 implemented in 9fe0a4f4


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
6197 [ardour] features minor N/A 2015-03-10 00:11 2022-05-20 22:25
Reporter: x42 Platform:  
Assigned To: x42 OS:  
Priority: normal OS Version:  
Status: resolved Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: freesound import needs to be updated to new FS API
Description: just a TODO reminder.. see summary.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: 0001-New-DebugBit-for-Freesound.patch (1,277 bytes) 2016-01-19 12:04
https://tracker.ardour.org/file_download.php?file_id=2851&type=bug
0002-Update-to-Freesound-API-v2-search-only.patch (11,131 bytes) 2016-01-19 12:05
https://tracker.ardour.org/file_download.php?file_id=2852&type=bug
0003-Freesound-abuse-previews-to-get-some-kind-of-downloa.patch (6,032 bytes) 2016-01-19 12:05
https://tracker.ardour.org/file_download.php?file_id=2853&type=bug
0004-Freesound-s-api_key-token-g.patch (3,110 bytes) 2016-01-19 12:05
https://tracker.ardour.org/file_download.php?file_id=2854&type=bug
Notes
(0017809)
colinf   
2016-01-19 01:10   
I have the search part of this nearly working already, but the Freesound APIv2 now requires OAuth in order to download sound files, so we're going to have to provide a means for users to log into their own Freesound accounts in Ardour if they want to download anything.

Not necessarily a big deal, but it is a bit more hassle than I hoped for. On the bright side, once I understand OAuth I can maybe make Soundcloud upload use it as well. Hopefully I'll have time to carry on looking at this soon.
(0017810)
colinf   
2016-01-19 12:02   
For the moment now, I've hacked it to download the high-quality OGG preview when clicking on an item in the search results. That's not ideal, but I reckon is (marginally) better than nothing for the moment
(0017929)
colinf   
2016-02-13 23:14   
Utterly hacky but basically working implementation now pushed to freesound-apiv2 branch.

The concept may well be too ugly to live; even if it's not deemed totally unacceptable there's a lot of tidying still to be done there, but I hope it's at least a starting point.
(0017937)
timbyr   
2016-02-15 12:55   
I pulled and tested the freesound-apiv2 branch and it seems to work OK.

I haven't got any comments about code as yet but one small detail would be to set the focus on the "OK" button in the CredentialsDialog(or whatever you called it) and also that authorization occasionally seems to take some time(I noticed perhaps 15 seconds) so it may be worth having a progress bar.

Perhaps a progress bar could be added to the credentials dialog if that doesn't look too weird as that will also allow access to the Cancel button.

If I input the incorrect username and password there is no indication of failure and it appears that it will just play the last file that successfully downloaded.
(0017942)
colinf   
2016-02-15 13:52   
(Last edited: 2016-02-15 18:10)
timbyr: thanks for testing!

Yes, the CredentialsDialog (can you think of a better name? I almost called it LoginDialog) really ought to have the <Enter> key act as 'OK'. I shall make it so. [EDIT] Done.

A progress bar is a nice idea. I'm not sure that it should be part of the credentials dialogue: I have a feeling it might be a bit weird that 'OK' doesn't dismiss the dialogue immediately, but I suppose if it gave you the chance to re-enter a mistyped user name or password it might make some sense.

And yes, it really ought to report login failures somehow. I'm not sure what the best way to proceed in that case would be either: I had an idea that we could just download the .OGG preview file if the user doesn't provide valid freesound login details, but I'd like to know what others think of that.

(0017943)
timbyr   
2016-02-15 21:21   
(Last edited: 2016-02-15 22:38)
Yes, I agree about the progress bar, it doesn't seem appropriate. Some sort of indication like setting the wait cursor would be good eventually but considering there are other long operations in Ardour that don't do this it probably isn't much of a concern at this point.

(0017976)
colinf   
2016-02-20 13:58   
Login progress now appears (as text) in the file download progress bar: this also allows the user to cancel the login.
(0018003)
timbyr   
2016-02-24 02:18   
I just re-tested the latest changes.

I think the login status in progress bar works well but I still think some sort of dialog or something is needed on failure.

The other main issue I noticed is that double clicking on a file will start it downloading, but it will also play the previously downloaded file immediately which is quite confusing.

How hard would it be to have a "use low quality preview" option? As I think it may provide a faster workflow with the reduced download time. I find myself previewing many files but only importing a few of them into the session.

I'm not sure how that would tie into "only download preview on login failure" but personally I don't think it is a good idea to allow importing of low quality preview files.
(0018009)
colinf   
2016-02-24 14:23   
I agree that we need better login failure reporting: I'm not sure a dialogue is the right thing, because it's quite possible to click 'OK' in the credentials dialogue and then carry on with something else while waiting for the login to complete, so popping up an error dialogue might interrupt that, or alternatively be missed. Would putting an error into the 'Log' window be too obscure?

Good point about the double-click, too: I guess it needs to be handled differently in the freesound list view from the other file lists, since in the other tabs the clicked file is available immediately for preview.

I like the idea of just downloading the preview on clicking the file, and only downloading the original full-quality file on request. The best way I can think of at the moment for this would be be an extra column in the file list with a tick box to mark which files are to be downloaded, and then either to download them on clicking 'Import', or via a new 'Download chosen files now' button.
(0019104)
turion   
2016-12-02 20:16   
Is there anything besides C++/C-coding that I can do to make this issue progress further? (Right now I'm basically stalled on my music project because there is no freesound.org import.) I'd be happy to test or debug or give/discuss UI ideas.
(0026448)
colinf   
2022-05-20 13:43   
Done in 9fe0a4f4.
(0026452)
x42   
2022-05-20 22:25   
Implemented in 7.0-pre0-2782-g9fe0a4f4dd Thanks to @colinf


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
5847 [ardour] features feature N/A 2014-01-30 18:13 2022-05-20 18:13
Reporter: bruno Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.0  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Display and/or collect attribution info from CC-licensed files from Freesound.org
Description: To facilitate and encourage the user to attribute the source when importing Creative Commons licensed sounds from Freesound.org, Ardour could display attribution info for the selected sound file somewhere in the import window. In addition (or alternatively), it could collect and save a text file with attribution info for all CC-licensed files that were imported into a session from Freesound.org.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
6311 [ardour] features tweak always 2015-05-08 21:53 2022-05-20 18:12
Reporter: gremlink Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 4.0  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Freesound CC license authors
Description: The Freesound import should list authors in some fashion so that appropriate CC licensing credit can be given in works using Freesound material.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
3072 [ardour] bugs minor always 2010-04-17 23:01 2022-05-20 13:48
Reporter: kernel_geek Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: SVN/2.0-ongoing  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Freesound password not hidden
Description: When you input password on freesound screen, its not stared out.

Seems a pretty basic thing, for a program.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0026451)
colinf   
2022-05-20 13:48   
Pretty sure this was fixed years ago, but it's not even relevant now that Freesound import doesn't log directly into freesound.org any more.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
5943 [ardour] bugs major always 2014-06-25 09:09 2022-05-20 13:44
Reporter: ahellquist Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Freesound browser unable to cope with / in the clip name
Description: Searching Freesound sometimes results in clips named for instance:

175586 Dubstep/Wobble Effect 1

That and probably all other tracks will not be playable or possible to import. Nor will the meta information window display tags or audio clip information.

This maybe could be fixed with some regression magic ?

And no: I have no interest in dubstep :-) this i only an academic case
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0026450)
colinf   
2022-05-20 13:44   
Probable fix in 40f8dc69


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8768 [ardour] bugs minor always 2021-07-03 10:58 2022-05-18 18:44
Reporter: DaniDeSaro Platform: Debian GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ardor 6.8 does not close
Description: Since the last versions 'nightlies' (Ardor-6.7.288 or Ardor-6.7.302) I have seen that, opening a new session, and saving it even if you don't do anything in it, when you want to close the program to finish, it stays in the middle close without responding to further mouse events. The ArdorGUI process needs to be terminated in order to terminate Ardor.
I have done tests with other versions of Ardor installed on the same system: Both with Ardor5 and Ardor6.7.0, this does not happen, and the program ends correctly.
Attached log of qjack in case it was useful.
Tags:
Steps To Reproduce: 1. Login with QjackCtl.
2. Open Ardor2.8 and create a new session.
3. Save the session.
4. Try to close the program, activating the Ardor menu 'Exit'.
Additional Information: SO:Linux Mint Ulyssa
Kernel: 5.0.8-59-lowlatency
PC: Acer Aspire
RAM: 16GB
Soft for vst: yabridge + linvst
System Description
Attached Files: conf-inicial-qjack.png (94,176 bytes) 2021-07-03 10:58
https://tracker.ardour.org/file_download.php?file_id=4075&type=bug
cuelgue-ardour.png (61,573 bytes) 2021-07-03 10:58
https://tracker.ardour.org/file_download.php?file_id=4076&type=bug
mensajes-jack-bug-ardour.txt (114,940 bytes) 2021-07-03 10:58
https://tracker.ardour.org/file_download.php?file_id=4077&type=bug
backtrace.txt (17,971 bytes) 2022-02-26 22:46
https://tracker.ardour.org/file_download.php?file_id=4162&type=bug
ardour-backtrace_2022-05-18_17-00 (7,249 bytes) 2022-05-18 18:44
https://tracker.ardour.org/file_download.php?file_id=4188&type=bug
Notes
(0026026)
DaniDeSaro   
2021-07-03 12:03   
Important note: This bug does not happen in the Ardor6.8.0 release version, that version closes without problems. The bug only happens in the 'nigthlie' version of Ardor.
(0026036)
x42   
2021-07-07 04:11   
(Last edited: 2021-07-07 04:13)
Does it still happen with recent 6.8.xx nightlies? debug version?

If so. please run `Ardour6 --gdb` , then inside gdb:
run

then get arodur to hang. back on the gdb window: ctrl+c
this returns you to the gdb prompt, there call:
bt

and
thread apply all bt


this prints a backtrace where ardour hangs. see also https://ardour.org/debugging_ardour

(0026037)
DaniDeSaro   
2021-07-07 09:58   
As I said, this problem was fixed in version 6.8 release. That is why I have not continued to download 'nigthlies' versions. In order to be able to answer you, I just downloaded and installed version 6.8.83-x86_x64-gcc5 (it is not a debug version) and it seems that this failure no longer occurs. Therefore it has been a temporary bug that no longer gives problems. Consider this report more than anything informative.
Greetings, if I can help you here you have me, x42.
(0026038)
x42   
2021-07-07 11:30   
OK. I was asking because there is no obvious difference between 6.7.302 and 3.8 (really 3.7.305) that would explain the difference.
(0026041)
DaniDeSaro   
2021-07-08 12:28   
If no one else has reported it, it may be a product of my bad configuration, although I tried it on two different Mint linux systems and the same thing happened to me ...
(0026313)
niklasliebig   
2022-01-27 20:57   
I'm using Ardour6.5.0~ds0 (built using 6.5.0~ds0-1 and GCC version 10.2.1 20210110) and I'm having a similar (if not the same) problem with Debian 11.2 LXDE. However, it is not 100 percent reproducible. If I only open my project for a short time to play the song and make minor changes, it sometimes closes without any problems. The longer a recording session lasts and the more edits I make, the more likely it seems I'll have to kill Ardour to exit. It happens for both Jack and Alsa backend. Saving my project file works fine. I'm not very familiar with the debug mode described above, but I think I managed to capture the backtrace. I will insert i below. I hope this will help solve this problem and make Ardour more stable.

(gdb) bt
#0 __pthread_clockjoin_ex (threadid=140736697612032,
    thread_return=0x7fffffffc4c0, clockid=<optimized out>,
    abstime=<optimized out>, block=<optimized out>)
    at pthread_join_common.c:145
0000001 0x00007ffff3992150 in ?? () from /lib/x86_64-linux-gnu/libjack.so.0
#2 0x00007ffff39732bc in ?? () from /lib/x86_64-linux-gnu/libjack.so.0
#3 0x00007ffff39746b5 in ?? () from /lib/x86_64-linux-gnu/libjack.so.0
0000004 0x00007ffff39951e1 in jack_client_close ()
   from /lib/x86_64-linux-gnu/libjack.so.0
0000005 0x00007fffe8aadad6 in ARDOUR::JackConnection::close() ()
   from /usr/lib/ardour6/backends/libjack_audiobackend.so
#6 0x00007fffe8ab2e60 in ARDOUR::JACKAudioBackend::stop() ()
   from /usr/lib/ardour6/backends/libjack_audiobackend.so
#7 0x00007ffff769a040 in ARDOUR::AudioEngine::stop(bool) ()
   from /usr/lib/ardour6/libardour.so.3
0000008 0x0000555555a40947 in ?? ()
0000009 0x00007ffff6e2df48 in Glib::SignalProxyNormal::slot0_void_callback(_GObject*, void*) () from /lib/x86_64-linux-gnu/libglibmm-2.4.so.1
0000010 0x00007ffff6d830a2 in g_closure_invoke ()
   from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
0000011 0x00007ffff6d95602 in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
0000012 0x00007ffff6d9b6cf in g_signal_emit_valist ()
   from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
--Type <RET> for more, q to quit, c to continue without paging--
0000013 0x00007ffff6d9bc3f in g_signal_emit ()
   from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
0000014 0x00007ffff684ea01 in ?? () from /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#15 0x00007ffff6d830a2 in g_closure_invoke ()
   from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
0000016 0x00007ffff6d950aa in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#17 0x00007ffff6d9b6cf in g_signal_emit_valist ()
   from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
0000018 0x00007ffff6d9bc3f in g_signal_emit ()
   from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
0000019 0x00007ffff6a30d94 in gtk_widget_activate ()
   from /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
0000020 0x00007ffff6924af5 in gtk_menu_shell_activate_item ()
   from /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
0000021 0x00007ffff6924e09 in ?? () from /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
0000022 0x00007ffff69121ab in ?? () from /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
0000023 0x00007ffff6d830a2 in g_closure_invoke ()
   from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#24 0x00007ffff6d94e6e in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
0000025 0x00007ffff6d9b259 in g_signal_emit_valist ()
   from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
0000026 0x00007ffff6d9bc3f in g_signal_emit ()
   from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
--Type <RET> for more, q to quit, c to continue without paging--
0000027 0x00007ffff6a31fe4 in ?? () from /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
0000028 0x00007ffff69107d4 in gtk_propagate_event ()
   from /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
0000029 0x00007ffff6910c4b in gtk_main_do_event ()
   from /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
0000030 0x00007ffff677aafc in ?? () from /lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
0000031 0x00007ffff6c91e6b in g_main_context_dispatch ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
0000032 0x00007ffff6c92118 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
0000033 0x00007ffff6c9240b in g_main_loop_run ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
0000034 0x00007ffff690fb2a in gtk_main ()
   from /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
0000035 0x00007ffff6fbea7b in Gtkmm2ext::UI::run(Receiver&) ()
   from /usr/lib/ardour6/libgtkmm2ext.so.0
0000036 0x0000555555a081f1 in main ()
(gdb) thread apply all bt

Thread 26 (Thread 0x7fffd0de3700 (LWP 1317) "audioengine"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
0000001 0x00007ffff3993c42 in ?? () from /lib/x86_64-linux-gnu/libjack.so.0
#2 0x00007ffff39769d5 in ?? () from /lib/x86_64-linux-gnu/libjack.so.0
#3 0x00007ffff3975438 in ?? () from /lib/x86_64-linux-gnu/libjack.so.0
0000004 0x00007fffe8ab13d2 in ARDOUR::JACKAudioBackend::process_thread() () from /usr/lib/ardour6/backends/libjack_audiobackend.so
0000005 0x00007ffff39758eb in ?? () from /lib/x86_64-linux-gnu/libjack.so.0
#6 0x00007ffff3991dbc in ?? () from /lib/x86_64-linux-gnu/libjack.so.0
#7 0x00007ffff5d52ea7 in start_thread (arg=<optimized out>) at pthread_create.c:477
0000008 0x00007ffff5616def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 25 (Thread 0x7fffd100d700 (LWP 1316) "audioengine"):
#0 __libc_read (nbytes=4, buf=0x7fffd100c7d0, fd=16) at ../sysdeps/unix/sysv/linux/read.c:26
0000001 __libc_read (fd=16, buf=0x7fffd100c7d0, nbytes=4) at ../sysdeps/unix/sysv/linux/read.c:24
#2 0x00007ffff3992fee in ?? () from /lib/x86_64-linux-gnu/libjack.so.0
#3 0x00007ffff399675d in ?? () from /lib/x86_64-linux-gnu/libjack.so.0
0000004 0x00007ffff39965a2 in ?? () from /lib/x86_64-linux-gnu/libjack.so.0
--Type <RET> for more, q to quit, c to continue without paging--
0000005 0x00007ffff3991dbc in ?? () from /lib/x86_64-linux-gnu/libjack.so.0
#6 0x00007ffff5d52ea7 in start_thread (arg=<optimized out>) at pthread_create.c:477
#7 0x00007ffff5616def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 24 (Thread 0x7fffd3c0d700 (LWP 1306) "audioengine"):
#0 futex_wait_cancelable (private=0, expected=0, futex_word=0x5555572a32c8) at ../sysdeps/nptl/futex-internal.h:186
0000001 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5555572a3270, cond=0x5555572a32a0) at pthread_cond_wait.c:508
#2 __pthread_cond_wait (cond=0x5555572a32a0, mutex=0x5555572a3270) at pthread_cond_wait.c:638
#3 0x00007ffff399287e in ?? () from /lib/x86_64-linux-gnu/libjack.so.0
0000004 0x00007ffff3986d45 in ?? () from /lib/x86_64-linux-gnu/libjack.so.0
0000005 0x00007ffff3991dbc in ?? () from /lib/x86_64-linux-gnu/libjack.so.0
#6 0x00007ffff5d52ea7 in start_thread (arg=<optimized out>) at pthread_create.c:477
#7 0x00007ffff5616def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 15 (Thread 0x7fffd32cb700 (LWP 1284) "gdbus"):
#0 0x00007ffff560c3ff in __GI___poll (fds=0x555556a5a450, nfds=2, timeout=-1) a--Type <RET> for more, q to quit, c to continue without paging--
t ../sysdeps/unix/sysv/linux/poll.c:29
0000001 0x00007ffff6c920ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007ffff6c9240b in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007ffff4b79a36 in ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
0000004 0x00007ffff6cbb0bd in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
0000005 0x00007ffff5d52ea7 in start_thread (arg=<optimized out>) at pthread_create.c:477
#6 0x00007ffff5616def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 14 (Thread 0x7fffd3aee700 (LWP 1283) "gmain"):
#0 0x00007ffff560c3ff in __GI___poll (fds=0x555556a4cc10, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
0000001 0x00007ffff6c920ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007ffff6c921cf in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007ffff6c92221 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
0000004 0x00007ffff6cbb0bd in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
0000005 0x00007ffff5d52ea7 in start_thread (arg=<optimized out>) at pthread_create.c:477
#6 0x00007ffff5616def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
--Type <RET> for more, q to quit, c to continue without paging--

Thread 8 (Thread 0x7fffe93d9700 (LWP 1277) "DeviceList"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
0000001 0x00007ffff6ce334f in g_cond_wait () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007ffff769bb45 in ARDOUR::AudioEngine::do_devicelist_update() () from /usr/lib/ardour6/libardour.so.3
#3 0x00007ffff6e1edb2 in ?? () from /lib/x86_64-linux-gnu/libglibmm-2.4.so.1
0000004 0x00007ffff6cbb0bd in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
0000005 0x00007ffff5d52ea7 in start_thread (arg=<optimized out>) at pthread_create.c:477
#6 0x00007ffff5616def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 7 (Thread 0x7fffea2ca700 (LWP 1276) "EngineWatchdog"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
0000001 0x00007ffff6ce334f in g_cond_wait () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007ffff769c6b7 in ARDOUR::AudioEngine::do_reset_backend() () from /usr/lib/ardour6/libardour.so.3
#3 0x00007ffff6e1edb2 in ?? () from /lib/x86_64-linux-gnu/libglibmm-2.4.so.1
0000004 0x00007ffff6cbb0bd in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
0000005 0x00007ffff5d52ea7 in start_thread (arg=<optimized out>) at pthread_create.c--Type <RET> for more, q to quit, c to continue without paging--
:477
#6 0x00007ffff5616def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7fffeaffd700 (LWP 1274) "Analyzer"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
0000001 0x00007ffff6ce334f in g_cond_wait () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007ffff7659c5f in ARDOUR::Analyser::work() () from /usr/lib/ardour6/libardour.so.3
#3 0x00007ffff6e1edb2 in ?? () from /lib/x86_64-linux-gnu/libglibmm-2.4.so.1
0000004 0x00007ffff6cbb0bd in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
0000005 0x00007ffff5d52ea7 in start_thread (arg=<optimized out>) at pthread_create.c:477
#6 0x00007ffff5616def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7fffeb7fe700 (LWP 1273) "PeakFileBuilder"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
0000001 0x00007ffff6ce334f in g_cond_wait () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007ffff7c6a28f in ?? () from /usr/lib/ardour6/libardour.so.3
#3 0x00007ffff6e1edb2 in ?? () from /lib/x86_64-linux-gnu/libglibmm-2.4.so.1
--Type <RET> for more, q to quit, c to continue without paging--
0000004 0x00007ffff6cbb0bd in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
0000005 0x00007ffff5d52ea7 in start_thread (arg=<optimized out>) at pthread_create.c:477
#6 0x00007ffff5616def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 3 (Thread 0x7fffebfff700 (LWP 1272) "PeakFileBuilder"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
0000001 0x00007ffff6ce334f in g_cond_wait () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007ffff7c6a28f in ?? () from /usr/lib/ardour6/libardour.so.3
#3 0x00007ffff6e1edb2 in ?? () from /lib/x86_64-linux-gnu/libglibmm-2.4.so.1
0000004 0x00007ffff6cbb0bd in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
0000005 0x00007ffff5d52ea7 in start_thread (arg=<optimized out>) at pthread_create.c:477
#6 0x00007ffff5616def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7ffff0925700 (LWP 1271) "LXVSTEventLoop"):
#0 0x00007ffff55dec61 in __GI___clock_nanosleep (clock_id=clock_id@entry=0, flags=flags@entry=0, req=0x7ffff0924780, rem=0x7ffff0924790) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:48
0000001 0x00007ffff55e4443 in __GI___nanosleep (requested_time=<optimized out>, rema--Type <RET> for more, q to quit, c to continue without paging--
ining=<optimized out>) at nanosleep.c:27
#2 0x00007ffff6cbcb4f in g_usleep () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00005555563978d6 in ?? ()
0000004 0x00007ffff5d52ea7 in start_thread (arg=<optimized out>) at pthread_create.c:477
0000005 0x00007ffff5616def in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7ffff09bbcc0 (LWP 1267) "ArdourGUI"):
#0 __pthread_clockjoin_ex (threadid=140736697612032, thread_return=0x7fffffffc4c0, clockid=<optimized out>, abstime=<optimized out>, block=<optimized out>) at pthread_join_common.c:145
0000001 0x00007ffff3992150 in ?? () from /lib/x86_64-linux-gnu/libjack.so.0
#2 0x00007ffff39732bc in ?? () from /lib/x86_64-linux-gnu/libjack.so.0
#3 0x00007ffff39746b5 in ?? () from /lib/x86_64-linux-gnu/libjack.so.0
0000004 0x00007ffff39951e1 in jack_client_close () from /lib/x86_64-linux-gnu/libjack.so.0
0000005 0x00007fffe8aadad6 in ARDOUR::JackConnection::close() () from /usr/lib/ardour6/backends/libjack_audiobackend.so
#6 0x00007fffe8ab2e60 in ARDOUR::JACKAudioBackend::stop() () from /usr/lib/ardour6/backends/libjack_audiobackend.so
#7 0x00007ffff769a040 in ARDOUR::AudioEngine::stop(bool) () from /usr/lib/ardou--Type <RET> for more, q to quit, c to continue without paging--
r6/libardour.so.3
0000008 0x0000555555a40947 in ?? ()
0000009 0x00007ffff6e2df48 in Glib::SignalProxyNormal::slot0_void_callback(_GObject*, void*) () from /lib/x86_64-linux-gnu/libglibmm-2.4.so.1
0000010 0x00007ffff6d830a2 in g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
0000011 0x00007ffff6d95602 in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
0000012 0x00007ffff6d9b6cf in g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
0000013 0x00007ffff6d9bc3f in g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
0000014 0x00007ffff684ea01 in ?? () from /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
#15 0x00007ffff6d830a2 in g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
0000016 0x00007ffff6d950aa in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#17 0x00007ffff6d9b6cf in g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
0000018 0x00007ffff6d9bc3f in g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
0000019 0x00007ffff6a30d94 in gtk_widget_activate () from /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
0000020 0x00007ffff6924af5 in gtk_menu_shell_activate_item () from /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
--Type <RET> for more, q to quit, c to continue without paging--
0000021 0x00007ffff6924e09 in ?? () from /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
0000022 0x00007ffff69121ab in ?? () from /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
0000023 0x00007ffff6d830a2 in g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#24 0x00007ffff6d94e6e in ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
0000025 0x00007ffff6d9b259 in g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
0000026 0x00007ffff6d9bc3f in g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
0000027 0x00007ffff6a31fe4 in ?? () from /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
0000028 0x00007ffff69107d4 in gtk_propagate_event () from /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
0000029 0x00007ffff6910c4b in gtk_main_do_event () from /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
0000030 0x00007ffff677aafc in ?? () from /lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
0000031 0x00007ffff6c91e6b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
0000032 0x00007ffff6c92118 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
0000033 0x00007ffff6c9240b in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
0000034 0x00007ffff690fb2a in gtk_main () from /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0
0000035 0x00007ffff6fbea7b in Gtkmm2ext::UI::run(Receiver&) () from /usr/lib/ardour6--Type <RET> for more, q to quit, c to continue without paging--
/libgtkmm2ext.so.0
0000036 0x0000555555a081f1 in main ()
(gdb)
(0026314)
x42   
2022-01-27 21:02   
This specific backtrace shows that Ardour waits for JACK to close the connection. -- In any case could try with Ardour 6.9.0?
(0026319)
niklasliebig   
2022-01-29 15:46   
Currently I have to stick with the version from the official Debian sources. However, I'm colaborating with another musician who uses Ardor 6.9 on Linux Mint, so we are exchanging the same project file. He always runs the Alsa backend and actually told me that Ardor also freezes when closing. And again no problems with saving the file. Maybe something to do with the project file anyway? Any incompatibility issues between 6.5 and 6.9?
(0026337)
niklasliebig   
2022-02-26 22:46   
After completing my current project, I switched to Ardor 6.9.0 "After Bach" (rev 6.9) Intel 64-bit. Unfortunately, it's the same as for my fellow musician. Ardour doesn't close sometimes and it affects both: Jack and Alsa back end. I attached another backtrace when running Ardour with Alsa back end.
(0026447)
s0600204   
2022-05-18 18:44   
I appear to be having the same problem as @niklasliebig: when attempting to close Ardour the UI freezes and the application has to be force-closed. The backtrace (see attached) is also similar to that given above in note 0008768:0026313.

My symptoms differ in that, having tried running with both the JACK and ALSA backends, closing a session using the ALSA backend does not appear (on the surface) to be problematic.

With the JACK backend, it might be worth noting that at the point that Ardour freezes, QJackCtl's "Connect" dialog shows that Ardour's web of connections has been reduced to two ports: `physical_audio_input_monitor_enable` and `physical_midi_input_monitor_enable` (in the "Audio" and "MIDI" tabs respectively). Neither remain connected to anything.

Further experimentation shows that it doesn't matter whether JACK is using the internal soundcard or an external USB soundcard.

With the ALSA backend, although the UI doesn't freeze when closing (for more than a second), when running Ardour from the terminal the very last line printed is: `Process is still running! trying SIGKILL`. It is unclear what process this is referring to, or if this is an expected message. There isn't any apparent crash, and thus no backtrace.

----

System : ArchLinux
`ardour6 -v` : Ardour6.9.0 (built using 6.9 and GCC version 11.2.0)


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8909 [ardour] features minor N/A 2022-04-27 16:00 2022-05-15 14:16
Reporter: DopplerNyquist Platform: GNU  
Assigned To: OS: Linux  
Priority: high OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: MIDI region decrease saturation when disabled
Description: Sometimes when rearranging a track we need to disable some audio or MIDI regions, and Ardour today only shows a slight different color in the waveform and a simple "!" sign in the MIDI region name.
It would be interesting to have a more pronounced visual feedback of the status of the regions to speed up the work.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files: Screenshot_20220427_124356.png (223,731 bytes) 2022-04-27 16:02
https://tracker.ardour.org/file_download.php?file_id=4180&type=bug
Notes
(0026422)
DopplerNyquist   
2022-04-27 16:02   
Sometimes we have Audio and Midi regions disabled in the same view, but it is difficult to distinguish them.
(0026445)
x42   
2022-05-15 14:16   
Ardour uses transparency to indicate audibly transparent regions (hear data on layers underneath). Also the default track/region-colors are already rather desaturated to be easier on the eye when working long hours.

However thanks to https://github.com/Ardour/ardour/pull/706 the exclamation mark has been replaced with a large "mute" icon which already helps significantly.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8264 [ardour] features minor have not tried 2020-06-22 19:45 2022-05-15 01:20
Reporter: consint Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 6.0  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: More automation modes
Description: It would be very nice if there were other automation modes besides drawing lines.

1. the possibility to draw curves (especially for a faster workflow)
2. an LFO with different shapes
3. a random generator with range adjustment
4. a step sequencer

These tools would be especially useful for music producers and could expand the creative possibilities many times over.
Tags: automation
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0024548)
paul   
2020-07-01 16:32   
(4) is under development.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8559 [ardour] features minor N/A 2021-02-01 19:33 2022-05-15 01:19
Reporter: thebutant Platform: GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: Mixbus 6.x  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Feature request: Non-linear options for automation lines
Description: I really wish for automation lines that aren't linear, but have curves in some way(s).
Either different modes (preferably), like the modes when fading an audio region in or out, or the possibility to drag automation lines into curves.
My experience from other daws is that curvy automation lines tend to sound more musical and lively than the static linear ones.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0025483)
x42   
2021-02-01 19:58   
Keep in mind that the Y-axis may not be linear, but can be logarithmic or exponential, depending on the control.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8911 [ardour] bugs crash always 2022-05-08 13:27 2022-05-10 17:06
Reporter: robertaramar Platform: Linux  
Assigned To: OS: Fedora  
Priority: normal OS Version: 35  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Session doesn't load (ERROR: Unexpected exception during session setup: tr1::bad_weak_ptr)
Description: When loading the session Narcotic.ardour, Ardour presents a "Loading Error" see "Ardour-Loading-Error.png" for details.
On the console, it says:

Log Messages:
INFO: AlsaAudioBackend: adjusted output channel count to match device.
INFO: AlsaAudioBackend: adjusted input channel count to match device.
WARNING: AlsaMidiIO: Cannot acquire realtime permissions.
WARNING: AlsaMidiIO: Cannot acquire realtime permissions.
WARNING: AlsaMidiIO: Cannot acquire realtime permissions.
WARNING: AlsaMidiIO: Cannot acquire realtime permissions.
WARNING: AlsaMidiIO: Cannot acquire realtime permissions.
WARNING: AlsaMidiIO: Cannot acquire realtime permissions.
ERROR: AlsaSeqMidiIO: Device initialization failed.
WARNING: AlsaMidiOut: failed to open midi device '144:0'.
ERROR: AlsaSeqMidiIO: Device initialization failed.
WARNING: AlsaMidiIn: failed to open midi device '144:0'.
ERROR: AlsaSeqMidiIO: Device initialization failed.
WARNING: AlsaMidiOut: failed to open midi device '145:0'.
ERROR: AlsaSeqMidiIO: Device initialization failed.
WARNING: AlsaMidiIn: failed to open midi device '145:0'.
WARNING: AlsaMidiIO: Cannot acquire realtime permissions.
WARNING: AlsaMidiIO: Cannot acquire realtime permissions.
WARNING: AlsaAudioBackend: cannot acquire realtime permissions.
INFO: harvid version: 803
INFO: Loading menus from /opt/Ardour-6.9.0/etc/ardour.menus
ERROR: Unexpected exception during session setup: tr1::bad_weak_ptr
Tags:
Steps To Reproduce: Launch Ardour, open this session.

After clicking away the Loading-Error, if you try to load any other session that would normally load,
you get an exception:

Thread 1 "ArdourGUI" received signal SIGSEGV, Segmentation fault.
0x00007ffff3da0781 in gtk_radio_action_set_group () from /opt/Ardour-6.9.0/lib/libgtk-x11-2.0.so.0
Additional Information: (gdb) bt
#0 0x00007ffff3da0781 in gtk_radio_action_set_group () from /opt/Ardour-6.9.0/lib/libgtk-x11-2.0.so.0
0000001 0x00007ffff1ef37a7 in Gtk::RadioAction::set_group(Gtk::RadioButtonGroup&) () from /opt/Ardour-6.9.0/lib/libgtkmm-2.4.so.1
#2 0x00007ffff1ef3a67 in Gtk::RadioAction::RadioAction(Gtk::RadioButtonGroup&, Glib::ustring const&, Gtk::StockID const&, Glib::ustring const&, Glib::ustring const&)
    () from /opt/Ardour-6.9.0/lib/libgtkmm-2.4.so.1
#3 0x00007ffff1ef3b42 in Gtk::RadioAction::create(Gtk::RadioButtonGroup&, Glib::ustring const&, Glib::ustring const&, Glib::ustring const&) ()
   from /opt/Ardour-6.9.0/lib/libgtkmm-2.4.so.1
0000004 0x00007ffff5b89b0d in ActionManager::register_radio_action(Glib::RefPtr<Gtk::ActionGroup>, Gtk::RadioButtonGroup&, char const*, char const*, sigc::slot<void, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil>) () from /opt/Ardour-6.9.0/lib/libgtkmm2ext.so.0
0000005 0x00005555559a6b7e in ?? ()
#6 0x00005555559bc407 in ?? ()
#7 0x000055555597ed33 in ?? ()
0000008 0x000055555588ff40 in ?? ()
0000009 0x000055555587fed4 in ?? ()
0000010 0x0000555555848f51 in ?? ()
0000011 0x000055555584ad1c in ?? ()
0000012 0x000055555605de94 in ?? ()
0000013 0x000055555606116e in ?? ()
0000014 0x00007ffff1ebe5f5 in ?? () from /opt/Ardour-6.9.0/lib/libgtkmm-2.4.so.1
#15 0x00007ffff4a6c945 in g_closure_invoke () from /opt/Ardour-6.9.0/lib/libgobject-2.0.so.0
0000016 0x00007ffff4a7e01b in ?? () from /opt/Ardour-6.9.0/lib/libgobject-2.0.so.0
#17 0x00007ffff4a87c30 in g_signal_emit_valist () from /opt/Ardour-6.9.0/lib/libgobject-2.0.so.0
0000018 0x00007ffff4a88082 in g_signal_emit () from /opt/Ardour-6.9.0/lib/libgobject-2.0.so.0
0000019 0x00007ffff3cac80c in gtk_dialog_response () from /opt/Ardour-6.9.0/lib/libgtk-x11-2.0.so.0
0000020 0x00007ffff1f37b35 in ?? () from /opt/Ardour-6.9.0/lib/libgtkmm-2.4.so.1
0000021 0x00007ffff4a6c945 in g_closure_invoke () from /opt/Ardour-6.9.0/lib/libgobject-2.0.so.0
0000022 0x00007ffff4a7e01b in ?? () from /opt/Ardour-6.9.0/lib/libgobject-2.0.so.0
0000023 0x00007ffff4a87c30 in g_signal_emit_valist () from /opt/Ardour-6.9.0/lib/libgobject-2.0.so.0
#24 0x00007ffff4a88082 in g_signal_emit () from /opt/Ardour-6.9.0/lib/libgobject-2.0.so.0
0000025 0x00007ffff3eb43c0 in ?? () from /opt/Ardour-6.9.0/lib/libgtk-x11-2.0.so.0
0000026 0x00007ffff3d50cac in ?? () from /opt/Ardour-6.9.0/lib/libgtk-x11-2.0.so.0
0000027 0x00007ffff4a6c945 in g_closure_invoke () from /opt/Ardour-6.9.0/lib/libgobject-2.0.so.0
0000028 0x00007ffff4a7e5a0 in ?? () from /opt/Ardour-6.9.0/lib/libgobject-2.0.so.0
0000029 0x00007ffff4a8769b in g_signal_emit_valist () from /opt/Ardour-6.9.0/lib/libgobject-2.0.so.0
0000030 0x00007ffff4a88082 in g_signal_emit () from /opt/Ardour-6.9.0/lib/libgobject-2.0.so.0
0000031 0x00007ffff3ed564c in ?? () from /opt/Ardour-6.9.0/lib/libgtk-x11-2.0.so.0
0000032 0x00007ffff3d4f29d in gtk_propagate_event () from /opt/Ardour-6.9.0/lib/libgtk-x11-2.0.so.0
0000033 0x00007ffff3d4f723 in gtk_main_do_event () from /opt/Ardour-6.9.0/lib/libgtk-x11-2.0.so.0
0000034 0x00007ffff396bb4c in ?? () from /opt/Ardour-6.9.0/lib/libgdk-x11-2.0.so.0
0000035 0x00007ffff475db67 in g_main_context_dispatch () from /opt/Ardour-6.9.0/lib/libglib-2.0.so.0
0000036 0x00007ffff475ddd0 in ?? () from /opt/Ardour-6.9.0/lib/libglib-2.0.so.0
0000037 0x00007ffff475e0f2 in g_main_loop_run () from /opt/Ardour-6.9.0/lib/libglib-2.0.so.0
0000038 0x00007ffff3d4e3e7 in gtk_main () from /opt/Ardour-6.9.0/lib/libgtk-x11-2.0.so.0
0000039 0x00007ffff5baaa55 in Gtkmm2ext::UI::run(Receiver&) () from /opt/Ardour-6.9.0/lib/libgtkmm2ext.so.0
0000040 0x000055555580c814 in ?? ()
0000041 0x00007fffee3d9f20 in __libc_start_call_main (main=main@entry=0x55555580c420, argc=argc@entry=1, argv=argv@entry=0x7fffffffd058)
    at ../sysdeps/nptl/libc_start_call_main.h:58
--Type <RET> for more, q to quit, c to continue without paging--
0000042 0x00007fffee3d9fd0 in __libc_start_main_impl (main=0x55555580c420, argc=1, argv=0x7fffffffd058, init=<optimized out>, fini=<optimized out>,
    rtld_fini=<optimized out>, stack_end=0x7fffffffd048) at ../csu/libc-start.c:392
0000043 0x000055555581360a in ?? ()

System Description
Attached Files: Ardour-Loading-Error.png (90,641 bytes) 2022-05-08 13:27
https://tracker.ardour.org/file_download.php?file_id=4181&type=bug
Narcotic.ardour (399,027 bytes) 2022-05-08 13:27
https://tracker.ardour.org/file_download.php?file_id=4182&type=bug
Narcotic-2.ardour (398,910 bytes) 2022-05-10 16:06
https://tracker.ardour.org/file_download.php?file_id=4183&type=bug
Notes
(0026439)
x42   
2022-05-10 16:06   
The problem relates to MIDI learn, The bound control is not available at session load. deleting line 4738 in the session file makes the session load again
<MIDIControllable id="19405" event="0xb0" channel="0" additional="0x14"/>
(0026440)
robertaramar   
2022-05-10 17:06   
Thanks, good to know. But is this still considered being a bug?
And we're you able to reproduce the exception when, after closing the error dialog, loading a recently used session?


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8889 [ardour] bugs minor always 2022-03-19 13:02 2022-05-10 06:36
Reporter: mrshroomy Platform: Arch  
Assigned To: paul OS: Linux  
Priority: normal OS Version: (any)  
Status: resolved Product Version: 6.9  
Product Build: Resolution: no change required  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Arch Linux has no sound playback when Ardour is exporting a song
Description: When i use latest arch linux Ardour with pipewire-jack (Wireplumber session manager) and 1024 samples and export a song, i can't hear anything im listening to like Discord voice or music when the song is exporting. When it has finished exporting i hear playback normally again
Tags: export
Steps To Reproduce: 1. Start Ardour
2. Record sound or midi in Ardour
3. Export the song
4. No sound is playback on Linux when its exporting
Additional Information:
System Description
Attached Files:
Notes
(0026350)
x42   
2022-03-22 18:33   
Ardour uses "freewheeling" to export.
It asks JACK to disconnect from the audio hardware and run as fast as possible and as slow as necessary. This was no dropouts can happen during export and it is usually also faster than wall-clock time.

I do now know how pipewire handles things, but with JACK this is expected behavior. All JACK applications cannot use hardware I/O while jack is freewheeling.
(0026387)
paul   
2022-04-16 00:33   
If you do not want this behavior, do not use JACK. We generally recommend against the use of JACK, particularly by new users, unless there is an actual need for it.

This is not behavior that we will change. If you use the JACK backend, the only way to reliably perform a faster-than-realtime export is to use freewheeling, which will necessarily silence all JACK output to your audio (and MIDI) hardware. That is by design, and isn't a part of Ardour.

Unless you need JACK, you should use Ardour's ALSA backend (which disconnects from the audio hardware entirely during faster-than-realtime export.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8910 [ardour] features minor always 2022-05-03 09:10 2022-05-04 13:47
Reporter: johne53 Platform: Microsoft  
Assigned To: OS: Windows  
Priority: normal OS Version: 10  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Strange inverted behaviour with track groups
Description: This was first reported by a Mixbus user but I couldn't reproduce it in Mixbus - however it seems very reproducible in Ardour. Although it refers to tracks, it's easier to see in the Edit window.
Tags:
Steps To Reproduce: 1) Select two Editor tracks and click 'Group->New Group' to add them to a group.
2) Moving one fader will now (correctly) move them both.
3) 'Shift+Move' will (correctly) move only the selected fader.
4) Now select 'Group->Edit Group' and mark the group as inactive.
5) Each fader can now (correctly) be moved independently - i.e. as if they weren't grouped.
6) BUT - 'Shift+Move' now moves both faders.
Additional Information: The Mixbus user found it in MB for Linux (not sure which Linux)
System Description
Attached Files:
Notes
(0026427)
x42   
2022-05-03 18:18   
That is intentional. Shift "inverts" the group behavior.
(0026428)
johne53   
2022-05-04 11:17   
In that case there seems to be an inconsistency between Ardour and Mixbus - namely:-

1) Select two Editor tracks and click 'Group->New Group' to add them to a group.
2) Moving one fader will now (correctly) move them both.
3) 'Shift+Move' will (correctly) move only the selected fader.
4) Now select 'Group->Edit Group' and mark the group as inactive.
5) Each fader can now (correctly) be moved independently - i.e. as if they weren't grouped.
6) And in Ardour - 'Shift+Move' now moves both faders.
7) But in Mixbus - 'Shift+Move' still only moves the selected fader.
(0026429)
johne53   
2022-05-04 11:23   
Sorry, I should have added that items 6) and 7) refer to adjustments made in the Mixer window (adjustments made in the Edit window seem okay)
(0026430)
x42   
2022-05-04 13:47   
(6) Ardour -- is what I expect to happen. Shift + action inverts the group setting: deactivated groups (group-settings) are enabled, and vice versa.

But yes, Mixbus changes various hardcoded modifiers in Route-UI for their mixer-strips. e.g. shift+click does not reset the Mixbus-Faders to default (double-click does).
Mute/Solo buttons group-override is ctrl+click in Ardour, but shift+click for Mixbus. and Solo-isolated toggle is also different ctrl+click in Mixbus...

It is inconsistent since the Ardour widgets retain their original behaviour.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8901 [ardour] bugs minor always 2022-04-16 07:06 2022-04-29 13:09
Reporter: johne53 Platform: Microsoft  
Assigned To: OS: Windows  
Priority: normal OS Version: 10  
Status: new Product Version: Mixbus 8.x  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Failed to find action: [ClipEditing/zoom-in]
Description: When I launch the latest Mixbus (from a terminal window) and then I load a session, a message appears in the terminal:-

Failed to find action: [ClipEditing/zoom-in]

If I subsequently attempt to zoom the Edit window, MB will usually crash. Or if it doesn't crash immediately, zooming the Edit window and then clicking in the Summary window will usually crash it.
Tags:
Steps To Reproduce:
Additional Information: This was first reported by a Mixbus user although I guess it'll also affect Ardour:-

https://forum.harrisonconsoles.com/thread-10662.html

There are reports that it affects Windows and Linux but not Mac.

And here's where it gets weird... if I copy text to the clipboard from some totally unrelated window (i.e. not even a Mixbus window) my MSVC build displays this text in Mixbus's terminal window:-

Gdk-CRITICAL **: inner_clipboard_window_procedure: assertion 'success' failed
System Description
Attached Files: Waveform-corrupted.png (23,159 bytes) 2022-04-17 08:49
https://tracker.ardour.org/file_download.php?file_id=4175&type=bug
Waveform-normal.png (15,672 bytes) 2022-04-17 08:49
https://tracker.ardour.org/file_download.php?file_id=4176&type=bug
read_fpp_crash_mac_m1.txt (146,301 bytes) 2022-04-25 15:11
https://tracker.ardour.org/file_download.php?file_id=4177&type=bug
Notes
(0026403)
johne53   
2022-04-16 08:04   
It just occurred to me that the Gdk-CRITICAL error is probably unrelated to the zooming crash.
(0026404)
johne53   
2022-04-17 08:49   
My MSVC build doesn't seem to crash but I've noticed something which might be connected. With some zoom factors, clips are getting drawn normally and with others, they look corrupted.
(0026408)
johne53   
2022-04-18 15:20   
This problem seems to have come sometime between the first MB32C release (8.0.17) and the second release (8.0.106). And given that I'm seeing some waveform issues here I decided to look at the 'waveview' branch and see if anything changed between those releases. I could only see 1 x change (on 28th Feb) which involved 2 x commits to change from using Glib::Threads to PBD::Thread (commits 24bbf403b9 and 50abcc74b5). So this morning I decided to revert those 2 commits and see if it'd fix the waveform problem - which it doesn't.

So it's looking like someone will need to track down the actual crash somehow in gcc
(0026412)
johne53   
2022-04-22 10:54   
An idea occurred to me this morning. As well as building with MSVC, Visual Studio now also supports building with Clang. So I rebuilt this morning and sure enough, Clang crashes in exactly the same way as gcc. What's weird is that each crash is always at a different place in the code but the thing they all have in common is that each crash happens immediately after 'WaveView::process_draw_request()' returns. AFAICT each waveform gets drawn in its own thread so maybe the threads are interfering with each other somehow? Or maybe a draw request is getting deleted before it's been fully processed?

I mentioned earlier that Glib::Threads got changed recently to PBD::Thread - but reverting that change didn't solve the problem. But maybe that one change isn't enough? Perhaps something else would need to get reverted too? I'm just flagging it up here in case it jogs someone's memory...
(0026414)
paul   
2022-04-22 18:13   
We are not using new mutex objects, so the Thread change is not relevant. Also, this crash happens on gcc builds, so it has nothing specifically to do with MSVC.

The warning about a missing action during startup is also a red herring.
(0026418)
BenLoftis   
2022-04-25 15:11   
a zoom+scale crash report from Mac M1 ARM; largely the same as other platforms
(0026425)
johne53   
2022-04-29 13:09   
This got fixed in commit #6f5d3d8dd9, from Apr 26th 2022. It looks like it was just a mis-type when converting from Mutex to RWLock.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8198 [ardour] bugs minor always 2020-06-04 07:11 2022-04-27 14:37
Reporter: Tremeschin Platform: Linux  
Assigned To: paul OS: Arch Linux  
Priority: normal OS Version: Rolling  
Status: resolved Product Version: 6.0  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Duplicating MIDI notes selection in internal edit does not select all the cloned notes but one
Description: Looks like while Ctrl + clicking + dragging a MIDI note selection to duplicate it, only the bottom-most right-most note is selected after cloning while leaving the other duped notes deselected.
Tags: editing, Midi, notes, select
Steps To Reproduce: 1. Create MIDI region
2. Write two or more notes in it
3. Enter internal edit mode
4. Select two or more notes
5. Ctrl + click + drag to duplicate the notes
6. Drag these duplicated notes to a empty space within the region for better visibility

Now only one note will be selected out of the ones that were duplicated
Additional Information: This is annoying when writing plucks / chords progressions as more often than not you want the notes to be playing repeatedly and not always selecting everything and duplicating fill in all the spots or fits them right.

Ardour compiled locally, commit 378a0af

waf configure -j 6 -p --optimize --cxx11

waf build -j 4 -p

Backed up ~/.config/ardour6.dev and ~/.config/ardour6, deleted and run a blank profile, issue still there.

Issue is present on current ardour 6.0-2 package on my Linux distro (compiled from the community as official releases are paid?)
System Description
Attached Files:
Notes
(0026421)
paul   
2022-04-27 14:37   
fixed in 9e77d8923ac (will be in v7.0)


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8422 [ardour] features minor have not tried 2020-09-25 23:50 2022-04-27 08:15
Reporter: wargreen Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Live clip launch mechanism
Description: Allow to launch one or many clips (audio or midi) while playing the timeline would be nice.
When a clip launched in single play or loop, the audio (or midi) data would take the place of the data of the timeline in the input of the track and remain in sync with the master beat (or not if defined in the clip). Have a parameter for the behavior at the end of the clip would be an advantage for creative use.

This would allow a live usage of Ardour without use trick in the main timeline.

It's a real mess in the FLOSS world, the only alternative in the "pro" live show world are Live or Qlab.
We are Linux Show Player of SuperBoucle (each with it benefices) but no one come with a full featured mixer, timeline, MIDI clips and OSC interface.
Tags: audio, live, loop, Midi
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0026402)
paul   
2022-04-16 02:44   
coming up in ardour 7.0


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8908 [ardour] bugs crash sometimes 2022-04-26 19:31 2022-04-26 19:31
Reporter: dannyb Platform: Redhat  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Crashes when exporting to audio file.
Description: 1. So far it happens when exporting the project to an audio file--flac format in these cases.
2. I create a mono project from a template with all LV2 plugins (EQ, Gate, FastLookahead Limiter, Expander, Compressor)
3. I drag and drop one flac file into the template track, reduce the whole region gain by 1 or 2dB, then export it to flack.
4. Usually I do NOT do any editing of the region except the gain. If I do more editing, it seems more likely to crash.
Tags: crash, export audio, mutex
Steps To Reproduce: I cannot directly reproduce the crash, but it tends to happen only while exporting to audio.
Additional Information: OS Info:
Operating System: Fedora Linux 35
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2
Kernel Version: 5.17.4-200.fc35.x86_64 (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 31.4 GiB of RAM
Graphics Processor: NVIDIA GeForce GT 710/PCIe/SSE2 (proprietary driver installed)
====

Console error message when run from the prompt: (occurs every time it crashes)
Attempt to unlock mutex that was not locked
Aborted (core dumped)
====

I wanted to run a debug version of Ardour, but was not able to just download one. I have the Linux know how to do it, but could not find a "simple" way to do it.
====
System Description
Attached Files: Ardour 6.9 - crash on file export (LWP 71654 gdb backtrace).txt (76,311 bytes) 2022-04-26 19:31
https://tracker.ardour.org/file_download.php?file_id=4178&type=bug
Ardour 6.9 - crash on file export (LWP 97375 gdb backtrace).txt (67,995 bytes) 2022-04-26 19:31
https://tracker.ardour.org/file_download.php?file_id=4179&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8906 [ardour] bugs minor always 2022-04-23 12:41 2022-04-23 18:20
Reporter: teodrolli Platform: Linux  
Assigned To: OS: Arch Linux  
Priority: low OS Version:  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Always switches to newly-saved version
Description: If you "Save AS" current session and uncheck "Switch to newly-saved version" Ardour switches to new version anyway.
Tags:
Steps To Reproduce: Go to Session > Save As...
Uncheck "Switch to newly-saved version"
Click "OK"
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8904 [ardour] bugs crash always 2022-04-22 16:23 2022-04-23 10:54
Reporter: robertaramar Platform: Redhat  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ardour crashes after some time
Description: Running Ardour on JACK.
No matter whether buffers are big 512 or small 64.
After some time, I get an exception and Ardour crashes.
I do not get this when running Ardour on ALSA.
As I ususally use ALSA, but did have to use JACK in this particular case, this bug is not really important to me.
I just thought, Ardour shouldn't crash for anything like that.
Tags:
Steps To Reproduce: No particular steps to be taken.
I don't even have to play anything, just launching Ardour with a project and leave it, will crash shortly after one minute (01:09, 01:15).
You have to open a project, having the project selection box open, does not count into that minute.
Additional Information: [Thread 0x7fffaffff640 (LWP 104142) exited]

Thread 25 "audioengine" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffc4367640 (LWP 104179)]
0x00007ffff744ce1b in ARDOUR::PortManager::run_input_meters(unsigned int, long) () from /opt/Ardour-6.9.0/lib/libardour.so.3


(gdb) bt
#0 0x00007ffff744ce1b in ARDOUR::PortManager::run_input_meters(unsigned int, long) () from /opt/Ardour-6.9.0/lib/libardour.so.3
0000001 0x00007ffff744f62b in ARDOUR::PortManager::cycle_start(unsigned int, ARDOUR::Session*) () from /opt/Ardour-6.9.0/lib/libardour.so.3
#2 0x00007ffff704f722 in ARDOUR::AudioEngine::process_callback(unsigned int) () from /opt/Ardour-6.9.0/lib/libardour.so.3
#3 0x00007fffc71c12fb in ARDOUR::JACKAudioBackend::process_thread() () from /opt/Ardour-6.9.0/lib/backends/libjack_audiobackend.so
0000004 0x00007fffdc015414 in non-virtual thunk to Jack::JackClient::Execute() () at ../common/JackClient.cpp:583
0000005 0x00007fffdc0330b0 in Jack::JackPosixThread::ThreadHandler (arg=0x555556a99f98) at ../posix/JackPosixThread.cpp:63
#6 0x00007fffee422b1a in start_thread (arg=<optimized out>) at pthread_create.c:443
#7 0x00007fffee4a7660 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
System Description
Attached Files:
Notes
(0026413)
paul   
2022-04-22 18:11   
Almost certainly caused by JACK "zombifying" Ardour for taking too long when processing audio OR by JACK itself going away.

Will hopefully be fixed in 7.0, but it is actually remarkably difficult for JACK clients as complex as Ardour to respond safely to either of those two conditions.
(0026417)
robertaramar   
2022-04-23 10:54   
Would you think that is something introduced by JACK lately. Because I'm using Ardour 6.9.0 since it came out, I was using it solely on JACK until I switch to using ALSA - roughly - six months ago. And I never had issues with JACK before.
If I can be of help further analyzing that, please let me know.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8890 [ardour] bugs minor always 2022-03-23 18:45 2022-04-21 11:25
Reporter: bmuxbeats Platform: Desktop  
Assigned To: paul OS: Manjaro Linux  
Priority: normal OS Version: 21.2.5  
Status: assigned Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Generic MIDI Binding Maps / bind sysex messages not working
Description: I'm currently creating a new generic MIDI binding map for an AKAI MPK261 MIDI controller.
First of all I want to re-map my transport controlling keys.

According to the dedicated documentation (https://manual.ardour.org/using-control-surfaces/generic-midi/midi-binding-maps/) I've tried the following command:

...
Binding sysex="f0 7f 7f 06 06 f7" action="Transport/RecordCountIn"/> <!-- Record w/Count-In -->
...

This definition will not be recognized fro Ardour.

As I tryed out the following definition:
...
Binding msg="f0 7f 7f 06 06 f7" action="Transport/RecordCountIn"/> <!-- Record w/Count-In -->
...
This worked without any problems.
Tags:
Steps To Reproduce: I've created a brand new file named AKAI_MPK261.map file in the folder /usr/share/ardour6/midi_maps/

I've attached the file to this post.
If you open up the file, you can see some lines with "...sysex=". They won't be recognized by Ardour.
The lines with the "...msg=" are recognized and they do their job.
Additional Information:
System Description
Attached Files: AKAI_MPK261.map (979 bytes) 2022-03-23 18:45
https://tracker.ardour.org/file_download.php?file_id=4171&type=bug
Notes
(0026394)
paul   
2022-04-16 00:49   
I think this is fairly simple. All sysex messages start with 0xf0 and end with 0xf7. If you define a message as "sysex", the definition should only contain the *contents* of the sysex message, not the start (0xf0) or the end (0xf7). Let me know if that works for you.
(0026410)
bmuxbeats   
2022-04-21 11:24   
@paul
Nope - it doesn' work.
(0026411)
bmuxbeats   
2022-04-21 11:25   
BTW:
The documentation shows the following lines:

 You can also bind sysex messages:
<Binding sysex="f0 0 0 e 9 0 5b f7" ….
<Binding sysex="f0 7f 0 6 7 f7" ….

The string after the sysex= part is the sequence of MIDI bytes, as hexadecimal values, that make up the sysex message.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8899 [ardour] bugs minor always 2022-04-13 20:37 2022-04-20 19:19
Reporter: mrMute Platform: Debian GNU  
Assigned To: paul OS: Linux  
Priority: normal OS Version: (any)  
Status: feedback Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Selected MIDI notes in regions stay selected when creating a selection in another region
Description: Creating a new selection in a region deselects the notes of the previous selection in that region.

But when you select midi notes in a region and make a new selection in a second region, the notes in the first region stay selected.

This selection can be expanded over multiple regions.

Edits like resizing and deleting notes are applied to all the notes you selected this way.

This can lead to unexpected data loss.

Tags:
Steps To Reproduce: Switch to edit mode.

Select some notes in a region.

Select some notes in another region.
Additional Information: This seems related to:
https://discourse.ardour.org/t/ardour-6-8-destroyed-my-midi-regions/106251
https://mantis.ardour.org/view.php?id=8729
System Description
Attached Files: selection.png (65,473 bytes) 2022-04-13 20:37
https://tracker.ardour.org/file_download.php?file_id=4174&type=bug
Notes
(0026406)
paul   
2022-04-18 05:01   
this should either be dramatically improved or totally fixed in git master (nightly builds) as of commit #a0d08232ad9


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8902 [ardour] features minor always 2022-04-18 20:47 2022-04-18 20:47
Reporter: unsafelyhotboots Platform: Arch  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Feature request: Humanization
Description: Most DAWS have some kind of right click context option, or a device that creates 'jitter' in MIDI velocity values and adjusts notes to be slightly off beat. I use this function after quantization and note correction to add human groove into my programmed MIDI clips.

It would be nice if the context menu had the following:
Velocity range: This is the +/- range that it would add jitter - so if the range was 10, it would add +/- 10 to velocity.
Velocity: This would set the centerpoint for the range value, so it would need to be set
Timing: This needs to be set up to rush or drag, ideally on a slider, and would set the centerpoint for any sample movement
Timing range: This is the +/- range that it would add jitter - so if the range was 10, it would add +/- 10 to timing. With this, if notes are set to subtly drag, but the range is set to be wide enough, it would need to cap it so that notes would land on the beat instead of being rushed. For example, if the timing is set to drag by 3 samples, but the range is set to 10, it would drag by up to 10 samples but rush by 3 (landing it on the beat instead of rushing it).
Tags: feature-request midi
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8721 [ardour] features minor N/A 2021-05-24 09:05 2022-04-18 05:23
Reporter: whitewolfmusic Platform: Apple Macintosh  
Assigned To: OS: MacOS  
Priority: normal OS Version: 10.12 or later  
Status: new Product Version: 6.7  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: MIDI workflow improvements for Ardour v7
Description: Original topic with explanations:
https://discourse.ardour.org/t/suggestions-to-improve-midi-workflow-in-ardour-v7/105979

Summary of requested changes:

==============
Add track dialog:
==============
- remember the last selected track type
and / or
- allow rearranging track types / making MIDI track the default selection

====================
Create new MIDI region:
====================
- double clicking inside a MIDI track creates a new 4-bar MIDI region, starting with the bar that has been double-clicked

==================
Editing a MIDI region:
==================

After double-clicking a MIDI region to zoom into it:

- if the region is empty, automatically switch to drawing mode

- if the region contains note data, automatically switch to internal edit mode; but in the settings:
- add an option to choose between internal edit mode and drawing mode for this

- default note velocity should be 127.

- when scrolling with mousewheel to change velocity before drawing a new note, keep this new velocity value for drawing further notes

===================================
Something that drives me crazy right now:
===================================

When drawing notes within a zoomed region, I want to scroll up and down the octaves. NOT the tracks. To do that, I currently have to move the cursor over this super thin strip of octave selector, which slows me down, is not intuitive and requires too much precision to keep the cursor in that slim region. So:

- When zoomed into a MIDI region, make scrolling the mouse wheel scroll up and down ovtaves instead of the track list, while the cursor is over an empty area and no notes are selected.

======================================================
Allow to exit the zoom to MIDI region the same way as entering it:
======================================================

- double-click with the grabbing tool inside a zoomed-in MIDI region goes back to the zoom level before
Tags: Ardour, editing, feature request, MIDI region, usability
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0025886)
x42   
2021-05-24 17:20   
Thanks, that is a nice list of good suggestions!

A few comments:

> - remember the last selected track type
> and / or
> - allow rearranging track types / making MIDI track the default selection

The latter is not great since GUI should be consistent. However The former has been near the bottom of my ToDo list for at least 10 years.
It is low priority since compared to hours and hours of recording, editing and mixing, adding tracks is a non-issue. Preselection shaves off a few seconds.
I keep it on a list for someone new to the coding who may want to start contributing to the project.


> - when scrolling with mousewheel to change velocity before drawing a new note, keep this new velocity value for drawing further notes

Currently Ardour uses velocity of the previous note when you append to a region, and otherwise the average of previous/next note.
This should perhaps be more explicit, and this ties in with https://tracker.ardour.org/view.php?id=5608


> - double-click with the grabbing tool inside a zoomed-in MIDI region goes back to the zoom level before

We need to be careful to not overload what double-click does. I don't like the double-click to zoom. That was added only as experiment and somehow remained.
Double-click usually it activates an action that operates on the current selection (e.g. create regions on selected track).

There are some edge-cases with your suggestion. e.g. what happens if you manually resize the track or window after maximizing? Does double-click fill again?
explicit "fill" (F) and "visual undo" (Ctrl+shift+Z) operations are preferable.


PS. Ardour 7 is mainly about fixing a fundamental issue how ardour represents time internally, major version change is needed since the session format changes.
Your suggestions are mostly incremental small changes that can happen later during the 7.x or 8.x minor releases. They're workflow specific and not session-format related.
(0025887)
Daniele1971   
2021-05-24 17:37   
I would add panning note inside pianoroll.
(0025890)
whitewolfmusic   
2021-05-25 03:08   
> - allow rearranging track types / making MIDI track the default selection

@x42: "The latter is not great since GUI should be consistent."

That is correct, in hindsight, I would prefer a simple "make default" button or an option in the settings.

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

@x42: "what happens if you manually resize the track or window after maximizing? Does double-click fill again?
explicit "fill" (F) and "visual undo" (Ctrl+shift+Z) operations are preferable."

Good point. However, I see an urgent need for improvement in this area. Since Ardour does not apply to the typical way of MIDI editing, having a separate window or screen area, my personal experience is that navigating tracks and navigating the piano roll get in each other's way. When I zoom into a MIDI event, I commit to edit only the note content of that event. I want to navigate only the information surrounding this task. That means to me, if I scroll, I want to scroll the octaves, not the tracks. Fully zooming in to a MIDI event equals opening a separate editor window in my mind, so double-clicking to zoom should lock this zoom state until manually exiting it. Zooming into a MIDI region should prevent scrolling tracks and instead scroll octaves inside the piano roll, that would be the best and most logical compromise to me, for not having a separate editing area.
(0026407)
paul   
2022-04-18 05:23   
as of commit b725b7ddb4, the scrolling behavior has been implemented as follows:

- scroll in a MIDI region with no notes selected with adjust the visible note range
- with no modifier, it moves by single notes
- with the tertiary modifier (shift) it moves by octaves (matches transpose behavior)
- with the primary (ctrl on linux/win, cmd on macOS) modifier, it modifies expands the note range rather than scrolling. scroll up will increase the uppermost visible note, scroll down will decrease the lowermost visible note

Remember that scroll if there are notes selected is used to adjust note velocity.

Thanks for this suggestion.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8729 [ardour] bugs minor sometimes 2021-05-28 15:46 2022-04-18 05:01
Reporter: unfa Platform: PC  
Assigned To: paul OS: Manjaro Linux  
Priority: normal OS Version: KDE  
Status: feedback Product Version: 6.7  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Impossible to deselects regions for multi-region MIDI editing - resulting in unwanted note alteration on multiple tracks
Description: When editing MIDI in a large project I've realized some of my notes are way longer than the y should be, and that I remember making them.

I've inspected the issue and realized when I enter the Edit Mode, there's a lot of MIDI regions selected, with all of the notes inside of them selected as well.
As a result when I try to change length of a single note in one region - dozens of other MIDI notes get altered as well in other regions on other tracks against my intention.

I have tried going in and out of Edit Mode or selecting notes, using Region > Select > Deselect all - to no avail.
it seems the only way for me to alter length of a note without messing up my project in unknown capacity is to delete a note I want to alter and add it again with a different length.

Any attempt at changing the note length will further mess up my project.

This has happened before in the 6.0 branch, but never to such a degree.
Tags: Midi
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0026098)
unfa   
2021-08-08 18:36   
This bug strikes again in 6.8:
https://discourse.ardour.org/t/ardour-6-8-destroyed-my-midi-regions/106251
(0026405)
paul   
2022-04-18 05:00   
this should either be dramatically improved or totally fixed as of commit #a0d08232ad9


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8824 [ardour] bugs minor always 2021-11-22 01:57 2022-04-16 00:44
Reporter: ragnarok Platform: amd64  
Assigned To: OS: Debian GNU/Linux  
Priority: normal OS Version: 10.11  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: the selected external midi device is not saved when ardour is closed
Description: the selected external midi device is not saved when ardour is closed and is back to the default value Generic / General Midi
Tags: Midi
Steps To Reproduce: create session
add midi track
select external midi device ex: Line -> POD
save and close the session

open session again
the device midi go back to Generic / General MIDI


Additional Information: I use (ardev) a build from 6.9.0 sources.
System Description
Attached Files: 2021-11-21_22-58.png (36,610 bytes) 2021-11-22 01:59
https://tracker.ardour.org/file_download.php?file_id=4137&type=bug
Notes
(0026222)
ragnarok   
2021-11-22 01:59   
capture
(0026390)
paul   
2022-04-16 00:44   
What you have shown is not a "selected MIDI device". Those controls related to the use of a MIDNAM file, which is an industry standard (albeit, under-utilized) for providing the names of patches/programs in a synth. They do not control the external device connected to the track, nor the synth inside the track. It is merely used for naming patches/programs.

In addition, I cannot reproduce that here with the official 6.9 build. What synth are you using within the track, if any?


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8883 [ardour] bugs minor random 2022-02-25 21:21 2022-04-16 00:36
Reporter: Arkforest Platform: GNU  
Assigned To: paul OS: Linux  
Priority: normal OS Version: (any)  
Status: feedback Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ardour destroys individual MIDI files upon closing and reopening of projects.
Description: I am using Ardour 6.7.0 (rev 6.7) on Bandshed Records' AV Linux (my current OS is based on the outdated MX Linux 19), but this problem also occurred when I used to use Obarun Linux (based on Arch Linux, but with S6 instead of systemd) last year as well, so it's not OS exclusive. There is a small chance (small, but significant) that whenever I close and reopen a project, Ardour destroys a few MIDI files in my music projects. This became particularly problematic with me recently, as I had been manually tuning my vocal takes with x42 autotune and MIDI, and it was those autotune clips I lost, which I struggle to remember the notes for since they're not used the normal way. I have also tried to find it among the interchange and dead folders, but that failed, since the specific files I needed came from another project (I saved this project from another one to reuse the same mix template, and it seems I didn't clear the dead MIDI from the previous project). This bug is one of those ones which is infrequent enough for people to underreport it, and I know the famous musician and YouTuber unfa also has this problem and I, also a somewhat popular musician and YouTuber, am now speaking about this problem too. I would like to be able to find a solution to this problem that can allow it to be patched somehow.
Tags: 6.7, Midi, MIDI region, missing source, overwrite
Steps To Reproduce: It usually happens when I save a project, close a project and then reopen it again. There is a low chance of reproduction with this bug and will potentially need extensive testing.
Additional Information:
System Description
Attached Files: ardourbug1.png (86,829 bytes) 2022-02-25 21:21
https://tracker.ardour.org/file_download.php?file_id=4158&type=bug
ardourbug2.png (156,858 bytes) 2022-02-25 21:21
https://tracker.ardour.org/file_download.php?file_id=4159&type=bug
ardourbug3.png (168,086 bytes) 2022-02-25 21:21
https://tracker.ardour.org/file_download.php?file_id=4160&type=bug
ardourbug4.png (114,309 bytes) 2022-02-25 21:21
https://tracker.ardour.org/file_download.php?file_id=4161&type=bug
Screenshot_20220326_085305.png (33,355 bytes) 2022-03-26 06:56
https://tracker.ardour.org/file_download.php?file_id=4172&type=bug
Notes
(0026336)
unfa   
2022-02-25 21:35   
I see Ardour 6.9 silently deleting data from MIDI files all the time.
I save a project, I load in the next day or next 15 minutes and some regions are just empty.
Recently I also had a few instances of Ardour refusing to load the entire session because some MIDI file was made empty (0 bytes).
I had to delete that file or remove a reference to in in the .ardour session file.
I don't know if it's the same issue we see here, but I think they all must have a common cause.

Ardour is eating MIDI files on a regular basis and that's just horrible.
PLEASE - FIX THIS!
(0026359)
Bugzey   
2022-03-26 06:56   
I can confirm I encountered this issue too today. After finishing up a project, some midi files were gone with the above described error message the next morning.

The only thing different for me is that I had duplicated a previously existing session using Session -> Save as, and then I continued working on the new session. This new session was affected by the bug, but only midi files added after the duplication disappeared. Midi files that existed in the old session are still there in the new session.

I ran a quick text search, and I'm finding instances of the old session's path still being referenced. I renamed "fiddling" to "fatal piano", and searching for fiddling showed the following:

$ grep fatal\ piano/ -Eire fiddling
fatal piano/fatal piano.ardour: <Option name="audio-search-path" value="/run/media/radi/Archives/Dropbox/Documents/Ardour/fiddling/interchange/fiddling/audiofiles"/>
fatal piano/fatal piano.ardour.bak: <Option name="audio-search-path" value="/run/media/radi/Archives/Dropbox/Documents/Ardour/fiddling/interchange/fiddling/audiofiles"/>

System: Linux 5.15.28-1-MANJARO 0000001 SMP PREEMPT Fri Mar 11 14:12:57 UTC 2022 x86_64 GNU/Linux
(0026388)
paul   
2022-04-16 00:36   
Please describe a precise step-by-step recipe that replicates this behaviour predictably, and I will be happy to take a look.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8898 [ardour] features minor N/A 2022-04-07 12:31 2022-04-07 12:31
Reporter: rdz Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Allow to de/activate tracks with OSC commands
Description: In dynamic setups where only a subset of tracks is used at any given time, this could help reduce DSP usage. Also, it seems natural to have the ability to disable tracks since you can already hide, rename, mute, solo (etc.) them.

This could look like this:
 
/strip/active 15 1 <-- activate strip 15
/strip/active 15 0 <-- deactivate strip 15
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8782 [ardour] bugs minor always 2021-07-27 09:54 2022-04-06 23:24
Reporter: MyLoFy Platform: Arch  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.8  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Export to audio file creates silent file with pipewire
Description: I'm testing pipewire in an audio production environment:
-pipewire 1:0.3.32-1 from arch repos
-Ardour 6.8
-Monitor section activated
-Ardour set to Jack backend
Tags:
Steps To Reproduce: -Activate Monitor section
-Master is routed to monitor
-Export project to audio => audio file is silent
-Connect Master to system output => audio file as expected
Additional Information:
System Description
Attached Files:
Notes
(0026376)
spixi   
2022-04-06 23:24   
Gentoo user here. Please switch to another PipeWire version. I switched from PipeWire 0.3.30 to 0.3.49 and WAV export works now with Ardour 6.9 and LibSndfile 1.1.0.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8887 [ardour] bugs minor always 2022-03-05 09:44 2022-04-04 07:29
Reporter: coenplanetc Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Consolidation of midi range(s) after a tempo-change unexpected effects length and timing of notes and region
Description: Occurs after a tempo change (for example 120 to 140):
Cconsolidation of one midi range or two midi ranges (bouncing) does something unexpected to the length and placement of the midi notes inside the range.
The range length is also affected. What you expect is that the new range is the same length as the selected region, bit it's not.
Tags:
Steps To Reproduce: Create one miditrack.
Create a tempo change after a couple of bars (for example, start tempo is 120, create a tempo change 140).
Create two regions after the tempo change and put some snapped notes in it, all tied to the grid.
Select the two midi region is one range and consolidate.

Even simpeler: if only one region is selected as a range and consolidate the same happens but a bit less noticable.
Additional Information: Ardour 6.9.0 ds-01
Ubuntu Studio 21.10
System Description
Attached Files: ResultOneRegion.jpg (152,981 bytes) 2022-03-05 09:44
https://tracker.ardour.org/file_download.php?file_id=4167&type=bug
ResultTwoRegions.jpg (142,993 bytes) 2022-03-05 09:44
https://tracker.ardour.org/file_download.php?file_id=4168&type=bug
Step1.jpg (150,198 bytes) 2022-03-05 09:44
https://tracker.ardour.org/file_download.php?file_id=4169&type=bug
Step2.jpg (144,392 bytes) 2022-03-05 09:44
https://tracker.ardour.org/file_download.php?file_id=4170&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8581 [ardour] bugs minor always 2021-02-19 00:13 2022-03-31 07:26
Reporter: SadKo Platform: GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Snap to grid behaves very strange
Description: When the zoom allows snapping to grid, Ardour doesn't allow to snap.
Even if 1/16 line is seen, Ardour doesn't allow to snap to it. The same for 1/32 and 1/64.
1/8 behaves OK.
Tags:
Steps To Reproduce: Example video showing the problem
https://youtu.be/hzGkFTCaEhk
Additional Information:
System Description
Attached Files: a.png (6,187 bytes) 2021-02-22 07:31
https://tracker.ardour.org/file_download.php?file_id=3945&type=bug
b.png (8,101 bytes) 2021-02-22 07:31
https://tracker.ardour.org/file_download.php?file_id=3946&type=bug
scrot20210223212221.png (20,378 bytes) 2021-02-23 20:36
https://tracker.ardour.org/file_download.php?file_id=3947&type=bug
scrot20210223212257.png (20,412 bytes) 2021-02-23 20:36
https://tracker.ardour.org/file_download.php?file_id=3948&type=bug
Notes
(0025533)
SadKo   
2021-02-19 00:28   
Here's an example of how region dragging works

https://youtu.be/2TeLi_yHCmc
(0025534)
SadKo   
2021-02-19 00:41   
Ardour 5.12 works as expected: the playhead is snapping to grid lines (and even more)

https://www.youtube.com/watch?v=YIf8Z6p12Vg
(0025543)
sciurius   
2021-02-22 07:31   
I've been informed that Ardour6 changed the behaviour to snap only to visible grid lines, to avoid abiguity. This may have been a wise decision.

However, the algorithm for deciding when to show grid lines behaves a bit weird. It tends to place grid lines much farther apart than necessary for convenient snapping. See exhibit a, where the lines are very wide (approx 80px) and there is no way to snap at a resolution finer than a measure (even though the grid is configured for 8th notes).
Exhibit b shows how far a measure must be zoomed to get the grid lines for 8th notes, and even then the spacing between the lines (approx 45px) is excessive.

There is a preference for 'Snap' which is 25px default and can be lowered but no less than 10px. I haven't noticed any difference in grid behaviour when changing this value.
(0025544)
SadKo   
2021-02-22 14:16   
Paul and Ben at Harrison made some recent changes to Ardour code and confirmed that the problem existed.

The build 6.5.268 behaves much better now. But there are still some problems with 1/64 and 1/128 grid.
(0025545)
sciurius   
2021-02-22 17:04   
Much, much better! Fantastic!

I'll play a bit bit the snap settings to find out what their settings do.
(0025547)
sciurius   
2021-02-23 07:24   
navonwolf's message is either a mistake, or maligne. Take care.
(0025548)
sciurius   
2021-02-23 20:36   
With Ardour6.6 I get the following.
Picture 1: Grid with 1/4 note lines.
Picture 2: Same, slightly smaller, shows measure lines. I would have expected 1/2 note lines grid first, and later


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
7590 [ardour] bugs major always 2018-03-28 13:34 2022-03-31 02:15
Reporter: martinbangens Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: Maverick  
Status: new Product Version: 5.X git (version in description)  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: There is a glitch In the metronomes click when looping
Description: so when we want to use loop functionally with the metronome the click that is the first one when the loop go back to the start position again is clipped or glitched
Tags:
Steps To Reproduce: turn on the metronome, set a loop and then listen to the last click that is also the first(at the point where the loop go back to start location) that metronome click is glitched or clipped.
Additional Information:
System Description
Attached Files:
Notes
(0020247)
unfa   
2018-04-08 18:31   
(Last edited: 2018-04-08 18:33)
I also experience this, seems like the last beat is played and after a short delay - the first one is played too, so it plays 2 clicks one only one should be played.



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8895 [ardour] bugs minor always 2022-03-28 09:40 2022-03-30 21:56
Reporter: thebutant Platform: Ubuntu  
Assigned To: x42 OS: Linux  
Priority: normal OS Version: (any)  
Status: resolved Product Version: Mixbus 8.x  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Automation disappears when region is edited
Description: Editing a region (audio or midi) destroys automation curves belonging to that region.
Tags:
Steps To Reproduce: Draw automation under a region (could be volume or anything).
Change the region by moving it, resizing or other ways.
Automation is removed.
Additional Information:
System Description
Attached Files:
Notes
(0026371)
x42   
2022-03-30 21:56   
Fixed since https://github.com/ardour/ardour/commit/d841b13673a5ef2b4458accb53120047e5d458a1
will be in any upcoming Mixbus release or nightly Mixbus 8.0.29 or later


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
4981 [ardour] features tweak sometimes 2012-07-03 08:10 2022-03-30 15:27
Reporter: BenSpector Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version: 3.0  
Summary: Punch in and out produces an unpleasant click
Description: Mostly depending on the audio type present on the track, but most of the times, when punching in and out from recording, there will be a loud click.
Checked the same audio on PT, no click.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0026370)
dannyb   
2022-03-30 15:27   
This issue still exists for me and it sounds just like an xrun. It's annoying, as I don't know whether it's in the recording or not. I always have to look for the punch in marker.

I can reproduce it all the time by playing past the punch in marker with punch in enabled, produceing a static like click. Disable punch in and there is no click.

Ardour 6.9.0
"After Bach"
(rev 6.9)
Intel 64-bit

Operating System: Fedora Linux 35
KDE Plasma Version: 5.24.3
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2
Kernel Version: 5.16.17-200.fc35.x86_64 (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce GT 710/PCIe/SSE2


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8897 [ardour] bugs minor always 2022-03-29 20:11 2022-03-29 20:11
Reporter: gedobbles Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ardour crashes, when jack transport is stopped when recording midi track
Description: Ardour crashes, when jack transport is stopped when recording midi track
Tags: crash, jack, Midi, transport
Steps To Reproduce: New project
add midi track
record on midi track
start recording
stop recording (strange yellow box continues to expand in midi track)
stop jack transport
Additional Information:
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
7585 [ardour] bugs minor always 2018-03-11 12:34 2022-03-29 20:06
Reporter: jihema Platform: Linux  
Assigned To: OS: Ubuntu  
Priority: normal OS Version: 17.10  
Status: new Product Version: 5.X git (version in description)  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Jack transport crash with midi track
Description: Version 6.0.pre.0.599 (98d6fe9c9113a88766340b99a164cbec0b39217f)

Assertion failing when turning on Jack transport on a midi track.

ardour-6.0.pre0.599: ../libs/ardour/midi_buffer.cc:157: virtual void ARDOUR::MidiBuffer::merge_from(const ARDOUR::Buffer&, ARDOUR::samplecnt_t, ARDOUR::sampleoffset_t, ARDOUR::sampleoffset_t): Assertion `mbuf != this' failed.
Aborted (core dumped)
Tags:
Steps To Reproduce: New empty session, add a midi track, turn on Jack transport ("enable external positional sync").
Additional Information:
Attached Files:
Notes
(0026369)
gedobbles   
2022-03-29 20:06   
This still seems to be an issue in 6.9


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8896 [ardour] bugs minor always 2022-03-28 09:42 2022-03-28 09:42
Reporter: thebutant Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: Mixbus 8.x  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Mixer list resizes at every startup of MB32C
Description: Mixer list (the panel on the left in the mixer, the panel that shows/hides when pressing Shift+L) resizes every time MB32C v8 opens.
Tags:
Steps To Reproduce: Change the layout of the mixer panel (drag down Groups, Strips).
Reopen MB32C v8.
They are resized to default and you have to drag them into your preferred position again.
Additional Information:
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8286 [ardour] bugs minor always 2020-07-03 22:34 2022-03-27 19:40
Reporter: jeythekey Platform: Arch  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.0  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Column widths are not adjustable in editor list and plugin manager, leaving some text unreadable
Description: Currently, one can resize the view of the editor list and of the plugin manager, but the columns are fixed. Sometimes, part of the texts are unreadable this way.

Suggestion:
Allow to adjust the widths of columns by grabbing the separators in the header, especially for columns with free text. The width of columns with fixed content could be allowed to be decreased/collapsed to save space. Empty columns should be set to minimal width (e.g. as much as the header needs) and also be allowed to be collapsed.
Additionally, the automatic adjustment of column widths when increasing the view could be made more intelligent, i.e. content-aware in a priority sequence, so that the most important (e.g. the first) column becomes totally readable first and others (e.g. the path-column) afterwards etc. by further increasing the view.

Reason:
While in the regions tab of the editor list, increasing the view further increases the `Region` column, in the sources tab, it increases the (last) path-column, often leaving the text in the first (`Sources`) column unreadable. Moreover, empty columns (e.g. take ID or tags) always take a fixed amount of space, which is a waste.

Discussion here: https://discourse.ardour.org/t/import-multiple-takes/103997/32
Tags: column width, editor list, plugin manager
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0026366)
jeythekey   
2022-03-27 19:40   
I think this one is still open. Is anything done in this direction already?


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8283 [ardour] features minor always 2020-07-03 18:13 2022-03-27 19:31
Reporter: jeythekey Platform: Arch  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.0  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Polyphonic import part II: Import several takes/files at once in sequence, one track per channel
Description: Currently, several (polyphonic) files can only be imported as sequence to a single (polyphonic) track.

Suggestion:
Allow to import several polyphonic files at once in sequence to several tracks, one track per channel.
This should optionally be possible to selected existing tracks or by generating new tracks as needed (see part 1: 0008281).

Reason:
Importing several takes of a polyphonic recording session (stereo or more channels) e.g. from a mobile/field recorder should be a straightforward task, as it is a routine step for every Ardour session with material recorded/created outside of Ardour. Polyphonic tracks are not suitable for mixing etc. but currently, it is not possible to split a polyphonic track to mono-tracks, e.g. after import. Otherwise, the latter could be a workaround for this feature.

Discussion here: https://discourse.ardour.org/t/import-multiple-takes/103997/24

As a bonus, import could be made more flexible later on, e.g. by:
- allowing to select the channels to import from a polyphonic file (e.g. to omit auto-mix channels),
- allowing for custom mapping of channels to tracks, e.g. the tracks from the stereo pair to a polyphonic stereo track and all other takes to mono tracks etc. Further suggestions here: https://discourse.ardour.org/t/import-multiple-takes/103997/21
- drag-and-drop import from the import window into tracks with nice feedback of channel-track mapping or even quick'n-dirty from a normal file browser.
Tags: 6.0, Import, polyphonic, stereo
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0026364)
jeythekey   
2022-03-27 19:27   
Is there anything done in this regard already? I still think being able to seamlessly import several files/takes at once as a sequence to several (selected) mono tracks, or one after another to selected tracks (i.e. without creating new tracks for every file/import) is utterly important whenever you record on an external recorder and not directly into Ardour.

Also, one addendum: I just noted, that, unlike stated in the original report, the option to import to selected tracks also appears when selecting several files in the import window and selecting "as sequence" also for stereo-files and irrespective of how many tracks are selected. However, it always only imports one (the left?) track per file, to the track selected first, which is totally unexpected behavior and therefore likely a BUG. (I.e. this option should not occur under these circumstances until properly supporting the feature to import polyphonic/stereo files to selected tracks, IMO.)
(Corss-posting here: https://tracker.ardour.org/view.php?id=8281 because also relevant to this issue.)
(0026365)
jeythekey   
2022-03-27 19:31   
Also linking to this issue, as it might be an alternative solution/workaround: https://tracker.ardour.org/view.php?id=8284


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8281 [ardour] features minor always 2020-07-03 16:22 2022-03-27 19:26
Reporter: jeythekey Platform: Arch  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.0  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Polyphonic (and stereo) import 0000001: Import to selected tracks
Description: Currently, the option to import to selected tracks is only available for (several) mono-files. It appears as soon as the number of selected files matches the number of currently selected tracks.

Suggestion: Make this option also available for polyphonic (stereo or more) files, as soon as the number of channels in a file matches the number of selected tracks.
As an additional (independent) suggestion: Leave the option to import to selected tracks selected as long as the import window stays open (as it is the case with all other options); at least it should become selected again once the number of selected tracks matches (again) the number of selected files/channels in a selected file.

Reason: Currently, importing polyphonic files (e.g. from a mobile/field recorder) creates new tracks on every import. Importing e.g. multiple takes of a recording session therefore is tedious and requires several manual steps (moving up the regions and deleting the created tracks for every imported file/take).

There are two further workarounds, but one does not gain much in convenience:
A) Polyphonic files can first be split to mono-files, either using sox on the command line or by first importing to regions. But having many (6, 16, or even 32) mono files for every take is very prone to errors when manually selecting the files belonging to a take to import.
B) Polyphonic files can be added to (existing) polyphonic takes. However, polyphonic takes can currently not be converted to mono tracks. (It only creates mono-regions/sources in the list view, that later could be imported one by one from the sources list and then aligned.)

As discussed here: https://discourse.ardour.org/t/import-multiple-takes/103997/24?u=jeythekey
Tags: 6.0, Import, polyphonic, stereo
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0026363)
jeythekey   
2022-03-27 19:26   
Is there anything done in this regard already? I still think being able to seamlessly import several files/takes at once as a sequence to several (selected) mono tracks, or one after another to selected tracks (i.e. without creating new tracks for every file/import) is utterly important whenever you record on an external recorder and not directly into Ardour.
See also: https://tracker.ardour.org/view.php?id=8283

Also, one addendum: I just noted, that, unlike stated in the original report, the option to import to selected tracks also appears when selecting several files in the import window and selecting "as sequence" also for stereo-files and irrespective of how many tracks are selected. However, it always only imports one (the left?) track per file, to the track selected first, which is totally unexpected behavior and therefore likely a BUG. (I.e. this option should not occur under these circumstances until properly supporting the feature to import polyphonic/stereo files to selected tracks, IMO.)


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8892 [ardour] bugs minor always 2022-03-24 20:44 2022-03-24 20:44
Reporter: wargreen Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: When multiple clip are selected via tracks grouping, double click alway open the properties window of the clip on the last track
Description: With tracks grouped and the option "selection" activated, if multiple clips is selected via this group, a double-click on a selected clip in a track alway open the properties window of the clip on the last track.
Tags: Editor
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8891 [ardour] documentation minor always 2022-03-24 17:27 2022-03-24 17:27
Reporter: bmuxbeats Platform: Desktop  
Assigned To: OS: Manjaro Linux  
Priority: normal OS Version: 21.2.5  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Function 'toggle-rec-enable' in documentation Home/Control Surfaces/Generic MIDI/Generic MIDI Binding Maps not specified
Description: The function 'toggle-rec-enable' is not specified in the listing under the header "Bindings to Ardour "functions" ", but fortunately it's still available and it does what it is supposed to.
(please refer to https://manual.ardour.org/using-control-surfaces/generic-midi/midi-binding-maps/)
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8533 [ardour] features minor have not tried 2021-01-07 22:17 2022-03-10 13:59
Reporter: DonJaime Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Make it possible to edit the metronome click pattern when editing the meter
Description: One reason for bothering to set the meter is to get a metronome. As things stand the metronome click is inflexible and of variable utility: if I switch on the metronome in 3/4, 4/4 or 5/4 time, I get a reasonable, usable beat. If I switch it on in 7/8 time, I get too many clicks to follow easily unless the tempo is very relaxed. In 13/16 I just get lost.

It would be useful to be able to choose on which beats the metronome clicks.

A sensible place to make the choice would be in the "Edit Meter" dialog.
Underneath the "Lock style:" menu there could be a "Click pattern" section, with an interface similar to that of a drum machine like Hydrogen, with togglable dots on the beats that should click.

Allowing for clicks on subdivisions of beats would be useful, too, or allowing for division into arbitrary tuplets. (Yesterday I wanted to record a simple little song using the metronome, and it turned out to be mostly in 7/8 time with a quadruplet spanning the first three beats, so I ended up having to roll my own MIDI metronome with clicks on beats 1, 2.5, 4, and 6. And some bars turned out to be a quadruplet over 5/4...)
When changing meter the initial pattern should be the most recent one in the track for the meter chosen.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0026345)
al f   
2022-03-10 09:48   
Would also like to see this feature +1
(0026346)
ragnarok   
2022-03-10 13:59   
+1 I like too!


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8884 [ardour] bugs minor always 2022-02-27 19:05 2022-02-27 19:05
Reporter: graymon Platform: Intel(R) Core(TM) i7-5557U CPU  
Assigned To: OS: 5.16.10-200.fc35.x86_64  
Priority: normal OS Version: Fedora 35  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: continuous stream of recvmsg(7, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable)
Description: My system locks up regularly.


When I run strace /opt/Ardour-6.9.0/bin/ardour6

There is a constant stream of:
poll([{fd=4, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8, events=0}, {fd=5, events=POLLIN|POLLPRI}], 4, 14) = 0 (Timeout)
recvmsg(7, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(7, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=4, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8, events=0}, {fd=5, events=POLLIN|POLLPRI}], 4, 2) = 0 (Timeout)
recvmsg(7, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(7, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=4, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8, events=0}, {fd=5, events=POLLIN|POLLPRI}], 4, 23) = 0 (Timeout)
recvmsg(7, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(7, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=4, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8, events=0}, {fd=5, events=POLLIN|POLLPRI}], 4, 14) = 0 (Timeout)
recvmsg(7, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(7, {msg_namelen=0}, 0) = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=4, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8, events=0}, {fd=5, events=POLLIN|POLLPRI}], 4, 22^C) = ? ERESTART_RESTARTBLOCK (Interrupted by signal)
strace: Process 4677 detached
Tags:
Steps To Reproduce: run ardour from command line
Additional Information: I am running pipewire in F35 with everything updated.
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8882 [ardour] bugs minor always 2022-02-25 19:21 2022-02-25 19:21
Reporter: MelissaRankin Platform: Microsoft  
Assigned To: OS: Windows  
Priority: normal OS Version: 10  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Crashes at same point in playback and when exporting audio
Description: I'm new so this software and have been working on the same session for about a week now. After having a break for a few hours, all of a sudden ardour crashes at the same point every time I playback or try to export audio.

I have used and both ACE plug-ins and meld productions.
Tags: audio, crash, editing, export, playback, plugin manager
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8879 [ardour] bugs minor always 2022-02-23 15:09 2022-02-23 15:09
Reporter: Alessandro Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Cannot export mp3
Description: Export in Flac, Wav.. ok.
When i try to export session in mp3 formar the result is:
2022-02-23T16:06:23 [ERROR]: Export ended unexpectedly: Exception thrown by AudioGrapher::CmdPipeWriter<float>: Could not write data to output file
2022-02-23T16:06:23 [ERROR]: Session: cannot have two events of type TransportStateChange at the same sample (0).
2022-02-23T16:06:23 [ERROR]: Session: cannot have two events of type TransportStateChange at the same sample (3072).
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8878 [ardour] bugs minor always 2022-02-23 15:03 2022-02-23 15:03
Reporter: Alessandro Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Cannot access outside Home Volume
Description: I do have 4 partition / Volume in my drive. 1) Media=NTFS(Fuse),2)Buffer=NTFS(Fuse),3) Home(Msdos), 4)BioMarta(USB-Msdos)
Under Ardour 6.9 - the only partition/volume that i can see and then access is Home.
Under Ardour 5.1 - is possible see and access any partition/volume.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8877 [ardour] bugs minor always 2022-02-20 13:20 2022-02-20 13:20
Reporter: daniels115 Platform: Debian GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: uri for /bus/gain Master is case sensitive
Description: I wrote a midi map file for a Nektar LX25+ midi keyboard (enclosed). I have found that it was necessary to capitalize the /bus/gain uri in order to map the main slider on the keyboard to the master bus fader. The final LX25+ map file is enclosed. The issue is not specific to the Nektar LX25+ but would affect any midi map that maps a control to the master bus fader.
Tags: CC, midi_map, surface
Steps To Reproduce: This line does not work (no mapping to control):

<Binding channel="16" ctl="20" uri="/bus/gain master"/>

This line works properly:

<Binding channel="16" ctl="20" uri="/bus/gain Master"/>

Additional Information: If this is a verified bug, it will affect many of the supplied midi maps as they all appear to use the lower case identification. I'm using the latest Debian release of Ardour which is 6.5.
System Description
Attached Files: nektar_lx25.map (1,995 bytes) 2022-02-20 13:20
https://tracker.ardour.org/file_download.php?file_id=4157&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8873 [ardour] bugs minor have not tried 2022-02-07 17:29 2022-02-18 19:38
Reporter: priya2312 Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: 502 bad gateway
Description: A 502 Bad Gateway error means that the web server you connected to is acting as a proxy to relay information from another server, but received a bad response from that other server. https://www.thoughtsmag.com/502-bad-gateway/
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8875 [ardour] features minor N/A 2022-02-18 03:06 2022-02-18 03:06
Reporter: Thovthe Platform: GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Add tooltip for xrun markers.
Description: Just starting to use ardour today. I had this strange black arrow pointing at my track, went on the IRC chat to find out what is was. After a few hours and a user (Ias) asking some more informed others (but getting it not quite right) and me testing some settings they put me near. I find out it's an xrun marker. This might only be a couple lines to add a tool tip on hover that says "xrun", "xrun marker" or "xrun recording error".
Tags:
Steps To Reproduce:
Additional Information: I like the software, and appreciate what you do. It's pretty nice once you watch unfa's 30 min quick start video.
System Description
Attached Files: Screenshot_2022-02-17_23-14-41.png (3,892 bytes) 2022-02-18 03:06
https://tracker.ardour.org/file_download.php?file_id=4156&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8814 [ardour] bugs minor always 2021-10-21 21:27 2022-02-15 07:35
Reporter: OaaH Platform: Arch  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ardour Crashes with ToneLib-GFX's impulse response
Description: While using ToneLib-GFX amp simulator inside Ardour (LXVST or VST3 version), Ardour constantly crashes every time I try the plugin's built-in impulse response effects (cabinet simulators).
trying to run this plugin on Carla worked fine. The ToneLib standalone version works fine either. I have checked it under Ardour at several sampling rates (thinking that this might be a sample rate conversion issue) but it crashed on both 44.1Khz, 48Khz and 96Khz.

I also tried to load Carla as an Ardour plugin, and loading ToneLib inside Carla, but again it crashed as soon as I uploaded the cabinet simulator. It seems to crash every time it somehow goes through Ardour, and it works fine otherwise.
Tags: crash, impulse response, ToneLib, VST
Steps To Reproduce: 1) Run Ardour
2) Load ToneLib-GFX plugin (either LXVST or VST3)
3) inside ToneLib, add the plugin "guitar IRs Cab" or "IR processer"
Additional Information:
System Description
Attached Files: ardour debug (186,247 bytes) 2021-10-21 21:27
https://tracker.ardour.org/file_download.php?file_id=4119&type=bug
Notes
(0026331)
ospi   
2022-02-15 07:35   
This was a Tonelib GFX bug as version 4.7-5 released on 2022-02-14 fixes the issue with IRs.
Tonelib version 4.7-3 crashed both Ardour and Qtractor when using IRs.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8795 [ardour] features minor N/A 2021-09-10 20:14 2022-02-12 22:11
Reporter: DavidLC11 Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Implement support for ARA Audio Random Access
Description: ARA is an extension to the VST3 and AU APIs. It was as developed by Celemony, and is used by plugins such as Melodyne. The SDK is available under the Apache License, Version 2. Now that Ardour is planning to move to C++11 with the development of Ardour 7, it can be used to add support for ARA to Ardour. The ARA SDK is available on GitHub at https://github.com/Celemony/ARA_SDK
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0026137)
x42   
2021-09-10 22:07   
Yes, it is already on our ToDo list. It is amazingly well documented as well.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8850 [ardour] features minor N/A 2022-01-04 16:12 2022-02-12 12:59
Reporter: timetre Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Alesis Q49 MKII MIDI Control Surface binding file
Description: Just got this master keyboard in my setup.
The 8 control buttons can work in Mackie, HUI or MIDI mode.
Since I'm already using a Mackie control surface, I've configured my keyboard in MIDI mode and built the binding file.
Attached to this ticket
Tags: MIDI control, midi_map
Steps To Reproduce:
Additional Information:
Attached Files: Alesis_Q49v2.map (701 bytes) 2022-01-04 16:12
https://tracker.ardour.org/file_download.php?file_id=4149&type=bug
Alesis_Q49v2-2.map (733 bytes) 2022-01-06 09:00
https://tracker.ardour.org/file_download.php?file_id=4150&type=bug
Notes
(0026290)
timetre   
2022-01-06 09:00   
Actually, after using the keyboard, I ended up making some changes to the previously submitted map.
1. The Record button now starts the recording (instead of just toggling global record)
2. The button at the center of the cross is mapped to stop-and-forget-capture which I use much more when recording keyboard than toggling loop :-D
(0026317)
timetre   
2022-01-29 11:42   
Created a pull request
https://github.com/Ardour/ardour/pull/665
(0026318)
timetre   
2022-01-29 13:07   
Sorry I had messed up my git fork ...
Pull request is : https://github.com/Ardour/ardour/pull/666


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
7645 [ardour] other feature always 2018-07-07 17:47 2022-02-11 15:32
Reporter: mrnuke Platform: hax86-64  
Assigned To: OS: Fedora 28  
Priority: normal OS Version:  
Status: new Product Version: 5.12  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ardour fonts icons and buttons are too small to be usable on high density screens
Description: On displays with high pixel density the text, buttons, icons and controls of Ardour are too small to be easily readable. Even when the desktop environment is configured correctly, where other applications display controls at the cprrect size, Ardour displays these elements in a size that is too small to be seen. On high enough pixel densities (200+ DPI), the controls become unreadable to a normal human eye.

Learnability: Almost impossible to understand what the knobs do when the user can't see them.
Efficiency: -100dB -- User puts in 100 dB of work to get something done, gets out 0 dB.
Memorability: N/A
Safety: N/A
Satisfaction: The user experience is horrible (-inf dB) when knobs can't be seen.
Tags:
Steps To Reproduce: For KDE5, open System Settings -> Fonts -> [x] Force fonts DPI: 300
Log out and log back in.
Launch Ardour.
I suspect other DEs have similar knobs if they don't automatically adjust scaling based on EDID.
Additional Information: ## Expected results

On old-school screens (100-120DPI), I'd expect the buttons and knobs in Ardour to scale up in size.


## Actual results

Ardour controls stay the same size. On a 163 DPI screen, this becomes quite hard to read. On a 330 DPI screen (as shown in screenshots), this is completely unreadable.


## Additional information

The screenshots were taken on a 330DPI screen. An on-screen magnifier (x3) is included for comparison to what a normal font should look like.S
Attached Files: ardour_magnified_x3.png (147,961 bytes) 2018-07-07 17:47
https://tracker.ardour.org/file_download.php?file_id=3407&type=bug
ardour_magnified_x3_info_screen.png (82,337 bytes) 2018-07-07 17:48
https://tracker.ardour.org/file_download.php?file_id=3408&type=bug
ardour-high-res.png (73,046 bytes) 2019-01-09 11:04
https://tracker.ardour.org/file_download.php?file_id=3438&type=bug
ardour-high-res-2.png (682,852 bytes) 2019-01-09 11:04
https://tracker.ardour.org/file_download.php?file_id=3439&type=bug
Notes
(0020347)
x42   
2018-07-07 17:58   
Did you try to increase:
Ardour Preferences > Appearance > GUI and font-scaling?
(0020348)
mrnuke   
2018-07-07 18:13   
Hi x42, I did (eventually) find that setting, and there are two issue with it:

1) It's damn near impossible to read the text and navigate the menus leading to the option (remember, the fonts are unreadable on some screens)
2) It doesn't go far right enough. It becomes readable on my laptop (330 DPI), but still too small for comfort. I still get eye squints and pushing head closer to screen.

My main issue, from a UX perspective, is that the scaling should just work (TM). There's nothing wrong to allowing the user to customize the scaling. That being said, being greeted by an ant colony is poor UX.

I do however revise my "Satisfaction" estimate from -inf dB to -80 dB.
(0020568)
jo-so   
2019-01-09 11:04   
Me having the same problem. I've installed the Debian package of Ardour (5.12) and started Ardour the first time. All dialogues are utterly small on my high-resolution display (280dpi) and the worst thing is, I can't open the preferences dialogue without going through the first initialization and opening a project and all this with an unreadable screen.

Why don't you respect the setting of GDK_DPI_SCALE and GDK_SCALE?
(0020666)
teejaydub   
2019-05-25 02:27   
I see this as well, on a DELL XPS 13 with Ubuntu 18.04, screen resolution 3840 x 2160. Ardour is unusable. Tried the Ubuntu package first, then the installer downloaded from the web site; no difference. Surprising that even going to 400% screen scaling doesn't seem to affect Ardour at all.
(0026279)
x42   
2021-12-21 04:26   
Since Ardour 6, when Ardour is first started (without existing preferences) an initial scaling factor is guessed depending on the screen resolution and the first step in the "new user wizard" allows to configure the scaling factor (which can later be changed in the usual place in the preferences).

This should resolve this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8602 [ardour] bugs minor always 2021-03-03 23:50 2022-02-11 07:57
Reporter: felipeemos Platform: Arch  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Weird imported MIDI behavior
Description: I recorded a small video of the bug so you can follow up. Here's the link: https://youtu.be/goPcgEXKW7E

THE BUG
It's impossible to modify attributes from the MIDI region without unlinking them from the original file.

BUG WORKAROUND
As soon as you import the region: "Unlink region from other copies"

EXPECTED BEHAVIOR:
Any modifications that WON'T take place without first unlinking the region should:
1. Ideally not be allowed
2. Warn the user to first unlink the region to see the effects taking place

MY EXPLANATION
Imported MIDI files are linked to the original file, ok, that's good. So Ardour "thinks", perfect, I don't even have to look at what is represented in the region, I'll just use the original file at "such" and "such" timestamp...
Well, if I edit the MIDI region and Ardour keeps looking at the source file, then it simply doesn't care about my edits... and that's a BUG.

That is perfectly acceptable behavior when dealing with sound waves, because in a non-destructive editor there won't be changes in the wave form and we won't be surprised by anything. I'm almost sure this approach comes from an optimization perspective and I'm not suggesting Imported MIDI files should be unlinked from the source by default. But the way Ardour behaves right now is just confusing.
MIDI regions are expected to have this granular modification freedom, so we either allow it or explicitly tell it's not possible in the current configuration because of "Y" and "Z".

SUGGESTED FIX
Linked MIDI regions don't have any visual queue about the link ... I know it's not easy to come up with good stuff (especially about UI ), but this really could be a great start! I would be 70% less confused with this behavior if a "chain link" or something appeared in this region I had just imported.

Although this situation is similar to 2 or more MIDI regions linked together inside the project, really I think there's something so different we should give it a different name. I'd say this is a HARD LINK, because in the previous everybody who's linked together change seamlessly on any change to any of the peers, but on this imported MIDI file, the situation is hard, static, because it's impossible to change the source file!

Good, I like this concept! We just have to make editing such regions HARD too. My approach would be:

1. Every MIDI region that is linked will signal a small "linking chain" icon. Right-clicking on it maybe can even show useful information about all the regions linked together, the file they are sharing (similar to the already existing "Properties / Source" menu) and show if they are HARD or not (in other words: EDITABLE or not)

2. Every HARD LINKED MIDI region won't be editable and instead of having a default grey background will have a continuous "stripe like" texture. (Similar to those "black and yellow" stripes Police Officers use to close the bounds of a crime scene. But not "yellow", let's respect our eyes, just simple variations of the intensity of the tone of "grey" already present in the default background)

The texture and the "chain link" are good ways of signalizing the user there's something different about the region. Once the user tries to make modifications and sees they are not allowed, then it should be enough for him/her to figure it out by himself/herself that the behavior is related to the property / visual queue of such MIDI files.

Tags: editing, Import, MIDI region, UX
Steps To Reproduce: https://youtu.be/goPcgEXKW7E

Import MIDI
Edit notes or change instruments
Changes are allowed and ignored by Ardour
"Unlink region from other copies" and Ardour stops ignoring the changes and works as expected
Additional Information: This is my first bug report, I'm super opened to feedback :)
System Description
Attached Files:
Notes
(0026326)
pjd   
2022-02-10 22:12   
I'm also experiencing this with Ardour 6.9, I'm able to import midi files and play them back but any changes to the midi are shown but will not play back. The workaround I found was to save and restart ardour, my changes will then be included in playback.

Ardour 6.9 (self compiled) on Ubuntu Studio 20.04


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8869 [ardour] bugs minor have not tried 2022-02-02 22:29 2022-02-02 22:29
Reporter: rob mullender-ross Platform: Apple Macintosh  
Assigned To: OS: MacOS  
Priority: normal OS Version: 10.12 or later  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Track randomly applies VBAP Panner
Description: created a new stereo track which had VBAP panning. Can't find a way to change this to standard stereo panning (doesn't seem to be in the manual) and the track goes silent if you tray to alter the automation.
Tags: panner
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8868 [ardour] bugs minor always 2022-02-01 18:45 2022-02-01 18:45
Reporter: Maut Platform: Microsoft  
Assigned To: OS: Windows  
Priority: normal OS Version: 11  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Midi
Description: Hi there,

I am pretty happy about having EZdrummer 2 working with Ardour on Windows!

Problem: As I open EZDrummer 2 as stand-alone or Plug-In: when I draw Midi Drum Sequences into Ardour, everything is fine…but the little moments (parts of a second) at the beginning and the end of the midi sequence are cut away, so that e.g. a 17 bar drum sequence is 16, 75 bars, and the following part begins to early and of of course without the little delay between sequence 1 and sequence 2…


Tanks for your help!

Dan
Tags:
Steps To Reproduce: Copy EZDrummer Midi Tracks to Ardour
Additional Information:
System Description Windows 11
Attached Files: ec01d8778e52af89cdf9be4a897d7244fc3de233.png (51,041 bytes) 2022-02-01 18:45
https://tracker.ardour.org/file_download.php?file_id=4155&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8867 [ardour] bugs minor always 2022-01-31 22:19 2022-01-31 22:19
Reporter: kgorelov Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: Mixbus 7.x  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Deadlock while adding VCA Master track
Description: Ardour deadlocks while trying to add a "VCA Masters" track.
The GUI stops responding.

Here's a backtrace obtained in GDB:

#2 0x0000555555c52ff0 in Glib::Threads::Mutex::Lock::Lock(Glib::Threads::Mutex&) (this=0x7fffffffbb10, mutex=...)
    at /usr/include/glibmm-2.4/glibmm/threads.h:687
#3 0x00007ffff6dfc53c in ARDOUR::VCAManager::vcas[abi:cxx11]() const (this=0x555558a73000) at ../libs/ardour/vca_manager.cc:77
0000004 0x00007ffff6c4ad05 in ARDOUR::Session::get_stripables(std::__cxx11::list<boost::shared_ptr<ARDOUR::Stripable>, std::allocator<boost::shared_ptr<ARDOUR::Stripable> > >&, ARDOUR::PresentationInfo::Flag) const (this=0x555558eb8800, sl=
    std::__cxx11::list = {...}, fl=127) at ../libs/ardour/session.cc:3932
0000005 0x00007ffff6c400f8 in ARDOUR::Session::ensure_stripable_sort_order() (this=0x555558eb8800) at ../libs/ardour/session.cc:2617
#6 0x00007ffff6c5b41f in ARDOUR::Session::notify_presentation_info_change(PBD::PropertyChange const&) (this=0x555558eb8800, what_changed=...) at ../libs/ardour/session.cc:6997
...
Tags:
Steps To Reproduce: 1. From the top menu choose:
Track -> Add

2. Choose "VCA Masters" track type

3. Click the "Add and Close" button
Additional Information: [~] $ uname -r
5.4.0-91-lowlatency
[~] $ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.6 LTS"

Ardour configuration:
./waf configure --with-backends=jack,alsa,pulseaudio,dummy

System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8858 [ardour] bugs minor always 2022-01-13 13:56 2022-01-31 07:46
Reporter: johne53 Platform: Microsoft  
Assigned To: OS: Windows  
Priority: normal OS Version: 10  
Status: new Product Version: Mixbus 7.x  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Playhead problem in development code
Description: In the latest development code, the timeline's playhead can only be located sensibly if the timeline view happens to begin at zero timecode.

For example, position the timeline playhead at a high timecode (say, 10 mins). Then click on the playhead and pull it fractionally to the right. What happens here is that the playhead doesn't move forwards. In fact it immediately jumps backwards to about 15 secs timecode.
Tags:
Steps To Reproduce:
Additional Information: This was discovered in Ardour master (on Windows 10) but apparently it affects all platforms.
System Description
Attached Files: Hbo.jpg (46,965 bytes) 2022-01-31 07:46
https://tracker.ardour.org/file_download.php?file_id=4154&type=bug
Notes
(0026321)
johne53   
2022-01-30 14:15   
Not sure when this got fixed but it seems to be working again now in git master.
(0026322)
ewebseoservices   
2022-01-31 07:46   
www.help-activate.com – are not official website. Provides the latest updates on news, entertainment.
Enter Activation Code Blow Link :
======================================================

Here you can see More useful Activation links:-
https://help-activate.com/9now-au-activate/
https://help-activate.com/tntdrama-activate/
https://help-activate.com/hbonow-tvcode/
https://disneyplusbegin.launchaco.com/
https://help-activate.com/abc-activate/
https://hbonow-tvcode.com/
https://hbomax-hbomax.com/
https://hbomaxtvsigninn.com/
https://amazon-amazonmytv.com/
https://amzon-mytv.com/
https://amc-activate.com
https://help-activate.com/nick-jr-activate/
https://amazntv.com/
https://help-activate.com/epicgames-activate/
https://a2amazonmytv.com/
https://help-activate.com/hbomaxtvsignin/
https://youtube-activation.com/
https://hulu-activte.com/
https://hulu-activates.com/
https://hulu-comhulu.com/
https://www.tubitv-activate.com/
https://help-activate.com/tubitv-activate/


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8866 [ardour] features minor N/A 2022-01-29 10:18 2022-01-29 10:23
Reporter: timetre Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Visualize the names of the tracks currently managed by Control Surface bank
Description: As discussed in this thread on the forum https://discourse.ardour.org/t/control-surface-banks-not-visually-recognisable/87918/5

Would it be an idea to offer the option to replace or add below the Editor Summary a simple view of the names of the n tracks currently controlled by the Control Surface ?

Mock for my CS that has 8 channels attached

Note that instead of being in the Editor, it could be at the bottom of the Mixer if it makes more sense.

I can imagine that if one has several CS, you might need to configure which CS banking is being shown.
Tags: control surface, mackie, Mackie control, MIDI control
Steps To Reproduce:
Additional Information:
Attached Files: cd4489eb2693077e5defd28fe87499c2e5436f59.jpeg (506,792 bytes) 2022-01-29 10:18
https://tracker.ardour.org/file_download.php?file_id=4153&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
6898 [ardour] bugs block have not tried 2016-06-18 08:14 2022-01-28 17:08
Reporter: aeLiXihr Platform: KX studio  
Assigned To: OS: GNU/Linux  
Priority: normal OS Version: KXStudio 14.04.2  
Status: confirmed Product Version: 5.12  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: ardour freezes during clean-up
Description: KXStudio 14.04.2 LTS - Release amd64

Dear all,
i have had a problem with Clean-up for a while:
If i go to Session>Clean-up>Clean-up Unused Sources...>Clean-up nothing happens. The popup below does not appear http://robin.linuxaudio.org/tmp/cleanup.png
Ardour freezes and if i try to close Ardour it takes a while and an "Ardour is not responding"screen pops up.

I ran in gdb and that is here: http://pastebin.com/7zETEQGS
If you tell me how i would attach my session file as well.

I found out: if i try to uncombine the first compounds from Droomvlucht-solo(@ 07:13:21:08, tracks: "gitaar-room" and "gitaar" ) they are deleted.

(i have the original session file(without -3001) too but it cannot be attached?, pressing browse nothing happens)
nb: i hope i filled in everything correctly: any questions, just ask please :)
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files: rommelen-3001.ardour (3,988,339 bytes) 2016-06-18 08:14
https://tracker.ardour.org/file_download.php?file_id=2969&type=bug
rommelen.ardour (3,988,339 bytes) 2016-06-18 09:47
https://tracker.ardour.org/file_download.php?file_id=2970&type=bug
Ardour-5.12.bug6898.trace.tar.xz (3,346,648 bytes) 2018-01-13 13:00
https://tracker.ardour.org/file_download.php?file_id=3357&type=bug
Winter_ARD_REC_007.rar (140,412 bytes) 2020-07-29 08:31
https://tracker.ardour.org/file_download.php?file_id=3791&type=bug
Notes
(0020109)
aeLiXihr   
2017-12-22 12:37   
the issue persists in Ardour 5.12
(0020114)
timbyr   
2018-01-11 13:07   
I can reproduce the freezing issue with cleanup sources and the Session you have attached with 5.12

Based on the gdb backtrace you have referenced and the comment in SessionPlaylist::source_use_count () there may be circular references between compound regions and this is causing an infinite loop/freeze.

Thanks for taking the time to report this and attaching a Session that can be used to reproduce the issue.
(0020115)
timbyr   
2018-01-13 13:00   
I've attached a trace that can be loaded in chrome://tracing that shows the function calls occurring with this session when calling Session::cleanup(At least the first few seconds before I have to interrupt the process so as to not write too large a trace file).

It indicates that the amount of deep nesting (8-9 levels at least) of compound regions in combination with the number of sources in this session may be causing the freezing as in the trace it is still processing the first source out of 0000109:0000400 after 4 seconds.

I'm unsure that the freeze is actually infinite at this point and how there can be circular references.

It does definitely indicate that another method of processing the sources to determine which ones can be "cleaned up" is perhaps needed.

It seems like a method in which each snapshot is loaded and then determining unused sources based on the reference count of the source would much quicker, or possibly just something like storing the Source reference count in a property of the Source on save and using that instead.
(0024848)
Hans Flikkema   
2020-07-29 08:05   
Hi, I want to add that freezing when trying to clean up still happens using Ardour 6.2. It always happens after a longer cut and paste session on for instance 5 recorded Vocals tracks or setting a bass drum track on time.
After that I consolidate those tracks and then I want to clean up and then is when it all goes wrong. When it freezes while cleaning up (selecting clean up unused sources). The project still can be re-opened again but only increases in size. So after this happening the session gets useless. Exporting track is the only options and you loose all mixing, bussing, and track plugin settings.

I did some research and found out it has nothing to do with which audio files are in the audio folder or even which tracks are in the project. Even after deleting all tracks in that pariticular project, is still freezes after clicking remove all unused sources. So it must be some corruption in the "projectname.ardour" file.

I still have a spare copy of one of these crashed projects. If someone wants to examine it i can load it up.
(0024849)
Hans Flikkema   
2020-07-29 08:14   
Crashing when try to clean up unused sources
Platform W10 Home 2004
Ardour 6.2
(0024850)
Hans Flikkema   
2020-07-29 08:16   
Refering to 0024848
Crashing when try to clean up unused sources
Platform W10 Home 2004
Ardour 6.2
Projectfile without audio tracks
(0024851)
Hans Flikkema   
2020-07-29 08:31   
Refering to 0024848 (excusing for repeating this but the file won't load up)
Is there a work around to recover from this project. Deleting all PEAK files didn't solve the problem either?
Is the a way to prevent this happening. would it help if I clean up more frequently?
(0026316)
chance_favre   
2022-01-28 17:08   
Crashing when try to clean up unused sources
Platform Windows 10
Ardour 6.9

Also, clean up of regions or writing to the session file may be involved? With simple projects, after I clean up regions, the number of <Region name=...> XML nodes matches the number of regions displayed in the Editor List. However, in one recent project that has a number of edits in it, the Editor List shows 24 regions after cleanup, but the session file has 2100+ <Region name=...> XML nodes. Maybe that is relevant.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8864 [ardour] bugs minor always 2022-01-21 20:35 2022-01-21 22:47
Reporter: SanbornFan Platform: Apple Macintosh  
Assigned To: OS: MacOS  
Priority: normal OS Version: 10.12 or later  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: macOS VST2 plugin wrapper offsets gui by few pixels in both x and y directions so right side and bottom edge are chopped off
Description: macOS VST2 plugin wrapper offsets gui by few pixels in both x and y directions. Since the wrapper is sized exactly to fit the plugin then the right side and bottom edge are truncated.

This is not consistent with VST3 and AU plugin wrappers where gui is positioned correctly at 0,0
Windows and Linux versions are also correct. It is only macOS VST2 wrapper that has the problem.

Call to gtk_widget_translate_coordinates appears to be offsetting 8 units(pixels?) in x direction and 6 in y direction
file: mac_vst_plugin_ui.mm line: 212
void
MacVSTPluginUI::lower_box_size_allocate (Gtk::Allocation& allocation)
{
    gint xx, yy;
    gtk_widget_translate_coordinates(
            GTK_WIDGET(low_box.gobj()),
            GTK_WIDGET(low_box.get_parent()->gobj()),
            8, 6, &xx, &yy);
    [_ns_view setFrame:NSMakeRect (xx, yy, allocation.get_width (), allocation.get_height ())];
    NSArray* subviews = [_ns_view subviews];
    for (unsigned long i = 0; i < [subviews count]; ++i) {
        NSView* subview = [subviews objectAtIndex:i];
        [subview setFrame:NSMakeRect (0, 0, allocation.get_width (), allocation.get_height ())];
        break; /* only resize first subview */
    }
}
Tags:
Steps To Reproduce: Open a VST2 plugin such as LennarDigital Sylenth1. Drag the right side and bottom edge of the wrapper window to reveal missing pixels.
Additional Information:
System Description
Attached Files:
Notes
(0026310)
x42   
2022-01-21 22:47   
This dates back to https://github.com/Ardour/ardour/commit/5b28e0bc6fa036464a3f4cf13300819f805d39d4
spacing corresponds to the container (box) spacing. Chances are that those have changed since...


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8390 [ardour] other minor always 2020-08-31 20:10 2022-01-20 20:21
Reporter: unfa Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 6.2  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ardour comes bundled with proprietary software and plug-in demo versions
Description: I've talked about this before, but I guess it got lost, so I'm bringing it up again.

1. Ardour for Linux comes bundled with proprietary Harrison GUIs for some of the stock Ardour plug-ins.

I think the GUIs are nice and all, but I run Ardour *specifically* because it's free software, and I just don't want to have it served with proprietary binary code that I have no idea what is doing.

I'd be most happy to see the Harrison GUIs be open-sourced as contribution to Ardour, but I don't expect that.

Since that's the case, I want to be able to have Ardour install without any proprietary plug-ins or plug-in GUIs.
And since Ardour's big selling point is the open-source nature of the project, I'd rather have these as opt-in than opt-out.
I guess the unofficial builds available in various Linux distributions will come without them, but I'd like to not be forced to use these to get a 100% free-software package.

2. Ardour for Windows comes bundled with demo versions of proprietary Harrison plug-ins.
I guess Windows users aren't complaining about it, but honestly this is nothing more than an annoying advertisement for Harrison software - these plug-in are near useless unless the user purchases a license. The Harrison plug-in GUIs are at least fully functional. I think it'd be best to get rid of this stuff, or at least provide an opt-out during installation. Or better: an opt-in.

3. There's also useless demo versions of paid x42 plug-ins bundled, which at least are free software, but still this is shovelware, becasue they are useless unless the user purchases a license.

I have nothing against paid FOSS plug-ins, and I think the x42 plug-ins are of great quality, but I'd highly prefer if Ardour bundled only fully functional plug-ins, not placeholders asking for a license.

---

One of the first things I do on any fresh Ardour installation on Windows is to mark all the useless demo plug-ins as hidden. This doesn't create a good user experience where 90% of the stock plug-ins turn out to be just cardboard cut-outs asking for more money (the user has already paid *something* to get the Windows build of Ardour).

I know this is done to help fund Ardour's development and support it's creators (x42 plug-ins etc.) and you probably have a deal with Harrison to bundle their demo versions, but it's not looking good for the users, especially those who are sensitive to software freedom.

Please provide users with a choice to *not* install proprietary GUIs or demo versions of plug-ins with Ardour.
Instead - please consider bundling fully functional plug-ins like x42 MIDI Filters, x42 DPL, x42 Tuna and x42 Autotune - these would greatly compliment Ardour's stock plug-in set and give users a better experience.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0024994)
x42   
2020-08-31 21:10   
> And since Ardour's big selling point is the open-source nature of the project

https://discourse.ardour.org/t/is-open-source-a-diversion-from-what-users-really-want/102665

> and you probably have a deal with Harrison to bundle their demo versions

Only an agreement that we can legally do so. We're glad that Harrison allows those to be bundled.
The main benefit here is that you can load sessions of other using the plugins -- the limitation is only the custom plugin GUI. The DSP is excellent, generally better than free software alternatives and you get it gratis. Even the generic UI works and they're even using a libre standard (LV2), I wish more plugin vendors would follow their lead.

No DRM. No hardware keys, no demo noise. -- I honesty think we should promote this and get more companies to ship cross-platform plugins in similar fashion if they cannot release the software under a free/libre license.

The only reason to not want them is a purism, and I found that best approach is to let those guys weed out files not matching their ideology themselves. Really, they should not trust us in the first place even if we add an opt in/out. :)
(0024995)
x42   
2020-08-31 21:12   
> I know this is done to help fund Ardour's development and support it's creators

Actually that's not the reason.
The plugins were added for user's convenience, because users asked if we we can include the plugins that are bundled with Mixbus also with Ardour.
(0024996)
unfa   
2020-08-31 22:35   
Thanks for clearing this up. I'm gonna read up on Paul's post later as it's quite a lengthy read.

It seems my assumption that the main drive for these plug-ins / GUIs to be included was upselling or product cross-promotion was wrong. And I am glad to be proven wrong there.

I know most users will not complain about it, or even notice - but for people like me who have decided on principle to run as little proprietary software as possible - this is a bummer.
Yes, we can dig files up, ask around and delete what we don't want after the installation, or just depend on unofficial builds where package maintainers have stripped this out for us.
Yet - it's not convenient and it's creating a suboptimal experience for a certain group of Ardour users if they choose to use official Ardour binaries.
I'd expect these should give the best possible experience to all users, shouldn't they?

It's not far away to say "if you don't like that just make your own build" - and it's not reasonable to expect regular users to be able to jump such hoops. And digging into program files to weed out proprietary plug-in binaries is far beyond the reach of an average non-savvy user. Should these people be forced to use proprietary software when they download Ardour (and open a-EQ), when it's advertised as a free/libre program? It's a bit misleading and I am surprised nobody has raised this issue before me.

I understand that it wasn't done viciously, but I think a clear information and a checkbox or two in the installer would go a long way here.

[ x ] Install additional open-source x42 plug-in demo versions
[ x ] Install additional proprietary Harrison plug-in demo versions

What do you think?
(0025022)
jumase   
2020-09-09 19:44   
I started using Ardour mainly as a political/ethical reason -political in an general/wide/'ancient' sense: politike techne, how we (want to) treat each other on a community. I was taught audio processing on an institution using proprietary software, but I wanted to prove (myself) I could be able to perform similar tasks with a more politically committed software.

And I see it's a difficult topic what Paul posted. I couldn't contribute as a developer as I don't know any program language. As far as I can get is reporting bugs, supporting as I can, spreading among my contacts, learning how to use the software and using it. I think that we all are influenced by conservative ideas (we are born in between them) so there are great chances that we get more "advices" to do it the way it is supposed to (as many users would ask too, mainly in DAW stuff). I know you know that, otherwise you wouldn't keep working on the projects and wouldn't have written all those post stating your point of view.

On the other hand, what you call "gratis" (in term of money), is not in other aspects. For example, the company is getting advertising as an exchange (the logo is there and I guess you could not remove it). Is it necessary to apply the proprietary GUI on Ardour's native plugins? I don't understand how is that allowing to load sessions that use Mixbus plugins; or I got it wrong?

We do put trust in many projects, not only Ardour. A community is based on trust, any relation is based on trust. And one obviously get some clues, judge, pre-judge, based on what others do... Think about food: there's a long chain that's imposible to be verified by 'external' people.

I agree that there would be fair not to include proprietary software by default, and a good approach could be what unfa proposes about extra demo plugins. And what about native plugins (a-EQ, a-Compressor, a-Delay)? Why do they have to use Mixbus GUI?
(0025023)
jumase   
2020-09-09 23:52   
>best approach is to let those guys weed out files

Sorry, never thought you were being literal :)
(0025024)
x42   
2020-09-10 00:01   
just delete the LV2/Harrison.lv2 folder
(0025025)
x42   
2020-09-10 00:03   
> And what about native plugins (a-EQ, a-Compressor, a-Delay)? Why do they have to use Mixbus GUI?

The LV2 plugin standard allows separate 3rd party GUIs for any plugin. In the last 3 years nobody stepped up and provided commercial-quality cross-platform UIs.
Ben at Harrison eventually volunteered to make some (a-eq is done, the others are functional but still being worked on).

If someone creates a better GUI, we'll happily ship that instead.

The goal of the Ardour bundles from ardour.org/download is to create a good out-of-the-box experience for typical users.
(0025026)
jumase   
2020-09-10 17:51   
I see the point, thanks for clarifying.
(0025082)
x42   
2020-09-29 18:34   
I forgot to follow up, but since Sep/10 the windows installer allows to opt-out of installing the Harrison plugins.
I hope this concludes this issue.
(0025083)
x42   
2020-09-29 18:34   
Addressed in 6.3-8-gf61ecae4b2
(0025084)
unfa   
2020-09-29 23:32   
Thanks! What about the Linux installers? Do they provide a choice too?
(0025085)
x42   
2020-09-30 01:04   
For GNU/Linux, 6.3 installers already offer to opt-out (that was changed in 6.2-201-g81fb723561; August/21).

macOS does not have an installer, so we cannot change this there.
(0025087)
unfa   
2020-09-30 09:22   
Thanks! I'll check this out and let known if I see any issues.

I guess for MacOS a solution could be to provide two packages - one with and one without the proprietary components?
(0025099)
unfa   
2020-10-02 11:18   
I've just got a development build and intalled it - it didn't ask about the proprietary plug-ins, and just installed them as usual:

$ pwd
/opt/Ardour-6.3.123/lib/LV2
[unfa@unfa-desktop LV2]$ ls
a-comp.lv2 a-delay.lv2 a-eq.lv2 a-exp.lv2 a-fluidsynth.lv2 a-reverb.lv2 gmsynth.lv2 Harrison.lv2 reasonablesynth.lv2

Here's the installer output:

$ ./Ardour-6.3.123-x86_64-gcc5.run
Verifying archive integrity... 100% All good.
Uncompressing Ardour 100%

Welcome to the Ardour installer

Ardour will be installed for user unfa in /opt

[sudo] password for unfa:
Fri Oct 2 01:13:54 PM CEST 2020
Architecture is x86_64
Checking for required disk space
Bundle is on tmpfs filesystem
Unpacking bundle for x86_64
Bundle unpacked

Checking system libs to see if they are compatible with Ardour.


Found existing Ardour installation.
Do you want to run the uninstaller /opt/Ardour-5.12.0.uninstall.sh ? [y/n]: n

Found existing Ardour installation.
Do you want to run the uninstaller /opt/Ardour-6.3.0.uninstall.sh ? [y/n]: n

Found existing Ardour installation.
Do you want to run the uninstaller /opt/Ardour-6.3.55.uninstall.sh ? [y/n]: n

Installing Ardour 6.3.123 in /opt

Adding Ardour to the applications menu

Creating a desktop link for Ardour in /home/unfa/Desktop

Copying uninstall script to /opt


Creating link Ardour6 in /usr/local/bin


Checking to see if Jack is installed

Jack already present

Jack Version Check OK (jackdmp version 1.9.14 tmpdir /dev/shm protocol 8)

which: no qjackctl in (/home/unfa/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/var/lib/flatpak/exports/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl)

The program QjackCtl is missing from this system.
QjackCtl is an extremely useful tool for any system that runs JACK applications like Ardour.
We recommend that you install it.

Install QjackCtl using system software repository? [y/n]: n

Cleaning up

!!! Install Complete !!!

Press ENTER to exit installer:
(0025100)
x42   
2020-10-02 11:59   
Oh dear, I've screwed up the path (missing `lib/`), thanks for catching that.

Fixed in https://github.com/Ardour/ardour/commit/e2639a1a588b8f75b101eb48bb717b78dabee7e3
(0025128)
unfa   
2020-10-18 15:08   
Allright, I've tested this and the proprietary plug-in opt-out works - thanks!

I haven't tested a Windows build and the x42 demo versions - what about these?

What do you think about bundling the free x42 plug-ins instead?
These would provide great value to users, and do not require any payment.
I think they'd greatly compliment Ardour's stock plug-in set.
(0025129)
x42   
2020-10-18 15:13   
While they're free-software the ready-to-run x42 binaries are commercial. Probably not what you'd expect either.
(0025131)
unfa   
2020-10-18 19:39   
Yes, but there's a bunch of "free" (no cost) ones as well listed here:
https://x42-plugins.com/x42/
Digital Peak Limiter, Autotune, setBfree and more - what about these?
(0025132)
x42   
2020-10-18 20:39   
I prefer not to tie release cycles of those plugins with Ardour releases.
5.12 -> 6.0 was 2 1/2 years without an ardour release, while at the same time there have been 16 x42-plugins releases.

And where would we stop? Bundle LSP, or DPF plugins?

Ardour's philosophy is to remain as neutral as reasonable and leave coloring DSP out (as opposed to Mixbus which focuses on a given sound character).
One thing I would be interested in is adding a few more a-*/ACE-* plugins that have tight integration in a matter that plugins otherwise cannot provide.
e.g. build-in noise-repellant, right-click on a region -> analyze and remove noise faster than realtime.
(0025147)
soundguy30   
2020-10-24 07:35   
Ardour should maybe have a build version that is just free open source version no other plugins from 3rd parties.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8128 [ardour] bugs minor always 2020-05-20 06:40 2022-01-20 14:55
Reporter: CTS Platform: Apple Macintosh  
Assigned To: OS: macOS  
Priority: normal OS Version: 10.15.4  
Status: new Product Version: 6.0-pre1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: First note of MIDI clip not visible in UI
Description: Seems like MIDI notes can disappear from the UI when the leading edge of the MIDI region is adjusted to touch note onsets. The notes do still sound however, so they are still there and audio is behaving correctly.
Tags: Midi
Steps To Reproduce: 1. Create empty MIDI region
2. Draw some notes on the grid
3. Adjust start of MIDI region until it touches the beginning of a MIDI note (both region edge & note onset snapped to the grid)
Additional Information: Version is 6.0.rc1.371
Attached Files:
Notes
(0024212)
CTS   
2020-05-20 06:45   
Update. In some instances the note no longer sounds after it disappears in the UI. I am seeing both behaviors - sometimes notes DO sound and are invisible and sometimes they neither sound nor are visible.
(0024263)
CTS   
2020-05-24 23:02   
After a bit more examination and looking at other issues, I think this is just another symptom of issue 7947. Looks like sometimes MIDI notes get microshifted forwards and backwards in various scenarios and quantization/snapping only moves notes to some offset compared to the grid.

In my case, it seems like MIDI notes that had been shifted forwards slightly were being removed when the region start snapped to the grid, which is expected since the note onset occurs before the snap point.
(0026282)
bartart3d   
2021-12-27 19:44   
In my case here, I imported a midi file, created with Musescore, I split the region with the cut tool.
Consistently all notes at the starting edge of split regions disappear.

Running Ardour 6.9, rev 6.9~ds0-1 on Ubuntustudio 21.10
(0026305)
hoadao3493   
2022-01-20 14:55   
Your article is very good and useful, thank you for sharing, https://mig8.asia hopes that next time you will have more good articles to send to all readers.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8861 [ardour] bugs minor always 2022-01-15 15:00 2022-01-15 15:00
Reporter: 12strings2hands Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: “No Align” warning initiated in error
Description: The “No Align” warning will appear by connecting the output of a track to a buss and also connect the track output to a hardware output (keep it all either L or R to reproduce).
Example:
 mono Track 1 left side goes to left side of mono buss 1.
“No Align” will blink on if you also attempt to send Track 1 left side to any hardware output left side.
I don’t think this should raise an error but it does.
Tags: feedback, workflow
Steps To Reproduce: The “No Align” warning will appear by connecting the output of a track to a buss and also connect the track output to a hardware output (keep it all either L or R to reproduce).
Additional Information:
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8860 [ardour] bugs minor have not tried 2022-01-14 17:24 2022-01-14 19:55
Reporter: imstre Platform: Microsoft  
Assigned To: OS: Windows  
Priority: normal OS Version: 7  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: ardour 7 does not start
Description: does not start(
Tags:
Steps To Reproduce: open ardour7
Additional Information:
System Description
Attached Files: Ardour.png (131,241 bytes) 2022-01-14 17:24
https://tracker.ardour.org/file_download.php?file_id=4151&type=bug
Notes
(0026297)
x42   
2022-01-14 17:42   
That "Microsoft Visual C++" error is weird.
Ardour does not use MSVC, nor require or involved anything from "Microsoft Visual C++".

I have no explanation what could lead to this.
Perhaps some [VST] plugin, or maybe some Antivirus tool?
(0026298)
x42   
2022-01-14 17:59   
Those icon warnings are also a mystery.

Have you installed Ardour to the C:\ drive?
(0026299)
imstre   
2022-01-14 19:44   
"Have you installed Ardour to the C:\ drive?" - Yes in C:\Program Files\Ardour7
With 5 or 6 any version has never had tha.

"Perhaps some [VST] plugin, or maybe some Antivirus tool?" no, heavily and newly installed.
with version 7 I always get this error
I thought maybe you'll fix it
but I see no
(0026300)
imstre   
2022-01-14 19:46   
mistake because I don't have that much chanel input..
version 6.9 great works
(0026301)
imstre   
2022-01-14 19:47   
i don't use antivirus
(0026302)
x42   
2022-01-14 19:48   
There is not version 7, yet. Latest release is 6.9, and that is known to work on Windows.
Also current pre-alpha release runs on windows, albeit with many other issues e.g, https://tracker.ardour.org/view.php?id=8859
(0026303)
imstre   
2022-01-14 19:53   
I about that it as a new version (7.0-pre0) - 263.76 MiB v7.0-pre0-1764 2022-01-14
Sha1: 1a425ea5c4514bf802f928cc519ec5ba8b2f919a
6.9 works great for my
(0026304)
imstre   
2022-01-14 19:55   
I realized I wasn’t reporting :)


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8857 [ardour] bugs minor always 2022-01-11 09:02 2022-01-11 12:18
Reporter: wmbm Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Gridlines not visible for 1/16 or smaller without snap on
Description: Unsure whether this is a bug or a feature, but I have noticed that the gridlines are not visible for 1/16 note or smaller (1/32, etc.)

If I am doing some sort of manual timing correction of live recordings this can be somewhat time consuming to go back and forth between snap on / snap off to view the gridlines and then turn them off to be able to adjust the live recording accordingly.
Tags:
Steps To Reproduce: Set gridline mode to 1/16 [or 1/32] without snap on
Additional Information:
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8751 [ardour] bugs minor always 2021-06-19 18:07 2022-01-11 12:18
Reporter: jumase Platform: Debian GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.7  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ruler is displayed wrongly when snap is not activated
Description: When changing from 1/8 (or bigger) to 1/16 (or smaller) grids, the ruler always shows 1/8, regardless of which value you choose. If you _previously_ activate snap, then it behaves correctly -if you select 1/16 it shows fifteen lines between bar lines included the reference numbers (beats and ticks). However, if you firstly select, for example, 1/16 and then activate "snap", the ruler doesn't diplay that resolution. So you have to set a greater value and then go back to 1/16 in order to get the right ruler.

Expected behaviour: ruler always displays the selected grid value, no matter if "snap" is on or off.
Tags:
Steps To Reproduce: 1. Turn snap off
2. Select 1/8 (or bigger) grid
3. Change to 1/16 (or smaller) grid
4. The ruler always shows 1/8, instead of 1/16 (or the smaller grid you have chosen)
Additional Information: It doesn't matter which mode you use. I've also tried changing "General Snap options" in preference, but it didn't seem to affect this behaviour.

I tried this on 6.7.187, 6.7.0 and 6.6.0 versions.
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8856 [ardour] bugs minor always 2022-01-09 22:06 2022-01-09 22:44
Reporter: remi.thebault@gmail.com Platform: Arch  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Websockets roll off relocates to previous position
Description: When stopping transport with the websocket API, the transport always relocates to where it was before roll start.

The bug is hit:
 - if starting transport from websocket and stopping transport from websockets.
 - if starting transport from Ardour UI and stopping transport from websockets.

The bug is not hit when stopping transport from Ardour UI, even if it was started from the websockets.
Tags: websockets
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0026293)
remi.thebault@gmail.com   
2022-01-09 22:44   
https://github.com/Ardour/ardour/pull/660


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8852 [ardour] bugs minor always 2022-01-04 20:17 2022-01-06 09:05
Reporter: JonnyMako Platform: Arch  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Crash using Pipewire/Jack and playing audio at 2x
Description: With Ardour running via Pipewire Jack, when I play youtube at 2x on my Firefox browser, after a certain amount of time, Ardour crashes.
Tags:
Steps To Reproduce: 1. Run Ardour using Pipewire Jack
2. Open Firefox and let any Youtube video run at 2x
3. After some time (sometimes in minutes sometimes upto an hour), Ardour crashes
Additional Information: #0 0x00007f85b0ce8cbb in () at /usr/lib/pipewire-0.3/jack/libjack.so.0
0000001 0x00007f85b268e535 in msort_with_tmp.part () at /usr/lib/libc.so.6
#2 0x00007f85b268e4c2 in msort_with_tmp.part () at /usr/lib/libc.so.6
#3 0x00007f85b268e4c2 in msort_with_tmp.part () at /usr/lib/libc.so.6
0000004 0x00007f85b268e4c2 in msort_with_tmp.part () at /usr/lib/libc.so.6
0000005 0x00007f85b268e4c2 in msort_with_tmp.part () at /usr/lib/libc.so.6
#6 0x00007f85b268e4c2 in msort_with_tmp.part () at /usr/lib/libc.so.6
#7 0x00007f85b268e88a in qsort_r () at /usr/lib/libc.so.6
0000008 0x00007f85b0cef4c2 in jack_get_ports () at /usr/lib/pipewire-0.3/jack/libjack.so.0
0000009 0x00007f85a5cc5fb8 in ARDOUR::JACKAudioBackend::get_ports(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, ARDOUR::DataType, ARDOUR::PortFlags, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >&) const ()
    at /usr/lib/ardour6/backends/libjack_audiobackend.so
0000010 0x000055d6c263fa75 in ()
0000011 0x000055d6c235c115 in ()
0000012 0x000055d6c264f36b in ()
0000013 0x00007f85b4179798 in AbstractUI<Gtkmm2ext::UIRequest>::handle_ui_requests() () at /usr/lib/ardour6/libgtkmm2ext.so.0
0000014 0x00007f85b409ec1f in BaseUI::request_handler(Glib::IOCondition) () at /usr/lib/ardour6/libpbd.so.4
#15 0x00007f85b40aa557 in cross_thread_channel_call_receive_slot(_GIOChannel*, GIOCondition, void*) () at /usr/lib/ardour6/libpbd.so.4
0000016 0x00007f85b3e35435 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
#17 0x00007f85b3e897b9 in () at /usr/lib/libglib-2.0.so.0
0000018 0x00007f85b3e34ab3 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0
0000019 0x00007f85b3aaf9fe in gtk_main () at /usr/lib/libgtk-x11-2.0.so.0
0000020 0x00007f85b4171649 in Gtkmm2ext::UI::run(Receiver&) () at /usr/lib/ardour6/libgtkmm2ext.so.0
0000021 0x000055d6c1f7a1ba in main ()
System Description
Attached Files:
Notes
(0026291)
x42   
2022-01-06 09:05   
Rule#1: If it does not crash when using JACK (not Pipewire's emulation thereof), then it is a Pipewire bug.

This particular issue (jack_get_ports) should already fixed in pipewire/git


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8851 [ardour] bugs minor have not tried 2022-01-04 18:21 2022-01-05 17:17
Reporter: Jimno Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: changing the buffer size affect my automations position!
Description: I started a project, recorded the full song at 48kHz 256 buffsize everything went well, I closed that project. the next day I opend qjackctl changed the buffer size to 512 (AND SAME SAMPLE RATE) to mix it with less DSP load and used some automations. One day after I needed more buffer size so that it can handle all the plugins I used last time so switched to 1024 (AND SAME SAMPLE RATE) and here begins the weird part, I noticed that my automations have moved! thought that was only on my output though when I exported that, the automation process felt delayed and bad...
Tags:
Steps To Reproduce:
Additional Information: someone told me to re-open the session on the same amount of buffer size when I first created those automations and it felt okay
(no delay) the real problem is: I tried to live with that but DSP load was high when I created the automations, now I must mix the song on 512 with high DSP and its hard!
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8854 [ardour] bugs minor always 2022-01-05 17:13 2022-01-05 17:13
Reporter: Jimno Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: changing the buffer size affects my automations position!
Description: I started a project, recorded the full song at 48kHz 256 buffsize everything went well, I closed that project. the next day I opend qjackctl changed the buffer size to 512 (AND SAME SAMPLE RATE) to mix it with less DSP load and used some automations. One day after I needed more buffer size so that it can handle all the plugins I used last time so switched to 1024 (AND SAME SAMPLE RATE) and here begins the weird part, I noticed that my automations have moved! thought that was only on my output though when I exported that, the automation process felt delayed and bad...
Tags: automation
Steps To Reproduce: I just open ardour at a specific buffersize using qjackctl (example: 256)
make some automations (very accurate ones)
save the project.
open qjackctl again change the buffer size (example 2048)
open the project on ardour again and listen
the automation lines will feel late (sonically speaking)
Additional Information: someone told me to re-open the session on the same amount of buffer size when I first created those automations and it felt okay
(no delay) the real problem is: I tried to live with that but DSP load was high when I created the automations, now I must mix the song on 512 with high DSP and its hard!
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8853 [ardour] features minor have not tried 2022-01-05 15:53 2022-01-05 15:53
Reporter: victorvianna Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: [feature request] Porting to the web with WebAssembly
Description: Photoshop got recently ported to the web via a joint effort of Google and Adobe.
https://web.dev/ps-on-the-web/
It would be awesome if we could do the same for Ardour.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8790 [ardour] bugs minor always 2021-08-31 02:03 2022-01-05 11:11
Reporter: dean48 Platform: Microsoft  
Assigned To: paul OS: Windows  
Priority: normal OS Version: 10  
Status: confirmed Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Using automation with arturia pigments changes pitch
Description: When I use Pigments 3 synth and use the sequencer, If I assign automation to a parameter or macro such as the decay envelope the notes unpredictably shift key/pitch when using automation. The sequence also plays when a note isn’t being played.
Tags: 6.8
Steps To Reproduce: 1. Open ardour
2. Open pigments 3 synth
3. Use a sequencer preset on pigments
4. Enter a single long note into ardour
5. Use automation to change macros in pigments 3
6. Notes become unpredictable and don't follow the sequence set up in pigments 3
Additional Information: Pigments 3 has free demo available here https://www.arturia.com/products/analog-classics/pigments/overview#en

This link shows the issue: https://youtu.be/L7zuFijfVPw
System Description
Attached Files:
Notes
(0026128)
paul   
2021-08-31 02:48   
confirmed fixed in 6.9 by reporter via forums. https://discourse.ardour.org/t/using-automation-with-arturia-pigments-changes-pitch/106334/10
(0026205)
anonymous   
2021-10-30 02:04   
Issue has been closed automatically, by Trigger Close Plugin.
Feel free to re-open with additional information if you think the issue is not resolved.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8849 [ardour] features minor N/A 2022-01-04 08:23 2022-01-04 14:23
Reporter: timetre Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Allow more than 32 Editor Action Scripts
Description: Today, 32 Editor Action Scripts can be registered to allow triggering LUA scripts.
While this is more than reasonable when these actions are triggered via the UI/keyboard, the fact that these actions can also be triggered via OSC offers HUGE possibilities to optimize one's workflow and I find myself having reached that 32 limit already.

If this is an arbitrary limitation, could it be increased to something like 64 or 128 to allow for headroom ?
Of course their OSC exposition counterpart should also be ensured.
Tags: Lua, osc, script
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0026288)
timetre   
2022-01-04 08:40   
Note that this limitation could be less of an issue if Editor Actions could receive parameters, say an int or float
Could be that when invoked via button or keyboard the parameter is not passed but invoking via OSC, the parameter could be passed. This would allow to use a single script/EditorAction for multiple things.

Sounds more complicated, not aligned with the philosophy of EditorActions etc ...; so probably a stupid idea but I thought I'd mention it anyway ;-)
(0026289)
x42   
2022-01-04 14:23   
Yes, it is mostly arbitrary. Since actions which are usually bound to keyboard shortcuts, 32 seemed plenty.

If you compile Ardour from source, you can increase it already:

#define MAX_LUA_ACTION_SCRIPTS 32

in gtk2_ardour/ardour_ui.h
https://github.com/Ardour/ardour/blob/547465e1fa1498b1ecd656b35bd2edcea6cc3bbe/gtk2_ardour/ardour_ui.h#L193-L194


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8846 [ardour] features minor N/A 2021-12-30 17:42 2021-12-30 18:25
Reporter: timetre Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Move toggle-exclusive-solo action from Monitor Section code to main Mixer code
Description: As discussed in this thread in the forum, it would be nice if the toggle-exclusive-solo action were defined in the main mixer code instead of the Monitor Section code as it can legitimately be used even if not using the Monitor Section

https://discourse.ardour.org/t/osc-and-toggle-exclusive-solo/106733
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0026286)
x42   
2021-12-30 18:25   
It is really a preference, and only for convenience also shown on the monitor section

Ardour > Preferences > Monitoring > Exclusive solo


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8841 [ardour] bugs minor always 2021-12-21 14:56 2021-12-29 14:54
Reporter: mrseiter Platform: Debian GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Sever X server memory leak
Description: While Ardour is running, xorg memory allocation grows by about 500kb/s. This eventually exhausts system memory and forces reset. Leak is not associated with any process in xrestop.
Tags: x11
Steps To Reproduce: Run Ardour
Additional Information: This is likely due to the drivers for the Intel Iris graphics processor and may not be correctable in Ardour's code.
System Description
Attached Files: sysinfo.text (15,813 bytes) 2021-12-21 14:56
https://tracker.ardour.org/file_download.php?file_id=4146&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8845 [ardour] bugs minor always 2021-12-29 11:33 2021-12-29 12:27
Reporter: johne53 Platform: Microsoft  
Assigned To: OS: Windows  
Priority: normal OS Version: 10  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Foldback bus / Show Sends can't be deselected if there are no selections
Description: Create a Foldback bus and add a couple of selected tracks, then press 'Show Sends'. As expected, the track display gets switched to show only the assigned tracks.

Now remove the tracks. Firstly, removing a track doesn't remove it from the displayed assignments. Secondly, if you remove ALL the assigned tracks, the 'Show Sends' button becomes inactive (i.e. you can't return the track display to normal any more). You need to assign another track, then hit 'Show Sends' and then remove the newly assigned track. Surely it'd make more sense if removing all he assigned tracks would simultaneously de-select 'Show Sends' if it happens to be activated?
Tags:
Steps To Reproduce:
Additional Information: And to me at least, it'd make more sense if removing an assignment would also remove it from the displayed tracks (i.e. whenever 'Show Sends' is active)
System Description
Attached Files:
Notes
(0026285)
johne53   
2021-12-29 12:27   
I forgot to add that there's an extra problem in Mixbus whereby (when 'Show Sends' is active) the displayed track(s) stop displaying their track name - so it can be difficult to tell which one's which. However, that seems to be okay in Ardour.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8844 [ardour] features minor N/A 2021-12-28 21:09 2021-12-28 21:09
Reporter: Lindisfarne Platform: Debian GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Clip list to help navigate big audio projects
Description: As a podcaster, I'd really like to have a clip list.

It could be this:
A side panel that can be toggled into view from the "view"-menu in the menu-bar.
The panel (clip list) would then appear to the left, onto which I'd be able to drag any clips or selections made in a track.
 In this clip list, I could then rename the clip - a great quote, for instance, that I'd like to use later - accordingly, so It'd be easy to find and drag it back in to my project. Maybe even leaving a copy of the clip behind in the list (but with a paler-coloured font), so for instance ambient sounds or music bits could be reused multiple times in one project.
Tags: montage, podcasting, radio
Steps To Reproduce:
Additional Information: I know that both Pro Tools and Hindenburg has this feature, but I have no idea how hard it is to build.
System Description
Attached Files: hindenburg-470x250.jpg (16,517 bytes) 2021-12-28 21:09
https://tracker.ardour.org/file_download.php?file_id=4148&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8843 [ardour] features minor have not tried 2021-12-26 11:27 2021-12-28 15:30
Reporter: erojahn Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Feature Request: optional Dry/Wet controll for Plugins in channel strip.
Description: I would like to be able to mix my processed Signal with the original inside the channelstrip. There is a lot of plugins that dont support that in their controls. I would like to add an dry/wet control to these Plugins inside the channelstrip. It is not too often it is needed so it could be also a hidden controll.
Thank you for reading! :)
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0026284)
x42   
2021-12-28 15:30   
We have considered this before but so far chose to not implement it for the following reasons:

The problem is that the host does not know the correct way to do this without introducing artifacts.
Proper Dry/Wet control depends on the DSP (as does properly bypassing a plugin). EQs are a prime example for this.

Additionally this would introduce overhead, even though it is minute, it can become significant if the session scales up.
Ideally dry/wet is only added in place where it is needed, on demand.

For your case there are 3 options currently:
 * Use Aux Sends to a separate bus to duplicate the steam
 * Duplicate the track with a shared playlist, use different set of plugins on both
 * Use Pin-connections to pass the signal around the plugin. Then Mix the result using a cross-fade or A/B plugin e.g. https://i2.paste.pics/de459e12bdc271e1844372ed68292f68.png


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8842 [ardour] features minor N/A 2021-12-26 11:22 2021-12-26 11:22
Reporter: erojahn Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Feature Request: More delaytime setttings in ace-delay
Description: I would love the Ardour community plugin to be able to set more complex delaytimes. For example every third quarter.
I like the Calf approach to setting the delaytimes.
Thanks for reading :)
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: Calf - Vintage Delay.jpg (93,575 bytes) 2021-12-26 11:22
https://tracker.ardour.org/file_download.php?file_id=4147&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8840 [ardour] bugs minor always 2021-12-18 21:04 2021-12-18 22:04
Reporter: timetre Platform: GNU  
Assigned To: OS: Fedora  
Priority: normal OS Version: 33  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Using OSC crashes Ardour when strip has Aux Send
Description: Using ToucOSC to control Ardour
Works fine except if:
A track has an Aux Send and the track is selected (either via ToucOSC or via the Ardour UI itself).
It crashes Ardour every time (core dump)
If the track is not selected it stays usable.
Whether the Aux Send is before or after the fader doesn't make a difference.
If the Aux Send is removed, then all is OK and it no longer crashes
Seems to be tied to the feedback.
Tags: osc
Steps To Reproduce: In a session put an Aux Send on one track
With the OSC client connected and receiving feedback, select the track that has the send
Additional Information:
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8839 [ardour] features minor have not tried 2021-12-17 11:22 2021-12-17 11:58
Reporter: snuggle Platform: GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: File Extensions
Description: Dear Ardour-Team,

Files have the extension filename.ardour. When using a new version, the old file is changed to filename-3002.ardour. If the originally used version is even older, filename-3002-3002.ardour is created.

It would be nice if Ardour would directly use as extension .ardour5 for version 5 and ardour6 for version 6. Then you could see directly with which version the song was originally recorded.
Best of all it would be nice if there was the possibility to leave in a newer version with "save as ardour5" etc in the old format.

Thank you
Regards
Reiner
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0026277)
x42   
2021-12-17 11:35   
The file-extension does not necessarily change with major versions.
e.g. Ardour3.x has 3 different revisions (3000 -3002), and then the file-format remained unchanged until Ardour 5.12 -> 6.0 transition.
 
Back-compatibility is important, but forward-compatibility is essentially impossible.
(0026278)
snuggle   
2021-12-17 11:58   
Thank you for this information.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
7714 [ardour] bugs minor always 2018-12-26 21:29 2021-12-15 11:34
Reporter: unfa Platform: PC  
Assigned To: OS: Linux Mint  
Priority: normal OS Version: 18.3 KDE5  
Status: new Product Version: 5.12  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ripple Edit Mode doesn't consider track groups
Description: I'd expect the Ripple Edit Mode to shift around all regions on all tracks together, or at least do so with respect to the Track Groups - unfortunately that's not the case.

It'll work great, but only in the scope of a single track - so as soon I have regions on multiple tracks - any editing done in the Ripple Edit Mode will break their relative sync, so it's not making anything easier, like I'd hoped it would.

Or maybe I'm just missing something?
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0025349)
bachstudies   
2020-12-23 19:25   
I think grouped ripple editing only works if the starts of regions are exactly aligned i.e. immediately after import or after making a cut. I would really appreciate a multi-track ripple edit mode as in Samplitude and Reaper with any markers automatically moved along with the regions.
(0026275)
Blindekinder   
2021-12-15 11:34   
It could be critical for some use. For example:
Editing a piece with >30 people speaking, one track for each. We are working with hundredths of regions since the interventions are all mixed. When we want to insert a region, we have to Select All after edit point (ctrl+shft+E), and move all together. If by accident one moves a fade or resize a region without unselecting, ALL regions will be affected.

Moving all region in all tracks after edit point in ripple mode edit is more secure and no need to make selection before moving.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8837 [ardour] features minor N/A 2021-12-12 17:05 2021-12-12 17:05
Reporter: finite_time Platform: Arch  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Feature Request: plugin bypass automation
Description: It would be beneficial to be able to bypass a given plugin in a given track with automation.
Tags: automation, bypass, plugin
Steps To Reproduce:
Additional Information: This could be implemented as a bypass option near Fader, Mute, Pan options (see fig_1) with a drop-down menu to chose the existing plugin to bypass. A particular form of this request is implemented in the Calf plugins through an existing Active or Bypass function (see fig_2), but most plugin don't offer this option.
System Description
Attached Files: fig_1.png (22,650 bytes) 2021-12-12 17:05
https://tracker.ardour.org/file_download.php?file_id=4144&type=bug
fig_2.png (38,271 bytes) 2021-12-12 17:05
https://tracker.ardour.org/file_download.php?file_id=4145&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8836 [ardour] bugs minor always 2021-12-09 12:05 2021-12-09 12:06
Reporter: szszoke Platform: Microsoft  
Assigned To: OS: Windows  
Priority: normal OS Version: 10  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ardour does not start up when Elektron Digitone is connected via USB in Overbridge mode
Description: Whenever I have my Digitone (FW 1.31) connected via USB in Overbridge mode to my computer, Ardour refuses to start up. I tried running Ardour from the console to see if something useful is printed but there is nothing.
Here is the output:

C:\Program Files\Ardour6\bin>Ardour.exe -P -O -d

C:\Program Files\Ardour6\bin>Ardour6.9.0 (built using 6.9 and GCC version 4.9.1)
Crash Log: C:\Users\szszo\AppData\Local\Ardour6\CrashLog\Ardour-6.9.0-crash-1639051252.txt
Ardour: [INFO]: MMCSS Initialized
Ardour: [INFO]: Your system is configured to limit Ardour to 2048 open files
ARDOUR_CONFIG_PATH not set in environment
Ardour: [INFO]: Loading system configuration file C:\Program Files\Ardour6\share\ardour6\system_config
Ardour: [INFO]: Loading user configuration file C:\Users\szszo\AppData\Local\Ardour6\config
Ardour: [INFO]: No H/W specific optimizations in use
Ardour: [INFO]: Loading plugin meta data file C:\Program Files\Ardour6\share\ardour6\plugin_metadata\plugin_tags
Ardour: [INFO]: Loading plugin statistics file C:\Users\szszo\AppData\Local\Ardour6\plugin_metadata\plugin_stats
Ardour: [INFO]: Loading default ui configuration file C:\Program Files\Ardour6\share\ardour6\default_ui_config
Ardour: [INFO]: Loading user ui configuration file C:\Users\szszo\AppData\Local\Ardour6\ui_config
Ardour: [INFO]: Loading 452 MIDI patches from C:\Program Files\Ardour6\share\ardour6\patchfiles
Ardour: [INFO]: Loading color file C:\Program Files\Ardour6\share\ardour6\themes\dark-ardour.colors
Ardour: [INFO]: Loading ui configuration file C:\Program Files\Ardour6\share\ardour6\clearlooks.rc
Ardour: [INFO]: Loading bindings from C:\Program Files\Ardour6\share\ardour6\ardour.keys
Loading ui configuration file C:\Program Files\Ardour6\share\ardour6\clearlooks.rc
Ardour: [INFO]: CPU vendor: AuthenticAMD
Ardour: [INFO]: AVX-capable processor
Ardour: [INFO]: AVX with FMA capable processor
Ardour: [INFO]: CPU brand: AMD Ryzen 9 5950X 16-Core Processor
Tags: digitone, elektron, overbridge
Steps To Reproduce: 1. Set USB CONFIG on Digitone to OVERBRIDGE
2. Connect Digitone to computer
3. Launch Ardour
Additional Information: There is an "Overbridge Engine" application that implements Overbridge mode as far as I know. Having this application running or not doesn't make a difference.

If I start up Ardour with the Digitone disconnected and then connect it, I can select it as an ASIO device within Ardour and I can see activity on the Recorder tab for all the input tracks.

If I set the USB CONFIG on the Digitone to USB AUDIO/MIDI then Ardour will start up as expected.

Is there a way to get more verbose logs out of Ardour?
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8661 [ardour] features minor have not tried 2021-04-11 09:16 2021-12-07 12:19
Reporter: DonJaime Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Gracefully ignore unknown plugin port types
Description: Some plugins have CV signal ports, which Ardour can't handle, but still provide useful signals on other ports. For example, the midimsg plugins (https://github.com/blablack/midimsg-lv2) can turn incoming MIDI messages into other MIDI messages (useful) and/or CV signals (no use in Ardour). Ardour refuses to insert these plugins.

It would be useful if Ardour would insert the plugin and let me use the usable ports. It could either completely ignore the unusable ports or (for forward compatibility) show them in the GUI but not allow connections. MIDI and audio ports are already shown in different colours and can't be connected to each other; unusable ports could be a sad dead grey, for example.
Tags:
Steps To Reproduce: Try to insert one of these plugins in Ardour. Dialog:

The plugin "...." could not be loaded
See the Log window for more details (maybe)

And in the Log window:
[ERROR]: LV2: "...." port 4 has no known data type
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
7886 [ardour] features minor have not tried 2020-01-27 02:25 2021-12-07 12:19
Reporter: milk Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Support for the recording/editing CV signal?
Description: CV signal essentially being the same as audio signal but often DC and thus (by default) unsuitable for direction to speakers (without some mechanism of intention required to be setup by the user).

Such signal could come from JACK client CV ports or LV2 plugin CV ports. Further possibilities include recording automation from modular synth hardware or applications such as VCV Rack.

More information is available on https://linuxmusicians.com/viewtopic.php?f=1&t=20701
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0020933)
x42   
2020-01-27 03:00   
I appreciate your enthusiasm to push every project to support CV, but I think in case of Ardour (and some others) it's misguided and we'd be much better off with more widespread use LV2:Atom sequences, or VST3 sample-automation.

sparse events require significantly less CPU power to process and are equivalent for all purposes.
also keep in mind that many LV2 plugins with CV ports don't even process CV signals sample accurately for that very reason.

That being said It would be great to have a LV2 plugin that takes parameter automation (port or Atom Sequence) and turns it into a CV data-stream. That plugin could be integrated or included with Ardour.
(0025681)
DonJaime   
2021-04-08 12:38   
It would be useful if Ardour could at least gracefully ignore CV ports on plugins. If I want to play/record MIDI while using one of the midimsg plugins, for example, (https://github.com/blablack/midimsg-lv2), I have to use Jack, load the plugin in Carla, and fiddle around with the connections. If I try to insert the plugin in Ardour I get:

The plugin "Midi AfterTouch (Channel Pressure)" could not be loaded
See the Log window for more details (maybe)

And in the Log window:
[ERROR]: LV2: "Midi AfterTouch (Channel Pressure)" port 4 has no known data type

Is there some deep technical reason why Ardour can't just ignore ports it can't do anything with?
(0025689)
x42   
2021-04-09 18:41   
> Is there some deep technical reason why Ardour can't just ignore ports it can't do anything with?

None that I can think of just now. perhaps compatibility once CV support gets added.
Yet generally plugins with CV I/O won't work properly until Ardour supports CV for control and allows patching CV networks.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8696 [ardour] bugs minor always 2021-05-08 15:41 2021-12-06 22:43
Reporter: marrs Platform: Apple Macintosh  
Assigned To: OS: MacOS  
Priority: normal OS Version: 10.12 or later  
Status: new Product Version: 6.6  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Waves plugins do not render correctly
Description: The skin of waves plugins does not render correctly. The background image appears to be rotated through 180 degrees. The particular plug-in shown is the Waves C6 Multiband Compressor and I've seen the same behaviour with the Linear Phase Multiband Compressor as well.

The issue exists for both VST and AU plugins.
Tags: Waves
Steps To Reproduce: Insert the plugin into a channel
Additional Information:
System Description
Attached Files: Screenshot 2021-05-08 at 16.24.14.png (201,198 bytes) 2021-05-08 15:41
https://tracker.ardour.org/file_download.php?file_id=4025&type=bug
Notes
(0026271)
hpfmn   
2021-12-06 22:43   
As proposed in 0008510 I compiled ardour on macos 11.6 with 11.1 SDK. Now the plugins are rendered correctly but I cannot interact with UI. It doesn't respond to clicks or anything. But maybe also there is something wrong with my build since also CMD+Q for example doesn't work. Do you provide a Version of ardour with a newer SDK for acounts that sponser you?


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8835 [ardour] bugs minor always 2021-12-05 19:56 2021-12-05 19:56
Reporter: mixdoctor888 Platform: Microsoft  
Assigned To: OS: Windows  
Priority: normal OS Version: 10  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Initial Setup: list of available drives not refreshed after a disk becomes available
Description: After plugging in a external hard drive, it does not show up in the list of available drives during the initial setup process.
Tags:
Steps To Reproduce: 1. Start Ardour after a fresh install
2. Have an external hard drive that you want to store your sessions to unplugged
3. Plug it in and wait for it to mount. The drive never shows up even after going backward and forward.
4. The drive appears in the list when you restart Ardour

Desired behavior:

Listen for device changes and update the view when a new drive is attached. At minimum, I believe this should be done when the view loads and not when the program starts.
Additional Information:
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8834 [ardour] bugs minor always 2021-12-03 16:11 2021-12-03 16:11
Reporter: sweptotter Platform: Apple Macintosh  
Assigned To: OS: MacOS  
Priority: normal OS Version: 10.12 or later  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: 6.8&6.9 crash when trying to add point to CC 'curves'
Description: Had this problem several months ago. Now returned.
Had been editing as above fine then repeated crashes when using pencil to add.
Have had to resort to dragging extraneous existing points (created by external ctller in rec)
Tags:
Steps To Reproduce: can upload project folder sans Audio files if you wish
Additional Information: have some 13 automation tracks. 1st 5 edit fine. All others I've tried crash repeatedly (you get bored after a bit)
Trying Hide All then showing one of the problem track(65) made no difference
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8833 [ardour] bugs minor random 2021-12-02 19:49 2021-12-03 04:09
Reporter: merejo Platform: Microsoft  
Assigned To: OS: Windows  
Priority: normal OS Version: 10  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Win 10 64BIT, ARDOUR CRASHES AND DROPOUTS.
Description: System: Asus M5 A97 R2.0
AMD FX 8 Core.
16 G Mem.

The system has crashed when 3 or more plugins have been enabled.
 Plugins are Ik Multimedia, sound effects and instruments.
Kontak player 6.
Dropouts while recording and playback. I suspect buffering issues.
Tags:
Steps To Reproduce: RE-load all again, or try saving all after loading the plugins.
The dropouts are harder to reproduce due to its inconsistency.
Additional Information: I believe it's s system specific problem.
I'm slowly configuring win 10 for audio, looking to reduce the issues
System Description
Attached Files:
Notes
(0026270)
x42   
2021-12-03 04:09   
In Menu > Window > Audio/MIDI Setup what buffersize do you use? Also also soundcard are you using?

Can you try to isolate the issue a bit further? e.g. create a couple of MIDI tracks with only Kontakt and no other plugins.

Are those VST2 or VST3 plugins?


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8831 [ardour] bugs minor always 2021-12-01 09:58 2021-12-02 00:31
Reporter: rohanlean Platform: GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Inconsistent MIDI messages generated by playhead repositioning depending on Aux Send vs port connection
Description: When repositioning the playhead, a MIDI track sends Damper Pedal Off (0x4000) and All Notes Off (0x7B00) on all channels when connected via port (i.e. Window ? MIDI Connections), but not when connected by Aux Send.

These same messages are sent on both connections when the track is being muted.

Incidentally this causes unwanted damper pedal noise from at least one virtual piano, so I would also like to enquire whether sending the messages is even correct and if so, how the piano should deal with them.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0026269)
x42   
2021-12-02 00:31   
I also noticed that recently.

MIDI panic messages injected and directly sent to synth-plugins on tracks and output ports (which usually feed external synths).
They are not produced at the input and passed though, because there may be multiple plugins and some "eat" MIDI messages, or a track may not monitor input (but play from disk) so it would be lost.

But it seems there is some inconsistency here with MIDI busses with this out-of-band data. The goal is to not collect the panic message from multiple aux-sources (so you get N times the panic message), but re-inject it directly to the synth on the Bus, or the Bus' output.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8830 [ardour] bugs minor sometimes 2021-12-01 01:46 2021-12-01 01:46
Reporter: pq2 Platform: Apple Macintosh  
Assigned To: OS: MacOS  
Priority: normal OS Version: 10.12 or later  
Status: new Product Version: Mixbus 7.x  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: MIDI notes are misplaced after reopening the file
Description: I have a MIDI track where I am placing MIDI notes as cues for other software and sending them out through BOME network MIDI interface. I place the notes in a specific place in time where other tracks are playing music and sound effects. After re-opening the file the midi files are misplaced, they are still in order, but not in the right place. I've fixed it a couple of times, but, as the file gets bigger, it is becoming annoying.

I am attaching the MIDI file converted to text.
Tags: Midi
Steps To Reproduce: Setup a MIDI track, add MIDI notes on a single MIDI space. Save, close and re-open, the files are not in the same place. No tempo changes.
Additional Information:
System Description
Attached Files: m2.txt (3,482 bytes) 2021-12-01 01:46
https://tracker.ardour.org/file_download.php?file_id=4142&type=bug
MIDI Signals-2.mid (576 bytes) 2021-12-01 01:46
https://tracker.ardour.org/file_download.php?file_id=4143&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8829 [ardour] bugs minor always 2021-11-30 20:08 2021-11-30 20:08
Reporter: rohanlean Platform: GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Drop down menus cover other windows and do not stick to their workspace
Description: Using Mutter 41.1 (Wayland);

Drop down menus cover other windows that are stacked over the Ardour window. They also do not stick to their original workspace and instead move to the active one, at which point they are impossible to get rid of other than by switching back to Ardour's workspace.

For reference, GTK and QT drop down menus disappear when their parent windows loses focus.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8584 [ardour] bugs minor have not tried 2021-02-25 16:51 2021-11-26 06:58
Reporter: unfa Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Crash when activating tracks
Description: Ardour 6.6 crashed when I activated a bunch of disabled tracks.
Here's the backtrace:

Thread 133 "autoconnect" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffe99a67640 (LWP 502483)]
0x00007fffee7fd75f in __cxxabiv1::__dynamic_cast (src_ptr=0x3f0000003f000000, src_type=0x555556659a38 <typeinfo for ARDOUR::Processor>, dst_type=0x7ffff7af65a8 <typeinfo for ARDOUR::LatentSend>, src2dst=-2)
    at /build/gcc/src/gcc/libstdc++-v3/libsupc++/dyncast.cc:50
50 /build/gcc/src/gcc/libstdc++-v3/libsupc++/dyncast.cc: No such file or directory.
(gdb)
(gdb) bt thread apply all
A syntax error in expression, near `apply all'.
(gdb) bt
#0 0x00007fffee7fd75f in __cxxabiv1::__dynamic_cast (src_ptr=0x3f0000003f000000, src_type=0x555556659a38 <typeinfo for ARDOUR::Processor>, dst_type=0x7ffff7af65a8 <typeinfo for ARDOUR::LatentSend>, src2dst=-2)
    at /build/gcc/src/gcc/libstdc++-v3/libsupc++/dyncast.cc:50
0000001 0x00007ffff74d50ec in ARDOUR::Route::update_signal_latency(bool, bool*) () from /opt/Ardour-6.6.0/lib/libardour.so.3
#2 0x00007ffff751a457 in ARDOUR::Session::update_route_latency(bool, bool, bool*) () from /opt/Ardour-6.6.0/lib/libardour.so.3
#3 0x00007ffff751a6f6 in ARDOUR::Session::update_latency_compensation(bool, bool) () from /opt/Ardour-6.6.0/lib/libardour.so.3
0000004 0x00007ffff751aa3c in ARDOUR::Session::auto_connect_thread_run() () from /opt/Ardour-6.6.0/lib/libardour.so.3
0000005 0x00007ffff751ad98 in ARDOUR::Session::auto_connect_thread(void*) () from /opt/Ardour-6.6.0/lib/libardour.so.3
#6 0x00007ffff08f9299 in start_thread () from /usr/lib/libpthread.so.0
#7 0x00007fffee501153 in clone () from /usr/lib/libc.so.6
Tags: crash
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0025560)
x42   
2021-02-26 11:59   
Does this also happen if you open the session in safe-mode, without plugins?


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8582 [ardour] bugs minor always 2021-02-24 18:49 2021-11-26 06:56
Reporter: unius Platform: GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: A large lag in the response of the UI in some VST3 plugins
Description: Some VST3 plugins (apparently based on JUCE) plugins have a very large delay on any user actions.
This does not appear on other hosts (for example, Reaper) and in the VST2 version of the same plugins in Ardour.

A similar effect is observed in Harrison AVA plugins on any host starting with beta version from 2020.08.07 (in 2020.07.31 and earlier, everything was fine).
Tags:
Steps To Reproduce: 1 get https://tal-software.com/downloads/plugins/TAL-J-8_64_linux.zip
2 install VST2 and VST3 version
3 create a MIDI Track in Ardour with the VST3 version of this plugin
4 try clicking on any button that brings up a pop-up window/menu (for example SC)
5 after a few seconds, the window/menu may or may not appear
6 try with VST2 version
7 all ok
Additional Information: tested on Ardour Nightly Build 6.6.40
x86_64, Optimized, Demo, gcc5
System Description
Attached Files:
Notes
(0026244)
jonesRebecca   
2021-11-26 06:56   
The reproducible steps are extremely detailed. Thank you so much for this information! https://fall-guys.co


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8825 [ardour] other minor have not tried 2021-11-22 02:42 2021-11-22 17:47
Reporter: EnderKing101rs Platform: Microsoft  
Assigned To: OS: Windows  
Priority: normal OS Version: 10  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: windows detected as virus
Description: when I tried to get the demo install going windows defender detected ardour as a virus which I found ironic as I just read that it didn't get flagged. I'm not mad, found it kinda funny actually.
Tags: install, Windows
Steps To Reproduce: try to install the 64x windows demo
Additional Information:
System Description
Attached Files: Screenshot_219.png (28,813 bytes) 2021-11-22 02:42
https://tracker.ardour.org/file_download.php?file_id=4138&type=bug
Notes
(0026223)
x42   
2021-11-22 17:47   
"unknown publisher" is expected. The application is not digitally signed by Microsoft. because we (ardour.org) do not pay Microsoft or any other entity for a windows certificate to sign the installer.

Similar issue exists on macOS. We also do not pay the Apple tax.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8826 [ardour] features minor always 2021-11-22 17:07 2021-11-22 17:07
Reporter: PavelAtr Platform: Debian GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Unable to select the opensles driver in the jack launch settings.
Description: Unable to select the opensles driver in the jack launch settings.

An OpenSLES backend for jackd actually exists and can be used. Now you have to run jackd separately, but I would like to be able to run it using ardor.

Thanks.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
7522 [ardour] bugs minor always 2017-12-10 04:23 2021-11-22 01:40
Reporter: ragnarok Platform: 64 Bits  
Assigned To: OS: Debian GNU/Linux  
Priority: normal OS Version: 9.x (stretch)  
Status: new Product Version: 5.X git (version in description)  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Video glitches on zoomed automation track
Description: I expand size and zoom the automation view from a audio track, i have video glitched when scroll it.

It's do not occur on audio track itself just only on the autimation part.

I upload a video capture that reproduce the issue:

https://www.youtube.com/watch?v=j4HG48d8EBY&feature=youtu.be

Please tell me if you need more info.
Thanks!


Tags:
Steps To Reproduce: resize to grow atomation from audio track. put some points, zoom and scrool it
Additional Information:
System Description
Attached Files:
Notes
(0020287)
agittins   
2018-06-04 10:51   
I'm having a similar issue. For me it only seems to happen in some projects, but when it does I can usually trigger it just by moving nodes. I've not yet been able to replicate it on demand, it seems to be just in certain projects.

I'm on Debian 9.3 using Ardour 5.12.0 built from kxstudio, with amdgpu graphics running kde.
(0020290)
ragnarok   
2018-06-05 01:25   
(Last edited: 2018-06-05 01:25)
Good to know. I also use debian 9.x on Laptop with onboard Intel Ivybridge video card. I can provide my project if can help to debug

(0020302)
lilith   
2018-06-19 11:00   
(Last edited: 2018-06-19 11:01)
I also have these glitches. Ardour 5.12 from the Ardour website with Debian Stretch XFCE and onboard graphic.
My board is a MSI H81M-E34.

(0026221)
ragnarok   
2021-11-22 01:40   
I cannot reproduce on receent version (6.9.0) so i think that this bug was fixed


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8822 [ardour] bugs minor always 2021-11-18 21:49 2021-11-18 21:49
Reporter: ivnamei Platform: Microsoft  
Assigned To: OS: Windows  
Priority: normal OS Version: 10  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Export distortion
Description: I have a minute voice recorded. It plays fine on Ardour, but every time I export the voice is badly distorted and becomes a much lower voice. It happens with every configuration possible, WAV, FLAC, MP3, Real time or not. When hearing it on Ardour`s windows after the export it sound fine, outside of it it`s distorted on every player and device. Please help!
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8784 [ardour] bugs minor always 2021-08-02 14:09 2021-11-14 10:00
Reporter: Werner Back Platform: Microsoft  
Assigned To: OS: Windows  
Priority: normal OS Version: 10  
Status: new Product Version: 6.8  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: LUA: Store Mixer Settings has pan wrong
Description: I used the "Store Mixer Settings" Lua script to save a "scene", but when I restore from that file the pans are set wrong. I checked the saved values and it looks as if the way the numbers are stored is wrong. It looks like the following:

...,pan_control=0,5,...
 but should look like
...,pan_control=0.5,0.5,...
(this example is for "center position").

If I correct this manually in the file the pans look alright.
Tags:
Steps To Reproduce: Store + recall mixer settings with LUA script.
Additional Information:
System Description
Attached Files: a_db2b41821.lua (10,885 bytes) 2021-08-05 06:21
https://tracker.ardour.org/file_download.php?file_id=4096&type=bug
mixer_settings_store.lua (10,781 bytes) 2021-11-14 10:00
https://tracker.ardour.org/file_download.php?file_id=4131&type=bug
mixer_settings_recall.lua (14,745 bytes) 2021-11-14 10:00
https://tracker.ardour.org/file_download.php?file_id=4132&type=bug
Simple-fb-duplicated.ardour (150,051 bytes) 2021-11-14 10:00
https://tracker.ardour.org/file_download.php?file_id=4133&type=bug
Simple-fb-triplicated.ardour (151,597 bytes) 2021-11-14 10:00
https://tracker.ardour.org/file_download.php?file_id=4134&type=bug
Simple.ardour (148,509 bytes) 2021-11-14 10:00
https://tracker.ardour.org/file_download.php?file_id=4135&type=bug
Notes
(0026087)
Werner Back   
2021-08-03 10:53   
Oh, just saw that it's a locale problem. LUA replaces the "." with "," in german environments.

Something like that should work:
            if pan ~= false then
                local strPan = tostring(pan)
                pan = strPan:gsub(",", ".")
            end
(0026089)
Werner Back   
2021-08-04 11:26   
Ah, I played a little with LUA (without understanding everything ;)) and it seems that this works:

Replace the following line:
if pan:isnil() then pan = false else pan = pan:get_value() end --sometimes a route doesn't have pan, like the master.

with
if pan:isnil() then pan = false else pan = ARDOUR.LuaAPI.ascii_dtostr(pan:get_value()) end --sometimes a route doesn't have pan, like the master.

Probably there are some more parameters where this problem occurs? I couldn't find out what "send_string" does? Guess that's Mixbus only, right? Since the LUA script's author is "Mixbus Team", is it possible, that this bug doesn't appear in Mixbus?
(0026090)
Werner Back   
2021-08-05 06:21   
This works for me now.
(0026216)
Werner Back   
2021-11-14 10:00   
Further Problems: Storing fails if project name contains blanks. Fixed this.

Still not fixed and beyond my skills: if the Project contains a foldback, recalling a stored setting duplicates all foldback strips again and again. This leads to unusable projects because DSP load increases every time you load.

See the simple attached project files (diff them and you'll see). These were made in mixbus, but in ardour it's the same.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8227 [ardour] bugs minor always 2020-06-11 18:27 2021-11-11 18:15
Reporter: derwok Platform: Thinkpad T460s  
Assigned To: OS: Ubuntu Linux  
Priority: normal OS Version: 20.04 LTS  
Status: new Product Version: 6.0  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ardour 6.0.0 crashes on session load
Description: Using Ardour 6.0.0 on Ubuntu 20.04 LTS. With ALSA drivers (No Jack).
Worked on this session for several days. It survived multiple opens/closes.
Neither Sound nor MIDI setup changed in theses days.

Now loading my session gives me a loading error (see screenshot) with Ardour crash after pressing OK.
Tags: crash load bad_weak_ptr
Steps To Reproduce: Load the attached session file (sorry only XML, no audio / midi)
Additional Information: I tried:

    Check other sessions. OK: All my other stored project’s sessions load great without a hic-up. Some more complex, some less complex as this one…
    I rebooted. No help
    I unpluged all devices. Then replugged all devices. At no avail…
    I tried to load the session “Safe Mode: Disable all plugins”
    I tried to create a new session: OK, works

Console log follows:

wok@thinkpad:~$ Ardour6
Ardour6.0.0 (built using 6.0 and GCC version 6.3.0 20170516)
Ardour: [INFO]: Your system is configured to limit Ardour to 1048576 open files
Ardour: [INFO]: Loading system configuration file /opt/Ardour-6.0.0/etc/system_config
Ardour: [INFO]: Loading user configuration file /home/wok/.config/ardour6/config
Ardour: [INFO]: CPU vendor: GenuineIntel
Ardour: [INFO]: AVX-capable processor
Ardour: [INFO]: CPU brand: Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz
Ardour: [INFO]: Using SSE optimized routines
Ardour: [INFO]: Loading plugin meta data file /opt/Ardour-6.0.0/share/plugin_metadata/plugin_tags
Ardour: [INFO]: Loading plugin meta data file /home/wok/.config/ardour6/plugin_metadata/plugin_tags
Cannot xinstall SIGPIPE error handler
Ardour: [INFO]: Loading default ui configuration file /opt/Ardour-6.0.0/etc/default_ui_config
Ardour: [INFO]: Loading user ui configuration file /home/wok/.config/ardour6/ui_config
Ardour: [INFO]: Loading 449 MIDI patches from /opt/Ardour-6.0.0/share/patchfiles
Gtk-Message: Failed to load module "canberra-gtk-module"
Ardour: [INFO]: Loading color file /opt/Ardour-6.0.0/share/themes/dark-ardour.colors
Ardour: [INFO]: Loading ui configuration file /opt/Ardour-6.0.0/etc/clearlooks.rc
Ardour: [INFO]: Loading bindings from /home/wok/.config/ardour6/ardour.keys
Loading ui configuration file /opt/Ardour-6.0.0/etc/clearlooks.rc
Found nothing along /home/wok/.config/ardour6/templates:/opt/Ardour-6.0.0/share/templates
Scanning folders for bundled LV2s: /opt/Ardour-6.0.0/lib/LV2
Set cursor set to default
 loading from ... templ is_new 0 bp 0
Butler drops pool trash
Log Messages:
INFO: AlsaAudioBackend: adjusted output channel count to match device.
INFO: AlsaAudioBackend: adjusted input channel count to match device.
INFO: harvid version: 803
INFO: Loading menus from /opt/Ardour-6.0.0/etc/ardour.menus
ERROR: Unexpected exception during session setup: tr1::bad_weak_ptr

Attached Files: load-error.png (35,124 bytes) 2020-06-11 18:27
https://tracker.ardour.org/file_download.php?file_id=3732&type=bug
Happy Birthday.ardour (269,237 bytes) 2020-06-11 18:27
https://tracker.ardour.org/file_download.php?file_id=3733&type=bug
Happy Birthday-2.ardour (269,237 bytes) 2020-06-11 18:55
https://tracker.ardour.org/file_download.php?file_id=3734&type=bug
2020-06-11_21-36 Ardour Screenshot.png (389,423 bytes) 2020-06-11 19:42
https://tracker.ardour.org/file_download.php?file_id=3735&type=bug
Notes
(0024452)
x42   
2020-06-11 18:55   
(Last edited: 2020-06-11 19:30)
The attached file allows to load the session again. Replace the "Happy Birthday.ardour" file in your session folder with the file.
The fix is to change line 3075 and disable <code>Protocol name="Generic MIDI" ... active="0"</code>

The bug is caused since you've apparently used MIDI-learn and the Control that was assigned is no longer available (a pitch-bend?). We'll need to address this in a future release.

(0024453)
derwok   
2020-06-11 19:42   
There it is in all its beauty!!
You're my hero!! Big thanx!
(And thanks to the XML format that makes patching so easy) :-)
Never would have thought of this root cause.

But I need to say: yes: I tried to learn the pitch bend. But it did not work out while the session was open. Anyhow it got saved?!
The pitch bend had no effect on the setBfree organ. When I tried to load the (then crashing) session , the MIDI keyboard was all available with the same hardware pitch bend.
So it might be, that the problem is not during loading (the hardware was available and connected!), but that the problem occured even more early during assigning and saving bad information?

Anyway: thanks again! Just out of sheer happiness a photo of Ardour with my session loading again.
(0024455)
x42   
2020-06-11 19:57   
Well, organs have no pitch-bend, so it may have been "working", but setBfree does not respond since a Hammond B3 has not pitch-wheel.

Anyway, I'll leave this issue open. The root cause remains to be fixed and that session of yours will come in handy for this.
(0024742)
consint   
2020-07-15 16:29   
I just wanted to inform you that I had the same problem with a project today. Setting "Generic MIDI" to active="0" also worked for me. Thanks a lot!
(0025373)
kevinw   
2021-01-03 16:31   
I had the same "tr1::bad_weak_ptr" exception on startup. I had used midi learning and not changed any hardware.

Removing this block made it run again:

$ diff "Pirate#0.ardour.orig" "Pirate#0.ardour.patchfixed"
2112,2126d2111
< <Protocol name="Generic MIDI" feedback="1" feedback-interval="10000" threshold="15" motorized="0" binding="Korg nanoKONTROL Studio" active="1">
< <Input>
< <Port name="MIDI Control In" direction="input">
< <Connection other="system:midi_capture_nanoKONTROL Studio"/>
< </Port>
< </Input>
< <Output>
< <Port name="MIDI Control Out" direction="output">
< <Connection other="system:midi_playback_nanoKONTROL Studio"/>
< </Port>
< </Output>
< <Controls>
< <MIDIControllable id="23059" event="0xb0" channel="0" additional="0xc"/>
< </Controls>
< </Protocol>


Actually if I just remove:
< <Controls>
< <MIDIControllable id="23059" event="0xb0" channel="0" additional="0xc"/>
< </Controls>

...Ardour will load the session. I'm up and running again thanks to finding this bug report.
(0026214)
MyLoFy   
2021-11-11 18:15   
Phew! This just saved me from a huge headache and the loss of two days work, thanks guys!
Had a setBFree track and assigned my Faderport via QMidiRoute to the rotary speed (which works). Setting <code>Protocol name="Generic MIDI" ... active="0"</code> solved it.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8821 [ardour] bugs minor always 2021-11-09 15:44 2021-11-09 16:07
Reporter: unfa Platform: AMD64, Ryzen 9 (Zen2)  
Assigned To: OS: Ach Linux (formerly Manjaro)  
Priority: normal OS Version: KDE  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Xjadeo is not in sync with Ardour when using Int. sync
Description: On the attached screenshot you can see that Xjadeo is 9 frames behind Ardour.
Ardour is using Internal Sync.

When switching to JACK transport external sync, the video plays fine.
I am using JACK2-dbus as backend.

Also: I have had to manually change the session framerate to 60 FPS (from 30) to have the video at least play at the same speed as the audio plays in Ardour (though there's the 9 or so frames lag).

The video Import dialogue does not automatically set the project framerate, and the option to do so is gone in Ardour 6.9 (I believe it was there in some previous versions.).

Even if the session is set to 30 FPS, the video plays fine when using JACK sync.
I tested that using JACK and PipeWire-JACK-dropin.

So teh out-of-the-box experience when importing a 60FPS vidoe file into Ardour is:
- video plays too slow and needs the project to have changed framerate
- after that it stil lags and needs the sync to be changed to JACK
- it still has bad black frames so the user needs to transcode the vidoe to a different format

And then it works as expected.
Tags: sync, timecode, transport, video, xjadeo
Steps To Reproduce:
Additional Information: All of thse iissues did not exist in older versions of Ardour, as you can see in this video:
https://youtu.be/QGI1QsFcNzU?t=805
(attached screenshot)

I was not using a custom video encoding, did not have to change my session framerate or change to a different sync than Internal and it just worksed in that video (it was recorded more than 8 months ago though).
System Description
Attached Files: Screenshot_20211109_164235.png (434,347 bytes) 2021-11-09 15:44
https://tracker.ardour.org/file_download.php?file_id=4130&type=bug
Notes
(0026213)
x42   
2021-11-09 16:07   
Try without pipwire -- latency compensation and playback alignment is still broken there.

Ideally with Ardour/ALSA (no JACK).
Also Ardour only supports SMPTE framerates. for 60 fps files make sure you have enabled Session > Properties >"Use Video File's FPS Instead of Timecode Value for Timeline and Video Monitor."

PS. Nothing has changed there on our side in the last 8 months. -- really video-timeline has not changed in 4+ years. If this worked in the past it is very likely an issue with your setup.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8820 [ardour] other minor have not tried 2021-11-09 15:39 2021-11-09 15:39
Reporter: unfa Platform: AMD64, Ryzen 9 (Zen2)  
Assigned To: OS: Ach Linux (formerly Manjaro)  
Priority: normal OS Version: KDE  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: AVI/MJPEG produced a lot of dropped frames, ProRes/MOV does not
Description: I've been having issues with video playback via Xjadeo when usign video reference ith Ardour.
In the past it worked ok, but not now.

When using default Ardour MJPEG transcoding, Xjadeo produces a huge amout of dropped frames, resulting on terrible image flicker.

I've tested a different codec and it worked flawlesly (also provided much better visual quality):

My input is a 1080p60 MKV file. I've transcoded it with:

     ffmpeg -i reference.mkv -s 854x480 -pix_fmt yuv420p -c:v prores reference.mov

I do what I can to avoid non-free codecs, but in this case the MJPEG encoding seems to work poorly. I don't know why, as it used to work great.

Please consider testing this and changing the default transcoding settings to make sure other users don't have this same issue.
Tags: video, xjadeo
Steps To Reproduce:
Additional Information: Here's a video demonstration of the issue:

https://youtu.be/KkZ3pzkl_H4
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
7221 [ardour] features minor N/A 2017-01-29 11:02 2021-11-07 21:16
Reporter: Lost_Highway Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 5.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Editor window track colours
Description: In the Editor window, it would be helpful if each track's colour were displayed somewhere in the track title box at the left hand side.

The reason for suggesting this is that, whilst it's really useful having the regions coloured and the bars in the summary, if you're looking at a section of the timeline where there is no recorded audio you cannot see what colour is selected for the track (and colour-coding tracks is a very useful navigational aid in large sessions).

As there is colour coding of the track title box to differentiatef audio and midi tracks and as track height can vary, perhaps the area around the track name box could be filled with the track colour as this would always be visible, leaving the area around the fader (when visible) and the rec/mute/solo/etc buttons to indicate track type. I guess the background to the actual text would be best left as is so that the text is always legible if really light or dark track colours are selected.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8819 [ardour] bugs minor always 2021-11-04 21:41 2021-11-04 21:41
Reporter: AliMacD Platform: Apple Macintosh  
Assigned To: OS: MacOS  
Priority: normal OS Version: 10.12 or later  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Stretch Mode: various issues
Description: Stretch Mode: relation between stretched result on timeline and source list
auto-naming, (re-naming), re-appearing with different names after re-opening session,
stereo splitting to mono
(and Duration window still doesn't mirror primary clock if it's not bars/beats)
Tags:
Steps To Reproduce: open a new session
create a new stereo audio track
import stereo sound e.g. ‘piano’
drag sound onto track
stretch sound: the name is automatically generated e.g. ‘piano.1@120
bug 1: this *sometimes/usually appears in Source list, but not always*
but assuming Source list has 'piano' and 'piano.1@120' listed for now...

look in Interchange….audiofiles:
in addition to the imported piano%L.wav and %R.wav I now see
piano%L%L.wav and piano%R%R.wav - these appear to be the source files for ‘piano.1@120

save and close session
re-open session

bug 2: Source list now has original ‘piano’ and two mono files: piano%L%L.wav and piano%R%R.wav
and
bug 3: my stereo piano.1@120 is no longer listed in Sources

If I left 'piano.1@120' on the timeline it remains there, and is listed in the Regions list but if I deleted it from the timeline it is gone and
I can’t drag the 2 mono halves of piano%L%L.wav and piano%R%R.wav into a stereo track (is this me or a missing feature?)

drag ‘piano’ in again, repeat
piano_stuff%L-2%L & R
piano_stuff%L-3%L & R etc.
again a mixture of piano.n@nnn sometimes appearing in the source list, sometimes not, but never after re-opening the session, only mono pairs

Also I would dearly like to (re-)name the files myself, not just accept the source+stretch amount even if that were to work
Additional Information:
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8815 [ardour] bugs minor always 2021-10-26 17:18 2021-10-26 17:18
Reporter: timkrause Platform: Debian GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: ACE Inline Spectrogram display becomes choppy after running for a day.
Description: ACE Inline Spectrogram display becomes choppy after running for a day.
Tags: ACEplugins, display
Steps To Reproduce: 1) Open Ardour with a fresh session
2) Add an audio track
3) Add the ACE Inline Spectrogram
4) Route a constant source of sound to the track
5) Let run for a day
Additional Information:
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8665 [ardour] bugs minor random 2021-04-16 22:12 2021-10-22 01:23
Reporter: ericfontaine Platform: Arch  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.6  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: when stop recording, ardour sometimes puts undesired empty region ontop of recorded region
Description: I’m sporadically encountering issue where the last region I recorded shows the waveform fine as it is recording, but then when I press stop, an empty region is placed on top of the recorded region. I don’t hear my recorded region when I playback and it appears as though nothing recording because a blank region is placed ontop of my recorded audio. However the audio did record, and can be found by clicking on the empty region and pressing delete.

See https://discourse.ardour.org/t/ardour-git-sometimes-returns-empty-region-after-stop-recording/105791
Tags:
Steps To Reproduce: Not easily reproducible, and I haven't determined the exact conditions which this happens on my computer, but it seems the more audio regions I record, the more likely I am to encounter this issue.
Additional Information:
System Description
Attached Files: Image1.png (112,313 bytes) 2021-06-22 19:07
https://tracker.ardour.org/file_download.php?file_id=4068&type=bug
Image2.png (62,449 bytes) 2021-06-22 19:07
https://tracker.ardour.org/file_download.php?file_id=4069&type=bug
Issue.ardour (100,592 bytes) 2021-06-22 19:07
https://tracker.ardour.org/file_download.php?file_id=4070&type=bug
bug-happened.tar.gz (26,391 bytes) 2021-10-22 01:23
https://tracker.ardour.org/file_download.php?file_id=4120&type=bug
Notes
(0025713)
x42   
2021-04-16 22:17   
Just to clarify: there is a correct region with expected audio underneath, and simply deleting the empty region fixes things?
(0025714)
ericfontaine   
2021-04-17 00:03   
yes, there is a correct region underneath the blank region, and simply deleting the empty region fixes things.
(0025991)
jumase   
2021-06-22 19:07   
Hi, I found something similar to this but couldn't reproduce it.

I started up a new project and started recording with Transport -> Follow Playhead and Stationary Playhead activated. These were the only different things I set, so I thought that could be the cause of this issue, but I couldn't reproduce it again by activating those preferences. I mention this here because I got this problem on the first recording. I "fixed" it by editing the region end (I tried to make it larger; of course that would be imposible, but when I released mouse, the waveform was there).

Recently I noticed that region name finishes in .2, indicating it is a "second edit region", but I think I hadn't done any edits when I did the screenshot. What I mean is that maybe the region with the waveform was under the .2 region.

Another difference from what ericfontaine reported is that I actually could hear the recorded audio, though no waveform was shown.

Lastly, I tried to drag and drop region Gtr-1.2 from the Region List but it didn't work. It creates another region, but shows nothing in the track, not even an empty region.

I attach two images. The second one has the track unarmed to show metrics. I also upload the session file as it may help (it has another track and a few edits and automation added).

Version used: 6.7.0 from ardour.org
(0026194)
ericfontaine   
2021-10-22 01:23   
I just experienced this issue again. On a 3-day fresh install of KDE neon user edition (which is based on Ubuntu 20.04-lts and KDE plasma 23.0) using the linux install binary from the Ardour website. My session has 3 tracks: "alto-flute", "06 Conv...Melody", "conveyer...larinet.2". I was recording my first take on alto-flute for the project duration (1 min 20 sec). After recording completed, I see there is a region "Take1_alto-flute-1.2" with no audio which is covering up what I actually recorded (region name "Take1_alto-flute-1.1").


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8813 [ardour] features minor always 2021-10-21 08:37 2021-10-21 08:41
Reporter: gunterkoenigsmann Platform: Debian GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Feature request: A default template
Description: I make nature recordings => the template I normally use doesn't occupy screen space with tempo and beats.
A low-hanging fruit would be to tell ardour to on creating a new session load the template namend "Default" if I haven't selected a different template to use.
Tags: feature request, start
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8794 [ardour] bugs minor always 2021-09-10 00:57 2021-10-17 17:21
Reporter: domingo Platform: Apple Macintosh  
Assigned To: OS: MacOS  
Priority: normal OS Version: 10.12 or later  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Hangs when Audio Interface USB is disconnected
Description: This problems bothers me since many versions and finally decided to report it, supposing this is a general problem that can be revised in the future.

Ardour hangs if the audio interface is turned off or unplugged when active.

Interface: Combo Amanero 384 (DAC) under OSX 10.13, using generic drivers.

I wish Ardour would be more agile automatically deactivating and reactivating usb interfaces when they are switched off and on.

Similar problem: When unplugging and replugging a USB sound recorder (Zoom H1), it is not detected automatically by the session in use, the device rather appears duplicated in the list of the Audio/MIDI engine and sometimes not even responding to any both.
Tags:
Steps To Reproduce:
Disconnect and reconnect an active USB interface.
Additional Information:
System Description
Attached Files:
Notes
(0026192)
al f   
2021-10-17 17:21   
Ardour freezes on USB disconnection on my system as well. (K)Ubuntu Studio 20.04, Ardour 6.9. Focusrite Scarlett 2i4.

It seems that sometimes disconections triggers the error message "Session: cannot have two events of type TransportStateChange at the same sample", but I haven' been able to reliably reproduce that.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8787 [ardour] bugs minor always 2021-08-16 16:25 2021-10-12 12:24
Reporter: ardourwlk Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Crash on dragging region to create new track
Description: After several successful iterations of recording 2 regions, then dragging them to create 2 new tracks, I hit a wall where I drag the region down to create the new track, and Ardour exits. On restarting, it does not suggest there was a problem, and I can reproduce this, apparently, ad infinitim with this session... drag, wreck, restart, drag, wreck.
Tags:
Steps To Reproduce: I have a session I am layering some guitars, so I am recording a clean track and a processed track (through guitarix, not plugin) each time. So, recording two tracks at a time (only about 10 seconds), then stop, drag each of those new regions down to create a new track for each, and repeat. I've done 4 iterations so far, and now on the 5th time on dragging the second of the two new regions to create a new track, Ardour exits, and on restarting, it does not suggest that it wrecked, and I can reproduce at will (within this session).
Additional Information: I have not tried with a new session. This is the AMD 64-bit binaries downloaded from the main site.

I don't believe this helps, but from the apport.log (the first incident):
ERROR: apport (pid 6998) Mon Aug 16 12:02:06 2021: called for pid 6791, signal 11, core limit 0, dump mode 1
ERROR: apport (pid 6998) Mon Aug 16 12:02:06 2021: executable: /opt/Ardour-6.9.0/bin/ardour-6.9.0 (command line "/opt/Ardour-6.9.0/bin/ardour-6.9.0 -N /home/aaron1/ArdourSessions/20210816.1144 -T BetterQuickGuitarWithGuitarix")
ERROR: apport (pid 6998) Mon Aug 16 12:02:06 2021: gdbus call error: Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

ERROR: apport (pid 6998) Mon Aug 16 12:02:06 2021: debug: session gdbus call:
ERROR: apport (pid 6998) Mon Aug 16 12:02:25 2021: wrote report /var/crash/_opt_Ardour-6.9.0_bin_ardour-6.9.0.1000.crash
System Description
Attached Files: ard_ouch.txt (31,442 bytes) 2021-08-16 16:34
https://tracker.ardour.org/file_download.php?file_id=4098&type=bug
ardfail_20210817_0934.png (16,421 bytes) 2021-08-17 13:41
https://tracker.ardour.org/file_download.php?file_id=4099&type=bug
Notes
(0026106)
ardourwlk   
2021-08-16 16:34   
attached gdb output in ard_ouch.txt file
(0026107)
ardourwlk   
2021-08-16 16:39   
Using Ubuntu Studio 20.04.2 LTS up-to-date on maintenance
(0026108)
ardourwlk   
2021-08-16 22:53   
Recycled jack (and ardour), and was able to successfully create the new track.
(0026110)
ardourwlk   
2021-08-17 13:41   
After having apparently successfully saving the session yesterday, today I tried to open the session and got the message in the screenshot (ardfail_20210817_0934.png), and am unable to open the session.

Then I closed Guitarix, and now the session successfully opens. Some kind of port conflicts within Jack? I've never run into this before.
(0026111)
ardourwlk   
2021-08-17 13:45   
And now, leaving Ardour up, I am no longer able to start Guitarix. And... I stop Ardour, and Guitarix is able to start. Interesting.
(0026114)
ardourwlk   
2021-08-18 16:50   
I boosted the number of ports in jack up to 1024, and am able to work again. Perhaps a tooltip help when giving that "failed constructor" message?
(0026187)
x42   
2021-10-12 12:24   
Glad you figured out the solution.

As for your suggestion: Ardour cannot know why registering a port fails with the server. In case of JACK, jackd reports the error and "port limit reached" is only one possibility.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8462 [ardour] bugs minor always 2020-10-29 00:40 2021-10-12 05:47
Reporter: chance_favre Platform: Microsoft  
Assigned To: OS: Windows  
Priority: normal OS Version: 10  
Status: new Product Version: 6.3  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Transport Controls Are Broken when using ASIO::ZOOM R16_R24 ASIO Driver
Description: Ardour 6.3
Jack:
Version: 0.3.13.10
Build: Sep 21 2015 20:12:10

ONLY happens when using the ASIO::ZOOM R16_R24 ASIO Driver in Jack. That driver can be found here:
https://zoomcorp.com/en/jp/digital-mixer-multi-track-recorders/multi-track-recorders/r16/r16-support/
Tags: transport
Steps To Reproduce: 1. boot windows
2. connect ZOOM R16 via USB, configure R16 as audio interface (click the enter button 3 times)
3. Launch qjackctl (Qt GUI for Jack), click Setup >> Interface, then select ASIO::ZOOM R16_R24 ASIO Driver
4. Start Jack server
5. Launch Ardour 6.3, make a new recording session
6. Begin recording some audio
7. Try normal transport operations with the mouse, stop, start, record enable.
8. Try to use the spacebar and hotkeys.
9. There seems to be some kind of click/key capture logic indexing issue or something because (although I have not yet found a pattern to the malfunctioning) it SEEMS like it is triggering the wrong events or something.
10. Same problems exist in playback mode (not recording)
Additional Information: I am using a lenovo laptop, and my clicking device is the touchpad, so I also tried a USB mouse -- same problem.

It seems like after the first time you click in the "track window" where the audio waveforms are, then the controls work for one or two events, but after that the space bar no longer toggles playback, and then you click on the gui controls, and maybe that works or the second time it does.

If I use the ASIO::ASIO4ALL v2 driver, the transport functions more predictably.

This one is a doozy.
System Description
Attached Files: transport.PNG (51,698 bytes) 2020-10-29 00:40
https://tracker.ardour.org/file_download.php?file_id=3861&type=bug
Notes
(0025201)
chance_favre   
2020-11-05 14:30   
I am happy to help troubleshoot this bug. With a little guidance I'm sure I can get a dev environment up and running so I can test things.
Please let me know what I can do to help! Thanks!
(0025330)
chance_favre   
2020-12-19 21:18   
Bump -- I would love to help in resolving this bug. If anyone has any ideas how I can get started, please let me know.
(0025347)
painltd   
2020-12-23 11:29   
I have similar problems (on Ardour 6.5.0 Intel 64-bit), I click play and then stop and sometimes it continues playing. Space bar does not help but sometimes clicking again it does.

Additionally, I am able to record audio but can't hear it during playback. If I listen to the file in Windows' file explorer it has been properly recorded but can't hear during Ardour playback. Routing is correct as I have the exact same routing settings in my Linux machine and it's working perfectly fine. Do you have this issue @chance_favre ?


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8809 [ardour] bugs minor always 2021-10-06 19:21 2021-10-08 19:45
Reporter: eastone Platform: PowerMac G5/G4  
Assigned To: OS: OSX  
Priority: normal OS Version: 10.5.8  
Status: new Product Version: 6.9  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Crashes when adding new midi track witht General MIDI synth instrument
Description: Ardour crashes on PowerMacs G5 and G4 when adding a new track only with General MIDI synth instruments.
Crash log attatched.
Tags: ppc
Steps To Reproduce: Steps to reproduce:
1) Open Ardour
2) F.e. double click to add a new midi track, choose General MIDI synth instrument (only this instrument!) The rest of instruments seems to be ok.
3) And pointer changing to beach ball and app crashes.
Additional Information:
Attached Files: Ardour6_2021-10-06-215905_g5s-power-mac-g5.crash (54,284 bytes) 2021-10-06 19:23
https://tracker.ardour.org/file_download.php?file_id=4116&type=bug
Ardour6_2021-10-08-165528_g5s-power-mac-g5.crash (57,682 bytes) 2021-10-08 14:43
https://tracker.ardour.org/file_download.php?file_id=4117&type=bug
<
Notes
(0026178)
x42   
2021-10-08 11:32   
The problem here seems to be the plugin. does it work when creating a track without synth?
(0026179)
eastone   
2021-10-08 14:43   
No problems with empty track.
BTW, recently, I think I missed a second problematic plugin, SinGen. It crashes in the same way, but at least I can use it by swapping another working plugin in the project (this method does not work for General MIDI plugin)

SinGen crashlog attatched.