David Eaks
Forum Replies Created
-
Hi EBond,
Just thought I should mention that you should be backing up your memory cards in their entirety. Not just pulling .mts files from the cards and saving individual clips to your computer.
Doing this will ensure you can do proper ingest to whatever NLE you choose. Every file and folder on the card is important, from empty folders to the .mts files. Don’t even go into any folders and look at the file structure or copy single files, leave it alone. Just backup the whole card (backup each card to its own folder and name the folder to identify the content on the card) to your computer and point your NLE to that folder for import.
-
Did you click to select the setting in the untitled window (batch window) before going to the inspector and turning on frame controls? If not, it’s likely that you changed the default setting in the settings browser, and not the setting applied to your clip.
-
Hmm, we’re missing something here. What setting are you using in compressor?
-
After exporting (assuming “self-contained, current settings”) from the timeline, are you compressing for the web in Compressor? If so, with the setting that you applied to the job selected, go to the inspector, turn on frame controls and set deinterlace to best. It might take a bit longer to encode.
60i is not uncommon but if you are shooting with the specific intention to deliver to the web, probably just shoot progressive and avoid interlacing all together in the future. I use Matrox MAX to encode H.264 for Web/Blu-ray/mobile and use its deinterlace. It encodes h.264 in just under real time.
I think the general consensus is that FCP7s deinterlace is crap, I’m sure someone will chime in with better details on this whole situation.
-
Delete render files from within final cut. From the project browser select the project and choose file> delete project render files> all render files.
-
If Logic Pro X tells us anything about the future of Final Cut Pro X maybe we will get the new undo features from Logic. List of last 200 actions, even from before the project was opened and out-of-sequence undos (but not without risk of creating a time paradox apparently)-
-
Good point Andy.
Building it in Motion for use right in FCPX is definitely solid advise, especially if you’ll be using it again in the future.
-
The timeline index is pretty handy for this type of thing, but its not quite what your asking for.
-
I was about to pull the trigger on a Sapphire Radeon 7950 for my Mac Pro 3,1 2.8, 8-core, 16GB. Primarily for use with FCPX, thinking that it was the “best” choice (replacing a 5770).
I’m having trouble finding comparisons of the GTX 680 vs Sapphire 7950 with regard to Mac Pro FCPX performance specifically. Bare Feats has tests including Final Cut “coming soon”, as mentioned at the bottom of this page-
https://www.barefeats.com/gpu680v3.htmlAnyone have any experience with each of these cards with FCPX? or links to comparisons/benchmarks?
-
I’m relieved as well, though surely to a lesser extent. Just glad that we all do not have to worry about a disappearing project bug tarnishing FCPXs excellent autosave track record (IME).
Thanks for posting the solution.
