-
Dropped frames when capturing 444
Hello. I’m trying to capture footage that’s 1080 444 to a 250mb/s RAID, and I’m getting dropped frames every time. The odd thing is, I’ve captured plenty of other tapes at 444 before, but suddenly now I can’t. There haven’t been any changes to the computer that I know of. I’ve even got a different computer now, but still the same problem. It’s not just this tape, either. I can’t seem to capture any 444 tape now. According to the Kona System test, the RAID is performing fine. I’ve also tried on another computer with the same results. Also, if I do a batch capture, the capture will sometimes stop and tell me there’s broken timecode when there is none. (I know because I’ve captured the same tape before) Does anyone have any idea why I’m dropping frames? Thanks in advance.
Specs: 2 x 3ghz Quad Mac Pro 4gb RAM Final Cut 6.0.2 Kona 3
-
11 Replies
-
Do you have the correct settings for your capture? That is your capture preset matches your tape format?
You could try creating a new Project and see if that helps.
Walter Biscardi, Jr.
Biscardi Creative Media
HD and SD Production for Broadcast and Independent Productions.STOP STARING AND START GRADING WITH APPLE COLOR
The new Color Training DVD now available from the Creative Cow! -
Yes, the settings are correct, and I’ve already started multiple new projects. Still dropping frames.
-
I am not familiar with capturing 444, but I do know there’s a specific 444 driver for the Kona. Did you get that? If not, give AJA a ring or an email.
Jeremy
-
Fairly certain I do, else I probably wouldn’t have been able to capture 444 in the first place.
-
How full is your RAID?
-
Have about 550 gb free, I’m trying to capture something that’s about 370 gb.
-
Harddrives in general are storing from the outer tracks and in. Because the drives rotate at a constant rpm the Inner tracks cannot handle the the same amount of data as the outertracks. Thats proberly the cause of your problems. Less data per track equals less read and write speed.
Let the machine work for you. Not you for the machine
-
[Tyler Dixon] “Have about 550 gb free, I’m trying to capture something that’s about 370 gb. “
that is most likely one of the issues, working in RGB often requires 2x as much free space on the drives as you are trying to capture. it is a known issue in FCP.
in my experience this happens more often on RAIDs that are barely up to the performance specs,
you can Contact AJA tech support for the deck polling fix, but I think the storage is another issue.
gary adcock
Studio37
HD & Film Consultation
Post and Production Workflows
Inside look at the IoHD -
Hmm. Now that you mention it, when I was having this problem before (enough space to capture but not twice as much as I needed), we cleared the raid and I didn’t have a problem anymore. I’m waiting for the RAID to be backed up now so that we can clear it again. Hopefully afterward it’ll work. Maybe it is the problem. I’ll post if it works.
-
I’ve had the same problem with my RAID capturing HD 444 video. My conclusion has been that when RAID starts to get full, the free space gets increasingly fragmented.
To solve this you can delete files and make more space on the RAID or another solution can also be to use iDefrag and do a full de-fragmentation of the whole RAID.
This do take quite a while to do but can be very useful especially if you’ve been using the RAID a lot with little space free (files and free space tend to get more fragmented that way).
Cheers,
—
Oyvind Stiauren
Post Production Supervisor
Terminal, Mexico City
Reply to this Discussion! Login or Sign Up