Recherche avancée

Sur d’autres sites (6607)

• How to resolve the source of an RTSP server unstable problem ?

  5 mars 2021, par EricLu

  I have already build an application by gstreamer rtsp-server with its appsrc.
It's workingflow like test-appsrc. And I implement static void need_data (GstElement * appsrc, guint unused, MyContext * ctx) function using read from a IP camera's RTSP stream cv::VideoCapture in need_data.

  


  All this function is working well and it's have worked already for a day.

  


  However, I must use some algorithm deal with the IP camera source by OpenCV. When I do this algorithm at
need_data. The RTSP Server seems unstable it always print something like the below :

  


  (opencv_rtsp_server:175041): GStreamer-CRITICAL **: 15:08:38.738: gst_mini_object_add_parent: assertion 'object != NULL' failed

(opencv_rtsp_server:175041): GStreamer-CRITICAL **: 15:08:38.739: gst_memory_get_sizes: assertion 'mem != NULL' failed

(opencv_rtsp_server:175041): GStreamer-CRITICAL **: 15:08:38.739: gst_memory_get_sizes: assertion 'mem != NULL' failed

(opencv_rtsp_server:175041): GStreamer-CRITICAL **: 15:08:38.739: gst_memory_get_sizes: assertion 'mem != NULL' failed

(opencv_rtsp_server:175041): GStreamer-CRITICAL **: 15:08:38.739: gst_mini_object_ref: assertion 'mini_object != NULL' failed


  


  It seems the RTSP-server have losing connect appsrc.

  


  One idea to reslove this problem is imporving the algorithm as it can respond as soon as framerate is.
Maybe there are some idea about caching the output of algorithm can let the appsrc element stable.
Can some one give me some advice or trahave already build a application by gstreamer rtsp-server with its appsrc.
It's workingflow like test-appsrc. And I implement static void need_data (GstElement * appsrc, guint unused, MyContext * ctx) function using read from a IP camera's RTSP stream cv::VideoCapture in need_data.

  


  All this function is working well and it's have worked already for a day.

  


  However, I must use some algorithm deal with the IP camera source by OpenCV. When I do this algorithm at
need_data. The RTSP Server seems unstable it always print something like below :

  


  (opencv_rtsp_server:175041): GStreamer-CRITICAL **: 15:08:38.738: gst_mini_object_add_parent: assertion 'object != NULL' failed

(opencv_rtsp_server:175041): GStreamer-CRITICAL **: 15:08:38.739: gst_memory_get_sizes: assertion 'mem != NULL' failed

(opencv_rtsp_server:175041): GStreamer-CRITICAL **: 15:08:38.739: gst_memory_get_sizes: assertion 'mem != NULL' failed

(opencv_rtsp_server:175041): GStreamer-CRITICAL **: 15:08:38.739: gst_memory_get_sizes: assertion 'mem != NULL' failed

(opencv_rtsp_server:175041): GStreamer-CRITICAL **: 15:08:38.739: gst_mini_object_ref: assertion 'mini_object != NULL' failed


  


  It seems the RTSP-server has losing connect appsrc.

  


  Or h264 encoder give me error :

  


  valid fps=23 [h264 @ 0x5598f7f2ba40] illegal short term buffer state detected
[h264 @ 0x5598f7f2ba40] Missing reference picture, default is 18
valid fps=24 Invalid UE golomb code
[h264 @ 0x5598f8011580] cbp too large (3199971767) at 8 95
[h264 @ 0x5598f8011580] error while decoding MB 8 95
valid fps=24 [h264 @ 0x5598f7eab3c0] corrupted macroblock 2 51 (total_coeff=-1)
[h264 @ 0x5598f7eab3c0] error while decoding MB 2 51
valid fps=25 [h264 @ 0x5598f8011580] illegal short term buffer state detected
[h264 @ 0x5598f8011580] Missing reference picture, default is 10
valid fps=24 [h264 @ 0x5598f7f2ba40] Invalid level prefix
[h264 @ 0x5598f7f2ba40] error while decoding MB 17 49
valid fps=24 Invalid UE golomb code
[h264 @ 0x5598f7fe1280] cbp too large (3199971767) at 3 163
[h264 @ 0x5598f7fe1280] error while decoding MB 3 163
valid fps=22 [h264 @ 0x5598f8011580] illegal short term buffer state detected
[h264 @ 0x5598f8011580] Missing reference picture, default is 40
valid fps=24 [h264 @ 0x5598f7fe1280] illegal short term buffer state detected
[h264 @ 0x5598f7fe1280] Missing reference picture, default is 40
valid fps=25 [h264 @ 0x5598f7eab3c0] illegal short term buffer state detected
[h264 @ 0x5598f7eab3c0] Missing reference picture, default is 36


  


  One idea to resolve this problem is improving the algorithm as it can respond as soon as framerate is.
Maybe there is some ideas about caching the output of the algorithm that can let the appsrc element stable.
Can someone give me some advice or strategy about caching it or resolve its idea ?

  


  Appreciate it so much...

  


• Revision bcaf1d69ec : Moved call to vp9_clear_system_state() to a proper location The commit moved a

  22 juillet 2014, par Yaowu Xu

  Changed Paths :
   Modify /vp9/encoder/vp9_encoder.c

  
  
  Moved call to vp9_clear_system_state() to a proper location

  The commit moved a call to vp9_clear_system_state() to a correct
  location, i.e. prior function calls using floating point numbers.
  This was to fix a mismatch mmx code and sse2 version, where a
  floating point number used in adjust_frame_rate(cpi) gets NAN due
  to mmx registers being in wrong state.

  Change-Id : I40e0a6de98812000ccee6a729badb630604fd7e6

• Installing ffmpeg

  22 décembre 2016, par Jseb

  I am not an expect with linux and new to rails but trying i am trying to have my user allowed to upload video and to view them. Now I have found this gem for ruby on rails https://github.com/owahab/paperclip-ffmpeg which seem to use paperclip and the ffmpeg software to upload video on my server. However in the documentation it state you must install ffmpeg and i am not sure how. I use ubuntu 12.04 and not sure how to install it.