[FFmpeg-user] no connections - ffserver rendered useless

[Da Rock]

On 12/01/11 23:19, Da Rock wrote:
> On 11/30/11 20:08, Carl Eugen Hoyos wrote:
>> Da Rock<ffmpeg-user<at>  herveybayaustralia.com.au>  writes:
>>
>>>      FreeBSD<server>  8.1-RELEASE-p1 FreeBSD 8.1-RELEASE-p1
>>>      ffmpeg version 0.7.7, Copyright (c) 2000-2011 the FFmpeg 
>>> developers
>> Please test current git master.
>>
>>
> I'm not 100% sure what the git master is as it isn't referenced 
> categorically on the ffmpeg site. I did try the git url at the top of 
> the list on the download page (snapshot link mentioned something about 
> head, so I went for it), but it won't build on FreeBSD. I get 
> assembler errors:
>
> CC    libavcodec/vp5.o
> /var/tmp//ccWKZjQg.s: Assembler messages:
> /var/tmp//ccWKZjQg.s:185: Error: `(%r8d,%eax)' is not a valid 64 bit 
> base/index expression
> /var/tmp//ccWKZjQg.s:230: Error: `(%r8d,%eax)' is not a valid 64 bit 
> base/index expression
> /var/tmp//ccWKZjQg.s:275: Error: `(%r8d,%eax)' is not a valid 64 bit 
> base/index expression
> /var/tmp//ccWKZjQg.s:329: Error: `(%r8d,%eax)' is not a valid 64 bit 
> base/index expression
> /var/tmp//ccWKZjQg.s:435: Error: `(%r8d,%eax)' is not a valid 64 bit 
> base/index expression
> /var/tmp//ccWKZjQg.s:544: Error: `(%r8d,%eax)' is not a valid 64 bit 
> base/index expression
> /var/tmp//ccWKZjQg.s:679: Error: `(%r8d,%eax)' is not a valid 64 bit 
> base/index expression
> /var/tmp//ccWKZjQg.s:724: Error: `(%r8d,%eax)' is not a valid 64 bit 
> base/index expression
> /var/tmp//ccWKZjQg.s:858: Error: `(%r8d,%eax)' is not a valid 64 bit 
> base/index expression
> /var/tmp//ccWKZjQg.s:897: Error: `(%esi,%edx)' is not a valid 64 bit 
> base/index expression
> /var/tmp//ccWKZjQg.s:931: Error: `(%esi,%edx)' is not a valid 64 bit 
> base/index expression
> /var/tmp//ccWKZjQg.s:971: Error: `(%esi,%edx)' is not a valid 64 bit 
> base/index expression
> /var/tmp//ccWKZjQg.s:1022: Error: `(%r8d,%eax)' is not a valid 64 bit 
> base/index expression
> /var/tmp//ccWKZjQg.s:3893: Error: `(%esi,%eax)' is not a valid 64 bit 
> base/index expression
> /var/tmp//ccWKZjQg.s:4307: Error: `(%esi,%eax)' is not a valid 64 bit 
> base/index expression
> /var/tmp//ccWKZjQg.s:4677: Error: `(%esi,%eax)' is not a valid 64 bit 
> base/index expression
> /var/tmp//ccWKZjQg.s:4931: Error: `(%esi,%eax)' is not a valid 64 bit 
> base/index expression
> /var/tmp//ccWKZjQg.s:5185: Error: `(%esi,%eax)' is not a valid 64 bit 
> base/index expression
> /var/tmp//ccWKZjQg.s:5439: Error: `(%esi,%eax)' is not a valid 64 bit 
> base/index expression
> /var/tmp//ccWKZjQg.s:5954: Error: `(%esi,%eax)' is not a valid 64 bit 
> base/index expression
> gmake: *** [libavcodec/vp5.o] Error 1
>
> There is a snapshot in the ports tree 09-10-2011 which I tried 
> building as well, but it failed as well on opencv; so I disabled 
> opencv to test and it built ok, but mpegts is now in strife:
>
> Invalid program index <stream 1 pid> while processing metadata maps
>
> There are 0.0-0.9 substreams, associated to 4 pids. All video is mpeg2 
> with bitrates varying due to frame size; audio is either ac3 5.0 at 
> 448K or mp2 at 256K; there is also a dvb_teletext stream associated 
> with each pid, and an "unknown" (epg?) for each. I am ignoring 1 of 
> the pids in my cmd because it is only a replica of <stream 1>, but it 
> hasn't been bothered by it in the past.
>
> Am I missing something here? Is there some documentation I should be 
> looking at that is different in the 0.7.7 version?
>
> Without the actual data I'm trying to work with though, I tried a test 
> with an mpg file cut from a ts stream with dvbcut and I actually got 
> 404 http error from ffserver. Numerous attempts with different 
> parameters and feeds- even though the stat page showed the feeds 
> existed. I also tried checking the permissions of the files: 666 
> (heaven forbid! :) ). All to no avail. This looks like it could be the 
> error from earlier, and I'd say its a good chance ffserver has been 
> borking it- I sent the data using ffmpeg 0.7.6. I'm still trying to 
> work out a stream _from_ ffserver.
>
> Having said all that about ffserver, ffmpeg from the same build can't 
> win no matter which way I cut it. Besides my primary goal (errors 
> mentioned above), the same test stream that worked on 0.7.6 seg 
> faults, I tried others and I get an error opening filters. There could 
> be more: the mpegts had real trouble with the raw stream- to get the 
> error above I used gstreamer dvbsrc to obtain the ts, it failed 
> completely from a raw pipe using the freebsd cx88 utility (I could 
> barely get ^c to work to kill it).
>
> Where to now?
Okay, here's an update on weirdness:

ffserver-devel error logs show http:// get and post return 200 to the 
client. I will mention that the logs show get sends some data but the 
post show 0 data sent in *all* cases.

ffmpeg-devel has numerous problems with mpegts and other formats AND i/o 
errors to ffserver.

ffmpeg 0.7.6 has no problems with input (as far as I can tell), but 
can't communicate with ffserver-devel- 404 errors even though ffserver 
says 200 in the logs- timestamps match the events.

ffserver 0.7.6 has no connection problems as far as I can tell.

ffmpeg-devel has 404 errors communicating with ffserver 0.7.6.

ffmpeg 0.7.6 can stream http to ffserver 0.7.6.

I must be down a few brain cells today, this is doing my head in trying 
to assimilate all this. I do still have some (perspective is everything 
at this point) errors in my ffserver.conf judging from my results from 
ffserver 0.7.6.

 From what I can tell I *could* run 0.7.6 happily, so I could transfer a 
port-pkg to the machine in question and install it. Is there any more 
data I can input to the devel team though while I do have the defective 
build installed? I'm afraid I'd be _Way_ out of my depth to help much 
further though- I may be able to code but I'm stretching it with this 
media stuff just setting this up. I only have a few hours though, but I 
could maybe setup a limited setup in a vm.

Cheers