Fastest Crash :: FFR Batch Submission
Wiosna -
Fastest Crash -
かめりあ (Camellia) [7.25 / 10]
OT17 Bounty Batch
PublicTokenPurchasedSecretEvents
Rejected
Simfile Folder Name
Fastest Crash (Wiosna)
Note Count
4474
Chart Length
4:02
Average NPS
18.8247
Estimated Difficulty
108.95
First Note
0:05
Ending Note Delay
0:01
Hand Bias
Framers
0 - 0
1 - 0
2 - 216
3 - 325
4 - 884
Jumps
Hands
Quads
Color Jumps
Color Hands
Color Quads
Most notes in:
1/3 of a Second
12 - 36.00 nps
0.5 Seconds
17 - 34.00 nps
1 Second
29 - 29.00 nps
2 Seconds
50 - 25.00 nps
5 Seconds
122 - 24.40 nps
10 Seconds
236 - 23.60 nps
30 Seconds
687 - 22.90 nps
1 Minute
1327 - 22.12 nps
Color Count
Largest Note Gaps
0.73s0.73s0.73s0.7s0.7s0.7s0.7s0.43s
Posted at 9:34pm on January 8th, 2024
Approved for 110ish bounty, cleared for judging.
Posted at 6:46pm on January 22nd, 2024
Fastest Crash (Wiosna)
- Offset's fine.
- Can just remove the かめりあ on the artist tag, since FFR most likely won't read that unicode.
When I saw this in the bounty, my mind goes: "how did we get here, it's been around 7 years since I last saw this"
Honestly, there's not really much I can say about this chart, it's perfectly fine for what it's trying to do for each sections, though at some level this is a bit backloaded for tournament purposes. Mainly it boils down to second half being more burst-heavy and there are some rigidity in your trilling usage after each 4th jump. The polyrhythmic jumpstream section was a nice breather after all of those too.
This is a definitive old file that stood out rather well, and pretty much recognizable for most D7-D9 players to tackle this chart in FFR. [7.5/10]
Posted at 10:10pm on January 22nd, 2024
Fastest Crash (Wiosna) [7/10] -FR-
PERMS OK
SYNC OK
10.671: Missing drum note.
10.956: Missing drum note.
11.599: Might as well integrate this hihat.
1:23.885-1:24.528: One example of a particularly awkward hand bias. Not tooo bad given the difficulty of the chart, but not the most fun patterning.
1:27.171: Fine as is, but such calmer sections probably have the leeway for using 48ths here since it's the actual timing.
1:39.647-1:40.635: Another example of bias (right hand) with unintuitive rhythms.
1:45.956 & 1:50.528 & etc: Not all wub sections with the 48ths are the same. The ones mentioned are not straight 8ths. See other iterations.
2:38.885-3:13.171 [FR]: Can't figure out the 32nds at all here. They seem to be abstractions of the melody (as opposed to the 24ths on the wubs), but it feels so difficult for what it abstracts. For example, 2:48.028 has a minijack in it, so maybe the 32nds just very much exaggerate those, but then right after at 2:48.318 there's a minijack but the song doesn't have it, and then 2:52.882 is suddenly triplet minitrills? The three sets of 32nds starting at 3:04.028 shouldn't have a single such minijack.
3:13.456: Maybe purposefully omitted but could probably be added.
This chart has pretty good execution on a per section basis, although the difficulty curve is a bit messy for tournament viability. The dubstep midsection is super fun on its own, but it feels pretty underwhelming relative to the rest of the chart, especially considering the other mentioned abstractions like the 32nds in a big part of the second half. Then there's the ending's difficulty spike of the dense 8th jumps and hands which is fine but for OT in a song that's 4 minutes long is not ideal. Some of the difficulty also comes from a few awkward patterns/transitions which could be avoided.
Ultimately, if the 32nds are made more relevant in the second half, And if they're actually just abstractions to the melody, then fixing those to not all be minijacks could maybe do it. Check the midsection wubs too, and if they can be buffed a bit that'd be neat but it's less major of a concern.
Posted at 10:25pm on January 22nd, 2024
I assume I have ample time to go through this, so put this on hold for now
Posted at 6:28pm on April 15th, 2024
Checking in on the status of this submission, as it's past the 1 month probationary period with a "Fixes Required" flag.
Files/Songs with the "Fixes Required" tag require at a minimum a fix submitted based on the above notes from judges, or a response appealing the notes involved in the reason for it being labeled as Fixes Required.
Since you've responded on this, willing to give extra time on fixes. Just, y'know, keep it in the loop. Would rather it not be on-hold indefinitely in-batch.
Posted at 12:33am on April 16th, 2024
Do reject this, thank you.