-
HD Capture/edit workflow
Greetings! A potential client wants to do an 8-camera shoot of a live performance. He will shoot it twice. Each performance is 75 minutes which when multiplied x8 x2 shows = 1200 minutes or 20 hours. It will be shot in HDCamSR. The question comes to capturing, live switching during the edit and then dumping out. I presume I should capture it using AppleProRez- not HQ right? Then the concern I have is bandwidth. I get approx 220 Mb/sec of throughput on my raid. But Im concerned with choking. How’s about this:
Capture the HDCam to an external SATA drive using AppleProRez. When finished, media manage the material to my RAID but recompress the footage as new ProRez Proxy resolution. Edit the show and when finished, reconnect the sequence to the original ProRez files. Thoughts? Thanks.
Geek/Nerd
Mac Pro 2.26 GHz Quad-Core Intel Xeon
16 GB RAM, 3Gig internal Raid -
3 Replies
-
Hi Darren,
I’m a little confused on what you’re accomplishing by [Darren Peister] “When finished, media manage the material to my RAID but recompress the footage as new ProRez Proxy resolution.”
You’re correct that trying to do a HD 8 angle multi-cam edit will take a HUGE amount of bandwidth. I’m not sure, but doubt even eSata can do this. My system choked when trying to use an internal raid, with 4 720p HD streams.
You’re best to either cut in SD then uprez or a proxy edit. But I don’t see the benefit to re-compressing?Good Luck,
Todd at UCSB
Television Production -
Todd, the idea would be to edit in a lower rez version of HD that takes up significantly less space on my edit system’s RAID and in turn the Raid would be capable of doing the 8-camera switch. I would not be editing in SD which is a plus and because the format is a variation of ProRez, FCP should be “happier” with the codec and not crash on me. It seems logical to me; dumb down for the edit while staying in HD and keeping the content moving along without choking.
Geek/Nerd
Mac Pro 2.26 GHz Quad-Core Intel Xeon
16 GB RAM, 3Gig internal Raid -
Hi Darren,
I missed the ‘proxy’ in your previous post, which lead to my confusion.
Yes, that’s the best workflow for your situation. Full ProRes is around 21MBytes per stream with audio, so multiple by 8 and your at 160MBytes per second of video. eSata is suppose to run a lot higher than that, but as is often the case, real world is different than the technical specs.With as much footage as you need to wade through, it would be a good idea to run a test with your footage before you commit to the workflow. You may find you don’t need to run with proxy.
Good Luck,
Todd at UCSB
Television Production
Reply to this Discussion! Login or Sign Up