Hi nogero

It's not entirely clear from your description whether PD13 ever worked for you (but is now broken), or if you're talking only about PD11 when you describe the way you've always done things.

The error messages you described seem to be the result of a corrupted install and your clips aren't the issue, so please follow the steps in this *post* - especially parts A (if you can get PD to open) and B. That will give us lots of details to help figure out what's going on.

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°

HI,
I agree with what optodata has posted and asked for. I'd also suggest you uninstall PowerDirector 13, reboot and then reinstall PowerDirector 13.
If you've purchased an upgrade, go for a PDR13 install and have the PDR11 key available when asked and later the PDR13 key to activate 13. Apply the latest patch 2907.1 after the activation.
Dafydd

I supplied the info requested on the first support form, including my product key, diagdx.txt, SRN number etc. I am a REGISTERED, PAID (twice) USER. I bought it ONLINE direct from Cyberlink (twice), downloaded it. So support emails me back a rejection asking that I take a photo of the CD's. I never got CD's.

I am pretty sure I got PD13 working after initial install and made a few videos. (Eyeball asked that)

Info: SRN number: VDE150529-01

File I downloaded (from your provided download link): 1_CyberLink_PowerDirector13_Ultimate_Upgrade_VDE140925-01.exe . I also downloaded the Patch and applied that. Both installed without any known errors.

Here is DxDiag64.txt attached ( I have Windows 7 Pro 64 bit)

It appears to load up and edit OK, but the moment I click "Produce" it crashes with error message (attached)

I noticed: If I just insert fewer video clips, tested 7, it worked OK. If I insert 42 10-second avi clips (same files) it crashes. So it might be a resource/memory issue. But I have an i7 with 24GB memory.



Does that help?

Thanks for the details. Please know that we are all volunteers and have no access to anything you may have sent to CL Tech Support, so I'm sorry that you've had to do some things twice.

Overall, your system looks to be in good shape, but your video drivers are almost 2 years out of date! Please visit nVidia.com and let the automatic detector present you with the correct driver. You can also download it manually by clicking *here*

When you install the new driver, please choose Custom Install and ONLY install the graphics driver. Also check the Clean Install button to remove your existing driver first. You may need to reboot, and then test that out to see if anything changes with the error messages.

I think it would also help if you could post a sample of your source clips. The attachment limit on the forum is about 30MB, so if your clip is larger than that, please post a link to a cloud folder like OneDrive or DropBox. That way we can see if there might be something problematic with the clips.

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°

OK, thanks for volunteering. It is frustrating (as you can imagine) since my overall experience has not been good. Overall I have installed/reinstalled 4 or 5 times now. Downloaded it twice over relatively slow connection.

But this latest dicovery is probably important: It will do fewer clips of same source clips without crashing. I need to use 42 10-second clips on this one and that is when it crashes.

Sorry if I seemed grouchy. I got grouchy after collecting all that info for support and have them email back asking for it all over again plus "photos of Cyberlink CD's". Obviously they didn't even read it. I sent them back copies of my purchase emails invoices anyway (that is all I got).

Here are some source clips. Don't be shocked: all the subjects in cli[ps are not wearing any clothes.

Three clips included.

I completely understand.

Thanks for sending over the "nudie" clips. I'm pretty sure you haven't broken any forum guidelines by posting, and I'll try stringing together 10+ clips and see how my system behaves.

In the meantime, have you had a chance to update your nVidia driver? Let us know whenever you have some news.

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 updated video drivers. It made no difference. Same errors.

OK. First, you're now up to date as far as your video driver is concerned, so that's a good thing even though it's not the cause of the crashes.

That honor belong to your clips. When I tried to load them into my timeline, I got lots of Media Source errors - so many that I couldn't even preview the clips.

What this is looking like is that you'll need to convert the clips into a more compatible format before you can work with them in PD13.

There are plenty of paid and free video converters available, and I used an older version of FormatFactory to convert them all to MP4 in 6 seconds. I was then able to load the clips 10x each on my timeline and produced the video without any problems. It took 3 minutes to produce the 5 minute video to 1920x1080/30p WMV.

I'm attaching the converted clips for you to test. Hopefully that's going to solve your issue and not be too much of a burden going forward.

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 think the upload to forum may have caused problems you are seeing I noticed upload to forum took a long time. I've never had this problem before, and doesn't conversion to mp4 reduce quality?

I've done clips from that camera lots of other times.

Here's a video of those clips: https://youtu.be/IHauhVxEbq4

Here is a raw clip from same camera, but youtube has probably converted it: https://youtu.be/yOj0nmqMOjg

CL made this batch OK: https://youtu.be/zCr7ZzBbmJU

I'll post some links to raw clips. It doesn't make any sense that I've done this many times with same camera and now get crashes.

Here are links to RAW clips I uploaded to Google Drive:

https://drive.google.com/open?id=0B0SYl04MZYEPY2hNamtsSTQxVGs

https://drive.google.com/open?id=0B0SYl04MZYEPYl9USTRCcjg0TW8

https://drive.google.com/open?id=0B0SYl04MZYEPdUpGQjBHaHB1YW8

https://drive.google.com/open?id=0B0SYl04MZYEPLXIwZGtCSzhZQms

The results are the same with the versions you uploaded to Google Drive. Storing and retrieving the clips from different locations wouldn't change anything about the clips as long as the entire clip gets up- and downloaded.

Sorry, this got posted too early. I'm typing my full response now...

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°

Please test the clips that I sent over. That will tell you right away if the issue is related to an incompatibility between your current setup with PD13 and these clips. We can work on why the incompatibility is there and/or where it may have come from once we know if the converted clips solve the problem or not.

Again, you said that you've done this many times before with this camera but I can't tell if that was only with PD11 or with PD13 as well. It's very important to realize that they are two completely different programs and even though they "should" both be able to work with the same clips, that isn't always the case, so my goal is to understand when things stopped working for you.

The most natural point would be when you changed to PD13. If you were able to make some videos initially after installing PD13, was it because you were using fewer than 10 clips, or were you able to produce longer videos at the beginning and then one day the crashes started? I'm trying to help you track down the moment when the problem appeared, and then we can focus on what might have caused the problem and/or what some fixes or work-arounds might be.

Another thing that comes to mind is that you might have installed some software that came with your camera, and that might have installed some codecs (coder/decoder drivers) that would allow Windows to correctly read and play those clips. I might be seeing these errors on my system because I don't have the codec installed and you might need to remove and then reinstall that software now that you're using PD13.

Let's take this one step at a time and see what we can come up with. My goal is to solve the problem permanently so you won't have to waste any more time on this once we have a solution.

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°

Hi optodata & nogero,
I have only downloaded the "EK000257.AVI" and it plays fine in PDR13 for me.
I don't have anything "special" re codec packs or anything.
I'm just scratching my head and pondering (reading what optodata posts )
Dafydd

I've only had PD13 a since May. I'm certain I've made videos with it. I don't have any camera software added. I tested a different batch of 28 clips and it worked. So maybe there is something wrong with those clips though I don't understand why. Other programs I've used tell user when it hits a bad video. On PD13 I got all kinds of errors about components not loading, need to reinstall, and old video drivers...almost random.

I finally used Microsoft Movie Maker to make the exact same video of 42 clips, no errors.

Many thanks to you volunteers. I never heard back from CL support.

Dafydd, thanks for the additional info as that may help rule out any specially-installed codecs as the issue. nogero, I don't think we're dealing with any "bad" video clips - that's usually something that's damaged or corrupted. We're talking here about an incompatibility issue, where one program isn't able to correctly understand all the data contained in the clip and ends up crashing.

I should have said that I tried playing the original clips on 5 different players on my Win 8.1 system and every one could play the clips without any problems. I also just tried them in PD12 and everything worked fine, so at least the issue the I'm having is clearly related to PD13.

It's even possible that my problems are completely unrelated to the problems that nogero is having, and that's why it would really help to know if the error messages still occur with the converted clips. It would also help to see if putting 10+ clips and producing in PD11 is successful. Each of those answers will point us toewards a solution and away from speculation.

Also, there may be a clear benefit in pre-converting the clips before importing them into PD even if they're not causing the problem. When I produced 10 sets of the converted MP4 versions of the 3 original clips, PD13 finished in 3 minutes. However, when I did the exact same thing in PD12 but using the original AVI format clips, it took over 11 minutes to produce the same results.

It's pretty hard to argue with the time savings of 6 seconds to pre-convert all the clips plus 3 minutes to produce vs. using the original clips and then taking 11 minutes to produce. Food for thought!

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°

Hi nogero and optodata,
The error message can be triggered by the audio as well as the video section of a clip, so maybe looking at the video is incorrect. The clashing/overwritten feature (video import/recognition) of PDR13 may be caused by a audio software player or program.
I realise this is going to be a really basic instruction and I have to state it (and apologize for doing so to ). How about doing a complete re-install of all of PowerDirector 13 including Smartsound and QuickTime.
Doing so will over-write and re-install/making PDR13 and components dominant.
For the record, I would
Uninstall via the Control Panel all three programs.
Re-boot/restart one's computer.
Re-install PowerDirector 13
Apply activation key for PDR13.
Apply the latest patch, in this case it'll be 2907.1

Dafydd

Thanks Dafydd, CL support finally contacted me and that is what they said I should do, a complete remove/reinstall. I'll try that later.

Hi nogero,
What's the situation now?

Hi optodata,
Just a correction. I noted recently (an update reminder), I do have DivX on my system and that might have some baring, opening the avi's.

Dafydd