musescore / musescore/MuseScore

too much information on the timeline

Open
#34,255 4 comments 0 reactions 1 assignee View on GitHub

@jessjwilliamson is already working on this.

Since Jul 21, 2026.

needs design needs review
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Your idea

The "timeline" on MS shows :

  • tempo,
  • time signature,
  • key signature,
  • barlines (wtf ?? if there's double barlines on the score why not simply put them on the grid instead of taking vertical space for that ??)

these informations :

  • take a lot of space on the screen
  • are irrelevant (at least to me) to navigate throughout long multipart scores.

2 options :

  • either give us the choice to personalize what is shown in the timeline
  • remove these altogether (my favourite option, tho the choice is yours)
Image
Problems it would solve
  • more space on the screen
  • less confusing to look at
  • less need to scroll up and down to see different parts on the score (since there's more space on screen)
  • attract more Guitar pro users to MS and smooth their transition to MS (the main thing that made me reluctant to come to MS at first was the absence of a usable timeline)
  • prevent users from developing carpal tunnel syndrome by scrolling up and down to find a specific part/track.
Prior art

guitar pro 8 (a "timeline-based score editor") has a "timeline" too (called "global view") which :

  • shows only necessary information to navigate throughout pieces (tracks name, the bar numbers and the rehersal marks)
  • has different personalisable colours for different instruments
  • has contrast (it's not just undistinguishable shades of grey)

it also integrates (not saying it's what MS should do, but just pointing that out) :

  • volume and panning controls (so you don't need to open the mixer to change the volume of a track)
  • mute and solo,
  • show and hide track on score (same little eye as in MS4 in the layout pannel),
  • EQ and activation of programmed automations (which i don't necesseraly think should be added to MS)
Image
Edit

clarifications, typos

Checklist
  • This request follows the guidelines for reporting issues
  • I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.