Activity › Forums › Apple Final Cut Pro Legacy › ProRes Capture Issue
-
ProRes Capture Issue
Posted by Michael Orlansky on July 21, 2008 at 9:03 pmHi Everyone,
I’m having trouble trying to capture any flavor of ProRes or 10 bit uncompressed, everything else seems to capture fine. It seems anything with a 10 bit digitizer won’t capture. At this point I’m only trying to capture to the internal drive but will later need to capture to our new SAN. Once the capture screen opens it immediately stops on the first frame and reports dropped frames.
Specs: Mac Pro, Leopard 10.5.4, Final Cut Pro 6.0.4, QT 7.5, AJA Kona LHe
One thing we tried was to take the ProRes 422 preset and change the digitizer to 8 bit which did capture. Regardless we need to figure out why the 10 bit stuff won’t, any help would be great, thanks everyone.
Gary Adcock replied 17 years, 9 months ago 6 Members · 16 Replies -
16 Replies
-
Aaron Neitz
July 21, 2008 at 9:11 pmHD or SD? What kind of capture card?
right off the bat, sounds like the drive can’t keep up. Do you have a fw800 RAID you can try (like a G-Raid)?
-
Walter Biscardi
July 21, 2008 at 9:16 pm[Michael Orlansky] “t this point I’m only trying to capture to the internal drive but will later need to capture to our new SAN. “
Your internal drive, if it’s a single drive, will not support uncompressed or probably even ProRes captures. Try capturing to your SAN and let us know if you still can’t capture.
Walter Biscardi, Jr.
Biscardi Creative Media
HD and SD Production for Broadcast and Independent Productions.STOP STARING AND START GRADING WITH APPLE COLOR Apple Color Training DVD available now!
Read my Blog!

-
Michael Orlansky
July 21, 2008 at 9:32 pmCapture Card – AJA Kona LHe – HD material , 1080i
We can capture 8 bit uncompressed, as well as the above mentioned variation to the SAN. I just tried to capture to a 1TB Glyph drive with no success using the regular ProRes HQ easy setup, it still dropped on the first frame. As soon as we get rid of the 10 bit digitizer it seems fine.
-
Keith Koby
July 21, 2008 at 9:59 pmwe get the same results using the aja vtr exchange utility. 1080i 8bit to uncompressed or to prores hq is fine. 10bit to anything doesn’t work. Altering the fcp setting to 8 bit defeats the purpose of using prores somewhat. I think the idea is to oversample on the way in even if you are using an 8 bit source like an hdw2000.
Keith Koby
Head of Post-Production Engineering
iNDEMAND NETWORKS
Howard TV!/MOJO/Movies On Demand/iNDEMAND Pay-Per-View -
Aaron Neitz
July 21, 2008 at 10:02 pmSounds like driver issues. A call to AJA tech support?
10bit works great on Tiger and Kona 3.
-
Jeremy Garchow
July 21, 2008 at 10:41 pm10 bit works in Leopard too.
Are you sure you guys have everything setup properly? Such as the proper easy setup? Kona control panel is showing the proper format? If it’s dropping frames right off of the bat, it’s usually that the drive is not fast enough, or your format is bonked between the deck, computer and FCP.
Jeremy
-
Keith Koby
July 21, 2008 at 11:13 pmcontrol panel showed 1080i 29.97 in. Incoming video is the correct format bc dvcpro hd 1080i60 and 1080i 8 bit uncompressed is fine. It’s not bandwidth bc we are testing 300 MBs read and writes, plus we have no problem capturing 8 bit uncompressed.
-
Jeremy Garchow
July 22, 2008 at 12:24 amAnd when you choose a 1080i29.97 ProRes easy setup, it doesn’t work? Something doesn’t sound right. I believe you that you know what you’re doing, but I capture ProRes a lot along with 10bit UC HD and I do not have these issues, altough I have a Kona3 and not an LH.
Let’s start with the Kona drivers, what version are you running?
What version of the MacPro do you have? Is it pre or post 2008?
Also, Keith, do you and the original poster work together or are we dealing with separate machines?
Thanks.
Jeremy
-
Keith Koby
July 22, 2008 at 1:53 amthanks jeremy. We do have some experience with FCP. ;). I thought configuration problem at first, but after a day of checking, I’m not seeing anything obvious.
FCP 6.0.4
10.5.4
Qt 7.5
AJA 5.1 (regular not ndd)
Xsan 2.1The CPU:
3.0 GHz quad core 2007 (we bought a bunch so as not to do what we are doing right now… Moving to leopard new San etc).And yes, the original poster and I are talking about the same CPU.
Thanks man!
KkKeith Koby
Head of Post-Production Engineering
iNDEMAND NETWORKS
Howard TV!/MOJO/Movies On Demand/iNDEMAND Pay-Per-View -
Jeremy Garchow
July 22, 2008 at 3:08 amAlright. I have a couple of ideas, and some of these may sound redundant and you might have tried them, but let’s go through it all anyway as maybe you didn’t.
First, I don’t understand this part:
[keith koby] “we bought a bunch so as not to do what we are doing right now… Moving to leopard new San etc”
You bought a bunch of pre2008 in the hopes that you wouldn’t go to Leopard?
First, what PCIe slot config are you set up to? Have you followed these instructions for a pre2008 model?
https://www.aja.com/html/support_kona_rec_sys.htm
Make sure to click the ‘Click here’ button.
I assume you’re on 5.1 and not NDD because you have Shake in your pipeline? What happens if you uninstall 5.1 and reinstall 5.1 NDD? Does it work? This of course would disable Shake output for the moment.
This 300MB/sec, you are getting from your SAN, correct?
How much RAM do you have, and how is it configured on the risers?
Jeremy
Reply to this Discussion! Login or Sign Up