[MPlayer-cvslog] r30243 - trunk/etc/codecs.conf

[Reimar Döffinger]

On Sat, Feb 20, 2010 at 09:58:33AM -0500, compn wrote:
> >> F:\mplayer-test>mplayern  -user-agent Quicktime "http://movies.apple.com/movies/independent/redriding/redriding-clip1974_h.320.mov"
> >> 
> >> MPlayer SVN-r30271-3.4.5 (C) 2000-2009 MPlayer Team
> >> 142 audio & 338 video codecs
> >> 
> >> Playing http://movies.apple.com/movies/independent/redriding/redriding-clip1974_h.320.mov.
> >> Resolving movies.apple.com for AF_INET...
> >> Connecting to server movies.apple.com[24.143.196.56]: 80...
> >> Cache size set to 320 KBytes
> >> Cache fill:  0.03% (87 bytes)
> >> MOV: Reference Media file!!!
> >> libavformat file format detected.
> >> [mov,mp4,m4a,3gp,3g2,mj2 @ 0p1e11010]moov atom not found
> >> LAVF_header: av_open_input_stream() failed
> >> MOV: Reference Media file!!!
> >> 
> >> 
> >> Playing http://movies.apple.com/movies/independent/redriding/redriding-clip1974_h320.mov.
> >> Resolving movies.apple.com for AF_INET...
> >> Connecting to server movies.apple.com[24.143.196.56]: 80...
> >> 
> >> F:\mplayer-test>
> >
> >This is windows-specific and a huge bug somewhere.
> 
> yeah i figured.
> 
> also playing two http streams doesnt work
> e.g. mplayer -endpos 3 http://1 http://2
> 
> will say 
> Playing http://whfr.primcast.com:4184/.
> Starting playback...
> mpg123: Can't rewind stream by 132 bits!
> A:   3.0 (03.0) of -0.0 (unknown)  0.3% 72%
> 
> Playing http://whfr.primcast.com:4184/.
> Resolving whfr.primcast.com for AF_INET...
> Connecting to server whfr.primcast.com[38.96.148.26]: 4184...
> 
> F:\mplayer-test>

That's the same issue.

> unrelated bug when using ffmpeg://http://
> it tries to seek back to start for a few times so its slow to load
> shoutcast streams.

No, that's not the real issue.
What happens is that stream_ffmpeg does not set the demuxer based
on mime-type.
Since our audio demuxer is so unreliable it comes very low on this list,
so each and every demuxer reads some data for its autodetection, overall
consuming many kB of data - that's what makes it slow.
The fix for it is simple: don't use -nocache but at least 512 kB or so of cache!
(note that I admit the cache could use a lot of fine-tuning to work really
well out-of-the-box in most cases).