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.

MantisBT
View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9213 [ardour] bugs minor always 2023-01-29 23:06 2023-01-30 00:05
Reporter: Yruama_Lairba Platform: Debian GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Cue markers are ignored in some occasion
Description: In some occasion, Cue markers are ignored
Tags:
Steps To Reproduce: - start a new empty project
- create a new audio (or midi) track
- got to Cue windows
- in the audio track, load a clip into a cue slot, lets say cue A for the example
- select cue a of the track and set Follow options to again
- go to the editor view
- in cue markers lanes add a "cue A" marker at the beginning, that is Measure 1, Beat 1
- add a "stop all cues" marker at measure 3, Beat 2
- play project from beginning

expected: at end of measure 3 the Cue A should stop to play
result: at end of measure 3, the Cue A continue to play
Additional Information: i'm unable to join a project example
System Description
Attached Files:
Notes
(0027255)
Yruama_Lairba   
2023-01-29 23:17   
sorry, forgot some important things:
- tempo should be set at 180 bpm exactly
- sampling rate is 44,1khz (didn't try other sampling rates)
(0027256)
Yruama_Lairba   
2023-01-29 23:47   
missing another parameter, the problem occur with a buffer size of 256 samples. It doesn't occur with a size of 1024. I didn't yet try another buffer size
(0027257)
Yruama_Lairba   
2023-01-30 00:05   
for some obscure reason, i can't join a file to a message, so here is a onedrive link to a project where the issue occur:
https://1drv.ms/u/s!Ao9-ll0yecywgTDanL-TwjcCluX4?e=2n2dWR

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9212 [ardour] bugs minor always 2023-01-29 17:21 2023-01-29 17:24
Reporter: sollapse 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: VST3 parameter issue in bx Console SSL 9000
Description: The 'console channel' parameter for the bx console SSL 9000 VST3 cycles between is high range while scrolling through the values. The GUI fails to step through the values properly, and the behavior is seen clearly using the automation track.

Tags:
Steps To Reproduce:
Additional Information:
Attached Files: params_sm.gif (865,293 bytes) 2023-01-29 17:24
https://tracker.ardour.org/file_download.php?file_id=4361&type=bug
Notes
(0027254)
sollapse   
2023-01-29 17:24   

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9211 [ardour] bugs minor always 2023-01-29 14:57 2023-01-29 14:57
Reporter: dking952012 Platform: Microsoft  
Assigned To: OS: Windows  
Priority: normal OS Version: 11  
Status: new Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Grid editor does not visually change when using triplets/tuplets
Description: When changing the grid to triplet and tuplet variations, the visual markers only reflect /4 subdivisions. For example, a 16th note triplet selection only shows straight 16ths on the grid. The cursor/marker will still snap to triplet start locations, but this does not match up visually.
Tags:
Steps To Reproduce: New session

New midi track

change grid to 1/3 or 1/6 triplets

ruler does not mark triplets correctly

can still edit notes to snap to triplet position, they just appear "off"
Additional Information:
System Description Windows 11
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9206 [ardour] bugs minor always 2023-01-24 15:20 2023-01-29 13:55
Reporter: colin.y Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: VST3 Plugin "Zebralette" does not recall state correctly when session re-opens
Description: When I re-open a saved session which contains a native Linux VST3 plugin for the Zebralette synth, I have to manually reset the plugin's inbuilt preset.

This did not occur in 6.9 or even 7.2.0.

I first noticed it in 7.2.104 and have since verified it in 7.2.148.

I see the same behaviour when I create a new session containing only one track with this plugin.
Tags: 7.2, Linux, plugin, VST3
Steps To Reproduce: Create a MIDI track in 7.2.148 with Zebralette and select inbuilt plugin preset. Save and close session.

Re-open session and although the preset displays the correct preset name, the plugin's settings are not correct, so I have to manually re-select the preset to obtain the desired sound.
Additional Information: VST3 module-path '/home/colin/.vst3/u-he/Zebra2.vst3/Contents/x86_64-linux/Zebra2.so'
System Description
Attached Files: _PluginTest7_2_171.ardour (166,097 bytes) 2023-01-29 13:55
https://tracker.ardour.org/file_download.php?file_id=4360&type=bug
Notes
(0027253)
colin.y   
2023-01-29 13:55   
I have re-tested using build 7.2.171, with the same results described previously. I also see issues with some other VST3 synth plugins (e.g. OT GENESYN 2).

I do not see the problem when I open the session (created with 7.2.171) with 7.2.0.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
6768 [ardour] features minor N/A 2016-02-11 00:37 2023-01-29 09:18
Reporter: timbyr Platform:  
Assigned To: timbyr OS:  
Priority: normal OS Version:  
Status: assigned Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Zoom Editor track area/canvas by clicking and dragging in the ruler
Description: Some other DAW's have the ability to zoom by clicking and dragging in a certain area of the canvas. In Ableton and Cubase this is in the ruler area.

I'm reporting this issue to see if there is any interest in having similar functionality in Ardour.

I prefer to use this functionality to zoom in those applications as it allows me to use the "nipple" on my laptop to zoom without moving my hands out of position.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: ruler-drag-zoom.webm (3,679,162 bytes) 2016-02-11 00:40
https://tracker.ardour.org/file_download.php?file_id=2867&type=bug
Notes
(0017902)
timbyr   
2016-02-11 00:41   
I uploaded a short video to demonstrate what I mean.
(0017904)
timbyr   
2016-02-11 01:00   
(Last edited: 2016-02-11 01:01)
One concern with this sort of functionality is that the performance of the canvas, as with a lot of items it can really slow the zooming operation down to the point of being almost useless.

(0018581)
timbyr   
2016-09-09 12:03   
I have a small series of changes that implements this functionality as an option that is off by default.

If there is no negative feedback I will commit the changes so that the functionality can at least be tested.
(0018893)
cooltehno_bugs   
2016-10-31 15:08   
Great feature! How it would be nice to see it committed)
(0018936)
timbyr   
2016-11-11 04:23   
This feature has been committed to master branch as of revision 5.4-317-gdac2d41 and so can be tested in a nightly >= 5.4.317

It is enabled via Preferences -> Editor -> Use time rulers area to zoom when clicking and dragging vertically

Feedback welcome.
(0018941)
rutsch   
2016-11-12 09:16   
(Last edited: 2016-11-12 09:19)
Excellent! Works great for me. Now add scrolling instead moving the playhead when moving left or right and this is perfect.

Edit: I see, it's scrolling when going to the left and right border.

(0018942)
timbyr   
2016-11-12 11:07   
Yes, it should scroll when moving the mouse to the edge of the track canvas area.

I think there might be a few tweaks to improve it.

One would be if there was a vertical drag threshold that had to be passed in order for zooming to start so that if you just click up in the ruler it doesn't zoom unless you drag the mouse a few pixels.

The other would be to see if only zooming when the mouse moves vertically every two or three pixels instead of every pixel would improve the issue with the delay in redrawing the waveforms.

I'll try to play around with these ideas when I get time. Let me know if you can think of anything else.
(0018943)
rutsch   
2016-11-12 15:15   
Sounds good, nothing to add from me at this time.
(0018954)
cooltehno_bugs   
2016-11-13 21:46   
Thanks for contribution!
After night-build testing I've got two Ideas:

1) It could be very comfortable (from Bitwig using):
- Click+drag vertically - zooms in/out;
- Click+drag horizontally - shifts right/left.

The horizontal shifting by clicking&dragging - could be nice for your Ardour's feature!

2) The playhead goes with clicking in the area of the canvas - it's not comfortable. It would be nice to zoom and shift no effecting the playhead position. Or may be for zooming/shifting - to use a middle mouse button (left m.button - to leave for playhead positioning).
(0018960)
timbyr   
2016-11-14 03:31   
I don't have access to Bitwig but I'm assuming this zoom/scroll operation you are describing has the same behaviour as in Ableton Live.

The way it is implemented currently was based on the behaviour in Cubase.

After using Ableton Live lite for a bit to test, I think I prefer its behaviour (and your suggestion) that it also scroll and that it not manipulate the playhead position. It seems to make navigation much easier and predictable when scrolling than trying to move the cursor to the side of the canvas to scroll.

It will probably be a bit more complicated to implement and I'll wait for some more feedback on the current behaviour before investing any time in changing it.
(0027238)
arpad.jakab@outlook.hu   
2023-01-25 10:38   
Hi! The vertical dragging of the mouse starting in the time ruler is working opposite to what Ableton Live has. I have in my fork reversed the direction. The best explanation why this is better than in the current version is that: (1) one has to drag the mouse up to zoom in, and the screen top sets a limit to the zoom, and one has to repeat the movement for more in-depth zooming. (2) when dragging down the mouse pointer will be exactly where I want it to have it: above the zoomed in tracks.
(0027252)
timbyr   
2023-01-29 09:18   
(Last edited: 2023-01-29 09:18)
The current mouse drag zoom behaviour in Ardour is not the same as when I implemented the feature and the zoom direction was inverted. The current behaviour of dragging up to zoom in is not useful to me.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9210 [ardour] features feature have not tried 2023-01-28 17:07 2023-01-28 17:07
Reporter: benald Platform: Microsoft  
Assigned To: OS: Windows  
Priority: low OS Version: 11  
Status: new Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Standard keyboard editing in track comments, plz
Description: Ctrl C,Z and V in Windows. Thanks.
Tags:
Steps To Reproduce:
Additional Information:
System Description Windows 11
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9209 [ardour] features minor have not tried 2023-01-28 14:56 2023-01-28 14:56
Reporter: benald Platform: Microsoft  
Assigned To: OS: Windows  
Priority: normal OS Version: 11  
Status: new Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Could we have editable names for automation controllers plz?
Description: This would lovely, and, thrice, lovely. XXX
Tags:
Steps To Reproduce:
Additional Information:
System Description Windows 11
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9204 [ardour] bugs minor sometimes 2023-01-24 10:55 2023-01-28 14:33
Reporter: benald Platform: Microsoft  
Assigned To: OS: Windows  
Priority: normal OS Version: 11  
Status: new Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Crash during repeat pasting region from several tracks (including control data)
Description: I have created a select region over several tracks, copied it and pasted it in a clear section after all of my recorded data. When I pressed 'Control-V' a second time the pasted section appeared briefly immediately following the first pasted instance of the data in the timeline. Immediately after this Ardour crashed.
It seems that if I wait for some time between pressing 'Control-V' then crashing will not occur.
The screen grab I am uploading shows the selected data towards the left of the screen and one instance of that selected data successfully pasted towards the right of the screen.
Here is my hardware spec:

Processor AMD Ryzen 7 4700U with Radeon Graphics 2.00 GHz
Installed RAM 8.00 GB (7.37 GB usable)
System type 64-bit operating system, x64-based processor



 
Tags:
Steps To Reproduce:
Additional Information:
System Description Windows 11
Attached Files: ardour paste crash.png (234,266 bytes) 2023-01-24 10:55
https://tracker.ardour.org/file_download.php?file_id=4352&type=bug
png

Ardour-debug.log (4,180 bytes) 2023-01-28 14:33
https://tracker.ardour.org/file_download.php?file_id=4358&type=bug
ardour hangs here.png (147,132 bytes) 2023-01-28 14:33
https://tracker.ardour.org/file_download.php?file_id=4359&type=bug
png
Notes
(0027243)
paul   
2023-01-26 05:45   
We would need a debug backtrace to be able to work on this. https://ardour.org/debugging_ardour
(0027246)
benald   
2023-01-26 18:02   
I've got this project do what I want by exporting all of the midi and loading it into a new project. I'll look into installing the bug tracking software at the weekend or next week when I'm back home.
(0027249)
benald   
2023-01-27 16:37   
Paul, the debug version web page download button is greyed out for me whether I select free or full download version. I am a subscriber.
(0027250)
benald   
2023-01-27 16:48   
Sorry, ignore that last message. Download is working now I selected '64 bit'.
(0027251)
benald   
2023-01-28 14:33   
Hi Paul. I have got a debug log for you. I had slightly different behaviour with the debugger running. I *could* re-open my compromised project under the debugger (without the debugger Ardour hung at the screen grab shown. I ran the debugger by running the debug.bat in the ardour7 file. Is this right? The instructions in your how to debug page may need updating...
https://ardour.org/debugging_ardour.html

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9208 [ardour] bugs crash random 2023-01-25 22:50 2023-01-27 01:47
Reporter: Schmitty2005 Platform: Microsoft  
Assigned To: OS: Windows  
Priority: normal OS Version: 10  
Status: new Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ardour 7 Nightly Win 10 7.2.130 DBG Drag Clip onto MIDI with VST loaded
Description: Adding a track with a VST and loading a MIDI clip ('Dm7' Chord from content) caused crash. It may have been related to dragging content while content was still playing in preview (Auto-Play Checked).

A few crashes with different VST's over a period of a few days. This particular VST was the Steinberg Model-E VST. This is the only crash I had DeBuG version running and able to get a log.
Tags: CLIP DRAG CRASH TRACK MIDI
Steps To Reproduce: Open new midi track with VST Instrument. Open clip selector. Drag MIDI Chord onto new track while playback is active. It may or may not crash.
Additional Information: I update to newest nightly and post more logs if I catch this happening again.
System Description
Attached Files: Ardour-debug.log (20,205 bytes) 2023-01-25 22:50
https://tracker.ardour.org/file_download.php?file_id=4354&type=bug
Ardour_DBG_CLipDragCrash.log (91,850 bytes) 2023-01-25 22:55
https://tracker.ardour.org/file_download.php?file_id=4355&type=bug
Ardour_SSL_V-MIDI_PORTS.png (52,286 bytes) 2023-01-26 12:54
https://tracker.ardour.org/file_download.php?file_id=4356&type=bug
png

Ardour-debug_Crash2.log (62,601 bytes) 2023-01-27 01:47
https://tracker.ardour.org/file_download.php?file_id=4357&type=bug
Notes
(0027241)
Schmitty2005   
2023-01-25 22:55   
Disregard other log file. Use this one.
(0027242)
paul   
2023-01-26 05:43   
Sadly, I doubt that this will be solvable via any rational process. The crash happens during a condition that just should never happen.
(0027244)
Schmitty2005   
2023-01-26 12:54   
Would that condition have to do will the ten Virtual Midi ports that the SSL-360 Plug in has created ? (pic attached).
(0027245)
paul   
2023-01-26 15:46   
Seems highly unlikely. That said, actual plugins should not do that.
(0027247)
Schmitty2005   
2023-01-27 01:45   
Correction, the SSL 360 is not a plug in. It is an Application that interfaces with a couple of SSL plug ins.
(0027248)
Schmitty2005   
2023-01-27 01:47   
Another log of a crash instance in Win10. I was unable to crash Ardour Linux (Debian / Ubuntu).

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9207 [ardour] bugs major always 2023-01-24 17:33 2023-01-25 12:38
Reporter: benald Platform: Microsoft  
Assigned To: OS: Windows  
Priority: normal OS Version: 11  
Status: new Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Splitting more than two midi regions (with control data and at the same playhead position) renders project unrecoverable
Description: I have three midi tracks, each with control data tracks. I found a region I wanted to copy and paste to repeat. I had serious issues doing this (see my bug report from earlier today - 24th January 2023 - link below) so I thought I might be able to achieve what I wanted by splitting each track at the start region point and the end region point. Every time I did this I could copy and paste the region once or twice before the project crashed. If I pasted the copied region just once and saved it, closed Ardour and tried to reopen the project Ardour would hang at the screen grab supplied.
I repeated this process many times and the found the fault to be consistent.
In order to narrow down the failure point I decided I would save the project at each of the six split points, save the project and try and reopen it. I was able to re open the project twice (after the first and second splits). The screen grabs are:-
1) Snip 1 (before project saved and reopened successfully)
2) Pre snip 2
3) Snip 2 (before project saved and reopened successfully)
4) Pre snip 3
4) Snip 3 (before project saved and could no longer be opened)
My bug report from earlier today: https://tracker.ardour.org/view.php?id=9204
Tags:
Steps To Reproduce:
Additional Information:
System Description Windows 11
Attached Files:
Notes
(0027230)
benald   
2023-01-24 17:56   
1) Snip 1 (before project saved and reopened successfully)
2) Pre snip 2
3) Snip 2 (before project saved and reopened successfully)
4) Pre snip 3
4) Snip 3 (before project saved and could no longer be opened)
(0027233)
benald   
2023-01-24 18:52   
I'll try again to upload the screen shots. I'm on holiday in a rural area at the moment and the internet isn't great...
(0027240)
benald   
2023-01-25 12:38   
Update: I have successfully split three midi tracks in two places each - containing ten automation tracks between them. The project could then be successfully saved and reloaded. The difference between this case and the case in which saving the project after the total six track splits (or, more likely, I think - any split in a third track), saving the project and the project being unrecoverable appears to be the eight further automation tracks (all of the automation associated with the third midi track) being cleared. This suggests to me that there is a tipping point somewhere between a total of ten and eighteen automation tracks in my setup.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9194 [ardour] bugs major sometimes 2023-01-07 10:34 2023-01-25 11:09
Reporter: Windsurfer152 Platform: Debian GNU  
Assigned To: paul OS: Linux  
Priority: high OS Version: (any)  
Status: assigned Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Manually edited MIDI cc messages do not retain position
Description: When entering a value it will sometimes appear to be ignored on playback. In fact the change will take place later than where it was entered. Changing the zoom level shows that the value is no longer where it was placed. Reverting to the initial zoom level confirms this.

It doesn't seem to matter whether snap is on or off, in lock or slide mode, in discrete or linear mode, or what the zoom level is when entering the values.

The issue does NOT occur when values are initially drawn. However once they are moved horizontally the behaviour occurs. This makes accurate use of controllers almost impossible.

Values can be edited using Grab, Draw or Internal Edit mode. The issue seems to be present regardless of which is chosen.
Tags:
Steps To Reproduce: Create a MIDI region. Make a controller visible and set to "play". Draw in some values. Edit their horizontal position. Note where those values are in relation to the timecode. Zoom in/out. Check position of value events. Behaviour is more obvious when discrete mode is used.
Additional Information: While working out how to reproduce the issue I note that when snap is enabled it sometimes seems impossible to actually snap to the grid. Possibly related?

Examples attached. Inputted values are 25, 8, 73, 95
System Description
Attached Files: Screenshot_2023-01-07_08-20-37.png (127,360 bytes) 2023-01-07 10:34
https://tracker.ardour.org/file_download.php?file_id=4341&type=bug
png

Screenshot_2023-01-07_08-22-51.png (128,631 bytes) 2023-01-07 10:34
https://tracker.ardour.org/file_download.php?file_id=4342&type=bug
png

Screenshot_2023-01-07_08-23-14.png (129,421 bytes) 2023-01-07 10:34
https://tracker.ardour.org/file_download.php?file_id=4343&type=bug
png

Screenshot_2023-01-07_08-23-47.png (129,115 bytes) 2023-01-07 10:34
https://tracker.ardour.org/file_download.php?file_id=4344&type=bug
png

Screenshot_2023-01-07_08-24-23.png (129,387 bytes) 2023-01-07 10:34
https://tracker.ardour.org/file_download.php?file_id=4345&type=bug
png

Screenshot_2023-01-07_08-24-53.png (129,271 bytes) 2023-01-07 10:34
https://tracker.ardour.org/file_download.php?file_id=4346&type=bug
png

Screenshot_2023-01-07_08-25-29.png (128,841 bytes) 2023-01-07 10:34
https://tracker.ardour.org/file_download.php?file_id=4347&type=bug
png

Screenshot_2023-01-07_08-26-22.png (121,643 bytes) 2023-01-07 10:34
https://tracker.ardour.org/file_download.php?file_id=4348&type=bug
png

ardour bug 2023-01-14 200143.png (144,313 bytes) 2023-01-14 21:13
https://tracker.ardour.org/file_download.php?file_id=4349&type=bug
png

2023_Folk_MIDI.zip (250,113 bytes) 2023-01-25 06:47
https://tracker.ardour.org/file_download.php?file_id=4353&type=bug
Notes
(0027185)
benald   
2023-01-14 21:13   
I'm having this issue, too - In Ardour 7.2 on Windows. I'm hoping to find how to find a reasonable workaround until this is fixed. If you look at my screen shot there are two tracks with CC midi controls. In the lower track the repeated section has edited CC data that remains stable during zoom operations. I'm currently working on the track higher up the screen with the single region of CC data. This will currently degrade with almost any operation - including saving the file, closing Ardour and re-opening it. I'm wondering if the bug is at its worst on duplicated tracks. I have (since I started writing this) and I think the problem might be slightly less bad with tracks made from scratch (rather than duplicated) and notes copied and pasted to the new track. Also I cut the region into two at the tempo change. At this point the section after the tempo change behaved itself after I added some CC data and I eventually got he region before the tempo change to behave by editing the CC data the same distance ahead of where it slipped by during a zoom - since at this stage it was only seeming to slip once. Hopefully there is something useful here to either people wanting to make their CC data behave and/or coders trying to fix the problem.
(0027227)
paul   
2023-01-24 17:37   
was not able to trivially reproduce this.
(0027228)
paul   
2023-01-24 17:41   
if you could attach a session that demonstrates this behavior, that would be helpful.
(0027231)
benald   
2023-01-24 18:07   
I have just been able to replicate the problem by editing the control data on the track 'Siren Synth' then zooming in and out again in the time domain.
I'm sorry if this upload fails - I'm on holiday in a rural area (hence having more time to spend on Ardour) - which is very nice but the internet is terrible. I'll keep trying.
(0027232)
benald   
2023-01-24 18:22   
I haven't been able to upload the file because of internet problems. The first track in my project was an imported audio file. I deleted that track to upload my problem project and then had another look at the problem control data. The problem seems to have gone away. I recorded some audio to recreate the presence of an audio track and the problem is still absent. I'll try and get the original file to you as soon as I can, though.
(0027234)
benald   
2023-01-24 21:51   
'storm bass to upload' provides the root folder of my project and some sub folders
'storm bass root files' are files to be extracted into the project root folder
'cardinal patches' is a sub folder of root
'interchange' is a sub folder of root
(0027235)
paul   
2023-01-24 22:04   
I don't see the link .... am I just missing it?
(0027236)
benald   
2023-01-24 22:22   
I'm having trouble with Mantis, Paul. I have sent an email to the address on the credits page. That's you isn't it?
(0027237)
Windsurfer152   
2023-01-25 06:47   
Apologies for being late to the party with this.

Attached is the session from which I took the screenshots in the original post.

It uses SFZ and DecentSampler instruments which obviously aren't in the attachment and which may be a problem.

However I've added a track using General MIDI Synth which shows the same behaviour. I attempted to add some some CC1 data on the 2nd 16th note of each beat. All seemed ok until I adjusted the values (not the horizontal position). I saved the session without zooming in the hope you might see the mismatch.

I notice a previous bug report 0009142 also related to MIDI automation and involving tempo changes. I do have tempo changes in this session so perhaps the 2 are connected.
(0027239)
benald   
2023-01-25 11:09   
Re: tempo changes. My project also has at least one tempo change in it.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9205 [ardour] bugs minor have not tried 2023-01-24 15:07 2023-01-24 17:44
Reporter: Sinuslabs Platform: GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Plugin crashes in Ardour with "X Error of failed request: BadWindow (invalid Window parameter)" on Plugin Scan
Description: Hello Ardour Team,
I am a Plugin Developer who is also releasing on Linux. My Plugin runs fine but I have a customer reporting a issue with Ardour on VOID Linux. This crash is not happening in other DAWs only in Ardour. I am unable to reproduce this issue with my own System and do not know where to start to solve this. The customer is running X11.

The Plugin I am developing is open source and can be found here: https://github.com/Sinuslabs/Reach

VST3 module-path '/home/rutsch/.vst3/Reach.vst3/Contents/x86_64-linux/Reach.so'
[Info]: Scanning: /home/rutsch/.vst3/Reach.vst3
X Error of failed request: BadWindow (invalid Window parameter)
  Major opcode of failed request: 20 (X_GetProperty)
  Resource id in failed request: 0x0
  Serial number of failed request: 54
  Current serial number in output stream: 54
Scan Failed.
Tags: 7.2, VST3, window, x11
Steps To Reproduce: Add Plugin to .vst3 folder
Open Ardour in Void Linux
Scan Pluginins
Fails
Additional Information:
System Description
Attached Files:
Notes
(0027224)
Sinuslabs   
2023-01-24 15:53   
The problem was solved by the customer by installing the xsettingsd package and creating a empty config file. Afterwards Ardour was able to successfully scan the Plugin.
(0027225)
paul   
2023-01-24 16:06   
Those errors typically happen when a thread that is not the main GUI thread attempts to draw.

Most/all applications on Linux use a single-threaded GUI (even when there are multiple other threads), and drawing from other threads will always cause issues.

Can you comment on whether or not this could be the case in your plugin?
(0027226)
Sinuslabs   
2023-01-24 16:09   
No my plugin is using a single thread for the GUI and runs the DSP on the other threads.
(0027229)
paul   
2023-01-24 17:44   
Your plugin works without errors here on my system (Debian 11). The issue would appear to be user-specific.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9061 [ardour] bugs minor always 2022-11-01 08:51 2023-01-24 12:06
Reporter: surfinspots Platform: Debian GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.0  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Undefined state while midi recording and pressing "arrow left"
Description: When recording MIDI (I've tried it with an audio track and there it works) and pressing arrow-left the playback line stops and it seems that
Ardour is a bit in an undefined state.
The "stop" button doesnt work anymore.
The "ruler" becomes messed (I added a screenshot).
Tags: 7.2, Midi, record
Steps To Reproduce: - MIDI Track on record
- start recording
- pressing left-arrow key

Additional Information:
System Description
Attached Files: ardour-midi-record-arrow-left-bug.png (11,606 bytes) 2022-11-01 08:51
https://tracker.ardour.org/file_download.php?file_id=4271&type=bug
png

ardour-bug-2023-01-21_10.03.07.mp4 (435,868 bytes) 2023-01-21 09:06
https://tracker.ardour.org/file_download.php?file_id=4351&type=bug
Notes
(0027219)
surfinspots   
2023-01-21 09:06   
this seems not be fixed in the actual master. So I maybe I need to provide a video.
In this video I only press the global record button with the mouse and the arrow right button while recording so the play head jumps back. As you may see ... the scale is becoming corrupt and the recorded regions in the midi track have been deleted on pressing arrow back.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9203 [ardour] bugs minor always 2023-01-23 20:04 2023-01-23 20:18
Reporter: Edward Platform: Apple Macintosh  
Assigned To: OS: MacOS  
Priority: normal OS Version: 10.12 or later  
Status: new Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: General UI slowness on an Intel Mac (compared to Ardour 6.9)
Description: The Ardour UI updating gets excessively slow when the amount of MIDI tracks grows. I noticed this when working on sessions and created a sample session to reproduce it.

In the example there are 45 MIDI tracks with imported MIDI files from previous Ardour sessions. I created the session in Ardour 6.9. When opening the same session in Ardour 7.2. it looks like the frame rate drops roughly to one fourth to what it was in 6.9.

I am running a 4K display (3840x2160). Scaling the display down to Full HD resolution improves the performance but the difference between 6.9 and 7.2 stays roughly the same.
Hiding tracks has an effect to the performance but still with just one track visible the frame rate on 7.2 is roughly on the level it is with all of them in 6.9.

The computer itself is not struggling - Mac Activity Monitor reports CPU usage of 5% - 8% and the memory consumption is also moderate between 400 and 700 MB. Audio / MIDI performance is flawless. Just the UI lags behind. In Ardour performance setting I have "all but one CPU" selected.

To try whether the computer itself is the problem I created the same session in Reaper. It ran considerably smoother there even if the playhead was slightly laggy.
Tags: 7.2, mac, ui
Steps To Reproduce: Test session on Dropbox:
https://www.dropbox.com/s/o8p52xoep1hydd3/Ardour-UI-perf-6-7.zip?dl=0

Video on how the UI looks on Ardour 7.2:
https://www.dropbox.com/s/lv9bywi662lbqnu/Ardour-72-4K.mov?dl=0

Video on how the UI looks on Ardour 6.9:
https://www.dropbox.com/s/ynrbbovm71lyphz/Ardour-69-4K.mov?dl=0
Additional Information: Computer:

MacBook Pro 16" 2019
Intel Core i9 2,4 GHz 8 cores
32GB RAM

macOS Monterey 12.6
System Description
Attached Files:
Notes
(0027223)
Edward   
2023-01-23 20:18   
The external screen I am using is not an Apple one. I tried setting the color correction to "Generic RGB Profile" as suggested in the other Mac performance related issue. It did improve the performance a little.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9201 [ardour] bugs major always 2023-01-18 11:45 2023-01-23 12:15
Reporter: bsj Platform: Apple Macintosh  
Assigned To: OS: MacOS  
Priority: high OS Version: 10.12 or later  
Status: new Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Slow Editor performance caused by the new opaque regions on Ardour 7.2 & Mixbus 8.2 Release!
Description: The editor section is slow when zooming in and out of audio regions.
Tags: 7.2, 8.2, Ardour, Editor, MIxbus, performance, slow
Steps To Reproduce: this issue is noticeable with a good amount of tracks, however 1 or 2 tracks seem to be ok but in a real mix environment this is not ideal as the slow performance will occur when you are having a real world mix session, if you add lets say 16-30 tracks as a example and then you zoom in and out on all regions its very slow, also you will notice this when you set the Zoom setting to (Fit All Tracks) and when you scroll around/zooming in and out its slow. Prior versions such as 7.1 for Ardour and Mixbus 32c 8.1 did not have any issues with this.
Additional Information: The new opaque regions seems to be causing this. Mixbus 8.1 and Ardour 7.1 do not have this issue, the only way to resolve this and get the same performance zooming in and out etc is to adjust the alpha setting to 0 which causes all audio regions to disappear and thus the perforce is back again but is useless due to the ability not to see your audio regions is gone. This new feature seems to be slowing down Ardour and Mixbus editor performance and should be changed and re-implemented in a way that doesn't create a performance hit.
System Description
Attached Files:
Notes
(0027187)
bsj   
2023-01-18 11:46   
I hope they can fix this issue. really been a drag and having to stay on older versions because of this.
(0027190)
paul   
2023-01-18 14:42   
The problem is that this issue appears to be system-dependent. We have tried to reproduce it on various macs in our possession, and none of them show the issue. It therefore becomes unclear whether this is hardware dependent, or triggered by some 3rd party software, or specific to a very precise version of macOS, or something else.
(0027191)
bsj   
2023-01-18 14:59   
I’m not sure if all m1 users have this issue or if some do and don’t? I tested this on 2 m1 computers and they both have this issue, one of the computers has a more fresh install on Monetary Mac OS. I’m not sure if going to Mac OS Ventura would help, I also don’t know if the latest versions of ardour and mixbus are compiled for the latest Mac OS either.
(0027192)
bsj   
2023-01-18 15:25   
Also were any your tested machines powered by Apple silicon. This may be a apple silicon issue but I don’t know if I read that someone using Linux had the same issue or not.
(0027193)
paul   
2023-01-18 15:39   
Yes, we've tested on 2 Apple Silicon systems.
(0027194)
bsj   
2023-01-18 21:31   
What version of OS was it tested on
(0027195)
bsj   
2023-01-18 21:51   
Also I know the slowness can be subjective to different people if they are not aware of use the program in different ways, example they may have a mouse with a slower mouse scroll speed for example. But on the systems you tested, there was absolutely no speed difference in the scroll speed or response rate of zooming in and out of all regions on screen on a large mix where all or most of the tracks or regions are displayed on the screen at the same time. I wish someone posted a video of their unaffected setup, it’s a bit discouraging since I tested on 2 different machines with same issue. Is this only a Mac OS issue, do people on windows or Linux have this issue at all?
(0027196)
paul   
2023-01-18 22:45   
Nobody has reported this behavior for Linux or Windows.

This is the sort of thing we've (and Reaper) have encountered in the past: https://user.cockos.com/~deadbeef/index.php?article=516
(0027197)
bsj   
2023-01-18 23:32   
Oh ok, sometimes I really dislike Mac OS for when things are just complicated. I guess the only way to fix this is for ardour to reverse the feature that causes this, but I know that’s not likely going to happen since it doesn’t affect all of users.
(0027198)
paul   
2023-01-19 00:49   
We won't reverse it for now, but not because it doesn't affect all users - more because we want to find a system where we can debug whatever is happening, and then fix it.
(0027199)
bsj   
2023-01-19 02:04   
Which operating system was it tested on.
(0027203)
bsj   
2023-01-19 16:59   
This issue seems to be a graphics acceleration issue. When disabled mixbus 8.2 works much smoother. However not sure on any possible cpu performance costs that I may face.
(0027204)
x42   
2023-01-19 22:26   
@bsj Can you elaborate which, and how you "disable graphics acceleration" -- there are various options.

I use Ardour on a M2 macbook air running Ventura 13.1, and do not have and issues. I do not use external screens though.
I could imagine that perhaps using some external displays with color correction, esp non apple hardware, might have an effect.
(0027205)
bsj   
2023-01-20 00:42   
I disabled it via the settings/preferences menu, not via terminal code. Which I do want to try. However I’m not sure why some have this issue and some don't, when I disable the hardware acceleration it does improve and it does improve even more when I reduce my Mac OS resolution scaling.

I’m not sure if I will have my CPU usage when running with disabled hardware acceleration, Does it also stop plugins from using GPU? When using ardour/mixbus I don’t see any GPU usage other than my plugins that use GPU so I don’t know what hardware acceleration is doing.

Also I’m wondering how could this be resolved without disabling.

I also was wondering if ardour can use something other than open GL for rendering, I know apple has their Metal API and I know there’s Vulcan. Not sure if this is just fantasy for a daw like ardour and mixbus to utilize.


Also, have you tried loading up a typical mix session with about 16-30 tracks and set the zoom to fit so all regions fit on screen, then zoom in and out of all regions, are you saying that you don’t have any slow rendering or delayed loading etc.
(0027207)
x42   
2023-01-21 00:12   
Ardour is 2D (not 3D), so neither Vulkan or Metal will help. openGL is used as work-around to bypass color-correction (see paul's post above) on older systems (until Catalina).

I test with a session with 12 tracks visible, zoomed to show 5 seconds. With follow playhead as well as stationary playhead things are smooth using "more space" with the Retina screen.
Quatrz debug reports 30 fps.
(0027209)
bsj   
2023-01-21 00:45   
Oh, so what about plugins that use GPU for GUI, I don’t think most plugins have any 3D elements to them. Also I always thought ardour and mixbus would be benefit from GPU acceleration based on how mixbus mixer GUI looks.

Also what happens when you disable hardware acceleration if it doesn’t use GPU for rendering.
(0027210)
x42   
2023-01-21 00:54   
With Hardware acceleration Ardour renders directly to a NSView.
Without Hardware acceleration Ardour renders to an image-surface in memory and then the result is copied as bitmap to the NSView.
(0027211)
bsj   
2023-01-21 02:00   
Is their like a performance hit that is noticeable, is there a way I can see how it affects CPU?
(0027213)
x42   
2023-01-21 04:03   
Could you try if changing the color profile helps? Set

Apple System Preferences > Displays > Color Profile ... to Generic RGB Profile
(0027214)
bsj   
2023-01-21 04:40   
So I try this before or after I disable hardware acceleration?
(0027216)
x42   
2023-01-21 05:00   
Disable HW acceleration.
(0027217)
bsj   
2023-01-21 06:06   
Well disabling hardware acceleration and changing colour profile didn’t help do bc anything different, when I do disable hardware acceleration it does speed up the editor section.,
(0027222)
bsj   
2023-01-23 12:15   
Text is a bit blurry without hardware acceleration. So I have to keep that in mind also.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8986 [ardour] bugs crash always 2022-10-14 23:39 2023-01-22 22:40
Reporter: Schmitty2005 Platform: Microsoft  
Assigned To: paul OS: Windows  
Priority: normal OS Version: 10  
Status: assigned Product Version: Mixbus 8.x  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: PPGWave3 VST3 Crashes when loaded
Description: Loading new MIDI track with PPGWave3 VST3 causes crash.

Causes crash in Aroudor 6, Ardour 7 and Mixbus 7, and Mixbus 8
Tags: crash, Multi-out, VST3
Steps To Reproduce: Start new session. Add MIDI track with PPG Wave 3 VST ( https://waldorfmusic.com/en/overview )
Additional Information: Causes crash in Aroudor 6.9 ,7 and Mixbus 7(latest) , and Mixbus 8 (latest) as of 10/14/2022.

PPGWave3 does start with 16 MIDI inputs, 16 MIDI outputs and 16 MONO audio outputs. There have been problems with other plugins using multiple outputs. I will submit those as I run across them.

PPGWave3 works flawlessly in Reaper, Cubase, and Bitwig.

System Description
Attached Files: Ardour-debug_PPGWave_V3_VST.log (58,353 bytes) 2022-10-14 23:39
https://tracker.ardour.org/file_download.php?file_id=4222&type=bug
image.png (435,006 bytes) 2023-01-21 02:05
https://tracker.ardour.org/file_download.php?file_id=4350&type=bug
Notes
(0026603)
Schmitty2005   
2022-10-14 23:42   
Mixbus 8 should be read as Mixbus32C 8

30-day trial versions are also available : https://waldorfmusic.com/en/30-days-trial-versions
(0027200)
Schmitty2005   
2023-01-19 02:17   
Another VST3 plug-in with multi-outs also crashes Ardour 7.2.

The free plug-in is Cylcone available here :
     https://soniccharge.com/download?~cyclone

The free plug in comes with a VST2 version that works with multi-outs. Only the VST3 version crashes, just like the PPG Wave VST

Does anybody know of a free VST3 / VST2 Plugin with multi-outs that will work with natively with linux for posting better debug info ?
(0027201)
Schmitty2005   
2023-01-19 02:32   
Also a known issue on the Harrison Mixbus forums
https://forum.harrisonconsoles.com/thread-10991-post-61519.html#pid61519
(0027206)
paul   
2023-01-20 16:18   
The current nightly builds of ardour have support for multiout VST3 plugins, so we'd expect this problem to vanish. On the other hand, multiout plugins should not have crashed before - they just showup as stereo output plugins. Please try out a nightly build (there's a free demo if necessary) and let us know.
(0027212)
Schmitty2005   
2023-01-21 02:05   
All Multi-out VST3's that were loaded worked! Kontakt6 with 16 outs, PPGWave3 with 10 outs ( 5 Stereo channels) , Cyclone, and Absynth 5!

Ardour would not crash! I tried for over an hour doing normal DAW usage using the multi-out VST3s and experienced no crash! I added FX to main channel of the VST, and the outputs. Recorded MIDI, playback, looped, and edited MIDI. Dragged MIDI content from Kontakt worked as well!

Thank you!

Ardour is one of the best DAW's around! Thank you Paul!
(0027215)
paul   
2023-01-21 04:58   
Just for the record the multi-out bus work (and related fixes) were done by robin gareus, so more thanks to him! Good to hear, anyway.
(0027220)
Schmitty2005   
2023-01-22 22:38   
All of the VST3's with multi-out worked on 'Strict I/O' mode.

All VST3's with the exception fof Kontact 6 worked with 'Flexible I/O' mode.

When Kontact6 with 64 outs was selected and the pin mode of 'Flexible I/O' was used. Ardour-7.2.130-dbg-w64 nightly crashed and went straight to desktop. No backtrace was generated from the dbg console. I tried several times and was unable to get a crash log for this.

Should this be filed as a separate bug ?
(0027221)
Schmitty2005   
2023-01-22 22:40   
Robin,

Thank you for the VST3 multi-outs! And all of the other features you work on!

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9202 [ardour] bugs minor always 2023-01-20 20:23 2023-01-21 00:41
Reporter: rastin Platform: Arch  
Assigned To: x42 OS: Linux  
Priority: normal OS Version: (any)  
Status: resolved Product Version: 7.2  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: missing print() messages in lua dsp processor
Description: When using the print() function from within a lua dsp processor, the printed messages do not reach the log until something else prints a message.
Tags:
Steps To Reproduce: 1) Load any lua dsp processor that calls print() anywhere, such as in dsp_init, dsp_configure, or dsp_run
2) Notice that nothing appears in Ardour's log
3) Load any lua session script that calls print()
4) Notice that all of the print messages from 1) now appear in the log and the first printed message from 3) is missing its time stamp.
Additional Information: Skimming through Ardour's code, I wonder if an endmsg is missing on line 206 of luaproc.cc which reads as follows.
PBD::info << "LuaProc: " << s << "\n";

A similar line in session.cc (line 5249) has endmsg, and lua session scripts have no issue using print().
PBD::info << "LuaSession: " << s << endmsg;

System Description
Attached Files:
Notes
(0027208)
x42   
2023-01-21 00:41   
Thanks. Fixed in 7.2-128-g7e4bb2ff68. Keep in mind that print() is not realtime-safe and should only be used for debugging.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9193 [ardour] bugs major always 2023-01-06 16:22 2023-01-20 16:15
Reporter: stefan-franz Platform: Ubuntu  
Assigned To: x42 OS: Linux  
Priority: high OS Version: (any)  
Status: resolved Product Version: 7.2  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Errors export to mp3
Description: i exportet a very small project with 5 audio and 2 midi tracks. As mp3 always sound interrupts - as wav it works.
Same on "quick audio export and normal export as mp3.
On every export there are errors in the file - like a corrup mp3.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0027164)
x42   
2023-01-06 16:30   
Are you using Ardour 7.2.0 from ardour.org or a nightly version or a distro build?

After export can you view Window > Log. and copy the "Encode command: ..."
(0027165)
stefan-franz   
2023-01-06 16:48   
2023-01-06T17:44:38 [INFO]: Encode command: { /opt/Ardour-7.2.85/bin/ffmpeg_harvid -f f32le -acodec pcm_f32le -ac 2 -ar 44100 -i pipe:0 -f mp3 -acodec mp3 -q:a 2 -metadata comment=Created with Ardour -y /home/stefan/Studio/Ardour Projekte/110 Eigene Songs/Ole - Master/Ole - Stefan Franz-03/export/Ole - Stefan Franz-03.mp3 }

Here is the export 0:44 you hear it
https://nco.stefan-franz.de/index.php/s/JicbMmjY5QZt8D2
(0027186)
x42   
2023-01-17 15:21   
We believe this is fixed in 7.2-112.

I was not able to reproduce this myself, but some macOS users who also experience this issue confirmed a fix. Please test!
(0027202)
stefan-franz   
2023-01-19 07:52   
With 7.2.123 it works. Fixed. Thanks.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9142 [ardour] bugs minor always 2022-12-04 13:46 2023-01-18 13:31
Reporter: noedig Platform: Ubuntu  
Assigned To: paul OS: Linux  
Priority: normal OS Version: (any)  
Status: resolved Product Version: 7.1  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: MIDI automation drawing is offset after tempo change
Description: When drawing in a region's automation lane for a MIDI parameter, when there has been a tempo change prior to that region, the drawing input is offset, i.e. when clicking to add a new automation node, the new node does not appear at the click position.
Tags: automation, draw, Midi, tempo change
Steps To Reproduce: 1. Create a midi track with two midi regions.
2. In-between the regions, create a tempo change marker, so the first region is in 120bpm and the second region is in e.g. 180 bpm.
3. Enable a midi parameter automation lane for the track, e.g. Bender or CC.
4. In draw mode, drawing in the first region's automation area works fine. Drawing in the second region's automation area (after the tempo change) does not work correctly. When clicking to add nodes, they are offset i.e. do not appear where clicked.
Additional Information: Forum post with gif screenshots:
https://discourse.ardour.org/t/midi-bender-automation-drawing-glitches/107986
System Description
Attached Files: Peek 2022-12-04 15-31 Ardour bender automation 2.gif (559,303 bytes) 2022-12-04 13:46
https://tracker.ardour.org/file_download.php?file_id=4317&type=bug
automation_tenpo_change_glitch.gif (292,132 bytes) 2022-12-04 16:45
https://tracker.ardour.org/file_download.php?file_id=4318&type=bug
ardour automation 2022-12-08.gif (316,004 bytes) 2022-12-08 12:08
https://tracker.ardour.org/file_download.php?file_id=4319&type=bug
Notes
(0026979)
paul   
2022-12-04 14:52   
Could you please try a nightly build, because I believe this is already fixed.
(0026980)
cooltehno_bugs   
2022-12-04 16:45   
Ardour 7.1.211 Nightly - can confirm the same bug
(0026981)
noedig   
2022-12-04 17:09   
Confirmed here too, bug is still in nightly v7.1-211 2022-12-04
(0026984)
paul   
2022-12-05 21:55   
fixed in commit 1728b691
(0027000)
noedig   
2022-12-08 12:08   
Drawing nodes in the second region (after the tempo change) works now (nightly Ardour-7.1.239-dbg-w64).
However, there is still this odd behaviour (see attached gif): when moving an existing node, and then inserting a new one, the former node position jumps.
(0027188)
Arello   
2023-01-18 13:06   
I think I still have this same issue on 7.2. (Debian 10)

I followed these steps to reproduce the problem:
1) make automation pattern on some MIDI parameter (like bend),
2) move the MIDI region elsewhere (not sure if relevant),
3) make a tempo change in the project before MIDI region,
4) try to add or edit automation point to different location (you'll see effects when it doesn't align with the snap setting and zooming in/out shows it gets messed up)
(0027189)
Arello   
2023-01-18 13:31   
To clarify my previous comment: It seems that editing the the already drawn points is the bigger issue. They still get misplaced after tempo change. Drawing new points somewhat works for me.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9200 [ardour] bugs crash always 2023-01-13 17:20 2023-01-13 17:21
Reporter: ercling Platform: Redhat  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Rescan All dialog crash on wayland
Description: When I go to Plugin manager -> Rescan All -> Yes a crash happens. The console output is below:

The program 'ardour-7.2.0' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 53053 error_code 3 request_code 38 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Tags:
Steps To Reproduce: 1. Start an empty session
2. Open Window -> Plugin manager
3. Press Rescan All button inside the plugin manager window
4. Press Yes in Are you sure you want to rescan all plugins? dialog
5. Receive crash immediately
Additional Information: I reproduced the bug on a freshly installed Fedora 37 Workstation with all updates installed. I used the default GNOME session on wayland.

The crash does NOT happen in the GNOME session on X.org

GDB logs:

[Thread 0x7fffb4fff6c0 (LWP 51497) exited]
[New Thread 0x7fffb4fff6c0 (LWP 51521)]
[New Thread 0x7fff9f7fe6c0 (LWP 51522)]
[New Thread 0x7fff9effd6c0 (LWP 51523)]
[New Thread 0x7fff9dffb6c0 (LWP 51524)]
[New Thread 0x7fff9e7fc6c0 (LWP 51525)]
[Detaching after vfork from child process 51526]
[New Thread 0x7fff9d7fa6c0 (LWP 51527)]
[Thread 0x7fff9d7fa6c0 (LWP 51527) exited]
[Detaching after vfork from child process 51528]
[New Thread 0x7fff9d7fa6c0 (LWP 51529)]
[Thread 0x7fff9d7fa6c0 (LWP 51529) exited]
[Thread 0x7fff9f7fe6c0 (LWP 51522) exited]
[Thread 0x7fff9dffb6c0 (LWP 51524) exited]
[Thread 0x7fff9effd6c0 (LWP 51523) exited]
[Thread 0x7fffb4fff6c0 (LWP 51521) exited]
Set cursor set to default
[New Thread 0x7fff9d7fa6c0 (LWP 51530)]
[New Thread 0x7fffb4fff6c0 (LWP 51531)]
[New Thread 0x7ffff0dfe940 (LWP 51532)]
[New Thread 0x7ffff05fe940 (LWP 51533)]
[New Thread 0x7ffff057a940 (LWP 51534)]
[New Thread 0x7ffff01fe940 (LWP 51535)]
[New Thread 0x7ffff017a940 (LWP 51536)]
[New Thread 0x7ffff00f6940 (LWP 51537)]
[New Thread 0x7fffefdfe940 (LWP 51538)]
[New Thread 0x7fffefd7a940 (LWP 51539)]
[New Thread 0x7fffefcf6940 (LWP 51540)]
[New Thread 0x7fffef9fe940 (LWP 51541)]
[New Thread 0x7fffef5fe940 (LWP 51542)]
[New Thread 0x7fffef57a940 (LWP 51543)]
[New Thread 0x7fffef4f6940 (LWP 51544)]
[New Thread 0x7fffeedfe940 (LWP 51545)]
[New Thread 0x7fffeed7a940 (LWP 51546)]
[New Thread 0x7fffea1ff6c0 (LWP 51547)]
[New Thread 0x7fff9dffb6c0 (LWP 51548)]
[New Thread 0x7fff9effd6c0 (LWP 51549)]
[New Thread 0x7fff47fff6c0 (LWP 51550)]
locate to 0 took 246 usecs for 1 tracks = 246 per track
[New Thread 0x7fff4f7fe6c0 (LWP 51551)]
[Thread 0x7fffb4fff6c0 (LWP 51531) exited]
[Thread 0x7fff9d7fa6c0 (LWP 51530) exited]
The program 'ardour-7.2.101' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 25783 error_code 3 request_code 38 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
[Thread 0x7fff4f7fe6c0 (LWP 51551) exited]
[Thread 0x7fff47fff6c0 (LWP 51550) exited]
[Thread 0x7fff9effd6c0 (LWP 51549) exited]
[Thread 0x7fff9dffb6c0 (LWP 51548) exited]
[Thread 0x7fffea1ff6c0 (LWP 51547) exited]
[Thread 0x7fffeed7a940 (LWP 51546) exited]
[Thread 0x7fffeedfe940 (LWP 51545) exited]
[Thread 0x7fffef4f6940 (LWP 51544) exited]
[Thread 0x7fffef57a940 (LWP 51543) exited]
[Thread 0x7fffef5fe940 (LWP 51542) exited]
[Thread 0x7fffef9fe940 (LWP 51541) exited]
[Thread 0x7fffefcf6940 (LWP 51540) exited]
[Thread 0x7fffefd7a940 (LWP 51539) exited]
[Thread 0x7fffefdfe940 (LWP 51538) exited]
[Thread 0x7ffff00f6940 (LWP 51537) exited]
[Thread 0x7ffff017a940 (LWP 51536) exited]
[Thread 0x7ffff01fe940 (LWP 51535) exited]
[Thread 0x7ffff057a940 (LWP 51534) exited]
[Thread 0x7ffff05fe940 (LWP 51533) exited]
[Thread 0x7ffff0dfe940 (LWP 51532) exited]
[Thread 0x7fff9e7fc6c0 (LWP 51525) exited]
[Thread 0x7fff9ffff6c0 (LWP 51456) exited]
[Thread 0x7fffb77ff6c0 (LWP 51421) exited]
[Thread 0x7fffbdbff6c0 (LWP 51420) exited]
[Thread 0x7fffce7fc6c0 (LWP 51417) exited]
[Thread 0x7fffceffd6c0 (LWP 51416) exited]
[Thread 0x7fffcf7fe6c0 (LWP 51415) exited]
[Thread 0x7fffcffff6c0 (LWP 51414) exited]
[Thread 0x7ffff47ff6c0 (LWP 51413) exited]
[Thread 0x7ffff4ffcdc0 (LWP 51174) exited]
[Thread 0x7ffff2178940 (LWP 51518) exited]
[New process 51174]
[Inferior 1 (process 51174) exited with code 01]
(gdb) thread apply all bt
System Description
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9099 [ardour] bugs minor always 2022-11-17 13:51 2023-01-13 15:28
Reporter: HirokiFutami Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: I cannot use Vital in Ardour 7.1.
Description: Nice to meet you. I would like to report a problem.

I am enjoying Ardour 7.1, but I have a problem.
It is that Vital installed in {.deb} format is not recognized by Ardour7.1.
Ardour 6.9 recognized them properly, but 7.1 does not show them in the plugin list no matter how much I scan.
This is probably a bug and I am reporting it.

I love Ardour, I use it all the time.
Thank you very much.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files: Ardour6.9_.png (12,130 bytes) 2022-11-20 00:27
https://tracker.ardour.org/file_download.php?file_id=4293&type=bug
png

Ardour7.1_.png (13,983 bytes) 2022-11-20 00:27
https://tracker.ardour.org/file_download.php?file_id=4294&type=bug
png
Notes
(0026897)
x42   
2022-11-17 14:56   
Where is the plugin installed to?
 Is it a LV2 or VST2? If the latter have you configured Ardour to search that location?
(0026902)
HirokiFutami   
2022-11-18 18:24   
Hello.

Yes, I have set up VST2 and VST3 folders to search, and both Ardour version 6.9 and 7.1 have the same search settings, but for some reason 7.1 is the only one that does not recognize Vital.

Of course, the version of Vital is the latest version currently available.
(0026903)
x42   
2022-11-18 20:39   
There should be no difference for VST3 plugins between Ardour 6.9 and 7.1 - so this is a bit of a mystery
Is there any information in Ardour's Plugin Manager when you scan for the plugin?

PS. there should be no need to set a custom VST3 path same for LV2 (only VST2 requires this).
(0026905)
HirokiFutami   
2022-11-20 00:27   
I'm sharing images from my scans with each of Ardour 6.9 and Ardour 7.1!

(I've been using the VST3 version for a long time because I couldn't figure out how to get the LV2 version to work.)
(0026906)
x42   
2022-11-20 00:58   
Select the Vital.vst3 and at the bottom the error message should show
(0026914)
HirokiFutami   
2022-11-20 10:54   
VST3 module-path '/usr/lib/vst3/Vital.vst3/Contents/x86_64-linux/Vital.so'
[Info]: Scanning: /usr/lib/vst3/Vital.vst3
[ERROR]: Could not load VST3 plugin '/usr/lib/vst3/Vital.vst3/Contents/x86_64-linux/Vital.so': /lib/x86_64-linux-gnu/libsecret-1.so.0: undefined symbol: g_task_set_name
Cannot load VST3 module: '/usr/lib/vst3/Vital.vst3/Contents/x86_64-linux/Vital.so'
Scan Failed.


I got the above message.
(0026915)
x42   
2022-11-20 12:51   
That looks like https://forum.vital.audio/t/not-working-on-linux-libraries-are-not-statically-linked/2194/13 is back.
(0026920)
HirokiFutami   
2022-11-21 10:37   
I saw the page you linked to.
Does this mean that the problem is on the Vital side and not Ardour?
Sorry if I am wrong X(
(0026994)
paul   
2022-12-08 00:56   
Yes, it is a problem with Vital not being statically linked. Consequently, it clashes with some hosts, because they both use different versions of the same software libraries. Plugins should always be statistcally linked.
(0027183)
HirokiFutami   
2023-01-13 15:28   
Understood.
Thank you very much for your kind attention!

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9199 [ardour] features feature have not tried 2023-01-11 19:11 2023-01-11 19:11
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: Custom position for signal "out"
Description: Allow a setting custom position in the signal chain for track/bus output, just as there is already for disk I/O.

Use case: I want the dry signal to go to the master bus before I start applying delay and EQ prior to sending it to a reverb bus (with an aux send at the end of the chain).

Currently only doable with extra busses, which create clutter and move part of the control of the sound of an instrument awy from its own track.

Alternatively, allowing an "aux send" to send to master would work, but be less convenient because the track output would then have to be routed to the effect bus.
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:
9107 [ardour] bugs major always 2022-11-20 13:35 2023-01-11 14:53
Reporter: Stummer Platform: Arch  
Assigned To: paul OS: Linux  
Priority: normal OS Version: (any)  
Status: assigned Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Cannot change tempo at a x/8 time signature change mark. Changing TS also causes a crash
Description: i have an Ardour project in 6/8 time. At the start of bar 5 the TS changes to 3/8 for one bar then back to 6/8 at bar 6. The tempo should change from 75 to 92 at bar 6, beat 1 but Ardour will not take a tempo entry at beat 1 (at the same time as a TS change), only beat 2. Making a test by changing the TS to other x/8 values then caused Ardour to crash.
Tags:
Steps To Reproduce: Tempo changes and TS changes work as they should for 4/4 time changing to 2/4 time. And 8/16 time changing to 12/16 time for example. But irregular behaviour seems to happen when the project is set up with x/8 time in the first place. Trying the above actions in a new project and I got further but then it caused problems. Screenshot attached.
Additional Information:
System Description
Attached Files: Ardour TS.png (109,661 bytes) 2022-11-20 13:35
https://tracker.ardour.org/file_download.php?file_id=4297&type=bug
png
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9190 [ardour] bugs major always 2023-01-04 17:42 2023-01-11 14:53
Reporter: mpk Platform: Redhat  
Assigned To: paul OS: Linux  
Priority: normal OS Version: (any)  
Status: assigned Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Tempo change snaps incorrectly after n/8 time-signature (n is odd)
Description: It is not possible to place a tempo change on a non-whole quarternote position.
Tags:
Steps To Reproduce: 1. Enter time-signatures as per attached screenshot
2. Try to add a tempo-change at bar 3
Additional Information: May be related to https://tracker.ardour.org/view.php?id=9107
System Description
Attached Files: tempo-map-bug.png (10,392 bytes) 2023-01-04 17:42
https://tracker.ardour.org/file_download.php?file_id=4338&type=bug
png

tempo-map-bug.ardour (21,368 bytes) 2023-01-04 17:42
https://tracker.ardour.org/file_download.php?file_id=4339&type=bug
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9191 [ardour] bugs major always 2023-01-05 16:43 2023-01-11 09:28
Reporter: mpk Platform: Redhat  
Assigned To: x42 OS: Linux  
Priority: normal OS Version: (any)  
Status: assigned Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ctrl-drag region in snap mode creates glued copy
Description: Copying a region using ctrl-drag while in snap mode creates a copy which is marked as "Glued to Bars and Beats". Note that the session option "Glue new regions to bars and beats" is not selected.

The new region's length property (in the saved xml) is a mix of both audio time and beat time, e.g.: length="a273568446480@b2818560" with the distance (length) portion expressed in audio time and the position portion expressed in beat time.

Subsequently it is not possible to unglue this region due to the logic in Editor::toggle_region_lock_style and Region::set_position_time_domain.

1. Editor::toggle_region_lock_style checks region->position_time_domain then calls Region::set_position_time_domain if the requested time domain differs. In this case the new region's position is different, so:

2. Region::set_position_time_domain checks _length.val().time_domain(). But in this case the new region's length is already in AudioTime so nothing happens further.
Tags:
Steps To Reproduce: 1. In a new session, import an audio region.
2. Enable snap mode
3. Ctrl-drag the region to copy it.
4. The new region has the musical notes icon denoting "Glued to Bars and Beats".
5. Attempt to unglue the region (Region > Position > Glued to Bars and Beats) - nothing happens.
Additional Information: Note that dragging a region or source from the Editor List in snap mode has the same problem.
System Description
Attached Files: debug-toggle-glue.patch (3,536 bytes) 2023-01-05 18:24
https://tracker.ardour.org/file_download.php?file_id=4340&type=bug
Notes
(0027162)
x42   
2023-01-05 18:04   
Thanks for that. There are various issues with "a...@b..."

It should not be possible to mix time domains, and I wondered how users managed to do this :)
(0027163)
mpk   
2023-01-05 18:24   
I used this patch to fix my session which had a...@b... regions with some brute force. But I don't really understand what's meant to happen here.
(0027170)
x42   
2023-01-10 17:43   
I can also create the inverse. ctrl+drag duplicate a music-locked MIDI region using a timecode grid. This results in "b...@a..."
(0027171)
x42   
2023-01-10 18:18   
The patch you suggested will allow an audio-region to have a duration specified in beats.
This will cause various issues. Beat granularity is coarser than samples. This can lead to the audio disk-reader trying to read more samples than are present.

An Audio region's length must always be given in samples, and (at this time) a MIDI region's duration in Music-time. Only the position's time domain can change.


--
This can change in the future: When Notes inside a MIDI region can use Audio-time, a MIDI region's duration can also be specified in in Audio time.
Likewise an audio region can to have Music Time duration once Arodur supports time-stretching
(0027172)
mpk   
2023-01-10 18:31   
Just to be clear, I didn't intend to suggest that my patch solves the problem! I just used this as a way to recover a session in which some regions had become broken (displayed as "glued", but actually with "a...@b..." lengths).
(0027173)
x42   
2023-01-10 19:09   
This should be fixed in Ardour 7.2-91-gf658a4c0b2 -- please test
(0027174)
x42   
2023-01-10 19:16   
> Just to be clear, I didn't intend to suggest that my patch solves the problem!

It was very helpful to further track down the actual issue. Thanks for that! The `timecnt_t::set_time_domain` part is still somewhat relevant.
I was thinking out loud and leaving a comment in case someone else investigates the issue. -- There are still various edge-cases related to this.
(0027176)
mpk   
2023-01-11 09:28   
Thanks, looks like this is working!

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9185 [ardour] features feature always 2022-12-27 17:50 2023-01-10 22:04
Reporter: Blindekinder Platform: Ubuntu  
Assigned To: paul OS: Linux  
Priority: normal OS Version: (any)  
Status: resolved Product Version: 7.2  
Product Build: Resolution: won't fix  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Bus automations should follow regions drag when selected
Description: This should be the case when selecting all, or all after/before edit point, etc.
Tags: automation
Steps To Reproduce: -create a session
-create some tracks
-import some sound, put the regions anywhere
-create a bus, or a group master bus
-create automations on tracks AND bus
-Ctrl+A to select all: all regions and automations are selected
-drag a region: all regions move, all tracks automations move, but not the bus automations
Additional Information:
System Description
Attached Files:
Notes
(0027168)
paul   
2023-01-10 15:03   
Busses do not have regions.Multiple tracks may feed a bus, with their own independent regions. There is no specific relationship between data on a track and anything that happens in a bus. Bus automation should always be thought of as independent of actual data.
(0027175)
Blindekinder   
2023-01-10 22:04   
I agree with that. I just wonder why all selected objects wouldn't move together.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9105 [ardour] bugs major always 2022-11-18 09:26 2023-01-10 21:06
Reporter: ksawerytreningowski Platform: Debian GNU  
Assigned To: paul OS: Linux  
Priority: immediate OS Version: (any)  
Status: resolved Product Version: 7.1  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Dosn't copy one quarter note C3 in a four bar region - several times
Description: After copying a four-bar region with one quarter note C3 several times, the copied regions are shifted one unit to the left

Multi-Duplicate
    Position End
1 001:01:0000 001:04:1919
2 001:04:1919 002:04:1918
3 002:04:1918 003:04:1917
4 003:04:1917 004:04:1916

Fill Track
    Position End
1 001:01:0000 001:04:1919
2 002:01:0000 002:04:1919
3 002:04:1919 003:04:1918
4 003:04:1918 004:04:1917

Same with Copy Paste and Drag&Drop
Tags: copy
Steps To Reproduce: Create a four-bar region with one quarter note C3. Multi duplicate it. or fill track
Additional Information:
System Description
Attached Files: Ardour Copy Regions.png (150,144 bytes) 2022-11-18 09:26
https://tracker.ardour.org/file_download.php?file_id=4292&type=bug
png
Notes
(0027008)
paul   
2022-12-10 17:34   
fixed in commit 4fdd8646b4bff, will be in release 7.2, out tomorrow or the day after. Thanks for noticing this!

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9183 [ardour] bugs minor always 2022-12-24 21:21 2023-01-10 15:05
Reporter: sollapse Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: MIDI Control Out periodically looses sync with current feedback values at times
Description: Copied from a previous bug report for version 4.x (https://tracker.ardour.org/view.php?id=6657). Issue is occurring with a AKAI MPK249 and assumably most generic MIDI controllers that receive feedback. While testing the feedback for a custom mute automation mapping, I noticed the feedback will loose sync at times with the pad's that are currently toggled. It seemed like a race condition due to the MIDI Control Out running asynchronously. Is this something that the use of atomics could fix?
 
Original message:
Tested on revision 4.4-145-g3e3a5e1 with a nanoKONTROL2 in CC mode.

Issue: Pressing a button on the nanoKONTROL2 sends a CC message. The nanoKONTROL2 expects to receive the new status as a feedback CC message to update the corresponding status LED. This works on solo and mute for tracks but not for the record button. Feedback fails also when a nanoKONTROL2 button is bound to a toggled control in a plugin. However, the feedback is sent correctly if the control is toggled in Ardour instead of the midi device.
Tags:
Steps To Reproduce:
Additional Information: Original message:
Looking at midicontrollable.cc, the previous control value from/to the midi device is stored in last_value. When writing midi feedback, if the value being sent is the same as last_value, feedback is aborted. What this means that none of the buttons should get feedback since the device expects to receive the same value it sent.

Why do the solo and mute buttons work then?

It turns out that MIDIControllable::midi_sense_controller sets the new value using controllable->set_value() and then uses controllable->get_value() to update last_value. However, Route::SoloControllable::set_value() and Route::MuteControllable::set_value() both put the new value in an asynchronous queue, which is why controllable->get_value() called immediately after set_value() usually returns the unchanged value instead of the new value. Now the current value is different from last_value and Ardour happily sends it as feedback.
Attached Files:
Notes
(0027169)
paul   
2023-01-10 15:05   
note: devices requiring feedback in this era (as opposed to 2000 when ardour began) generally deserve/require their own dedicated code support module. Although the feedback functionality exists, it was created for much simpler devices and I'd be surprised if it is of much use with contemporary devices.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9198 [ardour] bugs feature always 2023-01-10 05:12 2023-01-10 05:12
Reporter: P3P3 Platform: Apple Macintosh  
Assigned To: OS: MacOS  
Priority: high OS Version: 10.12 or later  
Status: new Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Midi Notes disappear from looped recording
Description: This is a continuation of a previous post: Midi Notes disappear from looped recording , where the midi notes disappear when recording in loop mode. They appear while recording, but vanish when I hit “Stop”. The track regions are still there, but they become empty.

This happens when recording an electric drum

Tags:
Steps To Reproduce: I connect an electric drum via USB cable and when I start recording the midi notes appear, but when I stop recording the midi notes disappear
Additional Information: i use ardour 7 en mac M1
System Description
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9197 [ardour] features minor always 2023-01-09 16:12 2023-01-09 16:23
Reporter: prokoudine Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: UX improvements for Step Entry dialog
Description: The Step Entry dialog currently has a few UX issues that would be nice to have fixed.

1. The keyboard could do with the same piano keys widget that is used in the Virtual Keyboard dialog where octaves are numbered and keys in C4-C5 are visibly mapped to shortcuts on the physical keyboard. Actually pressing keys works, but there is no visual feedback on the piano keyboard and no hint which key correspond to what shortcuts. So: please mark octaves and keys.

2. Being able to use shortcuts to set note duration would be rather helpful. E.g. Logic Pro uses 1 for 1/1, 2 for 1/2, 3 for 1/4 etc. Ardour could do the same and use 0 for toggling chord input. The hints about that could be displayed in tooltips on hover.

3. It might be useful to enhance tooltips for velocity presets and mention the exact velocity value that corresponds to ppp, mp, fff etc. E.g.: "Set volume to mezzo-forte (velocity 80)".
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0027167)
x42   
2023-01-09 16:23   
(2) should already be possible. See Window > Keyboard Shortcuts

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9195 [ardour] bugs major always 2023-01-07 16:08 2023-01-07 16:08
Reporter: mpk Platform: GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Not possible to drag Time Signature with lock style Audio to non-snapped position
Description: When initiating a drag on a Time Signature change (MeterMarkerDrag), snap is always turned on with grid mode bar, making it impossible to drop the marker freely. Once dropped, the Time Signature lock style has been changed to Music.
Tags:
Steps To Reproduce: 1. Add a time signature change with lock style = Audio
2. With or without snap mode active, drag the time signature marker to a new position
3. Snap mode with a bar grid will be engaged
4. When editing the moved time signature marker, note that its lock style has been changed to Music
Additional Information: This makes editing material which switches between strict tempo time and free time virtually impossible. Snap should not be automatically engaged when dragging Audio locked markers.
System Description
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9188 [ardour] bugs major always 2023-01-03 14:49 2023-01-07 04:16
Reporter: dking952012 Platform: Microsoft  
Assigned To: x42 OS: Windows  
Priority: normal OS Version: 11  
Status: resolved Product Version: 7.2  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Plugin internal time not synced to Ardour in tempo change
Description: Plugins do not sync rhythmic and meter information to Ardour's general time in the case of tempo/meter changes. For example, a drumkit or LFO will sync with a song's beginning tempo, but will only sync with that tempo even after a new tempo has been entered. This is true even for regions not crossing the tempo change threshold (starting in the new tempo still syncs with the first). The same is true for meter changes. The plugins synced just fine with both things in 6.9. I have tested with two plugins on Windows 11 with Ardour 7.2:

Strike, by Air Music (VST2)

Vital (VST3)
Tags:
Steps To Reproduce: -New Session

-Add new tempo and change it (or time signature for meter issues)

-Create midi track

-Create midi region

-Create midi notes on both sides or one crossing tempo threshold

-Plugins do not recognize the changes
Additional Information:
System Description Windows 11
Attached Files:
Notes
(0027166)
x42   
2023-01-07 04:16   
Fixed in 7.2-87-gebf7afc482

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9192 [ardour] bugs minor always 2023-01-05 17:15 2023-01-05 18:01
Reporter: mpk Platform: GNU  
Assigned To: x42 OS: Linux  
Priority: normal OS Version: (any)  
Status: resolved Product Version: 7.2  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Trailing comma in config variable
Description: Line 165 in rc_configuration_vars.h includes a trailing comma in the variable name.

CONFIG_VARIABLE (bool, recording_resets_xrun_count, "recording-resets-xrun-count,", false)
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0027161)
x42   
2023-01-05 18:01   
Thanks! Fixed in 7.2.83

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9189 [ardour] bugs minor always 2023-01-04 14:54 2023-01-04 14:54
Reporter: Largos Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Crash when bare midi track interacts with foldback bus
Description: With the assign selected tracks you assign a midi track to foldback bus but if there isn't a plugin with an audio connection it crashes. This also happens when you remove a plugin with an audio connection when the track it's on is connected to a foldback bus.
Tags:
Steps To Reproduce: 1. Create empty midi track
2. Create foldback bus
3. Assign empty midi track to foldback bus

and

1: Create midi track with an instrument plugin
2: Create foldback bus
3: Assign midi track to foldback bus
4: Remove instrument plugin from midi track.
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:
9187 [ardour] bugs major always 2023-01-01 20:44 2023-01-03 03:33
Reporter: automaciej Platform: Apple Macintosh  
Assigned To: OS: MacOS  
Priority: normal OS Version: 10.12 or later  
Status: new Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ardour doesn't react to mouse clicks about 50% of the time
Description: Also reported on the forums: https://discourse.ardour.org/t/ardour-7-2-0-sometimes-not-reacting-to-mouse-clicks-in-osx/108111/1
Video showing the problem: https://photos.app.goo.gl/vvsJUacUFYWwHvav6

About half the time Ardour doesn't react to mouse clicks. Sometimes a wrong window is reacting to clicks, not the window where I'm clicking but the window underneath it. Sometimes when I click an element, a small border around the button appears as if the element was selected / the focus shifted to it. But when I release the mouse button, nothing happens. The element just remains selected.

Most of the time I am able to complete tasks by using keyboard shortcuts, mainly keyboard arrows, TAB, SHIFT+TAB, cycling through buttons and confirming with ENTER. But this is very time consuming. Sometimes just mashing keyboard makes Ardour "unblock" and it starts reacting to clicks for a few seconds. Then it stops reacting again.

My Ardour is virtually unusable, every smallest task takes three to five times more time to complete.

I'm running Ardour 7.2.0.
Tags:
Steps To Reproduce: Just install Ardour 7.2.0, create a new session, create a new track, try recording, etc. You'll find that buttons just don't react to clicks and you can't do anything - can't select track input, or can't switch the metronome on off, can't do anything what is behind a button.
Additional Information: My Mac's details:

Model Name: iMac
  Model Identifier: iMac18,3
  Processor Name: Quad-Core Intel Core i7
  Processor Speed: 4.2 GHz
  Number of Processors: 1
  Total Number of Cores: 4
  L2 Cache (per Core): 256 KB
  L3 Cache: 8 MB
  Hyper-Threading Technology: Enabled
  Memory: 40 GB
System Description
Attached Files:
Notes
(0027158)
automaciej   
2023-01-01 21:34   
I discovered one more factor: a USB mouse connected to my iMac. When I try to use Ardour with the original Apple mouse, the session jumps around uncontrollably, possibly because the top of the mouse works like a trackpad, and when I just brush the mouse's top, Ardour starts scrolling vertically or horizontally, or zooms in or out, or makes tracks bigger or smaller, it's really out of control.

So I switched off the Apple mouse and connected a regular PC mouse using a USB cable. Then the problems with the clicks started.

I also noticed one more symptom. When I'm in the mixer view, and I click the track input selection, and then hover over the list of inputs, normally the UI would highlight the item I'm hovering over. But not when I'm using a USB mouse. So the item highlighting and mouse clicks issues are somehow connected.
(0027159)
x42   
2023-01-02 16:44   
Thanks for that info.

I use Ardour on M2 (macbook Air) and do not have this issue. -- but I do not have any external gear and use the touchpad. I'll see if I can find some USB mouse that I can connect to the USB3 ports..
Another clue (GTK3 based) gimp has the same issue: https://www.gimp.org/news/2022/11/18/gimp-2-99-14-released/#pointer-click-bug-with-macos-ventura
(0027160)
x42   
2023-01-03 03:33   
I have started to backport some changes to work around the issue

https://gitlab.gnome.org/GNOME/gtk/-/issues/5305
https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/5280/diffs

With some luck Ardour 7.2-77 no longer has this issue. -- Please try that when tomorrow's builds are up.

It is still a bit of a mystery. I cannot reproduce the problem here on macOS 13.1, and for some users gimp 2.10 (also uses gtk2, same as ardour) works, too.
Maybe it is indeed related to an external non-apple mouse.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9176 [ardour] features minor always 2022-12-19 23:47 2022-12-31 03:28
Reporter: paul Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: i/o names assigned in rec tab should show up in i/o menus
Description: ... instead of just "in 1" or "in 1+2" etc
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0027157)
Mek   
2022-12-31 03:28   
Mono channels seem to already behave this way for me? https://github.com/Ardour/ardour/pull/770 was my attempt to make stereo bundles also show up using pretty names rather than "in 1+2" (although currently in that PR it only uses pretty names if both channels have a pretty name).

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9038 [ardour] bugs major always 2022-10-26 09:18 2022-12-29 10:41
Reporter: al f Platform: Arch  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.0  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Shift+Alt+Left / Right shortcuts not working as expected
Description: In Ardour 7.0.0: After changing Shift+Alt+Left / Right shortcuts to "Playhead to Previous / next region boundary (No track selection)", both shortcuts place playhead at session start (same as Home button).

In Ardour 7.0.105 (rev 7.0-105-g6904a86576): After changing the shortcuts, if the playhead is at a region boundary only Shift+Alt+Right works as expected.
Shift+Alt+Left does nothing until the playhead is moved away from the region boundary. Then it will move the playhead to the previous boundary and get stuck again.
Tags: Editor, region, shortcuts
Steps To Reproduce: In a session with mulitple regions across multiple tracks, change shortcuts and (try to) navigate.
Additional Information:
System Description
Attached Files: ardour.log (4,028 bytes) 2022-10-26 09:18
https://tracker.ardour.org/file_download.php?file_id=4253&type=bug
Notes
(0027156)
al f   
2022-12-29 10:41   
I can not reproduce this in Ardour 7.2

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9179 [ardour] bugs minor always 2022-12-21 00:20 2022-12-28 17:20
Reporter: sub26nico Platform: GNU/Linux  
Assigned To: OS: Librazik 4  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ardour crashes after exporting if ‘Analyse Exported Audio’ in the Export window is selected
Description: Since version 7 (.0,.1 & .2), if ‘Analyse Exported Audio’ in the Export window is selected, Ardour crashes after export is done when clicking on ‘Close’ button in the ‘Export/Report Analysis’ window.
Tags:
Steps To Reproduce: Create a new session, import audio file then export the session, select ‘Analyse Exported Audio’ in the Export window then click on 'Export'. Once export is done, click on ‘Close’ button in the ‘Export/Report Analysis’ window.
Additional Information:
System Description
Attached Files: gdb (5,681 bytes) 2022-12-21 00:20
https://tracker.ardour.org/file_download.php?file_id=4332&type=bug
gdb2 (39,880 bytes) 2022-12-23 17:28
https://tracker.ardour.org/file_download.php?file_id=4335&type=bug
Notes
(0027132)
sub26nico   
2022-12-22 09:32   
Happen also without exporting, just using 'OnlyAnalyse', both with JACK or ALSA backend.
(0027133)
sollapse   
2022-12-22 16:01   
I'm experiencing the same crash after exporting audio as well.
(0027135)
x42   
2022-12-23 16:52   
@sub26nico can you reproduce the crash with a debug version and provide a backtrace?

(there should be function names instead of "??" on each line in the backtrace)
(0027136)
sub26nico   
2022-12-23 16:56   
@x42, i've made the backtrace (1st note) with a debug version (Ardour 7.2.32-dbg).
(0027137)
x42   
2022-12-23 17:05   
(Last edited: 2022-12-23 17:06)
odd. it looks like it was an optimized version (due to "in ?? ()") - sadly that backtrace is useless as-is :(
(0027138)
x42   
2022-12-23 17:08   
I see. you've used a core file without the corresponding source.

if you do not have the source-code, run ardour directly in gdb: `Ardour7 --gdb`
(0027139)
x42   
2022-12-23 17:10   
since I cannot reproduce it here

Does this happen with every session, or only some specific ones?
Does it happen if you disable translations?
(0027140)
sub26nico   
2022-12-23 17:11   
it happen for every session, and i have already disable translations. I re-made the backtrace with "Ardour7 --gdb' command line.
(0027141)
sub26nico   
2022-12-23 17:28   
@x42, new backtrace, i hope this one is good.
(0027142)
x42   
2022-12-23 17:30   
Yes, this is readable. thanks!
(0027146)
sub26nico   
2022-12-26 11:28   
I've tested on my laptop (same OS) and it doesn't happened. the laptop have an Intel cpu, the desktop have an AMD, don't know if it can be a useful information.
(0027149)
Blindekinder   
2022-12-27 17:29   
Issue also happens on Kubuntu 22.04.
(0027150)
x42   
2022-12-27 18:00   
Do you use ui-scaling? If so, Ardour 7.2.46 (or newer) might fix this.
(0027151)
Blindekinder   
2022-12-27 19:03   
indeed, my screen is (unfortunately) a 3840X2160, I changed both Kubuntu resolution and Ardour scaling.
(0027152)
sub26nico   
2022-12-27 20:31   
Yes, I use ui-scaling.
(0027154)
sub26nico   
2022-12-28 14:58   
Bug seems to be gone with ardour 7.2.54 (dbg), no more crash after export, analysis or Loudness Analyser and Normalizer.
Thanks.
(0027155)
sub26nico   
2022-12-28 17:20   
@x42, is that commit who fix the bug ?
https://github.com/Ardour/ardour/commit/140b373cace1c8c1aed26f44098d4f9a41d35174

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9184 [ardour] bugs minor always 2022-12-26 02:16 2022-12-28 12:22
Reporter: garyd Platform: Debian GNU  
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: "Temporal" not recognised in Lua session script
Description: Attempting to use Temporal.timepos_t() in a session script fails with error: "attempt to index a nil value (field 'Temporal')"

It works fine in action scripts (Mixbus), also in session scripts in Ardour.
Tags:
Steps To Reproduce: Dummy session script is attached.
Additional Information:
System Description
Attached Files: session_script.lua (316 bytes) 2022-12-26 02:20
https://tracker.ardour.org/file_download.php?file_id=4336&type=bug
Notes
(0027145)
garyd   
2022-12-26 02:20   
Note sure if the attachment attached. Couldn't see it so attaching again.
(0027147)
x42   
2022-12-26 15:52   
Which version of Mixbus is that (Menu > Help > About)

For the new Tempo API to work correctly you need at least 8.1.700 or newer. Upcoming 8.2 should fix this as well.
(0027148)
garyd   
2022-12-27 02:36   
v8.1.378
Glad to hear it's already sorted. Thanks.
(0027153)
garyd   
2022-12-28 08:37   
Confirmed to be working in Mixbus32C v8.2.66. Thanks.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9186 [ardour] other feature N/A 2022-12-28 04:35 2022-12-28 04:35
Reporter: YackBackman Platform: Arch  
Assigned To: OS: Linux  
Priority: low OS Version: (any)  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Midi control surface keymap preset for M-audio Oxygen Pro Mini
Description: A midi keymap for M-audio Oxygen Pro Mini that binds everything so the keyboard is usable in Ardour.
Tags:
Steps To Reproduce:
Additional Information: This keymap is made to be used in DAW mode, in the user preset.
System Description
Attached Files: M-audio Oxygen Pro Mini.map (3,048 bytes) 2022-12-28 04:35
https://tracker.ardour.org/file_download.php?file_id=4337&type=bug
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
6657 [ardour] bugs minor always 2015-10-28 01:09 2022-12-24 21:21
Reporter: yfkar Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 4.X git (version in description)  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: NanoKONTROL2 does not get feedback from track record control and toggled controls in plugins
Description: Tested on revision 4.4-145-g3e3a5e1 with a nanoKONTROL2 in CC mode.

Issue: Pressing a button on the nanoKONTROL2 sends a CC message. The nanoKONTROL2 expects to receive the new status as a feedback CC message to update the corresponding status LED. This works on solo and mute for tracks but not for the record button. Feedback fails also when a nanoKONTROL2 button is bound to a toggled control in a plugin. However, the feedback is sent correctly if the control is toggled in Ardour instead of the midi device.
Tags:
Steps To Reproduce:
Additional Information: Looking at midicontrollable.cc, the previous control value from/to the midi device is stored in last_value. When writing midi feedback, if the value being sent is the same as last_value, feedback is aborted. What this means that none of the buttons should get feedback since the device expects to receive the same value it sent.

Why do the solo and mute buttons work then?

It turns out that MIDIControllable::midi_sense_controller sets the new value using controllable->set_value() and then uses controllable->get_value() to update last_value. However, Route::SoloControllable::set_value() and Route::MuteControllable::set_value() both put the new value in an asynchronous queue, which is why controllable->get_value() called immediately after set_value() usually returns the unchanged value instead of the new value. Now the current value is different from last_value and Ardour happily sends it as feedback.

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

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9181 [ardour] features minor always 2022-12-23 14:31 2022-12-23 14:40
Reporter: finetuned Platform: Debian GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: FaderPort V2: map "Solo Clear" and "Mute Clear"
Description: On the FaderPort V2 Control Surface, there are buttons [SOLO] and [MUTE], that have secondary functions when [SHIFT] is held down, namely "Solo Clear" and "Mute Clear". At the moment, these don't work as expected; [SHIFT] + [SOLO] acts the same as pressing [SOLO] without [SHIFT], and the same goes for [MUTE]. [SHIFT] + [ARM] does work as "Arm All", so I think the basic functionaly should be doable. There exist buttons in the Ardour interface for canceling all SOLO and for canceling MUTE, so the functionality is there on the Ardour side as well.

I'd like to contribute a fix for this. I'm looking at the source code for the control surfaces, but I could use some guidance as to how this should be implemented.

I noticed that the source files for the faderport8 get re-used with some IFDEFS for the FaderPort2, FaderPort8 and FaderPort16.

In fp8_controls.cc, I notice these lines:

    NEWSHIFTBUTTON (0x00, BtnArm, BtnArmAll, false);
    NEWBUTTON (0x01, BtnSoloClear, false);
    NEWBUTTON (0x02, BtnMuteClear, false);

By first thought is that there should be entries with NEWSHIFTBUTTON for BtnSoloClear and BtnMuteClear, analogous to the BtnArmAll line above it.

There exists an ENUM that lists all the buttons, and while they do contain BtnSoloClear and BtnMuteClear, they don't contain BtnSolo and BtnMute entries. I'm a little confused as to how this is implemented and how I should go about implementing the SHIFT functions for these buttons.

Any guidance would be appreciated, and if I get it tested and working, I can submit a patch for this.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files: faderport2.jpg (85,792 bytes) 2022-12-23 14:31
https://tracker.ardour.org/file_download.php?file_id=4334&type=bug
jpg
Notes
(0027134)
finetuned   
2022-12-23 14:40   
The MIDI codes for these functions, for reference:

Pressing [Solo]
   226301800 NoteOn chn 1 08 7f
   226322080 NoteOff chn 1 08 40

Pressing [Mute]
   227721026 NoteOn chn 1 10 7f
   227745710 NoteOff chn 1 10 40

Pressing [Arm]
   228726544 NoteOn chn 1 00 7f
   228738029 NoteOff chn 1 00 40


Pressing [SHIFT] + [Solo]
   229577727 NoteOn chn 1 46 7f
   229607728 NoteOn chn 1 08 7f
   229615651 NoteOff chn 1 08 40
   229638600 NoteOff chn 1 46 40

Pressing [SHIFT] + [Mute]
   230293959 NoteOn chn 1 46 7f
   230302776 NoteOn chn 1 10 7f
   230309829 NoteOff chn 1 10 40
   230317774 NoteOff chn 1 46 40

Pressing [SHIFT] + [Arm]
   231193641 NoteOn chn 1 46 7f
   231205998 NoteOn chn 1 00 7f
   231212164 NoteOff chn 1 00 40
   231223642 NoteOff chn 1 46 40


It looks like the button values are all the same, with a surrounding SHIFT (0x46) NoteOn and NoteOff events.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9180 [ardour] features minor always 2022-12-21 14:35 2022-12-21 14:35
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: 'CD Frames' grid foibles
Description: There are a few minor annoyances when grid is set to 'CD Frames':
 * the visible grid lines never indicate CD frames, regardless of the zoom level
 * when zoomed out enough, snap is to the nearest second
 * when zoomed in enough, snap to CD frames is magnetic, allowing (e.g.) CD merkers to be positioned not on a CD frame

It'd be nice if snap to CD markers was always exact, regardless of zoom level, and also lovely if you could see that that's what's happening if you zoom in enough.
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:
9178 [ardour] documentation minor always 2022-12-20 20:29 2022-12-20 21:07
Reporter: Attila S. Platform: 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: Documentation: include more sites for discovering new plugins for Ardour on Linux
Description: If it is possible please mention additional sites for discovering plugins for Linux in the documentation of Ardour.

Place in the documentation:
https://manual.ardour.org/working-with-plugins/getting-plugins/

Proposed sites for discovering additional plugins:
https://www.kvraudio.com/plugins/the-newest-plugins/linux
http://linux-sound.org/linux-vst-plugins.html
https://www.audiopluginsforfree.com/linux/
https://libreav.org/software
http://linuxsynths.com/
etc ...

(I personally found the first one the most useful and most comprehensive - relatively.)
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0027128)
x42   
2022-12-20 20:58   
I agree that we should remove that page from ardour's documentation and rather delegate things to KVR and more dedicated sites to the subject
(0027129)
mikelupe   
2022-12-20 21:07   
Additional "aggregators":
- https://linuxmusic.rocks/
- https://lv2plug.in/pages/projects.html
- https://www.ubuntupit.com/top-15-best-linux-synthesizers-for-digital-audio-production/

I still think, it would almost be better to place a new tab "Resources" on the ardour.org page, or to add a group to the "Community" tab. It's maybe easier to manage it - downloaded/generated manuals cold otherways remain out-of-date.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9177 [ardour] bugs minor always 2022-12-20 08:51 2022-12-20 08:51
Reporter: cooltehno_bugs Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Bug: The new consolidated MIDI region doesn't match the grid after the consolidation of few MIDI regions
Description: If we consolidate few MIDI layered regions with 750 samples length using the Consolidate the range command - this makes a new region that has 737 length and make additional short regions with 25 samples length
Tags:
Steps To Reproduce: 1. Draw the MIDI region 750 samples (1/128 Note) long.
2. Draw the second MIDI region with the same length as a layer above the previous.
3. Select the full length of the drawn regions by the range selection.
4. Consolidate the range - BOOM - this makes the result consolidated region 737samples (expect 750!!) long and two short regions 25 samples long!
Additional Information:
System Description
Attached Files: range_consilidate_bug.gif (657,413 bytes) 2022-12-20 08:51
https://tracker.ardour.org/file_download.php?file_id=4331&type=bug
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9164 [ardour] bugs major sometimes 2022-12-14 09:18 2022-12-20 06:28
Reporter: stefan-franz Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: high OS Version: (any)  
Status: new Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ardour plays wrong
Description: Here i have a video made. Error is still agin.
https://discourse.ardour.org/t/ardour-plays-midi-track-wrong/108016
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files: Bass Track.jpg (68,384 bytes) 2022-12-14 16:03
https://tracker.ardour.org/file_download.php?file_id=4327&type=bug
jpg

Midi Setting.jpg (52,584 bytes) 2022-12-15 20:15
https://tracker.ardour.org/file_download.php?file_id=4328&type=bug
jpg
Notes
(0027080)
stefan-franz   
2022-12-14 10:03   
Seems Ardour is completely overwhelmed with the midi file - maybe because of pitch bend data
(0027081)
stefan-franz   
2022-12-14 10:04   
Ardour plays sometimes wrong elsewhere
(0027082)
stefan-franz   
2022-12-14 10:38   
mp3 export also wrong - The bass is not playing at the beginning....and then it plays wrong
Here is the mp3 export - https://nco.stefan-franz.de/index.php/s/8JfF7DyGoa2dQBJ
(0027083)
stefan-franz   
2022-12-14 12:04   
I think the problem here are the pitch bend data - because all other projects work.
here is the original midi file - the bass makes the biggest problems.
https://nco.stefan-franz.de/index.php/s/fkptcbsw4PqGaMD
(0027090)
x42   
2022-12-14 15:37   
We do need a lot more information.

Which note(s) are played wrong? At what timestamp?
What do you mean with "plays wrong"? Is the timing off? Is a note missing?

Can you isolate the problem? ideally to a single MIDI region with just a few notes.

Which MIDI Track and Channel has the Bass that is not playing? Perhaps Channel Volume is zero?

Can you check with the plugin "ACE MIDI Monitor" (add it before the synth) if all events are sent to the synth as you expect?
(0027091)
stefan-franz   
2022-12-14 16:03   
After start Ardour it play a few minutes right. But after about 10-15min, some notes were played in the false ranges, as here in the video you see
https://discourse.ardour.org/t/ardour-plays-midi-track-wrong/108016

Not always the same - it's randomly. As the tracks gets corrupt over time.....

The bass track is the 2nd track in the midi file here https://nco.stefan-franz.de/index.php/s/fkptcbsw4PqGaMD
The beginning looks so (screenshot).

Here is a mp3 export from Ardour where you here the error: https://nco.stefan-franz.de/index.php/s/8JfF7DyGoa2dQBJ
The first few bars you hear no bass (but the notes are there) and then some bass notes are played in the wrong note range. The first 7 seconds of the file you hear no bass (but the bass is there) and in second 8-9 you hear a false note range.

Randomly the wrong note range is one of the problems - i think the pitch bend data mess up Ardour.
Now i started Ardour and all is playing good - the problem came today in the morning after i work with the project about 15minutes. I recorded only a audio track, or adjusted the level of tracks or the ACE EQ setting i edited.

I have just re-exported it: At the moment all sounds right. You hear the right sounds and can so hear the difference / error: https://nco.stefan-franz.de/index.php/s/qGf3sBsK5dyBMdP
(0027092)
stefan-franz   
2022-12-14 16:18   
Here you hear and see the error from 5minutes ago - Ardour 7.2.5 https://vimeo.com/781156134/cf54a0930d
(0027093)
x42   
2022-12-14 16:47   
Thank you, the video helps a lot!
(0027094)
stefan-franz   
2022-12-15 15:58   
info to 7.2.10 - now the track 2 or 3 plays wrong too - and sometimes track 2 (or 3) play a note about 1 second i stoped.
And now the wrong playing is nearly alwas reproduceabel. Project needs only 3 times played (only the first 10 bars needed) and then the error comes.
(0027095)
x42   
2022-12-15 19:32   
There has been no change that would explain this.

I still cannot reproduce this. Here the bass track plays just fine repeatedly.

Looking at the vimeo video, the main difference is that I use 48k/1024 (not 44.1/512) and an English system (dot as decimal separator). Neither should make a difference but I'll check.
I also use a debug (not optimized) build.
(0027096)
stefan-franz   
2022-12-15 19:53   
I found now out some things: The new "problem" track caused by Redux - i loaded the sound new to Redux and now it works.
But the Bass was/is played from the General Midi Synth.

After loading the Sound new to Redux, now my project plays right. All tracks.

Are there any Sys-Ex data in the tracks what messes up the Redux or the GM Midi Synth? (i don't know if Ardour has an "old school" list editor with all midi events....)
(0027097)
x42   
2022-12-15 19:58   
https://manual.ardour.org/midi/midi-editing/midi-list-editor/ -- but only shows notes, not all MIDI Events.
(0027098)
x42   
2022-12-15 20:00   
Ardour's GM Synth handles SysEx messages (eg. MTS - MIDI Tuning Standard) .
I do however not see any SysEx messages in the file that you have linked (You can leave your hat on.mid) - Also Arodur would show SysEx on the Editor timeline if there were any
(0027099)
stefan-franz   
2022-12-15 20:15   
New findings: https://vimeo.com/781608543/5dd1a2f75c
If i adjust the monitor volume, redux plays note very long. But, i assigned the Behringer controller only to the Monitor Level and Stop, Play and Record Button in Ardour. Not at any track nor to any function of Redux. In Redux no Macros are active. Neither PitchBend.
(0027100)
stefan-franz   
2022-12-15 20:28   
Here ist my Ardour project: https://nco.stefan-franz.de/index.php/s/jAS9a3AFyfyicfd
(0027101)
stefan-franz   
2022-12-15 21:33   
After some further tests: The controller is the cause for the problem. If i don't touch the controller (the slider which is assigned to the monitor level) then the project is playing ok.

How is in Ardour the setting, that only Ardour self should react/listen to the controller - and only what i assign?
(0027107)
stefan-franz   
2022-12-16 21:00   
Unfortunately i have to say....the conrtoller is not the cause. Without the controller Ardour plays wrong. The bass is after playing the project 3 or 4 times only 20 seconds from start (2.3.0000) wrong in that way
https://vimeo.com/781156134/cf54a0930d
(0027108)
stefan-franz   
2022-12-16 21:18   
The controller messes up Redux - maybe there are 2 problems. BTW also at AV Linux.
(0027109)
stefan-franz   
2022-12-17 08:11   
Wrong pitch of notes bouncing results: https://vimeo.com/782037266/6558f31165
Ardour 7.2.12
(0027111)
stefan-franz   
2022-12-17 13:24   
Deaktivated Bass and the Distortion 1 track which brings Redux in trouble with the controller. (to mix the project i exported the 2 tracks as Wav out of Cubase and imported to Ardour.
Now the project works normal - include Behringer Controller.
The cause are the 2 tracks. I mean the controller / Pitch Bend / Automatism is the reason.....good luck to find the reason. But it's really in 2-3 minutes reproduceable. I testet on LInux Mint 21, AV Linux, and Linux Mint DE5 (Debian version). All the same.
(0027122)
paul   
2022-12-19 19:16   
I would suggest testing with another synth. ACE Reasonable Synth would be a good choice.
(0027123)
stefan-franz   
2022-12-19 20:56   
But that synth is not usable for projects..... i uploaded my whole "problem" project here. I think it saves time for all, you test in my project all what you need. Here is a info from PMB Sound:
https://discourse.ardour.org/t/ardour-plays-midi-track-wrong/108016/6

And Robin maybe had tried out something.
(0027124)
paul   
2022-12-19 21:38   
I wasn't suggesting it was usable. It's a mechanism to differentiate issues with a given plugin versus issues in the host/DAW/Ardour.

Us testing your project is efficient, it is true, except that we have dozens or hundreds of issues to work on, while you have ... less :)
(0027125)
stefan-franz   
2022-12-20 06:28   
Oh - i searched about 2 full days and made here many infos and contributed many information. It's now the work of the devs to find it. ;-)

At the moment i have 5 projects - a mix of Audio tracks, and about 10 midi tracks with Redux, Speedrum and ACE Fluid Synth.
4 projects work fine. Only that "problem" project makes errors. I think Ardour has a big problem with Pitch Bend data, because this is the only project of me, where pitchbend data are used. Details you find above.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9109 [ardour] bugs crash sometimes 2022-11-20 22:33 2022-12-19 19:13
Reporter: beto Platform: Arch  
Assigned To: paul OS: Linux  
Priority: normal OS Version: (any)  
Status: resolved Product Version: 7.1  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Unable to edit MIDI on a ramped BPM
Description: Ardour crashes when I try to add/edit MIDI on a region with ramped BPM
Tags:
Steps To Reproduce: 1. Create new project with BPM 120
2. Add a new tempo of 140 in bar 9
3. Edit the first tempo marker so it's ramped to 140
4. Add a MIDI track
5. Try to add a new MIDI region by dragging slowly (if you do it quickly it works)
6. Ardour crashes

This is with an official 7.1 build on Arch Linux.
Additional Information:
System Description
Attached Files: Ramp bug.ardour (31,492 bytes) 2022-11-20 22:33
https://tracker.ardour.org/file_download.php?file_id=4298&type=bug
Notes
(0026922)
paul   
2022-11-21 18:19   
I am unable to reproduce this bug, either with my own session or with the one attached.

Could you make a screen recording so that I can see in more detail what you are doing when the crash happens?
(0026937)
beto   
2022-11-24 00:52   
I've uploaded the video to https://youtu.be/xIT5dIjMNY0 (HD still processing).

Note that this doesn't happen when I remove the BPM ramp, which is why I think that's the problem here.
(0026993)
paul   
2022-12-08 00:54   
I believe this should be fixed now.
(0027118)
beto   
2022-12-18 02:43   
Just tested in 7.2 and it's now working!
(0027121)
paul   
2022-12-19 19:13   
see notes

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9175 [ardour] bugs crash have not tried 2022-12-19 09:24 2022-12-19 19:12
Reporter: musew Platform: Arch  
Assigned To: OS: Linux  
Priority: high OS Version: (any)  
Status: new Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Crash when creating new MIDI track
Description: Just what it says; this is a midi-only session with a few tracks; created a new one and it crashed as soon as I hit add in the dialog box.

Here's the backtrace:

(gdb) thread apply all bt

Thread 550 (Thread 0x7fffca6e3a40 (LWP 36259) "RT-main-(nil)"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
0000001 0x00007ffff7061e8b in PBD::Semaphore::wait() () at /usr/lib/ardour7/libpbd.so.4
#2 0x00007ffff781a9cb in ARDOUR::Graph::main_thread() () at /usr/lib/ardour7/libardour.so.3
#3 0x00007fffe8cb24f2 in ARDOUR::AlsaAudioBackend::alsa_process_thread(void*) () at /usr/lib/ardour7/backends/libalsa_audiobackend.so
0000004 0x00007ffff55e58fd in start_thread (arg=<optimized out>) at pthread_create.c:442
0000005 0x00007ffff5667a60 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 549 (Thread 0x7fffa37fe6c0 (LWP 36258) "ALSA-MIDI-LIST"):
#0 0x00007ffff565a0bf in __GI___poll (fds=0x7fffb42d86a0, nfds=1, timeout=200) at ../sysdeps/unix/sysv/linux/poll.c:29
0000001 0x00007fffe8cb6281 in ARDOUR::AlsaAudioBackend::midi_device_thread() () at /usr/lib/ardour7/backends/libalsa_audiobackend.so
#2 0x00007fffe8cb635e in ARDOUR::AlsaAudioBackend::_midi_device_thread(void*) () at /usr/lib/ardour7/backends/libalsa_audiobackend.so
#3 0x00007ffff55e58fd in start_thread (arg=<optimized out>) at pthread_create.c:442
0000004 0x00007ffff5667a60 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 548 (Thread 0x7fffc8f91a40 (LWP 36257) "audioengine"):
#0 0x00007fffa182fd13 in non-virtual thunk to calf_plugins::wavetable_audio_module::make_snapshot(int) () at /usr/lib/lv2/calf.lv2/calf.so
0000001 0x00007fffa182f7a5 in calf_plugins::wavetable_audio_module::process(unsigned int, unsigned int, unsigned int, unsigned int) () at /usr/lib/lv2/calf.lv2/calf.so
#2 0x00007fffa182f19a in non-virtual thunk to calf_plugins::audio_module<calf_plugins::wavetable_metadata>::process_slice(unsigned int, unsigned int) () at /usr/lib/lv2/calf.lv2/calf.so
#3 0x00007fffa1756450 in calf_plugins::lv2_instance::run(unsigned int, bool) () at /usr/lib/lv2/calf.lv2/calf.so
0000004 0x00007ffff7c40a29 in ARDOUR::LV2Plugin::run(unsigned int, bool) () at /usr/lib/ardour7/libardour.so.3
0000005 0x00007ffff7c45b95 in ARDOUR::LV2Plugin::connect_and_run(ARDOUR::BufferSet&, long, long, double, ARDOUR::ChanMapping const&, ARDOUR::ChanMapping const&, unsigned int, long) () at /usr/lib/ardour7/libardour.so.3
#6 0x00007ffff7a70a67 in ARDOUR::PluginInsert::connect_and_run(ARDOUR::BufferSet&, long, long, double, unsigned int, long, bool) () at /usr/lib/ardour7/libardour.so.3
#7 0x00007ffff7a72e98 in ARDOUR::PluginInsert::run(ARDOUR::BufferSet&, long, long, double, unsigned int, bool) () at /usr/lib/ardour7/libardour.so.3
0000008 0x00007ffff7af16cd in ARDOUR::Route::process_output_buffers(ARDOUR::BufferSet&, long, long, unsigned int, bool, bool) () at /usr/lib/ardour7/libardo--Type <RET> for more, q to quit, c to continue without paging--c
ur.so.3
0000009 0x00007ffff7af25c4 in ARDOUR::Route::run_route(long, long, unsigned int, bool, bool) () at /usr/lib/ardour7/libardour.so.3
0000010 0x00007ffff7b0359e in ARDOUR::Route::no_roll_unlocked(unsigned int, long, long, bool) () at /usr/lib/ardour7/libardour.so.3
0000011 0x00007ffff7a04829 in ARDOUR::MidiTrack::no_roll_unlocked(unsigned int, long, long, bool) () at /usr/lib/ardour7/libardour.so.3
0000012 0x00007ffff7afbcec in ARDOUR::Route::no_roll(unsigned int, long, long, bool) () at /usr/lib/ardour7/libardour.so.3
0000013 0x00007ffff7b8b4e9 in ARDOUR::Session::no_roll(unsigned int) () at /usr/lib/ardour7/libardour.so.3
0000014 0x00007ffff7b8c66d in ARDOUR::Session::process_without_events(unsigned int) () at /usr/lib/ardour7/libardour.so.3
#15 0x00007ffff7b8d085 in ARDOUR::Session::process_with_events(unsigned int) () at /usr/lib/ardour7/libardour.so.3
0000016 0x00007ffff7b8f603 in ARDOUR::Session::process(unsigned int) () at /usr/lib/ardour7/libardour.so.3
#17 0x00007ffff772f0b9 in ARDOUR::AudioEngine::process_callback(unsigned int) () at /usr/lib/ardour7/libardour.so.3
0000018 0x00007fffe8cc263c in ARDOUR::AlsaAudioBackend::main_process_thread() () at /usr/lib/ardour7/backends/libalsa_audiobackend.so
0000019 0x00007fffe8cb66a0 in () at /usr/lib/ardour7/backends/libalsa_audiobackend.so
0000020 0x00007ffff55e58fd in start_thread (arg=<optimized out>) at pthread_create.c:442
0000021 0x00007ffff5667a60 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 547 (Thread 0x7fffc985fa40 (LWP 36256) "AlsaMidiIO"):
#0 0x00007ffff565a0bf in __GI___poll (fds=0x55556473ccb0, nfds=1, timeout=100) at ../sysdeps/unix/sysv/linux/poll.c:29
0000001 0x00007fffe8cd2bd7 in ARDOUR::AlsaRawMidiIn::main_process_thread() () at /usr/lib/ardour7/backends/libalsa_audiobackend.so
#2 0x00007fffe8cbc4be in () at /usr/lib/ardour7/backends/libalsa_audiobackend.so
#3 0x00007ffff55e58fd in start_thread (arg=<optimized out>) at pthread_create.c:442
0000004 0x00007ffff5667a60 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 546 (Thread 0x7fffc8ee5a40 (LWP 36255) "AlsaMidiIO"):
#0 __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x55556519eee8) at futex-internal.c:57
0000001 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x55556519eee8, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87
#2 0x00007ffff55e251f in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x55556519eee8, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at futex-internal.c:139
#3 0x00007ffff55e4cd0 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55556519ee98, cond=0x55556519eec0) at pthread_cond_wait.c:503
0000004 ___pthread_cond_wait (cond=0x55556519eec0, mutex=0x55556519ee98) at pthread_cond_wait.c:618
0000005 0x00007fffe8ccb054 in ARDOUR::AlsaRawMidiOut::main_process_thread() () at /usr/lib/ardour7/backends/libalsa_audiobackend.so
#6 0x00007fffe8cbc4be in () at /usr/lib/ardour7/backends/libalsa_audiobackend.so
#7 0x00007ffff55e58fd in start_thread (arg=<optimized out>) at pthread_create.c:442
0000008 0x00007ffff5667a60 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 545 (Thread 0x7fffc8ed9a40 (LWP 36254) "AlsaMidiIO"):
#0 0x00007ffff565a0bf in __GI___poll (fds=0x555563a5df30, nfds=1, timeout=100) at ../sysdeps/unix/sysv/linux/poll.c:29
0000001 0x00007fffe8cd2bd7 in ARDOUR::AlsaRawMidiIn::main_process_thread() () at /usr/lib/ardour7/backends/libalsa_audiobackend.so
#2 0x00007fffe8cbc4be in () at /usr/lib/ardour7/backends/libalsa_audiobackend.so
#3 0x00007ffff55e58fd in start_thread (arg=<optimized out>) at pthread_create.c:442
0000004 0x00007ffff5667a60 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 544 (Thread 0x7fffc8ecda40 (LWP 36253) "AlsaMidiIO"):
#0 __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x5555617dbbb8) at futex-internal.c:57
0000001 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x5555617dbbb8, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87
#2 0x00007ffff55e251f in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x5555617dbbb8, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at futex-internal.c:139
#3 0x00007ffff55e4cd0 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5555617dbb68, cond=0x5555617dbb90) at pthread_cond_wait.c:503
0000004 ___pthread_cond_wait (cond=0x5555617dbb90, mutex=0x5555617dbb68) at pthread_cond_wait.c:618
0000005 0x00007fffe8ccb054 in ARDOUR::AlsaRawMidiOut::main_process_thread() () at /usr/lib/ardour7/backends/libalsa_audiobackend.so
#6 0x00007fffe8cbc4be in () at /usr/lib/ardour7/backends/libalsa_audiobackend.so
#7 0x00007ffff55e58fd in start_thread (arg=<optimized out>) at pthread_create.c:442
0000008 0x00007ffff5667a60 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 543 (Thread 0x7fffa3fff6c0 (LWP 36252) "ExecStdOut"):
#0 0x00007ffff565a0bf in __GI___poll (fds=0x7fffa3ffcad0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
0000001 0x00007ffff706ce69 in PBD::SystemExec::output_interposer() () at /usr/lib/ardour7/libpbd.so.4
#2 0x00007ffff70704ae in () at /usr/lib/ardour7/libpbd.so.4
#3 0x00007ffff55e58fd in start_thread (arg=<optimized out>) at pthread_create.c:442
0000004 0x00007ffff5667a60 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 445 (Thread 0x7fffaaffd6c0 (LWP 34888) "LV2Worker"):
#0 futex_wait (val=8, addr=0x7fffb017e1a4) at /usr/src/debug/gcc/libgomp/config/linux/x86/futex.h:97
0000001 do_wait (val=8, addr=0x7fffb017e1a4) at /usr/src/debug/gcc/libgomp/config/linux/wait.h:67
#2 gomp_barrier_wait_end (bar=0x7fffb017e1a0, state=8) at /usr/src/debug/gcc/libgomp/config/linux/bar.c:48
#3 0x00007ffff3a563e0 in gomp_simple_barrier_wait (bar=0x7fffb017e1a0) at /usr/src/debug/gcc/libgomp/config/posix/simple-bar.h:60
0000004 gomp_thread_start (xdata=<optimized out>) at /usr/src/debug/gcc/libgomp/team.c:133
0000005 0x00007ffff55e58fd in start_thread (arg=<optimized out>) at pthread_create.c:442
#6 0x00007ffff5667a60 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 444 (Thread 0x7fffaa7fc6c0 (LWP 34889) "LV2Worker"):
#0 futex_wait (val=8, addr=0x7fffa4364794) at /usr/src/debug/gcc/libgomp/config/linux/x86/futex.h:97
0000001 do_wait (val=8, addr=0x7fffa4364794) at /usr/src/debug/gcc/libgomp/config/linux/wait.h:67
#2 gomp_barrier_wait_end (bar=0x7fffa4364790, state=8) at /usr/src/debug/gcc/libgomp/config/linux/bar.c:48
#3 0x00007ffff3a563e0 in gomp_simple_barrier_wait (bar=0x7fffa4364790) at /usr/src/debug/gcc/libgomp/config/posix/simple-bar.h:60
0000004 gomp_thread_start (xdata=<optimized out>) at /usr/src/debug/gcc/libgomp/team.c:133
0000005 0x00007ffff55e58fd in start_thread (arg=<optimized out>) at pthread_create.c:442
#6 0x00007ffff5667a60 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 443 (Thread 0x7fffabfff6c0 (LWP 34887) "LV2Worker"):
#0 futex_wait (val=8, addr=0x7fffc4009894) at /usr/src/debug/gcc/libgomp/config/linux/x86/futex.h:97
0000001 do_wait (val=8, addr=0x7fffc4009894) at /usr/src/debug/gcc/libgomp/config/linux/wait.h:67
#2 gomp_barrier_wait_end (bar=0x7fffc4009890, state=8) at /usr/src/debug/gcc/libgomp/config/linux/bar.c:48
#3 0x00007ffff3a563e0 in gomp_simple_barrier_wait (bar=0x7fffc4009890) at /usr/src/debug/gcc/libgomp/config/posix/simple-bar.h:60
0000004 gomp_thread_start (xdata=<optimized out>) at /usr/src/debug/gcc/libgomp/team.c:133
0000005 0x00007ffff55e58fd in start_thread (arg=<optimized out>) at pthread_create.c:442
#6 0x00007ffff5667a60 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 442 (Thread 0x7fffb8d666c0 (LWP 34886) "LV2Worker"):
#0 futex_wait (val=8, addr=0x7fffb4015fc4) at /usr/src/debug/gcc/libgomp/config/linux/x86/futex.h:97
0000001 do_wait (val=8, addr=0x7fffb4015fc4) at /usr/src/debug/gcc/libgomp/config/linux/wait.h:67
#2 gomp_barrier_wait_end (bar=0x7fffb4015fc0, state=8) at /usr/src/debug/gcc/libgomp/config/linux/bar.c:48
#3 0x00007ffff3a563e0 in gomp_simple_barrier_wait (bar=0x7fffb4015fc0) at /usr/src/debug/gcc/libgomp/config/posix/simple-bar.h:60
0000004 gomp_thread_start (xdata=<optimized out>) at /usr/src/debug/gcc/libgomp/team.c:133
0000005 0x00007ffff55e58fd in start_thread (arg=<optimized out>) at pthread_create.c:442
#6 0x00007ffff5667a60 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 441 (Thread 0x7fffb95676c0 (LWP 34885) "AutomationWatch"):
#0 0x00007ffff562c7c5 in __GI___clock_nanosleep (clock_id=clock_id@entry=0, flags=flags@entry=0, req=req@entry=0x7fffb9566b40, rem=rem@entry=0x7fffb9566b30) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:48
0000001 0x00007ffff56312d7 in __GI___nanosleep (req=req@entry=0x7fffb9566b40, rem=rem@entry=0x7fffb9566b30) at ../sysdeps/unix/sysv/linux/nanosleep.c:25
#2 0x00007ffff6def4e1 in g_usleep (microseconds=<optimized out>) at ../glib/glib/gtimer.c:279
#3 0x00007ffff7776d26 in ARDOUR::AutomationWatch::thread() () at /usr/lib/ardour7/libardour.so.3
0000004 0x00007ffff706011a in PBD::Thread::_run(void*) () at /usr/lib/ardour7/libpbd.so.4
0000005 0x00007ffff55e58fd in start_thread (arg=<optimized out>) at pthread_create.c:442
#6 0x00007ffff5667a60 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 440 (Thread 0x7fffb9d686c0 (LWP 34884) "autoconnect"):
#0 __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x55555d2c3a38) at futex-internal.c:57
0000001 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x55555d2c3a38, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87
#2 0x00007ffff55e251f in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x55555d2c3a38, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at futex-internal.c:139
#3 0x00007ffff55e4cd0 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55555d2c39e8, cond=0x55555d2c3a10) at pthread_cond_wait.c:503
0000004 ___pthread_cond_wait (cond=0x55555d2c3a10, mutex=0x55555d2c39e8) at pthread_cond_wait.c:618
0000005 0x00007ffff7b54b7b in ARDOUR::Session::auto_connect_thread_run() () at /usr/lib/ardour7/libardour.so.3
#6 0x00007ffff7b54fae in ARDOUR::Session::auto_connect_thread(void*) () at /usr/lib/ardour7/libardour.so.3
#7 0x00007ffff55e58fd in start_thread (arg=<optimized out>) at pthread_create.c:442
0000008 0x00007ffff5667a60 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 439 (Thread 0x7fffba5696c0 (LWP 34883) "SessionSignals"):
#0 __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x55555d2c39cc) at futex-internal.c:57
0000001 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x55555d2c39cc, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87
#2 0x00007ffff55e251f in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x55555d2c39cc, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at futex-internal.c:139
#3 0x00007ffff55e4cd0 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55555d2c3978, cond=0x55555d2c39a0) at pthread_cond_wait.c:503
0000004 ___pthread_cond_wait (cond=0x55555d2c39a0, mutex=0x55555d2c3978) at pthread_cond_wait.c:618
0000005 0x00007ffff7b8fad5 in ARDOUR::Session::emit_thread_run() () at /usr/lib/ardour7/libardour.so.3
#6 0x00007ffff7b8fb0e in ARDOUR::Session::emit_thread(void*) () at /usr/lib/ardour7/libardour.so.3
#7 0x00007ffff55e58fd in start_thread (arg=<optimized out>) at pthread_create.c:442
0000008 0x00007ffff5667a60 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 425 (Thread 0x7fffbad6a6c0 (LWP 34869) "LV2Worker"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
0000001 0x00007ffff7061e8b in PBD::Semaphore::wait() () at /usr/lib/ardour7/libpbd.so.4
#2 0x00007ffff7c277f6 in ARDOUR::Worker::run() () at /usr/lib/ardour7/libardour.so.3
#3 0x00007ffff706011a in PBD::Thread::_run(void*) () at /usr/lib/ardour7/libpbd.so.4
0000004 0x00007ffff55e58fd in start_thread (arg=<optimized out>) at pthread_create.c:442
0000005 0x00007ffff5667a60 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 411 (Thread 0x7fffab7fe6c0 (LWP 34855) "LV2Worker"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
0000001 0x00007ffff7061e8b in PBD::Semaphore::wait() () at /usr/lib/ardour7/libpbd.so.4
#2 0x00007ffff7c277f6 in ARDOUR::Worker::run() () at /usr/lib/ardour7/libardour.so.3
#3 0x00007ffff706011a in PBD::Thread::_run(void*) () at /usr/lib/ardour7/libpbd.so.4
0000004 0x00007ffff55e58fd in start_thread (arg=<optimized out>) at pthread_create.c:442
0000005 0x00007ffff5667a60 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 397 (Thread 0x7fffbbd6c6c0 (LWP 34841) "LV2Worker"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
0000001 0x00007ffff7061e8b in PBD::Semaphore::wait() () at /usr/lib/ardour7/libpbd.so.4
#2 0x00007ffff7c277f6 in ARDOUR::Worker::run() () at /usr/lib/ardour7/libardour.so.3
#3 0x00007ffff706011a in PBD::Thread::_run(void*) () at /usr/lib/ardour7/libpbd.so.4
0000004 0x00007ffff55e58fd in start_thread (arg=<optimized out>) at pthread_create.c:442
0000005 0x00007ffff5667a60 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 383 (Thread 0x7fffbb56b6c0 (LWP 34826) "LV2Worker"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
0000001 0x00007ffff7061e8b in PBD::Semaphore::wait() () at /usr/lib/ardour7/libpbd.so.4
#2 0x00007ffff7c277f6 in ARDOUR::Worker::run() () at /usr/lib/ardour7/libardour.so.3
#3 0x00007ffff706011a in PBD::Thread::_run(void*) () at /usr/lib/ardour7/libpbd.so.4
0000004 0x00007ffff55e58fd in start_thread (arg=<optimized out>) at pthread_create.c:442
0000005 0x00007ffff5667a60 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 382 (Thread 0x7fffa9ffb6c0 (LWP 34825) "midiUI"):
#0 0x00007ffff565a0bf in __GI___poll (fds=0x7fffc0041900, nfds=4, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
0000001 0x00007ffff6e1b1ff in g_main_context_poll (priority=<optimized out>, n_fds=4, fds=0x7fffc0041900, timeout=<optimized out>, context=0x555559895e90) at ../glib/glib/gmain.c:4543
#2 g_main_context_iterate.constprop.0 (context=0x555559895e90, block=1, dispatch=1, self=<optimized out>) at ../glib/glib/gmain.c:4233
#3 0x00007ffff6dc3ddf in g_main_loop_run (loop=0x55555e11b7e0) at ../glib/glib/gmain.c:4438
0000004 0x00007ffff706011a in PBD::Thread::_run(void*) () at /usr/lib/ardour7/libpbd.so.4
0000005 0x00007ffff55e58fd in start_thread (arg=<optimized out>) at pthread_create.c:442
#6 0x00007ffff5667a60 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 381 (Thread 0x7fffc8d416c0 (LWP 34824) "butler"):
#0 0x00007ffff565a0bf in __GI___poll (fds=0x7fffc8d405b0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
0000001 0x00007ffff704c80d in CrossThreadChannel::poll_for_request() () at /usr/lib/ardour7/libpbd.so.4
#2 0x00007ffff704c893 in CrossThreadChannel::receive(char&, bool) () at /usr/lib/ardour7/libpbd.so.4
#3 0x00007ffff7779212 in ARDOUR::Butler::thread_work() () at /usr/lib/ardour7/libardour.so.3
0000004 0x00007ffff706006a in () at /usr/lib/ardour7/libpbd.so.4
0000005 0x00007ffff55e58fd in start_thread (arg=<optimized out>) at pthread_create.c:442
#6 0x00007ffff5667a60 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 32 (Thread 0x7fffcbfff6c0 (LWP 34178) "gdbus"):
#0 0x00007ffff565a0bf in __GI___poll (fds=0x555556b82af0, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
0000001 0x00007ffff6e1b1ff in g_main_context_poll (priority=<optimized out>, n_fds=2, fds=0x555556b82af0, timeout=<optimized out>, context=0x555556b81630) at ../glib/glib/gmain.c:4543
#2 g_main_context_iterate.constprop.0 (context=0x555556b81630, block=1, dispatch=1, self=<optimized out>) at ../glib/glib/gmain.c:4233
#3 0x00007ffff6dc3ddf in g_main_loop_run (loop=0x555556b81720) at ../glib/glib/gmain.c:4438
0000004 0x00007ffff4b6237c in gdbus_shared_thread_func (user_data=0x555556b81600) at ../glib/gio/gdbusprivate.c:284
0000005 0x00007ffff6df1e05 in g_thread_proxy (data=0x555556b7cd20) at ../glib/glib/gthread.c:831
#6 0x00007ffff55e58fd in start_thread (arg=<optimized out>) at pthread_create.c:442
#7 0x00007ffff5667a60 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 31 (Thread 0x7fffcb7fe6c0 (LWP 34177) "gmain"):
#0 0x00007ffff565a0bf in __GI___poll (fds=0x555556b6bad0, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
0000001 0x00007ffff6e1b1ff in g_main_context_poll (priority=<optimized out>, n_fds=2, fds=0x555556b6bad0, timeout=<optimized out>, context=0x555556b6ba10) at ../glib/glib/gmain.c:4543
#2 g_main_context_iterate.constprop.0 (context=0x555556b6ba10, block=1, dispatch=1, self=<optimized out>) at ../glib/glib/gmain.c:4233
#3 0x00007ffff6dc3132 in g_main_context_iteration (context=0x555556b6ba10, may_block=may_block@entry=1) at ../glib/glib/gmain.c:4303
0000004 0x00007ffff6dc3182 in glib_worker_main (data=<optimized out>) at ../glib/glib/gmain.c:6414
0000005 0x00007ffff6df1e05 in g_thread_proxy (data=0x555556b7a6a0) at ../glib/glib/gthread.c:831
#6 0x00007ffff55e58fd in start_thread (arg=<optimized out>) at pthread_create.c:442
#7 0x00007ffff5667a60 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 9 (Thread 0x7fffe95496c0 (LWP 34141) "DeviceList"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
0000001 0x00007ffff6e14695 in g_cond_wait (cond=0x555556772de8, mutex=0x555556772df8) at ../glib/glib/gthread-posix.c:1590
#2 0x00007ffff772f6dc in ARDOUR::AudioEngine::do_devicelist_update() () at /usr/lib/ardour7/libardour.so.3
#3 0x00007ffff706011a in PBD::Thread::_run(void*) () at /usr/lib/ardour7/libpbd.so.4
0000004 0x00007ffff55e58fd in start_thread (arg=<optimized out>) at pthread_create.c:442
0000005 0x00007ffff5667a60 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 8 (Thread 0x7fffe9ffb6c0 (LWP 34140) "EngineWatchdog"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
0000001 0x00007ffff6e14695 in g_cond_wait (cond=0x555556772db8, mutex=0x555556772dc8) at ../glib/glib/gthread-posix.c:1590
#2 0x00007ffff7730a61 in ARDOUR::AudioEngine::do_reset_backend() () at /usr/lib/ardour7/libardour.so.3
#3 0x00007ffff706011a in PBD::Thread::_run(void*) () at /usr/lib/ardour7/libpbd.so.4
0000004 0x00007ffff55e58fd in start_thread (arg=<optimized out>) at pthread_create.c:442
0000005 0x00007ffff5667a60 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 6 (Thread 0x7fffea7fc6c0 (LWP 34115) "Analyzer"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
0000001 0x00007ffff6e14695 in g_cond_wait (cond=0x7ffff7f7e400 <ARDOUR::Analyser::SourcesToAnalyse>, mutex=0x7ffff7f7e3f8 <ARDOUR::Analyser::analysis_queue_lock>) at ../glib/glib/gthread-posix.c:1590
#2 0x00007ffff770e899 in ARDOUR::Analyser::work() () at /usr/lib/ardour7/libardour.so.3
#3 0x00007ffff706011a in PBD::Thread::_run(void*) () at /usr/lib/ardour7/libpbd.so.4
0000004 0x00007ffff55e58fd in start_thread (arg=<optimized out>) at pthread_create.c:442
0000005 0x00007ffff5667a60 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 5 (Thread 0x7fffeaffd6c0 (LWP 34114) "PeakFileBuilder"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
0000001 0x00007ffff6e14695 in g_cond_wait (cond=0x7ffff7f808c0 <ARDOUR::SourceFactory::PeaksToBuild>, mutex=0x7ffff7f808d8 <ARDOUR::SourceFactory::peak_building_lock>) at ../glib/glib/gthread-posix.c:1590
#2 0x00007ffff7bdf8ec in () at /usr/lib/ardour7/libardour.so.3
#3 0x00007ffff706011a in PBD::Thread::_run(void*) () at /usr/lib/ardour7/libpbd.so.4
0000004 0x00007ffff55e58fd in start_thread (arg=<optimized out>) at pthread_create.c:442
0000005 0x00007ffff5667a60 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 4 (Thread 0x7fffeb7fe6c0 (LWP 34113) "PeakFileBuilder"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
0000001 0x00007ffff6e14695 in g_cond_wait (cond=0x7ffff7f808c0 <ARDOUR::SourceFactory::PeaksToBuild>, mutex=0x7ffff7f808d8 <ARDOUR::SourceFactory::peak_building_lock>) at ../glib/glib/gthread-posix.c:1590
#2 0x00007ffff7bdf8ec in () at /usr/lib/ardour7/libardour.so.3
#3 0x00007ffff706011a in PBD::Thread::_run(void*) () at /usr/lib/ardour7/libpbd.so.4
0000004 0x00007ffff55e58fd in start_thread (arg=<optimized out>) at pthread_create.c:442
0000005 0x00007ffff5667a60 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 3 (Thread 0x7fffebfff6c0 (LWP 34112) "LXVSTEventLoop"):
#0 0x00007ffff562c7c5 in __GI___clock_nanosleep (clock_id=clock_id@entry=0, flags=flags@entry=0, req=req@entry=0x7fffebffe9b0, rem=rem@entry=0x7fffebffe9a0) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:48
0000001 0x00007ffff56312d7 in __GI___nanosleep (req=req@entry=0x7fffebffe9b0, rem=rem@entry=0x7fffebffe9a0) at ../sysdeps/unix/sysv/linux/nanosleep.c:25
#2 0x00007ffff6def4e1 in g_usleep (microseconds=<optimized out>) at ../glib/glib/gtimer.c:279
#3 0x00005555561cdb27 in ()
0000004 0x00007ffff55e58fd in start_thread (arg=<optimized out>) at pthread_create.c:442
0000005 0x00007ffff5667a60 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 2 (Thread 0x7ffff075c6c0 (LWP 34111) "Trigger Worker"):
#0 0x00007ffff565a0bf in __GI___poll (fds=0x7ffff075bad0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
0000001 0x00007ffff704c80d in CrossThreadChannel::poll_for_request() () at /usr/lib/ardour7/libpbd.so.4
#2 0x00007ffff704c893 in CrossThreadChannel::receive(char&, bool) () at /usr/lib/ardour7/libpbd.so.4
#3 0x00007ffff7c1e922 in ARDOUR::TriggerBoxThread::thread_work() () at /usr/lib/ardour7/libardour.so.3
0000004 0x00007ffff706006a in () at /usr/lib/ardour7/libpbd.so.4
0000005 0x00007ffff55e58fd in start_thread (arg=<optimized out>) at pthread_create.c:442
#6 0x00007ffff5667a60 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 1 (Thread 0x7ffff0bf5a40 (LWP 33958) "ArdourGUI"):
#0 0x0000555555a14c9e in ()
0000001 0x0000555555a1568a in ()
#2 0x00007ffff706dc5a in PBD::StandardTimer::on_elapsed() () at /usr/lib/ardour7/libpbd.so.4
#3 0x00007ffff706df3e in PBD::Timer::_timeout_handler(void*) () at /usr/lib/ardour7/libpbd.so.4
0000004 0x00007ffff6dc50a2 in g_timeout_dispatch (source=0x55555e9188c0, callback=<optimized out>, user_data=<optimized out>) at ../glib/glib/gmain.c:5007
0000005 0x00007ffff6dc487b in g_main_dispatch (context=0x55555676a260) at ../glib/glib/gmain.c:3444
#6 g_main_context_dispatch (context=0x55555676a260) at ../glib/glib/gmain.c:4162
#7 0x00007ffff6e1b299 in g_main_context_iterate.constprop.0 (context=0x55555676a260, block=1, dispatch=1, self=<optimized out>) at ../glib/glib/gmain.c:4238
0000008 0x00007ffff6dc3ddf in g_main_loop_run (loop=0x5555574dd770) at ../glib/glib/gmain.c:4438
0000009 0x00007ffff6a3d9fe in gtk_main () at /usr/lib/libgtk-x11-2.0.so.0
0000010 0x00007ffff70f0cd9 in Gtkmm2ext::UI::run(Receiver&) () at /usr/lib/ardour7/libgtkmm2ext.so.0
0000011 0x00005555559d7f96 in main ()
Tags:
Steps To Reproduce: have not tried
Additional Information:
System Description
Attached Files:
Notes
(0027120)
paul   
2022-12-19 19:12   
Looks like a crash in a CALF plugin. Run in safe mode or try removing/disabling the CALF plugin.

We do not endorse/encourage the use of these plugins.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9117 [ardour] bugs minor always 2022-11-26 13:41 2022-12-18 18:24
Reporter: tired_eyes Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 7.1  
Product Build: Resolution: reopened  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Automation: combining two regions create an excessive amount of automation points
Description: Please see the attached screenshots
Tags: 7.2, automation
Steps To Reproduce:
Additional Information:
Attached Files: before.png (143,981 bytes) 2022-11-26 13:41
https://tracker.ardour.org/file_download.php?file_id=4304&type=bug
png

after.png (144,655 bytes) 2022-11-26 16:19
https://tracker.ardour.org/file_download.php?file_id=4305&type=bug
png

automation_bug.zip (17,340 bytes) 2022-12-17 21:43
https://tracker.ardour.org/file_download.php?file_id=4330&type=bug
Notes
(0026948)
tired_eyes   
2022-11-26 16:19   
(0026976)
x42   
2022-12-04 11:13   
Fixed in Ardour 7.1-212
(0027112)
tired_eyes   
2022-12-17 16:15   
Unfortunately the but is still reproducible in 7.2
(0027113)
tired_eyes   
2022-12-17 16:15   
*bug
(0027114)
x42   
2022-12-17 19:50   
How?
Can you provide step by step instructions or offer an example session?

When combining MIDI regions, MIDI data is played back and re-recorded, so initially there are many explicit CC events like in your 2nd screenshot,, but since 7.1.212 (and now 7.2) those are removed via automation thinning afterwards. This works fine here.
(0027115)
tired_eyes   
2022-12-17 21:43   
1. Create a default empty session
2. Add a single MIDI track
3. Add a region
3. Add some simple automation (e.g. bender)
4. Add another region right next to the first one
5. Select both regions -> right click -> edit -> combine

Attaching a minimal session with all steps except for 0000005
(0027116)
tired_eyes   
2022-12-17 21:45   
I'm not sure why the number sign in the previous message was converted to a link
(0027117)
tired_eyes   
2022-12-17 22:34   
A video with the exact sequence of actions: https://ufile.io/mmo9ntax
Tried to upload it here but uploading silently fails even with a file as small as 1.2mb
(0027119)
dspasic   
2022-12-18 18:24   
Hi, i can confirm that this issue is present (taken reproduction steps from OP)
here is video demonstration: https://youtu.be/KtrmVnmiLTo

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9172 [ardour] bugs major always 2022-12-18 00:25 2022-12-18 00:25
Reporter: MatthaeusHarris Platform: Microsoft  
Assigned To: OS: Windows  
Priority: normal OS Version: 10  
Status: new Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Regions on measure boundaries act weird after global tempo change
Description: This one is long, sorry. :/

I'm trying to match the tempo between two songs for a mashup. I do this by setting the global tempo to the tempo of one song, lining up the tracks on beat boundaries, then padding each track's region to perfectly align with both 001| 01 | 0000 and a measure boundary after the song ends. Once this is done I can change the global tempo to match the target tempo and use the stretch tool to extend or compress each region so it'll still end on the same measure after the tempo change. This works great for songs that need to be slowed down, but when I try to use the same method to speed songs up, the regions get truncated at the new measure boundary. For example, if I have padded a 121 bpm track with silence to end on measure 114 | 01 | 0000, when I change the tempo to 130 bpm some tracks will get truncated on measure 114 | 01 | 0000 even though the regions should contain audio that reaches past that point. If I use the trim tool to try to extend the regions, only audio that was previously trimmed will appear. If I try to undo the tempo change, Ardour will crash. I have not been able to reproduce the crash using a GDB build, although other weird stuff starts to happen (regions will not show the proper waveform unless zoomed in, and rebuilding peaks will result in the region being represented by a checkerbox instead of a waveform).
Tags:
Steps To Reproduce: https://youtu.be/uO1he0bJMYs shows the steps I took to reproduce this issue. This video shows 7.2 release; I was unable to reproduce the crash with GDB on the nightly build, but the underlying issue of unexpected region truncation remained.
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:
9171 [ardour] bugs crash always 2022-12-17 23:28 2022-12-17 23:28
Reporter: MatthaeusHarris Platform: Microsoft  
Assigned To: OS: Windows  
Priority: normal OS Version: 10  
Status: new Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Windows crash on import file
Description: Was trying to reproduce a different bug with the nightly debug build, but encountered this in the process. Ardour segfaults when trying to import a sound file into a new project.
Tags:
Steps To Reproduce: 1. Open Ardour7.2.16-gdb
2. Create a new project
3. Import a sound file
4. Ardour has crashed.

Note: the crash does not occur if Ardour is not running with GDB.
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:
9170 [ardour] features minor N/A 2022-12-17 12:32 2022-12-17 12:32
Reporter: x42 Platform: Web infrastructure  
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: Migrate bug-tracker to gitea
Description: Ideally issue tracking would be migrated to https://git.ardour.org/ and mantisBT retired
mantis has various issues (SPAM, token timeout to comment), the entry form is overly complicated, and it does no integrate with git.

gitea does offer SSO, has a much cleaner simple GUI, supports markdown.

For the migration to happen we
* first need need a SSO provider (main ardour site)
* find a way to map user-accounts
* migrate bug reports to gitea
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:
9169 [ardour] bugs block always 2022-12-16 17:42 2022-12-17 11:34
Reporter: rigandrix Platform: x86_64  
Assigned To: OS: Linux Fedora  
Priority: normal OS Version: 37  
Status: new Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Edit -> Tempo -> Set Tempo From Edit Range = Bar hangs Ardour -> Set global
Description: Ardour becomes unresposive when using Edit -> Tempo
Tags:
Steps To Reproduce: Option 1:
1. Select a portion of a track (even an empty one)
2. Edit, Tempo, Set Tempo From Edit Range = Bar , Set global tempo
Ardour blocks and a window alerts that the program is unresponsive

Option 2 (maybe more interesting):
1. Select a portion of a track (even an empty one)
2. Edit, Tempo, Set Tempo from Edit Range = Bar , Cancel
3. Edit, Tempo, Set Tempo from Edit Range = Bar
Ardour blocks and a window alerts that the program is unresponsive
Additional Information:
Attached Files:
Notes
(0027110)
rigandrix   
2022-12-17 11:34   
Forgot the stack:

Starting program: /home/rigazilla/git/ardour/build/gtk2_ardour/ardour-7.2.0
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
bind txt domain [gtk2_ardour7] to /usr/local/share/ardour7/locale
Ardour7.2.0 (built using 7.2 and GCC version 12.2.1 20221121 (Red Hat 12.2.1-4))
[New Thread 0x7fffef9016c0 (LWP 52953)]
Ardour: [INFO]: Your system is configured to limit Ardour to 524288 open files
Ardour: [INFO]: Loading system configuration file /home/rigazilla/git/ardour/system_config
Ardour: [INFO]: Loading user configuration file /home/rigazilla/.config/ardour7/config
[New Thread 0x7fffe20f66c0 (LWP 52954)]
Ardour: [INFO]: CPU vendor: GenuineIntel
Ardour: [INFO]: AVX-capable processor
Ardour: [INFO]: AVX with FMA capable processor
Ardour: [INFO]: CPU brand: Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
Ardour: [INFO]: Using AVX and FMA optimized routines
[New Thread 0x7fffe18f56c0 (LWP 52955)]
[New Thread 0x7fffe10f46c0 (LWP 52956)]
[New Thread 0x7fffe08f36c0 (LWP 52957)]
Ardour: [INFO]: Loading plugin meta data file /home/rigazilla/git/ardour/share/plugin_metadata/plugin_tags
Ardour: [INFO]: Loading plugin statistics file /home/rigazilla/.config/ardour7/plugin_metadata/plugin_stats
- Zero stats of plugin 'https://community.ardour.org/node/7596' use-count: 1 LRU: 461
[New Thread 0x7fffca4236c0 (LWP 52958)]
[Thread 0x7fffca4236c0 (LWP 52958) exited]
[New Thread 0x7fffca4236c0 (LWP 52959)]
[New Thread 0x7fffc9a7b6c0 (LWP 52960)]
[New Thread 0x7fffc8d8a6c0 (LWP 52961)]
Ardour: [INFO]: Loading 454 MIDI patches from /home/rigazilla/git/ardour/share/patchfiles
Ardour: [INFO]: Loading default ui configuration file /home/rigazilla/git/ardour/build/gtk2_ardour/default_ui_config
Ardour: [INFO]: Loading user ui configuration file /home/rigazilla/.config/ardour7/ui_config
Gtk-Message: 18:06:10.758: Failed to load module "pk-gtk-module"
[New Thread 0x7fffbbfff6c0 (LWP 52962)]
[Thread 0x7fffbbfff6c0 (LWP 52962) exited]
[New Thread 0x7fffbbfff6c0 (LWP 52963)]
[New Thread 0x7fffbb7fe6c0 (LWP 52964)]
[Thread 0x7fffbbfff6c0 (LWP 52963) exited]
[Thread 0x7fffbb7fe6c0 (LWP 52964) exited]
[New Thread 0x7fffbb7fe6c0 (LWP 52965)]
[New Thread 0x7fffbbfff6c0 (LWP 52966)]
[New Thread 0x7fffbaffd6c0 (LWP 52967)]
[New Thread 0x7fffba7fc6c0 (LWP 52968)]
[New Thread 0x7fffb9ffb6c0 (LWP 52970)]
[New Thread 0x7fffb97fa6c0 (LWP 52971)]
[Thread 0x7fffb9ffb6c0 (LWP 52970) exited]
[Thread 0x7fffb97fa6c0 (LWP 52971) exited]
Ardour: [INFO]: Loading color file /home/rigazilla/git/ardour/gtk2_ardour/themes/dark-ardour.colors
Ardour: [INFO]: Loading ui configuration file /home/rigazilla/git/ardour/build/gtk2_ardour/clearlooks.rc
[New Thread 0x7fffb97fa6c0 (LWP 52972)]
[New Thread 0x7fffb9ffb6c0 (LWP 52973)]
[Thread 0x7fffb97fa6c0 (LWP 52972) exited]
[New Thread 0x7fffb97fa6c0 (LWP 52974)]
[New Thread 0x7fffb8ff96c0 (LWP 52975)]
[Thread 0x7fffb9ffb6c0 (LWP 52973) exited]
[Thread 0x7fffb97fa6c0 (LWP 52974) exited]
[New Thread 0x7fffb97fa6c0 (LWP 52976)]
[Thread 0x7fffb8ff96c0 (LWP 52975) exited]
[New Thread 0x7fffb8ff96c0 (LWP 52977)]
[Thread 0x7fffb97fa6c0 (LWP 52976) exited]
[Thread 0x7fffb8ff96c0 (LWP 52977) exited]
Ardour: [INFO]: Loading bindings from /home/rigazilla/git/ardour/build/gtk2_ardour/ardour.keys
Loading ui configuration file /home/rigazilla/git/ardour/build/gtk2_ardour/clearlooks.rc
[New Thread 0x7fffb8ff96c0 (LWP 52978)]
[New Thread 0x7fffb97fa6c0 (LWP 52979)]
[Thread 0x7fffb8ff96c0 (LWP 52978) exited]
[New Thread 0x7fffb8ff96c0 (LWP 52980)]
[New Thread 0x7fffb9ffb6c0 (LWP 52981)]
[Thread 0x7fffb97fa6c0 (LWP 52979) exited]
[Thread 0x7fffb8ff96c0 (LWP 52980) exited]
[Thread 0x7fffb9ffb6c0 (LWP 52981) exited]
[New Thread 0x7fffb87f86c0 (LWP 52982)]
[New Thread 0x7fffb85fd6c0 (LWP 52983)]
[Thread 0x7fffb85fd6c0 (LWP 52983) exited]
[Thread 0x7fffb87f86c0 (LWP 52982) exited]
[New Thread 0x7fffb87f86c0 (LWP 52984)]
[New Thread 0x7fffb85fd6c0 (LWP 52985)]
[Thread 0x7fffb85fd6c0 (LWP 52985) exited]
[Thread 0x7fffb87f86c0 (LWP 52984) exited]
[New Thread 0x7fffb9ffb6c0 (LWP 52986)]
[New Thread 0x7fffb8ff96c0 (LWP 52987)]
[Thread 0x7fffb9ffb6c0 (LWP 52986) exited]
[Thread 0x7fffb8ff96c0 (LWP 52987) exited]
[New Thread 0x7fffb8ff96c0 (LWP 52988)]
[New Thread 0x7fffb9ffb6c0 (LWP 52989)]
[Thread 0x7fffb8ff96c0 (LWP 52988) exited]
[Thread 0x7fffb9ffb6c0 (LWP 52989) exited]
[New Thread 0x7fffb9ffb6c0 (LWP 52990)]
[New Thread 0x7fffb8ff96c0 (LWP 52991)]
[New Thread 0x7fffb97fa6c0 (LWP 52992)]
Found nothing along /home/rigazilla/.config/ardour7/templates:/home/rigazilla/git/ardour/share/templates:/home/rigazilla/git/ardour/build/templates:/home/rigazilla/git/ardour/gtk2_ardour/templates:/home/rigazilla/git/ardour/build/gtk2_ardour/templates
[New Thread 0x7fff9b3ff6c0 (LWP 52994)]
[New Thread 0x7fff9abfe6c0 (LWP 52995)]
[Thread 0x7fff9b3ff6c0 (LWP 52994) exited]
[Thread 0x7fff9abfe6c0 (LWP 52995) exited]
[Thread 0x7fffb9ffb6c0 (LWP 52990) exited]
[Thread 0x7fffb97fa6c0 (LWP 52992) exited]
[Thread 0x7fffba7fc6c0 (LWP 52968) exited]
[Thread 0x7fffb8ff96c0 (LWP 52991) exited]
[Thread 0x7fffc8d8a6c0 (LWP 52961) exited]
[New Thread 0x7fffb8ff96c0 (LWP 52996)]
[New Thread 0x7fffb97fa6c0 (LWP 52997)]
[New Thread 0x7fffb9ffb6c0 (LWP 52998)]
[Thread 0x7fffb97fa6c0 (LWP 52997) exited]
[Thread 0x7fffb9ffb6c0 (LWP 52998) exited]
[Thread 0x7fffb8ff96c0 (LWP 52996) exited]
[New Thread 0x7fffb8ff96c0 (LWP 52999)]
[New Thread 0x7fffb87f86c0 (LWP 53000)]
[New Thread 0x7fffb82ea6c0 (LWP 53001)]
[New Thread 0x7fff9bf2c6c0 (LWP 53002)]
[New Thread 0x7fffb9ffb6c0 (LWP 53003)]
[New Thread 0x7fffb97fa6c0 (LWP 53004)]
[New Thread 0x7fffba7fc6c0 (LWP 53005)]
[New Thread 0x7fff9ab226c0 (LWP 53006)]
[New Thread 0x7fff9a3216c0 (LWP 53007)]
[Thread 0x7fff9ab226c0 (LWP 53006) exited]
[Thread 0x7fff9a3216c0 (LWP 53007) exited]
Set cursor set to default
[New Thread 0x7fff9a3216c0 (LWP 53008)]
[New Thread 0x7fff9ab226c0 (LWP 53009)]
[Thread 0x7fff9a3216c0 (LWP 53008) exited]
[Thread 0x7fff9ab226c0 (LWP 53009) exited]
[New Thread 0x7fff9ab226c0 (LWP 53010)]
[New Thread 0x7fff9a3216c0 (LWP 53011)]
[Thread 0x7fff9ab226c0 (LWP 53010) exited]
[Thread 0x7fff9a3216c0 (LWP 53011) exited]
[New Thread 0x7fff9a3216c0 (LWP 53012)]
[New Thread 0x7fff9ab226c0 (LWP 53013)]
[Thread 0x7fff9a3216c0 (LWP 53012) exited]
[Thread 0x7fff9ab226c0 (LWP 53013) exited]
[New Thread 0x7fff9ab226c0 (LWP 53014)]
[New Thread 0x7fff9a3216c0 (LWP 53015)]
[Thread 0x7fff9ab226c0 (LWP 53014) exited]
[Thread 0x7fff9a3216c0 (LWP 53015) exited]
[New Thread 0x7fff9a3216c0 (LWP 53016)]
[New Thread 0x7fff9ab226c0 (LWP 53017)]
[Thread 0x7fff9a3216c0 (LWP 53016) exited]
[Thread 0x7fff9ab226c0 (LWP 53017) exited]
[New Thread 0x7fff9ab226c0 (LWP 53018)]
[New Thread 0x7fff9a3216c0 (LWP 53019)]
[Thread 0x7fff9ab226c0 (LWP 53018) exited]
[New Thread 0x7fff9ab226c0 (LWP 53020)]
[New Thread 0x7fff998726c0 (LWP 53021)]
[Thread 0x7fff9a3216c0 (LWP 53019) exited]
[Thread 0x7fff9ab226c0 (LWP 53020) exited]
[Thread 0x7fff998726c0 (LWP 53021) exited]
[New Thread 0x7fff998726c0 (LWP 53022)]
[New Thread 0x7fff9ab226c0 (LWP 53023)]
[Thread 0x7fff998726c0 (LWP 53022) exited]
[Thread 0x7fff9ab226c0 (LWP 53023) exited]
[New Thread 0x7fff9ab226c0 (LWP 53024)]
[New Thread 0x7fff998726c0 (LWP 53025)]
[Thread 0x7fff9ab226c0 (LWP 53024) exited]
[New Thread 0x7fff9ab226c0 (LWP 53026)]
[New Thread 0x7fff9a3216c0 (LWP 53027)]
[Thread 0x7fff998726c0 (LWP 53025) exited]
[Thread 0x7fff9ab226c0 (LWP 53026) exited]
[Thread 0x7fff9a3216c0 (LWP 53027) exited]
[New Thread 0x7fff9a3216c0 (LWP 53028)]
[New Thread 0x7fff9ab226c0 (LWP 53029)]
[Thread 0x7fff9a3216c0 (LWP 53028) exited]
[Thread 0x7fff9ab226c0 (LWP 53029) exited]
[Thread 0x7fffba7fc6c0 (LWP 53005) exited]
[Thread 0x7fffb97fa6c0 (LWP 53004) exited]
[New Thread 0x7fff995716c0 (LWP 53030)]
[New Thread 0x7fff994f06c0 (LWP 53031)]
[New Thread 0x7fff9946f6c0 (LWP 53032)]
[New Thread 0x7fff993ee6c0 (LWP 53033)]
[New Thread 0x7fff9936d6c0 (LWP 53034)]
[New Thread 0x7fff992ec6c0 (LWP 53035)]
[New Thread 0x7fff9926b6c0 (LWP 53036)]
[New Thread 0x7fffba7fc6c0 (LWP 53037)]
[New Thread 0x7fffb97fa6c0 (LWP 53038)]
[Thread 0x7fffba7fc6c0 (LWP 53037) exited]
[New Thread 0x7fffba7fc6c0 (LWP 53039)]
[New Thread 0x7fff9ab226c0 (LWP 53040)]
[Thread 0x7fffba7fc6c0 (LWP 53039) exited]
[Thread 0x7fffb97fa6c0 (LWP 53038) exited]
[Thread 0x7fff9ab226c0 (LWP 53040) exited]
[New Thread 0x7fff9ab226c0 (LWP 53042)]
[New Thread 0x7fffb97fa6c0 (LWP 53043)]
[Thread 0x7fff9ab226c0 (LWP 53042) exited]
[Thread 0x7fffb97fa6c0 (LWP 53043) exited]
[New Thread 0x7fff75e0f6c0 (LWP 53048)]
[New Thread 0x7fffb97fa6c0 (LWP 53049)]
[New Thread 0x7fff9ab226c0 (LWP 53051)]
[New Thread 0x7fffba7fc6c0 (LWP 53052)]
[Thread 0x7fffb8ff96c0 (LWP 52999) exited]
[Thread 0x7fffbaffd6c0 (LWP 52967) exited]
locate to 0 took 217 usecs for 1 tracks = 217 per track
[New Thread 0x7fffb8ff96c0 (LWP 53053)]
[New Thread 0x7fffbaffd6c0 (LWP 53054)]
[New Thread 0x7fff9a3216c0 (LWP 53055)]
[Thread 0x7fffbaffd6c0 (LWP 53054) exited]
[Thread 0x7fff9a3216c0 (LWP 53055) exited]
[New Thread 0x7fff9a3216c0 (LWP 53056)]
[New Thread 0x7fffbaffd6c0 (LWP 53057)]
[Thread 0x7fff9a3216c0 (LWP 53056) exited]
[Thread 0x7fffbaffd6c0 (LWP 53057) exited]
[New Thread 0x7fffbaffd6c0 (LWP 53058)]
[New Thread 0x7fff9a3216c0 (LWP 53059)]
[Thread 0x7fffbaffd6c0 (LWP 53058) exited]
[Thread 0x7fff9a3216c0 (LWP 53059) exited]
[New Thread 0x7fff9a3216c0 (LWP 53060)]
[New Thread 0x7fffbaffd6c0 (LWP 53061)]
[Thread 0x7fff9a3216c0 (LWP 53060) exited]
[Thread 0x7fffbaffd6c0 (LWP 53061) exited]
[New Thread 0x7fffbaffd6c0 (LWP 53062)]
[New Thread 0x7fff9a3216c0 (LWP 53063)]
[Thread 0x7fffbaffd6c0 (LWP 53062) exited]
[New Thread 0x7fffbaffd6c0 (LWP 53064)]
[New Thread 0x7fff5be536c0 (LWP 53065)]
[Thread 0x7fff9a3216c0 (LWP 53063) exited]
[Thread 0x7fffbaffd6c0 (LWP 53064) exited]
[Thread 0x7fff5be536c0 (LWP 53065) exited]
[New Thread 0x7fff5be536c0 (LWP 53066)]
[New Thread 0x7fffbaffd6c0 (LWP 53067)]
[Thread 0x7fff5be536c0 (LWP 53066) exited]
[Thread 0x7fffbaffd6c0 (LWP 53067) exited]
[New Thread 0x7fffbaffd6c0 (LWP 53068)]
[New Thread 0x7fff5be536c0 (LWP 53069)]
[Thread 0x7fffbaffd6c0 (LWP 53068) exited]
[New Thread 0x7fffbaffd6c0 (LWP 53070)]
[New Thread 0x7fff9a3216c0 (LWP 53071)]
[Thread 0x7fff5be536c0 (LWP 53069) exited]
[Thread 0x7fffbaffd6c0 (LWP 53070) exited]
[Thread 0x7fff9a3216c0 (LWP 53071) exited]
[New Thread 0x7fff9a3216c0 (LWP 53072)]
[New Thread 0x7fffbaffd6c0 (LWP 53073)]
[Thread 0x7fff9a3216c0 (LWP 53072) exited]
[Thread 0x7fffbaffd6c0 (LWP 53073) exited]
[New Thread 0x7fffbaffd6c0 (LWP 53075)]
[New Thread 0x7fff9a3216c0 (LWP 53076)]
[Thread 0x7fffbaffd6c0 (LWP 53075) exited]
[New Thread 0x7fffbaffd6c0 (LWP 53077)]
[New Thread 0x7fff5be536c0 (LWP 53078)]
[Thread 0x7fff9a3216c0 (LWP 53076) exited]
[Thread 0x7fffbaffd6c0 (LWP 53077) exited]
[Thread 0x7fff5be536c0 (LWP 53078) exited]
[Thread 0x7fffb9ffb6c0 (LWP 53003) exited]




^C
Thread 1 "ArdourGUI" received signal SIGINT, Interrupt.
syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
Downloading 0.00 MB source file /usr/src/debug/glibc-2.36-8.fc37.x86_64/misc/../sysdeps/unix/sysv/linux/x86_64/syscall.S
38 cmpq $-4095, %rax /* Check %rax for error. */
(gdb) thread apply all bt

Thread 94 (Thread 0x7fffb8ff96c0 (LWP 53053) "AutomationWatch"):
#0 0x00007ffff2c15095 in __GI___clock_nanosleep (clock_id=clock_id@entry=0, flags=flags@entry=0, req=req@entry=0x7fffb8ff8a80, rem=rem@entry=0x7fffb8ff8a70) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:48
0000001 0x00007ffff2c19847 in __GI___nanosleep (req=req@entry=0x7fffb8ff8a80, rem=rem@entry=0x7fffb8ff8a70) at ../sysdeps/unix/sysv/linux/nanosleep.c:25
#2 0x00007ffff4e7b83f in g_usleep (microseconds=<optimized out>) at ../glib/gtimer.c:279
#3 0x00007ffff6dcdd8d in ARDOUR::AutomationWatch::thread() (this=0x46e0c00) at ../libs/ardour/automation_watch.cc:207
0000004 0x00007ffff6dd2ebf in boost::_mfi::mf0<void, ARDOUR::AutomationWatch>::operator()(ARDOUR::AutomationWatch*) const (this=0x47048a0, p=0x46e0c00) at /usr/include/boost/bind/mem_fn_template.hpp:49
0000005 0x00007ffff6dd2a53 in boost::_bi::list1<boost::_bi::value<ARDOUR::AutomationWatch*> >::operator()<boost::_mfi::mf0<void, ARDOUR::AutomationWatch>, boost::_bi::list0>(boost::_bi::type<void>, boost::_mfi::mf0<void, ARDOUR::AutomationWatch>&, boost::_bi::list0&, int) (this=0x47048b0, f=..., a=...) at /usr/include/boost/bind/bind.hpp:238
#6 0x00007ffff6dd23c7 in boost::_bi::bind_t<void, boost::_mfi::mf0<void, ARDOUR::AutomationWatch>, boost::_bi::list1<boost::_bi::value<ARDOUR::AutomationWatch*> > >::operator()() (this=0x47048a0) at /usr/include/boost/bind/bind.hpp:1273
#7 0x00007ffff6dd1ec2 in boost::detail::function::void_function_obj_invoker0<boost::_bi::bind_t<void, boost::_mfi::mf0<void, ARDOUR::AutomationWatch>, boost::_bi::list1<boost::_bi::value<ARDOUR::AutomationWatch*> > >, void>::invoke(boost::detail::function::function_buffer&) (function_obj_ptr=...) at /usr/include/boost/function/function_template.hpp:158
0000008 0x000000000076d15e in boost::function0<void>::operator()() const (this=0x4704898) at /usr/include/boost/function/function_template.hpp:763
0000009 0x00007ffff51d1787 in PBD::Thread::_run(void*) (arg=0x4704870) at ../libs/pbd/pthread_utils.cc:488
0000010 0x00007ffff2bce14d in start_thread (arg=<optimized out>) at pthread_create.c:442
0000011 0x00007ffff2c4fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
--Type <RET> for more, q to quit, c to continue without paging--c

Thread 93 (Thread 0x7fffba7fc6c0 (LWP 53052) "autoconnect"):
#0 __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x3e6b1f0) at futex-internal.c:57
0000001 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x3e6b1f0, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87
#2 0x00007ffff2bcad9f in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x3e6b1f0, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at futex-internal.c:139
#3 0x00007ffff2bcd530 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x3e6b1a0, cond=0x3e6b1c8) at pthread_cond_wait.c:503
0000004 ___pthread_cond_wait (cond=0x3e6b1c8, mutex=0x3e6b1a0) at pthread_cond_wait.c:618
0000005 0x00007ffff74c6e12 in ARDOUR::Session::auto_connect_thread_run() (this=0x3e69130) at ../libs/ardour/session.cc:7444
#6 0x00007ffff74c691f in ARDOUR::Session::auto_connect_thread(void*) (arg=0x3e69130) at ../libs/ardour/session.cc:7375
#7 0x00007ffff2bce14d in start_thread (arg=<optimized out>) at pthread_create.c:442
0000008 0x00007ffff2c4fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 92 (Thread 0x7fff9ab226c0 (LWP 53051) "SessionSignals"):
#0 __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x3e6b180) at futex-internal.c:57
0000001 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x3e6b180, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87
#2 0x00007ffff2bcad9f in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x3e6b180, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at futex-internal.c:139
#3 0x00007ffff2bcd530 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x3e6b130, cond=0x3e6b158) at pthread_cond_wait.c:503
0000004 ___pthread_cond_wait (cond=0x3e6b158, mutex=0x3e6b130) at pthread_cond_wait.c:618
0000005 0x00007ffff754bbd6 in ARDOUR::Session::emit_thread_run() (this=0x3e69130) at ../libs/ardour/session_process.cc:1232
#6 0x00007ffff754bb7f in ARDOUR::Session::emit_thread(void*) (arg=0x3e69130) at ../libs/ardour/session_process.cc:1221
#7 0x00007ffff2bce14d in start_thread (arg=<optimized out>) at pthread_create.c:442
0000008 0x00007ffff2c4fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 91 (Thread 0x7fffb97fa6c0 (LWP 53049) "midiUI"):
#0 0x00007ffff2c4205f in __GI___poll (fds=0x7fff68021ad0, nfds=4, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
0000001 0x00007ffff4ea950d in g_main_context_poll (priority=<optimized out>, n_fds=4, fds=0x7fff68021ad0, timeout=<optimized out>, context=0x45c9b00) at ../glib/gmain.c:4543
#2 g_main_context_iterate.constprop.0 (context=0x45c9b00, block=1, dispatch=1, self=<optimized out>) at ../glib/gmain.c:4233
#3 0x00007ffff4e5328f in g_main_loop_run (loop=0x45c9c20) at ../glib/gmain.c:4438
0000004 0x00007ffff51922bf in BaseUI::main_thread() (this=0x45c95d0) at ../libs/pbd/base_ui.cc:102
0000005 0x00007ffff5196c8b in boost::_mfi::mf0<void, BaseUI>::operator()(BaseUI*) const (this=0x45c9d50, p=0x45c95d0) at /usr/include/boost/bind/mem_fn_template.hpp:49
#6 0x00007ffff5196955 in boost::_bi::list1<boost::_bi::value<BaseUI*> >::operator()<boost::_mfi::mf0<void, BaseUI>, boost::_bi::list0>(boost::_bi::type<void>, boost::_mfi::mf0<void, BaseUI>&, boost::_bi::list0&, int) (this=0x45c9d60, f=..., a=...) at /usr/include/boost/bind/bind.hpp:238
#7 0x00007ffff51965a3 in boost::_bi::bind_t<void, boost::_mfi::mf0<void, BaseUI>, boost::_bi::list1<boost::_bi::value<BaseUI*> > >::operator()() (this=0x45c9d50) at /usr/include/boost/bind/bind.hpp:1273
0000008 0x00007ffff5196075 in boost::detail::function::void_function_obj_invoker0<boost::_bi::bind_t<void, boost::_mfi::mf0<void, BaseUI>, boost::_bi::list1<boost::_bi::value<BaseUI*> > >, void>::invoke(boost::detail::function::function_buffer&) (function_obj_ptr=...) at /usr/include/boost/function/function_template.hpp:158
0000009 0x000000000076d15e in boost::function0<void>::operator()() const (this=0x45c9d48) at /usr/include/boost/function/function_template.hpp:763
0000010 0x00007ffff51d1787 in PBD::Thread::_run(void*) (arg=0x45c9d20) at ../libs/pbd/pthread_utils.cc:488
0000011 0x00007ffff2bce14d in start_thread (arg=<optimized out>) at pthread_create.c:442
0000012 0x00007ffff2c4fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 90 (Thread 0x7fff75e0f6c0 (LWP 53048) "butler"):
#0 0x00007ffff2c4205f in __GI___poll (fds=0x7fff75e0e204, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
0000001 0x00007ffff51a9ac6 in CrossThreadChannel::poll_for_request() (this=0x3b546d0) at ../libs/pbd/crossthread.posix.cc:108
#2 0x00007ffff51a9b35 in CrossThreadChannel::receive(char&, bool) (this=0x3b546d0, msg=@0x7fff75e0e2bf: 0 '\000', wait=true) at ../libs/pbd/crossthread.posix.cc:133
#3 0x00007ffff6de307a in ARDOUR::Butler::thread_work() (this=0x3b54630) at ../libs/ardour/butler.cc:188
0000004 0x00007ffff6de2df3 in ARDOUR::Butler::_thread_work(void*) (arg=0x3b54630) at ../libs/ardour/butler.cc:170
0000005 0x00007ffff51d0c44 in fake_thread_start(void*) (arg=0x45b3c90) at ../libs/pbd/pthread_utils.cc:101
#6 0x00007ffff2bce14d in start_thread (arg=<optimized out>) at pthread_create.c:442
#7 0x00007ffff2c4fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 83 (Thread 0x7fff9926b6c0 (LWP 53036) "RT-6-0x7fff9926"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
0000001 0x00007ffff51d79be in PBD::Semaphore::wait() (this=0x3b5c764) at ../libs/pbd/semutils.cc:120
#2 0x00007ffff6f1ed6d in ARDOUR::Graph::run_one() (this=0x3b5c630) at ../libs/ardour/graph.cc:322
#3 0x00007ffff6f1f279 in ARDOUR::Graph::helper_thread() (this=0x3b5c630) at ../libs/ardour/graph.cc:374
0000004 0x00007ffff6f2a07f in boost::_mfi::mf0<void, ARDOUR::Graph>::operator()(ARDOUR::Graph*) const (this=0x7fff9926abd8, p=0x3b5c630) at /usr/include/boost/bind/mem_fn_template.hpp:49
0000005 0x00007ffff6f2971d in boost::_bi::list1<boost::_bi::value<ARDOUR::Graph*> >::operator()<boost::_mfi::mf0<void, ARDOUR::Graph>, boost::_bi::list0>(boost::_bi::type<void>, boost::_mfi::mf0<void, ARDOUR::Graph>&, boost::_bi::list0&, int) (this=0x7fff9926abe8, f=..., a=...) at /usr/include/boost/bind/bind.hpp:238
#6 0x00007ffff6f2872f in boost::_bi::bind_t<void, boost::_mfi::mf0<void, ARDOUR::Graph>, boost::_bi::list1<boost::_bi::value<ARDOUR::Graph*> > >::operator()() (this=0x7fff9926abd8) at /usr/include/boost/bind/bind.hpp:1273
#7 0x00007ffff6f2713f in boost::detail::function::void_function_obj_invoker0<boost::_bi::bind_t<void, boost::_mfi::mf0<void, ARDOUR::Graph>, boost::_bi::list1<boost::_bi::value<ARDOUR::Graph*> > >, void>::invoke(boost::detail::function::function_buffer&) (function_obj_ptr=...) at /usr/include/boost/function/function_template.hpp:158
0000008 0x000000000076d15e in boost::function0<void>::operator()() const (this=0x7fff9926abd0) at /usr/include/boost/function/function_template.hpp:763
0000009 0x00007fffc923809c in ARDOUR::JACKAudioBackend::_start_process_thread(void*) (arg=0x3e615f0) at ../libs/backends/jack/jack_audiobackend.cc:955
0000010 0x00007ffff2bce14d in start_thread (arg=<optimized out>) at pthread_create.c:442
0000011 0x00007ffff2c4fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 82 (Thread 0x7fff992ec6c0 (LWP 53035) "RT-5-0x7fff992e"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
0000001 0x00007ffff51d79be in PBD::Semaphore::wait() (this=0x3b5c764) at ../libs/pbd/semutils.cc:120
#2 0x00007ffff6f1ed6d in ARDOUR::Graph::run_one() (this=0x3b5c630) at ../libs/ardour/graph.cc:322
#3 0x00007ffff6f1f279 in ARDOUR::Graph::helper_thread() (this=0x3b5c630) at ../libs/ardour/graph.cc:374
0000004 0x00007ffff6f2a07f in boost::_mfi::mf0<void, ARDOUR::Graph>::operator()(ARDOUR::Graph*) const (this=0x7fff992ebbd8, p=0x3b5c630) at /usr/include/boost/bind/mem_fn_template.hpp:49
0000005 0x00007ffff6f2971d in boost::_bi::list1<boost::_bi::value<ARDOUR::Graph*> >::operator()<boost::_mfi::mf0<void, ARDOUR::Graph>, boost::_bi::list0>(boost::_bi::type<void>, boost::_mfi::mf0<void, ARDOUR::Graph>&, boost::_bi::list0&, int) (this=0x7fff992ebbe8, f=..., a=...) at /usr/include/boost/bind/bind.hpp:238
#6 0x00007ffff6f2872f in boost::_bi::bind_t<void, boost::_mfi::mf0<void, ARDOUR::Graph>, boost::_bi::list1<boost::_bi::value<ARDOUR::Graph*> > >::operator()() (this=0x7fff992ebbd8) at /usr/include/boost/bind/bind.hpp:1273
#7 0x00007ffff6f2713f in boost::detail::function::void_function_obj_invoker0<boost::_bi::bind_t<void, boost::_mfi::mf0<void, ARDOUR::Graph>, boost::_bi::list1<boost::_bi::value<ARDOUR::Graph*> > >, void>::invoke(boost::detail::function::function_buffer&) (function_obj_ptr=...) at /usr/include/boost/function/function_template.hpp:158
0000008 0x000000000076d15e in boost::function0<void>::operator()() const (this=0x7fff992ebbd0) at /usr/include/boost/function/function_template.hpp:763
0000009 0x00007fffc923809c in ARDOUR::JACKAudioBackend::_start_process_thread(void*) (arg=0x2298590) at ../libs/backends/jack/jack_audiobackend.cc:955
0000010 0x00007ffff2bce14d in start_thread (arg=<optimized out>) at pthread_create.c:442
0000011 0x00007ffff2c4fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 81 (Thread 0x7fff9936d6c0 (LWP 53034) "RT-4-0x7fff9936"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
0000001 0x00007ffff51d79be in PBD::Semaphore::wait() (this=0x3b5c764) at ../libs/pbd/semutils.cc:120
#2 0x00007ffff6f1ed6d in ARDOUR::Graph::run_one() (this=0x3b5c630) at ../libs/ardour/graph.cc:322
#3 0x00007ffff6f1f279 in ARDOUR::Graph::helper_thread() (this=0x3b5c630) at ../libs/ardour/graph.cc:374
0000004 0x00007ffff6f2a07f in boost::_mfi::mf0<void, ARDOUR::Graph>::operator()(ARDOUR::Graph*) const (this=0x7fff9936cbd8, p=0x3b5c630) at /usr/include/boost/bind/mem_fn_template.hpp:49
0000005 0x00007ffff6f2971d in boost::_bi::list1<boost::_bi::value<ARDOUR::Graph*> >::operator()<boost::_mfi::mf0<void, ARDOUR::Graph>, boost::_bi::list0>(boost::_bi::type<void>, boost::_mfi::mf0<void, ARDOUR::Graph>&, boost::_bi::list0&, int) (this=0x7fff9936cbe8, f=..., a=...) at /usr/include/boost/bind/bind.hpp:238
#6 0x00007ffff6f2872f in boost::_bi::bind_t<void, boost::_mfi::mf0<void, ARDOUR::Graph>, boost::_bi::list1<boost::_bi::value<ARDOUR::Graph*> > >::operator()() (this=0x7fff9936cbd8) at /usr/include/boost/bind/bind.hpp:1273
#7 0x00007ffff6f2713f in boost::detail::function::void_function_obj_invoker0<boost::_bi::bind_t<void, boost::_mfi::mf0<void, ARDOUR::Graph>, boost::_bi::list1<boost::_bi::value<ARDOUR::Graph*> > >, void>::invoke(boost::detail::function::function_buffer&) (function_obj_ptr=...) at /usr/include/boost/function/function_template.hpp:158
0000008 0x000000000076d15e in boost::function0<void>::operator()() const (this=0x7fff9936cbd0) at /usr/include/boost/function/function_template.hpp:763
0000009 0x00007fffc923809c in ARDOUR::JACKAudioBackend::_start_process_thread(void*) (arg=0x228d690) at ../libs/backends/jack/jack_audiobackend.cc:955
0000010 0x00007ffff2bce14d in start_thread (arg=<optimized out>) at pthread_create.c:442
0000011 0x00007ffff2c4fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 80 (Thread 0x7fff993ee6c0 (LWP 53033) "RT-3-0x7fff993e"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
0000001 0x00007ffff51d79be in PBD::Semaphore::wait() (this=0x3b5c764) at ../libs/pbd/semutils.cc:120
#2 0x00007ffff6f1ed6d in ARDOUR::Graph::run_one() (this=0x3b5c630) at ../libs/ardour/graph.cc:322
#3 0x00007ffff6f1f279 in ARDOUR::Graph::helper_thread() (this=0x3b5c630) at ../libs/ardour/graph.cc:374
0000004 0x00007ffff6f2a07f in boost::_mfi::mf0<void, ARDOUR::Graph>::operator()(ARDOUR::Graph*) const (this=0x7fff993edbd8, p=0x3b5c630) at /usr/include/boost/bind/mem_fn_template.hpp:49
0000005 0x00007ffff6f2971d in boost::_bi::list1<boost::_bi::value<ARDOUR::Graph*> >::operator()<boost::_mfi::mf0<void, ARDOUR::Graph>, boost::_bi::list0>(boost::_bi::type<void>, boost::_mfi::mf0<void, ARDOUR::Graph>&, boost::_bi::list0&, int) (this=0x7fff993edbe8, f=..., a=...) at /usr/include/boost/bind/bind.hpp:238
#6 0x00007ffff6f2872f in boost::_bi::bind_t<void, boost::_mfi::mf0<void, ARDOUR::Graph>, boost::_bi::list1<boost::_bi::value<ARDOUR::Graph*> > >::operator()() (this=0x7fff993edbd8) at /usr/include/boost/bind/bind.hpp:1273
#7 0x00007ffff6f2713f in boost::detail::function::void_function_obj_invoker0<boost::_bi::bind_t<void, boost::_mfi::mf0<void, ARDOUR::Graph>, boost::_bi::list1<boost::_bi::value<ARDOUR::Graph*> > >, void>::invoke(boost::detail::function::function_buffer&) (function_obj_ptr=...) at /usr/include/boost/function/function_template.hpp:158
0000008 0x000000000076d15e in boost::function0<void>::operator()() const (this=0x7fff993edbd0) at /usr/include/boost/function/function_template.hpp:763
0000009 0x00007fffc923809c in ARDOUR::JACKAudioBackend::_start_process_thread(void*) (arg=0x22d6d80) at ../libs/backends/jack/jack_audiobackend.cc:955
0000010 0x00007ffff2bce14d in start_thread (arg=<optimized out>) at pthread_create.c:442
0000011 0x00007ffff2c4fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 79 (Thread 0x7fff9946f6c0 (LWP 53032) "RT-2-0x7fff9946"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
0000001 0x00007ffff51d79be in PBD::Semaphore::wait() (this=0x3b5c764) at ../libs/pbd/semutils.cc:120
#2 0x00007ffff6f1ed6d in ARDOUR::Graph::run_one() (this=0x3b5c630) at ../libs/ardour/graph.cc:322
#3 0x00007ffff6f1f279 in ARDOUR::Graph::helper_thread() (this=0x3b5c630) at ../libs/ardour/graph.cc:374
0000004 0x00007ffff6f2a07f in boost::_mfi::mf0<void, ARDOUR::Graph>::operator()(ARDOUR::Graph*) const (this=0x7fff9946ebd8, p=0x3b5c630) at /usr/include/boost/bind/mem_fn_template.hpp:49
0000005 0x00007ffff6f2971d in boost::_bi::list1<boost::_bi::value<ARDOUR::Graph*> >::operator()<boost::_mfi::mf0<void, ARDOUR::Graph>, boost::_bi::list0>(boost::_bi::type<void>, boost::_mfi::mf0<void, ARDOUR::Graph>&, boost::_bi::list0&, int) (this=0x7fff9946ebe8, f=..., a=...) at /usr/include/boost/bind/bind.hpp:238
#6 0x00007ffff6f2872f in boost::_bi::bind_t<void, boost::_mfi::mf0<void, ARDOUR::Graph>, boost::_bi::list1<boost::_bi::value<ARDOUR::Graph*> > >::operator()() (this=0x7fff9946ebd8) at /usr/include/boost/bind/bind.hpp:1273
#7 0x00007ffff6f2713f in boost::detail::function::void_function_obj_invoker0<boost::_bi::bind_t<void, boost::_mfi::mf0<void, ARDOUR::Graph>, boost::_bi::list1<boost::_bi::value<ARDOUR::Graph*> > >, void>::invoke(boost::detail::function::function_buffer&) (function_obj_ptr=...) at /usr/include/boost/function/function_template.hpp:158
0000008 0x000000000076d15e in boost::function0<void>::operator()() const (this=0x7fff9946ebd0) at /usr/include/boost/function/function_template.hpp:763
0000009 0x00007fffc923809c in ARDOUR::JACKAudioBackend::_start_process_thread(void*) (arg=0x2a19850) at ../libs/backends/jack/jack_audiobackend.cc:955
0000010 0x00007ffff2bce14d in start_thread (arg=<optimized out>) at pthread_create.c:442
0000011 0x00007ffff2c4fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 78 (Thread 0x7fff994f06c0 (LWP 53031) "RT-1-0x7fff994f"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
0000001 0x00007ffff51d79be in PBD::Semaphore::wait() (this=0x3b5c764) at ../libs/pbd/semutils.cc:120
#2 0x00007ffff6f1ed6d in ARDOUR::Graph::run_one() (this=0x3b5c630) at ../libs/ardour/graph.cc:322
#3 0x00007ffff6f1f279 in ARDOUR::Graph::helper_thread() (this=0x3b5c630) at ../libs/ardour/graph.cc:374
0000004 0x00007ffff6f2a07f in boost::_mfi::mf0<void, ARDOUR::Graph>::operator()(ARDOUR::Graph*) const (this=0x7fff994efbd8, p=0x3b5c630) at /usr/include/boost/bind/mem_fn_template.hpp:49
0000005 0x00007ffff6f2971d in boost::_bi::list1<boost::_bi::value<ARDOUR::Graph*> >::operator()<boost::_mfi::mf0<void, ARDOUR::Graph>, boost::_bi::list0>(boost::_bi::type<void>, boost::_mfi::mf0<void, ARDOUR::Graph>&, boost::_bi::list0&, int) (this=0x7fff994efbe8, f=..., a=...) at /usr/include/boost/bind/bind.hpp:238
#6 0x00007ffff6f2872f in boost::_bi::bind_t<void, boost::_mfi::mf0<void, ARDOUR::Graph>, boost::_bi::list1<boost::_bi::value<ARDOUR::Graph*> > >::operator()() (this=0x7fff994efbd8) at /usr/include/boost/bind/bind.hpp:1273
#7 0x00007ffff6f2713f in boost::detail::function::void_function_obj_invoker0<boost::_bi::bind_t<void, boost::_mfi::mf0<void, ARDOUR::Graph>, boost::_bi::list1<boost::_bi::value<ARDOUR::Graph*> > >, void>::invoke(boost::detail::function::function_buffer&) (function_obj_ptr=...) at /usr/include/boost/function/function_template.hpp:158
0000008 0x000000000076d15e in boost::function0<void>::operator()() const (this=0x7fff994efbd0) at /usr/include/boost/function/function_template.hpp:763
0000009 0x00007fffc923809c in ARDOUR::JACKAudioBackend::_start_process_thread(void*) (arg=0x3d07ac0) at ../libs/backends/jack/jack_audiobackend.cc:955
0000010 0x00007ffff2bce14d in start_thread (arg=<optimized out>) at pthread_create.c:442
0000011 0x00007ffff2c4fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 77 (Thread 0x7fff995716c0 (LWP 53030) "RT-main-0x7fff9"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
0000001 0x00007ffff51d79be in PBD::Semaphore::wait() (this=0x3b5c770) at ../libs/pbd/semutils.cc:120
#2 0x00007ffff6f1e856 in ARDOUR::Graph::reached_terminal_node() (this=0x3b5c630) at ../libs/ardour/graph.cc:269
#3 0x00007ffff6f2af47 in ARDOUR::GraphNode::finish(ARDOUR::GraphChain const*) (this=0x4463be0, chain=0x7fffa801f850) at ../libs/ardour/graphnode.cc:99
0000004 0x00007ffff6f2ae24 in ARDOUR::GraphNode::run(ARDOUR::GraphChain const*) (this=0x4463be0, chain=0x7fffa801f850) at ../libs/ardour/graphnode.cc:66
0000005 0x00007ffff6f1ef23 in ARDOUR::Graph::run_one() (this=0x3b5c630) at ../libs/ardour/graph.cc:346
#6 0x00007ffff6f1f6b8 in ARDOUR::Graph::main_thread() (this=0x3b5c630) at ../libs/ardour/graph.cc:427
#7 0x00007ffff6f2a07f in boost::_mfi::mf0<void, ARDOUR::Graph>::operator()(ARDOUR::Graph*) const (this=0x7fff99570bd8, p=0x3b5c630) at /usr/include/boost/bind/mem_fn_template.hpp:49
0000008 0x00007ffff6f2971d in boost::_bi::list1<boost::_bi::value<ARDOUR::Graph*> >::operator()<boost::_mfi::mf0<void, ARDOUR::Graph>, boost::_bi::list0>(boost::_bi::type<void>, boost::_mfi::mf0<void, ARDOUR::Graph>&, boost::_bi::list0&, int) (this=0x7fff99570be8, f=..., a=...) at /usr/include/boost/bind/bind.hpp:238
0000009 0x00007ffff6f2872f in boost::_bi::bind_t<void, boost::_mfi::mf0<void, ARDOUR::Graph>, boost::_bi::list1<boost::_bi::value<ARDOUR::Graph*> > >::operator()() (this=0x7fff99570bd8) at /usr/include/boost/bind/bind.hpp:1273
0000010 0x00007ffff6f2713f in boost::detail::function::void_function_obj_invoker0<boost::_bi::bind_t<void, boost::_mfi::mf0<void, ARDOUR::Graph>, boost::_bi::list1<boost::_bi::value<ARDOUR::Graph*> > >, void>::invoke(boost::detail::function::function_buffer&) (function_obj_ptr=...) at /usr/include/boost/function/function_template.hpp:158
0000011 0x000000000076d15e in boost::function0<void>::operator()() const (this=0x7fff99570bd0) at /usr/include/boost/function/function_template.hpp:763
0000012 0x00007fffc923809c in ARDOUR::JACKAudioBackend::_start_process_thread(void*) (arg=0x3e0ff10) at ../libs/backends/jack/jack_audiobackend.cc:955
0000013 0x00007ffff2bce14d in start_thread (arg=<optimized out>) at pthread_create.c:442
0000014 0x00007ffff2c4fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 49 (Thread 0x7fff9bf2c6c0 (LWP 53002) "audioengine"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
0000001 0x00007fffcab0aacb in Jack::JackLinuxFutex::Wait() (this=0x2b8a368) at ../linux/JackLinuxFutex.cpp:104
#2 0x00007fffcab0abdd in Jack::JackLinuxFutex::TimedWait(long) (this=<optimized out>, usec=usec@entry=9223372036854775807) at ../linux/JackLinuxFutex.cpp:113
#3 0x00007fffcaaecdaa in Jack::JackConnectionManager::SuspendRefNum(Jack::JackClientControl*, Jack::JackLinuxFutex*, Jack::JackClientTiming*, long) (this=<optimized out>, control=0x7fffcbf46000, table=table@entry=0x2b8a020, timing=timing@entry=0x7fff87df721c, time_out_usec=time_out_usec@entry=9223372036854775807) at ../common/JackConnectionManager.cpp:241
0000004 0x00007fffcaaef639 in Jack::JackGraphManager::SuspendRefNum(Jack::JackClientControl*, Jack::JackLinuxFutex*, long) (this=this@entry=0x7fff859a1000, control=<optimized out>, table=table@entry=0x2b8a020, usec=usec@entry=9223372036854775807) at ../common/JackGraphManager.cpp:130
0000005 0x00007fffcaaeadb0 in Jack::JackClient::WaitSync() (this=<optimized out>) at ../common/JackClient.cpp:640
#6 Jack::JackClient::CycleWaitAux() (this=<optimized out>) at ../common/JackClient.cpp:604
#7 Jack::JackClient::CycleWait() (this=0x275f800) at ../common/JackClient.cpp:624
0000008 0x00007fffc923815f in ARDOUR::JACKAudioBackend::process_thread() (this=0x1f14460) at ../libs/backends/jack/jack_audiobackend.cc:984
0000009 0x00007fffc92380ea in ARDOUR::JACKAudioBackend::_process_thread(void*) (arg=0x1f14460) at ../libs/backends/jack/jack_audiobackend.cc:963
0000010 0x00007fffcaaeb234 in non-virtual thunk to Jack::JackClient::Execute() () at ../common/JackClient.h:220
0000011 0x00007fffcab08cf0 in Jack::JackPosixThread::ThreadHandler(void*) (arg=0x275fa48) at ../posix/JackPosixThread.cpp:63
0000012 0x00007ffff2bce14d in start_thread (arg=<optimized out>) at pthread_create.c:442
0000013 0x00007ffff2c4fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 48 (Thread 0x7fffb82ea6c0 (LWP 53001) "audioengine"):
#0 __GI___libc_read (nbytes=4, buf=0x7fffb82e9a70, fd=22) at ../sysdeps/unix/sysv/linux/read.c:26
0000001 __GI___libc_read (fd=22, buf=0x7fffb82e9a70, nbytes=nbytes@entry=4) at ../sysdeps/unix/sysv/linux/read.c:24
#2 0x00007fffcab09f59 in read (__nbytes=4, __buf=<optimized out>, __fd=<optimized out>) at /usr/include/bits/unistd.h:38
#3 Jack::JackClientSocket::Read(void*, int) (this=0x7fffa80211a0, data=<optimized out>, len=4) at ../posix/JackSocket.cpp:196
0000004 0x00007fffcab0ed71 in Jack::JackClientNotification::Read(Jack::detail::JackChannelTransactionInterface*) (this=this@entry=0x7fffb82e9a70, trans=0x7fffa80211a0) at ../common/JackRequest.h:1711
0000005 0x00007fffcab0eba7 in Jack::JackSocketClientChannel::Execute() (this=0x21c3a90) at ../posix/JackSocketClientChannel.cpp:138
#6 0x00007fffcab08cf0 in Jack::JackPosixThread::ThreadHandler(void*) (arg=0x21c3bc0) at ../posix/JackPosixThread.cpp:63
#7 0x00007ffff2bce14d in start_thread (arg=<optimized out>) at pthread_create.c:442
0000008 0x00007ffff2c4fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 47 (Thread 0x7fffb87f86c0 (LWP 53000) "audioengine"):
#0 __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x2ba3b48) at futex-internal.c:57
0000001 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x2ba3b48, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0, cancel=cancel@entry=true) at futex-internal.c:87
#2 0x00007ffff2bcad9f in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x2ba3b48, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at futex-internal.c:139
#3 0x00007ffff2bcd530 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x2ba3af0, cond=0x2ba3b20) at pthread_cond_wait.c:503
0000004 ___pthread_cond_wait (cond=0x2ba3b20, mutex=0x2ba3af0) at pthread_cond_wait.c:618
0000005 0x00007fffcab097c4 in Jack::JackPosixProcessSync::Wait() (this=0x2ba3ae8) at ../posix/JackPosixProcessSync.cpp:81
#6 0x00007fffcaafdc9d in Jack::JackMessageBuffer::Execute() (this=0x2b9b8b0) at ../common/JackMessageBuffer.cpp:107
#7 0x00007fffcab08cf0 in Jack::JackPosixThread::ThreadHandler(void*) (arg=0x2ba3ac8) at ../posix/JackPosixThread.cpp:63
0000008 0x00007ffff2bce14d in start_thread (arg=<optimized out>) at pthread_create.c:442
0000009 0x00007ffff2c4fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 15 (Thread 0x7fffbbfff6c0 (LWP 52966) "gdbus"):
#0 0x00007ffff2c4205f in __GI___poll (fds=0x25c9b20, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
0000001 0x00007ffff4ea950d in g_main_context_poll (priority=<optimized out>, n_fds=3, fds=0x25c9b20, timeout=<optimized out>, context=0x25c87b0) at ../glib/gmain.c:4543
#2 g_main_context_iterate.constprop.0 (context=0x25c87b0, block=1, dispatch=1, self=<optimized out>) at ../glib/gmain.c:4233
#3 0x00007ffff4e5328f in g_main_loop_run (loop=0x25c88a0) at ../glib/gmain.c:4438
0000004 0x00007ffff461488a in gdbus_shared_thread_func (user_data=0x25c8780) at ../gio/gdbusprivate.c:284
0000005 0x00007ffff4e7d9c2 in g_thread_proxy (data=0x25c4240) at ../glib/gthread.c:831
#6 0x00007ffff2bce14d in start_thread (arg=<optimized out>) at pthread_create.c:442
#7 0x00007ffff2c4fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 14 (Thread 0x7fffbb7fe6c0 (LWP 52965) "gmain"):
#0 0x00007ffff2c4205f in __GI___poll (fds=0x25c0390, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
0000001 0x00007ffff4ea950d in g_main_context_poll (priority=<optimized out>, n_fds=2, fds=0x25c0390, timeout=<optimized out>, context=0x25be290) at ../glib/gmain.c:4543
#2 g_main_context_iterate.constprop.0 (context=0x25be290, block=1, dispatch=1, self=<optimized out>) at ../glib/gmain.c:4233
#3 0x00007ffff4e50f40 in g_main_context_iteration (context=0x25be290, may_block=may_block@entry=1) at ../glib/gmain.c:4303
0000004 0x00007ffff4e52bd1 in glib_worker_main (data=<optimized out>) at ../glib/gmain.c:6414
0000005 0x00007ffff4e7d9c2 in g_thread_proxy (data=0x256c980) at ../glib/gthread.c:831
#6 0x00007ffff2bce14d in start_thread (arg=<optimized out>) at pthread_create.c:442
#7 0x00007ffff2c4fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 9 (Thread 0x7fffc9a7b6c0 (LWP 52960) "DeviceList"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
0000001 0x00007ffff4ea4e83 in g_cond_wait (cond=0x1ed0028, mutex=0x1ed0038) at ../glib/gthread-posix.c:1590
#2 0x00007ffff6d6432f in ARDOUR::AudioEngine::do_devicelist_update() (this=0x1ecf670) at ../libs/ardour/audioengine.cc:747
#3 0x00007ffff6d72067 in boost::_mfi::mf0<void, ARDOUR::AudioEngine>::operator()(ARDOUR::AudioEngine*) const (this=0x1f16ec0, p=0x1ecf670) at /usr/include/boost/bind/mem_fn_template.hpp:49
0000004 0x00007ffff6d7172f in boost::_bi::list1<boost::_bi::value<ARDOUR::AudioEngine*> >::operator()<boost::_mfi::mf0<void, ARDOUR::AudioEngine>, boost::_bi::list0>(boost::_bi::type<void>, boost::_mfi::mf0<void, ARDOUR::AudioEngine>&, boost::_bi::list0&, int) (this=0x1f16ed0, f=..., a=...) at /usr/include/boost/bind/bind.hpp:238
0000005 0x00007ffff6d70cab in boost::_bi::bind_t<void, boost::_mfi::mf0<void, ARDOUR::AudioEngine>, boost::_bi::list1<boost::_bi::value<ARDOUR::AudioEngine*> > >::operator()() (this=0x1f16ec0) at /usr/include/boost/bind/bind.hpp:1273
#6 0x00007ffff6d70121 in boost::detail::function::void_function_obj_invoker0<boost::_bi::bind_t<void, boost::_mfi::mf0<void, ARDOUR::AudioEngine>, boost::_bi::list1<boost::_bi::value<ARDOUR::AudioEngine*> > >, void>::invoke(boost::detail::function::function_buffer&) (function_obj_ptr=...) at /usr/include/boost/function/function_template.hpp:158
#7 0x000000000076d15e in boost::function0<void>::operator()() const (this=0x1f16eb8) at /usr/include/boost/function/function_template.hpp:763
0000008 0x00007ffff51d1787 in PBD::Thread::_run(void*) (arg=0x1f16e90) at ../libs/pbd/pthread_utils.cc:488
0000009 0x00007ffff2bce14d in start_thread (arg=<optimized out>) at pthread_create.c:442
0000010 0x00007ffff2c4fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 8 (Thread 0x7fffca4236c0 (LWP 52959) "EngineWatchdog"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
0000001 0x00007ffff4ea4e83 in g_cond_wait (cond=0x1ecfff8, mutex=0x1ed0008) at ../glib/gthread-posix.c:1590
#2 0x00007ffff6d640dd in ARDOUR::AudioEngine::do_reset_backend() (this=0x1ecf670) at ../libs/ardour/audioengine.cc:711
#3 0x00007ffff6d72067 in boost::_mfi::mf0<void, ARDOUR::AudioEngine>::operator()(ARDOUR::AudioEngine*) const (this=0x1f16b80, p=0x1ecf670) at /usr/include/boost/bind/mem_fn_template.hpp:49
0000004 0x00007ffff6d7172f in boost::_bi::list1<boost::_bi::value<ARDOUR::AudioEngine*> >::operator()<boost::_mfi::mf0<void, ARDOUR::AudioEngine>, boost::_bi::list0>(boost::_bi::type<void>, boost::_mfi::mf0<void, ARDOUR::AudioEngine>&, boost::_bi::list0&, int) (this=0x1f16b90, f=..., a=...) at /usr/include/boost/bind/bind.hpp:238
0000005 0x00007ffff6d70cab in boost::_bi::bind_t<void, boost::_mfi::mf0<void, ARDOUR::AudioEngine>, boost::_bi::list1<boost::_bi::value<ARDOUR::AudioEngine*> > >::operator()() (this=0x1f16b80) at /usr/include/boost/bind/bind.hpp:1273
#6 0x00007ffff6d70121 in boost::detail::function::void_function_obj_invoker0<boost::_bi::bind_t<void, boost::_mfi::mf0<void, ARDOUR::AudioEngine>, boost::_bi::list1<boost::_bi::value<ARDOUR::AudioEngine*> > >, void>::invoke(boost::detail::function::function_buffer&) (function_obj_ptr=...) at /usr/include/boost/function/function_template.hpp:158
#7 0x000000000076d15e in boost::function0<void>::operator()() const (this=0x1f16b78) at /usr/include/boost/function/function_template.hpp:763
0000008 0x00007ffff51d1787 in PBD::Thread::_run(void*) (arg=0x1f16b50) at ../libs/pbd/pthread_utils.cc:488
0000009 0x00007ffff2bce14d in start_thread (arg=<optimized out>) at pthread_create.c:442
0000010 0x00007ffff2c4fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 6 (Thread 0x7fffe08f36c0 (LWP 52957) "Analyzer"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
0000001 0x00007ffff4ea4e83 in g_cond_wait (cond=0x7ffff7d4fee0 <ARDOUR::Analyser::SourcesToAnalyse>, mutex=0x7ffff7d4fed8 <ARDOUR::Analyser::analysis_queue_lock>) at ../glib/gthread-posix.c:1590
#2 0x00007ffff6d133d5 in ARDOUR::Analyser::work() () at ../libs/ardour/analyser.cc:95
#3 0x00000000010c2e05 in sigc::pointer_functor0<void>::operator()() const (this=0x1ea52d0) at /usr/include/sigc++-2.0/sigc++/functors/ptr_fun.h:77
0000004 0x00007ffff6d165a9 in boost::detail::function::void_function_obj_invoker0<sigc::pointer_functor0<void>, void>::invoke(boost::detail::function::function_buffer&) (function_obj_ptr=...) at /usr/include/boost/function/function_template.hpp:158
0000005 0x000000000076d15e in boost::function0<void>::operator()() const (this=0x1ea52c8) at /usr/include/boost/function/function_template.hpp:763
#6 0x00007ffff51d1787 in PBD::Thread::_run(void*) (arg=0x1ea52a0) at ../libs/pbd/pthread_utils.cc:488
#7 0x00007ffff2bce14d in start_thread (arg=<optimized out>) at pthread_create.c:442
0000008 0x00007ffff2c4fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 5 (Thread 0x7fffe10f46c0 (LWP 52956) "PeakFileBuilder"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
0000001 0x00007ffff4ea4e83 in g_cond_wait (cond=0x7ffff7d52e90 <ARDOUR::SourceFactory::PeaksToBuild>, mutex=0x7ffff7d52ea0 <ARDOUR::SourceFactory::peak_building_lock>) at ../glib/gthread-posix.c:1590
#2 0x00007ffff75f09ae in peak_thread_work() () at ../libs/ardour/source_factory.cc:75
#3 0x00007ffff7f29f9e in boost::detail::function::void_function_invoker0<void (*)(), void>::invoke(boost::detail::function::function_buffer&) (function_ptr=...) at /usr/include/boost/function/function_template.hpp:117
0000004 0x000000000076d15e in boost::function0<void>::operator()() const (this=0x1ea56b8) at /usr/include/boost/function/function_template.hpp:763
0000005 0x00007ffff51d1787 in PBD::Thread::_run(void*) (arg=0x1ea5690) at ../libs/pbd/pthread_utils.cc:488
#6 0x00007ffff2bce14d in start_thread (arg=<optimized out>) at pthread_create.c:442
#7 0x00007ffff2c4fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 4 (Thread 0x7fffe18f56c0 (LWP 52955) "PeakFileBuilder"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
0000001 0x00007ffff4ea4e83 in g_cond_wait (cond=0x7ffff7d52e90 <ARDOUR::SourceFactory::PeaksToBuild>, mutex=0x7ffff7d52ea0 <ARDOUR::SourceFactory::peak_building_lock>) at ../glib/gthread-posix.c:1590
#2 0x00007ffff75f09ae in peak_thread_work() () at ../libs/ardour/source_factory.cc:75
#3 0x00007ffff7f29f9e in boost::detail::function::void_function_invoker0<void (*)(), void>::invoke(boost::detail::function::function_buffer&) (function_ptr=...) at /usr/include/boost/function/function_template.hpp:117
0000004 0x000000000076d15e in boost::function0<void>::operator()() const (this=0x1ea5b58) at /usr/include/boost/function/function_template.hpp:763
0000005 0x00007ffff51d1787 in PBD::Thread::_run(void*) (arg=0x1ea5b30) at ../libs/pbd/pthread_utils.cc:488
#6 0x00007ffff2bce14d in start_thread (arg=<optimized out>) at pthread_create.c:442
#7 0x00007ffff2c4fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 3 (Thread 0x7fffe20f66c0 (LWP 52954) "LXVSTEventLoop"):
#0 0x00007ffff2c15095 in __GI___clock_nanosleep (clock_id=clock_id@entry=0, flags=flags@entry=0, req=req@entry=0x7fffe20f5ad0, rem=rem@entry=0x7fffe20f5ac0) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:48
0000001 0x00007ffff2c19847 in __GI___nanosleep (req=req@entry=0x7fffe20f5ad0, rem=rem@entry=0x7fffe20f5ac0) at ../sysdeps/unix/sysv/linux/nanosleep.c:25
#2 0x00007ffff4e7b83f in g_usleep (microseconds=<optimized out>) at ../glib/gtimer.c:279
#3 0x000000000156be0a in gui_event_loop(void*) (ptr=0x0) at ../gtk2_ardour/linux_vst_gui_support.cc:468
0000004 0x00007ffff2bce14d in start_thread (arg=<optimized out>) at pthread_create.c:442
0000005 0x00007ffff2c4fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Thread 2 (Thread 0x7fffef9016c0 (LWP 52953) "Trigger Worker"):
#0 0x00007ffff2c4205f in __GI___poll (fds=0x7fffef900aa4, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
0000001 0x00007ffff51a9ac6 in CrossThreadChannel::poll_for_request() (this=0x1e4e2e8) at ../libs/pbd/crossthread.posix.cc:108
#2 0x00007ffff51a9b35 in CrossThreadChannel::receive(char&, bool) (this=0x1e4e2e8, msg=@0x7fffef900b0f: -1 '\377', wait=true) at ../libs/pbd/crossthread.posix.cc:133
#3 0x00007ffff7651a5a in ARDOUR::TriggerBoxThread::thread_work() (this=0x1e4e2c0) at ../libs/ardour/triggerbox.cc:4841
0000004 0x00007ffff76519ef in ARDOUR::TriggerBoxThread::_thread_work(void*) (arg=0x1e4e2c0) at ../libs/ardour/triggerbox.cc:4829
0000005 0x00007ffff51d0c44 in fake_thread_start(void*) (arg=0x1de8b60) at ../libs/pbd/pthread_utils.cc:101
#6 0x00007ffff2bce14d in start_thread (arg=<optimized out>) at pthread_create.c:442
#7 0x00007ffff2c4fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81


Thread 1 (Thread 0x7ffff1730a00 (LWP 52952) "ArdourGUI"):
#0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
0000001 0x00007ffff4ea4dfc in g_mutex_lock_slowpath (mutex=0x1d637d8 <Temporal::TempoMap::_map_mgr+24>) at ../glib/gthread-posix.c:1503
#2 0x00007ffff59fb0a9 in SerializedRCUManager<Temporal::TempoMap>::write_copy() (this=0x1d637c0 <Temporal::TempoMap::_map_mgr>) at ../libs/pbd/pbd/rcu.h:162
#3 0x00007ffff59e74e2 in Temporal::TempoMap::write_copy() () at ../libs/temporal/tempo.cc:3367
0000004 0x0000000000b0a831 in Temporal::TempoMap::fetch_writable() () at ../libs/temporal/temporal/tempo.h:709
0000005 0x0000000000b09e59 in Editor::begin_tempo_map_edit() (this=0x2d5f850) at ../gtk2_ardour/editor_tempodisplay.cc:758
#6 0x00000000013fe7c3 in TempoMapChange::begin() (this=0x7fffffffb150) at ../gtk2_ardour/tempo_map_change.cc:50
#7 0x00000000013fe5dd in TempoMapChange::TempoMapChange(PublicEditor&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, bool, bool) (this=0x7fffffffb150, e=..., str="set tempo from region", uoc=true, begin_now=true) at ../gtk2_ardour/tempo_map_change.cc:31
0000008 0x0000000000a9cf5d in Editor::define_one_bar(Temporal::timepos_t const&, Temporal::timepos_t const&) (this=0x2d5f850, start=..., end=...) at ../gtk2_ardour/editor_ops.cc:7485
0000009 0x0000000000a9cac4 in Editor::use_range_as_bar() (this=0x2d5f850) at ../gtk2_ardour/editor_ops.cc:7408
0000010 0x0000000000985f72 in sigc::bound_mem_functor0<void, Editor>::operator()() const (this=0x2ed6fd8) at /usr/include/sigc++-2.0/sigc++/functors/mem_fun.h:1991
0000011 0x000000000097dada in sigc::adaptor_functor<sigc::bound_mem_functor0<void, Editor> >::operator()() const (this=0x2ed6fd0) at /usr/include/sigc++-2.0/sigc++/adaptors/adaptor_trait.h:256
0000012 0x000000000097db01 in sigc::internal::slot_call0<sigc::bound_mem_functor0<void, Editor>, void>::call_it(sigc::internal::slot_rep*) (rep=0x2ed6fa0) at /usr/include/sigc++-2.0/sigc++/functors/slot.h:136
0000013 0x00007ffff4fa0fac in sigc::slot0<void>::operator()() const (this=0x2ef81d8) at /usr/include/sigc++-2.0/sigc++/functors/slot.h:535
0000014 Glib::SignalProxyNormal::slot0_void_callback(_GObject*, void*) (self=<optimized out>, data=0x2ef81d0) at ../glib/glibmm/signalproxy.cc:103
#15 0x00007ffff5642fc0 in g_closure_invoke (closure=0x2efae90, return_value=0x0, n_param_values=1, param_values=0x7fffffffb650, invocation_hint=0x7fffffffb5d0) at ../gobject/gclosure.c:832
0000016 0x00007ffff5671054 in signal_emit_unlocked_R.isra.0 (node=node@entry=0x24f2f80, detail=detail@entry=0, instance=instance@entry=0x2ef7b70, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffffffb650) at ../gobject/gsignal.c:3867
#17 0x00007ffff566041a in g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7fffffffb7f0) at ../gobject/gsignal.c:3549
0000018 0x00007ffff5660633 in g_signal_emit (instance=instance@entry=0x2ef7b70, signal_id=<optimized out>, detail=detail@entry=0) at ../gobject/gsignal.c:3606
0000019 0x00007ffff487c7ae in _gtk_action_emit_activate (action=0x2ef7b70) at /usr/src/debug/gtk2-2.24.33-10.fc37.x86_64/gtk/gtkaction.c:795
0000020 0x00007ffff5642fc0 in g_closure_invoke (closure=0x25097f0, return_value=0x0, n_param_values=1, param_values=0x7fffffffba80, invocation_hint=0x7fffffffba00) at ../gobject/gclosure.c:832
0000021 0x00007ffff5670a35 in signal_emit_unlocked_R.isra.0 (node=node@entry=0x2509850, detail=detail@entry=0, instance=instance@entry=0x3bb4940, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffffffba80) at ../gobject/gsignal.c:3726
0000022 0x00007ffff566041a in g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7fffffffbc20) at ../gobject/gsignal.c:3549
0000023 0x00007ffff5660633 in g_signal_emit (instance=instance@entry=0x3bb4940, signal_id=<optimized out>, detail=detail@entry=0) at ../gobject/gsignal.c:3606
#24 0x00007ffff4a94b6c in IA__gtk_widget_activate (widget=0x3bb4940) at /usr/src/debug/gtk2-2.24.33-10.fc37.x86_64/gtk/gtkwidget.c:5048
0000025 0x00007ffff496b195 in IA__gtk_menu_shell_activate_item (menu_shell=0x3bb0450, menu_item=0x3bb4940, force_deactivate=<optimized out>) at /usr/src/debug/gtk2-2.24.33-10.fc37.x86_64/gtk/gtkmenushell.c:1305
0000026 0x00007ffff496d769 in gtk_menu_shell_button_release (widget=0x3bb0450, event=<optimized out>) at /usr/src/debug/gtk2-2.24.33-10.fc37.x86_64/gtk/gtkmenushell.c:730
0000027 0x00007ffff49551e9 in _gtk_marshal_BOOLEAN__BOXED (closure=0x25050f0, return_value=0x7fffffffbf50, n_param_values=<optimized out>, param_values=0x7fffffffbfb0, invocation_hint=<optimized out>, marshal_data=<optimized out>) at /usr/src/debug/gtk2-2.24.33-10.fc37.x86_64/gtk/gtkmarshalers.c:84
0000028 0x00007ffff5642fc0 in g_closure_invoke (closure=0x25050f0, return_value=0x7fffffffbf50, n_param_values=2, param_values=0x7fffffffbfb0, invocation_hint=0x7fffffffbf30) at ../gobject/gclosure.c:832
0000029 0x00007ffff5670eb5 in signal_emit_unlocked_R.isra.0 (node=<optimized out>, detail=detail@entry=0, instance=instance@entry=0x3bb0450, emission_return=emission_return@entry=0x7fffffffc0c0, instance_and_params=instance_and_params@entry=0x7fffffffbfb0) at ../gobject/gsignal.c:3835
0000030 0x00007ffff565fe16 in g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=var_args@entry=0x7fffffffc170) at ../gobject/gsignal.c:3559
0000031 0x00007ffff5660633 in g_signal_emit (instance=instance@entry=0x3bb0450, signal_id=<optimized out>, detail=detail@entry=0) at ../gobject/gsignal.c:3606
0000032 0x00007ffff4a96b44 in gtk_widget_event_internal (widget=0x3bb0450, event=0x2396520) at /usr/src/debug/gtk2-2.24.33-10.fc37.x86_64/gtk/gtkwidget.c:5017
0000033 0x00007ffff4957c74 in IA__gtk_propagate_event (widget=0x3bb0450, event=0x2396520) at /usr/src/debug/gtk2-2.24.33-10.fc37.x86_64/gtk/gtkmain.c:2503
0000034 0x00007ffff4959883 in IA__gtk_main_do_event (event=0x2396520) at /usr/src/debug/gtk2-2.24.33-10.fc37.x86_64/gtk/gtkmain.c:1698
0000035 IA__gtk_main_do_event (event=<optimized out>) at /usr/src/debug/gtk2-2.24.33-10.fc37.x86_64/gtk/gtkmain.c:1503
0000036 0x00007ffff4d98c33 in gdk_event_dispatch (source=<optimized out>, callback=<optimized out>, user_data=<optimized out>) at x11/gdkevents-x11.c:2425
0000037 0x00007ffff4e53cbf in g_main_dispatch (context=0x1eee420) at ../glib/gmain.c:3444
0000038 g_main_context_dispatch (context=0x1eee420) at ../glib/gmain.c:4162
0000039 0x00007ffff4ea9598 in g_main_context_iterate.constprop.0 (context=0x1eee420, block=1, dispatch=1, self=<optimized out>) at ../glib/gmain.c:4238
0000040 0x00007ffff4e5328f in g_main_loop_run (loop=0x2d254e0) at ../glib/gmain.c:4438
0000041 0x00007ffff4952fdf in IA__gtk_main () at /usr/src/debug/gtk2-2.24.33-10.fc37.x86_64/gtk/gtkmain.c:1270
0000042 0x00007ffff5389be5 in Gtkmm2ext::UI::run(Receiver&) (this=0x2486d50, old_receiver=...) at ../libs/gtkmm2ext/gtk_ui.cc:309
0000043 0x0000000000db15c4 in main(int, char**) (argc=1, argv=0x7fffffffcac8) at ../gtk2_ardour/main.cc:456
Warning: the current language does not match this frame.
(gdb)

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9168 [ardour] features minor have not tried 2022-12-16 12:47 2022-12-16 16:47
Reporter: Pat Platform: GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Editor view, also remember edit list and edit mixer
Description: Hello

In the Editor views one can store the track states. However also : edit list and edit mixer and which track is hidden could be stored.

Why
 
One use for Editor view is a fast way to view better tracks. Since the other also helps much to view better tracks, could they be included.

Mbr Patrik
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0027104)
x42   
2022-12-16 13:21   
(Last edited: 2022-12-16 13:22)
That should already be the case.

Can you check the file instant.xml - which saves the GUI state - in your session folder?
there should be the following information saved (and later restored)
show-editor-mixer="1" show-editor-list="1" editor-list-page="6"

(0027105)
Pat   
2022-12-16 14:25   
Hello, I checked, that the edit mixer and the edit list states could not be restored. (track zoom state works). I've attached here the file you requested:
<?xml version="1.0" encoding="UTF-8"?>
<instant>
  <LocationUI clock-mode="BBT"/>
  <Main x="0" y="0" w="1366" h="813" current-tab="editor"/>
  <Mixer mixer-rhs-pane1-pos="0.60000002384185791" mixer-rhs_pane2-pos="0.69999998807907104" mixer-list-hpane-pos="0.20000000298023224" mixer-inner-pane-pos="0.80000001192092896" narrow-strips="0" show-mixer="0" maximised="0" show-mixer-list="0" monitor-section-visible="0" foldback-strip-visible="1" show-vca-pane="1">
    <Window name="Mixer" visible="0" x-off="-1" y-off="-1" x-size="-1" y-size="-1" tabbed="1"/>
  </Mixer>
  <Preferences>
    <Window name="Preferences" visible="1" x-off="0" y-off="0" x-size="841" y-size="735" tabbed="0"/>
  </Preferences>
  <Meterbridge show-meterbridge="0">
    <geometry x-size="163" y-size="387" x-pos="3" y-pos="29"/>
  </Meterbridge>
  <Recorder recorder-vpane-pos="0.75">
    <Window name="Recorder" visible="0" x-off="-1" y-off="-1" x-size="-1" y-size="-1" tabbed="1"/>
  </Recorder>
  <TriggerPage triggerpage-hpane-pos="0.23154363036155701" triggerpage-sidebar-page="0">
    <Window name="Cues" visible="0" x-off="506" y-off="27" x-size="856" y-size="711" tabbed="1"/>
  </TriggerPage>
  <ClockModes>
    <Clock name="primary" mode="BBT" on="1"/>
    <Clock name="secondary" mode="Timecode" on="1"/>
    <Clock name="bigclock" mode="Timecode" on="1"/>
    <Clock name="nudge" mode="Timecode" on="1"/>
    <Clock name="EditorTimeInfo-selection-start" mode="Timecode" on="0"/>
    <Clock name="EditorTimeInfo-selection-end" mode="Timecode" on="0"/>
    <Clock name="EditorTimeInfo-selection-length" mode="Timecode" on="0"/>
    <Clock name="EditorTimeInfo-punch-start" mode="Timecode" on="0"/>
    <Clock name="EditorTimeInfo-punch-end" mode="Timecode" on="0"/>
    <Clock name="ToolbarTimeInfo-selection-start" mode="Timecode" on="0"/>
    <Clock name="ToolbarTimeInfo-selection-end" mode="Timecode" on="0"/>
    <Clock name="ToolbarTimeInfo-selection-length" mode="Timecode" on="0"/>
  </ClockModes>
  <LastUsedSnapshot name="pat second"/>
  <Editor id="49" edit-horizontal-pane-pos="0.86783438920974731" notebook-shrunk="0" edit-vertical-pane-pos="0.90518516302108765" mixer-width="Wide" zoom-focus="ZoomFocusPlayhead" zoom="172" grid-type="GridTypeBeat" snap-mode="SnapMagnetic" internal-grid-type="GridTypeBeat" internal-snap-mode="SnapOff" pre-internal-grid-type="GridTypeBeat" pre-internal-snap-mode="SnapMagnetic" edit-point="EditAtMouse" visible-track-count="-1" draw-length="GridTypeNone" draw-velocity="-1" draw-channel="-1" playhead="0" left-frame="176302" y-origin="0" maximised="1" follow-playhead="1" stationary-playhead="0" mouse-mode="MouseDraw" join-object-range="1" show-editor-mixer="1" show-editor-list="1" editor-list-page="0" show-marker-lines="0" show-touched-automation="0" nudge-clock-value="a1411200000@a0">
    <Window name="Editor" visible="0" x-off="-1" y-off="-1" x-size="-1" y-size="-1" tabbed="1"/>
    <Buttons>
      <Press/>
      <Release/>
    </Buttons>
    <Selection/>
    <EditorLocations clock-mode="BBT"/>
  </Editor>
</instant>
(0027106)
Pat   
2022-12-16 16:47   
your wrote it should read as xml as following
show-editor-mixer="1" show-editor-list="1" editor-list-page="6"

My session file was different
show-editor-mixer="1" show-editor-list="1" editor-list-page="0" show-marker-lines="0" show-touched-automation="0" nudge-clock-value="a1411200000@a0">

I did try several time to save with edit list with above elements disabled and the enabled them again. Finally i loaded the saved edit, but it did not affect the elements, only track zoom state.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9078 [ardour] bugs crash always 2022-11-07 19:37 2022-12-16 10:29
Reporter: Jxs Platform: Linux  
Assigned To: OS: Mageia  
Priority: normal OS Version: 8  
Status: resolved Product Version: 7.1  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Crash when trying to delete first tempo marker
Description: as in summary
Tags: 7.1, crash, Linux, Windows
Steps To Reproduce: 1. Open new empty project
2. select the first tempo marker
3. press Del key
4. crash

Additional Information: One of the messages in the console says: Floating point exception (core dumped)
Attached Files:
Notes
(0026866)
Jxs   
2022-11-07 19:52   
I was actually trying to follow instructions from https://manual.ardour.org/arranging/time-tempo-and-time-signature/techniques-for-working-with-tempo-and-time-signature/
While playing around with tempo changes I experienced weird behaviour and several crashes. Most of them not so easy to reproduce. This bug report is about the simplest case of the problems I had. I will try to see if I can cook up some easy steps to reproduce the others
(0026966)
krischan941   
2022-11-30 15:34   
Confirmed, with Shift-Right-Click on first tempo marker.
(0027102)
Jxs   
2022-12-16 08:33   
Fixed in 7.2, commit https://github.com/Ardour/ardour/commit/db3e87a7e4576cfa8e999adc26d956150e3d9fa9

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9096 [ardour] bugs minor always 2022-11-16 10:54 2022-12-16 08:53
Reporter: cooltehno_bugs Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: urgent OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Bug: Set Range to Selected Regions - doesn't match the grid for 25 samples
Description: If you create a MIDI region 750 samples long (1/128 Note) - and then use the operation "Set Range to Selected Regions" (Edit > Select > Set Range to Selected Regions) - this makes range 25 samples shorter than the selection.
Tags:
Steps To Reproduce: 1. Make a new MIDI track.
2. Set the Grid Mode to "1/128 Note" and activate Snap.
3. Draw a new region 750 samples long (1/128 Note).
4. Maximize zoom to the drawn region.
5. Set the mouse to the Grab Mode and select the region.
6. Do the operation: Edit > Select > Set Range to Selected Regions - Ups!! - this makes the range 25 samples shorter than the selection.

(7. Check the length of the rest area of the region - just cut (Ctrl+X) the formed range and look into the properties of the rest part of the region)
Additional Information: A gif is attached
System Description
Attached Files: Set_Range_Selected_Region_bug.gif (514,112 bytes) 2022-11-16 10:54
https://tracker.ardour.org/file_download.php?file_id=4288&type=bug
Nothing_Set_Range_Selected_Region_bug.gif (78,174 bytes) 2022-11-16 11:02
https://tracker.ardour.org/file_download.php?file_id=4289&type=bug
gif

bbt-mismatch.png (54,292 bytes) 2022-11-23 23:14
https://tracker.ardour.org/file_download.php?file_id=4302&type=bug
png

range_consilidate_bug.gif (657,413 bytes) 2022-12-16 08:53
https://tracker.ardour.org/file_download.php?file_id=4329&type=bug
Notes
(0026895)
cooltehno_bugs   
2022-11-16 11:02   
May be this can help somehow: if we select the rest piece of the region and then repeat the "Set Range to Selected Regions" - this does not range anything!! Look at the next gif:
(0026936)
x42   
2022-11-23 23:14   
Further relevant info 48kHz sample-rate 120BPM (48000*120/60/128 = 750)

The "End" is 1 tick before the 128th note, and Length is also reported incorrectly (changing Edit > Position > NOT glue to bar/beats works around this).
The selection uses `selection->set (selection->regions.start_time(), selection->regions.end_time());` and hence from 1|1|0 to 1|1|59 (rather than 1|1|60)
(0027103)
cooltehno_bugs   
2022-12-16 08:53   

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9167 [ardour] bugs major always 2022-12-16 06:30 2022-12-16 06:30
Reporter: musew Platform: Arch  
Assigned To: OS: Linux  
Priority: high OS Version: (any)  
Status: new Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Multiple MIDI issues, difficult to separate
Description: This is Manjaro, with ardour 7.1-1.

Multiple issues relating to MIDI, plugins, cues:

1) Plugin interface does not work, especially in the "clips" sidebar - I swtich to ACE Fluidsynth so the drum based clips make sense - then I try and load an sf2 file, but the plugin interface (clicking the button right next to the plugin selector) is either:
    a) stuck on the previous plugin, ACE reasonable synth;
    b) not showing up at all; or
    c) showing the ACE Fluid Synth interface, but then when I load an sf2 file, the "program" slots do not populate with any patches in the dropdown menus; basically I'm stuck using the defaults because it's not showing the proper things to change.
    d) the ACE Fluid Synth programs finally populate but it's random and then if I want to load a new sf2 file, they may or may not decide to update.

     Right now I'm stuck with it not showing up at all.

     The same thing happens sometimes in the ACE Fluid Synth plugin on some of the regular tracks too. I'll load an sf2 and then the interface will not refresh to give me all the patches in the channels (it will be showing the previous sf2 file's patches, and I don't know how to get it to refresh). This was not an issue in Ardour 6.9.

2) I don't know if this is a plugin issue or a MIDI issue, but after drawing a couple of regions (notes only, no program changes or anything), and dragging things around a bit, it seems that there is something in one of the regions that causes the ACE Fluid Synth plugin to revert back to the default patch on the channel I was using. I did not draw any program changes, I don't even know how to do that, and I don't even know if that would effect the patch selection in the Channels in the plugin interface.

3) Cues and Tracks.
    Does a Cue existing in a certain track and then being in that cue's area in the timeline cause that track's actual content to be silent?

4) Inconsistent cue stopping.
    If I am in the "cue" view and I start a region/clip playing, how do I stop it? Do I click on the "play" button again? It seems to have worked once and only once.
    Is the proper way then to click on the "stop" square next to one of the empty cues? What to do then if all the cues are filled up?

Sorry to lump all this together, it all seems related somehow and it's a little hard to tell where one problem stops and the next begins, especially related to the plugins/MIDI.
Tags:
Steps To Reproduce: New session.
Create some MIDI tracks. Assign ACE Fluidsynth to the tracks.
Load an sf2 file in a couple of the tracks, and if you can get the interface to work, assign a patch to the first channel.
Make a couple of regions with MIDI data in them.
Drag the regions around a bit.
(at some point, the Fluidsynth reverts the first channel's patch to the default. Unclear if this is because of something in the MIDI data in the track getting corrupted, or if it's completely independent of that.)

Go to the "cue" view. In the Clips sidebar, choose ACE Fluid Synth. Click the button to the right of the Plugin selector dropdown. Either nothing will show up, or you will get the interface of the previous plugin (ACE Reasonable Synth) which just shows a message about how it is basic and has no options, or you will get ACE Fluid Synth interface, but then the patches won't update in the Channel menus so you won't be able to select anything.
Additional Information: I have videos of some of this happening, can provide them if helpful.
System Description
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9163 [ardour] bugs major always 2022-12-13 19:50 2022-12-14 14:42
Reporter: DonJaime Platform: Arch  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.2  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Converting session with tempo changes puts some MIDI regions in wrong position
Description: Opening some Ardour 6 sessions with variable tempo containing MIDI regions that do not start at the start of the session leads to the MIDI regions being misplaced on the timeline in Ardour 7.
Tags: meter
Steps To Reproduce: Open the attached session file in Ardour 7.2 (7.1 crashed). The piano, bass and drums regions are in the wrong place. Piano and bass should start in bar 6, drums in bar 13. In version 7 they start in bars 13 and 20, respectively. The short regions in the bass track in bars 11 14 and 31 end up in bars 18, 21 and 40.
Additional Information:
System Description
Attached Files: bug.zip (175,483 bytes) 2022-12-14 14:42
https://tracker.ardour.org/file_download.php?file_id=4326&type=bug
Notes
(0027084)
DonJaime   
2022-12-14 13:35   
not tempo change, meter changes
(0027086)
DonJaime   
2022-12-14 13:51   
Maybe uploading the file will work now...
(0027087)
DonJaime   
2022-12-14 13:53   
File upload failed again
(0027089)
DonJaime   
2022-12-14 14:42   

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9162 [ardour] bugs major always 2022-12-12 16:12 2022-12-14 13:48
Reporter: DonJaime Platform: Arch  
Assigned To: OS: Linux  
Priority: high OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Bars and beats and MIDI tracks ignore tempo changes
Description: I have several sessions with variable tempo containing MIDI and audio tracks. During playback the MIDI playback gets increasingly out of phase with the audio. The bars and beats grid still lines up with the MIDI notes, but neither of them seem to be taking the tempo changes seriously.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files: Good Night.ardour (856,728 bytes) 2022-12-14 13:48
https://tracker.ardour.org/file_download.php?file_id=4325&type=bug
Notes
(0027033)
DonJaime   
2022-12-12 16:15   
Session files
(0027056)
DonJaime   
2022-12-13 18:55   
Still happens in 7.2
(0027085)
DonJaime   
2022-12-14 13:48   

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9130 [ardour] bugs crash always 2022-11-29 23:17 2022-12-13 18:57
Reporter: MatthaeusHarris Platform: Microsoft  
Assigned To: OS: Windows  
Priority: normal OS Version: 10  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Windows crash on zoom
Description: warning: HEAP[Ardour.exe]:

warning: Heap block at 00000000395FF7B0 modified at 00000000396037C0 past requested size of 4000


Program received signal SIGTRAP, Trace/breakpoint trap.
[Switching to Thread 19496.0x5e4]
0x00007ffaee40a773 in ntdll!RtlRegisterSecureMemoryCacheCallback () from C:\WINDOWS\SYSTEM32\ntdll.dll
Tags: 7.1, crash, Windows
Steps To Reproduce: Zoom in past a certain level in the editor window with a certain region in view. Project file can be provided on request.
Additional Information:
System Description
Attached Files: Ardour-debug.log (107,934 bytes) 2022-11-29 23:17
https://tracker.ardour.org/file_download.php?file_id=4311&type=bug
Notes
(0026963)
x42   
2022-11-30 00:04   
The crash apparently happens when rendering the text for the ruler (Timecore, Bar/Beat, Tempo ...).

Since you say "Zoom in past a certain level in the editor window with a certain region in view."
Can you tell us what the time position is? Perhaps a screenshot of the top of the editor window (clocks, and visible rulers) before you zoom in?
(0027058)
MatthaeusHarris   
2022-12-13 18:57   
Removing the region from my project fixed the issue. If you still think it is the time position that's at fault, I can recreate the project and send a video of the crash, but from what you said it sounds like Ardour crashed trying to render a more detailed view of that region.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9161 [ardour] bugs crash always 2022-12-12 16:09 2022-12-13 18:56
Reporter: DonJaime Platform: Arch  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Crash when clicking on MIDI patch on track
Description: Some MIDI tracks are shown with patches at the start that are not attached to a MIDI region. Clicking on one of these causes a crash.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0027057)
DonJaime   
2022-12-13 18:56   
Still there in 7.2

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9118 [ardour] bugs minor always 2022-11-26 16:17 2022-12-12 07:57
Reporter: stefan-franz Platform: Ubuntu  
Assigned To: paul OS: Linux  
Priority: normal OS Version: (any)  
Status: assigned Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Copy and Paste midi notes brings only the note visible - but not playable
Description: Linux Mint 21 Cinamon

If i copy in the midi editor a midi note and paste it to the destination, the destination created note is only visible, but is not playing and can't not modify

2nd wish/bug: In overlaping notes.
https://manual.ardour.org/working-with-midi/handle-overlapping-notes/

My setting: replace both overlapping notes with a single note
1. Undo is not working, if 2 notes were combined
2. It works only, if i pull the 2nd note from right to left. If make the left note longer and pull it over the right, no combining. If i only move the left note to the right, no combining, but the right is cut to the duration of the first note.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0027031)
paul   
2022-12-12 00:27   
I cannot reproduce the first issue here.
(0027032)
stefan-franz   
2022-12-12 07:57   
Maybe it's solved now.
That problem is solved also - project plays right now.
https://discourse.ardour.org/t/ardour-plays-midi-track-wrong/108016

I make next time a video if it comes again.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9147 [ardour] other feature always 2022-12-06 14:24 2022-12-11 22:39
Reporter: stefan-franz Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Performance is going down or crashes if i load a SF2 file with more than 500GB in the ACE Fluid Synth
Description: If i load a SF2 File with more than about 500 GB Ardour crashes very fast. My device has 16 GB RAM - so Ardour could use it.
An i have a good machine, i7 processor.....in the year 2018 a very fast machine for that time.
System runs on a SSD - the data (Sound files and Sounds, Ardour Project, recording wavs etc) are on a harddrive.
Governor switched to "Performance" mode in Linux Mint 21 Cinnamon
Tags:
Steps To Reproduce: Load huge SF2
Additional Information:
System Description
Attached Files:
Notes
(0027004)
stefan-franz   
2022-12-09 05:50   
Additional Info about performance:
My system: Linux Mint 21 Cinnamon - with the CPUPower GUI i switch always before starting to "Performance"! (default is Powersafe).
My machine: i7 with 16 GB Ram. Linux is on the SSD, the project and used SF2 sounds, Samples for Speedrum Drum Sampler and Sounds for Redux are on a HDD. Same setup as in Cubase.

I have a small project running with about 10 instrument tracks (ACE Fluid Synth and Redux in midi tracks) and Speedrum. At the moment no Audio / Wav tracks. if i let my project playing an click on the tracks e.g. to adjust the level the gui and sometimes the sound runs not fluent.

I'm not a programmer - startet my work with Ardour to contribute the development as i do with Mixxx (DJ Software) -. i'm there a reporter for testing and finding bugs - and let me here write some thoughts - maybe it helps you to improve someting.
First: Comparing Virtual DJ /Win 10 - Mixxx Linux: Mixxx on Linux runs stable and more fluent as Virtual DJ in Win10. Neither my nextcloud client nor the browser brings Mixxx out of step. Virtual DJ had dropouts. So Linux Mint 21 works for me more stable and nearly double fast as Win10. 10 years old machines work now fluent.
So i think Ardour can also run as stable as Cubase or or even with more performance.

Some thoughts: I saw that Ardour is not using the full 16 GB Ram - maybe you can here make something, that Ardour uses the RAM.
The VST integration is not at the moment optimal - maybe that is the reason for performance problems.
Maybe you find a way, that ardour does not let itself be put out of step, if i click through the tracks in the edit mode.

Thanks for your work - after repairing some issues, i post Ardour on social media and make advertise to get more users. I want support linux - and help people to switch from the corrupt Apple or Microsoft group to Linux.
(0027016)
paul   
2022-12-11 05:30   
Fluidsynth is not Ardour, it is a plugin. It does not suprise me that loading a 500GB soundfont into Fluidsynth causes issues, but these are not issues that the Ardour team is likely to be able to address. Did you really mean 500GB or did you mean 500MB?

Please read https://ardour.org/debugging ardour for information about how to get useful backtraces when Ardour crashes.
(0027019)
stefan-franz   
2022-12-11 08:55   
Oh, my fault. I meant 500MB of course. A GM/GS font with about 300 single SF2's in one big SF2.
No i splited up this big files - was my workaround.

Your debugging site is not found.....
(0027020)
groudsquirrel   
2022-12-11 11:17   
I think the debugging page actually is https://ardour.org/debugging_ardour
(0027029)
paul   
2022-12-11 15:23   
Yeah, even with 500MB, the issue is with Fluidsynth, not with Ardour, so it's not something we're likely to be involved in fixing.
(0027030)
x42   
2022-12-11 22:39   
The CrisisGeneralMidi301.sf2 (1.6GB) works reliably here.
Note however that fluidsynth loads the complete file into RAM. For that to work reliably memory-locking needs to be set up.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9156 [ardour] bugs minor always 2022-12-10 17:38 2022-12-11 15:22
Reporter: stefan-franz Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: urgent OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: reopened  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Controller can since 7.1.244 not assigned to the top left buttons (rec, play, stop etc....)
Description: Since 7.1.244 i'm not able to assign the controller to the buttons of the top. Only a few buttons can assigned in the monitor section.
Strg+ middle mouse brings no function alert. The monitor volume works.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0027009)
stefan-franz   
2022-12-10 18:24   
Works correct after restart - something was crashed.
(0027010)
stefan-franz   
2022-12-10 18:28   
The error comes only, if i close a open project and opens another. No controller function at the whole top area (play, stop, rec.....)
(0027014)
paul   
2022-12-11 01:11   
MIDI learn control surface bindings are per-session. If you close a session and open another, they will not persist. This is intentional.

If you want persistent control, you should create a binding map and use that.
(0027025)
stefan-franz   
2022-12-11 12:42   
Hmmm.....in all my projects i had assigned my controller for Monitor Leve, and play, stop, rec (not more at the moment).

So if i close a project and load another project (in which the controller is assigned) i would expect as user, that it works. Do you mean that this is not working?
And the monitor level assign works. But not the complete buttons / functions at the toolbar on the top.

About creating a map as you mentioned here:
https://tracker.ardour.org/view.php?id=9144#c27015

It's looks very complicated....let me wish an improvement, that i can create a map with your great learning method:
1. learn the conrtoller to Ardour
2. Export the controller learnings as map
3. Offer the possiblity to manage the map setting and the installation with user friendly menu's

At the end a solution, that the controller settings not deleted, if a project is startet without a controller.
(0027028)
paul   
2022-12-11 15:22   
To repeat: MIDI Learn is a per-session thing, it does not persist across sessions.

As for the binding maps, lots of people have successfully created a binding map for their device. I agree that it would be nice to do MIDI Learn + Export binding map, but this is merely one more nice thing of many thousands of nice things that we haven't had time to do yet.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9157 [ardour] features tweak always 2022-12-11 13:16 2022-12-11 14:48
Reporter: stefan-franz Platform: Ubuntu  
Assigned To: x42 OS: Linux  
Priority: high OS Version: (any)  
Status: resolved Product Version: 7.1  
Product Build: Resolution: no change required  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Spartanic Gui of the ACE EQ
Description: Since the 7.1.269 the ACE EQ Gui as a spartanical GUI.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files: Spartanic Gui now for the EQ.jpg (54,522 bytes) 2022-12-11 13:16
https://tracker.ardour.org/file_download.php?file_id=4321&type=bug
jpg
Notes
(0027026)
x42   
2022-12-11 14:15   
Do you use the official binary? Those custom ACE* GUIs are proprietary (provided by Harrison).

Does the following file exist: /opt/Ardour-7.1.269/lib/LV2/Harrison.lv2/a-EQ_gui.so
(0027027)
stefan-franz   
2022-12-11 14:32   
My fault - i download every day the actual nightly build - and today i didn't say yes for "install harrison plugins"
Now all works.
Issue is fixed by user....;-)

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9159 [ardour] bugs minor have not tried 2022-12-11 14:37 2022-12-11 14:38
Reporter: HarryR Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Fitting to the Editor Window adds tracks
Description: Situation:

There are several tracks.

I want to fit them to the Editor Window.

After fitting the last track is increased.

In my example I have seven tracks (including master).
After fiting the last track exits seven times

Maybe it's justan "optical" thing, I didn't test this.
Tags:
Steps To Reproduce: Look above
Additional Information:
System Description
Attached Files: Before-Fitting.png (30,353 bytes) 2022-12-11 14:37
https://tracker.ardour.org/file_download.php?file_id=4322&type=bug
png

After fitting.png (34,033 bytes) 2022-12-11 14:37
https://tracker.ardour.org/file_download.php?file_id=4323&type=bug
png
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9158 [ardour] features minor have not tried 2022-12-11 14:30 2022-12-11 14:30
Reporter: gunterkoenigsmann Platform: GNU  
Assigned To: OS: Linux  
Priority: low OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ability to set the default template
Description: I don't make music so I have no use for the time signature and tempo meter, but perhaps for the "samples" one. I can even create a template with these settings - but there currently is no way to make ardour use that template automatically by default => a low-prio feature request.
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:
8344 [ardour] bugs minor always 2020-07-31 10:44 2022-12-11 14:21
Reporter: apoorv569 Platform: Arch Linux  
Assigned To: paul OS: GNU/Linux  
Priority: normal OS Version: Arch Linux  
Status: resolved Product Version: 6.2  
Product Build: Resolution: no change required  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Unable to launch Ardour.
Description: I was working on a project a day before yesterday, and everything was fine, but today when I tried to open Ardour, nothing opened, tried a couple of more time and nothing showed up. So I tried opening from a terminal to if it outputs some error, it gave some warning about gtk murrine engine not found, so I installed it, and then I tried again and it gets stuck here
```
[apoorv@Apoorv-PC ~]$ ardour6
Ardour6.2.0 (built using 6.2 and GCC version 10.1.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/apoorv/.config/ardour6/config
Ardour: [INFO]: CPU vendor: GenuineIntel
Ardour: [INFO]: AVX-capable processor
Ardour: [INFO]: CPU brand: Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
Ardour: [INFO]: Using SSE optimized routines
Ardour: [INFO]: Loading plugin meta data file /usr/share/ardour6/plugin_metadata/plugin_tags
Ardour: [INFO]: Loading default ui configuration file /etc/ardour6/default_ui_config
Ardour: [INFO]: Loading user ui configuration file /home/apoorv/.config/ardour6/ui_config
Ardour: [INFO]: Loading 449 MIDI patches from /usr/share/ardour6/patchfiles
Ardour: [INFO]: Loading color file /usr/share/ardour6/themes/caineville-ardour.colors
```
I tried waiting for about 15-20 mins nothing happens. I tried removing Ardour and reinstalling again, no luck. After a long time trying to fix it, I gave up and formatted my drive and reinstalled my Arch Installation, after finishing installation, I installed Ardour and tried running it ran fine, but after installing all the other packages that I use on my PC, I rebooted and tried running Ardour, again nothing happens, tried running through terminal still stuck on the same output as I posted above.

One thing if I try to run it as root, it does open.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0024872)
x42   
2020-07-31 12:27   
That smells like a duplicate of https://tracker.ardour.org/view.php?id=5605#c18109 (your user's desktop theme defines colors and conflicts)

try
   export GTK2_RC_FILES=/usr/share/themes/Adwaita/gtk-2.0/gtkrc
or maybe
   export GTK2_RC_FILES=/nonexistent
before starting Ardour
(0024873)
apoorv569   
2020-07-31 12:44   
@x42 I tried running both commands, no luck. Still stays stuck there in the terminal.
(0024876)
apoorv569   
2020-07-31 13:53   
@x42 Well, I tried changing my GTK theme to Adwaita, its opening now. Does it means I won't be able use the theme I want?
(0027013)
paul   
2022-12-11 01:10   
Ardour doesn't really use your system theme anyway.
(0027021)
groudsquirrel   
2022-12-11 11:21   
I posted another duplicate of this in the forum: https://discourse.ardour.org/t/ardour-7-gui-does-not-show-up-with-kde-plasma-breeze-theme/108025
Maybe my workaround helps you.
(0027022)
groudsquirrel   
2022-12-11 11:30   
Ah, GTK2_RC_FILES=/nonexistent works as well. It's probably the better workaround.
(0027023)
groudsquirrel   
2022-12-11 11:39   
One can also put the workaround in ardour's .desktop file:
`Exec=ardour7` -> `Exec=bash -c 'export GTK2_RC_FILES=/nonexistent && ardour7'`

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9155 [ardour] other tweak sometimes 2022-12-09 13:06 2022-12-11 12:29
Reporter: stefan-franz Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Erorr messages - only to look if something is important
Description: Hello, at the top right, there is in Ardour an error signal - opening the window brings that in red.
Ardour works very well - i thought it helps the dev's

2022-12-09T13:36:37 [ERROR]: g_log: gtk_box_pack: assertion 'child->parent == NULL' failed
2022-12-09T13:36:43 [ERROR]: g_log: gtk_box_pack: assertion 'child->parent == NULL' failed
2022-12-09T13:37:12 [ERROR]: g_log: gtk_box_pack: assertion 'child->parent == NULL' failed
2022-12-09T13:37:18 [ERROR]: g_log: gtk_box_pack: assertion 'child->parent == NULL' failed
2022-12-09T13:37:42 [ERROR]: g_log: gtk_box_pack: assertion 'child->parent == NULL' failed
2022-12-09T13:38:05 [ERROR]: g_log: gtk_box_pack: assertion 'child->parent == NULL' failed
2022-12-09T13:39:17 [ERROR]: g_log: gtk_box_pack: assertion 'child->parent == NULL' failed
2022-12-09T13:39:20 [ERROR]: g_log: gtk_box_pack: assertion 'child->parent == NULL' failed
2022-12-09T13:59:56 [ERROR]: g_log: gtk_box_pack: assertion 'child->parent == NULL' failed
2022-12-09T13:59:58 [ERROR]: g_log: gtk_box_pack: assertion 'child->parent == NULL' failed
2022-12-09T14:00:02 [ERROR]: g_log: gtk_box_pack: assertion 'child->parent == NULL' failed
2022-12-09T14:00:05 [ERROR]: g_log: gtk_box_pack: assertion 'child->parent == NULL' failed
2022-12-09T14:00:07 [ERROR]: g_log: gtk_box_pack: assertion 'child->parent == NULL' failed
2022-12-09T14:00:09 [ERROR]: g_log: gtk_box_pack: assertion 'child->parent == NULL' failed
2022-12-09T14:02:40 [ERROR]: g_log: gtk_box_pack: assertion 'child->parent == NULL' failed
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0027017)
paul   
2022-12-11 05:31   
(Last edited: 2022-12-11 05:31)
In order to do anything about those messages, We would need to know what you were doing when those messages were generated.
(0027024)
stefan-franz   
2022-12-11 12:29   
I startet now the 7.1.269 and now i have such log: (Linux Mint 21 Cinnamon)

2022-12-11T13:22:23 [INFO]: AlsaAudioBackend: adjusted output channel count to match device.
2022-12-11T13:22:23 [INFO]: AlsaAudioBackend: adjusted input channel count to match device.
2022-12-11T13:22:23 [INFO]: Scanning folders for bundled LV2s: /opt/Ardour-7.1.269-dbg/lib/LV2
2022-12-11T13:22:25 [ERROR]: AudioClock::sample_duration_from_bbt_string() called with BBT mode but without session!
2022-12-11T13:22:26 [INFO]: harvid version: 900
2022-12-11T13:22:26 [ERROR]: AudioClock::sample_duration_from_bbt_string() called with BBT mode but without session!
2022-12-11T13:22:26 [ERROR]: AudioClock::sample_duration_from_bbt_string() called with BBT mode but without session!
2022-12-11T13:22:26 [ERROR]: AudioClock::sample_duration_from_bbt_string() called with BBT mode but without session!
2022-12-11T13:22:26 [ERROR]: AudioClock::sample_duration_from_bbt_string() called with BBT mode but without session!
2022-12-11T13:22:26 [ERROR]: AudioClock::sample_duration_from_bbt_string() called with BBT mode but without session!
2022-12-11T13:22:26 [INFO]: Lade Menüs von /opt/Ardour-7.1.269-dbg/etc/ardour.menus
2022-12-11T13:22:27 [INFO]: LV2: update midnam for plugin 'General MIDI Synth'
2022-12-11T13:22:28 [WARNING]: Ignored automation data for non-automatable parameter
Ignored automation data for non-automatable parameter
Ignored automation data for non-automatable parameter
Ignored automation data for non-automatable parameter
Ignored automation data for non-automatable parameter
Ignored automation data for non-automatable parameter
.....
-- 100 of same lines as above or below --
..........
Ignored automation data for non-automatable parameter
Ignored automation data for non-automatable parameter
Aux-Send ID 2 ist offenbar schon in Gebrauch
2022-12-11T13:22:28 [WARNING]: Aux-Send ID 2 ist offenbar schon in Gebrauch
2022-12-11T13:22:28 [WARNING]: Aux-Send ID 2 ist offenbar schon in Gebrauch
2022-12-11T13:22:30 [INFO]: LV2: update midnam for plugin 'ACE Fluid Synth'
2022-12-11T13:22:34 [INFO]: LV2: update midnam for plugin 'ACE Fluid Synth'
2022-12-11T13:22:34 [INFO]: LV2: update midnam for plugin 'ACE Fluid Synth'
2022-12-11T13:22:34 [ERROR]: ardour::connect: ungültiger Quellport (ardour:)
2022-12-11T13:22:35 [ERROR]: AudioClock::sample_duration_from_bbt_string() called with BBT mode but without session!
2022-12-11T13:22:35 [ERROR]: AudioClock::sample_duration_from_bbt_string() called with BBT mode but without session!
2022-12-11T13:22:35 [ERROR]: AudioClock::sample_duration_from_bbt_string() called with BBT mode but without session!
2022-12-11T13:22:35 [ERROR]: AudioClock::sample_duration_from_bbt_string() called with BBT mode but without session!
2022-12-11T13:22:35 [ERROR]: AudioClock::sample_duration_from_bbt_string() called with BBT mode but without session!
2022-12-11T13:22:35 [ERROR]: AudioClock::sample_duration_from_bbt_string() called with BBT mode but without session!
2022-12-11T13:22:35 [ERROR]: AudioClock::sample_duration_from_bbt_string() called with BBT mode but without session!
2022-12-11T13:22:35 [ERROR]: AudioClock::sample_duration_from_bbt_string() called with BBT mode but without session!
2022-12-11T13:22:35 [ERROR]: AudioClock::sample_duration_from_bbt_string() called with BBT mode but without session!
2022-12-11T13:22:35 [ERROR]: AudioClock::sample_duration_from_bbt_string() called with BBT mode but without session!
2022-12-11T13:22:35 [ERROR]: AudioClock::sample_duration_from_bbt_string() called with BBT mode but without session!
2022-12-11T13:22:35 [ERROR]: AudioClock::sample_duration_from_bbt_string() called with BBT mode but without session!
2022-12-11T13:22:35 [ERROR]: AudioClock::sample_duration_from_bbt_string() called with BBT mode but without session!
2022-12-11T13:22:35 [INFO]: Lade Benutzer-UI-Skriptdatei /home/stefan/.config/ardour7/ui_scripts
2022-12-11T13:22:35 [INFO]: Entferne MIDI-Patch-Datei custom:urn:ardour:a-fluidsynth:0x557af72b1130
2022-12-11T13:22:35 [INFO]: LV2: update midnam for plugin 'ACE Fluid Synth'
2022-12-11T13:22:35 [INFO]: Entferne MIDI-Patch-Datei custom:urn:ardour:a-fluidsynth:0x557ad4d85070
2022-12-11T13:22:36 [INFO]: LV2: update midnam for plugin 'ACE Fluid Synth'
2022-12-11T13:22:36 [INFO]: Entferne MIDI-Patch-Datei custom:urn:ardour:a-fluidsynth:0x557af80859e0
2022-12-11T13:22:36 [INFO]: LV2: update midnam for plugin 'ACE Fluid Synth'
2022-12-11T13:22:36 [INFO]: Lade Plugin-Reihenfolge-Datei /home/stefan/.config/ardour7/plugin_metadata/plugin_order
2022-12-11T13:22:40 [INFO]: Loading history from /home/stefan/WinD/15-Ardour/Ardour-Projekte/100 Party-DJ-Stefan/Aber bitte mit Sahne - Master/Aber bitte mit Sahne 05/Aber bitte mit Sahne 05.history
2022-12-11T13:24:08 [WARNING]: g_log: Input method gtk-im-context-simple should not use GTK's translation domain gtk20

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9138 [ardour] bugs major always 2022-12-03 16:56 2022-12-11 05:33
Reporter: plehal Platform: Redhat  
Assigned To: paul OS: Linux  
Priority: normal OS Version: (any)  
Status: assigned Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: tempo for tracks created using cue window changes when exporting the sound file, but plays fine during the session
Description: Any clips used in track with cue window do not retain their tempo (adjusted using clip Stretch options) when exporting the final sound file. Track plays just fine in the session though. This defeats the purpose of stretch functionality.
Tags:
Steps To Reproduce: Use a clip with a different bpm than the track and use stretch function to adjust the tempo of clip. Record the played sound and export the sound file. The recorded file will be different tempo than exported file.
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:
9136 [ardour] bugs minor always 2022-12-03 14:05 2022-12-11 05:32
Reporter: Pat Platform: Debian GNU  
Assigned To: paul OS: Linux  
Priority: normal OS Version: (any)  
Status: resolved Product Version: 7.1  
Product Build: Resolution: no change required  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Midi track directed to bus with synth dont play notes
Description: Hello,

The bus track contains fluidsynth with a gm bank connected.
In the midi track, I can hear notes clicking on the pianoroll ( editor view) and I can draw notes.
But when i start playback i cannot here the notes on the midi track.

Mbr Pat
Tags:
Steps To Reproduce: 1. Create a Midi bus track. insert fluidsynth and a gm bank as plugin on the midi bus track.
2. Add a midi track and direct it to the midi bus. Connect to the same play group.
3. Add some notes on the midi track
4. Try playback.
Additional Information:
System Description
Attached Files:
Notes
(0026971)
Pat   
2022-12-03 17:15   
Hi,

Noticed that the input monitor was activated on the midi track, which did cause this behavior.
If i disabled the input monitor in the editor mixer, the notes playback started to work on the midi track.

So this was not a bug, sorry and can be removed.
(0027018)
paul   
2022-12-11 05:32   
see notes

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9144 [ardour] bugs minor always 2022-12-05 05:28 2022-12-11 01:13
Reporter: stefan-franz Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Controller Setup deleted after starting a project one times without controller (Behringer X-Touch Mini)
Description: Linux Mint 21 Cinnamon
After starting a project (which worked before fine with the controller) without a connected Controller -and restart with connected controller - the project deleted the controller setting.
I had to reconnect manually in the global options, and the complete programming now i must do again.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0027015)
paul   
2022-12-11 01:13   
you should be creating a binding map that persists on disk and can be re-used, edited, copied etc.

https://manual.ardour.org/using-control-surfaces/generic-midi/midi-binding-maps/

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8883 [ardour] bugs minor random 2022-02-25 21:21 2022-12-11 01:09
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
png

ardourbug2.png (156,858 bytes) 2022-02-25 21:21
https://tracker.ardour.org/file_download.php?file_id=4159&type=bug
png

ardourbug3.png (168,086 bytes) 2022-02-25 21:21
https://tracker.ardour.org/file_download.php?file_id=4160&type=bug
png

ardourbug4.png (114,309 bytes) 2022-02-25 21:21
https://tracker.ardour.org/file_download.php?file_id=4161&type=bug
png

Screenshot_20220326_085305.png (33,355 bytes) 2022-03-26 06:56
https://tracker.ardour.org/file_download.php?file_id=4172&type=bug
png
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.
(0027012)
paul   
2022-12-11 01:09   
I believe that this has already been fixed.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9145 [ardour] bugs minor always 2022-12-05 16:51 2022-12-10 22:00
Reporter: GMaq Platform: Debian GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: ~/.vst should be a default PATH for Linux VST 2 Plugins
Description: All other Plugin types (LV2, VST3, CLAP) have a corresponding folder in the Users home that Ardour scans on first run by default Linux VST2 should be too. Most 3rd Party Vendors (Uhe as an example) install to ~/.vst.. Yabridge by default places it's shared object files for Windows VST 2 Plugins in ~/.vst/yabridge. It is accepted common practice. Ardour's convention of an LXVST path has not gained universal acceptance and even Repository Packages of LinuxVST Packages are a muddle of /usr/lib/vst and /usr/lib/lxvst with the majority favouring the more universal /usr/lib/vst.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0026983)
GMaq   
2022-12-05 17:00   
I had to post the above quickly before a timeout killed it again... Further to that the missing default ~/.vst path is a pretty significant hiccup for new Users trying Ardour for the first time with their own LinuxVST2 Plugins installed and getting missed while all other Plugin formats in the same location get detected.
(0026985)
paul   
2022-12-05 21:56   
VST2 does not have any default installation location - Steinberg left it unspecified. As you note, packaged LXVST2 plugins end up in various other system folders.
(0026987)
GMaq   
2022-12-06 16:13   
Soooo, since it's unspecified and ~./vst is known to work in daily use in real world situations, what would be the harm in adding it? While I would agree that Repository packages favour system-wide destinations that are in Ardour's default scan locations most other sources of common 3rd party Plugin either install to ~/.vst or recommend that as the install target. Distributions are quickly losing the ability to keep up with the sheer volume of new Audio Plugins for Linux and there are more and more commercial choices that will never be included in a Repository system and will be placed in the home folder. While ~/.vst is not 'specified' neither is ~/.lxvst or any of the other system-wide locations, yet they work anyway as ~/.vst does. Its really more about where the DAW will look than what the Plugin standard specifies in this case anyway so what's the harm in adding another common location when none of them are technically specified.
(0027007)
GMaq   
2022-12-09 22:27   
*Added note, with recent holiday Plugin sales I purchased Apisonic Speedrum and AudioThing's Bubble Thing and Dials, both of these are crossplatform VST2, VST3 (and CLAP) Plugins and just as an example for 2 random Plugins I happened to come across this week AudioThings's included installer script installs to ~/.vst, .vst3, and .clap and Speedrum also expects to be copied to ~/.vst and/or .vst3. If you want more examples than U-he, Apisonic, AudioThing I can easily find them and am happy to provide them Whether within the specification or not ~/.vst is a valid and indeed expected location for LinuxVST2 Plugins to be placed, for Ardour to overlook this is a source for potential confusion.. On the other hand Reaper ONLY looks in ~/.vst and .vst3 and does not search system-wide folders without modification, even they use it as their only valid location to search.. In both cases lxvst is not a thing that is mentioned anywhere other than in Ardour and a small number of Plugin developers that use or test with Ardour.
(0027011)
Daniele1971   
2022-12-10 22:00   
I agree with GMaq, even if not in the vst2 spec, it's a de facto standard for third parts plugins.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9111 [ardour] bugs minor always 2022-11-21 15:03 2022-12-09 16:28
Reporter: Pat Platform: Debian GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Menu Edit / Analyze always greyed out
Description: But I can activate Analyze Loudness and Analys Spectral using Right click on an audio file.

I tried this with the imageapp version 7.1. for Mx-Linux and with the demo binary version 7.1 for Windows.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0026942)
x42   
2022-11-25 02:11   
Those edit menu actions applies to selected Range (not Region).
(0026944)
Pat   
2022-11-25 09:44   
Ok x42,

Then this is not a bug, but from a usability point of view its not the best solution either.
In my opinion, it would be more intuitive if you have a generic submenu Analysis, which applies to both (greyed out when it doesn't apply).

Mbr Patrik
(0026992)
paul   
2022-12-08 00:53   
We don't have a region-based analysis action at present, so making this change now would not make sense.
(0026999)
Pat   
2022-12-08 08:13   
Hello,

Then let me explain better

In 7.1 i can select an audio object and then from the region menu one can select directly loudness analysis and spectral analysis which is then wrong. But from a usability point of view they could be in edit / analysis sub menu in addition to the case of an active range.

Then it would not need to be not duplicated to the region menu which is the case now.

Also since the analysis has a submenu which can be greyed out in the situations it do not apply.

mbr Patrik
(0027005)
Pat   
2022-12-09 13:15   
Even simpler explanation on a really minor thing

1. Today audio objects work for loudness analysis and spectral analysis
2. But from usability point I suggest they are only in edit / analysis submenu and not in region menu (as you write that they do not work)
3. And in edit / analysis submenu can we se for audio objects and range which work
4. Edit / Analysis has a submenu which can be greyed out in the situations when it don't work

My best regards

- Patrik
(0027006)
x42   
2022-12-09 16:28   
I do agree that it is confusing to have

 * Region > Loudness Analysis...
 * Region > Spectral Analysis...

and for Ranges:
 * Edit > Analyze > Spectral Analysis
 * Edit > Analyze > Loudness Analysis
 * Edit > Analyze > Loudness Assistant

They are however different operations.
I think we may have to add a "Range" menu at some point.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9115 [ardour] bugs minor always 2022-11-26 03:41 2022-12-08 17:54
Reporter: whanake Platform: Arch  
Assigned To: paul OS: Linux  
Priority: normal OS Version: (any)  
Status: assigned Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Colour of new tracks do not follow stripable-color-palette
Description: Every time a new track in Ardour is created, it gets assigned a random colour. This colour is supposed to be chosen from the 'stripable-color-palette' line in '~/.config/ardour7/ui_config'. However, changing the palette in ui_config does nothing and the colour assigned to new tracks is seemingly random.
Tags:
Steps To Reproduce: Open any existing Ardour session, or create a new one, then start adding tracks.
Additional Information: The colours seem to be assigned in the same order across sessions, but there is no repeating pattern upon initial investigation.
System Description
Attached Files:
Notes
(0026995)
paul   
2022-12-08 01:05   
"This colour is supposed to be chosen from the 'stripable-color-palette' line" ... looking into this, but can find no evidence that this was ever true. Do you have any?
(0026996)
paul   
2022-12-08 04:28   
there is a fix for this (of a sort) now in ardour master branch (git) Would appreciate feedback on how this works for you
(0026997)
whanake   
2022-12-08 04:52   
No, I don't have any evidence, but x42 said he thought this used to be the case in the IRC channel. Either way, would be nice to have the option to set default colours. I'll try compiling from master now and give feedback in a few hours.
(0026998)
whanake   
2022-12-08 07:53   
I have tried the master branch, and I appreciate the colour addition, thank you. Although I wish the colours were added in a sequential order rather than each track randomly selecting a colour from the palette. It looks like they have slight brightness variations too, which is especially prominent when all palette colours are set to the same value. Some more consistency would be nice :)
(0027001)
paul   
2022-12-08 17:54   
the colors are not used more than once, which is why you see the luminance differences after one cycle through the palette

sequential ordering now in place.

finally, we need some way to edit the palette :)

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9120 [ardour] bugs minor always 2022-11-27 12:07 2022-12-07 05:54
Reporter: stefan-franz Platform: Ubuntu  
Assigned To: paul OS: Linux  
Priority: normal OS Version: (any)  
Status: resolved Product Version: 7.1  
Product Build: Resolution: no change required  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ranges - 1st not displayed - and not deleteable
Description: I made 2 Ranges, but the 1st is not displayed. And i saw, it's not deleteable.
Tags:
Steps To Reproduce:
Additional Information: 2 improvement-Ideas in Ranges:
If the regions were continuous and colors could be assigned, I would like it very much.

The manual time entry in the list of regions is very cumbersome - a direct click on the respective number you want to change would be great.
System Description
Attached Files: Bereiche.jpg (99,057 bytes) 2022-11-27 12:07
https://tracker.ardour.org/file_download.php?file_id=4306&type=bug
jpg
Notes
(0026982)
stefan-franz   
2022-12-05 14:13   
Sorry, my fault. It's the full Project Range an not deleteable. No Bug.
(0026989)
paul   
2022-12-07 05:54   
see notes

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9143 [ardour] features feature always 2022-12-04 22:03 2022-12-06 23:31
Reporter: nonsequitarian Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Attach description / notes to session snapshots
Description: Over the course of creating a song, I like to use snapshots to capture the state at various points of the process. I also often create a snapshot thread to explore a particular idea that may or may not come to fruition. Right now the only metadata a snapshot has is its name, which usually isn't high fidelity enough for the context I want to include. It'd be delightful to be able to attach a text note to a snapshot so I can more easily keep track of which snapshot is which, especially when returning to a track after a few weeks or more of not working on it.
Tags: snapshots
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0026988)
x42   
2022-12-06 23:31   
You could use Ardour Menu > Session > Metadata > Description

The main downside is that it is only visible there (not in the recent session dialog, nor the snapshot list in the editor's sidebar).
The description is also inhered by new snapshots (which may be fine).

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9150 [ardour] bugs major always 2022-12-06 19:27 2022-12-06 19:27
Reporter: stefan-franz Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: After adding Redux no further Midi Tracks can added
Description: After making a new midi track with Redux https://www.renoise.com/products/redux Output: Strict I/O - next Window "Automatic" (because i want only in Stereo Mode)
i can't add a further Midi track. The dialogue opens, but i can not select an Instrument - the selection button is greyed out.
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:
9149 [ardour] bugs major always 2022-12-06 17:17 2022-12-06 17:17
Reporter: Pat Platform: GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Comment editor content gets deleted.
Description: Ardour can store comments per track. ( I use it to store instrumental information, but sometimes also lyrics for the singer.)

When switching focus to another track, the content is invisible, but when focusing on the original track it does not re-appear.

The information should be shown again when refocusing on that track.

Mbr Patrik

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:
9148 [ardour] bugs minor always 2022-12-06 15:15 2022-12-06 15:15
Reporter: Xansta Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Import of Protools session shows track list but no audio content
Description: I tried to import a Protools session back in the March/April 2022 time frame unsuccessfully. The problem was worked on and a fix was incorporated and scheduled for the next release. I was given an opportunity to try the fix myself, but I would need to compile Ardour myself. I made an effort to compile, but was unsuccessful. Now that there's a new release, I tried to import the Protools file again. The import ran to completion. I can see the tracks listed. The tracks seem devoid of any audio content. I picked a couple of the tracks and raise the gain, but that did not do anything either.

I'm running Lubuntu 18.04.6 LTS
Bionic
Tags:
Steps To Reproduce: Launch Ardour
Create a new session by clicking the New Session button in the Session Setup window
Name the session and click the Open button in the Session Setup window
Current settings in the Audio/MIDI Setup:
Audio System: ALSA
Input Device: HDA Intel PCH
Output Device: HDA Intel PCH
Sample rate: 44.1 kHz
Buffer size: 1024 samples (23.2 ms)
Periods: 2
Record monitoring handled by: Audio Hardware
Click the Start button in the Audio/MIDI Setup window
Note: I sometimes connect to a USB input box where the Audio/MIDI settings are different
Session > Import PT session
Navigate to the file on the hard drive (Session 015 - Mar 26, 2022.ptx)
Click the Import button in the Import PT Session window
I see the P...rt window while the import occurs and the dialog box with the message "PT import completed! See log for specifics" where I click the OK button.
Additional Information: Out of curiosity, I looked at the log file. I see these messages:
2022-12-06T09:04:21 [WARNING] PT Import: MISSING `/home/skaraan/Downloads/Fade Files/Drums_01.wav, inserting ref to missing source
[...]
2022-12-06T09:04:21 [WARNING] Failed to load one or more of the audio files for PT import, see above list

There's a line for a fade file for each of the tracks. It looks like I need to go back to the original recorder and ask for those files . I only just now noticed these messages. I appreciate you reading this far. I also appreciate the information in the log file. I should have read that sooner. Sorry about that.
System Description
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9140 [ardour] bugs crash always 2022-12-04 10:34 2022-12-05 21:57
Reporter: Hanry Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: immediate OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: after finishing recording ardour crashes, happens with mic recordings and MIDI
Description: every time I'm recording at one point it crashes right after finishing a take. if it doesn't I save it for when it will. sometimes I get an error like "BOOST : terminate called after throwing an instance of 'boost::wrapexcept<std::out_of_range>"
most of the times it gives an error like this ""Thread 61 "butler" received signal SIGABRT, Aborted"" it always happens right as I press stop or space bar after recording a take. doesn't matter if its MIDI or Mic or a direct instrument.
Tags: 7.1, butler, crash after a take
Steps To Reproduce: open ardour, record a few takes longer than 3-4 min. it will crash at some point. sometimes on the first or second sometimes on the 8th take.
Additional Information: I compiled it myself from source
System Description
Attached Files: ardour71_errorlog (2,667 bytes) 2022-12-04 10:34
https://tracker.ardour.org/file_download.php?file_id=4316&type=bug
Notes
(0026986)
paul   
2022-12-05 21:57   
https://ardour.org/debugging_ardour

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9135 [ardour] bugs crash have not tried 2022-12-02 13:37 2022-12-04 14:13
Reporter: Login4Jay Platform: Debian GNU  
Assigned To: OS: Linux  
Priority: urgent OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ardour Session contains 140 MB of automation data and crashes
Description: i There,

I used fader automation and the whole session is not working anymore, because it got really slow and crashes all the time. I first thought it is the same bug as @tired_eyes reported here https://tracker.ardour.org/view.php?id=9117 ("Automation: combining two [midi] regions create an excessive amount of automation points"). But i have the problem with audio regions and they are not combined. Just huge amount of automation data.

When i load the Session, it takes about one minute which is very long in comparison to other projects i worked on. While loading i see all my 8 GB RAM filling up and also the Swap going up and my system is showing me the note, that ardour is not responding. Once i see the editor view, the session is behaving very slow and playback starts with a delay of about 5 seconds. Sometimes i got notified that my storage (SSD) isn’t quick enough for playing back simple Audio tracks (about 10 Tracks with Flac files).

I realized, that the .ardour file is about 140MB huge. Once i deleted the Track with the Fader-Automation, the session is only 1MB. That means, there was is a ton of automation data in there. That surprises me, because the fader automation (that i recorded) is only for a region of about one minute.
What i find strange, that in the session folder, there is no .history file, but a .history.bak file of 400MB (which you can see in the screenshot). That .history.bak file is from the point of the screenshot on only automation data. I never deleted my .history file (or can it go away with a new snapshot?) and i wonder where it’s gone.
I can’t even show my fader automation data, because ardour is struggling to zoom in.

Besides ot that: Thank you guys for the wonderful DAW that Ardour is. I’m using it for years now and never wanna change!
Tags: 7.1, fader automation, track freeze
Steps To Reproduce:
Additional Information: Ubuntu 22.04.01 LTS
Lenovo ThinkPad T450s
Intel® Core™ i7-5600U CPU @ 2.60GHz × 4
8GB RAM
System Description
Attached Files: inside_the_history.bak-file.png (247,172 bytes) 2022-12-02 13:37
https://tracker.ardour.org/file_download.php?file_id=4314&type=bug
png
Notes
(0026975)
x42   
2022-12-04 10:39   
How did you create that automation-data? have you recorded this fader automation with a control surface?
There was a bug in Ardour7: automation thinning did not work correctly. Usually Ardour removes dense automation points at the end of each write pass. Fixed now in 7.1-207.

If that session is important to you, there are a few ways to recover it:

Either just delete the Automation in the .ardour session file using a text editor.

If it is fader automation, you can use a Lua script that comes with Ardour to remove dense events: Open Window > Scripting . Load script "Snippets > Thin Fader Automation", select the track(s) that have fader automation, press "Run" (in versions prior to 7.1-207. change line 30 from al:thin (50) to al:thin(128000).

You can also safely remove the .history file (that is undo/redo data).
(0026978)
Login4Jay   
2022-12-04 14:13   
Thanks for the response!
I have recorded the fader automation just with ardour by hand with the write mode. Control surface? I didn’t use any extra software or hardware (fader) to do this. So nothing special.

Thanks for the recovery tipps. Luckily i could restore from backup but good to know for the (hopefully not) next time. I’ll try to open my "corrupted" session with Ardour 7.2 when it’s out. In the moment i unfortunately don’t have time to learn how to use lua scripts or to install nightly builds of ardour.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9141 [ardour] bugs minor random 2022-12-04 13:16 2022-12-04 13:19
Reporter: stefan-franz Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Track move by strg+up doesn't work sometimes
Description: I made new tracks and then the shortcut combination "strg+up" doesn't work anymore. It works over the menu "track / selected tracks move up"
Tags:
Steps To Reproduce: Adding new tracks - can't reproduce it...
Additional Information:
System Description
Attached Files:
Notes
(0026977)
stefan-franz   
2022-12-04 13:19   
Found out: Adding a e.g. ACE Eq in any track bringts the shortcut function back

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9139 [ardour] features feature N/A 2022-12-03 19:42 2022-12-03 19:42
Reporter: al f Platform: all  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Feature request: Clip preview: loop part of the session, then test clips in sync with the loop
Description: The clip launcher works well when starting with clips and building from there, but sometimes I'd like to do it the other way 'round: starting with existing material and searching for fitting clips.

In that scenario, it would be awesome to be able to loop some part of the session and when browsing clips have them play back in sync with the loop. The start of the clip should start to play when the loop starts from the beginning.

The corresponding text in the manual now is "When playing a clip, Ardour will automatically pause the transport and resume playback when the clip playback is done".

If this feature is implemented it could change to something like "When pre-viewing clips, if Ardour is already playing a loop, the clip playback will be syncronised with the loop".

Tags: cue, loop
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:
9137 [ardour] bugs minor always 2022-12-03 14:15 2022-12-03 18:39
Reporter: Pat Platform: Debian GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Lua script ( at least for voice activation) lacks needed information
Description: The headers which is needed for saving the Lua script is not available, at least not for voice activation Lua plugin.
Information is also needed on where to put ( paste) the script in Ardour.
So the information should be

Mbr Patrik
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0026970)
x42   
2022-12-03 16:04   
Can you elaborate? I have just tested and works here.
https://github.com/Ardour/ardour/blob/master/share/scripts/voice_activate.lua
(0026972)
Pat   
2022-12-03 17:20   
Hello,

Yes.

I copied that script to Ardour Window menu / Scripting.
It does run ( says OK)
But when i try to save I get the following:
Missing script header.
The script requires an '{ardour}' info table and a 'factory' function.
(0026973)
x42   
2022-12-03 17:27   
There should be no need to copy it, Ardour comes with that script.
Here it is in C:\Program FIles\Ardour7\share\ardour7\scripts\

> I copied that script to Ardour Window menu / Scripting.

AHA. That console is for GUI script (EditorAction). It is not meant for DSP scripts with run in realtime-context in the mixer.

You load the voice-activate script like a normal plugin in the Mixer Window.
(0026974)
Pat   
2022-12-03 18:39   
Hello,

Ok that clear. I did actually look in the Plugin manager, where it is not, therefore it went wrong.

This plugin is indeed visible only from the mixer. Could it show up also in the Plugin manager?

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9133 [ardour] bugs minor always 2022-12-01 17:15 2022-12-01 17:15
Reporter: stefan-franz Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: ACE Fluid Synth can't load other SF2 files if LibreArp is used
Description: Linux Mint 21 Cinnamon
If i use libre Arp https://librearp.gitlab.io/ - the ACE Fluid Synth doesn't load new loaded SF2 Files. I can load, but played is always the song before using ACE Fluid used.

Error in LibreArp: The VST3 version (lv2 didn't run) is not able to load or save pattern (no file requester opens). And if i adjust a pattern, the plugin does often not recognize, that something has changed and the save button for save a the preset is not usable.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files: Bildschirmfoto vom 2022-12-01 18-08-56.jpg (4,675 bytes) 2022-12-01 17:15
https://tracker.ardour.org/file_download.php?file_id=4313&type=bug
jpg
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9132 [ardour] bugs minor always 2022-11-30 22:45 2022-12-01 13:29
Reporter: domingo Platform: Arch  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Jack Transport: LUA script for snapping region to playhead behaves bizarre
Description: OS: Linux Manjaro Gnome 43
Ardour 7.1

A LUA script for Ardour 7.1 moves a region to the playhead (included on 'Additional Information'). It works fine when timecode is set to INT, but using JACK as timecode master produces a strange effect. After running the script the selected region will move a few frames after the playhead, instead of the playhead itself. ie., If the playhead is at 00:10:00:00, the region will fall on 00:10:00:02.

Jack Transport is interfaced by QJackCtl 0.9.8, JACK version 1.9.21.
I noticed the failure in sync with Blender, but it also occurs when Ardour is the only Jack client.

A related discussion of the issue here: https://discourse.ardour.org/t/snap-audio-region-to-playhead-ardour-7/107972/6


Tags: jack, Lua, playhead, script, sync, timecode, transport
Steps To Reproduce:
Additional Information: =====================
LUA Script
=====================

ardour {
  ["type"] = "EditorAction",
  name = "Move Regions to Playhead",
  license = "MIT",
  author = "Ardour Team",
  description = "Move selected regions to playhead position"
}

function factory () return function ()

  local sel = Editor:get_selection () -- get current selection
  local sel_regions = sel.regions:regionlist() -- get selected regions

  local playhead = Session:transport_sample () -- get playhead position

  -- prepare undo operation
  Session:begin_reversible_command ("Move Regions to Playhead")

  -- iterate over selected regions
  for region in sel.regions:regionlist ():iter () do
      -- prepare for undo operation
      region:to_stateful ():clear_changes ()

      -- move region to playhead position
      region:set_position (Temporal.timepos_t (playhead))

      -- collect undo/redo diff
      Session:add_stateful_diff_command (region:to_statefuldestructible ())
  end

  -- all done, commit the combined Undo Operation (if any)
  if not Session:abort_empty_reversible_command () then
    Session:commit_reversible_command (nil)
  end

end end
System Description
Attached Files: Screenshot from 2022-11-30 19-20-58.png (66,355 bytes) 2022-11-30 22:45
https://tracker.ardour.org/file_download.php?file_id=4312&type=bug
png
Notes
(0026967)
x42   
2022-11-30 23:22   
can you add a

  print (Session:transport_sample ())

and run the script in Window > Scripting (so that the output is visible)
Assuming a sample-rate of 48kHz, the result at 00:10:00:00 should be 48000 * 10 * 60 = 2880000
(0026968)
domingo   
2022-12-01 13:29   
Running the script with JACK timecode prints: 28804096
With INT timecode: 28800000

Playhead at 00:10:00:00

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9131 [ardour] bugs crash have not tried 2022-11-30 10:11 2022-11-30 10:11
Reporter: Pat Platform: Debian GNU  
Assigned To: OS: Linux  
Priority: high OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ardour refuses to reopen project.
Description: I am not certain what caused this, but i did change browser (from Brave to Firefox). I also before this installed pipwire, but Ardour successfully opened the project after that. Also this is the only project i have, so It is not possible that a cleanup from another project has caused it. Re-installing Brave did not help either.

I have added the error description i get when i try to open the project.

Session "/home/pat/pat first (snapshot pat first)" did not load successfully:
Cannot initialize session/engine: Invalid or corrupt session state.

---ERROR: Could not set session state from XML
ERROR: Session: cannot create Playlist from XML description.
ERROR: Playlist: cannot create region from XML
ERROR: Session: XMLNode describing a AudioRegion references an unknown source id =159856
ERROR: Session: cannot create Region from XML description. Can not load state for region 'Take35_Audio 2-1'
ERROR: Session: XMLNode describing a AudioRegion references an unknown source id =159856
...
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:
9128 [ardour] features minor have not tried 2022-11-29 19:10 2022-11-30 07:06
Reporter: Pat Platform: Debian GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Voice/Level Activate plugin location?
Description: Voice activated recording was possible using a plugin called Voice/Level Activate according to the Tutorial.

It is however not among the plugin that came with Ardour 7.1.

So can you advise on where to find it?

My best reagrds Patrik

Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0026958)
x42   
2022-11-29 19:28   
It is a Lua DSP plugin: https://github.com/Ardour/ardour/blob/master/share/scripts/voice_activate.lua

I've just checked it is available in Ardour 7.0 and 7.1 from ardour.org/download
Where did you get ardour from?
(0026964)
Pat   
2022-11-30 07:06   
Hello

My version 7.1. As a customer I downloaded it after buying from you as download.

If it is a Lua script inside Ardour, please describe where.

Or I can also download the script from your link and run it, and get the header syntax from other Lua scripts
But then i need to know which category of Lua scripts it should be in. There are 3 different ones.

 Mbr Patrik

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9129 [ardour] features feature have not tried 2022-11-29 22:13 2022-11-29 22:13
Reporter: johnmayqwerty Platform: Microsoft  
Assigned To: OS: Windows  
Priority: normal OS Version: 11  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Git friendliness
Description: Built-in integration with Git would be awesome. Like, point at a repo, commit, push, with appropriate ignore settings. You could go crazy with this, but maybe just enough built-in functions to make musicians happy.
Tags:
Steps To Reproduce:
Additional Information:
System Description Windows 11
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9126 [ardour] bugs minor always 2022-11-29 16:41 2022-11-29 20:13
Reporter: hyph3n Platform: Fedora  
Assigned To: OS: Linux  
Priority: normal OS Version: 37  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: System Screensaver Mode has no Effect in Fedora 37
Description: By default, Ardour is configured to inhibit the system screensaver while recording, and it also offers the option to inhibit the screensaver while Ardour is open. Regardless of the setting used, Fedora 37's screensaver starts after its configured idle period, apparently causing xruns in the process.

This occurs on a clean installation (not an upgrade) of Fedora Workstation 37.
Tags:
Steps To Reproduce: 1) In Preferences>Appearance>System Screensaver mode, configure Ardour to either "Inhibit while Recording" or "Inhibit while Ardour is running"

2) Leave the machine idle for an appropriate amount of time (ie. if screensaver is configured to start after 5 minutes, leave the computer idle for 5+ minutes)

Expected result: Ardour prevents the screensaver from starting.
Actual result: Screensaver starts.
Additional Information:
System Description
Attached Files:
Notes
(0026956)
x42   
2022-11-29 16:48   
Are you using Wayland instead of X11/Xorg?
(0026959)
hyph3n   
2022-11-29 19:44   
Yes, correct. Wayland is the default for Fedora Workstation and I believe for Ubuntu now as well.
(0026960)
x42   
2022-11-29 20:01   
Not sure what we can do about this, perhaps with Ubuntu moving to Wayland will raise more attention. Ardour is not alone here:
https://bugs.freedesktop.org/show_bug.cgi?id=89440
https://gitlab.freedesktop.org/xorg/xserver/-/issues/675
(0026961)
hyph3n   
2022-11-29 20:12   
One simple workaround is to lengthen the "Blank Screen Delay" setting in the OS. However, the longest option offered by default is 15 minutes. If you need to delay the screensaver for longer than that, I believe this command will create new options in the list:

gsettings set org.gnome.desktop.session idle-delay 1800

Where 1800 represents the number of seconds you want the idle timeout to be (1800/60 = 30minutes). I haven't tested this on Fedora specifically, but I used it successfully on an Ubuntu 20.04 machine in the past.
(0026962)
hyph3n   
2022-11-29 20:13   
Ah, I stand corrected--there is also a "Never" option in Fedora. If you want something between 15 minutes and never, the above command should apply. :)

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9127 [ardour] features feature sometimes 2022-11-29 18:45 2022-11-29 18:45
Reporter: eqeqeqweqeq Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: master fader not follow track color
Description: watch Attach file
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files: Screenshot.png (337,941 bytes) 2022-11-29 18:45
https://tracker.ardour.org/file_download.php?file_id=4310&type=bug
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9124 [ardour] bugs minor always 2022-11-27 17:31 2022-11-29 16:57
Reporter: stefan-franz Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Save as new project error, if (unused) sounds not found
Description: In my project i tested some SF2 Files with the ACE Flud Synth. Some then i deleted or moved to another directory on my harddisk.

Not after saving as new project this comes:

Save As failed:
copying "/home/stefan/WinD/15-Ardour/Ardour-Projekte/110 Eigene Songs/Ole - Master/Ole/Ole - Stefan Franz/externals/Laidbass.sf2" failed !

In the project this sound is not used neither the ACE Flud Synth is used.....
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0026957)
Daniele1971   
2022-11-29 16:57   
it happened to me too in the past with Ardour 6.9.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9125 [ardour] bugs minor always 2022-11-29 06:13 2022-11-29 06:13
Reporter: hyph3n Platform: Fedora  
Assigned To: OS: Linux  
Priority: normal OS Version: 37  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ardour 7 Can't Autostart ALSA Backend
Description: The “Autostart” option in the Audio/MIDI setup dialog (or Preferences>General>Try to auto-launch audio/midi engine) has no effect on a fresh install of Ardour 7.1.0 when using the ALSA backend. When I had Ardour configured to use pipewire’s JACK, it started up without displaying the Audio/MIDI setup dialog. When configured to use ALSA, it shows the Audio/MIDI setup dialog every time, even when autostart is enabled.

I'm using a single audio device for both input and output, and have confirmed that a recent .ardour session file lists the correct input-device and output-device.

Original forum post here: https://discourse.ardour.org/t/ardour-7-cant-autostart-alsa-backend/107960
Tags:
Steps To Reproduce: 1) On a fresh Fedora 37 install (using pipewire) configure Ardour to use ALSA backend.

2) Ensure "Autostart" is selected in the Audio/Midi Setup dialog (or Preferences>General>Try to auto-launch audio/midi engine).

3) Start Ardour.

Expected result: Ardour starts the audio engine automatically.
Actual result: Ardour prompts the user to start the audio engine manually.
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:
9122 [ardour] bugs minor always 2022-11-27 13:23 2022-11-27 23:40
Reporter: lorenzosu Platform: GNU  
Assigned To: x42 OS: Linux  
Priority: normal OS Version: (any)  
Status: resolved Product Version: 7.1  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ardour generates un-open-able session (XML) when archiving a session which has stero wav files as sources
Description: Archiving a session via File > Archive which had stereo files as sources. In turn these were encoded into mono FLAC but their channels retained in the <Sources> as 0 an 1 (see attached)

Changing the destination session by hand in a text editor and setting all the sources' channel attribute to 0 (i.e. channel="0") fixes the session and Ardour can successfully open it.
Tags: 7.1, archive, unable to load
Steps To Reproduce: - Have a session which has stereo wav file(s) as source(s)
- File > Archive
- Make sure some FLAC compression is selected
- Archive
- When done, uncompress the archive and try opening the session
- Ardour gives an error simlar to the following
In a dialog:
Session "/home/lo/ardour_sessions/Valentina_prova_2017_07_15_2022-11-27_134626 (snapshot Valentina_prova_2017_07_15_2022-11-27_134626)" did not load successfully:
Cannot initialize session/engine: Invalid or corrupt session state.

---ERROR: Could not set session state from XML
ERROR: Session: cannot create Playlist from XML description.
ERROR: Playlist: cannot create region from XML
ERROR: Session: XMLNode describing a AudioRegion references an unknown source id =336
ERROR: Session: cannot create Source from XML description.
ERROR: Found a sound file that cannot be used by Ardour. Talk to the programmers.
...

On the terminal:
ERROR: SndFileSource: file only contains 1 channels; 1 is invalid as a channel number
ERROR: Found a sound file that cannot be used by Ardour. Talk to the programmers.
ERROR: Session: cannot create Source from XML description.
ERROR: SndFileSource: file only contains 1 channels; 1 is invalid as a channel number
ERROR: Found a sound file that cannot be used by Ardour. Talk to the programmers.
ERROR: Session: cannot create Source from XML description.
ERROR: SndFileSource: file only contains 1 channels; 1 is invalid as a channel number
ERROR: Found a sound file that cannot be used by Ardour. Talk to the programmers.
ERROR: Session: cannot create Source from XML description.
ERROR: SndFileSource: file only contains 1 channels; 1 is invalid as a channel number
ERROR: Found a sound file that cannot be used by Ardour. Talk to the programmers.
ERROR: Session: cannot create Source from XML description.
ERROR: Session: XMLNode describing a AudioRegion references an unknown source id =336
ERROR: Playlist: cannot create region from XML
ERROR: Session: cannot create Playlist from XML description.
ERROR: Could not set session state from XML
Additional Information:
System Description
Attached Files: ORIGINAL_Session.ardour (118,575 bytes) 2022-11-27 13:23
https://tracker.ardour.org/file_download.php?file_id=4307&type=bug
BROKEN_session.ardour (118,695 bytes) 2022-11-27 13:23
https://tracker.ardour.org/file_download.php?file_id=4308&type=bug
Notes
(0026955)
x42   
2022-11-27 23:40   
Fixed in Ardour 7.1-177-g842f4517de

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9123 [ardour] bugs major always 2022-11-27 14:19 2022-11-27 19:16
Reporter: 71bpm Platform: Debian GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Bars & Timecode Ruler do their own thing ;-)
Description: Ahh, the Bars:Beats and the Timecode ruler move, yes, they dis-align with respect to the editor grid -- please refer to the operational steps to reproduce this bug as described below.

This problem happens consistently, however there is at least one inconsistency that I wasn't able to isolate so far: In the project where I first noticed this bug starting playback would realign the Bars:Beats ruler to the grid. On the other hand, in the test file (attached) the ruler remains dis-aligned and closing/reopening the session is needed to fix it.
Tags:
Steps To Reproduce: 1. Create a new session, 48kH
2. Create a mono audio track
3. Record anything at least a few bars long at 120 bpm (I recorded 6 bars)
4. Position playhead at bar 3 (or anywhere left of bar 2, even beyond session end) with the shortcut P
5. Move playhead to the left with the cursor key
6. Snap is on, when I reach bar no. 2 the bar & timecode ruler move to right and do not match the bar grid of the editor anymore. They stop moving after a "width of approximately 1.5 bars left of 00:00:00:00" (sorry, I cannot express this any better).

Sidenotes:
- The ruler seems to make bigger steps to the right when Snap is set to Bar, whereas the steps are smaller with Snap set to 1/16 or 1/128.
- Nothing happens when moving the playhead to the right and before reaching bar no. 2 when moving left.
Additional Information: Please find the Ardour file that I used to explore this strange behavior attached.

I use AV Linux, please ask if you need more specifications.
System Description
Attached Files: TestBuggyBarsDisplay.ardour (43,358 bytes) 2022-11-27 14:19
https://tracker.ardour.org/file_download.php?file_id=4309&type=bug
Notes
(0026954)
71bpm   
2022-11-27 19:16   
Edit: "width of approximately 1.5 bars left of 00:00:00:00" is not accurate, it seems to depend on the zoom level but in fact I am not sure about this, also what I said about "bar no. 2" is crap, in another project it is not bar 2 but anyway the problem persists across diverse sessions.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9071 [ardour] bugs major always 2022-11-05 20:30 2022-11-27 16:43
Reporter: krischan941 Platform: Microsoft  
Assigned To: OS: Windows  
Priority: normal OS Version: 11  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Editor List doesn't really work on Windows
Description: Ardour on Windows 11. I can't really interact with "Tracks & Bus"-Tab in Editor List. I can not check or uncheck f.e. visibility state or active state. I also cannot rename tracks und busses. Click or double click to call/do these actions does nothing. The same in Sources and Regions Tab. F.e. double click "Tags" does nothing. Only "Track & Bus Groups" Tab works as expected.

I discovered this issue as I wanted a track in the Editor view to add to Cue page afterwards. I think a possibility to do so via right click a track and a option below "Active" or so would be nice as well.
Tags:
Steps To Reproduce:
Additional Information:
System Description Windows 11
Attached Files:
Notes
(0026885)
Napadator   
2022-11-12 22:58   
You need to hold Alt key and left click to check or uncheck or to rename.
(0026887)
krischan941   
2022-11-13 06:21   
Indeed. It should work without holding Alt key (like on Linux).
(0026888)
Napadator   
2022-11-13 10:20   
Yeah, I don't see any reason why it shouldn't.
(0026952)
NickyP   
2022-11-27 16:36   
In Ardour 7, Windows 11 it worked fine without having to hold the ALT key.
(0026953)
NickyP   
2022-11-27 16:43   
Sorry, I meant in Ardour 6.9.0 it worked fine

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9121 [ardour] features feature N/A 2022-11-27 12:48 2022-11-27 12:48
Reporter: lorenzosu Platform: GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Allow to preserve original time/date when archiving
Description: The Archive functionality is rather useful in particular to archive older projects, e.g. using audio compression (e.g. FLAC). However the new file and compressed Ardour session are created with the current time and date. For archival purposes it would be useful to have an option to preserve the original time/date so that in the future one can track when the session was last saved. AFAIK the original session creation and save timestamps are not preserved anywhere.
Tags: 7.1, archive
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:
9119 [ardour] bugs major always 2022-11-26 16:56 2022-11-26 17:44
Reporter: Pat Platform: Debian GNU  
Assigned To: OS: Linux  
Priority: urgent OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: for mono recordings, normalize nor gain work
Description: I recorded in mono, and the editor mixer readings are Out left/Out right, fader is on 2.0 and fader automation mode is active (button P)
Neither normalize nor boost gain works.
Selecting Properties I can however select region gain (tried up to 21 dB) which works.

I have not tested stereo recording so it might be there too.

Tags:
Steps To Reproduce: 1. Create mono audio track and record
2. Activate the recorded audio, and select Normalize or Boost gain from right mouse mouse.


Additional Information:
System Description
Attached Files:
Notes
(0026949)
Pat   
2022-11-26 17:44   
Hello,

I recorded once more, but with a higher volume, and this time Normalized worked ( on the same track, same track parameters).
The difference to the first one was that the volume was really low (needed to ampify it 21dB) and that it was the first audio recording in a new project.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9116 [ardour] bugs minor have not tried 2022-11-26 13:26 2022-11-26 13:29
Reporter: tired_eyes Platform: GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Automation: unable to select the rightmost point
Description: It's impossible to select the rightmost automation point if automation line spans it's entire region. Please see the attached screenshot
Tags: 7.1, automation
Steps To Reproduce:
Additional Information:
System Description
Attached Files: automation.png (117,964 bytes) 2022-11-26 13:26
https://tracker.ardour.org/file_download.php?file_id=4303&type=bug
png
Notes
(0026947)
tired_eyes   
2022-11-26 13:29   
It's still possible to edit the rightmost point by temporary expanding the region to the right

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9056 [ardour] bugs minor always 2022-10-31 12:01 2022-11-26 13:17
Reporter: cooltehno_bugs Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.0  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Bug: Ardour 6.9-7.0 - "Delete" key is not working for automation control points
Description: "Delete" key is not working for automation control points. Only "Backspace" key can delete the selected control points (may be this is somehow related with double "Delete" action in the Keyboard Shortcuts dialog)
Tags:
Steps To Reproduce: 1. Make few control points in any automation line.
2. Select few control points by rectangle selection with the mouse.
3. Press "Delete" key - this does nothing (Press "Backspace" key to delete these points - to ensure that the control points can be deleted in principle)
Additional Information:
System Description
Attached Files: Delete_control_points.gif (230,207 bytes) 2022-10-31 12:01
https://tracker.ardour.org/file_download.php?file_id=4264&type=bug
gif
Notes
(0026946)
tired_eyes   
2022-11-26 13:17   
Still relevant for 7.1

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9083 [ardour] bugs crash always 2022-11-08 16:49 2022-11-25 13:25
Reporter: Daniele1971 Platform: GNU  
Assigned To: x42 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: segfault in libardour opening a session made with 6.9
Description: I've a session made with Ardour-6.9 (openSUSE build), official 7.1 crash on loading::
RT-7-(nil)[4038]: segfault at 0 ip 00007f88a1579b4a sp 00007f889b17d8d0 error 4 in libardour.so.3[7f88a0e00000+d54000]

Does not crash with 7.1 openSUSE build (tested by a friend, we're both on TW)

Session its an unfinished project, so it's small without strange things..

I'd like to attach the session archive but there' s an error: "413 Request Entity too large". The archive is 1,7mb
(https://discourse.ardour.org/t/bugtracker-upload-size/107847)

If may help, loading the session with official 6.9, Ardour warns about a missing plugin (samplv1) untrue it's selectable from plugin window and no issue with the openSUSE build.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0026870)
Daniele1971   
2022-11-08 18:29   
Sorry, some corrections: with the openSUSE builds:
7.0 -> ok
7.1 -> crash

official package:
6.9 -> ok *
7.0 -> ok *
7.1 -> crash

(*) missing samplv1 plugin
(0026941)
x42   
2022-11-25 01:54   
Could it be that the session has a track that has a MIDI output, but no MIDI input?

If so that should meanwhile be fixed in ardour/git.
(0026945)
Daniele1971   
2022-11-25 10:40   
Tested Ardour-7.1.168 and it's ok.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9001 [ardour] bugs crash always 2022-10-17 19:08 2022-11-24 22:59
Reporter: martin.vlk Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.0  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ardour crashes when I try to add the ZynAddSubFX synth plugin to a MIDI track
Description: It used to work fine in 6.9

For some reason when I start Ardour7 from the console, it doesn't crash in this scenario and works as expected.
Tags:
Steps To Reproduce: Create a new MIDI track and replace the default synth with ZynAddSubFX - the application crashes.
Additional Information:
System Description
Attached Files: ardour-backtrace.txt (32,709 bytes) 2022-11-23 23:12
https://tracker.ardour.org/file_download.php?file_id=4301&type=bug
Notes
(0026629)
martin.vlk   
2022-10-17 19:41   
Further testing shows that the app crashes on trying to show the plugin GUI. When I don't try to show the GUI, the plugin itself works fine.
(0026935)
rcheesley   
2022-11-23 23:12   
I am able to replicate this on Ardour 7.1.0 - as soon as the GUI opens, Ardour crashes. Short screencast here: https://watch.screencastify.com/v/as3AG13drqiNKP4x1Qhf in case that is helpful.

Happy to help with debugging and have attached a backtrace (thanks for the excellent docs, my first time so let me know if there's anything wrong/missing!)
(0026939)
Daniele1971   
2022-11-24 22:59   
Works fine on openSUSE TW.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9114 [ardour] bugs major always 2022-11-22 13:28 2022-11-24 03:42
Reporter: Pat Platform: GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Vsti dont work after saving and restarting with fluidsynth disabled
Description: I have fluidsynth connected to gm soundband.

Original state : fluidsynth is playing drums ok
de-activated fluidsynth and restarted ardour
Now after re-activate fluidsynth no sound (could not enable it )
After one more Ardour restart, fluidsynth now only plays the last two notes ive insterted
After re-selecting fluidsynth patch, and channel 10 (drums) i got it working normally again.

It seems that the fluidsynth configuration is not save successfully.

Tags:
Steps To Reproduce: 1. Disable fluidsynth
2. Save and restart Arduor
3. Activate fluidsynth
4. Try playback again, note that its not ok
5. Restart Ardour
6. Try playback, note only newest notes play.
Additional Information:
System Description
Attached Files:
Notes
(0026934)
x42   
2022-11-23 19:31   
The patch/progam state is not saved as part of the plugin, but Ardour's MIDI track (this way it also works with external synths).
When re-loading a session Ardour replays bank/patch changes, but i the plugin is disabled it will not process those events.

So this is more or less expected behavior.

A more reliable solution is to add the bank/patch changes to the MIDI region, so that they are sent to the synth whenever you play though them (not just at session load).
(0026938)
Pat   
2022-11-24 03:42   
Hello x42

I like to add some more related issues which you might take into account
- When Ardour restarted it was in a state where it could not play fluidsynth sounds at all ( tested that audio played so no sound card issues)
- When selecting drums in fluidsynth using GUI i also select Midi channel 10. But Ardour does not read the channel right from the GUI so i have to set the channel to play only on channel 10 from Ardour track right mouse menu.
- The plugin state should be saved as above (with channel info and VSTI activation status) also if the midi track is deleted and recreated.
- And the information should also be in patch changes in the Midi.

So i assume based on above that :
. Ardour need to save also the Midi channel from GUI configuration, and it should also have a default channel if no channel has been set
- The Vsti state need to be saved with on/off status. It should be read "on the fly" ( not written in the midi file) in the beginning of midi track playback. so that any previous patch changes in the midi track need to partially or fully override that information.

Mbr Patrik

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9113 [ardour] bugs minor always 2022-11-22 11:40 2022-11-22 11:40
Reporter: nicbeu Platform: Apple Macintosh  
Assigned To: OS: MacOS  
Priority: normal OS Version: 10.12 or later  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Display of paths in the project settings dialog
Description: Although you can make the project settings window larger, the paths are not fully displayed.
Tags: 7.1
Steps To Reproduce: Open project settings dialog, go to Locations and take a look at the sessions folder paths.
Additional Information:
System Description
Attached Files: Bildschirmfoto 2022-11-22 um 12.17.34.png (107,795 bytes) 2022-11-22 11:40
https://tracker.ardour.org/file_download.php?file_id=4300&type=bug
png
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9112 [ardour] bugs minor always 2022-11-22 09:53 2022-11-22 10:07
Reporter: DavidB Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Current Preferences GUI and Font scaling value isn't obvious if not 100%
Description: Seen on both Linux and Windows 10.

Preferences > Appearance > Size and Scale > GUI and Font scaling

The currently selected scaling value isn't obvious if it's not 100%. There's only one value above the slider, i.e. 100%.

Possible suggestions:
* Put other static values above the slider, although they probably won't all fit.
* Have the currently selected value displayed (and it dynamically changes as the slider is moved).
* Remove the slider and just allow the user to type in the value or select from a list of values.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files: gui-and-font-scaling.png (21,271 bytes) 2022-11-22 09:53
https://tracker.ardour.org/file_download.php?file_id=4299&type=bug
png
Notes
(0026932)
DavidB   
2022-11-22 10:07   
Putting static 50% and 200% values above the slider would be helpful, and presumably would be a quick fix.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9049 [ardour] bugs major always 2022-10-29 16:27 2022-11-22 07:21
Reporter: gonsolo Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.0  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Crash when trying to jump and play
Description: A session upgraded to Ardour 7 seems to be seriously confused.
When playing and trying to jump after location marker 8 Ardour crashes.

Stack trace:

```
#0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:44
0000001 __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
#2 __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#3 0x00007ffff343bc46 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
0000004 0x00007ffff34227fc in __GI_abort () at ./stdlib/abort.c:79
0000005 0x00007ffff58a2d27 in Temporal::TempoMap::get_grid(std::__cxx11::list<Temporal::TempoMapPoint, std::allocator<Temporal::TempoMapPoint> >&, long, long, unsigned int) const
     (this=0x55555793c700, ret=empty std::__cxx11::list, start=282401617680, end=282401617680, bar_mod=0) at ../libs/temporal/tempo.cc:1916
#6 0x00007ffff774b722 in ARDOUR::LV2Plugin::connect_and_run(ARDOUR::BufferSet&, long, long, double, ARDOUR::ChanMapping const&, ARDOUR::ChanMapping const&, unsigned int, long)
     (this=0x55556d9d8e40, bufs=..., start=48027486, end=48027486, speed=0, in_map=..., out_map=..., nframes=1024, offset=0) at ../libs/ardour/lv2_plugin.cc:2668
#7 0x00007ffff73d0e57 in ARDOUR::PluginInsert::connect_and_run(ARDOUR::BufferSet&, long, long, double, unsigned int, long, bool)
     (this=0x55556d9d3d60, bufs=..., start=48027486, end=48027486, speed=0, nframes=1024, offset=0, with_auto=true) at ../libs/ardour/plugin_insert.cc:1107
0000008 0x00007ffff73d2785 in ARDOUR::PluginInsert::run(ARDOUR::BufferSet&, long, long, double, unsigned int, bool)
    (this=0x55556d9d3d60, bufs=..., start_sample=48027486, end_sample=48027486, speed=0, nframes=1024) at ../libs/ardour/plugin_insert.cc:1329
0000009 0x00007ffff74c62a6 in ARDOUR::Route::process_output_buffers(ARDOUR::BufferSet&, long, long, unsigned int, bool, bool)
     (this=0x55556c1bd8d0, bufs=..., start_sample=48027486, end_sample=48027486, nframes=1024, gain_automation_ok=false, run_disk_reader=false) at ../libs/ardour/route.cc:543
0000010 0x00007ffff74c7441 in ARDOUR::Route::run_route(long, long, unsigned int, bool, bool)
    (this=0x55556c1bd8d0, start_sample=48026446, end_sample=48026446, nframes=1024, gain_automation_ok=false, run_disk_reader=false) at ../libs/ardour/route.cc:734
0000011 0x00007ffff74dcd49 in ARDOUR::Route::no_roll_unlocked(unsigned int, long, long, bool)
    (this=0x55556c1bd8d0, nframes=1024, start_sample=48026446, end_sample=48026446, session_state_changing=false) at ../libs/ardour/route.cc:4054
0000012 0x00007ffff731ce15 in ARDOUR::MidiTrack::no_roll_unlocked(unsigned int, long, long, bool)
     (this=0x55556c1bd8d0, nframes=1024, start_sample=48026446, end_sample=48026446, state_changing=false) at ../libs/ardour/midi_track.cc:389
0000013 0x00007ffff74dcbfa in ARDOUR::Route::no_roll(unsigned int, long, long, bool)
    (this=0x55556c1bd8d0, nframes=1024, start_sample=48026446, end_sample=48026446, session_state_changing=false) at ../libs/ardour/route.cc:4024
0000014 0x00007ffff6f3a24e in ARDOUR::Graph::process_one_route(ARDOUR::Route*) (this=0x555558223800, route=0x55556c1bd8d0) at ../libs/ardour/graph.cc:547
#15 0x00007ffff74c7262 in ARDOUR::Route::process() (this=0x55556c1bd8d0) at ../libs/ardour/route.cc:705
0000016 0x00007ffff6f45b45 in ARDOUR::GraphNode::run(ARDOUR::GraphChain const*) (this=0x55556c1bdd20, chain=0x7fffb40826d0) at ../libs/ardour/graphnode.cc:65
#17 0x00007ffff6f38853 in ARDOUR::Graph::run_one() (this=0x555558223800) at ../libs/ardour/graph.cc:346
0000018 0x00007ffff6f38c11 in ARDOUR::Graph::helper_thread() (this=0x555558223800) at ../libs/ardour/graph.cc:374
0000019 0x00007ffff6f44bb1 in boost::_mfi::mf0<void, ARDOUR::Graph>::operator()(ARDOUR::Graph*) const (this=0x7fffa1ffa958, p=0x555558223800) at /usr/include/boost/bind/mem_fn_template.hpp:49
0000020 0x00007ffff6f4413d in boost::_bi::list1<boost::_bi::value<ARDOUR::Graph*> >::operator()<boost::_mfi::mf0<void, ARDOUR::Graph>, boost::_bi::list0>(boost::_bi::type<void>, boost::_mfi::mf0<void, ARDOUR::Graph>&, boost::_bi::list0&, int) (this=0x7fffa1ffa968, f=..., a=...) at /usr/include/boost/bind/bind.hpp:259
0000021 0x00007ffff6f43090 in boost::_bi::bind_t<void, boost::_mfi::mf0<void, ARDOUR::Graph>, boost::_bi::list1<boost::_bi::value<ARDOUR::Graph*> > >::operator()() (this=0x7fffa1ffa958)
    at /usr/include/boost/bind/bind.hpp:1294
0000022 0x00007ffff6f41601 in boost::detail::function::void_function_obj_invoker0<boost::_bi::bind_t<void, boost::_mfi::mf0<void, ARDOUR::Graph>, boost::_bi::list1<boost::_bi::value<ARDOUR::Graph*> > >, void>::invoke(boost::detail::function::function_buffer&) (function_obj_ptr=...) at /usr/include/boost/function/function_template.hpp:158
0000023 0x0000555555cb32d3 in boost::function0<void>::operator()() const (this=0x7fffa1ffa950) at /usr/include/boost/function/function_template.hpp:763
#24 0x00007fffd7fba431 in ARDOUR::JACKAudioBackend::_start_process_thread(void*) (arg=0x555558394410) at ../libs/backends/jack/jack_audiobackend.cc:955
0000025 0x00007ffff3490402 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442
0000026 0x00007ffff351f590 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
```
Tags:
Steps To Reproduce: 1. Open the session.
2. Play.
3. Jump via mouse to location marker 8 or a bit later.
4. Crash.
Additional Information: Archive (3MB which is bigger than the allowed 2MB):
https://drive.google.com/file/d/1qI6lSKW8yoTqECEjxAuxoKdlyNQomG0k/view?usp=share_link
System Description
Attached Files: wrong.png (20,368 bytes) 2022-10-30 16:40
https://tracker.ardour.org/file_download.php?file_id=4262&type=bug
png

debug_output.gz (79,887 bytes) 2022-10-31 17:47
https://tracker.ardour.org/file_download.php?file_id=4265&type=bug
debug_output-2.gz (2,826 bytes) 2022-10-31 18:50
https://tracker.ardour.org/file_download.php?file_id=4266&type=bug
bars.png (28,829 bytes) 2022-11-07 10:00
https://tracker.ardour.org/file_download.php?file_id=4280&type=bug
png
Notes
(0026752)
paul   
2022-10-29 17:05   
There are at least 3 other bug reports withthe same backtrace.

Thanks for the session archive, should be useful.
(0026753)
gonsolo   
2022-10-29 17:39   
I find https://tracker.ardour.org/view.php?id=9027 which is marked fixed with 7.0-116-g489c9ace9f which it isn't (I believe).
A search for "TempoMap::get_grid" doesn't reveal any other reports.

And sorry for being a PITA. :)
(0026754)
paul   
2022-10-29 17:43   
Not a pain at all. Please keep reports coming.
(0026756)
gonsolo   
2022-10-30 10:48   
I think the culprit is TempoMetric::bbt_at at tempo.cc:622 because it is confused of the 3/4 in the middle of a bar.
I managed to manually get it to work by moving the 3/4 to the beginning of a bar.

gonsolo start0: 47001057, end: 47001057
 start0 superclock: 276366215160
 end superclock: 276366215160
  sc: 276366215160
  dg.get_beats(): 10
  _meter->note_value(): 4
  note_value_count: 10
  ticks: 1077
  _meter->bbt(): 290|1|0
  bbt_offset: 0|10|1077
  add: 293|2|1077
  bbt: 293|2|1077
  new_start: 276441352257
  sc: 276366215160
  dg.get_beats(): 10
  _meter->note_value(): 4
  note_value_count: 10
  ticks: 1077
  _meter->bbt(): 290|1|0
  bbt_offset: 0|10|1077
  add: 293|2|1077
  sc: 276366215160
  dg.get_beats(): 10
  _meter->note_value(): 4
  note_value_count: 10
  ticks: 1077
  _meter->bbt(): 290|1|0
  bbt_offset: 0|10|1077
  add: 293|2|1077
gonsolo start0: 47001057, end: 47001057
 start0 superclock: 276366215160
 end superclock: 276366215160
  sc: 276366215160
  dg.get_beats(): 10
  _meter->note_value(): 4
  note_value_count: 10
  ticks: 1077
  _meter->bbt(): 290|1|0
  bbt_offset: 0|10|1077
  add: 293|2|1077
  bbt: 293|2|1077
  new_start: 276441352257
  sc: 276366215160
  dg.get_beats(): 10
  _meter->note_value(): 4
  note_value_count: 10
  ticks: 1077
  _meter->bbt(): 290|1|0
  bbt_offset: 0|10|1077
  add: 293|2|1077
(0026757)
paul   
2022-10-30 13:34   
hmm, meter (time signature) changes are supposed to be allowed on bars only. This is part of the conceptual changes that make full compatibility with 6.x hard. Importing a 6.x session that allowed those changes off-bar would definitely cause issues.
(0026758)
paul   
2022-10-30 14:49   
(Last edited: 2022-10-30 14:51)
that said, the .ardour file you attached doesn't seem to show any meter changes off-bar:

      <Meter note-value="4" divisions-per-bar="4" sclock="0" quarters="0:0" bbt="1|1|0"/>
      <Meter note-value="4" divisions-per-bar="3" sclock="112409227592" quarters="400:0" bbt="101|1|0"/>
      <Meter note-value="4" divisions-per-bar="4" sclock="132422609396" quarters="478:0" bbt="127|1|0"/>
      <Meter note-value="4" divisions-per-bar="4" sclock="237611970470" quarters="986:0" bbt="254|1|0"/>
      <Meter note-value="4" divisions-per-bar="3" sclock="274559752262" quarters="1130:0" bbt="290|1|0"/>
      <Meter note-value="4" divisions-per-bar="4" sclock="300066321800" quarters="1154:0" bbt="305|1|0"/>
      <Meter note-value="4" divisions-per-bar="4" sclock="323415267238" quarters="1266:0" bbt="333|1|0"/>

when loading here, the 3/4 meter starts at bar 101

Is that not the case for you?
(0026761)
paul   
2022-10-30 16:23   
OK, I understand the bug now. But it will take a day of putting up tiles in my bathroom to come up with a solution.

The problem is that when we are computing the grid near a sample position, we first determine meter and tempo in effect at that point. Then we compute the number of quarter notes since the tempo change, and then use that to compute the delta in quarter notes between the meter change and the given position.

Problem is, if the meter is before the tempo, then for the interval from the meter to the tempo, the duration of a quarter note is defined by the *previous tempo*, not the one in effect at the time we're interested in. This ends up leading to the "we've gone backwards" error.

To the tiles!
(0026762)
paul   
2022-10-30 16:25   
BTW, I did try just using the *later* of the tempo or meter change for the computation, which initially looked like a simple fix. But this just breaks other stuff.
(0026763)
gonsolo   
2022-10-30 16:40   
```
<Meter note-value="4" divisions-per-bar="3" sclock="112409227592" quarters="400:0" bbt="101|1|0"/>
```
If you're saying that the last number in "bbt="101|1|0" has to be always zero, then yes, my ardour file is sane.
But after opening the meter change is still off-bar as can be seen in the picture.

I see that you now have an understanding of the bug and I expect the fix just after the tiles. (Kidding, as I said, I manually fixed the session, but it's still nice to hear that I can help to make Ardour rock solid again.)
(0026764)
gonsolo   
2022-10-30 17:13   
Since it is related (or the same bug): Dragging the tempo marker at bar 300 around is also crashing.
Stack trace:

#0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:44
0000001 __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
#2 __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#3 0x00007ffff343bc46 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
0000004 0x00007ffff34227fc in __GI_abort () at ./stdlib/abort.c:79
0000005 0x00007ffff342271b in __assert_fail_base
    (fmt=0x7fffef6039b5 "%s%s%s:%u: %s%sZusicherung »%s« nicht erfüllt.\n%n", assertion=0x7ffff58d7f1e "qn >= _quarters", file=0x7ffff58d7d47 "../libs/temporal/tempo.cc", line=471, function=<optimized out>) at ./assert/assert.c:92
#6 0x00007ffff3433596 in __GI___assert_fail
    (assertion=0x7ffff58d7f1e "qn >= _quarters", file=0x7ffff58d7d47 "../libs/temporal/tempo.cc", line=471, function=0x7ffff58d7eb0 "Temporal::superclock_t Temporal::TempoPoint::superclock_at(const Temporal::Beats&) const") at ./assert/assert.c:101
#7 0x00007ffff58936cd in Temporal::TempoPoint::superclock_at(Temporal::Beats const&) const (this=0x5555864279f0, qn=...)
    at ../libs/temporal/tempo.cc:471
0000008 0x00007ffff58b7551 in Temporal::TempoMetric::superclock_at(Temporal::Beats const&) const (this=0x7fffffffafa0, qn=...)
    at ../libs/temporal/temporal/tempo.h:480
0000009 0x00007ffff58a3978 in Temporal::TempoMap::get_grid(std::__cxx11::list<Temporal::TempoMapPoint, std::allocator<Temporal::TempoMapPoint> >&, long, long, unsigned int) const (this=0x5555844a6230, ret=std::__cxx11::list = {...}, start=282572606127, end=286108540200, bar_mod=0)
    at ../libs/temporal/tempo.cc:2001
0000010 0x00005555560b5ea2 in Editor::compute_current_bbt_points(std::__cxx11::list<Temporal::TempoMapPoint, std::allocator<Temporal::TempoMapPoint> >&, long, long) (this=0x555558391250, grid=std::__cxx11::list = {...}, leftmost=46659834, rightmost=48657915) at ../gtk2_ardour/editor_tempodisplay.cc:413
0000011 0x0000555556083994 in Editor::metric_get_bbt(std::vector<ArdourCanvas::Ruler::Mark, std::allocator<ArdourCanvas::Ruler::Mark> >&, long, long, int) (this=0x555558391250, marks=std::vector of length 0, capacity 256, lower=46659834, upper=48657915) at ../gtk2_ardour/editor_rulers.cc:1172
0000012 0x00005555560b62af in Editor::maybe_draw_grid_lines() (this=0x555558391250) at ../gtk2_ardour/editor_tempodisplay.cc:462
0000013 0x00005555560b8ab4 in Editor::mid_tempo_change(Editor::MidTempoChanges) (this=0x555558391250, what_changed=Editor::TempoChanged)
    at ../gtk2_ardour/editor_tempodisplay.cc:801
0000014 0x0000555555fa35fb in TempoMarkerDrag::motion(_GdkEvent*, bool) (this=0x5555876af7f0, event=0x7fffffffbc30, first_move=false)
    at ../gtk2_ardour/editor_drag.cc:3320
#15 0x0000555555f90a86 in Drag::motion_handler(_GdkEvent*, bool) (this=0x5555876af7f0, event=0x7fffffffbc30, from_autoscroll=false)
    at ../gtk2_ardour/editor_drag.cc:522
0000016 0x0000555555f8f7fa in DragManager::motion_handler(_GdkEvent*, bool) (this=0x5555583b6650, e=0x7fffffffbc30, from_autoscroll=false)
    at ../gtk2_ardour/editor_drag.cc:231
#17 0x000055555600db0d in Editor::motion_handler(ArdourCanvas::Item*, _GdkEvent*, bool)
    (this=0x555558391250, event=0x7fffffffbc30, from_autoscroll=false) at ../gtk2_ardour/editor_mouse.cc:2300
0000018 0x0000555555f86b57 in Editor::typed_event(ArdourCanvas::Item*, _GdkEvent*, ItemType)
     (this=0x555558391250, item=0x5555776cbbf0, event=0x7fffffffbc30, type=TempoMarkerItem) at ../gtk2_ardour/editor_canvas_events.cc:223
0000019 0x0000555555f89793 in Editor::canvas_tempo_marker_event(_GdkEvent*, ArdourCanvas::Item*, TempoMarker*)
(0026765)
paul   
2022-10-30 18:01   
At present, if you see ::get_grid() in the stacktrace, then more useful output is obtainable via running ardour from the cmdline with -D grid,temporalmap
(0026771)
paul   
2022-10-31 01:36   
should be fixed in git master, 9c2c08973d894

was easier than tiling!
(0026782)
gonsolo   
2022-10-31 17:47   
Not yet:

#0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:44
0000001 __pthread_kill_internal (signo=6, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
#2 __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#3 0x00007ffff343bc46 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
0000004 0x00007ffff34227fc in __GI_abort () at ./stdlib/abort.c:79
0000005 0x00007ffff342271b in __assert_fail_base
    (fmt=0x7fffef6029b5 "%s%s%s:%u: %s%sZusicherung »%s« nicht erfüllt.\n%n", assertion=0x7ffff58d7f1e "qn >= _quarters", file=0x7ffff58d7d47 "../libs/temporal/tempo.cc", line=471, function=<optimized out>) at ./assert/assert.c:92
#6 0x00007ffff3433596 in __GI___assert_fail
    (assertion=0x7ffff58d7f1e "qn >= _quarters", file=0x7ffff58d7d47 "../libs/temporal/tempo.cc", line=471, function=0x7ffff58d7eb0 "Temporal::superclock_t Temporal::TempoPoint::superclock_at(const Temporal::Beats&) const") at ./assert/assert.c:101
#7 0x00007ffff589272d in Temporal::TempoPoint::superclock_at(Temporal::Beats const&) const (this=0x555577625950, qn=...)
    at ../libs/temporal/tempo.cc:471
0000008 0x00007ffff5893de8 in Temporal::TempoMetric::superclock_at(Temporal::BBT_Time const&) const (this=0x7fffffffb090, bbt=...)
    at ../libs/temporal/tempo.cc:667
0000009 0x00007ffff58a2be3 in Temporal::TempoMap::get_grid(std::__cxx11::list<Temporal::TempoMapPoint, std::allocator<Temporal::TempoMapPoint> >&, long, long, unsigned int) const (this=0x555588116670, ret=std::__cxx11::list = {...}, start=290064432769, end=345781174612, bar_mod=1)
    at ../libs/temporal/tempo.cc:2027
0000010 0x00007ffff58a57fe in Temporal::TempoMap::count_bars(Temporal::Beats const&, Temporal::Beats const&) const
    (this=0x555588116670, start=..., end=...) at ../libs/temporal/tempo.cc:2182
0000011 0x0000555556083303 in Editor::compute_bbt_ruler_scale(long, long) (this=0x5555583ad640, lower=43142526, upper=58760601)
    at ../gtk2_ardour/editor_rulers.cc:1078
0000012 0x0000555556081b99 in Editor::update_tempo_based_rulers() (this=0x5555583ad640) at ../gtk2_ardour/editor_rulers.cc:754
0000013 0x00005555560b8aa5 in Editor::mid_tempo_change(Editor::MidTempoChanges) (this=0x5555583ad640, what_changed=Editor::TempoChanged)
    at ../gtk2_ardour/editor_tempodisplay.cc:800
0000014 0x0000555555fa351f in TempoMarkerDrag::motion(_GdkEvent*, bool) (this=0x555565786e40, event=0x7fffffffbc10, first_move=true)
    at ../gtk2_ardour/editor_drag.cc:3320
#15 0x0000555555f909aa in Drag::motion_handler(_GdkEvent*, bool) (this=0x555565786e40, event=0x7fffffffbc10, from_autoscroll=false)
    at ../gtk2_ardour/editor_drag.cc:522
0000016 0x0000555555f8f71e in DragManager::motion_handler(_GdkEvent*, bool) (this=0x5555583d1720, e=0x7fffffffbc10, from_autoscroll=false)
    at ../gtk2_ardour/editor_drag.cc:231
#17 0x000055555600dab1 in Editor::motion_handler(ArdourCanvas::Item*, _GdkEvent*, bool)
    (this=0x5555583ad640, event=0x7fffffffbc10, from_autoscroll=false) at ../gtk2_ardour/editor_mouse.cc:2300
0000018 0x0000555555f86a7b in Editor::typed_event(ArdourCanvas::Item*, _GdkEvent*, ItemType)
    (this=0x5555583ad640, item=0x5555777ac030, event=0x7fffffffbc10, type=TempoMarkerItem) at ../gtk2_ardour/editor_canvas_events.cc:223
0000019 0x0000555555f896b7 in Editor::canvas_tempo_marker_event(_GdkEvent*, ArdourCanvas::Item*, TempoMarker*)
    (this=0x5555583ad640, event=0x7fffffffbc10, item=0x5555777ac030, marker=0x5555777ab460) at ../gtk2_ardour/editor_canvas_events.cc:1095

I attached the output of "-D grid,temporalmap"

One tile down.
(0026783)
paul   
2022-10-31 18:09   
Could you repeat that with Edit > Preferences > Performance > processor usage set to 1 processor ? The debug output is unreadable when multithreaded ... thanks

Alternatively, let me know the steps to make this happen (your existing instructions no longer crash for me)
(0026787)
gonsolo   
2022-10-31 18:46   
Output attached (with set to 1 processor).

Session: https://drive.google.com/file/d/1cUZyxJnVvgjXUO5DhSBd15JnknysQJK2/view?usp=sharing

1. Open session
2. Drag the tempo marker at bar 306 around.
(0026788)
gonsolo   
2022-10-31 18:50   
Debug output with setting processors to 1, restarting, and making sure that processor is set to 1.
(0026790)
paul   
2022-10-31 19:07   
and this was generated/triggered how?
(0026794)
gonsolo   
2022-10-31 20:47   
Open the session and drag the tempo marker around.
(0026862)
gonsolo   
2022-11-07 10:00   
Also note how Ardour doesn't respect the 4/4 change at bar 298.
Also the time change is in the middle of bar 306 which should not be the case.
That is still the session above.
(0026863)
gonsolo   
2022-11-07 10:01   
https://tracker.ardour.org/view.php?id=9067 seems to be related as it also crashes at tempo.cc:471.
(0026929)
paul   
2022-11-22 01:26   
archive no longer readable. would like to check if f5887b978d4 fixes this issue
(0026931)
gonsolo   
2022-11-22 07:21   
The session in https://tracker.ardour.org/view.php?id=9049#c26787 is essentially the same (with processor set to 1 for debugging).

I opened the session and dragged said marker around for half an hour now (slightly exaggerating) and couldn't get Ardour to crash so it seems to be fixed.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9110 [ardour] features minor N/A 2022-11-21 11:01 2022-11-22 04:51
Reporter: Pat Platform:  
Assigned To: paul OS:  
Priority: high OS Version:  
Status: resolved Product Version: 7.1  
Product Build: Resolution: won't fix  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Need for compressed audio format
Description: Hello,

Ardour 7.1 is a inspiring Daw, thanks to you!

I suggest that you add Ogg compression to the existing media formats in the Session properties. My actual target is that a 3 minutes stereo track would consume less that 10 Mb. I think this need is generic for both linux and windows.

Motivation
i record songs with 4-8 audio tracks, and I noticed that I can easily consume 0.3 - 0.5 Gb per song, even using the flak compression, which is too much. I have a netbook running Linux ( MX linux) with a 32 Gb disk.

I also would add out that several other daws (like Reaper) has support for Ogg (and indeed Mp3) for similar reasons..

Thank you
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0026921)
paul   
2022-11-21 18:15   
We will not add lossy compression formats to the native format list for Ardour. FLAC is available (lossless compression). Disk space is cheap, data lost by compressing to vorbis or mp3 is not. You can export to any of these formats, but they are not appropriate as the internal data format for a professional tool.
(0026925)
paul   
2022-11-21 21:53   
(Last edited: 2022-11-21 21:54)
Memory is not used by DAW-created audio files, only disk space. I haven't seen a laptop in some time that has less than a *huge* amount of space, and the ones that do not will accept external USB3 drives, which are cheap and fast enough.

FLAC will still save you a significant amount of space compared to WAV/AIFF, and has no quality issues.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9067 [ardour] bugs crash always 2022-11-04 17:42 2022-11-22 01:24
Reporter: prokoudine Platform: Ubuntu  
Assigned To: paul OS: Linux  
Priority: normal OS Version: (any)  
Status: assigned Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Crash when playing back a tempo ramp and a TS change
Description: 1. Open the attached session (archived)
2. Place a 6/8 time signature at bar 3 (right in the middle of a tempo ramp)
3. Start playback
4. BOOM

This is an optimized 64-bit of v7.1 for Linux, running on Ubuntu 22.04.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files: markers-2022-11-04-12-20-23_2022-11-04_203831.ardour-session-archive (6,383 bytes) 2022-11-04 17:42
https://tracker.ardour.org/file_download.php?file_id=4276&type=bug
Notes
(0026852)
x42   
2022-11-04 17:49   
libs/temporal/tempo.cc:471: Temporal::superclock_t Temporal::TempoPoint::superclock_at(const Temporal::Beats&) const: Assertion `qn >= _quarters' failed.
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
0000001  0x00007fe7147f9537 in __GI_abort () at abort.c:79
#2  0x00007fe7147f940f in __assert_fail_base
    (fmt=0x7fe7149716a8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x7fe7169c9c6e "qn >= _quarters", file=0x7fe7169c9a97 "../libs/temporal/tempo.cc", line=471, function=<optimized out>) at assert.c:92
#3  0x00007fe714808662 in __GI___assert_fail
    (assertion=0x7fe7169c9c6e "qn >= _quarters", file=0x7fe7169c9a97 "../libs/temporal/tempo.cc", line=471, function=0x7fe7169c9c00 "Temporal::superclock_t Temporal::TempoPoint::superclock_at(const Temporal::Beats&) const") at assert.c:101
0000004  0x00007fe7169f051b in Temporal::TempoPoint::superclock_at(Temporal::Beats const&) const (this=0x55b1870ee5f0, qn=...) at ../libs/temporal/tempo.cc:471
0000005  0x00007fe7169f1b12 in Temporal::TempoMetric::superclock_at(Temporal::BBT_Time const&) const (this=0x7fe6d5fb58a0, bbt=...) at ../libs/temporal/tempo.cc:667
#6  0x00007fe7169ff89f in Temporal::TempoMap::get_grid(std::__cxx11::list<Temporal::TempoMapPoint, std::allocator<Temporal::TempoMapPoint> >&, long, long, unsigned int) const (this=
    0x55b180e47c10, ret=Python Exception <class 'AttributeError'> 'NoneType' object has no attribute 'pointer': 
empty std::__cxx11::list, start=379258824, end=380463048, bar_mod=0) at ../libs/temporal/tempo.cc:1925
#7  0x00007fe718a638c0 in ARDOUR::LV2Plugin::connect_and_run(ARDOUR::BufferSet&, long, long, double, ARDOUR::ChanMapping const&, ARDOUR::ChanMapping const&, unsigned int, long) (this=
    0x55b1865a8ee0, bufs=..., start=322499, end=323523, speed=1, in_map=..., out_map=..., nframes=1024, offset=0) at ../libs/ardour/lv2_plugin.cc:2668
0000008  0x00007fe71873be31 in ARDOUR::PluginInsert::connect_and_run(ARDOUR::BufferSet&, long, long, double, unsigned int, long, bool) (this=
    0x55b18659b010, bufs=..., start=322499, end=323523, speed=1, nframes=1024, offset=0, with_auto=true) at ../libs/ardour/plugin_insert.cc:1109
0000009  0x00007fe71873d88a in ARDOUR::PluginInsert::automate_and_run(ARDOUR::BufferSet&, long, long, double, unsigned int)
    (this=0x55b18659b010, bufs=..., start=322499, end=323523, speed=1, nframes=1024) at ../libs/ardour/plugin_insert.cc:1377
0000010 0x00007fe71873d4b8 in ARDOUR::PluginInsert::run(ARDOUR::BufferSet&, long, long, double, unsigned int, bool)
    (this=0x55b18659b010, bufs=..., start_sample=322499, end_sample=323523, speed=1, nframes=1024) at ../libs/ardour/plugin_insert.cc:1328
0000011 0x00007fe71881c955 in ARDOUR::Route::process_output_buffers(ARDOUR::BufferSet&, long, long, unsigned int, bool, bool) (this=
    0x55b182750600, bufs=..., start_sample=322499, end_sample=323523, nframes=1024, gain_automation_ok=true, run_disk_reader=true) at ../libs/ardour/route.cc:543
0000012 0x00007fe71881da80 in ARDOUR::Route::run_route(long, long, unsigned int, bool, bool)
    (this=0x55b182750600, start_sample=321459, end_sample=322483, nframes=1024, gain_automation_ok=true, run_disk_reader=true) at ../libs/ardour/route.cc:734
0000013 0x00007fe718832332 in ARDOUR::Route::roll(unsigned int, long, long, bool&) (this=0x55b182750600, nframes=1024, start_sample=321459, end_sample=322483, need_butler=@0x7fe6d5fbb95f: false)
    at ../libs/ardour/route.cc:4007
0000014 0x00007fe7183211eb in ARDOUR::Graph::process_one_route(ARDOUR::Route*) (this=0x55b182db4f70, route=0x55b182750600) at ../libs/ardour/graph.cc:544
#15 0x00007fe71881d8b8 in ARDOUR::Route::process() (this=0x55b182750600) at ../libs/ardour/route.cc:705
0000016 0x00007fe71832ae55 in ARDOUR::GraphNode::run(ARDOUR::GraphChain const*) (this=0x55b182750a50, chain=0x7fe6c80038e0) at ../libs/ardour/graphnode.cc:65
#17 0x00007fe71831f9b8 in ARDOUR::Graph::run_one() (this=0x55b182db4f70) at ../libs/ardour/graph.cc:346
0000018 0x00007fe71832011e in ARDOUR::Graph::main_thread() (this=0x55b182db4f70) at ../libs/ardour/graph.cc:427
0000019 0x00007fe71832a579 in boost::_mfi::mf0<void, ARDOUR::Graph>::operator()(ARDOUR::Graph*) const (this=0x7fe6d5fbbef8, p=0x55b182db4f70) at /usr/include/boost/bind/mem_fn_template.hpp:49
0000020 0x00007fe718329c4d in boost::_bi::list1<boost::_bi::value<ARDOUR::Graph*> >::operator()<boost::_mfi::mf0<void, ARDOUR::Graph>, boost::_bi::list0>(boost::_bi::type<void>, boost::_mfi::mf0<void, ARDOUR::Graph>&, boost::_bi::list0&, int) (this=0x7fe6d5fbbf08, f=..., a=...) at /usr/include/boost/bind/bind.hpp:259
0000021 0x00007fe718328dd9 in boost::_bi::bind_t<void, boost::_mfi::mf0<void, ARDOUR::Graph>, boost::_bi::list1<boost::_bi::value<ARDOUR::Graph*> > >::operator()() (this=0x7fe6d5fbbef8)
    at /usr/include/boost/bind/bind.hpp:1294
0000022 0x00007fe7183277ae in boost::detail::function::void_function_obj_invoker0<boost::_bi::bind_t<void, boost::_mfi::mf0<void, ARDOUR::Graph>, boost::_bi::list1<boost::_bi::value<ARDOUR::Graph*> > >, void>::invoke(boost::detail::function::function_buffer&) (function_obj_ptr=...) at /usr/include/boost/function/function_template.hpp:158
0000023 0x000055b17f817ce4 in boost::function0<void>::operator()() const (this=0x7fe6d5fbbef0) at /usr/include/boost/function/function_template.hpp:763
#24 0x00007fe6fa9fb541 in ARDOUR::PulseAudioBackend::pulse_process_thread(void*) (arg=0x55b1834f8fc0) at ../libs/backends/pulseaudio/pulseaudio_backend.cc:732
0000025 0x00007fe715725ea7 in start_thread (arg=<optimized out>) at pthread_create.c:477
0000026 0x00007fe7148d3a2f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
(0026864)
gonsolo   
2022-11-07 10:02   
https://tracker.ardour.org/view.php?id=9049 also crashes at tempo.cc:471.
(0026928)
paul   
2022-11-22 01:24   
should be fixed (crashed here before, now works) with commit f5887b978d4

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9102 [ardour] bugs crash always 2022-11-17 22:57 2022-11-22 00:45
Reporter: Zelv Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Crash when editing MIDI region after loading it as clip
Description: After creating a MIDI region in the timeline, it is possible to load it in the clip launcher. However when trying to further edit the MIDI region, Ardour crashes.
Tags: clip, crash, MIDI region
Steps To Reproduce: 1. Create a new session
2. Add a MIDI track
3. Create a MIDI region with a few notes
4. Load the region in the clip launcher
5. Edit or add notes in the MIDI region
Additional Information:
System Description
Attached Files:
Notes
(0026911)
paul   
2022-11-20 04:43   
Just as a side note: this won't do what you want. The region in the timeline is independent of the one in the clip launcher slot.
(0026926)
Zelv   
2022-11-21 22:54   
Fair enough, I can deal with reloading the region after modifications.

I can see how that could be difficult to handle a shared region between clip and timeline. That could be a nice feature though.
(0026927)
paul   
2022-11-22 00:45   
Actually, it's not hard, and a few months ago, that was how things worked.

The potential for user confusion, however, was too great, so we changed things.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8041 [ardour] features minor have not tried 2020-04-22 08:51 2022-11-21 18:40
Reporter: unfa Platform: PC  
Assigned To: x42 OS: Linux  
Priority: normal OS Version:  
Status: resolved Product Version: 5.12  
Product Build: Resolution: no change required  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Switch to Dummy back-end when exporting in non-realtime using JACK
Description: When i export files from Ardour 5.12 on Windows (using PortAudio driver) - the OS sounds still work fine.

When I do the same on Linux using JACK back-end - Ardour switches JACK to freewheel mode for export (unless realtime export is used).

This causes all other sound to be muted, and fro example playing a video in the browser will play at much higher speed and without sound.

It's nice to be able to watch a video while waiting for the export to complete, but regardless of reasons - I see this as a flaw.

I've managed to work this around by switching to a Dummy backend before exporting.

If Ardour would switch to Dummy whenever exporting in non-realtime mode, the export would work as usual, but the user could still use their JACK server normally, play some music or watch a video while waiting for Ardour to finish.

Not to mention if I'm on a VoIP call with a co-worker and I need to export a sound effect for them, my sound will cut off and that's bad.

The Dummy back-end seems like a simple solution. I could do this manually, but it'd be fantastic if Ardour could do it on it's own.

I see that this might be a bit OS-specific, but this would be a huge life quality improvement for me, and (I guess) other people using Ardour as their daily driver for sound work under Linux. It's not an issue on Windows, and I have no idea how it behaves on Mac.

What do you think?
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: Screenshot_20200423_131352-1.png (62,685 bytes) 2020-04-23 11:18
https://tracker.ardour.org/file_download.php?file_id=3609&type=bug
png
Notes
(0023854)
x42   
2020-04-22 13:38   
The whole point of Ardour/JACK is to allow using external applications in an Ardour Session. Those also need to be included in the export, and switching to Dummy backend would exclude those.

If you don't need this feature, don't use JACK. Like on Windows with PortAudio, prefer Ardour/ALSA (which is also a tad more efficient) or Ardour6/Pulseaudio (if you don't need to record).
Alternatively export using the commandline util /opt/Ardour-5.12.0/bin/ardour5-export (that does use the dummy backend).
(0023859)
unfa   
2020-04-22 16:21   
Oh - I see. I have always kept my Ardour sessions self-contained. Even in the old times of Ardour 2 whenever I used Hydrogen for drums, I would record Hydrogen's output into an audio track first before exporting my Ardour session. I never thought I could route in external software and keep it working. I have heard about using outboard gear (hence the Real-time option), but it never occurred to me I could also use external software.

I use JACK over ALSA, because I often use multiple programs at once, and also I need to use FreeSound very often or reference videos online - if I were to use ALSA, I'd not be able to share my audio I/F with any other program.

I'll see if I can export with the command line utility, though I'll miss the export analysis and summary features. Though maybe I'll create PNG files if I configure that? I doubt that, since these seem to be screenshots of the UI.

Thanks!
(0023860)
paul   
2020-04-22 16:37   
As x42 noted, if you don't need to record, A6 has a PulseAudio backend that does just playback, and allows you to share the interface with other Pulse-using applications.
(0023869)
unfa   
2020-04-22 20:31   
Oh! I missed that! That's interesting - I think it can simplify the work a lot of many people who only sequence and edit, not record!
So far I haven't switched all my work to Ardour6, as there's some bugs I'm waiting to see fixed.

PulseAudio support is mighty neat though! I wonder why doesn't it support capture though?
(0023870)
x42   
2020-04-22 20:55   
Pulseaudio cannot offer reliable capture latency, nor any accurate latency information. So recording overdubs is not possible.

It's also not really suitable for any kind of reliable pro-audio work. The main motivation for this was to offer bluetooth support for guys mixing while traveling.
(0023873)
unfa   
2020-04-23 11:18   
I see. That's gonna be pretty neat.

I wouldn't mind even flawed PulseAudio capture possibility, as for example when I'm doing sound design I record various elements and then edit everything, so timing of my capture is not important.
Though It'd be important that the captured audio is 24-bit (I am not sure if PulseAudio supports more than 16-bit samples?)

Also -I wonder if with the commandline export I can export only selected timeline ranges?

When iterating over sound effects I very often have dozens of CD ranges in my session and I usually export a few at a time to update them.
If I save my session with chosen export ranges, will the commandline utility export only those?
(0023874)
unfa   
2020-04-23 11:37   
I've just tried exporting this session with ardour5-export, but it ended up in a SegFault, so I need to resort to the regular export.
I can try and get a backtrace, but I don't know how to run it in gdb with approperiate commandline arguments.
(0023875)
unfa   
2020-04-23 11:39   
Oh, ok seems like Calf plug-ins can't live in the headless version of Ardour:

ardour5-export[174528]: segfault at 7f7cb00010d8 ip 00007f7c8154c16f sp 00007f7cb00010e0 error 6 in calf.so[7f7c81505000+e6000]

I wonder why is that, but well - that's not Ardour's fault.
(0023876)
unfa   
2020-04-23 11:44   
I've reported the problem to Calf:
https://github.com/calf-studio-gear/calf/issues/249
(0023880)
x42   
2020-04-23 16:55   
Re: "as for example when I'm doing sound design I record various elements and then edit everything, so timing of my capture is not important."

I'm wary of opening Pandora's box. Once that would be possible users will expect it to work. Nobody reads the small print "only use for XXX". Pulse also re-samples when using multiple devices, and all capture settings including volume, are outside or Ardour's control. It is really not suitable to be used in a DAW context.

With some luck pipewire will eventually solve this. PW also supports MIDI (Pulse doesn't).
(0026923)
x42   
2022-11-21 18:40   
The original idea "Switch to Dummy back-end when exporting in non-realtime using JACK" excludes other JACK apps from being exported.
And using external 3rd party apps is the main reason why JACK exists, so this is counterproductive.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8960 [ardour] bugs crash always 2022-09-11 18:59 2022-11-20 18:40
Reporter: secke Platform: x86_64  
Assigned To: OS: Ubuntu  
Priority: normal OS Version: 20.04  
Status: acknowledged 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
Notes
(0026889)
secke   
2022-11-13 17:16   
Problem persists in Ardour-7.1
(0026898)
secke   
2022-11-17 18:00   
Update: Crash doesn't happen when the Faderport is in "Studio One" operation mode.
As that mode is the one that's to be used with Ardour, the cause for the crash is much more esoteric than I thought at first.
(0026899)
x42   
2022-11-17 18:16   
Great to hear that you have figured this out. I would not have thought of that.

I suppose it still is a bug that ardour crashes when the Faderport is not used in Studio One mode.
Ardour should not crash, and yet still somehow inform the user to change the FP to use S1 mode.
(0026918)
secke   
2022-11-20 18:40   
Additional info on how to reproduce:
The device needs to be in "Cubase / Nuendo (MCU)" mode. (Power off, press and hold Next while powering back on, hit Bypass.)

Then activate control surface PreSonus FaderPort2 in Ardour.

Hit Master > Section > Next.

The crash doesn't occur in other modes. (At least not with this sequence of button presses.)

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9108 [ardour] bugs minor always 2022-11-20 18:22 2022-11-20 18:22
Reporter: sollapse Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Changing audio engine state by script fails to update Audio/MIDI menu.
Description: When stopping and starting the audio engine with Lua, the status bar and Audio/MIDI menu still retains is last setting (stopped, when started in the script). The engine however works as expected.
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:
9106 [ardour] bugs crash always 2022-11-20 11:32 2022-11-20 14:07
Reporter: coenplanetc Platform: Ubuntu  
Assigned To: x42 OS: Linux  
Priority: normal OS Version: (any)  
Status: resolved Product Version: 7.1  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Session-conversion from 6 to 7 crashes with segmentation fault
Description: Session is called RAGE
When trying to convert the version-6-session to Ardour 7 it crashes with a Segmentation fault (core dumped)

Base was a session with lots of busses, tracks and plugins but I've cleaned it all up to a stage where there is only one Masterbus, no plugins, no files.
Tags:
Steps To Reproduce: Extract the zip files and open the RAGE.ardour file
Or open the archive-file from within Ardour 7.1.0
In both cases Ardour makes an -6000.ardour backupfile and crashes with the Segmentation fault
Additional Information: Ardour 6.9.0~ds0 (distribution version)
Ardour 7.1.0 (downloaded binary)
Ubuntu Studio 22.04.1 LTS / xfce 4.16
I use Jack 0.9.6 most of the times but I tried it also with Alsa, makes no difference
System Description
Attached Files: RAGE_2022-11-20_111218.ardour-session-archive (3,939 bytes) 2022-11-20 11:32
https://tracker.ardour.org/file_download.php?file_id=4295&type=bug
RAGE_NoConversionTo7Possible.zip (9,683 bytes) 2022-11-20 11:32
https://tracker.ardour.org/file_download.php?file_id=4296&type=bug
Notes
(0026916)
x42   
2022-11-20 13:28   
The issue here is that session's master bus has no MIDI input but a MIDI output.

I'll look into a solution.
(0026917)
x42   
2022-11-20 14:07   
Fixed in 7.1-154-g82512422a7

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9098 [ardour] bugs minor always 2022-11-16 19:25 2022-11-20 04:34
Reporter: gonsolo Platform: Ubuntu  
Assigned To: x42 OS: Linux  
Priority: normal OS Version: (any)  
Status: resolved Product Version: 7.1  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Compile error because glib.h could not be found.
Description: A fix for waf is at:

https://github.com/Ardour/ardour/pull/757
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0026896)
gonsolo   
2022-11-16 19:27   
I'm not sure about the minimum version so I just picked the one on my distribution.
(0026909)
x42   
2022-11-20 04:34   
Should be fixed since 7.1-108

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8403 [ardour] bugs minor random 2020-09-13 13:31 2022-11-20 01:17
Reporter: unfa Platform:  
Assigned To: x42 OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 6.3  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Export silence trim is very hard to get working reliably
Description: I'm using export silence trim function in Ardour to export sounds effects for game engines.

I've always had issues with that feature, as it seems to be very pick about input signals.

Example from a job I'm doing currently:

At first trimming wouldn't work unless I disabled Ardour's export dithering - checking the exported files shown dithering noise was present and it stopped trimming from happening - solution: dither after trimming? (EDIT: I've found this to not be true in all cases - read more later).

I've disabled the dither and used NotJustAnotherDither by AirWindows instead, after a Master Limiter and before an LSP noise gate that applied 72 dB of gain reduction if signal was dropping below -60 dB (to make sure the dither noise is not going to trip up the trimming). This worked for a while, but then it stopped and I have no idea why.

Disabling the NotJustAnotherDither plug-in didn't fix it.
Also duplicating the LSP Gate 2 times for a total of 216 dB of gain reduction didn't help either.

I think silence trim needs some work - it's a very good idea, and I'd love to have this working reliably, as it's extremely helpful for working with audio for video games.

Sound effects or music loops are much easier to get working properly in a game engine with this feature, as it's much less error prone than manually aligning export markers.
Because of various issues the only real workaround is to bounce the master bus output to another track and truncate it manually there - which is laborious and error-prone.

---

I've checked my master bus with x42 Bit Meter plug-in - the average level was around - 400 dB, yet trim still was tripped by that.
I've added a Hard Gate plug-in set to 0.0001 threshold (the lowest possible value) and it seems to work now.

I suspect some reverb tail is producing these extremely low level sounds.

Interestingly after I've added this Hard Gate, Ardour's Shaped dither doesn't break the Trim function any more.

Could the export trim function have a customizable threshold and attack/release maybe?
I'm not sure how to get this to work reliably without using a bunch of plug-ins in the master bus and risking quality degradation (the hard gate doesn't seem like a great option, but I don't hear issues, and it fixed the trimming for me).
Tags: export, silence trim
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0026907)
x42   
2022-11-20 01:16   
Since Ardour 6.7 the default is -90 dBFS.
Silence trimming is performed before decimation on the float signal, and the given value is more than a factor of two above the max S/N of undithered 16bit audio.
Overall dithering noise (eg. Harrison's channel dithering) is also well below that level.

GIven that it is common to loudness normalize to -23 LUFS (EBU-R 128), this allows for 60dB S/N which is reasonable. Cases that require a steeper cut-off should likely use a expander/gate.
(0026908)
x42   
2022-11-20 01:17   
Ardour v7 will have pushed a config-change to set the value to -90

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9104 [ardour] features feature N/A 2022-11-18 08:56 2022-11-18 08:56
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: Feature request: MIDI note info when moving with arrow keys
Description: In Internal Edit Mode (E-mode), when hovering the mouse over a MIDI note, the note info is displayed.
"B4 0000071 etc"

It would be really neat if this info was also displayed when editing with your arrow keys.
The arrow keys are great for moving MIDI notes up and down without losing their positioning, but you have to keep your head pretty straight to remember if 6 steps down gets you to an F or an E.

Really no big issue, but I guess it wouldn't be the most difficult to implement either. And it would be really handy.
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:
9103 [ardour] other trivial always 2022-11-17 23:29 2022-11-17 23:29
Reporter: prokoudine Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Marker discrepancies
Description: ## Creating single markers

All new markers can be added via right-click menu. However, modifier + click/double-click combination doesn't work the same way between different rulers with single markers.

- BBT markers: a new BBT marker can only be added via right-click menu, there is no modifier + click combo.

- Time signature: Ctrl + single click opens a dialog to specify settings, a marker with some default value is not created at that point.

- Tempo: Ctrl + single click places a marker on the ruler, where value is copied from the closest marker to the left of it. Ctrl + double-click creates a marker and opens a dialog to specify settings

- CD Markers: Ctrl + single click places a marker on the ruler and automatically names it. Ctrl + double-click additionally opens a dialog to specify settings

- Location markers: Shift/Ctrl + single click places a marker on the ruler and automatically names it. Shift/Ctrl + double-click additionally opens a dialog to specify settings

- Cue markers: Ctrl + single click places a marker on the ruler and automatically names it. Ctrl + double-click additionally opens a dialog to specify a different name for the marker, however this information is only visible in the Ranges & Marks sidebar.

To reiterate, Ardour seems to gravitate towards the workflow where:

- Ctrl + click places a marker with some default values
- Ctrl + double-click places a marker with some default values and opens the dialog to edit settings

However, not every ruler with markers has that behavior. Moreover, BBT markers don't even respond to modifier + click/double-click.

## Creating paired markers / Range markers

Range markers (as well as loop/punch ranges) can be created directly on the ruler by pressing a modifier, then clicking and dragging.

Range Markers: both Shift and Ctrl work as that modifier. With Ctrl, markers are named using the 'unnamedN' pattern, with Shift, they are 'skipN' (where N is an integer that starts at 1 and is incremented by 1).

Loop/Punch ranges: only Ctrl works as that modifier

CD markers: only Ctrl works as modifier for creating range markers, while Ctrl + Click creates single markers

## Selecting markers

Ardour uses two different ways to tell that a marker is selected: 1) recoloring the background of a marker, 2) rendering the vertical line.

All marker types except one (cue markers) only render the vertical line and recolor a marker's background on hover only. Cue markers do it both ways: selected marker retains the "selected" background color _and_ renders a vertical line.

On top of that, TS and Tempo markers have the color of selected location/cue markers. Which means there is not much visual confirmation for selecting a TS or a tempo marker. They always look selected.

Selecting multiple markers with shift+click affects all rulers except for BBT, TS, and tempo. This doesn't seem to be an expected behavior, while both use cases (moving a range of markers in one ruler or all rulers) have a place. So there should be a way for the user to select a range of consecutive markers on just one ruler or all rulers.

## Moving Markers

"If you happen to drag exactly where the red vertical line of a marker is, then it will drag that marker. A microscopic, 1-pixel-wide interaction area in a UI [is not usable], therefore, it shouldn't be an interactable UI element..."

## Right-click options

All types of markers can be hidden and/or locked. Some types of markers expose this option in the right-click menu and some don't.

Hiding not available in:

- Time signature
- Tempo
- Loop/Punch ranges
- Cue markers

Locking not available in:

- Time signature
- Tempo
- Range markers
- Loop/Punch ranges
- Cue markers

Additionally, the same command (Hide) is called differently. It's _Hide range_ for range markers yet just _Hide_ for CD markers.

## Unexpected behavior

Ctrl + Shift + click creates a copy of the selected location maker and hides the original.
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:
9101 [ardour] bugs minor always 2022-11-17 21:22 2022-11-17 21:24
Reporter: cooltehno_bugs 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: Bug (not able to improve) Blueberry theme: unable to resolve text visibility in the clip launch section
Description: We have almost invisible light text on the light area in the clip launching window in Blueberry Milk theme.

We have two ways to resolve a problem:
1. Make the text -> dark - that is impossible! - There are no items & aliases in the theme file. I've made "one color palette" - it has no result - the text stays the same.

2. Make the area -> dark - that is possible through the changing pallete color: Color name="theme:bg", BUT this involve almost all main items of the light theme.

I've made a list of Aliases, where the "theme:bg" has a place:
    <ColorAlias name="arrange base" alias="theme:bg"/>
    <ColorAlias name="audio automation track fill" alias="theme:bg"/>
    <ColorAlias name="gtk_background" alias="theme:bg"/>
    <ColorAlias name="inactive group tab" alias="theme:bg"/>
    <ColorAlias name="meterbridge label: fill" alias="theme:bg"/>
    <ColorAlias name="midi device: fill active" alias="theme:bg"/>
    <ColorAlias name="monitor section processors toggle: fill" alias="theme:bg"/>
    <ColorAlias name="monitor section processors toggle: fill active" alias="theme:bg"/>
    <ColorAlias name="monitor section solo model: fill active" alias="theme:bg"/>
    <ColorAlias name="monitor section solo option: fill active" alias="theme:bg"/>
    <ColorAlias name="processor control knob" alias="theme:bg"/>
    <ColorAlias name="stereo panner rule" alias="theme:bg"/>
    <ColorAlias name="tracknumber label: fill" alias="theme:bg"/>

 - no one of them can control mentioned clip area.

That mean we need a new SEPARATE Item for clip launching area.
Tags:
Steps To Reproduce:
Additional Information: "One color palette" with unchanged text and desired "dark (violet)" clip launching area pictures - are attached.
Attached Files: palette_independent_text.png (72,805 bytes) 2022-11-17 21:22
https://tracker.ardour.org/file_download.php?file_id=4290&type=bug
png

propose_separate_item.png (191,274 bytes) 2022-11-17 21:22
https://tracker.ardour.org/file_download.php?file_id=4291&type=bug
png
Notes
(0026900)
cooltehno_bugs   
2022-11-17 21:24   
"That mean we need a new SEPARATE Item for clip launching area."

OR - we need a new SEPARATE Item for the clip text (to make it dark)

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9097 [ardour] features feature N/A 2022-11-16 14:38 2022-11-16 14:43
Reporter: Attila S. Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Make “Plugin analysis” a standalone thing, to be able to use it with graphic plugin ui
Description: In my view it would a be good thing to be able to use the “Plugin analysis” tool independent of the “Edit with generic controls” window.

It would be a good thing to launch it from the right lick menu like the “Edit with generic controls”, or from the plugin window’s toolbar with a button, or something like this, and it would open in a standalone own window.

(Thank You in advance for considering this.)
Tags:
Steps To Reproduce:
Additional Information: Probably, problem 0009074 could be solved with this.
https://tracker.ardour.org/view.php?id=9074
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9074 [ardour] bugs minor always 2022-11-06 15:22 2022-11-16 14:43
Reporter: Attila S. Platform: GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Not enough space for the “Plugin analysis” section
Description: For the plugins in the “Edit with generic controls” window the plugin controls often listed in a way that for the additional “Plugin analysis” section not enough space left on the screen/windows. See the attached screenshot.

Probably the controls section should be resizable and scrollable.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files: not-enough-space-for-plugin-analysis.png (248,634 bytes) 2022-11-06 15:22
https://tracker.ardour.org/file_download.php?file_id=4277&type=bug
png
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9095 [ardour] bugs minor always 2022-11-16 06:46 2022-11-16 06:47
Reporter: stefan-franz Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Eventeditor - On edition a value with the mouse wheel, the list jumps up or down if the rotation direction is chenged
Description: It the event editor is a great feature, that e.g i can chose more events and with the mouse wheel the value (e.g. velocity) for all selected can edited.

But if i change the rotation direction, the list is moved ant some other events were edited.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0026894)
stefan-franz   
2022-11-16 06:47   
I meant the Midi Event Editor of course.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9033 [ardour] bugs crash always 2022-10-24 10:15 2022-11-16 03:33
Reporter: Thomas Krocker Platform: Microsoft  
Assigned To: x42 OS: Windows  
Priority: immediate OS Version: 10  
Status: resolved Product Version: 7.0  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ardour 7.0 crashes and freezes Windows 10 when deleting a preset in Midi Chord.
Description: By clicking on the delete icon in Midi Chord, Ardor 7.0 crashes and freezes Windows 10.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files: Ardour 7 Absturz Midi Chord.jpg (170,856 bytes) 2022-10-24 10:15
https://tracker.ardour.org/file_download.php?file_id=4246&type=bug
jpg
Notes
(0026687)
x42   
2022-10-24 12:07   
Confirmed. Those "factory presets" cannot be deleted, and trying do to so currently causes crashes in libserd/sord.
(0026893)
x42   
2022-11-16 03:33   
Fixed since Ardour 7.1-86-g6c3a1d98fe

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9072 [ardour] features feature have not tried 2022-11-06 07:44 2022-11-15 23:48
Reporter: ksawerytreningowski Platform:  
Assigned To: OS:  
Priority: immediate OS Version:  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Midi Velocity Lanes
Description: Non destrictive or destructive edition - Midi Velocity Lanes.
One or many velocity lanes for a midi region or track (versions)
Tags: Midi velocity lanes
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:
5608 [ardour] features feature N/A 2013-07-21 15:55 2022-11-15 23:48
Reporter: Leatuspenguin 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: Velocity track idea
Description: The one midi feature which is currently lacking is the lack of proper velocity editing. Unless there's something i'm unaware of, the only current way is to edit individual note velocity, or groups of notes together. The only visual way of telling the velocities of multiple notes is via colour intensity.

One solution to this, and without bringing a whole new window into the equation, would be to make use of an automation track to edit note velocities. I have included a mock up, influenced by qtractors velocity editing.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: velocity track.png (137,658 bytes) 2013-07-21 15:55
https://tracker.ardour.org/file_download.php?file_id=2217&type=bug
png

Ardour_MIDI_Velocity_channel.png (31,833 bytes) 2014-12-24 02:08
https://tracker.ardour.org/file_download.php?file_id=2488&type=bug
png

out.patch (5,825 bytes) 2018-06-26 17:31
https://tracker.ardour.org/file_download.php?file_id=3402&type=bug
Velocity_Editor.png (201,856 bytes) 2018-06-29 05:49
https://tracker.ardour.org/file_download.php?file_id=3404&type=bug
png

thinnervline_01.patch (1,055 bytes) 2018-07-08 06:14
https://tracker.ardour.org/file_download.php?file_id=3409&type=bug
Simple_Velocity_Automation_Lane.jpg (115,291 bytes) 2018-07-13 03:38
https://tracker.ardour.org/file_download.php?file_id=3412&type=bug
jpg

ghostlollipop_patch.diff (3,928 bytes) 2018-07-17 10:16
https://tracker.ardour.org/file_download.php?file_id=3413&type=bug
Notes
(0015150)
x42   
2013-07-21 16:46   
Do you have any idea how that can work with polyphony, as well?
(0015151)
Leatuspenguin   
2013-07-21 17:44   
I never thought about that. It was just an idea i had that i thought I'd throw out there. Thinking about it now, i see what you mean. Automation tracks only works on one parameter at a time. So there's no way it could work with an automation track without a lot of work? Is it feasible at all or are there any other thoughts about velocity editing at the moment?
(0015158)
paul   
2013-07-23 02:46   
its not a problem with automation track limits per se.

its a problem with conditions that involve chords. how do you edit the velocity of just one of the notes?
(0015159)
paul   
2013-07-23 02:48   
i suspect lines, not bar charts, will be the likely solution to this, btw. doesn't fully solve the polyphony design problem, but it would allow editing once it was clear what line affected which notes.
(0015164)
Leatuspenguin   
2013-07-23 06:58   
(Last edited: 2013-07-23 11:06)
So the issue isn't a technical one regarding polyphony on an automation track? It's to do with how it would be visually implemented? Other daws allow you to select the note with your mouse to bring it's velocity bar to the top so you can edit it, if there are multiple event notes at the same time. Would something similar not work? Or have I misunderstood?

(0016075)
naught101   
2014-12-23 14:10   
Good editors I've seen have a circle for each note, which can be moved up or down. You could do the same thing with a line that goes out horizontally to the end of the note.
(0016080)
drobilla   
2014-12-23 19:27   
Bars suck. If all we really need is the ability to edit in ramps and so on, seems we can add that easily enough without a clunky bar thing that's confusing as soon as any polyphony is around.
(0016081)
naught101   
2014-12-24 02:08   
UI proposal: designed to fit with the current automation UI design.

The example doesn't include chords, but you can see how it would work for them. Just the red squares are draggable. The green lines are just indicators. If notes are selected in the actual track, then those notes are brought to the top of the stack in the velocity channel, thus allowing chord notes to be velocity-edited independently (if the chord has the same velocity on all notes, just select one note in the track, edit the velocity, select another note, repeat, etc.). If multiple notes are selected in the track, moving one of them in the velocity editor should move all of them.
(0016085)
florianb   
2014-12-24 02:52   
(Last edited: 2014-12-24 02:53)
Love this idea for 3 another reasons:
 
1- It helps a lot to visualize the timing of the notes.
I often have this problem when editing piano notes. e.g. there are 4 notes that are supposed to be at equal distance from each other, but not really on the tempo because plenty of emotion... and something sounds wrong in their timing but I can't hear where because they are too fast or too subtle... It helps a lot to see them on a horizontal timeline. Problems become obvious this way.
 
2- Currently, when scrolling for velocity, each step of scroll is an Undo/Redo action... So you have to undo 8 times to put back your 48 to the 40 it was before you scroll.
Of course this issue could be fixed another way.
 
3. We could get rid of the Alt+Scroll x10 velocity that is very confusing because of the Alt+Scroll for vertical zoom (which is fantastic). I bet nobody knows about this anyway, or they discovered it by mistake when trying to Y-zoom.
This way, we could simply click for large velocity steps.

(0016096)
drobilla   
2014-12-25 01:29   
? The notes *are* on a horizontal timeline. How does a velocity thing make any difference there?

I'm not fundamentally opposed to a separate velocity thing, but it's a massive mount of work completely unlike anything else we currently have for little to no mentioned benefit. I'd rather see a list of exactly what things users need to accomplish that we can't currently do (e.g. ramp up velocity from here to there) than "hey let's just blindly make a bar thing because some other programs do"...

e.g. it seems to me that a velocity tool that lets you edit the velocity of notes in linear ways might be (almost) universally superior. Perhaps we should have a bar thingie, and the benefits outweight the polyphony problems. So, what benefits?

In other words: justify with something other than "program X did it". If "we" are going to do a ton of work on velocity editing, it might as well be thought out properly first...

I am also interested in these questions because making the on-note velocity editing more powerful is something that is *way* more feasible to do relatively shortly than implementing this, and would be good regardless of whether or not we eventually have a bar thing.
(0016099)
florianb   
2014-12-25 01:48   
@drobilla, I don't know about the priority, there are definitely some bugs that I would consider more urgent than this. 0006055 e.g. or the fact that Ardour does not send any NoteOff in record mode. (I need to create a report for this)
 
But my point 1- above is clearly important. Let me show you why a horizontal view is important, what it is, and what it's not...
http://dl.florianbador.com/20141224-ardour-5608.png
In this example, how do you know that the 4 piano notes following my playhead are rhythmically at equal distance from each other?
It's a piano part, not a drum, so it's not supposed to be exactly on a beat, it's just supposed to make sense emotionally.
In this example, I can hear something wrong in the timing of these notes but I can't explain it. If I could visualize these notes with vertical bars next to each other, the problem would become obvious.
 
In other words, with vertical bars, the visualization of the notes timing (X) is not disturbed by their frequency (Y).
 
Having velocity bars would help a lot to visualize the rhythmical side of the music.
I don't care what other programs use.
How urgent is it? I don't know, you judge...
I still think this x10 velocity steps with Alt+Scroll should already disappear.
(0016102)
naught101   
2014-12-26 01:12   
A quick solution that would work in the mean-time would be to <Modifier>+Drag changes the velocity of a note. Scrollwheel is not very precise, and it also doesn't easily let you define multiple scrolls as one event (as opposed to click and release).

But, there are good reasons that a height-based visualisation (not bars - I wouldn't describe my UI design as bars). For one, human colour perception is not that accurate - we don't really have a way of estimating the absolute value of something from the luminosity/saturation, as with the current colour scheme. You *might* be able to improve that by adding a hue change with velocity too (e.g. red->white->blue). We're better at comparing relative colours, but I don't think many people have the ability to easily tell the difference between a note at 65 velocity and one at 70 (in the current color scheme, but it's not going to be easy in any colour scheme), but that can make a big difference, depending on the synth/sampler.

The fundamental problem is that you're trying to show 3 variables (time, pitch, velocity) in 2 dimensions. There are lots of visual variables you could use (e.g. http://jcsites.juniata.edu/faculty/rhodes/ida/images/Figure_6_8.jpg ), but size and colour are probably the only ones that might work in this situation, and size also has problems (like overlapping).

Adding a velocity bar allows you to have two correlated plots of 2 variables each. It's a pretty concise way of displaying and allowing manipulation of the information, without having too much complexity (you could make it 3D, and it'd work, but it'd get visually confusing :D ). If you add a height-guide grid behind the plot (e.g. every 32 velocity, or something), then you get *really good* absolute and relative velocity estimation.
(0016103)
florianb   
2014-12-26 01:21   
(Last edited: 2014-12-26 01:21)
Scroll is VERY precise (and very handy) One scroll step is 1 step of velocity.
Velocity upon scroll is IMO the best idea Ardour ever had... unless you have a crappy mouse.

(0016696)
rgwan   
2015-05-16 15:45   
I think Velocity TRACK is a GREAT idea to edit velocity
(0016871)
ssj71   
2015-07-14 03:49   
I think the goal is to achieve easy "fader rides" for crescendos etc. I propose the second mockup be approached but on a mouse drag to change velocities, apply it to all notes of the chord the same way the fader does on a midi track (scale all notes by the same factor). You can scale the highest velocity note to the new velocity or have the behavior in the preferences (highest velocity note, highest pitch note, lowest etc). Basically automating the gain fader from the mixer but applying the effect to each note event.

If an individual note is clicked and dragged in the "velocity track" it changes velocity, but you can also do quick shaping of the overall dynamics a passage through a mouse drag. Perhaps there is a better way than an extra track or bar to achieve this, but I think this is a pretty reasonable definition of the behavior for chords. I would sure appreciate a change to quickly shape drum pattern dynamics the same way I used to do in hydrogen (which does a velocity bar for whichever drum/note is currently selected).
(0019438)
GMaq   
2017-02-26 00:41   
(Last edited: 2017-02-26 00:42)
*Added note from IRC discussion on Feb.25/2017

In asking about the status of this feature on IRC it was suggested that a barrier to integrating this feature was how to handle 'chords' on the MIDI timeline (or multiple notes in the same vertical timeline grid axis). In my experience with other DAW's it occurred to me that visual MIDI velocity editing where the velocity is represented by a vertical 'bar' is often handled by selecting only one group of notes at a time on the same horizontal key/note path. Below are 2 examples from screenshots:

Example 1: http://bandshed.net/images/screenshots/H2.png

Example one is a screenshot of the Hydrogen Drum Machine, as you can see in it's editor window keys/notes (or drumkit pieces) can be selected on the left hand side which highlights the horizontal grid axis and exposes the vertical visual 'bars' to change the velocity of ONLY the notes on that grid axis (or note key). This allows individual adjustment of only single notes at a time without affecting note velocities on other note keys.

Example 2: http://bandshed.net/images/screenshots/EnergyXT.png

Example two is a screenshot of EnergyXT which incidentally also shares the ideology of MIDI within a timeline track like Ardour. EnergyXT does not allow selecting note keys on it's MIDI keyboard on the left like Hydrogen does however if multiple notes are 'drag-selected' then their velocity bars appear in the 'Velocity' lane under the grid. This also allows selection of individual notes on the same horizontal grid axis without changing the velocity of other notes.

This is how 2 other Linux grid-based editors handle visual velocity editing of notes, there are more examples like Seq24...

Perhaps the addition of a new MIDI type or class of track (ie MIDI-Drum track) could incorporate the suggested visual velocity drawing features without modifying or making changes to the existing scroll wheel features in Ardours existing MIDI tracks. In my own workflow and discussion with users it seems this kind of in-depth visual velocity note editing is most often employed in drum and percussion MIDI tracks.

PLEASE consider adding this feature as it is present in almost every other MIDI-capable DAW on every platform and is very much a standard and expected method of drum sequencing, I don't think this is a feature Ardour/Mixbus should be without.

Thanks for reading,
Glen

(0019440)
rghvdberg   
2017-02-26 09:54   
I would like to add that in order for the velocity track/lane to be really useful, it's should be possible to drag a line across several events to adjust the velocity.
(0019445)
GMaq   
2017-02-26 14:57   
(Last edited: 2017-02-26 20:46)
Hi,

@rghvdberg

Good point! Most DAW's employing vertical bars also allow to draw ramps and curves across the velocity 'bars', so this would be desirable as well.

Added Example 3: http://bandshed.net/images/screenshots/ReaperMIDI.png
                 http://bandshed.net/images/screenshots/ReaperMIDI2.png

This example is showing Reaper (Native Linux Version) and it actually combines the features shown above, so a note/key remains highlighted (in pink) and notes shown across that horizontal axis can then be edited without affecting other notes. Actually the Reaper editor is quite full-featured and also shows the numerical velocity values on the drawn note displayed on the grid as well as handling velocity bars of chords in different colors depending on the note selected.

(0020259)
alexmitchellmus   
2018-04-19 03:55   
(Last edited: 2018-04-19 06:14)
I think an in-region MIDI layering system could be used to show additional information for MIDI notes. Data displayed could be selected (flags?) in a layer menu- which would show a graphical, editable overlay. (editing dependent on style and sort of data)

Such overlays could be velocity lines drawn into the notes- and paired with Color, (and a Velocity Track) could make editing of MIDI velocities clearer- and easier for the end user.

The development of a MIDI overlay system, could also be the first step to enable other data that is relevant per note (such as MPE data) to be displayed. A user could choose to enable velocity / pressure / bend etc... all at once (different color automation?) or only one at a time.

Alternatively MPE data may only be shown per selected note, however having an overview of all events that occur in a MIDI region is very powerful, and allows fast editing.

To speed up editing velocity information, it may be necessary to have a dedicated Velocity tool, allows the user to left-click onto a note, and drag while holding down the left-button, to change the velocity.

A few mockups (painted on with Krita - not accurate):

MIDI Velocity in Note:
https://photos.app.goo.gl/fNC4yzKd0Fh7pV323

MIDI MPE Data in Note:
https://photos.app.goo.gl/KOqyF4hTB4WrUdaQ2

(0020303)
ssj71   
2018-06-20 18:43   
(Last edited: 2018-06-20 18:44)
I think that visualizes the event values nicely, but certainly doesn't provide an easy way to manipulate them. I still think that the biggest need is to be able to quickly "draw" dynamics, the same way you can with fader automation on an audio track. I think a lollipop thing to visualize AND manipulate the velocity info, be it overlay or another lane is the most logical way, though it probably needs a few editing modes like snap to value and scale to support a few use cases. I can't think of any way to do this that isn't a departure from current capabilities in ardour.

"To speed up editing velocity information, it may be necessary to have a dedicated Velocity tool, allows the user to left-click onto a note, and drag while holding down the left-button, to change the velocity."
I don't see that as much improvement over the current situation of using mousewheel and color to visualize. I think rghvdberg's point is the essence of this feature request: 1 click+drag to manipulate many notes' velocities.

The problem remains that note events have 3 degrees of freedom (4 if you include channel) and we only have 2D screens to visualize and edit on. When Ardour VR comes out we'll laugh that this was ever an issue. ;)

(0020304)
naught101   
2018-06-21 03:38   
As far as editing goes, a "multiplication ramp" tool might be good, and require very little in the way of new interface.

For example:

1. Select a bunch of notes
2. context menu -> velocity ramp
3. Draw a line in the current midi track, where the bottom of the track = 0, and the top = 1 (or 2?).
4. When the ramp is finished, multiply each note's current velocity value by the value at the corresponding position in the ramp.

This would be nice because it would allow you to maintain some of the relative variation between consecutive notes (rather than just over-writing the values.

The line drawing could have a couple of different options: 2 or more points (linear ramps in between), bezier curves, or free-hand draw. Hit enter to finish and apply the ramp.

If there's a tool configuration dialogue, it could include things like adding humanisation to the ramp (add a random component from 0-50%).
(0020305)
alexmitchellmus   
2018-06-25 10:22   
(Last edited: 2018-06-25 10:54)
VIEW NOTE VELOCITY WHEN NOTE IS SELECTED:
I put together a mock-up in Ardour doing this to gtk2_ardour/note_base.h:

inline static uint32_t meter_style_fill_color(uint8_t vel, bool selected) {
    /*
     if (selected) {
     return _selected_mod_col;
     } else
     */

Example:
https://www.youtube.com/watch?v=xMjDTRr5FO0

I experimented with other ideas:
* Dimming color of note outline
* Dimming color of note fill

However it was not clear to me when I was using Ardour which notes were selected.

If the outline can become 2 pixels then maybe these other methods would work better. However I think that 1 pixel has been chosen for a reason. (maybe only when selected the outline becomes 2 pixels?)

Also this video outlines an issue when changing multiple notes velocities. (which is already evident to any user of MIDI and Ardour) Which is that once the MIDI velocity becomes 0 or 127 there is no way to adjust the additional notes up or down.

Other software solves this issue by saturating the high and low values.

However due to Ardour using the scrollwheel for Velocity adjustment it makes it impossible to calculate 'velocity change start' events. As there can always be velocity change events.

In other software the start event is simply left click when using a dedicated velocity tool. Thus the delta of the mouse movement can be translated to velocity up and down.(Which gives the user the ability to decide how much to move the velocity without loosing too much velocity information for saturated values.)

NOTE:
The only issue with my solution is if the user sets one of the three velocity colors to the same as the selected color there will be no way to see selected notes. However as all colors are user changeable, this could be easily fixed by the user by selecting a 'selected color' that is not present in the velocity colors.

(0020310)
alexmitchellmus   
2018-06-26 16:32   
(Last edited: 2018-06-26 17:40)
Here is a concept of placing velocity line 'inside' each MIDI note:

https://photos.app.goo.gl/C28ahFYy7qDxBwRu6

https://www.youtube.com/watch?v=M_nsnZYAAMA&feature=youtu.be

Combined with the above: VIEW NOTE VELOCITY WHEN NOTE IS SELECTED

Also increased the outline size of all MIDI notes to 2px (originally 1px)

(out.patch above is a Git patch that contains this working concept. Not a pull request, or intended for production- only to work out ideas)

(0020316)
alexmitchellmus   
2018-06-29 05:54   
(Last edited: 2018-06-30 12:11)
+---------------------- IDEA ONLY------------------------+
                   I am not even 100% I like it myself
   posted to build a conversation around Velocity Editing
 +----------------------------------------------------------+
I uploaded an image of an 'In Region' Note Velocity Editor.

The idea is to be able to select notes, then right-click and be able to select from the Note menu the "Velocity Editor".

The Velocity editor would then show (as in the mock-up) the range of notes selected, and show a lollypop graph above the highest selected note.

It would be good to have a 'pen' tool, (for freehand drawing of velocities), and also a bezier curve tool (to allow any sort of velocity ramp to be drawn).

Any note that was not selected (when entering the tool would not be able to be edited. Possibly notes could be included and excluded on-the-fly while the tool is activated?

If notes overlap (as in same temporal position, then the drawn curve velocity would effect all notes (and give them all the same velocity for that time).

There would also be an exit box on the top right to close the tool, and return to normal note editing.

(0020317)
paul   
2018-07-03 15:29   
alex: the master branch now has the basics of your patch, reimplemented as discussed on IRC. What's missing is color management. I think that's all.
(0020318)
paul   
2018-07-03 15:44   
I set up the code to automatically compute the right color based on the fill color. I think that HSV::opposite() is probably too radical .. try playing with HSV::darker() ... ?
(0020319)
paul   
2018-07-03 16:55   
color now works as it did in your patch.
(0020322)
paul   
2018-07-03 20:49   
and the bars can be turned on and off.
(0020345)
alexmitchellmus   
2018-07-06 04:23   
(Last edited: 2018-07-08 11:29)
Absolutely amazing work Paul! Thank you so much for taking the time to implement this.

Here are some additional thoughts (in no order) that I am thinking could help MIDI editing in Ardour work better. (some dot points are simply changing settings- or adding a preference):


* A way to edit velocity of multiple notes (as per this thread) as either an overlay or lane.
* Clearly showing MIDI regions (currently zoomed out- and in, its a bit hard to see the MIDI region from the canvas)-Theme:Cubasish does this well.
* MIDI Region (and Audio Region) end loop tool (drag end of region to loop, loop connects to same region, but can be changed in future edit.
* Making the outline of the white/black note rows able to be translucent, (like the white/black note row colors are) Currently the row outlines can become very busy visually, and actually don't help in locating which note is which as everything looks white(or the set color)
*(DONE) Velocity bar can be thinner? And also able to not show based on note vertical/horizontal height (this could already work).
* In note text (note name and velocity) and/or with velocity? EG: "A#4:127"
* Ability to change note outline thickness (currently 1px, could be 2px?) this may make a good preference.
* Smarter track zooming (when making track vertically larger) the MIDI region could expand to show more content? Instead of simply zooming in?
* When moving a note up/down highlight the whole note bar that it is currently on.
* Resound MIDI notes while changing velocity (as this is an audio software, it is good to hear the note velocity as well as see it)
* For resounding MIDI notes it may be better to have a dedicated velocity tool (or use the current 'Internal Edit Tool' to LMB a note and drag up/down to change velocity) as currently both 'DRAW MODE TOOL' and 'INTERNAL EDIT TOOL' have the same behavior when LMB clicking. (possibly we can use the middle mouse button for velocity change? MMB could be utilized more)
*(DONE) More note state colors: Currently there are 3, which only shows visually Low, Mid, High. [0,64,127] 5 Note states would show: Min, Low, Mid, High, Max. [0,32,64,96,127]

Changes to "DRAW MODE TOOL" & "INTERNAL EDIT TOOL":

Currently RMB is not used for anything in Draw mode (when no notes are selected), it could be used to 'highlight notes' which can then also be moved with the same tool (LMB).
Then we don't need to worry about moving notes with the "Internal Edit Tool". Thus possibly we should be able to control velocity when LMB onto the selected notes in "Internal Edit". (currently both Note Edit, and Internal Edit both do same thing, and I wouldn't consider moving notes to be 'internally editing notes', rather editing 'note content' would be internal. Velocity is currently one of the only internal 'note' attributes we can edit.

If MPE is implemented, 'Internal Edit' could also be used for those values 'inside' notes as well (because LMB would no longer move the whole note):

Per-Note:
* Note-on (strike)
* Note-off (lift)
* Aftertouch (press)
* Pitch-Bend, X-Axis (glide)
* Y-Axis (slide)

If (in the future) MPE is implemented, then showing 'internal' velocity bars is simply just one attribute of "show internal note data". Thus we should be able to select (per track) what sort of internal data we want to display (and edit).

Already there could be two modes for "show velocity bars", Note-on velocity, and Note-off.

(0020350)
alexmitchellmus   
2018-07-08 06:16   
(Last edited: 2018-07-08 11:28)
I attached a patch to make the in-note horizontal velocity lines thinner, with a 1px gap at either end. I think this looks a bit less visually imposing.

see: 'thinnervline_01.patch' above

Screenshot: https://photos.app.goo.gl/dayGEAZuG976G6QL7

(0020351)
alexmitchellmus   
2018-07-08 07:44   
(Last edited: 2018-07-08 11:35)
Another idea I had for a solution to the 'lollipop' display. (Not implemented)

How about showing selected notes velocities vertically as an overlay on the piano roll editor.

https://photos.app.goo.gl/m4ArvA7woFQNRwqE7

User would:

1) Select multiple notes (or one note)
2) RMB notes and select from menu "Lollipop Editor"
3) Lollipop editor shows as overlay on screen, (only selected notes are displayed)
4) Freehand draw with LMB
5) Vector draw with RMB (click to create two points to draw a line between)
6) RETURN key to apply line values to note velocities
7) ESC key to leave "Lollipop Editor" mode

(0020355)
alexmitchellmus   
2018-07-13 03:43   
(Last edited: 2018-07-13 03:59)
Having thought about this for a while, I think that actually a simple velocity automation lane would suffice. (Simple, as in the ideas that I have proposed previous were probably quite complex- not implementation).

Mockup "Simple_Velocity_Autiomation_Lane.jpg"

To solve the 'polyphony issue' I would suggest to only be able to edit selected notes. As this is an automation lane (I know technically its not automation) but due to there being another lane, the user would be able to add or remove editable velocity lollipops by selection in the main midi region view.

Possibly a first iteration of this idea lane could simply be drawing velocity with the pen tool, or changing velocity up - down. No tools for velocity ramps - lines etc. which could come later.

(0020357)
alexmitchellmus   
2018-07-17 09:00   
(Last edited: 2018-07-17 14:17)
Here is an example of a rudimentary (read Hack) change I made to Ghostregions that displays their notes as lollipops in an automation view.

https://youtu.be/1wc2YDuLIjw

Currently there is no editing, but it at least shows what it 'could' look like in Ardour. The lollipop lane is currently just an automation track, (without any automation in it).

I have attached ghostlollipop_patch.diff for anyone interested.

I can see this working such as:

* Automation header menu has 'velocity' checkbox
* When 'velocity' checkbox is toggled, a velocity layer is added
* The velocity lane will always be underneath the associated track
* If no MIDI notes are selected in a MIDI region, then all lollipops will be editable
* If there are selected MIDI notes then only those would be editable in the velocity lane (to preserve polyphonic velocity editing)
* Access to two tools: Pen (to draw velocity in) & Line (to draw lines)

(0020358)
paul   
2018-07-17 12:10   
wow, this is brilliant.

now you need to look into the Drag code (editor_drag.{cc,h}) to see how to implement velocity dragging :)
(0020359)
alexmitchellmus   
2018-07-17 12:56   
(Last edited: 2018-07-17 13:05)
@paul, I personally don't like the idea of velocity dragging for all notes. But I do think that lollipops should be able to be:

* Drawn into
* Adjusted (selected notes)
* Get value from drawn line over all selected lollipops.

In regard to 'velocity automation', enumerating lollipop should allow us to pass this as a automation track type? Which would be drawn along with all the other automation tracks?

It looks like currently global tracks are dealt with elsewhere so I am not sure if this should be the same place.

(0024940)
naught101   
2020-08-19 05:28   
@alexmitchellmus Is that the right patch? I may well be mistaken, but it seems to be a patch relative to another change (there is a line with an ALEX comment removed). Did you perhaps not diff against master?

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9090 [ardour] bugs minor always 2022-11-10 23:41 2022-11-15 23:46
Reporter: Attila S. Platform: GNU  
Assigned To: x42 OS: Linux  
Priority: normal OS Version: (any)  
Status: resolved Product Version: 7.1  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Window > Meterbridge in VU mode has a bad red background
Description: Window > Meterbridge in VU mode has a bad red background
See on the attached screenshot.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files: meterbridge-red-vu.png (41,759 bytes) 2022-11-10 23:41
https://tracker.ardour.org/file_download.php?file_id=4285&type=bug
png
Notes
(0026892)
x42   
2022-11-15 23:46   
Fixed in 7.1-90-g16ce8b3331 (back to yellow)

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9082 [ardour] bugs minor random 2022-11-08 14:50 2022-11-15 05:06
Reporter: JP_Bennett Platform: Fedora  
Assigned To: OS: Linux  
Priority: normal OS Version: 36  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Playhead occasionally jumps when seeking with a Midi shuttle wheel
Description: Editing a large project (6 tracks, a couple hours of audio), when using a Behringer X-touch One to scroll though the timeline, the playhead will occasionally jump to a previous location. This usually happens after stopping playback, then shuttling, then the playhead will pop back to where playback stopped. Note that Auto Return is disabled.
Tags:
Steps To Reproduce: Large project, Interview Ripple mode, make multiple cuts throughout the project. Then play and shuttle with a shuttle wheel in Mackie Control mode. Not every time, but often enough to be annoying, the playhead will jump.
Additional Information: Next time I'm editing one of these sessions, I'll try to use a screen recorder to capture the exact behavior.
System Description
Attached Files:
Notes
(0026891)
JP_Bennett   
2022-11-15 05:06   
Managed to catch a few instances of this while editing. Most obvious one at 12:25 https://youtu.be/hJFUf0FCM3M?t=745

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9094 [ardour] bugs major always 2022-11-14 19:00 2022-11-14 19:10
Reporter: stefan-franz Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Plugin Selector empty on new start - First need the Plugin Manager, Discover new/Updated Button
Description: Mint 21 Cinnamon

On every new start of Ardour, the plugin selector is empty. After running the Plugin Manager, Discover new/Updated Button, there is list as normal.
Tags: plugin
Steps To Reproduce: Close Ardour, restart.
Additional Information:
System Description
Attached Files:
Notes
(0026890)
stefan-franz   
2022-11-14 19:10   
New insight: It depends on the project. One makes no problem. Other have it.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8987 [ardour] bugs crash always 2022-10-15 00:13 2022-11-14 14:06
Reporter: Schmitty2005 Platform: Microsoft  
Assigned To: OS: Windows  
Priority: normal OS Version: 10  
Status: new Product Version: 7.0  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: SEG Fault when discarding Ardour Session
Description: SEG Fault in log when QUIT>DISCARD SESSION is selected.
Tags:
Steps To Reproduce: Open a new blank session in Ardour 7rc3.
QUIT -> DISCARD SESSION = SEG Fault in Debugger
Additional Information:
System Description
Attached Files: Ardour-debug.log (65,578 bytes) 2022-10-15 00:13
https://tracker.ardour.org/file_download.php?file_id=4223&type=bug
Notes
(0026623)
paul   
2022-10-17 16:51   
developer note: this is caused by the destructor for the TempoMap occuring in some random thread (which is exiting) and encoutering an error (null ptr?) when doing so. possibly related to some weird windows stuff connected to thread-local variables.
(0026886)
leochras   
2022-11-12 23:43   
I'm not sure if this is related, but when I try to discard a session, ardour freezes and I get this error:

ardour7.desktop[263659]: Butler drops pool trash

It's particularly annoying, because it sometimes seems to halt pipewire and I have to close ardour via htop.
I am on arch with gnome and ardour 7.1.0

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9093 [ardour] bugs minor always 2022-11-12 13:21 2022-11-14 14:05
Reporter: finotti Platform: Debian GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Follow playhead does not work when starting from start
Description: If I go to the start of the sessions (like, pressing "home"), the playhead is not followed. If I move it away from the start, it works normally.

I noticed that it works in a new session, until I create a track.
Tags:
Steps To Reproduce: 1) Create a new session.
2) Make sure "Follow Playhead" is selected.
3) Add an audio track.
4) Press "home" or move to start and press play. It does *not* follow the playhead.
4) Put the playhead anywhere else and press play. It does follow the playhead.
Additional Information: This has happened with many past versions. (I think since Ardour5, at least.)
System Description
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9088 [ardour] features tweak always 2022-11-09 22:51 2022-11-14 13:56
Reporter: Attila S. Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Unifying plugin bypass/on-off function and feedback light
Description: Currently if a plugin is enabled it will have a turned on green light on the mixer view. But if the plugin is opened in its window it will have a turned off red light. If the plugin is disabled/bypassed then on the mixer view the green light will turn off and the red light will turn on in the plugin window.

Now, in my opinion it would be a good idea to unify the behavior of the bypass functions and feedback lights.

So the turned on plugins would be green everywhere and the turned off/bypassed plugins would be red everywhere. Or something like this.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files: fig-bypass.png (65,114 bytes) 2022-11-09 22:51
https://tracker.ardour.org/file_download.php?file_id=4284&type=bug
png
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9089 [ardour] bugs major always 2022-11-09 23:58 2022-11-12 03:40
Reporter: exxelxior22 Platform: Debian GNU/Linux  
Assigned To: OS: Debian 11  
Priority: urgent OS Version: Bullseye  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: When recording with Count-in in MIDI tracks the first beat is not recorded after count-in
Description: When recording a MIDI track and counting in (using "Record with Count-in: in the Transport menu), recording starts after a two-bar count-in, notes played are showed in the track but the first beat is not recorded when stop. This does not happen with Audio tracks.
My Ardour version is
Ardour 6.5.0~ds0
"Old Land"
(rev 6.5.0~ds0-1)
Intel 64-bit

This bug is the same reported in 0007314 dated in 2017. Is there a solution that I've not found?
Thanks in advance.
Tags: 6.5, count-in, Midi, recording
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0026878)
x42   
2022-11-10 21:48   
Works here with Ardour 7.1 - however if you play a bit early (just before the last click of the count-in), the note will indeed be ignored.
(0026879)
x42   
2022-11-10 21:48   
Could you test with Ardour 7.1?
(0026882)
exxelxior22   
2022-11-12 03:40   
I've not tested with 7.1 because I'm using the Debian stable version which is 6.5.0+ds0-1

As an aside:
When is recording the first whole beat is in the screen, but when I push stop it disappears entirely and the rest of the beats position at the beginning of the record. In other words: the first beat desappears and the rest of the beats take its place from the second beat.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
7314 [ardour] bugs major always 2017-04-11 10:32 2022-11-10 21:45
Reporter: bramilo Platform: Ubuntu Studio  
Assigned To: OS: Ubuntu 16.04  
Priority: high OS Version: Maverick  
Status: new Product Version: 5.8  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: When using Count-in with MIDI tracks, the first beat is not recorded after count-in
Description: When recording a MIDI track and counting in (using "Record with Count-in: in the Transport menu), recording starts after a two-bar count-in, but the first beat is not recorded. This does not happen with Audio tracks.
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:
9087 [ardour] bugs minor always 2022-11-09 22:23 2022-11-10 18:19
Reporter: Attila S. Platform: GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: h-he Satin plugin’s dropdown menus stopped working
Description: The dropdown menus stopped working.
For example try setting the Compander's Encoder or Decoder.
Beforehand clicking on the downwards arrow a menu showed up.

Works in Mixbus 8.1 and Reaper.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0026876)
Attila S.   
2022-11-09 22:25   
"h-he Satin" correctly is "u-he Satin"
(0026877)
Attila S.   
2022-11-10 18:19   
This problem seems to be restricted to the official builds and/or to the current OpenSUSE Tumbleweed distribution.
Because Satin works correctly with Ardour v7.1 build provided by the Geekos DAW Tumbleweed repo.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9086 [ardour] bugs minor always 2022-11-08 20:56 2022-11-08 20:56
Reporter: Jxs Platform: Linux  
Assigned To: OS: Mageia  
Priority: normal OS Version: 8  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: no screen refresh after tempo change by ctrl-dragging
Description: as in the title

ps: the documentation mentions "constraint modifier" which is shift by default. This appears to set the tempo left of the marker. But the documentation doesn't seem to mention ctrl-dragging
Tags:
Steps To Reproduce: 1. create a new tempo
2. ctrl drag the tempo. A text appears with the value of the new tempo
3. release the mouse button. Screen is not refreshed
4. zooming, shift dragging or right click + edit + ok updates the screen
Additional Information:
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9085 [ardour] bugs major always 2022-11-08 20:23 2022-11-08 20:23
Reporter: Jxs Platform: Linux  
Assigned To: OS: Mageia  
Priority: normal OS Version: 8  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Edit tempo with a BBT creates a second tempo
Description: As in the title
Tags:
Steps To Reproduce: 1. create a new tempo at bar 6
2. create a new BBT with Bars:Beates 1:1 at bar 8
3. right click + edit the tempo at bar 6. Immediately click apply (no properties need to change)
4. in addition to our tempo, we have now a second tempo at bar 6 inside the BBT
Additional Information:
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9084 [ardour] bugs major always 2022-11-08 17:07 2022-11-08 17:07
Reporter: Daniele1971 Platform: GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: problems with multi monitor setup
Description: I have already written on the forum about this problem (https://discourse.ardour.org/t/ardour-7rc2-menu-always-opens-to-the-right/107687/4), few more info here..
With all official build from 6.9 to 7.1 Ardour is not confined to main screen but spawn some windows and tooltip bwtween screens.

On loading, splashscreen on screen 1 but session load/config and plugin scanning windows are on screen 2. Attached pictures clearly showh the problem.

Does not happens with the openSUSE build, for this I didn't notice before..

openSUSE TW, with Plasma desktop on Xorg.
vcard: Radeon rx 550
Tags:
Steps To Reproduce: start Ardour with 2 (maybe more) monitors
Additional Information:
System Description
Attached Files: ardour2screen.jpeg (348,659 bytes) 2022-11-08 17:07
https://tracker.ardour.org/file_download.php?file_id=4282&type=bug
ardour_tooltip.jpg (30,329 bytes) 2022-11-08 17:07
https://tracker.ardour.org/file_download.php?file_id=4283&type=bug
jpg
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9052 [ardour] translation trivial always 2022-10-30 19:10 2022-11-08 17:06
Reporter: ufocia Platform: Microsoft  
Assigned To: x42 OS: Windows  
Priority: normal OS Version: 10  
Status: resolved Product Version: 7.0  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Misspelled name of patch/instrument
Description: Accordion misspelled as "Accordian" in the Patch Selector for standard MIDI patches Channel 1, Patch Bank 0
Tags:
Steps To Reproduce: Open Patch Selector for Channel 1, Patch Bank 0
Additional Information:
Attached Files:
Notes
(0026770)
x42   
2022-10-30 19:20   
This is odd, It was fixed about a year ago (for Ardour 6.9):
https://github.com/Ardour/ardour/commit/dd0c543943e5526fe9a161fd5dbf15f734363240

Are you using a synth plugin that provides those names? General MIDI synth? or ACE Fluidsynth with a .sf2 that provides those names?
(0026845)
x42   
2022-11-02 19:06   
Fixed in general-midi synth plugin.
(0026869)
trombet   
2022-11-08 17:06   
Good afternoon, the validation of the correction is carried out in version 7.0 for windows desktop.Thank you so much

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8751 [ardour] bugs minor always 2021-06-19 18:07 2022-11-07 22:41
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:
Notes
(0026867)
Napadator   
2022-11-07 22:41   
I confirm this error, please fix it, due to this error I am unable to edit a multi-track recording of live drums.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9079 [ardour] bugs minor always 2022-11-07 21:55 2022-11-07 21:55
Reporter: Jxs Platform: Linux  
Assigned To: OS: Mageia  
Priority: normal OS Version: 8  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Erratic behaviour of time signature markers + crash
Description: 1. jumpy, erratic behaviour when left dragging time signatures
2. with a BBT the real crazyness begins
3. a crash can also be seen when manipulating both time signature and BBT
Tags:
Steps To Reproduce: 1. create a new time signature marker
2. left drag it to the right and watch it jump immediately to the next bar
3. continue dragging, this time to the left. It will jump immediately to the previous bar

Looks like moving to a next or previous bar is coupled to the mouse direction. This behaviour makes it very difficult to manipulate. Note that dragging the tempo marker has more stable behaviour.


With a BBT:

1. create new time signature marker, at bar 4 for example
2. create new BBT marker with bars:beats 1:1, just after bar 8
3. left drag the time signature marker to the right of the BBT marker
4. watch it jump to BBT+8
5. draggin the time signature is now confined within the BBT marker (unless steps 8-10 are executed)
6. drag the time signature back to the left of the BBT marker
7. watch it jump again to BBT+8

8. move it back to the right of the BBT marker, more specifically to bar 2 within the BBT marker
9. move it a tiny amount to the left and watch the Bars:Beats ruler reset itself as if there was no BBT at all. The time signature is at bar 9
10. move it further to the left and observe that it has indeed left the BBT. The Bars:Beats ruler again shows the BBT marks
11. note that this effect cannot be obtained by dragging the time signature marker in one go from right to left. In that case the time signature marker will stay inside the BBT and jump wildly each time you cross the BBT marker

A crash can also be observed:

1. create new BBT marker with bars:beats 1:1, at bar 8 for example
2. create new time signature marker to the left of the BBT
3. watch it jump immediately to the right of the BBT ! That's already weird.
4. left drag the BBT marker to the right of the time signature marker
5. watch how a bunch of vertical guide lines disappear to the left of the BBT marker
6. scroll mouse wheel up
7. crash...
Additional Information:
Attached Files:
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9077 [ardour] bugs minor always 2022-11-07 12:02 2022-11-07 13:27
Reporter: supernovajm Platform: Ubuntu  
Assigned To: x42 OS: Linux  
Priority: normal OS Version: (any)  
Status: resolved Product Version: 7.1  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Gain envelope being duplicated on delete/split
Description: If you delete or split a region, the gain envelope from the original region gets replicated on both halves of the split track.
Tags:
Steps To Reproduce: add a track
manipulate the gain envelope
split or delete the track at a point after the envelope, the gain envelope settings will be duplicated on both halves of the split track.

video example: https://www.youtube.com/watch?v=CL0y4k75AuM
Additional Information:
System Description
Attached Files:
Notes
(0026865)
x42   
2022-11-07 13:27   
Fixed in 7.1-1-g7b86ef8eff

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8976 [ardour] translation trivial always 2022-10-04 16:52 2022-11-07 13:08
Reporter: ufocia Platform: Microsoft  
Assigned To: x42 OS: Windows  
Priority: normal OS Version: 10  
Status: resolved Product Version: 6.9  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Misspelled name of patch/instrument
Description: Accordion misspelled as "Accordian" in the Patch Selector for standard MIDI patches Channel 1, Patch Bank 0
Tags:
Steps To Reproduce: Open Patch Selector for Channel 1, Patch Bank 0
Additional Information:
System Description
Attached Files: image.png (69,891 bytes) 2022-10-04 16:52
https://tracker.ardour.org/file_download.php?file_id=4220&type=bug
png

image-2.png (68,494 bytes) 2022-10-04 18:04
https://tracker.ardour.org/file_download.php?file_id=4221&type=bug
png
Notes
(0026601)
ufocia   
2022-10-04 18:04   
Similar mistake in Patch Bank 8 for Italian Accordion misspelled as "Italian Accordian".
(0026844)
x42   
2022-11-02 19:06   
OK this seems to have been a bug in general MIDI synth (or rather the general user soundfont https://github.com/x42/gmsynth.lv2/tree/master/sf2).
Fixed now.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9076 [ardour] bugs minor always 2022-11-06 21:59 2022-11-07 05:18
Reporter: cooltehno_bugs Platform:  
Assigned To: OS:  
Priority: high OS Version:  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Bug: snap issue - a summary gap between copied midi regions
Description: While the copying snapped to time line MIDI regions - there's some accumulated error in the length of copies. For example, if we copy x50 times the region 4bars length - this make a gap 612 samples long between the end boundary of the last (50-th) region & grid.
Tags:
Steps To Reproduce: 1. Create a new MIDI track
2. Draw 4 bars length MIDI region in Snap state activated.
3. Duplicate the created region 50 times through the Alt+D command.
4. Zoom to the end boundary of the last 50-th region - you'll see the GAP the end boundary of the last 50-th region and grid.
5. Draw the new region between the end boundary of the 50-th region and the grid - this must be 612 samples long - which must not be.
Additional Information:
Attached Files: midi_copy_accumulated_error_gap.gif (600,665 bytes) 2022-11-06 22:03
https://tracker.ardour.org/file_download.php?file_id=4278&type=bug
midi_copy_accumulated_error_gap-2.gif (636,166 bytes) 2022-11-07 05:18
https://tracker.ardour.org/file_download.php?file_id=4279&type=bug
Notes
(0026860)
cooltehno_bugs   
2022-11-06 22:03   
(0026861)
cooltehno_bugs   
2022-11-07 05:18   
better quality gif

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9069 [ardour] bugs minor always 2022-11-04 21:42 2022-11-06 19:28
Reporter: CraigPid Platform: GNU  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Cannot select inputs in the connection matrix after opening a video and extracting the audio
Description: After opening a video and choosing to extract audio only, when another audio track is added I cannot select any inputs in the connection matrix.
The workaround is to save and close Ardour. After restarting Ardour and opening the project I am able to select inputs. I have reproduced this in
an up to date version of Mint with the 6.9 bundle from ardour.org and also in Arch with the 7.1 version from the Arch repo. Both systems are using pipewire.
When attempting to select an input, a green dot appears when hovering but when clicked, does not make the connection.
Tags:
Steps To Reproduce: 1. Create new project
2. Open video and extract audio to a new track
3. Create new audio track
4. Open the grid and attempt to select an input
Additional Information: Both systems are running pipewire-jack at 44.1 khz.
The video I imported was 48k and resampled by Ardour when importing.
System Description
Attached Files:
Notes
(0026853)
CraigPid   
2022-11-05 15:55   
Seems that it's not dependent on importing audio from a video but just importing audio in general. Or maybe random. I've noticed that when I click the square on the input, the green dot does not appear but I actually am getting input from the mic, even though it says it's not armed. There doesn't seem to be a way of disconnecting it though.
(0026855)
kiilerix   
2022-11-05 22:29   
Can you reproduce if using the ALSA or PulseAudio backend?
(0026856)
CraigPid   
2022-11-05 23:24   
When Ardour starts I don't have an option of choosing a backend. Do I need to disable Jack?
(0026857)
kiilerix   
2022-11-06 01:13   
You can always open the backend dialog in Window -> Audio/MIDI Setup. "Close" the old backend and "start" the new one. (The ALSA backend should connect directly to the device after telling PipeWire to back off.)

(My hypothesis is that this could be a JACK/PipeWire issue that I also have seen, apparently related to timing issues between creating JACK "channels" in PipeWire and being able to use them for signal routing.)
(0026859)
CraigPid   
2022-11-06 19:28   
I tried it with the Alsa backend and was not able to reproduce.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9073 [ardour] features feature have not tried 2022-11-06 07:50 2022-11-06 07:50
Reporter: ksawerytreningowski Platform:  
Assigned To: OS:  
Priority: immediate OS Version:  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Mute midi notes
Description: Mute selected notes in Editor.
Absolutely essential function absolutely necessary
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:
9066 [ardour] bugs minor always 2022-11-03 15:50 2022-11-05 22:31
Reporter: paul 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: bbt ruler is incorrect when using non-quarter note time signatures
Description: as in summary
Tags:
Steps To Reproduce: use 11/8 time

lines/points appear to be quarter notes, which seems wrong.
Additional Information:
Attached Files: badtime.png (20,821 bytes) 2022-11-03 15:50
https://tracker.ardour.org/file_download.php?file_id=4275&type=bug
png
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9068 [ardour] bugs minor always 2022-11-04 18:14 2022-11-05 22:29
Reporter: prokoudine Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Range markers not rendered properly when CD mode is toggled
Description: Range markers are not rendered properly when CD mode is toggled in the Ranges & Marks list.
Tags:
Steps To Reproduce: 1. Create a custom pair of range markers
2. Tick its "CD" checkbox in the Ranges & Marks list
3. The markers disappear from the "Range Markers" ruler, but do not appear on the CD Markers ruler until the canvas/timeline is somehow updated, e.g. by scrolling it left/right or hovering the mouse over the ruler
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:
9006 [ardour] bugs minor always 2022-10-18 19:01 2022-11-05 19:48
Reporter: Attila S. Platform: GNU  
Assigned To: x42 OS: Linux  
Priority: normal OS Version: (any)  
Status: resolved Product Version: 7.0  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Plugin analysis goes astray
Description: I observed that the “Edit with generic controls” window’s “Plugin analysis” goes astray with the ACMT ACM-2SA and ACM-5SA vst3 plugins, if I set values on the standard plugin UI and then I open the plugin with “Edit with generic controls” and here I open the plugin analysis. It will not show the changes that I made.

BUT if I’m using from start only the generic controls then the analysis seems to work correctly.

I also contacted the plugin’s developer and he said the problem is not on the plugins side.

I attached a screenshot.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files: plugin-analysis-acm-2sa.png (226,325 bytes) 2022-10-18 19:01
https://tracker.ardour.org/file_download.php?file_id=4232&type=bug
png
Notes
(0026851)
x42   
2022-11-04 17:03   
Fixed in 7.1-18-g0aad0ae464
(0026854)
Attila S.   
2022-11-05 19:48   
Thank You!

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9062 [ardour] bugs minor always 2022-11-01 17:58 2022-11-02 18:37
Reporter: sollapse Platform: Microsoft  
Assigned To: x42 OS: Windows  
Priority: normal OS Version: 11  
Status: resolved Product Version: 7.0  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Motorized fade setting not saved with session.
Description: I've noticed that I have to re-enable the Motorized option on opening a session. This causes assignment to be lost for automation controllers.
Tags:
Steps To Reproduce: Open a session, add a Generic MIDI controller and select Motorized. Assign parameters with any MIDI control. Save the session then reopen. Motorized will be disabled.
Additional Information:
System Description Windows 11
Attached Files:
Notes
(0026815)
sollapse   
2022-11-01 18:00   
*Meant to say motorized option instead of fade.
(0026837)
x42   
2022-11-02 16:22   
Are you perhaps using an AKAI_MPKmini preset (or a custom preset that explicitly sets motorized = false?
(0026840)
x42   
2022-11-02 16:48   
Fixed in Ardour 7.0-200-g6813884857
(0026843)
sollapse   
2022-11-02 18:37   
It's a custom MPK225 mapping file. I now see there is a setting for motorized under bank in the MPKmini map.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9065 [ardour] features minor have not tried 2022-11-02 09:00 2022-11-02 16:40
Reporter: cooltehno_bugs Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 7.0  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Proposal: to add 'write' and 'touch' functions to CC MIDI
Description: It could be so comfortable to modify CC while playback MIDI regions using 'write' and 'touch' functions to CC MIDI - analogically to plugin of fader automation.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0026835)
paul   
2022-11-02 13:57   
There's a reason we don't do this. Right now I can remember what it is. It might be a bad reason.
(0026838)
cooltehno_bugs   
2022-11-02 16:40   
Thanks for response, Paul! It's absolutely not a critical feature! Good luck in current stage polishing! :)

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
5100 [ardour] features major have not tried 2012-09-10 15:33 2022-11-02 11:00
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:
7186 [ardour] bugs major random 2016-12-25 21:49 2022-11-02 09:44
Reporter: unfa Platform: PC/ Linux  
Assigned To: OS: Linux Mint  
Priority: normal OS Version: 18 KDE5 64-bit  
Status: feedback Product Version: 5.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: ZynAddSubFX patches are not saved
Description: After saving and reloading my session, all of my ZynAddSubFX patches are replaced with default sine-wave patch.

I tried this with two Ardour 5.x versions. Looks like it affects only ceritan sessions.

I have made 2 sessions with the same ZynAddSubFX LV2 plugin - one seems to never load (or even save) the Zyn patches - the other loads them fine.

I loaded my flawed session to realize my sounds are gone, I remade some of them, saved the session, reloaded and they are gone again.

I tried loading that session with many different Arodur 5 versions - none loaded the Zyn patches. Looks like patches the haven't been saved in the project.
Tags:
Steps To Reproduce:
Additional Information: I'm attaching my session.
Attached Files: What is JACK 2.ardour (478,334 bytes) 2016-12-25 21:49
https://tracker.ardour.org/file_download.php?file_id=3151&type=bug
What is JACK.tar.bz2 (350,443 bytes) 2016-12-26 18:27
https://tracker.ardour.org/file_download.php?file_id=3152&type=bug
Notes
(0019217)
x42   
2016-12-25 23:43   
LV2 preset save/load is between the plugin and liblilv. Ardour takes no part in presets. LV2 presets are usually saved to ~/.lv2/ and available to all lv2 hosts. Can you try with jalv?

Are you using Ardour binaries from ardour.org (with liblilv-0.22.1). If not, which version of liblilv did you compile and run Ardour with?

LV2 *state* (current settings) are saved with the session, in SESSION-DIR/plugins/ID/ and not part of the session file.

You also seem to be using an old version of zyn in what looks Carla as wrapper (the plugin URI is the session file is http://kxstudio.sf.net/carla/plugins/zynaddsubfx). Can you try with zyn-fusion (proper LV2 plugin, not a wrapped carla instance) http://zynaddsubfx.sourceforge.net ?
(0019218)
unfa   
2016-12-26 18:35   
I'm using only Ardour binaries form ardour.org - usually nightlies to check for new bugfixes.

I mean plugin states, not presets.

I have attached a bz2'ed copy of the whole session directory without the audio files in interchange (because they are big).

In a subfolder "Zyn patches" I have manually saved XMZ files from the ZynAddSubFX instruments to have a backup in case Ardour won't recall the plugin states.

I the "plugins" subfolder I saw there are some plugin states saved but I have no idea if they contain what I manually saved in "Zyn patches" - even if so, Ardour doesn't load this data.

Could you please take a look?
(0019221)
x42   
2016-12-28 00:04   
What is the absolute path to the session on your disk? Is the file-system using UTF-8 charset (default on gnu/linux for fs) or some non-standard codepage?

The state-manifest files have some very strange reference:

   rdfs:seeAlso <#07/What\u0020is\u0020JACK/plugins/1097/state8/state.ttl>

that should be just

   rdfs:seeAlso <state.ttl>

It looks like lilv/serd fail to detect the the common ancestor of the state directory, but I haven't found a way to reproduce this nor find an obvious code-bug that results in this, yet.
(0019222)
x42   
2016-12-28 01:12   
PS. can you also include the output of `locale` on your system?
(0019224)
unfa   
2016-12-28 14:22   
IIRC the absolute path for the session is:

"/unfa/Projects/YouTube/Vlog/Episodes/UV#07/What is JACK/What is JACK 2.ardour"

Maybe the "#" character in the path is problematic?

The "/unfa" dir is mounted using fstab from a separate partition than the system one.
I'll provide more details later.
(0019227)
x42   
2016-12-28 15:36   
Yep, the hash (#) is the issue.
(0019231)
x42   
2016-12-28 23:39   
forwarded upstream: http://dev.drobilla.net/ticket/1150
(0019234)
unfa   
2016-12-29 17:39   
(Last edited: 2017-01-01 18:51)
Here's the requested detail about my system:

$ locale
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=en_UM.UTF-8
LANGUAGE=
LC_CTYPE="en_UM.UTF-8"
LC_NUMERIC=pl_PL.UTF-8
LC_TIME="en_UM.UTF-8"
LC_COLLATE="en_UM.UTF-8"
LC_MONETARY=pl_PL.UTF-8
LC_MESSAGES="en_UM.UTF-8"
LC_PAPER=pl_PL.UTF-8
LC_NAME=pl_PL.UTF-8
LC_ADDRESS=pl_PL.UTF-8
LC_TELEPHONE=pl_PL.UTF-8
LC_MEASUREMENT=pl_PL.UTF-8
LC_IDENTIFICATION=pl_PL.UTF-8
LC_ALL=


The filesystem is an EXT4 - I have no idea how to check if it's using UTF-8. I didn't mess with it so I guess it is.

x42: thank you for proposing a fix!

PS:

I tried changing the absolute path to remove the "#" charactetr, but the plugins states are not loaded correctly. Is there anything I can do to fix the session?

(0019260)
x42   
2017-01-03 19:51   
Since the problem happens during "save", it's too late.

You can however manually edit the files in plugin/NNN/stateMMM/manifest.ttl and change the "rdfs:seeAlso <...>" to "rdfs:seeAlso <state.ttl>"
and remove the invalid \u0020 in both .ttl files


something like (make a backup first)

----- BASH -----
for file in plugins/*/*/manifest.ttl; do
  sed -i'' 's/rdfs:seeAlso.*$/rdfs:seeAlso<state.ttl> ./' $file
done
for file in plugins/*/*/*.ttl; do
sed -i'' 's/\\u0020//g' $file
done
----------------

I can't test this with your session, the only plugin from your session that I also have installed is "Autotune".
(0019265)
unfa   
2017-01-04 09:56   
(Last edited: 2017-01-04 18:57)
Thank you, I'll try fixing the session - good that I saved an external backup of the patches in XMZ files.

EDIT: The bash script didn't fix my session, but after reloading the backed-up ZynAddSubFX patches into the tracks and saving the session in a new location ("Save as...") I was able to get it running well again.

I wonder if there are any more special characters that can break ZynAddSubFX when put in the session's path.

(0019292)
x42   
2017-01-21 02:39   
Can you confirm that the issue is no longer present when using a recent nightly build (or update liblilv to v0.24.2)?

Old sessions still won't restore the (wrongly saved) preset, but when saving a new session that issue should no longer be present.
(0021216)
x42   
2020-04-06 18:48   
Is this still an issue with Ardour 6.0-pre1?
(0026827)
willbradley   
2022-11-02 09:44   
I still experience this issue under Ardour 6.9/Ubuntu 22.04/latest Zyn, but I've found a reliable workaround and I'm describing it here in case it may help with troubleshooting.

What works, I have no idea why, is to disable (just switch off, not remove) every affected instance of Zyn before you save the project and switch them back on after reload. And then, at least for me, the patches are still there.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9064 [ardour] bugs minor always 2022-11-01 19:56 2022-11-01 19:56
Reporter: lootre Platform: Ubuntu  
Assigned To: OS: Linux  
Priority: normal OS Version: (any)  
Status: new Product Version: 7.0  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Jump to next/previous mark stuck between 2 marks
Description: When using the keyboard shortcuts W or Q to jump to the next or previous location mark and if there are more than 2 location mark, the playhead only jumps between the 2 same marks, it doesn't go to the next or the previous.

Example: In a session with 4 location marks, I set the playhead between mark 2 and 3. Using the keyboard shortcuts (Q/W) I can only jump to mark 2 or 3, but not to 1 (as a previous of 2) or to 4 (as the next of 3).

In a session with several location marks, the behavior is not consistent with this example. Sometimes it's only possible to jump to previous, sometimes only to next.
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:
8313 [ardour] features minor N/A 2020-07-15 17:41 2022-11-01 13:23
Reporter: Oliver Platform: x86_64  
Assigned To: x42 OS: Xubuntu  
Priority: normal OS Version: 18.04LTS  
Status: resolved Product Version: 6.2  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Preference window needs scrollbars
Description: On my 1024x768 screen, I need to detach the preferences to see all of the editor and mixer when in
full screen mode (Maximise Editor Space).

The detached preference window is still too large and I need to move the window around to see all entries,
sometimes awkwardly so if the interesting part is on the bottom (selecting first 'Move' from the window
manager menu, then place it with the mouse). There is no way to resize the preference window.

The usual remedy for this, I believe, are scrollbars.
Tags:
Steps To Reproduce:
Additional Information:
System Description Pentium Dual-Core E5200 (2.50GHz)
Attached Files: Ardour Mixer maximised attached.png (77,668 bytes) 2020-11-08 09:08
https://tracker.ardour.org/file_download.php?file_id=3862&type=bug
png

Ardour Mixer maximised detached.png (57,519 bytes) 2020-11-08 09:08
https://tracker.ardour.org/file_download.php?file_id=3863&type=bug
png
Notes
(0025177)
Oliver   
2020-10-28 09:59   
Another window that is too large on my screen is the 'Edit Export Format Profile' window.

Couldn't all secondary windows have scrollbars if exceeding the screen size?
(0025187)
x42   
2020-11-01 21:48   
Try Preferences > Appearance > GUI and font scaling and make Ardour smaller. Scaling is relative to the default desktop font-size and a scaling of 0000088:0000085% - 90% is usually required for small screens <= 1024x768.

Full widow scrollbars are tricky to add in a way that does not otherwise interfere with native min. window sizes, and it's hard to justify spending time on this in 2020 where most screens are 4k or 8k.
(0025188)
Oliver   
2020-11-01 22:00   
I do use GUI scaling already, indeed in the suggested range, as otherwise the main window overflows. Some secondary windows are still way larger than my screen.

I was hoping (apparently in vain) that it would just be a few lines of code to add scrollbars (also hiding automatically when not need), as in other GUI tool kits (e.g. Qt).

I agree that this screen size is less common, on the other hand it was always a strength of Linux versus windows to not make working hardware obsolete so quickly. It is possible to work around this with window manager functions, but it is awkward.
(0025189)
x42   
2020-11-01 22:19   
Same problem with QT. It would enable resizing regardless of screen-size.
(0025190)
x42   
2020-11-01 22:35   
Which dialogs are affected?

The export-profile dialog could be fixed with some re-layout. make it wider less tall.
(0025191)
Oliver   
2020-11-01 23:00   
Quickly scanning through the available windows:

'Preferences' - too wide after selecting the 'Transport' category
'Edit Export Format Profile' - too high
'Transport Masters' - too wide

The Preferences initially fit on the screen (after program start), but by selecting the 'Transport' category they expand horizontally. Then, even if selecting another category, they do not revert to the previous width anymore.
(0025209)
al f   
2020-11-08 09:08   
I have the same or a very similar problem on Ardour (version 5.12 up to 6.3) on (X)Ubuntu Studio 18.04. Toshiba laptop with 1366x768 screen resolution.

GUI scaling is not really an option for me as I would struggle to read the text if smaller than default.

Opening Ardour first time, the main window is too high. Selecting 'Maximise Editor Space' fixes this, deselecting reverts. The titlebar button to maximise does nothing.

Most of the windows accessible from the Window menu fit on the screen, but not these:

'Preferences' - too high (from first opening, can't resize it - the arrow changes to a moving hand as soon as I click it)
'Edit Export Format Profile' - too high (can't see nor reach the buttons cancel / save).
'Mixer' - if detached OK, if attached the main frame OK but some of the contents a little too big. See screenshots
(0025238)
x42   
2020-11-18 18:39   
The Export Profile Dialog layout was updated, and it should now fit on smaller screens.
(0025262)
Oliver   
2020-11-24 10:07   
Thanks, this dialog is good now with ardour 6.5. Would be nice if also Preferences/Transport and Transport Masters could be updated if scrollbars are out of the question.
(0025263)
x42   
2020-11-24 13:39   
Yes, that's the idea.
The Transport master window will be next, since that's also used in preferences.
(0025287)
al f   
2020-12-04 10:55   
Ardour 6.5 fixed these, thank you very much!

- Size of main window now good, regardless of 'Maximise Editor Space' being selected or not. The titlebar buttons now works as expected.
- 'Edit Export Format Profile' - good size, accesible controls.

These issues remain (minor, as they do not lose access to any controls):

- 'Mixer' - if detached OK, if attached the main frame OK but some of the contents a little too big.
- Preferences dialog still overflowing (but all options accessible)

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9039 [ardour] bugs crash always 2022-10-26 14:39 2022-11-01 09:30
Reporter: al f Platform: Microsoft  
Assigned To: paul OS: Windows  
Priority: immediate OS Version: 10  
Status: resolved Product Version: 7.0  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Looping audio causes Ardour 7 to crash
Description: Tested with Ardour 7.0.0 and Ardour 7.0.105 (rev 7.0-105-g6904a86576)

Creating a loop and starting it with the shortcut L, the loop plays once and then stalls with a high pitched noise. Subsequently Ardour hangs or crashes with lots of xruns reported by QJackctl. Right-clicking on a region and chosing "Loop region" = same result.
Tags: crash, Editor, loop, range marker
Steps To Reproduce: Create and start a loop.
Additional Information: Manjaro KDE, PulseAudio and Jack2. Everything up to date except glib2 which is temporarily held at 2.74.0-2 because the newer versions causes Timeshift crashing.
System Description
Attached Files: Ardour.log (47,038 bytes) 2022-10-26 14:39
https://tracker.ardour.org/file_download.php?file_id=4254&type=bug
Notes
(0026702)
al f   
2022-10-26 17:06   
There's an error in my report, the crash does NOT happen with Ardour 7.0.0 but only with Ardour 7.0.105.

Also, I'm on Manjaro KDE, don't know how I messed it up to look like I'm on Windows. Apologies!
(0026704)
paul   
2022-10-26 19:05   
fixed in git master 489c9ace9f87b5

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9060 [ardour] bugs minor always 2022-11-01 08:15 2022-11-01 08:15
Reporter: krischan941 Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 7.0  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Make "Open Clip library button" stay visible
Description: Like in this thread:
https://discourse.ardour.org/t/location-of-installed-samplepacks/107744/3

In the clip list editor, wehn you have some sample packs installed via Library Downloader and you click an arrow to expand a libraries content, the "Open Clip library button" vanishes, which is confusing.
When double click to enter the libraries content an then double click on the two dotts (..) to access root directory again, the button remains. Would be good if it also remains when using arrows to navigate samples/samplepacks.
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:
9059 [ardour] bugs tweak always 2022-11-01 08:04 2022-11-01 08:04
Reporter: surfinspots Platform: Debian GNU  
Assigned To: OS: Linux  
Priority: low OS Version: (any)  
Status: new Product Version: 7.0  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Painting "long" notes when MIDI record is paused and started while playing
Description: If the recording of a MIDI track is paused and restarted the played notes are rendered very long while the notes are actually played short.
Tags:
Steps To Reproduce: I added a screencast.
1. record a midi track
2. turn off the recording for the track while recording
3. end the note you are playing
4. turn recording on again
5. play the note again
Additional Information:
System Description
Attached Files: ardour-screen-paint-error-2022-11-01_09.03.10.mp4 (916,232 bytes) 2022-11-01 08:04
https://tracker.ardour.org/file_download.php?file_id=4270&type=bug
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9017 [ardour] bugs major always 2022-10-20 19:12 2022-10-31 23:08
Reporter: paul Platform:  
Assigned To: paul OS:  
Priority: normal OS Version:  
Status: resolved Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: when zoomed out, bars/beats ruler is insanely crowded
Description: what the summary says and the screenshot shows
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: bnb.png (22,586 bytes) 2022-10-20 19:12
https://tracker.ardour.org/file_download.php?file_id=4236&type=bug
png
Notes
(0026796)
paul   
2022-10-31 23:08   
fixed via several commits ending with 6d1e4207de524

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
7182 [ardour] features minor have not tried 2016-12-19 17:41 2022-10-31 20:47
Reporter: cooltehno_bugs Platform: Linux  
Assigned To: paul OS: KXStudio  
Priority: normal OS Version: 14.04  
Status: acknowledged Product Version: 5.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: To limit or switch off sound, when few MIDI notes are selected
Description:  Ardour has a useful possibility to sound selected MIDI notes. This mode can be activated here:

 Preferences>MIDI>MIDI Preferences>

"Sound MIDI notes as they are selected in the editor".

 This mode works fine with single notes, but when we select several notes - they sound together (volume level summary!). If, for example, we have about 20 notes in a region and press Ctrl+A (to select all of them) - it produces an impermissible level of sound.
 The proposal is:
-to make a level limitation for several notes sounding;
-or to switch off the sounding of the selected group of notes at all;
-or to sound the first note of the selected note group.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: bundle_selection_sound_overload.gif (466,147 bytes) 2022-10-31 20:04
https://tracker.ardour.org/file_download.php?file_id=4267&type=bug
Notes
(0019535)
cooltehno_bugs   
2017-03-20 05:17   
One extra thought:
-to sound the note which we pick during dragging the group.
(0026791)
cooltehno_bugs   
2022-10-31 20:04   
added gif example

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
7605 [ardour] features minor always 2018-04-23 18:41 2022-10-31 20:27
Reporter: cooltehno_bugs Platform: Linux  
Assigned To: OS: KX Studio  
Priority: normal OS Version: 14.04  
Status: new Product Version: 5.12  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ardour 5.12 & 6.0 focusing issue when to select the header of midi/audio track during many automation tracks are opened
Description: If to open few automation tracks and make them vertically sized out of ardour's window, and than to select (click left mouse button) the header of this track - the view focuses (jumps) to the center of all (the track itself + all the automation tracks) tracks vertically. Such jumping is a bit annoying during editing automations in complex sessions.
Tags:
Steps To Reproduce: 1. Open few automation tracks in any midi/audio track.
2. Make the size of the automation tracks such wide vertically, so they can't fit to the ardour's window.
3. Select the track header.(it provokes focusing to center of all the opened automation tracks)
Additional Information: Some help video is uploaded
Attached Files: vertical_focusing_issure.mkv (1,953,706 bytes) 2018-04-23 18:41
https://tracker.ardour.org/file_download.php?file_id=3381&type=bug
There are no notes attached to this issue.

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9053 [ardour] bugs minor always 2022-10-30 19:16 2022-10-31 19:22
Reporter: ufocia Platform: Microsoft  
Assigned To: paul OS: Windows  
Priority: normal OS Version: 10  
Status: assigned Product Version: 7.0  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: "Play from playhead" button remains active and does not switch to "Stop playback" upon "Go to start of session"
Description: The transport stops automatically on "Go to start of session", but the "Play from playhead" button remains active and does not switch to "Stop playback". Subsequent clicking on "Stop playback" button does not reset the "Play from playhead" button state.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
Notes
(0026769)
ufocia   
2022-10-30 19:17   
Probably related to bug 0008521 fix in the 6.x versions.
(0026773)
paul   
2022-10-31 05:42   
What is the "play from playhead" button?
(0026789)
ufocia   
2022-10-31 19:04   
This doc page explains what "play from playhead is : https://manual.ardour.org/ardours-interface/the-transport-bar/

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
8930 [ardour] features minor always 2022-06-19 15:18 2022-10-31 18:37
Reporter: Alkukoira Platform: Ubuntu  
Assigned To: paul 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: 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:
Notes
(0026767)
cooltehno_bugs   
2022-10-30 18:54   
Hi, @Alkukoira!
I've made a PR with your remarks here (if Paul or Robin will implement my changes - your request will be satisfied):
https://github.com/Ardour/ardour/pull/747

Big thanks for your advises!! Really good! :)
(0026774)
paul   
2022-10-31 05:44   
PR was merged.
(0026785)
cooltehno_bugs   
2022-10-31 18:33   
Thanks again, Paul! As the nightly test is perfect - I suppose this feature could be marked resolved (I can't change status of this feature request by myself, sorry).
(0026786)
paul   
2022-10-31 18:37   
see notes

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9055 [ardour] bugs minor always 2022-10-30 19:38 2022-10-31 18:27
Reporter: cooltehno_bugs Platform: Ubuntu  
Assigned To: paul OS: Linux  
Priority: normal OS Version: (any)  
Status: resolved Product Version: 7.0  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Bug: Alt+D with several selected MIDI regions - makes copies superimposed to one position
Description: When in "G-mode" we select two or more MIDI regions and use Alt+D function to copy - this makes all copied regions well - but puts them to one start position (all copied regions are placed in one time position like layers).
Tags:
Steps To Reproduce: 1. Make two or more MIDI regions in one track an put them touched to each other.
2. Select these regions by the rectangle selection with the mouse.
3. Press Alt+D combination - this action makes copies of the selected regions superimposed to each other (puts them at the and of the selection).
Additional Information:
System Description
Attached Files: Alt_D_copying_regions_bug.gif (650,813 bytes) 2022-10-30 19:38
https://tracker.ardour.org/file_download.php?file_id=4263&type=bug
Notes
(0026772)
paul   
2022-10-31 05:41   
fixed in git master 21e8885e00261
(0026784)
cooltehno_bugs   
2022-10-31 18:27   
Paul - great thanks! Tested in nightly 7.0.158!

View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
9005 [ardour] bugs minor always 2022-10-18 16:14 2022-10-31 12:35
Reporter: lfont Platform: PC  
Assigned To: x42 OS: Fedora Linux  
Priority: normal OS Version: 36  
Status: resolved Product Version: 7.0  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Session > Import > Search Freesound does not work because of an SSL CA cert error
Description: Hello,

On Ardour 7.0.0 (rev 7.0) official build, it is currently not possible to use the "Search Freesound" feature (at least on Fedora Linux 36).

The Ardour log window contains this error:
2022-10-18T17:48:25 [ERROR]: curl error 77 (Problem with the SSL CA cert (path? access rights?))
2022-10-18T17:48:25 [ERROR]: no root XML node!
Tags:
Steps To Reproduce: Open the import window: "Session > Import"
Go to the third tab "Search Freesound"
Type something in the "Tags" field
Click on the "Search" button

> The Ardour log indicator at the top right will blink in red.
The window will contains the following error:
... [ERROR]: curl error 77 (Problem with the SSL CA cert (path? access rights?))
... [ERROR]: no root XML node!
Additional Information:
System Description
Attached Files:
Notes
(0026641)
x42   
2022-10-18 16:52   
Where does Fedora keep its SSL Certs these days?

is there still /etc/pki/tls/certs/ca-bundle.crt on your system, or is it newer than https://bugzilla.redhat.com/show_bug.cgi?id=1053882 ?
(0026643)
x42   
2022-10-18 17:38   
A potential workaround is now in Ardour 7.0-45-g073d6f5e80
(0026645)
lfont   
2022-10-18 20:19   
/etc/pki/tls/certs/ca-bundle.crt is still there and looking at the README provided by the ca-certificates package (https://src.fedoraproject.org/rpms/ca-certificates/blob/f36/f/README.etcssl) it seems that (/etc/ssl) should be compatible with Debian like distro.

So I'm not sure that this https://github.com/Ardour/ardour/blob/master/gtk2_ardour/ardour_http.cc#L106 is still required.

7.0-45-g073d6f5e80 is not yet available to download, I will test it but I'm not sure about the fix as ca_info should not be empty.
(0026646)
lfont   
2022-10-19 13:13   
I've try to run the latest nightly build (rev 7.0-46-g22829e96b1) and I still get the same error message:
strace output:
stat("/etc/pki/tls/certs/ca-bundle.crt", {st_mode=S_IFREG|0444, st_size=214712, ...}) = 0
openat(AT_FDCWD, "/etc/pki/tls/certs/ca-bundle.crt", O_RDONLY) = 65
stat("/nonexistent_path", 0x7ffd799d8b50) = -1 ENOENT (No such file or directory)

I've build Ardour (rev 7.0) on my system and I was not able to reproduce the issue:
strace output:
openat(AT_FDCWD, "/etc/crypto-policies/back-ends/openssl.config", O_RDONLY) = 62
openat(AT_FDCWD, "/etc/pki/tls/certs/ca-bundle.crt", O_RDONLY) = 62

In the second case there is not attempt to open (/nonexistent_path).
I don't know if this is relevant or not, I can provide more output if needed.
(0026647)
x42   
2022-10-19 14:42   
> So I'm not sure that this https://github.com/Ardour/ardour/blob/master/gtk2_ardour/ardour_http.cc#L106 is still required.

Apparently it is a trap. Red Hat tries to provide a debian compatible but fails at that (see the linked bug report).
I just realized that the check is incorrect. It should check for Glib::FILE_TEST_EXISTS|Glib::FILE_TEST_IS_REGULAR


>I've build Ardour (rev 7.0) on my system and I was not able to reproduce the issue:
The issue is only relevant for binaries from Ardour that bundle libcurl. In this case curl has to be informed where to search for SSL certs.

If you compile Ardour locally and use libcurl from your GNU/Linux distro, your distro has already configured libcurl correctly.
(0026648)
lfont   
2022-10-19 15:16   
> Apparently it is a trap. Red Hat tries to provide a debian compatible but fails at that (see the linked bug report).
Hmm, I don´t know if this has been fixed or not. Some part of the discussion seems to say yes.

> If you compile Ardour locally and use libcurl from your GNU/Linux distro, your distro has already configured libcurl correctly.
Sorry but I'm not familiar will all of this and I don't know how to reproduce exactly the same bundle configuration.

> I just realized that the check is incorrect. It should check for Glib::FILE_TEST_EXISTS|Glib::FILE_TEST_IS_REGULAR
Yes, but the result will be the same. ca_path will end up with the (/nonexistent_path) value which seems to be a problem.
As Glib::file_test ("/etc/pki/tls/certs/ca-bundle.crt", Glib::FILE_TEST_EXISTS|Glib::FILE_TEST_IS_DIR) check is wrong and that (/etc/ssl/certs) exists we should not currently have (/nonexistent_path) in strace. On fedora, (/etc/ssl/certs) is a symlink to (/etc/pki/ca-trust/extracted/pem/directory-hash).
(0026649)
krischan941   
2022-10-19 15:30   
Hi, I don't know whether there is a connection to this but I had a similar problem using the new Download-Library-Manager of Ardour on Linux. It first didn't work and I got some SSL CA cert errors. I closed Ardour and deleted the Ardour config in ~/.config/ and after starting Ardour again it worked. Before official Ardour release, I had a Nihgtly version installed, maybe that config got corrupted or something simlar. Perhaps it helps
(0026651)
lfont   
2022-10-19 20:56   
Thanks for the suggestion, but this is not a configuration problem.
I've run different builds and do not reproduce the issue with all of them.
It seems that the issue is due to the configuration of the bundled libcurl.
(0026661)
paul   
2022-10-21 04:47   
I forgot to mention in the release announcement that if you had used a build of Ardour during the 7.0 development process, you should almost certainly delete or rename your ardour preferences/configuration folder.