|
|
Hi Robert,
Yes it was indeed after finding your earlier posts about cores that I started trying disabling them. I was extremely happy to find your posts about this, as I was quite disappointed, not to mention frustrated.
But I think I'm a bit confused now about when it crashes - I think it only occurs when rendering to 1080p, but it's been almost 2 weeks since I last did that.
My daughter rendered an 8m30s clip today to 720p and it worked fine with all 8 cores enabled.
BTW - I have watched a couple of your hang gliding videos, which are just spectacular. Nice work! That sure looks like a beautiful part of the world you live in. I've posted a few of my videos here: http://www.youtube.com/blathermouth1
Only the 2 most recent ones (Dogs.. and Wengen...) were made with PowerDirector. The others were made with Windows Live Movie Maker (blech!) before I had bought PD.
Cheers!
Mike
|
|
|
Aha - that explains why my last video looks bad on YouTube. I'm also using nVidia's CUDA. The resulting 720p video looked just fine on my machine, but on Youtube seems to have noise (kind of horizontal lines) when objects move.
Interestingly, this last video was just under 2 minutes long, and I had all 8 cores of my i7 920 active. I was too lazy to reduce this to 4 and reboot prior to rendering, and it completed successfully. So there must be some video duration threshold, above which rendering will fail with more than 4 cores...
|
|
|
I have also seen this message, but I have been messing around with too many variables to isolate it just yet. When rendering failed and message appeared (exactly as in screen shot provided by Lee) I also had to kill PD8 in Task Manager. The resulting video was playable though, right up to point of failure. This seemed to point to a clip to which I applied speed adjustment (slowed down to 33%).
Will try removing any such adjustments and see if I can isolate this. But it also seems to depend on what the output format is. (Note that my source files are Canon MTS AVCHD). Also, after reading this post, I've just disabled Shadow File creation.
Sorry, but I'm getting a bit frustrated, battling this as well as fairly frequent application hangs (Standard Win7 "Program has stopped responding" error message) while doing nothing in particular, like saving my project. That combined with having to reduce the number of cores my i7 chip is using to get around another problem... groan! (although I'm successfully running on 4 of 8 cores now).
I'm beginning to wonder if it wouldn't be better to convert my original footage into something like standard mp4 and avoid AVCHD editing all together. It strikes me that if high end modern rigs like mine can't properly deal with these codecs, maybe I'm asking too much of the software...
Any feedback from more experienced PD8 users would be appreciated. I'm very new at PD...
----------------EDIT------------------
Ok, I isolated this problem to a clip that I had slowed down - rendering failed at the exact time stamp of the start of this clip. Disabling the speed adjustment for this clip allowed rendering to complete (AVCHD 1920x1080) successfully. Oddly, in the same project I had a another clip that I had slowed down, and it did not cause any trouble.
Now for more confusion... I decided to try rendering to MPEG-2 1920x1080 and this time PD8 crashed (standard Win7 Application has stopped working message - Application PDR8.exe, Fault Module StackHash_963a). This crash occurred precisely at the start of another clip to which I had applied a Crop. So I guess I'm having problems rendering 1080 with Power Tools effects.
Note that I am currently running with 4 of 8 cores enabled on my i7.
I thought I should check the exact nature of my source Canon MTS files, and they are as follows:
Video................
Type: H.264 AVC
Birate: 23.09 Mbps
Resolution: 1920x1080
Frame rate: 29.97 fps
Aspect Ratio: 16:9
Audio................
Type: Dolby Digital
Sampling rate: 48kHz
Bitrate: 256Kbps
Channel: Stereo
I am really a noob when it comes to formats, bitrates, frame rates etc., so if anyone out there can point me to thread that sheds some light on this, and ideally can point me to some preferred settings for the camera and rendering, I'd be grateful!
Thanks
|
|
|
|
Value for money, I still think it's a good product. But I could honestly do without a bunch of the features, and just have a solid tool to edit videos with nice transitions, and be able to render them nice and fast. That is after all the only reason I chose the components that are in this machine...
|
|
|
I am very new to PD (literally just days) and I was quite happy with it until I also encountered this problem when rendering to 1080 AVCHD.
I'm running PD8 Ultra ver 8.00.2220c.
Seeing that the last post in this thread was over 2 months ago, I'm guessing nothing much has changed. I'm also fairly sure I'm on the latest version.
This is rather disappointing for a product that claims to be optimized for the latest CPU's like Core i7.
|
|
|
