Arri Raw Anamorphic 2560x2145 footage importing at 1080, Square Pixels?

[Department4]

Hey there Adobe Forum! Got a bit of a head-scratcher here.

I'm editing a project that was shot Anamorphic in Arri Raw on an Alexa Mini. The media clips are the RAW .MXF files, NOT ProRes.

When I import one of the raw clips into Premiere Pro (v12.1.2), it claims via the Clip Properties that the clips is 2578x1080 (1.0) (Square pixels). The image looks perfectly fine (no squeezing). This seems odd to me, because being anamorphic I was pretty sure the pixel resolution would need to be 2.0, and the pixel dimensions would be different so I:

If I bring the exact same clip into DaVinci Resolve, the attributes I get are: 2560x2145 (Cinemascope PAR (Pixel Aspect Ratio)).

Now, the DaVinci specs seem accurate to me. My question is: why is Premiere telling me that the same exact clip has different specs than Resolve is?

To compound the problem, the DP is asking me to have my working sequences in Cinemascope Pixel Aspect Ratio (2.0), and export my edit at 3414x2198 Squeezed in ProRes 4444 for color (Colorist would then desqueeze on his end by applying the cinemscope PAR again).

What is going on here? Why am I getting a different reading on the same clip in Premiere as I am in Resolve? Looking at older posts and videos, it seems like typically, when bringing anamorphic into Premiere, I'd need to tell the clips to "Modify>Interpret Footage>Pixel Aspect Ratio 2.0" in order to get my clips looking groovy, but luckily (sort of?) my clips already look great on direct import and I don't need to modify anything.

Anyone's help and insight would be much appreciated! Thank you so much! 

Premiere:

Resolve:

[rodneyb56060189]

https://www.arri.com/forum/viewtopic.php?f=105&t=407

[GRF Archer]

Hi, 

Im looking for an answer on this as i have a simialr issue and the answer below is to an outdated forum post... any resolutions?

thanks

[Ann Bens]

You could interpret the footage to Anamorphic.

.

[GRF Archer]

Unfortunately that doesnt work - the footage in resolve is recognised as
anamorphic (2.0) but in premiere it is square pixels (1.0)

The footage, reported through silverstack / Resolve is coming up as 3424 x
2200 (2.0), which is the correct camera settings required - however upon
ingest to premiere pro it is reading as 3424 x 1100 (1.0) - the image
looks to already be de-squeezed and in the correct aspect ratio, but now
i've lost the height instead of doubling my width.... has anyone
encountered something similar and is there a workaround for maintaining
full height... ?
i'll be using a proxy workflow, so it's not a huge issue roundtripping from
premiere pro to the colourist but i'm keen to figure out whats up... I've
tried both PP14.9 and PP15.1
ann: interpret footage is set to square - I've tried the usual method of
changing to ana2.0 but it distorts the image in this instance...

I normally dont have an issue with any formats from alexa mini, venice, red
- all on raw workflows at high end, but for some reason Premiere is reading
the files as something different to what they are.

For ref, current system spec:
Mac pro 2013 - Mac OS 10.14.6, 8-core Intel Xeon, Firepro d700 6Gb
Tried on both Premiere Pro 14.9 and latest Premiere Pro 15.1
QC'd in Arriraw converter tool 4.2, and Davinci resolve Studio 16 which
both recognise the 2.0 aspect ratio correctly.

does anyone know what the previous forum link reply was in reference to?
thanks

[default91wr7fiufz7d]

Hey,

Did you find any workarounds? I`m trying to generate proxies but I can't find a way to export my footage with full resolution (3.4k)

What a nightmare.

[GRF Archer]

My only workaround for this was to Transcode to Proress4444 in LOG, at the correct size, using Arri Raw converter.

Then create proxies from that new clip in PP / davinci etc.

It means you are slightly lowering the bitdepth but it does allow you to have the full size clips etc for racking....and depending on how the footage is lit / to be graded then its probably nothing too noticable anyway. 

Not sure if this has been resolved in the latest version of PP - worth checking.