1
Indeed, but it's up to you whether you can afford to spend less than 2 seconds to fix the offset(even song doesn't start after 3-4 secs).Dm1321 wrote:
Sooo..
You're telling me to mess with my offset every time I'm going to play a different beatmap...
...
I'm going to stay with my bad accuracy.
B1rd wrote:
so instead of trying to hit to the beat of the song you should try and change the offset to compensate for you own sense of rhythm?
You're missing the point. There are an incredible amount of songs that are incorrectly timed, he is saying you can fix that by changing your local offset.B1rd wrote:
so instead of trying to hit to the beat of the song you should try and change the offset to compensate for you own sense of rhythm?
I thought it was a ranked prerequisite to have a map timed properly....Mathsma wrote:
You're missing the point. There are an incredible amount of songs that are incorrectly timed, he is saying you can fix that by changing your local offset.B1rd wrote:
so instead of trying to hit to the beat of the song you should try and change the offset to compensate for you own sense of rhythm?
I wouldn't do it because I am lazy and there are simply too many songs to even bother.
It is probably better handled now, but in the past there were many maps that were ranked with hardly passable timing.Woobowiz wrote:
I thought it was a ranked prerequisite to have a map timed properly....
wow these forums' quote limitations thoMartell wrote:
Riince wrote:
Mistimed maps are out there, I will admit, but I don't think there are as many as you say because of the current ranking criteria. I'm not saying never change the local offset, but what I am saying is always check whether a map is mistimed or you're mistiming the map before changing the local offset. Most of the time it will be the latter (unless you're retro and you exclusively play maps from 2008), which is why this is damaging for accuracy.Mathsma wrote:
You're missing the point. There are an incredible amount of songs that are incorrectly timed, he is saying you can fix that by changing your local offset.
How does changing the offset "compensate for ones sense of rhythm"?B1rd wrote:
so instead of trying to hit to the beat of the song you should try and change the offset to compensate for you own sense of rhythm?
it's rarely or never off enough to cause a noticeable hit error margin that can't be made up by simply playing better. this is just an unnecessary chore.buny wrote:
How does changing the offset "compensate for ones sense of rhythm"?B1rd wrote:
so instead of trying to hit to the beat of the song you should try and change the offset to compensate for you own sense of rhythm?
It doesn't change how the map plays to the beat, it simply shifts the timeline.
Also, pretty much only old maps are going to have the wrong offset and this is a pretty bad way on determining offset because it only gives you a general idea of if you're too early or too late - in your screenshot we can see that you hit notes too late too, and a lot can factor into this such as streams (nobody will ever perfectly maintain a long stream without having to compensate speed).
You should only be changing offset if you know for certain that it's off.
It is, but apparently inaccuraries of ~10ms are acceptable.Woobowiz wrote:
I thought it was a ranked prerequisite to have a map timed properly....
More like +/- 5. I've had quite a few maps changed online by 6-7ms in the past.GoldenWolf wrote:
It is, but apparently inaccuraries of ~10ms are acceptable.Woobowiz wrote:
I thought it was a ranked prerequisite to have a map timed properly....
I don't think ignoring hit error bar is a very good idea because it DOES work as it should and it's for you to diagnose(not sure how to spell) between your click timings and the actual song, rather than the beatmap itself, because it's the beatmap that's mostly not right.Dexus wrote:
To get higher accuracy it's better to IGNORE the hit error bar (one less thing to look at/worry about while playing). Instead focus on what the hitsounds relate to in the music and time it in sync with them. Also fixing your UO takes priority over messing with LO. The only time you really need to mess with the LO is when the map is clearly and painfully out of sync; the couple ms inaccuracy are acceptable because windows itself fluctuates plus I don't think anyone can hit a stable -1/+1 every time they play. If you're seeing that on EVERY map you're playing that you hit early or late then it's commonly 2 things: 1) your UNIVERSAL offset is wrong 2) you're not listening to the music.
To fix your universal offset simply go download the offset wizard song by peppy and put these sounds into your skin [ http://puu.sh/9BkRs.zip ] Then go into the options and open up the offset wizard (Have the offset wizard song by peppy playing). Stop the music and raise the offset to +10 or +20 and then start it; every tick try and lower it by 1ms until the sound shifts to a deeper almost muted kind of sound. From there go further about 3ms and you should be fine. If you're uncertain about it you should be able to hit stop and then play, the metronome ticks should sound the same as before you stopped the music. I use -5ms on my laptop, -3ms on my desktop. Commonly I see computers be within this range.
This work of art has an online offset of 15ms.Lach wrote:
More like +/- 5. I've had quite a few maps changed online by 6-7ms in the past.
I believe "Map" is a rather exaggerated term for this.NarrillNezzurh wrote:
This map has an online offset of 15ms.Lach wrote:
More like +/- 5. I've had quite a few maps changed online by 6-7ms in the past.
You're missing the soundcard.Kousaka Tenshi wrote:
Any how, I already listed a few factors that affects your accuracy:
- Keyboard delay
- Song timed incorrectly
- Your skin's hitsound could have delays
SupaWolfTiga wrote:
Mathsma wrote:
I wouldn't do it because I am lazy and there are simply too many songs to even bother.