search

musescore / MuseScore

MuseScore is an open source and free music notation software. For support, contribution, bug reports, visit MuseScore.org. Fork and make pull requests!
https://musescore.org
Other
12.15k stars 2.63k forks source link

Local Time Signatures don't like being implemented in non-chronological order #23411

Open TheodoreBrown314 opened 3 months ago

TheodoreBrown314 commented 3 months ago

Issue type

Interaction

Bug description

Easy example: I have a piano piece in 2/4 where I want the LH to swap to 6/8 for one bar. I first add a local time signature of 2/4 to the bar afterwards. Then I add a local time signature of 6/8 to the bar in question. Now a 2/4 has appeared in the RH as well, and I can't delete that without deleting the one I want as well. If I have notes already inputted in that bar, then deletion works, leaving me with 4 quavers in a 6/8 bar (see photo below), but when I try to correct it back to 2/4, I get an error message saying "Cannot change local time signature, Bar is not empty"

If I wanted to swap to 3/4 afterwards instead of 2/4 then 2/4 still appears in the RH, and deletion issues still occur

These issues seem to occur for all time signatures I've tried. 2/4, 6/8, and 3/4 are just used as examples

image

Steps to reproduce

  1. Create any new file with multiple parts (e.g. Solo Piano, Orchestra, String Quartet), and pick your favourite time signature. For the sake of demostration, use a Solo Piano set the time signature to 2/4 - the below instructions assume you've done this, but they can be generalised to any case
  2. Add a minim to the 3rd bar of the LH. Any note works
  3. Add a local time signature of 2/4 (hold ctrl and drag/drop the time signature) to the 3rd bar of the LH
  4. Add a local time signature of 6/8 to the 2nd bar of the LH. This should cause an extra unwanted 2/4 to appear in the 3rd bar of the RH
  5. Delete the extra 2/4. The one you wanted should disappear as well
  6. Try adding a local 2/4 to the 3rd bar of the LH. You should get an error message

Screenshots/Screen recordings

No response

MuseScore Version

4.3.2.241630831

Regression

No.

Operating system

Windows 11

Additional context

https://musescore.org/en/node/246926 - this thread discusses the fact that this feature was buggy for Musescore 3 as well. In particular, mike320 mentions that the error message pops up if you attempt to add local time signatures to bars that have ever been modified, even if they're currently empty

dcorson-ticino-com commented 3 months ago

May be linked to the fact that this is a piano system. I have used local time signatures a lot recently for a string trio without any problems, but each instrument has only one staff.

TheodoreBrown314 commented 3 months ago

It's definitely not a piano exclusive issue. I first encountered this issue while typesetting Holst's Mercury, and I'm pretty the issue was between the English Horn and Oboe parts. I'll see if the issue replicates on a score with Ob/Eh/Harp though, just to be sure