Hi :D
Week 8 is done and it was full of closely looking at the results generated using the XMLs generated. We have planned that we will chunk 988 scores into chunks of 150 to 200 scores and closely examine each segment so that by the time we are on the last segment, we will have everything sorted. I have shared some list of shapes on the issue tracker which are missing in OMR. I will keep refining our code
Hi :D
Week 7 is over and we are into making things better and better, day by day. As discussed with Lasconic, I'm into testing now and discussing with Herve about the results that are generated for our test set of 988 scores. I have shared the test results with Herve, his review is crucial to better understand the requirements. Coming to this weeks analysis:
Below is the segmented status of the project:
Current status of the project
We are
Bonjour! :D
Week 6th is done and we are cool with the project. There were a list of things which were to be done this week and the good news is - we have it done now. Did get some positive reviews for the work by Lasconic and Herve, so yes, we are good. 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
Heya! :D
Week 5th is over by now and we are at a good pace with the project. Currently, I think our Implementation part is almost done but we need to heavily test the outputs so that we can be surer for each and everything and make minor changes if required. I and Lasconic are constantly in touch with Herve to understand what is required, how it is to be presented in the XML and other pieces of information from
Hola! :D
It's hard to believe that it had been a month working on this project. Feels like I started it a week ago only :)
The project is quite engaging and learning is high.
Bringing to everyone 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 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
Hello! :D
It is the third week of coding and things seem to be under control. Had a discussion with lasconic about a problem which was occurring while testing the scores. The application kept on crashing with a weird kind of behavior. After a closer look, we finally have it sorted. The application is working fine on a set of 988 scores. Moreover, from the 988 scores, I have some 70 to 80 scores on which I need to test
Hey! :D
It had been two weeks now working on OMR Dataset project. It's a cool project I would say at the same time, the idea of exploring the codebase on your own, helps in understanding the nuances of implementation. 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 from imeta to master.
2. Grace Notes Implementation for OMR tackling the issue:
Hey! :D
I have started working on the project. During the Proposal time, I worked on porting the changes from the imeta to the master branch of MuseScore. After that, during the Community Bonding period, I had discussions with Lasconic and Herve about the various issues that are there currently with the annotations and how do we want them in the XML. One by one, for a couple of issues, I got deeper into the codebase to understand the working
Greetings,
I am Animesh Tewari, a Computer Science undergraduate at Jaypee Institute of Information Technology, Noida.
About to begin this awesome journey of GSoC with MuseScore.
Project Goal:
The basic idea would be to support the current scenario of Audiveris OMR integration with MuseScore by accumulating a large correct dataset. The OMR needs to be successfully trained on a large dataset so that it can provide precise outputs which will help the Music community. To carry out this task, a