Skip to main content
Known Participant
January 24, 2023
Open for Voting

Relative Export Paths PLEASE!

  • January 24, 2023
  • 28 replies
  • 2462 views
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!

28 replies

Participant
January 24, 2023
i need this its such a pain!! just export to current project location in a subfolder or whatever. this needs to be a thing/
Participant
January 24, 2023
I can't begin to estimate how many work hours per year I waste tracking down files I accidentally exported to the wrong folder. I don't understand how After Effects can have this feature (at least when exporting using Media Encoder) but Premiere does not. I work on hundreds of projects per year, and at least having the OPTION of saving exports adjacent to your project folder would be a drastic QOL improvement.
Participant
January 24, 2023
I can't tell you how many times I've exported to the wrong folder, then had to go hunting through my projects folders to find the right one. It's incredibly frustrating.
Participant
January 24, 2023
Lmao I just love that they totally rebuilt the export module in whatever recent release that was and did not address this at all. What a mess.
Participant
January 24, 2023
Great presentation of the problem, like the solution. We often think about grand improvements, but I'd like a version to come out whose only feature is "It has 378 less clicks than before". This feature suggestion is exactly this. And I love it.

Right now, there's a plug in call Compass that does this, kinda. It's better than what this is right now. https://knightsoftheeditingtable.com/compass

Thanks to this person to set this up so nice for Premiere. Great stuff.
Legend
January 24, 2023
Agreed, there should be a pref to use the location of the project file as the relative starting point for all import/export.
Inspiring
January 24, 2023
There is no need to have a "relative path" checkbox because, at least in windows, the user can specify either absolution path (e.g. E:\video\projectA) or specify a relative path (e.g. .\export)
Participant
January 24, 2023
PLEASE! I keep finding exports in a folder under other (past) projects, which is highly annoying!
Justin Taylor-Hyper Brew
Community Expert
Community Expert
January 24, 2023
Pro IO has been doing this for years FYI: https://aescripts.com/pro-io/

(shameless plug)

Community Expert
January 24, 2023
I second the COMPASS extension. Simple and free.
-------------------------------------------------------------------------JVK | Editor/Designer/Software Instructor. Pr, Ae, Ch, Ps, Ai, Id