Convert 23.98 to 25 timecode calculator4/18/2024 ![]() However, when changing the frame rate on import (or after import), say to 29.97 fps, the result isn't correct. ![]() With unchanged frame rate on import it show the same timecodes as 2021.3 and Resolve. Now, with build 139778, it auto detects the frame rate from the BWF metadata of the shared clip on import: The sequence is 'anchored' to video frames.Įxpose the the sound media samples alone to a bunch of fps options - and one would guess each change of fps triggers a complete recalculation of samples - hence the seemingly strange timecode results.īack on this with feedback. The original 'frame rate' was 23.976-ND but of course sound has no frames - it has samples.Īdd video or LW generated video black to a sequence with the - change the frame rate of the sequence via the sequence playback format to a compatible format - all is normal. wav a possibility with user error it has changed frame rates in that process but that's doubtable. It's been converted from a Zaxcom MARF file to a. Track 1 is called 'Party MIX' probably a composite used for picture editing, 2-4 are solo mics for later sound work ![]() Some users know not where to go other than ill founded abuse.Ī quick look at the file itself shows it's been recorded on a Zaxcom Deva 5, one of our long standing sparring partners. However, the timecodes are fully off the rails.Īs reference: DaVinci Resolve shows the expected values and autodetects the embedded frame rate:Īssuming that Lightworks still targets commercial markets, at least partially, I don't understand how such an issue can survive internal pre-beta tests? When using the import tool to import, the frame rate isn't properly detected as well, but the changed frame rate carries over. You will see this:ĭelete the clip and drag and drop again, but now, change the frame rate to 23.98 on the panel.Īfter a closer look, you will recognize that it's the same as above, meaning the change on the panel was not effective. Drag and drop the clip into the GUI, same thing, it shows 30 fps instead of 23.98. ![]() It says 30 fps (the project default), but it should say 23.98 based on the metadata (LW 2021.3 show it correctly). Use the current release and from the Import context, set 'Behaviour->Default frame-rate' to 30 fps. It contains time reference and frame rate (23.976 fps) in its BWF metadata. To test, use the audio-only clip attached below (It should be know, because shared in a bug report on missing timecode by johngeronilla in 2019). ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |