Zack Bender

My feedback

  1. 4 votes
    Sign in Sign in with: Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Premiere Pro » Export  ·  Flag idea as inappropriate…  ·  Admin →
    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  · 
  2. 48 votes
    Sign in Sign in with: Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    23 comments  ·  Premiere Pro » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    Zack Bender supported this idea  · 
  3. 1 vote
    Sign in Sign in with: Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    9 comments  ·  Premiere Pro » General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Zack Bender commented  · 

    Here's some more data from new projects today.

    Project created on iMac in one of the last versions of CC 2018 (not sure the exact patch number). Tried opening on my iMacPro which I left on Pr 13.0.1 yesterday, thinking that was the safest. Quit Pr without saving, downloaded 13.0.3, then re-opened the project. Everything worked and was lined up properly.

    I tested this on two other computers and they didn't have issues updating the 2018 project to 13.0.1 or 13.0.3. This inconsistency is really confusing. And I know it's not just my main iMac Pro, because all the systems I tested, plus at least one of our MacBook Pros had previously experienced these issues with projects created elsewhere.

    The only files that are affected in the timeline are avci .mxf files from the C300 MKII. 1DX MKII .movs, renders from After Effects (animation .movs), and other assets are unaffected by the timecode issue. And there doesn't seem to be much rhyme or reason to how they're shifted—not all of them have these zebra stripes. If a clip is long enough, it will just reference the wrong point in the clip. I had a long interview that I discovered was shifted to 46;14 before the point it was supposed to be, but then this interval was inconsistent throughout the project (other clips were shifted by several minutes, though I didn't search long enough to figure out the exact time difference).

    My brain is starting to melt from all these tests. I'd love if someone smarter than me could weigh in.

    An error occurred while saving the comment
    Zack Bender commented  · 

    Okay, I came across another project with the misaligned clips. One of my editors made this project on 10/30/2018 on an iMac Pro, so I assume this was created in 13.0, since he has auto-update on. This project was modified multiple times between the end of October and early December (so it probably went through at least one version update).

    I tried to open this project on my iMac Pro with Premiere 13.0.3 and the footage was super wack, as if the timeline is referencing timecode that doesn't exist, creating the zebra-stripe issue. I switched computers and it opened just fine in the same version of Premiere on the computer it was originally created on, and it worked flawlessly. I switched back to my system and re-installed version 13.0 of Premiere, opened the project and it was great. I updated to 13.0.1 and it worked fine. Then I updated to 13.0.2 and that's when the issue showed up again—all the C300 shots were way off in the timeline. Just to confirm, I re-downloaded 13.0.3 on my system and the project was still messed up. Out of curiosity, I ran this over to a 2015 iMac and tested it in 13.0.2, which produced the same zebra-stripe issue.

    In conclusion these projects seem to work when updated on the same system, but in versions 13.0.2 and 13.0.3, timelines can be majorly screwed up by upgrading on a different computer (at least in OS X Mojave).

    An error occurred while saving the comment
    Zack Bender commented  · 

    Thank you for responding, Brian. I am on OS X 10.14.3. These issues have been happening across the last couple updates of both the Adobe and OS versions. We work off of external drives (mostly 8 TB Western Digital and Seagate USB 3.0/SS); these drives hold all information from the media to the .prproj files.

    We have a team of editors, and we try to keep projects isolated to one machine/one editor, but by necessity one editor will do changes to a project edited by someone else. So, one of the zebra-stripe instances was when a project was updated from 13.0.1 to 13.0.2, in order to revise a short video (originally edited on the same iMac Pro). Luckily that's one I experienced myself, so I quit the app, re-installed the previous version of Premiere, and was able to work just fine. Another instance was an editor switching from a 2015 iMac to a MacBook Pro. He was adding some basic text to a video and didn't pay attention to the timeline and saved the existing project and even exported it with the zebra-striped clips. The result was that each clip would play as a freeze first frame of the clip. I'm not 100% certain on the versioning, but after talking to the editor, I believe it was pretty much the same thing (upgrading a project). I know it's a best-practice to stay within the same version for a project, but we work on ~20 projects every week, and sometimes wait for months before getting all feedback from clients.

    Not sure which preferences you're referring to, so here's everything I can think of. We have different keyboard shortcuts, workspace layouts, default transitions, etc. I'm the only editor who uses Mercury Transmit, and that's only once every few months, then I turn it off. None of us modify the Debug console. We all have the same plugins (Red Giant Colorista, Looks, Universe). I believe the only plugin used on the problem projects was Red Giant Looks.

    The more annoying day-to-day issues are the crashes and file corruptions. The misaligned media is a nasty issue, but much less common and I don't have much data besides these two instances (I'm trying to get our other editors to keep track of project versions now). I'd love to hear if anyone else is experiencing these issues.

    Zack Bender shared this idea  · 
  4. 12 votes
    Sign in Sign in with: Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Premiere Pro » Stability  ·  Flag idea as inappropriate…  ·  Admin →
    Zack Bender supported this idea  · 
  5. 16 votes
    Sign in Sign in with: Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Premiere Pro » Stability  ·  Flag idea as inappropriate…  ·  Admin →
    Zack Bender supported this idea  · 
  6. 4 votes
    Sign in Sign in with: Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Premiere Pro » Stability  ·  Flag idea as inappropriate…  ·  Admin →
    Zack Bender supported this idea  · 
  7. 79 votes
    Sign in Sign in with: Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    24 comments  ·  Premiere Pro » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    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  · 
  8. 358 votes
    Sign in Sign in with: Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Under Review  ·  71 comments  ·  Premiere Pro » Color/Lumetri  ·  Flag idea as inappropriate…  ·  Admin →
    Zack Bender supported this idea  · 
  9. 48 votes
    Sign in Sign in with: Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Premiere Pro » Color/Lumetri  ·  Flag idea as inappropriate…  ·  Admin →
    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  · 
  10. 19 votes
    Sign in Sign in with: Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Premiere Pro » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    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.

    Zack Bender supported this idea  · 

Feedback and Knowledge Base