Die Walküre, Act III Scene I- complete!
The score for the complete scene is too large to upload to MuseScore.com (the limit seems to be between 1000kB and 1200kB), so I am providing the score for the complete scene attached to this forum topic.
As split into two parts on MuseScore.com please see here:
https://musescore.com/martystrasinger/die-walk-re-act-iii-scene-i-part-…
(This version was slightly revised from my original upload to provide forward continuity as I continue to work on the rest of Act III.)
and here:
https://musescore.com/martystrasinger/die-walk-re-act-iii-scene-ib
IMSLP45497 was the primary source and the pagination of my transcription matches it exactly.
IMSLP341993 was used to provide the English and French lyrics, and as a check when errors were suspected or noticed in IMSLP45497.
I make no claims to making no mistakes, and if anyone notices any I would appreciate the correction.
Act III Scene II is in progress and will (hopefully) be done around mid-2021.
Many thanks to all the forum members who provided assistance!
| Attachment | Size |
|---|---|
| Die Walküre, Act III Scene Ia+b.mscz | 1.25 MB |
Comments
Marty,
I didn't take a detailed look at this until now. It seems you may have made a transcribing error. See Trabspose for a discussion. If you are aware of this notation and chose to make it look correct but play some notes an octave low, that is a perfectly valid decision. If you want to fix it there are instructions in the link.
In reply to Marty, I didn't take a… by mike320
Please find attached the corrected score. As noted at the forum entry above, I took mike320's suggestion to use an ottava bass clef with the 8 above the clef rather than the standard bass clef and then move the notes up an octave.
In reply to Please find attached the… by marty strasinger
One last set of issues corrected, hopefully no more going forward!
In reply to One last set of issues… by marty strasinger
You have “III Trumpets in E“ scored. Measure 41 (and others) have notes that are only playable by experienced players and with instruments with slides. Changing to C trumpets takes away this problem.
This score perfectly shows where MuseScore still needs to improve performance: playback on my Core2Duo laptop is laggy in many places and even aborts multiple times throughout the piece; at least part of this is definitely because someone had the great (hah) idea to split rendermidi into chunks instead of doing the whole piece at one time (which is also needed for proper collision detection and handling).
You can reduce the size of the file by removing the 600 kB title picture (or ahem compromising ahem on quality with it)… even losslessly,
jpegoptim -s --all-progessivereduces it to 560 kB already, resaving in GIMP with 80% quality (and no tags, colour profile, etc.) gets it down to 415 kB… 70% 329 kB, which might just be enough to bump you to the threshold musescore.com needs (removing the thumbnail from the .mscz container before uploading (this can only be done by manipulating the PKZIP container manually, not from within the software) shaves off another 30 kB, and while it probably wouldn’t save much, removing optional whitespace from the.mscxinside the container could also save some).In reply to This score perfectly shows… by mirabilos
Hmm, my Core2Duo (Desktop) got retired some 5 years ago, and I do tend to keep my computers rather long...
In reply to Hmm, my Core2Duo got retired… by Jojo-Schmitz
This is a laptop, newer models have massively worse ergonomy and it’s fully sufficient for all my needs given I don’t use those proprietary high-blingbling operating systems or desktop environments.
Resource waste is never okay though, and if this makes it easier to see it…
In reply to This is a laptop, newer… by mirabilos
I already tried completely deleting the title page picture, it wasn’t enough to allow the .com website to accept it.
I emailed the .com site to find out what the actual size limit was. They declined to answer the question directly, other than to acknowledge that there is a size limit. They also offered to split the score into smaller pieces for me but I decided to do that myself.
No problems with audio playback at my end, but all of my systems are pretty robust.
In reply to I already tried completely… by marty strasinger
Makes me wonder if they even know themselves… the .com site has so many problems anyway…
In reply to Makes me wonder if they even… by mirabilos
It would be nice if one were advised up front that a score was too large to be accepted. Sometimes you get an error message of some sort after 10 or 15 minutes, but sometimes you just give up after several hours of the “processing your score” message.
In reply to It would be nice if one were… by marty strasinger
Ah, so it’s a score complexity limit, not a file size limit.
Too bad.