Tablature stems too long

Can you provide more information about how you created this? When I try to reproduce it from scratch, I don't get that result. Was the file created in the same build you tested with?

The process step by step and with pictures to understand:

Nigthly 17a24d9 / Windows7

- All in Voice1(tab 6.str Full) : begin here

- All ok for the moment

- The stems change of direction: ok

- The issue appears here. When you add the number 3 on the second string.

- When you add one note, the stems decrease, and then a new note, etc., the stems continue to decrease jump par jump.

- And when you add a new treble note, again, the stem is again too long.

Bad news: With the tab 'full' style, the same algorithm as for standard staves is used to layout beams and stems.

I have attempted to debug this issue, but I have not been able to understand that algorithm, which computes dozens of intermediate values, with cryptic names and unclear usage.

I am afraid someone more familiar with that area of the code is required to understand what is going on.

Thanks,

M.

Any insight into why the same basic sequence doesn't cause problems on standard staves, then? Or *can* you reproduce it on a standard staff?

I can't reproduce with 2469284a98
Can anyone confirm please?

Indeed, with this commit (the previous?) : https://github.com/musescore/MuseScore/commit/d85bee21ad42ce5e89bf50a6e…,

I can't reproduce, as you can see in attachment. Good new! :)

I will look tomorrow when this has been fixed.

Unfortunately, the only reason you don't see the issue with that example is that the beaming algorithm changed a week or two ago so that a dotted eighth & sixteenth pair is no longer beamed to a following eighth note. But if you enter all eighth notes, they will be beamed together, and you do still get the too-long stems.

Fixed in 07f7cc6891

Automatically closed -- issue fixed for 2 weeks with no activity.