Introduction
Reading is weird. The community has come up with pretty good theories for playing osu! which can be backed up either by common knowledge, or by science. Aim is just muscle memory. Snap/flow is about forces, acceleration, and momentum. Tapping stamina is... pretty much in line with just other kinds of exercise. However, we've never been able to come up with a rigid explanation for reading; it just seems to escape us. Luckily, some cool studies in neuroscience might be able to help us know what reading actually is, so we could pinpoint our weak spots and overall become much better players. This guide will deal with osu! reading, scientific explanations for reading, and how we can connect the two ideas and get a better picture of how to improve.Reading, as we know it
Reading is about patterns. We see a pattern. We know which order to click the circles. Then we play it.We're very used to seeing the same old patterns over and over, and mapping meta has done a pretty good job of making sure we see the same old patterns over and over. This seems to be no problem as long as the farmers stick to the same old AR10. But, when they encounter AR9 (or god forbid, AR8!), everything falls apart. There seems to be this strange divide between learning how to play high AR and how to play low AR. If you go higher than you're used to, it feels like circles are blazing by and you can't hit them in time. Go lower, and then the playfield becomes a tangled mess, and you just can't work out which circle to click in time. In both of these cases, it seems to be a mental delay which causes us to go out of sync with the rhythm.
Since it takes time for our mind to process patterns, it follows that we actually read ahead of what we play. It's not easy to notice, but it makes sense: For us to play naturally, our brain wants us to be reading patterns ahead of time, so that we have the time to process them and play properly.
From this, we can say that there are two major obstacles to reading: "reading time" (high AR) and number of notes (low AR). We still don't know the exact steps; the way our brains actually do it, even if we have some idea of how it goes. We also don't know the exact skills involved; which part of reading is just made-up stuff, and which part is a real thing that we can train and get better at.
Eye-Hand Span
Eye-hand span is one of the lesser known concepts of neuroscience. It's been developed as one of the explanations on how our brain handles taking in chunks of info, alongside "peripheral vision" and "saccades & fixations". On closer inspection, it seems to fit snugly with our description of reading, the same way muscle memory fits into aiming.A study (Furneaux & Land) from the Sussex Centre for Neuroscience, about how skill affects the way pianists read sheet music, introduces us to the concept. Eye-hand span is the mental delay caused by the entire process of acting on live information in four distinct steps: Detecting info, processing it, storing processed data in an internal buffer, then translating it into signals at the last second, telling the body to move. In short, it is an analogue of what we osu! players call "reading", except in a much clearer way. Most players simplify (and think of) reading as just the first part - essentially "reacting" - and minimize the middle steps as much as possible. However, this may actually hurt their improvement.
There are two ways to measure eye-hand span. "Note index" is how many objects the performer reads ahead. "Time index", on the other hand, is how far ahead in time the performer reads. The study shows that, the note index gets bigger as the pianist becomes more skilled. Novice players can only read at least two notes consistently, but professional players can go up to at least four notes. This gives us a clue that professionals could process or store info a lot more efficiently and thus play better than the novices. Time index is a lot more interesting, however.
In time index, novices and professionals all played with the same average delay. Instead, the delay changed when the tempo (BPM) of the performance changed; higher BPM meant a lower time index, and vice versa. This makes sense, since you can end up filling your note index with less time if the song was faster. This confirms the idea that BPM and AR are both factors in reading difficulty, as shown by some charts made in the osu! community.
Though average delay is not related to performers' skill, what matters is actually the fluctuation in their actual time index. Novices played at a common average with professionals, but their reading was very erratic; they often read too far ahead or too far behind. This means that another clue to skill is if performers can keep a consistent pace with how far along they read.
Another study (Truitt et al.) from the University of Massachusetts provides more data using "moving-window techniques". The pianists' view of the sheet music is limited and only shows a few notes ahead during play (similar to AR in osu!). The general trend is that smaller window sizes (higher AR) resulted in poorer performance. This is reasonable since pianists do not play with a restricted view unlike osu! players. Overall, professionals delivered more consistent timing, better eye-hand spans, and shorter fixations (meaning they spent less time focusing on a single object) than novices in both unrestricted and restricted cases. In this case, skill seems to correlate both to no window (low AR) and small window (high AR) performance, even if the latter was never practiced.
Okay, but what does that actually mean?
The idea of eye-hand span lets us give a more solid meaning to "reading". We can now say that reading is a four-step process: "detect, process, store, translate", and that better reading simply means being better at the process/store parts, which shows in being able to read further and more consistently. We have definite proof that BPM should be considered when talking about reading difficulty.We can also draw parallels with the research and approach rate in our circle-clicking game. When we play with lower AR, there are more objects and the playfield becomes cluttered. This forces the player to actually process and store info instead of reacting to it. Professional pianists, despite not being exposed to window size (higher AR), was able to adapt better using their experience and efficiency in breaking down data. While there is no supporting data for higher AR improving reading proficiency, it can still be argued that being able to detect and translate basic patterns effortlessly is as important a skill, and may in fact be a stepping stone as it allows the brain to focus completely on deciphering more complicated patterns. It seems that practice for the two works well with each other.
Along with anecdotes from regular and top players alike that low AR practice has improved their overall play, there may be benefits to having a wider comfort zone for both lower and higher ARs, rather than sticking to a single comfortable AR that many players have.
(note: this guide is kinda rushed due to a tight schedule, it may be polished as time goes.)