From 0a93237cb5e4642d3b698ff9b7d0cfae5401478c Mon Sep 17 00:00:00 2001
From: Carl Hetherington <cth@carlh.net>
Date: Wed, 27 May 2015 20:55:51 +0100
Subject: Handle multiple audio streams in a single piece of content in a
 similar way to the V1 patch.

---
 doc/design/decoder_structures.tex | 5 +++++
 1 file changed, 5 insertions(+)

(limited to 'doc/design/decoder_structures.tex')

diff --git a/doc/design/decoder_structures.tex b/doc/design/decoder_structures.tex
index 1f7ae0ec4..588b33695 100644
--- a/doc/design/decoder_structures.tex
+++ b/doc/design/decoder_structures.tex
@@ -28,6 +28,7 @@ This suggests that decode-and-see is a better match, even if it feels
 a bit ridiculous when most of the decoders have slightly clunky seek
 and pass methods.
 
+
 \section{Multiple streams}
 
 Another thing unique to FFmpeg is multiple audio streams, possibly at
@@ -50,4 +51,8 @@ and the merging of all audio content inside the player.
 
 These disadvantages suggest that the first approach is better.
 
+One might think that the logical conclusion is to take streams all the
+way back to the player and resample them there, but the resampling
+must occur on the other side of the get-stuff-at-time API.
+
 \end{document}
-- 
cgit v1.2.3

