Hacker News Reader

Comment by HPsquared | Hacker News Reader

If there isn't much movement, it's probably a modest increase in bitrate anyway as the codec will see that most frames aren't changing.

View on HN

At that, captured video of these things can be a total pain in the hoop to edit because OBS, Gamebar et al will write them as variable framerate files, only writing a frame with a suitably distant presentation timestamp when something changes.

And this will make most NLE software shit its legs off.

Improve software? It's job is to serve video editors, not the other way around. And it's a fun task, I bet there might be a dev or two who's working on that right now. And if someone is ready to pay for them, even better.

There is absolutely no reason for any sane video editing software to be able to read VFR files.

It should, however, reject them gracefully but positively.

I read that last bit in Hank Hill's voice.

We sell codecs and codec accessories.

Of course there is. A lot of older TV shows are effectively variable frame rates when properly detelecined/deinterlaced. And mixing two fixed frame rate sources with different framerates would naturally produce a VFR video and with current editing software you need to destroy some of the source information or interpolate some slop to make it work. There is no good reason for editing software to have these limitations either when most players and all modern video containers have caught up and are VFR-first with a fixed frame rate hint in the headers if you're lucky.

> A lot of older TV shows are effectively variable frame rates when properly detelecined/deinterlaced.

How do you figure that?

Broadcast TV is very very very very firmly locked to 25 interlaced frames per second (or 29.97ish in the US where they have to do everything with funny numbers), interlaced to 50 (59.94 US) fields per second.

How could that in any way be VFR?

Reply on news.ycombinator.com