Known Participant

Question

Glitching frames during GPU Acceleration

Forum|Forum|5 years ago
December 27, 2020
9 replies
8259 views

Does anyone have a solution for this problem?

I've been having problems in Adobe Premiere where random frames in my sequence appear glitched and broken, and sometimes even render out in that state.

I've attached three pictures of the problem occuring, note how they look suspiciously like a typical "bad frame" on a corrupt H264 video. While my source footage is AVCHD format (and therefore actually H264 under the hood), I can confirm they aren't the result of corrupt files or an actual part of the footage - these glitched frames appear at different points in the sequence each time I open Premiere, do not appear in other programs and sometimes "fix themselves" after a while.

I have confirmed that turning off GPU Acceleration fixes the issue, but for a couple of reasons I would prefer to find a better solution that this. I can also confirm that the GPU Hardware itself is not at fault, as I tried other GPUs and the problem remained.

I am using the latest version of Premiere Pro (14.7) and the latest NVIDIA Studio Graphics driver (460.89).

Here are my specs:
Ryzen 7 3700X
MSI Tomahawk X570 Motherboard

NVIDIA RTX 3070 (the issue also occured with two different RTX 2060 SUPER cards I borrowed for testing)
Samsung 1TB 970 Evo Plus M.2 NVMe SSD (Boot Drive, Adobe Installation and Media Cache)

ADATA 1TB M.2 NVMe SSD (for source footage)
Seagate 2TB SATA 7200RPM HDD (for project files, Auto Saves and Preview Renders)

This topic has been closed for replies.

FlyingFourFun

Inspiring

EBalma; Have you tried to convert your videos to H264 using media encoder (or handbrake) before importing them and see what happens? If you provide a dropbox to download a sample of your footage, I would be prepared to check if I see the same artificating you do on my system for you if that would be helpfull.

E

EBalmaAuthor

Known Participant

Here's a OneDrive link to one of the source videos. Note that this was filmed in slow motion and needs to be sped up 4x to match realtime.

https://jupitermediavic-my.sharepoint.com/:v:/g/personal/ethan_jupitermediavic_onmicrosoft_com/EZO5a157CjhDi88sCXjohdcBFWgx1N4AWku_oEWhcXWZRw?e=d2iyme

FlyingFourFun

Inspiring

Okay, I downloaded you file and found somethign very interesting.....

The file is perfect by the way, not a single frame is damaged.

Premier and media player will play it perfect at the native frame rate, also plays fine at 200%, 300% and 400% when using frame sampling (The default). I had to do no rendering, despite the timeline being red and in same cases yellow is played fine;

If I changed the blend mode to Optical Flow; it starts to look like the sample you provided. I will attempt to attach the screen shot. Once I changed it to Optical flow; the playback issues started to show up. I could change it to frame blend or frame sample, and the issues were still present. If I scrubbed the timeline the issue would appear on different parts of the video, not always the same

I decided to render preview the timeline, and then when scrubbing all those artifcats were no longer present. It didnt matter how hard I tried, scrubbing didnt reveal the artificats pictures below.

I will also say, that its 100% repeatable, I can very seldom scub without issue. Playback was always fine for me after I rendered the preview files without fail.

This is the timeline after I enabled optical flow, and started to scub it agressive. The quicker the movement of the playhead, the easier it was to get this result.

I then decided to use Media encoder to drag the file you provided into it, and used the YouTube Present and converted it to a MP4 container. The file performs flawless on all scubbing and I could not duplicate the issue at all that I captured above. The MP4 container takes a marginal split second that you can notice to render the frame the frame you stop at when scrubbing. But in 100% of the testing, there was never any artificating.

I am can say that 100% of every single frame of video you provided is fine. There is somethign wrogn with the encoding or decoding of the .MOV container you were using. I lean towards the decoder in premier for the timeline itself, as media encoder had no issue using the NVENC encoder to convert it to a MP4 file, and it scubbs and plays back perfect at 100%, 200%, 300% and 400% with agressive time line scrubbing.

Does this help you?

FlyingFourFun

Inspiring

I have a few tips for you to try, I read the whoel thread, but there is a ton of details in it, if I am repeating something apologies in advance;

First, do not use this drive for previews:

Seagate 2TB SATA 7200RPM HDD (for project files, Auto Saves and Preview Renders)

Previews, generates lots of drive fragmentation, which is the enemy of video files.

Basicaly, I would ONLY use this drive for exported projects.

The other thing you want to do, is run the trim command on all your SSD/NVME drives. When you do this, also run the defragment command on the SATA drive I noted above. If you are not sure what Trim/Defrag are its best to google it, but run these commands.

Second, depending on what version of windows / build number, you may have the version with the issues with the trim command, that wasnt working proper. If you can, upgrade to the latest Windows Builds, also, look for option drivers while you update, windows 10 update doesnt make it very clear when it offers options updates, but look for them on the update page.

Also, if you have not downloaded the samsung magition software, down it, and check to ensure firmware is up to date on those drives. They also offer a NVME enhanced driver (I use it) and it will help.

Turn off the MSI game mode boost. Often, game mode boost stuff disables certain things that can allows errors to show up in the math it does. Your driver / Bios setup should be focused on quality, not speed.

I dont know if you have screen recording software installed, but sometimes, driver packages etc can offer OBS install ot specific tunning, please ensure thats all off/unistalled (unless you use it, in which case try it as trouble shooting).

Do your mother board bios updates, if you have any. Thats a very new Chip, and they may have updates that you need. I have nto run AMD before, but for intel, there is often a 'chipset' driver package for the operating systems that match the Bios update path. AMD might have a simular path.

What your seeing on that screen appears to be envenc decode issues. I suspected that your root issue has to do with the overclock of video card at first, but it appears to me that your issue progressed from none, to increase in occurances. This leads me to belive that 7200RPM drive fragmentation and possible TRIM and firmware for the SSD/NVME might be playing a role.

I had a issue with the NVME driver causing me all sorts of issues in the late fall, I had to install the driver again as a windows update appeared to damage the driver, but device manager was reporting it was current. You might have the same issues, so best to install the NVME driver again (full install/overwrite).

Here is a half decent link for the driver details, but download it from samsung direct, I never trust these 3rd party sites for links to drivers:

Samsung NVMe SSD Driver Download v3.3 (guru3d.com)

And please, stop using that 7200RPM SATA drive for preview files, between the speed of the drive and the fragmention issues with that type of drive, it will cause you greif at some point. (run the defrag also as noted earlier).

And last thing, if you have antivirus software installed, remove it for at least testing. I have used windows defender and have had no issues, but if your running other scanners, they tend to be very agressive, and when you create/read/move a file (such as block of preview video) the anti virus wants to read the block first, and this gets in the way of playing it back.

Hopefully one of these steps gets you further along, if you have not tried them already. I am interested in your feedback on this topic.

as a side note, I run the multiple 970, 960 drives, an RTX 3090, with the current studio driver and current premier CC, with no play back issues. The GPU is NEVER busy enough in playback to give me any reason to think that a 3070 would have issues (I do note you tried multiple other video cards).

As a side note, I am not a big fan of the ADATA brand, I would suggest if you can (not already) for your testing, try putting your source footage on a the samsung for testing. If you open task Manager, you will see that the disk actrivity for all those drives, and those NVME's are not very busy at all, so for testing using the samsung for source is fine. The reason why dont have an good opnion of ADATA is mostly because I dont trust thier specs. I dont know which version you have, but its possible they are using QLC (slower) memory, and often they dont include cache on the drive, or too little cache, and this creates challanges for writting data mostly, but can for reading data also. However, ven the worst NVME drive should be okay for 4k video, but if not already, try to exclude the ADATA and the SATA for testing purposes.

Apologies for the long response, hopefully somethign that can help you will be found within it.

E

EBalmaAuthor

Known Participant

Oh don't worry about long responses - I love how you've gone into detail and broken everything down! It really gives me some insight.

Unfortunately, I still haven't found a solution so far. I've tried:
- Disabling MSI Game Boost
- Shifting everything onto the Samsung SSD
- Updating Ryzen Master (which it turns out I badly needed to do, actually!)

- Deleting my media cache several times

- Disabling antivirus realtime protection

- Uninstalling and reinstalling Samsung NVMe driver

- TRIMming and Defragging my drives

On a side note, I noticed some interesting points:
- Someone pointed out that my GPU is overclocked and may be unstable as a result. But it turns out that I am running it in Silent mode, which appears to be an *under*clock.

- I said earlier that the "glitches" I experience happened in different places, but for a while one particular frame consistently glitched. After my last few attemps to fix it, the "glitch" did move away to another frame of the same video. Again, since these glitches move around in this way and do not appear in an external player (VLC) I don't think it's the source footage at fault.

- you mentioned that you don't trust ADATA, and from your description I can understand why (cache-less SSDs are bullsh*t), but I benchmarked the drive using CrystalDiskMark and it almost matched the Samsung drive in terms of speed. It also has good reviews online.

- For some reason, I can't find a download link for the AMD Ryzen Chipset drivers anymore, and MSI Dragon Centre can't find an available update either.

There are two more things that I want to try for now, and I'll post again with updates:
- When I get the time tonight, I'll run a handbrake render and transcode my footage into H264 as you suggested in a later comment. I may actually try HEVC/H265 as well to be thorough.

- I'm running the latest stable MSI Motherboard BIOS, but for some reason the "next" update has been marked as Beta for a while, for far longer than other motherboards have done so for the same AMD AGESA update. I don't want to risk installing a beta, but on this latest stable release my motherboard has had issues taking a little too long to POST. With that information in mind, I'm considering rolling back to the *previous* stable BIOS version.

E

EBalmaAuthor

Known Participant

Oh yeah, one more thing: I'm not sure preview renders are to blame. You know how there's that bar on the top of the timeline that shows different colours for the render status? One of the clips that consistently glitches is marked yellow, which I gather is "should be fine with GPU acceleration turned on".

In another project file where the same clip and same effects are used, but with the Mercury Playback Engine set to Software Only, I have rendered that segment and it appears with the color green. However, the glitch still occurs here now and then. Having said that, this project file was still using the SATA/HDD drive for previews at the time.

Ann Bens

Community Expert

E

EBalmaAuthor

Known Participant

Here are the images from when i first encountered this problem:

And this image is from when the same error occured with Mercury Playback Engine set to Software Only:

Also, quick update: i noticed only yesterday that Nvidia released a graphics driver update (461.09), albeit via the "Game Ready" channel rather than the "Studio" Channel. I tried switching to that channel to get the update but alas, the error remains. Here's a screenshot from after that update:

FlyingFourFun

Inspiring

I use 460.89 (Dec 15, 2020) nvidia driver, and have no issues. Provided as a data point for you.

C

Carlos Ziade

Community Expert

try to transcode one of your glitchy videos to H.264 (match source) or QuickTime GoPro Cineform YUV 10 bits

Test that exported clip with both GPU Acceleration and Software Only Renderers in project settings and export

E

EBalmaAuthor

Known Participant

UPDATE: To my horror, the error has now appeared in another project with GPU Acceleration turned off!

Again, I have confirmed it isn't the video at fault. I moved to the next frame and back and the glitch vanished immediately.

I am using a feature on my motherboard called MSI Game Boost, which I gather is essentially a sizeable CPU overclock. There is a *chance* that it's pushing my CPU a little too hard and making my system unstable, but I'll look into it. Stress testing with a program called OCCT threw up one stability-related error, but the same test later showed no errors. I *think* the original error with GPU Acceleration turned on still occured with Game Boost turned off. As established earlier, downclocking my RAM/turning off XMP has no effect.

Here's an image of the glitch reappearing without GPU Acceleration:

C

curt0D45

New Participant

I just purchased a new laptop yesterday with 40gb ram and my premiere pro video clips are laggy and choppy. I can't even edit my video because of this. I made all the recommended changes, spoke to an Adobe rep and a Microsoft rep and the lagging choppy issues are still there. Anyone here can confirm that their 2020 version of premiere pro is working flawlessly?

FlyingFourFun

Inspiring

curt0D45

Your inquire should be posted as a new topic so people can find it. Its been lost within this thread and thus no one has been respoding. With that said, when you start the new thread, please include more details about your hardware, what the source footage is, size, bit rate etc. The laptop model and specs would be very important in helping you alogn with what version of Premier your using, if your running internal HDD, or USB etc. With all this said, please open it as a new thread, as I am pretty sure your issue is not the same as what the OP started this thead for.

M

Michael Grenadier

Community Expert

as a workaround try doing a "smart render." Change your preview format to a high quality format like prores422 hq and render your entire timeline. Any place the problem occurs, re-render the shot. You could even try changing the render engine to software for those shots... when you export, enable "use previews." Not ideal, but should get the job done.