|
Quote
Tomasc has linked to the post I was referring to. I see that I've made a mistake in conflating the exception that CL made to go back 3 versions to patch PD15 (for the Produce Room crash) with the nVidia 416 driver issue as they were both happening at the same time.
I will go back and revise my statements. Thank you for pointing this out!
Okay, time for me to feel like a complete idiot; wouldn't be a first: Reinstalling the old drivers did in fact re-enable the HW acceleration, which sort of puzzles me - I rendered videos in late November last year, and am fairly sure I had updated drivers after the suggested driver version. Been a long time since I applied the fix to get things working, and I'm fairly sure it consisted of doing certain modifications that's not necessarily safe nor adviseable. As you're saying, the changes to the SDK is where the elephant roams, and I'm sure the 'fix' I used involved using parts of an older SDK version to trick PD into believing it was using older video drivers - maybe I remember wrong?
In any case, I do apologize for being an idiot, but I'd rather be wrong and have it working than be right and unable to use the substantially faster rendering
|
|
Quote
I see no point in taking this any further; I have absolutely no reason to lie to you, nor do I find your 'spelling out' comment appropiate - don't know how old you think I am, but I'm old enough to remember the time before there was anything remotely resembling a computer available for purchase - and I mean the 8bit era. Thanks for your advice, however little value it had - if I tell you something, it's not a 'bold claim', but a fact; I have a habit of only opening my mouth when I know what I'm talking about
You know what? I may owe you an apology - if memory serves me, at my age your forget things , the reason I haven't had any issues with newer Nvidia drivers is due to the fact that I haven't been using parts of them for PD 14.
The fix that was suggested long ago was either relying on PD14 looking in its own folders first for .dll files, or overwriting certain .dll files in Windows; if the latter turns to be the solution, it's at own risk - need to dig out some more in the archives here, as it was from this site the advice was given.
Hope no hard feelings
|
|
Quote
Just to be clear, this is a user forum and I'm a fellow user, like you. Nobody on here except the moderator works for Cyberlink. This is certainly not Cyberlink technical support.
If you'd please look at my post again, you'll see that there's no reason you have to spend any money - but to get back HW acceleration you can't use the newest versions of the nVidia drivers. I spelled all of that out.
Despite your bold claims, I'm afraid that without using the 411.70 drivers, your 1060 is not being used by PD for producing in any way so the rendering that's occuring is due soley to your CPU. Many people get by without a dedicated GPU, and you're free to keep the new drivers and remain in the no-GPU group.
As for actual support, if you were to contact them, they would respond and try to get you running, even though there are 3 newer versions of PD. The thing Cyberlink doesn't do is to update older versions of software. Typically they'll support each version for two years, and in the case of the nVidia driver change, they went back 3 and patched PD15 as well.
Again, I'm giving you the ground truth about the nVidia situation, and I sincerely hope you'll find at least one of my suggestions helpful.
I see no point in taking this any further; I have absolutely no reason to lie to you, nor do I find your 'spelling out' comment appropiate - don't know how old you think I am, but I'm old enough to remember the time before there was anything remotely resembling a computer available for purchase - and I mean the 8bit era. Thanks for your advice, however little value it had - if I tell you something, it's not a 'bold claim', but a fact; I have a habit of only opening my mouth when I know what I'm talking about
|
|
Quote
Wolf_2293 I'm sorry you're having trouble. I can tell you though that there's no way PD14 will ever work with the current (v417.xx and above) nVidia drivers, because they're built for the newer version of their Software Design Kit (SDK), and PD15, 16 and 17 had to be patched to use the new drivers.
PD14 is no longer supported, so there are only 2 ways for you to get back GPU access: go to the nVidia website and download the final version of the older style drivers (which is 411.70 from Sept 27, 201; or upgrade to PD17.
Very sorry about that - you see, some of us aren't made of money and having to get a new version of our existing products, because a card manufacturer dare to update their drivers, is just plain dumb - much as I like the product itself, the support has been horrible; not exactly encouraging people to keep throwing money at it
Besides, I update my drivers regularly, and prior to 6th of January (before Windows died on me) my acceleration was working fine - it may be that it can't be solved from official side, but it was a user that sorted me out.
If I sound slightly displeased, while I understand a company has to make money to survive, surely you can understand that it's not within everyones ability to just buy, buy, buy...
Besides, that has been the official answer every time I've had issues with PD14: Buy latest version - I had my first issue when PD15 was released, yet I've managed to get the HW acceleration going through PD15 and 16.
Thankfully, my 1060 is more than powerful enough for my rendering needs, even without the acceleration; just a nuisance that it doesn't work and getting that same old cooperate answer is just getting tedious - smells too much of 'Help, Microsoft, my computer is on fire! - Just restart and it'll be fine'
Before dismissing this as just a heated rant, I want to clarify that I'm fully composed and in an amiable mood; as I said, I really like the product itself - it's the 'support' that's - hmmm - 'interesting'
|
|
Quote
Hi
Is this defect resolved yet? I have come across quite a few incidents being logged in various forums/youtube etc but still seem to be an open issue.
It is not possible and advised to downgrade your graphics card drivers in order to get your video editing software working! Surely there is a way to get this fixed?
Thanks
I'm having issues as well - the worst part is, I had Powerdirector 14 doing HW acceleration fine using a GTX 1060 with latest drivers; latest Win 10 feature update failed to install, and the initial Microsoft tech support 'solution' corrupted my Windows installation, hence I had to reinstall and now can't remember the wizardry I was using to make the acceleration work
EDIT: The comfort being that I have had it work, I guess..
|
|
Quote
There could be many causes for this. A system restore to the time before this happened should fix it or reinstall the video driver. You may have had a crash with PD14 while trying to encode. If this is the case then see this post on how to fix it: http://forum.cyberlink.com/forum/posts/list/48900.page .
Thanks a bunch - worked a charm - turned out I had 3 values at 1, which after editing to 0, gave me all of them back - including the 1920x1080 When the difference in rendering time can be upwards 20 mins, it's frustrating not being able to use the HWA.
Thanks again
|
|
Hi,
I know this is going to be a relatively broad issue, but I'm getting rather frustrated with losing HWA in more and more setups, using PowerDirector 14.
First, it was 1920x1080 - any combination of framerates/bitrates/whatever
And just this morning, it now refuses to apply HWA to 1280x720 - again any framerate/bitrate - which is the resolution I switched to after 1920x1080 stopped being supported.
Last time, Cyberlink was putting the blame on Nvidia - but I'd not done anything to change settings, driver version or whatever else could be involved with Nvidia
This time, the problem just started out of nowhere - I updated Nvidia drivers (clean install) after the fact - and still nothing...
EDIT: I should add that it's MP4 H.264 - and, an interesting thing is that PDR is happy to apply HWA to 2048x1080...
Any ideas? Before commenting on specs/graphics card/etc, I want to re-emphasize that everything worked fine last night...
|
|
|