Hardest frame fix I've done yet

[DossarLX ODI]

grind2 was recently put up with frame fixes.

I made this thread because I learned a LOT about the actual file itself. blu's file had so many BPM changes that I couldn't just simply shift stuff around because I did not know their rhythmic value/BPM.

Basically, there were three general phases:
1) Reconstructing the file to a static BPM
2) Shifting around placements after conversion
3) Recoloring to the original file's colors

In total, those three phases took 7 total hours. 11:30 PM - 4:30 AM Friday night to Saturday early dawn (5 hours), then 11:30 AM -1:30 PM (2 hours) Saturday afternoon.

1) Reconstructing the file to a static BPM

In order to figure out what the hell to shift in the first place, I had to restep the file at a static BPM. The song's real BPM is 230/460. Below are some pictures showing the comparisons (cmod) of the rhythmic values the bpm changes in the file were supposed to be snapped to.

Click the spoiler to see these images. I noticed that notes like 3/64ths and 32nd intervals appeared many times, and there were several interesting cases for 230 and 460 bpm.

230 BPM on the left


230 BPM on the left


460 BPM on the left


230 BPM on the left


460 BPM on the left


460 BPM on the left


460 BPM on the left

So basically, there were a lot of 32nd and 3/64th type intervals if the steps were snapped to a static bpm.

2) Shifting around placements after conversion

After reconstructing the file to a static BPM I saw that no parts should have had any 2 frame minijacks except for the 16th wall which forces a minijack. This took some time, but I got hit with some "comma" BS when trying to convert the file for like 20 minutes and it really pissed me off. I playtested the file and it played a lot smoother than before, but the file is still ass.

3) Recoloring to the original file's colors

Oh boy. So I've recreated the file to a static BPM and shifted placements after converting and playtesting. I *still* have to put the file back to its original colors. This was a tedious process and I had to use qqwref's and Velocity's replay program to help me locate which colors to change.

With all that said, you guys now know that grind2 has a lot of weird 3/64th rhythms and broken 32nd intervals if you have it at its original static BPM, 230/460. blu's file had a million BPM changes with ridiculous color usage, but the approximate values do snap to the original (but a lot of the file is still BS technically). This is by far the longest and hardest frame fix I've done as of now, and hopefully there aren't too many ridiculous BPM changing files like grind2 in the future.

Here is a download link if you want to see the 230/460 BPM version of grind2, reconstructed by me from the original: http://www.mediafire.com/?nsy947lb50aab5a