i think a more complete solution would be to make so you dont have to have a different offset for every single song
This has to do with when the sound file starts in the swf. For every song release I have to make three different versions and see which one snaps the best. Some songs are usually 1/4 or 1/2 a frame off during conversion which requires this.
For songs that need more than 1 offset (300 for instance is super late), it was basically a crapshoot in which you just hoped your file converted somewhat decently. Actually adjusting the sync requires inserting silence padding and shifting frames when needed, which was not done earlier in the day.
I wouldn't be averse to someone making a thread about the offsets they use for different songs. There should be a majority offset that works for most songs, and then some other songs that are noticeably off.
Originally posted by hi19hi19
oh boy, it's STIFF, I'll stretch before I sit down at the computer so not I'm not as STIFF next time I step a file
if someone is willing to go through and find out problematic songs (hardkore atomic, rave 7, system doctor, tell v3, etc. off the top of my head) and what their +- offsets are with respect to a song that is established as 100% on sync (pick a base song or something), and that person has reputable accuracy, then swfs could probably be fixed or something. Often times, it's like a .5 offset though so rip that would be fixing the mp3 or something idk
dossarninja with the mp3 and better explanation lol
Most cases are probably "in between" cases (1/4 to 3/4 frames off). There should only be a handful of cases that are 1 or more offset different. Either way, that requires decompiling every swf and making three different versions which takes a long time for even a few songs.
Originally posted by hi19hi19
oh boy, it's STIFF, I'll stretch before I sit down at the computer so not I'm not as STIFF next time I step a file
Comment