Re: ssc/sm/dwi
Looking into it, it's actually pretty simply in .sm. But seems like it'd be quite time-consuming to an extent.
I'm gonna take one of my pad files as an example.
Let's start at the top shall we? It's pretty straightforward, it's for the Challenge difficulty, with a rating of 13. The numbers I BELIEVE are the values for chaos, voltage, etc (what you see in the default SM3.9 theme with the circle below the banner).
NOW, the important part are the numbers between each "measure". The measure part is straightforward. Between em is a lot of 0's though right? Those are empty measures, as in nothing are in them whatsoever.
Now let's look at Measure 5. See how there are 1's now? Those are tap steps. 4th note tap steps to be exact. So 1001 is obviously a left-right jump, 1100 is a down-left jump, etc. Straightforward right? 0000 are the position of the arrow markers, first 0 is left, second 0 is down, etc. So when there's a 1, it means that there's a tap arrow there.
But WAIT, the next measure has more rows of 0's and 1's and EVEN other numbers. Why is that you may ask? Well because there are more arrows in the measure. In measure 5, they were ALL 4th notes, red notes, etc. But in the next measure, there are holds and 16th notes and etc. Because of the 16th notes, it had to be extended so it could be read. When there's only 4 rows of notes, it assumes that there are ONLY 4th notes or less in the measure. If there are 8 rows, it assumes 8th notes or less, etc. Get the idea?
2's are the beginning of a hold, and 3's are the end of a hold (and rolls). 4's are also the beginning of a roll. So from 2/4 to 3, there will be a hold there. I have no idea what would happen if you put a 1 in between it though. M's are mines.
That's pretty much it for .sm files I guess. It's pretty straightforward but pretty time-consuming to do manually, especially with no music to test with, etc. BPM changes are under #BPMS in the .sm file (ie if you put 26.000=150.000, under BPMS, the BPM will be 150 at beat 26). Stops are under #STOPS and work the same way (except instead, the 150 will be how long it would run for in seconds).
Hope that helps you out :V
Looking into it, it's actually pretty simply in .sm. But seems like it'd be quite time-consuming to an extent.
I'm gonna take one of my pad files as an example.
Code:
//---------------dance-single - ----------------
#NOTES:
dance-single:
:
Challenge:
13:
1.000,1.000,0.430,0.302,1.000,694.000,47.000,33.000,71.000,6.000,27.000,1.000,1.000,0.430,0.302,1.000,694.000,47.000,33.000,71.000,6.000,27.000:
// measure 0
0000
0000
0000
0000
, // measure 1
0000
0000
0000
0000
, // measure 2
0000
0000
0000
0000
, // measure 3
0000
0000
0000
0000
, // measure 4
0000
0000
0000
0000
, // measure 5
1001
1100
0101
0110
, // measure 6
0020
0000
0000
0000
0000
0000
0000
0000
2030
0000
0000
0000
0000
0000
0000
0000
3001
0100
0001
0100
0001
0000
0010
0000
0100
0000
1000
0000
0001
0000
1000
0000
, // measure 7
0020
1000
0100
1000
0230
0001
0010
0301
, // measure 8
1000
0100
1000
0001
0100
0010
1000
0010
0100
0001
0010
0100
0010
0001
0100
0010
, // measure 9
0100
0001
1000
0100
0010
0001
1000
0001
0100
0001
1000
0001
M100
001M
M100
001M
, // measure 10
M100
0001
1000
0001
0100
0010
1000
0001
0010
0100
1000
0100
0010
0001
1000
0100
, // measure 11
0010
0001
0100
0010
0100
0001
0010
0100
1000
0100
M010
0001
1M00
0001
M100
0010
NOW, the important part are the numbers between each "measure". The measure part is straightforward. Between em is a lot of 0's though right? Those are empty measures, as in nothing are in them whatsoever.
Now let's look at Measure 5. See how there are 1's now? Those are tap steps. 4th note tap steps to be exact. So 1001 is obviously a left-right jump, 1100 is a down-left jump, etc. Straightforward right? 0000 are the position of the arrow markers, first 0 is left, second 0 is down, etc. So when there's a 1, it means that there's a tap arrow there.
But WAIT, the next measure has more rows of 0's and 1's and EVEN other numbers. Why is that you may ask? Well because there are more arrows in the measure. In measure 5, they were ALL 4th notes, red notes, etc. But in the next measure, there are holds and 16th notes and etc. Because of the 16th notes, it had to be extended so it could be read. When there's only 4 rows of notes, it assumes that there are ONLY 4th notes or less in the measure. If there are 8 rows, it assumes 8th notes or less, etc. Get the idea?
2's are the beginning of a hold, and 3's are the end of a hold (and rolls). 4's are also the beginning of a roll. So from 2/4 to 3, there will be a hold there. I have no idea what would happen if you put a 1 in between it though. M's are mines.
That's pretty much it for .sm files I guess. It's pretty straightforward but pretty time-consuming to do manually, especially with no music to test with, etc. BPM changes are under #BPMS in the .sm file (ie if you put 26.000=150.000, under BPMS, the BPM will be 150 at beat 26). Stops are under #STOPS and work the same way (except instead, the 150 will be how long it would run for in seconds).
Hope that helps you out :V
Comment