2014-01-24, 20:26
(minor nitpick, x265 an encoder library, H.265 is the codec)
Not all H.265 content is created equal. Not all H.264 content is created equal either. The high CPU usage comes in when the various settings are really cranked up, in order to get real file size savings without losing quality. There was an ARM processor vender at CES that demoed H.265 being software decoded, but it was a joke because the compression wasn't very complex and there wasn't a lot of work for the processor to do. It's one thing to be able to handle the codec at all, and another to be able to keep up with what will likely be the common settings (otherwise there isn't much point in using H.265 over H.264).
EDIT: Note that the video from the screen shot is 640x360.
"Scene release" standards are not likely to change for 2015. Individual groups might foolishly try to jump on the latest encoders, but it will be a long time before it over takes H.264. Like I said, it will take time, especially for an open source implementation, to actually gain the benefits of the standard (size/quality ratio). There will be little incentive to use H.265 over H.264 until that happens, and even then there will be releases for H.264 for years. Heck, most groups still provide divx versions of releases.
Don't get me wrong, I want it to happen sooner than later, because H.265 is an actual standard. It will replace non-standard (at least in the consumer space) stuff like Hi10P. It just takes time, even though I expect H.265 adoption to be far more aggressive than H.264 was. Maybe I'll be wrong, but I don't think I will be. In 2015 H.264 will still "outrank" H.265 as the main go-to codec for the masses.
Not all H.265 content is created equal. Not all H.264 content is created equal either. The high CPU usage comes in when the various settings are really cranked up, in order to get real file size savings without losing quality. There was an ARM processor vender at CES that demoed H.265 being software decoded, but it was a joke because the compression wasn't very complex and there wasn't a lot of work for the processor to do. It's one thing to be able to handle the codec at all, and another to be able to keep up with what will likely be the common settings (otherwise there isn't much point in using H.265 over H.264).
EDIT: Note that the video from the screen shot is 640x360.
"Scene release" standards are not likely to change for 2015. Individual groups might foolishly try to jump on the latest encoders, but it will be a long time before it over takes H.264. Like I said, it will take time, especially for an open source implementation, to actually gain the benefits of the standard (size/quality ratio). There will be little incentive to use H.265 over H.264 until that happens, and even then there will be releases for H.264 for years. Heck, most groups still provide divx versions of releases.
Don't get me wrong, I want it to happen sooner than later, because H.265 is an actual standard. It will replace non-standard (at least in the consumer space) stuff like Hi10P. It just takes time, even though I expect H.265 adoption to be far more aggressive than H.264 was. Maybe I'll be wrong, but I don't think I will be. In 2015 H.264 will still "outrank" H.265 as the main go-to codec for the masses.
