I use Musescore 2.0.0 (1efc609) (Date modified: 2014/12/10)
When I add a measure at the beginning of a score, it takes away the key signature.
I am very impressed with Musescore 2!
Thanks
Can you reproduce this in a current nightly build? The version number of the build you are using suggests it was actually from August (the "Beta 1" build); the date you mention is probably when you installed it.
If you can reproduce in a current build, please attach the score you are having problems with and steps to reproduce. I find inserting measures at the beginning of a score works as expected in current builds.
This is indeed the latest msi (Muscscore-2.0beta1.msi) as downloaded from Musescore.org.
I do use Windows 7.
I reproduced it with different scores in different keys.
Attached two files. Begeleiding I use as a template and l300 an example illustrating the - I think - bug.
Thanks
The Beta might be the latest "msi" file, but as mentioned, it actually dates from August. The Nightly builds are more recent - all the way up until just a few hours ago.
In any case, if I load l300.mscz into the latest build, select the first measure, and press Insert, the newly inserted measure does get the correct key signature. And I can verify it was broken with the Beta build, reported and fixed as #31576: Insert measure in front of score deletes key signature.
So unless you are seeing otherwise with a more recent build, or have different steps to follow than the ones I listed, I think we can close this. Feel free to reopen if you have precise steps to reproduce the problem with a current build.
I downloaded •MuseScoreNightly-2014-12-18-1841-0ae917e.7z - tried all the instructions on the page. Get a "This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information" message - and when I click it stops working.
From the DOS prompt I tried nightly -f as well as nightly.exe -f. No reaction,
This problem is only on my Windows 7 desktop. It does word on my Windows 8.1 Laptop
Comments
On Vista + 0ae917 not happen, you have Win 7, try a nightly latest version
Can you reproduce this in a current nightly build? The version number of the build you are using suggests it was actually from August (the "Beta 1" build); the date you mention is probably when you installed it.
If you can reproduce in a current build, please attach the score you are having problems with and steps to reproduce. I find inserting measures at the beginning of a score works as expected in current builds.
This is indeed the latest msi (Muscscore-2.0beta1.msi) as downloaded from Musescore.org.
I do use Windows 7.
I reproduced it with different scores in different keys.
Attached two files. Begeleiding I use as a template and l300 an example illustrating the - I think - bug.
Thanks
The Beta might be the latest "msi" file, but as mentioned, it actually dates from August. The Nightly builds are more recent - all the way up until just a few hours ago.
In any case, if I load l300.mscz into the latest build, select the first measure, and press Insert, the newly inserted measure does get the correct key signature. And I can verify it was broken with the Beta build, reported and fixed as #31576: Insert measure in front of score deletes key signature.
So unless you are seeing otherwise with a more recent build, or have different steps to follow than the ones I listed, I think we can close this. Feel free to reopen if you have precise steps to reproduce the problem with a current build.
I feel quite stupid! Where do I get the latest built? When I click on Update, the respond is that there are no updates...
Thanks
Here:
http://musescore.org/en/download#Nightly-versions
I downloaded •MuseScoreNightly-2014-12-18-1841-0ae917e.7z - tried all the instructions on the page. Get a "This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information" message - and when I click it stops working.
From the DOS prompt I tried nightly -f as well as nightly.exe -f. No reaction,
This problem is only on my Windows 7 desktop. It does word on my Windows 8.1 Laptop
The problem is solved in the latest Nightly version
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.