John Heagy
Forum Replies Created
-
John Heagy
June 20, 2007 at 3:22 pm in reply to: Be Careful. Mistake in AJA Easy Setups for ProRes NTSCAccording to Apple’s white paper, ProRes is 8bit ProRes(HQ) is 10bit.
John Heagy
NFL Films -
You want to use 59.94 as a frame rate. 60 is not supported by any deck I’m aware of. The advantage of encoding from DVCPROHD to ProRes would be if your doing a lot of color correction or graphics, both will benefit from ProRes’s 10bit color and full 1920 frame size.
John Heagy
-
Apple really needs to add an alternative to the very long in the tooth OfflineRT. Short of hacking the RTenabler.txt file, it’s either OfflineRT or DV25 for offline media. OfflineRT came out with FCP 2.0 for heavens sake, can we please have a 5-10Mbit 16×9 RT offline codec already! About to try an RTenabler hack to at least open up Photo-JPEG to a more pleasing frame size and data rate.
As for 16×9 offline, don’t forget there is a 384 x 216 HD OfflineRT Easy preset in a variety of frame rates, you just have to create a custom Capture preset.
John Heagy
NFL Films -
Hey Walter, can you give us the link to MacPro requirements you found. I can’t find it on Apple’s site.
Thanks
John Heagy -
The data rate has little to do with the ease of capture. The load is on the cpu when compressing HD ProRes in software. I can gaurentee a G4 will not be able to capture HD ProRes in software. With an IO HD… yes, because the IO is doing all the heavy lifting, maybe that is what you meant by required hardware, but my question was about software encoding of HD ProRes.
So we got FCP6 and did so tests of our own using the ProRes codec in a custom app. On a Quad G5 with 2G of ram we were able to capture 10bit 1080i for 15min until it dropped frames. All 4 processors were nearly pegged at 380%. We were able to capture 8bit without dropping, processors were at 300%. Both without preview.
-
John Heagy
May 2, 2007 at 2:52 pm in reply to: Quicktime 7.1.6 doesn’t see timecode from exported h.264 clipsThe timecode display is great, now I’d like to see source name displayed as well as real audio meters that show the actual discrete tracks in the movie, not a stereo mixdowm with those little parametric audio indicators it has now.
John Heagy
NFL Films -
Thanks for your help Jerry.
The fields that are mysteriously missing are Description, Scene and Log Note. We are currently trying to figure out what steps caused this. We had hoped it was just an errant keystroke that was deleting the info. It may turn out that the editor edited in a fresh clip into the timeline and did not use the clips on the timeline returned from the xml, but he claims this was not the case. The info determines which clips from the timeline are posted to the web.John Heagy
NFL Films -
Now that I think about it, Apple’s fibre card (newest version) is PCI-X so the DeckLink HD Pro car should work in the Xserve… No?
-
Your right… I misspoke. It’s actually a custom app our chief engineer wrote not FCP that we have running on the Xserve. The Xserve is a client on our Xsan so it has a Fibre card in one of the slots, that would explain the slow down.
Thanks
John Heagy -
The Intel desktops will be fast, with Apple software, but if you use After Effects or other complex apps you may have a very long wait for Intel versions. Remember how long it took Photoshop to go OS X native, and you can bet Adobe apps aren’t coded in Xcode so it will be a difficult port.
John