The note marker doesn’t match the counter; instead of 23.1.1, it displays [time beat 92], and so on.
And this has never worked correctly, as far as I remember. Everything should be identical, both on the counter and in the note marker: 23.1.1 should equal [time beat 23.1.1], and not [time beat 92]
V 2.2.101
Hi @sergeantt67 following because asked what is the mechanism/method of this back in version 1.x but I think it’s counted somehow differently. Somehow every beat is a 1/4 in any circumstances…
Say.. like… but I need to try… in notes time.beat5 will be bar2-beat1 in 4/4 or bar2-beat2 in 3/4, but still will measure time.beat5 for a sure anchor… something like that.
@musicullum , can you help us to understand it correctly?
Hi! I only understand one thing: if the counter (time display), and the one (near the transport controls at the bottom), can count accurately even with two different time signatures and tempo changes in the piece! Then the marker should also be able to do this correctly. There can be no other opinions here, period!
So, two counters can count accurately, but the marker can’t? You know that’s simply not possible! And it shouldn’t be!
No, you’re wrong. The video clearly shows that in this place, each beat is 1/8, and the counter is working correctly. They both adapt to the size of the piece, and in this place, it’s 12/8. I deliberately filmed it slowly by hand so that it would be visible and understandable.
And the metronome, if you turn on its video display, it will also, for example, first beat 4/4 and then switch to 12/8)
I sent you this project in a private message, you can see for yourself that I’m right.
Checked. I’m right. Time measure for Notes are starting with “beat.0” and second 1/4 is measured therefore as Beat.1
Then all is independent from Signature changes and just focusing counting every single 1/4
It can count however it wants.
The marker is attached to the grid on the timeline; it doesn’t matter whether it shows 1/16 , and it should display the value exactly as it does on the counter! I don’t care about its internal countdown.
And you won’t convince me that white is black and that’s how it should be!
exactly. the text cannot know what the user does with time signature.
No, but 3/4 is different from 5/8.
So the counters know their location in the timeline, but the marker can’t do the same? The metronome also knows when to switch from 4/4 to 12/8, but the notation marker can’t. That’s absurd.
I understand, of course, that no one is going to do that, but okay.
And what does the text have to do with it? The text is secondary; the time stamp is placed first, and it already knows its location precisely! Because it’s placed on the timeline.
It’s text. It’s like I send you a text file and it says bar 96 bar 3 (or “96.3”).
Then you switch tempo, or time signature. Then you send a message to this thread “it doesn’t work”.
Well, yes, in the finished piece, will I change the time signature? And the tempo? That’s not an argument. At least I have a cubebase for that. I can change it there, and then I can change the notes if that suddenly happens.
But this is lyrical. I understand your position. It may be a bicycle with square wheels, but it somehow moves, even though it constantly skids. That’s the whole VST live thing.
I have no more questions!
We couldn’t say that to our customers “why do you change that” 
I get your point though. The main reason is performance and modularity. We’ll check if we can improve but it takes a lot of work to establish that communication whenever anything changes.
If your project is static it would probably best to set cursor to marker and input time instead of beats.
BTW @sergeantt67 I don’t really understand why fighting always when ending up at something you don’t like. Also had my question anno (see below, 2024 marc)
but need to accept if developers have a concept. Also (and again, you see, was this in my mind before), it’s not such a thing to keep demainding and demanding and argue how bad this is.
I guess the reason behind: NOTES aren’t anchored to track/timeline, therefore counting just 1/4s working relatively lightweight (no need for exact bar-calculation) and the result - NOTE lines will jump to position - is absolutely the same.
I don’t find this example good at all. It’s rather like measuring your riding distance in meters and never changing displaying in kilometers, because BarNumberDisplay is “just” a flexible grupping of beats in my reading, nothing about “square wheels”.