Time Stretch

• Dec 28, 2018 - 05:16

Was the time stretch feature for Musescore changed for version 3.0? Fermutas still work the same, but every other articulation, despite having a time stretch property, has it seemingly permanently set to 0.10. Is this a bug, or intended?


In reply to by Jojo-Schmitz

Well, that's rather unfortunate.

I see also that the resolution to having time stretch be stacked on top of each other was to have each time stretch apply only until another note is played, in any voice, in any staff, across any instrument. I'm mortified to think how this will interact with tuplets.

Y'know, I'm starting to think that I'm better off not mentioning any idiosyncrasies that come up when I fiddle with playback, because somehow the "fixes" are always worse.

In reply to by Marc Sabatella

No specific issue, but it would make using time stretch more frustrating due to jumping across voices/staves if there's a tuplet in one voice/staff. For instance, if there's a quarter note triplet in one staff and over the same duration two eighth notes in another, that now requires 5 invisible fermutas rather than 2 or 3, with much annoyance in working out exactly where the beats fall. It gets more complex if you're working with more complex tuplet arrangements.

In reply to by LuuBluum

Invisible ACTIVE fermatas are the single most powerful and useful tool to impart human-like emphasis. I have been using them for a long time, as have most of the composers I communicate with. Their only disadvantages are (1) MS3 still having "I'm new" problems with them (2) they go into XML as real fermatas, confusing both visual output and programs looking for fermatas inserted by the composer (e.g., chorale-line ends). Here's a recent score of mine which relies on them very heavily and produces a very satisfactory effect. https://musescore.com/user/1831606/scores/5342923

Do you still have an unanswered question? Please log in first to post your question.