@monorail my brain's been just guessing since i hit puberty tbh

@monorail@glaceon.social this is a plot point (sort of) in my book lol

@InspectorCaracal oooh

@monorail@glaceon.social nerd comes up with a hypothesis for how dragons make themselves invisible, comes up with one based on that fact, determines that this implies there must be a maximum field of view they can affect and the solution for this is to see them Up Close

@monorail Fun Fact: It's possible to see the blind spot if you force your eyeball to stay still for a few minutes.

@monorail We very technically live slightly in the past and that's fucking batshit

@monorail bold of you to suggest that this brain is ever not doing that tbh

@monorail I learnes that the eye also is never standing really still because of that.
Always noving around a bit to get a voew of that blind spot - and then I think the brain inserts it the same way as when you're consiously move your eyes somewhere.

@monorail Like… It gains focus and keystroke delay is 0. The delay slowly ramps so that you don’t notice, but resets as soon as you switch focus or if you haven’t typed for, say, 10 minutes. After the delay gets to whatever level matters, it sits there for a bit so the human is acclimated, then cuts it off.

@monorail So that the experience feels like you start typing and if you stay in it the editor starts anticipating your thoughts and it’s all so effortless.

I want to use this as an experiment. I want to experience this thing.

@IceWolf yes but it's also unnerving how often they lie

@cadence @monorail the delay needs to be consistent

@cadence @monorail don't get me started on rhythm games and latency syncing - you have input latency, video latency, and audio latency, which are all different!

@cadence @monorail have yet to see a rhythm game handle it well

The Rock Band 4 guitar has a microphone and optical sensor so it can handle the calibration automatically by putting it against the TV

except they forgot it's over Bluetooth so there's a somewhat random delay of 5-50 ms

@ChlorideCull @cadence the rb/gh games do honestly handle it well if you do it manually as opposed to using the automatic calibration

it's just a hard problem to solve

@cadence @ChlorideCull @monorail video latency is rarely needed since its a rhythm game, unless its really high which it basically never is
useful for predicting rhythms youve never heard, though our brains react to audio way quicker than video so its not feasable to play without audio

input latency is really hard to calibrate, but still is important

audio latency is the most important one, and easy to calibrate AS LONG AS input latency is calibrated properly

most games dont care about video latency, and count audio and input latency as one thing because, why wouldnt they
the only case where input latency differs is on keyboards with low polling rates

im guessing per-map latency is offsets? which is just as important, however in most cases if your bpm isnt doing weird changes youre safe automatically detecting it and then adjusting via assistticks and waveform alignment

@cadence @ChlorideCull @monorail im not defending osu, it still sucks
but one offset is the standard rhythm game treatment
youll find it in itg, arcaea, basically anywhere

@oat @cadence @ChlorideCull also unless i'm seriously misunderstanding

a positive change in two of the three is equivalent to a negative change in the last one. like +5 +10 +0 plays exactly the same as +0 +5 -5

so if visual latency isn't super important to you, you should be mostly okay with just the adjustment for audio latency

@monorail @cadence @ChlorideCull yeah, input latency is a part of audio latency
if you press a button and 50ms later you hear a sound, theres either 50ms of audio latency, 50ms of input latency, or its something inbetween

if you have 50ms of audio latency, you can offset the song by 50ms so that when you hit the key, the song has already went 50ms ahead to account for the latency

if you have 50ms of input latency however, you cant just offset the input. you cant really just sleep(-50ms), only count that input as if it was 50ms ago, but thats really complicated and ""fun"" to implement in its own ways
doing the same method as audio latency would work however, and you can just sum up the input and audio latency and offset the song by that much

plus its easier to understand and calibrate from the player side. assuming 25ms of input latency and 25ms of audio latency, how do you tell which of the 50ms total latency is audio and which is input? aligning a picture blinking to player inputs is still input + video latency, and aligning a beat to player inputs is input + audio latency, so most just calibrate the sum of both at once and use that