NinSheetMusic Forums

Please login or register.

Login with username, password and session length
Advanced search  

News:

NinSheetMusic is the LARGEST video game sheet music archive on the entire internet worldwide!

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 5
16
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

17
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'!)

18
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.

19
Help Guides / Re: Formatting in MuseScore & Exporting to Finale
« on: July 22, 2021, 01:28:11 AM »
Applying a Style to a Sheet

Now, we need to format either our newly-created sheet or a pre-existing sheet so it looks like an NinSheetMusic sheet. We do this using a Style.
A Style is a template containing lots of formatting options, such as margins, font sizes, and positioning data.

To save some time and effort, I've gone ahead and made some basic style files that you can use. I go through the details of making such a style in the attached slides located above.
While there are two files here, the only notable differences between them are the staff spacing and font sizes. If you don't know which to choose, choose the 1.625mm one.
NOTE: These are neither perfect nor endorsed, they are just a good starting point.
  • [Style 1 (1.625mm)] - Has 1.625mm staff spacing, which is very close to what the NinSheetMusic Template uses. This style will generate more compact sheets.
  • [Style 2 (1.75mm)] - Has 1.75mm staff spacing, which is very close to what MuseScore defaults to. This style will generate less compact sheets.
Once you have your style, you can load in into the sheet by going to Format -> Load Style... and selecting the style file you wish to load.
Now, MuseScore will automatically format most things in the new style and your sheet should start to look more like an official NinSheetMusic sheet!
There are a few things we might need to adjust now that the style is loaded.

What if I want to adjust the margins or staff spacing?
Ordinarily, it'd be quite simple, however, due to a MusicXML oversight in MuseScore v3.6.2, it's not.

I'll talk about the margins first and staff spacing second.

The settings are located in Format -> Page Settings... and the checkbox Two sided should be unticked. Unticking this means we have one set of margins for every page, which is what we want! Unfortunately, once exported to MusicXML, the margins will be separated between even and odd numbered pages, which is a problem if your left and right margins aren't equal because MuseScore is built so the left margin on odd-numbered pages is always the same as the right margin on even-numbered pages, which is not what we want.
If we just tweak the values here, when we import into Finale, we'll find a small left-margin and a fat right-margin on even-numbered pages and it doesn't look good.

How to overcome this? First, experiment with what values you want in the Page Settings menu, but don't set them here! Now, save the style you currently have by going to Format -> Save Style... and save it somewhere and remember where you saved it! Next, open that file you just created in a text editor like Windows Notepad, Notepad++, Sublime Text, VS Code, etc. It's okay, it's just an XML file, which any text editor can read.

When you open it, it'll look like this:


Fortunately, what we're interested in is right at the top.
The values we want to adjust are right at the top of the file. I'll now explain them.
  • pageEvenLeftMargin (line 7, in the image) - this is the page's RIGHT margin's value in inches. If you want to adjust the page's RIGHT margin, change the number between the tags.
  • pageOddLeftMargin (line 8, in the image) - this is the page's LEFT margin's value in inches. If you want to adjust the page's LEFT margin, change the number between the tags.
  • pageEvenTopMargin (line 9, in the image) - since our sheet is not two-sided, we can ignore this value.
  • pageEvenBottomMargin (line 10, in the image) - since our sheet is not two-sided, we can ignore this value.
  • pageOddTopMargin (line 11, in the image) - this is the page's TOP margin's value in inches. If you want to adjust the page's TOP margin, change the number between the tags.
  • pageOddBottomMargin (line 12, in the image) - this is the page's BOTTOM margin's value in inches. If you want to adjust the page's BOTTOM margin, change the number between the tags.
If the values you want are in millimeters, you'll need to convert them to inches and then enter them. Ask the omniscient Google if you need to!

For example, suppose I want to change the right margin to 0.5 inches. Then, what I'll do is go to line 7 (where it says pageEvenLeftMargin) and replace the 0.590551 with 0.5 and then save the file.
As another example, suppose I want to change the top margin to 14 millimeters. First, I'll Google what 14 millimeters in inches is (0.551181 inches) and then, what I'll do is go to line 11 (where it says pageOddTopMargin) and replace the 0.5 with 0.551181 and then save the file.

After you've made your adjustments, make sure you save the file and then go back to MuseScore and reload the style by going to Format -> Load Style... and selecting the file you just modified. That's it! Yes, it's tedious. Yes, it's hacky. Yes, it's annoying, but until that bug is fixed, it's the best way unless you want to modify the MusicXML file every time you export.

So, in summary, here's the method:
  • Experiment with the margin values in MuseScore, but don't save them.
  • Save your style by going to Format -> Save Style... and remember where you saved it.
  • Open that file you just saved using a text editor like Windows Notepad.
  • Convert your desired value to inches by asking the almighty Google, if necessary.
  • Replace the number next to tag corresponding to the margin(s) you wish to tweak with what you want.
  • Save the file.
  • Reload the style by going to Format -> Load Style... and selecting the modified value.
  • Done.

Oh yeah, if you want to modify the staff spacing, that value is in the same file, right at the very bottom.


It's the value called Spatium (line 1269 in the image) and its value is in millimeters, not inches. Basically the same approach as before applies.
  • Experiment with the values in MuseScore, but don't save them.
  • Save your style by going to Format -> Save Style... and remember where you saved it.
  • Open that file you just saved using a text editor like Windows Notepad.
  • Convert your desired value to millimeters by asking the almighty Google, if necessary.
  • Replace the number next to <Spatium> with what you want.
  • Save the file.
  • Reload the style by going to Format -> Load Style... and selecting the modified value.
  • Done.
[close]

Asserting the Score Metadata
Underneath MuseScore's hood, there is a place where information about the score is stored.
This information will be passed on through MusicXML to Finale, so it's important it be correct. This is especially relevant if you use a template file as this information is likely from the sheet you copied from and is likely now wrong.

To access this information, go to File -> Score Properties... and you'll be greeted by a dialog box of information.

Note: Depending on what version of MuseScore your sheet is from, you may have extra fields that aren't shown here.

Some of these fields are essential and matter a lot, but most of these fields really don't have an impact in MuseScore, MusicXML Cleaner, or Finale. Nevertheless, it's still a good practice to do.
  • arranger: Put the "Arranged by ____" text here. If you used the lyricist field to store this information on creation, you should cut and paste it from there. Not critically important.
  • composer: Put the "Composed by ____" text here. Not critically important.
  • copyright: Put the two-line copyright info we did earlier here. The same copy-and-paste trick we did earlier to get a multiline copyright works here too. This is very important as MuseScore will export this information straight from here and MusicXML Cleaner reads this information when removing duplicate information that MuseScore creates.
  • lyricist: Unless your song has lyrics, this should be empty. Not critically important.
  • movementNumber & movementTitle: Finale uses these fields as its defacto way to store a score's title. However, we use the workTitle field instead and so these should be blank.
  • workTitle: Should be the title of your piece, with the quotes included. This is very important as MusicXML Cleaner uses this information to create the mini-titles on pages 2+.
Anything not listed here is (likely) not important.

Adding Composer and Arranger Info
If you're using a pre-existing sheet, you might not have used the "put the arranger information in the lyricist box" that we did earlier and now your composer and arranger information is messed up.
Fret not! you can simply go to Add -> Text -> Lyricist or Add -> Text -> Composer and then enter the information and it should be properly formatted! You can then delete the old ones if they are not good.
And yeah, you would think it would just insert the values from the Score Properties window, but nope!

Adjusting the Header Frame's Height
Firstly, if your composer information needs to be on multiple lines, do it now! Just double click it and edit it like you would normally.

Now, you might notice that the composer and arranger information are a bit too close to the title and subtitle.
For whatever reason, the height of the frame that holds the title, subtitle, and such isn't saved in the Style file, so we have to manually adjust it for each score individually. A pain, for sure.


First, select the frame (you can do this by clicking anywhere empty in that dashed rectangle. If you want to see the dashed rectangle, but can't, check the box in View -> Show Frames).
Now, we can change this height in two ways:
  • Notice how there is a square at the bottom middle of the frame. That's the frame's handle. You can click and drag it to change the height of the frame. You can also just click the handle and then use the up and down arrow keys to adjust it (hold Ctrl to make it go faster).
  • In the Inspector window (if you can't see this, go to View -> Inspector or press F8), you can change the value under Height.
You should make it as tall so as to provide ample space... and then some. I find that, upon import, the height is shrunk a bit, so if they're close together in MuseScore, they'll be closer together in Finale.
In general, I find that you should go no smaller than 15.00sp for single-line composers and 17.00sp for two-line composers, but you should probably add 1 or 2 sp. to that.

Removing "Pno." from Systems 2+
The Style sheets untick a box that causes "Piano" to appear on the first system and "Pno." on every subsequent system. For a solo sheet, we want to get rid of the "Pno."
  • Right click on the instrument name (can be either "Piano" or "Pno.")
  • Select Staff/Part Properties...
  • In the window that appears, delete everything in the Short instrument name box (where you should see "Pno.")
  • Click Okay to save and commit the changes.
That's it! You can now begin arranging as you normally would. Add notes how you like, add accidentals & slurs how you like, etc. However, you'll want to be aware of some formatting options to make your sheet the best it can be!

20
Help Guides / Re: Formatting in MuseScore & Exporting to Finale
« on: July 22, 2021, 01:27:18 AM »
Creating a New Sheet

Here, I'm going to show you how I create a new sheet so that all the relevant information is all in one place. You don't have to do it this way, but I am! :P

Create a new sheet like you normally would (be it click the icon, Ctrl + N, or File -> New...).


  • Title: Put the title of your piece here. Make sure to include the quotation marks (")!
  • Subtitle: Put the name of the game here. Make sure to include accents if the game has them (e.g. Pokémon).
  • Composer: Put the words "Composed by" and then the name(s) of the composers. Don't worry about spacing them onto multiple lines yet.
  • Lyricist: Here, we're going to cheat - we're going to the put the arranger info here. Start by writing "Arranged by" and then your name. We can do this because MuseScore knows about as much as what an "arranger" is as it does a "lyricist". In other words, it just puts text on the page, which is all we need.
  • Copyright: Here, we need to do something different. We need a two line copyright, but we have only one line.
    • Open a text editor (like Windows Notepad, Notepad++, Sublime Text, VS Code, etc.) and type your copyright on two lines, exactly how you'd want it, like so:


      Then, highlight the text you just typed, copy it (Ctrl+C), and then paste it in the MuseScore wizard. It will look like one line, but it's actually two!
      (Note: You can insert the copyright symbol © by either copying and pasting it from somewhere (like here or Google) or, on Windows, hold down the Alt key and type 0169, then release the Alt key.)
Everything after this is just standard. Pick your instruments (I'm going to assume solo piano), key signature, time signature, and tempo. Et voilà! A brand new sheet! :)

21
Help Guides / Formatting in MuseScore & Exporting to Finale
« on: July 22, 2021, 01:27:04 AM »
Overview

This is a guide on one particular method of how to format a MuseScore sheet so as to try to minimize the amount of work required in Finale or Finale Notepad.
Why? Because MuseScore is awesome and Finale Notepad is not! So, let's try to maximize the amount of stuff we can do in the superior program and leave only necessary fixes to the inferior one. 8)

This guide will cover the following things:
  • A method of creating a new sheet to get all the information on the sheet
  • Applying a Style file to a new or pre-existing sheet
  • Useful formatting options in MuseScore
  • Exporting to MusicXML and post-export cleaning via MusicXML Cleaner
  • Importing into Finale/Finale Notepad, common final adjustments, and tips
For this guide, I will be using MuseScore v3.6.2 and Finale Notepad.
Different versions of MuseScore may have more or fewer issues than listed here. I'm also going to assume to know how to use MuseScore well enough (like how to add notes, articulations, slurs, etc.).
As for Finale, full Finale has tools to fix every and any issues, but Finale Notepad does not so I will be taking the lesser of the two here and cater the guide around Finale Notepad.

I am also going to avoid going to into gory details here. I go into more depth in the slides that I used for the presentation that motivated this guide. You can find the slides [here]. You should check them out!

22
Project Archive / cacabish's Colors Sheet
« on: July 20, 2021, 08:19:58 PM »
Here is first (and probably definitely only) sheet for the Colors project from the wonderful game, Bug Fables! :D
I'll try to keep the attached PDF file up-to-date with the .musx revisions, so that people can just look at that.


"Blessed Golden Lands"*
[PC] Bug Fables: The Everlasting Sapling
[MUSX] [PDF]


*The actual title of this piece is unclear. According to the composer's bandcamp, the title is just "Golden Lands", whereas according to the character you talk to in the game to set the music, it's called "Blessed Golden Lands".
I've chosen to use the latter on the logic that anyone playing the game and seeing the song title's there would be motivated to search for that and not just "Golden Lands". If you believe it should be the other title, do let me know!


23
Neato! I like the more-spaced-out version! I was afraid it was going to look too stretched out, but it really doesn't -- it looks nice!
Anyway, I've modified it so it tries to use up the bottom space a bit more. I've added some extra space between the composer info and the title info, the top system and the arranger info, and more space between the systems.

Personally, I think the new version is pretty good, however, do let me know if I've accidentally taken it too far or if you have some more suggestions. I'd be down to hear them and make them!  :)

24
More space it is then!  8)

I've added some more space between systems. I'm not exactly sure how much to add, so I added a modest amount and tried to keep the appearance balanced.
If there is a specific place you feel needs more or less space, do let me of the specific place as another round of just "hmmm, needs more space" is likely to be equivalent to me as "hmmm, needs more cowbell". :P

25
- Alright, I've changed the A's to Bn's in m. 9 and added the courtesy accidental.
- While the tied triplet sounds a little weird to me (possibly because I've heard it the other way before so much I prefer it that way), I can understand the change and so I've made it.
- Finally, after a headache pleasant experience with Finale trying to sort out the repeats, I've added a repeat section for the last two systems (now made into one system) and added some additional system spacing, now that there is more space to work with. I didn't do this originally because it looked a little off to me, but then again, I haven't encountered anything with this many adjacent repeated sections outside of something like "The 12 Days of Christmas" and was unsure if it was too clutter-y. Nevertheless, I have made this revision.

With that, all files are updated to reflect these changes. Do let me know of any additional changes I need to make. :)

26
Interesting... Are the other boards/tracks similar in that way?
Yes, actually! All the boards from Mario Party 1 have the character's name removed from the track theme. I'm not sure why, but they are.

Source
Fun fact: this is also true for all boards of Mario Party 4, except for one: Boo's Haunted Bash, which I did a sheet for last October (which confused me back then and I had to go play that board to actually be sure that was the song's title).

I agree the dynamic for m9-16 is softer than for the m1-8, so I've rectified this. Let me know if it's sufficient.
Also, I've added pedal markings, but I've never added pedal markings in Finale v26 before, so let me know if I'm messed something up (especially alignment-wise). :P

27
While this song plays on the board called "Bowser's Magma Mountain", the actual title of the song is just "Magma Mountain", according to the in-game jukebox.


28
Thanks for the feedback, Zeila! I really appreciate it. :)
  • The double repeat idea to reduce the sheet to one page is a good idea! I think I'll do this as I think it'll still look nice and be more fitting for a short song like this.
  • As for adding more based on the timpanis, I'll spend some time listening to them and see how they sound and try to work them in. Thanks for the tip!
  • For m13, I still hear an A and not a Bn, but I could easily be mistaken (wouldn't be the first time :P); I'll take a few more listens to try to ascertain it. Aside from that, the Bn would add some parallel structure in the RH, with the RH in m13-14 becoming the same as m15-16. Something more for me to consider, I guess.
  • I'll probably forego adding the pickup measure for now because of the D.C. and trying to compress this onto one page.
Thanks again!

29
After a few months off due to school and learning more about formatting & MuseScore, I've got a new sheet from shock, shock a Mario Party game!
While this music plays on the board named "Bowser's Magma Mountain", the song is actually just called "Magma Mountain" according to the in-game jukebox.

Mario Party - "Magma Mountain"
[PDF][MIDI][MUS][MUSX]


30
Site News / Re: NinSheetMusic's 17th Birthday!
« on: April 11, 2021, 06:11:23 PM »
Happy Birthday NinSheetMusic! ;D

I remember when I found this site several years ago, I knew I had discovered something amazing, but since then, it's become even more amazing to me!

My thanks to everyone, past and present, who has made this community into the wonderful place it is. Here's to many more amazing years!

Pages: 1 [2] 3 4 5

Page created in 0.165 seconds with 22 queries.