|
|
Quote
Hi,
As this is a member to member forum and CL do not monitor it, perhaps the best way to get your suggestion into the system and in front of folk that can action it is to use the File>Rate us and provide suggestions route from the main PDR menu.
But if you can share an example or a short partial recording for testing, members might also come up with some suggestions?
Cheers
PowerDirector Moderator
Thanks for the first suggestion. It's a shame CL don't monitor - you'd have thought it's a useful source of feedback.
Anyway, regrading an example, it's really quite straightforward - anything recorded from an HD channel is saved in a .TS HD format and when an import into PD is attempted, the following message is received;
"An error occured while opening the media file in the media library. It may be because the file is broken, an unsupported format, protected video content, or for another reason."
It seems odd that after many years of this problem being prevalent in the software, its never been addressed.
|
|
|
I've been a user of Power Director since I think v12. I have very simple requirements - I record free to air films from UK TV, edit using PD (365 version) and output into a Plex library. I have tried various other bits of software but nothing comes close to the user experience PD gives BUT ......
It is odd that PD does not handle TS HD format downloads. Probably 50% of films I download are in HD now and I have to convert them using some other piece of software into a format that PD likes to edit them which can take hours.
Could the Powerlink boffins please look at addressing this after all these many years - this near perfect software is seriously let down by this deficiency. I've flirted with other software but always come back to PD - I promise if this is fixed, I'll never need download any other video editing software ever.
|
|
|
I upgraded yesterday to 21.0.2116.0 and now find that I cannot use GPU hardware Acceleration when producing movies. Exactly the same thing happened to me last year after an upgrade (covered here https://forum.cyberlink.com/forum/posts/list/84422.page) and a resolution was never found - I eventually was provided with a link to a previous version (support ticket CS002331174).
The difference from last year is that I have an entirely different machine and graphics card so there is nothing common in my set up. The graphics card I am using has all drivers up to date (AMD Radeon R5 Graphics_27.20.20904.1004).
I have followed all the recommended remediation steps - deleting HKEY_CURRENT_USER\SOFTWARE\CyberLink\CES_FunctionLogger and HKEY_CURRENT_USER\SOFTWARE\CyberLink\MediaCache5 and rebooting but nothing has changed.
Anyone else having a similar experience or have any thoughts how to resolve? I'd rather just go to the previous version but I realise there isn't an option to do that without support assistance.
|
|
|
Quote
HA and SVRT are totally separate issues. Take a look at this post and see if that will restore hardware acceleration for producing.
I went through all of this as a support ticket back in April. As per my original post, nothing worked and I was given an old version to roll back too., I had some hope that multiple releases since might have resolved the issue but to no avail.
I am therefore stuck on a older version of PD19 yet pay an annual 365 subscription for releases I can't take - as there seems no likelihood that will change as PD20 has just been released, I'd like to know how I get out of the 365 contract.
|
|
|
|
Sorry, I actually mean that Hardware Accelaration is not working and hasn't been for me since the pre Jan 21 release. Any help I can get would be appreciated although my support ticket raised in April wasn't resolveable and roll back was the only option.
|
|
|
SVRT is not working for me in PD20. I spent two hours installing and testing and it still doesn't work so I rolled back to the Pre Jan 21 version that was supplied to me as a result of my last ticket in March this year not being resolved. That works fine. I was unaware of any previous hot fix, if it was only communcuated through this forum I would have missed it as I don't visit here regularly.
|
|
|
|
SVRT is not working for me in PD20 so I have had to uninstall and go back to a Pre Jan 21 version of PD19 (provided as a result of a previous PD19 support ticket). It doesn't look like I'll ever get beyoind that version which makes a mockery of having a 365 subscription. Who would I speak to change my plan?
|
|
|
Quote
I can totally relate, it my view this feature was a half completed effort that really maybe was just a focus on perhaps the laptop market but has implications for any desktop too and the plethora of configurations maybe not properly vetted.
I've run with simultaneous AMD and NVideo GPU's and see one set of anomalies
I've run with two simultaneous Nvidia GPU and see another set of anomalies
I've run with two AMD GPU's and see another set of anomalies
I helped a recent user that had a issue very similar to yours, a blank and unselectable fast rendering technology box like you show. In a nut shell the end approach that worked was:
1) Use DDU and remove all traces of installed GPU's. He had several and several brands. Not only discrete but CPU based too.
2) Get GPU functional with just VGA drivers, don't let windows beat you to installing a driver
3) Make sure BIOS set appropriately for specific PCI first slot of GPU and any CPU specific GPU disabled and monitor only plugged into discrete GPU
4) Load GPU specific drivers
5) I've launched PD periodically in these steps to see what it has for hardware encoding, what the about box indicates and so on of confirmation of config vs PD capability shown.
Approach probably not something I'd suggest to the typical PD user that is struggling. In the end, I had a Nvidia working system for him. I can only think the issue was from multiple GPU's once installed in his system and inadequate full uninstalls of all pertinent stuff. Nvidia, AMD, nor windows alone achieve that.
Hopefully CL will resolve with your ticket.
Jeff
Thanks for your response. As a test, I did all of this today - no change.
|
|
|
Two months on and despite trying almost every combination of uninstall, re-install of both PD, the graphics cardand following helpful advice offered here, I've never got this to work again.
I've raises a support ticket - CS002331174,
|
|
|
|
This is probably a common problem. Often when I try to open PD19, nothing happens. I saw elsewhere thatt his is because the previous instance hadn't closed properly so I now know that when it happens, I can go to Task Manager and close any lingering processes. |This is annoying though - has any found a permanent solution to this issue?
|
|
|
Quote
Thanks very much for that! I think you'll find the answer here.
I admittedly didn't spend a lot of time yesterday but did try as suggested with no change. I will look in more depth today - thank you though for the gudiance.
|
|
|
Quote
Any chance you can post a pic of your entire "Produce" screen, I would like to see what you have in this non-working state prior to your corrective actions.
Jeff
|
|
|
|
Unfortunately, everything suggested I've tried but hasn't resolved the issue so it looks like I will have to raise a ticket, although I think I may first try to fully uninstall PD and then re-install - the only thing left I can think of.
|
|
|
Quote
Thanks for uploading the DxDiag results. Overall things look good there, but there are two things I can suggest.
You have the latest nVidia driver installed for your GTX 1050, but it's possible that something went wrong when it was installed that's interfering with PD's ability to access the video encoder. Try downloading the Studio Driver here then follow the instructions in this post to force a clean installation.
After rebooting, see if the hardware video encoder option is available. If it is and you need to install any other nVidia utilities (especially if you're a gamer), you can run the installer again and add those components. No need for a clean install this time.
The end of the DxDiag results show the 10 most recent crashes, and there are several for a Windows component called ScanForUpdates. These issues probably aren't related to the problem with PD, but you may want to run the two commands as described here to see if there might be some damage to Windows' core files.
If the problem with PD accessing the hardware encoder is still present, I suggest you open a support request directly with Cyberlink. You can do that from their main support page.
Thanks very much for the advice - I shall follow the steps later. I did think it could be related to the recent driver update so rolled it back yesterday but nothing changed so re-installed the driver. It does seem to me though too much of a co-inidence that I updated both PD and the driver in the last few days and then have had this problem. What I wanted to do was rollback both, test and then re-apply updates but as you have pointed out, thre isn't a rollback option for PD.
On your scond point, that's very helpful,. I have suspected that I have had some kind of issue with Windows recently but my lack of knowledge couldn't pin it down - will definitely be exploring this.
|
|
|
|
DXDiag attached. Nothing showing up in the registry.
|
|
|
|
Ran a job (too ages) but still nothing showing in the registry. Ran DXDiag, no issues being highlighted. Bit stuck now. Does anyone know how I roll back the to the previuous version?
|
|
|
Quote
That just means you haven't tried producing with any of these profiles since the update. Maybe seeing your DxDiag results will help.
Maybe that's the answer then - create something with my custom profile and it will be become available.
|
|
|
|
Thanks. I was aware of that fix from a previous time I had an issue (it worked on that occasion). This time though, I have only one entry in that folder whereas last time I could see all the default and custom profiles.
|
|
|
Upgraded to the latest PD19 version this morning and cannot Enable Hardware Acceleration when producing now. Have checked and reset all the settings in preferences but can't get it to work against any default or own created profiles.
Anyone else have similar or anyone got any suggestions?
|
