[FFmpeg-trac] #180(undetermined:new): ffmpeg and ffserver different builds interraction

FFmpeg trac at avcodec.org
Mon May 9 15:53:06 CEST 2011


#180: ffmpeg and ffserver different builds interraction
--------------------------+--------------------------
 Reporter:  andrixnet     |        Type:  defect
   Status:  new           |    Priority:  normal
Component:  undetermined  |     Version:  unspecified
 Keywords:                |  Blocked By:
 Blocking:                |  Reproduced:  0
 Analyzed:  0             |
--------------------------+--------------------------
 First an end user question : has ffserver behaviour changed '''by
 design''' since ffmpeg-0.5 ?

 Since having problems with the latest ffserver, I build 0.7-rc1.

 Using :
 ffmpeg (on a win32)
 FFmpeg version SVN-r25857, Copyright (c) 2000-2010 the FFmpeg developers
   built on Dec  1 2010 04:07:58 with gcc 4.4.2
 and
 ffserver 0.7-rc1 (on linux)
 results in :
 {{{
 HTTP error 404 Not Found
 http://xxxxxxx:8090/feed1.ffm: Input/output error
 }}}
 and in the logs :
 {{{
 Mon May  9 16:38:37 2011 File '/feed1.ffm' not found
 Mon May  9 16:38:37 2011 10.1.1.10 - - [GET] "/feed1.ffm HTTP/1.1" 404 149
 }}}


 ----

 I was also unable to use the same ffmpeg and ffserver 0.5 with the error
 "operation not permitted". (no, not a firewall issue).

 Then I tried ffmpeg (on win32)
 FFmpeg version SVN-r20428, Copyright (c) 2000-2009 Fabrice Bellard, et al.
   built on Nov  1 2009 04:03:50 with gcc 4.2.4
 with ffserver 0.5 (linux)
 and it worked.


 ----

 then I did a new test with the latest win32 build :
 ffmpeg version git-N-29638-g95f163b, Copyright (c) 2000-2011 the FFmpeg
 developers
   built on May  6 2011 12:50:01 with gcc 4.5.3
 with ffserver-0.7-rc1
 and got :
 [http @ 01E78D60] HTTP error 404 Not Found
 http://xxxxxxx:8090/feed1.ffm: Input/output error


 ----
 I am not sure what aspects are to be considered ?

 1) different versions for ffmpeg and ffserver should work, regardless of
 the build and/or platform
 2) if the ffserver api has changed since ffmpeg-0.5 time, ffmpeg should
 report to the user a version incompatibility error message
 3) if 2) is not the case, then it is indeed a bug ffmpeg being unable to
 talk to ffserver

-- 
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/180>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list