Removing ties shortcut
Hi!
Is there any way to toggle note ties on and off?
Thanks
Uri
Do you still have an unanswered question? Please log in first to post your question.
Hi!
Is there any way to toggle note ties on and off?
Thanks
Uri
Do you still have an unanswered question? Please log in first to post your question.
Comments
No. + to add, Del to remove
Well, if you mean, you have a whole passage of music where you want to remove the ties, you can do that the same way you'd remove the lyrics, articulations, or anything else: select the passage, right-click one tie, Select / All Similar Elements in Range Selection, then delete.
In reply to Well, if you mean, you have… by Marc Sabatella
No, I mean like an on / off kind of toggle. Would it be very hard for it to be the same key? Like, "+" on a note with a tie, removes the tie...
Cheers
Uri
In reply to No, I mean like an on / off… by urisala
Not sure why you'd want that when delete already does it? If you explain your special use case in more detail, we can understand and assist better. Deleting ties would normally be a very rare operation, so it would be good to understand what it is you are doing that has this coming up for you.
In reply to Not sure why you'd want that… by Marc Sabatella
Delete means:
1. lift hand from keyboard
2. get the mouse
3. click on the tie
4. press delete
...right? Would be nice if it was a 1-key solution.
In reply to Delete means: 1. lift hand… by urisala
The reason I asked for more context is that I am having trouble imagining what kind of workflow you have that involves creating ties and then later deleting them on a regular basis. Of all the markings MuseScore can create, ties would normally need to be deleted less often than virtually anything else, so I'm really struggling to understand what it is you are actually doing.
In any case, you only need to do steps 1-3 if you made the additional mistake of selecting the note rather than the tie to begin. Why not just select the tie, rather than first select the note then change your mind and decide to select the tie? If it's because you want to select things with keyboard only, that's fine, after navigating to the note you want, simply use Alt+Right or Alt+Left to select a tie that is attached. but again, I'm not understanding how this comes up more often than once every thousand measures or so. Are these ties you entered yourself but are now changing your mind about because you wish to shorten the note? Instead of deleting the tie first, just shorten the note directly. Or maybe you are editing a score where someone erroneously entered ties instead of slurs? Note you can also select multiple ties at once as I described above. Again, if you explain what's actually going on to cause you to have all these extra ties that seem to need deleting, we can probably help with something far more efficient than requiring you to delete them one by one using a shortcut.
In reply to The reason I asked for more… by Marc Sabatella
Alt+right / left doesn't select the tie for me...
You'll have to take my word that adding and removing ties is something that I do a lot in my compositional practice. Like several times every measure, not once every thousand ;) What I have used once every thousand is, well, TONS of things that are there in MS... I am really after a direct answer to the question "would it be possible to add a tie toggle". I have no idea really, but I am guessing it shouldn't be a major difficulty? Have a nice sunday!
In reply to Alt+right / left doesn't… by urisala
What does Alt+Right do instead? Should traverse each and every element of your score.
Anyhow, without a better understand of the unusual nature of you workflow - how these ties you don't want are coming to exist the first place, for example, it's difficult to assist further. Can you attach a samole score and describe how these ties are creeping in and when/where/why you are wishing to remove them?
It's certainly possible to add a tie toggle, but it's not necessarily advisable without evidence that the desire to remove ties is actually common. Otherwise people may find themselves accidentally deleting ties. That's one reason it's crucial to understand your special compostional practice (are you dealing with an experimental notation, perhaps?)) Another is that is may turn out the ties are appearing in the first place only because of some misunderstanding or error on your part, and once we correct that, you won't need to waste time toggling ties at all. Wouldn't you rather a solution that prevents to the need to toggle ties several times a measure?
In reply to What does Alt+Right do… by Marc Sabatella
alt+right does nothing on my 3.3..
And I really need a toggle, not a workaround or suggestion ;) Yes, I am trying a contemporary music technique
In reply to alt+right does nothing on my… by urisala
Check Edit / Preferences / Shortcuts and see if “Next element” has been defined. If you are on. Mac, note it’s probably Option instead of Alt.
Anyhow, as I said, without an understanding of your special workflow, it’s unlikely that a command would be implemented to optimize it. So if you really do want this, it would, again, help if you explained the situation in more detail.
In reply to alt+right does nothing on my… by urisala
I should mention also that one reason I am confused is that, at least in the normal/common cases, "+" does remove existing ties, at least in the current version of MuseScore. So it could be something about your unusual case that is causing this not to happen for you. Or it could be that you are using an older version. But I have been assuming you want something different from the normal behavior, and that's something we need more context to understand - in which cases do you need it to be different, and exactly how it would differ.
In reply to I should mention also that… by Marc Sabatella
Ok, this is the 3rd time in a row I go down the "why would you ever want to do that!"-rabbit hole when requesting a feature, only to find out that the feature is there all along. Now it's me who is having a hard time understanding what was not to understand about my original question, and how the answer was not an immediate "this exists in 3.4, make sure you update"...
In reply to Ok, this is the 3rd time in… by urisala
Perhaps next time include your version information in your request. Or check for updates ;-)
In reply to Perhaps next time include… by jeetee
I said I was in 3.3 some posts above. And I check for updates. I have nowhere seen us being informed about about the implementation of the tie toggle.
In reply to I said I was in 3.3 some… by urisala
Not in this post. None of us can remember which user once said which release (s)he's using, nor whether this is still true.
If you check for updates,you'd see that 3.4.2 is available and since quite a while
I don't know either since when this + toggle exists
In reply to Not in this post. None of us… by Jojo-Schmitz
I know now: since 3.3.3 and it is in the release notes: https://musescore.org/en/handbook/developers-handbook/release-notes/rel…
Tie button behaves as a toggle now
So you're not even on the (2nd to) latest 3.3?
In reply to Ok, this is the 3rd time in… by urisala
Well, asking for features but not being on the latest version would one good reason for such confusion
BTW: I just noticed that feature myself, never knew it existed, nor since exactly when, regardless closely monitoring (and participating in) the development...
In reply to Well, asking for features… by Jojo-Schmitz
I respectfully disagree. My opinion is that it is perfectly legitimate to ask for features even if you are not on the latest version. A lot of people don't update to the latest version on purpose, you should understand that. It seems that you are just considering that there are 2 options:
1- Always be on the latest version
2- if you are not, make sure you read all the release notes anyways — and that is granting that the addition appears somewhere.
Not sure it's the right move to demand this...
In reply to I respectfully disagree. My… by urisala
I agree it's legitimate to ask for new feature even if you've made the conscious choice to avoid updating and getting the features that are already added. But practically speaking, it's also going to be more productive if you are upfront about not having updated. This would be a good tip-off to the people who are volunteering their time to help you that maybe it's been added meanwhile. That way no one - not you who are sitting around awaiting help, not the volunteers who are trying to provide the help - wastes time unnecessarily. And again, when people ask for more information in order to understand and assist better, it takes less time to simply provide the information than to get into an argument about why you shouldn't. It's up to you of course, but I promise, it really does go better this way. We've been doing this for ten years now, we've helped untold thousands of happy users during that time.
In reply to I agree it's legitimate to… by Marc Sabatella
I was not aware of the expectation that we should always be updated, otherwise we should say so. Lesson learned, it is good practice to state the version one is on. Not sure if it warrants the placing of the blame fully on my side, as well as the appeal to experience, though. One could also say that support groups, when being asked about a problem or getting a request, should first try the thing, and if it works, tell the guy <>". But pointless to play the blaming game. Will try to remember to state the version from now on.
Still disagree that me stating my compositional practice in more detail would have played a role here at all, still don't know what was not to understand about a "tie-toggle".
In reply to I was not aware of the… by urisala
the text between <> disappeared. it should say: "i tried it on my computer and it works. Sure you are updated?"
In reply to I was not aware of the… by urisala
When a feature gets requested, we'd need to understand why it gets requested to make sure it isn't just a misunderstanding on how the program works, or to find that it exists already, just in a slightly different way, as well as to understand the intended workflow, so that if it is going to get implemented, it fits the needs.
In reply to I respectfully disagree. My… by urisala
These are not the two options we mentioned:
1. Be on the latest version
2. Mention your version in your request (which I indeed now see you did in a later reply)
But yes, when someone asks for a feature I didn't know about (as a transcriber I virtually never have to remove a tie), I indeed assume that they're using the latest version.
For complete reference, the change in tie command is mentioned in the 3.3.3 release announcement: https://musescore.org/en/3.3.3
In reply to Ok, this is the 3rd time in… by urisala
Since you were requesting the feature, we assumed it didn't exist already, or didn't work that way already in your unusual special case. We simply didn't have the information we needed to understand why the existing tie feature wasn't working the way you wanted. We didn't know you were using an old version, but also, maybe your unusual special case involved note input mode rather than normal mode (the toggle is necessarily only in normal mode). Maybe your ties were unusual ties, like cross-voice, or extended to a note not the very next note. It was frankly impossible for us to say what exactly was going on without more information on your particular brand of contemporary notation and your unique workflow. When we ask for more information, it really is so we can understand and assist better. Resisting such requests does no one any good, it just makes everyone frustrated on both sides.