|
|
I have PD9-ultra64 build 2316 installed with W7 64bit. Also 6 gig memory and I7-930 cpu. (PD9 installed with no prior PD8 or other video editing products ever installed)
First, I must say that PD9 looks like a great upgrade. Stability and layout are very much improved. While I just got used to PD8 crashing (particularly after a produce and going back to edit), PD9 has not crashed yet.
Initial observations are: (pending further use of the program!)
In some areas PD9 is a bit slower than PD8, but reliability and capability are much more valued.
Ouput, particularly when burning the default DVDHQ format, is much cleaner without the severe interlacing artifacts often seen in PD8
WTV import seems improved regarding audio sync - but still need to run more clips to see how it goes overall
Now, HOWEVER,
While running PD9, I popped up the windows task manager tool, and selected 'performance' which shows cpu and ram use.
With PD9 up and running, I have never seen memory use go above 2.2gig, and most often is around 1-2gig. I have loaded up single clips ranging from about 2-8gig in size, and multiple clips with total size from about 4 to 20gig. Memory use does not signiciantly change at the edit or produce screens.
I have tried this with the PD9 shadow file engaged and disabled.
Is there a RAM quantity threshold for the '64bit memory capabilty' to engage? Or, is the does the memory use occur at a specific operation of PD9?
Any suggestions how I can use this 64bit memory resource in PD9?
Ken
|
|
|
I have been struggling with PD-8 and sound sync with WTV imports. PD8 was usually fine with 1080 or 480 imports, but lost about a second of sync per hour with 720 content. With PD8, I had to split the audio and adjust the audio duration with powertools to bring it back to sync.
However, just completed a 720p import and sync was great. PD9 did pop up the 'which audio and video stream?' window for this clip.
When PD8 popped this up, it was an automatic lockup. PD9 did fine.
So, not sure if its ALL good, but much better!
|
|
|
You are correct that smartfit can sometimes cause problems. But my experience has been good with smartfit, provided my starting video is a 480 progressive format. I have done many single layer DVD's with smartfit, and they look quite acceptable.
I know that a 480 progressive format seems to cure a few ills. I suspect it is something in the way PD8 manages interlaced format.
When I was using roxio 2009, it did a much better job at 'smart fitting' and editing with interlaced format, but IMO not as good as PD8 with a progressive file with which to work. Whenever I am saving a 480 format file in PD8, I always choose the progressive option.
|
|
|
Cyberlink does poorly with the typical interlaced format with standard def content. Pixelation is common, particularly when 'downconverting' from an HD source or zooming or cropping.
The workaround is to set up a custom profile for the 'produce' process. For Standard Definition 480 output, select progressive, not interlaced format. A sample rate of at least 8Mb is best as well, but the main solution is to ALWAYS use progressive format when producing SD content. This method produces clean looking videos while the default 'HQ' format for producing SD content is awful.
You will have to navigate a couple of menus for video and audio format when setting up your custom profile, but it is quite worth the trouble.
Then, burning the DVD from that progressive formatted file provides good SD quality as well. (Also note burning MUST be a two step process - produce the progressive file and remove the original video from the edit track; THEN reload the progressive video to the edit track and burn the disk.)
Overall Cyberlink has a number of nice features, but this is one user trick that helps solve this particular problem.
|
|
|
It could be you are running in to the HD to DVD problem that I found.
You could try to create a 'custom' menu to produce a MPEG2 720/480 DVD file format, and select 'progressive' instead of interlaced.
There are some details a couple of posts back of how to do this.
I usually get much crisper 480 content from an HD file with this approach. Then, that 480 video file will record to a standard DVD if you wish.
|
|
|
Try saving the original video using a custom progressive 480 format - I used about a 10Mb data rate - but the resulting files are not that huge.) Then from a fresh re-open of PD8, load up that progressive encoded file, and burn that progressive encoded file to disk. I had some jaggie issues as well saving files using the standard DVDHQ interlaced format
Quote:
Hi Gang,
I've got PD8 (8.00.22) on a brand new Windows 7 machine.
I was able to achieve a pretty nice quality video for YouTube by letting PD8 produce and upload my finished project to YouTube. Here's that video:
http://www.youtube.com/watch?v=WURzjc7IA18
That one was produced at 640 by 480 in AVI format. I had produced another version with the finished product as an Mpeg2 but the quality wasn't as good. But I think that was because I produced it in 720 by 480 without knowing it till later. Here is that video:
http://www.youtube.com/watch?v=qw-6Gk0QSPE
Notice how the straight edges of the hang gliders are pixelated in the second video. Yet in the first video those straight edges are nice and clean.
So I took that very same 640 by 480 AVI "made for YouTube" file that PD8 had produced, imported it into a new project then burned it to a DVD. I figured this would produce a lovely, clean video on my TV.
But no! I have the very same pixelated straight edges when I play this 640 by 480 .AVI produced file on my TV. However, in the past when I've burned DVDs before (with PD6) and watched them on my TV, the quality is outstanding. Those files were produced in Mpeg2 format.
But when I tried to burn a DVD in the Mpeg2 format for my TV, I get the same pixelated straight lines. I'm confused. What's going on?
Thanks for all your help,
- Andy
|
|
|
First, It seems that PD8 is one of the better editing programs out there. I have tried a bunch of em, and they all have their issues. However, here are the issues I have found during my use of PD8.
(System is an Asus E8600/X38 8Gb, nvidia 8800GT, Hauppauge 1600, Win7-64-- with all the latest bios/drivers I can find; PD8 2220)
Processing .wtv files -- Powerdirector re-renders (and changes resolution of) these files when importing. The workaround is to first convert to dvrms format using Win 7. ( I know this issue has already been posted - thanks to the other folks out there!)
When converting dvrms files, audio sync gradually goes off by about a second per hour of recorded video for 720p content. The gradual sync offset does not occur when converting 480 or 1080i content. The workaround is to split the audio and experiment with shortening the audio clip duration until the sound is back in sync, then save that modified clip. Note, for short clips of a few minutes, this gradually increasing offset would not be noticed. When these same 720p dvrms files are played in WMC, the sync issue does not occur.
Sometimes when importing ts files from the Hauppauge capture program WinTV7, multiple copies appear in the PD media file list (like a dozen or so from the one file import action), and some files are listed as some hundreds of hours long, even though the clip is an hour or so. This makes any editing action difficult.
PD8 sometimes 'hangs' when doing dvrms conversion (not a crash). Processing starts quickly, then slows and grinds to a halt (I can tell by watching the file size progress in a windows explorer window). It happens on occasion, but I can't tell if it's a PD8 or a MS problem. Clicking cancel returns PD8 to normal operation
When converting 4:3 content broadcast in 16:9 format back to 4:3: The 16:9 file is imported to a 4:3 project and using aspect ratio control, choose crop to fill the screen. But saving as the default HQ dvd format results in severe jaggies. (It looks like 320x240 or worse). The workaround is to save as custom 480 progressive format, which results in a very nice looking 4:3 video.
Hauppauge 1600 - PD8 capture worked with an older hauppauge driver (2xxxx), but does not work with the current driver (2714 .
My thanks to all in this forum, and hopefully this info is helpful.
|
|
|
The promt to choose the audio and video stream when converting is a nice feature. (Some clips have SAP or other dual audio streams) - Nice touch. I have noticed that when there is only one audio and video stream choice available, I do not get this prompt.
BUT. now.. cyberlink totally re-renders the WTV files, often changing the resolution. 720p changes to 1440x1080, etc. This rendering can take as long or longer than the clip run time itself. Before the recent released build update, conversion would take just a few minutes. (But some of the videos I converted had no sound - so again . nice job on the stream selection)
Hopefully, conversion can be changed to just that - conversion - without total re-rendering.
|
|
|
