3 May
2019
3 May
'19
2:55 p.m.
I do see some utility in this, personally.
If I'm checking a file for quality, I would always prefer to not scale,
or scale by an even factor, to ensure what I'm seeing is as faithful as
possible to the original. For example, on an iMac 5K display I would
watch a 2K file at 3996x2160 (x2 zoom), rather than scaling it up to
full screen.
I don't know if this applies to DCP-o-matic, but I've found when viewing
files in e.g. Premiere Pro, it's hard to assess interlacing artefacts
unless you're at exactly 100% or 200% zoom. At 210%, for example, the
scaling messes with the fields and can either hide any combing, or
massively exaggerate it. Either way, you can't make a proper judgement
of how the file will look when it's projected.
Fair enough; https://dcpomatic.com/mantis/view.php?id=1546
One other thing... I assume the OpenGL you're
talking about is for
displaying image *after* conversion from J2K right? Or are we at last on
the brink of GPU-accelerated J2K encode/decode???
OpenGL is just for the rendering, hopefully to speed it up and possibly to
do the scaling and colourspace conversion on the GPU. Accelerating J2K
encode/decode is a separate thing. I've made some progress on GPU
encoding but the speeds I'm seeing aren't too great; I need to pick the
brains of a GPU expert really.
Best,
Carl