Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro 4K Playback – Is my system to weak?

  • 4K Playback – Is my system to weak?

    Posted by Bernd Hauser on May 4, 2017 at 1:33 am

    Hello dear Community

    I am having big troubles running 4k files – SPEED UP BY 400% or more – in Premiere Pro CC 2017.
    4K Files: .MOV H264 MPEG 4 AVC, 23.976 fps
    The sequence settings are matching the files: Editing Mode: DNxHR 4K

    No filter or effects.
    CUDA or OpenCL makes no difference.
    Full, 1/2, 1/4 etc. Playback: no difference
    61 GB RAM available for Premiere Pro

    Mac Pro (2009)
    2 x 3.33 GHz 6-Core Intel Xeon
    64 GB DDR3
    GeForce 980 4GB
    Internal SSD

    Same project is running on a Windows 4 Core 3.6 GHz, 32 GB, GeForce 970 without any problems.

    Isn’t this a very powerful system, and shouldn’t the files run smoothly?
    Or do i get something wrong?

    Thank you very much for your opinion!

    Vince Becquiot replied 8 years, 12 months ago 6 Members · 6 Replies
  • 6 Replies
  • Shane Ross

    May 4, 2017 at 2:27 am

    What hard drive is this footage stored on? The SSD?

    H.264 MPEG-4…isn’t DNxHR. Those are two different codecs, so your sequence settings and clip settings don’t match. Not that it matters, just saying they are different. H.264 takes a bit to decode on the fly.

    Perhaps the driver for the GPU is more up to date on the Windows side?

    Shane
    Little Frog Post
    Read my blog, Little Frog in High Def

  • Tero Ahlfors

    May 4, 2017 at 7:22 am

    [Bernd Hauser] “Isn’t this a very powerful system”

    Not really. You should try transcoding the H264 files to DNxHR or Prores.

  • Edward Laws

    May 4, 2017 at 7:35 am

    Agree about transcoding to ProRes or DNxHD and making sure your sequence settings match the footage.

    Try doing a disk speed test perhaps, Blackmagic have free utility I think.

    You might want a RAID0 on two drives or at least have a separate SSD for footage and one for your OS.

  • Al Bergstein

    May 6, 2017 at 4:43 pm

    That is a very old machine by today’s standards. I have an iMac from 2014 and while it runs 2k footage great, it chokes on 4k. I like the idea of transcoding. That makes sense. I’ll try it and see if it helps Probably time for a computer upgrade but I’ll start with SSD drives in the Raid bay too.

    Al

  • Bernd Hauser

    May 15, 2017 at 5:51 pm

    Hey Everyone

    Thanks for taking time to answer.
    After i took your suggestions into consideration i can report the following:
    – Working from SSD. So that shouldn’t be the problem
    – GPU Drivers are up to date
    – Transcoding to ProRes and edit those files works fine. BUT: The files are 10 times the size then the original H264 MPEG. The files come from a DJI Mavic Pro. So the quality is already – lets say borderline, and i dont want to risk even more lost due to compression.

    I recently bought this 12 core 3.22 GH because my Macbook Pro (2,8 GHz Quad-Core Intel Core i7 Prozessor) couldn’t handle the 4K files.

    I understand that the 12 core 3.22 GH is a very old machine by today’s standards.
    But it should be still a very powerful machine, or not?
    I dont understand why a Windows 4 Core 3.6 GHz, 32 GB should bring the performance and a 12 core 3.33 GH doesn’t.
    Is it possible, that the performance of one core is more important than the sum of all cores multiplied by the performance of each core?

    Thanks for your answers
    B

    Power

  • Vince Becquiot

    May 20, 2017 at 2:54 am

    You’d be surprised how quickly CPU and as important, everything around them become obsolete.

    Here are some benchmarks to give you an idea: https://browser.primatelabs.com/mac-benchmarks.

    You can transcode to a lower quality format to edit and replace at render time.

    Vince Becquiot

    Indigo Live | Kaptis Media

    San Francisco Bay Area

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