summaryrefslogtreecommitdiffstats
path: root/DOCS
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2012-12-01 23:52:04 +0100
committerwm4 <wm4@nowhere>2012-12-03 21:08:52 +0100
commitc02f2529385ab2ddd9605c5ebe5d2a68be200ec4 (patch)
tree360218c41694cf931f0607b64d0e7bc36684ef1c /DOCS
parent6294c785490be5fc31d29758ca592510fd161371 (diff)
downloadmpv-c02f2529385ab2ddd9605c5ebe5d2a68be200ec4.tar.bz2
mpv-c02f2529385ab2ddd9605c5ebe5d2a68be200ec4.tar.xz
stream_lavf: use ffmpeg for http/https streaming
The internal mplayer http implementation is terrible and old. Try to use ffmpeg instead. Enable ffmpeg https as well (we don't have native support for it and never will). Enable the cache for ffmpeg streams. In theory, we want to enable the cache for network streams only (or at least, not enable it for files), but there doesn't seem to be any way to query this. ffmpeg has its own read-cache, but apparently it doesn't get filled asynchronously (only to the degree internal socket/kernel buffers do). Should it turn out that the mplayer implementation is better than ffmpeg's in some way (unlikely), this commit might be reverted until ffmpeg is ready. So far, the ffmpeg implementation seems to work very well though. The original mplayer stream implementation is made available under "mp_http://" and "mp_http_proxy://". This is for testing, until the http implementation is completely removed. Note that this is unlikely to happen soon: ffmpeg doesn't support Microsoft streaming, while mplayer has some support. This code has dependencies on http. Note: "http_proxy://" doesn't work anymore. Use "httpproxy://" to get the ffmpeg implementation of it. Using https requires enabling OpenSSL in ffmpeg by adding the --enable-openssl switch to ffmpeg's configure.
Diffstat (limited to 'DOCS')
0 files changed, 0 insertions, 0 deletions