Song Setup is the fourth section of the Beatmap Editor. It contains metadata and general beatmap configuration settings.
See also: [Guide] Metadata
An example of complete metadata (General tab) in Song Setup
These fields should be completed before creating a second difficulty. This is primarily to ensure that the metadata will be consistent across all difficulties in the beatmapset.
The band, singer, composer, or group that performed or created the song. Normally, this is automatically taken from the MP3 file's metadata, but double-check for proper spelling and punctuation.
Foreign/Eastern names should be presented in the same name order as used on Wikipedia (generally, given name followed by family name; the western order, for consistency).
This field should prefer to the spelling of the official release sources. The artist can sometimes be found on Wikipedia or other unofficial sources such as Anime News Network or MyAnimeList. As with any unofficial sources, provided content should be cross-checked against the official sources or if it provides a link to the official source, visit the official source instead. When in doubt, fill in all the information known now and make a verification request post.
The romanised name of the artist. This should be presented in the same name order as used on Wikipedia (generally, given name followed by family name; the western order, for consistency). This field will only become available if Unicode characters are used in the Artist field.
The song title. Normally, this is automatically taken from the MP3 file's metadata, but double-check to ensure proper spelling and punctuation.
The romanised name of the song. This field will only become available if Unicode characters are used in the Title field.
The beatmap creator's username. The game client should handle this automatically and will not allow you to edit this field, that is to say, if you are the creator.
The name of the beatmap, in other words, the difficulty's name. The dropdown contains the preset names of
Insane. The creator can select one of the preset names from the dropdown menu or type one in. While it is good to be creative, do try to make the difficulty names very clear as to which difficulty they represent. Ambiguous difficulty names will annoy players and are unrankable.
This field can also be used to indicate that it is a guest difficulty (e.g. "Larto's Hard").
The origin of the song. Generally, this field should be used only for anime or video game songs and occasionally for novelty (movies, TV, or internet) songs.
If the song is from an anime, a video game, or is famous for its use in a movie or TV program; then the title of that source should be added in this field. If otherwise, this field should be left empty.
Notice: This is not to be used for album titles, those belong in the Tags field.
Not every song needs something on the source field. The source is only for songs that are from something (e.g. a video game or an anime). Regular rock and pop songs can have this field be left empty. Other relevant information should be entered on the Tags field such as album title or subgenre information.
A list of keywords to help with search queries. Commonly, tags should include album names, guest creator usernames, company names, and other terms that may be used by users when searching for beatmaps. If the beatmap has collaboration elements (such as storyboarding) done by other users, their usernames should be added to this field.
Tags are separated with spaces. It is not necessary to use this field as other metadata from the other fields are used to help query beatmaps; however, it is greatly appreciated for users trying to find a specific beatmap.
Difficulty section. The right section is for osu!mania-specific beatmaps.
Notice: The game mode specific Ranking Criterias have rankable values that should be used.
The beatmap's difficulty settings; each setting affects different aspects of the beatmap.
Note: Holding down
Shift allows for a precise 0.1 value adjustment over the standard 1 value adjustment.
The common notation to represent a difficulty setting and its value is the setting's abbreviation followed by the setting's value. For example,
HP4.3 would be a beatmap with a Circle Size of 4 and HP Drain Rate of 4.3 respectively. In theory, negative difficulty settings may look like
AR-2 for an Approach Rate of -2.
HP Drain Rate, commonly abbreviated as HP, determines the rate of health recovery from good hit scores and health punishment from bad hit scores. The value ranges from 0 to 10; higher HP values will give lower health recovery with higher health punishment.
Note: More HP is recovered with Geki and Katu hit scores, which can be given from the last hit object in a combo.
Overview of various Circle Sizes
Note: This option is visible in osu!taiko, but it does not do anything that affects gameplay.
Circle Size, commonly abbreviated as CS, exists only in osu!standard and osu!catch. CS determines the size of hit objects or, more specifically in osu!catch, determines the size of the catcher and fruit. The values range from 2 to 7; higher CS values will make hit objects smaller. Using the highest value will make the hit objects as big as the cursor.
Most beatmaps use a value of 3 or 4, while a value of 5 or 6 is sometimes used and a value of 7 is almost never used. A value of 7 onwards is likely to be seen when using the Hard Rock mod.
It is possible to set the CS value to something less than 2 or greater than 7 by manually editing the OSU file, but this is be avoided as it is considered to be unrankable.
Key Count, also known as Keys, replaces the Circle Size metric for osu!mania-specific beatmaps. Key Count is self-explanatory; it defines the key count that is used. The values range from 1 to 9 keys.
Co-op mode checkbox will double the currently selected amount (from 5 onwards), leading to a total of 10K (5), 12K (6), 14K (7), 16K (8), and 18K (9).
Detailed AR chart
Note: This option is visible in osu!taiko and osu!mania, but it does not do anything that affects gameplay. This is mainly because both use a scroll speed, which is based on BPM (beats per minute).
Approach Rate, commonly abbreviated as AR, exists only in the osu!standard and osu!catch. The values range from 0 to 10; higher AR values will make the hit windows of hit objects shorter. AR indicates how long hit objects will stay on the screen, from the moment they appear until the time to tap/collect.
Higher Approach Rates mean that hit objects will be shown for a shorter period of time, thus giving less reaction time to plan ahead. Inversely, lower Approach Rates mean that hit objects will be shown on the screen for a longer time, allowing more time to react, but can result in an excessive amount of hit objects appearing on the screen at once if the AR is too low.
The duration of a hit object that stays visible on the screen (without mods) ranges from 1800ms at AR0 to 450ms at AR10.
There are four mods that alters the Approach Rate timing when activated:
While Half Time and Double Time does not change the actual given AR value, the speed difference leads to an apparent AR change, as low as AR-5 or as high as AR11. In the AR chart provided, those apparent values are given to allow easy comparison between approach speeds with and without mods. Actual AR, however, is always a number between 0 and 10. Note that AR levels scale by 120ms for below AR5 and 150ms for above AR5.
Detailed OD chart
Notice: On the beatmap page, Overall Difficulty is listed as Accuracy.
Overall Difficulty, commonly abbreviated as OD, defines how difficult it is to achieve high accuracy. The values range from 0 to 10; higher OD values will require more accuracy and precision. Since accuracy is important for gaining HP, Overall Difficulty indirectly influences how hard it is to pass the beatmap. Higher OD values mean shorter time windows to clear the hit objects, both in general and terms of getting the highest score value from the hit object.
In osu!standard, this also affects spinners, in which they must be spun more to fill up the gauge in time. In osu!taiko, the denden (osu!taiko spinner) will also need more hits to clear it.
Note: This does imply that raising the OD too high can make previously possible spinners near impossible to clear on time.
In osu!standard, the timing system will not allow a hit object to be tapped until the previous object is tapped (or missed after the hit window passes); resulting in a miss. With a low OD value, the hit window of one hit object may overlap with the next. Thus, a player could hit the second hit object with perfect timing after failing to hit the first hit object but this would result in completely missing both hit objects due to the hit window of the first hit object being active.
At OD0, a player can get a hit score of 300 at less than 79.5ms away from exactly hitting it on-time. On the other end of the scale, OD10 requires being less than 19.5ms away for the same hit score of 300.
There are four mods which alter Overall Difficulty timing when activated:
While Half Time and Double Time do not change the actual OD value, the speed's effect on hit windows will make the hit objects seem to have a lower or higher apparent OD, respectively. In the OD chart provided, apparent OD values are provided to allow comparison between timings with and without these mods. Note that these apparent OD values only apply to 300s on circles. Windows for 100s, 50s, and sliders (which use the 50 hit window) scale more harshly with Double Time than this apparent OD suggests and more leniently with Half Time. Again, outside of NoMod, HR, and EZ (on the left side); the OD values provided are only for comparison: the actual OD value is always a number from 0 to 10.
The Audio section. The right is shown if the beatmap contains custom timing on volume settings.
Configuration for hit sounds. Using this will apply globally over the entire beatmap; however, using the timing sections (
F6), the creator can change both hit sound sets or volume individually through timing points.
Sample Set Selection and the
Sample Set Volume will be inaccessible if there are any timing-sensitive volume adjustments used in the beatmap. Clicking on the
Reset Settings button will remove all the custom timing volume adjustments.
Select to use the
Drum built-in sample sets globally. It is possible to enable custom overrides to use hit sound files inside the beatmap's folder first for custom hit sounds.
Set the volume of the sample set globally.
Clicking on those buttons to test out how the sample set sounds. Four buttons are provided, namely:
Clap. These sounds are additive;
Whistle is a combination of
Samples match playback rate (for fully-hitsounded maps) checkbox will adjust the hit sounds' pitch accordingly to match the speed modifiers (both in the editor and in-game). Unchecking this will allow the hit sounds to play at its own preset pitch.
Configure the combo colours and playfield's background colour.
Configure the custom combo colour set. Combo colouring is an important aspect to a beatmap's aesthetic value.
Clicking a combo colour or clicking on
New Combo Colour opens up the operating system's colour picker (as shown in the image; Windows' colour picker). Choose colours that compliment the background, not camouflage into the background.
At most, eight combo colours can be selected, although most beatmaps commonly use four.
Enable Custom Colours checkbox must be checked to enable the custom combo colour set above. Unchecking it will return to either the default combo colour settings or the player's skin combo colour settings. It is generally recommended to keep it checked so the beatmap can have its own unique identity in terms of combo colours. It can be safely unchecked for osu!taiko-specific and osu!mania-specific beatmaps.
Remove Combo Colour will remove the last defined combo colour.
Click on the
Background Colour to change the blank playfield's background colour.
A debatable setting to change except for storyboards that may expose the blank playfield's background.
Enable countdown checkbox to enable the countdown animation cheer before the beatmap starts.
When enabled, the countdown animation can be refined using the
Countdown Speed radio buttons (
Double) and the
Countdown Offset (default is 0; higher value means earlier countdown).
Widescreen Support: Remove sidebars/pillarboxes from the left and right side of the playfield if the client is using any aspect ratio greater than
4:3. This is typically enabled when using storyboard elements but can be disabled.
Display storyboard in front of combo fire: An obsolete setting, this can be ignored.
Display epilepsy warning (storyboard has quick strobing): Display an epilepsy warning for (quick or any) flashing storyboards in the beatmap.
Letterbox during breaks: Determine if the beatmap should (or should not) put letterboxes during breaks in the beatmap. This is usually enabled by default, but using this option in for osu!mania-specific beatmaps is not allowed.
Preferred Skin dropdown is used to set the preferred skin for the beatmap. Using this option assumes that the player has the skin you want them to use. However, if the player does not have the skin, a notification will appear for the player, stating that the requested skin is missing, but the player's current skin will be used instead. By default,
User's preference (No Change) is used.
You can, however, include the skin elements inside the beatmap folder. As most creators will just do this instead, this option is rarely used unless it would decrease the file size or is part of a beatmap project, where the skin may be provided on the project page itself.
Stacking hit objects while editing
Stacked hit objects while playing
In osu!standard, hit objects will automatically stack if they are both placed in the same spot while being close in-time. This is to help players see hit objects that overlap each other.
Moving the slider towards the right will space out the "closeness" of hit objects in-time before stacking will occur. Rules dictate that if
Stack Leniency is set so that stacking no longer occurs, the creator must manually offset the hit objects. This option is best left as is to its default value of
Notice: Stacked hit circles in osu!standard will move towards the point where the stacking occurs.
Objects are considered to belong to same stack if they are at the same coordinate and no further in-time than
[(Approach Window) * (Stack Leniency) / 10], where
Approach Window is the duration for which objects stay on screen (see Approach Rate above).
Allowed Modes is a dropdown to confirm that the beatmap can only be played by the specified mode. Default setting is
All, which means the creator will create an osu!standard beatmap that can be converted into the other game modes. This can be changed to be osu!taiko-specific, osu!catch-specific, or osu!mania-specific; but keep in mind that the change will remove every hit object in the beatmap.
Note: Decide at the time of creation and confirm the beatmap's playable mode(s) first before adding in any hit objects to prevent wasted effort.
Note: osu!mania has its own beatmap editor that is different from the typical beatmap editor.
Use special style(N+1 style) for mania checkbox does not do anything, considering the player can set a personal preference specifically in the Options using the
osu!mania layout button.
Designtab was formerly called "Storyboarding".
Difficultytab, there used to be
Approximate Difficulty Ratingwhich is a summary of all of the settings chosen on this page. More stars would imply a harder beatmap. This was, however, not the final star ranking of the beatmap as it was just an approximation based on the current difficulty settings. This was replaced for a label that explained that holding
Shiftwould allow for fine-tuning the values by an increment of 0.1.