Unable to move tab note to adjacent string with 8va

• Sep 26, 2023 - 20:21

Hi everyone,

I hope you are doing well! I am working on a score for Peter Frampton's Do You Feel Like We Do and there is a section, (measures 307-315), where he is playing octaves on the guitar and I have marked the section as playing an octave higher than written. In the tab staff, Musescore 4.1.1 is placing the lower note on the adjacent string, which would be quite difficult to play and I want to move that note to the next string over. When I click the note on the tab staff and hit Ctrl-down arrow the note sounds, but doesn't move. I have tried copying the contents from the linked staff to an unlinked staff and the issue still occurs. If I delete the 8va marking, then I can move the two notes independent of each other. I tried running it with the nightly build and output to the console, but I didn't find much information:

11:48:00.083 | INFO | 140646002185920 | FluidSynth | addSoundFonts: success load soundfont: /tmp/.mount_MuseScRpbxKJ/share/mscore4portablenightly-4.2/sound/MS Basic.sf3
11:48:13.923 | INFO | main_thread | ActionsDispatcher | dispatch: try call action: pitch-down-octave
11:48:15.780 | INFO | main_thread | ActionsDispatcher | dispatch: try call action: pitch-up-octave
11:48:16.731 | INFO | main_thread | ActionsDispatcher | dispatch: try call action: pitch-down-octave
11:48:17.531 | INFO | main_thread | ActionsDispatcher | dispatch: try call action: pitch-down-octave
11:49:40.163 | INFO | main_thread | ActionsDispatcher | dispatch: try call action: pitch-down-octave
11:49:41.291 | INFO | main_thread | ActionsDispatcher | dispatch: try call action: pitch-down-octave
11:49:46.067 | INFO | main_thread | ActionsDispatcher | dispatch: try call action: pitch-down-octave
11:50:00.491 | INFO | main_thread | ActionsDispatcher | dispatch: try call action: notation-delete
11:50:47.186 | INFO | main_thread | ActionsDispatcher | dispatch: try call action: undo
11:51:02.811 | INFO | main_thread | ActionsDispatcher | dispatch: try call action: pitch-down-octave
11:51:11.042 | INFO | main_thread | ActionsDispatcher | dispatch: try call action: pitch-down-octave
11:51:14.339 | INFO | main_thread | ActionsDispatcher | dispatch: try call action: pitch-down-octave
11:52:07.547 | INFO | main_thread | NotationProject | doSave: success save file: "/home/someone/Downloads/Frampton_Peter_Do_You_Feel_Like_We_Do (1).mscz.autosave"
12:00:43.399 | WARN | main_thread | MuseSamplerResolver | clearSources: Not supported!!

Version info:
OS: Ubuntu 23.04, Arch.: x86_64, MuseScore version (64-bit): 4.1.1-232071203, revision: e4d1ddf

I have attached the score.

Can someone help me with either a workaround, or a way to debug the problem so that I can submit a bug, if there is one?

Thanks,
Shannon


Comments

Nevermind. I came up with a work-around. I unlinked the standard notation and tablature staves, then manually added a third note on the string I wanted, then deleted the octave note on the wrong string.

This does feel like a bug, though. I'm not sure why I couldn't change strings once I added the octave line.

Attachment Size
fixing_1.png 34.25 KB
adding_note.png 26.72 KB

In reply to by shannonpeevey

Here is some more information:

I can't reverse the deletion process, or musescore will readd my note to the wrong string.

Reproduce:
1. Tab notes:
17th fret 1st string
10th fret 2nd string
2. Delete the note: 10th fret 2nd string
3. Enter note input mode and move to the 3rd string
4. Type 2 and musescore adds back the 10th fret 2nd string note,

Do you still have an unanswered question? Please log in first to post your question.