Thanks for the quick response!
Generally speaking, I don't like to use pre-packaged benchmarks, but in the case of this one, I would consider using it as an addition but not a replacement of the project I mentioned. That benchmark executes rather fast, while I'd prefer a lengthier project that would do well to separate the men from the boys (with a benchmark that finishes in 1m on a six-core CPU, it doesn't leave much room for noticeable scaling).
I am checking this out nonetheless, since it claims to use some of the GPU, which my project does not. Waiting for VB to install so I can run the script to generate the results...
Personally I think the benchmark would be more telling with standardized media - specifically AVCHD. Set up a 30 minute sequence using 1080p/24 media, and export out to MPEG2-DVD at the same frame rate. Leave "Maximum Render Quality" on. Have the project file on one drive, the media on a second, and send the export to a third. (None of these should be the System drive with Windows on it.)
I think this is still a pretty common workflow - shooting HD and delivering DVD - and it'll stress the CPU enough to show how well it performs.
Thanks for the response!
I don't own a video camera (boy, do I ever feel like a reject, now). Would it be an inaccurate way of doing things if I took the same project I have as mentioned above, export it to AVCHD 1080p/24 and then use that as the source file to encode to MPEG-DVD? It'd still be game footage, but essentially the codec is what really matters (I could be wrong; perhaps the codec would work better with real images).
Sorry if that comes off as a ridiculous question. If that's not a good solution I will see about getting such a source from somewhere.
Thanks a ton!
Edit: Would it be sufficient to use a Blu-ray .m2ts file specced at 1080p/24 AVC MPEG-4 as a source? I assume it's AVCHD given it's 1080p.
Personally I'd rather not make the assumption. If you start with raw camera footage, as most people use, then you have eliminated one possible variable. And that's the key to good benchmarking.