[T800]

Good job HEVC is four letters :-)

<ducks>

You might want to duck further than that.

Guys, please take that discussion elsewhere.

On topic:
For VP9 and HEVC support we need to upgrade ffmpeg to a newer version than is currently in the source. This is a big undertaking and usually brings quite a few issues, which is why it is generally done once every release cycle. It was done when development on Gotham started.

At this moment we are in feature freeze for the Gotham release which means no new stuff will go in.

The first time you will see VP9 or HEVC support is sometime after the release of v13.

See the wiki article about HEVC (wiki)

I won't pretend to know anything about upgrading ffmpeg but if it's only done once every release cycle why isn't it done towards the end (obvioulsy with enough time to hammer out issues) then we aren't using a 12 month ffmepg or is that 12 months needed to get it sorted?

[Prof Yaffle]

@T800 - my understanding is that they tried the merge, and it failed badly with memory leaks. So the decision was made to skip it now rather than delay Gotham further.; it almost doesn't matter when the merge was tried, the implications were too great to just patch quickly and risk releasing dodgy software.

At some point, you have to draw a line in the sand and go with something that's releasable, and that's the feature set that's now in place. H.265 *will* come, support *will* improve, XBMC *will* include it - just not now.

[Ned Scott]

Because adjusting it for use in XBMC, so that things run smoothly and there are less bugs, takes time. It's not an arbitrary decision of when to include the update. Hopefully this won't always be the case, and hopefully one day you could just slap some FFmpeg update into an existing XBMC install as if it were an add-on, but a lot of other things have to happen first.