- Posts: 29
- Joined: Fri Feb 07, 2014 8:47 am
Wed Feb 25, 2015 2:16 pm
Resolve 11.1.1
We are finding that when we bring in separate audio material that has been delivered as non-broadcast wave files from the audio house, without explicit frame rate information embedded in the meta data, the .wav file is assumed to be 23.98 FPS and is retimed as such when applied to the timeline. So if on a 25 FPS timeline we bring in nonbroadcast wave files that match the picture in a 25 FPS environment, the audio is automatically retimed to be 4% shorter (assumed to be 23.98) and so on the Resolve timeline does not run in sync, and I have not been able to find a way to force the audio wave to behave differently.
Does anyone have a workaround?
Scott
We are finding that when we bring in separate audio material that has been delivered as non-broadcast wave files from the audio house, without explicit frame rate information embedded in the meta data, the .wav file is assumed to be 23.98 FPS and is retimed as such when applied to the timeline. So if on a 25 FPS timeline we bring in nonbroadcast wave files that match the picture in a 25 FPS environment, the audio is automatically retimed to be 4% shorter (assumed to be 23.98) and so on the Resolve timeline does not run in sync, and I have not been able to find a way to force the audio wave to behave differently.
Does anyone have a workaround?
Scott