1st Upload using V.2.0 Disappointment
This afternoon I upload my first piano score that I had made using Version 2.0. The result was so disappointing that I deleted it. Some issues were:
1. Even though I scored it using the old sound font from V.1.3 to get the Acoustic Grand Piano sound instead of the tin-pan Yamaha Grand Piano sound of V.2, what came out of the player at MuseScore.com was the undesired Yamaha sound.
2. Line breaks were ignored.
3. Making a hairpin "invisible" was ignored.
Was this a learning experience of how it's going to be, i.e. the User has lost some functionality of how their uploaded scores look and sound or are these known bugs?
On another matter, upon trying to open MuseScore.com is anybody else but me getting the warning message of: "Your connection is not private" (Chrome) or "There is a problem with this website's security certificate" (Internet Explorer) and access denied (Chrome) or not recommended (Internet Explorer). I sent a message to MuseScore about this but received no reply.
Comments
Thanks for sharing your feedback. There is an ongoing effort going on to make sure the score as you created it on your local machine will be rendered the same online. In order for us to improve things, all we need is the link to your online score and the list of issues with it. This way we can improve things. If the score is private, you can share a secret link with us via support at musescore dot com. Thanks for your support.
As for the last part of your post, I emailed you directly.
In reply to Thanks for sharing your by Thomas
I've uploaded the score again and the link is: https://musescore.com/user/24069/scores/831001# The issues are:
1. The sound is the Yamaha piano from the V.2 sound font and not the Acoustic Piano sound font from V.1.3 that I used to make the score.
2. Measures 12-13 should be on same line.
3. Hairpin under measure 12 should be invisible.
4. Measures 23-24 should be on same line.
5. Measures 25-26 should be on same line.
6. Measures 44-45 should be on same line.
7. The stretching of the above measures make the page breaks at measures 16 and 66 misplaced.
In reply to I've uploaded the score again by hmscomp
For the measures on the same line, it looks on my system exactly how it looks on musescore.com for the measures I checked. Often what happens is due to slight font differences between systems or floating point round-off differences, you get very occasional differences in these calculations. I've never seen so many in one score, though - at least, not with 2.0, which is somewehat better about this than 1.3 was. When you are using line breaks to enforce a particular layout, it is good practice to select all and reduce stretch a notch as a final step. It will have no visible effect because the line breaks will lock the current layout, but it greatly reduces the likelihood of that these slight difference in calculations will cause a visible difference.
As for the hairpin, not sure what's going on there. You might try deleting it and adding it again. I don't suppose you started this with a prelease build? Occasionally, especially for hairpins that stretch across systems, MuseScore can get confused as to whether you are trying to hide the whole hairpin or just the "segment" for the particular system you have selected. Several bus along these lines were fixed leading up to the release of 2.0, but it's possible some case got missed.
In reply to I've uploaded the score again by hmscomp
You can follow up the root cause of this issue at #43661: Inconsistent font rendering on Windows vs Linux
Also, be aware that sound is going to depend on speakers, plus it is subjective. On some people's speakers and in some people's subjective opinions, the 1.3 sound for piano or some other particular instrument might have sounded better, but for most of us, the exact oppposite is true. So I wouldn't reject a score just because you happen to prefer how it sounds to you on your particular system with your particular speakers using a different soundfont.
In reply to Also, be aware that sound is by Marc Sabatella
Correction: It's measures 10-12 should be on same line. Measures 13-14 on the same line is correct.
In reply to Correction: It's measures by hmscomp
I guess we could argue the sound issue forever with agreeing to disagree the only outcome. As for the formatting, my point is that in using V.1.3 I never had to think so much about it as you now describe. What I saw on the page locally is EXACTLY what I got at MuseScore.com. Now it seems some uploading trial and error is going to have to happen to really find out what reformatting is going to take place in order to really know what adjustments have to be made.
In reply to I guess we could argue the by hmscomp
@hmscomp You can take it from me as the site developer that we are working towards a full proof solution, both for sound and score rendering. You can follow up the issue at #43661: Inconsistent font rendering on Windows vs Linux. As with all software development, it may take some time before we got to the bottom of it. Thanks for your patience.
In reply to I guess we could argue the by hmscomp
I'm glad you happened to find that your particular scores looked exactly the same on musescore.com as on your system for 1.3, but the underlying issue existed in 1.3 as well and I actually saw these sort of differences just as often. I'm not saying it isn't occasionally an issue, but I am suggesting you happened to get lucky in the past and happened to get unlucky with this particular score. Luck of the draw, not some new regression.