View Issue Details
| ID | Category | Date Submitted | Last Update | ||
|---|---|---|---|---|---|
| 0008472 | bugs | 2020-11-21 20:08 | 2021-01-26 19:15 | ||
| Reporter | martin.vlk | Assigned To | x42 | ||
| Reproducibility | always | ||||
| Status | feedback | Resolution | open | ||
| Platform | Ubuntu | OS | Linux | OS Version | (any) |
| Product Version | 6.3 | ||||
| Fixed in Version | |||||
| Summary | 0008472: Newly added audio tracks are not correctly compensated for latency until Ardour session is reloaded | ||||
| Description | When I add one track to a new sassion, the compensation works fine. On a second and next newly added tracks latency compensation is wrong, leading to the recording being off. | ||||
| Tags | jack | ||||
|
|
I cannot reproduce this. Does this only happen with jack? and if so which version of jack? |
|
|
Ah, yes I forgot to mention it is with JACK v1.9.12 |
|
|
I'm affected by this issue as well and it's quite easy to see that adding tracks to loaded session are not in sync with the existing tracks. This covers both audio and midi tracks. As requested I did a "jack_lsp -l" after 1. adding a track to existing project 2. saving the project and reloading it Ardour_jack_latency_dbg.log (8,228 bytes) |
|
|
I'll upload to new file as the copy & paste from terminal was borked in the last post and this forum does not seem to support editing. Ardour_jack_latency_dbg2.log (9,731 bytes) |
|
|
And before forgetting I also have JACK2 1.9.12 so that seems to match. |
|
|
Also this seems to consider only new tracks being added to existing projects. After saving and loading a project everything is in sync again. To mitigate this issue a pool of needed (audio, midi, bus) tracks can be created in advance and then saving and loading the project again as changing tracks routing and plugins does not affect the latency. |
|
|
I can confirm this issue with Ardour 6.3 on Ubuntu 20.4 using JACK. I also have this problem when I use the import dialog to load an audio file into a new track of an existing project. |
|
|
Possibly fixed in 6.5-120-g0c81ba33d2, please test! |
|
|
Hello, Sorry this took a while to try but I tested using Jack with 6.5-172-g046d7d01f5 build which I pulled from git master branch and the problem is still present. However as I'm not sure which commit was related to the potential fix so I'm not sure if it's included in my build or not. (or if there's something related to build environment) |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-11-21 20:08 | martin.vlk | New Issue | |
| 2020-11-21 20:10 | x42 | Relationship added | related to 0008365 |
| 2020-11-21 20:10 | x42 | Note Added: 0025247 | |
| 2020-11-21 20:16 | martin.vlk | Note Added: 0025248 | |
| 2020-11-21 20:17 | martin.vlk | Tag Attached: jack | |
| 2020-11-21 22:59 | Xard | File Added: Ardour_jack_latency_dbg.log | |
| 2020-11-21 22:59 | Xard | Note Added: 0025249 | |
| 2020-11-21 23:04 | Xard | File Added: Ardour_jack_latency_dbg2.log | |
| 2020-11-21 23:04 | Xard | Note Added: 0025250 | |
| 2020-11-21 23:47 | Xard | Note Added: 0025251 | |
| 2020-11-21 23:57 | Xard | Note Added: 0025252 | |
| 2020-11-25 10:36 | consint | Note Added: 0025267 | |
| 2020-12-15 23:12 | x42 | Relationship added | has duplicate 0008502 |
| 2021-01-14 02:24 | x42 | Relationship added | related to 0008304 |
| 2021-01-14 02:25 | x42 | Assigned To | => x42 |
| 2021-01-14 02:25 | x42 | Status | new => feedback |
| 2021-01-14 02:25 | x42 | Note Added: 0025418 | |
| 2021-01-26 19:15 | Xard | Note Added: 0025471 |
