MLV App Transcode and Import RAW2MLV produces wrong resolution

Started by tdbartley, September 08, 2022, 02:13:41 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

tdbartley

I am trying to make a time lapse using MLV App's Transcode and Import feature. The input files are raw images from my 5D3 with full 5760x3840 resolution (3:2). However, after import, the canvas shown in the Transformation tab becomes 5792x3870 (Clip Information also shows 5792x3870). So not only has the resolution changed, but the aspect ratio has also been subtly altered.

I expected the canvas to be the original 5760x3840 resolution. Is this a bug, or is there something I am not understanding about the RAW2MLV process?

Walter Schulz

5D3's sensor actually has a few "spare" pixels.
Are you sure about the exact numbers? I found "5796x3870".

tdbartley

I can confirm that the .CR2 raw files show 5760x3840 in file properties. After transcode and import, MLV APP shows 5792x3870. It would surprise me if there are spare pixels hiding in the raw file that are not reflected in the file properties. At the same time, I can't see any obvious artifacts in the stretched image, so it at least does not look bad. It is a mystery to me where those extra pixels are coming from. Maybe RAW2MLV is resampling.

A single .CR2 is enough to reproduce this result, and I am including one here.

https://www.dropbox.com/s/my9iiygoxnbbi9q/3V1A0328.CR2?dl=0

I am using Windows 10 and MLV App v1.14.

Walter Schulz

Quote from: tdbartley on September 08, 2022, 06:53:21 PM
It would surprise me if there are spare pixels hiding in the raw file that are not reflected in the file properties.

Time to be surprised, then: Please open your CR2 and look for exif tags "SensorWidth" and "SensorHeight". You will be surprised by their values:

SensorWidth 5920
SensorHeight  3950

If you lookup 5D Mark III specs you will most likely find "Sensor pixels 22 Megapixel (effective). If you are lucky you will also find a second number "23 MegaPixel". Now do the math ...

You are also confusing CR2 and MLV.
MLV is not the same as CR2! It grabs its contents from liveview buffer and that is 5792x3870. Nobody has claimed your CR2 doesn't have 5760x3840! Yet. Because it has 5788x3862. Download RAWtherapee and open your CR2.

Altogether: Converted DNG is not stretched!

tdbartley

Yes, I can confirm in the exif metadata:
SensorWidth 5920
SensorHeight 3950


And looking at RAWTherapee shows 5788x3862 as you say.

So including file properties (5760x3840) and the MLV generated by RAW2MLV (5792x3870), now we have four different values and none of them match. I'm sorry to say it, but now I am more confused than ever.

QuoteYou are also confusing CR2 and MLV.

The only data coming off the camera card is the .CR2 file. The MLV is generated by RAW2MLV.

QuoteIt grabs its contents from liveview buffer and that is 5792x3870.

How is this possible? Are you saying the contents from the liveview buffer is stored inside the .CR2 file?

I'm sorry for the trouble, I'm just trying to understand the process to ensure IQ is preserved through each step. If you say it is all correct and as expected I will trust you.

Walter Schulz

Ah, I get it. It is time to ask the mage himself:

@ilia3101:
1) Question about resolution. You are generating MLV with 5972x3870, right? Shouldn't it be 5976x3870?
2) What are you doing with pixels not represented in CR2? 5788 -> 5972(5976) and 3862 -> 3870? Just paint it black? Just for curiosity ...

ilia3101

Sorry I don't get notified.

Raw2mlv is giving you as many pixels as possible (without exposing the raw file's black borders), according to information provided by libraw... which might still be underreporting the actual size of the image area, but bettwr safe than sorry.

The official 5760x3840 size is slightly cropped in.

So yes, there are spare pixels.

You can't resample raw files.