summaryrefslogtreecommitdiffstats
path: root/mpeglib/lib/frame/README
diff options
context:
space:
mode:
Diffstat (limited to 'mpeglib/lib/frame/README')
-rw-r--r--mpeglib/lib/frame/README4
1 files changed, 2 insertions, 2 deletions
diff --git a/mpeglib/lib/frame/README b/mpeglib/lib/frame/README
index e54bd918..9e21059f 100644
--- a/mpeglib/lib/frame/README
+++ b/mpeglib/lib/frame/README
@@ -27,7 +27,7 @@ IOFrameQueues
=============
IOFrameQueues deal with the problem, that you first start
-with an empty FrameQueue (this is a FrameQueue which tqcontains
+with an empty FrameQueue (this is a FrameQueue which contains
prealloceated data, but the data is empty (eg:all pcm samples zero)
Only after converting an "empty" Frame by a decoder (mp3decoder)
the frame if "full" (== Frame with data)
@@ -58,7 +58,7 @@ A IOFrameQueue, which allows converting "dataFrames back to continous
stream".
What is this?
Lets say an application wants only 20 byte from a dataFrame which
-tqcontains 3KB of data?
+contains 3KB of data?
There must be some mechanism to read less or more data from the
queue. And the data should be written to a continus memory
segment.