Different time signature for 1 out of 5 instruments? (4/4 vs. 12/8?)
Hi.
In the piece attached, I need to use the 4/4 time signature, whilst the other instruments are still in 12/8 time.
How do I accomplish that?
I am referring to measures 28 and 29 for trumpet 1.
Thanks
Peet
| Attachment | Size |
|---|---|
| Il_Silenzio - N Rosso Celeste & G Brezza (5tet).mscz | 64.69 KB |
Comments
See https://musescore.org/en/handbook/time-signatures#local-time-signatures
I believe you'd need to delete the linked parts and regenerate them after having added that local time sig
You are going to have to recreate the Trumpet 1 staff (I would do it immediately below the existing one. Fill the staff with notes (by using copy and paste) to include measure 27 then enter the local 4/4 time signature by ctrl+drag it from the palette. I would next put the 12/8 time signature back into measure 30 at this point. You can then manually enter notes in the 4/4 section, you will not be able to paste into it. Since measure 30 has the same time signature as the other instruments you can continue the copy and paste method of entering notes at that point. Once all the notes are in the new staff, you can delete the unneeded trumpet staff.
The problem is that a measure that has ever been changed cannot have a local time signature entered into it (or removed from it). Even if you delete the contents of the measure, MuseScore remembers that the measure once had notes in it and is not considered empty.
In reply to You are going to have to… by mike320
Actually, it's not true that MuseScore remembers a measure once had notes, but it is true that lots and lots of other things can get in the way of MuseScore being able to add a local time signature, and it's a very finicky and somewhat buggy feature.
In reply to Actually, it's not true that… by Marc Sabatella
I know that if you enter notes, select the measure and press delete MuseScore thinks the measure is not empty.
In reply to I know that if you enter… by mike320
I tried this and it works fine:
1) create new score SATB template, 4/4
2) enter notes into measure 3 of alto staff
3) delete them
4) ctrl+drag 2/4 to measure 3 of lto staff
Result: success
So, something 8else* must be going on in the example(s) you have tried to trigger the message - there is nothing in MuseScore capable of remembering former contents of a measure. One possibility is that due to a corruption in the measure, your attempt to delete the notes wasn't fully successful.and some invisible remnant was left behind. But this doesn't happen in the general case.
In reply to I tried this and it works… by Marc Sabatella
I have finally figured it out. It has something to do with the existence of notes in other measures. Even though the local time signature does not affect the other measures, removing it from an empty measure that has another instrument in the global time signature with notes leads to an error.
In your example you can drag the 2/4 to measure 3 of the alto staff, enter any notes into the bass staff in measure 3. Removing the local time signature will cause an error until all instruments have no notes in measure 3. If you enter notes into the bass before entering the local time signature into the empty alto measure, it will allow this. Immediately try to delete it and you will get an error until measure 3 is completely empty.
In reply to I have finally figured it… by mike320
Correct - there are some operations that require not just the staff being affected but all staves in the affected range to be empty.
The local time signature code could definitely stand a bit of an overhaul. The basic design is sound, I think, but what happened in the run up to the release of 2.0 was, as we discovered more and more bugs that led to corruption and/or crashes, we realized that complete fixes would require much rewriting, and in the end made the difficult decision to simply disallow certain operations that were creating problems.
I suspect someone with a couple of months to spare could probably go back in and really fix some of the underlying issues and make the facility more robust. It actually wouldn't make a bad GSoC project, except it's probably not the sort of thing many students would be excited to work on.
In reply to Correct - there are some… by Marc Sabatella
Properly fixing this requires replacing ticks with fractions everywhere in the code (except in MIDI-specific functions, of course). I believe Werner plans to do this at some point and may have started this already.
In reply to Properly fixing this… by shoogle
I hope so. It definitely needs fixed.