Bruno Centanaro

Is that information in the format or device object? If that's the case you can pass an extra object in each frame processor plugin call (the second param)

Hello. I've looked into the `PreviewView.kt`. One thing I do not understand is why the `CameraDeviceDetails.getMaximumPreviewSize()` is used for the aspect ratio in `getSize`. Using the `contentAspectRatio` instead of `containerAspectRatio`...

Sorry, I messed up, as for my first message, it was containerAspectRatio instead of contentAspectRatio and not vice-versa. Nevertheless now that i get the intended use I think that's correct...

That PR does cause the onMeasure to re-run, but it is strange because the preview is still stretched. This are the logs without my aspect ratio change > 2024-02-19 10:19:08.709...

Yes, to be honest the widthOverHeight I did not test it as its false for me

The operators there are correct I think. For anyone who has issues and is sure the aspect ratio of the camera container is the same as the resolution's one this...

It seems as your container aspect ratio might not be the same as the video preview (set on the format prop)

The aspect ratio of the preview is the same as video, not the picture one, also the fact that you use an aspect ratio in the format does not necessarily...

Same for me, were you able to find a fix?

Are you running it on a device later? Because my issue is not compiling/building but if I run it on a physical device