Tuesday, 17 December 2013
Final Cut Pro is Dead….Long live…..something else
So it's finally happened.
I now make more money as an Avid editor than a FCP editor.
Weird.
I fought against Avid for so many years, banging on about how great FCP was and now I am a god damn turn coat.
It does feel strange. It does feel like I backed the wrong horse. This must have been what it was like for people with BetaMax players and Atari STs.
I knew this day would come at some point. I'm still using FCPX at home, but none of the post houses I work for are going anywhere near it. A few have adopted Premiere, but not many. Some are still running FCP, but most seem to be moving to Avid.
Now where did I put that Edit Droid?
Monday, 16 December 2013
Global effects disable
One of the things that's been biting me with my current project is the lack of a global 'turn effects off' toggle. With Neat Video or FilmConvert slammed on a clip (occasionally both) trimming operations are painful, which results in a lot of clicking to disable effects, edit, then re-enable effects.
Ignore the stuff about 'complex clips' – that's the pre-10.0.6 way of doing compound clips which, if you remember, led to so many problems that (a.) people like me avoid compound clips to this day out of some weird folk memory of how bad things were, and (b.) the new way, which suffers basically none of the problems, was introduced.
But that layering technique in compound clips? That's genius.
Hmm. It does mean a bucketload of clicking if you want to adjust effects, though.
Ignore the stuff about 'complex clips' – that's the pre-10.0.6 way of doing compound clips which, if you remember, led to so many problems that (a.) people like me avoid compound clips to this day out of some weird folk memory of how bad things were, and (b.) the new way, which suffers basically none of the problems, was introduced.
But that layering technique in compound clips? That's genius.
Hmm. It does mean a bucketload of clicking if you want to adjust effects, though.
Tuesday, 12 November 2013
Playing around
No, I'm not being tempted into the willing arms of Premiere Pro CS CC CIA MIA MBA. Whatever the current version, I only have eyes for one floozie of an editing package.
But I do find myself tickling the zoom. Being able to edit audio at sub-frame precision is cool and all, but it involves an awful lot of zooming in and out on the timeline. In, to find the itty-bitty little grab handles for audio fades and adjust them carefully enough. Then out, to actually play the edit through without the playhead zipping off the side of the visible timeline and scrolling the viewpoint when I stop it.
Then in again to tweak the edit. Out again to play again. In again. Out again. In. Out.
Sorry, got distracted.
Today, the solution: ⇧/. Whack that sucker, and FCPX will get it on and play around the current playhead position. Once it's done, it returns to the current point.
I am so done with the spacebar. Just as soon as I've mapped ⇧/ to something I can reach with my left hand, my right being otherwise engaged while I'm editing.
With the mouse, obviously.
But I do find myself tickling the zoom. Being able to edit audio at sub-frame precision is cool and all, but it involves an awful lot of zooming in and out on the timeline. In, to find the itty-bitty little grab handles for audio fades and adjust them carefully enough. Then out, to actually play the edit through without the playhead zipping off the side of the visible timeline and scrolling the viewpoint when I stop it.
Then in again to tweak the edit. Out again to play again. In again. Out again. In. Out.
Sorry, got distracted.
Today, the solution: ⇧/. Whack that sucker, and FCPX will get it on and play around the current playhead position. Once it's done, it returns to the current point.
I am so done with the spacebar. Just as soon as I've mapped ⇧/ to something I can reach with my left hand, my right being otherwise engaged while I'm editing.
With the mouse, obviously.
Monday, 11 November 2013
Yes, FCPX is this fast
This isn't Damien cutting his latest piece, but he works about this quickly. I spend far too long gawping at my own pretty pictures; my own time-lapse would look incredibly dull in comparison.
Friday, 1 November 2013
Benchmark that, sucker!
Back in the day of the not-a-law Moore's Law, I had a rule that I only upgraded my Mac when the new system offered three times the performance of the old. That was easy to achieve when moving from, say, a dreadful Power Mac 4400/160 to a Quicksilver G4/933, but it's become progressively more challenging.
My reasoning behind the factor-three rule was straightforward:
Now, my current edit system is a 2008 8-core Mac Pro, which despite being five years old continues to chug along at maybe half the speed of the fastest current Macs. That's both commendable longevity and frustratingly slow progress. For an example of what I mean: every editor's favourite plugin author Alex Gollner has a newly-minted FCPX benchmark: head to this fcp.co thread for the file, example results, and discussion.
My Pro takes about 120 seconds, which to be sure ranks as 'getting a bit old', but even the fastest current Mac struggles to reach a factor two improvement. That's good, but hardly represents the improvement one would like to see after half a decade.
This is why the new Mac Pro is interesting. My 2008 model holds its own because I rammed an upgraded video card into it. It's nothing special, but neither are the cards in the current iMacs. The trashcan Pro not only packs a newer graphics card, it packs two of them. Interesting.
Want an example? That G4/933 could handle noise reduction in video, but only for simplistic algorithms and only for an overnight job. For a short film, the 2008 Pro does a better job over a coffee break. The Trashcan? I'll be interested to see how much it can do in real time.
Factors of three turn special-case tools into everyday tools. They also enable completely new tools, and it's been a while since we've had the capacity to handle those on the desktop.
My reasoning behind the factor-three rule was straightforward:
- Most things happen effectively instantaneously, and they aren't going to get any more instantaneous with a faster system.
- Things that happen merely 'very quickly' add up, but memory capacity and disk performance tend to have more impact here than CPU performance.
- Things that take 10 minutes are an absolute pain, and are to be avoided. Happily, there never seem to be very many operations that take 10 minutes.
- Things that take 20 minutes are 'coffee breaks'. When I'm working, I actually want some operations to fall into this category. They can be a pain, but I can also schedule around them during the day.
- Things that take an hour are where problems start. An hour is too long a break during the working day, which means hour+ processes are best queued up and run overnight.
Now, my current edit system is a 2008 8-core Mac Pro, which despite being five years old continues to chug along at maybe half the speed of the fastest current Macs. That's both commendable longevity and frustratingly slow progress. For an example of what I mean: every editor's favourite plugin author Alex Gollner has a newly-minted FCPX benchmark: head to this fcp.co thread for the file, example results, and discussion.
My Pro takes about 120 seconds, which to be sure ranks as 'getting a bit old', but even the fastest current Mac struggles to reach a factor two improvement. That's good, but hardly represents the improvement one would like to see after half a decade.
This is why the new Mac Pro is interesting. My 2008 model holds its own because I rammed an upgraded video card into it. It's nothing special, but neither are the cards in the current iMacs. The trashcan Pro not only packs a newer graphics card, it packs two of them. Interesting.
Want an example? That G4/933 could handle noise reduction in video, but only for simplistic algorithms and only for an overnight job. For a short film, the 2008 Pro does a better job over a coffee break. The Trashcan? I'll be interested to see how much it can do in real time.
Factors of three turn special-case tools into everyday tools. They also enable completely new tools, and it's been a while since we've had the capacity to handle those on the desktop.
Thursday, 17 October 2013
alt - v // pastey onto-of-y thing
Yes! Press alt v instead of cmd v to paste a clip above the storyline instead of in it!
Why didn't anyone tell me about that!
Wednesday, 11 September 2013
Overwriting Photoshop files automatically updates the file in the Storyline
So.....I'm using a photoshop file in my storyline.....It's actually a layered tiff, but who's counting?
I had to change something in photoshop and I saved over the old file. I was expecting to have to relink media and all that bullshit, but no. The image is automatically updated in the storyline.
That's not normal right? I know it should be normal. And now it is. But that never happened with FCP or AVID did it? I don't think it did. I can't remember, my brain is addled and confused by how awesome FCP is.
That deserves a fanfare. Right?
Subscribe to:
Posts (Atom)
