summaryrefslogtreecommitdiffstats
path: root/player/command.c
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2019-07-15 03:16:38 +0200
committerwm4 <wm4@nowhere>2019-09-19 20:37:05 +0200
commitda612acacdf41a9a72b095fa582a6b37996b0811 (patch)
tree984c964c8fc899d7efa22c22e08a036bf788723d /player/command.c
parenta05b847879dbb5d30bebf188562d16fa3e68ca70 (diff)
downloadmpv-da612acacdf41a9a72b095fa582a6b37996b0811.tar.bz2
mpv-da612acacdf41a9a72b095fa582a6b37996b0811.tar.xz
command: make vf-metadata/af-metadata somewhat observable
Until now they weren't observable and never reported any updates. Apply a shitty hack to make them mostly-observable. It relies on the "idle" event, which is basically triggered on every frame displayed, or similar. This can lead to property change notifications not being sent quickly enough. The cleaner solution would be adding a notification mechanisms from filters, but I'm too lazy for that.
Diffstat (limited to 'player/command.c')
-rw-r--r--player/command.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/player/command.c b/player/command.c
index e8822c2f69..5dce2ccd05 100644
--- a/player/command.c
+++ b/player/command.c
@@ -3621,7 +3621,7 @@ static const char *const *const mp_event_property_change[] = {
"vo-delayed-frame-count", "mistimed-frame-count", "vsync-ratio",
"estimated-display-fps", "vsync-jitter", "sub-text", "audio-bitrate",
"video-bitrate", "sub-bitrate", "decoder-frame-drop-count",
- "frame-drop-count", "video-frame-info"),
+ "frame-drop-count", "video-frame-info", "vf-metadata", "af-metadata"),
E(MP_EVENT_DURATION_UPDATE, "duration"),
E(MPV_EVENT_VIDEO_RECONFIG, "video-out-params", "video-params",
"video-format", "video-codec", "video-bitrate", "dwidth", "dheight",