"hmm.. why would disk usage in your 2nd render (no preview screen) be higher?! Same CODEC and same project should have been identical disk usage."
Disk usage is trivial for me, but I'll write it off to sampling theory. Way back in the early days of digital volt ohm meters, the accuracy was expressed as some accuracy +/- one digit.
I can't buy the sampling theory on this one m'friend.
Render identical source footage, identical region with identical CODEC (same algorithm) and identical quality settings and rendering choices (e.g. hardware vs non-hardware, deinterlacing method, etc) -- bit-for-bit the results should be identical.
"I can't buy the sampling theory on this one m'friend.
Render identical source footage, identical region with identical CODEC (same algorithm) and identical quality settings and rendering choices (e.g. hardware vs non-hardware, deinterlacing method, etc) -- bit-for-bit the results should be identical."
I drink coffee in the morning before I do anything meaningful. While drinking coffee and watching a render, I observed that the "Disk Usage" displayed in the Vegas Pro Rendering dialog box changes periodically. The result is not cumulative. There should be no expectation of comparative numbers at the end of a render. The display reflects the disk I/O in the last sample period. While the render was in progress, I observed values from 0.00% to 1.34%.
@john_dennis Speaking of coffee -- I shouldn't be trying to logicize my brain after 1am ;-) Reading back it looks like I was completely thinking of output size (disk space used) and not the disk utilization during some sample period. *headdesk*
THAT said, I'm shocked to think it would anything but a cumulative average -- similarly for the CPU utilization number at the end of the render. Are you saying both the CPU and Disk Usage reported are *not* actual averages over the render period?? If not, what value do they provide at the end there?
Whatever is in the buffer at the end of the render.
Whatever is in the buffer at the end of the render.
hahaha.. by "what value do they provide" I didn't mean "where is the value coming from" -- rather, I meant "what is the point of displaying any value if it's not the actual average from over the course of the render?"
Knowing the number from a tiny window would be meaningless at that point.