This is my weekly update on my Google Summer of Code project. There will be three parts of this blog post: what I did, what had issues, and what is next. Then, I will end it with a question that I would like answered for part of the project.
Hello!
As there are only two weeks left for this GSoC I think it would be better to discuss some plans for the rest of that time in this post. Still I'll begin with those changes that were done during this week.
I. Improvements in a comparison readability
1. A consistent way of adding a human-readable representation of various properties was added to MuseScore code. Note pitches and barlines types are not shown as just numbers anymore but
Hello!
I have worked on the previous week issues and now the application has stopped from crashing. It's sorted but I will have to test it and understand more on the root cause of the issue as the implementation was working for most of the scores. I am not considering this project as a part of GSoC but as my willful contribution to the community. Coming to this week's analysis,
Below is the segmented status of the project:
Current status
Read moreThis is my weekly update on my Google Summer of Code project. There will be three parts of this blog post: what I did, what had issues, and what is next. Then, I will end it with a question that I need answered for part of the project.
Hello!
During this week the score comparison tool got a small redesign and an ability to show score chunks that are relevant to the displayed changes. The current look of the tool is shown below (or here in better resolution).
[inline:Screenshot_20180723_033120.png]
User can choose for comparison any scores that are opened in tabs at the moment. The choice can be done either using drop-down lists inside the tool area itself or just by opening the needed scores in two tabs
Hey!
These couple of weeks are going to be a notch up in performance as many things are supposed to be taken into account. I have been testing the implementation for a couple of weeks now and getting more and more updates in the implementation as I proceed forward. I have done further testing, bringing us to the last 472 scores, completing our entire set of 988 scores. There are two issues which are needed to be resolved and some
This is my weekly update on my Google Summer of Code project. There will be three parts of this blog post: what I did, what had issues, and what is next. Then, I will end it with a question that I need answered for part of the project.
Take a look at an example of the tours on YouTube.
Added overlay
Hello!
This week after fixing some issues of the developed score comparison engine (mostly concerning spanners handling) I have started a work on a graphical interface for the score comparison tool. Currently its look is far from perfect but to some extent it works. Below is the screenshot of MuseScore with the new tool launched, as it looks at the moment (full resolution):
[inline:Screenshot_20180716_023050.png]
During the next week I will improve the interface of the tool — hopefully
Read moreHello!
This week I have thoroughly tested 350 more scores, so now we are done with almost done with 520 scores from a bunch of 988 scores. There are some issues that I found which crashed the application so the XML generated were not complete and eventually, the OMR gave parsing error. There was no other issue than this which I found. Some new shapes again that are not annotated. I will be compiling them, posting them on the issue
This is my weekly update on my Google Summer of Code project. There will be three parts of this blog post: what I did, what had issues, and what is next. Then, I will end it with a question that I need answered for part of the project.
Expanded the tour framework
