mirror of https://github.com/streamlink/streamlink
docs: remove common issues page
This commit is contained in:
parent
4664d25bad
commit
a541921afd
|
@ -76,10 +76,9 @@ specify ``worst`` to get the lowest quality.
|
||||||
Now that you have a basic grasp of how Streamlink works, you may want to look
|
Now that you have a basic grasp of how Streamlink works, you may want to look
|
||||||
into customizing it to your own needs, such as:
|
into customizing it to your own needs, such as:
|
||||||
|
|
||||||
- Creating a :ref:`configuration file <cli/config:Configuration file>` of options you
|
- Creating a :ref:`configuration file <cli/config:Configuration file>` of options you want to use.
|
||||||
want to use
|
- Setting up your player to cache some data before playing the stream to help avoiding buffering issues
|
||||||
- Setting up your player to :ref:`cache some data <issues:Streams are buffering/lagging>`
|
or reducing its default buffering values for being able to watch low-latency streams.
|
||||||
before playing the stream to help avoiding buffering issues
|
|
||||||
|
|
||||||
|
|
||||||
.. _Command Prompt: https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/windows-commands
|
.. _Command Prompt: https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/windows-commands
|
||||||
|
|
|
@ -82,7 +82,6 @@ Table of contents
|
||||||
cli
|
cli
|
||||||
plugins
|
plugins
|
||||||
players
|
players
|
||||||
issues
|
|
||||||
deprecations
|
deprecations
|
||||||
migrations
|
migrations
|
||||||
developing
|
developing
|
||||||
|
|
|
@ -1,47 +0,0 @@
|
||||||
Common issues
|
|
||||||
=============
|
|
||||||
|
|
||||||
Streams are buffering/lagging
|
|
||||||
-----------------------------
|
|
||||||
|
|
||||||
Enable caching in your player
|
|
||||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
||||||
|
|
||||||
By default most players do not cache the data they receive from Streamlink.
|
|
||||||
Caching can reduce the amount of buffering you run into because the player will
|
|
||||||
have some breathing room between receiving the data and playing it.
|
|
||||||
|
|
||||||
.. list-table::
|
|
||||||
:header-rows: 1
|
|
||||||
|
|
||||||
* - Player
|
|
||||||
- Parameter
|
|
||||||
- Note
|
|
||||||
* - MPC-HC
|
|
||||||
-
|
|
||||||
- Currently no way of configuring the cache
|
|
||||||
* - MPlayer
|
|
||||||
- ``-cache <kbytes>``
|
|
||||||
- Between 1024 and 8192 is recommended
|
|
||||||
* - mpv
|
|
||||||
- ``--cache=yes --demuxer-max-bytes=<kbytes>``
|
|
||||||
- Between 1024 and 8192 is recommended
|
|
||||||
* - VLC
|
|
||||||
- ``--file-caching <ms> --network-caching <ms>``
|
|
||||||
- Between 1000 and 10000 is recommended
|
|
||||||
|
|
||||||
Use the :option:`--player-args` option to pass these options to your player.
|
|
||||||
|
|
||||||
|
|
||||||
Multi-threaded streaming
|
|
||||||
^^^^^^^^^^^^^^^^^^^^^^^^
|
|
||||||
|
|
||||||
On segmented streaming protocols (such as HLS and DASH) it's possible to use
|
|
||||||
multiple threads for downloading multiple segments at the same time to
|
|
||||||
potentially increase the throughput. This can be done via Streamlink's
|
|
||||||
:option:`--stream-segment-threads` argument.
|
|
||||||
|
|
||||||
.. note::
|
|
||||||
|
|
||||||
Using 2 or 3 threads should be enough to see an impact on live streams,
|
|
||||||
any more will likely not show much effect.
|
|
Loading…
Reference in New Issue