Andy Adkins
My feedback
-
14 votes
An error occurred while saving the comment Andy Adkins
supported this idea
·
-
13 votes
An error occurred while saving the comment Andy Adkins
commented
The requests to improve thumbnail generation/loading (an absolute productivity-killer which Adobe should be embarrassed about) are scattered all over the place so let's try to clean this up a bit. The one with the most votes appears to be here, so please vote and comment if you haven't:
Maybe this will make them hears us better. Maybe. I personally don't care how they fix it - either through a cache, loading in the background or by just making them 10x faster to load. I have a fast modern machine and fasts storage and it's still awful. Pulling stuff off older/slower archive drives is just painful. Seems to be worse w/ h264 gop media and faster w/ prores. 422 10 bit long-gop footage from a GH5 has been about the slowest.
Andy Adkins
supported this idea
·
-
810 votesIn Progress ·
AdminFergus Hammond
(Product Manager, Video & Audio Cloud Workflows, Adobe DVA)
responded
Hi all,
MKV support is actively being worked on. I don't have a release date to share currently but when that changes, I will update this message.
Regards,
Fergus
Andy Adkins
supported this idea
·
-
6 votesAndy Adkins
supported this idea
·
-
9 votesAndy Adkins
supported this idea
·
-
87 votes
An error occurred while saving the comment Andy Adkins
commented
Some more flexibility here would be great. It appears that the way it works now is that audio for the *entire* nested sequence is rendered (and you have no other choice), even if it's trimmed to only use a few seconds of it. This helps you extend the clip and not have to generate new waveform/peaks (a good thing), but for a really long nested sequence (extended multiclip seq, say) you may be forced into a several-minute render to see any peaks.
-
70 votes
An error occurred while saving the comment Andy Adkins
commented
Search bin functionality still unfathomably terrible. It's something so so so basic, yet so so so bad.
I just created a search bin for Tape Name = DAY_X
Bin populates with DAY_Y
No joke. With the 2020 version.
I really can't believe it. After bing under review for 6 months and reports going back more than a year. With what, like a dozen updates in the interim? Really?
This screenshot says it all. WTF. Get your s*** together Adobe. Premiere is becoming a total joke for folks trying to do serious/large projects with it.
An error occurred while saving the comment Andy Adkins
commented
It may be fixed in 13.1. Been testing it out a bit today and so far so good. Fingers crossed.
Andy Adkins
supported this idea
·
-
37 votesAndy Adkins
supported this idea
·
-
19 votesAndy Adkins
supported this idea
·
-
14 votes
An error occurred while saving the comment Andy Adkins
commented
I've just had this come up on one particular project. It's near finished and already graded w/ Lumetri and I noticed a few clips looking off when I opened it today. The clips look under exposed and more contrasty than did previously (or compared to another clip from the same interview, say). But it also changes mid-clip sometimes, looks like an exposure change at a random point as you scrub or bounce around. I've seen happen during normal playback as well, where it looks like the exposure is flickering. And it does make it's way into the final export through AME unfortunately.
Here's what I've tried, none of which has made this problem go away:
-Reboot
-Clear prefs
-Export sequence to a new project
-Disabling the stock input lut I had applied
-Uninstall, reinstall all adobe stuff (CC, Premiere, AE, AME)
-OpenCL rendering
-Metal rendering
-Software renderingI'm on the latest & greatest version. Just re-installed today. Will try to grab screencap of this and post later.
Andy Adkins
supported this idea
·
-
541 votes
As Wes noted, we are looking at many areas for optimization and have made strides in the last few releases already.
We recognize there are still many areas to improve performance and we are investing in appropriate areas.
Threads that are catch-alls are often non-actionable. Please keep giving us specific feedback on what workflows are slow for you.
Technical solutions may not always be as obvious as some people may be suggesting as the application architecture is often very different than people’s conception.
Short answer. Yes, we want to and will make it faster.
Andy Adkins
supported this idea
·
-
674 votesIn Progress ·AdminFergus Hammond
(Product Manager, Video & Audio Cloud Workflows, Adobe DVA)
responded
We are actively working on this feature. I don't have a date to share yet but I'll update this message when I do.
Andy Adkins
supported this idea
·
-
5 votesAndy Adkins
supported this idea
·
-
51 votesAndy Adkins
supported this idea
·
-
8 votesAndy Adkins
supported this idea
·
-
1,602 votesUnder Review ·
AdminPatrick Palmer
(Director of Product Management, Pro Video and Motion Design, Adobe DVA)
responded
Thanks for all the feedback. It’s pretty clear that we’ve got to look into the workflow using this format more closely, there are enough reports about gaps at this point to reopen this item. I’ll post more info about next steps shortly. In the meantime, a couple of questions are easy to answer:
- The plugin is designed for Premiere Pro. It currently doesn’t provide support for After Effects.
- It does work with AME, so if you want to use it for batch processing, that’s very doable
- If you’ve started a project with Autokroma, there’s no easy way to transfer it to be running with the new plugin.Patrick
Andy Adkins
supported this idea
·
-
6 votes
An error occurred while saving the comment Andy Adkins
commented
Yep, this is pretty ridiculous and it's been an issue and known bug for years. Please fix this. It's a major time waster.
It has something to do with additional bin tabs that are open but I haven't been able to figure out how to predict the behavior. Even if you change nothing about what bins are open or tab you're on, one subclips goes where you want and the next doesn't. No matter what I do it always wants to dump them in my music bin on the project I'm working on right now for instance. Super frustrating.
FYI: subclips are going into random bins, not folders. Technically bin is the proper term and I'm stating this only to help people find their way here - I searched some combination of "subclip" and "bin" and this didn't come up right away.
Andy Adkins
supported this idea
·
-
7 votesAndy Adkins
shared this idea
·
-
21 votesAndy Adkins
supported this idea
·
-
6 votesAndy Adkins
shared this idea
·
This is similar to other requests to improve thumbnail generation/loading (an absolute productivity-killer which Adobe should be embarrassed about), which are scattered all over the place. The one with the most votes appears to be here, so please vote and comment if you haven't:
https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/33849352-save-thumbnails-cache-for-project-panel-thumbnail
Maybe this will make them hears us better. Maybe. I personally don't care how they fix it - either through a cache, loading in the background or by just making them 10x faster to load. I have a fast modern machine and fasts storage and it's still awful. Pulling stuff off older/slower archive drives is just painful. Seems to be worse w/ h264 gop media and faster w/ prores. 422 10 bit long-gop footage from a GH5 has been about the slowest.