diff options
author | wm4 <wm4@nowhere> | 2017-12-17 14:03:33 +0100 |
---|---|---|
committer | Kevin Mitchell <kevmitch@gmail.com> | 2017-12-17 15:45:24 -0800 |
commit | d690ee095942c06ee3157480e970ff70b399e04e (patch) | |
tree | ee6b400daba3ca50d83a50b052ef1639c252fca1 /etc/builtin.conf | |
parent | 9ed8ca2529524665129b6892e21740c2217286c2 (diff) | |
download | mpv-d690ee095942c06ee3157480e970ff70b399e04e.tar.bz2 mpv-d690ee095942c06ee3157480e970ff70b399e04e.tar.xz |
client API: change --stop-playback-on-init-failure default
This was off for mpv CLI, but on for libmpv. The motivation behind this
was that it would be confusing for applications if libmpv continued
playback in a severely "degraded" way (without either audio or video),
and that it would be better to fail early.
In reality the behavior was just a confusing difference to mpv CLI, and
has confused actual users as well. Get rid of it.
Not bothering with a version bump, since this is so minor, and it's easy
to ensure compatibility in affected applications by just setting the
option explicitly.
(Also adding the missing next-release-marker in client-api-changes.rst.)
Diffstat (limited to 'etc/builtin.conf')
-rw-r--r-- | etc/builtin.conf | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/etc/builtin.conf b/etc/builtin.conf index ee46f8cb00..8e954b90d2 100644 --- a/etc/builtin.conf +++ b/etc/builtin.conf @@ -20,7 +20,6 @@ osc=no ytdl=no input-default-bindings=no input-vo-keyboard=no -stop-playback-on-init-failure=yes # OSX/Cocoa global input hooks input-appleremote=no input-media-keys=no |