|
|
|
Peter100, with patch 1703 released yesterday I am seeing the same "mangled frame sequence" as you after a transition from rendering to SVRT. See http://forum.cyberlink.com/forum/posts/list/15/23191.page#125030. Cheers, Gerry.
|
|
|
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.
|
|
|
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.
|
|
|
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.
|
|
|
Hi Neil / CubbyHouseFilms,
Thanks for your input. I agree I don't have the fastest computer around (when I bought it it was ), but if during producing CPU load doesn't go above 30-50% and memory usage typically stays below 2GB, I'd say it should be more than good enough. I have considered upgrading to Windows 7 to get the full 6GB of memory in my PC, but I'd have to shell out $300 and go through the hassle of reinstalling drivers etc.
I will indeed take the approach you're suggesting if that's the only way, but in that case I do believe that PD contains some important bugs that need fixing.
Will keep you posted on further experiments.
|
|
|
Ho jmone,
Thanks for your post.
My PC doesn't hang or crash after I adapted my BIOS settings. The method you described I also tried, but now that I think about it, that may have been before I changed BIOS settings... After changing them I did the same again, but by that time I had a custom profile and the settings may have been slightly different, so I'll try again by deleting profile.ini and using the profile offered.
Questions:
1) There are 2 profiles offered for 28Mbps, one with video bitrate 25.5 and one with 26.3. Which one do you choose?
2) Have you been able to produce a big project like that?
3) What camera is your source material from?
|
|
|
Hi SteveK,
Thanks for your quick reply!
Sorry if I wasn't entirely clear: I'm working with HD source material (TM900 1080p50 clips and 10+ MP photos), and want to produce to a 1080p50 file as close as possible to the TM900 source material.
The media player I use to watch everything is a Popcorn Hour C200, which does not support L4.2 H.264, so I will convert the PD-produced output to L4.1 or L5.1 using Handbrake (L4.1 officially does not support framerates above 30 for 1080p). In time I will buy a media player that does support L4.2, so I would still like to produce to 1080p50 H.264 High Profile Level 4.2.
Trying things in a short project I think is not gonna help me: I've already tried that. Also, I had an occurrence where 1 hr 47 mins of the large project was produced (albeit with 3 frozen clips), and other unsuccessful attempts failed at points where this one went OK. Short projects work fine, the problem is with the large project.
For clarity: I have 3 remaining problems:
1. Program Freeze: PD stops rendering at random times, and there is no way I can get it to resume (tried everything, from pausing and resuming in PD's GUI, killing PDHanumanSrv (restarts automatically but rendering does not resume), killing CES_CacheAgent, killing RichVideo, and combinations of those in different orders.
2. Frozen clips: somehow I think this is related to problem 1: rendering stops, but in this case the rendering resumes after the current clip finishes.
3. Artifacts (black frames) at the transition from SVRT to rendering.
Problems 1 and 2 only occur sometimes, so normally not seen in short projects.
|
|
|
|
Dxdiag got lost somehow.
|
|
|
Hi all,
I'm new here so hello everyone, I'm Gerry from The Netherlands, 44 year old, male, and trying to get my project produced for over a week now .
I have the following situation:
PC: MSI X58 Pro-E, Intel i7 950, ATi HD5850, Windows XP SP3, 6GB memory of which only 3GB visible (yeah I know ), latest drivers of everything, etc. Dxdiag attached.PD: PD10 Ultra, patch 1424cCamera: Panasonic HDC-TM900, PAL version
I shot a lot of footage on vacation in New Zealand, and after coming back I searched for a good program to compile parts of that footage, and photos, into a nice movie with transitions, title, etc. Power Director had the best papers IMO, so I purchased it.
Have spent a lot of time authoring my movie, which was nice to do with PD; the UI is intuitive and offers plenty of functionality to do whatever you like. I actually enjoyed making the movie even though it took ages, but seeing all the footage and discovering the possibilities of PD was a pleasure. Some minor frustrations every now and then, like when using PD for a while, previews first have to render before they play, whereas after starting up fresh it always plays previews without having to wait. BTW does anybody know why this is? Cache memory getting full?
Anyway, movie authoring is finished, movie is 2 hrs 37 mins, and now I've been trying for a week to get it produced. I want to produce it to 1080p50 with minimal quality loss. I think I've read all related posts on the forum and tried all suggestions, but I'm still not successful. Here's my experience of the past week, and current status:
First attempt I clicked Intelligent SVRT, it suggested two 1080p50 profiles, one with 25.5Mbps video and one with 26.3Mbps. I chose 25.5 and left it running overnight. It got to 45 mins (movie time) and it crashed (don't remember whether it was BSOD or reboot). The file was rendered with SVRT largely (Single IDR enabled), and has transition artifacts (couple of black frames) at the transition from SVRT to rendering (strange since most of you seem to have problems in the reverse). I thought it could have something to do with cross fades instead of overlap fades, so I made a second version of the project with only overlap fades. BTW I also saw that a small number of clips (2 or 3 out of maybe 100) had been rendered in a "frozen" state, just the first frame after the transition is there, and then it stays like that until the next transition. Audio is continuing during that freeze.Second attempt I tried 26.3Mbps with overlap fades, and this one got to only 13 mins after which it also crashed. For the rest same results as first attempt: transition problems and frozen clips.Third attempt tried 25.5 Mbps with overlap fades: 6 mins crash or program freeze, don't remember. Same problems in the result. The program freeze: program is still alive but rendering has stopped. In most cases a process called CES_CacheAgent is occupying 13% (sic; ?) of CPU, but no changes in memory use. PDR10.exe has 0% CPU use and no change in memory use. In some other attempts I've also seen no CES_CacheAgent after a program freeze, but PDR10.exe is occupying 1 or 2% of CPU.Fourth attempt: disabled Fast rendering / SVRT, 25.5Mbps with cross fades. Got to 24 minutes. No transition problems, but still some frozen clips.Fifth attempt: also disabled "remove blocking" (in preferences and in the profile), chose 26.3Mbps again, project with cross fades. Got to almost 26 mins, same result.Sixth attempt: bumped up the min and max bitrates in the profile. Got to 1h 3min! No transition problems, but some frozen clips (1 or 2).Seventh attempt: I remembered I did not install Quicktime when installing PD. Quicktime is only used by Smartsound, which I didn't/don't use. But I read on the forum that it may cause problems, so I installed it (extracted from the PD installer). I also disabled Shadow Files, and made sure to delete all existing ones from the hard drive. Only got to 4 mins.Eighth attempt: changed BIOS settings to the "BIOS failsafe" values. No Crash anymore!!! Also changed GOP structure from M=2, N=29 to M=3, N=22. I actually wanted N=24, same as the original clips from the camera, but the structure IBBPBBPBBPBBPBBPBBPBBPBB yields 22: PD seems only capable of GOPs ending in a P frame. Got to 14 mins, after which it freezes (stops rendering).Further attempts: various combinations of GOP structure, dynamic GOP yes/no, overlap or cross fades, different bitrates, CAVLC instead of CABAC, update of Quicktime, even safer BIOS settings (Intel cstate disabled, phase control disabled, spread spectrum disabled), ran memory and CPU stress tests only to find that even the stress test applications were getting tired. Heck I even tried rendering in Windows safe mode to rule out any interference from certain drivers, and I tried disabling the Realtek audio driver because someone on the forum reported it solved his problem. I pushed bitrate down to 20Mbps with no luck, PD still freezes after a while. I tried various speedquality settings: all the above is setting 8, I tried 7 and 6, but the latter already yields a lot of quality loss. I tried rendering to the PD-supplied 720p profile, and to 1080p25 (adapted profile), both freeze after a while. Best result I had was with GOP sizes 2:29 (same as the custom profile that Intelligent SVRT originally suggests), dynamic GOP disabled, 26.3Mbps (video bitrate 26314344), min and max bitrates increased (from default 0 and 28000000 to 22500000 and 32000000), overlap fades, and SVRT and SSE-unblocking disabled. Got to 1h 47 mins, with only 3 clips frozen.Last attempt I did was to completely uninstall PD (control panel followed by CLCleaner just in case), reboot, reinstall including Quicktime, and try again with the most successful settings as before. Freeze at 14 mins.
I did not use GPU acceleration (not supported by PD under Windows XP), and I did not use hardware encoding (not supported either and I know it produces bad quality results).
I monitored CPU and memory usage during PD's work: CPU has its 8 cores busy, but only at about 30 to 50%. Physical memory use never gets above 2.2 GB, most of the time it's around 1.8 GB. I did not see anything unusual around a freeze. I am convinced that it is not my system's capacity that is the problem. I can have Handbrake running a batch with around 95% continuous CPU usage with no problem at all.
In fact, that is what I'm doing right now: while I'm typing away, Handbrake is converting all my clips to 15Mbps. Then I'm going to try again to produce the project (I tested and I can use the transcoded files, even though they're MKV, as drop-in replacements for the .MTS files by renaming them). Not that I'll stop if that works, since quality will take a hit, I just want to know if it then fully renders.
Ideally, SVRT would work without transition problems. I understand that the artifacts are due to timestamp problems, and that some players do not seem to have be bothered by them and do not show the artifacts. So far I have only tested on VLC on my PC. My Popcorn Hour cannot handle L4.2 (but a future player I buy will : so to test with it I'd have to convert with Handbrake, which means I'd actually be testing with Handbrake. I'll do that and see what happens.
Does anybody know a remuxer or even a "recoder"/converter that handles the timestamp mismatches well, without artifacts?
I would very much appreciate your feedback. Suggestions to make it work are more than welcome. I will probably try splitting up my project at points where an SVRT transition artifact is not a problem, produce those separately without SVRT, and then import them into a new project that I'll render with SVRT.
Is there anybody out there that has successfully produced a real project, not just some test clips but a 2+ hr project with video from a TM900, photos, titles, transitions (different ones, 2D and 3D-like), background music, changes in volume in both background music and main track, trimmed and multi-trimmed parts, magic motion effects on photos, sped up video, and perhaps even an audio dub here and there?
Cheers,
Gerry.
|
|
|
