Ron Priest
Veteran
Jan 24, 2008, 10:23 AM
Post #1 of 3
(393 views)
Shortcut
|
|
Abort Capture on Dropped Frames Feature is Not Working as Advertised
|
Can't Post
|
|
The manual specifically states on page 308 Part IV " Abort capture on dropped frames: When this option is selected, capture stops immediately when a dropped frame is detected. All media captured before the dropped frame has frame-accurate timecode and is preserved. The resulting media file is saved and a clip for that media file is placed in the Browser."
So, if you have this feature turned on, according to the manual, FCP is suppose to abort the capture, save the file, and place the file in your browser. This IS NOT working as advertised. I have posted this discovery on other forums and have been told by long time users of FCP that this feature has never worked this way. I even had one guy tell me it's not supposed to work this way! ??? I don't understand that mentality. If the manual states it is in fact suppose to work this way, shouldn't we expect it to do what it says? Since it's not behaving properly, then there is a bug in the programing, wouldn't you think? If it's not programed to behave in this matter, shouldn't we expect Apple to remove the improper reference from the manual? I've had others tell me this function had been documented to behave this way since version 4 however, they have never seen it properly work. Again, my beef is, if it's not suppose to work this way, then change the manual. If is IS suppose to work this way, fix the program! Is that so hard to understand? I don't get it? People on other boards have the attitude of "so what?"
I believe what is actually NOT happening here is the file that is being captured is NOT being closed properly after the abort action. If you look at your scratch folder while capturing a file, you'll notice the file name which you are capturing has a "-av" following the file name. Once you've completed capturing this data, the -av is removed form the file name and the file is now an accessible .mov file, and the clip is placed in your browser. Furthermore, when FCP aborts the capture because of a dropped frame, you'll still find this file with the -av at the end of the file name and the file is not accessible.
So has anyone here experienced this issue? Granted, I shouldn't get dropped frames in the first place, and most people have never seen a dropped frame while capturing. It's only happen to me 2 times, and I contribute it to the fact that I have a camera that is malfunctioning, it wants to reset timecode every so often (which is frustrating in of itself and I need to get that cam fixed). In any case, the real issue here is the failure of the feature. It's a little frustrating to capture 50 minutes of a 50 minute tape and then have it Abort on a dropped frame (as selected) but then not save (or close the file) properly.
___________________
Ron
(This post was edited by Ron Priest on May 13, 2008, 8:24 PM)
|
