[Michael Gissing]

It makes no sense for a camera to ever use the same file name again. RED, Arri, Blackmagic etc make sure that can’t happen.

[Michael Gissing]

There are camera manufacturers out there that have made cameras that repeat file names. No idea why that is even possible when unique names are always required. DJI, certain Sony’s, certain Canon’s etc

Before editing, duplicate file names need to be identified and renamed. File rename software makes it easy to rename a whole folder and add a suffix or prefix which might be the date and camera ID (handy if it’s a multi cam shoot). All copies of the camera originals should be renamed if they have already been duplicated. It really matters that files do not duplicate, especially as they so often also duplicate timecode.

Once you have started editing it is a problem to rename files as you will break the link. I’m talking about the files on the drive, not names in Bins. Renaming in Bins only helps to a degree. If you have to move to another computer or have a crash and have to rebuild, you will struggle with those duplicates. Handing over to a facility to grade & mix – same issue with duplicated files. It’s the bane of my existence.

[Michael Gissing]

This is the one I use. It’s for Windows https://www.advancedrenamer.com/

I don’t have a Mac recommendation

[Michael Gissing]

I guess in a few more years AI will do shot recognition and find files that have been renamed.

At least you have the joy that the renaming during the proxy creation was a simple prefix. Here’s what I would do to fix this mistake. Using file rename software, add the same prefix to a copy of the camera originals. I hope the prefix is fixed per folder so you can batch add that prefix.

Pre import the renamed files into Resolve so it doesn’t go looking for proxies by unticking the automatically import files option when you load the AAF. Unless you have made the fatal mistake of not matching timecode with the proxies, you should get a perfect relink (well it is so rarely 100% perfect).

[Michael Gissing]

I guess this will spell the end of the Hackintosh. It also would make me nervous about how long I could run an expensive shiny new Intel MacPro before having to stay put on an OS that worked and forgoing any software updates for popular apps as a result.

That said I think Apple are smart to do this move to ARM. Apart from having more control and lower power for laptops, it will annoy the hell out of Adobe, Blackmagic and AVID to have to support an OS running on very different hardware.

Meanwhile I’m weighing up my options to do a PC rebuild and maybe run Resolve on Linux. Apple is even further away for me as an option.

[Michael Gissing]

Typically I use three nodes when using a LUT. Node 1 is for pre LUT trimming. Node 2 is the LUT. Node three is the post LUT trim. Very normal to set final white & black levels after the LUT but often need the node pre LUT to avoid clipping or crushing (highlight, shadow recovery etc). I also sometime do a basic balance pre LUT then finesse post LUT. After that whatever else I need to tweak I add more nodes.

[Michael Gissing]

Have you tried to paste various files into another timeline and see if there is a particular file causing the timeline to have delay? With a combo of file types including image sequences plus possible frame rate differences, I would suspect there is a particular file that might be causing issues. Isolate one by one to see or it may be a combination of two file types that trigger the delay issues.

And it’s always worth checking that your preferences are correctly set to match your GPU. I would set for CUDA and not let auto options decide for example.

[Michael Gissing]

What codec is the clip? It may have been rendered using a codec with alpha which might explain why things are changing in the timeline from the preview.

Check the clip attributes and let us know what sort of codec and clip settings Resolve is dealing with.

[Michael Gissing]

I had this happen a couple of times. Two tricks to face refinement. I often zoom the image up to do the analyze pass so the face is full in the frame. Sometimes it has trouble picking up a face. Once the analyze is done you can reset your framing.

Second trick and the one that will help you is to do the analyze with a few frame handles. I just extend the clip top & tail a few frames then re-trim after the analyze pass. That should solve your issue.

[Michael Gissing]

I would start with the manual. Resolve uses a database to store the various projects on your system. This database usually lives on the system drive. What you need to understand is how to back up the project files (.drp) from that database to the external drive to transport the project back to another system.

I also suggest you discuss this interchange with the editor at the agency who is supplying you the drive and media. There are lots of basic training videos on YouTube by practitioners like Casey Farris, JayAre, Meisner media etc. You want to get the understanding of setting things up right from the start. I so often see people jump in and assume the system defaults work perfectly for everyone.