musescore / musescore/MuseScore

Timeline can't move the score to landmarks when the top stave is hidden

Open
#21,346 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

P2 UX/interaction
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

UX/Interaction bug (incorrect behaviour)

Bug description

When the top stave is hidden, clicking on a landmark such as a tempo marking or rehearsal mark in the timeline won't move the score to that position. It does still work for landmarks where the top stave is not hidden.

Steps to reproduce
  1. Create a new score, using, say the SATB template, and giving enough bars - I used 128
  2. Sprinkle tempo markings liberally through the score
  3. Add notes to all staves to force the score onto several pages
  4. Open the timeline and click on any of the tempo markings - the score moves to the marking, and so does the playback cursor
  5. Delete the notes on the top stave for most of the score
  6. Use the timeline to see that jumping to tempo markings still works
  7. Format > Style > Score > Hide empty staves within systems
  8. Jumping to tempo markings on staves that are shown still works, but the score won't move to any that are above a hidden top stave

A resulting score is 2024-02-03 MuseScore timeline jump bug.mscz.zip

Screenshots/Screen recordings

No response

MuseScore Version

MuseScore version (64-bit): 4.2.1-240230937, revision: github-musescore-musescore-d757433

Regression

I don't know

Operating system

OS: Windows 10 Version 2009 or later, Arch.: x86_64

Additional context

This is surely related to #21302, though a different symptom.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue in MuseScore 4.2.1 with the attached SATB score, using the timeline's tempo and rehearsal landmarks after hiding empty staves within systems. Trace the timeline jump and score navigation behavior for landmarks above a hidden top stave; done means every landmark click moves both the score and playback cursor to the correct position.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.