Cannot Read Trimmed Alexa35 Clips From Media Management

For the last two jobs I have had on that was shot on Alexa 35 (mix of raw and prores4444XQ) I have had issues with media management.

When I copy and trim the media like usual - resolve does generate the trimmed files, but those files can no longer be read in resolve. It opens up fine in quicktime etc on the mac.

Version 18.6.5

Example of a trimmed clip that I cannot get to import into resolve:
https://www.dropbox.com/scl/fi/eybgj8zk ... s0urk&dl=0

Never had this issue in the past - especially with prores.

[Dwaine Maggart]

I don't see an issue with 18.6.5. Are you sure that's the version the trim happened with?

And it happened on an Intel Mac?

If so, what type of file was the source file this was trimmed from? Codec type and resolution and frame rate? As displayed in the Resolve Metadata window.

Hi Matt and Dwaine,
I had a look at it and that clip doesn't import to 18.6.5, neither on Apple Silicon nor Intel.

There is a workaround as long as these are ProRes: re-wrap them into MOV, which is lossless and fast, then they can be read. Of course, it's up to BM to fix the issue.

P.S. I'd also suspect they have been trimmed on an older version.

I don't see an issue with 18.6.5. Are you sure that's the version the trim happened with?

And it happened on an Intel Mac?

If so, what type of file was the source file this was trimmed from? Codec type and resolution and frame rate? As displayed in the Resolve Metadata window.

Hi Dwaine,

It was an Intel Mac Pro - Sonoma 14.3.1
It was definitely done on Resolve Studio 18.6.5 Build 7

Original File:
.MXF
Apple Prores 4444XQ
24.000 fps
4608x3164
Audio - Format 2, Linear PCM, 48,0000Khz

I can send a camera original is here (10gb):
https://www.dropbox.com/s/as1a3p9v03p1y ... L.mxf?dl=0

May take a while, even on optical fibre. I'll give it a try.

OK, half an hour, internet is in good mood.
Trying to trim the timeline with the .mxf clip results in this:

Bildschirmfoto 2024-02-27 um 10.41.36.png (113.27 KiB) Viewed 945 times

Gave it a try on a version re-wrapped to .mov too. This one got through, but the colourspace is not recognised any more and the in/out points get lost (I had set handles). Definitely needs some work, Dwaine.

Gave it another try, I had some Arriraw lying around. Interesting result: it's trimming just fine (timeline trim), and the resulting timeline is identical. Both of our cameras were on firmware 1.02.00.
So, the issue seems to be limited to ProRes.

Thanks for testing Uli.

I get an error also.

It has happened now from two different shoots on arri 35 (so different cameras, drives etc.) in the last week or so.

[Dwaine Maggart]

Yeah, I've repro'd as well and reported. Happens all all platforms with the same error.

I'm thinking the issue might be specific to the 4608x3164 resolution, because I have an Arri MXF ProRes444XQ file at 4448x3096 and it trims with no issue.

Please see above, I added a test of Arriraw (4608 by 3164). It was in 25 fps, though.

Yeah, I've repro'd as well and reported. Happens all all platforms with the same error.

I'm thinking the issue might be specific to the 4608x3164 resolution, because I have an Arri MXF ProRes444XQ file at 4448x3096 and it trims with no issue.

Hi Dwaine,

I am also having this issue today with 3072x3072 24FPS Prores4444XQ .MXFs from the Arri 35

Issue Still present in 18.6.6

Same here. Came across the same issue creating trimmed files from Alexa35 MXFs.
I was testing with older Alexa35 footage (this one was anamorphic) and it throws the same error as Ulis.
This is really annoying with tight deadlines and turnarounds to the colorist.

Sending everytime 1-2TB via MASV or something else is not practical. Trimmed would be about 100-200GB.

Has anyone found a fix or workaround for that?

[Dwaine Maggart]

This is fixed in the Resolve 19 beta code, FWIW.