Feel free to talk to my dayjob boss and pay my consultancy fee, including the penalty fee for no longer working fulltime for my current client -) I can come up with several ways to do this in code and fix it (see the paragraph above for one of them). If the current workaround is too labor intensive, then perhaps a plugin could be conceived to automate the process (like for tempochanges) but apparently, yes in all those years and the grand scheme of things, this one issue hasn't been addressed yet. So this means you now also have to somehow force the playback order information to be available at that point in the flow, of course without impacting editing speed.Īnd yes, for me at least, focusing my free voluntary time on features/issues that have no workaround at all but are at least equally important (from my point of view/value, which is different for every person) makes somewhat more sense than focusing it on things that (although clumsy) have some kind of workaround. It might surprise you, but if you only have a note and the tie command, you simply currently don't have access to this kind of information easily nor is it likely processed at that point in time. So the first change in code would be to allow that, but then be very aware of when it is ok to allow that and all ripple-on effects.Īside from that the tie code is now to be made "repeat-aware". So a tie is defined as something that ties two notes (and exactly two notes) together, not one starting note to two ending notes. That's almost spoken as if you're no programmer. "it shouldn't be THAT hard to programmatically tell Musecore that this note is tied to that note" We shouldn't have to go onto a support forum to find out how to do such a basic aspect of music notation. I find it hard to believe that nobody can come up with a way to do it, I can only imagine that they can't be bothered (over several years) because people have invented daft ways to pretend to do it. Do what all us users have had to do by hand. And if the software can't manage to play the note across the tie, for the whole length it ought to, then don't play the note at the end of the tie, at all. If it starts with a note that's supposed to be tied, draw the ending of the tie. Pseudo-code: When two tied notes have voltas between them, only draw the ending tie to the second note. After all, it can draw ties when they span across bars with a line-break between them. Even if it can't properly PLAY a score through the repeats, it shouldn't be THAT hard to programmatically tell Musecore that this note is tied to that note, and draw the ending of the tie.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |