“It’s the Tesla of NLEs”

[Bill Davis]

Hey, what does an ex-AVID nerd hanging around WGBH in Boston know, anyway.

And X workflows can’t be this fast, because – (long pause) well it just because.

Creator of XinTwo – https://www.xintwo.com
The shortest path to FCP X mastery.

[Herb Sevush]

[Bill Davis] “And X workflows can’t be this fast, because – (long pause) well it just because.”

Nice article, especially since the workflow is so similar to mine, as is the town it was shot in. The Quiz show format is a simpler version of the cooking shows I do, with the same multicam concerns and the 26:46 PBS spec for finished shows.

Herb Sevush
Zebra Productions
—————————
nothin\’ attached to nothin\’
\”Deciding the spine is the process of editing\” F. Bieberkopf

[Bill Davis]

Glad it was of interest to you.

X has always been about exposing more of the metadata flow to end users so they could find ways to leverage it into unique efficiencies.

When Phil and Greg formed Lumberjack systems to leverage that exposure, they worked with both FCP X and Premiere Pro implementations.

I obviously can’t speak for them, but it has always seemed to me as an observer, that the level of exposure available in FCP X – particularly the way it’s purpose built to track not just “whole clips” but agiley described ranges within clips -gave it real advantages for the type of prep work this article highlights.

It’s taken quite a bit of time for the advantages some of us felt it would enable – to percolate down into real-world workflows.

But I think this is more evidence that it’s now happening and will continue to accellerate.

Creator of XinTwo – https://www.xintwo.com
The shortest path to FCP X mastery.

[Herb Sevush]

[Bill Davis] “When Phil and Greg formed Lumberjack systems to leverage that exposure, they worked with both FCP X and Premiere Pro implementations.”

I have used some of Phil’s utilities in the past, they’ve always been great. When I went to the website it looks like Lumberjack is only for FCPX – I take it the Premiere implementation didn’t work out?

Herb Sevush
Zebra Productions
—————————
nothin\’ attached to nothin\’
\”Deciding the spine is the process of editing\” F. Bieberkopf

[Bill Davis]

[Herb Sevush] “I have used some of Phil’s utilities in the past, they’ve always been great. When I went to the website it looks like Lumberjack is only for FCPX – I take it the Premiere implementation didn’t work out?”

Don’t know.

Back on Gone Girl, I believe they were working (perhaps peripherally?) with Premiere Pro.

And I know they have products that are designed to translate between the environments with their X to CC product.

But I don’t know the current status of where they are focused regarding development.

When we talk NLE stuff, it’s exclusively about FCP X, as you’d imagine.

Creator of XinTwo – https://www.xintwo.com
The shortest path to FCP X mastery.

[Robin S. kurz]

[Herb Sevush] “I take it the Premiere implementation didn’t work out?”

No, there simply is little to no point. Or how do you see that working out? PPro doesn’t even do half the metadata that Final Cut Pro X does (in the sense of actually putting it to any helpful use) and uses it in completely different ways. Lumberjack caters specifically to FCP’s metadata capabilities. The mere fact that PPro is stuck in a near 20 year old time-loop with its use of an age old version of XML excludes it from even being able to access everything of functional use and value that LJ spits out. I suppose I could see e.g. the automatic keyword-based string outs working, but I’m guessing it pretty much ends there. Since how are you going to get that information into PPro?? XMEML is far too limited (little more than an EDL on steroids by today’s standards) and Adobe is clearly more interested in keeping you isolated in their own little ecosystem (and Avid even more so for that matter) to ever consider supporting something like FCPXML.

– RK

____________________________________________________
Deutsch? Hier gibt es ein umfassendes FCP X Training für dich!

[Andy Patterson]

[Robin S. Kurz] “PPro doesn’t even do half the metadata that Final Cut Pro X does (in the sense of actually putting it to any helpful use) and uses it in completely different ways. Lumberjack caters specifically to FCP’s metadata capabilities. The mere fact that PPro is stuck in a near 20 year old time-loop with its use of an age old version of XML excludes it from even being able to access everything of functional use and value that LJ spits out.”

Keep in mind Premiere can accept metadata form Adobe Story, Bridge, AE, Audition etc. Premiere Pro is also cross platform. Premiere Pro does not have a timeline index but we can find content in the timeline. Premiere Pro does not have keywords but it does have metadata fields. Both FCPX and Premiere Pro (Adobe in general) offer more metadata than most users will actually use. Having said that I always find it fascinating when FCPX user hail Apple as the pioneers of metadata and keywords but then again there are some FCPX user who think Apple invented background rendering and GPU acceleration. FCPX has good metadata capabilities but then again so does Premiere Pro. FCPX will get better but then again so will Premiere Pro.

https://www.youtube.com/watch?v=KTYDiKTLlyk

Some 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.

[Andy Patterson]

[Robin S. Kurz] “PPro doesn’t even do half the metadata that Final Cut Pro X does (in the sense of actually putting it to any helpful use) and uses it in completely different ways. Lumberjack caters specifically to FCP’s metadata capabilities. The mere fact that PPro is stuck in a near 20 year old time-loop with its use of an age old version of XML excludes it from even being able to access everything of functional use and value that LJ spits out.”

Keep in mind Premiere can accept metadata form Adobe Story, Bridge, AE, Audition etc. Premiere Pro is also cross platform. Premiere Pro does not have a timeline index but we can find content in the timeline. Premiere Pro does not have keywords but it does have metadata fields. Both FCPX and Premiere Pro (Adobe in general) offer more metadata than most users will actually use. Having said that I always find it fascinating when FCPX user hail Apple as the pioneers of metadata and keywords but then again there are some FCPX user who think Apple invented background rendering and GPU acceleration. FCPX has good metadata capabilities but then again so does Premiere Pro. FCPX will get better but then again so will Premiere Pro.

https://www.youtube.com/watch?v=KTYDiKTLlyk

https://www.youtube.com/watch?v=h6dLFBm7kJQ

Some 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.

[Brian Seegmiller]

How do you implement those smart collections into Premiere Pro CC?

[Andy Patterson]

[Brian Seegmiller] “How do you implement those smart collections into Premiere Pro CC?”

Premiere uses metadata fields but bridge used keywords and keyword collections prior to the launch of FCPX. Having said that Adobe is no stranger to metadata and all the Adobe programs will get better just like FCPX.