Community Blog

Hello,
This week I began the coding for the implementation of range annotation as a spanner. However, I caught a viral fever earlier this week, which stalled the work for a few days. I am feeling better now, and can resume working on the same.
I created a new branch for the implementation. This can be found here :
https://github.com/shredpub/MuseScore/tree/RangeAnnotation2

I looked into the flow of spanner creation, spanner segment creation, and layout in more detail and still have a

Hi,
a new small update for this week. This week was a lot about fixing small bugs and testing things on different platforms!

Because of my work on MidiSpanners I found some more bugs with midiAction. It didn't use the right channel. Instead of using the the actual channel number to emit it's Midi Messages it emitted them on the channel relative to the current Instrument. (Meaning a instrument can have multiple channels and midi Actions was using this channel

Hello,
Last week I tried to understand the implementation of spanners more clearly. I specifically concentrated on hairpin.cpp and hairpin.h at first, by playing around with the hairpin, and seeing how the data structures are reflected.
I also spent time on seeing how the parent classes are implemented (TextLineSegment and SLine, in that order of hierarchy)
I also looked at slur.cpp and slur.h, which inherit from the base class SlurTie . I looked at the implementation of spanners wrt slur.

This was my eighth week working on note entry with MuseScore for Google Summer of Code. I made rapid progress implementing a working proof of concept early in the project. For the past couple of weeks I have been going back over my previous work, improving the structure and performance of the code, and giving users more control over note entry via additional options and preferences.

This week’s summary:

• Improvements to Automatic Real-time note entry mode:
  • Improved performance
  • Auto-advance triggered

The actual PR for the improved Implode tool and the actual PR for the new excerptsdialog.

Last week

I worked a bit on some new tests, and switched some test cases, so the tests are better sorted. This also affects the new directory of PR 2738.
The test for the improved Implode is finished, it does just show, that the Implode tool doesn't matter on most things as slurs, hairpins or something else. It also contains a empty destination

Hello everyone,
this time a small update - but I think some big changes are going to happen till the end of GSoC!

First of all some update on things from last time - the #include and <global> opcodes made it into the master branch. I changed some things about how the preprocessing works and while I was at this I also fixed some things about comments. Currently comments that didn't start with a line we're not recognized as comments

Hello,
This week I was working on implementing read and write for the current implementation of Range Annotation.
The code for the same can be found in this branch : https://github.com/shredpub/MuseScore/blob/RangeAnnotationtmp
It is writing successfully, but it cannot find the measure during read. Anyhow, it makes more sense to take care of it after we port the implementation to be spanner based, since we would want to be able to select the range annotation and set various properties. The range

This was my seventh week working on note entry with MuseScore for Google Summer of Code. Last week submitted a pull request containing the first part of my code to prepare the user interface for the new note entry modes. This week I prepared a second pull request to implement the new modes.

This week’s summary:

• Basic implementation of each new note entry mode
• Further improvements to the UI

Still to do:

• Improve performance of auto mode
• More sophisticated algorithm

The actual PR for the improved Implode tool.

Last week

I was mainly working on bug fixes. Biggest one was the tie thing, where ties weren't connected to next note if there was a measure break between them. This was fixed by a big change to the cloneVoice() method. This method does now get the exact start segment (source), destination segment and the tick of the last segment, so the whole clone process is done in the cloneVoice method. This

Hi,
this week I started working on MidiSpanners. That is the functionality I described last week. With this you can let any spanner send midi information. All main modes (switch, continuous, note on event) have been realized. But currently there is no GUI. I also tested this with hairpins, pedal and slurs. Lasconic also proposed we could have a configuration file (most likely in xml) for sounds that would set good defaults for these spanners and would also add MidiActions