Tablature note string change request has no effect
Steps to reproduce the issue:
1) Create a tablature staff for a stringed instrument with N frets.
2) Add a note at fret N, on a string which is not the highest in pitch.
3) Select the note, and press CTRL+UP. The note moves to the higher string, as expected.
4) Select the note moved in step 3, and press CTRL+DOWN. The note does not move to the lower string. This is unexpected.
I've attached an image of a note at fret 19 on the high 'E' string of a 24-fret electric guitar. The note should also be playable at fret 24 of the 'B' string, but the note cannot be moved using CTRL+DOWN.
I am using a recent build of 4.x from the github project's master branch.
OS: Debian GNU/Linux 11 (bullseye), Arch.: x86_64, MuseScore version (64-bit): 4.0.0-, revision: github-musescore-musescore-
Attachment | Size |
---|---|
Screenshot 2023-01-05 17.10.01.png | 66.01 KB |
Comments
Thanks for the report, this is a known issue affecting note input mode only (works fine in normal mode). See https://github.com/musescore/MuseScore/issues/15588
No problem. I had a look at issue 15588. The report I provided describes a different issue, and affects both musescore versions 3 and 4.
I can confirm that there seems that there is an "off by one" error here - whatever the max fret number is, you can only move a note down to that string if it's playable with one fewer fret. Please report this on GitHub, and attach the actual score (ZIP it first) to makje it easier for the develoeprs to reproduce the problem. Here is a link - https://github.com/musescore/MuseScore/issues/new?assignees=&labels=&te…
Woah, nice job submitting the issue and a PR!
My pleasure. Just waiting for the github tests to pass. (ctest passed locally.)
https://github.com/musescore/MuseScore/issues/15729
And https://github.com/musescore/MuseScore/pull/15730
You were saying that this issue exists in 3.x too?
Yes, same line of code in 3.x, not sure since when though: https://github.com/musescore/MuseScore/blob/2513676e512d29d554cb6c4d37d…
Yes, it's 3.6 I saw it in too.
Ok, so I'll cherry pick your PR into my 3.7 PR #9000 😉
Sounds good. I hadn't noticed the 3.x branch, or the mighty PR #9000 :-)
Done