Recherche avancée

Sur d’autres sites (9618)

• send point to point video stream using ffmpeg with rtsp (c++)

  8 décembre 2015, par seleciii44

  I need to send a h264 encoded video stream to a(only one) specific IP address with RTSP protocol on a windows PC with C++. I’m trying to use the FFMPEG library.

  I used the example in this post and i can play the stream as :

  ffplay -rtsp_flags listen -i rtsp://127.0.0.1:8554/live.sdp

  The problem is, according to the solution of post i need a server. Where -rtsp_flags listen option of ffplay behaves like a server.

  On the other hand, according to StreamingGuide of ffmpeg i can send a point to point stream like :

  ffmpeg -i INPUT -acodec libmp3lame -ar 11025 --f rtp rtp://host:port

  This is fine and works well. But i need to use rtsp. According to StreamingGuide again,

  Another option is to use RTP (which by default uses UDP) but by
  specifying it use TCP :

  ffmpeg -i input -f rtsp -rtsp_transport tcp rtsp://localhost:8888/live.sdp

  which seems to be what i’m looking for. Yet the ffmpeg tool seems to be doing nothing when i try this method (don’t know why i need tcp,but udp does not work neither). Why is that ?

  FFMPEG protocols documentation, says that i need to use a media server to send the video.

  • Why would i need a media server to just send the video stream to another PC or whatever ?
  • If i need a media server, how does the IP Camera sends the stream ?
  • If i have no option but to use a media server, could some one please recommend a server for Windows 7 ?
    • ffserver is only for linux
    • live555mediaServer seems to be used for local files or am i wrong ?
    • ..?

  Best regards,
  Gokhan.

• Architecture of video-based service for mobile phones

  27 juin 2015, par David Azar

  I guess this is more of a conceptual question than a technical one.

  I’m trying to figure out the best way to upload short videos to a server and also be able to download them and watch them on both Android and iOS.

  Lets focus on Android for the moment.

  I’ve done some experiments, and my results have been :

  • I’m able to compress 12-14MB video down to 500KB using FFMPEG lib with pretty good results in quality, but it takes about 12 seconds.

  • Next, im uploading those videos to my Parse backend as ParseFile to store them.

  • Finally, i can download them and watch them with no problem using a VideoView widget.

  Now, for the tests i’ve been running, these are great results. But i want to see if there is a better way to manage and scale all of this.

  My questions are :

  • Is there a better, lighter way to compress video ?

  • Is Parse the right way to go ?

  • How can i stream videos instead of downloading them and storing the on local storage before playing them ? i know this will cause my app to use significant space on disk and i dont want that.

  • How do big companies do this kind of tasks ?

  I’ve heard Amazon S3 is a cool thing for projects like this one, also Google Cloud Platform. I want to understand the best approach before building everything so i can do it the right way and also, provide the absolute best user experience for watching these videos.

• Stream Recorder Using FFmpeg Fails on AWS Lambda

  10 mai, par user30495567

  I am trying to stream audio from URLs and save them to a file in S3 using AWS Lambda with FFmpeg. Here is an example FFmpeg command I'm using :

  


  ffmpeg -hide_banner -loglevel error -t 10 -i http://playerservices.streamtheworld.com/api/livestream-redirect/KTOOFMAAC_SC -ar 16000 -b:a 64k -ac 2 output.mp3


  


  

  • The FFmpeg command is getting called in a python script using subprocess.Popen()

  


  • The command works as expected on local, but does not work in an AWS Lambda python environment using a custom FFMPEG layer configured with these instructions.

  


  • When run on Lambda, I get the following error : FileNotFoundError : [Errno 2] No such file or directory : '/tmp/output.mp3'

  


  


  Note : I've also tried a version where I use python requests to stream chunks and pipe them into ffmpeg. This works for some stream URLs, but for others, such as the streamtheworld URL above, it only saves 5 seconds of audio from the stream or results in a Broken Pipe error.