Recherche avancée

Sur d’autres sites (5714)

• DirectShow RTSP SourceFilter with MPEG-4 Video Stream

  5 octobre 2011, par 6.45.Vapuru

  I create a simple direct show source filter using FFmpeg.I read rtp packets from RTSP source and give them to decoder. It works for h264 stream.

  MyRtspSourceFilter[H264 Stream] ---> h264 Decoder --> Video Renderer

  The bad news is that it does not work for MPEG-4. I can able to connect my rtsp source filter with MPEG-Decoder. I got no exception but video renderer does not show anything. Actually just show one frame then nothing [just stop]... Decoders and Renderers are 3rd party so i can not debug them.

  MyRtspSourceFilter[MP4 Stream] ---> MPEG-4 Decoder --> Video Renderer

  I can able to get rtp packets from MPEG-4 RTSP Source using FFmpeg sucessfully.There is no problem with it.

  It seems that i have not set something(?) in my Rtsps Source
  Filter which is not necessary for H264 stream but may be important for
  MPEG-4 stream

  What may cause this h264 stream and MPEG-4 stream difference in a direct show rtsp source filter ? Any ideas.

  More Info :

  — First i try some other rtsp source filters for MPEG-4 Stream...Although my rtsp source is same i see different subtypes in their pin connections.

  — Secondly i realy get suspicious if the source is really MPEG-4 SO i check with FFmpeg...FFmpeg gives the source codec id as "CODEC_ID_MPEG4".

  Update :
  [ Hack ]

  I just set m_bmpInfo.biCompression = DWORD('xvid') it just worked fine...But it is static. How to dynamically get/determine this value using ffmpeg or other ways...

• DirectShow RTSP SourceFilter with MPEG-4 Video Stream

  20 mars 2021, par Novalis

  I create a simple direct show source filter using FFmpeg.I read rtp packets from RTSP source and give them to decoder. It works for h264 stream.

  



  MyRtspSourceFilter[H264 Stream] ---> h264 Decoder --> Video Renderer


  



  The bad news is that it does not work for MPEG-4. I can able to connect my rtsp source filter with MPEG-Decoder. I got no exception but video renderer does not show anything. Actually just show one frame then nothing [just stop]... Decoders and Renderers are 3rd party so i can not debug them.

  



  MyRtspSourceFilter[MP4 Stream] ---> MPEG-4 Decoder --> Video Renderer


  



  I can able to get rtp packets from MPEG-4 RTSP Source using FFmpeg sucessfully.There is no problem with it.

  



  


  It seems that i have not set something(?) in my Rtsps Source
 Filter which is not necessary for H264 stream but may be important for
 MPEG-4 stream

  


  



  What may cause this h264 stream and MPEG-4 stream difference in a direct show rtsp source filter ? Any ideas.

  



  More Info :

  



  — First i try some other rtsp source filters for MPEG-4 Stream...Although my rtsp source is same i see different subtypes in their pin connections.

  



  — Secondly i realy get suspicious if the source is really MPEG-4 SO i check with FFmpeg...FFmpeg gives the source codec id as "CODEC_ID_MPEG4".

  



  Update : 
[ Hack ]

  



  I just set m_bmpInfo.biCompression = DWORD('xvid') it just worked fine...But it is static. How to dynamically get/determine this value using ffmpeg or other ways...

  


• Pod in Kubernetes can not establish a RTSP session, UDP port unreachable

  7 septembre 2020, par Raphael Mazzine

  I am trying to make a connection between my pod and a camera through RTSP (using ffmpeg).

  


  My container, when running locally and in the server can establish the connection.

  


  However, in Kubernetes, looks to be able to reach and identify the camera server, but it can not initialize a stream. I did a tcpdump on my container when trying to connect and I received the following :

  


  10:55:37.065954 IP **CAMERA_SERVER_IP** > **POD_NAME**: ICMP **CAMERA_SERVER_IP** udp port 36337 unreachable, length 44

10:55:37.066003 IP **CAMERA_SERVER_IP** > **POD_NAME**: ICMP **CAMERA_SERVER_IP** udp port 36336 unreachable, length 48


  


  **CAMERA_SERVER_IP** -> is the camera server IP addresss

  


  **POD_NAME** -> is my pod's name in kubernetes.

  


  When I try locally, the first UDP port fails too, but the second can establish a connection and stream.

  


  I think this has something to do with port communication, but I am bit lost in what I should try or test.

  


  Thanks !

  


  UPDATE*

  


  Actually I found something strange.

  


  I tried again to start the connection and I analyzed the logs from tcpdump and netstat -tulpn.

  


  When connecting locally, netstat identified the creation of two UDP connections. And tcpdump showed ffmpeg was trying to reach a connection from the server using the same UDP ports from netstat

  


  However, in a pod in Kubernetes, the ports opened on netstat were different from the ports that ffmpeg tried a connection (verified using tcpdump).

  


  I think this is the error, as ffmpeg immediately fails when trying to access a port that is not opened.