(Since my English is buggy, I will express by an ordered list.)
- “Run” button is pushed now.
- “Clear unused definition from a list” will be running if this item was checked.
- “Delete unused files in this BMS folder” will be running if this item was checked (on the basis of the result of Procedure 1)
- “Sort definition list” will be running if this item was checked (on the basis of the result of Procedure 1-2)
- “Change filename to list number [01-ZZ]” will be running if this item was checked (on the basis of the result to Procedure 1-3)
#WAV / #BMP / #BGA)
- The list item which was not placed as a note is deleted from a definition list. e.g.:
before after remarks #wav11 a.wav #wav22 b.wav #wav33 c.wav #wav44 d.wav #wav55 e.wav #00111:113355#wav11 a.wav #wav33 c.wav #wav55 e.wav #00111:113355- This function prevents unnecessary files from being loaded by BMS reproduction softwares.
- That is, this has effects which shortens load time and reduces Memories usage.
- A part of software warns of a musical score with “the list items which are not used”.
Users will not be made uneasy if noters apply this processing. - More items could be defined when some definition slots become empty.
- This process does not delete actual files. Only definition list-items are deleted.
- This process can undo. Therefore, this processing may be used in order to detect “a definition which forgot for noter to place as a note”.
- The “Expand” tab of BMSE is isolated from all operations of BMSE. Therefore, the following problems may arise.
before after remarks #wav11 a.wav #wav22 b.wav #wav33 c.wav #wav44 d.wav #wav55 e.wav #00111:113355 #random 2 #if 1 #00113:22 #endif #if 2 #00115:44 #endif #endrandom#wav11 a.wav #wav33 c.wav #wav55 e.wav #00111:113355 #random 2 #if 1 #00113:22 #endif #if 2 #00115:44 #endif #endrandom- Description of
#wav22/44exists only in the “Expand” tab. - Therefore, when this processing is applied, these definition list items are deleted.
- As a result,
#wav22/44in a#RANDOMsection appear as an empty note. - Therefore, when Noter adds description to the “Expand” tab, Noter must finish all other work. (at least in BMSE)
- By the way, the phenomenon similar to this occurs also in “Move Up/Down” of definition list items.
- Description of
- This processing searches “the file which is not registered into the definition list at point in time of running this processing” out of the folder in which BMS in which BMSE is open now exists. And all the files corresponding to that condition are deleted.
A.bms’s definition list before after remarks #wav01 a.wav #wav02 b.wavA.bms a.wav b.wav c.wav d.wav e.wav
A.bms a.wav b.wav
- This processing makes it possible to constitute a BMS folder only by necessary minimum files.
- The sizes of archives can be reduced when distributing BMS works.
- It is very important that archives do not become a burden of servers, HDDs, etc.
- When running this processing, the dialog box for a confirming is displayed just before deletion.
- When the file which should be deleted is the singular number, that filename can be checked in advance.
- However, when the file which should be deleted is plurality, those filenames cannot be checked in advance.
Only when deletion is canceled in BMSE, those filenames can be checked. (I think that this is a problem which new editors should solve ... ) - By the way, the list text of this filenames can be copied to a clipboard. (Focus and Ctrl+C)
However, those all could not be copied when the file of the quantity which cannot be displayed on this dialog is displayed.
- The “Expand” tab of BMSE is isolated from all operations of BMSE. Therefore, the following problems may arise.
A.bms before after remarks #wav01 a.wav #wav02 b.wav #banner 300x80.pngA.bms a.wav b.wav 300x80.png
A.bms a.wav b.wav
- Description of
#bannerexists only in the “Expand” tab. - Therefore, BMSE will delete 300x80.png.
- I already mentioned above one of the ways noters cope with it to this problem.
- Description of
- Another problem is that this processing is based on “the musical score file in which BMSE is open now”.
A.bms B.bms C.bms before after remarks #wav01 a.wav #wav02 b.wav#wav01 c.wav #wav02 d.wav#wav01 e.wav #wav02 f.wavA.bms B.bms C.bms a.wav b.wav c.wav d.wav e.wav f.wav
A.bms B.bms C.bms a.wav b.wav
- When this processing is performed on A.bms, other musical score files receive a critical damage.
- When the contents of the definition list differ according to a musical score, users need to devise.
- This image is one of the ways users solve this problem.
- First, the folders of the same quantity as musical score files are copied.
- Next, one kind of musical score is assigned to one folder.
- Next, “Delete unused files in this BMS folder” is performed on each musical score in each folder.
- Finally, all the folders are merged. Only required files remain by this.
- However, this work is troublesome.
- BMSCleaner can detect two or more musical score files simultaneously.
If BMSCleaner is used, a troublesome procedure like this image will be unnecessary. - However, if my memory is clear, BMSCleaner has some bugs.
- When “Clear unused definition from a list” and “Delete unused files in this BMS folder” are checked simultaneously,
- Unused definition is deleted first.
- Next, unused files are deleted on the basis of that result (↑).
- The filename extensions (range of search) of the file to delete are specified. A delimiter is a comma.
- It can be used in order to clean garbage (e.g. score file for specific software generated at the time of a test play) not to include to an archive at the time of distribution.
- Users can specify these filename extension filters freely. But, BMSE does not save that customization.
- If this processing can clean “Thumbs.db”, “desktop.ini”, etc., it is very useful, but it is impossible in BMSE.
(The archive with which these unnecessary files are included will make users unpleasant. )
- The option which performs literal action control.
- But, if “Do not move files to the Recycle Bin. Remove files immediately when deleted” is effective with the property of Recycle Bin, this option of BMSE is invalid.
- The unused index of a definition list is reduced.
before after remarks #wav11 a.wav #wav33 #wav55 a.wav #00115:00113355#wav01 a.wav #wav02 #wav03 a.wav #00115:00010203- If the note was placed on the main panel, a definition item will be sorted regardless of the contents.
- It may be one of following: multiplex definition / empty definition / definition of a relative path / definition of a fictitious filename extension / definition without a filename extension
- BMSE also replaces correctly the
#BMPindex currently referred to from#BGA.
- Although I can understand
#BMP, I cannot understand most#BGA. - However, the
#BGAlist of BMSE seems to completely be sorted correctly. - I respect Hayana which completed this action without room for a bug to enter.
- Or can all programmers realize such an uncanny thing? If so, programmers are God in my view.
- The “Expand” tab of BMSE is isolated from all operations of BMSE. Therefore, the following problems may arise.
The sound which noter meant does not sound any longer.before after #wav04 a.wav #wav05 b.wav #wav06 c.wav #wav07 d.wav #wav08 e.wav #random 2 #if 1 #00111:0506 #endif #if 2 #00113:0708 #endif #endrandom#wav01 a.wav #wav02 b.wav #wav03 c.wav #wav04 d.wav #wav05 e.wav #random 2 #if 1 #00111:0506 #endif #if 2 #00113:0708 #endif #endrandom
- Although I can understand
- If the number of use definitions falls in less than 255 slots, BMSE will sort by the hexadecimal number index of [01-FF].
- When this processing is successful, option “Use Old Format [01-FF]” becomes effective automatically.
- When 256 or more slots of either of list of
#WAV/#BMP/#BGAare required, even if it is checking this, conversion to [01-FF] is not performed. - In the case of the musical score which defined 1 file as 256-fold, and the musical score which placed 256 kinds of empty objects, conversion to [01-FF] is not performed.
- Checking this is recommended in order to maintain compatibility with the oldest possible software.
(Although it is in the situation about which it is not necessary to care these days. ) - If this processing is successful when there is a list-cursor after
#xxx74(Base36), BMSE will do forced termination.
In this case, backup file of a musical score is not generated.
- A list is sorted in order of a filename. Noters become easy to grasp the contents of the definition list by this.
- Moreover, noters become easy to obtain the benefit of add-ons, such as BmWh.
- The result of this processing does not necessarily agree with the order of a row of the order sorting of a name by Explorer etc.
before after remarks 
- In BMSE, the text of a definition item is only sorted by code point value.
- A registration order of a definition list also becomes a mark of the progress of work.
- Therefore, the order change of a definition list of a row is not necessarily useful during musical score edit.
- All the “files defined to the list at point in time of running this processing” is renamed to the same name as each definition number.
- Of course, each list item name is also renamed as the same name as each index.
A.bms (before) A.bms (after) remarks #wav01 aa.wav #wav02 #wav03 nonexistent.file #wav05 bb.wav #wav06 aa.wav #wavCC dd.wav #wavEE __ #wavFF ..\parent.oggA.bms aa.wav bb.wav cc.wav dd.wav __ (parent.ogg in parent folder)
#wav01 01.wav #wav02 #wav03 nonexistent.file #wav05 05.wav #wav06 01.wav #wavCC dd.wav #wavEE EE.__ #wavFF FF.oggA.bms 01.wav 05.wav cc.wav dd.wav EE.__ FF.ogg
- By this, the number of bytes which description of a file name consumes is reducible from a musical score.
- Moreover, a BMS work acquires anonymity.
- On a BMS scene of Japan, since the evaluation which is not influenced by the established reputation is expected, anonymization has fixed demand.
- That is, a hint for users to guess the tendency of BMS work and the author’s true character can be reduced by this processing.
- Moreover, when putting a BMS folder on a very deep class, it may be able to come to play normally. (avoiding path length limit of OS)
- If this is used together with “Sort definition list”, probably file names will be consecutive numbers.
- If this is used together with “Sorting by filename”,
- The original definition items’ name are first sorted by code point value.
- Next, renaming is performed on the basis of that result.
- An empty object and the file which is not found (invalid path) are only disregarded.
- When a definition item is multiplex definition, it continues being multiplex definition even after renaming.
- If it is an effective path in the definition of a path, it will be processed as follows.
- BMSE moves the file which a musical score refers to to “the same folder as a musical score open now”.
- The file after movement is renamed as an index.
When users do not want to break the directory composition of the reference place of a musical score, it is necessary to copy applicable files beforehand. - When the file which becomes the same name as “the result of renaming” already exists in the directory of the present musical score, BMSE does not rename that item. If it is the definition of a path, neither movement of a file nor renaming is performed.
- It is also renamed if a file with a strange extension can be referred to from a musical score.
- When there is a filename extension, a filename extension is not changed, but only the basename of a file is changed.
- When there is no filename extension, it is renamed to [the definition number . original name].
- The “Expand” tab of BMSE is isolated from all operations of BMSE. Therefore, the following problems may arise.
before after remarks #wav01 a.wav #exwav02 vfp -50 100 -10000 a.wav#wav01 01.wav #exwav02 vfp -50 100 -10000 a.wav#EXWAV02becomes invalid.
- After performing this processing, the information which can be acquired from a file name decreases sharply.
Noters need to take a work procedure into consideration in order not to interfere with musical score creation.
Therefore, backing up a BMS folder beforehand is recommended.