Re: [meta-intel] GStreamer 1.0 and VAAPI
On 9 January 2015 at 20:58, Chris Tapp opensou...@keylevel.com wrote: I think I've got it working (well, building and in the image!), but it looks like GStreamer doesn't like my pipeline for a DVB-T stream (mpegts) as this starts with a few empty frames which causes libva to terminate the pipeline... I can't really help with this, but #gstreamer will be able to. Ross -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] GStreamer 1.0 and VAAPI
On 7 January 2015 at 17:43, Chris Tapp opensou...@keylevel.com wrote: Ignore gst-va-intel, all you need is gstreamer-vaapi-1.0 to get GStreamer 1.0 to do VAAPI. Thanks. What about va-intel and libva-intel-driver - looks like I need these? Erm, yeah, libva-intel-driver might be useful if you want it to actually work, I should have mentioned that! That said 1.0 and 0.10 shouldn't be conflicting, what were the errors? I don't have the exact message to hand at the moment, but it was something to do with 0.10 shared libs being installed with the same name as the corresponding 1.0 libs. The 0.10 then took precedence as they were installed later. 0.10 was pulled in due to some RDEPENDS in gst-va-intel (e.g. for gst-plugins-good-isomp4, which is 0.10 specific). Ah right, that's the problem where private libraries in different directories with the same basename get confused for the same library. Known problem and I thought there was a workaround. I'll dig. For what it's worth I plan on getting the va metapackages removed from meta-intel now as they're pointless - they were created to abstract the choice between EMGD and gst-vaapi but EMGD doesn't exist in meta-intel any more. Ross -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] GStreamer 1.0 and VAAPI
On 2 January 2015 at 22:35, Chris Tapp opensou...@keylevel.com wrote: As I'm using GStreamer 1.0, I'm pulling gstreamer-vaapi-1.0 in to my image. How does gst-va-intel relate to this? I've tried adding this to my image as well, but that results in GStreamer 0.10 being pulled in, resulting in installation conflicts with the 1.0 libraries. Ignore gst-va-intel, all you need is gstreamer-vaapi-1.0 to get GStreamer 1.0 to do VAAPI. That said 1.0 and 0.10 shouldn't be conflicting, what were the errors? Ross -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
Re: [meta-intel] GStreamer 1.0 and VAAPI
Hi Ross, On 7 Jan 2015, at 12:02, Burton, Ross ross.bur...@intel.com wrote: On 2 January 2015 at 22:35, Chris Tapp opensou...@keylevel.com wrote: As I'm using GStreamer 1.0, I'm pulling gstreamer-vaapi-1.0 in to my image. How does gst-va-intel relate to this? I've tried adding this to my image as well, but that results in GStreamer 0.10 being pulled in, resulting in installation conflicts with the 1.0 libraries. Ignore gst-va-intel, all you need is gstreamer-vaapi-1.0 to get GStreamer 1.0 to do VAAPI. Thanks. What about va-intel and libva-intel-driver - looks like I need these? That said 1.0 and 0.10 shouldn't be conflicting, what were the errors? I don't have the exact message to hand at the moment, but it was something to do with 0.10 shared libs being installed with the same name as the corresponding 1.0 libs. The 0.10 then took precedence as they were installed later. 0.10 was pulled in due to some RDEPENDS in gst-va-intel (e.g. for gst-plugins-good-isomp4, which is 0.10 specific). -- Chris Tapp opensou...@keylevel.com www.keylevel.com You can tell you're getting older when your car insurance gets real cheap! -- ___ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
