Problem using CTRL-DwnArrow and Ctrl-UpArrow to move selected notes down strings sets on the Tablature Staff
Posted to Forum on Feb 22, 2021 - 08:57
Several other users have verified the issue with one stating the issue was observed in Ver 2.
I have uploaded a score that has 4 one-measure examples with text above each example on how to make the error occur and not occur.
1) Installed the latest release of Musescore 220.127.116.118021803 (Windows 10 Pro, 64-bit) .
2) Created a new score with a linked staff using Acoustic Guitar and Tab. 6-str. Simple.
3) First noticed the issue in a larger score, but I have reduced the score to 1 measure to simplify the issue.
4) Entered 4 quarter notes such as F A C E in arpeggio fashion in the top standard (Notation) Staff.
5) Selected the tablature measure and the pressed CTRL+DownArrow several times until at least one note was on the lowest string (Low E). That process takes the selected notes in the tablature staff and moves them to lower string sets, higher up on the fretboard. This usage is described on Page 118 of the latest PDF manual.
6) I then pressed CTRL+UpArrow several times until the notes were back at the original strings and frets. That exercise was successful!
7) I then stacked the F note with an A above it. When I pressed the CTRL+ DownArrow until it could go no lower and then Pressed CTRL+UpArrow numerous times, the stacked F & A moved back where they were, but the other notes didn't move back to where they were originally.
I tried numerous other combinations. The only stacked version that worked successfully was if the last note of the measure was stacked. This has led me to believe it could be an indexing error.
I downloaded two in-work musescore builds, the nightly MuseScoreNightly-202102210427-3.x-2ba915f-x86_64, and the MuseScoreNightly-latest-x86_64. Both of these exhibited the same behavior. I tried other scores that I was using, newly created scores specifically for this purpose, and some older version 2 files. Same behaviors as above were observed.
While a user could use CTRL-V repeatedly to back step, this isn't always successful. This was acknowledged by another user in my forum post. On larger notes selections, the score must be carefully reviewed before pressing the save button.
I have uploaded a score that has 4 one-measure examples with text above each example on how to make the error occur and (not occur).
I took a screen video of this occurring which I tried to upload with this submission, but it did not accept it.