Scenery’s XML import feature lets you import XML files exported from Adobe Premiere Pro. This allows you to convert a simple Premiere Pro sequence into a Scene in Scenery.
How it works
These are the major steps you will follow, and you should do them in this order:
Collect the media used by your Premiere Pro sequence
Export an XML file from your sequence in Premiere Pro
Import/Upload the media to Scenery
After the media is done processing, import/upload the XML file into Scenery
Collect media using Premiere’s Project Manager
To successfully import an XML file from Premiere Pro into Scenery, you need to first upload all the media files used by the Premiere Pro sequence to Scenery and let them finish processing.
The Project Manager in Premiere Pro is a helpful tool to help you collect the media files used by the sequence you want to export to Scenery through XML.
The Project Manager copies selected sequences into a new Premiere Pro project, and either collects and copies the referenced media to a new destination or creates new transcoded and trimmed media files with handles.
How to: Collect media using Premiere Pro’s Project Manager
Make sure the Premiere Pro project that contains the sequence is active, then choose File > Project Manager…
Under the “Sequence” section, enable the checkbox for the sequence you wish to collect the media for
Under “Resulting Project”, choose whether you want to copy the entirety of the used media files, or if you want to Consolidate and Transcode, which creates trimmed media
Under “Options”, choose Exclude Unused Clips
Under “Options”, review the Handles size if you are trimming the media
Under “Options”, turn off Include Audio Conform Files
Under “Options”, turn off Include Preview Files
Under “Destination Path”, select the location of the new Premiere Pro project and the copied media files
Click OK
Premiere Pro processes and copies files
Note: the project manager does not collect accessory files like LUTs
In the Finder or Windows Explorer, navigate to the destination folder that contains the folder with the newly-created Premiere Pro project file (.prproj) and media files
Export XML from Premiere Pro
Open the Premiere Pro project file (.prproj) you created in the previous step
Select the sequence in the new project and export it to XML File > Export > Final Cut Pro XML…
The version of XML that is exported by Adobe Premiere Pro is technically an XML format created by the previous generation of Final Cut Pro from 2003-2011. This XML cannot be exported from the current generation of Final Cut Pro.
Upload media and import the XML into Scenery
In Scenery, create or open the project into which you want to add the sequence from Premiere Pro
Create a new collection
This is not strictly required, but it can be helpful to keep your imported media in one place.
Upload the media files created in the Project Manager destination folder into the new collection you created in Scenery
After the media has finished processing in Scenery, import the XML file into the same collection by dragging the XML file into it.
Scenery creates a new Scene from the XML and it opens in the Timeline
Import warnings
Because some features of a Premiere Pro timeline are lost when sending an XML to Scenery, it is important to know what didn’t translate.
When Scenery detects unsupported features, it presents a dialog listing the known issues and invites you to download a report in HTML format. Click Continue to download the report file. If you click Cancel, the dialog dismisses without downloading the report.
When the user clicks Continue, Scenery downloads an HTML file that lists unsupported features together with the clip name and its location in scene time.
You can open the HTML file in any browser and refer to it while reviewing the newly-created scene.
Features from Premiere Pro that translate to Scenery
All parameters are constant values only.
If parameters are keyframed, Scenery takes the value of the first keyframe.
| Note |
Scale | Parameter found in Effect Controls>Video>MotionTest non-uniform scale as well |
Position | Parameter found in Effect Controls>Video>Motion |
Rotation | Parameter found in Effect Controls>Video>Motion |
Opacity | Parameter found in Effect Controls>Video>Opacity |
Crop | Crop in Premiere comes from Effects>Video Effects>Transform>Crop |
Cross Dissolve | transitions between two clips are set to centered-on cut |
Audio clip volume/level | need to test with Scenery audio keyframes when they turned on |
Speed | Not time-remapping. This is from Speed command accessed via right-click on timeline clip.Negative speeds not supportedSpeeds outside of Scenery’s supported range (25%-400%) adjusted to within Scenery’s range |
Text clips | Contents of Premiere Pro text clips are placed into a Scenery Basic Text clip (no style) |
Clip markers | Translate to Clip Comments (both single frame and with duration) |
Sequence markers | Translate to Scene Comments (both single frame and with duration) |
Clip enabled state | Audio and Video cannot be enabled/disabled separately |
Merged clips | These result in synced clips in Scenery’s timeline |
Features we know don’t translate
| Note |
Non-standard edit rates | Sequence edit rates can only be among those that Scenery supports (23.98, 24, 25, 29.97, 30, 50, 59.94, or 60). Other edit rates are changed on import into Scenery. |
Scene sizes larger than 1920x1920 | Sequences with dimensions larger than 1920x1920 will be scaled to fit Scenery’s limit. |
LUTs |
|
Video Transitions | Transitions get turned into Cross Dissolves, they don’t actually translate |
Video effects |
|
Audio effects |
|
Blending modes |
|
Audio transitions |
|
Audio volume/level keyframes |
|
Time remapping |
|
Freeze frame (Frame hold) |
|
Nested sequence |
|
Multicam | Multicam clips are not exported to XML by Premiere Pro |
Renamed clips | Clips that are renamed in Premiere don’t keep the name in Scenery, Scenery only uses the file name |
Subclip names | Scenery only uses the file name, subclip names are not used |
Track volume |
|
Transcriptions | Premiere Pro transcription data is not exported to XML |
Clip metadata like Description, Log Note, and Comment |
|