-
Logged Clip Timecode Changes after Batch Capture
I’m working with the Kona 3 and the Panasonic D5 (HD3700B), OSX 10.4.7,FCP 5.0.4, G5DP 2.3 8GIG RAM, X-RAID 3.0 TB
I’m having a problem with FCP changing my logged clip TC after Batch Capture in 720p 59.94 10bit Uncompressed. This problem only occurs in 720p mode, 1080i is just fine.
While capturing 720p 59.94 from the D5
In FCP when I log a clip at:
01:20:00:00 in
01:20:30:00 out
After Batch Capture is complete the clip shows up in the browser as:
01:19:55:05 in
01:20:25:05 outFCP is effectively changing the logged timecode of the clip. I’m capturing with burned in TC and the Burned in TC is Frame accurate, but why is FCP changing the clip’s TC?
In all my experience with FCP I have never encountered this issue and I am completely puzzled. I’ve contacted AJA and they have said that they do not know of this issue and were puzzled also. I am using a Tri-Level Sync and everything seems to be getting proper reference.
There is no reason why FCP should be changing my logged clip settings. (right?) Also, I tried a test where I made the clip that came in with the bad timecode offline, and then ran a Batch Capture again, and it changes the logged timecode even further. I’ve tried a variety of Device Control settings playing with frame offset etc with all having the exact same numeric result (see TC above).
Anyone who has any insight or similar experience your thoughts are greatly appreciated. Thanks for the help
Ted – Editor, NYC
-
10 Replies
-
Are you adding handles to your capture? What does the media start and media end columns say, not the in and out columns.
-
Good point, I should have specified, the timecode listed is from Media Start and Media End. No Handles. So to revise:
——
While capturing 720p 59.94 from the D5
In FCP when I log a clip at:
01:20:00:00 Media Start
01:20:30:00 Media End
After Batch Capture is complete the clip shows up in the browser as:
01:19:55:05 Media Start
01:20:25:05 Media End
——-
Also, I’ve just done the same tests on an identical setup that we have here with the same exact result. Hope thats helpful, thanks.Ted
-
Have you calculated that deck’s offset? it’s really weird that in both instances the tc is exactly 4 seconds and 55 frames off. This is a shot in the dark, but find the TC rate column in the browser and if it’s not there control click on the top of the browser to bring up the list of columns. Select show tc rate. What number is in the tc rate column? If it’s set to anything but 60, change it to 60. I am not familiar with the d5, but does the tc read true 60 fps or is it based on 30fps like Varicam material?
-
The frame offset is -3.5 Payback offset -:01 Capture is frame accurate to the entended Timecode, the burned in TC I’m capturing is right on, just don’t know why FCP feels inclined to change the files TC.
Panasonic D5 is set at 59.94 in its menus, if it opperates in the same way as the Varicam I’m not exactly sure, but at 59.94 setting the TC on the D5 runs to 30 (with 2 fields a frame) not 60. Not sure if that answers your question, but I don’t think that this is the main issue.
I looked at the TC Rate in Browser and after loggin it is set to 30, I changed it to 60 before capture…..after capture, same exact result, and FCP had changed the TC rate back to 30. I tried then switching it back to 60, but that just messes up the TC even more.
Thanks for the help.
Ted -
Well, Ted. I am out of ideas except that maybe there’s a difference between VTC and LITC and you are capturing the wrong one.
Hopefully someone out there has a better answer for you. Sorry I can’t help more.
Jeremy
-
[JeremyG] “VTC and LITC”
Woops, VITC and LTC.
Jeremy
-
Thanks Jeremy. Also just for reference, capturing VITC + LTC, capturing just LTC, and capturing just VITC render the same exact results.
It really is starting to feel like a FCP / Kona3 issue.
Here is what I’ve tried capturing from D5, Source tape is 720p 59.94 D5:
720p 59.94 8bit
720p 59.94 DVCProHD
(The above have the same results as before)1080i 29.97 10 bit has been working fine, when I tried to uprez the 720p tape to 1080i via Kona Control Panel, and captured 1080i 29.97 10Bit, it came in without the TC glitch. So it seems this is a 720p capture codec/harware issue, rather than a problem with the D5, ref loop or the tape.
I feel like I’ve exhasted my trials. urgh…Ted
-
Did you get this fixed?
Did anyone at AJA help you solve this?
(it doesn’t look like you got an answer here).
I’m interested because I’m in the middle of the “AJA or Blackmagic”
question and D5 may be in our future.
Your problem is serious, to say the least.Thanks,
Dan -
No I have not gotten it fixed. The second time I talked to AJA, they still did not have any idea of what this might be. When I talked to them they had just released the new drivers that morning, so I’ll try that, but I need to get the FCP Universal upgrade from apple so I can run 5.1.1 on my G5. Interesting that while on the phone with Apple inquiring about the upgrade process, etc. The guy on the phone said that there are 720p improvements in FCP 5.1. When asked to be more specific and told about my problem, his response was vague but focused toward getting the upgrade. Maybe, this was a know issue? not sure. I’m getting the upgrades by mail on Tuesday and will revisit the issue. For now I still cannot capture 720p without big TC issues.
-
He might have been referring to 720p60 captures. It used to happen where you would capture 720p60 stuff and only a series of weird subclips would show up after a batch capture. You would then have to import all of the media (it did in fact successfully capture, it’s just that FCPs database was screwed up somewhere in the process).
Jeremy
Reply to this Discussion! Login or Sign Up