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.

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...

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.

Exporting RED Epic footage from a sequence with the following settings yields a white artifact along the bottom of the frame. 23.976fps project file with frame size of 8192x3456 square pixels in Re.709 color space. This happens anytime two clips are stacked over each other in different video layers. Often, the layer on top won't be visible at all. This is occurring in Premiere Pro 22.0.0 (build 169) version on an M1 iMac with 16GB of memory. See screenshots. Project was 1hr 40 min. Export settings were 1920x1080 scaled to fit H.264 with D1 16:9 aspect ratio, software encoding VBR, 1 pass set to target bitrate of 2 Mbps and Max of 5 Mbps with a TC overlay generated. If just a small region of the timeline is exported, the same area does not export with that glitch, so it seems to be a processing issue associated with the size (length) of the export and/or the hardware and software configuration/versioning. This same export preset/setting for the same material was used in PPro version 15.4.1 without issue.

DaVinci Resolve now has the ability to set the Gamma Tag on export of a clip, and Premiere needs this ability.

By Setting the Gamma tag you can set a clip instead of 111 to 121 which will make mac quicktime show the clip correctly and will look the same on Windows. I know you don't want to do this for final export or for upload to YouTube (which forces everything to a 111 setting so will have the gamma shift) but with testing for remote viewing copies, this allows you to export a version that is much more likely to look like correct version on both Mac and Windows.

Currently to guarantee that the version looks correct I try and get people to look at versions in VLC, but most remote clients will just double click on a clip and watch it, so being able to change the gamma would mean they can see something closer to what I see on an external monitor.

I made a post on my blog about this, to show some example as shown on a Mac and a PC. https://jonahleewalker.com/2021/10/27/more-with-the-mac-gamma-shift-and-tagging-video-with-the-2-4-gamma-in-davinci-following-my-post-on-color-correction-in-premiere-pro/

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.

I recently upgraded to Mac M1 updated version of Premiere pro... works like a jiffy now.
Found out this problem recently which happens in few exports...
When I use a text animation graphic... and use ADD FRAME HOLD feature to extend the text all thru the timeline..... while working on premiere pro it doesn't show any issue... but once you export the video... there are duplicate images coming in the exported video (SCREENSHOT ENCLOSED).

The only work around I found for time being was to remove ADD FRAME HOLD portion of the Text graphic... and then COPY PASTE the graphic stacking multiple times... till end of timeline (which is tedious process)... but doing copy-paste instead of Add frame hold... worked for me... the DUPLICATE images didn't come this time while exporting.

Request Adobe team to look into this please.

In the new Export screen (22.1.1 beta), I like everything about it except where the Export/Send to Encoder buttons are. To change settings I'm working in the upper left corner of the big 4K screen. The buttons are in the lower right. It takes extra time to find those buttons after configuring settings. Call me picky, but it would be much more intuitive if those buttons were also in the upper left area of the screen where they could be more quickly accessed. This is an issue when I have hundreds of timelines to export in a day, so every second counts.