Heyy!
I worked on refining the code as well as resolving issues that came in the way. I'm currently on diving deep into the matter as I can find few issues for 3 scores. Busy with finding the root cause for it. Also focusing on getting OMR updates for imeta working on 2.3.2. Coming to this weeks analysis:
Below is the segmented status of the project:
Current status of the project
We are done with:
1. Porting the OMR work
This is my last weekly update on my Google Summer of Code project. There will be four parts of this blog post: what I did, what had issues, what I will do next, and what is next for a continuation of this project. Then, I will end it with a question that I would like answered for part of the project.
Hello!
In my last blog post I wrote about things that need to be finished to consider the score comparison tool in its basic version be complete. In general, those points I mentioned in that post were accomplished during this week. So the key changes are:
1. Read-only mode for scores
This was implemented for the purpose of being used for the versions comparison feature. The implemented read-only mode is far from being perfect and certainly lacks any user-visible signal
Heya!
Worked on testing the entire set once again. Finalised on some issues which I faced during testing. For the future, I will be working on those issues. Hope we take this project to new heights. Coming to this week's analysis,
Below is the segmented status of the project:
Current status of the project
We are done with:
1. Porting the OMR work from imeta to master.
2. Grace Notes Implementation for OMR tackling the issue: https://github.com/Audiveris/omr-dataset-tools/issues/27
3. Bracket Implementation
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
