30 Apr
2019
30 Apr
'19
4:36 p.m.
Just to thrown in my two pennies on one point...
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.
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???
As ever, massive big up for your tireless work on DCP-o-matic Carl.
Can't wait for 2.14.0.
Jim
I was trying
to get Carl to set the video display optionally to the same size (or integer mutiples) of
the actual decoded resolution, so to avoid scaling. Using the
mouse and window resize elements, it is impossible to set it to a specific viewport
resolution like 999/540 for half-flat.
So far, he hasn't been triggered by that idea. Maybe he missed it where I mentioned
it. Maybe I should file a Mantis entry for it.
At this stage I'd rather fix it
"properly" rather than spend time on
things that feel like hacks (unless there is a utility here that I'm not
seeing).