-
History Channel P2 specs
Just read Shane Ross’s article “P2 Tapeless Workflow Helps Rewrite History” Very helpful, thanks Shane.
My question is, since this article was written in 07, is History Channel still at this level of delivery? Looking at their spec sheet it matches what Shane wrote in the 07 article.
We’re heading into production on a History show using a HVX 2000 as cam A and a HPX 200 as cam B. As stated on History Channels spec sheet we can only use 25% of the HPX 200.
Looking at the workflow from Shane’s article, I want to cut the show at 720p24 (FCP) then bump it to 1080p for delivery on D5 using either our Terenex or after the grade in daVinci Resolve.
Thanks in advance
Martin
-
2 Replies
-
[Martin Spirit] “is History Channel still at this level of delivery?”
Yup. Bear in mind that the MAIN camera was a Varicam, and the HVX-200 cameras were B-cameras. The Channel still considers them B-cameras and specifies that only a certain percentage of footage from those cameras can be in the final show.
But then there are cases where the ENTIRE show was all shot with HVX-200s. The show about the tunnel diggers of NY, the guys who dig the aquaducts (forget their actual names) was shot ENTIRELY with those cameras. So if needed you can get wavers.
[Martin Spirit] “I want to cut the show at 720p24 (FCP) then bump it to 1080p for delivery on D5 using either our Terenex or after the grade in daVinci Resolve. “
What will you be editing with? Avid? Then that would be the workflow. On FCP it is a lot cheaper to edit with FCP and cross convert on the fly when you output with the AJA Kona 3 or LHi…that’s what we did.
Shane
GETTING ORGANIZED WITH FINAL CUT PRO DVD…don’t miss it.
Read my blog, Little Frog in High Def -
Thanks Shane, very helpful.
We’re all FCP all the time. Been using the P2 FCP work flow for the last 3 years, couldn’t live with out it now.
Although our HPX2000 (A Cam) is not a Varicam it’s chip size is within the A Cam specs listed.
Cheers
Martin
Some contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
Reply to this Discussion! Login or Sign Up