Recherche avancée

Sur d’autres sites (5308)

• Ffmpeg gentle stop sending [closed]

  31 mars 2023, par Ли Шеньшунь

  Good day. I'm trying to do a simple video sending and receiving on two computers that are on the same network. Video simulates streaming (video conference for example). I want to use ffmpeg but have run into a number of difficulties.
I start with two simple scripts :
Sender machine

  


  ffmpeg -re -i input_file.mp4 -c copy -f mpegts udp://192.168.2.10:1234


  


  recipient machine :

  


  ffmpeg -i udp://192.168.2.10:1234 -c copy save_video.mp4


  


  I got 2 questions :

  


  

  1. Is there a way to correctly end video reception when the sender does not send anything else ?

  


  


  The receive command works by waiting indefinitely. If the sender is still sending video and at this moment interrupt the receiver with ctrl+c, then the video is saved correctly. If the sender is finished, then after that, to stop, you need to use ctrl + c twice and the video is "broken", because. does not open apparently due to damage to the meta-data or codecs.

  


  I'm aware of options like using timeout, or saving to mkv format, they really work. But setting a specific number of seconds is problematic, and simply killing a process does not look very nice.

  


  

  2. Is the -re switch enough to simulate a "webcam" from a video file ? I heard that ffmpeg buffers packets in case of loss and can send them later later. I need to send it as it is, if there are any problems, then we lose the package forever. The -flush_packets key, as I understand it, is for writing to a file, but not when sending over the network.

  


  


• Apache2 - RTSP stream redirection without ffmpeg processing

  10 août 2022, par Janusz

  I have IP camera on local network with address let say : 192.168.5.111:36121 (for rtsp conection)
So I can view real time video in local network for example with :

  


  ffplay rtsp://admin:xxxx@192.168.5.111:36121/cam/realmonitor?.......


  


  I can access my camera from any place as well from my linux VPS server with :

  


  ffplay rtsp://admin:xxxx@xbox2.com:37021/cam/realmonitor?.......


  


  To do this on my remote VPS linux server I have VPN server and locally DD-WRT router connected to this server as client :
So on the local router I have :

  


  iptables -t nat -A PREROUTING -i tun11 -p tcp --dport 36121 -j DNAT --to-destination 192.168.5.111


  


  And on VPS server :

  


  iptables -t nat -A PREROUTING -d 176.123.123.123/32 -p tcp -m tcp --dport 37021 -j DNAT --to-destination 10.8.0.10:36121


  


  and that is allowing me to connect my camera from global network with :

  


  ffplay rtsp://admin:xxxx@xbox2.com:37021/cam/realmonitor?.......


  


  or

  


  ffplay rtsp://admin:xxxx@176.123.123.123:37021/cam/realmonitor?.......


  


  Everything works fine - but I would like to avoid to use specific port number directly (and use only :443 for all my cameras) so for example instead of
using xbox2.com:37021 to use xbox2.com/cam1 with redirection from apache2, so to access the camera it would be : ffplay rtsp://admin:xxxx@xbox2.com/cam1/cam/realmonitor?.......
Was trying to use RedirectMatch, ProxyPass, ProxyPassReverse in the VirtualHost config but did not succeed.
So :
question nr.1 - is it at all possible to use apache2 to redirect the rtsp as described before ?
question nr.2 - if yes so how ?

  


  Please note that I can redirect the stream with the node-rtsp-stream within apache2 (over port :443) using :

  


  ProxyPass        /wss1 ws://127.0.0.1:3001
ProxyPassReverse /wss1 ws://127.0.0.1:3001


  


  and later to play it with jsmpeg on the web page but the problem is that ffmpeg processing on my VPS server makes big load to the processor, that's why I would like only to redirect the rtsp stream using apache2 without any ffmpeg processing.

  


• FFMPEG : Multicast packets incoming, but input stream does not open

  2 septembre 2022, par oldslow

  I have a weird problem with ffmpeg and I was wondering if someone might know what's going on.

  


  We have transcoding clusters outputting video to a multicast network. In some computers of the same network, I'm able to open these streams with a command like :

  


  ffplay -i "udp://239.{mutlticast address}:10001?localaddr={Local adapter IP which receives packets}" -nodisp -loglevel trace

  


  But in other computers it does not work. Particularly in a server running Centos 7 I just get :

  


  [NULL @ 0x7fc9a4000920] Opening 'udp://239.xxx.xxx.xxx:10001?localaddr=xxx.xxx.xxx.xxx' for reading
[udp @ 0x7fc9a40012a0] No default whitelist set 
[udp @ 0x7fc9a40012a0] end receive buffer size reported is 131072
nan    :  0.000 fd=   0 aq=    0KB vq=    0KB sq=    0B f=0/0


  


  I was thinking it might be a network problem. I started Wireshark to see if the packets were coming in and the thing is, they are ! As soon as I start FFMpeg/FFplay, the MPEG TS packets start coming in, but still FFMpeg won't open the stream :

  


  1067 1.897872161 192.168.194.92 -> 239.193.2.221 MPEG TS 1358 Source port: 51718  Destination port: scp-config
1068 1.898576050 192.168.194.92 -> 239.193.2.221 MPEG TS 1358 Source port: 40892  Destination port: documentum-s[Malformed Packet]
1069 1.900472740 192.168.194.92 -> 239.193.2.221 MPEG TS 1358 Source port: 37505  Destination port: documentum
1070 1.901850051 192.168.194.92 -> PTS 30268.882311111 MPEG TS 1358 video-stream
1071 1.903688205 192.168.194.92 -> 239.193.2.221 MPEG TS 1358 NULL packet
1072 1.905842200 192.168.194.92 -> 239.193.2.221 MPEG TS 1358 Source port: 51718  Destination port: scp-config
1073 1.906249539 192.168.194.92 -> 239.193.2.221 MPEG TS 1358 NULL packet
1074 1.909831587 192.168.194.92 -> 239.193.2.221 MPEG TS 1358 Source port: 51718  Destination port: scp-config
1075 1.911357251 192.168.194.92 -> 239.193.2.221 MPEG TS 1358 NULL packet
1076 1.912000106 192.168.194.92 -> 239.193.2.221 MPEG TS 1358 NULL packet
1077 1.913819520 192.168.194.92 -> 239.193.2.221 MPEG TS 1358 NULL packet
1078 1.917778444 192.168.194.92 -> 239.193.2.221 MPEG TS 1358 Source port: 37505  Destination port: documentum
1079 1.917802429 192.168.194.92 -> 239.193.2.221 MPEG TS 1358 NULL packet
1080 1.920473981 192.168.194.92 -> 239.193.2.221 MPEG TS 1358 NULL packet


  


  Anyone have any idea what can I do to fix this ?
Thanks a lot !