Justin VanAlstyne

My feedback

16 results found

  1. 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 » 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)
    An error occurred while saving the comment
    Justin VanAlstyne commented  · 

    Ditto. This is tripping me up on a project today.

    Justin VanAlstyne supported this idea  · 
  2. 28 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

    5 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)
    Justin VanAlstyne supported this idea  · 
  3. 18 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

    15 comments  ·  Premiere Pro » Effects & Transitions  ·  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)
    Justin VanAlstyne supported this idea  · 
  4. 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

    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)
    Justin VanAlstyne supported this idea  · 
  5. 261 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

    21 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)
    Justin VanAlstyne supported this idea  · 
  6. 126 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

    39 comments  ·  Premiere Pro » Preference & Settings  ·  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)
    Justin VanAlstyne supported this idea  · 
  7. 380 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

    61 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)
    Justin VanAlstyne supported this idea  · 
  8. 593 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

    454 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)

    All,


    first of all I wanted to thank everyone for making this a productive conversation over the last couple of days.


    As several people responded to my comment about keeping the tone civilised, I need to dwell on that for a minute. Please hear me out, this is important to everyone on my crew and I hope it will be to you.


    Saying that we shouldn't be surprised when things get heated is very problematic in my opinion. How do you expect a junior person on my team to respond to a technical question when it is combined with something that can easily be described as hate speech? How do you think we can actually come together on actual issues when there's already the assumption that we're a big faceless corporation, not even listening to our customers?


    People on my team have received threats. I've been there over the years,…

    Justin VanAlstyne supported this idea  · 
  9. 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

    26 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
    Justin VanAlstyne commented  · 

    Personally, I was very afraid of this issue when I first got my M1 Max. But I rendered out a previous project when I got it (hardware acceleration, same preset as before), took 100% screen grabs of the same frame and overlaid them in Photoshop. There were minor differences in the noise/compression pattern, but one was not obviously better than the other. It was VERY difficult to tell the two renders apart. I've now rendered out several 4K 100mbps projects and have no concerns with the quality.

    And as a commercial pro photographer/videographer working on client projects, I feel confident in saying the above. Maybe there's an issue, I won't deny it, I'm just thinking that either it's intermittent, affecting only certain machines, or certain PP settings are triggering it.

    Justin VanAlstyne supported this idea  · 
  10. 218 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

    79 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)
    An error occurred while saving the comment
    Justin VanAlstyne commented  · 

    @Andy Adkins and @TB54… as long as your math is exact, it should divide those frames up evenly. For my specific camera and workflow, I can shoot in 59.94 fps and use speed/duration to drop it to 40% and plop it on a 23.976 fps timeline. 59.94 goes into 23.976 exactly 2.5x. But if say your original clip was actually 60.0 fps going onto a 23.976 fps timeline, then the math gets trickier and you might have some frame changes. BUT, the same thing would happen with "interpret footage". You can't cleanly interpret 60.00 into 23.976 without dropped frames.

    An error occurred while saving the comment
    Justin VanAlstyne commented  · 

    Alberto, you can change framerate/speed of individual clips on the timeline using the "Speed/Duration" option. I also keep this little list handy, which gives me the speed percents to input when I want to convert a clip to play on a 23.976 fps timeline…

    Convert —> 24fps

    30 FPS: 80%
    48 FPS: 50%
    60 FPS: 40%
    96 FPS: 25%
    100 FPS: 24%
    120 FPS: 20%
    15 0FPS: 16%
    180 FPS: 13%
    240 FPS: 10%

    An error occurred while saving the comment
    Justin VanAlstyne commented  · 

    Andreas is correct. I was mad about Premiere's inability to create proper interpreted proxies… but after some research and further learning and experimentation… the CORRECT WAY to handle this is to simply create proxies at the native FPS, and then when placing that footage in your sequence, simply slow it down with speed/duration. This works much much better and more reliably.

    Justin VanAlstyne supported this idea  · 
  11. 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

    48 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
    Justin VanAlstyne commented  · 

    This is likely super incorrect, but is there a chance that something about the M1 GPU makes for more efficient files with the same visual information?

    I have noticed the shift in file size myself after getting an M1 Max and a 3.2GB render went down to 2GB. But I compared screenshots of the videos in Photoshop, and while there is a difference, it's hard to distinguish which is which just looking at the image. This was with a 4K h264 100mbps export. I dunno, just a though.

    Justin VanAlstyne supported this idea  · 
  12. 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

    6 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
    Justin VanAlstyne commented  · 

    Sample files of what? PP project files or rendered videos? Honestly, not comfortable sharing either. The "bad" video renders all have their audio off sync by a few frames. The "good" video rendered with software encoding has perfect sync. Not much else to see.

    An error occurred while saving the comment
    Justin VanAlstyne commented  · 

    I'm not experiencing drifting per se, but my 4K exports all have their audio sync off slightly when "hardware encoding" is on. This happened to me when exporting to ProRes 422 and h.264. I was very surprised by that. Both were off by 2-3 frames.

    With software encoding, no issues with audio sync. I just spent an entire day troubleshooting this and exporting with various settings.

    I'm on PP 2022 (v22.1.2) on macOS 12.1 with Intel i9 and AMD Radeon Pro 5500M GPU.

    Justin VanAlstyne supported this idea  · 
  13. 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 » 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)
    Justin VanAlstyne supported this idea  · 
  14. 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

    2 comments  ·  Premiere Pro » 3rd Party Software  ·  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
    Justin VanAlstyne commented  · 

    Agreed. Other threads I've found have this issue dating back to 2012! Absolutely insane. And here we are two weeks away from 2022. A decade and Adobe hasn't managed to get this fixed! Mind blown.

    Justin VanAlstyne supported this idea  · 
  15. 201 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

    28 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)
    Justin VanAlstyne supported this idea  · 
  16. 12 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 » 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)
    Justin VanAlstyne supported this idea  · 

Feedback and Knowledge Base