Blackmagic Forum

Hi,

A project I'm working on right now, has a lot of clips which are partly offline in Resolve.
The video of these clips is offline after 3 minutes, 58 seconds and 5 frames.
The audio is still there, but the video is offline from there.
The clips all play fine in Avid Media Composer and VLC. But when I import the same clips into Resolve most clips longer than 3:58:05 have the video offline after this length.

Here are some details:

OS Windows 10
The clips where all recorded with a Panasonic GH5 in 1080 25P
Linked in Avid Media Composer
Transcoded to DNxHR HQ in Avid Media Composer
The external harddrive is formatted in exFAT (editing will be done on both Windows and Apple systems)
Editing will be done in Avid Media Composer, grading in Resolve
Moving the clips to a NTFS formatted drive gives similar result
Resolve 17.2 build 11 and an earlier beta version of Resolve 17 gave similar results

Anyone who has had this aswell?

Are the original clips correct in Resolve?

Jim Simon wrote:Are the original clips correct in Resolve?

That's something I'll have to check. I don't have the origional source clips at this moment. But I will ask for them, and will post my findings at a later stage.

Since the GH5 records in a H264 or H265 codec I would like to have the media transcoded to a edit and grade friendly codec in Avid Media Composer. Right now they choose DNxHR HQ, I'm thinking of redoing the transcode to DNxHR HQX (10bit) if all the source clips are recorded in 10 bit. But would like to do that in Avid Media Composer as that is our editing platform.

Ofcourse there are other ways to get my sequence into Resolve for grading, but my preference would be to use the transcoded media from Avid Media Composer.

Someone will surely amplify or refute this comment.

My vague recollection about the older FAT32 file system was that there was a size limit to the files of about 4gb give or take. Longer casptures and exports would fail in an old Premiere version. There was some sort of trickery called concatenation to make camera files which spanned this limit work.

I assume that the exFAT file system solves this issue but that chunks of data remain sized at about 4Gb. I wonder if due to some technical mismatch in softwares due to legacy file support, that the vision hits a wall when that 4Gb limit is reached and some tie across the limit is broken by the transcoding.

I am really only guessing wildly so please do not pay too much heed.

robert Hart wrote:Someone will surely amplify or refute this comment.

My vague recollection about the older FAT32 file system was that there was a size limit to the files of about 4gb give or take. Longer casptures and exports would fail in an old Premiere version. There was some sort of trickery called concatenation to make camera files which spanned this limit work.

I assume that the exFAT file system solves this issue but that chunks of data remain sized at about 4Gb. I wonder if due to some technical mismatch in softwares due to legacy file support, that the vision hits a wall when that 4Gb limit is reached and some tie across the limit is broken by the transcoding.

I am really only guessing wildly so please do not pay too much heed.

Well to be honest, something like that was my guess aswell. The files which I'm trying to open are all single .mxf files which are bigger than 4 Gb. With other projects I've never had these problems, now the difference is that the files were generated/transcoded on an exFAT drive.

Neither exFAT nor NTFS have the 4GB limit. I don't expect that'll be the explanation.

My notion was that there might have been some leftover legacy FAT32 facility as a bug in the originating software which broke the vision file at 4Gb n Resolve.