-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
new way of specifying inter-syllable stretching #923
Comments
I don't quite understand the proposal. To me, it sounds no better than defining them as they are now (as skips) and casting to dimension when doing computations, but I'm sure I'm missing something. |
That would be something like that yes, but it would improve coherence, for instance now we define a different stretching for |
(I'm talking about a case like |
How would it be different if you define a dimension and a skip (with 0 base value) for those things? I think I'm beginning to get a feel for what you're trying to fix, but maybe a concrete example for something like |
It would be the same kind of things I did for In the example
Right now I don't know how it works, I think it takes the rubber of |
Ok, so to sum it up, you suggest we use multiple dimensions to build up a "base" and apply a single skip to it. Makes sense to me. Thanks. |
Exactly yes |
How many cases are there which warrant different stretches? My think-out-loud list has one for between syllables and one for between words, but doesn't differentiate between bars and notes. Should there be a differentiation between bars and notes? If so, is notes->bar the same as bar->notes? Also, bars usually come in singletons, so would bar->bar really be needed? |
Currently we have tons of different values with different stretchings, combined in many different ways, compared in many different ways, etc. and the final output has a stretching which can more or less not be predicted, at least by the end user. The idea here would be to just use dimen for all these values, but introduce their stretching counterparts, specified as skips with a main value of 0. The different algorithm would just work with the non-stretching values, and, just after the final skip they compute, add the corresponding stretching value asked by the user. This would make things a bit more complex to set up, but way more predictable and coherent. What do you think?
The text was updated successfully, but these errors were encountered: