In productions, we should be able to rename a clip in the timeline independently from the master clip, just like you can in a regular project. I honestly don't see why this feature didn't make it to productions.

I rename timeline items such as adjustment layers all the time, as well as black video on which I write the scene nr and version. Having migrated a project to productions, I now have to fix this workflow somehow (create a new item in the project for each instance... boooo)- or migrate back to a regular project.

I like working in Productions for its faster save and load times, but there's a few gotchas that make me consider it's not worth it for me: no search, no usage indication, and now this...

In Pr 15.0 (currently in Beta), Adobe solved a 'problem' with a solution no one's been asking for: when Pr finishes exporting, a dialog box temporarily pops up in the bottom right corner of the screen (see illustration).

In a perfect world of unlimited software development resources, there wouldn't be anything wrong with this per se. However, in the real world, this new feature is a slap in the face to User Voice contributors.

Why?

Because programming resources were spent to solve a problem that never existed (where is the User Voice thread asking for an export success confirmation box?), while ignoring dozens of very real issues that haven't been solved in years, some of which could even be solved with about the same programming effort that was used to create that pop up! Exporting itself still has a very real issue that still hasn't been solved: the fact that the export location for a project always defaults to the last used location, regardless of the project it was set by! Contrary to the new pop up box we're given in Pr 15.0, this issue has SEVERAL FR threads asking for it to be fixed:

https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/34225054-export-mp4-mov-any-format-in-same-folder-of-p

https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/35669152-add-a-set-default-export-location-option?tracking_code=dd9dc4948cc87fef70360709e31d602d

https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/40315684-export-pathway-savrd-to-the-project-file

https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/36057466-an-option-for-export-media-output-location-where

And for a concrete solution to the problem, here's a FR I just posted:
https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/42617104-relative-export-paths-please

Adobe, please show your paying customers respect by solving actual problems we're asking solutions for rather than 'fixing' non-existent 'problems' with 'solutions' no one is requesting! :( The lack of sensible prioritizing is disheartening to say the least, and to be honest, is disrespectful to your User Voice contributors.

I apologize if the tone comes across the wrong way, but please try to understand our point of view as User Voice contributors. Perhaps then, those responsible for setting priorities will appreciate just how frustrating it is for us to receive new features no one is asking for when things we repeatedly request keep getting ignored.

Thank you!

For the Lumetri Color Effect’s curves controls (Hue vs Sat, Hue vs Hue, and Hue vs Luma), cyan is in the center, while red is on the far left and right sides. This is inconvenient, because most users will probably want to adjust skin tones more than anything else, and skin tones are almost always somewhere in the reds and yellows. Therefore, I propose that red be in the center by default, while cyan is on the edges.
NOTE: Because a horizontal scroll bar is already available, it is possible for the user to essentially do this themselves... but because skin tones are the most common thing I adjust, I find that I have to manually scroll that bar all the way to the left or right, 80% of the time I use these controls. So it would definitely be less hassle (for me) if red was already in the center.
There may be a good reason to have cyan in the middle, but I can't think of it.

Having consistent problems with HEVC footage recorded with the Canon XF 705. This is not related to one individual computer and has been tested on many different systems to find the same issues consistently.

Bug description:

First of all the footage is incredibly laggy, it's impossible to edit from as it just freezes up after about 1 second of playback. We've tested this on even higher spec systems and the best we can get is some semi-smooth playback at 1/4 resolution with 1080p footage. If there is a way to improve playback of this footage that would solve the problem.

As a result, we have tried to implement a Proxy workflow. When attempting to create proxies we run into the same error every time on every machine which is as follows:

Frame substitution recursion attempt aborting after multiple attempts on file: FILENAME.MXF
Inserting black for frame number 0

This happens with ProRes, Cineform and DNxHR codecs. This causes media encoder to fail the export, on less powerful computers it actually causes media encoder to crash altogether. When trying to create proxies manually through media encoder rather than through premiere pro we run into the exact same issue.

We are able to create H.264 proxies, however, we then receive the error that the audio tracks do not match because our source footage Is often 4 track audio and we can only create 2 track H.264 files.

This makes it impossible to edit with the original footage and also impossible to create working proxies for the footage we are required to edit.

An example system that it has been tested on:

Processor: Intel(R) Core(TM) i7-7820HK CPU @ 2.90GHz (8 CPUs)
Memory: 32MB RAM
GPU: NVIDIA GeForce GTX 1080

All with the latest drivers and HEVC codecs from windows and Canon. We have been having these problems for the last few months and hoping it will be fixed with every Premiere Pro Update.

We have no issues working with HEVC/H.265 footage from other cameras but Canon says the issue lies in the NLE, not the codec. Please fix XF 705 HEVC footage in premiere pro.

Thank you.