[Tablature] Note value repeat section: "At new system" renders the same as "At new measure"
Reported version
3.1
Priority
P1 - High
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
No
Project
In the lute tablature "advanced style properties" (Musescore 3) 
These problems do not exist in Musescore 2.
| Attachment | Size |
|---|---|
| MuseScoreProblem.png | 193.28 KB |
Fix version
3.3.0
Comments
Relates to #270551: [EPIC] Tablature issues
New specific title (the other mentioned issue, truncated Preview, is already known)
About this section "Note values/Note Symbols/Repeat", test files:
Never (expected): Never.mscz
Always (expected): Always.mscz
But unexpected (same result) with New system ( System.mscz ) and New measure ( Measure.mscz )
(typo)
The issue here is similar to that in #284002: Tablature: unexpected default behavior with tied fret mark and parenthesis in that it comes down to a check to see if the current measure is on the same system as the previous measure, at a point where the current measure has not yet been assigned a system. I guess code probably stopped working when we started doing partial layout for performance reasons, which changed how and when we assign measures to systems. The solution in both cases may be to put both of these decisions off until later during layout.
In reply to The issue here is similar to… by Marc Sabatella
Unfortunately, this issue has not been resolved by the fix of #284002: Tablature: unexpected default behavior with tied fret mark and parenthesis
Still not working in Musescore 3.
Too bad.
Musescore 2 still works fine for me though.
We did take a look at this but it's kind of complicated. Can someone help me understand the use case for this. It's something used in certain historical lute scores, I gather. Is that the main use case, or are there others?
Hi. For me it is indeed for use in lute tablatures. It makes for an easier to read and less cluttered tablature as only new rhythm symbols are indicated whenever they occur. Otherwise it will only appear on a new system (as a reminder) which is useful.
Thank you for looking into it. Musescore 2 does this flawlessy. Have a nice day. Peter.
For the record, while MuseScore 2 does this flawlessly, it has a number of extremely serious bugs involving things like beaming across barlines and other similar issues that required changes to how layout was performed in order to fix. Also in order to allow automatic placement to create space between systems as necessary, etc. It is the changes necessary for these improvements that unfortunately broke the way this particular feature used to work. The trick will be figuring out how to fix this bug without sacrificing any of the tremendous improvements these changes made possible. No doubt it's possible, it just requires effort, and one step in prioritizing the effort is to understand how commonly used the feature is, which is why I'm trying to understand what other use cases might exist.
https://github.com/musescore/MuseScore/pull/5261 should fix this issue.
Hello mattmcclinch,
I am not sure what to do (not a code expert). I downloaded your "MuseScore-290011-tab-duration" zip. How do I try it out (install it) on mac os x?
Do I need to somehow compile your zip to make a mac os x dmg?
Thank you.
If you are interested in building MuseScore yourself on macOS, the instructions can be found here. Otherwise, you can download this DMG of MuseScore 3 which contains the fix.
.
Thank you very much mattmcclinch ! It works! Problem brilliantly solved! Congratulations! Bravo!
When Musescore offers a future update, should I update or stick to your version?
Maybe you could look into this other problem (#147031: Note symbols are truncated in Tab Preview - you can also see my photo attached at the beginning of the present thread) if you have the time?
Have a nice day and thanks again !!!
If and when this PR is merged, this issue will be marked as fixed, and everyone who has commented on this thread will get a notification. Once that happens, all subsequent releases and development builds will contain this fix.
I looked into #147031: Note symbols are truncated in Tab Preview like you asked, and I have submitted a fix for that issue as well.
In reply to If and when this PR is… by mattmcclinch
Thank you very much mattmcclinch.
When you have time, could you post a link to a mac dmg with both your fixes?
Are you one of the creators of MuseScore?
It is, by far, in my opinion, the best notation software for lute tablature I have tried. I haven't used it yet for anything else in conventional notation where there is more "competition" out there, but browsing through scores posted online, it looks very good for those as well. Anyway, for me, it has really enhanced my tablature production. Thanks again.
Here is a Mac DMG that contains both of these fixes, as requested.
And no, I am not one of the creators of MuseScore. I just contribute patches every now and then.
In reply to Here is a Mac DMG that… by mattmcclinch
Thank you very much. Great contribution!!!
Fixed in branch master, commit 3cd5154f37
fix #290011: [Tablature] Note value repeat section: "At new system" renders the same as "At new measure"
Fixed in branch master, commit 2a1fc1f5d7
_Merge pull request #5261 from mattmcclinch/290011-tab-duration
fix #290011: [Tablature] Note value repeat section: "At new system" renders the same as "At new measure"_
Hmm, these two settings work now, but apparently this has broken another one ("Never"). I'm opening a new issue for that.
relates to #270551: [EPIC] Tablature issues
Automatically closed -- issue fixed for 2 weeks with no activity.