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 >
Quote Hello,

The OP and others were referring to the last build of PowerDirector 365 (21.0.2214) released last week, not the standalone version (Ultra or Ultimate?) you purchased.

It very well could be that you are using Windows 7 that is causing the issue in the latest version for you. See this FAQ for more details:

https://www.cyberlink.com/support/faq-content.do?id=27521



Unfortunately that is not in the cards, since Microsoft has stopped technical support as noted in the FAQ.

Cheers
PowerDirector Moderator


I know all were referring to 365 but 365 and 21 are in the same family, and I have been reading similar reports between the 2 of bugs. And I hoped by including my similar crashes here and my system that maybe it will be found that the bugs between 365 and 21 are the same, shedding some light on the same programming they share, perhaps helping more potential buyers to make educated deductions what may work for them, system wise, price wise. But I agree with you that Win 7 may no longer be compatible as time passes with the newer versions and so I hope that cyberlink will take honest hard look at that and stop perhaps auto-including Win 7 if they haven't tested it in truth, since as you say, it is well known that Microsoft no longer supports it, and so no further system updates will exist. Now if everyone started reporting they had win 7 then soon it would be clear that's the issue. But I did make double sure that Win 7 64 bit was included as compatible, before purchasing. Any rate I have gone and gotten a PD 16 version off ebay for the color match feature that should definitely work with Win 7 - I do wish cyberlink would sell older versions for those as myself, but that may be intentional on their end to force into monthly plans. Personally for me Win 7 I love because it keeps me free from having to pay perpetually in the new never-own-your-software marketing angles today, with older programs that still work wonderfully, and sometimes even better than the newer ones. Cheers to you also!
Quote I made the upgrade to the 365 Suite 6 weeks ago - i have crashes very frequent when performing very simple task, such as dragging the end of title asset to increase its duration - I NEVER had issues with that simple edit before - now I have to Save offen due to frequent crashes. I am running PD on a workstation that exceeds standard system requirements and I usually only have it running during video production/editting.
What is the Hotfix schedule for the 365 suite?
At this point, due to loss of productivity I may go back to PD17 until this crashing issues is resolved. . .



I have had frequent nonsensical crashes since getting this standalone 21. As well as I have experienced numerous issues with it that I had to abandon using it a few days back in order to keep it from destroying precious time getting a project done. So I had to go back to version 15 on my same computer that has the capability to do the same job, except for the color match. Although I have Win 7 64 bit, it more than meets the minimum. Interesting going back in full to version 15 to see that version 15 can handle and do the very same things better than version 21.

For instance, besides not crashing without cause, or crashing when loading certain FX, it does far better job at chroma key with the native powerdirector way that involved using Edge Sharpness. Without the option to sharpen edges, one can have double or more the extra color choices and end up with noisy edges that make useless amateur keying. PD 15 can handle normal workload, and a lot of multiple tracks without crashing, and can render them quickly.

Besides the senseless crashing, PD 21 consistently would take over 90 minutes to render every 1 minute of video using the same exact settings as PDD 15 on the same computer, of which I select to make mp4. It was/is so horrible that only volunteer beta testers who receive the software for free for their troubles to go through the demanding job to trouble shoot all the issues until it is really ready to be released should be the ones to suffer experimenting with this. I am seriously thinking of returning this, and just get an earlier stable version from ebay to do color matching.

I noticed that pd 15 will sometimes get confused if I select a video to resize near a picture and try to jump, but I only need to make another re-attempt and it behaves. Not so with PD21: every time I go to resize a video, it will jump to the nearest image and resize that, and be stubborn about it, so I have to disable that picture to do a resize, but then it will jump to the next nearest image, and then even after then start jumping to nearer videos so it becomes a dark comedy of oh no you won't jump/disable to it displaying almost a willful intent to trouble the user and indeed jump yet again so no work can get done.

And I never heard my computer rev up so much like a jet plane gearing to take off from all of the cpu and reactions this version has, that simply does not happen on the same computer with version 15. I thank God I have stuck with version 15 as I never would have done all the various creative videos I have using multiple fx and videos together, because never could I have done any of that with a severely buggy inoperable software as powerdirector 21 is as I have experienced it. No, I will not jump through the various homework hoops that are so involved to the many bugs this version yet has that only beta testers should go through, as I never volunteered to be a beta tester, and opted to pay full lifetime price for a software release that is ready for release. Right now I would advise people to not buy the lifetime pd 21; check back again in a few months when cyberlink may decide to put out patches to make this a worakble version. At this point it is so buggy to be an early beta release for just the brave or technical-interested-geekers who like to aid in bringing versions to workable levels for all. No Joe-Public buyer should have to discover what he/she thought was a working version they paid full price for is a nightmare that will stop all their work at a time when no patches will be coming for weeks if not months at least.

This release isn't buggy, it's ultra buggy to the point of impractical. I do not like how cyberlink dumps such beta releases on the public as if they are ready to go, and then freshly puts same unsuspecting through demands that the more ethical companies will up front put notices out for volunteer beta testers, respecting their customers base enough to NOT deceive them beta-releases are stable releases. WIth all the sales out there, cyberlink should be able to do the ethical protocol of getting beta testers to jump the hoops on beta releases and be clear what is up for sale is not stable. Many persons use these for their jobs, and beta releases can cause serious workflow disruptions. No I am not going to stop my work to give support more than the 7 support ticket issues I reported since day one of getting this beta release, and just get their canned homework responses. I suspect they are fully aware this is beta and to work out the bugs will take some gathering of info. Well again I am not going to be one of the beta testers; I 've had one form or another of PDirector ultimate since 2014, and this is the worse of the worse not-ready-for-prime-time release I have had the misfortune to buy. My bad for not checking out first this was announced just this summer and too new.

So, like you I have NEVER had issues with simple edits before that it wasn't enough for me to just set to every 3 minutes back up, I simply had to abandon it because as time went on I encountered so many other issues that I could see it was too beta, too buggy to be still in experimental beta, and NOT ready for release, and seeing similar complaints and also just the homework responses from cyberlink. So I just wanted to add my me-too post here before I take the time once I complete my pressing project to get a refund on this lemon. I am just going to send Maliek a love tip when I do as I got it through his aff link, never before having such a nightmare wrestle with any previous powerdirector version releases as I have had since I regretfully took the plunge and got this early release of PD 21.

I have to add this: my refund was immediate. I had used paypal/cleverbridge and am pleased there was no haggle, no need to prove dissatisfaction, but instant process by cleverbridge via paypal to my credit card. So to any wanting to take the risk, you can see my example that you can/will get refunded if you find it doesn't work for you within 30 days of purchase as advertised. Personally I will check back in a few months, maybe a year for a stable release. Or maybe it may be cyberlink will admit that even if the hardware is right on those using Win 7, that PD 21 / 365 will not work properly on this version of Windows for those of us committed to keep their Win 7 64bit computers that will never have any microsoft updates to use as their preferred systems. Hopefully time will tell. When I see the refund in my ccards, will be sending Maliek a love tip as he is the reason I can use PD so well. I simply cannot sit around with a version too buggy that may or may not end up getting patched to be useful for me.
Quote



Thanks for your response. I tried all this and I'm still having the same issue. I'm still waiting on a response from cyberlinl tech support.


Same thing is happening to me. I got PD21 yesterday, and so far it has crashed several times. It cannot handle opening and viewing certain transitions like the paint, and it crashes when opening some fx. I only got pd21 to have the colormatch as I have been happy with my pd15 that has been crash free for years, stable. In order to finish my project I exported produced to pd15 as pd21 is not stable for me. I am running on a win7 64bit and not going to do any upgrading to any other win which I have on laptops.

If pd15 can handle all these things, and for the reason it was developed to point to get out the bugs, then pd21 needs more developing. I also cannot use any HD preview, yet I can run HD preview in PD15. Hope these bugs are worked out. At least I am glad that buying different versions does not override previous copies. This reminds me of my DAW mixcraft, the latest version just does not run anywhere as good as the 8, and so I keep using the older version.

And, as an aside, I had to change browers from firefox to another to post here, because clicking on forum links lead to tomcat.com / tomcat slash forum, could be apache but only happens on firefox.
Go to:   
Powered by JForum 2.1.8 © JForum Team