Page moving after a tie is inserted

• Oct 14, 2017 - 17:38

Hello, after searching the forum using key words I couldn't find a thread that addressed this issue. I am transposing some songs from a book using the rhythm then repitch method in MS 2.1. When I go back to tie certain notes together, instead of the screen staying where I last tied notes, it takes off with a mind of its own, going down a few staffs, or to the end of the song. Is there some setting I have turned on or off that could be doing this? Every time it does this, I have to search for where I left off, only for it to move to another spot after tying another pair of notes. Any help would be much appreciated.

s0crate


Comments

MuseScore drives me crazy with its recalculations and redrawing the score every time an edit it made. The score jumps when there appears no reason it should. I don't remember ties being a specific problem with it, but I wouldn't be surprised.

Version 3, which is still in the early stages of development, is going to improve this greatly from what I've heard.

In order to understand what you mean, we would need you to attach the score you are having trouble with and list precise steps to reproduce the problem.

But in general, adding a tie might well increase the space required by a measure slightly, which culd indeed cause the last measure of the system to wrap to the next system, which could have a ripple effect - all perfectly normal. Just like sometimes adding a letter somewhere in the middle of a line of text might push the last word of the line down to the next line, etc.

In reply to by s0crate

It really isn't a "workaround", it's more or less the purpose of "continuous view". This jiggling behaviour was a big problem in version 1, and the continuous view was the outcome of discussion about it. Personally I would always use continuous for entering/creating a score. You only need to start thinking about pages once it is basically all in place.

If I understand correctly, this is recalculation because of a slight change in the amount of space taken. Musescore 2 has a great improvement which avoids this problem entirely: use the "Continuous view" mode while you are actually entering the score.

In reply to by s0crate

Well, not just slurs and ties. Any edit to a score can potentially change the width of a measure and potentially force a measure onto the next system, with the resulting ripple effect I described. This is 100% normal and unavoidable in any page-based view in any program. So if the possibility of this sometimes happens is problematic, you should just plan to do all editing in continuous view - there is nothing special about slurs or ties that makes those particular edits more susceptible to this than, say, changing the pitch or duration of a note, adding lyrics or chord symbols, etc.

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