[libcamera-devel] [RFC 0/4] libcamera: Replace CameraConfiguration::transform

[David Plowman]

Hi everyone

Thanks for that message. I think it's very helpful to quote the source
documentation:

 * The transform is a user-specified 2D plane transform that will be applied
 * to the camera images by the processing pipeline before being handed to
 * the application. This is subsequent to any transform that is already
 * required to fix up any platform-defined rotation.

What this is trying to say, badly, is that the transform you request
is applied after ("subsequent to") fixing up the platform rotation. So
you do indeed get auto-correction. This is also the actual behaviour
of the code on the Pi, has been for, I don't know, nearly 2 years? At
this point, the earth does indeed get my official permission to
swallow me up for not writing something that was less prone to
misinterpretation,

But I think this does leave us in a position where large amounts of
this thread are a mixture of not very helpful or even plain confusing,
and with people's permission, I'd honestly like to start again, with
everyone on the same page.

You might have noticed that "orientations" were really bugging me as
to what they were, and how one could use them. I've managed to resolve
these problems in my own mind and think that there's a very simple
connection between "orientations" and "transforms" that I would be OK
to implement and use. I think our next attempt at this discussion
should start by being clear on our requirements, and then we can look
at how "orientations" and "transforms" can get us there.

(Rest of thread purposefully deleted... hope that's ok!)

Thanks!
David