tuplets not easily deleted

• Sep 4, 2014 - 08:09

Expected behavior is 'Tuplet...' in the context menu - or something in Inspector, perhaps - that would include 'Delete Tuplet'. It doesn't exist; the only way to get rid of the tuplet is to delete a range that includes the tuplet; nothing will un-create or undo the tuplet per se.



This isn't quite true - if the tuplet has a number or bracket, selecting that and hitting Delete deletes the tuplet.

But it would be better if selecting just the notes in the tuplet deleted the tuplet. It would even be OK if it first deleted the notes but replaced them with rests (as it does now) if a *second* press of delete deleted the entire tuplet.

A tuplet should always have a number or bracket. If you dont want either you should mark the tuplet as invisible. Then the tuplet is easy selectable and can be deleted.

The current version of MuseScore allows to select a tuplet even if it does not have a number or bracket. This can be done via the inspector by first selecting a note or rest of the tuplet and then click "Tuplet".

Title tuplets cannot be deleted tuplets easily deleted

I don't know; I personally would still prefer the behavior I proposed. There were already workarounds, now we have a new workaround, but it still feels like a regression compared to 1.3 to me. A minor one, though, I guess.

Not sure what got fixed in Nov 2014 ? I've been manually cleaning up this score imported from a PDF. Everything went pretty smoothly until I encountered the invisible(?) sextuplet in measure 4. There is no direct way I can see to remove the tuplet property, it appears I would need to delete the notes and re-enter them manually. Is this correct ?

select one note of that invisible 6-tuplet, click on the toplet button at the bottom of the inspector, now set number type to number and bracket to automatic.

Now you can at least see the tuplet. You can remove it by seleciting the number and/or bracket and hitting delete.

Anyway, questions like this are better suited in the forum rather than the issue tracker...

Hi, thanks for the quick response. Following your instructions deletes all the notes in the tuplet as well, so it does appear that I will need to re-enter them manually, as I expected. I was hoping there might be a way to remove the tuplet property, leaving the notes with their nominal 'native' time values. In my particular case it would have filled out the measure perfectly. Again this situation arose out of a PDF conversion, misinterpreting a chord symbol I'm guessing.

Sorry about posting here, this was the only relevant result of searching the site for "remove tuplet".

There is no such thing as a "tuplet property". Notes have a specific time position and a specific duration. "Tuplet property" or no, if you have notes that have a duration of 1/6 of a beat, and that start every sixth of a beat, that's a tuplet. That's a tuplet no matter how you slice it. You would need to individually change the time position and duration of each note in order for it to not be a tuplet, and that would ultimately be more work than simply reentering it.

In reply to by Marc Sabatella

Also having this difficulty. The problem is that the "tuplet" isn't meant to be there, and can't be removed without re-editing the whole bar. Merely removing the number does not solve the issue, because the software believes that there is a tuplet there, and applies the rest. This issue has not been resolved as of the 24 Dec 2017 version of the software.

More specifically, if you are still finding you have a score in which simply deleting the tuplet is not working, then in order to help, we would need you to ask for help in the Support forum, and attach the specific score that is giving you trouble. Most likely, either the score is corrupt and we can help you fix it, or the score is fine and there is simply a misunderstanding over how to delete tuplets. If it turns out some unusual special aspect of your score is exposing a heretofore undiscovered bug in MsueScore, then we would direct you to submit a new bug report. But the issue described in this thread was fixed long ago, so whatever you are seeing is unrelated.