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!

When exporting a video sequence premiere randomly leaves out part of the audio. Those part were not muted, but in the same channel and of the same kind of other parts exported fine, not even cut: so for instance you have a talker that randomly get the voice silent.
This is a big reliability issue, because there is no correspondence of what you have on timeline and what you are going to have on final export. This happens on different machines and happened also with previous versions of Premiere different from this one at moment of writing 15.4.1 (build 4).
The only reliably working workaround has been export only the single audio channels in wave files and then import it back into the timeline, that is time consuming and unacceptable for a professional software.

h264 exports done on an M1 MacMini show significantly more compression artefacts than those done on non-M1 hardware. In investigating the problem I noticed that the file sizes are significantly smaller than expected and digging into the export shows that the resultant bitrate is only around 60% of what it should be. This is across all the built-in presets that use single-pass h264 hardware encoding as well as any custom ones. To prove the point I encoded the same file on several platforms, (both Mac and PC), with several export presets. See the attached file that shows the results.

h264 exports on M1 hardware only achieve 60-65% of the target bitrate, where-as other hardware is in the 80-90% range.

Bitrate isn't the whole story as increasing it such that the resultant file has the intended bitrate still produces files with more noticeable macro-blocking, (although the differences are now more subtle).

I have also tried using v22.1 BETA of both Premiere and Media Encoder, which give the same low bitrate exports on M1 hardware.

Please allow the user to be able to select “same as source” audio channels in the export settings of both Premiere Pro and Adobe Media Encoder. This is to allow fixing the audio channel mismatch error you might get when working with proxy workflows. The reason I am requesting this and hoping to get it upvoted is when we receive footage shot across a wide variety of cameras, i.e. Canon C300 / GoPro / Drone / Canon 5D / Other various cameras that may be using different channels other than “Stereo” or even switching the channels halfway through a shoot card, then creating proxies is extremely difficult as you have to then manage the export settings across all files versus just batch encoding all the files based on source. This is a very large problem for me when I receive 1-2+ TB of media shot across various media and therefore my workaround is to use Davinci Resolve to export. Would love to start keeping this all in Adobe at some point. Thank you for your support.

The quality of exporting from Premiere Pro using hardware encoding on the new MacBook Pro with M1 PRO chip is extremely poor. I've tried exporting with multiple different projects and footage but the quality when exporting with hardware encoding is pixelated and blurred - the file size is also significantly smaller than the estimated file size.

There is no issue with software encoding and footage is as expected.

I've tried Premiere Pro 2022 and also gone back to 2021 and tried opening with Rosetta instead, still hardware encoding into H264 is extremely poor quality with file sizes less than half the expected file size. This only happens with hardware encoding.

Bug report: After upgrading to Premiere v15, exporting an H264 file from either Premiere or Media Encoder to my NAS creates a file which the program claims exported successfully, but actually creates a glitched file. At some point in the file, the audio will drop out, and the video will freeze on a single frame, which will remain on screen for the rest of the duration.

Exporting a quicktime file to my NAS doesn't cause this problem, and exporting an H264 file to my internal harddrive doesn't cause this problem, so there's only an issue with the combination of encoding to the H264 export setting to a NAS location that is causing a problem.

This is hugely disruptive to my workflow, and I really need it fixed...

Summary:
Premiere Pro CC will not upload/publish the video to YouTube after encoding has completed, but instead throws an error about "invalid credentials".

Steps to Reproduce:
Open the Export Settings window and click the "Publish" tab. Check the box next to "YouTube" and login using your credentials. Click "Export" and wait for the video to finish encoding. After encoding has completed, Premiere Pro will attempt to upload/publish the video to YouTube and encounter a fatal error.

Expected Results:
The video is uploaded/published to YouTube after encoding has finished

Actual Results:
Premiere Pro finishes encoding and upon moving on to upload/publish to YouTube, encounters an error citing:

YouTube - {

"error": {

"errors": [

{

"domain": "global",

"reason": "authError",

"message": "Invalid Credentials",

"locationType": "header",

"location": "Authorization"

}

],

"code": 401,

"message": "Invalid Credentials"

}

}

Attempted Troubleshooting:
After exhausting my own efforts, I have contacted Adobe Support only to be met with the suggestion to export with Premiere Pro and then upload/publish to YouTube using YouTube's web interface.

I have tried several clean installs of Adobe Premiere Pro CC, but have so far only been able to resolve this issue on one of my computers after the third clean install. The success rate seems to increase proportional to the shortness of the video in question. Longer videos tend to produce this issue most frequently; sometimes shorter videos (<5-10m) upload just fine.

Further Information:
https://forums.adobe.com/thread/2437224
https://forums.adobe.com/thread/2419351