Announcement: Our new CyberLink Feedback Forum has arrived! Please transfer to our new forum to provide your feedback or to start a new discussion. The content on this CyberLink Community forum is now read only, but will continue to be available as a user resource. Thanks!
CyberLink Community Forum
where the experts meet
| Advanced Search >
PDR15 Performance and 4K Editing
AlS
Senior Member Location: South Africa Joined: Sep 23, 2014 18:07 Messages: 290 Offline
[Post New]
There have been several concerns expressed about PDR performance and disappointment with it's advertised 4k editing support and the impact improved GPU support may have. I've done some research and think we may have unfair expectations.

There is little info out there on the effect of using GPUs for editing vs gaming. In an attempt to better understand how NLEs work I looked at professional software. Professional video editors have had more time with 4k cameras and editing than we consumers. It's a different market to PDR as a consumer level product - but I was interested in their performance and technology and how GPUs affected performance for editing and rendering. Again - no benchmarks. The results suprised me. THIS IS NOT A TECHINCAL EVALUATION.

There is not a lot of info out there on PDR performance. This is all based on the info I've found. I use "4k" to refer to 4k and UHD. I also use the term "NLE" to refer to video editing software and "PDR" for Power Director.

HD pushed the limits for most NLEs and consumer level PC hardware. Anything above HD and all NLEs recommend expensive professional workstations. Software has it's performance limitations. Adobe Premiere and Edius have been around for decades and both are used by the Pros. Both were CPU based for many years and have only recently added GPU support.

PDR was ahead of most when they added Intel Quick Sync (Intel HD Graphics) support. Edius (considered the fastest NLE) only added Quick Sync support in their latest Ver 8 and claim 5X faster render for H.264.

Adobe added GPU support by "The GPU-accelerated Adobe Mercury Playback Engine, co-developed by Adobe and NVIDIA, leverages NVIDIA GPUs and the NVIDIA® CUDA® Parallel Computing Platform to deliver interactive, real-time editing and up to 24x¹ faster performance on final rendered exports."4k editing is a challenge on most NLEs. Even with expensive hardware and pro software there are limitations when you start adding multiple 4k layers, effects, etc.. Adobe test mentioned above was done with a Xeon (8 cores) at $2k and dual Quadro M6000 GPUs at $5k each! http://www.nvidia.com/object/adobe-premiere-pro-cc.html#. That's a $15k+ workstation for realtime 4k editing!! One test shows two Xeons with two Quadros are even better!

Video codecs and software edit effects may or may not be optomised for GPU and can affect Edit/Render performance.So, in summary, the claim that PDR supports 4k editing is putting unreasonable expectations on the software as a consumer grade product. Professional software supporting 4k also struggles with 4k on the timeline.So - how do others handle 4k editing without spending $15-20k on a professional PC?

The biggest challenge is realtime editing/playback on the timeline. There are other solutions and work-arounds being used - and could be easily added to PDR to solve the 4k challaenge.

Proxy Editing Several programs now support "Proxy Editing" internally. Proxy files are created via transcoding as temp files within the program at a lower resolution and used on the timeline for edit. Ie if you are editing 4k you might use a 720p lower bitrate proxy format. Advantage - fast smooth realtime edit as the program is editing 720p and not 4k/UHD. If your consumer PC can edit 720p - it can edit 4k! Once editing is finished the program substitutes the 720p files in the timeline for the original 4k files to render. Disadvantage - it takes a little time to wait for proxy files to be created before you can start editing and timeline preview is limited to 720p proxy file resolution. If you have a second 4k monitor you cannot preview your edit effects in 4k resolution - may be a problem for the Pros - but most are happy with a 720p preview. It is integraded in the edit software. PDR15 could easily add a transcode option to a user specified resolution before you start editing as one solution for 4k editing on a consumer PC similar to shadow file creation.

Here's an example of Prroxy Editing on Adobe Premiere Pro CC. https://helpx.adobe.com/premiere-pro/how-to/proxy-media.html and here on a lowly laptop Edit 4K video on the 12" MacBook with Final Cut Pro X. It's not rocket science but it works. Note that's it's integrated into the software.



Use Edit Friendly Codecs - Simply put, the formats used by our cameras like H.264 are great for compressing video into small file sizes with minimal quality loss to fit on an SD card. Each compressed frame is not a full image but only records a small partial image which is basically only the differences between frames. Edit software has do a lot of work to do in order to to get frame accurate images. "Edit Friendly" codecs produce files that are too large for most camera storage. They are also known as "Intermediate codecs" as they are not commonly used for output of a finished project.

One of the reasons claims "EDIUS Pro 8 is the fastest and most versatile real-time editing software — period" is that they have always had a proprietary codec for editing called GV HQ/HQX and Edius 8 automatically generates intermediate files in this codec for editing nad render which decompresses your MP4 files on your PC. The difference between transcoding into a 720p Proxy and an Intermediate Codec is thet the proxy is smaller and lower quality but the Intermediate Codecs retain the 4k quality and the files are much larger. You can get realtime editing with a high quality preview for more accurate editing. Every frame is now a keyframe so editing is much faster and things like colour correction more accurate.

These well known professional intermediate codecs were licensed and expensive so not available to us. Now Edius GV HQ/HQX, Cineform, Apple ProRes, Avid DNxHD, and others are now free to downlod and use. If you have a GoPro and have used GoPro Studio you will see that it transcodes your camera files into Cineform AVI files automatically before you Edit. Cineform is now integarted into PPro, DaVinci Resolve and many other NLEs now support these intermediate codecs. They work in PDR (we tested it) as does any VFW codec.

Here is an example using PPro Edit 4K Footage Easy with Adobe Premiere Pro and Cineform. Cineform is also GPU accelerated which improves performance. Transcoding to an intermediate codec make 4k editing with high quality preview posible on a consumer PC. It was proven to work in PDR14 with a user developed transcoder (Magic+PD Solution in the forum) using the MagicYUV codec. I use it for 4k editing on my Core i5 and PDR14. Files are large but I delete them when I'm finished. PDR could easily add transcoding to an intermediate codec as an option before edit as long as you have downloaded and installed any of the intermediate codecs mentioned above and they are VFW codecs.

Here are more links for further reading:

How to Work Efficiently with 4K Footage on Old Computers

Faster Editing in DaVinci Resolve 12.5 Using Optimized Media

Proxy Workflow: Edit Large 4k RAW files on a Laptop! Premiere Pro CC 2015.3

Sony Vegas - MagicYUV codec coming on strong for 4K

Why you should use Avid DNxHD and Apple ProRes

The Intermediate Codec Thread

Summary


  1. There is currently NO software out there that can edit 4k on a consumer level PC smoothly. When you add 4k clips in multi layers to the timeline and add some effects any NLE software is going to struggle or freeze without very expensive hardware. It is unreasonable to expect Power Director as a consumer grade NLE to do any better. Whether you spend a hundred dollars or or a thousand dollars for an NLE you need more to edit 4k.

  2. GPU acceleration is also limited to the effects and codecs written to support it - not only the NLE software. Improved GPU support won't guarantee 4k realtime editing but as Jeff (JL_JL) has shown it can improve performance.

  3. Professional NLE software on high end hardware supports and uses transcoding to Proxy Files and Intermediate Codecs for smooth 4k editing. Power Director can easily do the same to enable users to edit 4k on a consumer level core i5 or i7 PC. 4k editing will never be a reality for most PDR users until they do.


Sooooooooooo - for those (me included) who have expressed their disappointment with PDR performance - other NLE software may not solve your problems. Furthermore, upgrading your PC CPU/GPU may not give you 4k editing - unless you have a very large budget.

Does that mean you can't edit 4k now? Not at all! You can transcode your 4k videos to a lower resolution using third party software You can also try the user developed Magic+PD solution in the PDR14 forum to transcode your 4K clips to a fast intermediate codec but both are time consuming and difficult for most users - but they do work.

I left out render speed intentionally as it's really another topic. 4k render is not a problem in PDR. At lot of software is adding Intel QuickSync support. PDR has had it for some time, Edius added it with Ver 8 and Resolve has recently added it as well. Here is a an independent evaluation of render speeds http://www.dvc.uk.com/acatalog/Edius_quicksync.html



Al



PS - Please excuse my typing. I like the new forum look but can't believe there's still no Spell-check, cut, paste etc.

This message was edited 7 times. Last update was at Oct 31. 2016 09:37

Power Director 13&14 Ultimate, Photo Director 6, Audio Dir, Pwr2Go 10
Win 10 64, Intel MB DH87MC, Intel i5-4670 CPU @ 3.40GHz, 16Gb DDR3 1600, 128Gb SSD, 2x1Tb WDBlue 7200rpmSATA6, Intel 4600 GPU, Gigabyte G1 GTX960 4GB, LG BluRay Writer
ynotfish
Senior Contributor Location: N.S.W. Australia Joined: May 08, 2009 02:06 Messages: 9977 Offline
[Post New]
Very informative Al!

I haven't investigated further by following the links you posted, but THANK YOU for taking the time to share your findings.

Recently, I installed Camtasia 9 (used to be called Camtasia Studio), which can record in UHD/4K if that's what your screen is. I've only tested that briefly, but it's clearly a greater load on the system!

Cheers - Tony
Visit PDtoots. PowerDirector Tutorials, tips, free resources & more. Subscribe!
Full linked Tutorial Catalog
PDtoots happily supports fellow PowerDirector users!
AlS
Senior Member Location: South Africa Joined: Sep 23, 2014 18:07 Messages: 290 Offline
[Post New]
Quote Very informative Al!

I haven't investigated further by following the links you posted, but THANK YOU for taking the time to share your findings.


Cheers - Tony


Thanks Tony,

I added links for a better understanding and additional info (post was already a bit long winded). I've since added a few more. If you get a chance have a look. Would appreciate your thoughts/comments.

There are many more software examples out there but I chose the best implementations for transcoding (easy to use).

Just an aside, but MagicYUV codec has gained larger acceptance for speed and quality since the Magic+PD project. Now being used in several Pro NLEs.

Cheers

Al Power Director 13&14 Ultimate, Photo Director 6, Audio Dir, Pwr2Go 10
Win 10 64, Intel MB DH87MC, Intel i5-4670 CPU @ 3.40GHz, 16Gb DDR3 1600, 128Gb SSD, 2x1Tb WDBlue 7200rpmSATA6, Intel 4600 GPU, Gigabyte G1 GTX960 4GB, LG BluRay Writer
[Post New]
Mercury Engine in Adobe does NOT use fully the GPU to actually accelerate the final rendering (encoding) or preview (decoding):

https://blogs.adobe.com/creativecloud/cuda-mercury-playback-engine-and-adobe-premiere-pro/

"It’s worth mentioning one set of things that Premiere Pro doesn’t process using CUDA/OpenCL: encoding and decoding."

I have tested also Sony Vegas and Corel NLE products and they are not using the GPU properly either. Only PD is actually using the GPU for decoding and encoding tasks, accelerating somehow the work in 4K. But that needs to be supported by the GPU, so using the proper formats is VERY important. At this point only H264 and H265 formats are properly supported.

As a side-note, any QuickTime video will be software only, 32 bit. Plus QT for Windows is not supported by Apple anymore and is a huge security risk and should be uninstalled from Windows:

https://www.us-cert.gov/ncas/alerts/TA16-105A

http://bgr.com/2016/04/15/uninstall-quicktime-for-windows-security/

This message was edited 1 time. Last update was at Oct 28. 2016 10:14

AlS
Senior Member Location: South Africa Joined: Sep 23, 2014 18:07 Messages: 290 Offline
[Post New]
Quote Mercury Engine in Adobe does NOT use fully the GPU to actually accelerate the final rendering (encoding) or preview (decoding):



Sonic - Not sure what you mean by "not fully used"? Quote from your blog link above "A common misconception is that CUDA/OpenCL processing is only used for rendering for previews. That is not true. CUDA/OpenCL processing can be used for rendering for final output, too."

And Nvidia http://www.nvidia.co.uk/object/adobe_PremiereproCS5_uk.html "At the heart of Premiere Pro CS5.5 is the Adobe Mercury Playback Engine, built using the NVIDIA CUDA parallel processing architecture. Accelerated by both Quadro and NVIDIA Tesla graphics cards, you get real-time previewing and editing of native, high-resolution footage, including multiple layers of RED 4K video. Get 15 times faster performance, enabling you to refine and apply multiple color corrections and effects in SD, HD, 2K, and higher-resolutions, with smooth scrubbing and playback – all in real-time!" The Mercury Engine was a joint Adobe/Nvidia project so I assume it's getting as much as possibe of those $5k GPUs.

Most Windows NLEs have now elimated the need for Quicktime including PDR.

This message was edited 1 time. Last update was at Oct 28. 2016 14:22

Power Director 13&14 Ultimate, Photo Director 6, Audio Dir, Pwr2Go 10
Win 10 64, Intel MB DH87MC, Intel i5-4670 CPU @ 3.40GHz, 16Gb DDR3 1600, 128Gb SSD, 2x1Tb WDBlue 7200rpmSATA6, Intel 4600 GPU, Gigabyte G1 GTX960 4GB, LG BluRay Writer
[Post New]
Quote
Quote Mercury Engine in Adobe does NOT use fully the GPU to actually accelerate the final rendering (encoding) or preview (decoding):



Sonic - Not sure what you mean by "not fully used"? Quote from your blog link above "A common misconception is that CUDA/OpenCL processing is only used for rendering for previews. That is not true. CUDA/OpenCL processing can be used for rendering for final output, too."


The Adobe terminology is misleading. They use "rendering" for a different process than the actual "encoding and decoding".

See my link that points directly to Adobe statement that I have quoted.

Quote Most Windows NLEs have now elimated the need for Quicktime including PDR.


Did they really? Or they just incorporeted the last version of QT binaries (that are never to be patched)?



[Thumb - QT_kernel.JPG]
 Filename
QT_kernel.JPG
[Disk]
 Description
CL QT kernel
 Filesize
42 Kbytes
 Downloaded:
866 time(s)

This message was edited 2 times. Last update was at Oct 29. 2016 09:32

AlS
Senior Member Location: South Africa Joined: Sep 23, 2014 18:07 Messages: 290 Offline
[Post New]
Quote
Quote
Quote Mercury Engine in Adobe does NOT use fully the GPU to actually accelerate the final rendering (encoding) or preview (decoding):



Sonic - Not sure what you mean by "not fully used"? Quote from your blog link above "A common misconception is that CUDA/OpenCL processing is only used for rendering for previews. That is not true. CUDA/OpenCL processing can be used for rendering for final output, too."


The Adobe terminology is misleading. They use "rendering" for a different process than the actual "encoding and decoding".

See my link that points directly to Adobe statement that I have quoted.

Quote Most Windows NLEs have now elimated the need for Quicktime including PDR.


Did they really? Or they just incorporeted the last version of QT binaries (that are never to be patched)?




Thanks Sonic,

You may well be correct but all of the NLEs I tested now claim they are QuickTime independent and ran fine since I uninstalled QT which was the security threat. DaVinci Resolve 12.5 now claims "DaVinci Resolve 12.5.1 now uses its own native 64-bit code to read and write .mov files."

My understanding is that codecs (encoding and decoding) for rendering and timeline editing and effects only benefit from GPU acceleration if they are written for GPU acceleration. I can't afford $10,000+ for two Quadro GPUs to challenge Adobe's claims.

In a previous post I mentioned that DaVinci Resolve 12 professioal NLE was GPU intensive and died on my "mickey mouse" i5 CPU with no GPU card. New version 12.5.1 added, with Intel help, Intel HD Graphics support and "Now, DaVinci Resolve, with new code changes, runs 1200% faster on Intel Graphics systems." Ver 12.5.2 now runs fine on my consumer level PC with the free onboard Intel GPU using their Proxy Editing or Transcoding features - as shown in the link on Resolve Optomized Media in my first post above. Same technology PDR has had since I started with PDR12.

Blackmagic and Iris™ Graphics: A Match Made at Intel .

Al

This message was edited 3 times. Last update was at Oct 29. 2016 19:46

Power Director 13&14 Ultimate, Photo Director 6, Audio Dir, Pwr2Go 10
Win 10 64, Intel MB DH87MC, Intel i5-4670 CPU @ 3.40GHz, 16Gb DDR3 1600, 128Gb SSD, 2x1Tb WDBlue 7200rpmSATA6, Intel 4600 GPU, Gigabyte G1 GTX960 4GB, LG BluRay Writer
[Post New]
Well I have great respect for Blackmagic. If they pulled the task to deveop a 64 bit plugin for QT, that's more power to them. Maybe they affforded paying for the licensing to make it compatible with Final Cut Pro 7. Unfortunatelly for me their free DaVinci is not as capable as the "Studio" version, color, grading, noise reduction, are not using the GPU in the free version:

https://www.blackmagicdesign.com/products/davinciresolve/compare

In the past Apple, that has the licensing rights to the format, didn't allow companies to develop their own QT software, forcing everyone to use their crippled 32 bit software, without any GPU involvment (see my exemple above, CL is still using the 32 bit version).

So all in all, I am staying away from any software that is using almost exclusivelly Apple's formats:

https://documents.blackmagicdesign.com/DaVinciResolve/20160408-ebf601/DaVinci_Resolve_12.5_Supported_Codec_List.pdf
AlS
Senior Member Location: South Africa Joined: Sep 23, 2014 18:07 Messages: 290 Offline
[Post New]
Quote Well I have great respect for Blackmagic. If they pulled the task to deveop a 64 bit plugin for QT, that's more power to them. Maybe they affforded paying for the licensing to make it compatible with Final Cut Pro 7. Unfortunatelly for me their free DaVinci is not as capable as the "Studio" version, color, grading, noise reduction, are not using the GPU in the free version:

https://www.blackmagicdesign.com/products/davinciresolve/compare

In the past Apple, that has the licensing rights to the format, didn't allow companies to develop their own QT software, forcing everyone to use their crippled 32 bit software, without any GPU involvment (see my exemple above, CL is still using the 32 bit version).

So all in all, I am staying away from any software that is using almost exclusivelly Apple's formats:

https://documents.blackmagicdesign.com/DaVinciResolve/20160408-ebf601/DaVinci_Resolve_12.5_Supported_Codec_List.pdf


My experience is the same. I'm not recommending Resolve at all. It is used in Hollywood movies and designed for the Pros post production workflow only. I only tried it as part of my testing for relatime edit performance with professional software- and to illustrate that even the pros use the built-in features for transcoding to proxy files and to intermediate "edit friendly" codecs like Cineform and DNxHD before edit as per my first post.

Agreed - Even the professional studios are shifting from Apple to Windows systems where QuickTime is now becoming history.

Al

This message was edited 3 times. Last update was at Oct 30. 2016 05:13

Power Director 13&14 Ultimate, Photo Director 6, Audio Dir, Pwr2Go 10
Win 10 64, Intel MB DH87MC, Intel i5-4670 CPU @ 3.40GHz, 16Gb DDR3 1600, 128Gb SSD, 2x1Tb WDBlue 7200rpmSATA6, Intel 4600 GPU, Gigabyte G1 GTX960 4GB, LG BluRay Writer
[Post New]
The truth of problem that editing 4K video on Cyberlink PowerDirector
Reason 1. Do you install the latest Cyberlink PowerDirector version? The older Cyberlink PowerDirector version, such as: 11/12/13/14 which can't support Ultra HD 4K videos because of the ultra high video resolution and the format compatibility.
Reason 2. Make sure your computer is good. Especially you want to get a better 4K video, It will put a strain on your computer, the computer configuration is low and not very high, you may have to slow down and wait the result.
Reason 3. Although Cyberlink PowerDirector can support 4K UltraHD, AVCHD 3D/Progressive, XAVC-S and H.265. Video resolution can up to 4096 X 2160. The different format type, Bitrate, Resolution, FPS, Profile, Frame type,etc factors will effect your 4K video editing in Cyberlink PowerDirector.
Powered by JForum 2.1.8 © JForum Team