trent happel

My feedback

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

    We’ll send you updates on this idea

    33 comments  ·  Premiere Pro » General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    trent happel commented  · 

    Sorry for the wait, but Detach Proxies has finally been added in Premiere Pro 14.3.1.
    https://helpx.adobe.com/premiere-pro/using/whats-new/2020-4.html#detach-proxies

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

    Sorry for the wait, but Detach Proxies is now added to Premiere Pro 14.3.1.
    https://helpx.adobe.com/premiere-pro/using/whats-new/2020-4.html#detach-proxies

  3. 2 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Premiere Pro » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    trent happel commented  · 

    Sorry, this issue has not been fixed yet.

    An error occurred while saving the comment
    trent happel commented  · 

    I did notice that if I started with the last marker, then make edit and go to previous marker, it did not appear to have this issue. I know it's not ideal, but that might be a possible workaround until this issue can be addressed.

    trent happel supported this idea  · 
    An error occurred while saving the comment
    trent happel commented  · 

    Thank you for the report. This is being investigated.

  4. 4 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 →
    An error occurred while saving the comment
    trent happel commented  · 
    An error occurred while saving the comment
    trent happel commented  · 

    You may be running into a Premiere Pro 14.2 issue with graphic cards that do not support NVENC. A possible workaround is to go to Preferences > Media and uncheck “Enable hardware accelerated encoding and decoding (requires restart)” then Save, Quit and relaunch Premiere Pro. Does Export now work?

    You can find more information at https://community.adobe.com/t5/premiere-pro/faq-how-to-solve-crash-while-using-export-settings-in-premiere-pro-v14-2/td-p/11152571?page=1

    Also, this issue was recently fixed in Premiere Pro 14.3 Beta build 24+, if you want to verify on your system. 14.3 Beta can be found in Creative Cloud > Categories > Beta apps.

    Hope this helps.

    trent happel supported this idea  · 
  5. 4 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 →
    An error occurred while saving the comment
    trent happel commented  · 
    An error occurred while saving the comment
    trent happel commented  · 

    You may be running into a Premiere Pro 14.2 issue with graphic cards that do not support NVENC. A possible workaround is to go to Preferences > Media and uncheck “Enable hardware accelerated encoding and decoding (requires restart)” then Save, Quit and relaunch Premiere Pro. Does Export now work?

    You can find more information at https://community.adobe.com/t5/premiere-pro/faq-how-to-solve-crash-while-using-export-settings-in-premiere-pro-v14-2/td-p/11152571?page=1

    Also, this issue was recently fixed in Premiere Pro 14.3 Beta build 24+, if you want to verify on your system. 14.3 Beta can be found in Creative Cloud > Categories > Beta apps.

    Hope this helps.

    trent happel supported this idea  · 
  6. 6 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    11 comments  ·  Premiere Pro » Audio  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    trent happel commented  · 

    Thank you again for your patience. Windows 14.3 Beta build 31 is now available on Creative Cloud.

    An error occurred while saving the comment
    trent happel commented  · 

    Thanks, Michael! Glad you were able to confirm on Mac. I will post back here once Windows build has been updated in Creative Cloud.

    An error occurred while saving the comment
    trent happel commented  · 

    It appears that we are having issues with Windows builds, Due to the issues, today's Window Beta build did not post to Creative Cloud, so Creative Cloud still has the last good build 24. Mac did not have issues, so Creative Cloud now has been updated Mac Beta build 29.

    Sorry for the inconvenience. I'm looking into it, but It looks like we might need to check again tomorrow.

    An error occurred while saving the comment
    trent happel commented  · 

    That is what I am still trying to figure out, but I am hopeful new builds will be pushed tomorrow. Sorry for the wait, but try "Check for updates" tomorrow (I will also check in the morning PST and post back here)

    An error occurred while saving the comment
    trent happel commented  · 

    I'm sorry. I hate to ask, but did you make sure that you have at least Premiere Pro 14.3 Beta build 27? I noticed on one of my systems that build 24 was showing up in in Creative Cloud (another system was showing build 27, however).

    If you are using build 27, perhaps you might need to clear your Media Cache and Preferences.
    More info on deleting Media Cache - https://community.adobe.com/t5/premiere-pro/faq-how-to-clear-your-cache-in-premiere-pro-2019/td-p/8324672?page=1
    To clear Preferences, hold down Alt/Opt key while launching Premiere Pro.

    If the issue still reproduces, would it be possible to supply your Project?

    Thank you, again.

    trent happel supported this idea  · 
    An error occurred while saving the comment
    trent happel commented  · 

    Sorry for the wait, but a fix should be in Premiere Pro 14.3 Beta build 27+, if you would like to try it out. 14.3 Beta is a separate install, so it should not interfere with other shipped versions of Premiere Pro (eg: latest shipping version 14.2). You can find 14.3 Beta in Creative Cloud under Beta apps.

  7. 2 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 →
    trent happel supported this idea  · 
    An error occurred while saving the comment
    trent happel commented  · 

    Thank you for the report. This has been reproduced.

    Until a fix can be made, a possible workaround is to force an update such as scrub or play the Timeline Sequence.

  8. 2 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 » Effects & Transitions  ·  Flag idea as inappropriate…  ·  Admin →
    trent happel supported this idea  · 
    An error occurred while saving the comment
    trent happel commented  · 

    This issue should be fixed in Premiere Pro 14.0, which was released today.

    More information on issues fixed in 14.0:
    https://helpx.adobe.com/premiere-pro/kb/fixed-issues.html

    An error occurred while saving the comment
    trent happel commented  · 

    Thank you for the report! I have reproduced this issue and have reported it you our Developers for investigation.

  9. 3 votes
    Sign in Sign in with Adobe ID
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Premiere Pro » General  ·  Flag idea as inappropriate…  ·  Admin →
    trent happel supported this idea  · 
    An error occurred while saving the comment
    trent happel commented  · 

    Thank your reporting this. This issue has been reproduced and has been submitted for investigation.

    Until this is fixed, a possible workaround is to not drag the In/Out sections to the Project panel. Instead, set your In/Out in the Source Monitor and drag that to the Timeline Sequence (does not create additional instances in Project panel). I tried this and it created only one copied file after running Collect Files and Copy to New Location in the Project Manager.

    I know it does not help you for your existing Projects and may differ from your desired workflow, but might help going forward until this issue can be addressed.

  10. 2 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 » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    trent happel supported this idea  · 
    An error occurred while saving the comment
    trent happel commented  · 

    Thank you for the report. This has been reproduced and is under investigation.

  11. 4 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 » Transmit  ·  Flag idea as inappropriate…  ·  Admin →
    trent happel supported this idea  · 
    An error occurred while saving the comment
    trent happel commented  · 

    Thank your reporting this. This issue has been reproduced and has been submitted for investigation.

    Until this is fixed, a possible workaround is to not drag the In/Out sections to the Project panel. Instead, set your In/Out and drag that to the Timeline Sequence (does not create additional instances in Project panel). I tried this and it created only one copied file after running Collect Files and Copy to New Location in the Project Manager.

    I know it does not help you for your existing Projects and may differ from your desired workflow, but might help going forward until this issue can be addressed.

  12. 12 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 » Preference & Settings  ·  Flag idea as inappropriate…  ·  Admin →
    trent happel supported this idea  · 
    An error occurred while saving the comment
    trent happel commented  · 

    This issue should be fixed in Premiere Pro 14.0.1 that was just released.

  13. 47 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 →
    trent happel supported this idea  · 
    An error occurred while saving the comment
    trent happel commented  · 

    With Premiere Pro 14.0.3, it has been changed back to the existing functionality of previous versions of PPro (eg: 13.1.5 and earlier). ie: Trim shortcuts will trim clip Edit Point and Not move the Playhead.

    Based on feedback, it was best to roll back the changes to keep our long-standing behavior, until we can come up with a better solution.

    An error occurred while saving the comment
    trent happel commented  · 

    Using the shortcuts for Trim Forward/Backward or Extend Selected Edit to Playhead will no longer go into Trim Mode in Premiere Pro 14.0.1 (just released).

    For the Trim Forward/Backward shortcuts, it will remain in the view that you were in and the Playhead will now follow the trim (what was intended in 14.0 changes).

    An error occurred while saving the comment
    trent happel commented  · 

    Going into Trim Mode when using Extend Selected Edit Point to Playhead or Trim Forward/Backward shortcuts is an issue being investigated and the hope is to address ASAP.

  14. 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 » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    trent happel supported this idea  · 
    An error occurred while saving the comment
    trent happel commented  · 

    Based upon issues & feedback, we reverted this change in Premiere Pro 14.0.3. The Playhead/CTI will no follow Trim shortcuts in 14.0.3.

  15. 2 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 » Essential Graphics  ·  Flag idea as inappropriate…  ·  Admin →
    trent happel supported this idea  · 
    An error occurred while saving the comment
    trent happel commented  · 

    Premiere Pro 14.2 just shipped and contains the fix for legacy Tiles with GPU Renderer.

    What's new and fixed in PPro 14.2:
    https://helpx.adobe.com/premiere-pro/using/whats-new.html
    https://helpx.adobe.com/premiere-pro/kb/fixed-issues.html

    An error occurred while saving the comment
    trent happel commented  · 

    By any chance are you using legacy Titles using GPU Renderer in Premiere Pro 14.1? If so, there is an open issue in Premiere Pro 14.1 using legacy Titles with the GPU Renderer. The good news is that this issue has already been fixed in 14.2 Beta.

    Possible workarounds include setting the Renderer to Software Only (File menu > Project Settings > General > Video Rendering and Playback > set to Mercury Playback Engine Software Only) or use Essential Graphics (the current Titler in Premiere Pro) instead of legacy Titler or using 14.2 Beta (if you feel comfortable working in Beta version) or you can always go to Creative Cloud and install 14.0.4 if you wish to use GPU in a shipping version with the legacy Titler.

    More information on this issue can be found here: https://community.adobe.com/t5/premiere-pro/faq-how-to-solve-low-level-exception-error-after-updating-to-premiere-pro-14-1/m-p/11050854?page=1
    More information on Essential Graphics: https://helpx.adobe.com/premiere-pro/using/essential-graphics-panel.html

    Hope this helps.

  16. 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 » General  ·  Flag idea as inappropriate…  ·  Admin →
    trent happel supported this idea  · 
    An error occurred while saving the comment
    trent happel commented  · 

    FYI, the fix for legacy Titles with GPU Renderer is in Premiere Pro 14.2, which just shipped.

    What's new and fixed in PPro 14.2:
    https://helpx.adobe.com/premiere-pro/using/whats-new.html
    https://helpx.adobe.com/premiere-pro/kb/fixed-issues.html

    An error occurred while saving the comment
    trent happel commented  · 

    Apologies for this issue. There is an open issue in Premiere Pro 14.1 using legacy Titles with the GPU Renderer. The good news is that this issue has already been fixed in 14.2 Beta (build 24+), so you can try that if you like or wait until 14.2 ships.

    More information can be found here: https://community.adobe.com/t5/premiere-pro/faq-how-to-solve-low-level-exception-error-after-updating-to-premiere-pro-14-1/m-p/11050854?page=1

    Other possible workarounds include using Essential Graphics (the current Titler in Premiere Pro) or using 14.2 Beta (if you feel comfortable working in Beta version) or you can always go to Creative Cloud and install 14.0.4 if you wish to use GPU in a shipping version with the legacy Titler.

    More information on Essential Graphics: https://helpx.adobe.com/premiere-pro/using/essential-graphics-panel.html

    Thank you.

  17. 2 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 » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    trent happel supported this idea  · 
    An error occurred while saving the comment
    trent happel commented  · 

    The fix for legacy Titles with GPU Renderer is in Premiere Pro 14.2, which just shipped.

    What's new and fixed in PPro 14.2:
    https://helpx.adobe.com/premiere-pro/using/whats-new.html
    https://helpx.adobe.com/premiere-pro/kb/fixed-issues.html

    An error occurred while saving the comment
    trent happel commented  · 

    Apologies. There is an open issue in Premiere Pro 14.1 using legacy Titles with the GPU Renderer. This issue has already been fixed in 14.2 Beta.

    As you have found out, a possible workaround is to set the Renderer to Software Only. You may need to Save, Quit Premiere Pro, then relaunch and open the Project. It should now display your footage as it is set to Software Only Renderer.

    More information can be found here: https://community.adobe.com/t5/premiere-pro/faq-how-to-solve-low-level-exception-error-after-updating-to-premiere-pro-14-1/m-p/11050854?page=1

    Other possible workarounds include using Essential Graphics (the current Titler in Premiere Pro) or using 14.2 Beta (if you feel comfortable working in Beta version) or you can always go to Creative Cloud and install 14.0.4 if you wish to use GPU in a shipping version with the legacy Titler.

    More information on Essential Graphics: https://helpx.adobe.com/premiere-pro/using/essential-graphics-panel.html

  18. 8 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 » Editing  ·  Flag idea as inappropriate…  ·  Admin →
    trent happel supported this idea  · 
    An error occurred while saving the comment
    trent happel commented  · 

    Apologies. The fix for legacy Titles with GPU Renderer is in Premiere Pro 14.2, which just shipped.

    What's new and fixed in PPro 14.2:
    https://helpx.adobe.com/premiere-pro/using/whats-new.html
    https://helpx.adobe.com/premiere-pro/kb/fixed-issues.html

    An error occurred while saving the comment
    trent happel commented  · 

    There is a known issue with Premiere Pro 14.1 using legacy Titles and the GPU Renderer, which has already been fixed in 14.2 Beta (Beta builds are available in Creative Cloud > "Beta apps" if you wish to verify the fix)

    In 14.1, possible workarounds include using Software Only Renderer (File menu > Project Settings > General > Video Rendering and Playback and set the Renderer to Mercury Playback Engine Software Only) or you can go back to 14.0.4 if you require GPU Renderer.

    https://community.adobe.com/t5/premiere-pro/faq-how-to-solve-low-level-exception-error-after-updating-to-premiere-pro-14-1/td-p/11050854

  19. 2 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 » Essential Graphics  ·  Flag idea as inappropriate…  ·  Admin →
    trent happel supported this idea  · 
    An error occurred while saving the comment
    trent happel commented  · 

    Premiere Pro 14.2 just shipped and contains the fix for legacy Titles with GPU Renderer.

    What's new and fixed in PPro 14.2:
    https://helpx.adobe.com/premiere-pro/using/whats-new.html
    https://helpx.adobe.com/premiere-pro/kb/fixed-issues.html

    An error occurred while saving the comment
    trent happel commented  · 

    This is a known issue with Premiere Pro 14.1 using legacy Titles and the GPU Renderer, which has already been fixed in 14.2 Beta (Beta builds are available in Creative Cloud > "Beta apps" if you wish to verify the fix)

    In 14.1, possible workarounds include using Software Only Renderer (File menu > Project Settings > General > Video Rendering and Playback and set the Renderer to Mercury Playback Engine Software Only) or you can go back to 14.0.4 if you require GPU Renderer.

    https://community.adobe.com/t5/premiere-pro/faq-how-to-solve-low-level-exception-error-after-updating-to-premiere-pro-14-1/td-p/11050854

  20. 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 » GPUs  ·  Flag idea as inappropriate…  ·  Admin →
    trent happel supported this idea  · 
    An error occurred while saving the comment
    trent happel commented  · 

    The fix for legacy Titles with GPU Renderer is in Premiere Pro 14.2, which just shipped.

    What's new and fixed in PPro 14.2:
    https://helpx.adobe.com/premiere-pro/using/whats-new.html
    https://helpx.adobe.com/premiere-pro/kb/fixed-issues.html

    An error occurred while saving the comment
    trent happel commented  · 

    This is a known issue with Premiere Pro 14.1 using legacy Titles and the GPU Renderer, which has already been fixed in 14.2 Beta (Beta builds are available in Creative Cloud > "Beta apps" if you wish to verify the fix)

    In 14.1, possible workarounds include using Software Only Renderer (File menu > Project Settings > General > Video Rendering and Playback and set the Renderer to Mercury Playback Engine Software Only) or you can go back to 14.0.4 if you require GPU Renderer.

    https://community.adobe.com/t5/premiere-pro/faq-how-to-solve-low-level-exception-error-after-updating-to-premiere-pro-14-1/td-p/11050854

← Previous 1 3 4 5

Feedback and Knowledge Base