JP2004199787A - File management method , and recording device provided with the file management method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To prevent disappearance of required information by taking over and utilizing required information recorded at the time of recording format of one at the time of recording format of the other, even if recording is changed from recording format of one to recording format of the other. <P>SOLUTION: In a file management method by which a plurality of recording formats can be recorded in a rewritable recording medium, a common file of which contents are information which can be utilized when recording is performed with each recording format is provided, when the recording format is changed, the common file is taken over from a recording format before change. The common file manages the number of times of recording for a recording region of the management information. <P>COPYRIGHT: (C)2004,JPO&NCIPI

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a file management method when recording can be performed in a plurality of recording formats by initialization or the like on a recording medium such as a rewritable optical disk, and a recording apparatus including the file management method.
[0002]
[Prior art]
A DVD-RW disc (optical recording medium) is a rewritable phase-change type that can record information by irradiating the recording medium with a light beam and causing an optical change in the recording material. An optical recording medium. Also, since video information can be recorded for several hours, it is used for recording video information such as television broadcasting.
[0003]
Two recording formats for DVD-RW discs are defined: a video recording format (hereinafter, referred to as a VR format) and a video format.
[0004]
In the VR format, user information to be recorded is managed by volume information and file system information based on the UDF 2.0 standard as a logical recording format, and the information body (VR_MOVIE.VRO Since the file and the playback control information (VR_MANGER.IFO file) are generated and recorded as independent files, this is a recording format suitable for recording in real time such as a television broadcast. In this recording method, when information such as video is recorded by a user, file system information for managing the information recorded by the user is frequently rewritten. Also, the volume information is rewritten as needed. Therefore, the recorded information can be reproduced using the volume information and the file system information.
[0005]
A method of recording a file in the VR format on a DVD-RW disc will be briefly described. FIG. 2 shows the allocation of disk areas when recording on a disk in the VR format. The logical sector number (LSN) 0h (h indicates a hexadecimal number; the same applies hereinafter) to 217Fh from the volume information recording area 107, and 2180h to 277Fh from the file system information and manager file recording areas 108 and 2780h to the data recording area Assign to 109.
[0006]
The file recording sequence when recording in VR format is shown below. First, an initialization operation for initializing to a VR format is performed. On the disc, there is an area called Recording Management Area for managing recording information, and a Control Data Zone for describing physical information of the disc. When the information is initialized to the VR format, information is also recorded in these areas, but the recording in these areas is not directly related to the present invention, and a description thereof will be omitted. When the initialization operation is started, the area from LSN = 0h to 217Fh and the area from 2180h to 277Fh in FIG. 2 are all cleared to 0x00. Next, volume information is recorded in the volume information recording area 107 from LSN = 0h to 217Fh, and file system information from LSN = 2180h to 277Fh and file system information in the manager file recording area 108.
[0007]
Next, when the user starts recording video data such as a television broadcast, recording of the VR_MOVIE.VRO file, which is the information body of the video data, in the data recording area 109 from LSN = 2780h is started. When the recording of the video data ends, the file system information from LSN = 2180h and the VR_MANGER.IFO file as the playback control information are recorded in the manager file recording area 108, and the file system information is updated and recorded. If necessary, the volume information is recorded in the volume information recording area 107 of LSN = 0h to 217Fh.
[0008]
On the other hand, the video format uses a UDF (Universal Disk Format) bridge as a logical recording format, and controls the reproduction mode of information to be recorded in a recording format that becomes the same format as a read-only DVD when finalized. All of the playback control information (called navigation information in the DVD standard) is created in consideration of the correspondence between the playback control information and the created playback information and information corresponding to the playback information. The main body (content) must be collected and recorded on an optical disk. Therefore, this recording method is not a recording format suitable for recording along real time such as television broadcasting. A method of recording a plurality of pieces of information in real time in this format and a method of reproducing information recorded before finalization are disclosed as conventional techniques (for example, see Patent Documents 1 and 2). ).
[0009]
The file recording sequence when recording in video format is shown below. First, an initialization operation for initializing to a video format is performed. On the disc, there is an area called Recording Management Area that manages the recorded information, and a Control Data Zone that describes the physical information of the disc. When the video format is initialized, information is also recorded in these areas. Since the recording in these areas is not directly related to the present invention, the description is omitted. At this time, in order to secure the volume information recording area 101, the file system information recording area 102, the VMGI file recording area 103, the menu VOBS file recording area 104, and the backup VMGI file recording area 105 shown in FIG. Clear all areas up to 5FFh with 0x00.
[0010]
Next, when the user starts recording video data such as a television broadcast as one title, 00h to secure an area of 30h for recording a VTSI (Video Title Set Information) file from LSN = 600h as shown in FIG. Clear with data and start recording VOBS (Video Object Set for Titles) file from LSN = 600h + 30h. Note that P = 600h in FIG. When the recording of the video data is completed, the backup VTSI file 112 is recorded from the position following the VOBS file, and finally the VTSI file 110 is recorded from LSN = 600h. To record another title, the operation just described is repeated.
[0011]
Then, when there is a request for finalization from the user, the UDF Bridge Volume Structure is recorded in the volume information recording area 101 of LSN = 0h to 100h from LSN = 0h to 5FFh initially secured, as shown in FIG. = File structure information recording area 102 from 101h to 2FFh, File structure information in VMGI file recording area 103, VMGI (Video Manager Information) file in menu VOBS file recording area 104, Menu VOBS (Video Object set) file Is recorded in the backup VMGI file recording area 105.
[0012]
Since a DVD-RW disc has two recording formats and is a rewritable recording medium, recording and erasing can be performed in the same format, and initialization is performed in the same format or in another format. It is also possible.
[0013]
Generally, a phase-change type rewritable optical disk is heated to melt a recording film for recording. Therefore, if the rewritable operation is performed several times, the number of defects in the film increases, and errors tend to increase.
[0014]
In the VR format of DVD-RW, file system information (volume information if necessary) is frequently rewritten, so if repeated recording is performed, reading errors of file system information and volume information increase, and in some cases, all There is a problem that information cannot be read out. Therefore, before it becomes impossible to read the file system information and the volume information, it is necessary to move the file system information to another location so that the file system information and the volume information can always be read. Therefore, a spare area (Sparing Management Area) for that purpose is secured in the volume information of the DVD-RW, and when read errors increase, the specific management information is moved to the Sparing Management Area and used.
[0015]
Also, a method of recording a dummy file on a disc without relation to the reproduction information of the disc has been disclosed as a conventional technique (for example, see Patent Document 3).
[0016]
Further, a method for solving the problem of increasing read errors by securing a plurality of locations for recording files and rewriting the locations each time to a different location is disclosed as a conventional technique (for example, see Patent Document 4).
[0017]
[Patent Document 1]
JP 2002-56650
[0018]
[Patent Document 2]
JP 2002-63765
[0019]
[Patent Document 3]
JP 2001-243096
[0020]
[Patent Document 4]
JP 2001-291367
[0021]
[Problems to be solved by the invention]
In Patent Document 4 described above, the number of times of recording of file management information can be increased by holding the file management information in a plurality of recording locations and recording the file management information in a recording area where the number of recordings is as small as possible. Cannot support format.
[0022]
Also, even if recording is repeatedly performed in the DVD-RW VR format and the file system information and volume information with increased read errors are moved to the Sparing Management Area, if they are initialized with a video format with a different recording format, It is impossible to determine whether the error in the area has increased. Even if you do not understand once, even if you re-initialize it again in the VR format, you already lost the information of the area where the error has increased, so you will have to re-record it in the place where the error increased. In the worst case, there is a problem that, when reproduced, the error is too large to be read.
[0023]
Also, when recording video information in VR format, if an area that can not be recorded due to scratches etc. is found on the disc, that area can be recorded as an invalid area in File Entry (Non-Allocatable Space Stream) However, this information is completely lost once it is initialized in the video mode.
[0024]
An object of the present invention is to record necessary information recorded in one recording format in another recording format even when the recording format is changed from one recording format to another recording format when recording in a plurality of recording formats on a rewritable recording medium. It is also used to take over the format and prevent loss of necessary information.
[0025]
[Means for Solving the Problems]
In order to solve the above problems, the present invention mainly employs the following configuration.
In a file management method capable of recording a plurality of recording formats on a rewritable recording medium,
Provide a common file containing information that can be used when recording in each recording format,
In each recording format, a common file is recorded as a dummy file, and when the recording format is changed, the common file is inherited from the recording format before the change.
[0026]
In a file management method capable of recording a plurality of recording formats on a rewritable recording medium,
When changing from one recording format to another recording format, and further returning to the one recording format,
When changing the necessary information of the one recording format to the other recording format, record as a dummy file,
When returning to the one recording format, the necessary information recorded as the dummy file in the other recording format is restored.
[0027]
By adopting such a configuration, the present invention adopts one recording format even when the recording format is changed from one recording format to another recording format when recording on a rewritable recording medium in a plurality of recording formats. The necessary information that is sometimes recorded can be taken over and used for other recording formats, and the loss of the necessary information can be prevented.
[0028]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, a recording apparatus according to an embodiment of the present invention will be described with reference to the drawings. First, UDF 2.0, which is a file used in the VR format, will be briefly described. This UDF 2.0 is divided into volume level management information and file system level management information. There are two types of address specification methods. One is a logical sector number (LSN) where the head of the volume level management information is 0, and the other is a logical block that specifies an address in a partition excluding the volume level management area. There is a number (LBN).
[0029]
FIG. 5 shows an example of the arrangement of volume information in the VR format. From LSN = 0 to 8575, Volume Recognition Sequence, Main Volume Descriptor Sequence, Reserve Volume Descriptor Sequence, Logical Volume Integrity Sequence, 1st Anchor Point, and Sparing Management Area are described.
[0030]
FIG. 6 shows file system information in VR format, and FIG. 7 shows Directory Structure in VR format. In the example of FIG. 6, Space Bitmap, File Set Descriptor Sequence, ICB for System Stream Directory, System Stream Directory, ICB for Non-Allocatable Space Stream, ICB for Root Directory, Root Directory, ICB for DVD_RTAV Directory from 8SN to 8730. , ICBs for DVD_RTAV files.
[0031]
To record this volume information and file system information on the DVD-RW disc, the volume information recording area 107 from LSN = 0h to LSN = 217Fh and the volume information from LSN = 2180h to 277Fh are recorded on the disc as shown in FIG. It is allocated to the file system information and the manager file recording area 108. The size of the volume information in FIG. 5 is 8576 (= 2180h) sectors, which are recorded in the volume information recording area 107 from LSN = 0h to LSN = 217Fh in FIG. In FIG. 6, the size of the file system information is 155 sectors, and the file system information from LSN = 2180h in FIG. Then, the VR_MANGER.IFO file, which is playback control information, is recorded in the remaining 108 area of the file system information and the manager file recording area 108 where no recording is made (see the arrangement relationship in FIG. 14 described later).
[0032]
FIG. 14 shows the relationship between the volume information and the file system information. The 1st Anchor Point of the volume management information is always recorded in LSN = 256, and describes the position information and the size information of the Main Volume Descriptor Sequence and the Reserve Volume Descriptor Sequence. In the Main Volume Descriptor Sequence and the Reserve Volume Descriptor Sequence, the position information and the size information of the Logical Volume Integrity Sequence, the First Sparing Table, the Second Sparing Table, the File Set Descriptor Sequence of the file system information, and the Space Bitmap are described.
[0033]
In the File Set Descriptor of the file system information, position information and size information of File Entry (Root Directory) and File Entry (System Stream Directory) are described. Here, when the File Entry (hereinafter, referred to as FE) is a directory, position information and size information in which directory information (a set of File Identifier Descriptor (hereinafter, referred to as FID)) is recorded are described. As the directory information, an FID indicating the position information and size information of the FE in which the own directory information is recorded, and an FID indicating the position information and size information in which the FE corresponding to the file name and the directory name are recorded are recorded. ing. Therefore, the location information and size information of FE (DVD_RTAV) can be known from FID (DVD_RTAV) of Root Directory, and VR_MANGER.IFO file and VR_MOVIE.VRO file under DVD_RTAV directory from FE (DVD_RTAV). You can know. The position information and the size information of the FE (VR_MANGER.IFO) can be obtained from the FID (VR_MANGER.IFO) of the DVD_RTAV directory, and the position information and the size information of the FE (VR_MOVIE.VRO) can be obtained from the FID (VR_MOVIE.VRO). When the FE is a file, the position information and the size information on the disk where the file exists are described. Obtain the position information and size information of the VR_MANGER.IFO file recorded on the disc from FE (VR_MANGER.IFO), and the position information and size information of the VR_MOVIE.VRO file recorded on the disc from FE (VR_MOVIE.VRO) be able to.
[0034]
Since this information starts from the 1st Anchor Point of the volume management information and is linked to the file recorded on the disk, if even one of them cannot be read, the file recorded on the disk cannot be reached, and the information is recorded on the disk. The information such as the reproduced video cannot be reproduced. Therefore, it is desired that the volume information and the file system information be written within the guaranteed number of rewrite times without writing more than the guaranteed number of rewrite times on the disk. DVD-RW records 16 sectors as one block, in units of blocks. Therefore, it is desirable to avoid recording more than the specified number of rewrites in a specific block. Therefore, a Sparing Area that can be replaced in units of blocks is provided in the volume management information.
[0035]
When a specific block is moved to the Sparing Area, the source and destination are managed in the Sparing Table. A method of managing the source and destination will be described with reference to FIG. In the Sparing Table, there is a field called Sequence Number, and the value in this area indicates which Map Entry should be used if alternative processing is performed. For example, if Sequence Number = 1, 1st Map Entry Is moved to the destination indicated by.
[0036]
The Map Entry has a field describing the source address and a field describing the destination. The destination of the 1st Map Entry is the first LSN of the Sparing Area = 140h. The destination of the 2nd Map Entry is 150h, and the destination of the 3rd Map Entry is 160h. The source field of the Map Entry corresponding to the Sparing Area not yet used contains FFFFFFFFh, and if FFFFFFF0h is contained in this field, it indicates that the field cannot be used or is in use. In this source field, it is necessary to describe not the LSN but the LBN.
[0037]
When the volume information moves to the Sparing Area and when the file system information moves to the Sparing Area, the description method in the Sparing Table is different, so the volume information will be described first. For example, a case will be described in which a Main Volume Descriptor Sequence described from LSN = 32 with Sequence Number = 1 is moved in Sparing Area. When the Main Volume Descriptor Sequence is moved to a block starting from LSN = 140h, FFFFFFF0h indicating that it is in use is described in the field describing the source LBN of the 1st Map Entry. Since the position information of the Main Volume Descriptor Sequence is described in the 1st Anchor Point, the position information of the Main Volume Descriptor Sequence of the 1st Anchor Point is rewritten to 140h. Then, the Sequence Number of the Sparing table is incremented to 2 in advance.
[0038]
As another example, if you want to move a block from LSN = 140h of Sparing Area with Sequence Number = 2, since the block from 140h now contains the Main Volume Descriptor Sequence, the source field of the 2nd Map Entry FFFFFFF0h, and rewrite the position information of the Main Volume Descriptor Sequence of the 1st Anchor Point to 150h. Then, set Sequence Number = 3.
[0039]
Next, when moving the file system area to the Sparing Area, since the file system area is within the partition, the address can be specified by the logical block number LBN. When a block in the LBN is moved, for example, when Sequence Number = 3 in the Sparing Table and it becomes necessary to move one block of the Space Bitmap described from LBN = 0h, Sequence Number = 3 in the Sparing Table Therefore, one block from LBN = 0h of the Space Bitmap is recorded in the block from LBN = 160h at the destination of the 3rd Map Entry, and LBN = 0h is written to the source of the 3rd Map Entry. Then, the Sequence Number of the Sparing Table is incremented to four.
[0040]
Another method is to use the space bitmap that describes whether or not the LBN has already been used, move it to a part that has not been used, and write it. For example, when moving a block starting from LBN = 90h, a method is used in which an area corresponding to 9Fh from LBN = 90h is used on the Space Bitmap and moves to an area not used on the Space Bitmap. In this method, as shown in FIG. 14, related position information must be rewritten so as to trace from the 1st AnchorPoint to each file.
[0041]
In the present invention, a volume information recording area 107 and a common (COMMON) file for managing the number of times of recording in the file system information and the manager file recording area 108 are further provided. Here, this COMMON file is a file that is ruled only by the file management method of the present invention, and is always recorded in the present invention both when recording in the VR format and when recording in the video format. In a recording device that does not employ the file management method of the present invention, this COMMOM file is a dummy file.
[0042]
Here, the management of the number of times of recording in the volume information recording area 107, the file system information and the manager file recording area 108 will be described. In FIG. 2, the volume information recording area 107, the file system information and the manager file recording area 108 = 0h to LSN = 277Fh. Since a DVD-RW records 16 sectors as one block, if the volume information, file system information, and manager file recording area 108 are expressed in block units, from Block No = 0h to Block No = 277h, 278h, 10 In hexadecimal, there are 632 areas. If the area for recording the number of times of rewriting of one block is represented by 2 bytes, the number of times of recording 65535 can be counted. Since the number of recordings of the DVD-RW can be sufficiently managed by this 65535 times, the number of rewrites of one block may be managed by 2 bytes. Therefore, to represent the blocks of the volume information recording area 107, the file system information, and the manager file recording area 108, 278h (632) blocks × 2 bytes = 4f0h (1264) is sufficient. Therefore, the COMMON file for managing the number of recordings can be represented by one sector (2048 bytes), and can be represented as shown in FIG. If the Reserved Volume Descriptor Sequence recorded from LSN = 64 is recorded on the disc 10 times, 10 is described in the area of Block No = 4 in FIG. When the COMMON file itself is recorded on a disk, the number of recordings is described in the Block No. for recording the COMMON file.
[0043]
This COMMON file is located under the Root directory as shown in FIGS. Here, FIG. 8 shows a VR-format File Structure when recording a COMMON file, and FIG. 1 shows a VR-format Directory Structure when recording a COMMON file. In this example, the COMMON file is located under the Root directory and can be traced as FE (Root) → FID (COMMON) → FE (COMMON) in the Root directory, but as mentioned earlier, this COMMOM file Is a rule created only by the file management method of the present invention, and becomes a dummy file in a recording apparatus that does not employ the file management method of the present invention. The position to be recorded on the disc is described in the file system information and the manager file recording area 108.
[0044]
Two threshold values are used for the number of times of rewriting, and a first threshold value and a second threshold value are provided. For the first threshold value and the second threshold value, the second threshold value is set to a larger value. Both the first threshold value and the second threshold value are set within the range of the guaranteed number of recordings of the DVD-RW. The first threshold is used as an alternative criterion for a block, and the second threshold is used as a criterion for write-protection (the second threshold is used when recording in video format, so the description of how to use it is omitted here). The first threshold value and the second threshold value may be the same value. When recording in the VR format, a block exceeding the first threshold is moved to another location.
[0045]
And even if this disk is re-initialized in VR format again, the contents of this COMMON file will not be cleared and will be inherited as it is. Then, the number of times of recording of the COMMON file is checked, a block in which recording exceeding the first threshold is performed is searched, and recording is not performed in the block. For example, if the number of recordings of Block No = 2 exceeds the first threshold, the Main Volume Descriptor Sequence that should have been recorded from LSN = 20h is recorded in Sparing Area without recording in LSN = 20h. Also check the Sparing Area in the COMMON file, search for a valid Sparing Area, and build a Sparing Table. Specifically, since the block numbers 14h to 213h of the COMMON file in FIG. 10 correspond to the Sparing Area, the number of recordings is checked from 14h. Sequence Number = 1, and if the number of recordings of 14h exceeds the first threshold, the Sequence Number of the Sparing table is incremented by 1, the source of the 1st Map Entry is set to FFFFFFF0h, and 15h is checked. If the recording count of 15h exceeds the first threshold value, the Sequence Number of the Sparing table is incremented by 1, the source of the 2nd Map Entry is set to FFFFFFF0h, and 16h is checked. This is repeated to construct a Sparing Table while searching for Sparing Areas not exceeding the first threshold.
[0046]
Similarly, in the file system information and manager file recording area 108, the number of recordings is checked from Block No = 221h of the COMMON file in FIG. 10, and if Block No = 221h exceeds the number of recordings by the first threshold, The 221h is moved to the Sparing Area or is being used on the Bitmap, and is recorded in a place other than the 221h, so that it is not recorded in the Block exceeding the first threshold of the number of recordings.
[0047]
Next, a case where this disc is recorded in a video format will be described. First, initialize in the video format. At this time, to secure the volume information recording area 101, the file system recording area 102, the VMGI file recording area 103, the menu VOBS file recording area 104, and the backup VMGI file recording area 105 as shown in FIG. .
[0048]
When the user records video data or the like, VTSI, VOBS, and backup VOBS are recorded in the data recording area 106 as shown in FIG. When the user instructs finalization, the volume management information, file system management information, VMGI file, VOBS file for menu, and backup VMGI file shown in FIG. 3 are constructed, and the volume information is recorded in the volume information recording area 101 in FIG. The file system information is recorded in the file system recording area 102 of FIG. 9, the VMGI file is recorded in the VMGI file recording area 103, the menu VOBS file is recorded in the menu VOBS file recording area 104, and the backup VMGI file is recorded in the backup VMGI file recording area 105. I do.
[0049]
At this time, the COMMON file for managing the number of recordings used in the VR format is also moved to the video recording mode. When the user attempts to record in the video recording mode, it initializes first, but then saves the COMMON file used for VR recording. Then, the number of recordings of the block from Block No = 0h to 277h is updated even when recording is performed in the video recording mode. If it is necessary to record this COMMON file before finalization, the COMMON file is recorded in the block having the largest possible address in the file system information recording area 102 while checking the number of times of recording of the COMMON file. When finalizing, as shown in FIGS. 11 and 17, a COMMON file is described and recorded on a disk. Also in this example, the COMMON file is placed under the Root directory and can be traced as FE (Root) → FID of Root (COMMON) → FE (COMMON), but this COMMON file is ruled only by the file management method of the present invention. It is a dummy file when viewed from a recording device that does not employ the file management method of the present invention.
[0050]
When re-initializing this disc to the video format again, the COMMON file will be inherited and initialized. The same applies when re-recording a disc recorded in the video format in the VR format. The COMMON file is inherited and the disc is initialized in the VR format.
[0051]
In the volume information of the video format in FIG. 3 or FIG. 11, there is no Sparing Management Area which is an alternative area in order to have the same file management format as the DVD of the reproduction system. Therefore, the same management information is recorded in the same place. Therefore, the first threshold of the COMMON file may be exceeded. When finalizing, if it exceeds the second threshold, if the disk is initialized and recorded in the future, the file management information may not be able to be read correctly. In the worst case, playback will not be possible There is a possibility. "
[0052]
In addition, when recording in the VR format, if all areas of the Sparing Area exceed the first threshold value, the user is prompted, "If this disc is initialized and recorded in the future, file management information will be read correctly. May be unable to play. In the worst case, playback may not be possible. "
[0053]
Next, an embodiment will be described in which when recording from one recording format to another recording format, information is taken over by a dummy file. In this embodiment, the dummy file exemplifies a content having a Non-Allocatable Space Stream representing a non-recordable area on the disc, which is not used in the video format and is used only in the VR format. Things. Therefore, when the format is changed from the VR format to the video format, the file containing the Non-Allocatable Space Stream or the like is a dummy file (the dummy file is stored even if initialized to the video format). When the video format is changed to the VR format again, the dummy file is restored and used.
[0054]
If the disc recorded in the VR format has scratches on the disc, and if it can not be recorded on that part, it indicates that the Non-Allocatable Space Stream file is recorded in the area including the front and back of the scratch and it can not be played ing. At this time, the FE (Non-Allocatable Space Stream) records the position information and the size information of the area including before and after the flaw.
[0055]
When the disc is re-initialized in the video format, FE (Non-AllocatableSpace Stream) is written to the disc as a dummy file. Specifically, when the initialization in the video mode is requested, as shown in FIG. 9, the volume information recording area 101, the file system information recording area 102, the VMGI file recording area 103, the menu VOBS file recording area 104, the backup Clear in 00h to secure the VMGI file recording area 105. Then, a FE (Non-Allocatable Space Stream) in VR format is recorded in a block having the largest possible address in the file system information recording area 102 while observing the number of recording times of the COMMON file. Further, when the user records video data or the like on a disc, the video data is recorded in the data recording area 106 in FIG.
[0056]
Then, when finalizing, as shown in FIGS. 16 and 12, FE (Non-Allocatable Space Stream) of the VR format recorded on the disc is constructed as a DUMMY file, and file system information is constructed and recorded on the disc. Here, FIG. 16 shows Volume Structure and File Structure of a video format when recording a DUMMY file, and FIG. 12 shows Directory Structure of a video format when recording a DUMMY file.
[0057]
Further, when the disk is re-initialized in the video format again, the DUMMY file (FE (Non-Allocatable Space Stream) in VR format recorded on the disk) is taken over and the disk is initialized.
[0058]
Then, when initializing this disc in the VR format, when re-initializing it in the video format, read the FE (Non-Allocatable Space Stream) of the VR format recorded on the disc as a DUMMY file in the video format, and Based on this, reconstruct FE (Non-Allocatable Space Stream) in VR format.
[0059]
As described above, the present invention is characterized by having the following configuration and having functions and functions. That is, in a recording device capable of recording a plurality of recording formats on one rewritable recording medium, a common (COMMN) file (for example, a file indicating the number of recordings) can be recorded in each recording format. Yes, when changing information of one recording format (for example, VR format) to another recording format (for example, video format), a Descriptor used only in one format (VR format) is used for another recording format (video format). It can be recorded as a dummy file above.
[0060]
In this way, by inheriting the common file of the common contents in each recording format, even if the recording format changes, the necessary information previously recorded can be always inherited through the common file. Even if the recording format (eg, video format) is changed, the necessary information is recorded as a dummy file, so that when the original recording format (eg, VR format) is restored, the previous information can be inherited. In addition, loss of information can be prevented.
[0061]
【The invention's effect】
According to the present invention, it is possible to manage disc-specific information such as the number of times of recording independent of the recording format by creating a common file even if the recording format is different.
[0062]
Also, information (for example, Sparing Table or Non-Allocatable Space Stream in VR format; these information are used only in VR format) that are to be continuously managed on one recording format (for example, VR format) are also in the middle. Even if the recording format changes, it can be restored in the original format (for example, the VR format) without losing (when changing to the video format).
[Brief description of the drawings]
FIG. 1 is a diagram showing a directory structure in a VR format when a COMMON file is recorded.
FIG. 2 is a diagram showing a recording area on a disc when recording is performed in a VR format.
FIG. 3 is a diagram showing a volume structure and a file structure of a video format.
FIG. 4 is a diagram showing a directory structure of a video format.
FIG. 5 is a diagram showing a Volume Structure of a VR format.
FIG. 6 is a diagram showing a file structure in a VR format.
FIG. 7 is a diagram showing a directory structure in a VR format.
FIG. 8 is a diagram showing a file structure of a VR format when a COMMON file is recorded.
FIG. 9 is a diagram showing a recording area on a disc when recording in a video format.
FIG. 10 is a diagram showing a COMMON file.
FIG. 11 is a diagram showing Volume Structures and File Structure of a video format when a COMMON file is recorded.
FIG. 12 is a diagram showing a directory structure of a video format when a DUMMY file is recorded.
FIG. 13 is a diagram showing a file to be recorded in a data recording area.
FIG. 14 is a diagram showing a relationship between VR format volume information and file system information.
FIG. 15 is a diagram showing management information of a Sparing Table.
FIG. 16 is a diagram showing Volume Structure and File Structure of a video format when a DUMMY file is recorded.
FIG. 17 is a diagram showing a directory structure of a video format when a COMMON file is recorded.
[Explanation of symbols]
101 Volume information recording area
102 File system information recording area
103 VMGI file recording area
104 VOBS file recording area for menu
105 Backup VMGI recording area
106 Data recording area
107 Volume information recording area
108 File system information and manager file recording area
109 Data recording area
110 VTSI file
111 VOB file
112 Backup VTSI file

Claims (6)

In a file management method capable of recording a plurality of recording formats on a rewritable recording medium,
Provide a common file containing information that can be used when recording in each recording format,
When changing the recording format, the file management method inherits the common file from the recording format before the change. In a file management method capable of recording a plurality of recording formats on a rewritable recording medium,
When changing from one recording format to another recording format, and further returning to the one recording format,
When changing the necessary information of the one recording format to the other recording format, record as a dummy file,
When returning to the one recording format, the necessary information recorded as the dummy file in the other recording format is restored. In claim 1,
The file management method according to claim 1, wherein the common file functions as a dummy file common to a plurality of recording formats. In claim 1,
The file management method according to claim 1, wherein the common file manages the number of times management information is recorded in a recording area. In claim 2,
A file management method according to claim 1, wherein said dummy file includes a non-allocatable space stream representing a non-recordable area on a disk. A recording apparatus comprising the file management method according to any one of claims 1 to 5.

Images