From 88947731c24beb12e1a149bb41de0301b05c7ebc Mon Sep 17 00:00:00 2001 From: gabucino Date: Mon, 12 Nov 2001 17:30:49 +0000 Subject: *** empty log message *** git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@2856 b3059339-0415-0410-9bf9-f77b7e298cf2 --- DOCS/tech/formats.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'DOCS/tech/formats.txt') diff --git a/DOCS/tech/formats.txt b/DOCS/tech/formats.txt index 687e356a1f..03ac0b46e9 100644 --- a/DOCS/tech/formats.txt +++ b/DOCS/tech/formats.txt @@ -35,7 +35,7 @@ - AVI streams. Two kind of RIFF AVI files exists: - 1. interleaved: audio and video content is interlaved. it's faster and + 1. interleaved: audio and video content is interleaved. it's faster and requires only 1 reading thread, so it's recommended (and mostly used). 2. non-interleaved: audio and video aren't interleaved, i mean first come whole video followed by whole audio. it requires 2 reading process or @@ -46,7 +46,7 @@ played as non-interleaved otherwise you get a-v desync or buffer overflow. MPlayer supports 2 kind of timing for AVI files: - - bps-based: it is based on bitrate/samplerate of video/audio steram. + - bps-based: it is based on bitrate/samplerate of video/audio stream. this method is used by most players, including avifile and wmp. files with broken headers, and files created with VBR audio but not vbr-compliant encoder will result a-v desync with this method. @@ -73,7 +73,7 @@ I also note, that most AVI encoders/multiplexers create bad files if using VBR audio. only 2 exception (known by me): NaNDub and MEncoder. - FPS: only constant framerate allowed, but it's possib;e to skip frames. + FPS: only constant framerate allowed, but it's possible to skip frames. - ASF streams: ASF (active streaming format) comes from Microsoft. they developed two -- cgit v1.2.3