Hi,

Does this version incorporate version beta 2421?

Thanks

Quote - Fixes the issue that hardware decoding sometimes malfunctions.

STILL broken, no fixes here. Below threads all clearly show issue by multiple users and the issue still exists.

http://forum.cyberlink.com//forum/posts/list/25/45503.page#236759
http://forum.cyberlink.com/forum/posts/list/49689.page#post_box_261412
http://forum.cyberlink.com/forum/posts/list/49689.page#post_box_261434
http://forum.cyberlink.com/forum/posts/list/50731.page#post_box_266429

Would some other representation of the issue help resolution? Obviously what the user community has tried for 2+ yrs has not been fruitful.

Jeff

Hello BetoValle,

Yes, all the fixes up to beta patch 2509 are in this patch update, including those in 2421.

Hi Jeff,

They are still working with the manufactuerers to find the proper solution it seems. I will ask now whether they need anything more from yourself to help speed up the process.

Cheers,

PowerDirector Moderator

For customer support related issues, please contact:
- Customer service: https://membership.cyberlink.com/support/customer-services.do
- Technical support: https://membership.cyberlink.com/support/service/technical-support.do

Quote Hi Jeff,

They are still working with the manufactuerers to find the proper solution it seems. I will ask now whether they need anything more from yourself to help speed up the process.

Thanks, appreciate the response. Hard to understand "Fixes" statement in release and then "still working" but I guess I'm still hopeful for a solution.

Also, very disappointed to see "Enable hardware video encoder" disabled in the “Create Disc” module in this official release for Nvidia users, http://forum.cyberlink.com/forum/posts/list/50950.page#post_box_267535

Jeff

Hi Jeff,

Here’s the response:

For the first link you shared, it is for PowerDirector 14. HEVC 4K video hardware decoding was not supported until version 15. Are you saying HEVC 4K video hardware decoding is not working for you in PowerDirector 15?

The development team says the issues in the three other links are all related as they can be tied to the same root cause/program behavior. They are currently working on a way to improve this, but a possible solution should not be expected in the current version.

As for the hardware video encoding disabled issue, it is a time consuming update that is required and they are still working on it. They did consider your request, but want to use all the resources to fix the problem, not to implement a temp one. They plan to have it fixed in a future patch update.

Cheers,

PowerDirector Moderator

For customer support related issues, please contact:
- Customer service: https://membership.cyberlink.com/support/customer-services.do
- Technical support: https://membership.cyberlink.com/support/service/technical-support.do

Quote Here’s the response:

For the first link you shared, it is for PowerDirector 14. HEVC 4K video hardware decoding was not supported until version 15. Are you saying HEVC 4K video hardware decoding is not working for you in PowerDirector 15?

The development team says the issues in the three other links are all related as they can be tied to the same root cause/program behavior. They are currently working on a way to improve this, but a possible solution should not be expected in the current version.

Well, nothing in your PD14 distribution ever stated hardware decoding is not supported with certain formats that one's hardware supports. After all, your media library playback supported it. But okay, my outdated PD14 link which showed it didn't work gave dev a item they knew needed to be addressed in a future version, now enter PD15, fully supported right?

I guess the communication is a little hard to understand. You release a new patch with the notes of "- Fixes the issue that hardware decoding sometimes malfunctions." which to me means the issues have been fixed. What does it mean to you? Now the dev team says we are working to improve this, but don't expect a solution with this current version. Did you not release this version with "nVidia, Intel & AMD H.265 (HEVC) Hardware Decoding" as a feature? It was clearly stated here https://www.cyberlink.com/products/powerdirector-ultra/compare-versions_en_US.html Does that imply H.264 decoding is not supported, supported in PD14 since older technology?

But, here is PD15 with your latest 2509 patch with the decode fix, and yes, the issue as described in the links that were referenced still exists. Did your dev team even try, or are you implying my platform is unique, as well as others? Attached is a video, entirely unedited from start to finish, which clearly demonstrates your PD product with current patch cannot maintain hardware decoding after incorporating a straddle clip transition.

The steps in the video are simply listed below:
1) create sample 4K footage H.264 based on Kites.wmv producing to PD default profile, 4K 4096x2160/60p (50Mbps) with CPU encoding so it's entirely CL product footage, one can't blame any video content source
2) add produced clip to timeline and playback, one clearly sees the Nvidia GTX1070 video engine load as you should with GPU-Z
3) split the clip, both pieces playback utilizing the Nvidia GTX1070 video engine as it should
4) add a transition that straddles the split clips, the clip prior to transition plays back utilizing Nvidia GTX1070 video engine as it should, clip post transition does not, absolutely ZERO load as shown by GPU-Z.
5) remove transition, both clips play back with hardware decoding as evident by GPU-Z load

The above also applies to other footage like 2K.....so on and yes H.265 as well.

So, are you implying this is a flawed test with flawed expectations of the hardware decoding feature released with PD15 or dev simply has a bug that needs resolution?

Jeff

Hi Jeff,

Thanks for your response.

We understand the confusion and apologize, as we should have been more specific in the original release notes and also been more specific in the response to your initial points.

We have clarified the following:

The issue that was fixed in the patch release is that “Enable hardware decoding” in Hardware Acceleration preferences is sometimes greyed out on certain platforms.

We have updated the original release notes accordingly.

For the other current hardware decoding issue that you analyse, we understand you are referring to the same issue for all four links you shared.

Our information is that this has been found to be a program limitation in the editing engine that they are currently working on to improve. The improvement will take some time, which means that a possible solution should not be expected in the current version.

Your comments about the comparison chart features in this regard have been noted .

Cheers

PowerDirector Moderator

For customer support related issues, please contact:
- Customer service: https://membership.cyberlink.com/support/customer-services.do
- Technical support: https://membership.cyberlink.com/support/service/technical-support.do

Quote
Our information is that this has been found to be a program limitation in the editing engine that they are currently working on to improve. The improvement will take some time, which means that a possible solution should not be expected in the current version.

Thanks, appreciate the response, much more clear on what “Fixes” means in the notes.

So, I think CL has come to realize the edit engine does not hardware decode as a user would expect which is what has been stated for multiple years as I had mentioned in the thread. From what I see, these issues occur for H.264, H.265(PD15 added decode feature) 2K, 4K.... with various timeline edits (a simple transition used as one example in the demonstration video). Hopefully CL dev team can do a thorough evaluation and release a product supporting the stated release claims.

Thanks again for bearing with me in the thread, getting to the bottom of a potential issue, for the future benefit of all your users.

Jeff