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.)
Showing the changes to DOCS/client-api-changes.rst (1 of 3 files). Show all
Unified · Split
| @@ -32,9 +32,12 @@ API changes · 31 unmodified lines | ||
| 32 | 32 | |
| 33 | 33 | :: |
| 34 | 34 | |
| 35 | + --- mpv 0.28.0 --- | |
| 35 | 36 | 1.26 - remove glMPGetNativeDisplay("drm") support |
| 36 | 37 | - add mpv_opengl_cb_window_pos and mpv_opengl_cb_drm_params and |
| 37 | 38 | support via glMPGetNativeDisplay() for using it |
| 39 | + - make --stop-playback-on-init-failure=no the default in libmpv (just | |
| 40 | + like in mpv CLI) | |
| 38 | 41 | --- mpv 0.27.0 --- |
| 39 | 42 | 1.25 - remove setting "no-" options via mpv_set_option*(). (See corresponding |
| 40 | 43 | deprecation in 0.23.0.) |