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

P: Strange Pixelation Glitch when Exporting

Community Beginner ,
Dec 17, 2024 Dec 17, 2024

Copy link to clipboard

Copied

Hi all, I'm a very amateur video editor but I edit podcasts part-time. I've recently been having really weird graphical glitches when I export my files and I have no idea why or what to do. I've been searching the web for answers and figured I'd ask here.

 

For context, I use the latest version of Premiere Pro and I'm on Windows 11. I export using the default settings so I think it's H.264 and Match Source High Bit Rate. If I need to provide any system specs please ask and I will find it. I've exported twice already and both times I've had this glitch, but in different places. It happens briefly, but it's still very noticeable so any help would be much appreciated, thank you.


(mod edit title for tracking)

 

 

Bug Acknowledged
TOPICS
Editing and playback , Export

Views

459

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

correct answers 3 Pinned Replies

Adobe Employee , Nov 14, 2024 Nov 14, 2024

Hi @AhmadFarman ,

 

Welcome to the Premiere Pro forums!  We’re happy you’ve reached out.  We’ll need a bit more info to try to help with your issue.

 

Please see; How do I write a bug report?

 

I hope we can help you soon.

 

Thanks,
Rach

Status Needs More Info

Votes

Translate

Translate
Adobe Employee , Dec 18, 2024 Dec 18, 2024

Hi @resourceful_rainbow2877  & @nadineg73174863,

 

Thanks for submitting your bug report. I merged your posts since it looks like you are both having the same issue.  Can you confirm which version of Premiere you are using and give more info about the footage type?

 

Sorry for the frustration and thanks for reaching out.  Hopefully, we can help you soon.

Status Needs More Info

Votes

Translate

Translate
Adobe Employee , Dec 18, 2024 Dec 18, 2024

updating status

Status Acknowledged

Votes

Translate

Translate
16 Comments
New Here ,
Nov 14, 2024 Nov 14, 2024

Copy link to clipboard

Copied

Dear Adobe Premiere Pro Team,

I am writing to report an issue I've encountered while editing in Premiere Pro 2024 and 2025. When I open and edit a project in these versions, the video glitches during playback, with visual distortions and frame skipping. However, when I open the exact same project file in Premiere Pro 2023, the video plays back smoothly without any glitches or issues.

The glitching appears consistently at specific points in the video where no issues are present in the 2023 version. I have tried the same video files and edits in both 2024 and 2025, and the problem persists in both versions.

Could you please investigate this issue? I would appreciate any guidance or fixes regarding this playback glitch.

Thank you for your attention to this matter.

Best regards,
Screenshot 2024-11-14 201508.png

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Nov 14, 2024 Nov 14, 2024

Copy link to clipboard

Copied

Hi @AhmadFarman ,

 

Welcome to the Premiere Pro forums!  We’re happy you’ve reached out.  We’ll need a bit more info to try to help with your issue.

 

Please see; How do I write a bug report?

 

I hope we can help you soon.

 

Thanks,
Rach

Status Needs More Info

Votes

Translate

Translate

Report

Report
New Here ,
Nov 14, 2024 Nov 14, 2024

Copy link to clipboard

Copied

Adobe Premiere Pro version number: Version 25.00 (Build 61)

Operating system: Windows 11 Pro (23H2)

System Info:

  • CPU: 11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz
  • GPU (Intel-based Macs and PCs): Nvidia GeForce RTX 3070
  • GPU driver (PC): Version 566.14
  • RAM: 64GB
  • Hard Drive: 464 GB SSD, 1.81TB HDD

Video format: MXF

Workflow details: Sequence HD 1080p 25fps

Steps to reproduce:

  1. Open the project in Premiere Pro 2024 or 2025.
  2. Make trims or cuts in the video sequence.
  3. Play back the edited clips.
  4. Observe if glitches occur, typically at the beginning few frames of the trimmed or cut clips.
  5. Compare with Premiere Pro 2023, where the same trims and edits do not result in glitches and play back smoothly.

Expected result: The video should play back smoothly without glitches or visual distortions, even after trimming or cutting clips.

Actual result: The video shows glitches and visual distortions specifically at the starting few frames of trimmed or cut clips during playback in Premiere Pro 2024 and 2025.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Nov 19, 2024 Nov 19, 2024

Copy link to clipboard

Copied

Hi @AhmadFarman 

Would you be able to provide us with a few file samples of what you are editing with? I need to run he media through some test to get a better reproduction of what your experiencing so I can send along the info to the team. Any share method for file delivery you choose is fine just tag my email or message me directly. Thank you

Ian

Votes

Translate

Translate

Report

Report
New Here ,
Dec 18, 2024 Dec 18, 2024

Copy link to clipboard

Copied

I work for TV and Premier has grown more and more unreliable in recent years.
The problem is that I have glitched Footage when I export Videos in Premier pro as mxf. 
I keep having those issues over the last year. I really have no idea what to do anymore. 

Screenshot 2024-12-18 154649.png

nadineg73174863_0-1734533361743.png

 

The glitches usually "stick" to a certain spot. But they look different and if relocate footage or sth the places change. 

What I already did.
Update/Reinstall Premier and use the newest or older versions. 
Update/Reinstall Drivers (clean install ofc)
Change Footage
Change Footage storage place, nvme hdd or external ssd
Change CPU and Motherboard....
Update/Reinstall Windows
With AVX 2 or without it
Change my PC. (I used 3 different systems. On apple it works. And on Davinci resolve it works always, also it's faster. Also I keep having issues with premier since forever but never with resolve which is free over years.... Just a sidenote.)
Disable GPU Rendering.
Clean Media chache.
rEsTaRt mY pC
Use Media encoder or Premier.
Disable Plugins, only have neatvideo. Also same issues when I didn't have neat video. 
Rendered to different drives than the one the footage is on.
Changed name of the Footage.
Replaced the footage from the SD of the Camera.
Electricity is stable.
Cooling is for CPU is 28 degrees. 
And I don't touch my PC during rendering. 
22 Minutes 10Bit of 4k Footage in 10 Mins render. 

I can't render it as 422 prores and then render it as mxf since the channels don't work for TV then. 
I have the issues only on HVEC, h264 and mxf.

A friend uses the same cameras and never has issues. 

I am really frustrated since I pay a lot for premier but it keeps bugging out. And I never had more than a month where it just worked. 

My System has enough power.
96 Ram
4080.
i9-kf14900 (yes old one with the bug and new one with bios that fixxed it) also the older system had another cpu.  

Everything else on the system is perfect. 
Please help me. 

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Dec 18, 2024 Dec 18, 2024

Copy link to clipboard

Copied

Hi @resourceful_rainbow2877  & @nadineg73174863,

 

Thanks for submitting your bug report. I merged your posts since it looks like you are both having the same issue.  Can you confirm which version of Premiere you are using and give more info about the footage type?

 

Sorry for the frustration and thanks for reaching out.  Hopefully, we can help you soon.

Status Needs More Info

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Dec 18, 2024 Dec 18, 2024

Copy link to clipboard

Copied

updating status

Status Acknowledged

Votes

Translate

Translate

Report

Report
Community Beginner ,
Dec 18, 2024 Dec 18, 2024

Copy link to clipboard

Copied

Hello, I am on version 24.6.1 (Build 2), and the footage I'm working with is MP4s. I also export with Match Source High Bit Rate and H.264 so my export is also an MP4.

Votes

Translate

Translate

Report

Report
New Here ,
Dec 19, 2024 Dec 19, 2024

Copy link to clipboard

Copied

Try to work with a sequence resolution that is equal to your original footage, and your export to match the sequence and see if it solves the situation. I had similar issues when using an UHD 3840x2160 timeline for a 4264x2408 ProResRaw resolution  footages.

Votes

Translate

Translate

Report

Report
New Here ,
Dec 19, 2024 Dec 19, 2024

Copy link to clipboard

Copied

Currently I am using Premier Pro (25.1)

Footage is: either MXF or MP4

Type: MXF
File Size: 8.82 GB
Image Size: 3840 x 2160
Frame Rate: 50.00
Source Audio Format: 48000 Hz - 24-bit - 4 Channels
Total Duration: 00:07:55:40
Pixel Aspect Ratio: 1.0
Color Space: Rec. 709

MXF File details:
Wrapper type: MXF OP1a (type: SingleItem SinglePackage MultiTrack Stream Internal)
File generated by: Sony, Mem (2.00)
Bitstream Format: Sony
H.264/MPEG-4 AVC Long GOP High Profile 4:2:0 Unconstrained Coding
Bitstream Format: Sony
Class 156
Gamma: S-Log3 Cine

 

Type: MPEG Movie

File Size: 11.44 GB
Image Size: 3840 x 2160
Frame Rate: 50.00
Source Audio Format: 48000 Hz - 16-bit - Stereo
Total Duration: 00:07:56:08
Pixel Aspect Ratio: 1.0Color Space: Rec. 709
Video Codec Type: MP4/MOV H.264 10 bit 4:2:2

 

Usually rather long and big files.
I work in a 4k sequence with 4k footage and then I export to mxf Full HD 25 fps. 

Votes

Translate

Translate

Report

Report
Community Beginner ,
Dec 19, 2024 Dec 19, 2024

Copy link to clipboard

Copied

Here same glitch problem in rendered clips and on the timeline during playback. Editing with Sony MXF files.

Votes

Translate

Translate

Report

Report
Participant ,
Dec 24, 2024 Dec 24, 2024

Copy link to clipboard

Copied

We have seen this too, with the HDCAM mxf format.

If you export in this format, you can fix export problems bij disable smart codec.

This setting enables very fast export of clips without any effects in the timeline. (Raw datacopy)

Clips have absoluty to be without any clitches and in the right format.

This is not always the case, sometimes there a copy errors, or clips are delivered with wrong export settings.

If you disable smart rendering codec, all edits are re-rendered to the correct MXF format.

 

theok8577996_0-1735032047055.png

 

Votes

Translate

Translate

Report

Report
New Here ,
Dec 28, 2024 Dec 28, 2024

Copy link to clipboard

Copied

Since I'm also encounting same issue, I upvoted this. I have seen this with two different computers (referencing one same network drive) with multiple projects. It's from about a week ago, but I didn't any updates or changes around system and Adobe apps.

 

Detail of the issue

  • Exported video contains pixelated glitch, at just after switching clips, in around 3-5 frames
  • Using H.264 "Match source - Adaptive high bitrate" or "Match source - High bitrate"

 

Computer A

  • Windows 11 Home Version 10.0.22631 Build 22631
  •  AMD Ryzen 7 3700X 8-Core Processor, 3593 Mhz, 8 Core(s), 16 Logical Processor(s)
  • 32GB RAM
  • AMD Ryzen RX 6600XT

Computer B

  • Windows 11 Pro Version 10.0.26100 Build 26100
  • Processor AMD Ryzen 7 5700X 8-Core Processor, 3401 Mhz, 8 Core(s), 16 Logical Processor(s)
  • 32GB RAM
  • NVIDIA GeForce RTX 4060

 

App info

  • Adobe Premiere Pro 2024, first with 24.5.1 and tested with each versions between 24.6 and 24.3
  • What  I tried: Cleaning media cache and previews, and clean install

 

Source video

  • Multiple clips captured with SONY Z-90
  • File type: MXF OP1a, AVC Long GOP High 4:2:2 10-bit
  • 1920x1080 or 3840x2160, 29.97f/s

 

Other thing I noticed

  • Only few (not all) clips seem to have the issue.
  • There are the issues exporting whole sequence (around 60-90mins) , but not with exporting only 1 mins around same point.
  • No issues with exporting with macOS from same disk and projects.

 

I'm sorry I can't provide any sample since I'm mainly working with client works.

Votes

Translate

Translate

Report

Report
Community Beginner ,
Jan 08, 2025 Jan 08, 2025

Copy link to clipboard

Copied

Hi, we are having a very similar experiencie overall as most of these users (specially as @nandenjin), as we also use a Sony Z90. I'll be adding a .XML file from one of the files that got those glitches, as we also have to work with client's content and unable to share none of it:

 

<NonRealTimeMeta xmlns="urn:schemas-professionalDisc:nonRealTimeMeta:ver.2.00" xmlns:lib="urn:schemas-professionalDisc:lib:ver.2.00" lastUpdate="2024-12-11T01:15:58Z">
<TargetMaterial umidRef="060A2B340101010501010D431300000030807A0D550606CDDCFE23FFFE2F49EB"/>
<Duration value="216"/>
<LtcChangeTable tcFps="25" halfStep="false">
<LtcChange frameCount="0" value="10262202" status="increment"/>
<LtcChange frameCount="215" value="00352202" status="end"/>
</LtcChangeTable>
<CreationDate value="2024-12-11T01:15:49Z"/>
<TypicalUbit value="0000000000000000"/>
<KeyFrame frameCount="0"/>
<BodyUmidBasicChangeTable>
<BodyUmidBasicChange frameCount="0" value="060A2B340101010501010D4313012C0D667B7A0D550606CEDCFE23FFFE2F49EB" status="start"/>
</BodyUmidBasicChangeTable>
<KlvPacketTable>
<KlvPacket key="060E2B34010101050301020A02000000" frameCount="0" lengthValue="095F5265635374617274" status="spot"/>
</KlvPacketTable>
<VideoFormat>
<VideoRecPort port="DIRECT"/>
<VideoFrame videoCodec="AVC_3840_2160_HP@L51" captureFps="25.00p" formatFps="25p"/>
<VideoLayout pixel="3840" numOfVerticalLine="2160" aspectRatio="16:9"/>
</VideoFormat>
<AudioFormat numOfChannel="4">
<AudioRecPort port="DIRECT" audioCodec="LPCM24" trackDst="CH1"/>
<AudioRecPort port="DIRECT" audioCodec="LPCM24" trackDst="CH2"/>
<AudioRecPort port="OTHERS" audioCodec="LPCM24" trackDst="CH3"/>
<AudioRecPort port="OTHERS" audioCodec="LPCM24" trackDst="CH4"/>
</AudioFormat>
<Device manufacturer="Sony" modelName="PXW-Z90V" serialNo="4012130"> </Device>
<RecordingMode type="normal" cacheRec="false"/>
<AcquisitionRecord>
<Group name="CameraUnitMetadataSet">
<Item name="CaptureGammaEquation" value="nxcam-std"/>
<Item name="CaptureColorPrimaries" value="rec709"/>
<Item name="CodingEquations" value="rec709"/>
</Group>
</AcquisitionRecord>
</NonRealTimeMeta>

 

I'll be sharing some tips to overcome this situation for other users who find this:

 - When you got your corrupted clips detected and selected, transcode them with Shutter Encoder (recommended), Handbrake or similar to any compression you desire (I used Apple ProRes just in case). Then replace the file inside the timeline.

- It doesn't happen on any other cameras apart from this Z90 we own (not happening on GoPro footage for example)

- It may happen at the beginning of clip cuts, or even in the middle of a video suddenly. It also has a bitter taste for faces.

- We also found out version 24.4.1 is the one that has a fair balance of features without the glitching issue.

 

Hope we could help anyone and the Adobe Team notifies us when this 2025 version gets usable for us, as of this moment we are avoiding it despite the features.

 

Votes

Translate

Translate

Report

Report
Community Beginner ,
Jan 09, 2025 Jan 09, 2025

Copy link to clipboard

Copied

I also want to add to this experience. The issues I am experiencing are specifically with .MXF source files from my sony FS7. The glithes seem to appear on from the 2025 release onward, I am currently on 2025.1.0. CC2024 did not have these issues. The glitches appear throughout the editing at random locations, but the glitches are not consistent throughout the editing timeline. Spooling through the timeline at the same location will replay the glitch (from frame memory?), but when jumping through the timeline (or sometimes minimizing/maximizing adobe) will resolve the glitch. It might appear in a different spot next.

The glitches also appear in the Media Encoder exports but they have a different behavior:
1) They ARE reproducable at the same locations, rendering the entire timeline or only a problematic spot through in/out point
2) They appear on CUTS only
3) I have found no export settings (tried all of them which I know off) which changes the behavior.
4) The glitch happens also with different codecs (tried a bunch like prores, H264/HEVC, MXF, uncompressed AVI, etc)
5) The glitch appears in the export preview (within PP, not media encoder) window as well, telling that this glitch is very likely a decoding error
6) Shifting the cut one frame forwards completely fixes the glitch in my example. Is the cut maybe precisely on a keyframe in the sourcefile?)

7) Shifting the cut back to the original location re-introduces the glitch.

Attached is a screenrecording from me scrubbing at the location where a glitch appears while editing. Note that first the frame is loaded from some kind of framememory / cache (where the glitch is persistent), but the frame updates later to the correct one.
https://mega.nz/file/SjQS3ZSa#pSzPVyBeR0jKlGsTetsy_9IN4tU9IVlJKWauIIrOBvg

And here is a piece of the export where the glitch appears on the cut, in a reproducable manner:
https://mega.nz/file/ryBAQZwb#CHG6pKfdijxJ2WHrWzQMzJCNzKxPea_wAMJ9N-izkXA

Lastly, I have created a testproject (including a sourcefile), from which I can reproduce the glitch. I am very curious if other people can reproduce it as well.
https://mega.nz/file/6rAT3JAS#G0NBBpdf2R43hj7tBQmrROEPWnC9jIDrXeY4SEBlAlc

I invested a few hours of my time into trying to reproduce and experiment with this glitchy behavior. It would be very kind of the Adobe team if they can bump this in priority and investigate this behavior. For now I will (like other people) be downgrading tot CC2024.

Votes

Translate

Translate

Report

Report
Community Beginner ,
Jan 09, 2025 Jan 09, 2025

Copy link to clipboard

Copied

LATEST

For me downgrading tot 2024.3 eventually helped, but I also read about a fix for the 2025 version, and that is to disble hardware accelerated decocing in settings -> media. Found it on this reddit thread
Appearantly this is a bug already longer associated with Nvidea hardware accelerated decoding. So people opening my previous project might not be able to reproduce it, because your hardware is different.

Votes

Translate

Translate

Report

Report