P: Glitchy Video in Timeline

[eegriff]

After I upgraded to 24.4 several days ago, I can no longer edit MXF video files. The video in the timeline is glitchy, with pixelated blocks displayed whenever something moves in the scene. The glitches are exported in the final render, so it’s not a temporary or display-only issue. (If I render the MXF to MP4 with HandBreak, there are no glitches in the output, so I think the MXF container is OK.) My camera is unchanged and I’ve used this workflow hundreds of times. I went back to an editing session from before the 24.5 upgrade and all is fine–no glitches. I cleared the cache, rebooted my Mac, checked the sequence settings, but nothing helps.

[Radim37046208zysv]

Hello, I have struggled with the artifacts and glitches so long, as you can read in this thread. And finally the posts about disabling the hardware decoding helped me. So far I haven't noticed any glitch. Thank you!

But I don't uderstand why this feature is causing problems.

[davids77232656]

Same issue!! MXF files from 2 cameras mixed with MP4 in timeline.

Even if i don't use nvidia GPU  problem persists with glitchs in render. Even if i pre-render first and image appears ok in timeline, when i render, the problem continues. 

At this point solution like convert to Prores 444 or 422 all MXF and relink with right click on mxf file and "replace footage"is out of question for me but it can be a a short solution for someone with less footage. If this error appears during edit: switch off gpu then go to sequence>delete render files or sequence>delete render files in to out. Then pre-render again and switch on gpu again. It worked for me but render still have some glitchs.

My Cpu is AMD Ryzen Threadripper 3960X 24-Core Processor 3.80 GHz, motherboard msi trx40 pro 10G, i have a full 256GB RAM installed/192 Available . GPU Nvidia (M4000). Cameras are 2 sony FX6 and 1 sony FX3. 

[davids77232656]

Hi Jamie, thanks for help! I will install beta version 25. i will let you know soon.

[davids77232656]

Hi Jamie ! I have installed premiere pro beta and render 1 minute where i have 2 Glitchs.

I tried render with GPU and Mercury and now i only have 1 Glitch. Any other workaround? thanks in advance

[jamieclarke]

Hi @davids77232656 - in your render settings can you try switching to 2-pass VBR, or CBR and let us know if that helps your issue.

[MartynMoore]

Hi there.

Back in June I posted about a bizarre glitch that appears in the program monitor and also output files. The problem prevails and seems to be happening mostly with .MXF files. Here's my original post with a clip: https://community.adobe.com/t5/premiere-pro-discussions/glitch-after-cut-between-clips/m-p/14719592#...

I have just set up a new project and imported footage using the prescribed Media Browser method. Now I have pulled clips down to a timeline, I'm seeing this:

It always seems to be .MXF files. Could the two problems be related?

System spec: Premiere Pro version 24.6.1 (Build 2). Windows 10 Pro. Intel i9-7900X CPU @3.30GHz, 64GB RAM, GeForce GTX 1080 Ti, NVIDIA Studio Driver 561.09.

Ideas and suggestions are most welcome.

Martyn

[jamieclarke]

Hi @MartynMoore - I'm sorry for the trouble.  We have made big improvements with MXF files in version 25 or Premiere Pro.  Where is your media located?  I'm sorry about the glitching.  Can you try going to your preferences under media and disable hw acceleration.  restart your project and then let us know if you are still receiving the glitch.  

 

[davids77232656]

Hi, Ok i have tried for Beta version to render in h264 CBR and VBR2 with max bitrate but problem continues.

Tried with GPU and Mercury Render. Export successfully but no diference in result - always with 1 glitch in same spot. Also tried MXFopta xdcam 50 pal 422 and here i got 3 Glitchs at same clip.

I have unistall 24.6.1 and tried 24.6.  I have 2 glitchs with same specs as before to H264, quicktime and MXF opta.

This time I have unistall 24.6. and tried 24.3. Same specs ZERO glitchs. Both with gpu and mercury. Export successfully with no errors at all. Mercury render takes like 30 minutes to render which is odd but its ok in result.

In beta version is 2 to 3 minutes borh GPU and Mercury.

For now, I think the solution is in Version 24.3 !

[jamieclarke]

HI @davids77232656 - When you upgraded did you ever clear your cache?  When you update to a new version you should always hold down "shift" and select the option to "clear media cache". There is a media cache bug upgrading from 24.3 to any newer 24 version.  Can you let us know what graphics driver version you are using,  If you aren't on the studio driver please use that one.

[MartynMoore]

Hi Jamie. My media is on a dedicated production 500GB SSD, along with the project file. I have a separate 250GB SSD for my media cache files, which is the way I was recommended to configure it in 2018. I think I followed advice from Puget Systems. The problems seem to have a similar feel. It's like Premiere Pro is having difficulty accessing the media. Sometimes I see the glitch in the program monitor as heavy pixellation and it remains if I pause the playback. But it clears after about a second, like PP was able to pull in the data after a delay. I hope this is useful.

[MartynMoore]

Do you think it might be worth me downloading the beta version of PP 25? If you have improved the way it handles .MXF it would be great for my FS5 files.

[jamieclarke]

Hi @MartynMoore - Please download version 25 it should be available for you now.  Let us know if you have any issues.

[MartynMoore]

Doing that now Jamie. Will let you know. Thanks.

[Kevin-Monahan]

Updating the status for this bug report.

[jakew39230329]

 

Exports using hardware encoding are very slow, and cause this glitch throughout the video. Happened since updating to Sequoia. Have just installed latest version of premiere and issue is still happening.

[jamieclarke]

Hi @jakew39230329 - In your export settings can you try  switching to 2-pass VBR, or CBR resolves the issue.  If you turn off hardware acceleration do you still receive the glitches?  Can you post a screenshot of your media file properties.

[jakew39230329]

Rendering with software encoding fixes the issue, although still slow.
Turning off hardware decoding in properties does nothing. The issue is on export only.

Switching to CBR or 2 pass only allows software encoding on my system anyway, so it also resolves it becasue it doesnt use hardware encoding. Im using an M1 Max Macbook Pro. Issues only started after updating to Sequoia a few weeks back.

[jamieclarke]

Thanks for the info.  Can you post a screenshot of your media file properties?

[jakew39230329]

Heres the properties of the source video file (Xavc-s from A7siii)
And also the exported files media properties.

[Edward3492930152k1]

@jamieclarke Hi, just chiming in to say I've had the same issues, and trying out the version 25 beta didn't help.

[MartynMoore]

Hi Edward, Jamie. I'm working in PP25 now and see occasional 'glitches' in the program monitor but none carrying through to output files, yet. (I've only completed three edits.) No errors retrieving frames, so far. I'm feeling hopeful...

[Edward3492930152k1]

That's good to hear, but unfortunately I'm still getting glitches in the exports. See attached.

[jamieclarke]

Hi @Edward3492930152k1 @MartynMoore - can you post screenshots of your media file properties for your media.  Thank you for your help.

[MartynMoore]

That is very frustrating, Edward. This is exactly the error I see in the Program Monitor, which would then appear, like yours, in the output file. It only seems to appear on .MXF files created by my Sony FS5. The .MP4 files from my A6400 don't do it.

One workaround that sometimes fixed it was to move the preceding clip to the track above on the timeline and drag the start of the .MXF clip to the left, under the tail of the previous clip. The .MXF clip didn't display until the previous clip was cut but resulted in some untidy timelines.

This fix added weight to my theory that it was a lag in PP pulling in the clip that caused the glitch but it didn't seem to always work. Sometimes simply lifting the clip out of the sequence, dropping it at the end, and then putting it back in exactly the same place would help. Sometimes trimming or extending the lead-in to the rogue clip would work. But only sometimes.

I also found that certain clips would be very prone to this effect, while others from the same camera, on the same shoot, would not. The problem has plagued me all summer and with glitches still appearing during editing, I fear I might not be out of the woods yet, Edward. Before version 25 I could put the playback head on a clip that showed the glitch and the glitch would stay there on the frozen frame indefinitely. Now with version 25 the glitch appears in the Program Monitor and when I pause playback it remains for about a second and then disappears. The paused frame cleans up and displays properly all by itself. Again, it's like PP is experiencing a delay accessing the clip.

To throw in another curved ball, I first saw this effect on a project that had been started on location on a laptop with a different hard drive configuration. Normally, transferring this work to my studio desktop was very simple and problem-free, until May of this year. The transfer went OK but I started to see the glitches on that project on my desktop. This might be a red herring, as all my summer projects have been created on my desktop machine and they've all had glitches.

I'll post file details from my workstation today, Jamie.

[MartynMoore]