Tvheadend

I think many of us are waiting for this :-). If you do a search for vaapi on the site you will find a few workarounds. Either pipe the output through ffmpeg or install lekmas build which has presets in the gui for vaapi(not that stable though).

//Anders

Thank you for reply
I already checked you wrote

Hope vaapi native support in tvh soon

Vaapi is 1/2 of potential of QSV performance.

Drivers (back-ends) that implement VA-API
   Broadcom Crystal HD (work-in-progress): * <http://gitorious.org/crystalhd-video>
   Intel Embedded Graphics Drivers (IEGD): * <http://edc.intel.com/Software/Downloads/IEGD/>
   Intel Embedded Media and Graphics Drivers (EMGD): * <http://edc.intel.com/Software/Downloads/EMGD/>
   Intel GMA500 driver (OEM only): * <https://launchpad.net/~ubuntu-mobile/+archive/ppa>
   Intel integrated G45 graphics chips: * <http://cgit.freedesktop.org/vaapi/intel-driver>
   IMG VXD375/385 and VXE250/285 video engines: * <http://cgit.freedesktop.org/vaapi/pvr-driver/> 
   VDPAU back-end for NVIDIA and VIA chipsets: * <http://cgit.freedesktop.org/vaapi/vdpau-driver/>
   VIA / S3 Graphics Accelerated Linux Driver: * <http://www.s3graphics.com/en/index.aspx>
   XvBA / ATI Graphics Backend (for proprietary driver only) * <http://cgit.freedesktop.org/vaapi/xvba-driver/> 

I would also like to see vaapi options in the transcode/av options. I can't get intel QSV working on my ubuntu server... I have a vaapi compatible build of ffmpeg but don't how to use it for livetv transcoding.

Chris Koster wrote:

I would also like to see vaapi options in the transcode/av options. I can't get intel QSV working on my ubuntu server... I have a vaapi compatible build of ffmpeg but don't how to use it for livetv transcoding.

You can use an IPTV network with a pipe:// URI using ffmpeg' h264_vaapi codec. However, that is presently the only way I know of to use vaapi with Tvheadend.

Your other option is to modify the source to implement vaapi transcoding.

Using a dynamically linked ffmpeg with Tvheadend to get vaapi encoding is broken in Tvheadend, as it passes additional options that are hardcoded to avlib that cause errors upon trying to create the stream. This is mostly due to passing profile and preset options which work for libx264, but not h264_vaapi, as far as I can tell.

Hi Robert, thanks for your answer. I read about the pipe possibility but my source is not iptv. I'm watching tv with usb dvb-c tuners. So it's only possible with iptv source?

Chris Koster wrote:

Hi Robert, thanks for your answer. I read about the pipe possibility but my source is not iptv. I'm watching tv with usb dvb-c tuners. So it's only possible with iptv source?

Yes and no. The pipe:// protocol only works with IPTV networks in Tvheadend, but that does not mean that only IPTV streams can be used as IPTV networks.

If you can get your DVB-C stream into ffmpeg, then you can use that command to craft your pipe:// URI. Perhaps something like:

pipe:///usr/bin/ffmpeg -hwaccel vaapi -hwaccel_output_format vaapi -vaapi_device /dev/dri/renderD128 -i [however you access your DVB stream] -vf 'format=nv12|vaapi,hwupload' -c:v h264_vaapi -c:a copy -f mpegts pipe:1

Thanks but I don't know what to fill in at [however you access your DVB stream]. This is just the current input/service/channel

This should work:

http://user:[email protected]:9981/stream/channelnumber/1?profile=pass

Change user, pass and channelnumber.
You can insert your pipe-url as iptv automatic network.

It would be easier if you copy your relevant channels/URLs in m3u-file, something like in attachement. In iptv network you have to enter the path to your file, beginning from root; i.e.: file:///home/hts/test.m3u

Giuseppe Sicilia wrote:

This should work:

http://user:[email protected]:9981/stream/channelnumber/1?profile=pass

Change user, pass and channelnumber.
You can insert your pipe-url as iptv automatic network.

It would be easier if you copy your relevant channels/URLs in m3u-file, something like in attachement. In iptv network you have to enter the path to your file, beginning from root; i.e.: file:///home/hts/test.m3u

When using service on same machine or private network, user access can be without user and password by enabling user "*" with responding ip networks