yea but … i make 1 tv version that most people watch in SD(because its free) with “true motion” and AI upscaling anyhow …
and 400 “social” and “web” assets.
so if you have to decide on what should get the main attention, in my book thats not broadcast TV anymore… can always do a 50i version but stay (and shoot) 30fps for everything else.
Especially on stuff that doesnt even get broadcasted, which is … the bulk of what I do nowadays, its all… web, social, whatever.
I also was at a friends place with some kind of IP-TV receiver from german telekom , it outputs 60i to his TV
Lots of markets are making 25fps content and broadcasting in PAL still. Australia and New Zealand are two, as well as the UK. Sure, it’s digital broadcast but it is still PAL and the majority of broadcast channels are still only SD, not HD.
I don’t understand why interlaced pictures are still a thing considering there hasn’t been an interlaced panel created in well over a decade (probably close to 2) but anyway…
Conceptually I agree. In a global content economy and no analog distribution and circuitry left, there is little reason not to standardize on a single frame rate to avoid the quality issues of mismatched rates.
Of course if you add politics and national identities into the recipe, unlikely to happen. Look at the Euro.
PAL is definitely not going to be dead anytime soon. We’re still writing checks in the US, and y’all are still spelling Color with a U so buckle up @finn.
@andy_dill We could do 24 / 48 / 96 to keep everyone happy and the math easy.
24 - film
48 - tv
96 - games
Any conversion just relies on frame duplication or averaging, no fractional frame time stretch / optical flow. Of course the motion blur would still be based on the acquisition frame rate.
My only hesitation would be all the extra storage and processing for 48/96. In games the renders are real-time, for the rest it’s extra frames on disk, extra frames in every single stage of processing, roto, tracking, etc.
Ok, but why do you want work 16% more per second, tracking, rotoscoping…, ? … and 60fps (or 50), oh god, what a nightmare.
Seriously, the problem is conversions, or bad conversions, like the ones you posted (what a botch job). For short jobs I’ve always been a fan of taking a sequence frame by frame, and yes, end up with slightly different durations and compensate in other ways. Otherwise, there are now good tools to generate fluent tw (not just in flame and our beloved twml).
Since it’s a standard electrical thing, it’s simply an unsolvable problem that will never change, so I don’t think it’s worth getting upset about it.