Clarification: Authoritative Cursor Anchor Position for Beats with Ornaments (PH, bends) in 1.8.x

[AvaTheArchitect]

So this is not a bug, it's a custom cursor alignment fix that I don't know if there is a solution for.. a purely cosmetic
This PH <17> / <15> cursor skew is pure geometry + bounds model behavior.

So on beats like:
5 <17>
3 <15>
custom cursor appears slightly right-shifted compared to the native cursor.

Appears This is strictly:

Beat container bounds ≠ note head bounds

We observed that BeatBounds.visualBounds includes ornament width (e.g., PH <17>), which causes slight rightward cursor skew in custom cursor implementations.

The native cursor aligns correctly.

Which property represents the authoritative rhythmic anchor?

Is BeatBounds.onNotesX the intended coordinate for custom cursor positioning?

What is the authoritative anchor coordinate for a beat, I believe we tried both of these:

•	boundsLookup.findBeat(beat).visualBounds
•	boundsLookup.findNote(note).visualBounds

In AlphaTab 1.8.1, what is the canonical x-coordinate the native beat cursor uses for positioning?

For beats with ornaments (PH <17>, bends, slides, etc.), should custom cursor implementations anchor to:

• BeatBounds.visualBounds.x
• BeatBounds.onNotesX
• NoteBounds.visualBounds.x
• Or another internal property?

In the image I shared it does not happen anywhere but the PH <17> and not so much in a (5) bend situation.

[Danielku15]

For beats with ornaments (PH <17>, bends, slides, etc.), should custom cursor implementations anchor to:

The default alphaTab behavior is to place the cursor with a fixed width, centered at BeatBounds.onNotesX. I'd need to dig through the theory but I think there is no 100% agreement on whether playback cursors should be at the left edge or centered when the note is played. Most references rather talk about the spacing between notes which needs to reflect the rhythm.

https://alphatab.net/docs/reference/api/boundslookup gives some good insight in the sizes but unfortunately has no element .

Centering across the whole width feels generally wrong. from some quick tests:

1. alphaTab uses the onNotesX which is in standard cases the center of the main note head. in cases of displaced note heads this might shift depending on whether the stem is up or down.
2. Guitar Pro also rather considers the "center" of the main note heads the place of the cursor when the note starts playing.
3. MuseScore has rather a weird behavior (IMO). The cursor is located even before the note heads when it starts playing.
4. SoundSlice considers the stem position to be the point when the note is played.
5. Flat.io has the cursor at the left edge of the notes when it starts playing.