Skip to content

Commit 2b99522

Browse files
authored
Update README.md
1 parent 68bf0d1 commit 2b99522

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

README.md

+3-1
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ It works on a common line with arguments, which are all optional. If you just ru
1414

1515
The arguments are:
1616

17-
input=[file/dir] output=[songs dir] duration=[seconds to process] tap=[true/false] tapsync=[offset time in seconds for tap, default: -0.11] hard=[true/false]
17+
input=[file/dir] output=[songs dir] duration=[seconds to process] tap=[true/false] tapsync=[offset time in seconds for tap, default: -0.11] hard=[true/false] updatesm=[true/false]
1818

1919
Example:
2020

@@ -24,6 +24,8 @@ If you set tap=true, AutoStepper won't try and automatically calculate the BPM o
2424

2525
It is best to let AutoStepper run through a whole bunch of music, and ones that it might not get exactly right -- to then pull out & use tap=true on them.
2626

27+
updatesm=true will look for existing .sm stepfiles using the same filenames generated by AutoStepper. If found, it will take the offset & BPM from those files & just update the steps. This is useful for updating steps generated with old versions of AutoStepper, or changing the "hard" argument without having to recaculate BPM/offset times.
28+
2729
You can also use the output as a base to further edit & perfect songs, with AutoStepper doing most of the dirty work.
2830

2931
I will add it is optimized for pad use, not keyboard use (e.g. difficulty isn't high enough).

0 commit comments

Comments
 (0)