NinSheetMusic Forums

Please login or register.

Login with username, password and session length
Advanced search  

News:

Congratulations!! You, yes, YOU, dear user, have been selected for the "You Read This News Item" award! Click here for your prize!!

Show Posts

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.

Messages - cacabish

Pages: [1] 2 3 4
1
Site News / Re: Update, Monday 11th of October 2021
« on: October 12, 2021, 02:40:10 AM »
Nice work everyone! ;D
And don't worry Bloop, it takes practice to announce updates; I'm certain you'll be a crowd pleaser before too long. ;)

oh yes, shoutouts to static and whoppybones for the (probably) longest submission to date.
And good grief! That sheet is a monstrosity!  :o

2
Projects / Re: cacabish's Halloween Sheets
« on: October 07, 2021, 08:55:39 PM »
I personally think this would be clearest. I asked other updaters for a third opinion, and one is pro without a tie, while another is pro with a tie, so it's an even split lol. Either way is probably fine, so I guess just keep it like you have now :p
It really only matter what our glorious leader Latios thinks... His words are absolute.

I think this is fine! My initial reaction would have been to put it below the L.H., but I think placing it around the area where the simile applies to (like you have now) is actually better
Good! Glad to hear it. :D

It may be there, though it is a bit hard for me to hear tbh. It could also just be N64 soundfont stuff that disconnects some notes. Anyway, it'd probably be nicer to play it like you have now in a phrasing standpoint.
Right, and that's what I figured was going to be the case.

I meant something like this originally:

The 8va marking won't really interfere with the L.H., so you don't have to worry about that. I personally think it's alright to have it like this, but if you feel it looks a bit confusing for one bar, I can understand that too ^^
Oops! This didn't even cross my mind! I thought you were talking about some crazy cross-staff shenanigans! Derp. :P
Well, this works great (save actually doing it in Finale... *grumble* *grumble*), so I've gone ahead and done it! I've also applied it for the F/A dyads as well since they could benefit from it too. I do have to wonder if this might be appropriate elsewhere, like m. 28 to keep the system uniformly formatted, or something like that. If you think other places may benefit from the same modification, let me know! :)

I wouldn't worry too much about if something is played laidback or not. The question we'll have to ask is "Does it matter if the player knows this one note is played a bit later than normal?" and I personally would answer "nah not really, it sounds fine if they play it like normal too". You could even say it would sound a bit weirder on piano than on oboe (is it an oboe?), as the oboe has a less strong attack than a piano.
Yeah, I figured this was the rationale and it makes sense. If somebody cares enough for being accurate, they're probably already familiar enough with the song and the notes are really just what they need.

It mainly has to do with strong and weak accents in a bar. In 4/4, beats 1 and 3 are strong, while beats 2 and 4 are weak. When working with nothing faster than 8th notes, it's fine to hide beats 2 and 4 behind quarter notes or dotted quarter notes, because they are the weak beats. We wanna see beat 3, because that's a strong beat. (Of course, beat 1 will always be visible, you can't hide that one :p)
Now, in 3/4, there's just one strong beat, namely beat 1. Beats 2 and 3 are weak beats. As we don't really care much about weak beats (again, when working with nothing faster than 8ths), it's fine to hide beats 2 and 3. For example in m30, you currently have beat 3 hidden like I suggested. I would've said the same if the tie was on beat 2 instead of beat 3. So that's why I think it's also fine to hide both of them: it doesn't create any ambiguity in my opinion.
I see. You've made your case well enough. I'll have to let that stew for a little while in the ol' noggin, but that's not important right now, so I've gone ahead and made the change.


That should be everything addressed! The file has been updated too. Do let me know if I've overlooked something in the sea of text. :)

3
Projects / Re: cacabish's Halloween Sheets
« on: October 07, 2021, 05:56:01 PM »
ohhhhhh my favourite childhood mario party board :O
Neato! I didn't grow up with Mario Party 2, so I don't have a "favourite childhood" board, but this one's pretty good, ngl. 8)


Anyway, addressing the feedback...

-m2 and 4: Not sure if this is controversial, but you could add a tie between the two notes in the R.H. to show that the trill continues from the note in beat 1. Currently, it may look like you need to lift your finger, restrike the note and then do the trill. Making the first note a dotted half note while keeping the triller where it is could work too, though it may look a bit confusing.
I didn't do this originally because I wasn't sure if this worked or not. I referred to Gould and, while she doesn't mention anything explicitly, her advice would seem to suggest that this works, particularly since the trill line helps clarify. So, I've tied the quarter to the half note. Let me know if this looks off and should be changed!

-m5 and on: If you want, you can put a tenuto marking on the 3rd beat to emphasize that this beat is not played staccato. You could also put a simile marking after 2 or 4 bars or so, so you don't have to show all the staccatos (and possible tenutos) in all other bars.
The tenuto makes sense and does clarify the articulation pattern, so good idea! As for the sim., I've never done one before and so I didn't use one originally, but since the LH never changes the articulation pattern, it's pretty reasonable to use one here. I've included it, however, since I haven't used one before, let me know if my positioning is off, something is ambiguous, or other such derp-age has occurred. :P

-m5 and 9: Is there a particular reason you started the slur on beat 3 instead of beat 2?
To me, the legato doesn't begin until beat 3. I can hear slight breaks for the two eighth notes that come before, but afterwards I cannot. However, I would say it does look nicer if the slur starts on beat 2 and, arguably, would be better for playing (and it's probably not even a big deal). I've changed it to beat 2 for now, but if you believe my rationale is justified, let me know and I can switch it back.

-m6 and 10: The D's on beats 3 should have a staccato too.
Good call! Fixed.

-m7-8 and 11-12: I think I'd prefer having beats 1 here as A# in m7-8 and E# in m11-12, as they're the M7 and #4 in their respective chords.
Sounds good! I went through like 3 or 4 different accidental combos while going through this originally. This was one of them that I had considered, but I wasn't sure of which was the best, so I just picked one I thought worked.

-m10: The F on beat 3.5 is in that soft xylophone background right? I actually don't think you should add it in, as it's not part of the main melody you're transcribing.
Fair point. REVERT!

-m20: The D grace note should be a D# I think.
I was pretty sure I had this as a D#, but I guess I didn't? Maybe it got lost somehow. Anyway, it's there now. :)

-m27 and 35: I think you can put the G-Bb dyads in beats 2 and 3 in the treble clef, for a bit better readability (arguably also for the F-A's m25-26 and 33-34). Though, if you wanna keep them as is, that's fine too: the stepwise motion makes the ledger lines a bit more managable.
You make a good point and I certainly don't prefer towers of ledger lines in my music, however, in this case, I think what I have works fine. There are several issues I have with moving them up and one such issue would be ambiguity with the 8va that controls the melody in measures 25-27 (this wouldn't be an issue in measures 33-35). I'm also not sure if I should just move them as if it were cross-staff notes, add LH brackets, how the stems of the RH should be oriented, etc. That said, if you have a nice elegant solution that works, let me know and I'll gladly put it in! But in my limited testing, stuff looks weird and I'm not confident enough in what I'm doing to make that change. :-\

-m29: Though I can hear the F here is timed a little laidback, I think it's still better to just write this with D# and E grace notes and a dotted half note F.
Good call! It certainly cleans that measure up really nicely. That said, should I add something that makes it sound more laidback? Or is that something left for the performer?

-m30: What you have is not necessarily wrong, but you can write the tied 8th notes F's on beats 2.5 and 3 as just a quarter note too.
Interesting... I wouldn't have considered that before. Anyway, I've made the change, but given the slew of tied notes around it, I thought it looked pretty nice with the tie. That said, if it looks good to you, it works for me! :D

-m33: I don't think the grace note is here, I just hear the F connected to the E in m32.
Yeah, definitely not necessary with the whole section under a legato. Derp. :P Removed!

-m37: I remember seeing a question about the beaming from this bar on discord, though in 3/4 I don't think it's as much of a problem to use two dotted quarter notes.
Would you mind expounding on this? I definitely am still learning about how rhythmic groupings work, but based on my present understanding, I think what I have is good and the Discord members seemed to agree. However, if there is some good reason why two dotted quarters work here, I'd like to know it! I'd be happy to make the change once I better understand "why" that change is better than what I have.

About Boo House, the only thing I can say is that the G on beat 1.5 from m2 would probably work better as a staccato 8th note (instead of 16th + 16th rest). Otherwise this looks fine! (It kinda sounds like the first 8th of m1 is two 16ths, but I believe that's just a percussion note that's throwing me off)
Yeah, that staccato eighth cleans it right up and definitely makes it look better. Thanks! :)


That should be everything! Thanks for all the feedback, Bloop! I really appreciate it. (Hopefully, you didn't get carpal tunnel after typing all that up. :P)
I've updated both files and feel free to let me know of additional things I can fix! :)

4
Projects / Re: cacabish's Halloween Sheets
« on: October 07, 2021, 04:12:15 AM »
The real horror is the NPC difficulty level on very hard
True that. And nothing is quite as terrifying as a computer with 50 coins nearing Boo when you're in first place with a star. :'(

Horror Land
- m10 RH beat 3.5 sounds like there's a staccato F here
Ooh, this one was really subtle, but it's there. Barely, but it's there. Good catch! I've put it in.

The Boo House
- I like the tempo marking! Just one thing to mention, but maybe you could add an 8vb/8va to the LH part. What you have currently is correct, but lowering it would just be to increase the octave range since this is missing out on the higher octave. It's fine the way it is now though
Sounds reasonable. I've gone ahead and added and 8vb to the LH and, I mean, it sounds spookier because spooky music loves that D E E P  B A S S. But, if it doesn't sound good or needs to be removed (or if I've misunderstood something), nothing one tap of the Delete key won't fix. Thanks for the suggestion!

With that, both files have been updated! Thanks Zeila! :)

5
Projects / cacabish's Halloween Sheets
« on: October 06, 2021, 02:36:55 AM »
This year, I've got two Halloween sheets, both from Mario Party! :D Gee, what a surprise...

The larger piece is a spoOoOoky board's theme (which will also be included in the upcoming Mario Party Superstars game)!
And the shorter is just a 4-measure little ditty that plays in the background when you're deciding which of your friendships you'd like to end. No biggie.


"Horror Land"
[N64] Mario Party 2
[MUSX]


-----
"The Boo House"
[GCN] Mario Party 4
[MUSX]


6
Site News / Re: One more updater update
« on: October 06, 2021, 01:01:47 AM »
Thank you so much for your countless hours of hard work and effort bettering the site, MSF! :D
I have learned so much from you across these last couple years, and for that, I am grateful. :)
Enjoy your rest in the shadows...

7
Project Archive / Re: cacabish's Colors Sheet
« on: September 28, 2021, 05:39:39 AM »
- Not sure if this is just Finale, but a few of the dynamics look a bit further right than they should be. m. 34, 35, 42 - could poke these left a bit to be centered over the note.
Okay, no biggie! Adjusted.
- I would consider a slur on the lower layer in m. 19-20 to show the phrasing there. In particular the D looks like it could be part of the upper layer. Similarly, it might help to put one on top of the upper layer in m. 21-22 to differentiate the legato part.
Ooh, a very good suggestion! I've done so. I am slightly worried that the slur from m19-20 might swoop a bit too low, though, so let me know if that's the case.
- Top layer F# in m. 22 beat 3 should be a half note
Done!
- For m. 33-34 and 41-42 the top E should be in its own voice sustained throughout the pair of measures.
Yeah, I had this originally, but worried about playability. However, now that I reexamine it, it's not too bad. Reinstated!
I would suggest just omitting it. The second layer here follows the (strings?) which ascends in single notes. The clarinet part here just rhythmically outlines the G chord throughout the measure so I wouldn't say it's important to write in on beat 4 when you haven't included it anywhere else.
Good point. It certainly also makes it look cleaner this way too. As such, I've removed it.

- Wonder if you still want to keep the staccatos in m. 23? The melody isn't particularly detached in the original there, and there is a contrast between how those notes are articulated vs. the notes in the next couple of measures
This I'm not quite sure of. I mean, it's just the same vibraphone that played the melody in m. 19-22, right? Do those staccatos need to go as well? Furthermore, if I were to edit m. 23, wouldn't I also need to edit m. 24 since it's just a continuation of the melody (I'm pretty sure that's logical, but I'm just checking)? Or am I missing the point here? Are you saying that I should introduce contrast, despite it being the same instrument as m.19-22? If you would expound some more, I'd appreciate it.

Anyway, I've gone ahead and updated the submission file with all the suggestions implemented, save the suggestion about the staccatos in m. 23. :)

8
Site News / Re: Updater update
« on: September 09, 2021, 05:56:52 PM »
Thanks for all you've done, Maelstrom! Best of luck in grad school! (Try not to die, okay?) :P
And congrats Bloop on becoming an updater! I look forward to working with you in the future! :D

9
Site News / Re: Update, Tuesday 31st of August 2021
« on: August 31, 2021, 03:50:09 AM »
A simply, spiffing set of sheets! Splendid!  ;D

10
Site News / Re: Update, Saturday 31st of July 2021
« on: July 31, 2021, 03:30:24 AM »
Lots of good stuff! Well done, everyone! ;D

11
Project Archive / Re: cacabish's Colors Sheet
« on: July 29, 2021, 04:58:19 PM »
One last thing, this is a very annoying Finale "feature" - when you add grace notes to groups of four 8th notes, the group splits. You might want to re-beam m14 LH. idk why Finale does that, it's really weird
An annoying feature, indeed. Thanks for catching that! I've fixed it now.

12
Project Archive / Re: cacabish's Colors Sheet
« on: July 29, 2021, 03:10:30 AM »
  • Console should just be [PC] rather than [MUL], since it came out on PCs first - this is more something for the updaters when we upload the sheet later, nothing you really need to worry about now lol. Likewise, the copyright year should technically just be 2019, but that's not a big deal.
Good to know! I wasn't exactly sure how the tagging work, but now I know! I've revised both, regardless.

  • m4/12 LH beat 2.5: The D should be a G.
  • m8/16 LH beat 4: There's a B under the D.
  • m10 RH beat 2.5: I don't hear the grace note here.
...
  • m16-17 RH: Missing a slur here (like in m8-9).
  • m17 LH beat 2: The lower F# should be Fn instead, or E# if you prefer.
All fixed!

  • m6/14 beats 1-2: The melody and accompaniment should still be legato here, but I'm assuming you wanted to emphasize the snare drum part here.
Yeah, that was the idea. However, I've decided to change it so it has some parallel structure with the neighboring measures, which I think works better.

  • m19 RH beat 4: The G is actually part of the off clarinet background voice, not the vibraphone melody.
This one took me a whole bunch of listens, but you're right! Wow!
But what should I do with it? I've put it on the second layer with the strings for now, but did you have something else in mind?

  • m23-24 LH: This kinda looks weird and is pretty ambiguous to read. I think this would convey the same idea more clearly:

    Remember, articulation and note length are two separate things. Don't use staccatos just because you want a note to be shorter.
  • Going off the above, I would use quarter notes for all of the staccato half notes and dotted quarters throughout page 2.
I concur. I often forget that, but yours works nicely without clutter, so I've implemented it.

  • Is there a reason why you only have a slur on the 16ths at the start of m25, and nowhere else in the same section?
Not really. I think I put it in there when I was listening, but now that I look at it (and listen to it) again, it's really not necessary.

I think that's everything! I've went and updated the files.
Also, thanks for your feedback, Static, I really appreciate it! Do let me know where there's more to be fixed. :)

13
Help Guides / Re: Formatting in MuseScore & Exporting to Finale
« on: July 22, 2021, 01:29:30 AM »
Importing into Finale, Common Final Adjustments, and Tips

So, you've got your cleaned MusicXML file in hand and ready to use Finale/Finale Notepad.

For both Finale Notepad and full Finale, you can simply drag-and-drop your .musicxml file onto the window.
  • For Finale Notepad, you can also go to File -> MusicXML -> Import... and select your file (you'll need to change the filter on the bottom right to All Files *.*).
  • For full Finale, you can also go to File -> Import -> MusicXML... and select your file.
At this point, cross your fingers, say your prayers, and hope that what appears before you is a semblance of your original MuseScore sheet.

If it doesn't look a NinSheetMusic sheet, don't pretend it is and submit it anyways!

With luck, it should be, but if it isn't, back up a few steps in this guide and try again. When in doubt, ask for help! :D

Common Adjustments
So, what now?
Well, inspect the imported sheet and see if there are any glaring (i.e. really bad) formatting problems. Here are some common ones:
  • Probably the most common issue I've seen is that stuff is too close together. Upon importing, some stems get longer and stuff gets more squished than in MuseScore. You'll just need to give stuff more room in MuseScore.
  • Another common issue is some of your text looks like Arial font. This happens if you accidentally had something that used MuseScore's default fonts (FreeSerif, for old versions, and Edwin, for newer versions). Go and fix it in MuseScore.
If you see issues like this, go back to MuseScore, make the adjustments (e.g. add more space, fix fonts, etc.), re-export to MusicXML, re-run through MusicXML Cleaner, and re-import. Rinse and repeat this until the issues are resolved. (You can also directly modify the .musicxml file. It's not for the faint of heart, but check the posted slides for more information, if you're curious!)

Now that the really bad stuff has been taken care of, we probably don't need to re-import anymore and we can now do our Finale adjustments!
Word of advice: as you do these - write them down! Seriously! You may need to re-import for some reason and you will lose all Finale adjustments when you do, so writing them down allows you to redo them without having to figure them out again! You can use a .txt file, a Word document, a Google doc, or a good ol' fashioned piece o' paper. Just do it! :)

Here is a not exhaustive list of common things you'll need to fix in Finale/Finale Notepad:
  • Accidentals on tied notes or grace notes often disappear, even though they are played back (or even reappear) during playback in Finale Notepad. Compare against your MuseScore sheet and see what broke and then add them manually.
  • Staccatos and other articulations like to go on magical journeys and flip to the opposite side of the stem they're supposed to be. This is common if you have multiple layers or changing clefs, but can appear even if everything is normal. Compare against your MuseScore sheet and see what broke and then reposition them.
  • Arpeggios (aka “rolls”) and glissandos (aka “slides”) almost always break in some way, shape, or form. Make it look nice and you should be good to go!
  • Slurs can sometimes become the world's steepest mountains, like to overlap stuff, or go on magical journeys. So, as needed, flatten them out, make them not intersect, make sure they point to their correct starting and ending notes, etc.
  • Hairpins (i.e. crescendos and decrescendos) tend to extend more than they did in MuseScore. Dial them back so they look like nice!
  • For many things, the import defers to Finale's default formatting, which MSF remarked is wrong sometimes. Make sure 8vas, dynamics, and tempo markings (among other things) are aligned properly. Make MSF proud of you! ;D
If it wasn't abundantly clear: Double Check Everything! Use the MuseScore sheet as a reference to make sure nothing has gone rogue! It doesn't mean stuff is correct (MuseScore isn't perfect. I know. *shock* *shock*), but it's better than nothing!

Want some bad news? Here is a list of some things that are believed to be impossible using this method (you'll need to ask someone who has full Finale to do these for you):
  • Invisible dynamics, pedal markings, etc. Whilst indirectly supported by Finale Notepad (it cannot create them), MusicXML does not support them, so, in essence, there is no way to create them.
  • Adjusting beam heights. Whilst fully supported by MusicXML, and even exported by Finale and Finale Notepad, Finale Notepad seems to ignore this information upon import.
  • Aligning volta texts. Much to MSF's dismay and despite being supported by MusicXML, Finale Notepad just refuses to use the information. I have successfully modified it using a memory editor program like CheatEngine, but it's quite technical for most.
  • Turning off swung eighths. Not really supported prior to MusicXML 4.0 (which released June 2021 and doesn't matter because Finale Notepad doesn't support past v3.0), it is possible to turn swung eighth notes on using MusicXML (MusicXML Cleaner does this as of v1.2.0), but there is no known way to turn them off.
Except for those that are explicitly unsupported by MusicXML, it is hypothetically possible to do these in Finale Notepad. If you can come up with a method that eliminates any of these, do let us know!
[close]

For those that have full Finale and would like to test what may be impossible, here's something you can try...
  • Load a sheet in full Finale.
  • Export it to MusicXML.
  • Re-import it that MusicXML file. (Do it in Finale Notepad for bonus points!)
  • Take note of what changed. Stuff that broke may be impossible.
The reason why this test reveals anything at all is that it may show either an unsupported operation in MusicXML or parameters being ignored by Finale. Either way, these are both bad news for the whole method, IF they are true.
Note: this is test is necessary to fail in order to be impossible, but it is not sufficient to prove it. This means something can fail this test and yet still be possible. This will just serve as a first filter to weed out what is possible from what isn't.
[close]

Some Finale Notepad Tips
Finally, some Finale Notepad tips! (Again, not exhaustive and not really well-covering as I'm not super familiar with this kind of stuff.)
  • If you select an articulation, dynamic, or other such thing and hold Shift, you can make it so you can only move it in one axis (either up/down or left/right). This is especially helpful if a staccato decided to go to the other side of a stem.
  • If you select an object and hit Backspace, it will return to its default position. This is useful to do if something is just out of alignment and you want to check if the default is correct OR if you messed up and want a do-over.
  • Zoom in! You can see things better that way (especially if you're having to realign a rebel staccato).
  • Use the arrow keys for fine tuning! Also, take screenshots (Win + Shift + S or hit the print screen button on your keyboard) and opening it up in Paint or Paint.net can really help for perfect alignments.
  • Don't waste your time exporting MusicXML from Finale Notepad and importing back into MuseScore. You're just asking for headaches migraines. It's seriously much easier to just do everything from scratch. Don't believe me? Try it. Don't say I didn't warn you, though.

Whew! That's a lot, but I hope this guide was helpful.
Remember that the attached [slides] go into much more depth, so if you want more, go look there! If you seek any clarifications, do let me know!

That's all from me for now! Have fun using MuseScore and making great music! :D

14
Help Guides / Re: Formatting in MuseScore & Exporting to Finale
« on: July 22, 2021, 01:29:08 AM »
Exporting to MusicXML and MusicXML Cleaner

So, you've finally got your arrangement done in MuseScore and it looks like an official NinSheetMusic sheet thanks to the Style files and settings mentioned above. Hooray! Now, it's time to get it into Finale and let the real headaches commence!
To get your sheet from MuseScore to Finale, we're going to use an intermediary, standardized, XML derivative called MusicXML. MusicXML is designed for transferring sheets between programs and for historical preservation.

To export to MusicXML, go to File -> Export... -> MusicXML. Now, you can selected between Compressed, Uncompressed, and Outdated Uncompressed. We want to always use Uncompressed (.musicxml).
In a nutshell, Compressed (which ends with .mxl) is just wrapping our stuff in a ZIP file and makes it uneditable and not human readable, whereas Uncompressed (which ends with .musicxml for newer versions and .xml for older ones) is not in a ZIP file and is humanly readable and modifiable, which is what we want.

Now, that we've got our MusicXML file, everything should be hunky-dory, right?! Wrong.
Unfortunately, MuseScore isn't the greatest or most accurate when it comes to exporting to MusicXML.

If you were to dump this straight into Finale or Finale Notepad, you'd notice several things are wrong.
  • Mini-titles and page numbers for pages 2+ aren't there.
  • Exclusive to Finale Notepad, measure numbers have disappeared.
  • If you had a tempo marking with text, it looks like a mess.
  • The copyright information is now at the bottom of every page.
  • And maybe some more...
And then there are things that you likely won't notice, but are still wrong.
  • The title, subtitle, and copyright are likely not centered correctly.
  • The leftmost barline of systems 2+ doesn't align with the page's left margin.
  • And maybe some more...
All of these (and probably more I haven't discovered yet) are MuseScore's fault as it didn't export your sheet correctly. So how do we clean up the MusicXML file?

MusicXML Cleaner
A while back, the mighty Mudkip Trasdegi wrote a program that fixed a couple of these issues (read more here). However, as a sort-of "spiritual successor" to Trasdegi's program, I've written a more sophisticated program that should™ fix all of these issues and a few more!

It's called MusicXML Cleaner and is an easy-to-use, open source program!


Simply download it, run it, and then drag-and-drop (or use the large button that says "Open") your MusicXML export. A few seconds later, you'll be prompted to save (default is to override the old file, but you can create a new one, if you like) and these issues should™ be fixed!

A couple notes about the program:
  • It's not perfect. It's still a work-in-progress and so there are likely to be bugs. If you ever encounter any bugs, first of all, sorry! But secondly, please let me know by sending me the MusicXML file that caused it and I'll look into getting it patched! (Discord DMs preferred, but the forum messaging system works too.)
  • It's not a free pass to submission. In case you've lost count, there is one more major section after this which talks about common adjustments you can make in Finale. I'd wager that 99.999999% of the time, you will have to spend some time making some final adjustments in Finale. Do not just run your sheet through this program, import into Finale, and call it a day!
  • It's a tool, not a crutch. My program doesn't know or care about what your sheet looks like; it just fixes MuseScore's export bugs in an algorithmic way. This means that if your sheet is trash, the program will not make it perfect. The core idea behind this program is that you use the Style settings (which came pre-packaged in the provided files above) to get your sheet so that it basically looks like how it should -- my program just tries to remove a roadblock to keep that pristine formatting intact.
The instructions for use can be found at the GitHub link [here]. Please read them!

[Download] (download the .jar file, not the source code). Yes, it's not a virus. :P
You will need Java 8 or higher installed. You can install Java here.
Note: there is a MuseScore version number associated with this. If you use a different version of MuseScore, my code should™ work, but don't be so surprised if it doesn't!

As this is a labor-of-love and a work-in-progress, I am open to adding more features or quality-of-life improvements to the program. If you have any ideas, let me know via DM (Discord is preferred). I can't guarantee that I will be able to add them, but it can't hurt to ask!
(I mean, the code's also open source, so... y'know... you could just add whatever you wanted.... Just sayin'!)

15
Help Guides / Re: Formatting in MuseScore & Exporting to Finale
« on: July 22, 2021, 01:28:43 AM »
Useful Formatting Options in MuseScore

Breaks & Spacers
In Latios212 and MSF's amazing and useful guide on formatting (see here, if you haven't), they discussed things like number of measures per system, number of systems on a page, and spacing between staves.
All of these can be performed in MuseScore (and yes, they will export to Finale!).

Everything we need to perform these is in the Breaks & Spacers palette located (usually) on the left-hand side.

Of the 6 tools here, we only care about 5 of them. (If the pictures here are broken, simply hover over them in MuseScore to get what their names are.)
System break: Adding this to a measure will cause that measure to be the last in the system. This can also just be added by selecting the measure and hitting Enter/Return.
Page break: Similar to System break, adding this to a measure will cause that measure to be the last on the page. This can also just be added by selecting the measure and hitting Ctrl + Enter/Return.
Staff spacer fixed down: The spacer tool to rule them all. This tool will fill the space between two staves/systems and prime it to be modified. Add it to the staff that is above the distance you are trying to change/query.
This tool has several purposes.
  • In the Inspector, it will tell you the exact value of that particular distance. If you only wanted to know that information, you should delete it after you read the value.
  • It will fix that particular distance, so it won't change when MuseScore resizes distances to make systems fit on a page.
  • Selecting it and then grabbing the handle at the bottom (or changing the value in the Inspector) will allow you to add or remove distance between staves/systems.
  • If used on the last staff on a page, it will allow you to add distance between that staff and the bottom page margin.
Staff spacer up: This tool will add the space above a staff. This is particularly helpful if you need to add extra space between the first system on a page and the top page margin.
Staff spacer down: This tool will add the space below a staff. However, since the Staff spacer fixed down does everything this does and more, it has little unique use.

The one we didn't talk about is the Section break, which may have applications in compilation sheets, but otherwise, you aren't likely to use this.

You can refer to MuseScore's documentation about these breaks and spacers here.

Style -> Page
If you want to modify everything at once, then you can do this in Format -> Style -> Page.



I prefer the pre-v3.6 spacing they did (which is why you see Disable vertical justification of staves is selected), but you are free to use the advanced spacing options, if you like.
As a rule of thumb, you should just set these values to generic values (like they are in the style files I provided for you) and then tweak them on a staff-by-staff, system-by-system, or page-by-page basis using Breaks & Spacers.

If you want my explanation of these values...
Note: I'll just be speaking from my own experience -- you can choose to follow or ignore anything I say.
  • Music top margin: This is the minimum distance between the first system on a page and the top page margin. I use at least 9.0sp so as to try to avoid crowding the mini-title, but you can use larger values. I would avoid using smaller values without testing how it looks in Finale first.
  • Music bottom margin: This is the minimum distance between the last system on a page and the bottom page margin.
  • Staff distance: This is the minimum distance between two staves of different instruments. In other words, if you making a solo piano sheet, this value doesn't matter.
  • Grand staff distance: This is the minimum distance between two staves of the same instrument. This is the value you likely wanted to tweak and is the distance between the LH and RH staves for a piano part. A value of 8.0sp will give you 1" spacing in Finale, which is what Finale's default is (no, it's not actually 1 inch tall).
  • Min. system distance: This is the minimum distance between two systems MuseScore will use. If MuseScore is forced to use a value smaller than this, then it will send a system to the next page. You'll likely never adjust this value unless you want to really compact your sheet, which I'd advise against unless you know what you're doing.
  • Max. system distance: This is the maximum distance between two systems MuseScore will use. MuseScore will try to use this value, if it can. Otherwise, it will use the largest value less than this. You'll likely be tweaking this the most, trying to reasonably compact your sheet. I find the default of 15.0sp tends to make your sheet seem very spread out, so I use 12.0sp to start and adjust on a sheet-by-sheet basis.
  • Vertical frame top margin: This is the distance between the top of a vertical frame and the system above it. Since the only vertical frame we have is the one containing the Title, Subtitle, Composer, and Arranger, there isn't a system above it, so this value is meaningless to us.
  • Vertical frame bottom margin: This is the distance between the bottom of a vertical frame and the system below it. You can think of this as the distance between the Arranger information and the first system. I find 7.0sp works well enough, but I prefer to not crowd things, so I like using a larger value like 8.0sp and adjusting, as needed. You can also adjust this value on the frame itself under the "Bottom gap" field in the Inspector.
  • Last system fill threshold: This percentage represents the amount of the page's width (margins included) the last system has to take up before it is stretched to fill the page's width. You'll ultimately set this based on what you choose. If you want it to always fill the page, set it to 0%. If you want to never fill the page, set it to 100%.
[close]
You can refer to MuseScore's documentation on these settings here here.

Viewing Page Margins
MuseScore, by default, hides the page margins from you. While not exactly a formatting option, I still find it's often nice to see them so I know how much space I have to work, especially near the bottom of pages.
To show the margins, check the box under View -> Show Page Margins. You can uncheck this box to make them go away again.

Pages: [1] 2 3 4

Page created in 0.273 seconds with 22 queries.