-
what is editing speed ?
-
[Charlie Austin] “The civil discourse still gets derailed by the same people who’ve always derailed it.”
Since it is rather obviously my civility that you are, no doubt rightly, calling into question, I thought I should try to excuse myself to some degree.
I posted a specific example of a specific real world project with a specific set of source material and a specific very tight deadline to illustrate a point of about editing speed, the topic of this thread. Using this example, I argued for the specific benefits of the subtractive string-out method, as against a subclipping/keywording method, as it pertained to this particular project, the argument being NLE-agnostic. (I wanted to make the broader case for having a pluralistic editing outlook rather than adhering to a rigid, single-system methodology at the expense of others.)
A certain other contributor countered that FCP X was exactly the right tool for this job (although I hadn’t said it wasn’t), and detailed another specific method for achieving the same result.
I then demonstrated, by exactly counting our respective keystrokes, that this other person’s method was up to TWO TIMES SLOWER – when both methods were compared inside FCP X.
In pointing out a basic error of FCPX technique in this other person’s method, I jokingly and unwisely suggested that some elementary training could be helpful – the context for the joke being that this person is in the habit of recommending the same to others at every opportunity.
Rather than take the joke in the spirit in which it was intended, this person then decided to claim, entirely without justification, but repeatedly and vociferously, that I know nothing about how FCP X works.
It is invidious to have to defend my expert knowledge of an application that I use professionally all the time. I will point out that in the very first week of FCP X’s release, I was the leading voice asking Tim to set up the Techniques forum so that those of us who wanted to learn and share tips on working with FCP X could do so in relative peace (as no doubt he can confirm). I have used FCP X continuously ever since. I posted many tips and tricks for FCP X both there and on the (far less prestigious!) fcp.co forum, and of course I published more free Motion templates for FCP X than any other user apart from Alex Gollner. More than that, as a plug-in developer for FCP X (as well as Motion, After Effects and Premiere Pro), I have seen far more than most users here of its dark underbelly where weaknesses still lurk. In providing support to our plug-in users, I have to rely on an in-depth knowledge of FCP X to help them with issues relating to aspects of the application with which they are not conversant. And so on – I won’t labour the point.
It is my view that this person’s unwarranted claim seriously overstepped the bounds of professional courtesy. Certainly it is acceptable to point to specific details that one has got wrong or misunderstood (who knows any application well enough never to make mistakes?), but a blanket claim without adequate/any justification that one of your peers is fundamentally ignorant goes way beyond the rough and tumble of this forum and I hope that most contributors here would agree that it is unacceptable. (Tim right or wrongly agreed to moderate the posts in which this claim was repeated and I am grateful to him for having done so. Many here will be unfamiliar with my contributions to the FCP X community and will have been left with a wildly inaccurate picture.)
I fully accept that I can be overbearing in some of my posts but in this instance I do believe I offered a sufficiently fulsome apology to the person concerned, so perhaps I can be a little more civil than you give me credit for … occasionally. I’ll go away now and leave you all in peace.
Simon Ubsdell
tokyo-uk.com -
There have been enough deserters.
I hope, Simon, you’ll be back on other threads as I, for one, value your balanced opinion and your insight from a developers point of view.
Not to mention, your plugins have helped me tremendously and I hope to see more work in the future.
Hopefully, someday soon, we can return to a more civil discourse.
-
[Phil Lowe] “What my comparison settled for me (if no one else) was that I can do basic, news-style editing using my Avid keyboard settings in X in a way that incurs no time penalty on me, previously expressed misgivings from some notwithstanding.”
I would tend to agree and I don’t think this approach is necessarily wrong. Just a different path to the same destination. As an aside, this article about FCPX in TV enterprise-level installations might be of interest.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Phil Lowe] “The biggest thing for me – in looking at both – is how much more information the Avid timeline presents me without having to hover or click on anything.”
I prefer to see the waveforms in the TL. It’s a shame you have to turn those off for performance.
When a have VO’s I can “see” where the breaks in the takes are and it’s faster to skim up to the next take visually.
I also want to see the video thumbnails to quickly see what’s what.
Those things are more important to me then seeing the length of a source clip when it comes to speed.
That blank TL would slow my workflow down.
-
[Simon Ubsdell] “Since it is rather obviously my civility that you are, no doubt rightly, calling into question, I thought I should try to excuse myself to some degree.”
Simon, I assure you that you were not even in my mind when I wrote that post. Not referring to you at all. I hate the contextless internet sometimes. 🙁
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
Simon –
Please don’t go.
To quote from my favorite Christmas family movie, “The Lion in Winter” when Katharine Hepburn playing Eleanor of Acquitane turns directly to camera and says, at the end of a day when sodomy, patricide, infanticide, treason and incest were running their daily course.
“Well, what family doesn’t have its ups and downs.”
Herb Sevush
Zebra Productions
—————————
nothin’ attached to nothin’
“Deciding the spine is the process of editing” F. Bieberkopf -
[Herb Sevush] “To quote from my favorite Christmas family movie, “The Lion in Winter””
I love that movie – I still have the LP of the soundtrack somewhere, worn out with playing.
Simon Ubsdell
tokyo-uk.com -
[Tero Ahlfors] “So a ripple insert then?”
Well, a magnetic ripple insert, actually.
In X the magnetic timeline has a whole set of behaviors that govern the relationship between adjacent assets in the storyline.
For example, the ripple insert anywhere on the primary doesn’t mess with the sync relationships you’ve established with anything else up or downstream of the area of action.
It’s more than persistent ripple. It’s persistent ripple WITH what amounts to default asset relationship locking.
An environment with different rules.
Know someone who teaches video editing in elementary school, high school or college? Tell them to check out http://www.StartEditingNow.com – video editing curriculum complete with licensed practice content.
-
[Simon Ubsdell] “I love that movie – I still have the LP of the soundtrack somewhere, worn out with playing.”
It is the greatest and only of a unique genre – the screwball medieval family tragi-comedy – it’s “Bringing Up Baby” crossed with”Becket.”
O’Toole: “The day they band together is the day that pigs sprout wings.”
Hepburn: “There’ll be pork in the treetops come morning.”https://www.youtube.com/watch?v=5cVwBjwRGgg
Herb Sevush
Zebra Productions
—————————
nothin’ attached to nothin’
“Deciding the spine is the process of editing” F. BieberkopfSome contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
[Bill Davis] “An environment with different rules.”
It’s a ripple insert. The X timeline prevents unintentional overwrites, but you can do essentially the same thing in Ripple mode in other NLE’s
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~
Reply to this Discussion! Login or Sign Up