[DJ_Izumi]

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.

[fritsch]

We have merged ffmpeg 2.5 into kodi - so any early adapters could test if there are some hevc improvements -if you like.

[AbRASiON]

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.

[DJ_Izumi]

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.

[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.

[DJ_Izumi]

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.

Well, more cores won't help till multi-threading is improved. I was running HandBrake WITH Civilization 5, an the CPU was still only at 50%-60%.

Though I suppose when ripping DVDs I could at least make up for the poor multithreading by running multiple concurrent encodes for different episodes.

[voochi]

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.

The speed presets allow you to trade-off between encoding speed and compression efficiency (the quality per bitrate).

[DJ_Izumi]

The speed presets allow you to trade-off between encoding speed and compression efficiency (the quality per bitrate).

yes, though from what I read, the gains between 'medium' and 'very slow' aren't very significant.

[bluechris]

With a 4790k at normal clock (4.5ghz) i get average 40 fps with all 8 cores going to 90% constand converting a good h,264 mkv for test with the quality setting in handbrake to default very fast..
With the CPU at 4.9ghz i go to 50fps.

The same file with quality to medium i get average 12 fps and with the cpu at 4.9ghz 16 fps

From what i see is not too bad... but keep in mind this, in handbrake settings in video you need to DISABLE dvxa2 or else you get very low FPS.

[Krautmaster]

Status?

when i encode a stock x265 file (mp4) in Handbrake nightly, it plays with Kodi (openelec 5) but skips frames. ~16-17 fps reach the screen. how to fix?

[bluechris]

What hardware you have?

[wsnipex]

Status?

when i encode a stock x265 file (mp4) in Handbrake nightly, it plays with Kodi (openelec 5) but skips frames. ~16-17 fps reach the screen. how to fix?

buy a faster CPU

[AbRASiON]

If most blu rays are encoded at .264 and we rip them to .265 would I be right in thinking, we're still just going to lose quality because the source codec is inferior?
In a best case scenario there might be a tradeoff level of compression where there's very little data lost but smaller files than the original disc, right?

[nickr]

Every re-encode loses quality.

[DJ_Izumi]

If most blu rays are encoded at .264 and we rip them to .265 would I be right in thinking, we're still just going to lose quality because the source codec is inferior?
In a best case scenario there might be a tradeoff level of compression where there's very little data lost but smaller files than the original disc, right?

Yes, but it's also highly subjective. You also loose quality when you re-encode from a 25GB untouched h.264 BluRay stream to a lower bitrate h.264 file to make your movie only like 7GB. HEVC will just the same, just do it more efficiently.

It wouldn't be about 'data loss', lossy compression has LOTS of data loss, it'd be how it effects the subjective experience of the viewer.