Re: [Mesa-dev] 10bit HEVC decoding for RadeonSI v2

2018-02-12 Thread rainer.hochec...@onlinehome.de
...@onlinehome.de> Cc: "Philipp Kerling" <pkerl...@casix.org>, s...@jkqxz.net, peter.fruehber...@gmail.com, mic...@daenzer.net, mesa-dev@lists.freedesktop.org, harry.wentl...@amd.com, lru...@libreelec.tv Betreff: Re: [Mesa-dev] 10bit HEVC decoding for RadeonSI v2 Hi Rainer,

Re: [Mesa-dev] 10bit HEVC decoding for RadeonSI v2

2018-02-12 Thread rainer.hochec...@onlinehome.de
König" <christian.koe...@amd.com> An: "Philipp Kerling" <pkerl...@casix.org>, s...@jkqxz.net Cc: rainer.hochec...@onlinehome.de, peter.fruehber...@gmail.com, mic...@daenzer.net, mesa-dev@lists.freedesktop.org, harry.wentl...@amd.com, lru...@libreelec.tv Betreff: Re

Re: [Mesa-dev] 10bit HEVC decoding for RadeonSI v2

2018-02-12 Thread rainer.hochec...@onlinehome.de
casix.org>, s...@jkqxz.net Cc: rainer.hochec...@onlinehome.de, peter.fruehber...@gmail.com, mic...@daenzer.net, mesa-dev@lists.freedesktop.org, harry.wentl...@amd.com, lru...@libreelec.tv Betreff: Re: [Mesa-dev] 10bit HEVC decoding for RadeonSI v2 Am 09.02.2018 um 21:35 schrieb Philipp Ke

Re: [Mesa-dev] 10bit HEVC decoding for RadeonSI v2

2018-02-11 Thread Christian König
quot; <pkerl...@casix.org>, s...@jkqxz.net, peter.fruehber...@gmail.com, mic...@daenzer.net, mesa-dev@lists.freedesktop.org, harry.wentl...@amd.com, lru...@libreelec.tv *Betreff:* Re: [Mesa-dev] 10bit HEVC decoding for RadeonSI v2 Hi Rainer, the render thread doesn't wait either. See wh

Re: [Mesa-dev] 10bit HEVC decoding for RadeonSI v2

2018-02-11 Thread Christian König
eter.fruehber...@gmail.com, mic...@daenzer.net, mesa-dev@lists.freedesktop.org, harry.wentl...@amd.com, lru...@libreelec.tv *Betreff:* Re: [Mesa-dev] 10bit HEVC decoding for RadeonSI v2 Am 09.02.2018 um 21:35 schrieb Philipp Kerling: > Hi, > > resurrecting this thread again since ther

Re: [Mesa-dev] 10bit HEVC decoding for RadeonSI v2

2018-02-11 Thread Christian König
Am 11.02.2018 um 11:35 schrieb Philipp Kerling: Hi, 2018-02-11 (日) の 11:02 +0100 に Christian König さんは書きました: Am 09.02.2018 um 21:35 schrieb Philipp Kerling: Hi, resurrecting this thread again since there's been some progress on the Kodi side. For the EGL part, see

Re: [Mesa-dev] 10bit HEVC decoding for RadeonSI v2

2018-02-11 Thread Philipp Kerling
Hi, 2018-02-11 (日) の 11:02 +0100 に Christian König さんは書きました: > Am 09.02.2018 um 21:35 schrieb Philipp Kerling: > > Hi, > > > > resurrecting this thread again since there's been some progress on > > the > > Kodi side. > > > > > For the EGL part, see > >

Re: [Mesa-dev] 10bit HEVC decoding for RadeonSI v2

2018-02-11 Thread Christian König
Am 09.02.2018 um 21:35 schrieb Philipp Kerling: Hi, resurrecting this thread again since there's been some progress on the Kodi side. For the EGL part, see and . We recently

Re: [Mesa-dev] 10bit HEVC decoding for RadeonSI v2

2018-02-10 Thread Philipp Kerling
Hi, resurrecting this thread again since there's been some progress on the Kodi side. > For the EGL part, see > and > . We recently started testing vaExportSurfaceHandle support,

Re: [Mesa-dev] 10bit HEVC decoding for RadeonSI v2

2017-10-01 Thread Mark Thompson
On 28/09/17 04:41, Lukas Rusak wrote: > Hello all, > > I'm bumping this to layout some progress that has been made on our (Kodi) > side and hopefully we can create a road map for what needs to be done on > the amd side to get it working with our vaapi implementation. > > I have merged the

Re: [Mesa-dev] 10bit HEVC decoding for RadeonSI v2

2017-09-28 Thread Lukas Rusak
Hello all, I'm bumping this to layout some progress that has been made on our (Kodi) side and hopefully we can create a road map for what needs to be done on the amd side to get it working with our vaapi implementation. I have merged the drm/kms display code into kodi. So in master currently is

Re: [Mesa-dev] 10bit HEVC decoding for RadeonSI v2

2017-06-25 Thread Peter Frühberger
Hi all, just as information: https://github.com/FernetMenta/kodi-agile/commit/ca8119b4e11a52415125af959f220b280f56ecae Rainer moved the specific parts of the buffer sharing into a separate infrastructure see the VAAPIEGL.cpp and VAAPIEGL.h in the above patch. This basically encapsulates the

Re: [Mesa-dev] 10bit HEVC decoding for RadeonSI v2

2017-03-20 Thread Peter Frühberger
Hi Christian, we use it the following way: Dependend on the surface NV12 vs. P010 we use: https://github.com/FernetMenta/kodi-agile/blob/master/xbmc/cores/VideoPlayer/DVDCodecs/Video/VAAPI.cpp#L1416 R8 and GR88 or alternatively:

Re: [Mesa-dev] 10bit HEVC decoding for RadeonSI v2

2017-03-20 Thread Peter Frühberger
Hi Christian, thank you for your message. We are still wondering about the render part. How do you want us to display the decoded surfaces? Looking at mpv it seems it will only work via vaPutSurface and is therefore tight to X11. That means it's dependend on the visuals 8 bit only. We are

Re: [Mesa-dev] 10bit HEVC decoding for RadeonSI v2

2017-03-20 Thread rainer.hochec...@onlinehome.de
> for example how does synchronization happen between the two APIs?   right, vaapi seems not as matured as vdpau in this regard. But Kodi's multithreading design does cope with this. We call vaSyncSurface before feeding vpp and before maping va buffers to GL.   I suggest to keep it simple

Re: [Mesa-dev] 10bit HEVC decoding for RadeonSI v2

2017-03-20 Thread Marek Olšák
On Sun, Mar 19, 2017 at 2:49 PM, Christian König wrote: > Hi Peter, > > Adding Michel and Marek for the Mesa interop side and Harry for the display > side. > > How do you want us to display the decoded surfaces? > > Well to make a long story short: I don't have the

Re: [Mesa-dev] 10bit HEVC decoding for RadeonSI v2

2017-03-20 Thread Alex Deucher
On Sun, Mar 19, 2017 at 9:49 AM, Christian König wrote: > Hi Peter, > > Adding Michel and Marek for the Mesa interop side and Harry for the display > side. > > How do you want us to display the decoded surfaces? > > Well to make a long story short: I don't have the

Re: [Mesa-dev] 10bit HEVC decoding for RadeonSI v2

2017-03-19 Thread Christian König
I suggest to keep it simple from a driver perspective and require applications to use vaSyncSurface Currently our vaSyncSurface doesn't really do what the name suggests. All what we do is flushing the command buffers and that for good reasons. That the application waits for all decoding to

Re: [Mesa-dev] 10bit HEVC decoding for RadeonSI v2

2017-03-19 Thread Christian König
What do you think? In general that it might work, but basic problem is the API design once more. While with VDPAU the steps where applications asks OpenGL to interop with VDPAU and the two APIs can do all the handshaking internally. With VA-API we have Application exporting buffers from

Re: [Mesa-dev] 10bit HEVC decoding for RadeonSI v2

2017-03-19 Thread Christian König
Hi Peter, Adding Michel and Marek for the Mesa interop side and Harry for the display side. How do you want us to display the decoded surfaces? Well to make a long story short: I don't have the slightest idea. Ideally we would of the same handling as Intel so that you guys don't have

Re: [Mesa-dev] 10bit HEVC decoding for RadeonSI v2

2017-03-13 Thread rainer.hochec...@onlinehome.de
Hi Christian,   I already removed the check for Intel in my dev branch. On startup Kodi does a functional test if vaapi works. If the test passes, it is availalbe regarless of the underlying type of hardware/driver.   Regards, Rainer   Gesendet: Mittwoch, 08. März 2017 um 13:29 Uhr Von: 

Re: [Mesa-dev] 10bit HEVC decoding for RadeonSI v2

2017-03-08 Thread Mark Thompson
On 08/03/17 12:29, Christian König wrote: > Hi guys, > > I finally found time testing this and hammering out (hopefully) all the > remaining bugs. Playing a 10bit HEVC file through VAAPI with mpv/ffmpeg git > master from about two days ago now works flawlessly and has only about 15% CPU > load on

[Mesa-dev] 10bit HEVC decoding for RadeonSI v2

2017-03-08 Thread Christian König
Hi guys, I finally found time testing this and hammering out (hopefully) all the remaining bugs. Playing a 10bit HEVC file through VAAPI with mpv/ffmpeg git master from about two days ago now works flawlessly and has only about 15% CPU load on one core on a Kaveri system. The VDPAU path should