<p>As @Mulvya suggested, the best approach is use short GOP chains, the filesize will obviously increase a bit, but the cpu processing will be limited doing so.</p>

CC BY-SA 3.0
2017-03-14T00:27:03.723Z
2017-03-14T00:27:03.723Z
user3450548
<p>Try Encoding using "--tune fastdecode" and also check if "Average Bitrate" with "2 Pass" is better than "Constant Quality" with your particular Decoder; trying to maintain Quality over Bitrate can spike the Bitrate (holding a particular Bitrate will drop the Quality on complex Scenes).</p>

<p>Try a few Test Files (short Clips from your Source) and determine which Encode Settings produce the lowest CPU load when Decoding. </p>

<p>Decoding x265 works best with Hardware support which is not going to be available in most Phones, the Phone will probably decode x264 much easier since so many people/years have gone into decoding x264.</p>

<p>Reference: <a href="http://x265.readthedocs.io/en/default/presets.html" rel="nofollow noreferrer">http://x265.readthedocs.io/en/default/presets.html</a></p>

<p>See also: <a href="http://www.techspot.com/article/1131-hevc-h256-enconding-playback/page4.html" rel="nofollow noreferrer">http://www.techspot.com/article/1131-hevc-h256-enconding-playback/page4.html</a></p>

CC BY-SA 3.0
2017-03-14T08:26:03.800Z
2017-03-14T08:26:03.800Z
Rob
<p>h265 is a very powerful but still not widely supported codec, recently I found myself in the need of prepare some h265 videos and have them played on various smartphones.</p>

<p>While a powerful desktop pc has less issues and is outlet powered modern smartphones still struggle with battery savings.</p>

<p>Recent ones are able to decode h264 / avc and aac audio with dedicated hardware but almost no one have support for h265 / hevc at time I'm writing this answer.</p>

<p>What settings can I use to reduce the CPU consumption (and so the battery) on the target devices? The best goal could be make the final cpu needings close to the h264 ones.</p>

<p>Are presets such as slow, veryslow useful for this task or they are good only for reducing the output file size ?</p>

<p>There are other settings that I can tweak for obtain my pourpouse?</p>

<p>PS: please also provide some examples with ffmpeg, thanks!</p>

CC BY-SA 3.0
2016-10-21T09:17:32.893Z
My first approach would be to limit the number of reference frames and GOP size.
Gyan
CC BY-SA 3.0
2016-10-21T12:28:43.380Z
@Mulvya limiting the reference frames doesn't work against shrinking the size of the final file? Can you provide some -flags for the h265 as examples?
user3450548
<ffmpeg><software><hardware><h.264><h265>
How h265 settings / presets affects the target device cpu while decoding and how can I tweak them?
user3450548
# How h265 settings / presets affects the target device cpu while decoding and how can I tweak them?

(Asked by: username_0 on 2016-10-21)

h265 is a very powerful but still not widely supported codec, recently I found myself in the need of prepare some h265 videos and have them played on various smartphones.

While a powerful desktop pc has less issues and is outlet powered modern smartphones still struggle with battery savings.

Recent ones are able to decode h264 / avc and aac audio with dedicated hardware but almost no one have support for h265 / hevc at time I'm writing this answer.

What settings can I use to reduce the CPU consumption (and so the battery) on the target devices? The best goal could be make the final cpu needings close to the h264 ones.

Are presets such as slow, veryslow useful for this task or they are good only for reducing the output file size ?

There are other settings that I can tweak for obtain my pourpouse?

PS: please also provide some examples with ffmpeg, thanks!

**Tags:** ffmpeg, software, hardware, h.264, h265

> **Comments:**
> **username_1**: My first approach would be to limit the number of reference frames and GOP size.  
> **username_0**: @Mulvya limiting the reference frames doesn't work against shrinking the size of the final file? Can you provide some -flags for the h265 as examples?  

---

## 2 answers

### Answer by username_0 on 2017-03-14. Score: 0 | Accepted answer

As @Mulvya suggested, the best approach is use short GOP chains, the filesize will obviously increase a bit, but the cpu processing will be limited doing so.


---

### Answer by username_2 on 2017-03-14. Score: 2

Try Encoding using "--tune fastdecode" and also check if "Average Bitrate" with "2 Pass" is better than "Constant Quality" with your particular Decoder; trying to maintain Quality over Bitrate can spike the Bitrate (holding a particular Bitrate will drop the Quality on complex Scenes).

Try a few Test Files (short Clips from your Source) and determine which Encode Settings produce the lowest CPU load when Decoding.

Decoding x265 works best with Hardware support which is not going to be available in most Phones, the Phone will probably decode x264 much easier since so many people/years have gone into decoding x264.

Reference: <http://x265.readthedocs.io/en/default/presets.html>

See also: <http://www.techspot.com/article/1131-hevc-h256-enconding-playback/page4.html>


---

