filesink by default has "sync" set to false, so GStreamer is probably dumping data as fast as it can. If you use "filesink sync=true" it should append at whatever bitrate vaapiencode_h264 works at by default.
This sounds like more of a GStreamer topic than libva. You might want to post more info about the pipeline you're trying to create on a GStreamer forum or list. On Wed, Feb 25, 2015 at 4:00 PM, Juan Robles <filosangra...@gmail.com> wrote: > Hi, > > I've managed to package gstreamer-vaapi 0.5.9 with all its dependencies > for my distribution, ubuntu 12.04 > > My application is tied up for now to gstreamer 0.10, but I badly need > vaapiencode_h264 element to work as I'm trying to use an underpowered > system for some tasks and hardware assisted h264 encoding would help. > > The problem is that with a testing pipeline like this: > > gst-launch-0.10 videotestsrc pattern=1 ! > video/x-raw-yuv,width=1280,height=720 ! vaapiencode_h264 ! mp4mux ! > filesink location=output.mp4 > > All I get is a muxed file with a crazy bitrate, something like 130Mbps, > and a really high cpu use (100% in one cpu thread). > > I know gstreamer 0.10 support is deprecated, and gstreamer-vaapi 0.5.9 was > the last version that I was able to build, as 0.5.10 requires something > that my gstreamer 0.10 packages don't have. > > Any ideas on how I could get gstreamer-vaapi encoding to work in this case? > > > > _______________________________________________ > Libva mailing list > Libva@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/libva > >
_______________________________________________ Libva mailing list Libva@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libva
