summaryrefslogtreecommitdiffstats
path: root/player
diff options
context:
space:
mode:
authorTheAMM <the.actual.amm@gmail.com>2021-05-29 01:11:19 +0300
committerJan Ekström <jeebjp@gmail.com>2021-07-08 12:44:06 +0300
commitf9527497c68c86b247ade965dafe362f0f43be09 (patch)
treed5f0e3f611a2d384fd1af835eb88c230149f05a8 /player
parentb0386fc5434e393d5e9dee97663ca59a22f2ef96 (diff)
downloadmpv-f9527497c68c86b247ade965dafe362f0f43be09.tar.bz2
mpv-f9527497c68c86b247ade965dafe362f0f43be09.tar.xz
recorder: ignore packet queue in mux_packets()
I've looked and studied the flow in the recorder, and to my understanding, the packet queue is moot after the initial sync, maybe even then - but that's beyond me right now. With the previous choice to mux trailing packets whatever the case, this doesn't result in any new ill effects (and some missing packets at the end is no big deal). Notably, since we don't have to hold onto the packets after we get muxing, we'll never run into any issues with veeery long GOPs filling up our queue (resulting in dropped packets and much user chagrin).
Diffstat (limited to 'player')
0 files changed, 0 insertions, 0 deletions