Am 10.11.2014 um 15:41 schrieb Carl Hetherington:
OK. What would keeping the aspect ratio from the pixel AR always
present look like in practice? Where does it appear in the user
interface that DCP-o-matic is treating all pixels as square?
I'm loosing my ground here ;-) I guess what I thought of initially was a more
universal approach to non-square pixels. E.g. if we'd had (rare...) a file with 2x
anamorphic stretch, like classic scope.
They way you are doing it now is that you need an existing/fitting 16:9 scale factor to
deal with the non-square pixels, so currently DCP-o-matic can only deal with square or
16:9 non-square.
If e.g. you'd come across a file with 1:2 pixel aspect ratio, you couldn't deal
with it, because there is no suitable scale factor in DCP-o-matic - every other non-square
pixel AR would need it's own scale preset in order to handle it.
If you'd have a way to correct the incoming file with it's flagged AR to square
pixels, you would not need to have a dedicated preset scale factor to adjust it.
Is that clearer? I know that currently this is of little practical relevance, that's
why I offer to pull out until someone comes across a file which DCP-o-matic can't
handle properly ;-)
Hmm, maybe this could be it - Instead of 'Scale to 16:9', or in addition to it,
offer a 'Scale to content AR' option? Then that could be any pixel AR, not just
non-square 16:9, and make this the default behaviour.
- Carsten