You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The space object is a spacer that occupies musical time without any graphical content. It would be much more flexible if its duration were a fraction. That is, an array of exactly 2 integer objects whose first number is the numerator and the second the denominator.
This would allow a voice to space precisely to any point in the sequence. Consider the following Finale example.
In this example, the quarter note triplets and the half note are all Finale v1. The two 8ths are Finale v2. The challenge is that v2 items launch from specific events (aka, notes) without participating in the triplet in v1. In this case, v2 arises—like Venus on the shell—directly from the middle quarter note triplet. To make it line up, I added a separate v2 triplet on the first of the 2 eighth notes and then hid it. Otherwise they would align as regular 8th notes that happen to launch from an odd location.
A note value quantity cannot represent 1/6 of a whole note, which is where v2 needs to start. Right now my export is converting it (with a warning) to a space of 683 4096th notes, which is the closest possible ratio to 1/6 it can represent. But a fraction would be exact. Given that there is no need to represent a space graphically, I'm not sure why we aren't using a fraction, just like we did with jumps.
I will admit this scenario may be slightly contrived. The more conventional encoding would be to start a triplet in both voices. Then the space would be a quarter (under the triplet). But that is not how Finale works, and it is not semantically what is there either. There is only a single triplet.
The text was updated successfully, but these errors were encountered:
Great idea -- I'm fully on board with using a fraction object. I think that we only should be using note values ("eighth" etc.) where we need to have a visual representation.
Space objects might, however, also benefit from an optional visual representation (for displaying as a ghost note; if hidden/unhidden, etc.) but that shouldn't be the main determination of duration.
The space object is a spacer that occupies musical time without any graphical content. It would be much more flexible if its
duration
were a fraction. That is, an array of exactly 2 integer objects whose first number is the numerator and the second the denominator.This would allow a voice to space precisely to any point in the sequence. Consider the following Finale example.
In this example, the quarter note triplets and the half note are all Finale v1. The two 8ths are Finale v2. The challenge is that v2 items launch from specific events (aka, notes) without participating in the triplet in v1. In this case, v2 arises—like Venus on the shell—directly from the middle quarter note triplet. To make it line up, I added a separate v2 triplet on the first of the 2 eighth notes and then hid it. Otherwise they would align as regular 8th notes that happen to launch from an odd location.
A note value quantity cannot represent 1/6 of a whole note, which is where v2 needs to start. Right now my export is converting it (with a warning) to a space of 683 4096th notes, which is the closest possible ratio to 1/6 it can represent. But a fraction would be exact. Given that there is no need to represent a space graphically, I'm not sure why we aren't using a fraction, just like we did with jumps.
I will admit this scenario may be slightly contrived. The more conventional encoding would be to start a triplet in both voices. Then the space would be a quarter (under the triplet). But that is not how Finale works, and it is not semantically what is there either. There is only a single triplet.
The text was updated successfully, but these errors were encountered: