JW Schram

My feedback

  1. 98 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    I'm sorry to hear you are having trouble with the new design.  I get it, change is hard, and this is a big change.  But I want to know what settings you need to adjust every time you export rather than saving a preset. We will not be going back to the old design or giving that as an option, so lets work together to get this new design working for everyone.  

    JW Schram supported this idea  · 
  2. 32 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    JW Schram commented  · 

    I can imagine the dev team is pretty busy, but can we at least get an indication of a timeline for a fix here? I am too feeling forced to leave the CC suite because of the seeming lack of action from Adobe's side.

    An error occurred while saving the comment
    JW Schram commented  · 

    Issue still not fixed in the latest version. We've been dealing with this for six months now, customer support tells me this is a known issue, and still no solution.

    I can understand that the Mac Pro userbase is relatively small but please Adobe, fix this or I (and a lot of users with me) will have no choice but to change our workflows to a new NLE.

    An error occurred while saving the comment
    JW Schram commented  · 

    I've just been in contact with an Adobe service rep who assured me this is a known problem that should be resolved in the next update of Premiere pro. Fingers crossed...

    JW Schram supported this idea  · 
    An error occurred while saving the comment
    JW Schram commented  · 

    Exactly the same issues on my end. I cannot comprehend why this issue has not been solved yet. We are talking about pro machines with pro specs, same issues on the recent 2022 update.

    Issues mostly start after a couple of minutes, and are most prevalent in projects with mixed media. .MXF, .RED, prores, etc.

    Please, please fix this as soon as possible.

  3. 27 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    22 comments  ·  Premiere Pro » Editing  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    JW Schram supported this idea  · 
  4. 532 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Under Review  ·  Reg Santo Tomas responded

    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.

    An error occurred while saving the comment
    JW Schram commented  · 

    Yes, better optimization for Pro Macs in general (Mac Pro 2019 w Vega II 32 in my case) would be highly appreciated. I understand the team has to try and find the best solution for many different use cases and setups. But the difference in general performance between Premiere and Resolve / Fcpx is too big.

    JW Schram supported this idea  · 
  5. 793 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    JW Schram supported this idea  · 
  6. 1,598 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    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

    JW Schram supported this idea  · 

Feedback and Knowledge Base