DE102004053877A1 - Media file preparation involves generating media file in accordance with video bitstream file, video metal file and audio bitstream file after recording has been continued - Google Patents

Abstract

The media file preparation method involves generating a video bitstream file, a video meta file and an audio bitstream file at running-time during recording and generating the media file in accordance with the video bitstream file, video metal file and audio bitstream file after the recording has been continued. The video and audio bitstream files are combined into an AV or audio-video bitstream file, audio and video header files are combined into an AV header file and the AV bitstream and header files are combined into a media file. An independent claim is also included for a media file preparation device.

Description

background the invention

The The present invention generally relates to media Files available and in particular, it refers to the inclusion of such Files and recovery in case of power failure.

In led the last years the proliferation of optical recording devices, such as DV (Digital Video) Camcorders, VDRs (Video Disk Recorders) and portable phones with cameras making the use of digital video widely available is. The digital video data can be easily edited and stored easily and securely.

The digitized video data, that is z. B. .mp4 and .3gp files, can be decoded and reproduced. The files include necessary Information to reproduce it, such as B. bitstream length per Frame, the location of the bitstream for each frame in a video File and other information. In general, the information while taken during the term and merged into a media file. The Runtime refers to the phase during the recording of the device. The However, information is complex and therefore requires extensive Use of system resources for AV (audio and video) integration. Furthermore you can the pre-stored information is lost if the recording devices with a Power failure during confronted with the recording. In general, there is no mechanism to restore the recorded data after a power failure, so that the recorded data may be completely lost. The lack Media file recovery mechanisms are a major disadvantage of recording devices and thus inhibits their development.

Overview of the invention

The The present invention discloses methods for providing Media files and corresponding devices. In a possible embodiment Such a method will be a video bitstream file, a video Meta File, an audio bitstream file at runtime during the Recording produced. The media file will be generated after recording after This was stopped, which usually means that this is interrupted or ended.

A possible embodiment a device includes a storage system and a processing unit. The processing unit works to determine if at least one video bitstream file and a video meta file exist on the storage system to determine whether the file size of the video Bitstream Files and the Video Meta Files with the originally recorded ones are compliant, and whether the video bitstream file and the video meta File exist, continue to determine if the video is bitstream File and the video meta file have sufficient information to generate a media file if the file size is compliant and the media file according to the video bitstream file and of the video meta file.

description the drawings

The Method for providing media files and corresponding devices be more explicit with reference to the following detailed Description, which refers to the accompanying drawings and in which:

1 Fig. 12 is a schematic diagram illustrating the architecture of one embodiment of a device providing media files;

2 FIG. 12 is a flowchart illustrating one embodiment of a method describing media files; FIG.

3 shows a schematic diagram illustrating an embodiment of a method for media file generation;

4 FIG. 12 is a flowchart describing one embodiment of a method for media file recovery; FIG.

5a - 5c FIGURES are flowcharts showing one embodiment of a method for checking files;

6 Fig. 10 is a flow chart showing one embodiment of a method for determining whether the file information is sufficient to produce a media file;

7 Fig. 10 is a flowchart showing one embodiment of a method for interconnecting media files;

8th Fig. 10 is a flowchart showing an embodiment of a method of video header file generation; and

9 is a flowchart that shows an execution form of a method for audio header file generation.

detailed description

method to provide media files and related devices disclosed in this invention. In this regard, exemplary embodiments of methods and devices described that perform different functions, so that recording and recovery of media files is possible. In some embodiments, becomes a media in response to the interruption of a recording File generated by different files. These files include Video Bitstream File, a Video Meta File, and an Audio Bitstream File, all typically during the duration of the recording were generated.

The 1 FIG. 12 is a schematic diagram showing the architecture of one embodiment of a media file recording apparatus. FIG. In this embodiment, the device is a DV camcorder, however, other embodiments are possible, which are formed as VDR, as a portable phone with camera capabilities or in any other form.

The device 100 includes a video encoder 110 , an audio encoder 120 , a storage device 130 , such as A hard disk or a memory card, and a processing unit 140 , The device 100 works by using recording and generating stages. During the recording stage, the video encoder generates 110 during runtime a video bitstream file and a video meta file, and the audio encoder 120 generates an audio bitstream file at runtime. The video bitstream file includes a video frame bitstream. The audio bitstream file includes an audio bitstream. The Video Meta File includes a video type, an average frame rate, a video time scale, a position that records the bitstream size in a video file, Visual Object Sequence (VOS) information, one frame timestamp per video frame, one frame length per video Frame and / or other information.

The generated files can be stored on a storage device 130 be filed. It is understood that these files z. B. temporarily in a RAM (not in 1 shown) of the device 100 are stored, and these temporary files can be automatically stored on the storage device 130 if the total number of written data exceeds a predetermined threshold, typically 2 Kb, or in a predetermined period. It goes without saying that the three files, generally the Video Bitstream File, the Video Meta File and the Audio Bitstream File are not playable by a normal Media Player, without a Media File was created.

During the generating step, the processing unit generates 140 automatically a media file corresponding to the Video Bitstream File, the Video Meta File and the Audio Bitstream File. Generally, the generating step is performed after the recording step or after the recording has been interrupted. It goes without saying that in some embodiments the device also includes a media player to decode the information and play the media file.

The 2 shows a flowchart of an embodiment of the present method for recording a media file, the z. B. on a device 100 out 1 can be implemented. The method for media file recording has a recording and a generating step. In detail, when the device 100 recording of media starts (Yes in step S210), the apparatus enters the recording step. In step S220, the video encoder generates 110 at runtime, a Video Bitstream File and a Video Meta File, and the Audio Encoder 120 generates an audio bitstream file at runtime. The files can be stored on a storage system 130 be filed. Then in step S23, it is checked whether the recording has been interrupted. If not, then return to step S2220. In one possible embodiment, the files may be temporarily stored in the main memory (RAM) of the device 100 and then automatically the storage device 130 update. If this is the case, the device will go 100 in the generating step via. In step S240, the processing unit starts 140 to create a media file that corresponds to the content of the Video Bitstream File, the Video Meta File and the Audio Bitstream File.

3 FIG. 10 is a schematic diagram illustrating one embodiment of a media file generation method. FIG. In particular, an audio header file 304 generated according to the audio bitstream file 203 and the contents of the audio header file 304 based on the definitions of a Media File specification. More specifically, an intermediate audio media file (in 3 not shown) by using the audio bitstream file 302 and this is used to create the Audio Header File 304 to create. Necessary information, such. As the frame length and duration, can directly from the audio bitstream file 302 be received and calculated.

A video header file 305 will according to the video Meta File 303 generated, and the contents of the video header file 305 based on the definitions of a Media File specification. The Audio Header File and the Video Header File 305 will be merged ( 308 ) into an AV header file 309 ,

Additionally, the video will be bitstream file 301 and the audio bitstream file 302 to an AV bitstream file 307 merged ( 306 ). The AV Bitstream File 307 and the AV header file 309 become a media file 311 put together ( 310 ).

In the embodiment shown in the 3 can be seen, two merge methods are used, generally normal merge and pseudo merge. Normal merge will create a source file, generally the Video Header File 305 is stored in a buffer (not shown) and the source file is added to the target file via the buffer, generally the audio header file 304 , In the case of pseudo merge, two files are directly linked without a buffer method. This can be achieved by deleting the directory entries of the second file. The size of the first file is then calculated and updated. As the file size with the file size unit of the storage system 130 The size of the first file typically requires a rounding of the cluster arrangement. The total size is (((size of the first file + cluster size - 1) / cluster size) · cluster size) + (size of the second file). Finally, the end of the file (or the end of the EOC chain) of the first file is provided with the first cluster of the second file. It should be noted that the details of the pseudo-merging from Taiwan patent application no. 093123029, filed on July 30, 2004, are known.

In the exemplary embodiment of 3 , is the merging 308 a normal merging process, and merging 306 and merging 310 are pseudo-merging processes that increase the efficiency of merging and thus save system resources. It goes without saying that if no audio file was recorded, the video bitstream file 301 and the video header file 305 can be transferred directly to the Media File.

4 FIG. 12 is a flowchart describing an embodiment of the present invention for recovering media files. FIG. How out 4 As can be seen, there are three stages used in this embodiment to recover media files. First, in step S4100, all necessary files are checked to make sure that these files exist and that these files can also be accessed. In step S4200, the file information is checked to ensure that there is enough information to create a media file. Finally, in step S4300, existing files are merged into a media file.

The 5a - 5c FIGURES are flowcharts disclosing one embodiment of a method for checking files. First, in step S4101, it is checked if a register file, such as a. For example, an .INI file that registers the storage paths for necessary files on the storage device 130 exist. If so, the process proceeds to step S4102. If the register File does not exist, as in step S4104 (FIG. 5b ), all temporary files (Video Bitstream File, Video Meta File and Audio Bitstream File) are stored on the storage device 130 deleted. If the register file exists, as can be seen from step S4102, it is checked whether the register File can be accessed (open / read / write). If this is not possible, as in step S4103, a repair is performed on the File tab to ensure that the file can be accessed next time. Thereafter, in step S4104, all the temporary files are deleted. If the register File can be accessed, as in step S4105, the storage paths for all necessary files are read. The necessary files are stored, based on the storage paths, so that they are stored on the storage device 130 are recoverable.

In step S4106, it is checked if a video bitstream file exists. If not, the process proceeds to step S4109. On the other hand, if a file exists, as in step S4107, a check of the video bitstream file is performed. It should be noted that the file is checked to see if its size matches what it is stored in the file system (not shown) that stores the files on the storage system 130 managed. If the file size matches (the check was successful), step S4112 is executed as the next step of the method. If the size does not match (No in step S4108), as in step S4104, the file or the size recorded in the file system is corrected. For example, the actual size of the file may be determined and the file size may then be updated by the size actually detected. In another embodiment, the file may be trimmed to match the size recorded in the file system.

If the correction is unsuccessful (Yes in step S4110), as in step S4111, a hard disk check (chkdsk) is performed. If the correction was successful (No in step S4110), as in step S4112, it is determined whether a video meta file exists. If this is not the case, the method is continued with step S4104. If so, as in step S4113, a check is made for the video meta file. If the file size matches, the procedure goes to step S4117 continued. If the file size does not match (No in step S4114) as in step S4115, the file or its size as recorded in the file system is corrected. If the correction does not succeed (Yes in step S4116), the process proceeds to step S4111. If the correction is successful (No in step S4116), as in step S4117, it is determined whether a video header file, an audio header file or an audio bitstream file is stored on the storage device 130 exists, and whether their sizes match the existing files. If the file sizes are compliant (Yes in step S4118), the process proceeds to the next stage (S4200). Accordingly, if the size of an existing file does not match (No in step S4118), as in step S4119, a correction is made. If the correction fails (Yes in step S4120), the process proceeds to step S4111. If the correction is successful (No in step S4120), the process advances to the next stage (S4200). At this stage, it is assumed that the media file includes video-referenced files and optionally even audio-referenced files. If there are no video-referenced files in the media file, the restore process is ended. If audio-related files do not exist, the recovery process will continue.

6 FIG. 12 is a flowchart disclosing one embodiment of a method for determining whether the file information is sufficient to produce a media file. First, as in step S4201, the size of the video bitstream file and the video meta file is determined. In step S4202, it is determined whether the size of the video bitstream file exceeds a value defined by the specifications and whether the size of the video meta file exceeds the prestored necessary data. If not (No in step S4202), the process ends. On the other hand, if it is the case as in step S4203, it is checked if the number of video frames exceeds one. If not (No in step S4203), the process ends. If yes, the procedure advances to the next step (S4300).

7 FIG. 10 is a flowchart disclosing one embodiment of a method for composing files. FIG. First, as in step S4310, a video header file is generated. 8th FIG. 10 is a flowchart disclosing an embodiment for generating video header files. FIG. In step S4311, meta information is read from the video meta file and header information is generated accordingly. The meta information includes the video type, an average frame rate, a video timescale, a location of a size that records the bitstream size in a video file, VOS information, a frame timestamp per video frame, and a frame length per video frame and other information , Then, in step S4312, the size of "mdat" ATOM (Audio / Video Bitstream) is set It should be noted that the size "mdat" and "ATOM" refer to the MPEG4 Media specification, so details are not disclosed If an audio bitstream file does not exist and a video header file already exists, the size of "mdat" ATOM is first determined, and the total number of frames in the video meta file is then recalculated. Then, the size of the media file after pseudo-merging is previously determined as Video File Size = ((Video File Size + Cluster Size - 1) / Cluster Size) Cluster Size) and the size becomes "mdat" ATOM Finally, in step S4313, a video header file is generated using the video header information.

In step S4320 of 7 An audio header file is generated. 9 FIG. 10 is a flowchart showing one embodiment of a method for audio meta-file generation. First, it is determined whether audio information has been recorded by determining whether an audio bitstream file or an audio meta-file exists (steps S4321 and S4322). If none of the files exist (No in step S 4321 and No in step S4322), as in step S9323, the correct size of "moov" ATOM is set and the process is terminated The term "moov" refers to the MPEG4 Media File specification, so details can be omitted. If the audio bitstream file exists, as in step S4324, an audio meta file corresponding to the audio bitstream file is generated, and the process proceeds to step S4325. It should be noted that the Audio Meta File contains the necessary information, such as: B. Frame length used to generate an audio header file. If the audio bitstream file does not exist and the audio meta file exists, the process proceeds to step S325. In step S4325, an audio header file corresponding to the audio meta file is generated, and the correct size of "moov" ATOM is set in step S4326, and finally, in step S4327, the audio header file and the video header file become an AV header file If you refer to it again 7 Thus, if audio information has not been recorded (No in step S4330), in step S4340, the video bitstream file and the video header file are merged directly into a media file. If audio information has been recorded (Yes in step S4330), as in step S4350), the video bitstream file and the audio bitstream file are merged into an AV bitstream file, and in step S4360 the AV bitstream file and the AV header file are merged merged into a media file.

It is understood that, if the recording If a device experiences a power failure during capture or creation (merge), an embodiment may check the Media File Recovery process, whether a Video Bitstream File, the Audio Bitstream File, the Video Meta File, the Audio Meta File, the Audio Header File, the Video Header File and the AV Header File exist to determine at which step the merge process was interrupted. To start the merge process, three essential files, generally the Video Bitstream File, the Audio Bitstream File and the Video Meta File are needed. During power outage, some files may disappear, allowing another merge process to be performed for recovery. If z. For example, if a power failure occurs during the pseudo-merge process for AV bitstream files, the audio bitstream file may disappear, but the audio meta-file still exists because the audio bitstream file has already been added to the AV bitstream file, but not applies to the Audio Meta File. From this, the method according to the present invention can check which files exist and thus it is able to determine in which step of the merging process the power failure occurred. Depending on what has been determined, the following merge procedure is performed for recovery.

method to create media files or certain aspects or areas of it, can in the form of a program code (generally executable instructions) on one storable medium, z. A product such as a floppy disk, a CD-ROM, a hard disk or any other machine-readable medium so if the program is in the memory of a machine was loaded, such. As in a computer, the machine thereby Skills get to perform the said procedure. The procedures can also in embodiments be distributed, in which the program code via a transmission medium, such. B. an electrical cable or a wiring, an optical fiber or over a radio wave or any other form of transmission is transmitted, wherein if the program was received by the machine, it into memory the machine will arrive, such. In a computer, so The machine becomes a device to the disclosed methods perform. Once implemented on a common processor, so the program code becomes one in connection with this processor inventive device that works in an analogous way, such as a customized circuit tailored to the application.

Also when the invention is in the form of examples and with reference to preferred embodiments However, it should be clear that the invention is not limited to these examples and preferred embodiments. Thus, you can Persons who are familiar with the prior art continue Modifications and modifications without departing from the scope and deviate from the core idea of the invention. It follows that that the protection of the present invention should be defined by the following claims and their equivalents.

Claims (40)

A method of providing a media file full: Generation of a video bitstream file, a video meta Files and an audio bitstream file at runtime during the recording; and Generation of the media file according to the Video Bitstream Files, Video Meta Files and Audio Bitstream Files after the recording has been paused. The method according to the preceding claim 1, further comprising: Generation of an audio header file according to the Audio bitstream files; Generation of a video header file according to the Video Meta Files; Connecting the video bitstream file and the Audio Bitstream Files to an AV Bitstream File; Connect of the audio header file and the video header file in an AV header File; and Connect the AV bitstream file and the AV header file in a media file. The method according to the preceding claim 2, further comprising: Generation of at least one audio header Files and a Video Header File according to the definitions of a Media File specification. The method according to the preceding claim 1, 2 or 3 further comprising: Generation of a video header Files according to the Video Meta Files; Determining if one Audio information recorded according to the audio bitstream file has been; and Connect the video bitstream file and the video header Files to a Media File if audio information has not been recorded. The method according to the preceding claim 4 further comprising: Generation of the Video Header File according to the definitions a media file specification. The method of any of claims 1, 2, 3, 4 or 5 further comprising: generating a video meta file by recording a video type, an average frame rate, a video time scale, a position that records the bitstream size in a video file, VOS (Visual Object Sequence) information, a frame timestamp per video frame, and a frame length per video frame of it. A method for providing media files full: Determine if at least one video bitstream file and a video meta file exist on the storage system; Determination, whether the file size of the video Bitstream Files and the Video Meta File match the file size, the originally was recorded when the video bitstream file and the video Meta File exist; Determining if the video bitstream file and the video meta file have sufficient information to create a media file if the file sizes conform are; and Creation of a media file according to the video Bitstream Files and Video Meta Files. The method of claim 7, further comprising: correction the video bitstream file or the video meta file if the file size is not compliant. The method of claim 8, further comprising: Perform a Volume check if the correction of the video bitstream file or the video meta file to fail. The method of claims 7, 8 or 9, further full: Determining Whether a Register File Exists the storage paths of the Video Bitstream Files and the Video Meta Files stores; and deletion all files from the storage device, if the register file does not exist. The method of claims 7, 8, 9 or 10, further full: Determining if a video header file, an audio header File or an audio bitstream file exist on the storage device, and Check if the file size of the exist Files are compliant. The method of claims 7, 8, 9, 10 or 11, further full: Determining if the video bitstream file and the Video Meta File have sufficient information to a media File, where it is determined whether the size of the video bitstream file the exceeds the value defined by the specification, and whether the size of the video Meta Files exceeds the necessary pre-stored data. The method according to claims 7, 8, 9, 10, 11 or 12, further comprising: Determine if the video is bitstream File and the video meta file have sufficient information to to generate the Media File, which determines if the total number the video frame numbers exceeds 1. The method of claims 7, 8, 9, 10, 11, 12 or 13, further comprising: Generation of a Video Header File according to the video meta file; and Introducing the video Bitstream Files and the Video Header Files in the Media File. The method of claims 12, 13 or 14, further full: Generation of a Video Header File with the Video Meta File corresponds; Generation of an audio header Files that correspond to the audio bitstream file if the Audio Bitstream File exists; Merging the video bitstream file and the audio bitstream file into an AV bitstream file; Merging the Audio Header Files and Video Header Files in an AV Header File; and bring together the AV Bitstream Files and the AV Header Files into a Media File. The method of claim 15, further comprising: generation an audio header file or the video header file according to the definitions a media file specification. The method of claim 16, further comprising: generation of the video header file by transforming a video type, a average frame rate, a video time scale, a position that has the bitstream size in one Video File Records, VOS (Visual Object Sequences) Information, one frame timestamp per video frame and one frame length per Video Frame, which was recorded in the video Meta File, to a Format of the Media File Specification. A method for providing media files, full: Determine if at least one video bitstream file and a video meta file exist on a storage device; and generation of the media file according to the video bitstream file and the video Meta files. The method of claim 18, further comprising: determining whether an audio bitstream file exists on the storage device and generating the media file corresponding to the video bitstream file, the Video Meta File, and the Audio Bitstream File. The method of claim 19, further comprising: generation an audio header file corresponding to the audio bitstream file; generation a video header file corresponding to the video meta file; Merging the Video Bitstream Files and the Audio Bitstream Files in an AV Bitstream File; bring together of the audio header file and the video header file in an AV header File; and bring together the AV Bitstream Files and the AV Header Files into a Media File. A device comprising: a video encoder, which generates a video bitstream file at runtime, and a video Meta File during the record; an audio encoder that is at runtime during recording generates an audio bitstream file; and a processing unit for generating a media file according to the video bitstream Files, the Video Meta Files, and the Audio Bitstream Files, in which this is done after termination or interruption of the recording. The apparatus of claim 21, wherein the processing unit an audio header file corresponding to the audio bitstream Files generated, and a video header file corresponding to the video meta Files, the video bitstream file and the audio bitstream File processed in an AV bitstream file, the audio header file and merge the video header file into an AV header file, and the AV Bitstream File and the AV Header File into a Media File merges. The device according to claims 21 or 22, wherein the Processing unit continues to generate a video header file, the corresponds with the video meta file that continues to determine whether an audio recording was recorded, according to the audio Bitstream Files, and the Video Bitstream File and Video Merge header file to a media file if no audio is recorded has been. The device according to claims 21, 22 or 23, wherein the video encoder continues to produce the video meta file through the Recording a video type, an average frame rate, a video time scale, a position that has the bitstream size in one Recording video file, a VOS (Visual Object Sequence) information, a frame timestamp per video frame and one frame length per video frame. A device comprising: a storage unit; and a processing unit to determine if at least a video bitstream file and a video meta file exists on the storage device, to determine if the file size of the video Bitstream files and the video meta file is conform to the file size, the original was recorded if the video bitstream file and the video Meta File exist to determine if the video is Bitstream File and the video meta file have sufficient information to create a media file if the file sizes are compliant and the media File according to the video Bitstream File and the video Meta File generated. The apparatus of claim 25, wherein the processing unit continue to correct the video bitstream file or the video meta file, if the file sizes are not are compliant. The apparatus of claim 26, wherein the processing unit continues to perform a disk check if the correction of the Video Bitstream Files or the Video Meta Files were unsuccessful. The device according to claims 25, 26 or 27, wherein The processing unit continues to determine if a register file exists, the memory paths of the video bitstream file and the Video Meta Files on the storage device records and all delete corresponding files on the storage device, if the register file Does not exist. The device of claims 25, 26, 27 or 28, wherein The editing unit also determines if a video header File, an Audio Header File or an Audio Bitstream File on the storage device exist, and further determines if the file size of all existing files is compliant. The device according to claims 25, 26, 27, 28 or 29, wherein the processing unit further determines if the video is bitstream File and the video Meta File have sufficient information to to generate a media file by determining if the size of the video Bitstream files outside the values defined in the specification and whether the size of the video Meta Files exceeds the necessary pre-stored data. The device according to claims 25, 26, 27, 28, 29 or 30, wherein the processing unit further determines whether the video Bitstream File and the video meta file sufficient information to generate a media file by determining whether the total video framing number exceeds 1. The apparatus of claims 25, 26, 27, 28, 29, 30 or 31, wherein the processing unit further generates a video header file associated with corresponds to the video meta file, and wherein the video bitstream file and the video header file are merged into a media file. The device according to claim 32, wherein the Processing unit continues to generate a video header file, the corresponds to the video meta file, an audio header file which corresponds to the audio bitstream file if the audio bitstream file exists, then the video bitstream File and the audio bitstream file into an AV bitstream file, the Audio Header File and the Video Header File in an AV Header File merge and the AV Bitstream File and the AV Header File into a Media Merge file. The device according to claim 33, wherein the Processing unit continues to generate a video header file by a video type, an average video frame rate, a video time scale, a position, the bitstream size in one Recording video file, a Visual Object Sequence (VOS) information, a frame timestamp per video frame and one frame length per video frame, recorded in Video Meta File, to be considered and taking into account a format of a Media File specification becomes. A device comprising: a storage device; and a Processing unit to determine if at least one video bitstream File and a video meta file exist on the storage device and a media File, according to the video bitstream file and the Video Meta Files. The device according to claim 35, wherein the Processing unit also determines if an audio bitstream file on the storage device exists, and a media file corresponding to the video bitstream File, the Video Meta File and the Audio Bitstream File. The device according to claim 36, wherein the Processing unit continues to generate an audio header file, accordingly to the audio bitstream file, furthermore a video header file is generated, which corresponds to the video meta file, the video bitstream File and the audio bitstream file merges into an AV bitstream file, and the AV Bitstream File and the AV Header File into a Media File merges. A device comprising: Means of production a video bitstream file and a video meta file at runtime the recording; Means for generating an audio bitstream file during the Duration of the recording; and Means for generating a media Files according to the Video Bitstream File, the Video Meta File and the audio bitstream file after the recording has finished. A device comprising: Means of determination, whether at least one video bitstream file and one video meta file on exist a storage system; Means of determining whether the file size of the video bitstream Files and the Video Meta Files compliant to the file size, the original was recorded if the video bitstream file and the video meta File exist; Means of determining if the video is bitstream File and the video meta file have sufficient information to create a media file if the sizes are compliant; and medium for generating a media file corresponding to the video bitstream Files and the Video Meta Files. A device comprising: Means of determination, whether at least one video bitstream file and one video meta file exist; and Means for generating the media file corresponding to the video Bitstream File and Video Meta File.