Recherche avancée

Sur d’autres sites (10375)

• 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.

  


• Can ffmpeg RTSP video stream be exchanged without an RTSP server ? [closed]

  17 décembre 2023, par natedogg

  I have two Ubuntu devices connected directly together via wired Ethernet (no router). One device (the sender) has a camera that I want to stream over RTSP, and the second device (the reciever) needs to process and view the RTSP stream. Is it possible to do this without an explicit RTSP server running on the sender ?

  


  Here is my test setup :

  


  


  • Sender

    


    

    • Static IP : 192.168.1.1/24

    


    • ffmpeg command : ffmpeg -f v4l2 -i /dev/video0 -pix_fmt yuv420p -f rtsp -rtsp_transport udp rtsp://192.168.1.2:12345/test

    


    


  


  • Receiver

    


    

    • Static IP : 192.168.1.2/24

    


    • ffmpeg command : ffplay rtsp://192.168.1.1:12345/test

    


    


  


  


  Each machine can ping the other successfully, and both devices have their firewalls disabled. However, I get connection refused errors when trying to run each command. For resource reasons, I'm trying to avoid running an RTSP server if it isn't necessary.

  


  # Sender error
Connection to tcp://192.168.1.2:12345?timeout=0 failed: Connection refused
Could not write header for output file #0 (incorrect codec parameters ?): Connection refused
Error initializing output stream 0:0 --


  


  # Receiver error
Connection to tcp://192.168.1.2:12345?timeout=0 failed: Connection refused
Connection to tcp://192.168.1.2:12345?timeout=0 failed: Connection refused


  


• Android, AOSP tree, external project (ffmpeg) is built for AMD64

  22 avril 2015, par kagali-san

  I’m trying to build ffmpeg4android on current AOSP tree (from /external), which is lunch-configured to aosp_arm-eng and set to PLATFORM_VERSION=4.2.

  Resulting files are generated for AMD64 (host native) architecture, even though the major rest of tree is built (as expected) ARM :

  readelf -a android/aosp_arm-eng/ffplay|egrep "Class :|Machine :"
  Class : ELF64 Machine :
  Advanced Micro Devices X86-64

  versus

  readelf -a
  aosp/out/target/product/generic/symbols/system/lib/libril.so | egrep "Class :|Machine :"

  Class : ELF32
  Machine : ARM

  ---

  I will probably switch to other ways of getting ffmpeg-arm (presumably the one described here) ; the reason of asking this question is to understand, at which build stage does cross-compilation environment breaks.