Bug 92134 - [gst-vaapi-master] [gst-vaapi-0.6] vaapidecode is unable to connect with vaapiencode_h264
Summary: [gst-vaapi-master] [gst-vaapi-0.6] vaapidecode is unable to connect with vaap...
Status: RESOLVED NOTOURBUG
Alias: None
Product: libva
Classification: Unclassified
Component: intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: highest blocker
Assignee: haihao
QA Contact: Sean V Kelley
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-27 05:13 UTC by janardana
Modified: 2015-09-30 04:46 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description janardana 2015-09-27 05:13:22 UTC
I installed latest intel graphics for linux by following wiki on ubuntu 15.04/intel baytrail (lenevo B50 touch laptop).:

https://01.org/linuxgraphics/downloads/intel-graphics-installer-linux-1.2.0

I am trying to execute following pipeline : (It seems that vaapidecode is unable to connect with vaapiencode_h264 .  Can anyone tell me why it is failing  ? )



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.
libva info: VA-API version 0.38.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_38
libva info: va_openDriver() returns 0
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Got context from element 'vaapidecode0': gst.vaapi.Display=context, display=(GstVaapiDisplay)NULL;
Progress: (open) Opening Stream
Progress: (connect) Connecting to rtsp://admin:admin@192.168.0.162:554/cam/realmonitor?channel=1&subtype=0
Progress: (open) Retrieving server options
Progress: (open) Retrieving media info
Progress: (request) SETUP stream 0
Progress: (open) Opened Stream
Setting pipeline to PLAYING ...
New clock: GstSystemClock
Progress: (request) Sending PLAY request
0:00:00.304117302  3863 0x7fef1c03f800 FIXME                default gstutils.c:3766:gst_pad_create_stream_id_internal:<fakesrc0:src> Creating random stream-id, consider implementing a deterministic way of creating a stream-id
Progress: (request) Sending PLAY request
Progress: (request) Sent PLAY request
Redistribute latency...
Redistribute latency...
0:00:00.709249061  3863      0x1608450 WARN                GST_PADS gstpad.c:3989:gst_pad_peer_query:<vaapidecode0:src> could not send sticky events
0:00:00.832054174  3863 0x7fef1c03f8f0 WARN                 basesrc gstbasesrc.c:2943:gst_base_src_loop:<udpsrc1> error: Internal data flow error.
0:00:00.832118375  3863 0x7fef1c03f8f0 WARN                 basesrc gstbasesrc.c:2943:gst_base_src_loop:<udpsrc1> error: streaming task paused, reason not-negotiated (-4)
ERROR: from element /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0/GstUDPSrc:udpsrc1: Internal data flow error.
Additional debug info:
gstbasesrc.c(2943): gst_base_src_loop (): /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0/GstUDPSrc:udpsrc1:
streaming task paused, reason not-negotiated (-4)
Execution ended after 0:00:00.528707555
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
0:00:00.842904885  3863      0x16082d0 WARN                 rtspsrc gstrtspsrc.c:6051:gst_rtspsrc_send:<rtspsrc0> error: Got error response: 455 (Method Not Valid in This State).
0:00:00.843011339  3863      0x16082d0 WARN                 rtspsrc gstrtspsrc.c:8011:gst_rtspsrc_pause:<rtspsrc0> error: Could not send message. (Generic error)
Setting pipeline to NULL ...
Freeing pipeline ...
janardana@janardana-Lenovo-B50-30-Touch:~/src/gstreamer/head$
Comment 1 janardana 2015-09-27 05:14:26 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
Comment 2 Víctor Jáquez 2015-09-29 09:06:42 UTC
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
Comment 3 haihao 2015-09-30 04:46:01 UTC
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.