Time signature change doesn't appear in parts which don't have voice 1
Reported version
3.0
Priority
P1 - High
Type
Functional
Frequency
Few
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.2.2.7534, revision: c893c61
1) New score for flute, two voices (1 & 2)
2) Enter a few notes in each voice, and with at least two time signatures in the score say 2/4 and 3/4
Test file at this step: Flute.mscz
3) Create individual parts for Flute1 (Voice1) and Flute 2 (Voice2) -> Ok
Test file at this step: Flute parts.mscz
4) Toggle in Parts
Result:
In first part, as expected
In second part, unexpected. The 3/4 time signature change is lost. Hence corruption, leading to crash.
- Same result if other voices 3 & 4. Only the voice1 honors the time signature changes
Fix version
3.5.0
Comments
I just observe this issue was already reported. Here : #282512: Time signatures omitted in voice 2 parts when using voice-to-part feature
So, one is a duplicate of the other. I suggest this one to stay open, it seems IMHO more documented with steps/test files.
(edited title)
(edited)
older issue got reported against 3.0
There are a couple of other serious issues with this feature, I'm guessing they are somewhat related and might not be that hard to fix. Would be nice to get this working for real, although it will still be limited in that it's "all or nothing" - no way to have passages written in only one voice get shared.
Came up again in : #295979: Changing time signature doesn't work for all voices, file gets corrupt
I can look into this a bit. I cannot reproduce the crash however.
Well, from the moment a score is corrupted, the crash is really underlying, and a nothing (or a little more depending on the score) can cause it. E.g. on this score ( fanfare2 parts.mscz) , go to measure 36 -> input double whole note (type 8), and repeat ("R" key) say 3 or 4 times. The crash will occur.
See https://github.com/musescore/MuseScore/pull/5412.
The fix is not correct...
See also #283964: Linked parts for single voices don't work which is somewhat related
And definitly related to #285855: Creating part from voice 2 does not respect key changes
Relates to #296009: [EPIC] Issues with linked parts of individual voices
FWIW, I would argue that this one and a couple of other related ones collectively render the "voices to parts feature" essentially useless - perhaps should still be considered critical, if we choose to make this part of the plan. The voices-to-parts feature was added some time ago as part of GSoC, and it's a great thing, but these couple of bugs render is all but unusable, so basically can't advise anyone to use it right now.
https://github.com/musescore/MuseScore/pull/5972
Fixed in branch master, commit 28d8d8772e
_Fix #291688, Fix: #285855
Solves:
#291688 - Time signature change doesn't appear in parts which don't have
#285855 - Creating part from voice 2 does not respect key change
Used element->tick() instead of segment->rtick() to check whether the element
was at the beginning of the measure._
Fixed in branch master, commit eeba20230e
_Merge pull request #5972 from njvdberg/voice-parts
Fix #291688, Fix: #285855_
Automatically closed -- issue fixed for 2 weeks with no activity.