I also use PowerDirector 13. I seem to have problems rendering AVI files in Windows 10. I always get Error Code 3. Hopefully, this problem will be solved soon. I can render with other video files, though.

Members, please check out: http://forum.cyberlink.com/forum/posts/list/44734.page#231813
Dafydd

After installing the update 3130, problems rendering DV AVI files is preserved:

Error type : Video cut
Material type : Video
Error information : Unknown
Material filename : D:\Александр\Videos\Captures\DV1\scene'20050801 02.07.25.avi
Detailed information : EC_ERRORABORT ..\CES_Source\Src\CES_Engine\CES_MediaLoader.CPP:6805

Yeah, I'm still not able to render AVI files, either. Still getting Error Code 3.

i'm having issues as well. cant edit any AVI files. audio cut, video cut. i just got a prompt to update powerdirector and am still having the same issues with the new update.

Hi all

As Dafydd said earlier, this thread is really sharing problems with PD on Win10, and not a place where you're likely to get any help with your specific problems.

For those of you with AVI problems, other members can assist if you follow the steps outlined in this *post* and specifically attach sections A, B and J. It would also help if you used the Attachments box to upload a short sample video. If the file size is more than around 30MB, post a link to a cloud service like DropBox or OneDrive so the whole file can be downloaded and tested.

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°

Link to the clip with the bug, 02:37:00 minute.

https://yadi.sk/d/OysTDNw8iNnQW

Александр/Aleksandr, I have tried your clip in 3 different versions of PD on my Win10 desktop and all show the crash when the scrubber reaches 2:37:11. PD13 can play the audio from the clip after the error message, but it is not able to show the video and I have to restart the program to see the video.

I tried several things but couldn't get any of them to work, so this looks like a codec/compatibility issue. I don't have PD installed on any Win8.1 PCs, but maybe you could tell me if you were able to work with this clip before upgrading to Win10.

The real solution is for Cyberlink to fix this issue and issue a new patch, but the quickest solution is to pre-convert theese clips before editing them in PD.

I used the free FormatFactory program to convert it to MP4. The converted file is 1/4 the size and it plays perfectly in PD. I have a fairly powerful machine, and it only took 40 seconds to convert. Here's a *link* to the converted clip. Let me know if that works for you.

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°

Optodata, thank you.
On Win8.1, the clip was processed without errors.
In Win10, I use VirtualDup, with the option "Direct Stream Copy" and save the "Save old format AVI...". After that, the clip is processed without errors.

I'm glad that the converted clip works. Until a patch is released, I think that is the best solution for clips that cause errors on Win10 systems

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°

Thank you, Optodata. That worked for me as well! I use Fraps and everything is AVI..

I have been using Powerdirector since version 8 and have done over 500 projects and over 1000 renders. The problem I am having is I am unable to render to H.264 AVC. since I upgraded to Windows 10. I get a message saying it is an unsupported format. I have rendered under previous programs to this format with no problems. I shoot hd 1920x1080/60p and it is one of the two formats that allows me to render at 60f (I shoot at the same rate). The other format is the newer H.265 HEVC which is has better compression but when I do a render it just hangs there counting off time. It renders the first 188k and then stops. I have to quit program using Task Manager because there is no way back to the editor or any way to quit the program normally. It seems that the fast render option does not function under Windows 10. I can render out to H.265 HEVC if I don't use fast render but now my renders take 4 times as long and none of the media players I have can play the video portion of the codec. I can only do proper playback in Powerdirector 13. I am going to attempt to upload my first video to YouTube using the new codec and see if it works.

I had been using PD 11 Ultimate just fine on Windows 7 and it worked on Win 10 except for the render problems. I only upgraded to PD 13 to solve the render problem but it remains. The only thing I have gained is the new H.265 HEVC codec but I have lost the ability to render fast at 60f. That's not a good trade off. It's typical of todays technology when upgrades often are downgrades because things are broke. Back in the day this was considered a "bug" and bugs were to be fixed BEFORE release but now it's release and patch and things still don't work....even though we paid$$ for a full functioning product. Can you imagine buying a car and have some things not work like the power windows or locks or air con and they say bring it back in we'll fix it later? Hell no!

Unfortunately you are right and Cyberlink is not alone in doing this. Software developers have decided that customers should do the beta testing and pay for the privledge and thats why there is seldom any refund guarentee even if the software doesn't work at all!! I expect within the next few months and many patches this software will start to do what they advertise for the masses or they may just release version 14 and get us to hopefully pay for the bug fixes.

Quote: ...they may just release version 14 and get us to hopefully pay for the bug fixes.

In my opinion, I don't think that's the case. New releases of PowerDirector are focussed on introducing new features, which is the main motivating factor for upgrading. The previous release is usually actively supported with bug patches for many months after the newer version is released.

An example is when YouTube changed their API a couple of months ago, which caused PD's built-in uploader to break. Even though PD13 had already been out for almost a year (and obviously got a patch), Cyberlink still released a patch for PD12 to retore the ability to upload directly to YT from that nearly 2-year-old version.

Yes, the rate of patches slows down on any product when a newer version is released, but I wouldn't say that we're expected to pay to update just to fix various bugs. I'd also say that NLEs are very complicated to build, and Cyberlink has been really good at addressing the issues that are discussed on the forum.

I don't see users reporting problems necessarily as us all being being beta testers (or guinea pigs). For me, the bigger issue is what Cyberlink does with the feedback - and as long as the patches keep coming, I'm pretty happy.

Quote: I have been using Powerdirector since version 8 and have done over 500 projects and over 1000 renders. The problem I am having is I am unable to render to H.264 AVC. since I upgraded to Windows 10. I get a message saying it is an unsupported format...

I always produce to M2TS 1080/60p and I haven't had any problems since upgrading to Win10. Could you please refer to my post at the top of this page and start a new thread? It would also help if you could get screenshots of the error message and what your Produce screen looks like.

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°

I have spent the last several days continuing to isolate my problem. On the system that generated my problem report, I installed PWDR13 onto my Win10 installation, which had just been updated from Windows 7. Over the weekend I tried something different. I installed PWDR13 on my working, current WIN7 System and tested it. Not only did it pass all my test cases with flying colors, each file and ISO generation went very fast. I encountered not one failure on the five test cases (on your FTP site now), and continued to test it against several other project files created by PWDR9. In NONE of these tests did I experience any error or failure. I then cloned this same drive using Acronis and installed it into the same system that ran the original hard drive. I then upgraded the Win7 installation (with the working PWDR13 program) to Win10 and then re-ran all tests. Not ONE of the test cases that the Win7/PWDR13 ran flawlessly completed without and error/failure. Not one. I do not see how the files can be the problem as you suggest since the Win7/PWDR13 HD performed all test on those file. Can you please suggest a reason why the Win10 installation over Win7 caused the faults in PWDR13? Thanks, Paul

rickblaine - Just to be clear, nobody on this forum works for Cyberlink and nobody here has any access to files uploaded to their FTP site.

I assume that you're sharing a response here that you already sent to CL's tech support, and from what you've posted it doesn't seem like there's anything people here can help with


YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°

I had a project in PW 13 build 2604. All was fine. I upgraded to Windows 10 and then got an error that seemed like a codec issue. I installed QuickTime and DivX but it didn't help. I checked the PD 13 site and saw a new version so I upgraded to build 3130 but still an error. It has trouble reading most of my AVI files now. It lets me save some info in a file when it happens, but it's not a lot of info:

Media Source Error Report :
Error type : Audio cut
Material type : Audio
Error information : Unknown
Material filename : F:\Fraps\Raw\DSYT\KSP 2015-08-10 20-14-51-04.avi
Detailed information : ..\CES_Source\Src\CES_Engine\CES_MediaLoader.CPP:5777
Source filter GUID : E436EBB5-524F-11CE-9F53-0020AF0BA770
Splitter filter GUID : 1B544C20-FD0B-11CE-8C63-00AA0044B51E

NVIDIA GeForce GTX 760
Driver 10.18.13.5362

Does the error mean I am still missing some sort of driver update?

Quote: ... It has trouble reading most of my AVI files now.
Does the error mean I am still missing some sort of driver update?

Based on what other users have reported, it's likely that you'll need to convert the AVI files into another format to avoid this error until a patch can be released for PD13. Please see my earlier posts on this page for details.

YouTube/optodata

DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors

Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°

This may not mean anything, but if I remember correctly when you update, it downloads the update file and then installs the new one, BUT! If you still have a previous update file in the same save location it will act as though it updated but it will not. So, before you update, look in the save location to see if there's another 'update file' in there.. If so, delete it or any others before proceeding (You don't need the old ones anyway once you've installed them). This got me by on a previous update.

One way you can tell that this is happening is that the download progress indicator will go to 100% almost instantly. If you see this, you need to delete the update file that's already there.

Hope this helps someone.

Russell1967 System specs: Windows 7 Professional x64; Gigabyte Z77-DS3H motherboard with i5-3579K 3.8Ghz processor with 32GB RAM; Zotac GTX 760 w/4GB; 1xWestern Digital 1TB 10,000RPM HD; 1x Samsung 840 Pro SSD System Drive

15th-August-2015



Hi there,



We bought PowerDirector 13 a couple of weeks ago. Since the upgrade from Win8.1 to Win10 the software keeps on crashing down, voluntarily.

Also, when it still on, when I try to add clips from my camera or tablet, the software says that they are not supported.



I tried the patch for Win10 (downloaded and ran it) and it solved the audio issue only temporarily. Now it once again does not recognise video clips. I need assistance please.





Thanks.

R.C.N.Z. - I noticed the same sort of behavior and have a problem ticket in for a while but have gotten no response. From what I gather from the forum, PWRD13 has a problem processing existing AVI files in the Win10 environment. I'm hoping a fix is in the works but will not hold my breath.