Seth Goldin

My feedback

  1. 7 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 » Export  ·  Flag idea as inappropriate…  ·  Admin →
    Seth Goldin supported this idea  · 
    An error occurred while saving the comment
  2. 3 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 →
    Seth Goldin supported this idea  · 
    An error occurred while saving the comment
  3. 7 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
    Seth Goldin supported this idea  · 
  4. 33 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    31 comments  ·  Premiere Pro » Export  ·  Flag idea as inappropriate…  ·  Admin →
    Seth Goldin supported this idea  · 
    An error occurred while saving the comment
    Seth Goldin commented  · 

    Ouch. Just discovered this very, very painful bug. Not sure if it helps, but this is on a vanilla installation of Windows 10 Pro for Workstations 1809 build on an HP Z8, with an RTX 2080Ti and the 441.66 NVIDIA driver. Didn't matter whether I used CUDA or software-only. Cleared media cache, application preferences, etc., to no avail.

    Rolling back to 14.0.0 did indeed let me render again.

  5. 29 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    30 comments  ·  Premiere Pro » Import  ·  Flag idea as inappropriate…  ·  Admin →
    Seth Goldin supported this idea  · 
    An error occurred while saving the comment
    Seth Goldin commented  · 

    Yes, can confirm this is happening with me, too. Didn't happen in 2019, only in 2020.

    This causes quite a nasty workflow problem!

    Was happening on Windows 10 1903, but also on Windows 10 1909.

    Windows 10 1909 18363.476
    Premiere Pro 14.0.0 (Build 572)
    GTX 1080 Ti with NVIDIA Studio Driver 441.12

  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 » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Seth Goldin commented  · 
    Seth Goldin shared this idea  · 
  7. 12 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Under Review  ·  5 comments  ·  Media Encoder » Presets  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Seth Goldin commented  · 

    Thanks for this, Francis. Was quite confused, but I appreciate the information about the workaround until the bug can be fixed.

    Seth Goldin supported this idea  · 
  8. 26 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Premiere Pro » GPUs  ·  Flag idea as inappropriate…  ·  Admin →
    Seth Goldin supported this idea  · 
  9. 17 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Premiere Pro » Export  ·  Flag idea as inappropriate…  ·  Admin →
    Seth Goldin supported this idea  · 
  10. 5 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Premiere Pro » Export  ·  Flag idea as inappropriate…  ·  Admin →
    Seth Goldin supported this idea  · 
  11. 48 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    14 comments  ·  Premiere Pro » General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Seth Goldin commented  · 

    Looks like this is indeed fixed in 13.0.2. Thanks!

    An error occurred while saving the comment
    Seth Goldin commented  · 

    I'll just have to test, but "Clips imported from XML, AAF, prproj, or any other project are not referenced correctly" is not an accurate description of the issue. The bug is with MXF OP1a DNxHR LB files imported via the Media Browser. The files are not from an XML, AAF, PRPRPOJ or any other project.

    An error occurred while saving the comment
    Seth Goldin commented  · 

    No mention of this in the bug fixes in the release notes for 13.0.2...? Unless this refers to this issue: “Multiple MXF files appear truncated on the system.” Has anyone tested 13.0.2 yet?

    Seth Goldin shared this idea  · 
  12. 2 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Premiere Pro » General  ·  Flag idea as inappropriate…  ·  Admin →
    Seth Goldin shared this idea  · 
  13. 4 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Premiere Pro » User experience/interface  ·  Flag idea as inappropriate…  ·  Admin →
    Seth Goldin shared this idea  · 
  14. 2 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Premiere Pro » Formats  ·  Flag idea as inappropriate…  ·  Admin →
    Seth Goldin shared this idea  · 
  15. 37 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  Premiere Pro » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    Seth Goldin supported this idea  · 

Feedback and Knowledge Base