|
|
|
I realized that a 10s clip should be doable, many MB but not a problem. How do I attach a large file? Attachment panel has a limit of 100kb/file.
|
|
|
|
Dafydd Bevan - SoftDeko said:
Developers are unlikely to post.
This is a forum for PD users to help each other.
Please read where Adrian has already directed you to.
I have raised the issue with CyberLink.
Dafydd
Well, I meant that developers provide feedback through you... the forum mod... ; Thanks for raising the issue.
One note, I did try to ask some questions of tech support, but they refer me to pre-sales customer service, who then refers me back to tech support... hence this forum is the only place I find where I can ask "pre-sales" support questions.
I do not *assume* that PD8 can support the new files with PF30 encoded via 60i. (in fact I'm now certain it doesn't support them 100% smoothly). I would only suggest that Cyberlink should want to add such features, to avoid that potential purchasers like myself are not driven away by glitches in commonly used features.
|
|
|
My opinion would be: since many cameras now operate this way (and I think Canon is not one of the "small manufacturers"), PD8 should be able to properly interpret this kind of video, natively.
At the very least, the developers should be able to comment on whether this is a known issue... and if/when it may be fixed...
|
|
|
Hi Adrian,
Yes, I suspect it's the same issue. It's due to the cameras which use 1080 60i hardware/software path to save 1080 30p footage.
It seems that PowerDirector 8 does not have the capability to deal with such footage in 100% of circumstances. At least in the case of using the "clip speed" function it does not work properly...
-Dave
|
|
|
Hi, I'm experimenting with the trial of PD8. By reducing the cores in use from 3 to 2 it can now produce without crashing (memory error) on transitions (as mentioned in another forum post). I hope Cyberlink fixes that core-usage bug soon.
However, I notice something else strange: when using "clip speed-up" there are occasionally deinterlacing problems, where the output goes from properly deinterlaced to completely interlaced within the 1920x1080 AVCHD output. This even happens in the middle of a clip sometimes. Note: I also have image stabilization on in this 1st-person sports video.
Camera: Canon HF200 using 1920x1080 AVCHD in PF30 mode (progressive format where it saves two "progressively" captured frames in a row, but in the 60i file format).
My suspicion is that PD8 is dropping a frame with the "clip speed" algorithm, and then instead of getting the correct format of deinterlacing, is using frames from different "progressive" sets. I'll make an example with progressive frame-pairs called A and B, with interlaced-format sub-frames 1 and 2 in each pair:
Correct:
A1+A2 = final progressive frame A
B1+B2 = final progressive frame B
Incorrect:
Drop A1
A2+B1 = final progressive frame "interlaced-looking"
B2+A1 = final progressive frame "interlaced-looking"
...and so on.
PD8 Version: Build 2013 Trial
PC: Win XP 64-bit with Phenom2 X3 (3-core), set to use 2 cores only
Gfx: Nvidia 9500GT
|
|
|
Hi dafydd, I'm glad I found this post (as a link from another one). My system has this rendering crash issue on 1920x1080 hd video as well. I'm rather unhappy about (almost having to purchase) a competitor, because it renders at the speed of molasses. I'd prefer to buy PD8 based on features + render speed!
My system is an AMD Phenom2 X3 (3-core). I have been using the Build 2013 trial version. Can you tell me if this rendering bug / memory issue is fully understood by the programmers? Is a bugfix release planned already?
If there is a fix soon enough, I will do another trial of PowerDirector before I make my final purchase decision. But that's coming up fast. Looking forward to your response,
Dave
|
|
|
Hi, I'm trying the trial version of PD8 (build 2013) to decide if I should buy it or a competitor.
System: Phenom2 X3, 4GB RAM, Win XP Pro 32 (and now 64-bit)
Camera: Canon HF200 with 1920x1080i AVCHD files
Symptoms:
1) Random crashes during editing (I believe due to background rendering)
2) Crashes during rendering, particularly at complex transitions (e.g. Alpha blending ones) where the surrounding clips have effects applied to them (e.g. stabilize, speed-up).
- Usually this is on the first frame of a transition, late in the movie (after 4-5 other transitions).
3) On the rendering crashes, I often get an "out of memory" error. Watching the task manager, I see there is plenty of physical and virtual memory left. But just before the crash, the PD8 memory starts to spike (from e.g. a steady 620,000K to >700,000K). Does PD8 have a limitation on how much memory it can address, and if so, why is it so low (or am I missing the end of the spike in Task Manager)?
Symptoms are independent of OS (as anyway it runs in 32-bit mode on Win XP 64-bit).
Is there another revision besides 2013 that might be more stable? I've heard that 1930a worked well for a member of another forum. As a many-year-long software testing engineer, perhaps Cyberlink reintroduced some older bugs in 2013, as he said a pre-1930a version had some kind of transition issues. Just a speculation.
If there is a solution, I would love to get a stable version of PD8. Otherwise I will probably soon purchase a competitor, because their product (although MUCH slower and less desireable to me) does not crash, ever. Please find a PD8 solution for me!
|
|
|
