![]() ![]() L&T offers users a preview window for looking through clips prior to ingestion. Yes, this can take a lot of disk space!Ĥ) The L&T playhead is screwy and moving it around can cause FCP to crash. Workaround: Ingest and work in a high-quality ‘online’ format like ProRes 422 HQ from the start so you don’t have to re-ingest, or a format at least as good as that which you want to deliver the project in. This can be a serious issue if, for example, you plan to transcode into a low-resolution version of ProRes 422 like ProRes Proxy for an ‘offline’ edit and then reconform the project by re-ingesting the footage for a final ‘online’ edit at higher quality FCP will not be able to find the points in the original files to ‘know’ which sections of those files to re-ingest because the timecode in the transcoded footage is not the same as that in the ‘parent’ AVCHD files. Each clip, after transcoding, has timecode starting at zero. Workaround: It’s not 100% reliable, but if you make sure to remove all AVCHD clips from the L&T clip menu before closing L&T they tend not to reappear next time you open the tool.ģ) L&T does not bring the source timecode of the clip through when transcoding. This can be a real pain in the rear end because it can take ages if you’ve plugged a drive with masses of clips on it into the computer and, I’ve noticed, it also OFTEN does not find all the clips or folders on the drive, so you’re left having to add those to the menu manually anyway, using the ‘folder-plus’ icon in the top left of the L&T window. Workaround: Set the camera to record Dolby Digital audio – MENU > AUDIO SET > AUDIO FORMAT > DOLBY DIGITAL – and yes, yes I know, LCPM audio is one of the selling points of the HXR-NX5, don’t tell me…Ģ) L&T sometimes populates the clip menu (if that’s what you call it) automatically. Short clips of a few seconds will often transcode in less time than the duration of the clip clips of 20 minutes can take an hour and a half to transcode. I’ll list these along with workarounds, if any.ġ) L&T takes extraordinarily long to transcode long AVCHD clips shot with uncompressed LCPM audio – by long clips I mean more than a couple of minutes. However, I’ve encountered a few problems with L&T. You can use L&T to ingest footage direct from recording media (via a card reader, for example) or from AVCHD files stored on a harddrive. ![]() ![]() This is accomplished via the Log and Transfer (L&T) tool, which can be found under the File menu in FCP. You need to transcode the AVCHD files created in the camera to another codec, such as ProRes 422, in order to edit the footage (this transcoding is also called ‘ingesting’). Clipwrap premiere pro pro#Not all problems will necessarily apply to both versions all the time.įinal Cut Pro (FCP) cannot handle AVCHD footage, like that created by the NXCAM, on the timeline. Note: All comments below are drawn from my experiences using Final Cut Pro 7.01 and 7.02. High-spec desktop machines seem to have fewer issues with L&T than laptops, no matter how high-spec the latter are. However, Log & Transfer is still unstable and you must be careful not to preview clips by moving the scrubber manually in the L&T preview window while transcoding as it has a tendency (on my machines at least) to crash. Having used it for a couple of days I can confirm that FCP no longer has an issue with long clips shot with LCPM audio (they transcode very quickly all the way through, what a relief!) and original timecode is carried through (at last). Clipwrap premiere pro update#UPDATE 22 September 2010: Apple has released an upgrade to FCP, 7.03. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |