How can we improve Premiere Pro?

← Premiere Pro

Relative Export Paths PLEASE!

The fact that Pr always defaults to the last export location, regardless of which project is exported from, is completely illogical. Why would a user ever want to export Project B's sequence into the last used export folder if that folder belongs to Project A, for example? (see illustration 1)

There are already about a half dozen FRs that ask for this to be fixed, however since they only offer half baked solutions, I'm posting a new FR, offering a full fledged solution.

The solution is simple:
Provide a new 'Export' tab in the Preferences window that allows users to define the default location they want all of their projects to export to (both from Export Settings and Quick Export). (see illustration 2)

A 'Relative path' checkbox would allow users to make the export path relative to each project. In the illustration's example, the location is set to .\Exports. This means exports from Project A will automatically appear inside a folder named 'Exports' next to project 'Project A.prproj', and exports from Project B will appear in Project B's 'Export' folder, and so forth. If an export folder doesn't exist, Pr would automatically create it upon export.

Should a user wish to automatically export to the same location regardless of which project is exported from, setting this up would be as easy as browsing to one's preferred export location (for example, a "Pr Exports" folder on the Desktop), and unchecking 'Relative path'.

Note that these options would only set each project's DEFAULT export location. If a user chooses to export to a different location from a certain project, then that (and only that) project's default export location would be automatically set to this new location.

Example:
Project A: User exports to Desktop = New default export location for Project A set to Desktop

Project B: Default export location continues to be 'Export' folder (next to Project B.prproj)

This workflow would address the needs of all editors: those who want exports saved in locations relative to each individual project, as well as those who want exports from all projects to appear in the same place!

The current exporting behavior makes zero sense and is incredibly frustrating, especially for editors who work on more than one project at a time. Please fix this already! Thank you!

80 votes

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Pierre Louis Beranek shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

17 comments

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Lucas Triebl commented  ·   ·  Flag as inappropriate

    Totally agree on that - pain in the A**. Even a simple generall setting to choose wheter export path should be recent folder/location or projects folder / location would be better than what we have now.

    This should be implemented for ALL Adobe CS apps like PS, AI, ID.

  • Alexandre Verreault commented  ·   ·  Flag as inappropriate

    Just remember the path of the last exportation of each project and same thing for file importation could save a lot of time!

  • Gammel Sami commented  ·   ·  Flag as inappropriate

    Or a much simpler solution: If the last used path of any path-picker was within the project directory, remember it as relative. And a checkbox in the settings to disable relative paths.

  • Michelle Dillard commented  ·   ·  Flag as inappropriate

    Thank you Pierre for consolidating all of these into a single cohesive thread. For the love of all that's good and pure, I really hope they finally fix this already.

  • Antoine Autokroma commented  ·   ·  Flag as inappropriate

    For AfterCodecs https://www.autokroma.com/AfterCodecs

    what I could potentially do is have a way to change the output dynamically in the filename with variables for example {{project}} would be the path of the .prproj then if I detect then I don't use the folder where Premiere Pro wants to render. We could have more macros like {{..}} would go one folder up etc.

  • Tor Sandum commented  ·   ·  Flag as inappropriate

    Very good job on this. I get incredibly sweaty just looking at your relative vs. global mock-up. It's so illogical it should't have made it past the drawing board.

    Hoping this get's prioritized!

  • Pierre Louis Beranek commented  ·   ·  Flag as inappropriate

    Hi Trevor, I think what you're asking for perhaps falls outside the realm of what we can reasonably expect from Adobe since it would introduce complexity unneeded by most users.

    Do you know about the plug-in Excalibur? It has export options that might suit your needs. It can't export a range based on the Work Area bar for now, but it can use in/out points to determine this range. You could simply create a preset for each export type you need, each with its own export location, custom file name format, and/or keyboard shortcut!

  • Trevor Asquerthian commented  ·   ·  Flag as inappropriate

    I would like different relative paths for different presets... eg 'Vieeing H264' goes to one folder 'video mixdown DNx HQ' to another, 'split track DNx HQ' to a third etc...

  • Pierre Louis Beranek commented  ·   ·  Flag as inappropriate

    Thanks Antoine! I do Beta testing for software and plug-ins. Are you a plug-in developer? If so, I'd be happy to help you beta test any plug-ins you develop that help Pr users.

Premiere Pro: Export

Categories

Feedback and Knowledge Base

(thinking…)