You're welcome
I'm reading these informations to make bms sometimes. It's very useful and helpful. Thanks for cheers!
There are very few contributions which I who am neither an engineer nor a programmer can do. I am glad if my documents are useful for someone related to BMS.
BGMレーンソーター (BGM Lane Sorter)
- About:
This tool changes into BGM all the visible notes (
#xxx[11-29]
) that BMS has.Furthermore, all BGM notes (
#xxx01
) align at numerical order (from#WAV01
to#WAVZZ
).Thereby, noters may be able to finish quickly the preparation which creates an appendix chart.
- Usage:
Drop BMS
/BME /BML /PMS file to this executable file. (Or, (1) Run this executable file, (2) Specify pathname of targeted BMS
/BME /BML /PMS.) (Or, (1) Run this, (2) Drop BMS
/BME /BML /PMS file to a console window, (3) Press Enter.) Then, a
targeted-filename_bgm.bmx
file is generated in the same directory as a targeted file.BGM channels of this
*.bmx
file have already aligned. We can copy this*_bgm.bmx
file and can change a filename extension into*.bms
/ bme
/ bml
/ pms
.- Tips:
Early BMS may be minifying BGM lines, in order to reduce filesize. For example, L9 (site search keyword: “Download(WAV)”). Noters who try to make the appendix chart of this BMS will be troubled by the excessive disorder of BGM area. BGMSorter can be used in order to solve this.
Drop “ 9_5.bms
” from L9Executable file: Console says: BGMs per measure: bgm
lane sorter .exe WAV定義数:253 1小節あたりの最大WAV定義数:48
Maximum: 48 lines bgm
lane sorter 999 .exe WAV定義数:253 1小節あたりの最大WAV定義数:253
Always: 253 lines - WAV定義数:
- The number of
#WAV
s which BMS uses. - 1小節あたりの最大WAV定義数:
In short, the number of BGM lanes which
*_bgm.bmx
requires from BMS chart editors.If this value is
29
or more, BMSC should not open*_bgm.bmx
file.If this value is
33
or more, BMSE should not open*_bgm.bmx
file.When iBMSC opens
*_bgm.bmx
file, it is recommended that noters set “Number of B Columns” more than this value. (See: Sidebar - Grid column - Downwards arrow symbol under “Disable vertical moves”)
- BMS Creator:
- When one of the musical measures has 29 or more kinds of
#WAV
s, BGM lanes may overflow from the BGM area of BMSC. BMSC reduces the number of BGM lanes per measure from 29 (or more) to 28, when opening a BMS/BME file. Overflowing notes are destructed. - BMx Sequence Editor:
- When one of the musical measures has 33 or more kinds of
#WAV
s, BGM lanes may overflow from the BGM area of BMSE. BMSE reduces the number of BGM lanes per measure from 33 (or more) to 32, when opening a BMS/BME /BML /PMS file. Overflowing notes are destructed. - GDA Creator Professional:
- When one of the measures has many BGM line rather than the BGM lanes number which lane-script (
*.gsc
) permits, GDAC2 is forced to terminate. - iBMS BMS Creator:
iBMSC can extend the number of BGM lanes to a maximum of 999.
iBMSC does not delete overflowing BGMs. (In other words, iBMSC avoids over optimization.)
Therefore, we should use iBMSC. Being used with iBMSC is safest for BGMSorter.
- These are not sorted:
- Invisible notes (
#xxx[31-49]
) - LONGNOTEs (
#xxx[51-69]
) - Landmines
/Bombs ( #xxx[D1-E9]
) - BGMSorter does not allow visible notes without KEY-sound:
- Visible notes which refer to undefined
#WAV
are deleted when sorting. Noters to use undefined notes (E.g.#LNOBJ
etc.) must assign the dummy contents explicitly. (E.g. “#LNOBJ FF
” + “#WAVFF fictitious-LNOBJ.wav
”) - BGMSorter does not allow notes of the same
#WAV
index to overlap simultaneously: -
Before Sorting BMS-A BMS-D #WAV01 v_f.wav #WAV02 v_o.wav #WAV03 v_o.wav #WAV04 v_n.wav #WAV05 v_f.wav #WAV06 v_o.wav #WAV07 v_o.wav #WAV08 v_n.wav #00101:01020304 #00112:00060700 #00114:05 #00115:00000008
#WAV01 v_f.wav #WAV02 v_o.wav #WAV03 v_o.wav #WAV04 v_n.wav #00101:01020304 #00112:00020300 #00114:01 #00115:00000004
After Sorting BMS-A BMS-D #WAV01 v_f.wav #WAV02 v_o.wav #WAV03 v_o.wav #WAV04 v_n.wav #WAV05 v_f.wav #WAV06 v_o.wav #WAV07 v_o.wav #WAV08 v_n.wav #00101:01000000 #00101:00020000 #00101:00000300 #00101:00000004 #00101:05000000 #00101:00060000 #00101:00000700 #00101:00000008
#WAV01 v_f.wav #WAV02 v_o.wav #WAV03 v_o.wav #WAV04 v_n.wav #00101:01000000 #00101:00020000 #00101:00000300 #00101:00000004
In BMS-A, visible notes have performance effectiveness (volume++, or pseudo-flange).
In BMS-D, visible notes do not have performance effectiveness.
uBMplay cannot detect “sound which sounds even if it does not perform” like BMS-D. When F1 key is pressed and uBMplay is made “BGM ONLY”, not only KEY but “BGM which overlaps to KEY” is muted.
The test method of daring to miss all the playable-notes is known. However, it is too inefficient that noters test BMS by their own ear. The check by man is not expectable in quality.
Noters can even do using BGMSorter, in order to debug BMS
/BME /BML /PMS certainly. If this tool is used carefully, the quality of appendix charts will improve.