[mythtv] mythtv 4K HEVC main 10 hardware video decoding

[Stuart Auchterlonie]

On 19/10/17 21:40, Andreas Mayer wrote:
> Hi,
> 
> I noticed 0.29 configure added options  --enable-cuda and --enable-cuvid.
> 
> But it looks like those options are just added for ffmpeg configuration
> and there is currently no Nvidia CUDA/CUVID/NVDEV support for hardware
> assisted video decoding available in mythtv?
> 

Correct, there is currently no direct support for CUDA based hardware
assist

> I'm asking because after buying a Nvida GT 1030 (which should support 4K
> HEVC Main 10 profile) I had to find out that VDPAU currently is not able
> to use this hardware capabilities (only main profile, and because of
> architectural limitations may never be able to do so) and Nvidia seems
> to provide future development for CUDA only.
> 
> What would be needed to use ffmpeg's existing HEVC CUDA hardware
> acceleration support in mythtv, would one need to write videooutput_cuda
> or is there something else that needs to be done?
> 

Not sure on this.

> Or would one be better off switching from Nvidia to Intel's Kaby Lake
> with VAAPI or something else?

That has its own set of pitfalls. Like right now on Fedora26, vaapi
fails to initialize, because wayland has removed the dri2 interface
that libva uses behind the scenes when you connect to wayland via X11
interfaces.

The TODO here is to connect to wayland directly, and then use
libva-wayland to interact with the display.


Regards
Stuart

> 
> It's not that much 4K HEVC content is currently availabe, but at least
> on Astra 19.2E in Europe all 4K (test) channels are using HEVC main 10
> profile (and currently I don't even own a 4K TV ;-), but I would like to
> be prepared - chicken and egg problem)
> 
> Thank you,
> 
> Andreas
> 
> 
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-dev
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org