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!

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.

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

I've been editing a TV Series, and previously I've been able to Mark "In" and "Out" in a sequence and it automatically rendered where I marked it. Now I have to remember every single time to click the drop down menu to only render where I marked In and Out, or it will render the entire Work Area. What is the purpose of marking In and Out points if it's not a quick way to export video within those points? We have to render out 4 parts per half-hour show individually, and I've already had several clips kicked back because I forgot to click on the drop down menu for just one out of the batch. PLEASE PLEASE set it back or allow us to set defaults for rendering video so that we can quickly export our work without it completely ignoring the markers that we put there for a reason.

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

I have a timeline with several AE comps that I have rendered to the green status in GoPro 10bit

When I try to export an h.264 with the 'Use Previews' option the previews are ignored and AE is run in the background slowing down the export to a crawl, even thought I spent a lot of time rendering previews already. This is a straight export out of Premiere, not an AME export. This is a very typical workflow for a lot of projects and it's very frustrating that it's broken again.

Steps:

1. Create project with several Dynamic links in a timeline
2. Render Previews for entire timeline in GoPro 10 bit(entire timeline is now green)
3. Export->Media
4. h.264 Render
5. Check use previews
6. Export using Premiere....its going way going slower than it should
7. Confirm in Task Manager that After Effects is using a significant %of CPU to render frames again instead of using the preview files.

System:

Windows 10
Premiere Pro 2020
Intel i7 4770k (yeah I know I'm due for an upgrade)
RAM 32GB Ram
EVGA Nvidia GeForce GTX 1080 8GB
Preview files kept on scratch SSD
Project files on C:

Hopefully this can be addressed quickly its a real bummer.