<div dir="ltr">On Fri, May 31, 2013 at 3:10 PM, Kenni Lund <span dir="ltr"><<a href="mailto:kenni@kelu.dk" target="_blank">kenni@kelu.dk</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2013/5/26 Justin Johnson <<a href="mailto:justin.johnson3@gmail.com">justin.johnson3@gmail.com</a>>:<br>
<div class="im">> It's what I'm currently using as a frontend only. It works pretty well. All<br>
> my experience is with FFMPEG playback; I attempted to get VAAPI working but<br>
> didn't have great success.<br>
<br>
</div>Good to know. Of curiosity, did you try to setup the drivers with the<br>
new Intel Driver Manager? It appears that some people have greater<br>
success with VAAPI and the graphics stack from new installer.<br>
<a href="http://www.phoronix.com/scan.php?page=news_item&px=MTMyNDQ" target="_blank">http://www.phoronix.com/scan.php?page=news_item&px=MTMyNDQ</a><br>
<div class="im"><br>
> I'm not sure about the limited audio capabilities you mention, is this the<br>
> fact that it cannot output multi-channel PCM? There is a setting in the<br>
> frontend somewhere to always re-encode to dolby. This is how I use multi<br>
> channel audio.<br>
<br>
</div>No, I was simply talking about the lack of physical connections :) I<br>
would have prefered if it was possible to connect the frontend<br>
directly to my DAC or my amplifier.<br>
<br>
Thanks,<br>
<div class="HOEnZb"><div class="h5">Kenni<br></div></div></blockquote><div><br></div><div style>Yes, I did use the Intel Driver Manager, before finding that little gem I was unable to get VAAPI working at all. It worked, but there was some problem, I no longer recall what it was though. Perhaps a lack of deinterlacing?</div>
</div></div></div>