85sid's blog

This page is a summary of all the work done as a part of GSoC 2021 for the Smart Tempo project.
Find more information about the project at:

Weekly blog posts
Project Proposal

Code Changes

All of the code that is part of the project exists in two Pull Requests - #8308, #8524

#8308

• Allowed opening a popup under specific elements when editing is triggered
• Created a general popup, which can be filled dynamically based on the selected element

Hi everyone! I spent the last week working on various improvements and bug fixes to the tempo popup. The most important of which are:
1. Positioning: The tempo popup appears to the side of the element, if it is too close to the bottom edge of the screen
2. Tab View Styling: The active tab is now highlighted.
3. Bug Fix: Prevent users from deleting part of the tempo equation through keyboard input
4. Bug Fix: Visibility toggle now works

Hey everyone!

My work on the tempo popup and the tempo element is finally complete. All major bugs have been fixed and the modifiedTempoText element can now be imported and exported across all formats.

Here is my PR for the Tempo Popup: https://github.com/musescore/MuseScore/pull/8524

Over the next week, I will be diverting my attentions to the second part of my project - Rubato and dynamic tempo markings.

Hey Everyone!

I am almost done with the Tempo Popup. Over the last week, I've fixed all of the bugs related to the popup and the element, and cleaned up the legacy code. This included:

• The new element is fully integrated with the palette
• The popup opens for newly elements created without a restart
• All import/export formats except musicxml now use the modified TempoText Element
• The element now renders equations using symbols and not unicode characters

Over the course of

Hey everyone!

I have completed all the functionality that goes into both the tempo popup and the tempo element over the past week. Users can input tempo using all 3 tabs. The marking does not allow the user to edit the equation. And bugs related to user input have been fixed.

This week, I plan of fixing a couple of minor bugs in the popup and integrating the modified tempo element with the import and export code. I hope to

Over the course of the past week, I've come close to completing the Tempo Popup, except for a few minor fixes

Users can now use the popup to enter equations with all three tabs - Tempo, Equation and Code. The Code tab currently only supports simple markings that can be notated using the other tabs because of limitations in the symbol set, but is designed to make it easy for future expansion

The tempo marking has also been modified to

Hey everyone!

This past week, I was focused on creating the UI for the Tempo Notation Popup. I've also gotten started on creating the functionality required for the user to edit the tempo element from the popup. The plan for this popup is to be able to return metrico style notation strings, which are parsed and converted into symbols by the tempo element and rendered as usual. This system will be designed to aid future expansion of the symbol set

A major part of the functionality of my project is contained within a popup under the tempo element which appears when the tempo element is being edited. I spent my first week coming up with a system that allows customizable popups to be positioned under any editable notation element. This popup will tie in with the existing Inspector Settings Models and work in tandem with the inspector popups.

This is how the popup looks in action.

[inline:popup.jpg]

Over the course

Hello! I’m Sidharth and I will be working with MuseScore during this summer as part of this year’s Google Summer of Code. My project, ‘Smart Tempo in MuseScore’ aims to primarily improve the existing tempo notation system, with a secondary focus on improving tempo playback.

Smart Tempos

In MuseScore 3, the tempo notations are treated at their core as text elements and are editable in their entirety. This makes it incredibly hard to input metronome markings, or change the note