MuseScore 2.0 release schedule
With all the blocking issues being addressed and the plethora of other bugs fixed since beta 2, we have now set a release date for MuseScore 2.0!
* March 12th 13th: 2.0 Release Candidate (RC) for Windows and Mac
* March 24th: Final MuseScore 2.0 release for all platforms
So what will happen between now and the release date:
* Translating the MuseScore interface
* Reviewing and improving the 2.0 handbook
* Create a press release and prepare for media buzz
* Also, you will be able to upload 2.0 files on your account at
* We continue to fix more bugs until the RC
* After the RC, only critical issues will be fixed. Other code contributions will not be accepted during this period.
If you have any questions about the release schedule, feel free to answer to this post or to ping me on IRC #musescore on freenode.net.
Comments
Wonderful news; it's great to have a finish line in sight!
In reply to Wonderful news; it's great to by Marc Sabatella
Great! Congratulations!
Good news!
Does Release Candidate mean that I can post new 2.0 sheets to http://musescore.com, and they will be online?
In reply to Good news! Does Release by MaximAL
As stated in the original post: with the release candidate, "you will be able to upload 2.0 files on your account at musescore.com"
In reply to As stated in the original by Thomas
Sorry, I missed that.
Great!
In reply to Sorry, I missed that. Great! by MaximAL
Oh what a great new ;)
Why not put the new also in the news at home page ...? ;)
In reply to Oh what a great new ;) Why by Zynette
I agree—isn't this News?
Joy! How long until MuseScore 2.1? ;-)
In reply to Joy! How long until MuseScore by Isaac Weiss
Hurrah!!!!
Great news, hope there will be the linux version published also at the release date??
Joe.
In reply to Hurrah!!!! Great news, hope by JoeAlders
Hey Joe, currently we have lined up Linux Mint, Ubuntu, Debian, OpenSUSE, PCLinuxOS, OpenBSD. If your distribution is missing, please leave a comment and if you know who is your distribution maintainer that would be great. This way I can get in touch.
In reply to Hey Joe, currently we have by Thomas
Thomas,
I started a thread on the (English)PCLinuxOS user forum copying your request.
Will keep you informed! Will do this also on the Linux Mint forum.
Joe.
In reply to How will the compatibility be by Svish
1.x files can be loaded into 2.0, and for the most part should look the same or better (due to numerous improvements to the layout algorithms). Some scores with heavy use of manual adjustments or other devices might require some tweaking to look the same. Feel free to install a beta or nightly build to see for yourself. But 2.0 scores *not* load into 1.3.
No idea if 1.3 will ask about update. I see there is an option in preferences to specify how often it checks, so in theory, it's possible.
In reply to 1.x files can be loaded into by Marc Sabatella
And I assume that if I open a 1.x score in 2.x and then save it, it will be saved as a 2.x score? Or will there be an option to save it as 1.x?
In reply to And I assume that if I open a by Svish
There will be no option to save in 1.3 format in 2.0. But if you open a 1.3 score in 2.0, it will ask you where you want to save, so you don't override the 1.3 file if you don't want to.
Is there any way to install 2.0 on Ubuntu 14.10 x64?
I already tried, but it ain’t havin’ it.
In reply to Is there any way to install by MaximAL
2.0 is not yet released...
In reply to 2.0 is not yet released... by Jojo-Schmitz
I mean beta, of course.
In reply to I mean beta, of course. by MaximAL
@MaximAL see http://musescore.org/en/node/33181#comment-224611
This is awesome news! I've been using 2.0 for a while, and is by far my preferred notation program (having ditched Finale Printmusic for 2.0). Hope all goes well :D
-----
*On a side note, I look forward to having .deb instead of compiling ;)
Will I be able to open MuseScore 2.0 scores on the Android Songbook app?
In reply to Will I be able to open by CombatCube
@CombatCube Yes you will be able to do so before the final release.
Is there any chance that it will be a regular Ubuntu release instead of a PPA? I don't really know how this works, but I wonder if there is any chance of getting it promptly for all currently supported Ubuntu versions. I thought I had version 1.3, but I just noticed that I actually have 1.2! I'm running 32-bit 12.04 LTS (Precise), and that's all I can get, even with a PPA. Will I need to upgrade the OS?
This is great! I also have a question. Have you added anything more for the guitar tabulature (i.e. hammer-ons, slides, etc.)?
Very nice!!! I really like the beta 2.0, so I know the RC and final release will be amazing. This software really blows Finale and Sibelius out of the water, (especially since it's open source). I have created beautiful looking scores with such ease using 1.3 and the 2.0 beta releases.
Ever grateful,
Anthony Tabacco
This Is Awsome :) Thank You Guys .. Good Job
>After the RC, only critical issues will be fixed
Does that mean I should hold off on reporting non-critical issues until after 2.0 has been released?
In reply to >After the RC, only critical by zian
Hi
You can report, but they may not be fixed until after 2.0.
In reply to >After the RC, only critical by zian
@zian No, you should absolutely keep on posting critical issues. Critical issues are those who lead to crashes or loss of data. But also other issues are welcome. So don't let the 2.0 release schedule stop you from reporting issues.
Wauw! I've been looking out for this a long time, and now suddenly it's almost there! Well done everyone!
Awesome !!! I'm looking foward to the Linux RC... :P Musescore is one of the best Open Source Software we have for musicians. Congrats guys !
Hey guys, it's already 12th and I cant see the releade candidate :(
In reply to Hey guys, it's already 12th by lupe.mandujano
@lupe the release is in the make. It may take a little longer than previewed as we bumped into a last minute hiccup. We'll reply on this forum post as soon as the RC is out.
In reply to @lupe the release is in the by Thomas
Thank you!
I've been testing the Beta and it's awesome, but when I tried to upload my scores the page warned me that only it's possible with the release candidate.
the marching percussion makes piano sounds and it wont let me upload some of my music its saying that i have some measures to fix
In reply to the marching percussion makes by jonathan aakene
Have you installed the marching percussion extension soundfont?
Marching percussion will not work properly otherwise.
You also may need to check the drumkit option in the mixer for the percussion parts.
Regarding the measures needing fixing, MuseScore 2 is much more finicky about complete bars than 1.x used to be. If you have measures with rests deleted in Voice 2 this will trigger this error.
The simplest solution is to load the score in 1.3 select each stave in turn and perform the "Exchange Voices 1 & 2" procedure twice.
This ensures all measures with a second voice are complete.
HTH
In reply to Have you installed the by ChurchOrganist
how do i install the marching percussion extension soundfont
In reply to how do i install the marching by jonathan aakene
From here....
http://musescore.org/en/node/21722
MAke sure you scroll down to the Google Drive link - the Filefactory version has been removed.
In reply to From by ChurchOrganist
so now that ive downloaded the document how do i use it in muse score?
In reply to so now that ive downloaded by jonathan aakene
http://musescore.org/en/node/50721
In reply to the marching percussion makes by jonathan aakene
I don't think it is intended that a hole in voice *2* would flag a score as being corrupt. As far as I know, it's still supported to delete rests from voices other than voice 1, although the trick you mention is helpful if you change you mind and wish to enter music into those hoels afterwards.
I am pretty sure the warning abut corruption should only happen if there is a hole in voice *1*, which should never happen, and which you cann;t make happen on purposes even if you tried, but occasionally will happen anyhow due to bugs in the software. These corrupt scores can lead to other problems later, including crashes, so it seems good to warn about them now. The warning that occurs when you load into the RC tells you exactly where the problem is, and then you can try to fix it.
In reply to I don't think it is intended by Marc Sabatella
you can't fix those holes in voice 1, other than by Ctrl-Del the offending measure, which will delete the non-offending measures in other staves too.
I'd rather have them fixed automagically by MuseScore or some 'MuseScore Doctor' tool
In reply to I don't think it is intended by Marc Sabatella
Actually, in many cases, you *can*, and in fact, we might consider putting together a how-to and perhaps linking to it from the warning dialog, if the system supports that.
See http://musescore.org/en/node/50566#comment-236431, in particular the second approach I mention. If the corruption is in the form of a "hole" in the measure, and you can tell where the hole is, simply lengthening the note before the hole fixes the corruption much of the time. I don't know why I never thought of this before, and maybe it wasn't effective in 1.3, but it actually works quite well much of the time in 2.0
And yes, automatically fixing holes (by adding rests and/or shortening notes) seems like a good thing to do, and could be worth trying to add. Depending on the actual problerm, any automatic solution might make the proboem worse, so we could make this something you initiate explicitly from that dialog (ie, a "Attempt Fix" button).
In reply to Actually, in many cases, you by Marc Sabatella
Well, you know my 'monster album', it has more holes in 2nd stave that measures with real content, so this is just not a viable solution.
It may work for the odd measure here and there though
In reply to Actually, in many cases, you by Marc Sabatella
Sometimes the exchange voices trick I mentioned works for a corruption in voice 1.
Not a 100% success story but I find it works in 90% of cases.
In reply to Sometimes the exchange voices by ChurchOrganist
Ah, that fixed it for me too! At least the vast majority of the issues with my alsbun, just a handful left for manual repair...
In reply to Sometimes the exchange voices by ChurchOrganist
Indeed, voice exchange is also a good thing to try for holes in voice 1. The downside is, if you weren't otherwise using voice 2, now you are :-). But you can easily delete those rests when you are done. Not so viable if you are sometimes using voice 2, sometimes not.
In reply to Indeed, voice exchange is by Marc Sabatella
selecting all voice2 rests and hiding them did it for me ;-)
In reply to the marching percussion makes by jonathan aakene
OH i get it now i have to open it to muse score then go to my synthesizer and then add it... THANK YOU SO MUCH !!!!
Should I download the RC or wait until the final release?
In reply to Should I download the RC or by JApgood
It's your choice. If you can wait a few days, then do so, as some bugs have been fixed between the RC and the actual release. The RC is usable if you need to do work before Tuesday, but you will still want to download the final version 2.0 when it's released.
It seems some keyboard shortcuts have been removed. Am I wrong?
In reply to It seems some keyboard by llopatin
No, you are right
In reply to It seems some keyboard by llopatin
Double post
In reply to It seems some keyboard by llopatin
Shift+number shortcuts were removed as they create conflcits with keyboards used in a number of countries. You can always added them back via Edit / Preferences / Shortcuts if you live in one of the counrtries where they work (or add *different* shortcuts for these commands otherwise).
Shift+up/down (formerly, diatonic transposition) and Alt+Shift+up/down (formerly, extend selection to previous/next staff) have been exchanged, for more compatibilty with 1.3 and generally consistency with how selection works in other applications.
That's the changes I know of since the RC, anyhow. Others were made earlier (like making Shift+S the staccato shortcut to solve the conflcit with ">" for diminuendo that existed for keyboard in a number of countries).
In reply to Shift+number shortcuts were by Marc Sabatella
I am still using the old version and there is a shortcut (undefined) for a natural sign. I defined it as shift+n. I don't see a way to add back a shortcut that is gone. I'm in the middle of a major project and it's probably for the best that I stay with the old familiar version until finished anyway.
Thanks,
Lenny
In reply to I am still using the old by llopatin
Now, that's interesting. I just went to check, and Sharp, Flat and Natural have been removed from the actions that can be assigned shortcuts. I wonder why?
In reply to Now, that's interesting. I by Isaac Weiss
No they haven't they've just been renamed.
Look under Note Input:
In reply to No they haven't they've just by ChurchOrganist
Thanks. Will do!
Lenny
In reply to I am still using the old by llopatin
To be clear, though: these are *not* the shortcuts you'd normally use to enter accidentals. Simple up & down arrow is the more proper way. The explicit accidental commands enter "user" accidentals, which is to say, they are commands to make the accidental appear whether needed or not. The intended use is courtesy accidentals. So if that's what you are using them for, great, then just re-apply your custom shortcuts in 2.0. But if you were trying to use them for ordinary accidentals, you should switch to using up & down instead.
In reply to To be clear, though: these by Marc Sabatella
Hi Marc. Right you are. Entering courtesy accidentals has been my main use for these shortcuts. Now that ChurchOrganist has pointed out to those of us who didn't know where to find them, all is right with the world!
Cheers!
Lenny
In reply to To be clear, though: these by Marc Sabatella
Sometimes when notating a measure with a momentary modulation, entering the correct accidentals is not possible with up and down (i.e., it will "skip" the desired accidental). I think this is also a use case for manual entry.
In reply to Sometimes when notating a by CombatCube
See this discussion....
http://musescore.org/en/node/51826
I find the audio sampling sets are very different Piano and Strings are less realistic sounding 1.0 is better in this regards. But brass instruments are much better in 2.0. I write mostly Classical music, and use the software as a performance too.
In reply to I find the audio sampling by rkarle
I guess what constitutes "better' is subjective - I find the piano and especially string sounds in FluidR3 (the default soundfont in 2.0) *infinitely* better / more relaistic than the corresponding sounds in TimGM6mb (the default in 1.0). But while personal preference is subjective, both 1.0 and 2.0 allow you to select whastever soundfont you want, and what is objectively better about 2.0 is that it allows to you select *multiple* soundfonts, so you can choose the brass sounds from FluidR3 and stirngs from TimGM6mb if you like. Althought I would recommend you check out the other avialable soundfonts as well - there many soundfont that are much better than default for 1.3.
I Don't know if this would be considered a bug or not. I successfully change sound fonts. After doing so I noticed the volume was much louder. But as soon as I change the instrument setting in the Mixer the Volume dropped a great deal maybe 70 to 80% lower I had to turn up my head set all the way to even hear the playback.
In reply to I Don't know if this would be by rkarle
It's better to start new threads for specific problem reports. If you do so, please include the score you are having problems iwth and *precise* step by step instructions to reproduce the problem.