Bend symbol - problems
See attached file:
The problem is that the bend symbols are often too high and there is no way for the user to customise the length. There are problems with the bend symbol and its "Bend properties" dialogue:
(1) It is not absolutely clear what the "x axis is for."
(2) What instruments are the bends for? All stringed instruments?. The guitar doesn't often use bends more than a tone.
(3) Many of the possibilities that can be produced are just a jumble of lines and arrows that are unreadable.
Can you provide some way of adjusting the height and width of the bend? (I have attached some examples of commonly used bends in guitar music).
Attachment | Size |
---|---|
oversized_bend_symbol.mscz | 8.43 KB |
guitar_bends.PNG | 94.07 KB |
Comments
I'm confused as to how the bends in MuseScore differ from those in the picture. The picture shows bends on the third line from the top. If you create such bends in MuseScore, they look the same to my eye. And my understanding is that these bends are supposed to start at the string/fret they apply to and extend above the staff, so indeed, the length will depend on which string they apply to. That's how I've seen it, anyhow, but I don't look at a ton of this type of music, so maybe the examples I've seen are unusual. How do you think it should look, and do you have examples?
Bends are allowed for all instruments, just as bowing markings are and other symbols that may or may not actually be relevant.
As for the jumble of lines, the facility is designed to be flexible and allow for more complex bends than just what is shown in your example. It is of course true with that felxibility comes the possibility of creating nonsense. That's not a bug. But if you have an example of something that does make musical sense and should be rendered a specific way but is not, that's a bug, and you should file it as such, with precise steps to reproduce.
also strange that those bends in a linked staff don#t seem to be linked, i.e. if you change them in tablature, they don't change in staff and vice versa. Any only when changed in staff, they also sound (in the current nightlies, not yet in 2.0.1)
In reply to also strange that those bends by Jojo-Schmitz
Until very shortly before release, bends weren't supported on standard staves at all. I enabled that at popular request, and *thought* the linking was working then. I see the code I added is still. But indeed, it seems to not work in the posted fill. It looks like it works right after the score is created, but somehow, after a save and reload, the links are gone. As are manual adjustments to position. That's a bug...
EDIT: #65831: Links and manual adjustments to bends not saved
Should be simple to fix.
In reply to Until very shortly before by Marc Sabatella
"The picture shows bends on the third line from the top. If you create such bends in MuseScore, they look the same to my eye"
Indeed, this is an important detail. I looked on other published documents. It is really tedious to detail the differences. However some examples:
- On a published guitar score, a bend starting on the last strings (6th, or 5th eg) pass through the Tab staff, but it is dependent of the beam (instead of the note head) in the standard staff.
- With GP, see the result. Ditto, in Tab staff, the bend line cross the Tab staff, but with a different display in the standard staff.
This is an option in GP for display the bends in standard staff. With MuseScore we can hide ("V") very easily, so ...
Maybe the line (very right) of the bend in MuseScore, compared to that of GP (more curved) can accentuate this effect of length? But this is only (?) a cosmetic appearance, right?
However, I see a bug on elsewhere (related to this sentence ? " a jumble of lines and arrows that are unreadable"
By default, in Bend Properties, choosing the Bend, Bend/Release and Bend/Release/Bend works as expected.
But with the Prebend and particulary with Prebend / Release, the word "full" collides badly with the bend lines.
I prefer the less tall bend, regardless of the position on the TAB staff, as shown in Cadiz1's first diagram, on the treble staff (the 1/4 note bend).
@geetar:"(2) What instruments are the bends for? All stringed instruments?. The guitar doesn't often use bends more than a tone."
Bends are not only for stringed instruments. Some synthesizers have a pitch wheel that helps to control the pitch. Also, as wiki says, it is possible to make a bend with trumpet, harmonica and human voice.
Agree with bending up to a tone, but if we are talking about guitar, we have to have a big pitch bend range to be able to emulate Floyd Rose effects. If we're talking about synthesizers, their settings are adjustable, so player can vary the pitch bend range even to very large.
The bend in the attached image is too tall. Could there be a new feature to allow the user to adjust height?
In reply to The bend in the attached by geetar
hello! thanks for all the info in this thread. how do I stop the bend in standard notation looking like this? it's ok if the note is lower...
In reply to hello! thanks for all the… by Mike Smith8
Not exactly sure what you want, but you can move the bend or right click it a select bend properties to make it look like you want.
In reply to Not exactly sure what you… by mike320
The Bend direction is incorrect.
The arrow and the bow should be upwards.
However, the center point seems to have been fixed to the "g" or "a" note (above the staff).
In reply to The Bend direction is… by Ziya Mete Demircan
exactly. I can move it wholesale but it won't change the direction of the bend unless I move the note until it is much lower!
In reply to exactly. I can move it… by Mike Smith8
I think it's because, as the "Bends" page says, the height of the bend is adjusted automatically so that it is as close to the top of the stave as possible. In my case that means that, because the notes I want to bend sit way above the stave the height of the bend is negative! How do I suggest that this is fixed in a later version?
In reply to I think it's because, as the… by Mike Smith8
See #93191: Bend tool: notation and layout problems.
In reply to See [#93191 ]. by geetar
thanks!