Date: Mon, 19 Oct 2015 17:07:07 +0200 From: Juan =?iso-8859-1?b?UmFt824=?= Molina Menor <listjm@club.fr> To: Arto Pekkanen <isoa@kapsi.fi> Cc: freebsd-x11@freebsd.org Subject: Re: Success! Was: Testing the new i915 driver (HD Graphics 4400) Message-ID: <5625071B.1020202@club.fr> In-Reply-To: <5624F6F3.1090901@kapsi.fi> References: <of89cjrnwte659h4soymbopv.1445176143433@email.android.com> <add65c83cf966f5cd4d358f3ba3af305@kapsi.fi> <5624F31E.4090904@club.fr> <5624F6F3.1090901@kapsi.fi>
next in thread | previous in thread | raw e-mail | index | archive | help
> I am glad I was able to be of assistance :) > > Does Vimb use multimedia/gstreamer1 or multimedia/gstreamer as codec backend? GStreamer1: vimb-gtk2 depends indeed on webkit-gtk2, which depends on gstreamer1-plugins, etc. > If it uses multimedia/gstreamer, then there's nothing you can do, since multimedia/gstreamer does NOT have VAAPI plugin. multimedia/gstreamer has only VDPAU plugin (for nVidia GPUs), but not VAAPI. > > On the other hand, multimedia/gstreamer1 has multimedia/gstreamer1-vaapi plugin, which should enable hardware decoding. > > So, if Vimb uses multimedia/gstreamer1, then just install multimedia/gstreamer1-vaapi package and you should get proper hardware decoding. If this does not help, then the fault is in GStreamer1 filter priorities. Yes, I have gstreamer1-vaapi installed, but playing quality is lower with vimb than with mpv and CPU usage higher. Oh well… Best regards, Juan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5625071B.1020202>