-
What was your biggest bottleneck in 2013?
-
Like Simon, mine was AMA in Media Composer. POS.
And like Shane, those further up the food chain who’ve never made a program but somehow have contrived to be in a position to tell you that you can’t.
Can I get a plug in for that? If so, what calibre?
_________________________________
Before you criticise a man, walk a mile in his shoes.
Then when you do criticise him, you’ll be a mile away. And have his shoes. -
- Script change versioning/collaboration, and storyboard creation. Nothing costs me more time in revisions and confusion than these two.
- Moving large amounts of data from local to SAN to LTO to SAN, and then making a local and offsite archive of everything.
- Never enough reliable upstream bandwidth.
- I used FCPX a fair amount in 2013, and creative editing sped up for me because of it. The new Event structure is slower for me, unfortunately. (But I do like Libraries)
- Our MacPros need to be relegated to iTunes servers, but I’m really looking forward to new MacPros, especially after getting a brand new laptop at the end of 2013 and getting a feel for Apple’s new hardware.
- Creative Cow
- Creative Cow
- Creative Cow
-
I find that some plug-ins will take longer to render than others. Could be a setting I am missing. The biggest one is the lack of “Send To Motion” command. Why they have not brought back this feature is beyond me.
-
My mac pro (soon to be replaced… roll on Shipping in February)
Bugs in FCPX which still aren’t resolved.
Annoying design choices in FCPX that still haven’t been resolved.
Personal procrastination and a love of life over work.
-
This varies a lot from project to project. “Rendering” is in general a problem, not sure how to quantify that as a “bottleneck”. We’re about to move to a new MacPro 2013-system from our older 2008 machine so we will see quite a boost in this area but I’m not sure it will “revolutionize” things as much as one would hope. We shall see…
A lot of manual work in prepping projects for example won’t change as this isn’t really a CPU, GPU och i/o limitation. What ever system we move to from our current (FCP7 / Color / AE) seems to have similar issue. Premier Pro CC doesn’t solve anything for us really, I’ve tried it on a few projects and for us the mercury engine and AE-integration is completely overrated and doesn’t even work as intended a lot of times. I have been quite impressed by what FCPX can do on modern systems but again it won’t solve everything. FCPX + Resolve should, in theory, be a much faster turn-around solution than FCP7 + Color but for us FCPX still lacks a few basics we constantly use (batch-exporting, SD-projects).
We work in short-form relatively high end advertising post production so lots of edits, but normally between 10s and 60s in length.
-
Great question.
For me, it was rendering NeatVideo’s “Reduce Noise” filter across 2 hours of fullHD captured cinefilm transfers I had been doing.
It took 36 hours! Made for some fantastic footage though.
27″ iMac 2.7GHz Intel Core i5, 16gb RAM, FCPX
http://www.apricotweddings.co.uk
-
Sluggishness when having many events open at the same time. However, I will say this was an even greater problem when FCP 7 had to access large amounts of material from multiple drives. And dealing with sparse bundles. It works for me, but there are pitfalls and limitations.
Biggest time savings. FCP X speed with finding footage when not bogged down. And FCP X almost never crashes and when it does I don’t lose anything. I calculated that I probably saved about 40 hours over the year with this compared to FCP 7.
-
Clients.
Scott Witthaus
Senior Editor/Post Production Supervisor
1708 Inc./Editorial
Professor, VCU Brandcenter
Reply to this Discussion! Login or Sign Up