complete triplet functionality
As far as I can tell, it is impossible to create a grouping of triplets where one of the triplets is replaced by two sextuplets (when attempting to do this, musescore breaks the last note out of the grouping of 3 into an odd assortment of rests).
Also, I cannot find anyway to remove triplets once they're created.
And lastly, when copying measures containing triplets, it doesn't maintain the notation or groupings of 3. The result I got was very messy, although the MIDI playback sounded the same.
Comments
Are you using the latest version of MuseScore that was released a few days ago (version 0.9.3). It fixes some issues with copy-paste of triplets.
I wasn't able to reproduce the first issue you describe with triplets and sextuplets. Could you specify step by step instructions if you still encounter this issue in 0.9.3?
I can confirm your difficulty with removing triplets. As a work-around you can copy a blank measure and paste over the triplet measure to clear it.
In reply to Version 0.9.3? by David Bolton
I'm using version 0.9.1, which is listed in synaptic as being the current version. Do I need to enable another repository, do a manual install each update, or is there an incorrect setting causing this?
Let me know and I'll try updating and see if that fixes things. Thanks for the help.
In reply to Looks like an older version, trying to update by hazysonic
I presume you are working on Linux. Check your package manager. In case the package is not up to date (0.9.3), try to get in touch with the MuseScore package developer.
I have a workaround that sometimes works. Select all the notes and rests belonging to the triplet, then press Del. I think it always works for notes alone but it sometimes fails with rests, and I could never delete the triplet if the notes/rests are not displayed. I have also encountered other problems with triplets. Firstly I could not enter using keyboard in the same way as for other notes, for example when I have created the triplet and want to edit it by typing in the note letters. Also a minor issue is that it does not playback properly on input unlike normal notes.
I have a few other issues with note entry and I'll just mention here. First I would like Backspace to remove the last note entered (as someone else has brought up), and Delete to be able to be followed up with more keyboard note entry without having to click on existing notes with the mouse. Also I would like an easy way of navigating the melody lines (multiple notes in chords and between staffs). I also found a reproducible bug: Open a score with some filled bars, click "Play", press Space (to pause), then press and hold Ctrl-Right (to navigate by bars). The cursor scrolls to the end then MuseScore crashes (without any signal). I am sorry I haven't tried these with the new releases yet because I want to complete writing some scores with the current stable release first. I am using Windows XP with MuseScore 0.9.3.
[edit]
I have two more requests. One, that there is a way to change a note to its enharmonic equivalent, preferrably with keyboard shortcut, because MuseScore guesses wrongly with pitch spell especially with rapid modulations, and when I manually apply accidentals it does not realise that the same accidentals already appeared in the same bar. Two, that the accidentals are placed as close to the chord as possible but without touching. For chords with many small intervals, MuseScore either places the accidentals too far or overlapping each other or the chord itself. If any of these problems are solved with the new release I would be glad to know, and I will try it out.
[/edit]
(I'm sorry somehow putting 0/1/2 blank lines between paragraphs or using HTML tags does not break them..)
I find it very revealing that the issue with triplets goes back 9 years. I thought it might be resolved in 10 - 20 years, but I'm revising my estimate to 50 to 100 years.
In reply to I find it very revealing… by gBouchard
Actually, every single one of the issues listed in this 9-year-old thread were fixed many years ago. It's quite an achievement, indeed - there are probably 10 different issues discussed here, and not a single one of them still exists. So this thread is proof that feedback here in the forum can and does lead to very real improvement.
But one of the issues here - certain copy/paste operations creating corruption - is precisely why some of these operations were disabled. Better to not allow something at all than to allow it and have your score destroyed as a result. Better still to make it actually work, of course, but as mentioned, easier said than done. If you have programming skills, feel free to volunteer your time on this as many of us have over the years.