mpv/TOOLS/lua/README.md

mpv lua scripts
===============

The lua scripts in this folder can be loaded on a one-time basis by
adding the option

    --script=/path/to/script.lua

to mpv's command line.

Where appropriate, they may also be placed in ~/.config/mpv/scripts/ from
where they will be automatically loaded when mpv starts.

Some of these are just for testing mpv internals.
TOOLS: better documentation of lua scripts 2014-04-29 12:11:39 +00:00			`mpv lua scripts`
			`===============`

			`The lua scripts in this folder can be loaded on a one-time basis by`
			`adding the option`

options: deprecate 'lua' based options/dirs for 'script' - --lua and --lua-opts change to --script and --script-opts - 'lua' default script dirs change to 'scripts' - DOCS updated - 'lua-settings' dir was _not_ modified The old lua-based names/dirs still work, but display a warning. Signed-off-by: wm4 <wm4@nowhere> 2014-12-14 23:31:30 +00:00			`--script=/path/to/script.lua`
TOOLS: better documentation of lua scripts 2014-04-29 12:11:39 +00:00
			`to mpv's command line.`

options: deprecate 'lua' based options/dirs for 'script' - --lua and --lua-opts change to --script and --script-opts - 'lua' default script dirs change to 'scripts' - DOCS updated - 'lua-settings' dir was _not_ modified The old lua-based names/dirs still work, but display a warning. Signed-off-by: wm4 <wm4@nowhere> 2014-12-14 23:31:30 +00:00			`Where appropriate, they may also be placed in ~/.config/mpv/scripts/ from`
			`where they will be automatically loaded when mpv starts.`
audio: add device change notification for hotplugging Not very important for the command line player; but GUI applications will want to know about this. This only adds the internal API; support for specific audio outputs comes later. This reuses the ao struct as context for the hotplug event listener, similar to how the "old" device listing API did. This is probably a bit unclean and confusing. One argument got reusing it is that otherwise rewriting parts of ao_pulse would be required (because the PulseAudio API requires so damn much boilerplate). Another is that --ao-defaults is applied to the hotplug dummy ao struct, which automatically applies such defaults even to the hotplug context. Notification works through the property observation mechanism in the client API. The notification chain is a bit complicated: the AO notifies the player, which in turn notifies the clients, which in turn will actually retrieve the device list. (It still has the advantage that it's slightly cleaner, since the AO stuff doesn't need to know about client API issues.) The weird handling of atomic flags in ao.c is because we still don't require real atomics from the compiler. Otherwise we'd just use atomic bitwise operations. 2015-02-12 15:53:56 +00:00
			`Some of these are just for testing mpv internals.`