Hey Guys,

Thanx for all the feedback and suggestions, even on the unrelated altitude topic .
Just to let you know that after converting all 28Mbps 1080p50 video clips from the TM900 to L4.1 1080p50 (unofficial) @ 15 Mbps, PD (still 1424c) was able to finish producing the movie completely! There were quite some video freezes in the final result though, about 15. Peculiar difference is that where with the original footage the freezes were always at the beginning of a clip and lasted the entire clip, now the freezes are also in the middle of clips.
I believe PD has some bugs that the bigger the project, the more they occur. Probably memory related, processes writing outside of their buffers, whatever. So until fixed, I'll just follow the experts' advice and split up my projects in max 20 minute parts.

When I finally have my movie produced without error, I'll try the original project with the 1703 patch (unless I already run into the same problems on the 20 minute parts).

So CyberLink, 3 bug reports:
1) On big projects with 1080p50@28Mbps source material, PowerDirector freezes at undeterministic moments; freeze here means: the program has not crashed, is still responsive on its UI, but rendering has stopped and there is no way to get it to resume.
2) On big projects with 1080p50 source material (any bitrate), PowerDirector produces results with some parts (undeterministic) of video frozen.
3) At transitions between SVRT and Rendering (CPU rendering at least), artifacts are introduced. On VLC, the artifacts manifest themselves as black frames.

By the way, perhaps also interesting for somebody wanting to investigate further:
1) When doing Intelligent SVRT with the Handbrake-converted clips, it took hours to analyse and came back with more than a hundred profiles, all the same: AVC 1920x1080/50p (28 Mbps) with 25.500 Kbps video bitrate. I chose my custom profile instead.
2) PD stores a lot of info about precache and shadow files in the registry. So to start producing with a clean slate, deleting files may not be enough. According to CyberLink (link buried somewhere in the forum, search for RichVideo) the process RichVideo enables PD to reuse things determined while authoring during the production, to decrease production time.
3) The option to enable/disable RichVideo is not there in the GUI (shadow files is something else apparently). But there is a registry setting for it (like there also is for shadow files).
Cheers.

SVRT tests with new patch 1703:
Where with 1424c I used to get a number of black frames just *before* a transition, now with 1703 I get a short freeze of the video right *after* the transition. I was able to reproduce the artifact with two clips, each one trimmed (beginning and end cut off), and a transition between them. Two full clips with a transition between them renders fine.

I am also able to confirm what Peter100 writes here: http://forum.cyberlink.com/forum/posts/list/15/20483.page. I frame-stepped through the old black frames and the new freeze with VLC. Framestepping through the sequence:
- The black frames produced with 1424c show as black frames
- The freeze produced with 1703 shows as a mangled sequence of frames: suppose the right order is 0123456789, then frames are in order 0516273849, after which the rest continues correctly.

Tried DynamicGOP=1, no luck.

Hi Gerry

Thanks for the follow up

The members here do not work for Cyberlink nor do Cyberlink monitor this forum.

We are all volunteer video editors - like yourself - sharing information and helping each other out due to the (sometimes, well almost) inadequate support from Cyberlink.

Your great suggestions should be directed to Cyberlink Technical Support:

http://www.cyberlink.com/prog/support/cs/contact-support.jsp

Happy editing Happing editing

Best Regards

Neil
CubbyHouseFilms
My Youtube Channel
My Vimeo Channel
PD3.5, 5, 6 & 7. Computer: Dell Dimension 5150, Intel Pen. 2.80 GHz, 2GB RAM, NVIDIA GeForce 8600GT 256MB, Windows XP Pro!!
PD8 Ultra v3022. Computer: Dell Studio 1747, Intel, i7 Q740 1.73 GHz, 8GB RAM, ATI Mob. Radeon HD 560v 1GB, Windows 7 Ult. 64
PD10 Ultra v2023. Computer: HP Pavilion dv7, Intel, i7 2630 2.00 GHz, 8GB RAM, ATI Mob. Radeon HD 6770 2GB, Windows 7 Pre. 64
PD12 Ultra v2930. Computer: HP Pavilion dv7, Intel, i7 2630 2.00 GHz, 8GB RAM, ATI Mob. Radeon HD 6770 2GB, Windows 7 Pre. 64
PD13 Ultim v3516. Computer: HP Pavilion dv7, Intel, i7 2630 2.00 GHz, 8GB RAM, ATI Mob. Radeon HD 6770 2GB, Windows 7 Pre. 64
PD16 Live v2101 Computer: HP Pavilion dv7, Intel, i7 2630 2.00 GHz, 16GB RAM, ATI Mob.Radeon HD 6770 2GB, Windows 7 Pre. 64
Director Suite 6: PowerDirector 16 Live, PhotoDirector 9, ColorDirector 6, AudioDirector 8

Cameras: Sony(s) HXR-NX5P, HXR-NX70P, NEX-VG10E, a6300 4k, HDR TG5E, GoPro 4 Black, Canon 6D DSLR

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

Quote: Hi,
I am going to show my ignorance why would a video camera fail at a certain altitude? I
Jim

He's going to be in the Andes -- the problem is the llama spit. Jerry Schwartz