Score Overview
Coming from a DAW background, I really miss not being able to see a complete overview of the score. This plugin is my attempt at remedying that by showing parts, measures and rehearsal marks. If measures contain notes, they are black, otherwise grey (see the attached screenshot below).
In addition, I added the ability to click on a part / measure to send the cursor to the first element of the selected measure. You can also click and drag to select a range of measures / parts. Shift click to select one measure in a part.
The plugin does not change the score in any way, but provides an alternate view of the score and a different method of access.
Moving to a selected part/measure is not immediate as it uses the cmd() routines to position the cursor, but it is still quicker than searching by eye.
The plugin can be found as a musescore project here: https://musescore.org/en/project/scoreoverview
And downloaded from github here: https://github.com/stevel05/scoreOverView
I have tested it as much as possible, and got rid of all the bugs I have found. That is not to say there won't be a few more. Any feedback gratefully received.
This is my first published plugin I hope you will find it useful.
| Attachment | Size |
|---|---|
| screenshot.png | 10.13 KB |
Comments
Sounds cool! I would really want to have this as a native feature in MuseScore. I proposed it for Google Summer of code this year, see https://musescore.org/en/developers-handbook/google-summer-code/ideas-2… but nobody picked it up. If you would be interested in implementing it in the core, I'd be happy to guide you! You can find me on #musescore on freenode.net for a chat or on this forum.
In reply to Sounds cool! I would really by [DELETED] 5
That's pretty close. I hadn't seen that proposal list, there are some interesting suggestions on there.
I have been thinking of trying to compile the musescore source, just to see if I could. I haven't done anything C++ and only C 30+ years ago, so I would probably need a lot of guiding, but yes, why not.
I couldn't promise a quick turnaround, but it would be interesting to see what's involved.
What's the best way to start the ball rolling?
In reply to That's pretty close. I hadn't by stevel05
First get the Setup and all the needed bist and pieces in place to compile MuseScore. For that check https://musescore.org/en/developers-handbook
In reply to First get the Setup and all by Jojo-Schmitz
Thanks, yes I managed to get that setup and running last night, much to my surprise it worked first time. The instruction are nice and clear.
In reply to Thanks, yes I managed to get by stevel05
Next, find your way though the code. You probably want to check the Measure/MeasureBase class and understand how they are chained. Also, you might want to check how to access the content of a measure on different staff, but you probably figured this out from the plugin framework already.
Another approach, check http://doc.qt.io/qt-5/qgraphicsview.html and friends, to draw the UI
In reply to Next, find your way though by [DELETED] 5
OK, thanks.
Are there any design guidelines I should be working to? Specifically for the Gui, and coding style / structure. I can match the look and feel of the existing elements, but anything else?
I generally like to build a model of the data that is going to be output, rather than get it piecemeal from it's sources at display generation. Is this an acceptable approach?
In reply to OK, thanks. Are there any by stevel05
I finally got some time to look at incorporating the overview and after a few hours of studying code and copy/pasting, I have managed to get a duplicate of the Navigator up and running. It seemed like a good place to start.
So now I can look at collecting the data and drawing the gui. This may take a while. I now have a head ache :)
In reply to I finally got some time to by stevel05
Just reading this now... I guess the head ache is gone :)
That's awesome! Let me know if I can help further!
Updated see : https://musescore.org/en/project/scoreoverview.
Should now not crash Ubuntu and OSX.