• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 98 subscribers
  • Views 511 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux/am5749: GStreamer ducatih264dec

Oleg Solovev
Expert 1985 points
Other Parts Discussed in Thread: AM5749

Hello support!!

I use custom board based on AM5749(Processor SDK Linux 06_03_00_106 ) and (SDK Linux 05.02.00.10).

I tryed to work with rtsp stream and use this one command: gst-launch-1.0 rtspsrc location=rtsp://50.197.223.170:554/axis-media/media.amp latency=1300 num-buffers=1000 ! queue ! rtph264depay ! h264parse ! ducatih264dec ! vpe ! 'video/x-raw, format=(string)NV12, width=(int)720, height=(int)480' ! waylandsink

The problem is..it is work on 05.02.00.10 and doesn't work on 06_03_00_106. Whats is wrong?

Log:

root@am57xx-evm:~# gst-launch-1.0 rtspsrc location=rtsp://50.197.223.170:554/axis-media/media.amp latency=1300 num-buffers=1000 ! queue ! rtph264depay ! h264parse ! ducatih264dec ! vpe ! 'video/x-raw, format=(string)NV12, width=(int)720, height=(int)480' ! waylandsink
Setting pipeline to PAUSED ...
Caught SIGSEGV
#0 0xb6d2bc78 in __waitpid (pid=1891, stat_loc=0xbea3816c, options=0)
#1 0xb6d5cefe in g_on_error_stack_trace () from /usr/lib/libglib-2.0.so.0
#2 0x00013076 in ?? ()
Spinning. Please run 'gdb gst-launch-1.0 1890' to continue debugging, Ctrl-C to quit, or Ctrl-\ to dump core.

BR,

Oleg

  • 0
    TI__Guru** 113810 points

    Hi Oleg,

    Lets try to see if this gets you through the problem.

    I've attached H264 parser library from the PSDKLA 5 and this needs to be copied to PSDKLA 6 rootfs.

    Copy the attached .so file in to the following location in your target rootfs at this location - /usr/lib/gstreamer-1.0/

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/libgstvideoparsersbad.so

    And then you can provide feedback if this resolves the problem.

    Regards

    Karthik

  • 0 in reply to Karthik Ramanan
    Expert 1985 points

    Hi Karthik..no it is still doesn't work. If it is help ...it is look like this..

    BR, Oleg

  • 0 in reply to Oleg Solovev
    TI__Guru** 113810 points

    Oleg,

    It seems like the original issue of the GStreamer crash is resolved. Please confirm that.

    I cannot make out very clearly what that image corresponds to but it looks like you are getting something on the screen. You may need to investigate the pipeline further if you have just got to this point.

    Regards
    Karthik

  • 0 in reply to Karthik Ramanan
    Expert 1985 points

    Karthik,

    It seems like the original issue of the GStreamer crash is resolved. Please confirm that.

    The same situation was before manipulations with library. I mean nothing has changed.

    BR,
    Oleg
  • 0 in reply to Oleg Solovev
    TI__Guru** 113810 points

    Oleg,

    I'm sorry, I do not understand.

    Are you still crashing with this below error after the change?

    Oleg Solovev said:
    root@am57xx-evm:~# gst-launch-1.0 rtspsrc location=rtsp://50.197.223.170:554/axis-media/media.amp latency=1300 num-buffers=1000 ! queue ! rtph264depay ! h264parse ! ducatih264dec ! vpe ! 'video/x-raw, format=(string)NV12, width=(int)720, height=(int)480' ! waylandsink
    Setting pipeline to PAUSED ...
    Caught SIGSEGV
    #0 0xb6d2bc78 in __waitpid (pid=1891, stat_loc=0xbea3816c, options=0)
    #1 0xb6d5cefe in g_on_error_stack_trace () from /usr/lib/libglib-2.0.so.0
    #2 0x00013076 in ?? ()
    Spinning. Please run 'gdb gst-launch-1.0 1890' to continue debugging, Ctrl-C to quit, or Ctrl-\ to dump core.

    Regards

    Karthik

  • +1 in reply to Karthik Ramanan
    Expert 1985 points

    I'm sorry, Karthik I was wrong here...it is seems like problem with pipeline settings. The reason of this errors  was stoped weston and matrix on 06_03_00_106. I did couple of tests it is work fine. I will close this question but I didn't understood why you close my previous question about enconding 4stream ???