Activity › Forums › Creative Community Conversations › Frame.io meets Adobe Premiere Pro
-
Frame.io meets Adobe Premiere Pro
Andrew Kimery replied 8 years, 7 months ago 12 Members · 40 Replies
-
Herb Sevush
March 25, 2016 at 3:54 pm[Jeremy Garchow] ” One of my major gripes with Premiere is it’s project organization. Files seem to double and triple in the browser for no reason, especially when you start adding versions of timelines via XML.”
Too true.
Herb Sevush
Zebra Productions
—————————
nothin\’ attached to nothin\’
\”Deciding the spine is the process of editing\” F. Bieberkopf -
Charlie Austin
March 25, 2016 at 4:05 pmIt’s very cool. Essentially it’s the exact same functionality as the Standalone X App, but integrated into the UI. The panel can control the Pr UI to see extent, but other than that it’s a one mostly way street. PR->the panel. You can drag from the panel to a bin (Import media), but not into the Timeline. I don’t think the frame.io folks are “done” with integration to either NLE. 🙂 Pr panels are HTML/CSS, you could probably do something very similar in X using FxPlug, though Apple doesn’t want you to mess with the UI. Alex 4D summed it up when he said:
Apple sticking point: “We don’t trust third parties with our UI”
Adobe sticking point: “Who needs a public interchange format when everything can be done within our suite”————————————————————-
~ My FCPX Babbling blog ~
~\”It is a poor craftsman who blames his tools.\”~
~\”The function you just attempted is not yet implemented\”~ -
Andrew Kimery
March 25, 2016 at 4:29 pm[Jeremy Garchow] ” Files seem to double and triple in the browser for no reason, especially when you start adding versions of timelines via XML. “
If you are sharing between PPro users have you tried using the Export->Selection as Premiere Project option, as opposed to XML, and then using the Media Browser to import what you need into your project? I’ve never used it but it seems like it could work better than XML.
-
Andrew Kimery
March 25, 2016 at 4:29 pm[Charlie Austin] “Adobe sticking point: “Who needs a public interchange format when everything can be done within our suite””
Aren’t AAF, FCP XML, OMF, EDL, etc., public interchange formats?
-
Jeremy Garchow
March 25, 2016 at 5:02 pm[Andrew Kimery] “If you are sharing between PPro users have you tried using the Export->Selection as Premiere Project option, as opposed to XML, and then using the Media Browser to import what you need into your project?”
Rarely, do I need to share edits between multiple Pr users, at least in my case. It’s usually going to/from some other application like FCPX/Baselight/Ae/Compositing via some form of interchange.
Relinking in Pr is also not great, when you need to relink to a subset of media from the original.
I would be very happy if a third party allowed me to do conforms in FCPX and not try and use Pr as the third party tool (or if Apple wrote in better conform capability).
-
Charlie Austin
March 25, 2016 at 5:17 pm[Andrew Kimery] “Aren’t AAF, FCP XML, OMF, EDL, etc., public interchange formats?”
Yeah, rereading his quote I think he was referring to FxPlug vs Panels, but the analogy doesn’t really make much sense.
————————————————————-
~ My FCPX Babbling blog ~
~\”It is a poor craftsman who blames his tools.\”~
~\”The function you just attempted is not yet implemented\”~ -
Andrew Kimery
March 25, 2016 at 5:23 pm[Jeremy Garchow] “Rarely, do I need to share edits between multiple Pr users, at least in my case. It’s usually going to/from some other application like FCPX/Baselight/Ae/Compositing via some form of interchange.
“Ah, I see. I think PPro relies a lot on XMP metadata and other metadata that the Media Browser reads on import to keep things straight so if you use an XML or the normal Import command it is more likely to not recognize that the right media already exists in the project.
-
Andrew Kimery
March 25, 2016 at 5:25 pm[Charlie Austin] “Yeah, rereading his quote I think he was referring to FxPlug vs Panels,”
Ah, thanks for the clarification.
-
Walter Soyka
March 25, 2016 at 6:15 pm[Andrew Kimery] “PPro relies a lot on XMP metadata”
The trick for non-duplication is to allow Premiere to enable “Write XMP ID to files on import,” then import everything into one Premiere project first before you begin. This will inject an unique ID into each file, and then Pr will recognize the same clip coming from different sequences in different projects.
Walter Soyka
Designer & Mad Scientist at Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive | RenderBreak [blog] | Profile [LinkedIn] -
Jeremy Garchow
March 25, 2016 at 6:16 pm[Walter Soyka] “The trick for non-duplication is to allow Premiere to enable “Write XMP ID to files on import,” then import everything into one Premiere project first before you begin”
Famous last words.
Reply to this Discussion! Login or Sign Up