Hello! I’m Kumar Kartikay, an undergrad computer science student from NIT Hamirpur, India. I have been selected this year in Google Summer of Code to work with MuseScore. I’m going to be working on a project involving refactoring of code in libmscore, which is the part of the code that handles most of the MuseScore internals, like the Score and the notes in it.

Here is a diagram of the current code structure in libmscore (click to open full sized

Greetings MuseScore blog readers!

I am Sergios - Anestis Kefalidis, an undergraduate Computer Science student from Greece. As you might have guessed from the title, for the next few months, I will be working on bringing back Albums. Many of you have been waiting a long time for this feature so I am quite eager to hear your thoughts and suggestions :^)

What is that 'Albums' feature? (Synopsis)

'Albums' is a feature that allows you to combine compositions into a

Over the past 3 months, I have worked to improve how instrument changes are implemented in MuseScore, to make them more user friendly, and more powerful. I have completed a lot of work in this time, and made many improvements. This would not have been possible without the help of my mentor, James Thistlewood, and the other developers of MuseScore, who have been incredibly helpful with their knowledge of the project in keeping me pointed in the right direction.

Evaluation

These past few weeks I have been busy with the Edinburgh Fringe Festival, but I have still managed to get a lot of work done. After finishing off with instrument change warnings, I started work on allowing changing to unpitched percussion staves. My initial thought was to add a staff type change object to the instrument change when necessary, but this provided a lot of complications when copying and pasting, as the user would be able to change the properties

More Information:

• Weekly Blog Reports

• Github Pull Request

  Project Overview:

My project for GSoC 2019 is Palette Accessibility and this post gives a brief description of all the work that I have done during this time period. The new Palette is designed using a QTreeWidget and it can provide the Musescore users to quickly access the elements by utilizing the ability of the hierarchical view. My idea was to implement keyboard navigation functionality to the palette. Before, we get into

Hi! This post is a summary of the work that was done for my GSoC 2019 project: Chord Symbol Playback.

Project description

This project aims to improve the experience of working with chord symbols in scores. Without being able to hear the harmony denoted by the chord symbols, it can be difficult to get a full idea of what a work of music might sound like in practice.

In my original proposal I hoped to, at minimum, solve a

Hi! This post is a summary of my Google Summer of Code project, and it also serves as an introductory material linked in The GSoC project page.

The project is devoted to improving the plugin facility of MuseScore, and more specifically, automating the process of downloading and installing MuseScore plugins. The above project page already gives a good explanation for its purpose.

Demo

This is a video demo demonstrating all major features the project covers.

I began by opening

Work Planned To Do:

Complete creating a right-Click Menu Option and also make the back-end logic for each of the options for the context Menu

Work Done:

I have added the right-Click menu option for the palette item and also for the elements within each palette. I have made this by reimplementing the conextMenuEvent() of the palette to the PaletteList which provides the option to customize the paletteCellItem or the elements and also reimplementing the contextMenuEvent() of the paletteBoxButton to

This week I still managed to add more comments and do more code cleaning. I must admit these were not done completely in previous days, partially because some functions are being added and renamed.

I did some fixes, too. One small but interesting one among them is, the space between the following QLabel and QTextEdit, was not constant when we switched between plugin items and package items. I fixed this by setting a minimum width value to the QLabel on

We're almost done!

So far

This week was a lot of cleanup and making sure everything is good and cleaning up the final bits. That means writing a lot of tests to make sure everything will be good going forward and for new developers to work with. On the user side of this week, it was fairly uneventful, although there is some stuff to hopefully look forward to coming soon :)

Coming up

Sometime in the next week, I will