Andrew

My feedback

  1. 5 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 » Effects & Transitions  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Andrew commented  · 

    I remembered another problem with the WS filter. Once you've stabilized and rendered a clip... you can't touch that clip without it unrendering. If you cut one frame from it, the whole clip unrenders. Not changing the shot at all, not touching the filter at all... not adding any frames that need to be analyzed... CUTTING a frame that was already analyzed unrenders the clip. It doesn't need to be re-analyzed, so it's not like the stabilization is changing. It just unrenders for some reason. This is another aspect of the notorious problems that Premiere has with holding onto render files, which I've also posted about.

    An error occurred while saving the comment
    Andrew commented  · 

    Something else I'd like to see is the ability to keyframe the "Smoothness" setting, so that if I want one part of the shot to be stabilized, but another part of the shot to be left alone, then I can keyframe the smoothness to go from 50% down to 0% during the shot.

    I sometimes have to do this if one part of the shot desperately needs to be stabilized, but another part of the shot either doesn't stabilize well or doesn't need it.

    Currently, the only way to do anything even close to that is to splice the clip into two, and then put the stabilizer on the one I want... then do a really tricky and time-consuming thing were I have to zoom into the other clip and carefully match it into the right position so it doesn't jump at the splice point. Obviously, not a great way to do it, but there's no other way to apply the stabilization to one part of a shot without affecting another part. KEYFRAMES, PLEASE!

    Andrew 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 » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Andrew commented  · 

    It's also weird that they skipped 2016. I know it was a terrible year and all, but you look through the versions and it's like, "Where's 2016? Did I miss a version?" Kinda like Apple skipping FCP 8 and 9.

  3. 30 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

    14 comments  ·  Premiere Pro » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    Andrew 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

    2 comments  ·  Premiere Pro » 3rd Party Software  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Andrew commented  · 

    PluralEyes mostly works for me in CC2018, but there is a major pain in how it handles footage of different framerates. Namely, it doesn't. It wants all footage to be the same, or I have to remove the different footage, sync with just the audio, then go in and put all the video clips back individually.

    I'm sure this is a Red Giant programming problem, and not Premiere's fault, but... maybe work with RG on that one if you could. I often have to sync footage of different framerates together, and this has always been a major time waster for me.

  5. 168 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  ·  87 comments  ·  Premiere Pro » Essential Graphics  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Andrew commented  · 

    I mostly like the Legacy Titler for the nice separate window that it opens in which allows you to cleanly do all the titling and then close it when you're finished. Whereas the way the Essential Graphics titling works is too "messy" by comparison, in my opinion. It opens a panel into the workspace instead, which makes it a little more messy to open and close. And you have to do all the titling in the program monitor, which you might often have to re-size or scroll around in, etc, while bouncing back and forth to the Essential Graphics window in your workspace, which doesn't fit into my normal workspace setup, etc.. basically, it's just a lot less nice to work with. Whereas the Legacy Titler is nice and clean... opens when you need it, do all the work in that window, then close it when you're done. Simple and efficient.

    Andrew supported this idea  · 
  6. 25 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 » Stability  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Andrew commented  · 

    YES! I've encountered this issue a lot as well. Nesting audio will often lead to out-of-sync exports. I can sometimes fix it by changing the sampling rate (if audio is 44.1khz with sequence at 48khz, or vice versa) but sometimes it doesn't help either way, and the only way to workaround is to do as you said and export the audio separately, then import it and re-sync. Quite a waste of time.

    Andrew supported this idea  · 
  7. 611 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

    18 comments  ·  Premiere Pro » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    Andrew supported this idea  · 
  8. 559 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  ·  62 comments  ·  Premiere Pro » Effects & Transitions  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Andrew commented  · 

    Sounds like you're putting the keyframe at the end of the clip instead of on the LAST FRAME of the clip, which is one frame back from the end of the clip itself. I do this a lot myself. When you just drag the keyframe to the end of the clip, it's putting it on the same frame as where the splice is, which is why it's showing the next clip, because that's the first frame of the next clip. Back your playhead up one frame, then move the keyframe to that frame.

1 3 Next →

Feedback and Knowledge Base