Andy

My feedback

  1. 20 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Premiere Pro » GPUs  ·  Flag idea as inappropriate…  ·  Admin →
    Andy supported this idea  · 
  2. 13 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Premiere Pro » GPUs  ·  Flag idea as inappropriate…  ·  Admin →
    Andy supported this idea  · 
  3. 10 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Premiere Pro » Color/Lumetri  ·  Flag idea as inappropriate…  ·  Admin →
    Andy 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 rendering

    I'm on the latest & greatest version. Just re-installed today. Will try to grab screencap of this and post later.

    Andy supported this idea  · 
  4. 368 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    18 comments  ·  Premiere Pro » Performance  ·  Flag idea as inappropriate…  ·  Admin →

    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 supported this idea  · 
  5. 363 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    23 comments  ·  Premiere Pro » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    Andy supported this idea  · 
  6. 5 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  After Effects » General  ·  Flag idea as inappropriate…  ·  Admin →
    Andy supported this idea  · 
  7. 57 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Under Review  ·  23 comments  ·  Premiere Pro » Performance  ·  Flag idea as inappropriate…  ·  Admin →
    Andy commented  · 

    It may be fixed in 13.1. Been testing it out a bit today and so far so good. Fingers crossed.

    Andy supported this idea  · 
  8. 43 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Premiere Pro » Color/Lumetri  ·  Flag idea as inappropriate…  ·  Admin →
    Andy supported this idea  · 
  9. 6 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Premiere Pro » General  ·  Flag idea as inappropriate…  ·  Admin →
    Andy supported this idea  · 
  10. 1 vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Media Encoder  ·  Flag idea as inappropriate…  ·  Admin →
    Andy shared this idea  · 
  11. 6 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Media Encoder » Batch Processing  ·  Flag idea as inappropriate…  ·  Admin →
    Andy supported this idea  · 
  12. 1,410 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    532 comments  ·  Premiere Pro » Formats  ·  Flag idea as inappropriate…  ·  Admin →

    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 supported this idea  · 
  13. 4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Premiere Pro » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    Andy 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 supported this idea  · 
  14. 29 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Premiere Pro » General  ·  Flag idea as inappropriate…  ·  Admin →
    Andy supported this idea  · 
  15. 3 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Premiere Pro » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    Andy shared this idea  · 
  16. 13 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Premiere Pro » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    Andy supported this idea  · 
  17. 5 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Premiere Pro » Projects  ·  Flag idea as inappropriate…  ·  Admin →
    Andy shared this idea  · 
  18. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Premiere Pro » Projects  ·  Flag idea as inappropriate…  ·  Admin →
    Andy shared this idea  · 
  19. 16 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Premiere Pro » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    Andy commented  · 

    Also... search bin issue still problem in 12.1.1. Search bar may have been improved but not sure

    Andy commented  · 

    Regarding the Search Bin bug... One painful result of this issue is that you cannot assign labels to clips in a search bin in icon view. You have to be in list view and can't take advantage of those nice big icons! And you can't be all the way "in" that bin so you have to back out a level.

    To reiterate: the workaround is to use list view and go up one bin level while leaving the search bin expanded. Then you can do stuff to clips like normal.

    Andy supported this idea  · 
  20. 111 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    25 comments  ·  Premiere Pro » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    Andy commented  · 

    For projects with a lot of overcranked footage (not at all uncommon) this makes proxies functionally useless.

    Looks like folks noticed this over two years ago. Pretty please? Sure seems like it would be trivial to just apply the same "interpretation" to the proxy that is applied to the original. This logic works for other things - like FX, which work whether applied to original or proxy (although I can appreciate that the interpretation probably happens deeper down).

    Andy supported this idea  · 
← Previous 1

Please do not use your Adobe ID and password.

Feedback and Knowledge Base