This post was last modified: 2022-04-22, 14:36 by magges.

Hi Gunther,

In my workflow, I am juggling with different resolutions for having maximum available resolution and I found something which is really on the level of pixel peeping and most users do not see

E.g. I have an tiff sequence with resolution 5712 x 3213 which is exakt aspect ratio of 16:9 (-> 1,77777777777777...)

When I load this into LRT in the render dialog and the "force aspect ratio" is not checked, it displays there 5712 x 3212 (which is 1,778331257783313)

When the "force aspect ratio" is checked, it shows 5710 x 3212 (1,777708592777086)

I did not check other aspect ratios. Looks like you are probably using a fixed value of 1,7777, maybe 16/9 would be more accurate.

When I render the video without having "force aspect ratio" checked, the video file has the resolution 5712 x 3212, which means one line of pixels is missing although no resizing should be applied.

How I found out: I am uploading maximum resolution with aspect ratio 16:9 to a footage portal. They downsize to different resolutions which can be purchased. At the end, FullHD was listed there as 1919x1080 instead of 1920x1080.

Best regards,
Markus

You cannot render video in odd pixel sizes like 3213 - videos here are different from Photos, where this doesn't matter.
Since LRTimelapse is the interface between photos and videos, it needs to do some transformations here to comply with the requirements of the video encoders. That's why certain minimal crops need to be applied when rendering the video.

Oh, you are totally right. Did not have that in mind. Thanks for the info!

By the way: I wanted to post this in "Bug reports"...

It's not a bug that's why I moved it.