<aphirst> have you guys already discussed this today? http://lists.freedesktop.org/archive...er/047084.html
<aphirst> the claim is the possibility to decode Hi10P using VDPAU on AMD graphics hardware, thanks to some state tracker stuff implemented for the sake of OpenMAX
* sL1pKn07 is now known as sL1p|OuT
<JEEB> aphirst, isn't that just basically adding support to the framework to note Hi10P stuff as such?
<JEEB> so that if some kind of hardware that supports it comes around it could be handled, and otherwise just thrown away
<JEEB> decoding in this case most probably means "parse" in this case methinks
<JEEB> yeah, seems so
<JEEB> I would be very surprised if anything on the end-user level of things would have Hi10P decoding support
<JEEB> because the only hardware I actually know that can handle it costs a LOT
<JEEB> (and intra only in many cases, as it's meant purely for the "pro" use cases of high bit rate 10bit H.264)
<aphirst> so you'd say that this, in fact, isn't going to give any tangible benefit
<aphirst> (to 'typical' hardware owners, now)
<JEEB> that patch has absolutely nothing to do with actual picture decoding
<JEEB> it does let stuff actually distinguish between Hi10P and the other normally used H.264 profiles, though
<aphirst> that clears that up for me
<aphirst> it smelled a lot of 'too good to be true' but i sure as hell couldnt tell for myself
* Oleg_ (~firstname.lastname@example.org) has joined
<aphirst> thanks mang
<Oleg_> we need to type ./update if we wanna sync our local git copy with the latest updates?
<JEEB> basically it seems like there was already a return value for Hi10P, but before now such stuff would have gotten output as "unknown stuff"
<JEEB> and now it actually outputs "this is Hi10P AVC"
<JEEB> and the second patch then adds the Hi10P value into the list of things "this is AVC, yo" somewhere else
<JEEB> basically unknown -> Hi10P AVC
<aphirst> what effect would this have on the way players fallback to software decoding of this content?
<aphirst> does it simplify the logic anywhere?
<aphirst> is it completely transparent?
<JEEB> depends, but it does let whatever is calling this stuff get some extra info
<JEEB> I have no idea what APIs these are that got changed
<JEEB> and most players already check the profile on their side to begin with methinks ^^;
<aphirst> so basically
<JEEB> yes and no
<JEEB> it's a useful change, since now the API gives some extra info
<JEEB> it's a non-useful change for end users tho :P
<aphirst> but its not a "groundbreaking" one
<aphirst> well, extra info is good