00:00

OpenScore - Tips for Transcribers


Uploaded on Feb 18, 2017

To-do list: https://goo.gl/onuEzN

If you would like to update the score with something on the list then please do! Send me a message with your version attached and I will credit you here.

Thanks to:
Isaac Weiss - corrected various typos

tutorial tips how to OpenScore

Pages 5
Duration 03:42
Measures 96
Key signature natural
Parts 3
Part names Piano(3)
Privacy Everyone can see this score
License Attribution
Show more Show less

This score appears in:


Your comment


Comments

A correction is needed at the bottom of the first page. It should say "reduce spacing to 1.0 (Style > General > Measure)".
This is a case of US English vs UK English: "bar" is the UK English term for "measure", and is what MuseScore users from the UK see when they use the program.
I've got a problem with the repeat sign ! When listening to the transcription, the last bar of the 1st part is also repeated before going to the second part, which is not satisfying. Should we make a copy/paste of the first part or let it as it is written ?
Please ask for help on the MuseScore forums (https://musescore.org/en/forum) and upload your score as an attachment to the post.
Under the section "Shared Instruments Staves", the first note for Trumpet 2 in the transcription is a B instead of a G. Not that it changes the method, but it does give a better impression to show the right notes!
Ties crossing through voltas will need to be modernised. Many Joplin engravings have this issue. You can see from my upload here https://musescore.com/jamesbrigham/scores/1942901 that I created false ties to give the impression of a tie which are not MusicXML friendly at all. It appears that even Sibelius does not support ties through voltas http://www.sibeliusforum.com/viewtopic.php?f=3&t=70449&p=80767#p80786

When it comes to proofreading, matching line breaks and page turns would be helpful for matching like for like with the PDF. Then they could be removed after this faze.
Shoogle, I was wondering: did your semi-realtime midi thing get implemented?, because that could be really useful
Just an update: it will be in 2.1, and not hidden either.
It will be in MuseScore 3 for sure, and possibly in MuseScore 2.1 as a hidden experimental feature.
thanks for sharing, cause I was under the impression that the strings whenever there are two notes, were supposed to be divisi.
whenever I saw the strings go into two notes I always cringed because I figured they were supposed to be double stops, not divisi.
so this clarified some things, Thanks :D