-
FCPX Is Now A Universal Logging and Organizing Tool For Any NLE
-
[David Lawrence] “I presume that any NLE that can import bins, clips, subclips and Log Note metadata from standard FCP7 XML will work.”
You presume that all NLE’s have XML support. Avid does not.
[David Lawrence] “Maybe *any* is too strong a word. It should work with any NLE that properly reads FCP7 XML.”
And that would be darn few:
Premiere Pro
Resolve (but it isn’t an NLE…yet)Buck stops there.
So now you are saying in order to utilize the great “Universal logging and organization tool” known as FCX, you need to buy:
FCX – $299
Xto7 – $50
Find a copy of FCP 7…unless you already own it. But…$1000And then either use FCP 7 to edit (3 years old, EOL)…or Premiere Pro CC (shiny, new…current)
So FCX/Xto7 is a great $350 logging and organizing tool for Premiere Pro or FCP 7.
Getting this to Avid by adding Resolve Lite to the mix, doing a lot of transcoding in there…but then that’ll get you media, not the bin structure.
Nope…great $350 solution for working with Premiere Pro or FCP 7.
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
[TImothy Auld] “Just curious, Walter. Are you saying I am delusional?”
No, Tim, I’m not saying that at all.
In another thread [link], and again up above, I thought that the debate over whether FCP X could be used for a “complex project” was more or less over, and that FCP X criticism had largely moved on to specific workflow needs and personal preference. I thought that the FCP X community was continuing to litigate a settled issue, trying to prove that FCP X can be used in the real world when proof is no longer required.
Your question, which you repeated for emphasis, shows that I was mistaken. There are obviously still professionals who question FCP X, so I understand better now why FCP X supporters still feel the need to justify or defend their own choices and professionalism.
Really, Tim, nothing directed at you. I think you’re entitled to your opinion.
Walter Soyka
Designer & Mad Scientist at Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive | RenderBreak [blog] | Profile [LinkedIn] -
If that debate were over then at $299 I would be using it – and believe me I have tried really hard to do so. As have many other producers and editors I know.
Tim
-
Thinking out loud — another possible Avid workflow:
FCP7 can probably be skipped if you made stringout sequences from your smart collections.
Then, the Xto7 output XMEMLs could be converted to ALE via XMiL Sequencer or maybe Sebsky Tools.
I’m not sure how much metadata would carry over that way, but you might at least be able to get the right footage into a set of organized bins.
Walter Soyka
Designer & Mad Scientist at Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive | RenderBreak [blog] | Profile [LinkedIn] -
Walter,
I checked with my contacts in the secret cabal that is trying to control the editing universe via FCP X. Your temporary blasphemy is provisionally forgiven. Carry on.
(Required sign off since I’m in an airport at the moment.)
; )
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.
-
[Shane Ross] “You presume that all NLE’s have XML support.”
An elements that hasn’t been mentioned is the reason for FCP 7. The Xto7 conversion to an XML does not cleanly transfer the info into Premiere Pro directly. This is fixed by “washing” the XML through FCP 7. That happens in a lot of instances. XML compatibility in general is still very much a moving target.
[Shane Ross] “And that would be darn few:”
Add Smoke to that list. Possibly also Vegas and Lightworks, though, I haven’t actually checked the latter.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Oliver Peters] “An elements that hasn’t been mentioned is the reason for FCP 7. The Xto7 conversion to an XML does not cleanly transfer the info into Premiere Pro directly. This is fixed by “washing” the XML through FCP 7. That happens in a lot of instances. XML compatibility in general is still very much a moving target.”
Is that also true of the latest versions? I don’t have personal experience, but the Xto7 web page actually lists Premiere Pro support before FCP7:
https://assistedediting.intelligentassistance.com/Xto7/
What doesn’t work right?
Walter Soyka
Designer & Mad Scientist at Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive | RenderBreak [blog] | Profile [LinkedIn] -
[TImothy Auld] “If that debate were over then at $299 I would be using it – and believe me I have tried really hard to do so. As have many other producers and editors I know.”
There’s a difference between “doesn’t work for my needs” or “not my personal preference” and “who in their right mind would use this?”
I’m not saying I thought the debate was over, just that I didn’t realize we were still questioning each others’ sanity anymore. I thought was reserved for discussions of subscription software!
Walter Soyka
Designer & Mad Scientist at Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive | RenderBreak [blog] | Profile [LinkedIn] -
[Walter Soyka] “Is that also true of the latest versions?”
I haven’t tested the version released today, but basically the answer is yes. It varies with what info you want to come across correctly. Sometimes an FCP 7 XML out of Xto7 will be perfect going into Premiere directly. Other times, you need to run it through FCP 7 first.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
[Richard Herd] “I’m having a terrible time using subclips in CS6 because they do not slip and roll. How do you solve that?”
I tested on a machine with FCP7, CS6 and CC. I don’t have an Avid so I’m waiting for my brother in LA to do a test later tonight. EDIT: Shane says Avid doesn’t support XML so I guess that won’t work.
In FCP7, command-option-F reveals the subclip frame in the parent clip.
In CS6, the workflow is you open the subclip in the source browser, mark in and out for the entire subclip, then edit the subclip’s start and end times using the Edit Subclip… menu item.
You can then drop the subclip into the timeline and extend or slip and roll.
CC’s checkbox for subclip boundaries is certainly more elegant, but you don’t need to use CC to be able to extend subclip boundaries in Premiere. Give it a try and let me know if it works for you.
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
https://lnkd.in/Cfz92F
facebook.com/dlawrence
twitter.com/dhl
vimeo.com/dlawrence/albums
Reply to this Discussion! Login or Sign Up