Posts: 527
Joined: Nov 2012
Reputation:
10
Kind of hard to do a comparison when they only post x264 or x265 and not both versions of the file. I'll have to download it though at one point just to see x265 CPU utilization. I got a pretty old laptop so it'll be a nice test to see how well old hardware handles x265 playback.
I have a 2.26 Ghz Penryn Processor
Part of the Intel Centrio 2 mobile family?
Really old like 2008 lol.
Posts: 19,982
Joined: May 2009
Reputation:
451
nickr
Retired Team-Kodi Member
Posts: 19,982
There are plenty of h264 examples of Big Buck Bunny and Sintel around the net, so omparison should be possible.
If I have helped you or increased your knowledge, click the 'thumbs up' button to give thanks :) (People with less than 20 posts won't see the "thumbs up" button.)
Posts: 31,445
Joined: Jan 2011
I think that's what he meant by "post-gotham" ;)
Posts: 387
Joined: Dec 2011
Reputation:
5
2014-01-23, 20:44
(This post was last modified: 2014-01-23, 20:53 by tutu.)
In the mean time, is it possible to launch an external ffmpeg compiled with hevc/h265 decoding on the linux (gotham) xbmc? h265 is already been adopted by the "scene"
Posts: 19,982
Joined: May 2009
Reputation:
451
nickr
Retired Team-Kodi Member
Posts: 19,982
gotham does away with the option to compile using external ffmpeg AFAIK.
If I have helped you or increased your knowledge, click the 'thumbs up' button to give thanks :) (People with less than 20 posts won't see the "thumbs up" button.)
Posts: 527
Joined: Nov 2012
Reputation:
10
It's an interesting issue but well, we'll see how it develops out. All of this talk and hey maybe x265 doesn't become relevant in 2k14 at all. And if it does become very relevant, I'm sure the issue will be addressed. I doubt the XBMC team would sit there and watch x265 become the main go to codec and then just refuse to support it until 2015.
Posts: 26,215
Joined: Oct 2003
Reputation:
187
@tutu: It's possible to build Gotham with an updated version of ffmpeg, yes. Obviously you need to know what you're doing when doing so - there are several minefields to hit, but basically the process is to update the internal ffmpeg version and go through the patches to ffmpeg we apply, applying any that aren't already there (many will be superseded as they are patches from newer versions of ffmpeg itself).
Once done, test, test, test some more.
Post-Gotham we'll be looking at moving the internal ffmpeg out into a separate subproject to make it easier to update (i.e. it'll be a fork of ffmpeg's git with our patches on top) which should simplify the above process a little.
Cheers,
Jonathan
Posts: 31,445
Joined: Jan 2011
2014-01-24, 15:36
(This post was last modified: 2014-01-24, 15:36 by Ned Scott.)
(2014-01-24, 03:00)tential Wrote: It's an interesting issue but well, we'll see how it develops out. All of this talk and hey maybe x265 doesn't become relevant in 2k14 at all. And if it does become very relevant, I'm sure the issue will be addressed. I doubt the XBMC team would sit there and watch x265 become the main go to codec and then just refuse to support it until 2015.
It won't be the main codec even in 2015. It might be a rising star, or even a major contender in 2015, but it will take longer than that for the market to shift. Content providers and consumers are not just going to throw away their old devices that don't have raw CPU power for h.265. Being able to play content back on various devices is a big factor. Plus, the open source encoders will take a long time to really become efficient. The bleeding edge will always have access to custom builds or nightly builds.
So yeah, we'd totally sit there and wait until 2015 for an h.265 stable release. (not saying we will, but it's certainly possible)