-
New blog post from Philip Hodgetts. Worth the read.
-
[Franz Bieberkopf] “Good comparisons are hard to come by; good discussions, harder?”
Did you actually read the rest of the post before hitting send? No offense, but your statement seems to contradict your intention.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Franz Bieberkopf] I’ll add to the compliments to you Jeremy (and those here in general): This forum offers so much more perspective.
That’s from my post down below – but if it isn’t clear, I think this forum is great!
My comment in post above was referring to PH orig blog – I’m not sure what it contributes.
Franz.
-
“And you have a CUDA as part of your setup?”
Yes, my main workstation (at work) has a Quadro FX 4800 and my home machines have FX 3800 and 1700 cards respectively. Again, I’m a Windows user so I can’t speak to the performance of my Mac OS counterparts.
Shawn
-
[Oliver Peters] “Sheesh! Why is Smoke even part of this discussion?”
I brought it up as a counterexample to Philip Hodgett’s nebulous claim that “FCPX is 200% to 400% faster.”
When Autodesk claims to be faster, they are very specific: they are 35% faster at finishing than a multi-app workflow, and they back it up with some data.
You’ll get no argument from me that FCPX is faster than FCP7 at many tasks, but I think that an effort to quantify it and its real impact on editorial deserves more specificity.
Walter Soyka
Principal & Designer at Keen Live
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
RenderBreak Blog – What I’m thinking when my workstation’s thinking
Creative Cow Forum Host: Live & Stage Events -
Shane, I definitely second what you are saying here.
-
Still comes back to the fact that some of us who are actually USING the software are reporting it’s faster for our work. If it were any other software people might take that as evidence that at least it might be partially correct ( 400% iimprovement is certainly not!)
“My Name is Steve and I’m an FCPX user”
-
Steve, I totally believe it is faster for you. I’m not doubting you at all. But when I try to work the equation of how it can be faster for me, I don’t see it. It is not a religious thing. Or a pride thing. Or even a habit thing. Really.
Maybe someday. I mean, I can’t even use it now, but maybe someday. I’m open. But not enough to jump off a cliff with it. But, I do believe you.
-
[Shane Ross] “The NLE cannot speed up my process of looking at footage, and listening to music. If the producers want things faster, then they’ll get something that is “good enough.” Because that is all they are giving me time for.”
Absolutely true Shane.
This is why I’ve been saying from the very beginning that FCPX is a solution looking for a problem.
David Roth Weiss
Director/Editor/Colorist
David Weiss Productions, Inc.
Los Angeles
https://www.drwfilms.comDon’t miss my new Creative Cow Podcast: Bringing “The Whale” to the Big Screen:
https://library.creativecow.net/weiss_roth_david/Podcast-Series-2-MikeParfitandSuzanneChisholm/1POST-PRODUCTION WITHOUT THE USUAL INSANITY ™
Creative COW contributing editor and a forum host of the Business & Marketing and Apple Final Cut Pro forums.
-
[Jeremy Garchow] “[Herb Sevush] “In PPro why would you want to make proxy files? (not being argumentative, just trying to understand.) What’s the advantage of Proxies if you can edit natively?”
It depends on your workflow. For instance, I just got off a shoot were we shot 4kHD Epic R3Ds and Alexa ProRes 444 LogC.
This footage will need to live a few different computers, there’s a desktop machine were it will finish and a few laptops. Most of the initial cuts are done here in house, then at some point we will take a laptop over to the clients (as it’s much easier for them for us to go over there) and then fine tune the final edits before coming back here for finish and output for broadcast. Having a lightweight Proxy workflow makes this doable. The Alexa footage can pretty much be handled natively on a laptop, even with a LogC to video filter on all the footage. The red Footage has been transcoded to ProResLT. If we wanted to move even faster, I would bake a 709 LUT in to the Alexa clips, but things seem to be OK with the 444 material.”
I gather then, that what Jeremy really meant to say is that proxies may be desirable in PrPro when working in conjunction with other, less native capable, systems. Neither Red nor Alexa material require them, that I’m aware of…though I’m not sure about Alexa Raw. Maybe Dennis R. can address that.
David
AllinOneFilms.com -
[Jeremy Garchow] “[Chris Harlan] “I’d probably be interested in Smoke, if it weren’t unjustifiable overkill for what I do. But, if the right project comes…”
By the way, Smoke would seemingly be awesome for us too, but alas to get 4 seats of it isn’t quite practical at this time, even 2 seats. I have high hopes for the next CS release. We use the rest of the Adobe suite all the time, and I am curious what’s going to happen with the Speedgrade acquisition.
“
Keep it down. Oliver doesn’t want us talking about this.
Reply to this Discussion! Login or Sign Up