-
dropped frames during capture
Ok…
I know this has been talked about a lot, but i’m hitting walls.
System Settings:
1.33 Ghz PowerPC G4 laptop
1 GB DDR SDRAM
OS 10.4.10 (just updated)
FCP 5.1.4So i’ve been trying to capture and i keep getting the dropped frames alert which halts me from capturing.
I have dumped my preferences, reformatted my ext firewire disc (extended but not journaled), did the spotlight privacy trick, and upgraded from OS 10.4..9 to 10.4.10. The upgrade seems to have helped a bit or the reformatting did (did both before testing again)….as it went longer before getting the dropped frame alert, but still happening.
One person on another list suggested getting a Firewire PCI Card, suggesting that since macs only have one firewire bus, that adding a second one would not allow things to get so clogged up. IS this my only solution left? what else can i do? At this point its looking like i’ll just have to tell FCP to start a new clip on dropped frames and then go back and capture the missing sections and then link the clips up on the timeline…not what i would say is an effecient or productive workflow. There’s got to be a way around this.
help.
Ren
-
5 Replies
-
Have you tried Forcing Capturing, Just do a straight CAPTURE NOW. Or have you tried Capturing as if it were a non-controllable device?
I have ran into these issues, and I still do … Check your Capture Settings. Check to see if you are capturing in DF or NDF. That does make a difference on the capture (FOR SOME REASON).
Are you capturing through a Deck or through your Camera?
Raymond Tuquero
-Houston Editor- -
I have tried both capture now and batch capture. Neither have worked…i believe i’ve tried both as DF and NDF but i’ll try that again too. I have not tried the non-controllable device method….that might be the way. THERE are NO dropped frames on the tapes and the areas where it stops are always different. So it really is a matter of just fooling FCP. While i’ve had issues with dropped frames in my timelines, i’ve never had it this bad……i can’t have this be a problem with each edit job.
-
What drives are you using?
How are they connected?
How fragmented are they?
What format are you trying to capture?
Walter Biscardi, Jr.
https://www.biscardicreative.com
HD Editorial & Animation for Broadcast and independent productions.All Things Apple Podcast! https://cowcast.creativecow.net/all_things_apple/index.html
Read my blog! https://blogs.creativecow.net/WalterBiscardi
-
[RayRayT] “Check to see if you are capturing in DF or NDF. That does make a difference on the capture (FOR SOME REASON).”
I have never seen DF or NDF make any sort of difference in capture. Those are just timing numbers. They have zero effect on capture, at least not that I have seen on any NLE I’ve ever used.
Walter Biscardi, Jr.
https://www.biscardicreative.com
HD Editorial & Animation for Broadcast and independent productions.All Things Apple Podcast! https://cowcast.creativecow.net/all_things_apple/index.html
Read my blog! https://blogs.creativecow.net/WalterBiscardi
-
Well, turns out it was my new drive that was bad. All is good now…
Reply to this Discussion! Login or Sign Up