Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues with palm mute placement on 7-string guitars in continuous view (horizontal) #26691

Open
4 tasks done
Iurig opened this issue Feb 23, 2025 · 1 comment
Open
4 tasks done
Assignees

Comments

@Iurig
Copy link

Iurig commented Feb 23, 2025

Issue type

Engraving bug (incorrect score rendering)

Description with steps to reproduce

  1. Add a 7 string guitar with both a Treble clef and a linked Tab. 6-str. Simple staff
  2. Add the 7th string through the staff/part properties right click menu, increasing the number of lines on the tablature from 6 to 7.
  3. Write a 7 string guitar part with palm mutes on the tablature on continuous view (horizontal), and edit at least 2 bars away from where the palm mute is.

Expected behavior: The P.M. symbol stays where it was first put as you're editing other bars

Actual behavior: P.M. symbol moves to overlap with the 7th string, moving back if you're editing in the proximity of it again

Image

I suspect this has to do with the inconsistency of the tab type being 6 strings, but the information of the staff being edited to contain 7 lines. Maybe the line change should change the type of tab instead of trying to work out how a 6 string tab with 7 lines should work? I am not sure.

Supporting files, videos and screenshots

An example of the P.M. symbol moving as I edit the next bar in video is in the zip, as well as the file at the end of the video
Example.zip

What is the latest version of MuseScore Studio where this issue is present?

OS: Windows 11 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.4-243461245, revision: github-musescore-musescore-2232670

Regression

I was unable to check

Operating system

Windows 11

Additional context

No response

Checklist

  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible
@Iurig
Copy link
Author

Iurig commented Feb 23, 2025

Upon further inspection, I noticed it also happens with the Tab 7-str. Simple staff, not only the 6-str. staff. I'm also reopening the issue as I closed it on accident.

@Iurig Iurig reopened this Feb 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants