Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Premiere Pro lagging with H.264

  • Premiere Pro lagging with H.264

    Posted by James Agro on March 24, 2017 at 10:50 am

    Hello everyone, I’ve found a problem, in which Premiere Pro (preview) lags and skips around when attempting to edit H.264 directly, and I was told to just re-encode to something like utvideo, which works, but I’m working with around 100GB of H.264, and re-encoding this is going to take many times as much space and time. So, something that I’ve noticed is that Aftereffects seems to preview the video fine, however, Premiere Pro seems to lag, and not like the files at all, unless they are re-encoded, then they work flawlessly.
    My system specs are:
    AMD Ryzen 7 1800x @ 3.8GHz,
    32GB DDR4 @ 2113MHz
    GTX 1080 GPU

    Which should be fine for editing, correct? So, I’m not quite sure if this can be solved, as i previously edited H.264 directly with my i7 system, which I no-longer have.
    Any ideas or suggestions would be greatly appreciated.

    Edit: I have tried enabling/disabling CUDA and yes, PP and AE both have access to 28GB’s of system memory. Also, CPU utilization is extremely low >2%. I’m working with 20Mbps H.264 in 1080P.

    Sunderland Green replied 8 years, 6 months ago 8 Members · 21 Replies
  • 21 Replies
  • Jud Archer

    March 24, 2017 at 11:53 am

    James,

    The advice you were given is the correct answer. H.264 is an extremely processor intensive codec and is not generally considered good for editing. Basically it is so compressed that your computer’s cpu is having to decode it on the fly, which is a big burden. Choose a DNX or ProRes variety proxy file.

    The latest version of Premier will automatically convert to a proxy on import if you set it up that way. Have you experimented with this? If your computer has trouble playing the DNX or ProRes then there are bigger problems going on. Perhaps drive speed?

    Good luck.

    Jud Archer
    Apple / Adobe Systems

  • James Agro

    March 24, 2017 at 3:56 pm

    Thanks for your responses, However, I used to run an i7 4790, and that ran this same type of footage perfectly. But since I’ve got my new CPU (Ryzen 7 1800x 8c/16t) it is lagging. Does anyone think the issue could be to do with this?

  • James Agro

    March 24, 2017 at 3:59 pm

    Also, I forgot to include, that I also get a green (thing???) like this at the 00:00:00:0/01 in premiere.
    https://i.gyazo.com/3d2b289c5a7a0346d17c216508efbde7.png

    Also, in the Project box

    https://i.gyazo.com/7bf0a1a41bc62582af84aae3ca8a36a4.png

    This file is only 1.8GB large.

  • Jon Doughtie

    March 24, 2017 at 8:13 pm

    One things that has not yet been mentioned is how and where you are storing your video. Where is your footage, and what is the connection type to the system? Internal drive, External? How connected? Please don’t say your footage is on the C drive.

    System:
    Dell Precision T7600 (x2)
    Win 7 64-bit
    32GB RAM
    Adobe CC 2015.02 (as of 6/2016)
    256GB SSD system drive
    4 internal media drives RAID 5
    Typically cutting short form from HD MP4 and P2 MXF.

  • James Agro

    March 24, 2017 at 10:10 pm

    Well, I’ve tried multiple locations, including SSD (C:\) WD Blue (HDD) and a RAM disk, neither of which changed the result, also all internal.

  • Chris Borjis

    March 24, 2017 at 11:51 pm

    I have to second the thought that you really shouldn’t have to transcode h.264
    I haven’t had to transcode anything since going from fcp 7 to premiere cs 5.5
    The only footage that ever slows me down is Red4k these days.

    I have an early 2009 mac pro with raid storage, 32gb of ram and
    an old GTX 670 and CC 2015.2. Thing cuts h.264 like a hot knife through butter.

    Have you tried lowering the program window resolution?

    Maybe do a google search of premiere cc editing with the new Ryzen cpu?

  • James Agro

    March 25, 2017 at 10:43 am

    Well, Ryzen is a brand new Architecture from AMD, It’s an 8 core 16 thread CPU, It does outperform the $1000 Intel CPU often. It was designed for productivity, and reviewers show Premiere Pro benchmarks, in which it outperforms or matches the i7 5960x 8 core 16 thread CPU, which can be seen here: https://youtu.be/7rT92-qopok?t=168 .
    I’m still a bit stumped on this whole thing, since I doubt it’s anything to do with the CPU at all anyways. It could be, but I think it’s some kind of software bug.

    Thanks for the responses.

    Some contents or functionalities here are not available due to your cookie preferences!

    This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

  • James Agro

    March 25, 2017 at 11:39 am

    So, after long days of trying to solve this, I found it was an issue with the output of the recording software I used (OBS). For some reason, OBS .mov’s and Premiere don’t play well. However, when transcoded to ANY other file container, work perfectly. Not just raw codecs, but .mp4, .mkv, etc. Thank you all for the help, and sorry for the burden of false flags.

  • Jon Doughtie

    March 27, 2017 at 6:26 pm

    If that OBS you mentioned created variable frame rate videos, that is indeed the source of grief. You’ll always want to transcode anything variable frame rate (like anything recorded on iPhones with the native app) to a codec with a fixed frame rate.

    System:
    Dell Precision T7600 (x2)
    Win 7 64-bit
    32GB RAM
    Adobe CC 2015.02 (as of 6/2016)
    256GB SSD system drive
    4 internal media drives RAID 5
    Typically cutting short form from HD MP4 and P2 MXF.

  • Chris Borjis

    March 27, 2017 at 8:21 pm

    [Dave LaRonde] “Yeah, I’ve never even heard of a Ryzen CPU. Since you mentioned that this started when started running it, I’ve been wondering about that.

    It may be cheap (don’t know), but I don’t think it’s great for Adobe applications.”

    It reminded me way back in the days when I was a pc tech, it was either the AMD K5 or K6 cpu
    could not run the then current version of photoshop.

    Good to know AMD has put that in the past.

Page 1 of 3

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy