The case of the vanishing soprano
Hello everybody and a happy new year 2014
I have this file from a friend's PC to which I added a few corrections and lyrics with Musescore version 1.1 for Mac (OSX 10.7.4). There is one note (measure 11, first note) that does not play. I erased and replaced it, I deleted the measure and rewrote a new one, all in vain.
The second bug is when I add "D.C. al fine" : suddenly the soprano's line partly vanishes. Only a few notes play but all is OK with the other voices and the tenor part sounds beautifully. Since the file was originally written by a tenor, I suspect foul play, but the man would have to be incredibly brilliant to insert code with such an effect. Ideas anyone ?
Best regards
Comments
It's usually almost possible to help without seeing the scores you are having trouble with (the actual MSCZ files),
In reply to It's usually almost possible by Marc Sabatella
Thank you for this prompt answer; I'm sorry; I thought I had attached the file correctly, but it seems I have not. I will try again.
In reply to Sorry by altebrilas
On the soprano staff:
For whatever reason, the first note in measure 11 seems to be tied from the note at the end of measure 10.
Delete the last note in measure 10 so a rest will appear, and then re-enter that same note.
Second point:
Where do you put the D.C. al fine?
It seems ok when I put the D.C. at measure 17, and the Fine at 10.
Regards.
In reply to Vanishing note (sound) by Jm6stringer
Thank you so much for helping out. As for the DC al fine, I guess that was a bit of overkill because I couldn't make the end repeat work properly, so I tried alternatives. Originally, I used this, which does not work, and I can't figure out why.
Why MuseScore 1.1 and not 1.2 or 1.3?
Could have been #3482: pasting after copy/cut creates note with wrong duration, fixed in 1.2.
Here's your score with the fixes Jm6tringer suggested
In reply to Why MuseScore 1.1 and not 1.2 by Jojo-Schmitz
Thank you so much. Everyone is being so incredibly helpful. The first bug, the missing note, is now fixed. But the repeat still does not work. Even with the Fine at measure 11. As a matter of fact, you have to listen to the soprano line only to hear what's wrong. The second time around, half the notes are missing. I left a copy of the file in the reply above.
In reply to repeat still buggy by altebrilas
Not only the 2nd time, the 1st time too
Look at the note properties, this do have a non-default ontime offset type and value, some also a non-default offtime offset type and value and a non-default velocity type and value.
That is why re-entering these notes fixes it (in some cases, but not all, strangely).
I've fixed this (everything to default velocity, ontime and offtime), see attached
In reply to Not only the 2nd time, the by Jojo-Schmitz
I can't thank you enough and all the people who have helped out too. It works beautifully now. Wish you could fix our choir in real life as easily. Do you think this was due to the transfer of the file from one machine to another ?
Thank you again
In reply to Brilliant by altebrilas
I'm pretty sure it wasn't the file transfer. Could have been your fiend imported a MIDI file? What version is he using?
In reply to I'm pretty sure it wasn't the by Jojo-Schmitz
Yes, that sounds right. He tells me that's what he did. Thank you. You have now solved the case, I think.
In reply to Why MuseScore 1.1 and not 1.2 by Jojo-Schmitz
That's a good question. I'm still very much a beginner and I am so amazed at the possibilities of musescore that it did not occur to me to check for newer versions; also, to tell you the truth, I have had very disappointing experiences with some software updates in the past. And I don't mean Windows only.
In reply to why not 1.2 or 1.3 ? by altebrilas
Triy 1.3. There have some issues cropped up recently with it, but only in connection with Mavericks, in which case the recommendation was to use 1.2 instead. And on some older Macs you 're still restricted to 1.1, that's why for Mac all 3 are available from the download page
In reply to Triy 1.3. There have some by Jojo-Schmitz
Thank you. I might try that. But I've also been thinking about another problem. I'm the one who edits scores for the choir so they can listen at home and learn musical notation at the same time. If I upgrade, everyone will have to upgrade too, in order to read the scores edited in the newer version, won't they ? The prospect is terrifying.
Best regards
In reply to exchange by altebrilas
All scores produced in 1.3 can be read in all versions back to 0.9.6, 4 years old. 1.3 is out since a year now...
See http://musescore.org/en/developers-handbook/release-notes/release-notes…
and http://musescore.org/en/developers-handbook/release-notes/release-notes…
This will change as so as 2.0 gets released and you switch to that.
But still all scores produces with any version can get read with newer versions
In reply to exchange by altebrilas
Unless you are MacOS / Mavericks, there are only advantages and no disadvantages to upgrading to 1.3. And even if you are on Mavericks, you are still better off in all possible ways upgrading to 1.2. These were both relatively minor releases that fixed bugs only, didn't break anything, and in particular didn't break backwards compatibility.
Now, when 2.0 comes out, that will be a different story. Dozens of new features, tons of bugs fixed, but likely new bugs will exists, and it definitely won't be backwards compatible at all. So that would be a release to not upgrade to lightly. But 1.3 is a no-brainer.
In reply to Unless you are MacOS / by Marc Sabatella
2.0 will read all old scores. They may not render exactly like they did in the older release unfortunately and some formatting might get lost, but surely not more than that. Anything else would be a bug that needs to get fix at highest possible priority.
In reply to 2.0 will read all old scores. by Jojo-Schmitz
Yes, I didn't to give the impression that 2.0 wouldn't read 1.3 scores. What I meant was, the reverse is not true - so if one person in a group upgrades to 2.0, everyone else will have to as well if they want to read the scores he creates.
In reply to Triy 1.3. There have some by Jojo-Schmitz
OK, I'm almost convinced. Just one more question : can I download 1.3 and still keep 1.1 running on my mac in case the other members of the group won't upgrade?
In reply to You are very persuasive by altebrilas
You can keep both installers on your Mac, but only one of them can be installed at a time.
So yes, you can download 1.3 and keep 1.1, if you only download it and nit install it...
No other member needs to upgrade. But you should recommend it to them too.
C'mon, be brave and just do it ;-)
In reply to You can keep both installers by Jojo-Schmitz
Sic itur ad astra
In reply to lol by altebrilas
Per aspera ...
Consider this hypothesis:
Write your official scores for the choir, for example, with 1.2 (for print and archive);
Ask to the singers to install the Nightly.
They can learn the songs by listening to and exploit the Loop option (see attachment) for storing the difficult passages or save in mp3 format (and listen on the mp3 player).
... to the infinity ... and beyond ;-)
In reply to @altebrilas by Shoichi
And nightlies even coexists wit a 1.x...
Ceterum censeo carthaginem esse delendam :-)
In reply to And nightlies even coexists by Jojo-Schmitz
My thought exactly :)
In reply to @altebrilas by Shoichi
… ad asperiora ;)
Thanks for the input.