Messages posted by rickblaine

BRAVO! GREAT JOB! I just performed the mods and have tested it on 3 test cases and have not gotten any errors. I'm now taking a more complex project, creating a file and ISO image which I'll use to generate a DVD. If that works, all's well. Optodata, you da man! Thanks for not only resolving the issue, but for taking the time to document the fix so well for us unfortunates. It's truly appreciated! As a secondary matter, is this a fix that Cyberlink can incorporate into a patch? Do you have some way to get this revelation to the Cyberlink engineers and tech support personnel?

My scenario is that I asynchronously take family movies of my grandkids mostly, and download the video from my camcorder into PowerDirector. This happens, say, once every month or two. And in case you're curious, I actually re-downloaded the last Mini-DV tape into PowerDirector13 on my Win10 HD, thinking, perhaps, the video downloaded by the former version was somehow suspect. When I did so, the results were the same. I've got about 80 existing 1-hour tapes in AVI files now. I also keep their respective AVI files and project files just in case I need to re-burn older DVDs (I have some that are well over 10 years old that have gone bad). I can't do that on my Win10 system and I get nervous about that.

I need the full cycle: import from my camcorder, edit, burn to disk/disk image/file.

Thanks again for bolstering my spirits on this. I'm naturally skeptical about CL 'almost certainly' working on a patch for this issue', given my experience with them over the past month. It's all I can hope for. If they aren't, I'm going to go back to Pinnacle Studio that I abandoned a few years ago for PowerDirector. Right now I feel like I'm in a quagmire. LOL Haven't felt like that since my Nam days.

Yes, when I try to do a production, I get the same message. I selected AVI, though. I forgot about it since I decided to concentrate on the Create Disk problem. I'm just trying to Burn Disks and with early repeated errors, I decided to just try creating a disk image (ISO) and/or create file instead of burning directly to disk (which never worked either, but I was out a disk). By the way, I fast forwarded through the file in Edit mode and got no errors. Likewise when I played the AVI file with the new hokey Win10 player, so if the file's bad, the player in Edit and the Win10 player don't notice it. Most curious, eh?

LOL. I just had to chuckle when you asked me if I could "list the specific steps that reliably cause a crash or error message", Optodata. No matter what I do I can reliably cause an error message. Seriously, though, I bring up a canned test case project that does nothing more than import the video file. I then go from Edit to Create Disk. I then click 'Burn in 2D' then select either 'Create a Folder' or 'Save as Disk Image' (the results are always the same: an error message stating:
Media Source Error Report :

Error type : Audio cut
Material type : Audio
Error information : Unknown
Material filename : F:\DEBUG\AVI Video Files Test Cases\Test Case 2\T77S-GarySchoolPlay26Jul15.avi
Detailed information : EC_ERRORABORT ..\CES_Source\Src\CES_Engine\CES_MediaLoader.CPP:6805
Debug information : EC_ERRORABORT ..\CES_Source\Src\CES_Engine\CES_MediaLoader.CPP:6805
I have to admit, I never get a program crash, just the error message. Sometimes it goes to 35%, sometimes to 50%, but it always produces the same type of error message.

Looks like I've got some kindred, i.e., elderly, spirits here. I can remember when my Penn State instructors told us we should be thankful for Assembly language, because it was not so long ago that he had to program in 'machine language'. Punched cards were a way of life even when I worked aerospace for TRW in the early 70's. AIS, I should have known better than to think I could switch my primary machine to Win10 prior to SP1. I personally think Win7 was the best and most stable Windows Microsoft ever produced. As I said earlier, my Win7 machine runs EVERYTHING, even PWRD13. I can't say that for my WIN10 installation.

Thanks again for the suggestions, optodata. I uninstalled the Asus AI Suite III and AVG Antivirus program but got the same error indications, and am thinking the DxDiag reports past issues as well as current ones. I performed the system scan before but I did it again just to make sure. As before, it showed no system errors (see attachment). I'm hesitant to try a beta build of Win10 at this point (to reduce the number of 'moving targets'), but I may if nothing else works. Regarding the video driver for my Asus Z97M Plus MoBo, the Asus site says I've got the most current Win10 driver installed now. When I downloaded the latest Win10 driver form the Intel site and tried to install it, the install apparently completed without errors, but after the mandated reboot, I see I had the same Asus-provided driver as before. When I ran the Intel tool, it said it couldn't find any Intel video drivers on the system, adding that MoBo manufacturers supply their users with Intel drivers under the Asus auspices and it may not show up on their tool (which it apparently didn't). I've never used OneDrive before, but I think I'm uploading a test AVI file now. Please let me know if you get it in your OneDrive. Regards, Rickblaine

Thanks for the words of encouragement, Optodata, but it's difficult to be optomistic given the support I've been provided so far by Cyberlink. I'm attaching the DXDIAG report I regenerated this morning. I sent one to the Cyberlink guy that requested it early on, but I got no comment on it. I'm not sure how to provide the AVI files. They are quite long and it even took a while to upload them to Cyberlink's FTP site. I sent 5 test case AVI files along with the resulting error messages, and got NO feedback on them from Cyberlink. The problem, I'm certain, isn't with a single AVI file because I can't find any of the 10 or so I tried with the Win10 HD that did not generate a premature error message. As I said, all of them worked fine on the Win7/PWRD13 HD. As a retired computer professional, it appears to me that there's a problem with the interface between the Win10 system software (including video adaptor driver) and PowerDirector 13, but I can't seem to get Cyberlink to investigate that angle. The AVI files, by the way, play well outside of PWRD13, so I believe PWRD13 is involved in the problem. Again, thanks for the words of encouragement.

I'm getting extremely frustrated with Cyberlink's PowerDirector 13 support (so-called). Today I inquired what the status of my problem's 'escalation'. I reminded them that PWRD13 runs fine on my Win7 HD, but when I clone that HD and immediately upgrade to Win10, I get failures on AVI files that worked flawlessly in the Win7 environment. The response I get is the same one the offered before: just convert your avi's to some other format. This is not a workable fix because I have TONS of avi's (that work fine under Win7) and don't feel I should have to convert them, and (2) Does not answer why they don't work in my Win 10 environment. The only difference in the two systems is the OS's and Win10 driver updates made as part of the OS switch. Is anyone else out there getting the same 'canned' responses to real questions? Sorry for the rant, but I'm getting no help from Cyberlink, which is holding up my actual switchover to Win10.

I believe it's a free update for a year, but only for Win7 and Win8 users (I wish it was for Vista!). And you have 30 days only to roll it back, though I should add that my friend tried to do so and it didn't work, screwing up both the Win10 AND his old Win7 installations. Proceed with caution.

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.

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

I'm at my wits end with using PWDR13 on my Win10 machine. Reading someone's forum comment regarding the need to update my Intel HD Graphics 4600 driver, my hopes were up, as the version cited was not the Win10 version I downloaded from the Asus site a few days. I was confident that the new driver would solve all my problems, and for a brief moment, I thought it did. Although I could not create a file or ISO image for my test case projects every time (About 75% of the time did I not get the dreaded error message), I soon found that the ISO images and output files did NOT generate good DVDS. Instead, the root menu and the first chapter recorded fine, but the other chapters were absent. I think an indication of this was the progress bar jump from about 60% to 100% complete in an instant, with no error message. So, in summary, I'm trading one problem in for several. I began to construct test cases again to ascertain the scope of the problem, beginning by building a new project with the same video files. In doing so I made the following bewildering observations: When I imported the existing .AVI file (captured from my Sony Camcorder with my PWDR9), I got the following popup warning message: "Selected file contains no RichVideo information to display scene information. Do you want to generate it now? It may take a few minutes to detect the scenes of the video". I clicked 'yes' and it took only a second or two to see the .avi files on my timeline. The other think I found strange was that there was no 'Date/Time' icon like there had been on the files when I was using PWDR9 on my Win7 system. I'm not sure how these 'clues' relate to the source of my headaches. Lastly, when I successfully generated an ISO file and burned it to DVD, I found that this 'virgin' test case (with legacy .avi files), showed the menu and played the first chapter only, the others non-existent. In summary I'm pretty bummed out with PowerDirector 13. It may not specifically the design of that software that's making my life miserable, but I can't help notice that my over-100 legacy applications are functioning flawlessly. As I said, I'm pretty bummed out. Can anyone suggest a course of action from here? I'm not even sure how to bring up this problem to Tech Support, when they haven't been much help to date. Regards, Paul

Thanks for the suggestion, but it appears MediaInfo - the version in the link you provide in Part J - appears to not work in Windows 10. When I double click on the exe file, it comes up for an instant and than disappears. I can trim an .avi file to 5 seconds. Where do you want me to put it?

For years of error-free video editing using PowerDirector 9 in my Win7 environement, I decided to update to Win10. I then found out that my beloved version 9 was incompatible with Win10, so I purchased PowerDirector 13 and installed it and the lone update to same. When I tried to process version 9 projects on the new system, I ran into problems. I tried numberous existing projects and found NONE worked on the new system. Trying to isolate the source of the problem, I created new projects using only legacy video files (.avi), thereby eliminating errors due to menu font changes, etc. These also failed early in the file creation process, so I didn't even get to the DVD burning state. I continuted my investigation by capturing selected files again from my camcorder again, but these yielded the same results (failure/errors early in the process). I next tried to Produce a file from several of these .avi files, but these again resulted in the same kind of failures. To eliminate the possibility of software conflicts, I took the time and laborious effort to do a clean install of Win10 on a formatted HD and then doing a clean install of PowerDirector 13 and it's update. I was surprised to see that all of my test video files failed in both the Produce and Create Disk (create ISO and file) steps. I considered perhaps a system issue, but, again, it's the same hardware platform I've been using successfully with Win7 and PWDR13 since I built it 6 months ago. It's got plenty of RAM (16G), a stable MoBo (Asus Z97M Plus), and a fast processor (4G Intel i7). I doubt hardware is the problem. My tentative conclusion is that there is an enherent incompatibility between .avi file processing in a Win10/PWDR13 environment. I contacted web-Tech Support and set up folder CS001392828 on their FTP site, and created 5 subfolders, each containing debug data for Test Cases 1-5. This debug data contains the test case PWDR13 project file, a screenshot of the failure screen, a detailed problem txt file (generated by PWDR13), and the subject video files. Again, these were simple test cases with no special effects, transitions, or menus. As yet I haven't heard back concerning investigation of these test cases.

I'd like to hear other PowerDirector users that are running it on a Win10 platform to see if they're having similar problems. As a retired Computer Scientist, I'm troubled that I'm having so many problems running legacy project files on Win10, and will be relieved when a resolution is determined.

Zimbietom, please advise when you've tried processing legacy projects in the Win10 environment. As I've been saying, I even went to the trouble of reinstalling a 'clean' copy of Win10 with PWR13 being the only app (to eliminate any software conflicts), and I still got error messages just processing my old .avi files.

Sure, I'll start a new topic, but I thought the topic was 'Windows 10 Compatibility and User Problems'. How do I start a new topic covering my problem? I see no 'button'
or menu items I can use to start a new topic?

I have been using PowerDirector 9 very successfully with my Windows 7 and 8.1 systems for years. Since I upgraded my primary Windows 7 system to Win10, I found it was incompatible with PWD9 and so purchased PowerDirector 13. That was about a week ago. Upon installing the new version as well as the update successfully, I tried to open projects I created in PWDR9. To make a long story short, I could not fine ONE old project that would allow me to produce a file or burn a file with the new version. In each instance I get the same obscure error message. I've had to contact tech support via Cyberlinks innane tech support website and have been frustrated every since. For one thing, there's no way to just 'reply' to an existing incident, which I had to do to request clarification on the support person's obscure directions. Each time I have to request assistance again, I have to go through the same long form that requests the same information (CD key, SR number, OS, error dropdown, etc. etc. Do they do this to push us poor users to pay the $30 for phone support? In any event, after 4 frustrating redundant responses to my specific requests for clarification, I'm at my wits end. Is there any way to complain to a Cyberlink supervisor? I have little confidence this online support will solve my problems.