-
AJA Ki Pro Dopping frames and slipping timecode-Is there a drive test utility?
To the point: is there a utility to test Ki Pro drives? One that will detect a drive that is failing and will drop frames?
Quick Why: one of my Ki Pros is dropping frames and the timecode AND video is slipping when it does. I am assuming it is the hard drive…AND I DON’T KNOW WHICH Drive it is. We have 8 Ki Pros, and well over 20 drives.
Details: So we set up a shoot around Christmas for a concert. Nice theater, nice lighting, all star band with a revolving cast of characters. I just sat down to start the editing and mastering this week, since they only want the finished product ready for this Christmas season.
The setup was 5 cameras (including one on a 30′ jib) all run into Ki Pros for iso as well as into a Panasonic 410 switcher for a line cut. The line cut was recorded on 2 separate Ki Pros for safety. There is also a multi-track recording (with timecode) of the show which will be mastered and laid back in. So now I am doing a really polished cut in FCP using multiclip, which is working fantastically.
I used timecode to get my in-points and synced that way. While cutting I noticed that camera 3, the jib, is occasionally dropping frames, screen jitter, whatever. Now, I run across a place where the camera iso drops a frame, but the program cut, which happens to have the same camera at this point, is just fine. So only the iso record is dropping. It happens to be the jib, which is almost always a great go to shot, so I want to use it a lot.
A bit later I take that camera for a vocal, and I notice it is WAY out of sync. I can’t figure out how only one clip in the multiclip slipped. Then it dawns on me, the dropped frames. So I open the raw footage, set new matching in-points, lay camera 1, which is fine, in a new sequence, then I lay the problem camera with the same in-point on top of it, and sure enough the audio echos, The clip and timecode no longer match. I don’t totally understand this, since a timecode generator is running, so I would think that even with dropped frames, it would record the right timecode.
So I slip the tracks until audio matches as best I can tell, and it is off by a full 7 frames. I then make a new multiclip with this camera offset, and cut away. A few hours later, I see the camera is out again. So I go through the same process, and now it has slipped 11 frames.
I originally had two questions, but now realize that since the timecode did indeed slip, creating the multiclips via timecodes vs in-point would likely have not been a resolution.
Thanks for any help and suggestions.
Rich Kaelin
Kaelin Motion Production Services
https://kaelinmotion.com
New York