Angelos
My feedback
-
17 votesAngelos
supported this idea
·
-
99 votesAngelos
supported this idea
·
-
2 votesAngelos
shared this idea
·
-
1 vote
An error occurred while saving the comment Angelos
shared this idea
·
-
5 votesAngelos
supported this idea
·
-
12 votesAngelos
supported this idea
·
-
15 votesAngelos
supported this idea
·
-
11 votesAngelos
supported this idea
·
-
2 votesAngelos
supported this idea
·
An error occurred while saving the comment Angelos
commented
Same error here. Happens randomly. It first occured when I changed the sequence resolution. If I close the project and re-open, it goes away temporary until I change something again.
I'm also on v13.1, Win10 Version 1809.
-
1 voteAngelos
shared this idea
·
-
9 votes
An error occurred while saving the comment Angelos
commented
I've been waiting for this for years. It seems weird that it only has 5 votes.
The difference is very noticeable.
DaVinci Resolve has this by default in the paid version and it is way better than the default H.264 MainConcept encoder that Adobe is using. Everything from gradients, to dark scenes render a lot better with x264. That's why it's been used for streaming services such as netflix and youtube.
When I have some time I will post some screenshots to check for yourself.Angelos
supported this idea
·
-
621 votes
Thanks for the suggestion(s).
Angelos
supported this idea
·
-
464 votes
Currently, Premiere uses the Lanczos method for intrinsic scale and rotation. Lanczos is an exceptionally high-quality interpolation method which generally yields better results than bicubic, bilinear or nearest neighbor. From reading the forum post, it seems that up-scaling is the real issue here. I suggest looking at the Detail-Preserving Upscale effect in After Effects. It does a really good job and gives you some parameters to tweak to fit your specific content.
Angelos
supported this idea
·
-
7 votesAngelos
shared this idea
·
-
5 votes
An error occurred while saving the comment Angelos
commented
I thing I've figured it out.
It's actually a combination of 2 problems.
1. Applying a custom LUT (as in first example) requires the LUT to be also copied in AME's folder. Not only on Premiere's folder.
This is not documented by Adobe and it should be.
2. If you enable DCM on Premiere's preferences, there is a small color inconsistency on AME's preview window (as seen on second example). I did checked however that the exported video has the correct color by importing it back to Premiere.
So for me DCM should be off unless you work on a P3 monitor.
An error occurred while saving the comment Angelos
commented
After playing a little bit, trying to figure out what's happening, it seems that Media Encoder completely ignores Input LUTs.
Creative LUTs also translate wrong when using Media Encoder. No issues when exporting straight from Premiere.
I did check, if Display Color Management is the reason for that, but it is not as it also happens with DCM off.
Angelos
shared this idea
·
-
2 votesAngelos
shared this idea
·
-
3 votesAngelos
shared this idea
·
-
531 votes
As Jim Simon noted, there is already a request for this so certainly upvote that request.
This is an area we are looking into for future versions to make auto-save more reliable and out of the way.
Angelos
supported this idea
·
-
60 votesAngelos
supported this idea
·
-
122 votesAngelos
supported this idea
·
Uninstalling and Reinstalling or reseting plugin cache does not fix the problem. So waiting for another hotfix by Adobe.