Linked Staves — Line object editing
Line objects seem "semi-synced" between a standard staff and a linked tablature staff.
Attempts at simple position editing show all sorts of issues afoot.
Linked Staves - Line object editing .mscz
scorster
Do you still have an unanswered question? Please log in first to post your question.
Comments
Hmm...
I encounter some anomalous behavior when re-sizing and re-orienting those lines.
Aside from being an exercise of discovery into the behavior of those "synched" lines, is there some notational purpose (and/or meaning) that you are striving for by incorporating such lines into a score?
Perhaps there is another way to achieve your goal.
In reply to Hmm... I encounter some… by Jm6stringer
Jm6stringer wrote >> I encounter some anomalous behavior when re-sizing and re-orienting those lines
Hi jm. Thanks for confirming anomalous behaviors!
Jm6stringer wrote >> the behavior of those "synched" lines
I'd classify those Line objects as "semi-synced." Because sometimes they operate independently, sometime not.
... is there some notational purpose (and/or meaning) that you are striving for by incorporating such lines into a score?
Thanks for asking! Yes, I want a simple line symbol to represent a "slide" into a note. In other words, Portamento, but without its big hairy, wavy symbol. And I don't want to use a guitar bend either.
A "short slanted line" that I can attach to a note would be ideal—a line that MuseScore positions relative to the note and that I can adjust both the x and y properties of its start point and end point. (It seems that MuseScore's Line object are relative to the measure; that said, the semi-synced behavior strikes me as quite odd. Slurs on TAB staves show some similar wonkiness when adjusting there start and end points, but that's for another thread.)
scorster
In reply to Hmm... I encounter some… by Jm6stringer
Jm6stringer wrote >> I encounter some anomalous behavior when re-sizing and re-orienting those lines
Hi jm. Thanks for confirming anomalous behaviors!
Jm6stringer wrote >> the behavior of those "synched" lines
I'd classify those Line objects as "semi-synced." Because sometimes they operate independently, sometime not.
Jm6stringer wrote >> ... is there some notational purpose (and/or meaning) that you are striving for by incorporating such lines into a score?
Thanks for asking! Yes, I want a simple line symbol to represent a "slide" into a note. In other words, Portamento, but without its big hairy, wavy symbol. And I don't want to use a guitar bend either.
A "short slanted line" that I can attach to a note would be ideal—a line that MuseScore positions relative to the note and that I can adjust both the x and y properties of its start point and end point. (It seems that MuseScore's Line object are relative to the measure; that said, the semi-synced behavior strikes me as quite odd. Slurs on TAB staves show some similar wonkiness when adjusting there start and end points, but that's for another thread.)
scorster
It's absolutely essential indeed that not all properties be linked. Consider, the line might be only a single system on the part but multiple systems on the score, and need to be moved on just one of those systems to avoid something on the staff above, etc. So, definitely an important feature.
For the record though, you definitely should not be trying to abuse line to create simple markings attached to single notes. That's going to be a disaster wiating to happen as soon as anything wehatsoever about the layout change. Lines by definition have two endpoints, they extend from one point in time to another. All adjustments are relative to the positions of those two points in time. There is no way to position a line in a way that will be independent of things like measure width etc.
As far as I can tell from your example, those symbols are meant to be ordinary slides and should be added with that symbol directly, not faked with text or with lines?
In reply to It's absolutely essential… by Marc Sabatella
Marc Sabatella wrote >> It's absolutely essential indeed that not all properties be linked.
We're in complete agreement on that. No one here asked for "all properties to be linked."
My posted observation simply stated that Line objects don't behave neither as fully synced nor fully unsyced. I'm surprised, because I'd expect one behavior or the other: synced or not. For the record, unsynced makes sense to me. The semi-synced behaviors befuddle me.
So the question is: Why does an adjustment to one Line anchor point sometimes affect the Line object in the Linked staff?
Marc Sabatella wrote >> those symbols are ... ordinary slides and should be added with that symbol directly
Ah ... Thanks Marc! Slide In Below works perfectly! And it's much more easily and reliably adjusted. Don't know how I overlooked that. It's right there in the Glissandi palette : |
In reply to Marc Sabatella wrote >> It's… by scorster
Yes, as mentioned, not all properties are linked. This is precisely the same thing as saying they are not fully synced. Different words to describe the exact same desirable / necessary state of affairs.
So the answer to your question: why does any adjustment sometimes affect the linked line - if the adjustment is to a property is linked, it affects both. If the adjustment is to a property that is not linked, it affects only the line being adjusted. Simple as that. same as for all other elements.
In reply to Yes, as mentioned, not all… by Marc Sabatella
Marc wrote >>
• if the adjustment is to a property is linked, it affects both.
• If the adjustment is to a property that is not linked, it affects only the line being adjusted.
Simple as that.
The question I asked was:
“Why does an adjustment to one Line anchor point sometimes affect the Line object in the Linked staff?”
The operative word in that question is “sometimes.” And you included sometimes when you paraphrased the question.
I don't see how "sometimes" fits into the concept of linked/synced.
Line objects are supposedly unsynced in MuseScore, right?
Simplest “sometimes” semi-synced example:
• Create a new score with a linked staff
• Add a Line object to Measure 2.
• Drag the right edge of the Line object beyond the right barline
• Drag the left edge of the Line object beyond the left barline
Bug or design?
In reply to Marc wrote** >> • if the… by scorster
Precisely for the reason I said - if the property you are adjusting is one that is linked, it affects both. If it is not a property that is linked, it doesn't.
In your example, dragging of an endpoint potentially adjusts two properties: the anchor (the note that end of the line is attached to), and the physical position of the endpoint of the line relative to that anchor. Any adjustment to the anchor is linked. Any adjustment to physical position is not. No "sometimes" about it.
And to be clear, yes, this is by design, exactly as one would normally want. The layout between one linked staff and another can easily differ such that the physical position of a line might need to differ between the staves, even though the line is anchored the same way. For example, on one staff you might be shortening a line slightly to avoid a marking not present on the other staff.