|
|
This topic comprises 10 pages: 1 2 3 4 5 6 8 9 10
|
|
Author
|
Topic: Gemini Man - HFR Test
|
|
|
|
|
|
|
Antti Nayha
Master Film Handler
Posts: 268
From: Helsinki, Finland
Registered: Oct 2008
|
posted 03-22-2019 04:14 AM
I was recently teching a documentary film festival with a total of 85 features. We received not one, but two HFR 2D DCP's – one 48 fps and one 50 fps.
I'm still not convinced of the benefits of HFR for fictional films, but based on these two, I could easily see this becoming a thing for documentaries. Both were "true" HFR, shot in at least 2K progressive instead of interlaced HD.
One of the films (Walden) was an avant-gardish, meditative piece that consisted of an endless slow pan across a forest, showing people chopping wood and going about their daily chores. The 50 fps framerate allowed the audience to see all the detail and action clearly, even though the camera never once stopped panning.
The other (Aquarela) had been shot at 96 fps, and according to what I'd read, the director was severely disappointed when Sony refused to distribute it as a 96 fps DCP. I didn't watch the whole film, but at least the drone-shot landscapes had a very nice smooth but high-budget look even in 48 fps. Had I seen the same rather impressive opening shot in a fiction film, I would probably have lost all suspension of disbelief right away… but that doesn't seem to be an issue for documentaries, at least not in the same way.
As for the general audience, no one seemed to be distracted by the HFR in any way, unlike the Hobbit 3D HFR screenings.
Of course, we screened Aquarela in a venue that could just as easily have run 96 fps. Thank you, Sony
quote: Carsten Kurz The tech bulletins issued for Billy Lynns Long Halftime Walk claimed that all HFR DCP versions were done at 250MBit/s only - even those at 120fps.
I don't know if the Gemini Man test footage also prototypes the intended datarate.
I was also curious about this and checked them: 2D 120 fps test clip: avg 186.95 Mb/s, max 240.34 Mb/s 3D 60 fps test clip: avg 223.88 Mb/s, max 240.00 Mb/s
quote: Carsten Kurz Note, choking will not only occur due to high bitrates. Some test releases of DCP-o-matic used an OPENJPEG optimization that changed only 2 'irrelevant' bytes in a J2K frame to zero, and that made CAT 862 and 745 choke...
Sorry for the off-topic, but does anybody here have any idea why Cat 862 chokes on some regular 24/25 fps DCP's with bitrates well under 250 Mbps? Most of these problem DCP's exhibit irregular stuttering, as if the film was paused for a fraction of a second every now and then. Others will simply freeze permanently (just like someone clicked the pause button, except that audio may still be playing on) – but I've found out that you can continue playback by manually skipping to eg. one second later, until it happens again after a while.
I've tried to pinpoint the problem several times by unwrapping the video MXF's and inspecting the individual j2k files with various tools, but I've always been unable to find anything out of the ordinary. No single-frame bitrate peaks, no suspicious metadata, nothing. Couldn't find anything useful in the Dolby logs either.
Many (but not all!) of these DCP's/MXF's were created in DaVinci Resolve.
Cat 745 seems to play these just fine, just like all other servers/mediablocks that I've tried. It's just the Cat 862.
| IP: Logged
|
|
Marcel Birgelen
Film God
Posts: 3357
From: Maastricht, Limburg, Netherlands
Registered: Feb 2012
|
posted 03-22-2019 04:55 AM
In general, if you selectively add motion blur in post, the soap opera effect will be mostly gone, yet the ultra-smooth panning will remain.
Even if you add some motion blur to the panning scenes, the smoothness will remain and the amount of detail that's being perceived will usually still be higher than playing it at 24 or 25 fps.
Maybe this is because of how our visual cortex works. If you look at a continuous moving hand without moving your head, for example, you'll see that it's almost impossible to get a sharp picture of it. It very much looks like our brain blurs those pictures together.
If I flash like 48 high-intensity stills without motion blur within a second at you of that same moving hand, our visual cortex is missing the blurry effect. I guess that this is introducing the unnatural, somewhat "sped up" look.
Now, those 48 fps are still well below the flicker fusion threshold of the average human being about 80 Hz.
But what happens when I flash 120 frames per second of that same moving hand without any motion blur at you? The 120 fps should be well above the flicker fusion threshold. So will the brain now "blur" it for us?
| IP: Logged
|
|
|
|
Carsten Kurz
Film God
Posts: 4340
From: Cologne, NRW, Germany
Registered: Aug 2009
|
posted 03-22-2019 05:58 AM
We have seen many of these complaints about Resolve JPEG2000 in DCPs. Many Resolve users seem to think that Cinema servers can eat any JPEG2000, or, that the only use for the JPEG2000 output option in Resolve is playout on cinema servers. But that is not the case. It's a generic JPEG2000 option that does not follow the Dcinema constraints of OpenJPEG. JPEG2000 has very many different coding options.
I guess one would have to be a real JPEG2000 buff to find out the technical reason why these code streams fail.
However, they changed that code in Resolve 14, and in 15.x they now support an internal DCP encoder based on Kakadu, that will certainly keep the codestream within DCI/SMPTE constraints.
Before, people were actually blaming DCP-o-matic for creating bad DCPs, but for JPEG2000 image series or J2K MXF containers, DCP-o-matic is only passing them through, and the original creator is responsible for codestream compliance.
- Carsten
| IP: Logged
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
All times are Central (GMT -6:00)
|
This topic comprises 10 pages: 1 2 3 4 5 6 8 9 10
|
Powered by Infopop Corporation
UBB.classicTM
6.3.1.2
The Film-Tech Forums are designed for various members related to the cinema industry to express their opinions, viewpoints and testimonials on various products, services and events based upon speculation, personal knowledge and factual information through use, therefore all views represented here allow no liability upon the publishers of this web site and the owners of said views assume no liability for any ill will resulting from these postings. The posts made here are for educational as well as entertainment purposes and as such anyone viewing this portion of the website must accept these views as statements of the author of that opinion
and agrees to release the authors from any and all liability.
|