Misplaced Lines
I have installed the Beta version of MuseScore 3.0 on my Windows 10 system. When trying to place dashed lines over solo passages, sometimes the line does not appear where I placed it, but instead pops up to the top of the score. When this occurs, I can't drag the line down to the desired location, because it just pops back up to the top. Sometimes it does work, and sometimes it doesn't. I haven't found any difference in the way I'm creating the line: 1) select the measures involved, 2) Add -> Lines -.> Note Attached Line, and if it appears in the right place I can customize it. If not, I have to find it at the top of the score and delete it.
By the way, I really like version 3.0! I hope there is a fix for this problem (or an explanation of what I might be doing wrong.)
Comments
That's a known issue that was partially fixed but apparently not completely. It only happens when double-clicking the line with a single note selected. Workaround is to select the whole range you want it applied to (even if the range is just the one note). if you see a blue box, you're good. Or use drag & drop.
In reply to That's a known issue that… by Marc Sabatella
Sorry, Marc. I thought my post explained that I DO select the range involved before creating the line. I'll try drag and drop, but the problem I cited still remains.
In reply to Sorry, Marc. I thought my… by chasbo
Maybe it's only the note attached lines that has issues with range selection? That's the only way I was able to reproduce the problem. It wasn't clear that was the only type of line you were trying? That isn't a normal way of placing a line above a staff, it's meant for something different and pretty specific.
In reply to Sorry, Marc. I thought my… by chasbo
Hmmm.... I tried drag and drop and, using this method, the line is properly placed. However, when I try to edit the line (right click and Edit Line) to make it dashed -- no go. The cursor just returns. I can alter or lengthen the line, but no other editing is available. (I hope this doesn't make me a pest!)
In reply to Hmmm.... I tried drag and… by chasbo
What kind of editing do you want to do? Most line editing is done via double click or the Inspector, not sure what you were trying to do through right-click.
Attaching your score would help us understand and assist better.
In reply to Hmmm.... I tried drag and… by chasbo
I'm curious how you are choosing a range to apply the lines to. There are two methods. first is to select a starting note/rest then shift + click the last note/rest, the second is to select the start then ctrl+click the end. I always see the location problem when I use ctrl+click to select the end point.
For editing the line properties it is not necessary to right click or double click like it was in version 2. Everything in version 3 is in the inspector for lines.
If you use double click and then drag the endpoints, auto placement will override most of these actions. Can you explain why you want to edit the length of the line. In version 3 it is probably more important than it was in version 2 to explain the proper step for what you are trying to do.
In reply to I'm curious how you are… by mike320
Sorry for the lack of clarity in why I wanted to edit the line. In my post I thought I explained that I want to make the line dashed -- not solid. There were no problems placing lines in my build of Version 2.3.2. It only showed up when I tried the same thing in Version 3.0. I selected the range by clicking the first note and using shift-click to select the end of the range. This always creates the line, but it jumps to the top of the score. As I mentioned to Marc, I can use drag and drop to create the line, and it works as expected, except that I can't edit it (make it a dashed line) from the Edit Element menu option.
I'll try using the inspector after I post this, but with all due respect I think there is a problem here.
In reply to Sorry for the lack of… by chasbo
You did say you wanted to make the line dashed, but you also mentioned using right click and "Edit Element", which is not how that is done, so I wasn't sure if you were talking about two different things. Edit Element is for putting an element in Edit mode - to change its shape and/or attachment points. As far as I can tell this works as expected. And it's still not clear to me if you really are using the note-anchored line and why, given that you also said your goal was to add a line above the staff, and that is done much more effectively using the palette. So again, we could understand and assist better if you attached your score.
As it is, I don't think there is a problem, aside from the one already acknowledged - note-anchored lines being added to the top staff. But the he Inspector does work to change a line to dashed, just as it is designed to, and Edit Element does work to put the line into edit mode and allow you to change its shape and/or attachment points, just as it was designed to.
In reply to Sorry for the lack of… by chasbo
Please do check it out. I believe the problem to be with your understanding since I've had no problems editing lines besides the known placement issue.
You must have been repeating yourself using different terms and confused me in the process, so I tried to explain different edit options in simple terms in hopes that it would help you. Never doubt that is our ultimate goal.
In reply to Please do check it out. I… by mike320
Thanks for clearing up any confusion I caused about terminology. The appropriate method for editing the lines is now clear to me. Apparently I thought (falsely) the the Edit Element option would allow customization. In any case, the central issue is with line placement. Once that's done properly, the Inspector handles the customization OK. By the way, thanks for your patience, and that of other posters. Your ability to deal with those of us who range from idiots to morons is greatly appreciated.
I have attached a copy of the score I was working on. The problem occurred when trying to place a dashed line over the drum break at bar 22.
In reply to Thanks for clearing up any… by chasbo
The problem is not usually dealing with morons and idiots. The problem has more to do with speaking the same language. The fact you're British (or at least speaking British English is easy to overcome with practice) the difficulty arises when we use different terminology and don't agree with what they mean. It sometimes takes patience to get to the point where we mean the same things. I try to use the terms that will help a user find the information they need in the handbook if they so choose, while you tell me what you are trying to do.
So, are you trying to do something similar to this?
Crammin'.mscz
In reply to Thanks for clearing up any… by chasbo
All's well! This was a case where I tried so many WRONG ways to do what i wanted that the details were all a jumble and it showed in my posts. I apologize for my ignorance and inability to focus on the correct steps given by Marc and Mike. Please just ignore this topic so I can preserve some modicum of dignity.
In reply to All's well! This was a case… by chasbo
Don't be ashamed, 3.0 is different than version 2.x and you must overcome this pesky bug that's hanging on.
In reply to Thanks for clearing up any… by chasbo
All's well indeed!
Thanks for attaching your score, it does help. Looks like you got the line straight (no pun intended), but there are some things I still don't understand. If I click the line and check the status bar, it says it is is a text line and is attached to staff 18, which seems correct. But if I then press Ctrl+R, it pops to the top of the system, which I am taking to be another symptom of that same bug that affects lines placed on double-click with a single note selected. Also, double-click does nothing - that's supposed to be the quick way to get to Edit mode. So something is definitely wrong with that line. But I can't reproduce that myself. If I add a text line to another measure on that staff, it behaves more as I expect.
So I'd like to make sure we fix whatever is going on here. Can you explain how you got that line here?
In reply to All's well indeed! Thanks… by Marc Sabatella
I noticed the measure listed on the line as being at the beginning of the system in the status bar said it started in measure 24 and ended in measure 25. The line is in voice 2, but I can't force it there. What you (@Marc) are probably missing is that part of the line is in the middle of measure 24 and hard to see. You can double click that portion of the line.
Edit: you get very different results selecting the line at the beginning of the system and pressing ctrl+r than the one in measure 24.
In reply to I noticed the measure listed… by mike320
As I mentioned in a previous reply to Marc, I am completely embarrassed by the bandwidth I've used up by this topic. Your advice has enabled me to put it to rest, for which I'm very thankful (but still embarrassed!) If there is any way I can contribute to MuseScore, don't hesitate to ask. By the way, I thought the measures under consideration were 22 and 23. Doesn't matter, though, as that has nothing to do with the current topic.
You guys deserve a gold star!
In reply to All's well indeed! Thanks… by Marc Sabatella
Again, thanks for risking your time on this. I'll take a day or so to exhaustively test all sequences of steps that I've taken, and try not to introduce any more incomprehensible babbling into this fantastic forum. I think what you're seeing is what I meant by 'sometimes it works, and sometimes it doesn't'. The only other fact I can offer before doing a thorough review is that this score was originally written in Version 2.3.2 and then moved to Version 3.0 with an accompanying message that some translation was done. I'm still embarrassed by the confusion I've caused, so I'm tempted to write very little.
In reply to Again, thanks for risking… by chasbo
It might help if you still had the 2.3.2 score.