Final Cut Pro 4.5 Drop Frame Error Firewire 10.3.9
ContestFree ResourcesLARRY RECOMMENDSRelated WebsitesRelated BooksFavorite ArticlesLEARN FROM LARRYFree Step-by-Step TutorialsArticles / BlogFree Weekly WebinarTip of the DayOTHER RESOURCESForum (beta)Editing as a BusinessNewsletter ArchivesSocializeStoreSupportGeneral FAQSupportSolving Dropped Frame ErrorsPosted on May 15, 2011 by Larry[ This article was first published in the May, 2007, issue of Larry's Final Cut Pro Newsletter. Click here to subscribe. ] There are three questions I get asked all the time:How do I trash preferences?How do I deal with images?How do I deal with dropped frames?The first two are already covered in articles in my library (Click the question to read related article.) However, this last one I haven't really addressed. So, here is a quick checklist you can use to solve a dropped frame problem.In general, dropped frame issues are caused by a hard disk that is too slow to keep up with the video format you are using.Here's an article that provides an overview of hard disk speeds compared to video data rates.NOTE: By the way, if terms like RAID 0 or RAID 1 confuse you, read this short explanation of how RAIDS are defined.System Setup Issues Make sure your hardware is supported by Final Cut - check Apple's web site.Make sure you are not using a hard disk connected using USB.Make sure your drive spins at least 7200 RPM, many inexpensive drives are slower. Don't capture media to your internal boot drive. If you are using FireWire drives, make sure your total cable length is less than 15 feet total among all devices.Make sure all your data drives are formatted for the Macintosh (Utilities > Disk Utility > Erase tab -- if the format popup menus says anything EXCEPT Mac OS Extended or Mac OS Extended Journaled you may have problems.)If you are using a third-party hard drive or RAID, make sure you have the latest drivers.Disconnect all external devices. Reattach one at a time to see when the problem recurs.Adding a second FireWire bus, via PCI card, can also solve data bottlenecks.Operational Fixes Make sure your Easy Setup settings correctly match the video format you are capturing.If problem occurs during playback of an RT sequence, render the sequence.If problem occurs during a rendered sequence, delete render files for that clip (Co
list is almost certain to help, and if it doesn't, refer to the Desperation Method at the bottom. (Some of these same ideas can help on capture) --Restart the computer from a cold start. Unplug it from the wall for a minute, replug, and then restart. --Set the Canvas and Viewer to "Fit To Window." --Don't overlap Canvas and Viewer or any other windows. --Close all other applications--even that email program down in the corner. --Disconnect the Network. --Make sure the Log and Capture panel is closed and not just hiding. --Go back and take out all the MP3 sound tracks. Convert them to AIFF 48/16/2. --Perform https://larryjordan.com/articles/solving-dropped-frame-errors/ an Audio Mixdown. This does not happen automatically in Render. --Mix down the audio to stereo if that's what the final show needs. --Render Everything. --Try Print To Video and turn the mirrors off. --Clean up your Hard Drives. No drive on a video system including the System Drive should be over 90% full. Any drive the machine can see is fair game for this problem whether you're using it for video http://www.kozco.com/tech/stuttering.html or not. --Launch your machine from the OSX Install CD (hold "C" during startup) and run Utilities, Repair Disk and Repair Permissions on all the drives. --Start normally, open Terminal (Applications, Utilities, Terminal) and type: sudo periodic daily weekly monthly ...and press the Return, or Enter key Wait. --Do Not cross QuickTime versions. QT6, FCP4, 4.5, and OSX 10.3.x get along really well. QT7, FCP5, and OSX 10.4.x get along really well. Crosses don't. --View, External Video, All Frames. That's the setting to play the TimeLine live to a deck, television monitor, or camcorder. Sound Sync follows the setting. If you throw video to a deck, that's where the sound is going to go. No fair watching the deck and listening to the computer. --Trash the Preferences. If you have corrupted Preferences Files, your instructions to the computer can get scrambled leading to much instability and craziness. Trashing the Preferences Files forces FCP to rebuild them and hopefully restore order. You will need to put all the capture, system, and timeline settings in again fresh. --Reloading Final Cut from the install CDs does not trash the preference files! --Cast off the FireWire drives. Systems have enough trouble with one FireWire drive. Looping or Daisy Chaining them is asking for trouble. See Desperation Method belo
If this is your first visit, be sure to check out the FAQ by clicking the link above. You https://forums.creativeplanetnetwork.com/forum/final-cut-studio/final-cut-pro-7-and-earlier/25822-repeatedly-hangs-up-on-2nd-capture-in-batch may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Announcement Collapse No announcement yet. Repeatedly hangs up on 2nd capture in batch Collapse X Collapse Posts Latest Activity Search Page of 1 Filter Time All Time Today Last Week final cut Last Month Show All Discussions only Photos only Videos only Links only Polls only Filtered by: Clear All new posts Previous Next Passtheketchup New User Join Date: Nov 2003 Posts: 17 #1 Repeatedly hangs up on 2nd capture in batch 05-15-2005, 04:37 PM Are you there Ken, et al.? I've started bringing in dailies for a feature on my FCP 4.5 system. final cut pro There have been no capture problems to speak of for the six months, or so, that I've been working with this setup. Last week the first DVCam tape was batch captured with no problem, but the second tape hung up on every other clip in the batch: i.e. Clip one captured fine, but on the next clip I would see a frozen frame on the capture screen followed by a dropped frames error message. I went back to the known-good first tape and encountered the same problem, so I know this is not related to the actual DVCam cassettes. I'm working on a mirrored-drive dual 1.25 G4, running 512Mb apple memory and another 512Mb of PNY memory. I'm running FCP 4.5 on OS 10.3.9 with QT 6.5.2. I'm capturing from a Sony DSR-11, via firewire. My media drive is a known-good 7200 RPM Maxtor one-touch firewire 400 (300GB). I have been capturing with this configuration for months, without incident. Here's what I've done to try to solve the problem: Put a cleaner tape in my DSR-11 deck Trashed FCP permissions Repaired OS permissions Re-seate