If you didn't run Windows 11 insider build but a stable released Windows 10, I think the latest version of powerdirector would not crash like crazy.

Yes, the new version claims it supports windows 11, however there is still not a stable version of windows 11 out there, neither the drivers for related hardware. Just like any new pc you bought today, it will be labelled with "Windows 11 compatible/upgrade-able", but they are still not installed with windows 11 insider preview version.


It doesn't really matter how your setup works so great with all other software. The OS version you installed is still an insider preview release., and if this windows 11 version was so perfect, it wouldn't name itself as "insider preview release or version".

Try the new powerdirector on a Win 10 PC, and see if it works smoothly.

Quote
If you didn't run Windows 11 insider build but a stable released Windows 10, I think the latest version of powerdirector would not crash like crazy.

Yes, the new version claims it supports windows 11, however there is still not a stable version of windows 11 out there, neither the drivers for related hardware. Just like any new pc you bought today, it will be labelled with "Windows 11 compatible/upgrade-able", but they are still not installed with windows 11 insider preview version.


It doesn't really matter how your setup works so great with all other software. The OS version you installed is still an insider preview release., and if this windows 11 version was so perfect, it wouldn't name itself as "insider preview release or version".

Try the new powerdirector on a Win 10 PC, and see if it works smoothly.

This build is very close to RTM so I highly doubt that's the issue. Especially since the prior version worked without crashing incessantly. Looking around this forum, others are having issues with other things. This program now has a serious problem and the devs are taking too long to fix it. I have an upload schedule to follow and can't get anything out now because it keeps crashing.

This message was edited 3 times. Last update was at Sep 17. 2021 17:21

I'm running the latest build of Win11 and PD365 is running like a boss!

Quote I'm running the latest build of Win11 and PD365 is running like a boss!

Not for me, crashes every single time I put an H.265 file on the timeline. Doesn't do this for h.264 so now I have to transcode every single one of my videos to h.264 until this is fixed which I doubt it will ever be. I should make a YouTube video shaming the sh*t out of these people but then by doing so I run the risk of people knowing what software I use.

This message was edited 2 times. Last update was at Sep 17. 2021 17:23

I also have 365 on two Win11 PCs and haven't had any crashes. Your DxDiag shows that your Intel iGPU driver is more than a year out of date, so maybe try the latest OEM version from Intel that's built for Win11. You can download it from here.

There are also indications of Windows stability issues in the WER reports at the end. These kinds of issues usually point to problems with Windows' core system files, and often running the two commands in this post will solve the issues. This is often enough for PD to run properly afterwards.

Finally, if you continue to have problems with H.265 clips try dragging it onto the MediaInfo online page then save the text results and attach them here.

Also, if you're comfortable sharing a sample clip, upload it to OneDrive or Google Drive and paste a publicly shareable link to it here and other people can see if they see the same issue on their systems. See this FAQ for more details.

Quote I also have 365 on two Win11 PCs and haven't had any crashes. Your DxDiag shows that your Intel iGPU driver is more than a year out of date, so maybe try the latest OEM version from Intel that's built for Win11. You can download it from here.

There are also indications of Windows stability issues in the WER reports at the end. These kinds of issues usually point to problems with Windows' core system files, and often running the two commands in this post will solve the issues. This is often enough for PD to run properly afterwards.

Finally, if you continue to have problems with H.265 clips try dragging it onto the MediaInfo online page then save the text results and attach them here.

Also, if you're comfortable sharing a sample clip, upload it to OneDrive or Google Drive and paste a publicly shareable link to it here and other people can see if they see the same issue on their systems. See this FAQ for more details.

Did everything suggested and still... CRASH!!! 💥💥💥

Actually you haven't shared a sample clip. MediaInfo shows that there are two embedded streams and it's possible that the 2nd stream is the issue.

Quote Actually you haven't shared a sample clip. MediaInfo shows that there are two embedded streams and it's possible that the 2nd stream is the issue.

Nothing I can do about it recording two different streams, have no idea why it does that actually. In the process of uploading a file now. It's going to be different from the one in mediainfo but they all cause the problem. Only workaround I have now is to set my camera to record h264, but that does nothing for the tons of GB I have in h265 to produce. I will have to transcode every single one (with a different program like handbrake or else 💥💥💥) or just go back to PD19 until they fix this 💩💩💩 program! I got the video I was trying to release today out, but again only after transcoding to h264.


EDIT

here's a sample file

https://drive.google.com/file/d/1NOA-UlwFSUNGROKfxjecl8uuoK-7Bhzf/view?usp=sharing

It's definitely the clip. It previews without any problems in the media library but PD365 crashes once I place it on the timeline and the preview screen image first appears. BTW the second stream is for low quality streaming/previewing, but the clip plays fine in PD13, 14 and 17 (and PD19 as you'd seen) so it's clearly something specific in the new version that they'll need to fix.

For fun I tried switching between Stereo and 5.1 Surround sound; turned OpenCL and Hardware Acceleration on/off; changed the timeline preview color space from RGB to YUV; and even used the Precut tool so the timeline clip wouldn't start at the very beginning but the crash still happened.

Then I switched to non Real-time preview and everything worked! (Note that you have to have some timeline content before you can switch the preview mode).

Muting the clip and switching back to Real-time preview caused a crash. While in non Realtime mode, I could unlink the audio and delete it, and when I switched PD back to Real-time mode everything was fine. This issue is clearly with the audio track.

If you have AudioDirector, you can right-click on the timeline clip in PD and choose Edit Audio. Make literally any change (like boosting the level by 1dB) and the resulting .WAV file that gets sent back will work perfectly. Here are the steps:



If you don't have AD, using Handbrake or another free app to simply transcode the audio to .wav should do the trick. This should also be very quick since the video stream(s) don't need to be changed at all and that should get you through your backlog until CL can patch the issue.

Make sure you report it directly to tech support from this page.

Quote It's definitely the clip. It previews without any problems in the media library but PD365 crashes once I place it on the timeline and the preview screen image first appears. BTW the second stream is for low quality streaming/previewing, but the clip plays fine in PD13, 14 and 17 (and PD19 as you'd seen) so it's clearly something specific in the new version that they'll need to fix.

For fun I tried switching between Stereo and 5.1 Surround sound; turned OpenCL and Hardware Acceleration on/off; changed the timeline preview color space from RGB to YUV; and even used the Precut tool so the timeline clip wouldn't start at the very beginning but the crash still happened.

Then I switched to non Real-time preview and everything worked! (Note that you have to have some timeline content before you can switch the preview mode).

Muting the clip and switching back to Real-time preview caused a crash. While in non Realtime mode, I could unlink the audio and delete it, and when I switched PD back to Real-time mode everything was fine. This issue is clearly with the audio track.

If you have AudioDirector, you can right-click on the timeline clip in PD and choose Edit Audio. Make literally any change (like boosting the level by 1dB) and the resulting .WAV file that gets sent back will work perfectly. Here are the steps:



If you don't have AD, using Handbrake or another free app to simply transcode the audio to .wav should do the trick. This should also be very quick since the video stream(s) don't need to be changed at all and that should get you through your backlog until CL can patch the issue.

Make sure you report it directly to tech support from this page.

The extract audio option also does the trick. This will definitely help. Especially with the road tours videos that I make where I just take all the sound out entirely. Still mindboggling why they don't test these things before selling it out to people.

Quote The extract audio option also does the trick. This will definitely help. Especially with the road tours videos that I make where I just take all the sound out entirely. Still mindboggling why they don't test these things before selling it out to people.

You're welcome. I'm sure they did test things out but there's no way to test every possible combination of hardware, OS and video clips.

Years ago they had a few experienced forum users do some beta testing but that hasn't happened recently to my knowledge.

I've been experiencing the exact same issue. I suspect other folks out there are encountering it, too.

Without getting too much into the weeds, this is my abbreviated story:

I often edit footage captured from home security cameras. The process is anything but complicated: I extract the clips from the camera's SD card, save the clips to a folder on my PC (Windows 10), and then happily edit/produce in PD. I've been doing this since the summer of 2018, using PD versions 17, 18, 19 and 365.

I have NEVER (not once in 3~ years) had any issues with my process...

Until now... After “updating” to the latest version of 365, PD now crashes EVERY time I drop a clip into the timeline. Not cool. Not acceptable.

And no. I'm not OK with having to implement additional steps to remedy an issue that did not exist in multiple previous versions of the same software.

If Cyberlink does not fix the issue soon, I'm dumping the software and moving on to something else. I don't want to take such extreme action, but if the software no longer works for me (as it once did), I don't feel that I have a choice.

Quote

You're welcome. I'm sure they did test things out but there's no way to test every possible combination of hardware, OS and video clips.

Years ago they had a few experienced forum users do some beta testing but that hasn't happened recently to my knowledge.

Yes. Ever since PD 17 / PD365 the good old days of beta testing are a thing of the past.

Quote


Yes. Ever since PD 17 / PD365 the good old days of beta testing are a thing of the past.

Because they are now using us paying customers as alpha testers. This version of PD should not have been released. Even with the solutions mentioned above. I still had a tremendous amount of trouble producing this video:

https://youtu.be/Xrau3EJrJig




I was still able to get it out with the same amount of talent as my other videos but I couldn't make an adjustment that I needed to as a result of the frequent crashing.

I noticed the same thing when I opened up 365 the other day. Doesn't matter what file I use in the app, whenever I change from one aspect of editing to another it crashes. Want to add a PiP object, it crashes. Open the project back up and it works ok to add the PiP object (saving the project each step of the way of course), but when I go to add a transition or switch to anything else, it hangs and then crashes. Doing this like clockwork. Runing Win10, 32GB RAM, and while I've had the odd crash from time to time in the past, it's not been as detrimental as this one has been. It seems like the overhead has increased in the app with slower response time in this update, which does not feel stable. It's very frustrating when working on a project that I am trying to get done. Hope they get this patched asap.

Quote I noticed the same thing when I opened up 365 the other day. Doesn't matter what file I use in the app, whenever I change from one aspect of editing to another it crashes.

OP's crash was caused by a specific type of media clip. Yours is almost certainly caused by something else and it would actually be better if you started a new discussion specfic to your issue.

Please view the Read Me Before Posting guide and provide the requested DxDiag test results so forum members can better assist you.

Quote I noticed the same thing when I opened up 365 the other day. Doesn't matter what file I use in the app, whenever I change from one aspect of editing to another it crashes. Want to add a PiP object, it crashes. Open the project back up and it works ok to add the PiP object (saving the project each step of the way of course), but when I go to add a transition or switch to anything else, it hangs and then crashes. Doing this like clockwork. Runing Win10, 32GB RAM, and while I've had the odd crash from time to time in the past, it's not been as detrimental as this one has been. It seems like the overhead has increased in the app with slower response time in this update, which does not feel stable. It's very frustrating when working on a project that I am trying to get done. Hope they get this patched asap.

Hello,

As Optodata suggested, your issue is most likely caused by something completely different. So because of that, please start a new thread so it can be worked out there. Please include the requested information and also contact CyberLink Technical Support about your issue: https://membership.cyberlink.com/support/service/technical-support.do

Since CyberLink QA is looking at the cause of the OP's crash, and he has figured out a temporary workaround, we will close this thread so it can be a future resource and also not complicate the thread with unrelated crash issues.

OP: Please feel free to start a new thread once you hear back from CyberLink Customer Service and have an update about the issue.

Cheers
PowerDirector Moderator

Hello,

This issue appears to have been fixed in the latest update to 20.0.2204. The OP's video works without issue now when added to the timeline.

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