Cannot create a new score

• Dec 31, 2020 - 04:27

I don't know what happened but suddenly Musescore -latest nightly dev version will not let me create a score that uses a template. I get this error (see below). If I just create the score without a template and add my own instruments, it is fine. Thinking it was some weird glitch, I downloaded a new version of Musescore, but it didn't help.

Cannot read file D:/MuseScore 3-Dev//templates/01-General/03-Grand_Staff.mscx:
This score was saved using a newer version of MuseScore.
Visit the MuseScore website to obtain the latest version.


Comments

Are you sure you are actually runnning the nightly build when you get that error? To me, this looks like you are actually running 3.5.2 (or earlier) but with settings manually changed to access configuration settings from a nightly build. It's true you'll get that warning when opening a 3.6 score in 3.5.2 or earlier. You can usually just ignore it though.

Go to Help / About and see what it says. Also tell us what OS you are on and how you are starting MuseScore (command line, program icon, etc).

In reply to by odelphi231

You wrote:
About > help says: "unstable Prerelease for version: 3.5.0". I hit that little symbol next to the revision # and get this:
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.5.0.13830, revision: 568e538

What??? ....unstable Prerelease for version: 3.5.0???
You should double check your versions - should be more like 3.6, and not 3.5.

In reply to by Jojo-Schmitz

I just downloaded the latest nightly build. If it was the wrong build, then the wrong build was put out there. Here is the file name I downloaded and installed on 12/30/2020:
MuseScoreNightly-latest-x86_64.7z
When the 3.5.0 build was the latest build, I didn't have this missing template issue, so there is something wrong with this build.
BTW: I am a he. (LOL)

In reply to by odelphi231

The one I downloaded just now correctly contains a 3.6.0 package (202101020438-3.x-ae5bcd3-x86_64). As the staff is currently on holiday, it is safe to assume the automatic build process did not change in the meantime.

If you wish to be on the safe side, don't download the "latest".7z, but download the most recent one with a designated timestamp and hash. they should be identical, but you might avoid some package issues in such a case.

In reply to by Marc Sabatella

I looked at what the preferences was saying for the folders and here is what it says:

Musescore folders.png
Notice that it puts forward slashes instead of back slashes. Forward lashes is Linux nomenclature, not windows. Also, it created a "Musescore3Development" directory ( I didn't create it) but put nothing in them. All the directories (styles, images, etc) at that address are blank.
Anywho, I changed the template directory to my stable release directory that DOES have templates in them (using backslashes). However, it didn't make a difference. It still gives me the error message in my OP.

In reply to by mike320

This is happening on the latest nightly release. Is not recognizing folders and putting forward slashes a known regression with the nightly releases? I have been using nightly releases for a few months now with no problems like this. I am using the latest stable release 3.5.2 also; you are right, it doesn't have this problem. However, before yesterday the latest nightly release didn't have this problem either.
Also, I thought the latest nightly release BUILDS on top of the latest stable release, so it should have NEWER code than the latest stable release.

In reply to by odelphi231

If you changed something in a nightly, it will stay changed in all nightlies until you either change it again or revert to factory settings, which I suggest you do, then make your changes again. Nightlies do not affect stable releases, they coexist without knowing the other one is there. This is a safety so a nightly with a disasterous bug will only affect nightlies rather than your stable install.

In reply to by mike320

Mike, you said the opposite of what I said. I know nightlies don't affect stable releases, but I thought stable releases affect nightlies. In other words, I thought once you have a stable release you BUILD upon that with the nightlies. So the latest nightly should have everything the stable release has PLUS any bug fixes, new features, etc. THEN when the nightly is considered "stable" enough it becomes the latest stable release. Then the cycle starts over. So, I disagree that the nightlies exist without knowing the stable release exists. The nightly is the child of the stable release. Are we saying the same thing just with different semantics?
I hit the "reset preferences to the default" button but all it does is switch the folder directories to the empty directories that it created and converts my back slashes to forward slashes. So I cancelled out of it.

In reply to by odelphi231

The two don't share files on your disk drive unless you specifically direct one to use the files of the others. Nightlies eventually get built by the developers and most of the features in nightlies end up in stable releases but this doesn't happen on your computer. The only relationship between the latest stable release and the latest nightly is that the latest nightly came out after the latest stable release.

You may disagree all you want but that doesn't change reality. You can delete a nightly completely from your hard disk and the only thing it will affect on you latest installed stable release is that if you have intentionally accessed anything in the nightlies directories. So, if you have set any of your directories in the stable release's preferences to the nightlies directories, MuseScore won't be able to find that directory if you delete it.

It's better that you've made a mess of the nightly because you can revert it to factory setting and it probably won't affect the installed stable version because you probably haven't made the stable version rely on anything you've done in the nightlies.

If you don't believe me then there's nothing more I can do for you.

In reply to by mike320

Sorry, we are cross-talking each other. I am not thinking that my nightly is some how affecting my stable release on my disk drive. I am just saying on Github (or wherever they keep the nightlies) the nightly program is a child program of the stable release. So the nightly release DOES "know about" the stable release.
Did you see the pic I included in one of my comments? The folders under preferences is using a forward slash, which is a Linux nomenclature, not windows. I am a windows computer. Soooo, I am thinking that is why it can't find my template folder to use when setting up a score. Oddly, (as I mentioned in one of my comments) even if I change the forward slash to back slash, it STILL is looking for a forward slash directory and it can't find it. I think this is a bug.

In reply to by odelphi231

This is simply not true. The nightly builds have no relationship to and indeed knowledge whatsoever of any stable version you have installed.

Definitely remove that unstable release for 3.50, that's guarantee useless junk. The only release you should ave installed& normally right now is 3.5.2.

Then if you also wish to help test a nightly build, feel free to do that as well, but those don't install or share any info with the stable versions. Hard to say what might have gotten messed up in previous tests of nightlies, best to run Help / Revert to Factory Settings from that nightly if you wish to help test further.

In reply to by Marc Sabatella

Just noticed something. Like I said in my previous post, I changed the folders to use back slashes instead of forward slashes. Oddly, here is the error message I get now:

Cannot read file D:/MuseScore 3-Dev//templates/01-General/03-Grand_Staff.mscx:
This score was saved using a newer version of MuseScore.
Visit the MuseScore website to obtain the latest version.

Notice anything funny. First, it is still using forward slashes in the error message eventhough I changed them to backslashes. Second, in between the "MuseScore 3-Dev" directory and the "templates" directory it is showing 2 forward slashes. ODD.

In reply to by odelphi231

The forward slashes is what we show and translate to because we're cross platform and only windows is the backwards one here. All of that (including the double slash) is handled correctly in the underlying file systems.
All you are noticing is that you've somehow contaminated nightlies with stable directories or the other way around.

The latest (3.x) nightlies haven't been called 3.5.0 unstable for a long time now, as they are working towards 3.6.

In reply to by jeetee

Contaminated? What? I download it and then install it in a separate directory. How am I contaminating it. I even reinstalled the latest nightly just to make sure, but it didn't do anything.
The stable version has backslashes in the folders preferences. It is just the nightly version that has forward slashes.

Do you still have an unanswered question? Please log in first to post your question.