-
The NLE that keeps moving forward?
-
[Morten Carlsen] “Imagine a project with about a 1000 media files. In a normal NLE that would take about 1000 double clicks alone to view them.”
Morten,
I’m always surprised by these approaches – did you really work this way? Did you never seem to wonder if there was a better way?
Select All and Drag to Sequence – 1 Click, 1 Drag.
Franz.
-
[Morten Carlsen] “Still – to me the single most important thing is getting the job done. I am a highly visual guy and what makes FCPx the superior choice to me, is the Event Library and its concept. I am a big fan of getting to know my material and “sort on the run” — I am also REALLY big on saving time.”
I’m really big on saving time to, and at the end of the day getting up on that screen what’s in my head.
The thing that I would add about X and speed, is that many of the things that speed up the edit for me by themselves seem small.
The skimmer
tagging
those fade handles
not patching tracks
retiming
Hack, even that Burns (they need to add a control for a pause in there like FX Factory)I could go on, but when you put all these things together they add up to an overall faster experience for me. It’s not just ONE thing, it’s a bunch of things all at the same time.
To me it speaks well to X that the debate has gotten to philosophy. (I can take that or leave it and still get my job done)
It started out as…….X CAN’T do this or that, but apple has kept taking those things off the table.
Leaving fewer and fewer things to point at in the can’t list.It’s just going to come down to which style you like.
-
[Franz Bieberkopf] “Morten,
I’m always surprised by these approaches – did you really work this way? Did you never seem to wonder if there was a better way?
Select All and Drag to Sequence – 1 Click, 1 Drag.
Franz.”
Hi Franz,
well, of course I did… Instead of bins in Premiere Pro (back then) I had sequences with the clips pertaining to scenes.
Still, getting them up into the “Source Viewer” took a kkey command or a double click. I even had my own skimmer in PPRO before they added
hoover scrub or FCPx came about. I had that programmed via apple script and system events. I have misused Premiere Pro and AMC to make it work more visually long before FCPx came about… That is WHY I switched to FCPx when it came about. -
[Morten Carlsen] “That is WHY I switched to FCPx when it came about.”
Morten,
It’s been interesting to watch FCPX discussion particularly around efficiency and speed.
The claim often repeated here is that you have to understand FCPX to use it properly – ie. there is an “optimum” approach.
But yours is not the first post that makes me wonder about how others use their NLE of choice (now and in the past). 1000 double clicks? and further down Tony West talking about patching tracks slowing him down. (I don’t think I’ve ever patched a track in 10 years or more of using FCP).
It’s interesting because there are often claims about users “not understanding” FCPX but I read stuff like that I wonder which users “understand” the current the NLE they use. I’ve seen all sorts of bad habits, and poorly thought-out process. It seems to me that’s true regardless of NLE – in other words any NLE requires understanding how to optimize the software to the task.
The 10 x speed claims are pretty funny though – if somebody told me their new software allowed them to edit ten times faster (transcoding, rendering, exporting times aside), I would really wonder about their editing practice.
Franz.
-
[Franz Bieberkopf] “The 10 x speed claims are pretty funny though – if somebody told me their new software allowed them to edit ten times faster (transcoding, rendering, exporting times aside), I would really wonder about their editing practice.
“I think these claims just give ammunition to FCPX detractors, objectively no NLE can be 10x faster in overall operation than another in the hands of a skilled Editor, but if it’s faster for the person using it, regardless of their previous editing practice, then that has to be a good thing doesn’t it?
Steve Connor
‘It’s just my opinion, with an occasional fact thrown in for good measure” -
[Steve Connor] “… if it’s faster for the person using it, regardless of their previous editing practice, then that has to be a good thing doesn’t it?”
Steve,
This is a common refrain here. But I’ve not made claims against people feeling good about what they do. If someone is feeling good about the software their using, that’s a good foundation for work.
For me claims of speed beg the question – what is it faster at doing? If someone claims it’s faster at “editing” then I’m going to wonder about what they really mean.
My point above is that the speed claims may say as much about previous practice as it does about new software.
Franz.
-
[Franz Bieberkopf] “My point above is that the speed claims may say as much about previous practice as it does about new software.
“Maybe true in some cases, but pretty much everyone who uses FCPX on real world projects say it’s faster, surely that has some weight? Not everyone who uses it was inefficient with using other NLE’s surely?
Steve Connor
‘It’s just my opinion, with an occasional fact thrown in for good measure” -
[Steve Connor] “… but pretty much everyone who uses FCPX on real world projects say it’s faster, surely that has some weight? Not everyone who uses it was inefficient with using other NLE’s surely?”
Steve,
I think people who try it and stick with it are the ones that like it – “speed” seems to be cited often. I think you probably won’t hear much from those who find it clunkier or slower – they just won’t use it – though there has been some notes (from Oliver Peters in particular) about things that tend to bog him down in FCPX.
That doesn’t answer the real speed question, though.
“Speed” relates to specific tasks, or general approaches. I’ve been working on the same scene assembly for over a week now – it’s been ridiculously slow. And though render speeds are slow, nothing about the NLE I’m using has had a meaningful impact on the speed of the process. This wouldn’t have been any faster in X, PPro, Avid – the issues are creative.
When you hear complaints about double clicking on 1000 clips, doesn’t it raise process questions?
Franz.
-
[Franz Bieberkopf] “further down Tony West talking about patching tracks slowing him down. (I don’t think I’ve ever patched a track in 10 years or more of using FCP).”
Just selecting where the audio from a clip of b-roll would go.
I don’t do that now. The sound of that b-roll of say a truck just goes with the video of the truck since they are imbedded.
I’m dropping the single item in a spot not multiple ones. Clearer?
I could break them apart if I wanted to most time I don’t have a need to. I want them to ride together.
-
Yes, but I’m imagining it was an extreme example to make a point.
Steve Connor
‘It’s just my opinion, with an occasional fact thrown in for good measure”
Reply to this Discussion! Login or Sign Up