FLASH FLV及F4V原版官方格式 不必翻译
??
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? Version 10 Copyright ? 2008 Adobe Systems Incorporated.?All rights reserved. This manual may not be copied, photocopied, reproduced,translated, or converted to any electronic ormachine-readable form in whole or in part without writtenapproval from AdobeSystems Incorporated. Notwithstanding ?the foregoing, apersonobtaining an electronic version of this manualfrom Adobe may print out one copy of this manual provided that nopart of this manual may beprinted out, reproduced, distributed, resold, ortransmitted for any other purposes, including, without limitation, commercial purposes, such as selling copies of thisdocumentation or providing paid-for support services. ? Trademarks Adobe, ActionScript,Flash, Flash Media Server, XMP, and Flash Player are either registered trademarks or trademarks of Adobe Systems Incorporated and may be registered inthe United States orin other jurisdictions including internationally. Other product names, logos, designs, titles,words, or phrases mentioned within this publication may be trademarks, service marks, or trade names of Adobe SystemsIncorporated ?or other entities andmay be registered incertain jurisdictions includinginternationally. No right or license is grantedto any Adobe trademark. ? Third-Party Information This guide contains linksto third-party websites that are not under the control of Adobe SystemsIncorporated,?and AdobeSystems Incorporated is not responsible for the content on any linked site. If you access a third-party website mentioned inthis guide, then you do so at your own risk. Adobe Systems Incorporated ?provides these links only as a convenience, and the inclusion of the link does not imply that Adobe Systems Incorporated ?endorses or accepts any responsibility for the content on those third- party sites. No right, license or interest isgranted in any third party technology referenced inthis guide. ? NOTICE: THIS PUBLICATION AND THE INFORMATION HEREIN ISFURNISHED ?“AS IS”, IS SUBJECT TOCHANGE WITHOUT NOTICE, AND SHOULDNOT BE CONSTRUED?AS A COMMITMENT ?BY ADOBESYSTEMS INCORPORATED. ADOBE SYSTEMS INCORPORATED ?ASSUMES NO RESPONSIBILITY ORLIABILITY FOR ANY ERRORS OR INACCURACIES, MAKES NO WARRANTY OF ANY KIND (EXPRESS,IMPLIED, OR STATUTORY) WITH RESPECT TO THIS PUBLICATION, AND EXPRESSLY DISCLAIMS?ANY AND ALL WARRANTIES OFMERCHANTABILITY, FITNESSFOR PARTICULAR PURPOSES, AND NONINFRINGEMENT OFTHIRD PARTY RIGHTS. ? Adobe Systems Incorporated ? Published November 2008 ? ? Contents ? ? ? ? ? ? Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ?1 The FLV? file format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 The F4V file format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 What’s new in Video File Format 10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Speex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 XMP ?Metadata .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 ? Chapter 1: The FLV File Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 The FLV header .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 The FLV? file body . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 FLV? tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Audiotags ?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 AUDIODATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 AACAUDIODATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Videotags ?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 VIDEODATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 AVCVIDEOPACKET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Data tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 onMetaData . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 ? Chapter 2: The F4V File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . 17 The F4V box ?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 ftyp box .. . .. . . . . . . .. . .. . .. . . . . . . .. . .. . .. . . . . . . .. . .. . .. . . . . . . .. 18moovbox ?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 mvhd box ?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 trak box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 udta box ?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 meta box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 mdia box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .? 22 minf box ?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 stblbox ?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .? 22 tkhd box?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .? 23 mdhd box ?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 stsd box? ?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 ? ? ? i ? stsc box ?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 stts box. .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 ctts box? ?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 stco and co64 boxes .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 stss box?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 stsz box ?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 chpl box ?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 pdin box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .?31 mdat box?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Required structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Supported media types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Unsupported boxes .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 ? Chapter 3: F4V Metadata. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Tag box ?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 ilst box ?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Imagemetadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Text metadata ?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 styl box??. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 hlit box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 hclr box?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 krok box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 dlay?box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 drpo box?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 drpt box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .? 41 href ?box?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .? 41 tbox box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 blnk?box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 twrp box? ?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 XMP ?Metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 uuid ?box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ii?????? ?Contents ? ? ? ? ? Introduction ? ? ? ? This document provides technical format information for the video file formats supported by Adobe? Flash? Player software—FLV and F4V. Adobe seriously considersall feedback to the video file format specification. E-mail any unclear or potentially erroneous information withinthe specification to Adobe at flashformat@adobe.com. ?All such email submissions shall besubject to the SubmittedMaterials guidelines inthe Terms of Use at www.adobe.com/misc/copyright.html. ? ? The FLV file format ? Starting with SWF files published for Flash Player 6,Flash Player can exchange audio, video,and data over RTMP connections with the Adobe Flash Media Server?. One way to feed datato Flash Media Server (and thus onto Flash Player clients) is from files inthe FLV file format.Starting with SWF files published for Flash Player 7,Flash Player can also play FLV files directly with MIME type video/x-flv. An FLV file encodes synchronized audio and video streams. The audio and video data within FLV files are encoded inthe same way as audio and video within SWF files. This document describes FLV version 1.For more information ontheFLV format, see Chapter 1, “The FLV File Format,” onpage 3. ? ? The F4V file format ? Starting with SWF files published for Flash Player 9Update 3 (9,0,115,0), Flash Player canplay F4V files. The F4V format is based onthe format specified by ISO/IEC 14496-12: ISO base media file format. For more information on the F4V format, see Chapter 2, “The F4V File Format,” onpage 17. A large part of the F4V format involves metadata. For more information onF4Vmetadata,see Chapter 3, “F4V Metadata,” onpage35. ? What’s new in Video File Format 10 ? The following features are new in theFlash video file format specifications (both FLV and F4V) corresponding to Flash Player 10. ? ? Speex ? Flash Player 10 supports the open source Speex audio codec. Speex data can serve as the audio stream in an FLV file. See “AUDIODATA” ?onpage 6. ? ? XMP ?Metadata ? The F4V file format supports a box type called 'uuid' which canstore data formatted in Adobe’s Extensible Metadata Platform (XMP?) and present it to a SWF file via ActionScript?. See “XMP Metadata” onpage 43. ? ? ? ? CHAPTER 1
The FLV File Format ? ? ? ? Each tag type in an FLV file constitutes asingle stream. There can be no more than one audioand one video stream, synchronized together, in an FLV file. AnFLV file cannot define multiple independent streams of a single type. Unlike SWF files, FLV files store multibyte integers inbig-endian byte order. For example, as a UI16 in SWF file format, the byte sequence that represents the number 300 (0x12C) is 0x2C 0x01; as a UI16 in FLV file format, the byte sequence that represents thenumber 300 is 0x01 0x2C. Also, FLV files use a3-byte integer type that is not used inSWF files: a UI24 represents anunsigned 24-bit integer. ? The FLV header ? All FLV files begin with the following header: ?
The DataOffset field usuallyhas a value of9 for FLV version 1. This field is present toaccommodate largerheaders in future versions. ? ? The FLV file body ? After the FLV header, the remainder of an FLV file consists of alternating back-pointers and tags. They interleave as shown in the following table: ?
?
? FLV tags ? FLV tags have the following format: ?
? In playback, thetime sequencing ofFLV tags depends onthe FLV timestamps only. Any timingmechanisms built into the payload data formatare ignored. ? Audio tags ? Audio tags are similar to the DefineSound tag inthe SWF file format. Their payload data isidentical except for the additional Nellymoser 8-kHz format,whichis not permittedin SWF. (For information on the SWF file format, see the SWF File Format Specification at www.adobe.com/go/swf_file_format.) ? ? AUDIODATA ?
?
else ? Format 3, linear PCM, stores raw PCM samples. If the data is 8-bit, the samples are unsigned bytes. Ifthe data is 16-bit, the samples are stored as little endian, signed numbers. Ifthe data is stereo, left and right samples are stored interleaved: left -right - left - right - and so on. Format 0PCM is the same as format 3 PCM,except that format 0 stores 16-bit PCM samples inthe endian order of the platformon which the file was created. For this reason,format 0 is not recommended for use. Nellymoser 8-kHz and 16-kHz are special cases— 8- and 16-kHz sampling rates are not supported in other formats, and the SoundRate bits can’t represent this value. WhenNellymoser 8-kHz or Nellymoser 16-kHz is specified inSoundFormat, theSoundRate and SoundType fields are ignored. For other Nellymoser samplingrates, specify the normal Nellymoser SoundFormat and use the SoundRate and SoundType?fields as usual. If the SoundFormat indicates AAC, the SoundType should be set to 1 (stereo) and the SoundRate should be set to 3 (44 kHz). However, this does not mean that AAC audio in FLV is always stereo, 44kHz data. Instead, the Flash Player ignores these values and extracts the channel and sample rate data is encoded in the AAC bitstream. For information ?regarding Speex capabilities and limitationswhen stored in a SWF file, seethe SWF File Format Specification. ? AACAUDIODATA ? The AAC format is supported in Flash Player 9,115,0 and higher. ?
else if AACPacketType == 1 Raw AAC frame data ? The AudioSpecificConfig is explainedin ISO 14496-3. Note that it is not the same as the contents of the esds box from an MP4/F4V file. This structure is more deeply embedded. ? ? ? Video tags aresimilar to the VideoFrame tag in the SWF file format, and their payload data is identical. (For information on the SWF file format, see the SWF File Format Specification atwww.adobe.com/go/swf_file_format.) ? VIDEODATA ?
If CodecID == 3 SCREENVIDEOPACKET If CodecID == 4 VP6FLVVIDEOPACKET If CodecID == 5 VP6FLVALPHAVIDEOPACKET If CodecID == 6 SCREENV2VIDEOPACKET AVCVIDEOPACKET ? If FrameType = 5,instead of a video payload, the message stream contains aUI8 with the following meaning: ■????? ?0 = Start of client-side seeking video frame sequence ■????? ?1 = End of client-sideseeking video frame sequence ? AVCVIDEOPACKET ? An AVCVIDEOPACKET ?carries apayload of AVC video data. ?
Composition time offset else 0 ? Data??????????????????????????????? ?UI8[n]?????????????????????? ?if AVCPacketType == 0 AVCDecoderConfigurationRecordelse if AVCPacketType== 1 else ifAVCPacketType == 2 Empty ? See ISO 14496-12, 8.15.3 for an explanation ofcomposition times. The offset in an FLV fileis always inmilliseconds. See ISO 14496-15, 5.2.4.1 for the description of AVCDecoderConfigurationRecord. Thiscontains the same information that would be stored inan avcC box in an MP4/FLV file. ? ? Data tags ? Data tags encapsulate single-method invocation, which is usually called ona NetStream object inFlash Player. Data tags are formed from a method name and a set of arguments. ?
? SCRIPTDATAOBJECT and SCRIPTDATAOBJECTEND ?
? SCRIPTDATASTRING and SCRIPTDATALONGSTRING The SCRIPTDATASTRING and SCRIPTDATALONGSTRING records are used todefinestrings for data tags. ?
? SCRIPTDATAVALUE ? SCRIPTDATAVALUE ? ? Type ? (see notes following table) UI8??????????????????????????????????????????????????????????Type ofthe variable: 0 = Number type 1 = Boolean type 2 = String type 3 = Object type 4 = MovieClip type 5 = Null type 6 = Undefined type 7 = Reference type 8 = ECMA array type 10 = Strict array type 11 = Date type 12 = Long stringtype ? ECMAArrayLength?????????????? ?If Type = 8, UI32???????????????????????????????? ?Approximate number of fields of ECMA array ? ? ? ScriptDataValue?????????????????? ?If Type == 0 DOUBLE If Type == 1 UI8 If Type == 2 SCRIPTDATASTRING If Type == 3 SCRIPTDATAOBJECT[n]If Type == 4 SCRIPTDATASTRING defining the MovieClip path If Type == 7 UI16 If Type == 8 SCRIPTDATAVARIABLE[EC MAArrayLength] If Type == 10 SCRIPTDATAVARIABLE[n] If Type == 11 SCRIPTDATADATE If Type == 12 SCRIPTDATALONGSTRING Script data values ? SCRIPTDATAOBJECTENDIf Type == 8 SCRIPTDATAVARIABLEEND Terminators for Object and Strict array lists ? If Type = 8 (ECMA array type), the ECMAArrayLength provides a hint to the software about how many items might be in the array. The array continues untilSCRIPTDATAVARIABLEEND appears. If Type = 10 (strictarray type), the array begins with a UI32 type and contains that exact number of items. Thearray does notterminate with a SCRIPTDATAVARIABLEEND tag. ? SCRIPTDATAVARIABLE and SCRIPTDATAVARIABLEEND ? ?
? SCRIPTDATADATE A SCRIPTDATADATE?record definesa particular date and time. ?
? onMetaData ? An FLV file can contain metadata with an “onMetaData” marker. Various stream properties are available to a running ActionScriptprogram via the NetStream.onMetaData property. The availableproperties differ dependingon the software used. Common propertiesinclude: ■??????? ?duration: a DOUBLE indicating the totalduration of the file in seconds ■??????? ?width: a DOUBLE indicating the width of the video inpixels ■??????? ?height: a DOUBLE indicating the height of the video inpixels ■??????? ?videodatarate: a DOUBLE indicating thevideo bit rate in kilobits per second ? ■??????? ?framerate: a DOUBLE indicating the number of frames per second ■?????? videocodecid: a DOUBLEindicating the video codec ID used in the file (see “Video tags” onpage 8for available CodecID values) ■?????? audiosamplerate: a DOUBLE indicating the frequency at which the audiostream is replayed ■??????? ?audiosamplesize: a DOUBLE indicating theresolution ofa single audio sample ■??????? ?stereo: a BOOL indicating whether the data is stereo ■?????? audiocodecid: a DOUBLEindicating the audio codec IDused in the file (see “Audio tags” onpage 6for available SoundFormat ?values) ■??????? ?filesize: a DOUBLE indicating the total size ofthe file in bytes ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? CHAPTER 2
The F4V File Format ? ? ? ? Flash Player Update 3 (9,115,0) and higher can play F4V files. The F4V format is based on the format specified byISO/IEC 14496-12: ISO base media file format. Unlike SWF files, F4V files store multibyte integers in big-endianbyte order. For example, asa UI16 in SWF file format, the byte sequence that represents the number 300 (0x12C) is 0x2C 0x01; as aUI16 in F4V file format, the byte sequence that represents the number 300 is 0x01 0x2C. This chapter discusses all aspectsof the F4V formatexcept metadata. For information on metadata, see Chapter 3,“F4V Metadata,” onpage 35. ? ? The F4V box ? The fundamental building block of an F4V file is abox which has the following BOX format: ?
? Many boxes are wellunder 4 gigabytes in length and can store their size in the TotalSize field. The format also supports very large boxes by setting the 32-bit TotalSize field to1 and storing a 64-bit size inExtendedSize. Each box is identified with a 32-bit type.For most boxes, this 32-bit type doubles as ahuman-readablefour-character ASCII code or FourCC, such as 'moov' (0x6D6F6F76) and 'mdat' (0x6D646174). The box payload immediatelyfollows the box header. Thesize ofthe payload in bytes is equal to the total size of the box minuseither 8 bytes or16 bytes, depending on the size ofthe header. For more information, see section 4.2 of ISO/IEC 14496-12. ? ? ftyp box ? The F4V formatis based on the ISO MP4 format, which inturn is based onthe Apple QuickTime container format. The subsets ofthe format support different features. The ftyp boxhelps identify the features that a program must support to play a particular file. Flash Player does not enforce anyrestrictionswith respect toftyp boxes. The program tries toplay any file it is given, within the restrictions of the codec types it supports. ?
For more information, see section 4.3 of ISO/IEC 14496-12. ? moov box ? An F4V file must containone and only one moov box. Themoov box is effectively the“header” ofan F4V file. The moov box itselfcontains one or more other boxes, which in turn contain other boxes which define the structure of the F4V data. ?
For more information, see section 8.1 of ISO/IEC 14496-12. ? ? mvhd box ? An F4V file must containone and only one mvhd box. The mvhd box is contained within a moov box and defines playback information that applies to the entire F4V file. ?
SI64 ? ModificationTime????????????? ?if Version == 0 SI32 if Version == 1 SI64 ? The last modification time of the F4V file, expressed as seconds elapsed since midnight, January1, 1904 (UTC) ?
?
For more information, see section 8.3 of ISO/IEC 14496-12. ? trakbox ? An F4V file must containone or more trak boxes. Each trak box is contained?within a moov box. Eachtrak box corresponds toan individual media track within the F4V file and contains other boxes which further define theproperties ofthe media track. ?
For more information, see section8.4 of ISO/IEC 14496-12. ? ? udta box ? The optional udta boxdefines free-form user data. Flash Player does not care what is contained inthisbox. An F4V file cancontain at most one udta box. ?
For more information,?seesection 8.27 of ISO/IEC 14496-12. ? ? meta box ? The optional meta box can contain a variety ofother boxes that carry metadata. An F4V filecancontain at most one meta box. ?
For more information, see section 8.44.1 of ISO/IEC 14496-12. ? mdia box ? Each trak box must containone and only one mdia box. The mdia box contains boxes that define media track properties. ?
For more information, see section 8.7 of ISO/IEC 14496-12. (编辑:李大同) 【声明】本站内容均来自网络,其相关言论仅代表作者个人观点,不代表本站立场。若无意侵犯到您的权利,请及时与联系站长删除相关内容! |