Threlm & Rovik
Threlm
Hey Rovik, ever notice how the old QuickTime Motion codec buried a tiny velocity header in each frame? I’ve archived every single one, cataloguing the exact frame rates that vanished when the spec changed, just in case someone wants to replay the speed of those early uploads.
Rovik
Yeah, that velocity header is like a secret speed glitch. If you can pull the frames out, you’ll get the same jitter you get when you sprint into a frame‑rate limit. Maybe upload a 3‑second clip, drop it in a loop, and see if the codec’s still feeling that punch. Don’t forget to frame‑rate it, or you’ll be stuck in a bureaucratic pause. Keep pushing the speed—gravity’s just a suggestion.
Threlm
I’ve got every velocity header from the old QuickTime Motion archive, 3 GB of pure metadata. Here’s a quick shell trick: ffmpeg -i input.mov -vf "select=gte(t\,0),setpts=N/FRAME_RATE/TB" out%04d.png, then loop with ffplay -loop 0 out%04d.png. That will preserve the jitter you’re hunting. Just remember to set the frame‑rate flag, or you’ll end up with a dead‑stop buffer. The codec still remembers that punch, even after my seven‑year tool protest.
Rovik
Nice trick, that shell hack is like a jump in code space. Keep throwing those 3‑second loops at the machine, it’ll feel the old velocity spike. Just make sure you don’t hit the frame‑rate lock, or it’ll freeze like a bureaucratic memo. Keep moving, keep glitching, and let the speed bite.
Threlm
Got it, here’s a quick script to keep the loop running at 23.98 fps so you won’t hit the lock:
```bash
#!/bin/bash
ffmpeg -i clip.mov -vf "setpts=0.5*PTS" -r 23.98 output_%04d.png
ffplay -loop 0 output_*.png
```
Run that, watch the jitter dance, and feel the old speed revive.
Rovik
Nice, set the tempo to 23.98 and let the old speed echo. Hit play, feel that jitter ripple, and if the frame‑rate lock bites, just jump past it. Keep the loop alive, keep the velocity humming.