comparison DOCS/tech/nut.txt @ 20966:dc1a02e98cb6

clarify syncpoint placement recommanditions (note i would also like to add a "there MUST be 1 syncpoint per second" rule)
author michael
date Fri, 17 Nov 2006 13:32:45 +0000
parents a8651041ba2b
children ad87c5c9bb94
comparison
equal deleted inserted replaced
20965:a8651041ba2b 20966:dc1a02e98cb6
918 The demuxer only has to find the appropriate keyframe in the index and 918 The demuxer only has to find the appropriate keyframe in the index and
919 start demuxing from the previous syncpoint 919 start demuxing from the previous syncpoint
920 920
921 Note, more complicated seeking methods exist which are capable of quickly 921 Note, more complicated seeking methods exist which are capable of quickly
922 seeking to the optimal point in the presence of an index even if only a 922 seeking to the optimal point in the presence of an index even if only a
923 subset of all streams are active but a muxer SHOULD place syncpoints, 923 subset of all streams is active
924 and keyframes if it can affect the placement of keyframes so that simple 924
925 low complexity seeking works with fine granularity 925 A muxer SHOULD place syncpoints so that that simple low complexity seeking
926 works with fine granularity, that is syncpoints should be placed prior
927 to keyframes instead of non keyframes and with high enough frequency
928 (once per second unless there are no keyframes between this and the previous
929 syncpoint)
930
931 encoders SHOULD place keyframes so that the number of points where all
932 streams have a keyframe at the same time is maximized, this ensures that
933 seeking (complicated or not) does not need to demux and decode significant
934 amounts of data to reach a point where a presentable frame for each stream
935 is available after seeking
926 936
927 937
928 Semantic requirements: 938 Semantic requirements:
929 ====================== 939 ======================
930 940