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.

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.

Not sure what the new export page is trying to achieve (we don't use Resolve because of its tabbed interface) but please fix the following...

1.
Allow keyboard entry in all drop-downs so we can hit 'q' for quicktime or the first letter of a custom preset for example.

2.
Remember previous settings per timeline as per the previous export window. Again, why create extra work? UPDATE: I have one project which never remembers the last export setting but another which does. Maybe the one that doesn't was created in an older version but I'm not 100% if this is why.

3.
The roll-ups/accordions are painful because you can't see both video and audio settings simultaneously - yet more pointing and clicking. Also, the vertical spacing on everything is too big, especially for laptops - which is why you've probably implemented accordions? We don't use Resolve because of it's large vertical spacing, it's a pain-point for many of us, especially when on the road.

4.
It's great that 'Export' is now the primary button and not 'Send to Media Encoder'. However, hitting enter to export opens one of the settings dropdowns and doesn't export anything? If we see a big blue button, we expect enter to trigger it - right?

5.
Several times now, the Range dropdown has set itself to 'Custom'. Not sure why, however I did notice that it had set itself to the previous video exported (20sec) when the new video was 15sec, thus rendering 5sec of black at the end. Not sure if this is a bug but I can't reliably replicate this.

6.
If you're going to reset workflows (agile development?) please keep a running list of UI/UX standards so you implement new features in a quality way from the start. Otherwise, it just wastes so much of our time.

Also, don't wait for up-votes, this stuff is so basic that it should be included from the beginning as a point of pride. You're Adobe - right? Not a start-up.

We need less pointing and clicking in general, not more!

Cheers, Ben.

We need the export browsing window to be file brose, not folder browse. You never export a file with the sequence name. You click the previous already rendered version, increase the version number and press Enter. Now I have to open a Widnows Explorer window, copy the file name, go back to premiere, paste it, change it, EVERY. ****. FIVE. MINUTES!!!!!! This the absolute worst 'innovation' i have seen in a while and believe me I've seen what Autodesk has been doing in that regard. You just put everything out of reach instead of making it streamlined. Why do I have to dig deep for the "Youtube 1080p" preset when it's the gold standard for almost all platforms these days? Why do I have to see other presets in the "more presets" when I search specifically for the format I already set? Why does the view not update accordingly? And mainly, why wasn't the old one good? It's not like you put anything new, you just ****** the layout. Productivity in my division practically halved, we had to revert to a previous version because this is just not a professional software any more.

If you're not willing to go back to the old export window which worked great (don't know why you try to fix something that isn't broken), bring back tabs to click between, this scrolling and clicking "more" to get to the settings you need is ridiculous, and especially when it reverts your set and saved preset back to "Match Source" randomly and each time you start a new project.

On top of that, you can't see previously exported files (or any files) when you're finding the location to save your file in? Now I can't see what files are in a folder when I'm trying to export without opening up that folder in explorer, and thus can't replace that file without looking up and copying the exact same filename, and also can't create a proper iteration of a file if I want a "v2" or "v3" without first having to check in a separate program which versions there are. That was a huge oversight, and this feels less like a "feature request" and moreso just a bug report.

Windows 10
Premiere Pro 22.3.1 (Build 2)

Premiere Pro randomly crashes when a project containing one (or more) VST3 plug-ins is exported to Final Cut Pro XML.

How to reproduce it:

• Add a VST3 plug-in to an audio clip;
• Select file -> export -> Final Cut Pro XML;
• (get a Translation Report warning about the effect not being translated, should be harmless);
• get a random crash after a while.

The crash is non-deterministic: sometimes it happens right away, sometimes after Premiere is sent to background below another app, sometimes after I delete the XML file manually.

The crash occurs also if the XML export is triggered via ExtendScript and the exportAsFinalCutProXML(path) function.

I was able to get the backtrace for a specific crash (see attachment).

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!

My job is to slow down .wav files 4.27% to sync with video clips for International Distribution. I have been using the Time Tuner tab in the Export Tool to accomplish this perfectly. Pitch is maintained, Length is as close to exact as I need down to the Sample and Millisecond.

In version 2022.3, I load my previous preset which displays 4.269999999999996. I select the box and want to change it to 4.27 and all I get is the 4 making my audio 5 seconds short and obviously not in sync.

Until this is fixed, I cannot use 2022.3 as it will literally make me useless to my employer. I haven't checked the Rate Stretch Tool or Audition yet. But I've never had the same confidence with them.

I'll check, but I'm not sure they will suit my needs. PLEASE MAKE IT THE WAY IT WAS!? I'm dead in the water without this functionality.

Bob K.

Hello Everyone,

I am editing videos for stock footages. I collect the shots I took and then put them on the timeline, I export them after editing, but I have to export them one by one, it's a waste of time. If the videos in the entire timeline were automatically named and exported with one click, as in the Davinci program (individual clips), it will be easier for me and those who do stock video work, and they will not think about switching to Davinci. I want a one-click solution, please don't be tired to say other long-distance solutions.

Thank you