View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010354 | ardour | bugs | public | 2026-05-23 13:32 | 2026-05-23 22:49 |
| Reporter | sound8 | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Platform | Debian GNU | OS | Linux | OS Version | (any) |
| Product Version | 9.5 | ||||
| Summary | 0010354: Clocks - Shows two Timecode clocks | ||||
| Description | 9.4.34 nightly 9.5.11 nightly Not sure what causes this but I have been noticing some strange behavior with the toolbar Clocks. I noticed that with fresh install of nightly build / with new Ardour config folder. When Ardour first opens / with new session, it shows the `Bars:Beats` clock and the `Timecode` clock in middle of main toolbar, which is expected. Not sure if maybe I am changing some kind of setting that could cause this bug? After a while of opening and closing Ardour, all of a sudden when I open Ardour with new session, it then shows two `Timecode` clocks. Something else that is strange is that when this occurs, if I right click on the LEFT `Timecode` clock and choose `Bars:Beats`, the clock does not change, it remains `Timecode` clock. Same behavior occurs with the RIGHT `Timecode` clock as well, only one time I tried this with the RIGHT clock and it did change to `Bars:Beats` clock but none of the other times I tested this. If you change clock to `Samples` clock it works, and then it will allow the clock to be changed to `Bars:Beats` Also the clock types do not get remembered at next launch, they open back to the two `Timecode` clocks. Again many times I have removed the .config folder to start Ardour fresh, and every time I do this, this issue does not occur when I first start opening Ardour. It happens once a .config folder gets created and some opening and closing of Ardour occurs. Also again not sure if maybe it is some kind of setting I am activating that triggers this issue? Just thought I would mention for others to keep a look out for any strange clock behavior. Not sure if anyone else has experienced any similar issues? Thank You | ||||
| Tags | No tags attached. | ||||
|
|
I cannot reproduce this. There is both a global preference (used for new sessions) and a per session preference to save/restore clock modes. In both cases instant.xml files (user config folder and session folder). For a new user (no config, new session), primary clock uses Music-time (BBT), secondary clock Timecode. |
|
|
PS. Clock types are correctly remembered. I know because I never use Music Time and always timecode and MinSec or Samples. I and would fix it immediately if Bar/Beat shows up :) It often annoys me when I load user provided sessions to test and those update my defaults as side effect.. |
