Just wondering how IW3 calculates the width of the depthmap

[RudiRastelli]

Let's assume we have a source video with a 1920x1080 resolution (aspect ratio 1,777...) and the depth resolution has been set to 518.
I further assume that the aspect ratio of the depthmap should be as close as possible to the aspect ratio of the source video.
(Keep in mind that both width and height must be divisible by 14)

A simple formula:
Width of depthmap = Width of source video / Height of source video * Depth Resolution

In this case:
1920/1080 * 518 ~ 921
To get the most accurate result divisible by 14 :
Round(921/14) * 14 = Round(65,78) * 14 = 66 * 14 = 924 (aspect ratio 924/518 = 1,784)

But IW3 calculates the width as 910.
So to me it looks like IW3 simply truncates the decimal places, which then leads to a greater inaccuracy:
Trunc(921/14) * 14 = Trunc(65,78) * 14 = 65 * 14 = 910 (aspect ratio 910/518 = 1,757)

I have no idea whether this matters or not. I just noticed it.

[nagadomi]

Yes, I am not too sensitive about that. It's using floor()/int() instead of round() as you pointed out.
For ZoeDepth, the calculation is even more complicated because of the use of padding.

I will change the code related to that when I fix #256 problem, so I may fix this then.
One problem is that the depth image size is used as is for export, so fixing this would break compatibility of the export feature.