3:4 tuplet appears corrupted
Reported version
3.0
Priority
P1 - High
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
I am hoping to "translate" Noble chatelaine from Le comte Ory from 6/8 to c using tuplets in a 3:4 ratio. The problem here is that such a tuplet does not match this ratio. I have a sample of this in the file below.
As always, any help is appreciated.
| Attachment | Size |
|---|---|
| Tuplet.png | 11 KB |
Fix version
3.1.0
Comments
In order to assist, we would need you to attach your actual score, not just a picture, and describe precisely how to reproduce the problem.
Adding an mscz file
They are corrupted indeed, the question remains, can you give precise steps to reproduce the problem?
In reply to They are corrupted indeed,… by Marc Sabatella
Go into MS
Create score requiring tuplets
Create 3:4 tuplet (Add->Tuplet->Other)
Add the note with twice the value of the value
confirmed, results in this madness:
![Unbenannt.png]( "Unbenannt.png")
and a corrupted score
In reply to Go into MS Create score… by Pushkin Guy
Steps:
1) Default score
2) Select whole rest -> menu "Add" -> Tuplets -> Other -> Type/Ratio: 3/4 -> Ok
3) Select half note value (or type 6)
4) Enter a C: corruption
5) Enter a second C:
----> crash
in 3.0.4, 3.0.5 and current master
In this scenario, the issue occurs on August 3, 2016, with aed09cc
You get first: corruption, but no crash yet.
![3 août.jpg]( "3 août.jpg")
![3 août suite.jpg]( "3 août suite.jpg")
Then:
The crash appears a few days later (around August 22/25, if it's useful (?), I can precise exactly)
See https://github.com/musescore/MuseScore/pull/4790.
Fixed in branch master, commit c1dd6aead4
fix #285662: 3:4 tuplet appears corrupted
Fixed in branch master, commit b3adb50bd6
_Merge pull request #4790 from mattmcclinch/285662-corrupted-tuplet
fix #285662: 3:4 tuplet appears corrupted_
Automatically closed -- issue fixed for 2 weeks with no activity.