It shouldn't be ranked if it has the wrong bpm. Timing the correct BPM is one of the easiest things to do while making your map, unless there are more than one.
then again, maps older than 1 week don't get unranked because they have many plays.theowest wrote:
It shouldn't be ranked if it has the wrong bpm. Timing the correct BPM is one of the easiest things to do while making your map, unless there are more than one.
Many older maps have the wrong BPM.theowest wrote:
It shouldn't be ranked if it has the wrong bpm. Timing the correct BPM is one of the easiest things to do while making your map, unless there are more than one.
By timing... do you mean BPM or offset?merchat7 wrote:
Timing shouldn't be off in the first place if you are talking about ranked beatmaps. Some of the old ones may have wrong timings, but no new ranked one should have timing problems and they are normally unranked fast if problems are found. Old beatmaps do not get unranked since they are so old and too many scores would be wipe.
If you can give some examples of some recently ranked beatmaps where timing are off, please list them.
From what I've read in an other thread, it's done like this so people cannot cheat in spinners.
If you have a problem with a timing of a beatmap (bpm or offset), contact a BAT. They'll probably verify with some people and change if necessary.Wiki wrote:
Your map must be perfectly timed. This means that your BPM and offset are spot-on, sliders end when they should, notes are generally following a recognizable rhythm (such as the lyrics or drums) which is comprehensible by a player, and that there are no unsnapped notes (you can check this by running AIMod (shortcut ctrl+shift+a) in the editor).
There is a big problem then.lolcubes wrote:
There are way too many wrongly timed maps with wrong bpms.
Exactly this.kriers wrote:
I was instantly punished by this new restriction. SO MANY maps have issues on offset and I used to chart all of these changes so I could change offset during gameplay for the really hardcore accuracy scores
Let me just try and put things clear as to why I feel very unfairly treated right now:peppy wrote:
Please report incorrectly timed maps and we will fix them. This has always been the case.
I think you misunderstand my point. We often do several changes during one map where offset fleets back and forth. We want the ability to adjust to this again.peppy wrote:
Please restart the map and change at the beginning.
http://osu.ppy.sh/s/34083peppy wrote:
Please report incorrectly timed maps and we will fix them. This has always been the case.
We can't fix bad BPMs though.peppy wrote:
Please report in the map thread of to a BAT. Rather than each player fixing this, they should be fixed in the beatmaps.
We can still adjust by adding local offset. Or that was the case before.lolcubes wrote:
We can't fix bad BPMs though.
It cannot be both?peppy wrote:
Please report in the map thread of to a BAT. Rather than each player fixing this, they should be fixed in the beatmaps.
ykcarrot wrote:
I don't care about miss timed beatmaps. Just I can't adjust offset during testing in the middle of the map, it's really annoying.
Restore it please peppy
Not every BAT can force update beatmaps.TheVileOne wrote:
If peppy says BATs can fix bad BPMs, then you have permission to fix bad BPMs. It would take a map update, but I'm not sure if updating would revert it to the latest version. That was an issue awhile ago.
I believe there're at least 20% out of all ranked maps that are off by >±5ms. I can help to make a tool to automatically detect the timing of most single-BPM songs with reasonable accuracy and compare against the beatmap (and also a list of songs it can't time) if you wish running it on all ranked beatmaps should take less than one day.peppy wrote:
Please restart the map and change at the beginning, and also report the issues in the map thread or to a BAT directly. If there are many ranked maps like this, we need to get started fixing 'em. Local offsets are not the solution.
Starting from xxxxxx ms, offset timing by +/- yy ms and skew timing by +/- zzz ppmlolcubes wrote:
Fixing offsets is easy and if the offset is bad we usually fix it already (if reported).
But yeah as I stated in my previous post, there are multibpm maps with different offsets and maps with wrong BPM which I guess need some waiting now for peppy to implement the possibility to fix BPMs as well.
I wonder how would this look like, cause if it's something like "online offset at" such things could effectively fix a lot of problems without a need to unrank & wipe scores.
Timing is objective but perception of it is subjective. The point is not that a person should be able to use their subjective perceived timing because they do not agree with an objectively correct timing, it is that the "objectively correct" timing may not be objectively correct because it is merely what another person subjectively perceived to be correct, hence why discrepancies exist at all.merchat7 wrote:
@plaird
Timing is an objective thing. It's either right or wrong. I guess it's fine if people prefer to adjust it themselves through, but this is not up for me to decide.
Replays contain an md5 hash of the .osu file they were played on. If the .osu is modified in any way, then the replay and score won't show up on the modified map.TheVileOne wrote:
If you save a local replay and then change the where the objects are in the song, will that not affect how the objects appear in the replay?