Local time sigs issue
Hey guys. Im having an issue having two time signatures at the same time. I have them localized but my line that should be in common time is beaming as if it were the 12/8 in the other part.
Any ideas on how to fix this because it make me come to a screeching halt in this piece.
Attached is a picture of the issue.
| Attachment | Size |
|---|---|
| Capture.PNG | 48.72 KB |
Comments
You can change the beaming manually, see https://musescore.org/en/handbook/beam-0
You can change the default beaming by right-clicking on the Time Signature and choosing Time Signature Properties and then "editing" the beams there. (At least, you can in Nightly build 5a8cf68).
This shouldn't happen - the beaming should be consistent with the current time signature for the staff. It works when I try it. Can you post the score you are having problems with?
In reply to This shouldn't happen - the by Marc Sabatella
its attached to the original post
In reply to its attached to the original by jason_burnham
not the image, the *.mscz file
In reply to not the image, the *.mscz by Shoichi
There ya go
In reply to There ya go by jason_burnham
something did not work in the file (Measure 35 Staff 1 incomplete. Expected: 12/8; Found: 0/1)
I attach the updated file, expecting the answer...
In reply to something did not work in the by Shoichi
Ok I got rehearsal 2 to work out but the bar right after wont let me place anything in it.
In reply to There ya go by jason_burnham
The corruption could be a result of #51626: Copy/paste to/from passage with local time signatures produces corruption.. If you originally created this score with an experimental prerelease version of MuseScore (eg, one of the Beta releases), it could also be due to any number of other causes - there were a whole slew of bugs involving local time signatures fixed between the beta and final releases of 2.0. Anyhow, this particular corruption will probably require you to coimpletely remove the affected measure then insert a new one. That seems to have worked for me.
Aside from the corruption, the beaming issue seems unrelated. If I right click the 4/4 time signature and choose Time Signature Properties, it clearly shows the default beaming is set to 3+3+2. Is it possible you did that yourself? It's definitely not the default for 4/4. Anyhow, to fix it, simply change the beaming in that dialog back to 4+4, which is the normal default. Unfortunately, it seems something is wrong with the notes already entered into those measures - they aren't lining up properly. That could possibly also have been a result of copy & paste, but if you don't think that's the case, and if you have any insight into what might actually have happened, please let us know. If you can find steps to reproduce that problem, we can try to fix it. But in this case, you can correct these measures by simply deleting their contents and re-entering them.
In reply to The corruption could be a by Marc Sabatella
Yup I started it in the beta form and swithced to the new version part way through in order to use the localized time sigs in the update. I noticed too that if I delete the problem bars and re do it, that it fixes itself. The beaming I have no idea why its in 3+3+2. As far as im aware, I didnt change it but its totally possible I could have.
In reply to Yup I started it in the beta by jason_burnham
Well, that might have caused by one of the bugs in the beta, so I wouldn't worry about that unless it happens again. I will say that I would not be surprised to find more bugs in local time signatures, but right now, the copy/paste one is the one serious one I know of. For the next release I have tentatively implemented a "fix" that simply disables the operation until we figure out how to get it to work for real. That's also how I "fixed" a number of other issues with local time signatures shortly before the release of 2.0.