Bug when adding measures at the beginning.
In both 3.6 and 4.0:
I created a score in 3.6, then decided to add an intro, so I inserted 8 measure before the first measure. The result was that measure 9 had clefs and key signatures. Without saving, I then opened the opened the score in 4.0 and inserted the 8 measures with the same result. I've attached the 4.1 version of that file.
I would guess that the initial clef and key signature are associated with measure 1 instead of with the score. If so, the simple solution would be to move, rather than copy, those from the original to the newly-inserted first measure.
|Mi Chamocha-Grosky-4.1.mscz||166.96 KB|
I've seen this too, but so far have been too lazy to report it...
Edit: and now it doesn't happen anymore, not in 3.6.2 at least
And not in 4.0.1 either.
In reply to I've seen this too, but so… by Jojo-Schmitz
This might be a good first bug for me - if I could get my GitHub account to access the MuseScore source.
In reply to This might be a good first… by Aaron Grosky
That should be the easy part
In reply to That should be the easy part by Jojo-Schmitz
I thought so, too. However, I followed the directions (or thought I did so) and GitHub told me it was working on it, but I neither got access nor a reason why I didn't.
That was before 4.0 work was started.
In reply to I thought so, too. However,… by Aaron Grosky
You create an accound on GitHub and fork the MuseScore repo
You won't get write access to the MuseScore repo
In reply to Huh? You create an accound… by Jojo-Schmitz
"Huh?" - I agree. My requests just sat there. I didn't even get as much as an acknowledgement that the request was being processed or had failed.
I have 50 years experience mostly using C, C++ and shells - Korn, Bourne (again (bash) or not (Unix sh)), and predecessors - but I've never use GitHub. Marc pointed me at some documentation and I though I had followed the steps.
In any case, I've switched to the nightly build so that should stop me from reporting bugs that somebody has already fixed. My working with big band scores uses some parts of MU that appear not as well tested.
In reply to "Huh?" - I agree. My… by Aaron Grosky
What request, one for getting an account created, or forking the repo?
In reply to What request, one for… by Jojo-Schmitz
Forking the repo.
In reply to Forking the repo. by Aaron Grosky
What's your GitHub account?
In reply to What's your GitHub account? by Jojo-Schmitz
GitHib's display of my profile (overview) lists that I have 1 repository: https-github.com-musescore-MuseScore
On my last project, I used git from LINUX. I currently use MU from Windows because I use the GoogleDrive for my MSCZ files.
Since I started this comment, I installed the GitHub Desktop and did the tutorial. I now have 2 repositories.
I think I know how to clone the repository. About how much disk do I need for this? I have several gigs available in my "business account" GoogleDrive and I'd like to have my work backed up.
On the last project I where I had worked, the git repository was structured - the main repository had numerous nodes on which other repositories could be loaded. Each one represented a part of the project, though some were common to most of the others.
In reply to aige02 (https://github.com… by Aaron Grosky
That https-github.com-musescore-MuseScore is empty and not a fork of https://github.com/musescore/MuseScore. Just go to that and hit the Fork button there
In reply to That https-github.com… by Jojo-Schmitz
% du -sh
In reply to % du -sh 1.6G by Aaron Grosky
In reply to Huh? by Jojo-Schmitz
The space taken up by clone before attempting to build (and the command to determine that space).
Thank you for the help. Now I get to do a lot of reading of code. :-)
In reply to The space taken up by clone… by Aaron Grosky
I know that, but...
First fork on GitHub (you hadn't done that when I last looked, but have now), then clone to your PC (you might have cloned the musescore repo instead, but won't be able to push to it)
In reply to I know that, but... First… by Jojo-Schmitz
That should be easy enough to correct once I've made and tested changes. First I have to understand enough to see what changes when measures are added (inserted or appended at a measure), how to recognize the first measure, etc., and lots more. In my last job, I used more than one method to move changes from one clone to another.
FWIW, When I add measures to the beginning of a score, The key signature stays at the start, not at the measure before the new measures. In both versions. Sure the clefs have to be deleted.
In reply to FWIW, When I add measures to… by bobjp
In MU 4.0.1, I thought when I inserted 8 measures to a score imported from 3.6 (as described in the original post), I got both clefs on every staff and a key signature. However, looking at the original of the attached score, I only see the tempo marking at the original first measure - neither extra clefs nor extra key signatures.
I just inserted a measure using 4.0.2-nightly to one score and I got clefs on only 2 of 17 instruments and no key signature. I inserted a measure to original of the attached score and got extra clefs on all staves. In any case, not having the key signature is a significant improvement.
I can reproduce with your score (but not with its" Bass (Treble)" part), but not with other scores
In reply to I can reproduce with your… by Jojo-Schmitz
Shiny_Stockings.mscz also shows the problem, but only on a single staff. I have to insert a measure and undo that change to get the measure numbering correct. Otherwise, multiple undo's tend to crash MU.