Tuplets over barlines improvement

• Apr 8, 2021 - 05:39

Hello,

Since this feature has been requested many times* in this forum from about one decade and assuming the related workarounds are not sufficient I think my question is legitimate :

Is this feature not implemented because of the internal MuseScore semantics / musical representation / "measure tyranny" or just because no one has dedicated time to it yet ?

What are the real technical issues ? Maybe MuseScore 4 code will facilitate this improvement ? Is this feature planned for the next decade or is there no perspective for this improvement ?

Looking forward to reading you !

Thank you in advance for your time.

Best,

Full question there (why workarounds are not sufficient) :

https://musescore.org/en/comment/reply/node/306604/comment_forum/107290…

First request a decade ago :
https://musescore.org/en/node/12284

  • many times :

https://musescore.org/en/search/content?keys=Tuplet%20across%20barline

https://musescore.org/en/search/content?keys=Tuplets+over+barlines


Comments

Is this feature not implemented because of the internal MuseScore semantics / musical representation / "measure tyranny" or just because no one has dedicated time to it yet ?

I guess it is a bit of both.

It is also in the issue tracker (and since ages): #19887: Tuplet across barline

In reply to by Jojo-Schmitz

Many thanks Jojo-Schmitz,

So even if I were good at C++ I would not be abble to implement this because of the actual underlaying structure ?

Please tell me honnestly if a C++ programmer could fix it easily at this time or if we have to wait several months or years before it will be possible (internal restructuration...) ?

I really have to know if I can trust MuseScore to grasp this kind of laks in the next decade... ?
I search for a fully functionnal open source alternative to Dorico. If certains MuseScore improvements were too incertains I'll go Lilypond but I would like to stay on MuseScore.

Thank you !

In reply to by CB.

The main problem is that while the start if each note of such a cross-barline tuplut would fall into one of the or the other measures, but the total dication of each nute, its ticks, whould cross the barline, so the first note in the 2nd measure doesn't start that that measures's tick 0. This is something MuseScore's code structure just isn't expecting, isn't build for, so a major architectural changes would need bo be made.
That's at least what I believe to be the problem.

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