JP5561950B2 - Recording apparatus, file management method, and program - Google Patents

Description

  The present invention relates to a recording apparatus, a file management method, and a program for recording an image file captured by an imaging apparatus such as a digital camera on a recording medium based on a file storage standard.

  In recent years, with the development of digital technology, digital cameras that process captured image information and video information electronically have been remarkably widespread. The digital camera converts a subject image formed by the subject luminous flux that has passed through the photographing lens to a solid-state imaging device such as a CCD into an electrical signal and outputs it as an image signal. Further, the image signal is subjected to various conversion processes in the image processing circuit, and finally stored as an image file in a recording medium such as a memory card.

  As a standard for managing image files on a recording medium, a DCF (JEIDA standard: Design Rule for Camera File System), which is a camera file system standard (file storage standard), is currently the mainstream. As standards for managing video files on a recording medium, standards such as SD-Video and AVCHD are widely known.

  The DCF standard will be described with reference to FIG. A directory (201) having a directory name “DCIM” directly under the root directory (200) is referred to as a DCF image root directory (hereinafter referred to as a DCIM directory).

  A plurality of DCF directories (202 to 204) for storing DCF objects (205 to 213) such as image files are created immediately under the DCIM directory (201). The DCF directory (202 to 204) is defined as follows according to the DCF standard. The directory name of the DCF directory (202 to 204) is defined to be composed of 8 characters, and the first to third characters must be half-width numbers (hereinafter referred to as directory numbers) from “100” to “999”. . The numbers “000” to “099” are not used. The fourth to eighth characters can be assigned free characters composed of single-byte uppercase alphanumeric characters and “_” (underscore).

  The names of DCF objects (205 to 213) (hereinafter referred to as DCF file names) are defined as follows. The DCF file name must be 8 characters, and the first to fourth characters must be free characters consisting of uppercase alphanumeric characters and “_” (underscore). The fifth to eighth characters must be “0001” to “9999” half-width numerals (hereinafter, file numbers).

  In normal shooting (single shooting, self-timer shooting), a maximum of 9999 DCF objects from “IMG — 0001.JPG” to “IMG — 9999.JPG” are created in the “900AAAA” (202) directory. Can do.

  According to the DCF standard, it is stipulated and recommended that recording be performed according to the following procedure according to the writer (recording apparatus) stipulation. The directory number is created when there is no DCF directory immediately under the DCIM directory in the DCF recording medium, and when a new DCF directory is created, the directory number to be created is free. In addition, when a DCF directory already exists immediately under the DCIM directory and a DCF directory is added, it is recommended by the DCF standard that the directory number is a sequential number starting from the maximum number +1 of the existing directory.

  On the other hand, the file number is created when the DCF file name does not exist in the file under the DCF directory to be recorded, and the initial value of the file number is free. Further, when a file having a DCF file name already exists under the DCF directory to be recorded, it is recommended in the DCF standard that the file number is the maximum number + 1.

  As described above, the DCF standard stipulates that a DCF directory with a directory number is created in a recording medium, and a DCF object with a file number is stored under the DCF directory.

  The following methods are known as a method for assigning directory numbers in a general digital camera at present. There is a specification for initializing a directory number by exchanging a recording medium for a digital camera. In addition, there is a specification in which a directory number of a recording medium before replacement is stored in a digital camera, and a directory number of a new recording medium attached to the digital camera is set after the stored continuous directory number.

  However, as described above, in the DCF standard, files and directories having a directory number of “999” and a file number of “9999” or more cannot be created. Therefore, a phenomenon occurs in which a new directory number or a new file number cannot be generated because the upper limit of the naming rule of the DCF standard has been reached despite the recording capacity that is less than the recordable capacity of the actual recording medium. Has become an issue.

  As a conventional technique for dealing with the above-described problems, when the directory number and the file number reach the upper limit, the recording medium is initialized (formatted) once to continue shooting, and the directory number and the file number are returned to the initial values. There is a technology that makes it possible to continue shooting.

  However, when initializing a recording medium, there is a problem that the information recorded on the recording medium must be copied to another recording medium before initialization. In addition, if there is no device or environment to copy to another recording medium, the user has to give up shooting or erase the information recorded on the storage medium without backing it up.

  As a technique for solving the above-described new problem, a recorded file structure is analyzed, a directory number and a file number that are not used are searched out, and a DCF object is used using the directory number and the file number that are not used. There is a way to record.

  However, a general digital camera has a specification of reproducing from a smaller directory number and file number. Therefore, there is a problem that the playback order of DCF objects recorded in unused directory numbers and file numbers is not guaranteed when played back by other DCF compatible playback devices.

  In order to solve such a problem, for example, there is a technique disclosed in Patent Document 1. The number of files that can be created on the recording medium is calculated based on the file storage standard, and the number of files that can be recorded on the recording medium is calculated based on the remaining capacity of the recording medium. Then, the number of both files is compared, and the smaller one is displayed as the number of shootable images, and a warning is given to that effect and a countermeasure is displayed. The coping method here is a method of reassigning directory numbers from the initial value in ascending order or a method of changing the directory name.

JP 2003-158645 A

  However, simply changing the directory number of each DCF directory has a problem that the use efficiency of the directory number and the file number is poor when the number of DCF objects under the DCF directory is small.

  The present invention has been made in view of such problems, and a state in which recording cannot be continued due to a file management standard limitation suddenly occurs despite the fact that the recording medium has free space. The purpose is to improve the efficiency of using directory numbers and file numbers.

The recording apparatus of the present invention includes a management unit that manages a file number of a file recorded in a recording medium and a directory number of a directory based on a file storage standard, a directory number determined by management of the management unit, and A recording means for recording a file on the recording medium using a file number, and a restructuring means for reconstructing a directory and file structure recorded on the recording medium, comprising a plurality of types of reconstruction methods Depending on whether the directory recorded on the recording medium is created by a user instruction or automatically created by control of a recording device, And reconstructing means for switching.

  According to the present invention, since the file structure can be reconstructed, it is possible to prevent a situation in which it is difficult to continue recording due to the inability to create a file even though there is free space on the recording medium. In addition, the recording medium can be returned to a state in which the recording medium can be used continuously even if the recording medium is in an incapable recording state. In addition, when the file structure is reconstructed, the use efficiency of the directory number and the file number can be improved.

It is a block diagram which shows the structure of the digital camera which concerns on embodiment. It is a figure which shows an example of the file structure based on DCF standard. It is a figure which shows an example of the file structure based on DCF standard. It is a figure which shows an example of the file structure based on the DCF standard after reconstructing. It is a figure which shows an example of a menu screen. It is a figure which shows an example of a folder creation screen. It is a figure which shows an example of a folder creation screen. It is a figure which shows an example of a folder creation screen. It is a figure which shows an example of a management file. It is a flowchart explaining the procedure until a file structure is reconstructed in 1st Embodiment. It is a flowchart explaining the procedure of reconstruction of a file structure. It is a flowchart explaining the procedure packed in a directory unit. It is a flowchart explaining the procedure packed in a file unit. It is a flowchart explaining the procedure which confirms whether it rebuilds. It is a flowchart explaining the procedure which confirms whether it is jammed in a directory unit. It is a figure which shows an example of the file structure based on DCF standard. It is a figure which shows an example of the file structure based on the DCF standard after reconstructing. It is a flowchart explaining the procedure until a file structure is reconstructed in 2nd Embodiment. It is a flowchart explaining the procedure of reconstruction of a file structure. It is a flowchart explaining the procedure packed in a directory unit. It is a flowchart explaining the procedure packed in a file unit. It is a flowchart explaining the procedure which confirms whether it rebuilds. It is a flowchart explaining the procedure which confirms whether it is jammed in a directory unit.

Preferred embodiments of the present invention will be described below with reference to the accompanying drawings.
(First embodiment)
FIG. 1 shows a system diagram for realizing the recording apparatus of the present invention. Here, a digital camera (hereinafter simply referred to as a camera) will be described as an example. The camera 100 according to the present embodiment includes a system controller 101 that controls the whole and blocks that process each function.

  When recording an image using the camera 100, first, external light that has passed through an imaging unit 102 (which is configured by an optical system and a motor for controlling the optical system, an imaging element, etc.) serving as imaging means An optical image is formed on the surface and converted into an electric signal by the image sensor. The electrical signal photoelectrically converted by the image sensor is converted into digital data by the image / sound processor 103.

  The directory / file management unit 104 functions as management means for managing the directory and file name of the recorded image file and managing the directory and file name of the already recorded image file. The digital data converted by the audio / video processing unit 103 is recorded on the storage medium 106 via the storage medium interface 105 in the storage destination directory and file name determined by the directory / file management unit 104. The storage medium 106 is a detachable storage medium attached to the camera 100, and its attachment state is detected by the storage medium detection unit 107. In addition, the digital data may be recorded on the built-in storage medium 108 of the camera 100.

  When data recorded on the storage medium 106 is reproduced, the data read from the storage medium 106 via the storage medium interface 105 is converted into data suitable for display by the image / audio processing unit 103 and then displayed on the display unit. 109.

  The user can operate the camera 100 through the user operation unit 111. Also, the audio output unit 110 can output a warning sound for notifying the user of the internal state of the camera 100 and a sound during video reproduction. At the same time, warnings and camera operating states can be displayed on the display unit 109. The charging control of the battery can be performed by the rechargeable battery interface 112.

  Next, the operation of the camera 100 according to the present embodiment will be described with reference to FIGS. FIG. 3 shows the file structure of a DCF (JEIDA standard: Design Rule for Camera File System) standard, which is a file storage standard created by a digital camera. The image number of the digital camera is managed by combining a 3-digit directory number and a 4-digit file number, such as 100-0001. There are generally two types of image number setting methods in a digital camera: “serial number” and “auto reset”. The “serial number” is a serial number of the last photographed image even if the memory card is replaced. This is effective when managing images collectively on a computer because the numbers do not overlap. On the other hand, “auto reset” is effective when the memory card is classified because the image number is reset to the initial value when the memory card is replaced.

  The process of constructing the file structure of FIG. 3 assuming that a new memory card is inserted in a digital camera in which the image number setting method of the digital camera is set to “serial number”. explain.

  First, when shooting is performed by operating the user operation unit 111, the captured image data is recorded with an image number and attached to a removable storage medium 106 (hereinafter referred to as a memory card). At this time, if the DCIM directory has not been created in the memory card 106, the “DCIM directory (301)” is created immediately below the root directory (300). If the image number recorded in the previous memory card 106 is 200-9999, the image number 200-9999 is assigned to the image captured this time. Therefore, if the directory with directory number 200 does not exist under the DCIM directory, “200AAAAA (302)” is created, and an image file “IMG — 9999.JPG (306)” with file number 9999 is created under this directory.

  Next, when the second operation is performed by operating the user operation unit 111, image numbers 201-0001 are assigned. Since the directory number is updated to 201 in this photographing, a new directory “201AAAAA (303)” with the directory number 201 is created. Then, an image file “IMG — 0001.JPG (307)” having a file number 0001 is created under the directory “201AAAAA (303)”.

  If normal shooting is continued in this way, the file number is incremented and saved, and when the file number reaches 9999, a new directory with the next directory number is created. Then, the file number is saved while being incremented again from the file number 0001.

  When a menu 500 as shown in FIG. 5 is opened by the operation from the user operation unit 111 and “Create Folder” is selected from the menu 500, a menu 600 as shown in FIG. 6A is displayed. When the item “new creation” is checked from the menu 600 in FIG. 6A (FIG. 6B), when shooting is performed, a new directory “202AAAA (304)” is created, and an image file “IMG — 0001. (308) "is created.

  In addition, when a condition is designated by “automatic creation / creation time” from the menu 600 of FIG. 6A (FIG. 6C), a new directory “203AAAAA (310)” is created when the conditions are matched. When shooting is performed thereafter, an image file “IMG — 0001.JPG (311)” is created under the same directory.

  “M0100.CTG (310)” under the MSC directory (306) is a management file for managing directories and files created under the DCIM directory. When the user creates a new directory by the above operation, the management file manages that the directory is intentionally created by the user. FIG. 7 shows an example of the management file. As shown in FIG. 7, the management file indicates whether the created directory name and the directory are created by the “folder creation” setting, or are created when the file number reaches the upper limit 9999. Consists of data. The management file is a text file, for example.

  In this way, the file structure of the DCF standard as shown in FIG. 3 is constructed. However, in the constructed file structure, the directory number is updated one after another even though there is a space in each directory, and a new directory is created.

  Here, the reconstruction of the file structure in the first embodiment will be described. FIG. 4 shows the reconstructed file structure. When reconstructing, it is examined how the directory directly under the DCIM directory is created, and the directory number and file number claw are changed depending on how the directory is created.

  First, “200AAAAAA (302)”, when examining the management file, it can be seen that there is no management data and it is not a directory created with the “create folder” setting. That is, the directory is not a directory created intentionally by the user for management, so the file under “200AAAAA (302)” is re-saved by assigning the smallest possible file number to the smallest numbered directory. Since “200AAAAA (302)” is the first directory to be reconstructed, it is changed to the minimum directory number 100 and becomes “100AAAAA (402)”. “IMG — 9999.JPG (306)” under “200AAAAAA (302)” is changed to “IMG — 0001.JPG (405)” by changing to the minimum file number 0001 under “100AAAAAA (402)”.

  Next, when the management file is examined, “201AAAAA (303)” has no management data like “200AAAAA (302)”, and it is found that the directory is not intentionally created especially for the user to manage. . Since “100AAAAAA (402)” is still empty, “file IMG — 0001.JPG (307)” under “201AAAAAA (303)” is stored as “IMG — 0002.JPG (406)” under “100AAAAAA (402)”. It will be done again. Then, “201AAAAA (303)” is deleted.

  Next, “202AAAAA (304)” is a directory created by the setting of “new creation” when the management file is examined. The directory created by the setting of “new creation” is intentionally created so that the user wants to manage the image file by category, and it is more convenient for the user to manage it separately from other directories. Therefore, there is a space under “100AAAAAA (402)”, but the file under “202AAAAAA (304)” is reconstructed as another directory. Since the next directory number is 101, the directory number of “202AAAAA (304)” is changed to 101 and becomes “101AAAAA (403)”. “IMG — 0001.JPG (308)” under “202AAAAA (304)” is stored as “IMG — 0001.JPG (407)” under “101AAAAAA (403)”.

  Next, “203AAAA (310)” is a directory created by setting the condition of “automatic creation / creation time” when the management file is examined. The directory created by the “automatic creation / creation time” condition setting is intentionally created so that the user wants to manage image files by category, and it is convenient for the user to manage them separately from other directories. There is sex. Therefore, there is a space under “101AAAAAA (403)”, but the file under “203AAAAAA (310)” is reconstructed as another directory. Since the next directory number is 102, the directory number of “203AAAAA (310)” is changed to 102 and becomes “102AAAAA (409)”. “IMG — 0001.JPG (311)” under “203AAAAAA (310)” is stored as “IMG — 0001.JPG (410)” under “102AAAAAA (409)”.

  As described above, the file configuration shown in FIG. 3 is reconstructed into the file configuration shown in FIG. That is, if the directory is intentionally created, the directory number is reassigned from the minimum value to a continuous number without changing the file structure under the directory (first reconstruction method). On the other hand, if the directories are not created intentionally, the image files that exist under each directory are integrated up to the maximum number of files that can be stored under the directory for multiple directories. While compressing the number of directories, the directory numbers are reassigned from the minimum value to consecutive numbers (second reconstruction method).

  Next, the procedure for reconstructing the file structure will be described with reference to the flowcharts of FIGS. The flowcharts of FIGS. 8 to 13 are performed by the system controller 101 operating based on a program for executing reconfiguration of a file configuration.

  First, the procedure until the file structure is reconstructed will be described with reference to the flowchart of FIG. In step S101, the file structure of the DCF standard is analyzed to check whether the directory number and the file number are free. If the directory number and the file number have a vacancy (Yes in step S102), the process proceeds to step S103. If there is no vacancy (No in step S102), the process ends. In step S103, the file structure of the DCF standard is reconstructed.

  The procedure for reconstructing the file structure (step S103 in FIG. 8) will be described with reference to the flowchart in FIG. In step S201, the number of directories under the DCIM directory is acquired and substituted for variable l. In step S202, initialization is performed by substituting 100 for the number of directories created in the reconstructed file structure, that is, the variable x for storing the directory number. In step S203, initialization is performed by substituting 1 for the number of files of the reconstructed file structure, that is, the variable y for storing the file number, in the same manner as in step S202. In step S204, initialization is performed by assigning 0 to a variable i for counting directories.

  In step S205, it is confirmed whether the directory number l is smaller than the count number i. If the count number i is smaller than the directory number l, the process proceeds to step S206. If the count number i is equal to or greater than the directory number l, the process ends.

  In step S206, it is confirmed whether or not the i-th directory has been intentionally created by the user according to the “create folder” setting (see FIG. 5). When the i-th directory is intentionally created (Yes in step S207), the process proceeds to step S208. In step S208, the file structure is reconstructed by filling the numbers in directory units. On the other hand, when the i-th directory is not intentionally created (No in step S207), the process proceeds to step S209. In step S209, the file structure is reconstructed by filling the numbers in units of files. Details of the process of counting numbers in units of directories in step S208 and the process of counting numbers in units of directories in step S209 will be described later.

  Next, in step S210, the count number i is incremented. Thereafter, the process returns to step S205, and if the count number i is smaller than the directory number l, the process proceeds to step S206 again, and if the count number i is equal to or greater than the directory number l, the process ends.

  The process of filling in directory units (step S208 in FIG. 9) will be described with reference to the flowchart in FIG. The variables i and x here are equivalent to the variables i and x used in the flowchart of FIG. In step S301, the i-th directory number is changed to the directory number x to be created next in the reconstructed file structure. In step S302, the variable x is incremented. In step S303, 1 is assigned to the file number y to be created next in the reconstructed file structure.

  The process of filling in units of files (step S209 in FIG. 9) will be described with reference to the flowchart in FIG. Here, the variable i and the variable y are equivalent to the variable i and the variable y used in the flowchart of FIG. In step S401, the number of files in the i-th directory is acquired and substituted for the variable m. In step S402, initialization is performed by substituting 0 for the count number j. In step S403, it is checked whether the count number j is smaller than the file number m. If the count number j is smaller than the file number m, the process proceeds to step S404. If the count number j is equal to or greater than the file number m, the process is terminated.

  In step S404, it is confirmed whether the file number y to be created next in the file structure after reconstruction is 9999 or less. If the file number y is 9999 or less, the process proceeds to step S407, and if the file number y is greater than 9999, the process proceeds to step S405. In step S405, the directory number x to be created next is incremented in the reconstructed file structure. In step S406, 1 is substituted for the file number y to be created next in the reconstructed file structure, and the process proceeds to step S407.

  In step S407, the j-th file number is changed to the file with file number y under the directory with directory number x in the reconstructed file structure. In step S408, the file number y to be created next is incremented with the reconstructed file configuration. In step S409, the count number j is incremented. Then, it returns to step S403 and it is confirmed whether the count number j is smaller than the file number m. If the count number j is smaller than the file number m, the process proceeds to step S404 again. If the count number j is greater than or equal to the file number m, the process is terminated.

  Here, when all the recorded directories are intentionally created by the user, the file structure cannot be reconstructed in units of directories. If the directory number and file number have reached the upper limit, it will be impossible to shoot any more, so the directory structure created intentionally by the user will be destroyed, but the file structure can be reconstructed on a file-by-file basis. Prompt to confirm whether or not to enter the state. As a result, when the user selects reconstruction in units of files, reconstruction is performed in units of files. The procedure will be described with reference to the flowchart of FIG. The flowchart of FIG. 12 is obtained by adding steps S501 to S507 to the flowchart of FIG. Here, the description of the processing described in the flowchart of FIG. 9 is omitted.

  In the flowchart of FIG. 12, after the initialization of the variables up to step S204 is completed, in step S501, it is confirmed whether or not the directory unit can be filled. Detailed processing for checking whether or not the directory can be jammed will be described later. If the directory unit can be jammed (Yes in step S502), the process proceeds to step S205. If the directory unit cannot be jammed (No in step S502), the process proceeds to step S503.

  In step S503, a confirmation screen is displayed on the display unit 109 to allow the user to confirm whether or not to squeeze the file unit. If the user selects “Patch by file” (Yes in step S504), the process proceeds to step S505, and if the user selects “Do not jam by file” (No in step S504), the process ends.

  In step S505, it is confirmed whether the count number i is smaller than the directory number l. If the count number i is smaller than the directory number l, the process proceeds to step S506, and if the count number i is equal to or greater than the directory number l, the process ends. In step S506, the file structure is reconstructed by packing files in units of files. In step S507, the count number i is incremented. Thereafter, the process returns to step S505 to check whether the count number i is smaller than the directory number l. If the count number i is smaller than the directory number l, the process proceeds to step S506 again. If the count number i is equal to or greater than the directory number l, the process is terminated.

  Processing for confirming whether or not a directory is jammed (step S501 in FIG. 12) will be described with reference to the flowchart in FIG. In step S601, the number of directories is acquired and substituted for variable l. In step S602, it is checked whether the number of directories l is 900. If the number of directories is 900, the process proceeds to step S603, and if the number of directories is smaller than 900, the process proceeds to step S616. In step S616, a message filled in directory units is returned and the process is terminated.

  On the other hand, in step S603, the count number j is initialized by substituting 0. In step S604, initialization is performed by substituting 0 into a temporary variable tmp that holds the number of files. In step S605, it is checked whether the count number j is smaller than the directory number l. If the count number j is smaller than the directory number l, the process proceeds to step S606. If the count number j is equal to or greater than the directory number l, the process proceeds to step S617. In step S617, a message that cannot be filled in directory units is returned, and the process ends.

  On the other hand, in step S606, it is confirmed whether or not the j-th directory is intentionally created by the user. If the j-th directory is an intentionally created directory (Yes in step S607), the process proceeds to step S608, and if it is not an intentionally created directory (No in step S607), the process proceeds to step S609. In step S608, 0 is substituted into a temporary variable tmp that holds the number of files.

  On the other hand, in step S609, the number of files in the j-th directory is acquired and substituted for the variable m. In step S610, it is confirmed whether tmp is zero. If tmp is 0, the process proceeds to step S611, and if tmp is not 0, the process proceeds to step S612. In step S611, the variable tmp is incremented.

  On the other hand, also in step S612, the variable tmp is incremented. In step S613, it is checked whether the variable tmp is 9999 or more. If tmp is larger than 9999, the process proceeds to step S614, and if tmp is 9999 or less, the process proceeds to step S616. In step S616, a message filled in directory units is returned and the process is terminated. On the other hand, in step S614, the value of tmp−9999 is substituted for the variable tmp.

  After steps S608, S611, and S614, the process proceeds to step S615. In step S615, the count number j is incremented. Thereafter, the process returns to step S605, and it is confirmed whether the count number j is smaller than the directory number l. If the count number j is smaller than the directory number l, the process proceeds to step S606 again. If the count number j is equal to or greater than the directory number l, the process proceeds to step S617. In step S617, a message that cannot be jammed in directory units is returned, and the process ends.

  The reconstruction of the file structure is assumed to be performed when the directory number and the file number reach the upper limit, and the recording is disabled during the shooting, but other timings may be used. For example, various timings can be considered, for example, when the directory number or the file number exceeds a certain value.

  As described above, since the file structure can be reconstructed, it is possible to prevent a situation in which recording cannot be continued due to the inability to create a file even if there is free space on the recording medium. In addition, the recording medium can be returned to a state in which the recording medium can be used continuously even if the recording medium is in an incapable recording state. In addition, when reconstructing the file structure, the directory information is examined, and the method for reconstructing the file structure is switched in accordance with a predetermined condition (whether the directory is intentionally created by the user). Therefore, the directory number and the file number can be used efficiently.

(Second Embodiment)
FIG. 14 is an example of a DCF directory and a DCF object configuration recorded in accordance with the DCF standard. Directly under the DCIM directory (1100) defined in the DCF standard are DCF directories (1101 to 1105), and under each DCF directory (1101 to 1105) are DCF objects (1106 to 1120). In FIG. 14, the directory number and the file number are not continuous, resulting in waste.

  Also, it is assumed that the recording date and time (1121 to 1134) of each file is the date and time as illustrated. In the DCF directory (1101), the DCF directory (1102), the DCF directory (1104), and the DCF directory (1105), the recording date and time of each DCF object extends over a plurality of dates. That is, it is understood that the DCF directory is not divided into folders by date. On the other hand, the DCF directory (1103) is composed of only the DCF objects (1112 to 1114) having the same recording date, and the user does not operate the free characters of the DCF directory, but it is possible to perform folder division by date. It shall have a sex.

  Therefore, in this embodiment, taking the file recording date as an example of the file attribute, all files under the same directory are renamed when the files have the same attribute, here the same date. If all files under the same directory do not have the same date, the directory name and file name are renamed. An example in which directory numbers and file numbers are efficiently used while maintaining the date-based folder division performed by the user in the directory and file configuration shown in FIG.

  FIG. 15 shows the reconstructed file structure. When reconstructing, the time stamp of the DCF object under the DCF directory is checked from the DCF directory with a small directory number. As a result, if all DCF objects under the same directory are not the same recording date, the directory number and the file number are packed in units of files. On the other hand, if all the DCF objects under the same DCF directory have the same recording date, there is a high possibility that the directory is a directory intentionally divided for each date and each event. Therefore, since it is more convenient for the user to manage the directory separately from other directories, the directory number is packed in directory units.

  14 and 15, the time stamps of the DCF objects (1106 to 1111) under “100AAAAA (1101)” and “200AAAAA (1102)” in FIG. 14 are not the same date. Accordingly, the directory numbers are collectively set to “100AAAAA (1201)”, and the file numbers of the files (1106-1111) in the respective directories are renumbered from 0001 (1204-1210).

  “300AAAAA (1103)” is the date with the same time stamp of the DCF object under the directory. Therefore, the directory number of “300AAAAA (1103)” is set to 101 by incrementing the number of the immediately preceding directory (1201), without distinguishing from other directories and collecting the files in other directories. .

  The DCF objects (1115 to 1117) under “400AAAAA (1104)” are not the same recording date. Therefore, the file numbers of the files in each directory are re-numbered from 0001 together in one directory (1203), similarly to “100AAAAAA (1101)” and “200AAAAAA directory (1102)”. Similarly, since the DCF objects (1118 to 1120) under “500AAAAA (1105)” are not the same time stamp, a process of adding a DCF object to the immediately preceding “102AAAAAA (1203)” is performed in the same manner as the above process. .

  Here, the file attribute is described by the recording date and time of the file. However, for example, it is possible to reconstruct the read-only flag as the file attribute.

  Next, the procedure for reconstructing the file structure will be described with reference to the flowcharts of FIGS. The flowcharts of FIGS. 16 to 21 are performed by the system controller 101 operating based on a program for executing reconstruction of a file configuration.

  First, the procedure until the file structure is reconstructed will be described with reference to the flowchart of FIG. In step S701, the file structure of the DCF standard is analyzed to check whether the directory number and the file number are free. If the directory number and the file number have a space (Yes in step S701), the process proceeds to step S703. If there is no space (No in step S701), the process ends. In step S703, the DCF standard file structure is reconstructed.

  The procedure for reconstructing the file structure (step S703 in FIG. 16) will be described with reference to the flowchart in FIG. In step S801, the number of directories under the DCIM directory is acquired and substituted for variable l. In step S802, initialization is performed by substituting 100 for the number of directories created in the reconstructed file structure, that is, the variable x for storing the directory number. Next, in step S803, initialization is performed by substituting 1 into a variable y for storing the number of files of the reconstructed file structure, that is, the file number, in the same manner as in step S802. In step S804, initialization is performed by assigning 0 to a variable i for counting directories.

  In step S805, it is confirmed whether the directory number l is smaller than the count number i. If the count number i is smaller than the directory number l, the process proceeds to step S806, and if the count number i is the directory number l or more, the process is terminated.

  In step S806, the file attribute (recording date) of the DCF object under the i-th directory is searched to check whether the file attributes are the same. If the file attributes of the DCF objects under the i-th directory are the same (Yes in step S807), the process proceeds to step S808. In step S808, the file structure is reconstructed by filling the numbers in directory units. On the other hand, if the file attributes of the DCF objects under the i-th directory are not the same (No in step S807), the process proceeds to step S809. In step S809, the file structure is reconstructed by filling the numbers in units of files. Details of the process of filling in directory units in step S808 and the process of filling in directory units in step S809 will be described later.

  In step S810, the count number i is incremented. Thereafter, the process returns to step S805. If the count number i is smaller than the directory number l, the process proceeds to step S806 again. If the count number i is equal to or greater than the directory number l, the process is terminated.

  The process of filling in directory units (step S808 in FIG. 17) will be described with reference to the flowchart in FIG. Here, the variable i and the variable x are equivalent to the variable i and the variable x used in the flowchart of FIG. In step S901, the i-th directory number is changed to the directory number x to be created next in the reconstructed file structure. In step S902, the variable x is incremented. In step S903, 1 is assigned to the file number y to be created next in the reconstructed file configuration.

  The process of filling in file units (step S809 in FIG. 17) will be described with reference to the flowchart in FIG. The variable i and the variable y here are equivalent to the variable i and the variable y used in the flowchart of FIG. In step S1001, the number of files in the i-th directory is acquired and substituted into a variable m. Next, in step S1002, initialization is performed by substituting 0 for the count number j. In step S1003, it is confirmed whether the count number j is smaller than the file number m. If the count number j is smaller than the file number m, the process proceeds to step S1004. If the count number j is the file number m or more, the process is terminated.

  In step S1004, it is confirmed whether the file number y to be created next in the file structure after reconstruction is 9999 or less. If the file number y is 9999 or less, the process proceeds to step S1007, and if the file number y is greater than 9999, the process proceeds to step S1005. In step S1005, the directory number x to be created next is incremented in the reconstructed file structure. In step S1006, 1 is assigned to the file number y to be created next in the reconstructed file configuration, and the flow advances to step S1007.

  In step S1007, the j-th file number is changed to the file with file number y under the directory with directory number x in the reconfigured file structure. In step S1008, the file number y to be created next is incremented in the reconstructed file configuration. In step S1009, the count number j is incremented. Thereafter, the process returns to step S1003 to check whether the count number j is smaller than the file number m. If the count number j is smaller than the file number m, the process proceeds to step S1004 again. If the count number j is greater than or equal to the file number m, the process is terminated.

  Here, when the time stamps of the DCF objects under all the recorded directories have the same recording date, the file structure cannot be reconstructed in directory units. If the directory number and file number have reached the upper limit, it will be impossible to shoot any more, so the directory structure divided by date for the user will be destroyed, but the file structure can be reconstructed on a file basis and shooting can be performed Prompt to confirm whether or not to enter the state. As a result, when the user selects reconstruction in units of files, reconstruction is performed in units of files. The procedure will be described with reference to the flowchart of FIG. The flowchart of FIG. 20 is obtained by adding the processing of steps S1101 to S1107 to the flowchart of FIG. Here, the description of the processing described in the flowchart of FIG. 17 is omitted.

  In the flowchart of FIG. 20, after the initialization of the variables up to step S804 is completed, it is confirmed in step S1101 whether or not the directory can be filled in units of directories. Detailed processing for checking whether or not the directory can be jammed will be described later. If the directory unit can be jammed (Yes in step S1102), the process proceeds to step S805. If the directory unit cannot be jammed (No in step S1102), the process proceeds to step S1103.

  In step S1103, a confirmation screen is displayed on the display unit 109 to allow the user to confirm whether or not to squeeze the file unit. If the user selects “Patch in units of files” (Yes in Step S1104), the process proceeds to Step S1105. If the user selects “Do not pack in units of files” (No in Step S1104), the process ends.

  In step S1105, it is confirmed whether the count number i is smaller than the directory number l. If the count number i is smaller than the directory number l, the process proceeds to step S1106. If the count number i is equal to or greater than the directory number l, the process ends. In step S1106, the file structure is reconstructed by packing files in units of files. In step S1107, the count number i is incremented. Thereafter, the process returns to step S1105 to check whether the count number i is smaller than the directory number l. If the count number i is smaller than the directory number l, the process proceeds to step S1106 again. If the count number i is equal to or greater than the directory number l, the process is terminated.

  Processing for confirming whether or not the directory is jammed (step S1101 in FIG. 20) will be described with reference to the flowchart in FIG. In step S1201, the number of directories is acquired and substituted for variable l. Next, in step S1202, it is confirmed whether the number of directories l is 900. If the number of directories is 900, the process proceeds to step S1203, and if the number of directories is smaller than 900, the process proceeds to step S1216. In step S1216, a message filled in directory units is returned and the process ends.

  On the other hand, in step S1203, initialization is performed by substituting 0 for the count number j. In step S1204, initialization is performed by substituting 0 into a temporary variable tmp that holds the number of files. In step S1205, it is confirmed whether the count number j is smaller than the directory number l. If the count number j is smaller than the directory number l, the process proceeds to step S1206. If the count number j is equal to or greater than the directory number l, the process proceeds to step S1217. In step S1217, a message that cannot be filled in directory units is returned, and the process ends.

  On the other hand, in step S1206, it is confirmed whether all DCF objects under the jth directory have the same recording date. If all the DCF objects under the j-th directory have the same recording date (Yes in step S1207), the process proceeds to step S1208. If all DCF objects under the j-th directory are not the same recording date (No in step S1207), the process proceeds to step S1209. In step S1208, 0 is substituted into a temporary variable tmp that holds the number of files.

  On the other hand, in step S1209, the number of files in the j-th directory is acquired and substituted for the variable m. In step S1210, it is confirmed whether tmp is zero. If tmp is 0, the process proceeds to step S1211, and if tmp is not 0, the process proceeds to step S1212. In step S1211, the variable tmp is incremented.

  On the other hand, in step S1212, the variable tmp is incremented. In step S1213, it is confirmed whether the variable tmp is 9999 or more. If tmp is larger than 9999, the process proceeds to step S1214, and if tmp is 9999 or less, the process proceeds to step S1216. In step S1216, a message filled in directory units is returned and the process ends. On the other hand, in step S1214, the value of tmp−9999 is substituted for the variable tmp.

  After steps S1208, S1211, and S1214, the process proceeds to step S1215. In step S1215, the count number j is incremented. Thereafter, the process returns to step S1205, and it is confirmed whether the count number j is smaller than the directory number l. If the count number j is smaller than the directory number l, the process proceeds to step S1206 again. If the count number j is equal to or greater than the directory number l, the process proceeds to step S1217. In step S1217, a message that cannot be filled in directory units is returned, and the process is terminated.

  The reconstruction of the file structure is assumed to be performed when the directory number and the file number reach the upper limit, and the recording is disabled during the shooting, but other timings may be used. For example, various timings can be considered, for example, when the directory number or the file number exceeds a certain value.

  As described above, since the file structure can be reconstructed, it is possible to prevent a situation in which recording cannot be continued due to the inability to create a file even if there is free space on the recording medium. In addition, the recording medium can be returned to a state in which the recording medium can be used continuously even if the recording medium is in an incapable recording state. In addition, when reconstructing the file structure, the directory information is examined, and the directory structure is reconstructed according to a predetermined condition (whether all files under the directory have the same file attribute). Since switching is performed, the use efficiency of the directory number and the file number can be improved.

  The object of the present invention can also be achieved by supplying a storage medium storing software program codes for realizing the functions of the above-described embodiments to a system or apparatus. In this case, the computer (or CPU or MPU) of the system or apparatus reads and executes the program code stored in the storage medium.

  In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiments, and the program code itself and the storage medium storing the program code constitute the present invention.

  As a storage medium for supplying the program code, for example, a flexible disk, a hard disk, an optical disk, a magneto-optical disk, a CD-ROM, a CD-R, a magnetic tape, a nonvolatile memory card, a ROM, or the like can be used.

  Further, the functions of the above-described embodiments are not limited to being realized by executing the program code read by the computer. For example, an OS (basic system or operating system) running on the computer performs part or all of the actual processing based on an instruction of the program code, and the functions of the above-described embodiments are realized by the processing. May be.

  Further, the program code read from the storage medium may be written in a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer. In this case, after being written in the memory, the CPU of the function expansion board or function expansion unit performs part or all of the actual processing based on the instruction of the program code, and the function of the above-described embodiment is performed by the processing. Is realized.

DESCRIPTION OF SYMBOLS 100: Digital camera, 101: System controller, 102: Imaging part, 103: Image audio processing part, 104: Directory / file management part, 105: Detachable storage medium interface, 106: Detachable storage medium, 107: Detachable storage medium Detection unit 108: Built-in storage medium 109: Display unit 110: Audio output unit 111: User operation unit 112: Rechargeable battery interface

Claims (8)

Management means for managing the file number of the file recorded in the recording medium and the directory number of the directory based on the file storage standard;
Recording means for recording a file on the recording medium using a directory number and a file number determined by management of the management means;
Reconstructing means for reconstructing the directory and file structure recorded on the recording medium, and having a plurality of types of reconstruction methods, wherein the directory recorded on the recording medium is a user's A recording apparatus comprising: a rebuilding unit that switches the rebuilding method depending on whether it is created by an instruction or automatically created by control of a recording apparatus.   As the reconstruction method, a first reconstruction method in which the directory number is reassigned without changing the number of files under each directory, and a second in which the image file existing under the plurality of directories is integrated and the directory number is reassigned. The recording apparatus according to claim 1, further comprising a reconstruction method.   3. The recording apparatus according to claim 2, wherein in the first reconstruction method and the second reconstruction method, the directory number is reassigned from a minimum value.   4. The recording apparatus according to claim 2, wherein when the directory is created by a user's instruction, the directory number is reassigned according to the first reconstruction method. It further has an imaging means,
5. The recording apparatus according to claim 1, wherein the file storage standard is a DCF (Design Rule for Camera File System) standard. 6.   The recording apparatus according to claim 1, wherein the rebuilding unit performs the rebuilding when the directory number or the file number reaches an upper limit of the file storage standard. . Managing the file number of the file recorded in the recording medium and the directory number of the directory based on the file storage standard;
Recording a file on the recording medium using a directory number and a file number determined by the management;
Reconstructing the directory and file structure recorded on the recording medium,
When reconstructing the directory and file structure recorded on the recording medium, the apparatus has a plurality of types of reconstruction methods, and the directory recorded on the recording medium is created according to a user instruction. A file management method, wherein the reconstruction method is switched according to whether the file is automatically created or is automatically created by control of a recording device. Management means for managing the file number of the file recorded in the recording medium and the directory number of the directory based on the file storage standard;
Recording means for recording a file on the recording medium using a directory number and a file number determined by management of the management means;
Reconstructing means for reconstructing the directory and file structure recorded on the recording medium, and having a plurality of types of reconstruction methods, wherein the directory recorded on the recording medium is a user's A program for causing a computer to function as reconstruction means for switching the reconstruction method depending on whether it is created by an instruction or automatically created by control of a recording apparatus.

Images