I still waited for this! Great job and congratulation, Mr. Armin-sama! :3
This is a mistake and will be resolved as soon as possible. The BAT apologies for any inconvenience caused, please be patient.Philippines wrote:
Beatmap does not exist? :O
no no no definitely not.
- Why Not Me
Offset: 2406 (-5), 15809(-5)
BPM: 143,25(Correct)
Notes: Violin's pretty hard to time, since you should find the peak. So I'm unsure if like this is more correct, you can use -2/3 though (Gaussian distribution of errors, the average value is the more probable)- Shot In The Dark
Offset: 39101(Correct)
BPM: 106,00(Correct)
Good good! I'm waiting for you!Derekku wrote:
EDIT: Had to leave halfway through; will finish asap!
Mercurial is posting this pic to every unranked map, I guess -.-Mercurial wrote:
I hope it got approved soon.
Lybydose wrote:
[Why Not Me]
-5ms on the first section 2406? Agreed
+15ms on the second section 15829? Agreed
[Shot in the Dark]
-18ms (39083) Offset feels fine at the beginning, but then I start hitting -5, -10, -15... so it seems like the BPM is actually wrong. Here's what I get:
106.025 BPM; 39101
106.000 BPM; 95696
106.000 BPM; 215686
[In the Middle of the Night]
-8ms (337095) Actually that's -10, but anyway, It think that -15 would be better. Some parts felt slightly late with only -10. Also, I'm not sure about 10:35:005 to the ending, due to there only being guitar, but I suppose it sounds fine.
[Faster]
fine (648736) Yeah, I guess this is fine. I fluctuated between -5 and +5, so there's no need to change it.
[Fire and Ice]
skipping for now 8 timing points? blehhhh let's see...
Beginning: 70.04 BPM is definitely incorrect; 933535 offset is also incorrect. I tried 70.00, but that seemed to be a bit too slow... 70.015 BPM with 933525 offset seemed to approximate things nicely (tested with like 3 different bpms and even multiple sections to make sure).
140 BPM section: +10 (1022649)
Slowdown:
135 BPM; 1137505
130 BPM; 1139282
105 BPM; 1140205
105 BPM; 1141347 (to fix the downbeat)
[Iron]
-8ms (1150313) Agreed
This should be 1/3 despite what derekku says. This is one of those 1/3 songs that could alternatively be mapped with a faster bpm (132*3/2=198), 3/4 time signature, and 0.75x SV. That's why I said that it's "not 1/3", but I hadn't looked into the song enough and was just skimming through before unapproving. However, there's no need to change the timing like this, so no worries!
[Where is the Edge]
fine (1494679) Could actually use a -5 (1494674), but otherwise fine
[Sinead]
fine (1730551) Agreed
[Lost]
-8ms (1994397) Agreed
[Murder]
fine (2309000) Actually, this feels a bit late. Try -8 (2308992)
[A Demon's Fate]
fine (2565180) Agreed
[Stairway to the Skies]
-10ms (2896210) Actually, -5 felt waaaay too early in many spots. -5 should be more than enough (2896215)
move the downbeat back one white tick Yep!
52:56:466 (1,2,3,4) - okay this isn't timing but HOLYYYYYY that's just a plain evil way to end the marathon. These 1/3 notes are NOT expected at all, and I had no idea what was going on while playtesting. ):
Fire and Ice 's timing is...erwwwwgh, I need other opinions on that.Lybydose wrote:
Why Not Me:
-5ms on the first section Hm... agreed.
+15ms on the second section This sounds too early here 00:26:711 (2,3) - for me.
Shot in the Dark:
-18ms (39083) Oh gawd, Derekku's timing sounds better, but there are some grey areas that feel just weird. I'll get other opinions.
Middle of the Night:
-8ms (337095) Agreed with -10ms
Faster:
fine (648736)
Fire and Ice:
skipping for now
Iron:
-8ms (1150313) Agreed
This should be 1/3 despite what derekku says.
Where is the Edge:
fine (1494679)
Sinead:
fine (1730551)
Lost:
-8ms (1994397) Fixed.
Murder:
fine (2309000) i used derekku's value
Demon's Fate:
fine (2565180)
Stairway:
-10ms (2896210)
move the downbeat back one white tickmoved downbeat and fixed with -5ms
Some BPMs *aren't* perfect numbers, though. It makes no sense to use a round value if you have to add extra uninherited sections to fix the offset from being completely off during a section.Ephemeral wrote:
my god, please don't compound bpms like that.. no music will ever be precisely 70.025 bpm or whatever, just get the closest round BPM possible and time out each specific offset drift if there are any
I disagree with this as well. Adding a new uninherited section per beat is very random and unpredictable. It makes more sense to approximate it as much as possible which is what I did in my timing as opposed to the original (which *did* use new red lines per beat).Ephemeral wrote:
as far as the bpm slowing at the end goes, instate a new timing section for each beat mapped when you become unsure of the BPM. this one is tricky since it isn't a "controlled" fade so to speak (ie non-linear). i can't see any other way of fixing this otherwise.
We *never* apply online offsets per-difficulty, and it's not even possible (unless peppy can do it). Either way, like I said in my mod post, the timing should be the same in all difficulties. Also, scores have already been deleted because timing isn't the only issue in this mapset.Ephemeral wrote:
you know, thinking about it, the only static timing changes should be made in marathon and fire and ice - the others can have online offsets applied and therein won't require a score reset
There's nothing strange(controlled), the only thing I can do is moving it one grid4 pixel uplolcubes wrote:
[*]09:49:255 (7,8) - This is not properly stacked. This needs to get fixed because they look incredibly confusing when using the default skin (skin toggle).
256,4,589405,1,0
09:51:805 (1) - The path of the slider is actually going offscreen. You really need to change this somehow. Hardrock it and you will see that a good chunk of the slider track is offscreen, compared to nomod where nearly the whole slidertrack is behind the HPBar which is bad.had to use some small jumps to preserve the mapping and the symmetry
332,128,591205,1,0
256,40,591355,1,0
180,128,591505,1,4
388,20,591805,6,0,B|451:30|513:82|510:163|476:218,2,259.999995350838
256,108,592555,1,0
124,20,592705,2,0,B|60:30|-1:82|1:163|35:218,1,259.999995350838
132,288,593155,1,0
some, yes. i sincerely doubt a professionally mastered song such as this has a bpm of 70.04. the BPM for this song -is- 70, there should be no doubt about that.Derekku wrote:
Some BPMs *aren't* perfect numbers, though. It makes no sense to use a round value if you have to add extra uninherited sections to fix the offset from being completely off during a section.
then you have every note in that section being approximately wrong as opposed to each note having a chance of being correct. believe me, my experience with bad apple's timing has equated me substantially to what happens when an incorrect bpm is selected. each section of the fadeout is an individual note, which makes this a significantly easier option.Derekku wrote:
I disagree with this as well. Adding a new uninherited section per beat is very random and unpredictable. It makes more sense to approximate it as much as possible which is what I did in my timing as opposed to the original (which *did* use new red lines per beat).
looks like we have criteria to address then!Derekku wrote:
We *never* apply online offsets per-difficulty, and it's not even possible (unless peppy can do it). Either way, like I said in my mod post, the timing should be the same in all difficulties. Also, scores have already been deleted because timing isn't the only issue in this mapset.
some, yes. i sincerely doubt a professionally mastered song such as this has a bpm of 70.04. the BPM for this song -is- 70, there should be no doubt about that.tell that to Taylor Swift, aka #1 BPM troll
Speak NowLybydose wrote:
some, yes. i sincerely doubt a professionally mastered song such as this has a bpm of 70.04. the BPM for this song -is- 70, there should be no doubt about that.tell that to Taylor Swift, aka #1 BPM troll
Yep. IIRC "You Belong With Me" had 3 uninherited sections and it was just very awkward.Lybydose wrote:
some, yes. i sincerely doubt a professionally mastered song such as this has a bpm of 70.04. the BPM for this song -is- 70, there should be no doubt about that.tell that to Taylor Swift, aka #1 BPM troll
some, yes. i sincerely doubt a professionally mastered song such as this has a bpm of 70.04. the BPM for this song -is- 70, there should be no doubt about that.this is what we call music.
And for obvious reasons I cannot fix these "other problems" If none writes or deepens them.Derekku wrote:
There's been too many complaints of timing issues and other problems
"with the video being black and white before, having the outer edge of the hitcircles black makes it impossible to see the approach circle hit the outer edge"
"and the beginning of the current song has hitbursts overlapping slidertrails"