YoshL's Quick "Find Your Offset" Tutorial

[YoshL]

YoshL's really quick "how to find your offset guide"

https://docs.google.com/spreadsheets...Va0/edit#gid=0
Click the link for a listing of song offsets, and post if you want specific songs added/pm me if you want to contribute

because the tournament is coming up and i feel like a lot of people will benefit from this

For those of you who feel like arrows are coming too soon or too late, or feel like there's some sync issues at hand.
This can be kinda seen when you're playing a file and you have an abnormal Perfect to Amazing ratio (with some random goods/other PA), where it feels abnormally high (for me, when i hit something around 1:2 perfects to amazings ratio, i feel like it's a little necessary to adjust offset).

There's a fairly easy way to fix it. Just remember that you have to have a framerate of (probably) 60 or 120 etc. or something for this to work relatively well. *(unconfirmed)

================================================

Step 1: select a part of the song that's very easy to get good accuracy well, but isn't slow. Usually this is a constant rhythm that you can tap, not single notes with large gaps in between. You don't want hard sections for this

-------------------------------------

I'm going to pick "System Doctor" as an example.
I don't want to select the intro to the song because the notes are spaced way too far apart, and thus will result in you visually watching the arrows to the receptor, rather than relying on rhythmical accuracy.
I don't want to select the ending of the song because there's nasty 32nd bursts that pretty much require mashing, or non-optimal accuracy to hit properly.
I do want to pick some of the 8th note sections that are really easy to hit with good accuracy, thus i'm going to start isolating at note 510 as my section.

================================================

Step 2: isolate said part (it's up to you how long you want to hold the section with good accuracy), and concentrate very hard on using only the audio for timing. If need be, try covering up the receptors in order to do this well.


as soon as you're done with the section, you want to quit out of it. As you can see, I still AAAed the section in question, however the accuracy seems a little bit off.

================================================

Step 3: right click the speed mod in order to get the "base offset" as I'll call it


In my case, my accuracy was -.350 ms with a variation of .452 ms in either direction. The "base offset" would be -.350 ms. You can repeat this to get a better understanding of where your hits are centered. Longer sections of file that you hit will result in (probably) a more accurate offset.

================================================

From here, you have 2 choices. Usually you would start with Choice 1, but if you find the base offset to be very similar regardless of what you set the global offset to, then probably choice 2 is the backup case.

Choice 1: modify global offset (visual positioning)
if you feel like the notes need to be shifted in respect to the music, in your options menu, go to your global offset, and set the value to the negative sign of your "base offset"


because my "base offset" was -.35, i want .35 as my global offset.

If you already are using a global offset, add the negative base offset to your current global offset.

================================================

Choice 2: modify judge offset (judgement positioning)
if you feel like the arrows are perfectly aligned with the receptors, or have been fiddling with global offset without finding any positive effects, then you'll probably have to mess with judge offset.
Simply plug the "base offset" into the judge offset box.

note: only use either choice 1 or choice 2 after a sync test. you can combine the choices, however when applying your base offset that you've found, only apply to 1. (or balance out the offsets, but this is probably not something you need to be worrying about)

and that's pretty much it. Again, i usually default to choice 1 because it just works better for me


and my accuracy skyrockets after fixing offset


please also keep in mind that you'll probably have a general "global offset" that you'll hover around, but many songs are off by like .3 in either direction, some go waaaay beyond and require a little more tuning to get. A lot of the time, the offset delta will be like .1 and fairly negligable, however to more sensitive players it may still be a problem. With FFR's limitations, the need for these offsets arise unfortunately, however this is a workaround that doesn't take too much time, and honestly is 100% worth it in the end in terms of nailing out those extra-tasty scores.

Happy arrow smashing!

[badman7772]

then yosh follows his own guide and gets promo'd to d7. yea guys this thing is super effective.

[Kanzas]

Will test thoroughly today with progressive pics

[MikeShinoda12345]

world of dreams, iso beginning at 401, and masked accuracy worked really well for me ^^

[YoshL]

also take note that again, sometimes if you check your accuracy after a full song play, there may be sections of the song *(usually harder sections) that you might tend to hit earlier, or later than you'd normally hit just because of the difficulty. so while the final accuracy of a full playthrough might represent the actual accuracy that you hit throughout the song, it won't properly represent your true accuracy. instead of fixing your offset here, you would need to fix your playing (i.e. figure out whether you need to envision yourself rushing forwards or lagging behind on patterns/sections)

[rushyrulz]

Adding a link/reference for this thread to the ATTN: Velocity Players thread.

[Kanzas]

Originally Posted by YoshL

also take note that again, sometimes if you check your accuracy after a full song play, there may be sections of the song *(usually harder sections) that you might tend to hit earlier, or later than you'd normally hit just because of the difficulty. so while the final accuracy of a full playthrough might represent the actual accuracy that you hit throughout the song, it won't properly represent your true accuracy. instead of fixing your offset here, you would need to fix your playing (i.e. figure out whether you need to envision yourself rushing forwards or lagging behind on patterns/sections)

This is definitely where I always had a problem. I would play something like Yoshi Cookie, and find the offset, but when I played (insert longer, harder files) I feel I would do trash, and thus think the offset I have is completely off due to way to many goods to perf/amz

[YoshL]

unless your perf/amazing ratio is off, if you're hitting a lot of goods, then it's just you playing bad, or bad lag

[Kanzas]

A lot of the time my p/a was about 1.1 somtimes, 1.2

i'd say it's about 1.3-ish now after doing this. still get goods, but much lower, and i know thats just due to my decrease in skill and probably just my laptop

[dell2150]

Is there going to be a quick tutorial on how to fix lag?

[YoshL]

YoshL's quick tutorial on how to fix lag

[Kanzas]

That tutorial actually helped! Wow, YoshL got mad help skills. 10/10

[V-Ormix]

Originally Posted by YoshL

YoshL's quick tutorial on how to fix lag

sonf a dink

[Gradiant]

I'm gonna use that right now yoshl, thanks

[shenjoku]

Well this fixed my accuracy problems, now if I could ever make it stop lagging it would be usable -_- I've tried a million things and every guide I can find and nothing ever works. It's really the only reason why I still use Velocity. At least that never lags on me =/

Thanks for the guide though, made it feel a lot better. One step at a time.

EDIT: I take that back. Figured out how to fix the lag by running fullscreen, but then I get these weird looking scanline type things that make it really hard to read. Almost there...

[LogicalBeast]

UMMMMM...HOLY SHIT!!! O.o MASSIVE thanks YoshL, I thought it was impossible to go for accuracy on a frames based engine. Best on this is 6 Perfects?


So you know I'm not pulling your leg...fuckin' insane eh? I don't claim to be "INSANE WR!!111!" material but this just blew my mind...thanks man.


This tutorial really helped me, now if I could clarify something: is the Global Offset in ms or still in FPS? (based on 30FPS) I ask this so I know what unit = 1ms, so I can use your method, then fine tune the number given so I'm square in the middle of the Amazing window, so getting Perfects would feel like getting Goods haha.

[YoshL]

the global offset is definitely in frames (i think to be 100% accurate, it's frames in 30 fps)

[DissonantMuse]

I definitely need to give this a shot.

[Mourningfall]

Great tutorial, bookmarking for future reference

[YoshL]

so whenever I start my next session, I'm going to begin compiling a google doc of all the standard offsets I use on songs that I normally play, and I think it'd be productive if people also contributed their offsets to the sheet as well. Just as a nice community tool to use to make finding offset easier