48hr Film Comp with an Epic

[William Schultz]

I'm very excited to be working on this. I personally find the RED workflow with CS6 to be extremely smooth and very flexible. The team has a great plan of attack put together which gives post-production plenty of time to work. I'll be using my Mac Pro (5,1) with 32GB RAM, SSD Boot Drive, RAID 0, GTX 570, GT 120, and Blackmagic Intensity Pro. While a couple rockets would be extremely helpful I'm more than confident in Adobe's workflow. I've proven this workflow on multiple projects since it was released and haven't had a problem yet. Working with the original .R3D's the entire way is the best part of post-production to me.

[James Drake]

We also shot our 48 on the Epic, and used fcp7 (editor choice)

What group are you showing in Jon?

[Shawn Nelson]

Woohoo! We're going! Just posted an update.

[Shawn Nelson]

We did it! Update on pg1

[Tehben Dean]

I shot a 48h on RED One last year. Never understood peoples assumptions about red workflow and we were even working in FCP7 and Resolve.
Shot for 9 hours, took an hour break to offload and then our Editor rendered out proxies from RCX and started on the rough while we shot for another 9 hours and brought it the rest of the footage and repeated the process. Once we had the edit I XMLed into Resolve for the grade then exported and connected back to the sound which was done alongside the grade.
We did have a rocket.

The scariest part was rendering the final 15 minute project and having it finish 20 minutes before the deadline ;) haha.
Was a blast!

Look forward to seeing yours Shawn!

[Will Keir]

The disadvantage could be seen in upload/download times. Larger files than shooting with a DSLR or the like.

I wonder if anyone does the competition with a GoPro? L(

I don't understand the disadvantage of the RED workflow in CS6 in a 48hr competition. Actually I don't see any disadvantage in the RED workflow at all. I'm knocking out edits faster in CS6 than I ever have with FCP. It's rock solid if you ask me.

[Alexander Thomson]

I just finished the 48hr in San Jose. Our original editor "became unavailable" so we edited on a consumer HP quad core AMD with ATI graphics.

We round-tripped from CS6 to Resolve and back and still had 2 hrs to spare. No rocket, no nvidia graphics cards, and since we didn't have an official editor, I had to cut together the project on CS6.

I've never used CS6 before but with FCP7 key presets I was good to go. The Adobe workflow really is a testament to the power of tools that work together. I may not go back to FCP on personal projects because of my good experience with CS6. I learned a lot of things this weekend... It's a shame they're projecting at 720P in San Jose :(

[Shawn Nelson]

I just finished the 48hr in San Jose. Our original editor "became unavailable" so we edited on a consumer HP quad core AMD with ATI graphics.

We round-tripped from CS6 to Resolve and back and still had 2 hrs to spare. No rocket, no nvidia graphics cards, and since we didn't have an official editor, I had to cut together the project on CS6.

I've never used CS6 before but with FCP7 key presets I was good to go. The Adobe workflow really is a testament to the power of tools that work together. I may not go back to FCP on personal projects because of my good experience with CS6. I learned a lot of things this weekend... It's a shame they're not projecting at 720P in San Jose :(

Yeah, it was a hearbreaker to take a 5k timeline and do a 'theatrical' export to 854x480 (what Portland screens at in this giant 500person theater)

[Alexander Thomson]

Oh shit. I meant to say it IS A SHAME (they're projecting at 720P). Yeah. It's been a long weekend. :P

[William Schultz]

Yeah, it was a hearbreaker to take a 5k timeline and do a 'theatrical' export to 854x480 (what Portland screens at in this giant 500person theater)

Definitely the most depressing part of the whole competition!