Quote:
Hi everyone!
One thing I've learned is DON'T RENDER in AVCHD using PD8! Tried it once, took nearly forever to render a 1-hour video. So, even though the new digital video camera I bought a few weeks back shoots in AVCHD or MP4, I've opted for MP4 in the camera, and for PD14(when I get it), I'll be sticking with tried-and-true MPEG2 which, in most cases renders so fast, you barely have time to sneeze before your video is rendered! That's the case with PD8. As for titling applications in PD14, is there an option? NewBlue or regular titling? As it is, I create my own animated titles, using letters I designed myself using Microsoft Paint. Having the vastly-expanded number of PiP tracks in PD14 with lift my game considerably there.
Cheers!
Neil.
PD14 has Newblue titler as an option if you buy at least Ultimate. But it's basically unusable if you are doing any 4K work.
But I guess if you are sticking to MPEG2, you must not be.
FYI, on a system with a recent nVidia card, in PD14, MPEG-4/AVCHD encoding is hardware accelerated, but MPEG-2 runs 100% on the CPU. This makes the MPEG-2 encodes actually slower. And at equal bitrate, an MPEG-4 encode will look better than MPEG-2, as well.
PD8 is very old - I would recommend moving up. The first 64-bit version of PD was PD9, and that gave a pretty good speed boost. Of course, you must run a 64-bit version of Windows, and have sufficient ran, to take advantage of it.
Anyway, I would suggest you start your own thread to discuss titling issues.
Cyberlink replied to the bug I filed in CS001521449 and the Newblue GPU issue.
"Thank you for writing back.
Regarding your concern, I would like to inform you that after checking, it is an expected behavior.
NewBlue Titler uses OpenGL and needs hardware driver's support to paint title. The plug-in doesn't support software mode."
I didn't like this answer, and I have reopened the bug. Here is my latest reply :
The problem isn't just that Newblue titler is requiring the GPU. It is that Newblue titler is using all of the GPU resources, including all RAM and video engine, when used in a 4K project. When using both GPU hardware decoding, GPU hardware encoding and NewBlue titler, which also uses the GPU, I have run into many problems in the past, which led to nVidia driver out of memory errors, that caused PowerDirector to crash.
I believe that in its current state, NewBlue titler is completely unusable for a 4K project. It might consume fewer resources in an HD project. I would appreciate if you could get Newblue to look into this and fix the resource usage. There is very likely some sort of memory leak going on."
MSI X99A Raider
Intel i7-5820k @ 4.4 GHz
32GB DDR4 RAM
Gigabyte nVidia GTX 960 4GB
480 GB Patriot Ignite SSD (boot)
2 x 480 GB Sandisk Ultra II SSD (striped)
6 x 1 TB Samsung 860 SSD (striped)
2 x LG 32UD59-B 32" 4K
Asus PB238 23" HD (portrait)