We have developed a clean way to move Premiere projects into Flame solving most of the irritating things like; set to frame size - scale to frame size - fill frame settings in Premiere, retiming, time remapping, mixed frame rates, animated transforms, stills etc. and we are looking for some beta testers.
This started as a Premiere to Resolve app, and now we have ported it to Flame and Baselight. At the moment Flame is Mac only, but the Linux build is underway and we hope to have it ready shortly.
You can see some of the features for the Resolve side on the website: https://konformista.com The site is Resolve specific, since we are not yet in public beta for Flame or Baselight, but most of it translates to flame as well.
If you are interested in in trying it for Flame, get in touch with Jim Cole jim@konformista.com and he will get you setup.
Once you have the linux version working… I’d love to kick the tires.
Ditto
As above when you have e the linuyx version I’d love to test
We are working on the Linux build now and hope to have it ready sometime next week. I will let you know when it’s ready.
Sounds cool.
Broad question, does this require anything specific on the Premiere editors end? Most of us working in commercials do not have any control over the editorials side of the workflow/pipeline. We get an xml, edl (or both), a reference .mp4 and a good luck.
What about nests?
In order to get this to work you need to ask for a Premiere project file (.prproj), The XML and EDL are the reason that we have had to do things manually for so long, because they can’t carry the necessary info. Once they get used to doing it, sending the prproj is even easier than shipping an XML or EDL, since there is no export needed, just a copy of the project file they already have on disk.
Nested sequences come across as Flame containers. Each one sits on the nest’s own track wherever the cut uses it, with the nest’s motion and opacity. You can step inside to work on it, and because the whole nest is in there, you have handles to trim into. Each nest is also in the reel as a sequence of its own.
A few specifics:
Different frame rate: a nest at another rate plays in real time, as it does in Premiere.
Transitions: dissolves and dips work between a clip and a nest, and between two nests.
Sound: a nest’s own volume comes across.
Opened out instead: if you’d rather have a nest’s layers on the timeline, set it to Flattened clips and each layer lands on its own track, framed and cropped as it was in the nest.
Two cases always arrive opened out rather than as containers: a nest that’s been sped up or slowed down, and a nest of a different frame size from the sequence. A dip or wipe across one of those, or a dissolve between two, arrives as a cut. The results page lists what changed before you send it to Flame.
If you have a cut with heavy nesting, I’d be glad to run it through and show you what lands.
What would the Flame-specific output of Konformista be? XMLs that come in correctly? A Flame archive of some sort?
The timeline gets built inside Flame through the API. Any file linking can be done in Konformista before you bring the timeline into Flame. You get info about all linked files, with options to find and link to others if needed (for proxy workflows etc.) and a mock timeline gets built in the app so that you can see what you are sending before you send it. You can collapse tracks, remove graphics, joint through cuts as well as a few other options. Anything that can’t be brought cleanly in gets flagged, as do all effects that were use in Premiere.
We now have a Linux version if you want to try it.