JP4144612B2 - Image data printing apparatus and image data printing method - Google Patents

Description

  The present invention relates to an image data printing apparatus and image data printing method for printing on an index card so that the contents of a plurality of image data recorded on a recording medium by an image filing system can be listed.

  2. Description of the Related Art Conventionally, an image filing system that captures image data from a scanner or the like, records the captured image data on a recording medium such as an optical disk, and filing the image data is known. This image filing system includes a memory that temporarily stores an image captured from a scanner, an image processing device that performs image processing such as enlargement, reduction, and rotation on image data recorded in the memory, and image processing A recording device for recording the recorded image data on the optical disc.

  By the way, since recent optical disks have a very large storage capacity, several hundred image data can be stored in one optical disk. Also, with this image filing system, it is possible to file thousands of image data by storing hundreds of image data not only on one disc but on each of a plurality of discs. Yes.

  However, if the number of discs on which image data is recorded increases, the user will not be able to tell what image data is recorded on which disc. When trying to find the image data desired by the operator from a large amount of image data recorded on a plurality of discs, the image data recorded on the disc is once mounted on the recording / reproducing apparatus. Must be read and checked on the monitor. Therefore, when such a process is performed on a plurality of disks, not only time but also a great deal of labor is required.

  The present invention has been made in view of such problems, and an image data printing apparatus and an image for making it possible to easily determine each image data stored on a disk by an image filing system. A data printing method is provided.

The image data printing apparatus according to the present invention is based on reading means for reading image data of a plurality of resolutions from a recording medium, management data indicating the relationship between the image data, and the image data read by the reading means. A list of image data by an image forming means for forming print image data, a print means for printing the print image data formed by the image forming means on an index card, and an index card on which the print image data is printed. And a control means for controlling the reading means, the image forming means and the printing means, the control means comprising a main directory and a plurality of image directories formed as sub-directories in the main directory. Has a hierarchical directory structure consisting of Management data composed of first management data formed in a bird and second management data formed in the plurality of image directories; and image data having a first resolution; Based on information included in the management data, the image data of the first resolution or the second resolution is recorded from a recording medium having image data having a second resolution lower than the first resolution. The reading unit is controlled to read image data, and the image forming unit is configured to form print image data from the read first resolution image data or the second resolution image data. controlled, Inte' in the first resolution or the second resolution by printing the print image data described above formed on index card And controlling the printing means to perform the splint.

The image data printing method according to the present invention includes a reading step of reading image data having a plurality of resolutions from a recording medium and information data indicating a relationship between the image data, and the image data read by the reading step. Based on the above, the step of forming the print image data, the print step of printing the print image data formed by the step of forming the print image data on the index card, and the index card on which the print image data is printed A reading step, a step of forming the print image data, and a control step of controlling the printing step so that image data can be listed, and in the control step, a main directory and a subdirectory in the main directory Hierarchical directory consisting of multiple image directories formed as The management data comprising first management data formed in the main directory and second management data formed in the plurality of image directories; From the recording medium having the image data having the resolution of 1 and the image data having the second resolution lower than the first resolution, based on the information included in the management data, the image data of the first resolution, Alternatively, the reading unit is controlled so as to read the image data having the second resolution, and print image data is formed from the read image data having the first resolution or the image data having the second resolution. , Intex in the first resolution or the second resolution by printing the print image data described above formed on index card And controlling to perform the lint.

  The present invention has a hierarchical directory structure composed of a main directory and a plurality of image directories formed as subdirectories in the main directory, and first management data formed in the main directory; Management data composed of second management data formed in the plurality of image directories, and image data having a first resolution and an image having a second resolution lower than the first resolution. Based on the information included in the management data, the reading means is controlled to read out the image data having the first resolution or the image data having the second resolution from the recording medium having data. The print image data is formed from the image data having the first resolution or the image data having the second resolution. By controlling so as to print onto the print image data formed index card, it is possible to create an index card desired by the user.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  First, the image data printing apparatus and the print image data generation apparatus according to the present invention are applied to a still image filing system as shown in FIG. 1, for example.

1. [Configuration of still image filing system]
The still image filing system includes a scanner unit 1 that reads an image from a film, a photograph, and the like, a printer unit 2 that prints a still image according to image data captured or recorded by the still image filing system, and the still image. The image processing block 3 forms high-resolution image data for printing, intermediate-resolution image data for monitor display, and low-resolution image data for index display from image data captured by the filing system. The image processing block 3 displays a video input unit 8 for capturing image data from other video equipment such as a video tape recorder device and a camera device, and a still image corresponding to the image data via the image processing block 3. The monitor devices 9 to be connected are respectively connected.

  Further, the still image filing system includes a thinning compression / decompression block 4 that performs thinning and compression / decompression processing on image data captured by the still image filing system, and image data of each resolution described above is recorded on the still image filing system. And a storage unit 5 that records and reproduces data on an optical disk, and a system controller 6 that controls the entire still image filing system. As will be described later, the system controller 6 is provided with a random access memory (RAM) 6a for temporarily storing image data read from the optical disk when the image data is rearranged in the order of reproduction and recorded on the optical disk. It has been. The system controller 6 is connected to an operation unit 10 for designating image data capture, recording, reproduction, printing, and the like.

  In the still image filing system, the scanner unit 1, printer unit 2, image processing block 3, thinning, compression / decompression processing block 4, storage unit 5 and system controller 6 are connected via a bus line 7, respectively. It is comprised by.

1-1 [Configuration of Scanner Unit]
As shown in FIG. 2, the scanner unit 1 includes a CCD image sensor 1a for reading a still image recorded on a negative film, a positive film, a photograph, and the like, and an image signal supplied as an analog signal from the CCD image sensor 1a. An A / D converter 1b that digitally converts to form image data, a correction unit 1c that performs correction processing such as shading correction and color masking correction on the image data from the A / D converter 1b, and the bus line 7 And an interface 1d connected to the.

1-2 [Configuration of Printer Unit]
As shown in FIG. 3, the printer unit 2 includes an interface 2a connected to the bus line 7, a data conversion circuit 2b for performing a data conversion process suitable for printing on supplied image data, and the data conversion circuit 2b. The thermal head 2c prints a still image corresponding to the image data on the printer paper 2d. The printing operation in the printer unit is controlled in accordance with print control data to be described later for controlling the number of prints, hue, and the like.

1-3 [Configuration of Image Processing Block]
As shown in FIG. 4, the image processing block 3 includes image data captured via the main memory 11a for temporarily storing image data captured by the still image filing system and the scanner unit 1 or the video input unit 8 or the like. A frame memory 11 comprising a video memory 11b, and an image processing circuit 12 for performing image processing such as enlargement processing and reduction processing on the image data stored in the main memory 11a. The memory controller 13 controls the frame memory 11, the image processing controller 14 controls image processing operations in the image processing circuit 12, and the interface 15 connected to the bus line 7.

  The frame memory 11 includes an R frame memory from which red (R) image data is read and written, a G frame memory from which green (G) image data is read and written, and a blue (B) image data from which B is read and written. It consists of a frame memory.

  Each of the color frame memories logically includes, for example, four DRAMs (Dynamic RAM) having a storage area of 1024 pixels × 1024 pixels × 4 bits in length × width × depth and a total of 4 Mbits in the depth direction. Stacked in stages, a total of 8 DRAMs are configured to have a storage area of 2048 × 2048 × 8 bits. The frame memory 11 is logically configured by stacking the frame memories for the respective colors having the storage area of 2048 × 2048 × 8 bits in the depth direction, for example, in the order of RGB. Therefore, the frame memory 11 has a storage area of 2048 × 2048 × 24 bits.

1-4 [Structure of decimation and compression / decompression processing block]
As shown in FIG. 5, the thinning / compression / decompression processing block 4 includes an interface 4a connected to the bus line 7, a buffer 4b for temporarily storing high-resolution image data supplied via the interface 4a, The 1/4 resolution circuit 4c that forms intermediate resolution image data by thinning the high resolution image data from the buffer 4b into 1/4, and the intermediate resolution image data from the 1/4 resolution circuit 4c are temporarily stored. And a buffer memory (buffer) 4d. Further, the 1/60 thinning circuit 4e for forming the low resolution image data by thinning the intermediate resolution image data read from the buffer 4d to 1/60, the high resolution image data from the buffer 4b, and the above And a selector 4f for selecting and outputting the intermediate resolution image data from the 1/4 thinning circuit 4c and the low resolution image data from the 1/60 thinning circuit 4e. The image data selected by the selector 4f is divided into blocks each having a predetermined pixel unit suitable for compression processing, and the image data block-formed by the raster-block conversion circuit 4g. It has a compression / decompression circuit 4h that performs fixed-length encoding processing, a decimation, a decimation in the compression / decompression processing block 4, a decimation / compression / decompression controller 4i for controlling the compression / decompression processing operation.

1-5 [Configuration of storage unit]
The storage unit 5 performs EFM modulation processing on the image data of each resolution from the interface 5a connected to the bus line 7 and the thinning / compression / decompression processing block 4 as shown in FIG. The circuit 5b includes a disk recording / reproducing unit 5c that records and reproduces image data from the EFM circuit 5b on the optical disc 20, and a storage unit controller 5d that controls the operation of the entire storage unit 5.

1-6 [Configuration of video input unit]
As shown in FIG. 7, the video input unit 8 includes an input terminal 8a for composite video signals, an input terminal 8b for video signals supplied in a Y (luminance) / C (chroma) separate format, and RGB Processing for converting the video signal input terminal 8c supplied in the format and the video signal in each format supplied via the input terminals 8a to 8c into an image size suitable for the still image filing system. And an A / D converter 8e for converting each video signal supplied as an analog signal from the video processing unit 8d into digital data to form each image data.

2. [Overview of recording operation]
Next, the first recording operation of the still image filing system having such a configuration will be described.

  First, when recording desired image data on the optical disk 20 of the storage unit 5, the user operates the operation unit 10 to specify the image data capture destination (scanner unit 1 or video input unit 8), and The output destination of the captured image data is set in the storage unit 5. As a result, the system controller 6 controls the scanner unit 1 or the video input unit 8 to an operating state.

2-1 [Explanation of operation of scanner unit]
The scanner unit 1 can read images of both a reflection original and a transmission original. Specifically, the scanner unit 1 can read, for example, an E size photo, an L size photo, and an A6 size photo as the reflective original, and a 35 mm, Broni size as the transparent original. The negative film can be read. The scanner unit 1 can also read a document on which the 35 mm, Broni-size negative film is printed as it is as the reflective document.

  When the film, photograph or the like is placed on the document reading table, the scanner unit 1 scans the document by scanning the CCD line sensor 1a shown in FIG. The CCD line sensor 1a forms an image signal corresponding to the read image and supplies it to the A / D converter 1b. The A / D converter 1b digitizes the image signal supplied from the CCD line sensor 1a to form image data and supplies it to the correction system 1c. For example, when the image is read from the 35 mm film, the correction system 1c corrects the image data to image data having a size of vertical × horizontal of 1200 pixels × 1700 pixels and outputs the image data.

  The scanner unit 1 also reads 1298 pixels × 975 to 1875 pixels, 1050 × 1450 pixels, and 1120 pixels × when the original to be read is a Brownie size film, an E size photo, an L size photo, or an A6 size photo, respectively. Image data having a size of 1575 pixels, 1325 pixels × 1825 pixels is corrected and output.

2-2 [Description of operation of video input unit]
As shown in FIG. 7, the video input unit 8 is supplied with, for example, a composite video signal from a video tape recorder, a video signal supplied in a Y (luminance) / C (chroma) separate format, and an RGB format. The video signals in three formats can be input, and these video signals are supplied to the video processing system 8d via the input terminals 8a to 8c, respectively.

  The video processing system 8d sets the pixels of the video signals of the respective formats to square lattice pixels and sets the image size to 480 pixels × 640 pixels, and supplies this to the A / D converter 8e. The A / D converter 8e digitizes the video signal to form image data corresponding to the video signal of each format and outputs it through the output terminal 8f.

2-3 [Description of Operation of Image Processing Block]
The image data formed by the scanner unit 1 or the video input unit 2 is, for example, high-resolution image data of 1024 pixels × 1536 pixels in length × width, and is input via the input terminal 18 of the image processing block 3 shown in FIG. To the video memory 11b in the frame memory 11.

  When the high-resolution image data is supplied to the video memory 11b, the memory controller 13 temporarily stores the video memory 11b, and writes and controls the video memory 11b so as to read out the stored high-resolution image data. To do. The high-resolution image data is thinned out via the data line 17, the interface 15, the bus line 7 and the data line 16 in this order, transferred to the compression / decompression processing block 4, and transferred to the main memory 11a. The memory controller 13 controls the writing to the main memory 11a so as to temporarily store the high resolution image data transferred to the main memory 11a.

  Next, when the high resolution image data is stored in the main memory 11a, the image processing controller 14 converts the high resolution image data into, for example, intermediate resolution image data for monitor display of 480 pixels × 640 pixels. The image processing circuit 12 and the memory controller 13 are controlled. As a result, the high resolution image data is read from the main memory 11 a by the read control of the memory controller 13 and supplied to the image processing circuit 12. Then, the high resolution image data is converted into intermediate resolution image data by the image processing circuit 12 and supplied to the video memory 11b via the data line 16, the interface 15, the bus line 7 and the data line 17 in this order. When the intermediate resolution image data is supplied to the video memory 11b, the memory controller 13 controls the writing to the video memory 11b so as to temporarily store the data, and reads and controls the video memory 11b so as to read the data. . Thus, the intermediate resolution image data stored in the video memory 11b is read out and supplied to the monitor device 9 shown in FIG.

  The intermediate resolution image data supplied to the monitor device 9 is converted into an analog signal by a D / A converter and used as an image signal for monitor display at an intermediate resolution. As a result, the image captured by the scanner unit 1 or the video input unit 8 is displayed on the monitor device 9.

  The image processing controller 14 shown in FIG. 4 designates image processing such as enlargement processing and reduction processing of an image captured by the scanner unit 1 or the video input unit 8 when the operation unit 10 is operated. If it is, the image processing circuit 12 is controlled so that the designated image processing is performed on the image data read from the main memory 11a. The image data subjected to the specified image processing by the image processing circuit 12 is supplied to the monitor device 9. As a result, the image subjected to the designated image processing is displayed on the monitor device 9. Further, the image processing controller 14 supplies data (image processing information) indicating image processing applied to the image data to the thinning / compression / decompression processing block 4 via the interface 15 and the bus line 7.

2-4 [Description of operation of decimation and compression / decompression processing block]
Next, the user confirms whether or not the image is desired by referring to the image displayed on the monitor device 9. If the image is desired, the user can operate the operation unit 10. The recording of the image displayed on the monitor device 9 is designated.

  The system controller 6 shown in FIG. 1 detects when recording is designated by the operation of the operation unit 10, and if there is data indicating that the recording is designated and the image processing information, this is detected. Is supplied to the compression / expansion controller 4i through the bus line 7 and the interface 4a shown in FIG.

  The thinning / compression / decompression controller 4i temporarily stores the image processing information, if any, and controls the interface 4a so as to fetch the high-resolution image data. When the high resolution image data is taken into the thinning / compression / decompression processing block via the interface 4a, it is temporarily stored in the buffer 4b. When the high resolution image data is stored in the buffer 4b, the thinning / compression / decompression controller 4i supplies the high resolution image data to the 1/4 thinning circuit 4c and the selector 4f for each line, for example. 4b is read and controlled.

  The ¼ decimation circuit 4c performs decimation processing such that the pixels of the high resolution image data are ¼, thereby forming 480 pixels × 640 pixels of intermediate resolution image data, which is stored in the memory 4d. Supply. When the intermediate resolution image data is supplied to the memory 4d, the thinning / compression / decompression controller 4i controls the memory 4d to temporarily store and read it. The intermediate resolution image data read from the memory 4d is supplied to the 1/60 decimation circuit 4e and the selector 4f.

  The 1/60 decimation circuit 4e performs a decimation process such that the pixels of the intermediate resolution image data read from the memory 4d are 1/60, thereby reducing the low resolution image data (index) of 60 pixels × 80 pixels. Image data) is formed and supplied to the selector 4f.

  The selector 4f is controlled to be switched by a thinning / compression / decompression controller 4i. That is, the thinning / compression / decompression controller 4i selects, for example, the image data of each resolution supplied to the selector 4f in the order of high resolution image data, intermediate resolution image data, and low resolution image data and outputs them. The selector 4f is switched and controlled. The image data of each resolution from the selector 4f is supplied to the raster-block conversion circuit 4g.

  The raster-block conversion circuit 4g divides each image data into processing units of compression coding, for example, processing blocks of 8 pixels × 8 pixels, and supplies this to the compression / expansion circuit 4h.

  Here, the image data of each resolution is divided into processing blocks of 8 pixels × 8 pixels in the raster-block conversion circuit 4g. The low resolution image data is an image of 60 pixels × 80 pixels. Size. For this reason, if this low resolution image data is divided into processing blocks of 8 pixels × 8 pixels, the vertical pixels cannot be divided by 8 pixels (60 pixels ÷ 8 pixels = 7.5 pixels). The low resolution image data cannot be divided in units of processing blocks of 8 pixels × 8 pixels. For this reason, when the low-resolution image data is supplied, the raster-block conversion circuit 4g adds the dummy data of 4 pixels × 80 pixels to the upper or lower stage of the image data, and thereby the 60-60 The low resolution image data of pixels × 80 pixels is set as low resolution image data of 64 pixels × 80 pixels. Then, since the vertical pixels are divisible by 8 pixels, the low resolution image data of 64 pixels × 80 pixels is divided into 8 processing blocks × 10 processing blocks and supplied to the compression / decompression circuit 4h. The dummy data is removed when the index is displayed, and an image related to the dummy data (for example, a black image or a white image) is not added to the index image and displayed.

  The compression / decompression circuit 4h includes a discrete cosine transform (DCT) circuit, a quantization circuit, and a fixed-length encoding circuit, and the image data of each resolution is first converted to the DCT circuit. To be supplied.

  The DCT circuit performs orthogonal transform processing for transforming the image data of each resolution onto the frequency axis to form DCT coefficients, and supplies the image data of each resolution subjected to the orthogonal transform processing to the quantization circuit. .

  The quantization circuit quantizes the image data of each resolution using an appropriate quantization coefficient set by the system controller 6, for example, and supplies these to the fixed-length encoding circuit.

  The fixed-length encoding circuit performs a fixed-length encoding process on the DCT coefficient of the image data of each resolution quantized with the appropriate quantization coefficient, and the result of the fixed-length encoding process is decimation and compression / decompression controller. Return to 4i. The thinning / compression / decompression controller 4i forms an optimum quantization coefficient for quantizing the image data in accordance with the result of the fixed-length encoding process, and supplies this to the quantization circuit. The quantization circuit quantizes the image data using the optimum quantization coefficient set for the second time, and supplies the quantized image data to the fixed-length encoding circuit. As a result, in the fixed-length encoding circuit, the image data of each resolution can be fixed to have a predetermined data length.

  Specifically, by such compression encoding processing, the intermediate resolution image data is fixed-length encoded to a data length of 2 clusters twice as large as 1 cluster which is one recording unit, and the high resolution image data Is fixed length encoded to a data length of 8 clusters, and the low resolution image data is fixed length encoded to a data length of 1/15 clusters. The resolution-encoded image data of each resolution is supplied to the storage unit 5 shown in FIG. 6 via the interface 4a and the bus line 7, respectively. Further, when the image processing information is added to the image data supplied as described above, the thinning / compression / decompression controller 4i supplies the image processing information to the storage unit 5 together with the image data of each resolution. To do.

2-5 [Description of operation of storage unit]
The image data and image processing information of each resolution from the thinning and compression / decompression processing block 4 are supplied to the interface 5a shown in FIG. When the storage unit controller 5d is supplied with the image data and the image processing information of each resolution to the interface 5a, the storage unit controller 5d controls the interface 5a so as to take them into the storage unit 5, respectively. The image data and the image processing information of each resolution taken into the storage unit 5 through the interface 5a are supplied to the EFM circuit 5b. When the image data and image processing information of each resolution is supplied to the EFM circuit 5b, the storage controller 5d converts the fixed-length encoded image data and image processing information into so-called EFM processing ( The EFM circuit 5b is controlled to perform (8-14 modulation processing). The EFM-processed image data and image processing information of each resolution are supplied to the disc recording / reproducing unit 5c. When the image data and image processing information of each resolution are supplied to the disk recording / reproducing unit 5c, the storage unit controller 5d records the image data and image processing information of each resolution on the optical disc 20 respectively. The recording / reproducing unit 5c is controlled. As a result, the image data of each resolution and the image processing information thereof are recorded on the optical disc 20.

  Specifically, the optical disk 20 is, for example, a magneto-optical disk having a diameter of 64 mm, and 200 pieces of image data can be rewritten any number of times for each resolution. The 200 pieces of image data are managed by being divided into a total of four image directories, for example, using 50 pieces of image data as one image directory. Therefore, when recording the image data, the user uses the operation unit 10 to select an image directory for recording the image data. As a result, the system controller 6 controls the disk recording / reproducing unit 5c via the storage unit controller 5d so as to record the image data of each resolution in the image directory selected by the user in order of capture.

  At this time, the low resolution image data is recorded as an index file for an index for displaying a plurality of images recorded in the image directory on one screen, and the intermediate resolution image data is recorded in the image directory. Recorded as an intermediate resolution image file for display on a monitor for displaying one desired image, and the high resolution image data is a high resolution image for printing for printing an image related to the high resolution image data. Each file is recorded.

3. [Description of optical disc format]
Next, the optical disc 20 on which the image data of each resolution is recorded in this way has a new image recording format described below.

3-1 [Cluster structure]
First, recording and reproduction are performed on the optical disk 20 with "cluster" as one unit. One cluster corresponds to, for example, two to three tracks, and one data track is formed by recording the clusters continuously in time. The one cluster includes a sub-data area of 4 sectors (1 sector is 2352 bytes) and a main data area of 32 sectors, and each address is recorded for each sector.

  In each sector, data is actually recorded in the area of 2048 bytes out of the above 2352 bytes. In the remaining bytes, header data, error correction code, and the like based on the synchronization pattern, address, etc. To be recorded.

  In the sub-data area of 4 sectors, when sub-data or subsequent data is recorded in another area, linking data indicating that the subsequent data is recorded in the other area is recorded.

  Further, TOC data, audio data, image data, etc. are recorded in the main data area of 32 sectors.

3-2 [Track structure]
Next, as shown in FIG. 8A, the entire area of the optical disc 20 is provided with a pit area in which data is recorded by embossed pits, and light on which data is recorded and reproduced by a magneto-optical method. It consists of a magnetic area (MO area).

  The pit area is a reproduction-only management area in which P-TOC (pre-mastered table of contents), which is management information recorded on the optical disc 20, is recorded, and a P-TOC sector to be described later is repeated. It is recorded.

  The MO area extends from immediately after the lead-in area on the innermost side of the disc to the end of the lead-out area on the outermost side of the disc. In this MO area, a recordable area is recorded from immediately after the lead-in area to immediately before the lead-out area on the outermost circumference side of the disc.

  The recordable area includes a recording / playback management area formed at the beginning of the recordable area, and a recordable user area formed immediately after the recording / playback management area and immediately before the lead-out area. Has been.

  In the recording / playback management area, a U-TOC, which is a TOC for recording / playback management, is recorded. Further, the area other than the U-TOC in the recording / reproduction management area is used as a calibration area for performing test writing in order to adjust the laser power of the optical pickup. The recording position of the U-TOC in the recording / playback management area is indicated by the P-TOC. The U-TOC is recorded continuously at a predetermined position in the recording / reproduction management area indicated by the P-TOC for three clusters.

  The recordable user area includes a data track in which image data of each resolution described above is recorded, and a free area that is managed as an area in which image data can be recorded (unrecorded area). It is comprised so that it may line up in order toward the outer peripheral side.

  In the data track, for example, a data file having image data indicated as “f1”, “f2”... “F5” in FIG. 8A and “data U-TOC” for managing each data file are provided. To be recorded.

The data U-TOC may be recorded at any position within the recordable area. However, in the still image filing system, the innermost disc side of the data file of the image data. Is recorded immediately before the data file f1, which is a data file.
As shown in FIG. 8B, the P-TOC recorded in the reproduction-only management area is a recording / reproduction management area in which the data U-TOC is recorded and a data track in which the image data of each resolution is recorded. Manage the whole.

  The data U-TOC manages the data files f1, f2,... F5 in the data track and free area unrecorded blocks in the data track in cluster units as shown in FIG. To do.

3-3 [Configuration of data track]
Next, the structure of the data track in which the data files FL1, FL2, FL3 having the image data and the data U-TOC are recorded will be described with reference to FIG. As described above, this data track is managed as a part (a track portion on which a series of physically continuous data on the disk is recorded) in the U-TOC, and each data file recorded in the data track. Are managed by data U-TOC recorded in the data track.

  The data U-TOC is recorded at the physical head position of the data track as shown in FIG. That is, the data U-TOC is recorded at a position closest to the inner circumference side of the disk in the data track. When the data track is divided into a plurality of parts, the data U-TOC is recorded at the head of the part located on the innermost side of the disc.

  As shown in FIG. 9B, this data U-TOC is composed of a boot area of 1 cluster and a volume management area of 16 clusters. An area following the data U-TOC is a file extents area. In the file extents area, data files FL1 to FL3 including image data are recorded as shown in FIG. 9A. Further, a data file can be further recorded in the unrecorded block “EB”.

  The volume management area is composed of a total of 512 management blocks from 0 to 511 as shown in FIG. The data area in one management block is 2048 bytes, and each data recorded in this management block is management information for recording / reproducing the data file.

  That is, each of the 512 management blocks is assigned a block number of 0 to 511, and the management block of block number 0 is used as the “volume descriptor VD”. In this case, the “volume” is a unit including all the parts in which general data including image data is recorded. The management block of block number 1 is used as “volume space bitmap VSB”, and the management blocks of block number 2 and block number 3 are used as “management table MT”. The management blocks after the block number 4 are used as “directory record block DRB” and “extension record block ERB” according to the usage form of the file extents area.

  Each management block in this management area is based on the size of one logical block (the area where data is actually recorded in one sector, which is 2048 bytes. For example, 32 sectors are 32 logical blocks). It has become. When data is recorded / reproduced in this management area, this logical block (management block) is a minimum unit for recording / reproduction and a management unit in the management area.

  On the other hand, when recording image data in the file extents area, an allocation block of one logical cluster size is set as a minimum unit for recording and reproduction, and is a management unit in the file extents area.

  Note that the “logical block” has 32 sectors in units actually used as a data recording area in one cluster, and is the same area as the main data area. The “allocation block” indicates the same data unit as the logical cluster. In this example, one logical class size is expressed as one allocation block. Therefore, the number of clusters on the disk matches the number of allocation blocks. All the file positions on the disk are designated by the allocation block number of the allocation block.

3-4 [Volume Descriptor]
The first management block in the volume management area is used as a volume descriptor VD. This volume descriptor VD performs basic management of data tracks (volumes) on the disk. As shown in FIG. 10, a header in which a synchronization pattern and an address are recorded, and various management information is recorded in 2048. It consists of a data area for bytes.

In the second to sixth bytes in the data area of the volume descriptor VD, “PIC” is used as identification information (ID) indicating that the sector is a sector of the volume descriptor. Character data of “MD” is recorded, for example, in ASCII code. Subsequent to this identification information, the version ID, logical block size, logical cluster size, and allocation block size of the system are recorded.

  Specifically, as the “logical block size”, a byte length indicating an actual data area in the sector of the data track is recorded. The sector of the data track is 2352 bytes, of which 2048 bytes are allocated as the data area. Therefore, “2048”, which is the byte length of the logical block, is recorded as the logical block size. The logical block is a minimum recording unit for recording / reproducing in the management area.

  Next, as the “logical cluster size”, the number of logical blocks of the logical cluster, which is a cluster in which management information and data are actually recorded, is recorded. One cluster includes 36 sectors, and 32 sectors (32 logical blocks) are allocated for data recording. Therefore, “32”, which is the block length of the logical cluster, is recorded as the logical cluster size.

  Next, as the “allocation block size”, the number of logical blocks in the allocation block is recorded. The allocation block indicates the same data unit as the logical cluster, and is a part where management information and data files are actually recorded in the data track. For example, an area of 32 sectors as a logical cluster in the volume management area and file extents area shown in FIG. 9B corresponds to one allocation block. This allocation block is the minimum unit for recording and reproduction in the file extents area.

  Next, following the allocation block size, “total number of allocation blocks” indicating the total number of allocation blocks in the volume is recorded. When the optical disc 20 is a so-called hybrid disc in which audio data and image data are mixed, the total number of allocation blocks including the number of allocation blocks in the pit area is recorded as the total number of allocation blocks.

  Next, “allocation block count” is recorded following the total allocation block count. The number of allocation blocks indicates the total number of recordable allocation blocks, and the number of allocation blocks in the recordable area is recorded. When the optical disc 20 is a premastered disc, “0” is recorded as the number of allocation blocks.

  Next, the “number of unrecorded allocation blocks” is recorded following the number of allocation blocks. The number of unrecorded allocation blocks indicates the number of allocation blocks that are not yet recorded among the recordable allocation blocks in the volume.

  Next, the “number of recorded allocation blocks” is recorded following the number of unrecorded allocation blocks. The number of recorded allocation blocks indicates the number of allocation blocks that have already been recorded among the recordable allocation blocks in the volume.

  Next, the “number of defect allocation blocks” is recorded following the number of recorded allocation blocks. The number of defect allocation blocks indicates the number of allocation blocks having defects due to scratches or the like on the disk.

  Next, following the number of defect allocation blocks, a “number of directories” indicating the number of directories in the volume and a “data file” indicating the number of data files in the volume are recorded.

  Next, “ID maximum value” is recorded following the number of directories and the data file. This ID maximum value indicates the maximum value of the ID number assigned in the order in which the directory or data file is formed.

  Next, “volume attribute” is recorded following the ID maximum value. This volume attribute indicates the attribute of data recorded in the volume management area. For example, whether the volume management area is recorded in the mirror mode, whether it is an invisible file (secret file), write Volume attribute data indicating whether protection (writing prevention) is applied, whether backup is necessary, and the like are recorded.

  Next, “volume management area length” is recorded following the volume attribute. The volume management area length indicates the length of the volume management area, and the byte length of the volume management area is recorded.

  Next, the “volume management area position” is recorded following the volume management area length. The volume management area position indicates the position of the volume management area on the disc, and the first allocation block number of the volume management area is recorded.

  Next, following the volume management area position, another management block formed by using the management block in the volume management area is recorded. Specifically, as other management blocks, “volume space bitmap position” indicating the position of the first allocation block of the volume space bitmap VSB, and “volume space” indicating the number of allocation blocks of the volume space bitmap VSB. The number of bitmaps, the “first management table position” indicating the position of the first allocation block in the management table MT, and the “number of management tables” indicating the number of allocation blocks in the management table MT are recorded. In addition, “first extent record block position” indicating the position of the first allocation block of the extent record block ERB, “extent record block number” indicating the number of allocation blocks of the extent record block ERB, and the first of the directory record block DRB The “first directory record block position” indicating the position of the allocation block and the “number of directory record blocks” indicating the number of allocation blocks of the directory record block DRB are recorded.

  As a result, the position of the first directory can be searched by detecting the block number of the allocation block recorded as the “first directory record block”.

  Next, following each management block, a “root directory length” indicating the byte length of the directory and a “root directory number” indicating the number of subdirectories in the directory are recorded, respectively, followed by various IDs and A character set code or the like is recorded. As the various IDs and character set codes, for example, a boot system ID, a volume ID, a publisher ID, a data prepare ID, an application ID, and a character set code of each ID are recorded. In addition to these, the volume formation date / time, volume update date / time, expiration date / time, valid date / time, and the like are recorded.

  Next, the 2048-byte data area is followed by a 4-byte EDC area and a 276-byte ECC area. In the ECC area, a 172-byte P parity and a 104-byte Q parity based on a so-called cross-interleave method are recorded, respectively.

  The data area has a 2048-byte area, and the 1024 to 2047-byte area of the 2048-byte data area is used as a system extension area (system extension area) for system expansion. Yes.

3-5 [Volume Space Bitmap]
Next, the management block of the block number 1 in the volume management area is used as a volume space bitmap VSB. This volume space bitmap VSB shows the recording status of the file extent area in units of all allocation blocks of the data track.

  As shown in FIG. 11, the volume space bitmap VSB has a total of 276 bytes including a header in which a synchronization pattern (Sync) and an address are recorded, a 2048-byte data area, 172 bytes of P parity and 104 bytes of Q parity. ECC area consisting of

  In the data area, the allocation block and the type of each allocation block are recorded.

  Specifically, as shown in FIG. 12 (a), each allocation block of the data track has an allocation block number (AL0, AL1, AL2...) In the order of number 0, number 1, number 2. And the seventh and sixth bits of the 0th byte, which is the first byte of the data area of the volume space bitmap VSB, are allocated to the allocation block AL0 of number 0. In addition, the fifth and fourth bits of the 0th byte are assigned to the allocation block AL1 of number 1, the third and second bits are assigned to the allocation block AL2 of number 2, and the first and 0th bits. Is allocated to the allocation block AL3 of the number 3, and the 7th and 6th bits of the first byte are allocated to the allocation block AL4 of the number 4, and 2 bits are allocated to each allocation block. Yes.

  The 2-bit information assigned to each allocation block indicates the type of each allocation block. As shown in FIG. 12B, when the allocation block is an unrecorded allocation block, “00”. However, “01” is recorded for a recorded allocation block, “10” is recorded for a defect (defective) allocation block, and “11” is recorded for an undefined allocation block.

  In the remaining area of the data area, that is, the area where the corresponding allocation block does not exist, “11” is recorded in the bit.

  The optical disk 20 has a data area for 2200 clusters, and information can be recorded in allocation blocks AL0 to AL8191. Actually, allocation to AL0 to AL2199 is included. Information is recorded using blocks.

3-6 [Management table]
Management blocks of block number 2 and block number 3 in the volume management area are used as a management table MT.

  This management table MT shows the usage form of each management block in the volume management area. As shown in FIG. 13, a header in which a synchronization pattern and an address are written, a 2048-byte data area, and a 4-byte EDC. The area is composed of an area and a 276-byte ECC area.

  In the 2048-byte data area, management block 0 to 511 entries each having 4 bytes allocated are recorded. This indicates the usage contents of 512 management blocks in the volume management area. It has come to be.

  The data contents of the management block of each entry (0 entry to 511 entry) having 4 bytes are as shown in FIG.

  First, the first management block (management block 0 entry) is used as a volume descriptor as shown in FIG. 14A, and the 0th to 2nd bytes are reserved. For example, “80h” is recorded in the third byte as an entry type for indicating that the management block 0 entry is a volume descriptor.

  Next, the second management block (management block 1 entry) is used as a volume space bitmap as shown in FIG. 14 (b), and unrecorded allocation from the 0th byte to the 1st byte. The number of blocks is recorded, and the second byte is reserved. For example, “90h” is recorded in the third byte as an entry type for indicating that the management block 1 entry is a volume space bitmap.

  Next, as shown in FIG. 14C, the management block used as the management table records the next management table position from the 0th byte to the first byte, and records the number of unused management blocks in the second byte. Is done. For example, “A0h” is recorded in the third byte as an entry type for indicating that the management block is a management table.

  Next, in the management block used as the extent record block, as shown in FIG. 14D, the next extent record block position is recorded from the 0th byte to the 1st byte, and the number of unused extent record blocks is recorded in the second byte. Is recorded. For example, “B0h” is recorded in the third byte as an entry type for indicating that the management block is an extent record block.

  Next, as the above-mentioned directory record block, a “single directory record block” completed by a directory record unit recorded using one management block and used alone, and a directory record unit constituting one directory are divided into a plurality of directory record units. There is a “multiple directory record block” used by dividing and recording into a plurality of directory record blocks which are management blocks.

  When the management block is used as a single directory record block, a directory ID is recorded in the management block from the 0th bit to the 29th bit as shown in FIG. For example, “00h” is recorded in the last 2 bits (from the 30th bit to the 31st bit) as an entry type for indicating that the management block is a single directory record block. .

  In the case of a plurality of directory record blocks, information as shown in FIG. 14 (f) to FIG. 14 (h) is recorded in each management block.

  That is, if the management block is the “first directory record block (first directory record block)” of a plurality of directory record blocks, the next directory from the 0th byte to the 1st byte as shown in FIG. The record block position is recorded, and the upper byte of the directory ID is recorded in the second byte. In addition, “D0h” is recorded in the third byte as an entry type for indicating that the management block is the first directory record block.

  If the management block is the “last directory record block” of a plurality of directory record blocks, the lower byte of the directory ID is recorded from the 0th byte to the 2nd byte as shown in FIG. Further, “F0h” is recorded in the third byte as an entry type for indicating that the management block is the last directory record block.

  Further, when the management block is an intermediate directory record block of a plurality of directory record blocks (in the case of the above-described first directory record block or a directory record block other than the last directory record block), FIG. As shown, the next directory record block position is recorded from the 0th byte to the 1st byte, and the second byte is reserved. In addition, “E0h” is recorded in the third byte as an entry type for indicating that the management block is an intermediate directory record block.

3-7 [Directory record block]
Management blocks after block number 3 in the volume management area are used as “directory record blocks DRB”. In this directory record block DRB, one or a plurality of directory record units are recorded.

  As the directory record unit, there are a “directory directory record unit” for configuring a directory, and a “file directory record unit” for specifying the location of a data file, and this directory record block. In the directory, file directory record units and directory directory record units are mixedly recorded according to files and subdirectories formed in the directory.

  As shown in FIG. 15, a directory record block DRB in which a directory record unit for a directory constituting a directory is recorded includes a header in which a synchronization pattern and an address are recorded, a 2048-byte data area, a 4-byte EDC area, It consists of a 276-byte ECC area.

  First, a directory record length indicating the byte length of the directory record unit is recorded in one directory record unit. The data length of one directory record unit is variable.

  Next, the directory attribute is recorded following the directory record length. Specifically, as the attribute of the directory, whether the directory record unit is a directory record unit for a directory, whether the directory including the directory record unit is an invisible directory, or a system directory Information indicating various attributes such as whether or not is recorded. This indicates whether or not the position of the data file is indicated by using an extent record block described later.

  Next, following the directory attribute, a character set code (CSC) indicating a character type of the short name ID and a short name ID are recorded. The short name ID is recorded with an 11-byte ASCII code, and a directory name of up to 11 characters can be recorded.

  Next, the directory formation date and time and the directory update date and time are recorded following the short name ID, and the update date and time of this directory record unit is recorded as the status update date and time. Further, the directory ID number and the directory length are recorded, followed by “index to DRB” and “number of DRB”.

  The index to DRB indicates the position in the volume management area in the first directory record block DRB in which the contents of the designated subdirectory are recorded. For this reason, as the index-to-DRB, any corresponding value of management numbers 0 to 511 is recorded.

  As the number of DRB, the number of directory record blocks for indicating the designated directory is recorded as the number of management blocks.

  Next, following this number of DRB, a “long name ID” is recorded. The long name ID has a variable length and the data length is recorded. In some cases, the long name ID is not recorded. In this case, “00h” is recorded as the long name ID. When the long name ID is an even number of bytes, “00h” is recorded as padding to fill the remaining bytes. The byte following the long name ID is used as a system extension area.

  The directory record unit corresponding to the directory has such a configuration, and a plurality of directory record units are provided in a 2048-byte data area.

  Next, as shown in FIG. 16, a directory record block DRB in which a directory record unit for a file corresponding to a data file is recorded includes a header including a synchronization pattern and an address, a 2048-byte data area, and a 4-byte EDC. The area is composed of an area and a 276-byte ECC area.

  In the 2048-byte data area, one or a plurality of directory record units each corresponding to a data file can be recorded.

  As with the directory record unit shown in FIG. 15, the directory record length is recorded first in one directory record unit, and then the attribute is recorded. This attribute specifies that this directory record unit does not correspond to a directory, and whether the corresponding data file is an invisible file or a system file, and its data file position is specified by the extent record unit. Various attributes such as whether it is a thing are displayed.

  Next, the character set code (CSC), the short name ID for recording the file name, the directory formation date / time, the directory update date / time, and the status update date / time are recorded in the same manner as the directory record unit shown in FIG. The As the short name ID, a data file name is recorded with an ASCII code of 11 characters or less.

  Next, following the short name ID, a data file ID number, a data file length, an extent start location, a number of block, and an associate data length are recorded.

  The extent start location indicates the position of the file recorded in the file extent area by the allocation block number, and the number of block is used from the start position specified by the extent start location. It shows the number of allocation blocks.

  Next, “index to ERB” and “number of ERB” are recorded following the associate data length.

  The index-to-ERB indicates the position in the volume management area of the extent record block including data for indicating each distributed position of the distributedly recorded data file. The block number is recorded.

  The number of ERBs indicates the number of extent record blocks for indicating the distributed and recorded data file, and is recorded by the number of management blocks.

  Next, following the number of ERB, a long name ID having a variable length is recorded with the data length. When this long name ID is not recorded, “00h” is recorded as the long name ID, and when the long name ID becomes an even number of bytes, “00h” is recorded as padding to fill the remaining bytes.

  The byte following the long name ID is used as a system extension area.

  The directory record unit corresponding to the data file is configured as described above, and a plurality of directory record units can be provided in a 2048-byte data area.

  Next, in order to record a data file such as an image file on the disk, there are the following two cases, and the data file position designation method differs depending on the case.

  First, in the first case, a continuous free area for the data of the image file to be recorded can be secured on the disc. In this case, an image file is recorded as one file in a physically continuous area. Specifically, in this case, one image file is recorded so as to be composed of continuous allocation blocks. Normally, the position of the data file is indicated by the allocation block number recorded in the physically continuous area and recorded as the extent start location in the directory record unit for the file.

  Next, the second case is a case where a continuous free area for the data of the image file to be recorded cannot be secured on the disc. In this case, one image file is divided and recorded in a dispersed area on the disc. Specifically, one image file is recorded so as to be composed of a plurality of separated allocation blocks. In this case, the position in the management area of an extent record block, which will be described later, is specified by the management block number recorded as index to ERB included in the directory record unit for the file. Based on the included data, the position of each distributed area is designated.

In the first case, the data of the index ERB is not recorded, and in the second case, the extent start location is not recorded.
3-8 [Extent record block]
Management blocks after block number 4 in the volume management area are used as extent record blocks ERB. The extent record block ERB is used when one image file is recorded in a distributed area designated by a remote allocation block as in the second case described above. In the extent record block ERB, data for indicating the allocation block position of each distributed area is recorded.

  A maximum of 64 extent record units (ER units) can be recorded in this extent record block ERB.

  The ER unit is composed of a 32-byte index ER unit and a 32-byte descriptor ER unit.

  The index ER unit is recorded as the earliest unit of the plurality of ER units in the extent record block ERB, thereby managing the usage status of the second and subsequent ER units. The second and subsequent ER units are used as descriptor ER units, and the recording position of each distributed area is indicated by the allocation block number by the data included in this unit.

  That is, as shown in FIG. 17, the extent record block ERB includes a header in which a synchronization pattern and an address are recorded, a 2048-byte data area, a 4-byte EDC area, and a 276-byte ECC area. Yes.

  In the 2048-byte data area, 64 extent record units can be recorded. One extent record unit consists of 32 bytes.

  FIG. 17 shows an example in which the first 32-byte extent record unit in the data area is used as an index extent record unit.

  In this index extent record unit, an index ID is recorded first. In this case, “FFFF” indicating that the extent record unit is used as an index extent record unit is recorded as the index ID.

  Next, the maximum depth is recorded following the index ID. The extent record tree structure is formed by the index extent record unit, and the maximum depth indicates the subtree hierarchy specified by the extent record unit. For example, when an extent record unit including an extent descriptor is designated by the index extent record unit (in the lowest layer), “0000h” is recorded as the maximum depth. After that, up to seven logical offsets and ER indexes can be recorded.

  The ER index indicates which ER unit is data indicating a distributed area among 64 ER units recorded in the extent record block. In this ER index, any corresponding ER unit number from 0 to 63 is recorded. In the logical offset, data indicating the ER unit indicated by the ER index is the ER unit for constituting the data file is recorded.

  Next, in the example shown in FIG. 17, the second and subsequent ER units are used as descriptor ER units.

  In the descriptor ER unit, a maximum of 8 extent start locations and the number of allocation blocks are recorded.

  As the extent start location, an allocation block number indicating the recording position of one distributed area is recorded. As the number of allocation blocks, data indicating the number of allocation blocks constituting the distributed area is recorded. For this reason, one distributed area is designated by one extent start location and one allocation block number. Accordingly, since eight extent start locations and the number of allocation blocks can be recorded in one descriptor DR unit, a maximum of eight distributed areas can be designated by one descriptor DR unit.

  When specifying 8 or more distributed areas, the third ER unit is newly used as the descriptor ER unit, and the index ER unit is used for the descriptor recorded in the second ER unit. The descriptor ER unit following the ER unit may be linked to the descriptor ER unit newly recorded in the third ER unit.

  Next, a case where the positions of image files recorded in a plurality of distributed areas are designated by the extent record block ERB will be described.

  First, the position in the management block area of the extent record block ERB is specified by the index to ERB recorded in the file DR unit in the directory record block DRB. Then, “FFFF” data indicating that the extent record unit is used as an index extent record unit is recorded at the head of the first ER unit of the ERB. Therefore, by reproducing this, it can be determined that the first ER unit is the index ER unit.

  Next, in order to search for the first ER unit constituting the data file, the data of the logical offset of “0000” is searched, and the data of the ER index corresponding to the data of the logical offset of “0000” is searched. As described above, the eight distributed areas are respectively designated by the eight extent start locations and the number of allocation blocks recorded in the descriptor ER unit indicated by the data of this ER index. Therefore, the position of each image file distributed on the disc can be detected by the data in the management area. Therefore, it is not necessary to search the disk when reading the image file, and high speed reproduction can be realized.

4). [Description of file and file hierarchy]
Files used in the still image filing system include a management file, an image file, an index image file, and the like.

The extension of the file name of the management file is “PMF”, and by detecting the extension of “PMF”, the file is identified as a management file. The management file includes the general information management file (OVF). INF. PMF), image data management file (PIC) INF. PMF), print data management file (PRT) INF. PMF), playback control management file (PMS) INF. PMF).

  The extension of the file name of each image file is “PMP”. By detecting the extension of “PMP”, it is identified that the file is an image file. The image file includes a high resolution image file that records high resolution image data HD and an intermediate resolution image file that records intermediate resolution image data SD.

  As shown in FIG. 18A, the high-resolution image file is a “PHPnnnn.PMP file” having an aspect ratio of 3: 2 and image data of 1536 pixels × 1024 pixels, and an aspect ratio of 16: 9 and 1920. There is a “PHWnnnn.PMP file” having image data of pixels × 1080 pixels. In addition, as one of the high-resolution image files, there is a “PUPnnnn.PMP file” which has image data of an aspect ratio of 3: 2 and 3072 pixels × 2048 pixels as a file for recording the ultra-high resolution image data UD.

  As shown in FIG. 18B, the intermediate resolution image file is “PSNnnnn.PMP file” having an aspect ratio of 4: 3 and 640 pixels × 480 pixels, and an aspect ratio of 16: 9 and 848. There is a “PSWnnnn.PMP file” having image data of pixels × 480 pixels.

  The file name of the image file with the extension “PMP” is determined by the first three characters (for example, PHP) depending on the type of the image, and is followed by the image number assigned in the order of image file formation. Five characters (nnnnn) are determined.

  Further, the extension of the index image file used in this image recording / playback system is PMX, and when it is detected that the extension is PMX, it can be identified that the file is an index image file. . The file name of this index image file is PIDXnnn. It is specified by PMX. In this index image file, as shown in FIG. 18C, 25 pieces of low resolution image data are stored as index image data. One low-resolution image data is composed of 60 pixels × 80 pixels generated by reducing the data rate by thinning out the intermediate resolution image data of 640 pixels × 480 pixels to 1/80.

Next, the still image filing system manages image data recorded on the optical disc 20 in a hierarchical directory structure. This hierarchical directory structure is as shown in FIG. 19, for example, and a directory D1 (PIC for recording image data) MD) is provided and file management is performed therein.
The directory D1 includes a general information management file f1 (OV) for managing the entire information. INF. PMF) and general index file f2 (OV) for managing the entire index file IDX. PMX) and image directories D2 to D4 (PIC00000 to PIC00002).

  In this example, image directories (PIC00000) to (PIC00002) having directory numbers “00000” to “00002” are provided as the image directories, respectively. Five characters following “PIC” of each image directory are given as a directory number in the order in which each image directory is formed, thereby indicating the image directory name.

In addition, the directory (PIC MD) includes a print directory (PRINT) for managing print control data such as print color, print size and rotation, and a telop directory (TERO) for managing telops such as titles of images to be displayed on a monitor. .PMO), the image number of each image, and the keyword search directory (KW) attached to each image. DTBS. PMO) and a time stamp directory (TS for managing image recording date and time) DTBS. (PMO) and a playback control directory (PMSEQ) for managing program playback such that only specified images are played back.

In the image directory D2 (PIC00000), an image data management file f3 (PIC) for managing a plurality of image files designated by the directory number “00000”. INF. PMF) and an image index file f4 (PIDX000.PMX) in which index images in the image directory D2 are collected. Further, in this image directory D2, an intermediate resolution image file f5 (PSN00000.PMP) and a high resolution image file f6 (PHP00000.PMP) formed based on the image data designated by the image number “00000”. And are recorded. Further, an intermediate resolution image file f7 (PSN00001.PMP) formed based on the image file data designated by the image number “00001” and an ultra-high resolution image file f9 (PUP00001.PMP) are recorded. . Further, the intermediate resolution image file f10 (PSN00002.PMP) formed based on the image data designated by the image number “00002” and the image data designated by the image number “00003” are formed. An intermediate resolution image file f11 (PSN00003.PMP) is recorded.

Next, the image directory (PIC00001) designated by the directory number “00001” contains the image data management file (PIC00001). INF. PMF) and two index files (PIDX000.PMX, PIDX001.PMX) for managing the index image of each image are recorded. The two image index files are used to manage the index images corresponding to the image files recorded in the image directory (PIC00001). Linked to be used.

Next, the print directory (PRINT) includes a print data management file (PRT) for managing a plurality of print data files. INF. PMF) and print data files (PRT000.PMO to PRTnnnn.PMO) managed by the print data management file are recorded.

Next, in the reproduction control directory (PMSEQ), a reproduction control management file (PMS) for managing the reproduction control data file recorded in the reproduction control directory (PMSEQ). INF. PMF) and a plurality of reproduction control data files (PMS000.PMO to PMSnnn.PMO) for controlling the image sequence are recorded.

  Next, as described with reference to FIG. 9C, the management blocks are assigned block numbers from 0 to 511. From the block number 0, volume descriptor VD, volume space bitmap VSB, management Table MT, management table MT, directory record block DRB, directory record block DRB, extent record block ERB, directory record block DRB, extent record block ERB.

Directory D1 (PIC The directory record block DRB for indicating (MD) can be determined to be the fourth block of the management block based on the data of the volume descriptor VD.

  That is, in FIG. 20, the directory record block DRB recorded in the fourth block of this management block contains the recording positions of the general information management file f1 and the general index file f2 shown in FIG. Two file DR units are provided to indicate

  The file DR unit recorded in the first unit indicates the allocation block position of the comprehensive information management file f1 by the allocation block number recorded as the extent start location. Yes. The file DR unit recorded in the second unit indicates the allocation block position of the comprehensive index file f2 by the allocation block number recorded as the extent start location. Yes.

  The general information management file f1 and the general index file f2 are not recorded in the index to ERB because they are recorded in continuous allocation blocks on the optical disc 20.

  Next, the third unit and the fourth unit, which are the units after the two file DR units, include an image directory D2 having a directory number of “00000” and an image directory D3 having a directory number of “00001”. There are provided two directory DR units for indicating the recording positions of each.

  Specifically, in this directory DR unit, the relative position in the management block of the DRB corresponding to the image directory D2 is indicated by the management block number of 0 to 511 recorded as index to DRB. It has become. In this example, “005” is recorded in the index-to-DRB data in the directory DR unit of the third unit as data indicating the block position in the management block of the index-to-DRB of the image directory D2. Yes. Similarly, “007” is recorded as data indicating the block position in the management block of the index to DRB in the image directory D3 in the index to DRB data of the directory DR unit of the fourth unit.

  Next, as described above, the index to DRB of the fifth block of the management block has its block position designated by the directory DR unit which is the third unit in the index to DRB of the fourth block of the management block. Yes.

  The fifth block index to DRB is a block in which data relating to the image directory D2 is recorded, and eight file DR units are provided following the header. The seven file DR units of the first to seventh units include an image data management file f3, an image index file f4, an intermediate resolution image data file f5, a high resolution image data file f6, and an intermediate resolution image data file f7, respectively. Data for indicating recording positions of the ultra-high resolution image data file f9 and the intermediate resolution image data file f10 are recorded. Further, similarly to the above-mentioned file DR unit, the image data management file f3, the image index file f4, and the intermediate resolution image are determined by the allocation block number recorded as the extent start location in each file DR unit. The recording positions of the data file f5, the high resolution image data file f6, and the intermediate resolution image data file f7 are respectively shown.

  Data for indicating the recording position of the ultra-high resolution image data file f9 is recorded in the file DR unit provided in the seventh unit. This ultra-high resolution image data file is recorded in a continuous area with a data length of 18 clusters, for example. If there is no continuous free area for 18 clusters on the optical disc 20, the ultra-high resolution image data file is distributed and recorded in non-consecutive allocation blocks. As described above, when one file is recorded in a distributed manner, the data of the extent start location of the DR unit for the file does not directly specify each distribution area of the file, but the directory record block DRB and the specification. An extent record block ERB is provided with the image file f9 to be executed, and the position of the distribution area of the image file is designated by the data of the extent record block ERB.

  As described with reference to FIG. 17, the extent record block ERB is provided with four extent record units (ER units) following the header. Note that a maximum of 64 ER units can be provided.

  The first ER unit is used as an index ER unit, and the second and third ER units are used as descriptor ER units. In the index ER unit, index data relating to the second and subsequent ER units is recorded. In the index ER unit, ER indexes and logical offsets are recorded for the number of ER units used.

  The ER index is data indicating which ER unit is present among the 64 ER units, and is indicated by ER unit numbers of 0 to 63.

  Further, the logical offset is data indicating what number of ER units the data of the ER unit indicated by the ER index constitutes one file.

  In the descriptor ER unit, 8 extent start positions and 8 extent block numbers can be recorded.

The extent start position is data for indicating the start position of the distributed area, and is indicated by an allocation block number. The number of extent blocks is data for indicating the data length of the distributed area, and is indicated by the number of allocation blocks. For this reason, eight distributed areas can be specified by one descriptor ER unit based on the data of the extent start position and the number of extent blocks.
That is, in the case of this example, as shown in FIG. 21, data “FFFF” indicating the index ER unit is recorded at the head of the first ER unit. In order to search for the first ER unit constituting the data of the ultra-high resolution image data file f9, it is only necessary to search where the logical offset data is “0000”. Since “2” is recorded as ER index data corresponding to the logical offset “0000” in the index ER unit, the second ER unit is the first ER unit constituting the data of the file f9. Can be detected.

  Next, referring to the second ER unit (descriptor ER unit), the start position of the first division area of the file f9 is the allocation block number “0152”, and the data of the first division area It can be seen that the length is “0002” as the number of allocation blocks. Similarly, data related to the second divided area to the eighth divided area are recorded in this descriptor ER unit in order.

  Next, “0001”, which is the next data of the logical offset “0000” in the index for index, is searched as data following the descriptor ER unit which is the second ER record. Since the data of the ER index whose logical offset is “0001” is recorded as “3”, it indicates that the third ER unit exists as data continuous to the second ER unit.

  Next, referring to the third ER unit (descriptor ER unit), the allocation block number indicating the start position of the ninth distribution area and the tenth distribution area and the number of allocation blocks indicating the data length are recorded. ing.

  Thus, since the allocation block position of each of the 10 distributed areas is indicated by the descriptor ER unit of the extent record block ERB, even when one image file is distributed and recorded, the extent In the management block having the record block ERB, the position of each distributed area can be grasped. For this reason, even when each distributed area is continuously reproduced as one file from the optical disk 20, it is not necessary to search each distributed area on the disk on the disk, and high-speed reproduction is possible. Can do.

  Note that such distributed recording of image files is not limited to the above-described recording of ultra-high resolution image files, and by overlapping the recording of image files, the unrecorded area on the disk is reduced, and depending on the image file of each resolution. This is performed when a continuous free area for a predetermined cluster cannot be secured.

5. [File structure]
Each file is composed of a header and a data body. The start address of the data body is specified by the header. The data body starts from, for example, an address that is a multiple of 4, and the upper byte is prioritized for data of 2 bytes or more. The data size is a multiple of 4 except for each fixed-length encoded image data (including 00h dummy data added when raster-block conversion of the above-described low resolution image data). The character string is terminated with null data (00h). In addition, it is good also as a structure which provides a vacant area between a header and a data main body.

5-1 [Configuration of header]
The header is composed of a plurality of tables, and a “format table” indicating what the file is is arranged at the head. Hereinafter, optional tables such as the image processing information are arranged in an arbitrary order. It is arranged. Each of the tables is started from an address that is a multiple of 4, for example, and the interval between the table and the next table is 256 bytes or less. A configuration in which empty data exists between a table and the next table may be adopted.

  Specifically, the types of the table include a format table (10h), a name table (11h), a comment table (12h), a disk ID table (14h), an image parameter table (20h), a recording information table (21h), There are a color management parameter table (22h), an option table (90h), and the like (in parentheses are IDs of the respective tables).

5-2 [Format Table]
As shown in FIG. 22, the format table includes a table ID (1 byte), a next table pointer (1 byte), a format version (2 bytes), a file format (1 byte), a file format version (1 byte), and all tables. Number (1 byte), free space (reservation: 1 byte), data start address (4 bytes), data size (4 bytes), free space (reservation: 4 bytes), all of which are binary ( The data is recorded in the data format B).

  As the “file format” recorded in 1 byte, the general information management file is recorded as “00h”, the image data management file is recorded as “01h”, and the print data management file is “03h”. The playback control management file is recorded as “05h”, the image data file is recorded as “10h”, the comprehensive index file is recorded as “11h”, and the image index file is recorded as “12h”. It has become. Also, the print data file is recorded at “30h”, the telop data file is recorded at “32h”, the keyword search data file is recorded at “33h”, and the time stamp search data file is recorded at “34h” for playback. The control data file is recorded with “35h”.

5-3 [Image Parameter Table]
The image parameter table is recorded in the header of each image file for recording the high resolution image data and the intermediate resolution image file data, and the image processing relating to the original image data based on the high resolution image data and the intermediate resolution image data. Information is recorded as a parameter.

  In the still image filing system, the high resolution image data and the intermediate resolution image data are formed based on original image data captured from a scanner or the like, and are recorded as a high resolution image file and an intermediate resolution image file. However, since the original image itself is not recorded on the disk, the original image data does not remain. However, based on the data of the image parameter table recorded in the header of the image file, the original image that is the basis of the high-resolution image data is recorded in what state, how it is processed, and the high-resolution image data and Whether intermediate resolution image data has been formed can be recognized based on the image processing information. Therefore, in order to leave information relating to the original image data, the data of the image parameter table is recorded in the header of the image file together with the image data, and is not rewritten.

  Next, as shown in FIG. 23, the image parameter table includes a 1-byte table ID, a 1-byte next table pointer, a 2-byte image size (horizontal size), and a 2-byte image size (vertical size). ), 1-byte image component, 1-byte vertical / horizontal identification, 1-byte wide ID, 1-byte compression ratio of the image data, 1-byte copyright, editing right information, 1-byte Input device identification information is recorded. In addition, information indicating the presence / absence of a 3-byte empty area (reservation) and 1-byte dummy data is recorded.

  The “image size” is information indicating the size of the number of pixels of the image, and the “image constituent element” has luminance (Y), color difference (Cr), and color difference (Cb) of 4: 2: “0” is recorded for 0, “01h” is recorded for 4: 2: 0 orthogonal, “10h” is recorded for 4: 2: 2, and 4: 2: 2 orthogonal. In this case, “20h” is recorded. Note that “orthogonal” indicates that the head Y data and the C data match.

  The “vertical / horizontal identification” is rotation information for displaying an image (counterclockwise). In the case of normal horizontal display, “00h” is recorded and rotated by 90 degrees with respect to the horizontal display. In the case of the vertical display, “01h” is recorded, in the case of the horizontal display rotated by 180 degrees with respect to the horizontal display, “02h” is recorded, and in the case of the vertical display rotated by 270 degrees with respect to the horizontal display “03h” is recorded. Note that “FFh” is currently undefined.

  Each of these pieces of information can be reproduced and displayed. Therefore, the user can easily recognize the parameters of the image by displaying the image parameter table on the monitor device 9.

5-4 [General information management file]
The comprehensive information management file is stored in a directory (PIC MD) is a management file for comprehensively managing all data files recorded in MD.

  The comprehensive information management file is composed of a header and a data body as shown in FIG. As described above, the format table (10h), name table (11h), comment table (12h), disc ID table (14h), and option table (90h) are recorded in the header.

  In the data body, the total number of images of 2 bytes, the next image directory number of 2 bytes, the total number of 2-byte image directories, the information indicating the presence or absence of a 1-byte playback control directory, the number of 1-byte playback control files, 1 byte The number of print data files and information indicating the presence / absence of a 1-byte telop data file are recorded. Also, information indicating presence / absence of 1-byte search information file, 1-byte automatic start file number, 2-byte last access image directory number, 2-byte last access image number, 8-byte password, 6-byte narration language information , A 2-byte free area (reserved) and N 48-byte image directory information units (N is the number of image directories) are recorded. These pieces of information are all recorded in a binary data format.

  The “total number of pixels” is information indicating the total number of pixels of a normal resolution (intermediate resolution image data) image having an aspect ratio of 3: 4, and the “next image directory number” is 1 in the final number of the image directory. The “total number of image directories” is information indicating the number (N) of image directories. Further, “00h” is recorded as “the presence / absence of the number of files of telop data”, and “01h” is recorded when it exists.

  As described above, the 48-byte image directory information unit is recorded in association with the index image recorded in the general index file. In this comprehensive index file, one index image selected by the user among the index images included in each image directory is recorded in the order of the image directory. Therefore, since one index image is extracted from the image directory, the same number (N) of index images as the image directory are recorded in the comprehensive index file.

  The one image directory information unit corresponds to one index image recorded in the general index file, and an image directory corresponding to the mth index image recorded in the general index file. The information unit is recorded as the mth unit. That is, this image directory information unit is recorded in the same order and the same number as the recording order of the index images of the general index file.

  Each image directory information unit has a 2-byte directory number, a 2-byte index image number, a 2-byte directory image count, a 1-byte index image individual information, and a 1-byte character as shown in FIG. It consists of an identification code, a 36-byte directory name, and a 4-byte free area. All except the “directory name” are recorded in a binary data format, but the “directory name” is recorded in ASCII code (A).

  When this “directory name” is recorded in a code other than an ASCII code such as an ISO code or a JIS code, the data format is “C”.

  A directory number for indicating an image directory including an image file corresponding to the index image is recorded in the directory number, and an image number for indicating the number of the image file corresponding to the index image is recorded in the index image number. Is recorded. Therefore, when the m-th index image of the general index file is designated by the user, first, the m-th image directory information unit from the head is referred to, and then the directory recorded in the referenced image directory information unit. Based on the number data, the image directory in which the designated image index is included is searched. Further, the index image individual information includes rotation information when the index image is displayed on the monitor, and the index image is displayed based on this information.

5-5 [Image data management file]
An image data management file is always provided for each image directory, and data for managing each image stored in the directory is recorded.

  The image data management file is composed of a header and a data body as shown in FIG. As described above, the format table (10h), the name table (11h), the comment table (12h), the disk ID table (14h), and the option table (90h) are recorded in the header.

  The data body includes a 1-byte link ID, a 3-byte free area (reserved), a 2-byte next image number, a 2-byte number of images, a 2-byte free area (reserved), and a 1-byte image index. The number of files, 1-byte next image index file number, 4 × 256-byte index file information, and N 16-byte image information units (number of images) are recorded. These pieces of information are recorded in a binary data format.

  The “number of images” is information indicating the total number of images (N) in the image directory. The “index file information” is arranged according to the display order, and for example, 256 entries are prepared regardless of the number of index files actually present.

The 16-byte image information unit is recorded in association with an index image recorded in an image index file to be described later. In the image index file, index images for indicating all the image files included in the image directory are recorded in the display order. For this reason, N index images of the same number as the total number N of images in the image directory are recorded in the image index file.
Further, this one image information unit corresponds to one index image recorded in the image index file, and the image information unit corresponding to the mth index image recorded in this image index file is m. Recorded as the second unit. That is, this image information unit is recorded in the same order and in the same number as the recording order of the index images of the image index file.

  Next, as shown in FIG. 25B, the image information unit includes a 2-byte directory number, 2-byte image number, 1-byte image type information, 1-byte image individual information, and 1-byte link number. , 1-byte narration information, 2-byte keyword search data number, 2-byte time stamp search data number, 2-byte telop number, and 2-byte empty area (reserved) are recorded. Each piece of information is recorded in a binary data format.

A directory number for indicating an image directory including an image file corresponding to the index image is recorded in the directory number, and an image number for indicating the number of the image file corresponding to the index image is recorded in the image number. Is to be recorded. Therefore, when the m-th index image of the image index file is designated by the user, first, the m-th image information unit from the top is referred to. In other words, the directory number data recorded in the referenced image information unit is searched for which image directory the specified image index is included in, and then the image number in the image directory is searched by the image number. The image file is searched for.
The image type information includes data indicating image types such as “PSN” representing an intermediate resolution image file and “PHP” representing a high resolution image file. When an intermediate resolution image file is designated, a file name (first three characters) is designated based on this image type information.

5-6 [Print data management file]
The print data management file is composed of a header and a data body as shown in FIG. A format table (10h), a name table (11h), a comment table (12h), and an option table (90h) are recorded in the header.

  In the data body, a 1-byte next print data file number, a 1-byte print data file total number, a 2-byte free area (reserved), and a 4 × N (several) -byte print data file management information unit are recorded. It has come to be.

  A value obtained by adding 1 to the number of the last print data file is recorded as the “next print data file number”, and the total number of the print data files is recorded as the “total number of print data files”. As the “information unit”, the number of print data files is recorded.

  In the “print data file management information unit”, as shown in FIG. 26B, a 1-byte print data file number, a 1-byte print execution ID, and a 2-byte free area (reserved) are recorded. It has become.

  The print data file number is information indicating the print data file number. As shown in FIG. 19, the print data file PRT000. A number corresponding to three characters “000” following the PMO PRT is recorded. As the “print execution ID”, “01h” is recorded when printing is not performed using the print data file specified by the print data file number, and the print data file specified by the print data file number is used. When printing, “00h” is recorded.

5-7 [Image data file]
The image data file includes a header and a data body as shown in FIG. The header includes a format table, an image parameter table, a division management table, a name table, a comment table, a copyright information table, a recording date table, a color management information table, an aviation information table, a camera information table, a scanner information table, and laboratory information. A table and an option table are recorded respectively. The “format table” and the “image parameter table” are indispensable recording items when configuring the system, and other than these are optional items.

  Each piece of data recorded in each of these tables is image processing information or the like indicating conditions when the original image data is processed to form high resolution data or intermediate resolution image data. For this reason, the data recorded in each of these tables is not rewritten during normal recording / reproduction.

  In the data body, fixed-length encoded high resolution image data or intermediate resolution image data is recorded.

5-8 [Total index file]
In this comprehensive index file, one index image selected by the user among a plurality of index images included in each image directory is recorded in the order of display on the monitor. Therefore, the same number of index images as each image directory are recorded in this comprehensive index file.

  The comprehensive index file is a set of index image data (low-resolution image data), and no header is provided in the file itself. The number of index images is recorded as “total number of directories” by the above-described general information management file. Each index is arranged in the same order as the order of management files.

  Specifically, as shown in FIG. 28A, the comprehensive index file is composed only of data bodies of index image data 0 to N each having 4096 bytes. Each index image data includes a header and a data body as shown in FIG. A format table is recorded in the header. This header is provided with an empty area following the format table, so that arbitrary information of the user can be recorded. The data body records fixed-length encoded index image data (low-resolution image data). In this data body, an empty area is provided following the index image data.

5-9 [Image index file]
In this image index file, index images for indicating all image files included in the image directory are recorded in the display order. Accordingly, N index images of the same number as the total number of images in the image directory are recorded in this image index file.

  The image index file is a set of index image data (low-resolution image data), and does not have a header of the file itself as shown in FIG. 29 (a). Instead, for each index image data, It has a configuration having a header. The number of index images is recorded as the total number of directories in the general information management file. Each index is arranged in the same order as the order of management files.

  Specifically, as shown in FIG. 29B, each index image data is composed of a format table and a header having an empty area, fixed-length encoded low resolution image data, and a data body having an empty area. Has been. The total amount of the header and the low resolution image data is, for example, 4096 bytes. Further, the header is fixed to 256 bytes including an empty area.

5-10 [Print Data File]
The print data file includes a header and a data body as shown in FIG. A format table, a name table, a comment table, and an option table are recorded in the header. In the data body, 2 bytes of print total, 2 bytes of free space (reserved), and 40 bytes of print information units (for the number of images) are recorded.

  In the “total number of prints”, information indicating the total number of images to be printed is recorded. In the “print information unit”, data indicating image data to be printed and when the images are printed out by the printer 2. Print control data and the like for controlling the printer 2 are recorded.

  Each piece of information is recorded in a binary data format.

  In the “print information unit”, as shown in FIG. 31, 2-byte image directory number, 2-byte image number, and 1-byte image type data are recorded as data representing image data.

  The “print information unit” includes, as print control data, the number of prints of 1 byte (number of prints), 1 byte of reservation (reserve), 1 byte of cutout ID, and 2 bytes of cutout start position (horizontal direction of the screen = X direction), 2-byte cutout start position (screen vertical direction = Y direction), 2-byte cutout size (vertical direction = X direction), and 2-byte cutout size (horizontal direction = Y direction) are recorded. It has come to be. 1-byte rotation ID, 1-byte mirror ID, 1-byte print size ID, 1-byte standard designation, 2-byte irregular size designation (horizontal direction = X direction), 2-byte irregular size designation ( (Vertical direction = Y direction), 1-byte multiplex ID, 1-byte multiplex mode, 1-byte caption ID, 1-byte caption type, and 1-byte color processing ID are recorded. . Also, 1 byte red (R) gain, 1 byte green (G) gain, 1 byte blue (B) gain, 1 byte contrast, 1 byte brightness, 1 byte sharpness, 1 byte saturation, 1 Data indicating the hue of the bite (rotation angle of the color coordinates) is recorded.

  The “print number” print control data is data indicating the number of prints of the same image. The print control data of “cutout ID” is data indicating whether or not a desired portion is cut out from the high resolution image data recorded on the disc and printed, and the high resolution image data recorded on the disc is used as it is. In the case of printing, “00h” is recorded as the cut-out ID, and in the case where a desired portion is cut out and printed, “01h” is recorded as the cut-out ID.

  The print control data indicating the “cutout start position” is the horizontal direction (X direction) and vertical direction (Y direction) of the screen when a desired portion is cut out and printed from the high-resolution image data recorded on the disc. Are data for designating the respective cutout start positions, and are recorded in units of pixels.

  The “mirror ID” is data for designating whether the high-resolution image data is printed in the normal rotation state or the reverse rotation state. When the normal rotation print is designated, the mirror ID is specified. “00h” is recorded, and when reverse printing is designated, “01h” is recorded as the mirror ID.

  The above-mentioned “print size ID” is data for designating whether to perform printing at a standard size described below or to print at an irregular size that is arbitrarily designated, and printing at a standard size is designated. When the print size ID is set, “00h” is recorded as the print size ID, and “01h” is recorded when printing with an irregular size is designated.

  The “standard designation” is data for selecting a desired print size from existing print sizes. “00h” is selected when the so-called E version is selected, and “00h” is selected when the L version is selected. “01h” is “02h” when the K version is selected, “03h” is selected when the cabinet (LL version) is selected, and “04h” is four when the six-cut size is selected. When the cut size is selected, “05h” is recorded. “10h” is selected when the A6 size is selected, “11h” is selected when the A5 size is selected, “12h” is selected when the A4 size is selected, and “10h” is selected when the A3 size is selected. 13h "is recorded.

  When printing with an irregular size is designated by the “print size ID”, “FFh” is recorded as print control data for the “standard” designation.

  The print control data of the above “unspecified size designation” is data for the user to arbitrarily specify the print size in addition to the above-described fixed size print size, and the vertical direction (X direction) and the horizontal direction (Y direction). Can be set in units of mm. When a standard is selected based on the “print size ID” and a desired print size is selected from the above sizes, “FFFFh” is recorded as print control data for this “indefinite size designation”. .

  The print control data of “Multiple ID” is data indicating the presence / absence of so-called multi-screen print designation in which one screen is divided into a plurality of portions and the same image is displayed on each screen. “00h” is recorded as “NO MULTIPLE”, and “01h” is recorded as “MULTIPLE” when printing a multi-screen.

  The “multiplex mode” print control data is data for designating how many one screen is divided when the multi-screen is printed. When one screen is divided into two, “00h” is “01h” when dividing one screen into four, “02h” when dividing one screen into six, “03h” when dividing one screen into eight, “04h” when dividing one screen into sixteen. Are recorded respectively.

  The print control data of the above “caption ID” is for designating whether or not characters such as a title and a recording date / time attached to the image are printed below (or above) the image to be printed. It is data. Characters such as the title and recording date / time are recorded in the 244 byte ASCII code as described above, and 244 characters (122 characters for Kanji) can be recorded. When the image is printed together with the title, recording date, etc., “01h” is recorded as the caption ID, and when the image is not printed together with the title, recording date, etc., “00h” is recorded. .

  The “caption type” print control data is data for designating whether to print each data constituting the header of the image data file described with reference to FIG. In this caption type, when the name data included in the “name table” is designated to be printed out together with the image data, “11h” is recorded as the table ID of the name table and included in the “comment table”. When the comment data to be printed is designated to be printed out together with the image data, “12h” is recorded as the table ID of the comment table, and the recording date / time data included in the “recording date table” is printed out together with the image data. In such a case, “14h” is recorded as the table ID of the recording date / time table.

  The print control data of the “color processing ID” is data indicating whether or not the user has performed color processing such as emphasizing red on a desired portion of the image, and the color processing is performed. If there is no color, “00h” is recorded, and if the color processing is performed, “01h” is recorded.

  The “R, G, B gain” print control data is data indicating the gain of each color data. Each color data can adjust the gain from 0 times to 5 times at an interval of 1/256 (8 bits), and the print control data for each gain is data indicating the adjusted gain. Is to be recorded.

  The “contrast” print control data is data indicating the contrast of an image to be printed, and can be adjusted at intervals of 1/256 as with the gain. A value indicating the contrast adjusted in this way is recorded as the print control data.

  The “brightness” and “hue” print control data is data indicating the brightness of an image to be printed, and is recorded as a percentage in the + direction and the − direction, with 128 represented by 8 bits being ± 0. ing.

  The “sharpness” print control data is data indicating the edge enhancement degree of an image adjusted between 0 and 5 times, and a value adjusted at an interval of 1/256 (8 bits) is recorded. It is like that.

  In the “saturation” print control data, a value adjusted between 1/2 times (8 bits) between 0 times and 5 times is recorded.

6). [Recording operation]
Next, based on the above hierarchical directory structure and each file structure, the recording operation of the still image filing system will be described using the flowcharts of FIGS.

  First, in the flowchart shown in FIG. 32, when the storage unit 5 enters a standby state, this flowchart is started and the process proceeds to step S1.

  In step S1, when the user inserts the optical disc 20, the process proceeds to step S2. As a result, the inserted optical disk 20 is loaded in the storage unit 5 and is ready to record and reproduce image data.

  In step S2, the system controller 6 controls the disc recording / reproducing unit 5c to read the P-TOC on the optical disc 20 shown in FIG. 8A via the storage unit controller 5d shown in FIG. Then, the read P-TOC data is transferred to the system controller 6 shown in FIG. The system controller 6 detects each data of the transferred P-TOC, thereby confirming whether the data U-TOC exists and confirming the recording position of the data U-TOC.

  If the data file exists, the system controller 6 determines that the data U-TOC exists at the head of the data file and proceeds to step S3.

In step S3, the system controller 6 controls the disc recording / reproducing unit 5c to read the data U-TOC on the optical disc 20 shown in FIG. 8A via the storage unit controller 5d. Then, the data U-TOC data is transferred to the RAM 6 a of the system controller 6. The system controller 6 once stores and reads out the transferred data U-TOC data in the RAM 6a, thereby grasping the position of each image directory and each file, and proceeds to step S4. The search for the storage location of the file will be described in detail later in the section “Explanation of operation during search”.
Next, in the step S4, the system controller 6 determines the directory (PIC) based on the data U-TOC data stored in the RAM 6a. MD) and whether or not the comprehensive information management file exists, it is determined whether or not the optical disc 20 is formatted for recording image data. If Yes, the process proceeds to step S5. If No, the process proceeds to step S11.

  In step S11, since the optical disc 20 is not formatted for image data, the system controller 6 formats the optical disc 20 for recording image data. Then, once all the routines shown in FIGS. 32 and 33 are finished, the standby state is maintained until recording is designated again.

  On the other hand, in step S5, the system controller 6 controls the disk recording / playback unit 5c so as to read all management files via the storage unit controller 5d, and stores all the read management files in the RAM 6a. And then proceed to step S6.

  In step S6, the system controller 6 controls the display of the monitor device 9 so as to display a screen for selecting a recording mode of an image to be recorded. Specifically, the monitor device 9 records an HD recording mode selection screen for recording a high-resolution image of 1024 pixels × 1536 pixels and an ultra-high-resolution image of 2048 pixels × 3072 pixels. The UD recording mode selection screen is displayed.

  The intermediate resolution image is recorded with a fixed data length of 2 clusters as described above, but a recording mode for recording the intermediate resolution image with a fixed data length of 1 cluster is provided. A fixed length encoding with a length and a fixed length encoding with a data length of one cluster may be selectable by the user. Thus, when a recording mode with a fixed data length of 2 clusters is selected, it is possible to record high resolution intermediate resolution image data, and when a recording mode with a fixed data length of 1 cluster is selected. Although the resolution is somewhat inferior, recording with an increased number of recordings can be made possible.

  Next, in step S7, the system controller 6 detects the operation state of the operation unit 10 to determine whether one of the HD recording mode and the UD recording mode has been selected. In the case of No, step S7 is repeated until the above selection is made, and in the case of Yes, the process proceeds to step S8.

  In step S8, the system controller 6 determines the total number of recorded images (total number of images of intermediate resolution image data) in the general information management file stored in the RAM 6a, the number of images in the image data management file, and Based on the image type information of the image information, the number of recordable images in the HD recording mode or UD recording mode designated by the user is calculated.

  Specifically, about 200 images can be recorded on the optical disc 20 by combining only two clusters of intermediate resolution image data and eight clusters of high resolution image data, and two clusters of intermediate resolution image data. In addition, about 100 images can be recorded by combining only 18 clusters of ultra-high resolution image data. For this reason, when the recorded capacity is subtracted from the recordable capacity of the entire optical disc 20, the recordable number when the HD recording mode is selected and the recordable number when the UD recording mode is selected can be calculated. it can.

  In step S9, the system controller 6 reads out the image directory information unit in the general management file from the RAM 6a, and controls display of data such as the directory name, the directory number, and the number of images in the image directory on the monitor device 9. Then, the process proceeds to step S10.

  In step S10, the system controller 6 detects the operation state of the operation unit 10 to determine whether or not the user has designated an image directory for recording the image data. If No, the process proceeds to step S12. In the case of Yes, it progresses to step S14 shown in FIG.

  In step S12, since the user does not specify an image directory, the system controller 6 detects the operation state of the operation unit 10 to determine whether a new image directory other than the existing image directory is specified. In the case of No, the above step S10 and step S12 are repeated until the formation of the new image directory is designated, and in the case of Yes, the process proceeds to step S13.

  In step S13, since the formation of a new image directory has been designated, the system controller 6 determines the number of existing image directories based on the general information management file, attaches the directory number of the new image directory, and this image directory. An image data management file and an image index file are formed in step S14, and the process proceeds to step S14 shown in FIG.

  Next, in step S14 shown in FIG. 33, the system controller 6 records and reproduces the disc via the storage unit controller 5d so as to read out all the image data recorded in the index file of the designated image directory. The unit 5c is controlled, and the image data of the index file is controlled to be transferred to the main memory 11a shown in FIG. 4, and the process proceeds to step S15. From the index file, the image data recorded by being fixed-length encoded together with the header is read as it is and is transferred to the main memory 11a without performing the decompression decoding process. Further, when image data is not recorded in the index file, the image data is not read out to the main memory.

  In step S15, the system controller 6 detects the operation state of the operation unit 10 to determine whether or not the user has designated the start of recording. If No, this step S15 is performed until the recording start is designated. If yes, go to step S16.

  In step S16, the system controller 6 determines whether or not the image to be recorded is an index image. If NO, the process proceeds to step S17, and if YES, the process proceeds to step S25.

  In step S25, the system controller 6 supplies data indicating that the image to be recorded is an index image to the thinning / compression / decompression controller 4i shown in FIG. When the data is supplied, the thinning / compression / decompression controller 4i sets a fixed length coefficient for the index image in the compression / decompression circuit 4h, and proceeds to step S26.

  In step S26, the system controller 6 performs compression encoding processing on the image data that has been thinned to ¼ based on the set fixed length coefficient via the thinning / compression / decompression controller 4i. By controlling the compression / decompression circuit 4h in this way, an index image that is fixed-length encoded to a fixed data length of 1/15 cluster is formed, and the process proceeds to step S27.

  In step S27, the system controller 6 controls the memory controller 13 to record a 4096-byte index image with a header added to the index file stored in the main memory 11a shown in FIG. Proceed to

  In step S28, the system controller 6 determines whether or not all index images have been recorded in the main memory 11a. If No, the process returns to step S16, and if Yes, the process proceeds to step S29.

  In step S29, the system controller 6 sets the 2-bit entry of the allocation block number of the volume space bitmap VSB in the data U-TOC stored in the RAM 6a to “00” (a code indicating an available allocation block). By searching for the location, an empty area is detected, and the process proceeds to step S30.

  In step S30, the system controller 6 controls the disc recording / reproducing unit 5c to access the detected empty area on the optical disc 20 via the storage unit controller 5d, and the process proceeds to step S31.

  In step S31, the system controller 6 controls the disc recording / reproducing unit 5c to record the index file having the index image in an empty area on the optical disc 20 via the storage unit controller 5d, and then proceeds to step S23. move on.

  That is, in the still image filing system, when the index image is fixed-length encoded and recorded on the optical disc 20, the main memory is once in turn before recording the fixed-number encoded index image on the optical disc 20. By recording on 11a, one index file is formed from a predetermined number of index images on the main memory 11a, and thereafter, it is recorded on a physically continuous area on the optical disc 20.

  On the other hand, as described above, one index image is fixed-length encoded to a data length of 1/15 cluster. For this reason, in order to record image data having a data length of 1/15 cluster on the optical disc 20, dummy data for 14/15 clusters is added to the image data for 1/15 clusters to add 1 Must be the data length of the cluster. Therefore, if the 1/15 cluster image data is recorded on the disk each time the dummy data recording area is larger than the index image data recording area on the disk. Cannot be used effectively.

  For this reason, in the still image filing system, a predetermined number of index image data is once recorded as an index file on the main memory 11a, and is recorded in the main memory 11a after all index image data has been captured. The index file is recorded on the disc.

  That is, for example, when recording an index file having 25 index images, 15 index images (15 × 1/15 clusters) are recorded in an area for one cluster, and the remaining 10 index images (10) are recorded. × 1/15 cluster) and 5/15 cluster dummy data are recorded in the next one cluster area. As a result, the amount of dummy data recorded on the disc can be reduced, and the recording area on the disc can be used effectively. Further, the still image filing system records a plurality of fixed-length encoded index images on the main memory 11a, thereby forming one index file with a predetermined number of index images on the main memory 11a. Since this index file is recorded in a physically continuous area on the disk, the index file recorded on the disk can be always a continuous file. For this reason, when reading the index file from the optical disk 20, it is possible to perform high-speed reading because it is continuously recorded on the disk.

  When a new index image is added to this index file, the index file data is read onto the main memory 11a prior to recording as described above. When recording, the new index image is recorded in the area immediately after the last recorded index image by deleting the dummy data added after the last recorded index image. (If there is no dummy data, there is no need to delete.)

  On the other hand, if it is determined No in step S16 and the process proceeds to step S17, the system controller 6 detects an empty area on the optical disk 20 for recording an intermediate resolution image or a high resolution image in step S17, and then proceeds to step S18. Proceed to

  Specifically, the system controller 6 sets the 2-bit entry of the allocation block number of the volume space bitmap VSB in the data U-TOC stored in the RAM 6a to “00” (a code indicating an available allocation block). The empty area is detected by searching for the location indicated by ().

  In step S18, the system controller 6 detects the optimum empty area among the empty areas searched in step S17, and the disk recording / reproducing unit 5c is accessed via the storage unit controller 5d so as to access this area. Control.

  Here, the optimum recording position is the area after the recorded file (the last recorded file) recorded in order under the same directory and the image (several clusters) to be recorded. Most preferably, the areas are physically contiguous areas.

  However, when recording large data, such as high-resolution image data (8 clusters) or ultra-high-resolution image data (18 clusters), if there are few unrecorded areas on the optical disc 20, recording is performed at the end of the same directory. There may be cases where a physically continuous area cannot be secured in the area behind the file. In such a case, an excellent record block ERB is formed in the management block, and a plurality of non-consecutive distributed areas are linked by this ERB to record one file.

  Next, in step S19, the system controller 6 sets a fixed length coefficient corresponding to the high resolution image data or the ultra high resolution image data in the thinning / compression / decompression controller 4i, and the process proceeds to step S20.

  In step S20, the thinning / compression / decompression controller 4i performs compression / decompression so as to form high-resolution image data for 8 clusters or ultra-high-resolution image data for 18 clusters based on the set fixed length coefficient. The circuit 4h is formed and the process proceeds to step S21.

  In step S21, the system controller 6 controls the disc recording / reproducing unit 5c to record the fixed-length image data in the optimum area on the detected optical disc 20 through the storage unit controller 5d. Then, the process proceeds to step S22.

  In step S22, the system controller 6 sequentially determines the image data management file data in the designated directory and the file name corresponding to the resolution of each image data, together with the recording control of the image data, and proceeds to step S23.

  Specifically, for example, when images 1 to 6 read from a negative film are recorded in the HD recording mode in the image directory “PIC00001”, the following is performed.

  That is, before recording, it can be determined from the data of the image data management file on the RAM 6a that the number of images recorded in the HD recording mode is zero, so the high resolution (HD) of the first image. Is PHP00000. At the same time, the intermediate resolution (SD) is PSN00000. PMP. Therefore, when all the six images have been recorded, PHP00000. PMP to PHP00005. PMP, PSN00000. PMP to PSN00005. A PMP file is formed.

  When the index images of these six images are recorded, these six index images are stored in the PIDX000. Recorded sequentially in PMX. For this reason, a new index file is not formed. However, if the number of index images to be recorded in one index file exceeds a preset number of index images (for example, 25 in this description), a new PIDX001. A second index file such as PMX is formed.

  Next, in step S23, the system controller 6 records all three types of resolution image data, that is, low resolution image data (index image), intermediate resolution image data, and high resolution image data (or ultra high resolution image data). If NO, the process returns to step S16 to record image data having a resolution that has not yet been recorded. If YES, the process proceeds to step S24.

  In step S24, the system controller 6 uses the data U-TOC, the general information management file, and the image data management file recorded on the disk as the data U-TOC, the general information management recorded on the RAM 6a. All the routines related to the recording operation shown in FIG. 32 and FIG.

  Specifically, in the data U-TOC, each of volume descriptor (VD), volume space bitmap (VSB), management table (MT), directory record block (DRB), extents record block (ERB), etc. Data is mainly rewritten.

  That is, in the VD, data relating to allocation blocks (recordable allocation blocks, etc.), number of directories (when the formation of a new directory is designated), number of files, data relating to directory record block DRB (new directory or file When the file is formed), data related to the extent record block ERB (when a newly formed file is recorded at physically discontinuous positions and linked by the extent record block ERB) is rewritten. In the volume space bitmap VSB, a 2-bit code or the like indicating the attribute of each allocation block is rewritten.

  The management table MT is entered when a directory record block DRB and an extent record block ERB are newly formed. However, when one directory record unit in the existing directory record block DRB is added, the management table MT is not updated.

  In the directory record block DRB, when a directory is newly formed, one directory directory record unit is added. Similarly, when a file is formed, one file directory record unit is added for each file.

  The extent record block ERB is formed when a file is specified by the directory record block DRB and the file is not physically continuous. It is not formed at the time of formatting.

  Next, in the general information management file, data such as the total number of images, the next image directory number, the total number of image directories, and the image directory information unit are mainly rewritten. When the image directory is newly formed, one unit is formed as the image directory information unit.

  Next, in the image data management file, when a new image directory is formed, a new image data management file is formed in the newly formed image directory. Data such as the number of images, the number of image index files, the next image index file number, index file information, and image information unit are mainly updated. The index file information is updated when an index file is newly formed, and the index number is updated when the index number in the index file is added. Further, since the image information unit is provided corresponding to each index image, the number of image information units increases by the increased number of images. In normal recording, the data in the image information unit is not updated, but when the order of the index images is changed, the image numbers are changed and updated.

7). [Description of Second Recording Operation]
Next, another recording operation of the image data of each resolution will be described with reference to the flowchart of FIG. The flowchart of FIG. 34 is started when the routine of steps S1 to S13 of the flowchart described in FIG. 32 is completed, and the process proceeds to step S41.

  In step S41, the system controller 6 reads all the image data recorded in the index file of the designated image directory, and proceeds to step S42.

  In step S42, the system controller 6 detects whether or not the recording start is designated by the user by detecting the operation state of the operation unit 10, and in the case of No, this step is performed until the recording start is designated. S42 is repeated, and if Yes, the process proceeds to step S43.

  Note that step S41 and step S42 shown in FIG. 34 are steps corresponding to step S14 and step S15 described in FIG. 33, respectively.

  Next, in step S43, the system controller 6 determines whether the image data to be recorded is high resolution image data (HD or UD), intermediate resolution image data (SD), or low resolution image data (index image). Data). When it is determined that the low resolution image data is being recorded, the process proceeds to step S53. When it is determined that the intermediate resolution image data is being recorded, the process proceeds to step S44, and the high resolution image data is being recorded. If it is determined, the process proceeds to step S52.

  Steps S53 to S59, which are determined to be at the time of recording low resolution image data in step S43, correspond to steps S25 to S31 shown in FIG. 33 described above.

  That is, in step S53, the system controller 6 supplies data indicating that the image to be recorded is an index image to the thinning / compression / decompression controller 4i shown in FIG. When the data is supplied, the thinning / compression / decompression controller 4i sets a fixed length coefficient for the index image in the compression / decompression circuit 4h, and proceeds to step S54.

  In step S54, the system controller 6 performs compression encoding processing on the image data that has been thinned to ¼ based on the set fixed length coefficient via the thinning / compression / decompression controller 4i. Then, the compression / decompression circuit 4h is controlled to form an index image that is fixed-length encoded to a fixed data length of 1/15 cluster, and the process proceeds to step S55.

  In step S55, the system controller 6 controls the memory controller 13 to record an index image of a total of 4096 bytes with a header added to the file stored in the main memory 11a shown in FIG. move on.

  In step S56, the system controller 6 determines whether or not all index images have been recorded in the main memory 11a. If NO, the process returns to step S43, and if YES, the process proceeds to step S57.

  In step S57, the system controller 6 sets the 2-bit entry of the allocation block number of the volume space bitmap VSB in the data U-TOC stored in the RAM 6a to “00” (a code indicating an available allocation block). By searching for a place where is, an empty area is detected and the process proceeds to step S58.

  In step S58, the system controller 6 controls the disc recording / reproducing unit 5c to access the detected empty area on the optical disc 20 via the storage unit controller 5d, and the process proceeds to step S59.

  In step S59, the system controller 6 controls the disc recording / reproducing unit 5c so as to record the index image in an empty area on the optical disc 20 via the storage unit controller 5d, and the process proceeds to step S50.

  Next, an empty area for low resolution image data in step S57, an empty area for intermediate resolution image data in step S44, and an empty area for high resolution image data (or for ultra high resolution image data) in step S52. Are detected respectively. As described above, the free area is detected when the 2-bit entry of the allocation block number of the volume space bitmap VSB in the data U-TOC stored in the RAM 6a is “00” (a code indicating an available allocation block). This is done by searching for the part indicated by (). At this time, the address to be searched is designated corresponding to the recording of each resolution.

  That is, the case of recording low-resolution image data (step S57) will be described. In normal use, up to 200 index images can be recorded in the HD recording mode. Even if the HD recording mode is selected or the UD recording mode is selected, the index image has a fixed data length of 1/15 cluster in any case. Therefore, the area necessary for the index image is 200 ×. 1/15 cluster = 13.33 cluster. However, if the number of image directories increases, there will be an image directory in which only one or two index images are recorded in one image directory. Since the maximum number of the image directories is set to 20 directories, in such a case, the capacity to record for the index image is most required, and at least 32 clusters are required. For this reason, the system controller 6 searches for the code of the allocation block designated by the address corresponding to the 1st to 32nd clusters from the inner periphery of the disk when detecting the free area at the time of recording the index image. Detect area. In this case, other empty areas are not detected.

  Next, the case of recording the intermediate resolution image data (step S44) will be described. Up to 200 sheets can be recorded in the HD recording mode, and the intermediate resolution (SD) image is recorded with a fixed data length of 2 clusters. Therefore, 2 clusters × 200 sheets = 400 clusters are required as an intermediate resolution image area. For this reason, the system controller 6 detects an area of 400 clusters after the index image area (1 to 32 clusters) from the inner periphery of the disk, that is, 33 to 33, when detecting an empty area of the intermediate resolution image recording. The code of the allocation block of the area specified by the address corresponding to the 432 cluster is searched to detect a free area, and the process proceeds to step S45.

  Similarly, in the UD recording mode, a maximum of 100 sheets can be recorded, and an intermediate resolution (SD) image is recorded with a fixed data length of 2 clusters. Cluster × 100 sheets = 200 clusters are required. For this reason, the system controller 6 detects an area for 200 clusters from the inner periphery of the disk to the index image area (1 to 32 clusters), that is, 33 to 33, when detecting an empty area for image recording at an intermediate resolution. The code of the allocation block in the area specified by the address corresponding to the 232 cluster is searched to detect a free area, and the process proceeds to step S45.

  Next, the case of recording the high resolution image data and the ultra high resolution image data (step S52) will be described. First, in the HD recording mode, a maximum of 200 images can be recorded, and the high resolution image data has 8 clusters. The fixed data length is. Therefore, 8 clusters × 200 sheets = 1600 clusters are required for the image area of the high resolution image data. For this reason, in step S53, the system controller 6 performs an area corresponding to 1600 clusters from the inner area of the disk to the index image area (1 to 32 clusters) and the intermediate resolution image area (33 to 432 clusters). That is, the code of the allocation block of the area specified by the address corresponding to the 433 to 2032 clusters is searched to detect a free area, and the process proceeds to step S45.

  Similarly, in the UD recording mode, a maximum of 100 sheets can be recorded, and the super high resolution image data has a fixed data length of 18 clusters. Therefore, the super high resolution image area is 18 clusters × 100 = 1800 clusters. Free space is required. For this reason, the system controller 6 detects the free area of the super high resolution image recording from the inner periphery of the disk to the index image area (1 to 32 clusters) and the intermediate resolution image area (33 to 232 clusters). A search is made for the code of the allocation block designated by the area corresponding to the subsequent 1800 clusters, that is, the addresses corresponding to the 233 to 2032 clusters, and an empty area is detected, and the process proceeds to step S45.

  Next, when the search for the free area is completed, in step S45, the disk recording / reproducing unit 5c is controlled via the storage unit controller 5d so as to access the optimum area among the free areas searched by the system controller 6. Then, the process proceeds to step S46. In this case, as the optimum recording position, regardless of the directory, a free area search is performed, and each data is recorded in order at a position where a free area exists first. Therefore, the recorded data is recorded in order from the head of each area.

  Next, in step S46, the system controller 6 sets a fixed length coefficient corresponding to the high resolution image data or the ultra high resolution image data in the thinning / compression / decompression controller 4i, and the process proceeds to step S47.

  In step S47, the system controller 6 uses the thinning / compression / decompression controller 4i to generate high resolution image data for 8 clusters or ultra high resolution image data for 18 clusters based on the set fixed length coefficient. The compression / decompression circuit 4h is controlled so as to form, and the process proceeds to step S48.

  In step S48, the system controller 6 controls the disc recording / reproducing unit 5c to record the fixed-length image data in the optimum area on the detected optical disc 20 via the storage unit controller 5d. Then, the process proceeds to step S49.

  In step S49, the system controller 6 sequentially determines the data of the image data management file in the designated image directory and the file name corresponding to the resolution of each image data, together with the recording control of the image data, and proceeds to step S50. .

  In step S50, whether or not the system controller 6 has recorded all the three types of resolution image data, that is, low resolution image data (index image), intermediate resolution image data, and high resolution image data (or ultra high resolution image data). If the answer is No, the process returns to step S43 to record image data having a resolution that has not yet been recorded. If the answer is Yes, the process proceeds to step S51.

  In step S51, the system controller 6 uses the data U-TOC, the comprehensive management information file, and the related data of the image data management file recorded on the disc as the data U-TOC, the comprehensive management recorded on the RAM 6a. All the routines relating to the other recording operations shown in FIG. 34 are completed after updating the data in the information file and the image data management file.

  Steps S45 to S51 correspond to steps S18 to S24 shown in FIG.

  In such another recording operation, search areas of low resolution, intermediate resolution, and high resolution (or ultra-high resolution) are designated by addressing the allocation block in the VSB stored in the RAM 6a. That is, since the recording area on the disk is divided by addressing only by reading the VSB data of the RAM 6a, it is possible to speed up the detection of the empty area.

  For example, it is conceivable to perform recording by physically determining the recording position of each area on the disc. However, in this case, since the amount of area (intermediate resolution area and high resolution area) used in the HD recording mode and the UD recording mode differs, the area is secured in advance assuming the most necessary amount. There is a need. That is, it is necessary to secure each area for 400 clusters in the HD recording mode in the intermediate resolution area and 1800 clusters in the UD mode in the high resolution area, and the recording area cannot be used effectively.

  Also, in this explanation, the address for searching the free area is specified for the index, intermediate resolution, and high resolution from the inner side of the disc, but this is conversely for the index and intermediate resolution from the outer side of the disc. , An address for searching for an empty area may be designated for high resolution, and can be changed as appropriate according to the design.

  Thus, based on the high resolution image data read out from the frame memory 11, intermediate resolution image data and low resolution image data are formed, and image data of different resolutions of the same image is recorded on the optical disc 20. Thus, at the time of reproduction, it is possible to select and reproduce image data having a resolution corresponding to the output device or application of the image data.

  That is, if only the high-resolution image data is recorded as the image data to be recorded on the optical disc 20, when the image is displayed on the monitor device, the high-resolution image data has too many pixels. Will be supplied to the device. However, by recording the above three types of image data, the intermediate resolution image data for monitoring can be directly read out, so the time until it is displayed on the monitor device can be shortened.

  Further, since image data having a required resolution can be directly read out, it is not necessary to perform a thinning process or the like depending on the device, and the circuit for the thinning process can be omitted.

  In addition, since the two types of image data are formed based on the high resolution image data from the frame memory 11, it takes a longer time to capture the image data than when the three types of image data are supplied separately. Since the frame memory 11 only needs to be read and controlled only once, the restraint time of the frame memory 11 can be shortened.

  Furthermore, since the image data of each resolution is encoded and recorded in a fixed length, the recording and reading time can be fixed, the number of recorded images can be fixed, and the data size to be handled is fixed. Therefore, the configuration of the file management system can be simplified.

8). [Description of Second Recording Operation]
Next, the third recording operation in which the system controller 6 records the high resolution image data and the intermediate resolution image data on the optical disc 20 and simultaneously records the index image data in the general index file (OV INDX.PMX) will be described. To do.

  This comprehensive index file is managed by the comprehensive information management file, and the index image recorded in each image directory is edited into one file.

  For example, in this example, when five image directories having 25 index images are formed, one index image at the head of each directory is taken out and recorded in order to obtain five index images. A comprehensive index file consisting of If the number of image directories is set to be small, the first five index images may be taken out from each directory to form a comprehensive index file.

  This comprehensive index file is formed when the screen data is formatted. For this reason, it is already formed when an image is recorded.

  The overall index file forming operation is as shown in the flowchart of FIG. The start of the flowchart shown in FIG. 35 is started when it is determined Yes in step S10 of FIG. 32 described above, and the process proceeds to step S61. Since the routine before step S10 is exactly the same, its description is omitted.

  Next, in step S61, the system controller 6 reads the comprehensive index file into the main memory 11a and proceeds to step S62.

  In step S62, the system controller 6 controls the disc recording / reproducing unit 5c via the storage unit controller 5d so as to read all the image data recorded in the image index file of the designated image directory, The image data of the image index file is controlled to be transferred to the main memory 11a shown in FIG. 4, and the process proceeds to step S63.

  From the image index file and the general index file, the image data that has been fixed-length encoded together with the header and recorded is read as it is and is transferred to the main memory 11a without being subjected to the expansion decoding process. Further, when no image data is recorded in the image index file and the general index file, the image data is not read into the main memory.

  In step S63, the system controller 6 detects the operation state of the operation unit 10 to determine whether or not the user has designated the start of recording. If No, this step S63 is performed until the recording start is designated. If yes, the process proceeds to step S64.

  In step S64, the system controller 6 determines whether the image to be recorded is an index image. If NO, the process proceeds to step S65. If YES, the process proceeds to step S72.

  In step S72, the system controller 6 supplies data indicating that the image to be recorded is an index image to the thinning / compression / decompression controller 4i shown in FIG. When the data is supplied, the thinning / compression / decompression controller 4i sets a fixed length coefficient for the index image in the compression / decompression circuit 4h, and proceeds to step S73.

  In step S73, the system controller 6 performs compression encoding processing on the image data that has been thinned to 1/4 based on the set fixed length coefficient via the thinning / compression / decompression controller 4i. Then, the compression / decompression circuit 4h is controlled to form an index image that is fixed-length encoded to a fixed data length of 1/15 cluster, and the process proceeds to step S74.

  In step S74, the system controller 6 first records the index image, which is fixed-length encoded in step S74, in the designated image directory based on the data of the general information management file stored in the RAM 6a. It is determined whether or not the image is an index image. If the result is No, the process proceeds to step S81. If the image is an index, the process proceeds to step S75.

  In step S81, the system controller 6 records the fixed-length encoded index image in the image index file, and proceeds to step S76.

  In step S75, the system controller 6 records the first index image in the general index file and the image index, and proceeds to step S76.

  In step S76, the system controller 6 controls the memory controller 13 to record a total of 4096-byte index images with headers added to the index files stored in the main memory 11a shown in FIG. Proceed to S77.

  In step S77, the system controller 6 determines whether or not all index images have been recorded in the main memory 11a. If No, the process returns to step S64, and if Yes, the process proceeds to step S78.

  In step S78, the system controller 6 sets the 2-bit entry of the allocation block number of the volume space bitmap VSB in the data U-TOC stored in the RAM 6a to “00” (a code indicating an available allocation block). By searching the place where is, an empty area is detected, and the process proceeds to step S79.

  In step S79, the system controller 6 controls the disc recording / reproducing unit 5c to access the detected empty area on the optical disc 20 via the storage unit controller 5d, and the process proceeds to step S80.

  In step S80, the system controller 6 controls the disc recording / reproducing unit 5c to record the index image in an empty area on the optical disc 20 via the storage unit controller 5d, and the process proceeds to step S71.

  As described above, when the index image is fixed-length encoded and recorded on the optical disc 20, before the fixed-length encoded index image is recorded on the optical disc 20, it is temporarily recorded on the main memory 11a in order. Then, one index file is formed from all index images on the main memory 11a, and then recorded in a physically continuous area on the optical disc 20.

  On the other hand, if it is determined No in step S64 and the process proceeds to step S65, in step S65, the system controller 6 detects an empty area on the optical disc 20 for recording an intermediate resolution image or a high resolution image. Proceed to S66.

  Specifically, the system controller 6 sets the 2-bit entry of the allocation block number of the volume space bitmap VSB in the data U-TOC stored in the RAM 6a to “00” (a code indicating an available allocation block). The empty area is detected by searching for a place where “

  In step S66, the system controller 6 detects the optimum empty area among the empty areas searched in step S65 as described above, and performs disk recording via the storage unit controller 5d so as to access it. The reproducing unit 5c is controlled and the process proceeds to step S67.

  Next, in step S67, the system controller 6 sets a fixed length coefficient corresponding to the high resolution image data or the ultra high resolution image data in the thinning / compression / decompression controller 4i, and the process proceeds to step S68.

  In step S68, the thinning / compression / decompression controller 4i performs compression / decompression so as to form high-resolution image data for 8 clusters or ultra-high-resolution image data for 18 clusters based on the set fixed length coefficient. The circuit 4h is formed and the process proceeds to step S69.

  In step S69, the system controller 6d controls the disc recording / reproducing unit 5c so as to record the fixed-length image data in the optimum area on the detected optical disc 20, and proceeds to step S70.

  In step S70, as described above, the system controller 6 sequentially determines the image data management file data in the designated directory and the file name corresponding to the resolution of each image data together with the recording control of the image data. Proceed to S71.

  In step S71, whether or not the system controller 6 has recorded all the three types of resolution image data, that is, low resolution image data (index image), intermediate resolution image data, and high resolution image data (or ultra high resolution image data). In the case of No, the process returns to step S64, and the image data of the resolution that has not been recorded yet is recorded. In the case of Yes, the process proceeds to step S91 shown in FIG.

  Here, when the recording of the image to be recorded is completed in this way, the data of the comprehensive index image can be replaced by the user. For example, since the first index image of each directory is set in advance in the general index file formed simultaneously with the formation of the high resolution, intermediate resolution, and index image files, 1 in each directory. Only the second index image is recorded. However, if the user desires, the first index image registered in the general management file can be replaced with another index image.

  This desired index image replacement operation is as shown in the routine after step S91 in FIG.

  That is, in step S91 of FIG. 36, the system controller 6 performs display control of the comprehensive index image and proceeds to step S92.

  In step S92, the system controller 6 detects the operation status of the operation unit 10 to determine whether or not the index image desired by the user has been specified. If No, this step S92 is repeated. Advances to step S93.

  That is, in this step S92, a desired index image is designated from the comprehensive index file. This indicates that an image directory corresponding to the designated index image is designated. In the following description, it is assumed that the designated image directory is the nth recorded image directory.

  Next, in step S93, the system controller 6 controls to reproduce the image index file in the nth image directory designated in step S92 and display it on the monitor device, and then proceeds to step S94.

  In step S94, the system controller 6 detects whether or not a desired index image has been designated from a predetermined number of index images of the image index file displayed on the monitor device by detecting the operation status of the operation unit 10. If the determination is No, step S94 is repeated. If the determination is Yes, the process proceeds to step S95.

  That is, in this step S94, a desired index image is designated from the nth image index file, that is, this designates an index image to be recorded instead of the first index image. is there. In the following description, the designated index image is assumed to be the mth index image recorded in the image index file.

  In step S95, the system controller 6 stores the mth index image data recorded in the image index file of the nth image directory on the main memory, and the nth index image data recorded in the general index file. The memory controller 13 is controlled to overwrite the position where the index image data is recorded. At the same time, the image directory information unit corresponding to the nth image directory in the RAM 6a, that is, the index image number “00001” recorded in the nth image directory information unit corresponds to the newly replaced index image. The image number “0000m” is replaced, and the process proceeds to step S96.

  In step S96, the system controller 6 controls the disk recording / reproducing unit 5c so as to record the comprehensive information management file on the optical disk 20, and the process proceeds to step S97.

  In step S97, the system controller 6 uses the data U-TOC, the comprehensive management information file, and the related data of the image data management file recorded on the disk as the data U-TOC, the comprehensive management recorded on the RAM 6a. All data in the information file and the image data management file are updated and all routines are terminated.

  The above-mentioned general index file records the first index image of each image directory at the time of data recording. However, when the number of image directories is reduced, the first five images of each image directory are recorded. An index image may be registered. For example, an example in which four image directories are formed and five index images are registered will be described. As shown below, the unit of the image directory information indicates the number of index images in the general index file. The following 20 units may be formed so as to correspond to 5 sheets × 4 directories = 20 sheets.

Directory number index Image directory information of the first image number 00 00
Second image directory information 00 01
Third image directory information 00 02
Fourth image directory information 00 03
5th image directory information 00 04
6th image directory information 01 00
7th image directory information 01 01
8th image directory information 01 02
9th image directory information 01 03
10th image directory information 01 04
Eleventh image directory information 02 00
12th image directory information 02 01
13th image directory information 02 02
14th image directory information 02 03
15th image directory information 02 04
・
・
・

9. [Reproduction and display of index images]
Next, index image reproduction and display operations in the still image filing system will be described in more detail with reference to the flowchart of FIG.

  The flowchart shown in FIG. 37 starts when the storage unit 5 enters the standby state, and proceeds to step S120.

  In step S120, when the user inserts the optical disc 20, the process proceeds to step S121. As a result, the inserted optical disk 20 is loaded in the storage unit 5 and the image data can be reproduced.

In step S121, the system controller 6 controls the disc recording / reproducing unit 5c to read the P-TOC and U-TOC recorded on the optical disc 20, and the P-TOC and U- It is determined whether or not a TOC exists. If each TOC does not exist, the process proceeds to step S139, where the display unit 26 is controlled to display “disk error”, and if each TOC exists, the process proceeds to step S122.
In step S122, the system controller 6 controls the disk recording / reproducing unit 5c to read the P-TOC and U-TOC, confirms the position of the data U-TOC, and proceeds to step S123. In the U-TOC, since the area where the data file is formed cannot be managed, if the data file exists, it is determined that the data U-TOC exists at the head thereof.

  In step S123, the system controller 6 stores the data U-TOC data in the RAM 6a, grasps the position of each directory and file, and proceeds to step S124.

In step S124, the system controller 6 determines whether or not the optical disc 20 is formatted for image recording. Specifically, the system controller 6 uses the directory (PIC) based on the data U-TOC data stored in the RAM 6a. MD), a general information management file, an image directory (at least one), an image data management file, and an image index file are determined to determine whether or not the optical disc 20 is formatted for image recording. Determine. If No, the process proceeds to step S140, and the display unit 26 is controlled to display “disk error”, and the process ends. If yes, the process proceeds to step S125.

  In step S125, the system controller 6 reads all the management files (the general information management file, the image data management file of each directory, the print control data management file, and the reproduction control management file) via the storage unit controller 5d. Then, the disc recording / reproducing unit 5c is controlled, and all the read management files are temporarily stored in the RAM 6a, and the process proceeds to step S126.

  In step S126, the system controller 6 determines whether an image to be displayed has been designated. If Yes, the system controller 6 proceeds to step S130, and if No, the process proceeds to step S127.

  In step S127, the system controller 6 searches for the comprehensive index file recorded on the optical disc 20, and proceeds to step S128.

  In particular, when an image directory is not specified, it is necessary to display what image data is recorded in each image directory to allow the user to specify a desired image. Therefore, in step S128, the system controller 6 controls the disk recording / reproducing unit 5c to display the comprehensive index file recorded on the optical disk 20, and the process proceeds to step S129. The comprehensive index file is a file in which the same index image data as any one index image among the index image data stored in the image index file in each image directory is registered in the display order of the monitor. is there. By displaying the comprehensive index file on the monitor, the user can specify a desired image directory.

  Next, in step S129, the system controller 6 detects the operation state of the operation unit 10 to determine whether or not the index image desired by the user is designated from the index image displayed on the monitor. In the case of, step S129 is repeated until the designation is made, and in the case of Yes, the process proceeds to step S130.

  In step S130, the system controller 6 searches for an image directory corresponding to the designated index image, and proceeds to step S131.

That is, the same number of image directory information units (48-byte data) in the general information management file stored in the RAM 6a as the number of displayed index images (= the number of image directories) are registered. And are recorded in order so as to correspond to the display order of the index images. For example, a case where the second index image displayed by the general information management file is designated will be described as an example. First, the 48-byte image directory information unit corresponding to the designated second index image is: It is recorded second from the beginning. It is understood that data “00001” is recorded in the directory number of the second image directory information unit, and the directory in which this index image is recorded by this data is the image directory of the second PIC0001.
Next, in step S131, the system controller 6 searches for the image index file in the directory searched in step S130, and proceeds to step S132.

  In step S132, the system controller 6 controls display of the first image index file (including 25 index images) in the searched directory on the monitor device 9, and the process proceeds to step S133.

  In step S133, the system controller 6 determines whether or not a user-desired image has been designated from among the index images displayed on the monitor device 9 by detecting the operation state of the operation unit 10. If No, the process proceeds to step S134, and if Yes, the process proceeds to step S136.

  In step S134, the system controller 6 detects the operation state of the operation unit 10 to determine whether display of the next image index file (including the remaining 25 index images) has been designated. In the case of No, the process returns to step S133 described above, and in the case of Yes, the process proceeds to step S135.

  In step S135, the system controller 6 controls display of the remaining 25 index images on the monitor device 9 and returns to step S133.

  On the other hand, if it is determined in step S133 that an index image is designated, the process proceeds to step S136, and the system controller 6 searches for a high resolution image file or an intermediate resolution image file corresponding to the designated index image. Then, the process proceeds to step S137.

  Specifically, the system controller 6 selects an image data management file corresponding to the image directory where the displayed index file exists from among the image data management files in each image directory stored in the RAM 6a. select. In the image information unit (16 bytes) of the selected image data management file, the same number of image information units as the number (N) of indexes registered in the image index file are registered. The image information units are recorded in order so as to correspond to the displayed index order.

  For example, a case will be described in which 25 index images displayed by the image index file are designated as the fourth index image from among the index files in the index file of the first image directory. First, since the displayed index file is the index file of the first image directory, the system controller 6 refers to the data of the first image data management file on the RAM 6a. When the fourth index image is designated by the user, the fourth image information unit of the referenced image data management file is searched. In the retrieved data in the image information unit, data “00000” as the directory number and data “00003” as the image information are recorded. Therefore, the high resolution image file corresponding to the designated index image is determined to have the file name “PHP000003” in the image directory “PIC00000”, and the intermediate resolution image file is the file in the image directory “PIC00000”. The name is determined to be “PSN00003”.

  In addition, when an index image is selected as described above and corresponding high resolution and intermediate resolution image files are searched, it is always supported based on the data in the image information unit of the image data management file. The image file to be searched is retrieved.

  For example, when the position of the index image is changed by editing or the like described later, there is a difference between the display order of the index image and the image number of the image file. However, in the still image filing system, since the display order of the index image and the image number of the image file coincide with each other, even if the display order of the index image is changed, the image information management unit uses the image information unit of the image data management file. Correspondence between the index image and the high-resolution and intermediate-resolution image files can be taken. Details will be described later in the section “Image Editing”.

  Next, in step S137, the system controller 6 detects the operation state of the operation unit 10 to determine whether monitor display of the searched intermediate resolution image file is specified. Proceeding to step S138, in the case of No, this step S137 is repeated.

  In step S138, the system controller 6 controls the disc recording / reproducing unit 5c to read the data of the searched intermediate resolution image file, and displays the reproduced intermediate resolution image file thereby. The display of the apparatus 9 is controlled, and it is determined whether or not a printout of the searched high resolution image file is designated. And in the case of No, the said step S138 is repeated. In the case of Yes, the system controller 6 controls the disk recording / reproducing unit 5c so as to read the searched high resolution image file, and supplies it to the printer unit 2 via the main memory 11a. All the index image reproduction and display routines shown in FIG. 37 are terminated.

  The printer unit 2 supplied with the high resolution image file converts the high resolution image data supplied as RGB data into yellow (Y), magenta (M), and cyan (C) data. These are printed on the print paper by the thermal head in order from the Y data.

10. [Search file and image directory]
Next, a case where, for example, an image file f5 (PSN00000.PMP) is searched will be described with reference to the hierarchical structure of the file described with reference to FIG. This search operation is as shown in the flowchart of FIG. The flowchart shown in FIG. 38 is started when the data U-TOC data is stored in the RAM 6a and a desired image directory and file name are designated by the user, and the process proceeds to step S141.

  In step S141, the system controller 6 searches the block number of the first directory record block (DRB) indicating the directory (PIC_MD) based on the volume descriptor (VD) of the volume management area, and proceeds to step S142.

  More specifically, the DRB position in the management block is recorded as a block number by data indicating the position of the first directory record block of the VD. In the still image filing system, the block number of the first DRB is “0004” as described above. Therefore, the system controller 6 determines that the DRB for indicating the directory D1 (PIC_MD) is the DRB indicated by the management block number “0004”.

  Next, in step S142, the system controller 6 determines whether the designated DRB is a single DRB or a continuous DRB by referring to the management block entry recorded in the MT, If it is alone, the process proceeds to step S143. If it is not alone, the process proceeds to step S147.

  In the file hierarchical structure shown in FIG. 20, since the DRB with the management block number “0004” is a single DRB, the process proceeds to step S143.

  In the above step S143, the system controller 6 indicates the directory DR unit for indicating the recording position of the image directory D2 (PIC00000) in which the image file f5 exists among the plurality of DR units provided in the DRB representing the directory D1. Search for.

  In the file hierarchical structure shown in FIG. 19, the third DR unit of the DRB representing the directory D1 is a directory DR unit for indicating the recording position of the image directory D2, and therefore the directory that is the third DR unit. The DR unit for use is searched. In this third DR unit, the directory DR unit, “index to DRB” is recorded, and the DRB block representing the image directory D2 by the management block number recorded as this “index to DRB” A position is specified. That is, in the file hierarchical structure shown in FIG. 19, since “0005” is recorded as “index to DRB” data, the DRB for representing the image directory D2 has a management block number “0005”. It is determined that the DRB is indicated by.

  On the other hand, in step S147, the system controller 6 sequentially searches for DR units in the DRB, and determines whether there is a directory DR unit for indicating the designated image directory. In the case of No (that is, the DR unit indicating the designated image directory does not exist in the first linked DRB), the process proceeds to step S148, and in the case of Yes (that is, the linked first DRB). If there is a DR unit indicating the designated image directory in the DRB), the process proceeds to step S144. In the file hierarchical structure of FIG. 20, when searching for the image file f5, the DRB representing the directory D1 (PIC_MD) and the DRB representing the image directory D2 (PIC00000) are both independent DRBs. Steps S147 and S148 are not used.

  In step S144, it is determined whether the directory DR unit that is searched in step S143 is a directory DR unit indicating the designated directory. Since the file structure used in the still image filing system has a tree structure as shown in FIG. 19, in step S144, the last directory in the process in which the searched directory reaches the designated directory. It is determined whether or not the directory is the lowest layer. When searching for the image file f5 in the file hierarchical structure of FIG. 19, since the image directory D2 shown in step S143 is the lowest layer directory, the determination result in step S144 is YES. Then, the process proceeds to step S145.

  In step S145, the system controller 6 selects a file DR unit for indicating the recording position of the image file f5 from the plurality of DR units provided in the DRB for representing the image directory D2 searched in step S143. Search for.

  That is, in the file hierarchical structure shown in FIG. 19, the third DR unit of the DRB representing the image directory D2 is a file DR unit for indicating the image file f5. A DR unit for a file that is a DR unit is searched. In this file DR unit, “extent start location” is recorded, and the recording position of the image file f5 is designated by the allocation book number recorded as this “extent start location”, and the process proceeds to step S146.

  In step S146, the system controller 6 accesses the allocation book position searched in step S145 in the file extents area, and confirms that the image file f5 exists at the accessed position. The image file f5 can be reproduced with the access position as the head.

  Since the still image filing system searches for an image file as described above, the number of physical reads for file search is reduced, and image files in an image directory having a hierarchical directory structure are reduced. You can search easily and quickly.

  In addition, since information related to the hierarchical directory structure is concentrated in the second area (volume management area), it is only necessary to access this volume management area when reading information necessary for file search. Since the recording position of the file can be grasped, the number of accesses can be reduced and the reading of the image file can be speeded up.

  Further, since the volume management area does not record any large-capacity data such as image data and records only management data, it is very suitable for storing in the RAM. Therefore, once this management data is stored in this RAM, the number of accesses to the optical disk to retrieve files can be further reduced.

11. [Edit image]
When the image recording is completed, the index image can be edited by the user's selection. This image editing refers to, for example, the work of moving image data in a certain image directory to another image directory, or the work of changing the display order of index images by replacing index images within the same image directory. is there.

  As an example, an example in which the fifth index image displayed in the first image directory is moved to the tenth display position in the second directory will be described with reference to the flowchart of FIG.

  The flowchart shown in FIG. 39 is started when recording of a desired image is completed and the user turns on the edit designation key, and the process proceeds to step S151.

  In step S151, the system controller 6 reads the index file in the source image directory (first), controls the disk recording / playback unit 5c to display 25 index images, and proceeds to step S152 (playback). See the Operation section).

  In step S152, the system controller 6 determines whether or not an index image to be moved in the source image directory is specified (whether or not the index image displayed fifth in the first directory is specified). If the answer is No, Step S152 is repeated. If the answer is Yes, the process proceeds to Step S153.

  In step S153, the system controller 6 detects the operation state of the operation unit 10 to determine whether or not the destination image directory and the movement position are specified (in this example, the tenth of the second directory). The original image is moved to the index image). If No, this step S153 is repeated, and if Yes, the process proceeds to step S154.

  In step S154, the system controller 6 reads out all index images of the index file of the source image directory and all index images of the index file of the destination image directory onto the main memory 11a. 5c etc. are controlled and it progresses to step S155.

  In step S155, the system controller 6 moves only the designated index image (including the header) from the index file of the movement source (first image directory) to the index file of the movement destination (second image directory). The memory controller 13 is controlled so as to proceed to step S156.

  That is, in the image index file, as described above, each index image is fixed at 4096 bytes including the header and the data body. Therefore, in this example, since 4096 bytes after 4096 × 3 bytes from the head of the index file are determined as the data of the fourth index image (including the header), the position of the index image in the image index file is Easy to grasp. Similarly, the data destination of the index image (4096 bytes) to be moved is specified in the area after 4096 × 9 bytes of the index file of the destination directory (second), and is inserted into that area. . The insertion described here is to insert between the 8th index image and the 9th index image, not to overwrite the 9th index image.

  Next, in step S156, the system controller 6 deletes the moved index image of the source index file to update the file, and adds the moved index image of the destination index file to the memory. The controller 13 is controlled. Then, the destination file is updated and the process proceeds to step S157.

  In step S157, the system controller 6 re-records the edited source index file and the destination index file in the same location on the disc, and proceeds to step S158. In addition, even if it is not the same place, if there is another place that can secure an area, that place may be used.

  In step S158, the system controller 6 is recorded in the fifth of the plurality of image information units (16 bytes) recorded in the image data management file of the movement source (first directory) on the RAM 6a. The existing image information unit is moved to the tenth image information unit in the image data management file of the movement destination (second directory) without changing the data, and the process proceeds to step S159. Note that there is no data update for high resolution and intermediate resolution image data files recorded on the disc.

  Next, in step S159, the system controller 6 determines whether or not an eject has been designated by the operation unit 10. If No, this step S159 is repeated, and if Yes, the process proceeds to step S160.

  In step S160, the system controller 6 reads the data U-TOC, the general information management file, and the image data management file on the RAM 6a, and controls the disk recording / reproducing unit 5c to write the data U-TOC on the disk. All the routines related to the image editing operation are completed by updating the data.

  Here, for example, a recording medium provided with a header in which data for matching the display order of index images is provided at the beginning of a file of high resolution or intermediate resolution image data will be described as an example. In such a recording medium, when editing as described above is performed, the display order of the index images can be matched by rewriting the header data. However, in order to rewrite the header data, it is necessary to once read all data (including the image data) of the image file, and it takes time to reproduce from the disk.

  However, in the above-described editing operation in the still image filing system, the index file swaps the physical position on the disc in the order in which it is actually displayed, but the high resolution and intermediate resolution image data is on the disc. The image information unit data in the image data management file read into the RAM 6a is exchanged without changing the position of. Then, only by such replacement of each data, the correspondence between the display order of the index images and the high resolution image file and the intermediate resolution image file can be obtained. For this reason, only rewriting of the index image in the index file and rewriting of the image data management file on the RAM 6a are required to be rewritten. Therefore, the rewriting data can be greatly reduced, and the rewriting operation can be speeded up.

  Further, since the physical position of the index image on the disc is changed so that the index file is in the same order as the display order, high-speed reading of the index file can be realized.

  Further, when changing the display order of the index images in the same index file in the same image directory, the same control can be performed. For example, when the display order is changed so that the seventh index image in the same index file is displayed second, first, all data of the index file is once read from the disk onto the main memory 11a, and the seventh The index image is moved to the second position, the index file is edited on the main memory, and then re-recorded on the disc. On the other hand, on the RAM 6a, the seventh 16-byte image information unit is inserted second in the image data management file without changing the data. That is, even when the display order of the index images is changed in the same image directory, only the index file and the image information unit on the RAM are rewritten, and the actual image data is not rewritten. Become.

12 [Description of index print]
Hereinafter, index printing will be described. The index print described here means that an index image is printed on an index card stored in a cassette case for storing a disk cassette.

  Hereinafter, a specific description will be given with reference to the drawings. First, an index card 50 on which an index image is printed by this still image filing system is printed so as to be arranged on a print paper 40 as shown in FIG. In the first embodiment of index printing in the still image filing system, A4 size paper is used as the print paper 40. Eight index cards 50 are arranged on the A4 size print paper 40, and a plurality of index images are printed. Each index card 50 is printed with 25 pairs of image print sections 51 and 25 related information print sections 52. In this image printing unit 51, index image data is printed. In the related information printing unit 52, a character “4” indicating an image directory, “U” indicating a recording mode of high resolution image data, and a character “5” indicating an image number are printed. A detailed description of each related information recorded in the related information printing unit 52 will be described later. Next, the index card 50 printed out on the print paper 40 is cut out along the cut line 40 and separated into eight index cards 50 each having a size of 6.3 cm long × 9.0 cm wide. The size of the index card 50 (length 6.3 cm × width 9.0 cm) is set in advance as a size that can be accommodated in a cassette case described later.

  As shown in FIG. 41, the cassette case 60 for storing the disk cassette 30 has a cassette storage portion 61 for storing the disk cassette 30 and a lid portion 62. The lid portion 62 is provided with a locking portion 63 that locks the index card 50. Each of the eight index cards 50 cut off is stored inside the lid portion 62 so as to be overlapped and locked to the locking portion 63.

  By removing the eight index cards 50 stored in the cassette case 60, the eight index cards 50 can be loaded into the eight index cards 50 without having to load the disc into a playback device and play back and check the image data recorded on the disc. It is possible to visually check the index images that have been printed. Therefore, the user can easily identify what is recorded on the disc.

  In the first embodiment of the index print, the A4 size is used as the print paper 40. However, in order to omit the work of cutting along the cut line 40 after printing the index image, the size of the index card (length 6) is used. It is also possible to print an index image on a printing paper (.3 cm × 9.0 cm wide). In such a case, eight index prints are performed.

  In the second embodiment of index printing in this still image filing system, an index card as shown in FIG. 42 is created. On the print paper 90, a cutout frame 91 indicating the outer shape of the index card 80 and an index card 80 having 25 index images are printed out. The index card 80 includes a front surface portion 80a, a back surface portion 80b, and a back surface portion 80c. Between the front surface portion 80a and the back surface portion 80b, and between the back surface portion 80b and the back surface portion 80c, a fold curve 85 is provided so as to indicate each boundary and bend along the boundary. . Similarly to the above-described index card 50, the front surface 80a is provided with 25 image printing sections 81 for printing index images and 25 related information printing sections 82 for printing related information related to index images. . The related information printing unit 82 prints the same data as the related information printing unit 52 described above. In addition, the front surface portion 80a is provided with an image directory printing portion 83 for printing the name of the image directory in order to indicate the image directory including the printed index image data. A disc name printing unit 84 for printing a disc name for indicating a directory name is provided on the back surface 80b.

  The index card 80 is cut along the cut frame 91 from the printed paper 90 that has been printed out. The index card 80 cut out is bent along the folding line 85 as shown in FIG. The index card 80 is accommodated so that the surface portion 80 a thereof corresponds to the lid portion 62 of the cassette case 60.

  Since the cassette case 60 is formed of a transparent plastic resin, it is possible to visually recognize the index image printed on the surface portion 80a of the index card 80 by storing the index card 80 as described above. It is. Accordingly, the user can visually check the index images printed on the front surface portion 80a of the index card 80 without loading the disc into the playback device and playing back and confirming the image data recorded on the disc. The user can easily identify what image is recorded on the disc.

  Further, in the index printing of the second embodiment, information for creating an index card such as the cut frame 91 and the folding line 85 is printed at the same time as the index image data, so that the index card can be easily processed. It can be carried out.

  In the description of the index print of the first and second embodiments described above, an index card is created by printing an index image on a print paper. For example, as shown in FIG. The above-described reduced-size image, album name, disc name, and the like may be printed on the label 99, and the disc label 99 may be attached to the disc cassette 30.

  As a result, the user can easily grasp the image, the disk name, and the like recorded on the optical disk 28 simply by looking at the disk label 99 on the surface of the disk cassette 30.

  Further, the punching position of the punch hole may be printed instead of the folding line 85 described above. In this case, the user can punch out printed punch holes and store the index card in, for example, a file.

Alternatively, instead of the folding curve 85, the user may be able to fold the index card in the same manner as in the above-described embodiment, by printing the color of the spine portion 86 in a color different from that of the print paper and displaying the processing position. The song position can be easily grasped, and the index card can be easily processed.
13. [Description of index print operation]
In the present still image filing system, index printing can be performed after all image data has been recorded on the disc. That is, index printing can be performed after step S24 in the first recording operation, after step S51 in the second recording operation, or after step S97 in the third recording operation.

  First, the operation of the first index print will be specifically described with reference to the flow shown in FIG. The first index printing operation is an operation for printing the index card of the first embodiment shown in FIG.

  The operation flow of the first index card is the same as step S24 in the operation flow shown in FIG. 33, step S51 in the operation flow shown in FIG. 34, or step S97 in the operation flow shown in FIG. Is started, the process proceeds to step S200.

  In step S200, it is determined whether to perform index printing. For example, when a text “Do you want to print index?” Is displayed on the monitor, and the operator instructs index printing in response to this, the process proceeds to step S201.

  In step S201, selection of a print mode is determined. This print mode includes two print modes, a high resolution print mode and a low resolution print mode. The high resolution print mode is a mode in which a plurality of print image data to be printed on the index card is generated by intermediate resolution image data. The low resolution print mode is a mode in which print image data to be printed on the index card is generated by the low resolution image data recorded in the index image file, that is, index image data. In step S201, if the operator designates the high resolution print mode, the process proceeds to step S202. If the operator designates the low resolution print mode, the process proceeds to step S210.

  First, the high resolution print mode will be described. That is, when the high resolution print mode is designated in step S201, the process proceeds to step S202.

  In step S202, the intermediate resolution file is searched. First, the system controller 6 refers to the directory number and image number of the image data management file stored in the RAM 6a, and designates the image directory and image file. The designated image directory is the directory with the smallest directory number “mmmmm”. That is, in the example of the file structure shown in FIG. 19, “PIC00000” is designated first. In addition, as the intermediate resolution file, a file having the smallest image number “nnnnn” in the designated directory is designated. In the example of the file structure shown in FIG. 19, the file “PSN00000.PMP” is first designated. In step S202, when a file name is designated by the system controller 6, the process proceeds to step S203.

  In step S203, the system controller 6 controls the storage controller 5d so that the file specified in step S202 is searched for and read on the disk. The file search operation is performed in accordance with the operation flow of FIG. 38 described in the section “Searching for Files and Image Directories”. Then, the intermediate resolution image data of the intermediate resolution file read from the storage unit 5 is JPEG decompressed and stored in the main memory 11 a of the image processing block 3. When the reading of the intermediate resolution image data is completed in step S203, the process proceeds to step S204.

  In step S204, image processing is performed on the intermediate resolution image data recorded in the main memory 11a. As shown in FIG. 46, this image processing is a process of reducing the amount of data by thinning out intermediate resolution image data having data of 640 pixels × 480 pixels and generating medium / low resolution image data of 256 pixels × 192 pixels. is there. The amount of image data reduced by this image processing is automatically set by the system controller 6 according to the resolution on the printer unit 2 side. In this embodiment, since the system controller 6 understands that the resolution of the printer unit 2 is 300 DPI, it is determined that 256 pixels × 192 pixels is most suitable for a printer having the resolution of 300 DPI. . The medium / low resolution image data whose data amount is reduced to 256 pixels × 192 pixels is stored at a predetermined address in the main memory 11a, and the process proceeds to step S205.

  In step S205, the related information data is combined with the medium / low resolution image data of 256 pixels × 192 pixels stored in the main memory 11a. The related information data is information relating to the high resolution file associated with the intermediate resolution file designated in step S202. This related information data is printed in the area of the related information printing unit 52 shown in FIG.

  Next, the related information data will be specifically described. The related information data includes an image directory number, a recording mode for high-resolution image data, and data such as an image number.

  First, how the image directory number to be printed as the related data and the data related to the image number are obtained will be described.

  In the previous step S202, since the directory name of the intermediate resolution file is designated based on the directory number of the image data management file stored in the RAM 6a, the image to be printed is designated by the image directory number designated in this step S202. The directory number data is determined. Similarly, in the previous step S202, since the file name of the intermediate resolution file is designated based on the image number of the image data management file stored in the RAM 6a, printing is performed with the image number designated in step S202. The image number data is determined.

  Next, how the recording mode of the high resolution image data printed as the related information data is obtained will be described.

  The recording mode is data indicating whether the high-resolution image data is recorded in the HD recording mode (1024 pixels × 1536 pixels) or the UD mode (2048 pixels × 3072 pixels). As described above, in step S7 in the operation flow shown in FIG. 32, the operator always selects the HD recording mode or the UD recording mode. The recording mode selected in step S7 is recorded as image type information in image information units provided in the number of image files in the image data management file. For example, in the HD recording mode, data indicated by “b2h” is recorded in the RAM 6a as image type information, and in the UD recording mode, data indicated by “b5h” is recorded in the RAM 6a as image type information. Accordingly, in this step S204, first, a high resolution file related to the intermediate resolution file designated in step S202 is designated. That is, a high resolution file having the same image number is designated. Next, the image information unit corresponding to the designated high resolution file is searched from the RAM 6a, and the recording mode printed as the related information data by referring to the image type information in the searched image information unit. Will be determined. If the high resolution image data is recorded in the HD recording mode, the letter “H” is printed. If the high resolution image data is recorded in the UD recording mode, the letter “U” is printed.

  In the above-described example, the image directory number, the image number, and the data relating to the recording mode are printed as the related information data. However, the image individual unit information and link information recorded in the image information unit are not limited to these data. Also, data such as keyword search data numbers can be easily recorded.

  When all the related information data is printed in step S205, the process proceeds to step S206.

  In step S206, it is determined whether medium / low resolution image data has been created from all the intermediate resolution image data. Specifically, the directory number recorded in the general information management file in the RAM 6a and the image number recorded in the image data management file are referred to. At this time, if the directory number is the last number and the image number is the last number, it is determined that medium / low resolution image data has been created from all the intermediate resolution image data, and the process proceeds to step S208. move on. If the directory number is not the last number or the image number is not the last number, it is determined that there is still intermediate resolution image data that has not been searched, and the process proceeds to step S207.

  In step S207, the system controller 6 specifies the next intermediate resolution file after the intermediate resolution file specified in step S202. Specifically, an intermediate resolution image file having an image number obtained by incrementing the image number specified in step S202 is specified. If the incremented image number does not exist, it is determined that there is no intermediate resolution image file in the image directory, and the intermediate resolution image file having the smallest image number in the next image directory is designated. In the example of the file structure shown in FIG. 19, “PSN00001.PMP” is designated as the file next to the “PSN00000.PMP” file designated in step S202. When the next file name is designated by the system controller 6, the process returns to step S203.

  Steps S203 → Step S204 → Step S205 → Step S206 → Step S207 → Step S203 are repeated until intermediate / low resolution image data is created from all intermediate resolution image data. When the resolution image data is generated, the process proceeds to step S208.

  In step S208, all the medium and low resolution image data stored in the main memory 11a and the template image previously recorded in the system controller 6 are combined. This template image data is image data composed of image data indicating the cut line 41 and image data indicating characters such as “PICTURE MDINDEX”.

  In step S209, the system controller 6 controls the image processing controller 14 to transfer the image data stored in the main memory 11a to the printer unit 2.

  In step S210, the system controller 6 controls to convert the image data transferred to the printer unit 2 into YMC data and print it out, and the process ends.

  Next, the low resolution print mode will be described. That is, when the low resolution mode is designated in step S201, the process proceeds to step S211.

  In step S211, the index image file is searched. More specifically, the system controller 6 refers to the directory number of the image directory information unit provided for the number of image directories in the general information management file stored in the RAM 6a, so that the image directory and the index image file are stored. Is specified. The designated image directory is the directory with the smallest directory number “mmmmm”. In the example of the file structure shown in FIG. 19, “PIC00000” is designated. The index image file is designated as the file with the smallest index number “nnn” in the designated directory. Therefore, in the example of the file structure shown in FIG. 19, “PINDX000.PMX” is designated. When the index image file is designated by the system controller 6, the process proceeds to step S212.

  In step S212, the system controller 6 controls the storage controller 5d to search and read the index image file designated in step S211 on the disk. The file search operation is performed in accordance with the operation flow of FIG. 38 described in the section “Searching for Files and Image Directories”. A plurality of low-resolution image data (index image data) included in the index image file read from the storage unit 5 is composed of N headers and N index image data as shown in FIG. It is configured. As already described, the index image data has a resolution of 60 pixels × 80 pixels. The N pieces of index image data are JPEG-decompressed by referring to the header, and are sequentially stored in the main memory 11a of the image processing block 3. When the reading of the N pieces of index image data is completed in step S212, the process proceeds to step S213.

  In step S213, related information data is combined with the N index image data stored in the memory 11a. Since this related information data is the same data as the related information data described in step S205, the description thereof is omitted. However, in the description of step S205, one piece of related information data is obtained every time one intermediate resolution image file is designated. In step S213, each time one index image file is designated, N pieces of related information data are obtained so as to correspond to N pieces of index images included in the index image file.

  Hereinafter, how to obtain N pieces of related information data will be described in detail. As shown in FIG. 25, N image information units are stored in the image data management file stored in the RAM 6a. Each of the N image information units stores data relating to a directory number, an image number, and image type information. Accordingly, N directory numbers, N image numbers, and N images are referred to by referring to the N image information units of the image data management file existing in the image directory that includes the index image file specified in step S211. Image type information can be obtained. The obtained N pieces of related information data are stored in the main memory 11a in association with the N pieces of index image data stored in the main memory 11a. As described above, the storage order of the N image information units stored in the image data management file is the same as the storage order of the N index image data stored in the index image file. , It is easy to associate N pieces of related information with N pieces of index image data.

  When N pieces of related information data are stored in the main memory 11a in step S213, the process proceeds to step S214.

  In step S214, it is determined whether all index image files have been read from the disc. Specifically, the directory number of the general information management file and the next image index file number in the image data management file stored in the RAM 6a are referred to. At this time, if the directory number is the last number and the next image index file number is the last number, it is determined that all index image files have been read from the disk, and the process proceeds to step S216. move on. If the directory number is not the last number, or if the image number is not the last number, it is determined that there are still unspecified index image files, and the process proceeds to step S215.

  In step S215, the system controller 6 designates the second index image file that is the next file after the first index image file designated in step S211. Specifically, an index image file having a file number obtained by incrementing the file number designated in step S211 is designated. If the incremented index image file does not exist, it is determined that there is no further index image file in the image directory, and the index image file with the smallest file number in the next image directory is designated. In the example of the file structure shown in FIG. 19, the file next to the file “PINDX000.PMX” specified in step S211 does not exist in the image directory “PIC00000”. Therefore, the first index image file “PINDX000.PMX” in the next image directory “PIC00001” is designated. Thus, when the second index image file name is designated by the system controller 6, the process returns to step S212.

  A case will be described in which the second index image file is read from the disk in step S212 and M index image data included in the second index image file is stored in the main memory 11a. When the second index image file is specified in step S215, the N index image data read from the first index image file are already stored in the main memory 11a. Therefore, the M index image data newly read from the disc are the N indexes stored previously as the (N + 1, N + 2, N + 3, N + 4,..., N + M) th index image data. It is stored in the main memory 11a so as to be arranged after the image data. Similarly, the index image data read from the second and subsequent index image files are stored in the main memory 11a so as to be arranged after the previously stored index image data.

  Steps S212, S213, S214, S215, and S212 are repeated until all index image files are read, and when all index image files are read, all indexes are stored in the main memory 11a. Image data is stored continuously.

  In step S216, all index image data stored in the main memory 11a and template image data stored in advance in the system controller 6 are combined. The template image data is image data including image data indicating the cut line 41, image data, and image data indicating characters such as “PICTURE MD INDEX”.

  In step S217, the system controller 6 converts the image data transferred to the printer unit 2 into YMC data, and controls to print out, and the process ends.

  In this low-resolution mode, after the index image data of 60 pixels × 80 pixels obtained from the index image file is transferred to the printing unit 2, interpolation processing is performed on 192 pixels × 256 pixels as shown in FIG. It is also possible to increase the amount of data.

  Further, the second index printing operation will be described with reference to the operation flow shown in FIG.

  This second index printing operation is an operation when printing the index card of the second embodiment shown in FIG.

  The operational difference between the first index card print and the second index card print is that the file designation steps are different. That is, step S202 and step S207 are different in the high resolution mode, and step S211 and step S215 are different in the low resolution mode. The reason why the file designation method is different will be described below.

  Only one index card 80 of the second embodiment can be put in the cassette case 60. Further, since the size of the index card 80 is limited, it is impossible to print all the index image data on the disc on the index card 80. Therefore, it is desirable to print only representative image data on the index card 80 from the image data recorded on the disc. Therefore, the first index card print that designates all index image data differs from the second index card print that designates only representative image data in a file designation method. The steps different from the first index card printing will be described below, and the description of the same steps as the first index card printing will be omitted.

In steps S202 and S207, an intermediate resolution image file is designated. This intermediate resolution image file is designated based on N image directory information units in the general information management file “OV_INF.PMF”. In the N image directory information units, data related to the N index image data recorded in the general index file “OV_INX.PMF” is recorded. As described above, in this general index file “OV_INX.PMF”, n (one in the embodiment) index image data in the order of decreasing image number in each image directory is stored for each image directory. It is remembered. Further, as shown in FIG. 24, a directory number and an index image number are recorded in each of the N image directory information units. That is, by referring to the N image directory information units, the directory number and the index image number related to the N index image data recorded in the general index file “OV_INX.PMF” can be obtained. Accordingly, in step S202 and step S207, N pieces of intermediate resolution image data are sequentially specified based on the N pieces of image directory information units.
In steps S211 and S215, it is only necessary to specify the general index file “OV_INX.PMF” and read out the N pieces of index image data recorded in this file.

  Other steps are the same as those of the first index card print.

  The image data recorded on the disc can be easily grasped by printing the image data recorded on the disc on the index card mounted on the cassette case for storing the disc.

  In addition, by forming print image data in which a plurality of index image data printed on the index card is combined with processing information used to process the index card for inserting the index card into the cassette case, the index card is formed. Can be easily created.

  In addition, since the directory number and index image number are printed together with the index image data printed on the index card, the user's desired image is recorded at what number in which directory simply by looking at the index card. You can figure out what is being done. Therefore, it is possible to specify a directory number and an index image number by simply looking at this index card without searching a directory in which a desired image data is recorded by mounting a disc on a recording / reproducing apparatus. The image can be reproduced, and the search operation can be simplified.

  Also, by selecting the above two modes, an index card desired by the user can be created.

  When the high resolution mode is selected, medium- and low-resolution image data having a resolution higher than that of the index image data is printed as print image data, so that a high-quality index card can be created. When index printing is performed in this high resolution mode, medium / low resolution image data generated from intermediate resolution image data is selected as print image data in accordance with the print resolution of the printer unit 2, so that the printer unit 2 High-resolution index printing can be performed.

  When the low resolution mode is selected, the index image data stored in the index image file created for displaying the index image data on the monitor is printed as print image data. Index printing can be performed quickly without compositing.

  Also, since the index image data (or medium / low resolution image data) printed on the index card is synthesized with related information data related to the high resolution image data associated with the index image data, the user can It is possible to obtain information on high-resolution data simply by looking at. Further, since the related information data is recorded in the image data management file stored in the RAM 6a in the system controller 6, the high-resolution image file including the associated high-resolution image data is searched without being searched. Information about resolution data can be obtained. That is, since the related information data regarding all the high resolution image data can be obtained from the RAM 6a without accessing the disk, the print image data to be printed on the index card can be quickly formed.

1 is a block diagram of a still image filing system to which the present invention is applied. FIG. It is a block diagram of a scanner unit provided in the still image filing system. FIG. 3 is a block diagram of a printer unit provided in the still image filing system. It is a block diagram of the image processing block provided in the said still image filing system. It is a block diagram of a thinning and compression / decompression block provided in the still image filing system. It is a block diagram of a storage unit provided in the still image filing system. It is a block diagram of a video input unit provided in the still image filing system. It is a figure for demonstrating the data structure of the image data recorded on the said optical disk. It is a figure for demonstrating the management block formed in data U-TOC. It is a figure for demonstrating the sector structure of a volume descriptor. It is a figure for demonstrating the sector structure of a volume space bitmap. It is a figure for demonstrating the structure of an allocation block. It is a figure for demonstrating the sector structure of a management table. It is a figure for demonstrating each data recorded on a management table. It is a figure for demonstrating the sector structure of the directory record for directories. It is a figure for demonstrating the sector structure of the directory record for files. It is a figure for demonstrating the sector structure of an extent record block. It is a figure for demonstrating each resolution of image data in the said still image filing system. It is a figure for demonstrating the hierarchical directory structure for managing the image data for every resolution in the said still image filing system. It is a figure for demonstrating DRB and ERB which comprise the said management block. It is a figure for demonstrating the structure of ERB which comprises the said management block. It is a figure for demonstrating the format table in the said hierarchical directory structure. It is a figure for demonstrating the image parameter table in the said hierarchical directory structure. It is a figure for demonstrating the comprehensive information management file in the said hierarchical directory structure. It is a figure for demonstrating the image data management file in the said hierarchical directory structure. It is a figure for demonstrating the print data management file in the said hierarchical directory structure. It is a figure for demonstrating the image data file in the said hierarchical directory structure. It is a figure for demonstrating the comprehensive index file in the said hierarchical directory structure. It is a figure for demonstrating the image index file in the said hierarchical directory structure. It is a figure for demonstrating the print data file in the said hierarchical directory structure. It is a figure for demonstrating the print control data which are the data contents of the print information unit contained in the said print data file. It is a flowchart for demonstrating the recording operation of the first half in the said still image filing system. It is a flowchart for demonstrating the recording operation | movement of the latter half in the said still image filing system. It is a flowchart for demonstrating the recording operation | movement of the image data for every resolution in the said still image filing system. It is a flowchart for demonstrating the formation operation | movement of the first half of the comprehensive index file in the said still image filing system. It is a flowchart for demonstrating the formation operation | movement of the latter half of the comprehensive index file in the said still image filing system. It is a flowchart for demonstrating reproduction | regeneration operation | movement in the said still image filing system. It is a flowchart for demonstrating the search operation | movement of the designated image data in the said still image filing system. It is a flowchart for demonstrating the edit operation | movement of the image data in the said still image filing system. It is a top view of the index card printed with the said still image filing system. It is a perspective view which shows the structure of the cassette case which accommodates an index card with a disk cassette. It is a top view of the other index card printed with the said still image filing system. FIG. 43 is a perspective view for explaining a storage state of the index card shown in FIG. 42 in a cassette case. It is a top view of the disc cassette which affixed the disc label produced with the said still image filing system. FIG. 43 is a flowchart for explaining an operation of printing the index card shown in FIG. 42. FIG. It is a figure which shows the image process which produces | generates medium low-resolution image data of 256 pixels x 192 pixels from the intermediate resolution image data which has 640 pixel x 480 pixel data. It is a figure which shows the interpolation process to 192 pixels x 256 pixels in a low resolution mode.

Explanation of symbols

  1 scanner unit, 1a CCD image sensor, 1b A / D converter, 1c correction unit, 1d interface, 2 printer unit, 2a interface, 2b data conversion circuit, 2c thermal head, 2d printer paper 2d, 3 image processing block, 4 Decimation compression / decompression block, 4a interface, 4b buffer, 4c 1/4 decimation circuit, 4d buffer, 4e 1/60 decimation circuit, 4f selector, 4g raster-block conversion circuit, 4h compression / decompression circuit, 4i decimation, compression / decompression controller, 5 storage unit, 5a interface, 5b EFM circuit, 5c disk recording / playback unit, 5d storage unit controller, 6 system controller, 6a RAM, 7 bus line, 8 video input unit, 8a-8c input terminal, 8 Video processing unit, 8e A / D converter, 9 monitor device, 10 operation unit, 11 frame memory, 11a main memory, 11b video memory, 12 image processing circuit, 13 a memory controller, 14 an image processing controller, 15 interface, 20 optical disc

Claims (10)

Read means for reading out image data of a plurality of resolutions from the recording medium, management data indicating the relationship between the image data,
Image forming means for forming print image data based on the image data read by the reading means;
Printing means for printing the print image data formed by the image forming means on an index card;
Control means for controlling the reading means, the image forming means and the printing means so that the image data can be listed by an index card on which the print image data is printed,
The control means has a hierarchical directory structure including a main directory and a plurality of image directories formed as subdirectories in the main directory, and includes first management data formed in the main directory; The management data composed of the second management data formed in the plurality of image directories, the image data having the first resolution, and the second resolution lower than the first resolution. Controlling the reading means so as to read the image data having the first resolution or the image data having the second resolution based on the information included in the management data from the recording medium having the image data. From the read image data having the first resolution or the image data having the second resolution. Controlling said image forming means to form a press image data, to perform the Intex printing the print image data described above formed by printing on the index card in the first resolution or the second resolution An image data printing apparatus for controlling the printing means .   The control means includes an intermediate resolution image file including intermediate resolution image data having the first resolution, an index image file including a plurality of index image data having the second resolution, and a third The management data indicating the relationship among the high resolution image data, the intermediate resolution image data, and the index image data from a recording medium having a high resolution image file including high resolution image data having resolution. Based on the intermediate resolution image data read by the reading means, the reading means is controlled to read the intermediate resolution image data included in the intermediate resolution image file or the index image data included in the index image file. Or print image data from index image data Image data printing apparatus according to claim 1, wherein the controlling the image forming means so as to formed.   2. The image data printing apparatus according to claim 1, wherein the control means includes storage means for temporarily storing the management data recorded on the recording medium.   The control means includes the storage means as information included in the management data from a recording medium in which general information management data is formed as the first management data and image data management data is formed as the second management data. The intermediate resolution image file or index image file read by the reading means is designated by referring to the image directory number and the image number included in the image data management data stored in the image data, and the designated intermediate resolution image file 4. The image data printing apparatus according to claim 3, wherein the reading unit is controlled to read intermediate resolution image data or index image data from an index image file.   The control means includes the storage means as information included in the management data from a recording medium in which general information management data is formed as the first management data and image data management data is formed as the second management data. The intermediate resolution image file or the index image file is designated in ascending order of the image directory number or image number by referring to the information of the plurality of image information units included in the image data management data stored in 4. The reading unit is controlled to read intermediate resolution image data or a plurality of index image data from all intermediate resolution image files or all index image files recorded on a recording medium. Image data printing device.   The control means controls the image forming means so that processing information used when processing for storing the index card in a storage case of the recording medium is combined with the index image data. The image data printing apparatus according to claim 2.   7. The image data printing apparatus according to claim 6, wherein the processing information is a cut line for cutting the index card from a print medium.   The control means includes an intermediate resolution image file including intermediate resolution image data having the first resolution, an index image file including a plurality of index image data having the second resolution, and a third The intermediate resolution image data included in the intermediate resolution image file is read by the reading means from the recording medium having the management data having the high resolution image file including the high resolution image data having the resolution. A first print image data forming mode for forming first print image data from the intermediate resolution image data by the image forming means, and a plurality of index image data included in the index image file are read by the reading means, and the reading is performed. From the index image data that has been output, the image forming means Image data printing apparatus according to claim 1, further comprising a selection means for selecting one of the modes of the second print image data forming mode for forming the print image data.   9. The image data printing apparatus according to claim 8, wherein the first print image data is composed of image data having a resolution higher than that of the second print image data. A reading step of reading out image data of a plurality of resolutions from the recording medium, information data indicating a relationship between the image data,
Forming print image data based on the image data read by the reading step;
A printing step of printing on the index card the print image data formed by the step of forming the print image data;
The reading step, the step of forming the print image data, and the control step of controlling the printing step so that the image data can be listed by the index card on which the print image data is printed,
The control step has a hierarchical directory structure including a main directory and a plurality of image directories formed as subdirectories in the main directory, and includes first management data formed in the main directory; The management data composed of the second management data formed in the plurality of image directories, the image data having the first resolution, and the second resolution lower than the first resolution. Controlling reading means so as to read the image data having the first resolution or the image data having the second resolution from the recording medium having the image data based on the information included in the management data; Marked from the read image data having the first resolution or the image data having the second resolution. Image data forming the image data printing and controls to perform Intex printing in the first resolution or the second resolution by printing the print image data described above formed on index card Method.

Images