Quote:
Try this default title in your own pds file.
Jeff
Thank you very much, that was very helpful.
I tried a bunch of renderings with this project, and with either the hardware or software encoder.
I also compared rendering time with the original project using Newblue, and an identical project using no titles at all (title track turned off).
And lastly, because optodata was saying in another thread that the older 337.88 drivers were performing better, I also tested that.
I have attached the results of all the tests in a screenshot.
The main takeaways are :
1) Newblue Titler Pro v1.0 is very good at filling the entire GPU memory. The default titles are much more efficient that way. My guess is that NewBlue Titler Pro v1.0 was never tested with 4K. And it is not usable with 4K in its current state.
2) Strangely, the PD hardware renderer actually uses a bit less GPU RAM when rendering with the default titles, than without any title track at all. You can see that for example by comparing test #1 with test #4, or test #2 with test #5 .
3) There was a significant increase in OS baseline GPU RAM usage between nVidia drivers 337.88 and 347.88 . About 200 MB more .
4) I didn't run into any issue with "out of GPU memory" this time, because I didn't have anything else of significance running on the machine at the time - no browser in particular. Just GPU-Z, HWmonitor, Task manager, and Openoffice.
5) Test #8 (and test #15, to a lesser extent) was seriously screwed up compared to all the others. During that test, the machine was nearly frozen, even though the CPU usage was down to the low 30% range . The bus load in GPU-Z had some very high peaks. Even just trying to drag the Task manager window during the rendering was very slow. I think this was due to the out of GPU RAM condition with Newblue, and memory being copied accross the PCIe 2.0 bus (there is no PCIe 3.0 on any AM3+ motherboard, sadly). I will attach a 4K video shot with my Note 4 of what the computer was acting like during this particular rendering.
I had to cut a few seconds in the middle of it when I noticed an envelope with my home address on it that came into the frame. You can really read everything with 4K
The day before, I actually had 2 BSODs during similar renderings, after hearing the PC speaker beep, which indicated the CPU was running too hot. This started to make me question my overclock. I decided to restore the AMD "cool & quiet" in the BIOS, even though that interferes with my audio recording with my Firewire interface as it adds pops & clicks into the recordings. At least I didn't have any other BSOD since restoring C&Q, .
6) When using titles, even with the default titles, the hardware acceleration is fairly minimal. Only an 11% difference between test #1 and tests #2 and #3 for example. And 15% between test #4 and test #5, also. The main benefit of the HA seems to be somewhat lower CPU utilization and lower temp, not so much as a faster rendering time. Presumably when using other CPU-based software effects, the remaining available CPU cycles would help.
|
Filename |
pd14.png |
|
Description |
Too many tests. |
Filesize |
336 Kbytes
|
Downloaded: |
84 time(s) |
Filename |
cutcapture.m2ts |
|
Description |
Computer acting crazy during test #8 |
Filesize |
220605 Kbytes
|
Downloaded: |
270 time(s) |
This message was edited 2 times. Last update was at Oct 10. 2015 12:40
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)