• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Artifacts exporting in Premiere 2024 on PC only

New Here ,
Jun 17, 2024 Jun 17, 2024

Copy link to clipboard

Copied

Currently, I'm having an issue with exporting in Premiere on PC (only). Basically, periodically, I'm getting encoding artifacts randomly in the videos I export. It is consistent in where it appears in the video (always in the same places), the errors don't appear in the source video, and when I export on a Mac - the artifacts aren't there. Here is an example of what we're seeing:

Tanner291414841ecw_0-1718669067275.png

Views

536

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Jun 17, 2024 Jun 17, 2024

Copy link to clipboard

Copied

in the future, to find the best place to post your message, use the list here, https://community.adobe.com/

p.s. i don't think the adobe website, and forums in particular, are easy to navigate, so don't spend a lot of time searching that forum list. do your best and we'll move the post (like this one has already been moved) if it helps you get responses.



<"moved from cc desktop bugs">

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jun 18, 2024 Jun 18, 2024

Copy link to clipboard

Copied

Thank you - looking forward to any guidance on this....

 

So far, I've tried:

- rebuilding the computer and reinstalling everything to the latest version, 

- walking back versions into 23.XX

- Rendering in other export formats (MPG2/AVI/H265)

- Rendering with all sorts of options switched back and forth in Export settings

- Rendering the same PPROJ/source files from a different PC

 

So far, if its on a PC, the problem exists, if its with a Mac/OSX, the problem is not present. 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Participant ,
Jun 18, 2024 Jun 18, 2024

Copy link to clipboard

Copied

Is the media on your timeline an All-I codec? While it doesn't help diagnose your exact problem, a solution that should work would be to convert your raw/source media to ProRes or Cineform, and then replace your media on the timeline with that, then try exporting.

I've seen the inverse of your problem (Macs having this issue where PCs didn't) and more or less came to the conclusion that the machines we were using were underpowered. Converting the source media (less work for the computer to use all-I codecs) worked for me.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jun 18, 2024 Jun 18, 2024

Copy link to clipboard

Copied

That is a graphics issue ... go to the Project panel dialog, change the GPU setting to Software Only, and see if it disappears. If so, there's your issue ...

 

Which GPU and what driver version are you using? If Nvidia, try updating to the most recent Studio driver, and using the "Clean install" options.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Jun 18, 2024 Jun 18, 2024

Copy link to clipboard

Copied

If using a Nvidia card and 24.4.1 or later update to the most current STUDIO driver.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jun 21, 2024 Jun 21, 2024

Copy link to clipboard

Copied

I am using an Nvidia 3070, and so I tried both of your suggestions - changing the GPU setting to software only, and installing the latest studio drivers as a 'clean install'. Blaming the GPU and the render process for encoding was next up on my list of things to track down....unfortunately neither of these suggestions worked, and the output is exactly the same.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Jun 21, 2024 Jun 21, 2024

Copy link to clipboard

Copied

quote

...unfortunately neither of these suggestions worked, and the output is exactly the same.


By @thom1329_2

 

I am assuming that your source footage is .mp4 footage. If yes, the result you see happens too often but can be solved 98 times out of 100 if you rewrap the current source file and then use the rewrapped file as your source file.

 

Rewrapping a file can be done in the free of charge Shutter Encoder - Encoder|Converter

 

Try that and report back if it helped or not.

 

Averdahl_0-1718993632435.png

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jun 28, 2024 Jun 28, 2024

Copy link to clipboard

Copied

 I tried re-wrapping the source files, and then replacing the footage in the timeline - and the exact same problem (at the exact same time) persists.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jun 28, 2024 Jun 28, 2024

Copy link to clipboard

Copied

Sounds like corruption in the sequence metadata.

 

Create a new sequence, copy/paste the clips from this to that. Next step of troubleshooting. And hope it works.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jul 01, 2024 Jul 01, 2024

Copy link to clipboard

Copied

I just tried this as well (creating a new sequence - I even did this in a brand new pproj) and copying/pasting the clips from the old sequence to the new....and no luck again. 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jun 20, 2024 Jun 20, 2024

Copy link to clipboard

Copied

I too have been dealing with the exact same issues regarding artifacts on export. On A PC as well with everything updated. Rolled back Premiere and AME to the previous version where it seemed to work but doesn't anymore.  The software rendering option still causes issues but they are never in the same spots on the exports and it is ALWAYS on MXF files from a Sony FX6. I've exported other MXF files from the same camera over the past few years and didn't have this issue until the last update. I deleted all the render files as well although everything in the timeline plays as it should. I appreciate the help.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jun 24, 2024 Jun 24, 2024

Copy link to clipboard

Copied

After having an Adobe tech work remotely through all the possible combinations on my comp the best option he came up with was to "render and replace" the trouble clip. He ran with the GoPro preset option which worked although it still doesn't explain why I was able to export out the exact same project with all the same settings a month ago with no artifacts.  

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jun 24, 2024 Jun 24, 2024

Copy link to clipboard

Copied

That's a huge pain! Yea ... and why the change? Huh.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jul 17, 2024 Jul 17, 2024

Copy link to clipboard

Copied

Interesting development to this issue.... Randomly a co-worker tried rendering this problem file, and Media Encoder rendered the video perfectly. Nothing had been changed, and all files were in their original configuration (I had walked back all troubleshooting efforts). To be sure this stuck, I installed an NVIDIA GPU update, and did a restart. Now the problem is back....consistently the same as it was before 😞 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Jul 17, 2024 Jul 17, 2024

Copy link to clipboard

Copied

I don't know which driver you've got, and Nvidia has made some really bad drivers over the last year. So it would be so helpful to get the driver number you have installed.

 

I have seen a post, maybe a week back, by someone else who's been having bad image breakup issues, and they had downloaded the 'newest' Nvidia Sutdio driver and all was well on their machine.

 

But they didn't say the number of that driver! 

 

I do not have the Nvidia "experience" installed, just their basic control panel, and I do not have things setup to auto-update any drivers. As the one that works, I keep until I need to change it.

 

So posting a driver number, whether because it's bad or good, is helpful.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Jul 17, 2024 Jul 17, 2024

Copy link to clipboard

Copied

quote

...I installed an NVIDIA GPU update, and did a restart. Now the problem is back....consistently the same as it was before 😞 


By @thom1329_2

 

  • Does it work if you export the file directly from Premiere Pro, iow take Media encoder out of the equation?

 

  • If you export as usual via Media Encoder, what happens if you prior to export launch Media Encoder and go to Edit > Preferences > General and under Video Renderer change to Mercury Playback Engine Software Only and then click OK and now export the timeline?

 

  • One other thing to test in Media Encoder is to once again go to Edit > Preferences > General and this time un-check Import sequences natively.

 

  • And as R Neil Haugen points out, use only the Studio Driver from Nvidia. Don not use the Game Ready driver.

 

Averdahl_1-1721233700180.png

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jul 18, 2024 Jul 18, 2024

Copy link to clipboard

Copied

To continue the discussion and address ideas/messages above (thank you for the help!):

 

- It does not work to directly export from Premiere Pro - I get the same exact issue

- I've tried both the Mercury Playback Engine Software Only and Mercury Playback Engine GPU Acceleration (CUDA), neither have fixed this issue

- I tried unchecking the box 'Import sequences natively' in Media Encoder, this did not fix it either, 

- I currently have Nvidia Studio Driver Version 560.70 WHQL for Windows 10 64-bit English (US) installed. I've also tried the following drivers (all Windows 10 64-bit):

  > NVIDIA Studio Driver 556.12

  > NVIDIA Studio Driver 555.99
  > NVIDIA Studio Driver 555.85
  > NVIDIA Game Ready Driver 560.70
  > NVIDIA Game Ready Driver 556.12
  > NVIDIA Game Ready Driver 555.99
  > NVIDIA Game Ready Driver 555.85

None of these drivers exhibited any different behavior, except that the NVIDIA Game Ready Driver 556.12 was the driver I had installed when it miraculously worked before restarting and updating drivers. I've since tried these same drivers again, and the issue is back.  

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Jul 23, 2024 Jul 23, 2024

Copy link to clipboard

Copied

LATEST

It appears that by selecting the option 'Use Proxies' in the render settings, this issue has cleared up. I can render from Premiere, or Media Encoder, and mess with all sorts of other settings, and it just works! Not sure why this is the case, but we're going to continue rendering with this option selected to solve this problem moving forward! 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines