Editing note length without "eating" next notes or adding rests ?
Changing a notes' length in MS is not something easy.
Either it will "eat" next notes, or it will introduces rest that are difficult to get rid off.
I would prefer MS moving the notes around than that behaviour.
E.g. 
If I press "Add triplet" on the 3 first quarters, instead of having a triplet, a quarter and a rest (Expected situation), I've got that weird situation of those 3 triplets of eight notes (Add triplet situation). Until now, I've not been able to solve these kinds of situation otherwise that copy/paste and delete.
I'd be so easier if MS could just move the notes.
Is there a way to activate such a mechanism ?
| Attachment | Size |
|---|---|
| Screenshot 2021-05-16 000411.png | 21.57 KB |
Comments
If you select three notes and press [UpArrow] they all go up by a semitone. If you select three notes and press [Del] they get deleted. If you select three notes and press the shortcut for staccato, they all get staccato. Now, if you select three notes and press the shortcut for triplets they all get made into triplets.
The correct (i.e. currently accepted) method for making triplets is documented in the Handbook. If you want it to do what you are trying to do (turn those notes into a triplet and move the next, unselected, note back a slot) then you can put in a Feature Request (it may have already been requested, of course).
In reply to If you select three notes… by underquark
Thanks for your answer. But actually, my question isn't really about triplets. This is about how changing the rhythm of some notes is impacting the next notes (here triplets are just an example).
![Screenshot 2021-05-16 090229.png]( "Screenshot 2021-05-16 090229.png")
Other example:
Here the next notes are just "eaten" by MS :-(
Feature Request ?
In reply to Thanks for your answer. But… by parkingb
There's the Insert mode, see https://musescore.org/en/handbook/3/note-input-modes#timewise
Other than that: just get used to it, it is unlikely to change.
In reply to There's the Insert mode, see… by Jojo-Schmitz
Or switch to Dorico where they have recognized the need for a true insert mode which has been sadly denied here for years. Probably because the data structure in the implementation have been wrongly designed a long time ago (it is measure based instead of note based) which makes implementation of things such as full copy or measureless mode pretty much impossible. Well not impossible but certainly very difficult.
Switching to Dorico means paying lot of money but more importantly saving your work in a proprietary format, so that would be a bad idea though.
In reply to Or switch to Dorico where… by frfancha
It is indeed way too deep in MuseScore's DNA to be an easy change, it would require a major redesign.
IIRC Capella has such a mode too. Including the problems that go along with it.
In reply to There's the Insert mode, see… by Jojo-Schmitz
I tried the Insert mode.... Well not really efficient.
![ms1.png]( "ms1.png")
I came to a situation where my measure misses one eighth:
Solution to that: add a dot to the last quarter ! Well... no? MS handles that really strangely.
![ms2.png]( "ms2.png")
In reply to I tried the Insert mode… by parkingb
Then you didn't use Insert mode
In reply to Then you didn't use Insert… by Jojo-Schmitz
Well, When I'm in "Insert" mode I can only add notes, not changing note durations.
Selecting a note, going to Insert mode, and then pressing on the "dot"/"whole"/"'half"/... does not do anything. Should it ?
In my case, I've to leave the "Insert" mode to have the knobs doing anything. And then, it does what's on my screen capture.
(I couldn't upload a video capture).
In reply to Well, When I'm in "Insert"… by parkingb
So add an 8th, then change duration of that quarted to a dotted quarter
In reply to So add an 8th, then change… by Jojo-Schmitz
Exactly the purpose of this thread: everything is feasible but with lots of extra steps that shouldn't be necessary.
In reply to Thanks for your answer. But… by parkingb
I realize that your example is a simple one. But,FWIW, Sibelius insert mode (Change Duration) will change the dotted half to a whole and move the 16ths over a beat. But the number of steps involved is roughly similar to, in MuseScore, selecting the 16ths/hit "R"/select the dotted half/select whole note.
I doubt any platform will let you select a note and change the value and automatically move subsequent notes accordingly. The software has no idea what you want unless you tell it. In this case you wanted a whole note on beat one. It did exactly that. How was MuseScore supposed to know what you wanted to do with the 16th notes?
In reply to I realize that your example… by bobjp
What is the point of your intervention ??
"I doubt any platform..."
Well there is one being Dorico. Sibelius experts were first skeptical when that was announced until they tried Dorico and recognized how well it works
In reply to What is the point of your… by frfancha
So, in Dorico, you select the dotted half, change it to a whole and the 16ths move over. What if I want the 16ths to go away? What happens if you change the dotted half to a quarter note? Do the 16ths move to the left?
What is the point of my intervention??
??
I have no doubt that Dorico, being newer, can do some things that other platforms can't. It depends on what you are trying to do.
In reply to I realize that your example… by bobjp
Here is how it GuitarPro handles this (*):
![GuitarPro.png]( "GuitarPro.png")
Its principle is to
* limit the impact of the modification to the current measure, leaving this measure either incomplete or my too many beats (none are outside of MuseScore's DNA).
* provide a function to reorganize the measures/beats correctly.
My first example is done in 2 steps in GuitarPro:
![GuitarPro2.png]( "GuitarPro2.png")
* Convert the 3 quarters to triplet: 1 keystroke
* Convert the last quarter to half : 1 keystroke
MuseScore can certainly get some inspiration here.
(*): which is (for me) by far more efficient at the level of the editing of score notes than MS.
In reply to Here is how it GuitarPro… by parkingb
Well, if your example wasn't involving tuplets, MuseScore single measure insert mode would work as easily as what you are showing.
Point is that changing notes from/to tuplets in MuseScore is pretty much impossible, and that should clearly be improved, but for the rest their single measure insert mode does exactly what you would expect.
In reply to Well, if your example wasn't… by frfancha
Insert is working fine. Modifying is a possible but longer story.
![dotted-half.png]( "dotted-half.png")
* 5 steps in MuseScore ( 4/4->5/4, add a rest after the dotted-half, remove the dot, change the half to whole, delete the rest added when moving from 4/4 to 5/4)
* 3 steps in GuitarPro ( 4/4->5/4, remove the dot, change the half to whole)
There is room for improvement here in MS.
Whenever I'll find some time, I'll take the source code from Github and dive into it. Is there an official way to proceed with Change Requests ? Such as discussion boards ? I would go for a "Timewise edit"...
In reply to Insert is working fine. … by parkingb
Or, in MuseScore, insert quarter note after dotted half, change dotted half to whole, change 4/4 to 5/4.
In reply to Here is how it GuitarPro… by parkingb
lvr124, "MuseScore can certainly get some inspiration here."
Totally agree. I used GP6 for a long time before moving to MS and it handles these types of measure operations efficiently and intuitively.
In reply to Thanks for your answer. But… by parkingb
You want to create a 5/4 measure? Just create one. You also want to Ctake the four sixteenth currently on bet four and move them to beat five? So just do so, directly cut and paste, simple as that. You also want to change the duration of the first note from dotted half to whole note? So do that too. Move the moves you want to move, change the duration of notes you want change the duration of, you're in complete control of whether you do just one of those operations, both, or neither.
In reply to You want to create a 5/4… by Marc Sabatella
No, "cut and paste" is not "simply as that"
For simple changes where only one keyboard or mouse interaction would be enough cut and paste will require at the very minimum 4 interactions.
That's the whole point of this request.
In reply to No, "cut and paste" is not … by frfancha
> No, "cut and paste" is not "simply as that"
Yes, you got my point :-)
Let's not be blind. There is room for improvent in MS on that matter.
In reply to > No, "cut and paste" is not… by parkingb
Sure there is room for yet more features. but the point is, cut and paste does work. Try it. It completely and totally handles the case shown here and millions of others. Your initial post shows you haven't yet learned how to use this to solve that problem, and so I showed you how you can indeed very simply solve that problem using the tools provided already.
After you learn how to use the tools that are already provided and work perfectly to solve problems like this, then one can begin to consider whether complicating the interface by adding yet more tools to accomplish the same thing but in a different way would be warranted.
In reply to Sure there is room for yet… by Marc Sabatella
Let's stop the talk. And even if in this single thread we are already 3 to say Musescore is not efficient in that domain, I understand why it is difficult for you to hear that.
So let's be constructive. What's the feature request mechanism here ? So that I can expose my proposition, have a chat, a vote about it, and (why not) implement it myself (I feel confident enough with MS data model) .
In reply to Let's stop the talk. And… by parkingb
To post an official suggestion/request go to the Musescore issue tracker.
Set the Severity Level to S5 (suggestion/request) before submitting your post.
scorster
In reply to To post an official request… by scorster
I recommend against using the issue tracker until a consensus is reached on a solid design proposal here in the forums. Otherwise it will likely go nowhere.
In reply to Let's stop the talk. And… by parkingb
I am being constructive. You posted steps showing you had not figured out how to accomplish this task, so I volunteered my time to provide you with free information to help you. Step one in continuing a constructive conversation would be to acknowledge this and stop accusing me of not wanting to hear suggestions.
If you have design experience and ideas on how to design alternate features to accomplish that same task differently, feel free to make a proposal on the feature request forum. The more specific the better, as the general idea of this has been floating around for years, but no one has really ever taken the time to think through how it would work in practice.
In reply to I am being constructive. … by Marc Sabatella
Marc, These guys won't engage with me either. Except to push their own agenda. I asked a simple question about Dorico.
In reply to I am being constructive. … by Marc Sabatella
Sure. I'll do like that. I already created the thread yesterday.
https://musescore.org/en/node/321244
Give me sometime to phrase my proposition correctly and do some screenshot to illustrate it.
Sorry if I've "hurt" you. And thanks for all the work you are doing trying to help other ones in this forum.
(And no agenda here, except the one to see Musescore even better)
I fell foul of this first time I made a triplet but the Handbook has the answer.
https://musescore.org/en/handbook/3/tuplets#instructions