The recorded ProRes file has a 00:00:00:00 timecode 'track' embedded which I need to 're-stripe' with a simple ffmbc/ffmpeg based tool.Īctually, I've discovered the easiest way to achieve both reliable TC and Reel numbers was to re-transcode the ProRes to ProRes - a process which is nearly as quick as a re-wrap and creates a perfect file only very slightly larger than the original but with zero deteriation. MTS as my camera now records to a third party ProRes recorder but I still need to process the ProRes files post shoot to include TC and Reel numbers as my camera does not generate either. It is a long time since I have worked with native. The additional disk space and time required was easily off set by these advantages however CPUs have become faster & cheaper so I see your point. MTS if only to achieve:ġ) easily editable I-frame codec which uses less CPU power I've always recommended users to transcode. I'm rewrapping files with ffmpeg (-vcodec copy, -acodec pcm_s16le, and extra reel/timecode options set). I'm using Lightworks 12.6 64-bit (Release, build 82375 dated Feb 3 2016), Linux version. Is it possible to fix this in next release or bugfix release? This is not possible until original files have no timecode/reel names embeded properly, but after rewrapping to MOV container the data exists but Lightworks can't read them. After very quick rewrapping we could easily transcode to proxies/intermediates, we could do edit, and just before delivering we could import the original files, avoid recompression (a potential quality loss) and avoid extra transcoding step when working on proxies. The benefits of embedding timecodes and reel names in rewrapped files are huge, because the most important data for the LWKS workflow are embedded directly in video files. Lightworks can read timecodes and reel names when MTS files are transcoded to ProRes. Lightworks can't read timecode nor reel name from rewrapped files. MTS rewrapped to QuickTime with timecode and reelname embedded contains these data for sure.ĭavinci Resolve, Premiere and ffprobe can read timecode properly from rewrapped files. I can extract timecode data from H264 and set reel names manually. MTS files contain timecodes but stored in a non-standard way (a specific H264 meta data MTS has no timecode track). The original files from my cam (Canon C100) are ACVHD (H264 in MTS container). PAL 50 (720/1080p 50, for editing use PAL 25)ĭF 59.94 (720/1080p 59.The problem is that Lightworks can't read timecode/reelname metadata from QuickTime files (MOV), until they will be transcoded to ProRes. Time code operations include adding, subtracting, multiply and dividing and time code types can be switch during operations without losing the current frame value.įilm 24 (720/1080p 24, p 23.98, psf 24, psf 23.98, 2K, 4K)ĭF 29.97 (NTSC, 720/1080i 29.97, 30, 59.94, 60) Time codes can be displayed as frame values or standard time code strings. It supports all the major frame rates (23.98, 24, 25, 29.97, 30, 50, 59.94 and 60) as well as drop and not drop frame time codes. TcCalc is a film and video time code/timecode calculator.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |