Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro GoPro Hero 6 H.265 (HEVC) Choppy Playback in Premiere Pro

  • Carlen Cyphers

    March 9, 2018 at 8:11 pm

    Great thanks! Very true that storage is cheap now a days…I won’t worry about it.

  • Yair Bartal

    March 10, 2018 at 3:16 pm

    I wonder why proxies aren’t appropriate in this instance.
    Could you elaborate?

  • Greg Janza

    March 10, 2018 at 4:04 pm

    The purpose of proxies is to make it possible to smoothly edit high quality (i.e., 4k) footage on a computer that doesn’t have enough power to easily work with the originals. The proxy workflow allows you to build your video with the proxies but to do your final mastering with the high quality original files.

    In situations involving h264 or h265 master files, there’s no need to go back to those originating files after transcoding them to an edit friendly codec so therefore the proxy workflow isn’t necessary.

    Windows 10 Pro
    i7-5820k CPU
    Nvidia GeForce GTX 970
    Adobe CC 2018
    Renders/cache: Samsung SSD 950 Pro x2 in Raid 0
    Media: Samsung SSD 960 PRO PCIe NVMe M.2 2280
    Media: OWC Thunderbay 4 x 2 Raid 0 mirrored with FreeFileSync

  • Ole Kristiansen

    March 10, 2018 at 4:11 pm

    Do not know if changes have been made to GoPro Hero 6 H.265 and Gopro Studio!

    Many times, when I shoot with my GoPro Hero 4 Black – I take the footage into GoPro Studio – starts the first trim of the recordings – remove fish eyes and saves the recordings like Cineform intermediate .avi or .mov!

  • Yair Bartal

    March 10, 2018 at 4:15 pm

    That’s fine, but why transcode them to an edit friendly codec in the first place and not use proxies instead?

  • Greg Janza

    March 10, 2018 at 4:28 pm

    H264 and H265 files are CPU intensive and therefore I would advocate to always transcode them to pro-res or DNxHD before editing. It’s a one step process with no need to round trip as with proxies.

    Windows 10 Pro
    i7-5820k CPU
    Nvidia GeForce GTX 970
    Adobe CC 2018
    Renders/cache: Samsung SSD 950 Pro x2 in Raid 0
    Media: Samsung SSD 960 PRO PCIe NVMe M.2 2280
    Media: OWC Thunderbay 4 x 2 Raid 0 mirrored with FreeFileSync

  • Yair Bartal

    March 10, 2018 at 4:55 pm

    Well, if one has a slow computer, proxies would still be lighter to edit than high quality files, and at the end one just exports with the originals. I think it’s a better workflow, but that’s me.

  • Ole Kristiansen

    March 10, 2018 at 5:09 pm

    It’s probably a matter of defining “better workflow”!

    It also depends on what the recordings will ultimately be used for!

    Can you tell why you think proxies are a better workflow?

  • Yair Bartal

    March 10, 2018 at 5:18 pm

    Well, I’ve just made a test on a 20 sec UHD H264 clip using PP 2017.1.2:

    – Transcoding it to a high quality file – DNxHR HQX UHD resulted in a 728 mbs file.
    – Making a proxy file – Cineform 720P resulted in 69 mbs file.

    It seems to me that a slow computer can cope better with the proxies workflow.

    Having said that, I’ve been told that proxies are not reliable for color correction, so… one has to decide.

  • Ole Kristiansen

    March 10, 2018 at 5:28 pm

    Yes, with your “better workflow” you need to make color correction with the original H.265 before export!

    “Transcoding it to a high quality file – DNxHR HQX UHD resulted in a 728 mbs file.”

    Why do you want to transcode to DNxHR HQX UHD, with GoPro 6, which is recorded with 78Mbit for Protune? Is it not overkill?

Page 2 of 4

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