summaryrefslogtreecommitdiffstats
path: root/player/command.c
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2018-01-05 16:41:16 +0100
committerKevin Mitchell <kevmitch@gmail.com>2018-01-05 18:34:29 -0800
commit8e1390e73433cede480c85828518fedada700d59 (patch)
treea926bf8d919f478859533b6a772cb72b83790653 /player/command.c
parent95dce50347cd9110c4a575483b1dfbd8b27f50f6 (diff)
downloadmpv-8e1390e73433cede480c85828518fedada700d59.tar.bz2
mpv-8e1390e73433cede480c85828518fedada700d59.tar.xz
demux: export some debugging fields about low level demuxer behavior
Export them as explicitly undocumented debugging fields for the "demuxer-cache-state" property. Should be somewhat helpful to debug "wtf is the demuxer" doing situations better, especially when seeking. It also becomes visible how long the demuxer is blocked on an "old" seek when you keep seeking while the first seek hasn't finished.
Diffstat (limited to 'player/command.c')
-rw-r--r--player/command.c5
1 files changed, 5 insertions, 0 deletions
diff --git a/player/command.c b/player/command.c
index b159f91708..31f76bcb1e 100644
--- a/player/command.c
+++ b/player/command.c
@@ -1755,6 +1755,11 @@ static int mp_property_demuxer_cache_state(void *ctx, struct m_property *prop,
node_map_add_flag(r, "idle", s.idle);
node_map_add_int64(r, "total-bytes", s.total_bytes);
node_map_add_int64(r, "fw-bytes", s.fw_bytes);
+ if (s.seeking != MP_NOPTS_VALUE)
+ node_map_add_double(r, "debug-seeking", s.seeking);
+ node_map_add_int64(r, "debug-low-level-seeks", s.low_level_seeks);
+ if (s.ts_last != MP_NOPTS_VALUE)
+ node_map_add_double(r, "debug-ts-last", s.ts_last);
return M_PROPERTY_OK;
}