Simply add an option to the proxy dialogue box where the user is able to type in a scale percentage instead of pixel dimensions for proxy generation. This will save the time of the user to generate aspect ratio locked proxies for media without having to consult look up tables for the values, or do the math. Maybe even adding in a "*****" window beside it to see the actual dimensions of the proxies you're generating. Being able to set scale percentage as in ingest, or proxy preset would also be extremely helpful.

for example:

create proxies for 3840x2160 media, you can either have an option to make 1280x720 proxies, or the option to make proxies at 25% scale of original, which is also 1280x720.

I have created a style look in AE that uses blending modes on solid layers with generators. They look great in there when I add a clip under the design and use pass through in the layer settings. However when I export them as a MOGRT they break when trying to use them inside of Premiere because Premiere does not support using the blending modes set inside of the AE project. This is a big snag because now the only solution I can find is to recreate the look in Premiere and save it as a project so that our other editors on the team can open that project as a start point.

MOGRTs are great and have come a long way, but making it so they hold the blending modes and pass them through to the layers under would save a lot of edit time and really speed up creativity with trying different custom MOGRT styles.

On my previous iMac and my current MacBook Pro the audio in Premiere and After Effects would switch to headphones when headphones were plugged in and switch back to the speakers when I unplugged, all without having to go up to Audio Hardware in preferences and switching.

Now, on the iMac Pro that is not the case. Each time I plug in headphones, the timeline stops playing and i have to go up to preferences and audio hardware and select external headphones or iMac Pro speakers if I'm unplugging them.

I was on the phone with Apple about this as well as Adobe, and what the Apple rep and I found out is that the iMac handles audio a little differently. When you plug in headphones it sees it as a new audio source while the previous iMac and the current MacBook Pro switches it.

On the older iMac and the current MacBook Pro in Preferences/Audio Hardware/Default Output you see Built-in Output (this will be whatever the output is for the computer it self)

On the iMac Pro in Preferences/Audio Hardware/Default Output you see iMac Pro Speakers and if headphones are plugged in External Headphones. It's reading it as two different sources.

Also, which I think is a complete bug is if you are on External Headphones and you unplug them, it won't play the video any more even if you switch the audio hardware to iMac Speakers, you have to quit (sometimes force quit) and reopen the application.

https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/38080990-everything-wrong-with-captions-in-premiere-pro-13

The above link is a post detailing issues with captioning. Here are some more that I would like to add to the list:

1.
----
The most egregious failing of the system is the text-editing inabilities of the Captions panel. The text box does not respect standard system keyboard shortcuts for caret navigation. All of the following standard text-editing shortcuts, that see heavy usage with document editing, do not work as expected:

- Home/End: Instead of moving the caret to the start/end of the line, it selects the first/last caption in the list.

- Up/Down: Instead of moving up/down a line, it selects the previous/next caption in the list.

- Ctrl+Home/End: Instead of moving to the beginning/end of the text, it selects all the captions before/after.

Shift+Home/End: Instead of selecting text to the start/end of the line, it selects all the captions before/after.

Ctrl+Backspace/Delete: Instead of deleting the previous/next word, it deletes the current caption.

There are probably more. Please use a standard text box implementation for the captions so all standard shortcuts work within them.

2.
----
You cannot use standard editing shortcuts to retime the captions (ripple edits, extending in/out points, adding/subtracting time, etc.) Since all the captions live within a single container clip, you are required to click and drag on the small handles on either end to adjust timing.

3.
----
The timing of the captions on export is determined by the in point of the container clip, and not by the in point of the first caption. This is an obtuse and un-intuitive mechanic and it required me to Google how to globally fix the timing, after I realised everything was out of sync (which only shows up on export, mind you, and not in the timeline itself while you're captioning).

4.
----
The captions do not wrap automatically. For long captions, you are required to manually create line breaks, or else they go off the screen.

5.
----
You cannot directly select any caption in the Timeline. Even with the mouse cursor placed directly over a caption, it will first only select the container clip. You need a second click to select the actual caption.

6.
----
There is no way to define a global style. Any global change requires you to select all the captions. If you want any captions to not be affected by that global change, you have to manually de-select those.

7.
----
In the Captions panel, clicking a caption will not actually navigate to that caption in the timeline, so you cannot immediately see a preview of your edit. You have to take the extra step of navigating the playhead to that clip manually.

8.
----
For whatever reason, you cannot select more than 2 captions in the timeline simultaneously. Even then, you cannot move them both at the same time.

9.
----
You cannot undo any value change in the Captions panel (e.g. font size, colour, etc.) unless you first deselect the caption. If you don't deselect the caption, hitting Undo will unexpectedly undo the last text change you made.

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.

I think that the full upgrades are released to often. One .0-verison each year is too often and has proved to be a very problematic procedure each year. Pr CC 2018 was problematic when it was released fall 2017 but today it has received several patches and works fine today.

Approx three months after the last update to Pr CC 2018 it is time for the brand new full release of Pr CC 2019 and we are back to square one once again with crashes, sometimes it won´t even launch, new bugs, etc.

We don´t need a full version each year, it would be enough to have a full version alive for two to three years and during that time release patches to fix bugs and stability issues and maybe new featrures along that path. The applications are so mature today so there is no need for "exciting versions with revolutionary features" releases of not-ready-for-prime-time-software.

During the Creative Suite years each full version had to be really good, otherwise it wouldn´t sell as good and it got consequences if it did not sell as expected. This was good since the goal to release a good version was high. Today the money flows in to Adobe no matter what, so the goal to release a good stable version is not as important anymore and that certainly reflects what we see today, new versions that are not near ready for prime time. It dosen´t simply matter anymore since Adobe could always recommend user to downgrade.

I think all software companies do the same thing, release new versions too often and everytime there are issues in the new version that should have been sorted out in the beta stage. But it seems more important to release "something" than to wait until the software is ready and really release something good and usable out of the box.

No one demands brand new versions every year. No one demands new and exiting features that don´t work as expected at launch.

What people demand is stable software that has been thoroughly beta tested for a long time before release.

Bottom line:
Just don´t release new buggy versions each year since there are no need to do it. A new verison every two years is enough, if it has been thoroughly beta tested that is.

<end>

You guys need to work on the system interface... Even in a workstation which has 32gb ram, xeon processor, nvidia quadro p2000 gfx card and ssd memory, premiere pro crashes.

It is because it doesn't utilize the graphic card and is heavily relied on cpu, whereas da vinci resolve and fcp x uses graphics performance so it crashes less and rendering speed is lightning fast.

Its been a decade since i'm using this software and only thing that is the best feature in this software is auto save other wise millions of users would have left using adobe premier pro including me.

Its a shame that after such a long time and with so many experts in adobe, customers still can't rely on adobe premiere pro since it crashes a lot.

In certain circumstances projects require massive amounts of dynamically linked compositions. For example I am currently working on a serious of talking heads in front of a green screen for a social media campaign with 100+ short clips.

When sending the clips over for keying and animation I have to manually rename all of them to identify which of the named sequences they are from and manually sort them into bins inside of After Effects. This workflow could be much improved:

1) Add a comp naming dialog when selecting "Replace with After Effects Composition." At the very least options for renaming after the source sequence + an incremental number instead of an incrementing number for the whole poject would be needed. More options, especially for embedding other metadata, custom naming schemes and naming presets would be great.

2) Provide an option to create a new bin inside the target AE project for the new composition and all its assets. Optionally, automatically creating a folder structure named after the PP source sequence with subfolders for all dynamic link comps within would be great.

3) Alternatively it would at least be nice to be able to choose the AE project bin from within Premiere without having to switch apps as we currently have to do.

Hello. I'd like to see a master key to assign effects OR a way to map effects and presets to the keyboard using the Keyboard Shortcut tool.

I've submitted this request before having come from Final Cut Pro and it was a huuuuuge time saver for me in the editing process as I used this feature on FCP multiple multiple times on every single edit I did, every day, and I can't imagine others would not have the same reason for using it as me and I likely very frustrated at how long it takes to apply the Warp Stabiliser effect, for example, to a clip or a series of clips. This is a very consistent task that I do in every edit and many many times in each edit usually. I'm sure I'm not the only person who is constantly adding warp stabiliser to shots by dragging the thing onto every clip and then setting the smoothness percentage. I can't even manage to just select every clip I want to throw the stabiliser on to and then copy paste a version of the effect that I've set the smoothness percentage for. This can't be unusual. Any clip shot handheld with a dslr will need this, just about, if you want to get rid of that minor jitter. Many dslr users out there you reckon..?

I would love to see this, it is a massive massive time saver and I'm confident many many editors would need this feature for the same reason.

I also would love to see functionality so that when you stop your playhead over a clip during playback or by moving the playhead that it automatically selects that clip so that it's settings are ready to play with in the effect controls window. This seems so basic common sense to me to me and I'm trying not to get angry because I know you are good people in there, but it seems some mind numbingly obvious to me as an editor that you would want the clip that you are now looking at to be the one that is selected and presenting it parameters in the effect controls window. FCP did this automatically. PP will do this when the Lumetri Colour window is open...why not for Effect Controls??

Thank you, I appreciate you listening to my rant. I would be over the moon with these changes!!