-
Timecode and Reel Name Issues
I thought I would start this again since it seems that Apple seems to notice multiple postings on problems and I’m hoping that we will get noticed by Apple on this very serious issue. Here’s what I sent to Apple in the Send Feedback dialog.
“Well…. Ever since upgrading to FCP 5.1.2, Quicktime 7.1.2 and MacOS 10.4.8, my log and capture has had many problems. Clips will digitize and never link after the digitizing process, timecodes and reel names will be reset to 00:00:00:00 with the reel names listed as 001. You have to physically recreate that clip and give it new timecodes and proper reel names to fix this, and sometimes you have to do this two or three times before it works properly.
Today, I opened several projects so that I could copy a few of the clips to a new project for a show open and alomst every project has an error box that pops up telling me that certian clips are not optimized properly for FCP. Most of these clips play fine but some loose sync and the video skips.
I had to upgrade to these verions of the programs since we use Sony’s XDCAM HD system and these versions allowed me proper access to these features (sort of – very buggy at best).”
This just seems to be the start of things that are now happening. Re-capturing media seems to be a real challenge, if you can do it at all, right now. Its getting really frustrating and annoying. AND NO….. I’m not having issues with non-drop vs drop frame timecodes. All of our media is recorded drop frame.
_______________________________
Wayne Carey
Schazam Productions
http://www.schazamproductions.com -
6 Replies
-
this is the third, at least, post I’ve seen like this in the last week. I posted about 2 weeks ago with the same problem. The consensus seemed to be to trash your preferences and try again.
I have been recently working on the same system that had this problem and it has not repeated. It seems completely random.
Good luck, and keep us updated if find a reason for this bug.
Todd -
I have trashed my preferences. Now, FCP just seems to just close out all on its own from time to time, too. BUT I have noticed that FCP seems to loose my machine control alot. And if you have captured something that uses a serial port and forget to change it to firewire, it will screw up your clips.
It seems like it has something to do with machine control – serial vs firewire.
_______________________________
Wayne Carey
Schazam Productions
http://www.schazamproductions.com -
Hmm, all your tapes are drop frame? Are you capturing dv?
-
[JeremyG] “Hmm, all your tapes are drop frame? Are you capturing dv?”
No… Everything we shoot is drop frame. The machines even specify that they are drop frame. But I do use firewire machine control on my HDV deck and 9-pin serial on my XDCAM HD deck. I use the same cature settings for both but I have to change machine control for each deck. If I forget to change machine control and try to batch capture with the wrong machine control selected, I get the drop/non-drop frame error message every single time. If I click cancel and change my machine control, then batch digitize, most of the time the clips are fine. BUT on occassions, my timecodes and reel names will be lost.
Getting weird isn’t it…. I trash my preferences, sometimes multiple time in a day, restart the computer and zap the PRAM. Then the computer will work fine until it happens again. Spooky….
Now, I restart FCP and I get an error message telling me that my media is not optimized for FCP any more that I will have problem unless I redigitize the media. Sometimes, its only the media that lost the metadata and sometimes its all of the media in the project.
Let me say that this is occuring on both of my edit systems, one a PPC, the other MacPro. AND, this has only started after the FCP 5.1.2 update, MacOS 10.4.8 update, and Quicktime 7.1.3 update.
_______________________________
Wayne Carey
Schazam Productions
http://www.schazamproductions.com -
See, I know it sounds weird, but to me it’s a drop frame issue. I have no problems capturing footage that’s non drop. No warnings, no hassles, no lost metadata. You are having all kinds of problems with drop frame material.
Every time I capture something with drop frame, I get that warning and funkiness ensues.
I have only had these problems after the same updates you have mentioned, but someone has mentioned that they were getting the same thing with FCP 5.1.1. I think Quicktime is the culprit but that’s just a hunch.
Thanks for chiming in, hopefully someone is listening.
I might put a call into AJA and see if they have heard of anything. I doubt it’s their fault, but sometimes they have fixes and they way more connected to Apple than we are. This also happens without AJA hardware (it first bit me on a dv offline coming in firewire). If I hear of anything I’ll let you know.
Jeremy
-
Now, that’s interesting! I have never had any problems like this at all until this latest round of updates.
APPLE, YOU HAVE SOME FIXIN’ TO DO!
_______________________________
Wayne Carey
Schazam Productions
http://www.schazamproductions.com
Reply to this Discussion! Login or Sign Up