JP4510686B2 - IMAGING DEVICE AND IMAGING DEVICE CONTROL METHOD - Google Patents

Description

  The present invention relates to an imaging apparatus, a control method for the imaging apparatus, a computer program, and a recording medium, and more particularly to a technique suitable for taking a still image during moving image shooting.

  In recent years, digital cameras having a moving image shooting function in addition to a still image shooting function have been proposed. Such a digital camera has a function of recording moving image data in an external recording medium such as a CF (registered trademark: Compact Flash) card in a video format such as AVI (Audio Video Interleaving). In addition, some digital cameras have been proposed that perform still image shooting simultaneously with moving image shooting.

  Further, the following technologies have been proposed as techniques for acquiring still images during moving image shooting related to digital cameras. For example, the imaging device described in Patent Document 1 has a function of storing still image data simultaneously acquired during moving image shooting in a still image buffer and constructing it as a still image file after moving image shooting ends. Proposed. In the imaging device described in Patent Document 2, when still image shooting is performed simultaneously with moving image shooting, the acquired still image data is resized and applied as one frame of moving image data, and as a still image file. Those having a function to construct have been proposed.

Japanese Patent Application Laid-Open No. 08-331496 JP 2003-219341 A

  However, when the moving image data and the still image data are recorded in one file, there are the following problems when the conventional technique is used. For example, in the case of the imaging device described in Patent Document 1, if the still image buffer size of the digital camera is used up, there is a problem that it becomes impossible to capture still images thereafter. In addition, in the case of the imaging device described in Patent Document 2, if the processing of still image shooting is performed intensively during moving image shooting, processing for writing a file of still image data continuously occurs. There was a possibility that sufficient bandwidth for writing data could not be obtained, resulting in dropped frames and interruption of moving image shooting.

  In view of the above-described problems, an object of the present invention is to enable efficient writing of still image data simultaneously acquired during moving image shooting to a file.

Imaging apparatus of the present invention, a moving image photographing means for performing moving image shooting, a still image photographing means capable of performing still image shooting during due Videotaping the moving image shooting means, before Kisei Tomega photographing means storing still image data captured, the still image storing means for storing the still image buffer, a video storage means for storing moving image data captured by the kinematic Well shadow means video buffer, in the still image buffer by Recording control means for selectively recording the divided still image data divided from the still image data and the moving image data for a predetermined time stored in the moving image buffer on a recording medium, and the moving image data for the predetermined time Determining means for determining the data size of the divided still image data based on the time required for the image to be captured by the moving image capturing means and the recording speed of the data on the recording medium. The recording control means, the division still picture data of size corresponding to the data size determined by said determining means, and recording on the recording medium.

Control method for an imaging apparatus of the present invention, a moving image photographing step of performing moving image shooting, a still image photographing process capable of performing still image shooting during moving image shooting by the video recording process, before Kisei Tomega shooting storing still image data captured by the process and the still image storing step of storing in the still image buffer, a video storage step of storing the moving image data captured by the kinematic Well shadow process video buffer, in the still image buffer A recording control step of selectively recording the divided still image data divided from the still image data and the moving image data for a predetermined time stored in the moving image buffer on a recording medium; and the moving image data for the predetermined time Determining step of determining a data size of the divided still image data based on a time required for shooting in the moving image shooting step and a recording speed of data on the recording medium Has the recording control step, the division still picture data of size corresponding to the data size determined by said determining step, and recording on the recording medium.

Computer program of the present invention, a moving image photographing step of performing moving image shooting, a still image photographing process capable of performing still image shooting during due Videotaping the moving image shooting process, before Kisei Tomega photographing step stored still image data captured still image storing step of storing in the still image buffer, a video storage step of storing the moving image data captured by the kinematic Well shadow process video buffer, in the still image buffer by A recording control step for selectively recording the divided still image data divided from the still image data and the moving image data for a predetermined time stored in the moving image buffer on a recording medium, and the moving image data for the predetermined time Determination of determining the data size of the divided still image data based on the time required for shooting in the moving image shooting process and the recording speed of the data on the recording medium A computer program for executing the extent to the computer, the recording control step, characterized in that the division still picture data of size corresponding to the data size determined by said determining step, recording on the recording medium And

  The recording medium of the present invention describes the computer program described above.

According to the present invention, it is possible to realize an efficient write process with a reduced time zone during which no data write process is performed.

  In addition, according to another feature of the present invention, the video recording time and the number of still images that can be captured can be displayed during shooting, so that the user can check the number of still images that can be captured as time passes. be able to.

  According to another feature of the present invention, when a file in which moving image data and still image data are mixed is reproduced, the fact that the file is a mixture of moving image data and still image data is displayed on the display means. Thus, the user can easily select a file in which moving image data and still image data are mixed.

  According to another feature of the present invention, a file in which moving image data and still image data are mixed can be created as a file that can be reproduced as a moving image, so that data can be efficiently written to the file. it can.

  According to another feature of the present invention, since the recording area of still image data can be handled in cluster units, separation of still image files is realized by changing the cluster chain without moving data within the file, The time required for separating still image files can be greatly improved.

  According to another feature of the present invention, when still image shooting is performed during moving image shooting, the file data size can be reduced as compared to recording still image data including header information and thumbnail information. Now that you can, you can shoot a larger number of still image files.

(First embodiment)
Hereinafter, embodiments of an imaging apparatus for recording moving image data and still image data in one file and a method for separating still image files according to the present invention will be described with reference to the drawings.
FIG. 1 is a block diagram illustrating an example of an imaging apparatus that records the imaging data in a file format according to the present embodiment.

  In FIG. 1, reference numeral 101 denotes a lens that forms a subject image (not shown). Reference numeral 102 denotes an aperture mechanism that adjusts the amount of incident light from the lens 101. An image sensor 103 converts an optical signal incident from the lens 101 through the diaphragm mechanism 102 into an electric signal. An analog / digital converter (A / D converter) 104 converts an analog signal from the image sensor 103 into a digital signal. A camera signal processing circuit 105 performs processing such as white balance (WB) set on the digital signal of the A / D converter 104.

  An image compression circuit 106 compresses image data using a compression algorithm such as JPEG. An internal storage device (RAM) 107 includes a moving image buffer area for moving image data and a still image buffer area for still images, and temporarily stores data output from the camera signal processing circuit 105 during shooting. To do.

  A controller 108 controls each circuit of the apparatus according to software recorded in a memory (ROM) (not shown). Reference numeral 109 denotes a recording medium, such as a memory card or disk that stores data temporarily stored in the RAM 107 in a file format. A write processing unit 110 writes data to the external recording medium 109. In the present embodiment, recording is performed on the external recording medium 109 in a file format in which moving image data and still image data are mixed.

  As this external recording medium 109, a CF (Compact Flash) card is used. In the present embodiment, it is assumed that the storage area of the external recording medium 109 has 512 bytes as one sector and a logical block address (LBA (Logical Block Address)) is assigned to each sector.

  A FAT (File Allocation Table) is used for the file system, and data is managed in units of clusters composed of a plurality of sectors. In addition, recording when shooting a still image during moving image recording is performed in a file format compliant with RIFF (Resource Interchange File Format).

FIG. 2 is a diagram illustrating an example of a front surface and a back surface of the imaging apparatus according to the present embodiment.
In FIG. 2, a moving image shooting SW 201 is a switch provided for moving image shooting, and starts moving image shooting preparation when pressed halfway and starts moving image shooting when pressed fully. Still image shooting SW 202 is a switch provided for still image shooting. In the present embodiment, the moving image shooting SW 201 and each function that operates according to the moving image shooting SW 201 are referred to as moving image shooting means. The still image shooting SW 202 and each function that operates in accordance with the still image shooting SW 202 are referred to as a moving image still image shooting unit.

  Reference numeral 203 denotes a lens barrel. Reference numeral 204 denotes a mode switch, which may be provided with a moving image / still image shooting mode, or may be set to enable still image shooting in the moving image shooting mode. A cross key button 205 is used to operate a menu displayed on the monitor. A menu button 206 is used to activate an application provided in the imaging apparatus.

  Reference numeral 207 denotes a determination button, and 208 denotes a cancel button. Both of these buttons 207 and 208 are used to operate a menu displayed on the monitor. Reference numeral 209 denotes a monitor, which displays shooting results and menus.

FIG. 3 is a diagram illustrating an example of an operation image when the moving image shooting and the still image shooting are simultaneously performed using the imaging apparatus according to the present embodiment illustrated in FIG. 2.
In FIG. 3, reference numeral 301 denotes a monitor that displays a subject being shot. Reference numeral 302 denotes a moving image icon indicating that moving image shooting is in progress. Reference numeral 303 denotes an elapsed time icon indicating the elapsed time of moving image shooting.

  A number icon 304 indicates the number of still images that can be shot, and displays the smaller of the number of shots that can be taken from the still image buffer size and the number of shots that can be shot on the storage medium. In the former case, if a still image shooting interval is set, data processing in the buffer is performed, and the number of shots that can be shot increases. Therefore, in the present embodiment, the user can identify which situation is present, such as changing the display color between the former case and the latter case. Reference numeral 305 denotes a still image shooting switch. If the remaining number of shots is not zero with the number icon 304, still image shooting is performed.

FIG. 4 is a diagram illustrating an example of an image when moving image data and still image data are recorded in a file in the imaging apparatus according to the present embodiment.
In FIG. 4, a moving image buffer 401 and a still image buffer 402 are internal memory areas of the imaging apparatus and exist in the internal storage device (RAM) 107.

  The moving image buffer 401 stores moving image data composed of audio data 403 and video frame data 404. The still image buffer 402 stores still image data. In the present embodiment, it is assumed that still image data is stored in an Exif format composed of a header portion 405, a body portion 406, and a thumbnail portion 407.

  A RIFF (Resource Interchange File Format) file 408 is a file that records a mixture of moving image data and still image data. The RIFF file format is a file format for managing various resources in one file. The RIFF file format features a structure that maintains basic structure compatibility even when new format resources are created. The RIFF file used in this embodiment includes a header part 409, a data part 410, a moving image INDEX part 411, and a still picture INDEX part 412.

  Reference numeral 413 denotes moving image data, which is recorded in the RIFF file 408 from the moving image buffer 401. Reference numeral 414 denotes still image data, which is recorded in the RIFF file 408 from the still image buffer 402.

FIG. 5 is a diagram illustrating an example of a hierarchical chunk structure of a general RIFF file format.
In FIG. 5, the RIFF file format has a RIFF chunk 501, a LIST chunk 502, and a sub chunk 503 as constituent elements, and each chunk has an ID portion 504, a size portion 505, and a data portion 506.

  The ID portion 504 is a 4-byte area (FOURCC code) for identifying the chunk type. If it is a RIFF chunk, a form type (for example, 'AVI' chunk 701 in FIG. 7) is stored, and if it is a LIST chunk, a list type (for example, 'movi' chunk 704 in FIG. 7) is stored. The size portion 505 is a 4-byte area indicating the chunk data size.

  The data portion 506 stores data or chunks to be hierarchized. An arbitrary LIST chunk and sub chunk can be stored here. With this structure, the RIFF file can obtain target data by sequentially searching for ID, size, and type.

FIG. 6 is a diagram showing an example of a chunk structure in the RIFF file format obtained by extending the AVI file used in the present embodiment.
In FIG. 6, the form type of RIFF chunk 601 is 'AVI', and below this, LIST (hdrl) chunk 602 (list type 'hdrl'), dummy sub chunk 603 (type 'JUNK'), and LIST (movi) chunk 604 There are blocks of (list type 'movi'), moving image index sub-chunk (idx1) 605 (type 'idx1'), and still image index sub-chunk (idxP) 606 (type 'idxP').

  The LIST (hdrl) chunk 602 records the header portion of the AVI file, and has an 'avih' sub-chunk 607, a 'strl' sub-chunk 608, and the like. The 'avih' sub chunk 607 stores a structure (AVIMAINHEADER) that manages information on the entire AVI file. The 'strl' sub chunk 608 stores a structure (AVISTREAMHEADER) that manages stream information and a structure (BITMAPINFO WAVEFORMATEX) that manages video frame data, audio data, and the like.

  In the JUNK sub chunk 603, dummy data is recorded in order to align the data storage area with the cluster boundary of the file system. The LIST (movi) chunk 604 stores audio data 609 and video frame data 610 that constitute a captured moving image. Further, in the LIST (movi) chunk 604 of the present embodiment, a still image data chunk 611 is recorded in a non-recognized area as a moving image file.

  The still image data chunk 611 may be divided into a plurality of chunks and recorded even in the same still image file data. In the moving image index sub-chunk (idx1) 605, information on the data position, data size, and reproduction data order of the audio data 609 and video frame data 610 stored in the LIST (movi) chunk 604 is recorded.

  In the still image index sub-chunk (idxP) 606, an attribute information table 612 for the still image data chunk 611 is recorded.

  The attribute information table 612 manages still image file number information 613 and data recording position and data size information 614 of the still image data chunk corresponding to the file number. As the data recording position, for example, an offset value from the LIST (movi) chunk 604 is used.

FIG. 7 is a diagram illustrating an example of a case where still image data is recorded by the recording method of the present embodiment, and an example of a result of a recording state.
In FIG. 7, the data head portion 701 indicates the head of the LIST (movi) chunk 604. The moving image data 702 indicates moving image data composed of audio data chunks or video frame data chunks.

  A cluster boundary 703 indicates a cluster boundary of the FAT file system used in this embodiment. The recording data is managed in cluster units (for example, if one cluster is 128 sectors and one sector is 512 bytes, the area size is 64 Kbytes). However, since the size of moving image data is not conscious of the sector / cluster unit, the head of each moving image data does not coincide with the cluster boundary in most cases.

  The first still image data A704 and the second still image data A705 indicate data chunks obtained by dividing and recording data of one still image file. The data size of the still image data A 704 and 705 is set to an integral multiple of the cluster size.

  The dummy data 706 indicates dummy data to be recorded in a non-recording area in the cluster area immediately before recording still image data. Thereby, the recording position of the still image data can be adjusted to the cluster boundary. The dummy data 706 is also dummy data for aligning the recording position of the moving image data after recording the still image data with the cluster boundary.

  If still image data is recorded as described above, separation of still image files can be realized by switching cluster chains by operating a FAT table.

  A method of writing data from the moving image buffer and the still image buffer for realizing the recording state described above will be described. In this embodiment, after writing data of moving image data for a certain number of seconds (hereinafter referred to as a moving image writing unit), writing of still image data of a certain size (hereinafter referred to as a still image writing unit) is performed. Do.

In the present embodiment, it is assumed that there is already a data recording history for the medium and the data writing speed is known. Therefore, the still image writing unit data size is calculated as follows from the maximum data size (worst value) that can be taken by the statically determined moving image writing unit data, the moving image data writing interval, and the data writing speed.
(Still image writing unit data size [byte])
= (Movie data writing interval [sec]) * (Writing speed [byte / sec])-(Maximum data size [byte] of movie writing unit).

FIG. 8 is a block diagram illustrating a configuration example of the write processing unit 110.
In FIG. 8, an input key controller 801 processes an input event from a moving image shooting button, a still image shooting button, or the like, and notifies the shooting task 802 of the input event. The shooting task 802 controls the moving image shooting controller 803 and the still image shooting controller 804. At the start of shooting, the moving image buffer 805, the still image buffer 806, the index buffer 807, the moving image buffer monitoring task 808, and the writing task 809 are initialized. At the end of shooting, the buffer task is instructed to the writing task 809.

  The moving image shooting controller 803 receives an instruction from the shooting task 802 and performs signal processing by moving image shooting. Audio data and video frame data obtained by the signal processing are stored in the moving image buffer 805, and an audio data generation completion event and a video frame data generation completion event are notified to the moving image buffer monitoring task 808.

  The still image shooting controller 804 receives an instruction from the shooting task 802 and performs signal processing by still image shooting. Still image data obtained by this signal processing is stored in the still image buffer 806. The moving image buffer 805 stores moving image data generated by the moving image shooting controller 803. The still image buffer 806 stores still image data generated by the still image capturing controller 804.

  The index buffer 807 stores attribute information such as the data position and size of the moving image data chunk and the still image data chunk written by the writing task 809. The moving image buffer monitoring task 808 checks the moving image buffer 805 in response to a data generation completion event from the moving image shooting controller 803. If there is a certain number of frames of data in the moving image buffer, the writing task 809 is notified of a moving image data write request event.

  The write task 809 receives a moving image data write request event from the moving image buffer monitoring task 808 and performs chunk data writing processing of moving image data and still image data to the file system 810. The index information regarding the written data chunk is stored in the index buffer 807. This index information is referred to when creating a moving image index portion and a still image index portion, which are constituent elements of a file, at the end of shooting. In the file system 810, a file writing process is performed.

Next, a series of moving image data / still image data write processing procedures according to the present embodiment will be described with reference to the flowcharts of FIGS. 9-1 to 9-6.
FIG. 9A is a flowchart illustrating an example of the procedure of the simultaneous shooting process of the moving image / still image of the shooting task 802.
In FIG. 9A, step S101 is a shooting wait state waiting for shooting by the user. In step S102, a moving image shooting preparation key event is received from the input key controller 801.

  In step S103, the free space of the media at the time of shooting is checked. In step S104, a focus fixing process (AF process) is performed. If the focus is fixed, the process proceeds to step S105. Step S105 is a moving image shooting preparation state in which moving image shooting preparation is performed.

  In step S106, a moving image shooting start key event is received from the input key controller 801. In step S107, the moving image buffer 805, the still image buffer 806, and the index buffer 807 are initialized.

  In step S108, the write task 809 is notified of the initialization event. In step S109, the moving image capturing controller 803 is controlled to start moving image capture. In step S110, the initialization event is notified to the moving image buffer monitoring task 808, and the process proceeds to step S111.

  Step S111 is a moving image shooting state in which moving image shooting is performed. In step S112, it is checked whether moving image shooting is continued. If the result of this check is that movie shooting is to continue, the process proceeds to step S113, and a still image shooting key event is received from the input key controller 801 in the movie shooting state.

  In step S114, it is checked whether the still image buffer 806 has a free area for taking a still image. As a result of this check, if there is an empty area, the process proceeds to step S115, the still image capturing controller 804 is controlled to start still image capture, and the process proceeds to step S111. On the other hand, if the result of the check in step S114 is that there is no free space, the process proceeds to step S116, a warning is displayed that still image shooting cannot be performed because there is no free space in the still image buffer, and the flow proceeds to step S111.

  If the result of the check in step S112 is that movie shooting is not continued, the process proceeds to step S117, and a movie shooting end key event is received from the input key controller 801 in the movie shooting state. In step S118, the moving image capturing controller 803 is controlled to end the moving image capture. Thereafter, the process proceeds to step S119, a buffer flush instruction event is notified to the write task 809, and the process proceeds to step S101.

FIG. 9-2 is a flowchart illustrating an example of a processing procedure of the moving image buffer monitoring task 808.
In FIG. 9B, step S201 is in a task initialization waiting state. When the initialization process is started, the process proceeds to step S202, and when a moving image buffer monitoring task initialization event is received, the process proceeds to step S203, where the moving image shooting controller 803 waits for the generation of moving image writing unit data. It becomes.

  When the moving image writing unit data generation process is started, the process proceeds to step S204, where a video frame data generation completion event and an audio data generation completion event are received from the moving image capturing controller 803.

  In step S205, it is checked whether moving image writing unit data is stored in the buffer. As a result of this check, if there is unit data, the process proceeds to step S206, where the writing task 809 is notified of the moving image data write request event, and then the state transitions to the state of step S203. On the other hand, if there is no unit data as a result of the check in step S205, the process jumps to step S206 and directly transitions to the state in step S203.

FIG. 9C is a flowchart illustrating an example of the processing procedure of the write task 809.
In FIG. 9C, step S301 is in a task initialization waiting state.
When the task initialization process is started, a writing task initialization event is received from the shooting task 802 in step S302. In step S303, the write task is initialized. This initialization process will be described in detail later with reference to the flowchart of FIG. 9-6. The next step S304 is a write wait state.

  If writing has been performed, the process proceeds to step S305, where it is checked whether or not moving image shooting is in progress. If the result of this check is that moving image shooting is in progress, the process advances to step S 306 to receive a moving image data write request event from the writing task 809. In the present embodiment, it is assumed that the video data is written first. In step S307, the number of frames in the moving image writing unit is designated and moving image data writing processing is performed. The moving image data writing process will be described in detail later with reference to the flowchart of FIG. 9-4.

  In step S308, it is checked whether there is data in the still image buffer 806. If there is no data as a result of this check, the process proceeds to step S304. On the other hand, if there is data in the still image buffer 806 as a result of the check in step S308, the process proceeds to step S309, where it is checked whether or not the still image writing unit data includes the end of the still image file to be written. In the present embodiment, the still image writing unit is set to be an integral multiple of the file system cluster size.

  If the result of this check is that the end of the still image file is included, the process proceeds to step S310 to acquire data up to the end of the still image file. On the other hand, as a result of the check in step S309, if the end of the still image file is not included, the process proceeds to step S311 to acquire still image writing unit data.

  When the process of step S310 or step S311 is completed, the process proceeds to step S312, where the still image data acquired in step S310 or step S311 is written, and the process proceeds to step S304. The still image data writing process will be described in detail later with reference to the flowchart of FIG. 9-5.

  On the other hand, if the result of the check in step S305 is that moving image shooting is not in progress, the flow advances to step S313 to receive a buffer flash instruction event from the shooting task 802. Next, proceeding to step S314, the number of all moving image frames stored in the moving image buffer 805 is acquired. Next, the process proceeds to step S315, and the moving image data writing process is performed by designating the number of moving image frames acquired in step 314.

  In step S316, it is checked whether there is data in the still image buffer 806. If there is no data as a result of this check, the process proceeds to step S301. On the other hand, if there is data as a result of the check in step S316, the process proceeds to step S317, and data up to the end of the file is acquired for the still image file data in the still image buffer 806. In the present embodiment, at the start of the buffer flash process, the remaining size up to the end of the file is acquired for the still image file data that was written before the flash process.

  Next, the process proceeds to step S318, and the data acquired in step S317 is written. Thereafter, the process proceeds to step S319, where it is checked whether data remains in the still image buffer. As a result of the check, if data remains, the process proceeds to step S317, and the next still image file is written.

  On the other hand, if no data remains as a result of the check in step S319, writing of all still image file data has been completed, so the process proceeds to step S320 to perform a write task end process, and then the process proceeds to step S301 to wait for initialization. Become. The termination process performed in step S320 will be described in detail later with reference to the flowchart of FIG. 9-6.

FIGS. 9-4 (a) and (b) are flowcharts showing an example of the moving image data writing processing procedure performed in step S306.
As shown in FIG. 9-4 (a), when the process is started, first, in step S401, an index value for writing moving image frame data is initialized. In step S402, moving image frame data is written. Details of the process of step S402 will be described with reference to the flowchart of FIG. In step S403, the index value is updated.

  In step S404, it is checked whether the designated number of moving image frames has been written. Here, the designated number of moving image frames is the number of frames in a moving image writing unit at the time of moving image shooting, and is the number of all frames in the buffer at the time of buffer flash. As a result of this check, if the designated number of moving image frames has not been written, the process returns to step S402. If the result of the check in step S404 shows that the designated number of moving image frames has been written, the process ends.

Next, details of the frame writing process in step S402 will be described with reference to FIG. 9-4 (b).
When the processing is started, first, in step S405, audio data for one second is acquired from the moving image buffer. Next, it progresses to step S406 and the audio data acquired by step S405 are written in a chunk.

  In step S407, the attribute information (data position, size) of the written audio data chunk is recorded in the index buffer 807. In step S408, video frame data corresponding to the frame rate is acquired from the moving image buffer 805.

  In step S409, an index value for writing video frame data is initialized. Thereafter, the process proceeds to step S410, and the video frame data acquired in step S408 is written in the chunk. Thereafter, the process proceeds to step S411, and the attribute information (data position, size) of the written video frame data chunk is recorded in the index buffer 807.

  In step S412, the index value is updated. Thereafter, in step S413, it is checked whether or not the writing of video frame data for one second has been completed. As a result of the check, if not completed, the process returns to step S410. On the other hand, if it is determined in step S413 that the process has been completed, the frame writing process ends.

FIG. 9-5 is a flowchart illustrating an example of a still image data writing process procedure in step S308.
As shown in FIG. 9-5, when processing is started, first, in step S501, a dummy chunk is written. In the present embodiment, the moving image data chunk writing process is performed before the still image data is written.

  However, as shown in FIG. 8, the writing end position of the moving image data chunk does not match the cluster boundary. Therefore, in this step S501, a dummy chunk is written in order to align the write start position of the still image data chunk with the cluster boundary of the file system.

  In step S502, it is checked whether the still image data designated for writing includes the end of the still image file. If the result of this check is that the end of the still image file is included, the process advances to step S503 to write still image data up to the end of the still image file designated for writing in the chunk. On the other hand, if it is determined in step S502 that the end of the still image file is not included, the process proceeds to step S505 to write the still image data designated for writing in the chunk.

  As described in step S305, since the still image data designated for writing is an integral multiple of the cluster size, it is not necessary to write a dummy chunk after writing in this step.

  In step S504, the dummy chunk is written again. The still image data chunk written in step S503 has a data size that is unrelated to the cluster size of the file system. In step S504, dummy chunks are written in order to match the still image data recording area to an integer multiple of the file system cluster size.

  In step S506, the attribute information (still image file number, data position, size) of the written still image data chunk is recorded in the index buffer 807.

FIG. 9-6 (a) is a flowchart showing an example of the write task initialization process in step S303 in FIG. 9-3, and FIG. 9-6 (b) shows an example of the write task end process in step S319. It is a flowchart.
As shown in FIG. 9-6 (a), when the process is started, first, in step S601, a RIFF file to which shooting data is written is opened. In step S602, a file header is generated. In step S603, a 'movi' chunk for writing moving image data and still image data is opened, and the writing task initialization process is terminated.

  As shown in FIG. 9-6 (b), when the process is started, first, in step S604, the 'movi' chunk is closed. In step S605, the attribute information of the moving image data chunk and the still image data chunk recorded in the index buffer 807 is read. In step S606, a moving image index and a still image index are created, and the attribute information read in step S605 is written. Thereafter, the process proceeds to step S607, a process for closing the file is performed, and the write task end process ends.

FIG. 10 exemplifies a buffer usage situation when moving image data and still image data are written to a file by the processing described above.
FIG. 10 is a diagram showing a buffer usage situation when moving image data and still image data are written in a file according to the present embodiment.
In FIG. 10, a diagram 1001 shows a data state in the moving image buffer during shooting. Reference numeral 1002 denotes the maximum buffer size [byte] of the moving image buffer.

  Reference numeral 1003 denotes moving image writing unit data, which indicates moving image data corresponding to the number of frames in the moving image writing unit. When the moving image writing unit data 1003 is stored in the moving image buffer, a moving image data writing event is notified to the writing task. Reference numeral 1004 denotes a moving image writing timing, which indicates a timing at which a moving image data writing event is notified to the writing task.

  A diagram 1005 shows a data state in the still image buffer during shooting. Reference numeral 1006 denotes the maximum buffer size [byte] of the still image buffer. Reference numeral 1007 denotes generated still image data, which shows how still image data is generated in the still image buffer by still image shooting during moving image shooting. Reference numeral 1008 denotes still image writing timing, which indicates the timing at which the writing task finishes moving image data writing processing and starts still image data writing processing.

  Reference numeral 1009 denotes still image data to be written, which indicates data of a still image writing unit to be written to a file after writing moving image data. By performing the processing described above, in this embodiment, still image data can be written between moving image data writes.

Next, a method for separating a still image file from a file recorded in the present embodiment will be described.
FIG. 11 is a diagram illustrating an example of a user interface of an application that separates a still image file from a recording file according to the present embodiment.

  In FIG. 11, an image 1101 shows a review image representing a recording file. An icon 1102 indicates that still image data is mixed in the recording file. A menu 1103 is a menu item for inquiring the user whether or not to separate a still image file from a recording file. The user decides to separate with the cross key and the enter button.

FIG. 12 is a diagram illustrating an example of a procedure for separating still image data by separating still image data recorded in a file according to the present embodiment.
In FIG. 12, a file 1201 is a file in which moving image data and still image data obtained by the recording method of the present embodiment are mixed. The table 1202 is a table that manages still image numbers, still image data chunk positions, and data sizes as attribute information of still image data chunks in the file.

  An image 1203 is an image diagram of a still image file created from a still image data chunk recorded in the file. In the present embodiment, the file with the still picture number “PICT0002” is composed of a still picture data storage area with a data size of b1 [bytes] and a still picture data storage area with a data size of b2 [bytes].

  A table 1204 is a file system directory / file management table. When separating a still image file from the file 1201, a still image file to be separated (for example, PICT0002.JPG) is registered in this table 1204. At this time, the start cluster indicated by 1205 designates the first cluster number of the data chunk storing the still image data. The subsequent data storage area is managed by the FAT table 1206.

  An arrow 1207 shows a state in which two still image data recording cluster areas are connected by switching the cluster chain. When the moving image data and the still image data are sequentially stored regardless of the cluster area, the file data must be repeatedly read and written in order to separate the still image files. For this reason, when the file size increases, a problem arises that a lot of processing time is required for separation.

  However, in the present embodiment described above, the still image data chunk recorded in the file is matched with the cluster boundary and the cluster size. Therefore, a still image file can be created by changing the cluster chain without performing data movement within the file, so that the still image file can be separated at high speed.

(Second Embodiment)
Hereinafter, a method of dynamically determining the data size of still image data writing performed between moving image data writing based on prediction from the writing history will be described. In the present embodiment, after writing data in units of moving image writing, the size of data that can be written is predicted by the next moving image writing timing, and still image data is written.

Since the moving image writing request event is issued every time moving image data of the number of seconds for moving image writing is generated, the moving image data writing timing almost follows the specified number of seconds. Accordingly, the predicted still image writable data size is calculated as follows using the measured values of the moving image data writing time and the data writing speed required for moving image writing.
(Still image writable data size [byte])
= {(Moving image writing unit seconds [sec]) − (moving image data writing time [sec])} * (writing speed [byte / sec]).

  At this time, a value obtained by the immediately preceding moving image data writing process may be used as the writing speed, or an average value of the writing history may be used. The configuration of the writing processing unit and the processing of the shooting task and the moving image buffer monitoring task are the same as those in the first embodiment.

FIG. 13 is a flowchart illustrating an example of a processing procedure of the writing task 809 that performs writing by predicting the still image data size in the present embodiment.
As shown in FIG. 13, step S1301 is in a task initialization waiting state. When the process is started, the process advances to step S1302 to receive a write task initialization event from the shooting task 802. In step S1303, the write task is initialized. This initialization process is the same as in the first embodiment. Then, the process proceeds to step S1304. Step S1304 is in a write wait state.

  If writing occurs in the writing waiting state in step S1304, the process advances to step S1305 to check whether a moving image is being shot. If the result of this check is that moving image shooting is in progress, the process advances to step S1306 to receive a moving image data write request event from the write task 802 in a write wait state.

  In step S 1307, it is checked whether there is still image data in the still image buffer 806. If there is still image data as a result of this check, the process advances to step S1308 to perform a process for predicting the writable data size. On the other hand, if the result of the check in step S1307 is that there is no still image data, the flow advances to step S1316 to specify the number of all data frames in the moving image buffer, perform moving image data writing processing, and then wait for writing in step S1304 Transition to.

  In the prediction processing in step S1308, measurement of the time required for the writing processing of the moving image writing unit data and the writing speed are started. Thereafter, the process proceeds to step S1309, and the moving image data writing process is performed by designating all the data frames in the moving image buffer. The moving image data writing process performed in step S1309 is the same as that in the first embodiment. Next, proceeding to step S1310, the moving image data writing measurement started at step S1308 is terminated.

  Next, the process proceeds to step S1311, and a predicted value of the still image data size that can be written by the next moving image data writing timing is calculated by the above formula. Next, in step S1312, it is checked whether or not the still image data of the size acquired in step S1311 includes the end of the still image file. If the result of this check is that the end of the still image file is included, the process advances to step S1313 to acquire data up to the end of the still image file.

  On the other hand, if the end of the still image file is not included as a result of the check in step S1312, the process proceeds to step S1314, and the maximum size that is an integral multiple of the file system cluster size within the range that fits in the predicted write size calculated in step S1311. Get the still image data.

  When the process of step S1313 or step S1314 is completed, the process proceeds to step S1315. In step S1315, the still image data acquired in step S1313 or step S1314 is written. When the still image data writing process is completed, the process returns to the writing wait state in step S1304.

  On the other hand, if the result of the check in step S1305 is that moving image shooting is not in progress, the flow advances to step S1317 to receive a buffer flash instruction event from the shooting task 802 in a writing wait state. Next, proceeding to step S1318, the number of all moving image frames stored in the moving image buffer 805 is acquired. Thereafter, the process proceeds to step S1319, and the moving image data writing process is performed by designating the number of moving image frames acquired in step S1318.

  Next, in step S1320, it is checked whether there is still image data in the still image buffer 806. If there is no data as a result of this check, the process transits to the initialization wait state in step S1301. If there is still image data as a result of the check in step S1320, the process advances to step S1321 to acquire data up to the end of the file for the still image file data in the still image buffer 806. At the start of the buffer flash process, the remaining size up to the end of the file is acquired for the still image file data that was written before the flash process.

  Next, the process proceeds to step S1322, and the still image data acquired in step S1321 is written. In step S 1323, it is checked whether still image data remains in the still image buffer. If still image data remains as a result of this check, the process returns to step S1321 to write the next still image file.

  On the other hand, if no still image data remains as a result of the check in step S1323, writing of all the still image file data has been completed, and the process proceeds to step S1324 to perform the writing task termination process. This termination process is the same as in the first embodiment.

  As described above, according to the present embodiment, the still image data size that can be written by the next moving image data write timing after the moving image data is written is predicted, and the still image data is written according to the predicted value. If the still image write data size is predicted to be larger than the actual writable size, all the video data in the video buffer is written at the next video write timing, so a video buffer size that can handle this case is secured. If so, buffer overflow will not occur. With this process, it is possible to realize an efficient write process with a reduced time zone during which no data write process is performed.

(Third embodiment)
Hereinafter, a method for separating still image files in the case where only the body portion of an Exif file is recorded in a file when still image shooting is performed during moving image shooting will be described with reference to the drawings.
FIG. 14 is a diagram illustrating an example of a procedure for separating still image data recorded in a file and separating an Exif format still image file in the present embodiment.

  In FIG. 14, reference numeral 1401 denotes a file in which moving image data and still image data obtained by the recording method described in the first embodiment are mixed. Reference numeral 1402 denotes a header portion of the RIFF file including date information and the like. A table 1403 manages still image numbers, still image data chunk positions, and data sizes as attribute information of still image data chunks in the file.

  An image 1404 is an image diagram of a still image file created from a still image data chunk recorded in the file. Reference numeral 1405 in the image diagram 1404 denotes a body portion of an Exif still image file separated from the file 1401. A thumbnail portion 1406 in the image diagram 1404 is created from the body portion 1405 when the still image file is separated. An Exif header 1407 in the image diagram 1404 is created from the header information diverted from the header part 1402 of the file 1401 and the thumbnail part 1406.

  A table 1408 is a file system directory / file management table. When a still image file is separated from the file 1401, a separation target still image file (for example, PICT0002.JPG) is registered in this table. At this time, the cluster number of the created Exif header 1406 is designated for the start cluster indicated by 1409. The subsequent data storage area is managed by the FAT table 1410.

  A first element 1411 in the FAT table is a data area in which the created Exif header 1407 is recorded. A second element 1412 is a data area in which a still image file body part 1405 separated from the file 1401 is recorded. An arrow 1413 indicates a state where the Exif header portion 1407 and the body portion 1405 of the first element 1411 and the second element 1412 recorded in different data areas are coupled by switching the cluster chain.

  As described above, in this embodiment, only the body portion of a still image file is recorded in the file, and header information and thumbnail information are created when the still image file is separated. Therefore, the data size of the file to be recorded can be made smaller than when still image data including header information and thumbnail information is recorded in the file.

(Another embodiment according to the present invention)
Each means constituting the imaging apparatus and each step of the image recording method in the embodiment of the present invention described above can be realized by operating a program stored in a RAM or ROM of a computer. This program and a computer-readable recording medium recording the program are included in the present invention.

  Further, the present invention can be implemented as, for example, a system, apparatus, method, program, or recording medium, and can be applied to a system composed of a plurality of devices. Moreover, you may apply to the apparatus which consists of one apparatus.

  In the present invention, a software program (in the embodiment, a program corresponding to the flowcharts shown in FIGS. 9-1 to 9-6 and FIG. 13) for realizing the functions of the above-described embodiments is stored in a system or apparatus. It includes a case where it is achieved by supplying directly or remotely, and by reading and executing the supplied program code by the computer of the system or apparatus.

  Accordingly, since the functions of the present invention are implemented by computer, the program code installed in the computer also implements the present invention. In other words, the present invention includes a computer program itself for realizing the functional processing of the present invention.

  In that case, as long as it has the function of a program, it may be in the form of object code, a program executed by an interpreter, script data supplied to the OS, and the like.

  As a recording medium for supplying the program, for example, floppy (registered trademark) disk, hard disk, optical disk, magneto-optical disk, MO, CD-ROM, CD-R, CD-RW, magnetic tape, nonvolatile memory card ROM, DVD (DVD-ROM, DVD-R) and the like.

  As another program supply method, a client computer browser is used to connect to an Internet homepage, and the computer program itself of the present invention or a compressed file including an automatic installation function is downloaded from the homepage to a recording medium such as a hard disk. Can also be supplied.

  It can also be realized by dividing the program code constituting the program of the present invention into a plurality of files and downloading each file from a different homepage. That is, the present invention includes a WWW server that allows a plurality of users to download a program file for realizing the functional processing of the present invention on a computer.

  In addition, the program of the present invention is encrypted, stored on a recording medium such as a CD-ROM, distributed to users, and key information for decryption is downloaded from a homepage via the Internet to users who have cleared predetermined conditions. It is also possible to execute the encrypted program by using the key information and install the program on a computer.

  In addition to the functions of the above-described embodiments being realized by the computer executing the read program, the OS running on the computer based on the instructions of the program is used for the actual processing. The functions of the above-described embodiment can be realized by performing some or all of the processes.

  Furthermore, after the program read from the recording medium is written in a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer, the function expansion board or The CPU or the like provided in the function expansion unit performs part or all of the actual processing, and the functions of the above-described embodiments are realized by the processing.

1 is a block diagram illustrating an example of an overall configuration of an imaging apparatus according to a first embodiment of the present invention. It is a figure which shows an example of the front surface and back surface of an imaging device in the 1st Embodiment of this invention. It is a figure which shows an example of the operation image at the time of performing moving image photography and still image photography simultaneously in the 1st Embodiment of this invention. It is a figure which shows an example of the image which writes the moving image data and still image data in a file with the imaging device of the 1st Embodiment of this invention. It is a figure which shows an example of the hierarchical chunk structure of a general RIFF file format. It is a figure which shows an example of the chunk structure in the RIFF file format which expanded the AVI file utilized in the 1st Embodiment of this invention. It is a figure which shows an example of the recording condition of the still image data according to the cluster boundary in the 1st Embodiment of this invention. It is a block diagram which shows the structural example of the write-in process part in the 1st Embodiment of this invention. 6 is a flowchart illustrating an example of a procedure for simultaneously capturing a moving image / still image of an imaging task in the first embodiment of the present invention. It is a flowchart which shows an example of the process sequence of the moving image buffer monitoring task in the 1st Embodiment of this invention. It is a flowchart which shows an example of the process procedure of the write task in the 1st Embodiment of this invention. It is a flowchart which shows an example of the moving image data write-in processing procedure of the write task in the 1st Embodiment of this invention. It is a flowchart which shows an example of the still image data write-in processing procedure of the write task in the 1st Embodiment of this invention. It is a flowchart which shows an example of the initialization / end process procedure of the write task in the 1st Embodiment of this invention. It is a figure which shows the buffer utilization condition at the time of writing of moving image data and still image data in the 1st Embodiment of this invention. It is a figure which shows an example of the user interface of the application which isolate | separates the still image file in the 1st Embodiment of this invention. It is a figure which shows an example of the procedure which isolate | separates a still image file from the recording file in the 1st Embodiment of this invention. It is a flowchart which shows an example of the process sequence of the write control task in the 2nd Embodiment of this invention. It is a figure which shows an example of the separation method of the still image file in the 3rd Embodiment of this invention.

Explanation of symbols

101 Lens 102 Aperture Mechanism 103 Image Sensor 104 A / D
105 signal processing circuit 106 compression circuit 107 memory 108 MPU
109 External recording medium 110 Write processing unit

Claims (15)

Movie shooting means for shooting movies,
And the still image photographing means capable of performing a still image shooting during movie shooting that due to the moving image shooting means,
The still image data taken by the front Kisei Tomega photographing means, and the still image storage means for storing a still image buffer,
And video storage means for storing moving image data captured by the kinematic Well shadow means video buffer,
Recording control means for selectively recording the divided still image data divided from the still image data stored in the still image buffer and the moving image data for a predetermined time stored in the moving image buffer on a recording medium ;
A determining unit that determines a data size of the divided still image data based on a time required for the moving image data for the predetermined time to be captured by the moving image capturing unit and a recording speed of the data on the recording medium; Have
The image recording apparatus, wherein the recording control unit records the divided still image data having a size corresponding to the data size determined by the determining unit on the recording medium . The recording control unit is configured to calculate a difference between a time required for the moving image shooting unit to shoot the moving image data for the predetermined time and a time required to record the moving image data for the predetermined time on the recording medium. The imaging apparatus according to claim 1, wherein the divided still image data is recorded in time. The recording control means includes measurement means for measuring a recording speed of data on the recording medium by the recording control means by measuring a recording speed at which the moving image data is recorded on the recording medium. Item 3. The imaging device according to Item 1 or 2. The determining means determines the data size of the divided still image data using the recording speed measured by the measuring means immediately before or the recording speed obtained based on the measurement history measured by the measuring means. The imaging apparatus according to claim 3. The kinematic Well during shooting by the shadow means, imaging according to any one of claims 1 to 4, characterized in that a display means for displaying the number of recordable video length of a still image at the same time apparatus. A region where the moving image data cannot be recognized as a moving image file, a recording region where the still image data can be recorded, and a still image for managing index information for the still image data region recorded in the recording region the imaging apparatus according to any one of claims 1 to 5, characterized in that it has a management file with the image data index information management section.   7. The imaging according to claim 6, further comprising: a file reproducing unit that reproduces a file in which the moving image data and the still image data recorded in the management file are mixed, a moving image file, and a still image file. apparatus.   The file playback means includes display means for displaying that the video data and the still image data are mixed when the file containing the video data and the still image data is played back. The imaging apparatus according to claim 7, wherein the imaging apparatus is characterized. According to any one of claims 6 to 8, characterized in that it has a still image data separating means for separating the still picture data from a file that the the management file to the recorded moving image data and still image data are mixed Imaging device.   The imaging apparatus according to claim 9, further comprising a still image file creation unit that creates a still image file from the still image data separated by the still image data separation unit.   11. The still image file creating means creates header information of the still image file with reference to header information of a moving image data file in which the moving image data and the still image data are mixed. The imaging device described in 1.   12. The imaging apparatus according to claim 10, wherein the still image file creation unit creates thumbnail image data from the still image data. Movie shooting process for shooting movies,
And the still image shooting process that can take a still photo during'm Videotaping in the moving image taking step,
A still image storing step of storing the still image data taken by the front Kisei Tomega shooting process in the still image buffer,
And video storage step of storing the moving image data captured by the kinematic Well shadow process video buffer,
A recording control step of selectively recording the divided still image data divided from the still image data stored in the still image buffer and the moving image data for a predetermined time stored in the moving image buffer on a recording medium ;
A determination step of determining a data size of the divided still image data based on a time required for the moving image data for the predetermined time to be shot in the moving image shooting step and a recording speed of the data on the recording medium; Have
In the recording control step, the divided still image data having a size corresponding to the data size determined in the determining step is recorded on the recording medium. Movie shooting process for shooting movies,
And the still image shooting process that can take a still photo during'm Videotaping in the moving image taking step,
A still image storing step of storing the still image data taken by the front Kisei Tomega shooting process in the still image buffer,
And video storage step of storing the moving image data captured by the kinematic Well shadow process video buffer,
A recording control step of selectively recording the divided still image data divided from the still image data stored in the still image buffer and the moving image data for a predetermined time stored in the moving image buffer on a recording medium ;
A determination step of determining a data size of the divided still image data based on a time required for the moving image data for the predetermined time to be shot in the moving image shooting step and a recording speed of the data on the recording medium ; A computer program for causing a computer to execute
In the recording control step, the divided still image data having a size corresponding to the data size determined in the determination step is recorded on the recording medium . 15. A computer-readable recording medium on which the computer program according to claim 14 is recorded.

Images