Changeset 1046
- Timestamp:
- 2005-03-04 23:54:50 (4 years ago)
- Files:
-
- standards/draft-pfeiffer-annodex-02-rc2.txt (modified) (12 diffs)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
standards/draft-pfeiffer-annodex-02-rc2.txt
r1044 r1046 956 956 5. Handling time in Annodex format bitstream 957 957 958 With time-continuous data like Annodex, one needs to handle data at 959 four different levels: 960 o at the bytes level, upon seeking. 961 o at the packets level, upon encapsulating. 962 o at the granules level, upon recompositing. 963 o at the time level, upon displaying and addressing. 964 This section explains how they all fit together. 965 958 966 5.1 Conceptual overview 959 967 … … 994 1002 audio bitstream 2 995 1003 ------------------------------- 1004 1005 1006 1007 Pfeiffer, et al. Expires September 3, 2005 [Page 18] 1008 1009 Internet-Draft ANNODEX March 2005 1010 1011 996 1012 | |/////| | | | 997 1013 ------------------------------- … … 1002 1018 associated with the granule position of 0 on all logical bitstreams. 1003 1019 Typically, a newly created Annodex file starts all its logical 1004 1005 1006 1007 Pfeiffer, et al. Expires September 3, 2005 [Page 18]1008 1009 Internet-Draft ANNODEX March 20051010 1011 1012 1020 bitstreams at granule position 0, and a typical extract of an Annodex 1013 1021 bitstream, such as the one starting at t_url in the image above, … … 1050 1058 secondary header packets for each logical bitstream. 1051 1059 1060 1061 1062 1063 Pfeiffer, et al. Expires September 3, 2005 [Page 19] 1064 1065 Internet-Draft ANNODEX March 2005 1066 1067 1052 1068 Each one of the bitstreams insert data into the Ogg bitstream through 1053 1069 packets which have an associated temporal duration based on the … … 1058 1074 1059 1075 The granule position together with the granulerate and granuleshift 1060 1061 1062 1063 Pfeiffer, et al. Expires September 3, 2005 [Page 19]1064 1065 Internet-Draft ANNODEX March 20051066 1067 1068 1076 information of the skeleton secondary header packets for the 1069 1077 particular logical bitstream are used for the calculation of the time … … 1107 1115 t_page = basetime + ((keyindex + keyoffset) / granulerate) 1108 1116 1117 1118 1119 Pfeiffer, et al. Expires September 3, 2005 [Page 20] 1120 1121 Internet-Draft ANNODEX March 2005 1122 1123 1109 1124 The basetime provides the time offset used at the beginning of the 1110 1125 logical bitstream for the first data packet and thus MUST be added … … 1114 1129 44100 (i.e. 44100 samples per 1 sec), a granuleshift of 0, and 1115 1130 starts at 4 sec. When reaching a granule_position of 88200, this 1116 1117 1118 1119 Pfeiffer, et al. Expires September 3, 2005 [Page 20]1120 1121 Internet-Draft ANNODEX March 20051122 1123 1124 1131 maps to a time position of 6 seconds: 1125 1132 … … 1163 1170 1164 1171 A note about field overflows: an overflow of the granule position 1172 1173 1174 1175 Pfeiffer, et al. Expires September 3, 2005 [Page 21] 1176 1177 Internet-Draft ANNODEX March 2005 1178 1179 1165 1180 field can destroy the temporal integrity of the Annodex physical 1166 1181 bitstream. In this case, a multiplexer MUST end the Annodex physical … … 1170 1185 overflow of the page_sequence_number on one of the logical 1171 1186 bitstreams. 1172 1173 1174 1175 Pfeiffer, et al. Expires September 3, 2005 [Page 21]1176 1177 Internet-Draft ANNODEX March 20051178 1179 1187 1180 1188 5.3 Addressing/seeking into the bitstream … … 1218 1226 1219 1227 Therefore, once seeking has located the correct Byte position that 1228 1229 1230 1231 Pfeiffer, et al. Expires September 3, 2005 [Page 22] 1232 1233 Internet-Draft ANNODEX March 2005 1234 1235 1220 1236 refers to the given temporal offset, it MUST seek back. For logical 1221 1237 bitstreams that have a non-zero "granuleshift" in the skeleton, it … … 1225 1241 position that satisfies all these requirements is the correct seek 1226 1242 position. 1227 1228 1229 1230 1231 Pfeiffer, et al. Expires September 3, 2005 [Page 22]1232 1233 Internet-Draft ANNODEX March 20051234 1235 1243 1236 1244 A player that presents from an offset MUST take into account that the … … 1270 1278 This is important also to allow caching of such files as is required 1271 1279 for Web proxies and described in temporal URI addressing [16]. 1272 1273 1274 1275 1276 1277 1278 1279 1280 1280 1281 1281