Thread Ripper Stutter Playback

[jayk02]

Hello everyone.  This is my first post so I hope I do it correctly.  I've just finished building system that I HOPED would give me many years of smooth editing.  Sadly I am not having that kind of luck.  Two problems of note:

Welcome screen sits upon launch for up to 20 -30 seconds before plug ins load.  Once they start, the program is up 2 seconds later.

As noted in the title playback is very stuttering.  Regardless of workspace, or resolution (turning it down to 1/4 still results in jittery playback)

Here are the specs on my system and file.. Any help in this process would be wonderful:

Computer and Premiere Data Sheet:

This is a newly built system.  Bacially, Windows 10, drivers, and Premiere.

Premiere Pro CC 2017 11.1.2

Processor  AMD Ryzen Threadripper 1950X 16-Core Processor, 3400 Mhz, 16 Core(s), 32 Logical Processor(s)

BIOS Mode  UEFI

Installed Physical Memory (RAM)  64.0 GB

Name  NVIDIA GeForce GTX 1080 Ti

C drvie is a 500gb 980 Pro onboard SSD (1700 MB/s write / 2555 MB/s Read)

D drvie (Cache drive) is the same. (Same Speed as C drive)

Project is on a 4 drive RAID consisting of SSDs. 

(Write 1269 MB/s / Read 1436 MB/s

File being played back:

Type: MXF

File Size: 12.71 GB

Image Size: 1920 x 1080

Frame Rate: 59.94

Source Audio Format: 48000 Hz - 24 bit - 4 channels

Project Audio Format: 48000 Hz - 32 bit floating point - 4 channels

Total Duration: 00;35;34;38

Pixel Aspect Ratio: 1.0

MXF File details:

Wrapper type: MXF OP1a (type: SingleItem SinglePackage MultiTrack Stream Internal)

File generated by: Sony, Mem  (2.00)

AVC Long GOP High 4:2:2 Profile 10-bit Unconstrained Coding

Bitstream Format: Sony

Class 50

During playback 30% of the CPU is being used.

Aprox 8 MB/s on the hard drvie.

I will be very grateful for any help I can get reaching the editing promised land of smooth playback!

Jay

[excited_Genie16B8]

I recommend the following for all H.264 media.  Choose one of the included Cineform presets.

Work offline using proxy media |

[jayk02]

Thank you Jim.. I will certainly look into that.  However I want to make sure I understand something, are you saying that no system is able to play this type of file smoothly?  Does that mean everyone else reading this is also having the same problem?

My "gut" tells me this may be a little deeper than the file type, so I will try the proxies and some others and get back to everyone on the results.

Jay

PS: I hope you are right?

[excited_Genie16B8]

I'm saying that Premiere Pro doesn't handle H.264 as well as it handles formats like Cineform, DNx and ProRes, all of which it handles as easily as DV.

[MyerPj]

I'm wondering about this:

jayk02  wrote

Two problems of note:

Welcome screen sits upon launch for up to 20 -30 seconds before plug ins load.  Once they start, the program is up 2 seconds later.

This seems to have happened after 2017.0.2 which is version on my previous computer, and the new one started already with the .1 upgrade. The screen that pops-up when the program is started - in v.0.2 the program loading items start scrolling by almost immediately. On my new computer (with much faster m2 drives) it takes 9 seconds before the items start scrolling. Quite disappointing really... is this just something adobe changed or could it be only on mine and to OP's computer?

[Bill Gehrke]

I suggest that you test your system with my Premiere Pro BenchMark (PPBM) which will tell us how well your CPU, GPU and storage system are operating.  Please download and run the project, it is self instructing and then Submit the results. I will get back to you.

[jayk02]

This is wonderful.  Downloading now, and will post results.

Thank you Bill.

[jayk02]

Results as follows:

Disk I/O Time = 38 seconds

Write Rate is 976.11 MB/second

Time to encode H.264 timeline = 54 seconds

Your system has a MPE gain of 143/14=102

[Bill Gehrke]

WOW! I am impressed with these first Threadripper scores are phenomenal.  That 143 seconds CPU intensive score is in second place on my CPU intensive scores, better than dual 12 core Xeons.  We will have to hope someone else can duplicate these scores to make sure it can be substantiated.  I want one!

What does your Task Manager/Startup tab look like I will comeback a little later and post my windows 10.

[jayk02]

I did not know it was that big a deal!  If it helps here is the screen cap of the results. 

But back to the matter at hand.  I am using a sony X70 and their HD 50Mbits Codec, no matter what it studders on timeline when played.  I can live with it if I have too.  Red 4k footage is no problem at all.  Go Figure.

[Bill Gehrke]

Your media is evidently is this:

XAVC Long : XAVC-L 50 mode

- VBR, maximum 50Mbps, MPEG-4 H.264/AVC

- LPCM 24-bit, 48kHz, 2 channels

I do not have a sample of this LongGOP media to test but it is much more CPU intensive

so any even minor interruption of CPU processing lost frames.  Here is my Startup on my Windows 10 Desktop:

 

Here are the processes going on before I start Premiere Pro video editing only desktop.

[jayk02]

Let me go through my process list and see what's going on.  I am grateful for all the help

Jay

[dutchy_on_a_bike]

I own a very similar system. 1950x, 64GB ram, Gtx 1080ti, m.2 boot drive. My fs5 .mxf files

shot at either 4k or even HD, playback choppy. Very disappointed. My old Mac Pro

5,1 with a Gtx 980 plays smoother. Transcoding to cineform has fixed the problem. It's a problem with premiere because in VLC playback is fine. Everything else is crazy fast but the SINGLE most important thing for editing, just sucks. Too bad we can't ProRes

on windows :-). Cheers. Mark.

[dutchy_on_a_bike]

I ran the benchmark test. Fore some reason I couldn't upload the results, the file "statistics PPBM12.vbs", I got stuck at that point. Test 1) 71secs Test2) 15secs Test 3) 48secs. That's using an m.2 for a boot drive, another m.2 for export, and an SSD for scratch. It is the long GOP .mxf that is the problem. Intra-frame .mxf is fine.

[GregEdits]

I had the same issue and I found a solution that worked for me.  I can now play h.264 footage, xavc-I, and 6K R3d footage with easy with no stutter. This worked for me.  I had to disable HPET with "false"

After I did this my whole system was stable running Premiere

[/cmd admin

to enable HPET - bcdedit /set useplatformclock true

to disable HPET - bcdedit /set useplatformclock false

bcdedit /deletevalue useplatformclock

[dutchy_on_a_bike]

Sorry this is my first PC in 10 years, could you please give me a "Dummies Guide" to that explanation 🙂

[GregEdits]

Likewise! A little bit of a learning curve but nothing insane.

You're going to want to run the "Command Prompt" as an Administrator.  Do this by typing in Command Prompt in the "Type here to search" box on the desktop.  Before you open it RIGHT CLICK it and press "Run As Administrator"

copy and paste this line when it opens up:

bcdedit /set useplatformclock false

Press "Enter"

It'll say "The operation completed successfully"

nothing else will happen.

Exit out and reboot your system and give Premiere a try.  This worked for me and now I have no stutters in the app.  Lifesaver.  I hope this does the same for you! The Threadripper is a BEAST

[matthewg45924989]

FIXED!!!

With all the research I had been doing it seemed the audio hardware was the issue. I updated my audio drivers and also installed ASIO drivers base on my motherboard, and it has seemed to fix the problem.

Let me know if this works for anyone else.

[billh913a]

I was having the same issue with stuttering of video playback in CS6.  My new build (1 week old) was almost identical to yours. I began my research today beginning with your question.  In reviewing the threads I tried the bench mark tests suggested by Bill G and in doing so found that my CUDA card/settings were not being recognized by Premiere so I downloaded the NVIDIA Cuda Toolkit that installed some drivers.  I then followed a tip from youtube where the "cuda_supported_cards.txt" file needed editing to include "GeForce GTX 1080 Ti" . Once I restarted my system and launched Premiere it recognized my card and allowed me to select Mercury Playback Engine GPU Acceleration.  The stuttering has stopped.  Bill H.

[MyerPj]

That .txt file has not been in use now for several versions / years - at least as far back as cc2014, but it was indeed used on your cs6 in 2012. Here's a relevant post:

Congratulations Adobe on GPU identification in 8.1.0.81

[matthewg45924989]

I feel like this problem is never-ending. Everytime I think I have it fixed I open a new project and it starts all over again. Adobe needs to figure this out because it's not a problem I'm having with any other program. This is an Adobe problem.

[IAH Digital]

SWITCH TO DAVINCI RESOLVE15. Its ultra powerful and my TR 1950X LOVES it. The problem is with Adobe and old code/optimization. Why are your apps single threaded still? RESOLVE is super multithreaded and used a ton of your GPU. MAKE THE SWITCH!

[excited_Genie16B8]

Why are your apps single threaded still?

Premiere Pro has been properly multi-threaded for quite a while now.  The superior playback performance on Resolve is because it uses the GPU for decoding, whereas Adobe is still using the CPU exclusively.

[R Neil Haugen]

One thing I've encountered with a few Resolve users ... especially one who posted here a while back, on playback issues. He touted Resolve's 'optimized media' option, saying that PrPro should have that rather than making people make proxies.

"Optimized media" is Resolve's way of talking about ... making proxies. (Like they call masks "power windows" ... sheesh.) The 'optimized media' is simply a proxy file. He told me I didn't know what I'm talking about, but hey ... read the manual, you know? And Resolve 'comes' with a rather glorious manual, and I've read the full thing. Adobe finally has a pdf ... if you can find it ... that is newly made and better than the older ones, but that Resolve manual is a thing of beauty!

On my Win10 machine, i7/6-cores, 64GB of RAM with a 1060/6-GB GPU ... playback in Resolve and PrPro are nearly identical with long-GOP media. Both original media & proxies.

Working much of a project, I'll tend to get a bit more lag for effects & such in Resolve ... but then, I've not tried 15 yet.

Neil

[excited_Genie16B8]

Resolve 'comes' with a rather glorious manual, and I've read the full thing.

God bless you, man.  I'm only a couple hundred pages into that 1400 page document.