davinci resolve freeze frame mutes audio

Oddly, Resolve doesn’t store the native frame rate anywhere in the project once we’ve changed it, so adding the native frame rate to the camera notes will help us reference it when needed. Logging Metadata Native Frame Rate MetadataĪfter we change the native frame rate, we should add metadata to the clips or “log” the native frame rate in the camera notes of the metadata field. Unfortunately, since 25 isn’t wholly divisible by 23.976, speeding these clips back up to real-time will lead to visual stutters and skipped frames. Now, if we wanted these clips to play back closer to real-time (while still conforming to the project’s assigned frame rate), we would need to increase the speed of the clips to 104.27 percent in our timeline. There won’t be any dropped or duplicated frames, but motion might look a bit different. Since 25 frames per second is a faster frame rate than 23.976, these clips will now play back slightly slower. In the Clip Attributes dialogue, select 23.976 as the Video Frame Rate and hit ok.

Now select all the clips with a frame rate of 25, right-click, and select Clip Attributes. If you click on the FPS column of the list view you can sort the clips based on their frame rates together. In this project, we can see that Camera A has files running at 24fps, and Camera B has files running at 25fps frames per second. As a reminder, we set our project to 23.976, so we need to find all the clips with a different frame rate. Open each of the camera bins we created in our project. Since we’ve already organized our clips into separate bins based on camera, it should be easy to find non-matching clips. Now let’s walk through the exact steps of changing clip attributes Resolve. You should leave these types of clips and their audio at the native frame rate, and utilize frame interpolation instead (which will be covered later in a later section). Just changing frame rate with clip attributes will make the audio unusable. It’s important to note that changes to a clip’s timecode will cause audio sync issues if the audio file’s timecode is different from your project’s frame rate. Conforming frame rates causes significant divergence between the native timecode and the conformed timecode, even though the number of frames is the same. This is important to keep in mind as you start to change frame rates of your source clips. Since timecode is generated based on frame rate, changing the frame rate in Resolve will require new timecode to be generated for the source clips within the project. So, if you have a clip with a native frame rate of 29.97, and you change the frame rate in clip attributes to 23.976 to match the project, that clip will play back slower than its native frame rate in the sequence.Īlso keep in mind that the timecode of the clips within the Resolve project will no longer match the timecode embedded in the source file on disk. When you change the frame rate in clip attributes, higher frame rate clips will play back slower in a lower frame rate project. The recorded number of frames in a file won’t change.

Of course, when we change the frame rate in clip attributes, we’re not actually altering a clip’s files, we’re simply telling Resolve to play back the files with a different frame rate.

We can change the native frame rate of clips in the clip attributes settings to match our project settings. This example is intended to give you a good idea of this workflow option, but keep in mind that your project might have different needs or requirements than my example here. In part 2 of this 5-part series, I’ll walk through a scenario for why and how you might want to change the native frame rates of the footage before editing.

Davinci resolve freeze frame mutes audio