MuseScore Development Blog
Welcome to MuseScore development news and digest blog.
More than 1000 new users tried 3.0 alpha! Welcome aboard, brave people. :)
We changed the MuseScore file format a month ago to facilitate the introduction of a new tool: a scores comparator which shows the diff between two scores. From now on, you cannot open files created in early 3.0 development versions, so to use your files, open them in 3.0 alpha build and select "Save As... new file".
Right now, My_First_Score.mscz needs to be resaved as well...
We updated the authorization engine on the website which may affect different user scenarios related to personal settings.
Should you find something is broken, please let us know.
MuseScore 3.0 alpha announced!
Highlight of the day:
- Werner is implementing optimized algorithm for collision detection. You can check out the actual (pretty good) state on Windows 64-bit, Mac and Linux 64-bit.
We again exceeded maximum allowed artifact storage size on AppVeyor. Sent the request to AppVeyor's support.
UPD: AppVeyor increased the limit for us.
Created new 3.0alpha branch based on the current master.
If you already did a checkout of the previous 3.0alpha branch, please force a new checkout with the recent changes.
Reviewed all existing pull requests.
Closed outdated and already fixed ones.
Added new label "Priority" to define PRs which are aligned with the current most requested features.
We made good progress and will keep working on the following issues organized in epics which are mostly about positioning elements and text:
- Positioning of the text in the layout
- Issues related to tempo elements including playback issues
- Displaying elements of the scores created in 1.X versions of MuseScore
- Displaying and positioning elements of the scores created in 2.X versions of MuseScore
We mostly finished solving issues related to continuous view and text editing:
3.0alpha branch has been created.
We are preparing a MuseScore 3.0 public alpha release. Links to the packages are going to be put on the download page. This release is supposed to show the current state and the significant progress in 3.0 development as well as attract more users to test the editor.
All pull requests must be created against master as usual.