845

submitted 10 months ago by Stamets@lemmy.world to c/adhd@lemmy.dbzer0.com

52 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] Turun@feddit.de 1 points 10 months ago

I blame the skip duration. Yt default is 5s, when playing at 2.5x speed (set via an extension) that becomes effectively 2s. It's perfect. If I need more I just press it again.

I have jellyfin set up and (at least on the webbrowser) the default is 30s. Seriously? Why would anyone need 30s skipping? I had the same issue as you before - but only on jellyfin, with YouTube I almost always hit the exact moment I need.

[-] GTG3000@programming.dev 1 points 10 months ago

Some codecs (and by extension, some video players), tend to hitch when skipping backwards since they don't necessarily store enough keyframes.

So if you have a choice between "skip back three times and get the weird half-decoded video or hitching three times" vs "skip back too much and then skip forward/watch the video", the latter can technically provide a better experience. Especially if you're streaming the data and it may have discarded what you've watched already or you've skipped a chunk and it was never loaded.

[-] astrsk@kbin.social 0 points 9 months ago

On YouTube desktop site you can use JKL for -10 pause/play +10 or left space right for -5 pause/play +5 respectively. As well as frame by frame with < > keys while paused.