http://www.cyberlink.com/products/powerdirector/requirements_en_US.html

Look under Hard Disc Space.

I don't know if that's the problem but, if it was me, I'd being having a clean up!

Cheers - Tony
Visit PDtoots. PowerDirector Tutorials, tips, free resources & more. Subscribe!
Full linked Tutorial Catalog PDtoots happily supports fellow PowerDirector users!

Another test I tried was to remove al special effects like colour balance, enhance and noise reduction. The problem still occurs during render.

I think its obviously something to do with the AVCHD encode process as outputting to a DVD file worked fine. I can't see it being the hard drive space as I've cleaned up bits and pieces and then re-encoded again but it always gets stuck at the same point.

Lee -

Have you tried producing it in smaller sections... then putting it together. I don't know the details of what's in your project.

I wasn't sure that HD space was the issue at all - clutching at straws.

What system are you using? Did you say before? I can't remember.

Cheers - Tony
Visit PDtoots. PowerDirector Tutorials, tips, free resources & more. Subscribe!
Full linked Tutorial Catalog PDtoots happily supports fellow PowerDirector users!

I havent tried that to be honest although it would be an absolute pain in the backside to do. The project contains AVCHD video, MP3's, Still images, Smartsound quicktracks, PiP tracks and transitions

The render stops before any of this though. It sucessfully navigates past the first MP3 track and then crashes at the start of a transition on a clip which has no processing (i.e. no colour fixing or enhancement). This is always 4 minutes and 33 seconds into the movie.

System is a 3ghz Quad core Intel, 4gb RAM with a Geforce 8800GT GPU

Hi Lee, this has a feeling of Deja Vu for me - it was this kind of problem that I always had with PD8. I too only processed AVCHD/m2ts files AND have the HD9 version of your Camera.
The only solution I ever found was to remove all the transitions from the work I was doing to get it all to render.
The guy's have given you all the "standard" solutions, but the problem is I think a fundemental one in PD8 which the cure for, we hope, will be in the next release of PD8 promised in the next 4/8 weeks. Currently I have stopped using PD8. The real puzzle on this is that many members of the forum have no problem with PD8. There is a cure available for Sony Vegas which I think IS applicable to PD8 which involves the use of CFF to change the dll headers to enable them to handle larger memory. Take a look at this link - http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=671862 . I dont currently have access to a copy of PD8 but this has been tried by one other member and he says it works worth very well.

Good Luck Don Gigabyte I7/4940 O/C 4.3, Noctua Cooler 10GB DDR3, 4 x 1TB, 1TB SSD, Geoforce GTX660 TI 8500W PSU, Windows 10 Pro 64bit.

Hi Donald,
Excellent bit of information. Thank you.
Dafydd
[Moderator]

Thanks guys. I'm going to give this a go and see if it helps at all.

can anyone tell me what DLL's and EXE files i should alter? I'm also going to try the fix on Video Studio as well to see how it effects performance.

Lee

One more thing for anyone reading that thread: Do i have to be running a 64 bit version of windows or can I try the fix on a 32 bit version?

Good one Don -

I don't think I have confidence to go messing with those files (even with a backup), but it does appear to have sorted out the same sort of problem in Vegas.

Thanks for posting. I wonder if CL R&D is onto this.

Lee - couldn't advise you on this - out of my league - but good luck

Cheers - Tony
Visit PDtoots. PowerDirector Tutorials, tips, free resources & more. Subscribe!
Full linked Tutorial Catalog PDtoots happily supports fellow PowerDirector users!

Upon investigation those files are specific to Sony Vegas so I'll need to figure out the encoder DLL's in PowerDirector and VideoStudio as the encoder woudl be part of the package rather than with an additional codec pack.

I'll update with my findings but please keep the suggestions coming.

Hi all,

The workaround that Donald has raised is one I came across when using Vegas in my pre-PD8 days - and on implementaion it worked like a charm.

How we go about doing something similar to PD8 is a mystery to me too I'm afraid.

Cheers,

Andrew

Alienware Aurora ALX R4 - Intel i7-4820 4.2 GHz - 32GB DDR3 RAM - Crucial 512GB SSD - 1TB Seagate HDD - 3TB WD Green HDD - 4TB WD Green HDD - MSI NVIDIA GTX 1070 8GB

Sony HDR-PJ810 and HDR-PJ530

I had a quick look last night and theres a folder called compile (i think from the top of my head) so i'm assuming that contains the DLL's needed to do the compiling. Its going to be a trial and error process but i'm going to set most of them to more than 2gb memory and slowly reduce the amount of files that has the tickbox and see where we go.

for anyone who has had this problem, can you tell me how much memory your system has?

Hi Lee,

I was going to try and download a trial version of PD8 but I am not sure it will allow me to (having once been a user) - so you may be n your own in finding which elements of the app you need to modify - sorry.

Don Gigabyte I7/4940 O/C 4.3, Noctua Cooler 10GB DDR3, 4 x 1TB, 1TB SSD, Geoforce GTX660 TI 8500W PSU, Windows 10 Pro 64bit.

Well, first thing I have done is upgraded to Windows 7 64bit. no change with rendering on that part. Crashes at the exact same point.

I'll make changes to files tonight and report back.

Another observation is that during a render the memory usage never goes above 2.2gb even though i have 4. Thats 2.2gb for everything thats running including the OS.

I really don't want to speak too soon but we certainly have some progress!

I've altered some files and its got a lot further than before. I crashed every time a 4mins and 33 seconds. I oberved normal memory usage and when it hit that point there was a pause, the memory jumped up by 400mb and it continued to render! Currently at 5 mins 53 and still going albeit slow. At this point i added the lighting filters ect so it will be processor intensive.

I'll report back with the end resulty and if sucessful i'll post the filenames to alter. I am hopeful this will improve, if not fix the issue.

Fingers crossed!!

Update.. i got to about 8 or 9 minutes then got another error.. something about a front end graph? I pressed the wrong key and it went away and stopped rendering so i'm going to go again and i'll post the error here.

Ok the error is:

media source error: a front-end graph streaming error occurred.

Now if i leave it it keeps on rendering. If i clock the OK button it stops

One thing i forgot about was that this project had links to native PIP stuff which, because i'm now in a 64 bit OS, exist in a different folder (program files (x86). I wonder if this is the cause of the error?

Either way the test project finished rendering! I havent had chance to check the output yet but progress non the less.

Hi Lee, was it a "clean install" of PD8 that you were experimenting with? - I am not sure I understand your comment about code existing in a different folder - But anyway this is looking better I think - well done.

Don Gigabyte I7/4940 O/C 4.3, Noctua Cooler 10GB DDR3, 4 x 1TB, 1TB SSD, Geoforce GTX660 TI 8500W PSU, Windows 10 Pro 64bit.

Well, I found the problem! It was an m4a file which couldnt be decoded so I guess I didnt have the itunes decoder activated.

For anyone else wanting to give this a try the files are as follows:

clvidenc.ax
clmp2vs2.dll
claudenc.ax
cl264dec
264dsse3
cledtdemuxer.ax
mpgmux.ax
pthreadvc2.dll
uvac3enc.dll
ltkrn15u.dll
ltfil15u.dll

I'd be grateful if everyone can post their results!

LEe

Quote: Hi Lee, was it a "clean install" of PD8 that you were experimenting with? - I am not sure I understand your comment about code existing in a different folder - But anyway this is looking better I think - well done.

Don

My problems started on a 32 bit XP machine. I upgraded to windows 7 64 bit and tested again - Exact same problem crashing at the same time.

Because PD8 is a 32 bit app, all 64 bit operating systems put 32 bit progams in a sperate program files folder. You have 'program files ' for native 64 bit apps and then 'program files (x86)' for 32 bit apps. Becaus emy project referenced some PiP objectswhich were installed perviously to my original 'program files' folder it errored as it was looking for the failes in that same location. The program is now installed to 'program files (x86)' so it couldnt find them. Over the next 2 days im going to push this to the limit with effects and PiP. I'll report back.

P.S. Do i get a free copy of the software for figuring this out?

Lee,
That is absolutely brilliant, and well done figuring the files out!
On the free software suggestion if you get one, could I also have copy being the initial proposer of this? - even though it was never picked up except by you and Mr anonymous.
The interesting challenge here that unless you have a 64 bit operating system installed it probably won't work (memory addressing limits?)

Regards

Don Gigabyte I7/4940 O/C 4.3, Noctua Cooler 10GB DDR3, 4 x 1TB, 1TB SSD, Geoforce GTX660 TI 8500W PSU, Windows 10 Pro 64bit.