Engraving Bugs related to the Staff Type Change - Step Offset

Issue type

Engraving bug (incorrect score rendering)

Description with steps to reproduce

I was playing around with the Step Offset option and found some issues.

Easiest to replicate in a new score. If you write for percussion, you will have to use this option a lot in order to change between pitched and unpitched instruments. Here are the steps to reproduce.

1. Create a new score with any instrument. Usually you would use a pitched percussion instrument. You can Also do this in an existing score, but just for ease of replication, I recommend a new score.
2. Go to the "Layout" Pallet, and add "Insert Staff Type Change" in any bar that isn't the first bar.
3. Go to the "Text" Pallet, and drag the "Change Instrument" text into the bar with the Insert Staff type Change. Change the instrument to any unpitched percussion instrument. If done correctly, it will automatically change the clef to drum clef.
4. Click on the Staff Type Change Box in the score and go to properties.
5. Navigate to "Staff type changes" underneath "General", and find "Step Offset". change this to whatever you like.
6. Add tenuto or staccato articulations.

There are two issues:

• The position of staccato and tenuto articulations is wrongly calculated and does not follow the notes correctly.
• The stem lengths and beam positions are wrongly calculated.

Supporting files, videos and screenshots

In which versions of MuseScore Studio is this issue present?

4.6.0.

Regression

No

Operating system

Windows 11

Additional context

For anyone experiencing this issue, the easiest workaround for a percussion instrument is to instead use the Percussion tab and use the "Customize Kit". feature to change the staff line the note traditionally rests on in your score.

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