>
>
> I was under the impression that in order to have working VAAPI/VDPAU
> accelleration we had to compile Mesa with it (which been a problem, as
> our Mesa is in maintained in base).
>
I wasn't aware of that (potential?) problem.
>
> IIRC libvaapi does compile, but fails at runtime without the Mesa
> components. Is this not accurate?
>
> I can scour the output from a quick gaming session and report back with
more details, but here is what my experience has been:
1. I built libva and intel-vaapi-driver because I knew that moonlight-qt
needed it.
2. Once I built moonlight-qt and ran it, I realized that it was using
ffmpeg to
do the actual decoding, which wasn't built with vaapi support. Upon
starting it, you get a warning message that it couldn't enable hardware
accelerated h264 decoding.
3. I rebuilt ffmpeg with --enable-vaapi.
4. moonlight-qt seemed perfectly content afterwards, and if there were any
errors/exceptions, they are hidden away in logs. The gaming experience
was perfectly acceptable. I spent a good 10-15 minutes playing
Borderlands 3 to test it out.
So, again, I will collect the full output and attach to a follow-up email.
--
--Brad DeMorrow
