As far as I know, they got it straight from the camera.
Oh, When I receive the footage, I have to request it without audio, right? I can’t remove just the audio because the clip information is not visible in Flame.
What you’re saying makes sense… is there any way you could post a clip so we could see what the issue might be? We might have better luck steering you in the right direction if we know exactly what we’re working with.
I work with arriraw a lot, and we usually ingest it via the arri reference tool as it gives you more options and higher quality debayers than both flame and resolve, that said I havent had any issues with arriraw other than that you cant publish arriraw with a colortransform without stuff crashing… I think the ALF4 stuff is not the issue, i would send a file to Autodesk as well, or to someone here, happy to test on my flame, maybe its some SUP upgrade thats not compatible with your 2025.0? arri SDK or something stupid
the software on the used alexa35 was released on June first 2024.
Flame 2025.0 was released on April 14th 2024 , so … that might be just a hint of why it might be incompatible 
even if there is nothing in the changelog, it should now read the arri SDK in the media hub thingy, mine on 2025.2 says…
Which is the same SDK as released in like flame 2024, so i dont think upgrading will help here, I am trying to find a clip that has been recorded with SUP 1.30 but everything I have seems to be older than that… interesting!
Ok found one I had with a ever newer software update and it works fine…
so yea no idea, but yea please PN me one of the files and I am happy to give that a go!
Yes, I am sharing the file that you can use for testing.
Thanks for your help with the issue. And I have confirmed that the file appears normally in Nuke. 
https://drive.google.com/drive/folders/1V4uZqFWcG1vCmxXjLMkZiLZ0J4bShbwK?usp=drive_link
1 Like
Not sure what Finn has come up with, but the best I can do is load it into ART (Arri Reference Tool) and re-export as OpenEXR Uncompressed Scene Linear/AWG, then load that into flame as ARRI wide Gamut 4. Although it seems to have misinterpreted the aspect ratio. I believe ART can do this in bulk to multiple shots.
I’ve also looked at Alexa35 footage with older and newer Software updates and one clip that is HDE codec and Software version 1.3.0, which is the same as the problem shots, and all load fine. Out of the 4 shots, the problem shot is the only one with Enhanced Sensitivity Active. I have no idea if this has anything to do with the problem.
2 Likes
Hi,
It seems the ARRIRAW Picture Coding line is quite suspicious. Typical files are either 12-bit or 16-bit, but yours shows 13-bit. It appears that Flame may not recognize 13-bit camera files directly. You should consider converting the file using the ARRIRAW Tool or Resolve.
1 Like
All of my shots that are Alexa35 Arriraw are 13bit and load fine. I think there is some sort of corruption in the metadata. Conversion in ART to Arri Log4 seems to be the solution. The only thing I found unique to the problem shot compared to the 3 I have that load is the Enhanced Sensitivity is active. I have some time to kill today, so I might take a look at some of the samples Arri provides and compare.
EDIT: I found a sample with Enhanced Sensor active and it loads fine. So much for that idea.
1 Like
Please open a ticket with our Support team.
1 Like