dmitrio95's blog

Hello!

The third week I continued working on the changes on MSCX fileformat. In the previous week I worked on a mechanism which would help to store spanners, beams and tuplets (in general, any "connecting" elements) without using IDs, then I made spanners use this mechanism while reading/writing thus eliminating the need for spanner IDs. However I used ticks for identifying positions of elements in its initial version so, as pointed by my mentor (shoogle), it needed a rework to

Hello!

This week I worked on changing MSCX fileformat, so to describe my work this weekly report will probably contain a bit more technical details. The main idea of the planned changes, as is mentioned also in the discussion on the forum, is to make all parts of the score which is written to the file be less dependent on each other and on the global state of the score. Probably the most common case of such dependence is a

Hi everyone!

This week I had a bit less time to work than I expected — I had to finish my master work, and it took a bit longer than I supposed before. Anyway I finished it and could finally start my work on this score comparison project.

The first week was reserved in my plans for the preparatory work which would allow me to focus fully or almost fully on the work on the first part of my project:

Hello!

I am Dmitri Ovodok, a master student in Saint Petersburg State University, and I am pleased to participate in this year's Google Summer of Code with MuseScore.

While working on a score one may often need to compare different version of the mastered score and identify those parts that were changed in it. One may also want to have a more convenient way to compare different scores, e.g. different arrangements of the same composition.

My GSoC project will be