Skip to content

Zack Bender

My feedback

13 results found

  1. 34 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
    Zack Bender commented  · 

    I've stress-tested the same production across multiple systems and confirmed that this is purely an Intel-Apple Silicone issue. My power-house Mac Pro (2019), as well as my iMac Pro (2017), cannot work in ANY version of PrPro 15.2 or later. They'll be fine for a few minutes, then start pumping out access errors. The production works beautifully on both of these intel systems in PrPro 15.1. I tested the same production on my MacBook Pro (2021) in PrPro 22.3.1 for 1 hr and didn't have a single issue. It's great that the latest system works so well, but it would be great if Adobe would support my $16k MacPro that isn't even 2 years old.

    An error occurred while saving the comment
    Zack Bender commented  · 

    The issue persists with 22.3.1.

    An error occurred while saving the comment
    Zack Bender commented  · 

    This issue persists in Premiere 22.2, forcing me to stay on Premiere 15.1. I've begun training my entire post team in DaVinci Resolve so we can begin the migration away from Adobe.

    An error occurred while saving the comment
    Zack Bender commented  · 

    UPDATE: This issue is still present with Premiere 22.0.0. I will be forced to switch my entire team to Avid or Resolve if this is not addressed. It has become completely unusable for professionals.

    Zack Bender shared this idea  · 
  2. 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

    3 comments  ·  Premiere Pro » Playback  ·  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)
    Zack Bender shared this idea  · 
  3. 16 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

    3 comments  ·  Premiere Pro » Transmit  ·  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)
    Zack Bender supported this idea  · 
  4. 20 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

    10 comments  ·  Premiere Pro » Transmit  ·  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)
    Zack Bender supported this idea  · 
  5. 177 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

    42 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)
    Zack Bender supported this idea  · 
  6. 10 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

    3 comments  ·  Premiere Pro » Export  ·  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
    Zack Bender commented  · 

    Adding a default Gamma Tag to all Premiere exports would be so helpful! It's very frustrating to only watch renders in VLC, never in QuickTime/Finder.
    DaVinci Resolve got this right. When exporting from Resolve, they add the tags defined by the working color space (by default). Since Premiere is primarily Rec.709 Gamma 2.4, exports should be tagged as 1-2-1. See attachment for the metadata on a DaVinci Resolve.

    Zack Bender supported this idea  · 
  7. 50 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

    23 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)
    Zack Bender supported this idea  · 
  8. 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

    2 comments  ·  Premiere Pro » Stability  ·  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)
    Zack Bender supported this idea  · 
  9. 16 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

    2 comments  ·  Premiere Pro » Stability  ·  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)
    Zack Bender supported this idea  · 
  10. 4 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 →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Zack Bender supported this idea  · 
  11. 100 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

    32 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)
    An error occurred while saving the comment
    Zack Bender commented  · 

    I have my "Editing" workspace customized to 2 displays. The two issues I run into constantly have to do with the Project panel. When I switch between projects, it often moves "Project" to a different panel, or to a brand new window. This throws off the entire workspace, shifting other panels (Effects, Source Monitor, Effect Controls) to where the "Project" is supposed to be. Hitting "Reset to Saved Layout" sometimes does nothing, or it just puts the Project panel in a different location, typically a new tab on my Source Monitor. This issue also messes with the layout of the metadata in the Project panel. I have a very specific list of metadata that's important to my day-to-day work, and the only way to get that back is to right-click into the Metadata Display, select my saved preset, then go into the Project window and reorganize and change the spacing for every single tab. This is a very time-consuming process that I do almost every day.
    I am very careful about only ever having one project window up, because I've run into many issues in the past with multiple bins open in different panels.
    These issues happen most frequently when opening projects created before 13.0.2, or opening projects from other editors. Projects that I've started recently on my personal workstation are capable of maintaining my latest workspace, but I am constantly referencing other editors' projects and revisiting old projects.
    Everyone in the office is on a Mac, running the same versions of Premiere Pro and Mac OS X (currently on Mojave 10.14.3).

    Zack Bender supported this idea  · 
    An error occurred while saving the comment
    Zack Bender commented  · 

    I notice this issue all the time when switching projects. I save my dual monitor workspace exactly how I want in a blank project and it'll work fine for a bit, especially if I create a project template for new edits. However, when I switch to a different project some of the panels rearrange themselves and "Reset Changes to Saved Workspace" doesn't put things back correctly. I notice this especially on my Project window and the Effects window.

  12. 402 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

    Under Review  ·  77 comments  ·  Premiere Pro » Color/Lumetri  ·  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)
    Zack Bender supported this idea  · 
  13. 52 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

    6 comments  ·  Premiere Pro » Color/Lumetri  ·  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
    Zack Bender commented  · 

    I work with a team of 5 other editors and we're constantly sharing projects across systems. I've created and purchased several custom LUTs and installed them correctly/consistently on all of our edit systems. Anytime we open a project on a different system, the LUT is disabled. This is very annoying and time-consuming to go through the individual clips and re-apply all LUTs.

    Zack Bender supported this idea  · 

Feedback and Knowledge Base