Recherche avancée

Sur d’autres sites (4939)

• avformat/utils : return pending IO error on EOF in av_read_frame()

  24 août 2019, par Marton Balint

  avformat/utils : return pending IO error on EOF in av_read_frame()
  avio_feof() returns true both in case of actual EOF and in case of IO errors.
  
  Some demuxers (matroska) have special handling to be able to return the proper
  
  error for this exact reason, e.g. :
  if (avio_feof(pb)) 
  
       if (pb->error) 
  
           return pb->error ;
  
        else 
  
           return AVERROR_EOF ;
  
       
  
  
  However, most of the demuxers do not, and they simply return AVERROR_EOF if
  
  avio_feof() is true, so there is a real chance that IO errors are mistaken for
  
  EOF.
  We might just say that the API user should always check the IO context error
  
  attribute on EOF to make sure no IO errors happened, but not even ffmpeg.c does
  
  this. It should be more intuitive to the API user if we simply return the IO
  
  error as the return value of av_read_frame() instead of AVERROR_EOF.
  Signed-off-by : Marton Balint <cus@passwd.hu>
  

  • [DH] libavformat/utils.c

• rtsp : Don’t warn about unparsed time ranges

  22 avril 2015, par Martin Storsjö

  rtsp : Don’t warn about unparsed time ranges
  This removes the error logging added in 4e54432164.
  This avoids warnings about "Invalid interval start specification ’now’"
  
  for live rtsp streams.
  We only try to parse some of the many valid values for time ranges
  
  in RTSP - the other ones are fully valid but not interesting for the
  
  use case in rtsp.c, so we shouldn’t warn about them.
  (Parsing the time ranges is needed to allow seeking, but e.g. setting
  
  the current realtime clock for the start time doesn’t make sense.
  
  av_parse_time has got a different mode for parsing absolute times
  
  as well, which can handle the special case "now", but that doesn’t
  
  make much sense for this particular use in rtsp.c.)
  Signed-off-by : Martin Storsjö <martin@martin.st>
  

  • [DH] libavformat/rtsp.c

• ffmpeg : not found (Conda Env + Gunicorn + Nginx)

  4 juin 2023, par Mirwise Khan

  I have installed ffmpeg and can run it from command line. I have anaconda installed and get different result for which ffmpeg command as follow :

  


  

  • /usr/bin/ffmpeg (base env)

  


  • /root/anaconda3/envs/myenv/bin/ffmpeg (myenv)

  


  


  python app.py - The app uses Flask. I've tested it on localhost it is working as expected.

  


  Ran it with gunicorn still working locally.

  


  When I deploy it using Nginx it doesn't work. It can't find ffmpeg. I get the error gunicorn[23436]: /bin/sh: 1: ffmpeg: not found.

  


  My usage inside python file is as follows :
subprocess.call('/root/anaconda3/envs/myenv/bin/ffmpeg ...) (I tried it with ffmpeg, full path and anaconda path - still to no success)

  


  I doubt there is something about Nginx that I'm missing, does it need special configuration for executables. Server config is as follows :

  


  server {
    listen 80;
    server_name x.x.x.x;

    location / {
        include proxy_params;
        proxy_pass http://unix:/home/myapp/myapp.sock;
        client_max_body_size 30M;
    }
}


  


  I had installed ffmpeg with pip but then I deleted it. It doesn't have anything to do with the error since I can run it locally without problems.