types of time signatures
Hi.
In the 'Create Time Signature' dialogue, I recommend that the slash in Text, between the two fields of numerator and denominator, should be removed, and therefore the two fields should be one instead. I’m requesting this since the slash separating the two fields only makes it harder to create alternating and interchangeable time signatures. I also believe that adding the time signatures in each measure can be long work. And so can this be reasonably asked for? If so, I hope it will further enhance users' music scenes.
Comments
You definitely need at least two fields: one for the top and another for the bottom. If you want to have two separate "fractions" (as it were), then you need two fields for each. Additive time signatures work fine with what's built in. For example,
In reply to You definitely need at least… by TheHutch
Yes I did mean alternating and interchangeable time signatures. I have found different separator styles in the master palette (like plus signs, equal signs, and parentheses) under ‘Time signatures’. But how do I use the separator styles in alternating/interchangeable signatures?
And what about inputting more than two separate fractions? Can you please show me how to do that?
In reply to Yes I did mean alternating… by jquesadilla70
To create two separate fractions, you would have to fake it. You would have to apply a "real" time signature that described the total size of each measure and hide it. Then create an image (or perhaps a text field?) with the two time signatures you wanted and place it over the hidden "real" time signature.
I don't know what alternating time signatures are supposed to look like but here's my take on how to do it. It's is a pretty poor example, but it works. The "real" time signature underneath the image is 9/8. The image is bit-mapped; it'd work MUCH better with a vector-mapped image. (I just don't have the software to do so.)
Yes, this is definitely a "workaround". The application can't do this: at least, now and I would expect ever. But if it ever would be able to do it, you would require two fields for each fraction. (Which was where this discussion started) Not one.