-
Abort Capture
I have been an FCP supporter since FCP2. I am losing faith rather quickly. The latest was a four hour marathon trying to capture lowly DV footage. No success ever came of it. I kept getting the unsolvable/mystery/change your firewire cable/ trash prefs/ change the capture scratch- still doesn’t work thing. My solution was to use Premiere Pro. I started a new project, captured THE WHOLE THING WITHOUT A GLITCH! I never thought I would be using Premiere but there you have it.
Why does FCP 6 report dropped frames on capture? New tape, no dropped frames are even present. Why can Premiere do what FCP cannot? This is distressing to me!!! I even had “abort on dropped frames” turned off in the preferences. Why does FCP continue to abort on dropped frames even though that function is checked off!
Why, why, why do I continue to support FCP Studio?
MacPro Dual Core 2 Duo 3.0Ghz, 6GB ram, 1TB Raid, Tiger 10.4.11, FCPStudio 6
-
2 Replies
-
I’d probably blame the software, too, since your binary solution was to use a different product.
You still cannot assume FCP is totally broken as an editing platform just because your system has some glitches.
My two systems work quite well.A reinstallation of the entire FCS2 package mya be your only hope, impossible to tell from here.
If you cannot or do not with to invest the effort to track down the root cause, uninstall your FCS2 products and move on.bogiesan
This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”
-
Binary! Boogiesan, you must be practicing being a Direct In Charge Kontroller in your spare time. As far as binary solutions go, I actually tried quite a few things, such as: change firewire cable/ trashing prefs/ change the capture scratch/ wiped out the raid, separated the drives/ reformatted drives/ tried different firewire ports/ checked system settings/ checked sequence presets/ eating green tea leaves and rubbing my tummy while humming Humuhumunukuapua’a. Nothing worked. Nothing is working for lots of others as well, if only you had looked, but you were busy practicing.
And still the question remains: Why does FCP 6 report dropped frames on capture? I have “abort on dropped frames” turned off in the preferences. Why does FCP continue to abort on dropped frames with that preference checked off!
And lastly, I imported the quicktime into FCP and continue to use the program as my editor.
MacPro Dual Core 2 Duo 3.0Ghz, 6GB ram, 1TB Raid, Tiger 10.4.11, FCPStudio 6
Reply to this Discussion! Login or Sign Up