Summary: | [gst-vaapi-master] [gst-vaapi-0.6] vaapidecode is unable to connect with vaapiencode_h264 | ||
---|---|---|---|
Product: | libva | Reporter: | janardana <janardanadasa3> |
Component: | intel | Assignee: | haihao <haihao.xiang> |
Status: | RESOLVED NOTOURBUG | QA Contact: | Sean V Kelley <seanvk> |
Severity: | blocker | ||
Priority: | highest | CC: | janardanadasa3, jocelyn.li |
Version: | unspecified | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
janardana
2015-09-27 05:13:22 UTC
GST_DEBUG=3 gst-launch-1.0 flvmux name=mux streamable=true ! rtmpsink sync=true location="rtmp://xxxxxxx" rtspsrc location="rtsp://admin:admin@192.168.0.162:554/cam/realmonitor?channel=1&subtype=0" ! rtph264depay ! queue ! h264parse ! vaapidecode ! queue ! vaapiencode_h264 rate-control=cbr tune=high-compression ! mux. This works fine with older vaapi <0.6 (default version in ubuntu 15.04). Please fix this bug for latest vaapi-0.6 or vaapi-master branch As Sree answered you in the mailing list [1], here is not the correct place to file this bug. In my opinion this report should be closed and you should open a new one in the gstreamer-vaapi's bugtracker [2], providing more information about your problem. Mainly, as Sree already said, provide a log with GST_DEBUG=vaapi*:4, or maybe this other one GST_DEBUG="vaapi*:4,*:3" (the former gives information about the rest of the elements in the pipeline) Finally, spamming the personal emails of the hackers for bug reports, is not considered polite :) 1. http://lists.freedesktop.org/archives/libva/2015-September/003549.html 2. https://bugzilla.gnome.org/enter_bug.cgi?product=gstreamer-vaapi Please file a bug in https://bugzilla.gnome.org/enter_bug.cgi?product=gstreamer-vaapi |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.