Hey thank you for your review! I'm really busy at the moment so I'll try to implement these suggestions as soon as I can
NinSheetMusic is the LARGEST video game sheet music archive on the entire internet worldwide!
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts MenuQuote from: Static on February 18, 2022, 07:11:10 PM
- The console label should be Xbox 360 instead of Multiplatform - we go usually by the original release platform. This game was originally a 360 exclusive before being ported to PC and Xbox One/Series. Just something to keep in mind for the future, no big deal really. Since you can't change the label yourself, we'll take care of that for you later.
- So, the two keys used in the piece are G Phrygian and F Phrygian, so your key signatures are technically already correct... But I'll also say, when choosing a key signature, another option is to pick the one that relates to the tonal center of the key and use accidentals to show modes. Gm and Fm key signatures would be used if you wanted to go that route. But, it's perfectly fine to keep what you have, so don't feel like you have to change anything.
- m15-17 RH: I'm not hearing these lower harmony notes in the original. It's fine to leave them in, but it sounds weird when it's just those three measures. I suggest either leaving them out or continuing through m24 (if you need help identifying chords lmk).
- m36 RH beat 1: I hear an Fb under the Ab here in the original piano part, but since the LH is in a similar range I think it's fine to exclude it.
- m38 LH sounds like it has an extra note towards the end than what you have written. You could maybe write it like this:
Everything else looks good, nice work
Quote from: Bloop on February 14, 2022, 05:34:18 AMHm it's still different, maybe it's just an issue with NotePad itself, or the mus file just displays differently in the full version of Finale. You could try downloading another pdf exporter and see if that fixes it, but we can also just export the pdf ourselves once everything is finished.I also see it fine in my Finale NotePad, I tried exporting it in other ways but it doesn't fix it, I think a Finale user with the full version could help me with that
Quote from: Bloop on February 14, 2022, 03:24:43 AM-The pdf has some weird formatting stuff going on compared to the mus file, do you happen to have exported the pdf from NotePad's built-in pdf exporter (if it has one)? If so, that pdf exporter is known to have some issues, so it's usually better to use an external pdf exporter (usually via the print menu). I personally use Microsoft Print to PDF.I'm pretty sure I exported with the Print menu and then "Microsoft to PDF". Anyway, I did it again with the edits I made.
Quote from: Bloop on February 14, 2022, 03:24:43 AM-m36-38: Did you consciously put the L.H. here up an octave? I hear it an octave down in the original.This is an old sheet (2-3 years ago) but I think I made it intentional. By listening to it again I prefer to have it an octave higher, it sounds better to me with the build-up chords in the next measures
Quote from: Bloop on February 14, 2022, 03:24:43 AM-Lastly, what is the context in the game for this piece? Usually we add repeat signs or D.S./D.C. markings at the end to signify where a piece repeats to, but if this is from a cutscene, then don't worry about it :p Maybe you could then add a fermate on the last L.H. note, or tie both the last R.H. and L.H. notes over to a final bar with whole notes and fermates: as long as it's clear that the player has to end and hold on the last note.Yep I won't spoiler which one but this piece is from a cutscene
Quote from: Kricketune54 on February 08, 2022, 10:05:09 AMI'm pretty busy atm to do a note check or anything but just wanted to pop in and say great first sub! It looks like a great sheet just from looking at it a bit. Just going to lay out some stuff I noticed on a visual pass. Haven't listened to Reach's music a whole lot or played in years but this one sticks out pretty memorably, one of my favs from it
I'm going to separate comments by things that can be addressed after converting from MuseScore to Finale Notepad, and things that unfortunately cannot be done on your own with Notepad (no fault of anyone who uses notepad, it's literally just not able to do a good number of things), but either myself or someone else who has the full Finale program can fix for you and send you a file with that stuff corrected
Stuff that can be addressed in Notepad
-Generally, crescendos (and decrescendos) if being paired with a dynamic extend up to that dynamic or through the last note before a dynamic. There's a couple instances like m.27 and m.38 where the cresc. stops before the end of a phrase. This photo below is an example of how this should lookSpoiler
[close]
- While they are correctly placed through most of the song, it's preferred to keep dynamics aligned with a notehead. For example, the mp in m.5 could go a little more to the left so it is centered over that first eighth note of the measure
-The first tempo mark should align with the time signature, rather than the first note, so just move that to the left till it's centered over 4/4
-I think Bungie should be credited at the bottom credit of the first page as well. Usually people on here do a developer, publisher formatting
Stuff Notepad can't do
-The first page is spaced out a little weird where there's a lot of extra space between the last measure system and the copyright info. Up to you if you want to put another system onto the first page, but if not, perhaps increase the distance between each system on that first page
-The "a tempo" mark is like 2 font points too big; I'm not sure what causes this but when I used to convert from MuseScore to Finale Notepad, I used to encounter it as well. Given this is a tempo symbol and not a regular text item, I don't think you are able to change this through Notepad, given it's limited interface and ability to change stuff.
Page created in 0.106 seconds with 16 queries.