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

P: Glitchy Video in Timeline

Community Beginner ,
Jul 20, 2024 Jul 20, 2024

Copy link to clipboard

Copied

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.

Bug Acknowledged
TOPICS
Editing and playback , Performance or Stability

Views

3.1K

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 , Jul 22, 2024 Jul 22, 2024

Hi @eegriff - We have received the files and I can confirm the problems you are experiencing.  In the meantime while we investigate further for a solution, a simple workaround is to go to your Settings > Media > and at the bottom there is a checkbox labeled "Enable Hardware Accelerated Decoding" make sure this box is unchecked then close Premiere Pro and relaunch this should clear the glitches.  Thank you for your help investigating and troubleshooting. 

Votes

Translate

Translate
Adobe Employee , Oct 14, 2024 Oct 14, 2024

Updating the status for this bug report.

Status Needs More Info

Votes

Translate

Translate
Adobe Employee , Oct 23, 2024 Oct 23, 2024

Updating Status

Status Acknowledged

Votes

Translate

Translate
replies 115 Replies 115
115 Comments
New Here ,
Aug 01, 2024 Aug 01, 2024

Copy link to clipboard

Copied

So i tested it out, and it seems the glitches and the slow performance of the XACV files has been fixed in the beta version. Its just that in the beta version, the effects window is completely blank and no effects are showing up. So, this is hardly improving anything.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Aug 01, 2024 Aug 01, 2024

Copy link to clipboard

Copied

Hi @maximiliank75930582 - I am glad that your glitches are not showing up anymore, but apologize for your effects being black.  Can you try going to your menu bar under Window > Workspaces > Reset to Saved Layout.  

If that doesn't help, can you let me know if changing the workspace helps or not.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Aug 01, 2024 Aug 01, 2024

Copy link to clipboard

Copied

Sorry about that, it was a typing error. The version is 560.67. I've corrected my post. Is the other system also running on NVIDIA GPU with the latest driver, or is it a different GPU/driver? Also, thanks for providing the sample media. I tried it & it seems to be working properly. For testing purposes, please try switching the Renderer to Mercury Playback Engine Software Only (File > Project Settings > General) to check if you are still getting the preview glitches. Let us know if it works.

 

Thanks,

Sumeet

Votes

Translate

Translate

Report

Report
Community Beginner ,
Aug 02, 2024 Aug 02, 2024

Copy link to clipboard

Copied

No problem. 
I have diffrents gpu, 3060, 1060. I changed to software only, still that same. 
I was trying this also on another computer.

obraz_2024-08-02_113249322.png

Votes

Translate

Translate

Report

Report
Community Beginner ,
Aug 02, 2024 Aug 02, 2024

Copy link to clipboard

Copied

The effects window is working on our end in the beta version, just to confirm.

Votes

Translate

Translate

Report

Report
Explorer ,
Aug 06, 2024 Aug 06, 2024

Copy link to clipboard

Copied

ppro_glitch.jpg

 

Here is an example of the digital artifacts I'm seeing in Premiere. This was a frame export. Renders do the same thing.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Aug 07, 2024 Aug 07, 2024

Copy link to clipboard

Copied

Hey swrutherford,

I'm sorry you're experiencing this issue. I have branched your reply for troubleshooting.

 

Have you adjusted the clip speed in your project? Please let us know which camera was used to record this footage and share your media properties (Project Panel > Right-click on file > Media File Properties).

 

Please also share your system specifications (OS, OS version, CPU, GPU, RAM). 

 

This post was branched from an older post.

Thanks,

Ishan

Please tag me (@) in your replies so that it notifies me and helps me respond promptly.

Votes

Translate

Translate

Report

Report
Explorer ,
Aug 07, 2024 Aug 07, 2024

Copy link to clipboard

Copied

Thank you for your reply!

 

Here is a link to an example of what is happening: https://www.youtube.com/embed/2OTgNvJX_no

 

Here are the Media File Properties (I have 4 total clips with identical settings - other than length, though all are in the 45 minute to 1 hour range):

 

File Path: D:\JDA 2024\JDA\RED\Clip0014.MXF
Type: MXF
File Size: 20.38 GB
Image Size: 3840 x 2160
Frame Rate: 29.97
Source Audio Format: 48000 Hz - 24-bit - 4 Channels
Project Audio Format: 48000 Hz - 32 bit floating point - 4 Channels
Total Duration: 00;49;47;15
Pixel Aspect Ratio: 1.0
Alpha: None
Color Space: Rec. 709
Color Space Override: Off
Input LUT: None

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 60

===

System Specs:

Device name Yuletide_i9
Processor Intel(R) Core(TM) i9-14900K 3.20 GHz
Installed RAM 128 GB (128 GB usable)
Device ID 04FEE4B2-8980-4A37-BB8A-3CB0F7D58730
Product ID 00330-80032-44482-AA911
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display

===

Windows Version

Edition Windows 11 Pro
Version 23H2
Installed on ‎6/‎15/‎2024
OS build 22631.3958
Experience Windows Feature Experience Pack 1000.22700.1026.0

===

Premiere Pro 24.5.0 (Build 57)

===

Nvidia Studio Driver 560.81 Released 8/6/2024

===

Thank you for your assistance!

Votes

Translate

Translate

Report

Report
Explorer ,
Aug 07, 2024 Aug 07, 2024

Copy link to clipboard

Copied

I thought the GPU info was listed in here, but I think I missed it:

 

NVIDIA System Information report created on: 08/07/2024 18:40:44
System name: YULETIDE_I9

[Display]
DirectX version: 12.0
GPU processor: NVIDIA GeForce RTX 4090
Driver version: 560.81
Driver Type: DCH
Direct3D feature level: 12_1
CUDA Cores: 16384
Resizable BAR Yes
Core clock: 2625 MHz
Memory data rate: 21.00 Gbps
Memory interface: 384-bit
Memory bandwidth: 1.01 TB/s
Total available graphics memory: 89970 MB
Dedicated video memory: 24564 MB GDDR6X
System video memory: 0 MB
Shared system memory: 65406 MB
Video BIOS version: 95.02.3C.40.D1
IRQ: Not used
Bus: PCI Express x16 Gen4
Error Correction Code (ECC): Off
Device Id: 10DE 2684 51041462
Part Number: G139 0332

[Components]

nvui.dll 8.17.15.6081 NVIDIA User Experience Driver Component
nvxdplcy.dll 8.17.15.6081 NVIDIA User Experience Driver Component
nvxdbat.dll 8.17.15.6081 NVIDIA User Experience Driver Component
nvxdapix.dll 8.17.15.6081 NVIDIA User Experience Driver Component
NVCPL.DLL 8.17.15.6081 NVIDIA User Experience Driver Component
nvCplUIR.dll 8.1.940.0 NVIDIA Control Panel
nvCplUI.exe 8.1.940.0 NVIDIA Control Panel
nvWSSR.dll 32.0.15.6081 NVIDIA Workstation Server
nvWSS.dll 32.0.15.6081 NVIDIA Workstation Server
nvViTvSR.dll 32.0.15.6081 NVIDIA Video Server
nvViTvS.dll 32.0.15.6081 NVIDIA Video Server
nvLicensingS.dll 6.14.15.6081 NVIDIA Licensing Server
nvDevToolSR.dll 32.0.15.6081 NVIDIA Licensing Server
nvDevToolS.dll 32.0.15.6081 NVIDIA 3D Settings Server
nvDispSR.dll 32.0.15.6081 NVIDIA Display Server
nvDispS.dll 32.0.15.6081 NVIDIA Display Server
PhysX 09.23.1019 NVIDIA PhysX
NVCUDA64.DLL 32.0.15.6081 NVIDIA CUDA 12.6.41 driver
nvGameSR.dll 32.0.15.6081 NVIDIA 3D Settings Server
nvGameS.dll 32.0.15.6081 NVIDIA 3D Settings Server

Votes

Translate

Translate

Report

Report
New Here ,
Aug 07, 2024 Aug 07, 2024

Copy link to clipboard

Copied

Thank you jamie, that did it. After some time with the beta, I havent found anything that didnt work, except: AE Dynamic Linking seems to be deactivated in the beta, do you have some info on that?

Votes

Translate

Translate

Report

Report
Community Expert ,
Aug 08, 2024 Aug 08, 2024

Copy link to clipboard

Copied

Hi,

 

For a project we have some long files that glitch on random frames in Premiere.

I can't share the file directly here but see the screenshot for reference. It feels like a bug related to decoding the long gop frames. This glitch is not present on a Mac or on other software like Resolve and Catalyst Browse.

Shebbe_0-1723114397168.pngShebbe_1-1723114410805.png

 

Please look at this asap, we currently have to resort to transcoding it all to be able to work on Windows.

Our Win systems are equipped with 3090/3090Ti/4090 not all machines run the same driver version but bug was noticed on all. Premiere 24.5 build 57. We also tested Software Playback but the issue remained.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Aug 08, 2024 Aug 08, 2024

Copy link to clipboard

Copied

Hi @maximiliank75930582 - Can you please make sure you have the After Effects beta installed.  Let us know if that helps your issue.  Thank you for the update,  I'm glad things are working for you!

Votes

Translate

Translate

Report

Report
Community Expert ,
Aug 08, 2024 Aug 08, 2024

Copy link to clipboard

Copied

Didn't realize there were already 2 threads about this issue, I posted my own.

Please check it for details, but this is quite a glaring issue that needs a hot fix asap. Our team is considering downgrading but this feels sketchy to do with the amount of ongoing projects.

Votes

Translate

Translate

Report

Report
LEGEND ,
Aug 08, 2024 Aug 08, 2024

Copy link to clipboard

Copied

They've really been having some issues with the XAVC stuff recently. Supposedly, the public beta has better performance with this.

 

They just dropped the first 25.x public beta build a couple days ago. Have you tried creating a project in that, and seeing if this works better? If so, PLEASE post back on your results whatever they are!

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Aug 08, 2024 Aug 08, 2024

Copy link to clipboard

Copied

Hi @Shebbe,

Thanks for posting this bug. It might be related to the new driver. Does this datamosh appear when scrubbing? If that is your problem, I have heard that 560.67 is not working. You may want to install a previously working driver.

 

After, try deleting all media cache first from the Reset Options dialog box or manually, and then go to Software Only mode.

 

Do you still see this issue? Let the community know.

 

Thanks,

Kevin

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio
Status Needs More Info

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Aug 09, 2024 Aug 09, 2024

Copy link to clipboard

Copied

Hi @Shebbe - Here are a few things you can try.  Do you have any plugins installed or sony catalayst?  

Please hold down "SHIFT" while launching Premiere and check the boxes 

"Reset Plugin Cache" 

"Disable third-party plugins (one time only)" 

"Clear media cache files" 

 

let us know if that helps your issue.

Votes

Translate

Translate

Report

Report
Community Expert ,
Aug 09, 2024 Aug 09, 2024

Copy link to clipboard

Copied

@Kevin-Monahan I believe mine was on 534.xx and the others arond 550 or something. It happens with playback/rendering timeline/scrubbing. Once visible it remains on that frame.

 

@jamieclarke 

I do have Sony Catalyst Browse but not the other machine it was tested on doesn't. And we do have a lot of plugins for Premiere. None of them were present in the project though. I'll try your steps after the weekend when I'm back at the office.

Hope to report back soon.

Votes

Translate

Translate

Report

Report
Community Expert ,
Aug 12, 2024 Aug 12, 2024

Copy link to clipboard

Copied

So my particular machine is on driver 537.58

Can't remember if it's studio or game ready.

 

But I'm really concerned now since we're moving into online. The problem is also present in After Effects 24.5 so I can't composite the source material. I've also graded the shots in Resolve and there are no issues at all.

I thought maybe the latest AE Beta v25.0 can save me. There the playback/scrubbing seems about 2-3x slower but haven't seen the glitch yet. The problem however is v25 project files are not compatible with v24.x.

 

Please whatever the problem is, issue a hotfix for v24.x.

 

Shebbe_0-1723472719611.png

 

Votes

Translate

Translate

Report

Report
Explorer ,
Aug 14, 2024 Aug 14, 2024

Copy link to clipboard

Copied

@Ishan Y - I finally was able to get the source files flipped to an .mov (there was another issue where AME wouldn't accept the .mxf files but it magically started working...) and then my renders were clean. It took about a week to find the right codec to keep it from artifacting, but I finally got it. 

 

There has to be something with how Windows 11 & NVIDIA handle H.264s and MXFs. I haven't experienced this in 20+ years of working with Premiere/After Effects/AME and it consistently shows up using these file types on Windows 11.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Aug 15, 2024 Aug 15, 2024

Copy link to clipboard

Copied

Hi! Sorry, I missed your previous replies. I'm glad that you were able to finish your project. This issue shouldn't be happening, though. Have you added any speed adjustments or reversed the clip speed in your project? Please also let us know which camera was used to record this footage. I see Sony mentioned in the media file properties. Was it an FX3? 

Votes

Translate

Translate

Report

Report
Explorer ,
Aug 19, 2024 Aug 19, 2024

Copy link to clipboard

Copied

No speed ramps/retiming was used. Straight footage from my PXW-X70 camera. I had a Windows 10 machine for years and it worked great with no issues. I still haven't gotten the .mxf to work as expected on Windows 11 yet.

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Aug 20, 2024 Aug 20, 2024

Copy link to clipboard

Copied

Could you share a sample source file and project through a personal message so we can replicate the issue? Also, let us know if you're using any third-party plugins, such as Sony Catalyst Prepare. I'll try to get to the bottom of this so users don't experience this issue again. 

Votes

Translate

Translate

Report

Report
Community Beginner ,
Aug 21, 2024 Aug 21, 2024

Copy link to clipboard

Copied

Unfortunately, I have still the same problem (in new beta version too). I didn't notice any alerts about "Frame substitution..." during my few hours of work, that's true, but I still have a problem with pixalation. Both in editing (the screen is attached)Výstřižek.PNG

and in exporting (demonstration here: https://drive.google.com/file/d/15UluqEDoFLNXVXbPpAkeF3brI6kYHgyW/view?usp=sharing)

I don't know what I will do. I have i big project to cut now but it's unthinkable in this sutuation. 

Votes

Translate

Translate

Report

Report
Adobe Employee ,
Aug 21, 2024 Aug 21, 2024

Copy link to clipboard

Copied

Hi @Radim37046208zysv - We are still investigating this issue.  Can you check the pinned post for workaround.

Votes

Translate

Translate

Report

Report
New Here ,
Aug 21, 2024 Aug 21, 2024

Copy link to clipboard

Copied

the MXF problem isn't solved using the Beta Version I installed today. Demaged frames are still there.
When the project was created, I had no problem like this one. It happens since the last 2 or 3 updates.
Please solve it fast. All my projects with MXF footage are unusable.

Sorry for my bad english!

Dateipfad: D:\...\Clip0016.MXF
Typ: MXF
Dateigröße: 2,25 GB
Bildgröße: 3840 x 2160
Framerate: 25,00
Audioformat der Quelle: 48000 Hz - 24 Bit - 4 Kanäle
Audioformat des Projekts: 48000 Hz - 32-Bit-Floating-Point - 4 Kanäle
Gesamtdauer: 00:03:08:16
Pixel-Seitenverhältnis: 1,0
Alpha: Keine
Farbraum: 1-18-1
Farbraum überschreiben: Aus
Eingabe-LUT: Keine

MXF-Dateiinformationen:
Wrapper-Typ: MXF OP1a (Typ: SingleItem SinglePackage MultiTrack Stream Internal)
Datei erzeugt von: Sony, Mem (2.00)
Bitstream-Format: Sony
H.264/MPEG-4 AVC Long GOP High Profile 4:2:0 Unconstrained Coding
Bitstream-Format: Sony
Klasse 100

Camera: SONY pxw-Z90

Votes

Translate

Translate

Report

Report