[tential]

I'm experimenting with HEVC encoding with Handbrake. I wouldn't go through the effort to replace my h.264 files with HEVC, it'd be a huge investment in processing resources, but in this case I'm ripping new DVD of mine to add to my server. I'm getting an average of 4.2fps right now with a six core i7 4930K. It's also worth nothing that it's only using maybe 40% of the CPU on average, maybe more like 30%. I think the encoder isn't QUITE mature yet, but that's not unusual for a codec at this point.

4.2fps on a 6 core? I know it needs significantly more power but wow.
I wonder if ATI/AMD or nvidia plan to add h.265 acceleration on card (and if it will be decode or encode)
4.2fps for a DVD (not BR) = wow, just wow. Appallingly slow.

Like I said, it's using maybe 35% of the CPU's available resources, so there's gains to be made just in implementing better multithreading of the encoder. I also imagine that there's a lot more efficiencies to be found over time overall, encoders do naturally evolve and improve over time as development continues. I imagine the primary goal of the devs was 'Make it work' with 'Make it work fast' being a concern for later.

EDIT: It seems that this was the result mostly of me using the VerySlow setting. By using the 'Medium' setting which will get NEARLY as good end results, I'm up to an average of 68fps. Though this is still 480p material and you'd see FAR worse encoding speed on 1080p or 4K.

Their "Very Slow" setting is usually as close to no compression as possible. You need to use settings above it to get some type of compression. Even on x264 it took awhile to encode with Very Slow.

Also, the 5820k is out and looking at the model number you can see they've dropped 6 core on the LGA2011 platform to the entry level processor from the midrange processor in that lineup. So at least there are more core processors at cheaper pricepoints to do the encoding. By the time x265 is mainstream skylake will be out and I'm hoping that will either enable QuickSync, or that processing power/corecount/mature encoder will allow decent encode times.