View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010354 | ardour | bugs | public | 2026-05-23 13:32 | 2026-05-26 02:14 |
| 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.. |
|
|
@x42 Hey Robin, thank you for looking into this. I had always thought that this was only a global preference, I never really thought of it as being saved with each project. Could make sense for certain scenarios. But yeah I could see what you mean though that that could be annoying behavior to have someone elses saved preference, change your own preferenced setups GUI. I can make a separate post for this if you want me to, but I wonder, have you guys ever thought about adding a kind of "override" setting, that would prevent saved session clock preference from being able to alter the clocks you decide to want to have shown? Let me know if you would like me to make a separate post about this. Back to the clock issue though, what you mention though maybe could describe the random behavior I was describing. Maybe clocks changed and I saved them with a test session and that is why this occurred so "randomly", because as mentioned I was not aware that this was possible at the time. Also, I might have a little more info on what could possibly be causing this. A setting that I was messing around with for a different issue, was the (apologize I cannot remember the exact name right now) "avoid blinking/flashing lights in GUI" setting. As I mentioned in one of my other posts, I had not realized that realtime clock updates was one of the "blinking lights" that this setting turned off. I spent of bunch of time trying to help narrow down the cause of this "bug" for you guys, before realizing that it wasn't one :) So after turning that setting off, I have not noticed this issue occurring any longer. Being that that blinking light setting does have a connection to the clocks, it might be possible that it could be a cause of the issue I mentioned in my original post above? I have not tested this theory out yet because I am still trying to see if I can generate this clock issue with this setting turned off. But just mentioning to you guys / other users to maybe keep an eye out for this if have that setting turned on. Hope this helps in some way. Thank you again for looking into this and for sharing this information that I was unaware about the clocks. |
|
|
The idea is that some project may only require music time (say you do sequencing) while another project is a soundtrack for a film where you never need it. So the setting is saved with each session. Using the most recently used setting for new sessions is also intentional. No need to file a report. You can also explicitly write defaults in Session > Properties > Misc. |
