Austin Hines

My feedback

  1. 39 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

    13 comments  ·  Premiere Pro » Stability  ·  Flag idea as inappropriate…  ·  Admin →
    Austin Hines supported this idea  · 
  2. 113 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

    17 comments  ·  Premiere Pro » Stability  ·  Flag idea as inappropriate…  ·  Admin →
    Austin Hines supported this idea  · 
  3. 2 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

    1 comment  ·  Premiere Pro » Playback  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Austin Hines commented  · 

    I started noticing this as well when using fullscreen playback on a second monitor, even with a timeline that has previews fully rendered.

    I'm on Windows 10 21H1, NVIDIA RTX 2080, Studio Driver Version 471.41.
    Also tested with a Quadro 4000 with same results.

    Playback gets progressively corrupted until program crashes. Restarting the program fixes the problem temporarily, but it comes back again.

    Screenshots of the errors are attached. The fact that I can take screen shots of this seem to indicate that it's a problem with what is being sent from premiere to the GPU, not with how the GPU is rendering it on the monitor.

    Austin Hines supported this idea  · 
  4. 3 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

    1 comment  ·  Premiere Pro » Playback  ·  Flag idea as inappropriate…  ·  Admin →
    Austin Hines supported this idea  · 
  5. 3 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

    1 comment  ·  Premiere Pro » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Austin Hines commented  · 

    This is still an issue two years later.

    Austin Hines supported this idea  · 
  6. 13 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

    1 comment  ·  Premiere Pro » Stability  ·  Flag idea as inappropriate…  ·  Admin →
    Austin Hines supported this idea  · 
  7. 35 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

    11 comments  ·  Premiere Pro » Performance  ·  Flag idea as inappropriate…  ·  Admin →
    Austin Hines supported this idea  · 
    An error occurred while saving the comment
    Austin Hines commented  · 

    I'm so glad it's not just me. I just got a nice new Razer Blade Studio with Quadro 5000 max q, thinking that the quadro would be more stable than the geforce cards on my desktop, but no - still getting this flickering timeline issue.

    For me, I can get it to reliably occur when I try to edit Lumetri on an adjustment layer. Lumetri panel stops responding, and effects control panel stops responding. Sometimes it eventually recovers, but it seems the problem gets worse and I eventually have to quit and relaunch.

    Razer Blade 15 Studio
    Windows 10 Pro, version 1903, build 18362.449
    Intel i7-9750H Hexa core
    Quadro 5000 Max-Q
    32GB RAM

  8. 175 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

    26 comments  ·  Premiere Pro » Stability  ·  Flag idea as inappropriate…  ·  Admin →
    Austin Hines supported this idea  · 
  9. 652 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

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

    This is a great request that is certainly something we want to implement. Rest assured our engineers DO understand the importance of this feature and how to get the job done. We also know that the performance and stability of the app should be our #1 priority and that is where our focus is right now.

    Austin Hines supported this idea  · 
  10. 571 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

    69 comments  ·  Premiere Pro » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    Austin Hines supported this idea  · 
  11. 1,582 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

    569 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

    Austin Hines supported this idea  · 

Feedback and Knowledge Base