JP2017038238A - Image recording apparatus, control method thereof, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To immediately transfer image data in process of recording to an external apparatus, when a transfer instruction is issued during recording the image data.SOLUTION: When receiving a transfer instruction during recording the image data of a scene, after receiving a recording start instruction until receiving a recording end instruction, an image recording apparatus for recording the image data on a recording medium, and transferring the image data recorded on the recording medium to an external apparatus, generates a file break 310 to complete the file at the time of receiving the transfer instruction, and generates a new second file for recording subsequent scenes, to transfer the completed first file.SELECTED DRAWING: Figure 1

Description

  The present invention relates to an image recording apparatus that records image data on a recording medium and transfers the image data recorded on the recording medium to an external device, a control method thereof, and a program.

  A digital video camera (hereinafter simply referred to as a video camera) converts an optical image into an electrical signal by an image sensor and records the image as a digital image data in a removable recording medium such as a built-in memory of the camera, a CF card, or an SD memory card. The recorded digital image data can be transferred to an external device such as a personal computer (PC) or a mobile terminal (smart phone, tablet terminal, etc.) using various communication units such as USB and wireless LAN.

Recently, a data transfer function via a wireless LAN has become widespread, and data transfer has been realized between a video camera and a PC or portable terminal that have acquired Wi-Fi (Wireless Fidelity) authentication. As a data transfer method, FTP (File Transfer Protocol), HTTP (HyperText Tansfer Protocol), RTP (Real-time Transport Protocol), etc. are common. FTP is often used to transfer digital image data such as video data shot by a video camera, and FTP itself is often used as a file transfer protocol that works in the upper layers of TCP / IP (Transmission Control Protocol / Internet Protocol). Has been. The video camera operates as an FTP client, and transfers image data to an external device such as a PC or a portable terminal having an FTP server function via an FTP command.
In particular, video data handled by ENG (Electornic News Gathering) often requires immediacy, and digital image data can be immediately transferred via a network.

  Patent Document 1 discloses a video recording device that transfers a recorded video to a remote device by network transmission. The video recording device searches the keyword / weight correspondence dictionary for a keyword input from the keyword input means during recording of the moving image file, and records the corresponding weight in association with the time on the moving image file. When the moving image file is transferred to the network, the moving image file is divided into independent moving image files at regular intervals, and the moving image file having the largest weight associated with each time is transferred. When all transfer moving image files have been transferred, a playlist in which the transferred files are rearranged in order of recording time is generated by the playlist generation means and transferred.

  Patent Document 2 discloses a recording apparatus that records video data obtained by a photographing unit on a randomly accessible recording medium. The recording device records the video data output from the image sensor in a first file provided on the recording medium. When the division instruction unit receives a division instruction input from the user during shooting by the image pickup device, the video data output from the image pickup device after the point in time when the division instruction is received is provided on the recording medium. Record to file.

JP 2009-225116 A JP 2005-328154 A

  In Patent Document 1, a moving image file is divided as a moving image file for transfer, and is transferred with priority. However, the moving image file is not transferred during recording, and if it is desired to transfer the moving image file, the recording must be stopped.

  In Patent Document 2, a file is closed in accordance with an instruction from the user during recording, a new file is generated, and recording is continued in the new file so that the closed file can be operated while recording. . However, it is possible to divide a file at the position intended by the photographer and not to transfer digital image data during recording.

  The present invention has been made in view of the above points, and an object of the present invention is to enable image data being recorded to be immediately transferred to an external device when a transfer instruction is issued during the recording of the image data. To do.

  An image recording apparatus of the present invention is an image recording apparatus that records image data on a recording medium and transfers the image data recorded on the recording medium to an external device, and receives a recording end instruction after receiving a recording start instruction. When the transfer instruction is received during the recording of the image data of the previous scene, the first file, which is the file at the time when the transfer instruction is received, is completed, and a new second file for continuously recording the scene And a transfer control means for transferring the completed file.

  According to the present invention, when there is a transfer instruction during recording of image data, the image data being recorded can be immediately transferred to an external device.

It is a block diagram which shows schematic structure of the video camera which concerns on 1st Embodiment. It is a figure which shows the example of a connection of the video camera which concerns on 1st Embodiment, and an external apparatus. It is a conceptual diagram which shows the relationship between the recording operation | movement in the video camera which concerns on 1st Embodiment, and a scene and a file. It is a figure which shows the example of the relationship between the recording operation | movement in the video camera which concerns on 1st Embodiment, a scene, a file, and a transfer instruction | indication. It is a figure which shows the example of the relationship between the recording operation | movement in the video camera which concerns on 1st Embodiment, a scene, a file, and a transfer instruction | indication. It is a figure for demonstrating the transfer list | wrist in 1st Embodiment. It is a flowchart which shows the transfer list registration process of the video camera which concerns on 1st Embodiment. It is a flowchart which shows the transfer control process of the video camera which concerns on 1st Embodiment. It is a figure which shows the example of the relationship between the recording operation | movement in the video camera which concerns on 2nd Embodiment, a scene, a file, and a transfer instruction | indication. 10 is a flowchart showing file generation control processing and transfer list registration processing of the video camera according to the second embodiment. 14 is a flowchart illustrating file generation control processing and transfer list registration processing of a video camera according to a third embodiment.

Preferred embodiments of the present invention will be described below with reference to the accompanying drawings.
<First Embodiment>
FIG. 1 is a block diagram showing a schematic configuration of a video camera 100 according to a first embodiment that functions as an image recording apparatus to which the present invention is applied. The video camera 100 includes a lens 101, a CMOS 102, a camera signal processing unit 103, a recording medium A104, a recording medium B117, a power source 105, an operation unit 106, an input interface (I / F) 107, a ROM 108, a RAM 109, a CODEC 110, and an output I / F 111. , A display unit 112, a CPU 113, a communication control unit 114, a communication module 115, and a communication I / F 116, and inputs and outputs data via the data bus 118.

A lens 101 is a photographing lens including a focus, a diaphragm mechanism, and the like, and forms an optical image of a subject.
A CMOS (Complementary Metal Oxide Semiconductor) 102 is an image sensor, includes an A / D converter, converts an optical image into an analog electric signal, and then converts it into a digital signal. The image sensor is not limited to a CMOS, and may be an image sensor such as a CCD (Charge Coupled Device Image Sensor).
The camera signal processing unit 103 performs resizing processing such as predetermined pixel interpolation / reduction, color conversion, various correction processing, and the like on the digital signal converted by the CMOS 102.
The recording medium A 104 and the recording medium B 117 are flash memories such as an SD memory card and a built-in memory, and record captured video data and audio data, and information necessary for control by the CPU 113. In the present embodiment, video data is recorded on the recording medium A104.

The power source 105 is an AC power source or a battery, and supplies necessary power to each part of the video camera 100.
The operation unit 106 receives an operation from the user, and the received operation information is input to the data bus 118 via the input I / F 107. For example, the encoded video data recorded on the recording medium A104 is selected via the operation unit 106, and a transfer instruction is given to transfer the selected video data to an external device (not shown) with which the communication control unit 114 communicates. . When a transfer instruction is issued, the numbers of encoded files to be transferred and the encoded file groups to be transferred are grouped together according to the format of a transfer list 500 shown in FIG. The scene number is stored in the RAM 109.
The ROM 108 stores a program for starting the video camera 100, and when an electric signal is supplied from the power source 105 by the operation unit 106, the program is read into the RAM 109 by the CPU 113.
The RAM 109 functions as a work area for the CPU 113. The work area of the CPU 113 is not limited to the RAM 109, and may be an external recording device such as a hard disk device (not shown).

The CODEC 110 reproduces video data and audio data recorded in the RAM 109 and the recording medium A 104, and the reproduced video data is displayed on the display unit 112. The reproduced audio data is supplied to a speaker (not shown) and output. The CODEC 110 performs compression encoding or decoding of video compression encoded data at a predetermined bit rate and format format. Although not specifically shown for the sound, the sound signal can be handled by the same processing by using the lens 101 and the CMOS 102 as a microphone and the display unit 112 as a speaker. At the time of video recording, audio and video are simultaneously recorded, and video and audio data can be generated by multiplexing video and audio with the CODEC 110.
The output I / F 111 outputs a display signal to be displayed on the display unit 112 based on display data such as GUI (Graphical User Interface) generated by the CPU 113 according to the program.

The CPU 113 executes a program loaded from the ROM 108 to the RAM 109. The CPU 113 manages information regarding recording of scenes and files when recording video. The CPU 113 performs file operation processing such as file break and file close, which will be described later, acquisition of the information, control of the recording operation of the video camera (change of recording state and recording preparation state), management of the transfer list, and the like.
The communication control unit 114 transmits / receives control data, video data, and audio data to / from an external device such as an FTP server (not shown) via the communication module 115 and the communication I / F 116.

FIG. 2 is a diagram illustrating an example of connection between the video camera 100 according to the first embodiment and an external device. The video camera 100 can be connected to an external device through at least one of a wired connection and a wireless connection described below.
FIG. 2A is a schematic diagram of an example in which the video camera 100 and the external device 200a are connected by wire. The external device 200 a is an external device that communicates with the video camera 100 via the wired cable 201. The external device 200a may be a device that directly communicates with the video camera 100 or a device that is connected via a relay device such as a network hub. The present invention can be applied to any communication using a wired medium such as a wired LAN or USB.
FIG. 2B is a schematic diagram of an example in which the video camera 100 and the external device 200b are wirelessly connected. The external device 200 b is an external device that communicates with the video camera 100 via the wireless communication 202. The external device 200b may be a device that performs direct wireless communication with the video camera 100 or a device that is connected via a relay wireless device such as an access point. The present invention can be applied to any connection using wireless communication such as Wi-Fi or Bluetooth (registered trademark).

FIG. 3 is a conceptual diagram illustrating a relationship between a recording operation, a scene, and a file in the video camera 100 according to the first embodiment. A horizontal axis 300 represents a time axis, and indicates that the time elapses toward the right in the figure.
Mode Start 301 indicates an input operation by the operation unit 106 that causes the video camera 100 to transition to the recording preparation state. When this input operation is performed, the video camera 100 transitions to a recording preparation state. Rec Pause 302 indicates a recording preparation state of the video camera 100. The recording preparation state is a state in which the recording state is immediately entered when the Rec Start 303 is instructed.

  Rec Start 303 indicates an input operation of a recording start instruction by the operation unit 106 that causes the video camera 100 to transition to a recording state. When this input operation is performed in the recording preparation state, the video camera 100 transitions to the recording state. Rec 304 indicates the recording state of the video camera 100. In the recording state, a signal input via the lens 101 and the CMOS 102 is encoded as a file format to be recorded on the recording medium A 104 by the CODEC 110 and sequentially stored in the RAM 109. When the file stored in the RAM 109 reaches an arbitrary capacity, the file is recorded on the recording medium A104. This process is sequentially performed until the Rec Stop 308 is instructed.

Rec Stop 308 indicates an input operation of a recording end instruction by the operation unit 106 that stops the recording state and causes the video camera 100 to transition to the recording preparation state.
Mode Stop 311 indicates an input operation by the operation unit 106 that shifts the recording operation of the video camera 100 to the end state.

  Rec Delay 305 is a time difference until recording of video data actually starts on the recording medium A 104 after the Rec Start 303 is instructed and the video camera 100 enters the recording state. This time difference increases and decreases depending on the bit rate of the video to be recorded and the arbitrary capacity when stored in the RAM 109. It should be noted that a similar time difference occurs from when the Rec Stop 308 is instructed to when recording is actually finished.

  A scene (Scene) 306 is a recording unit when video is recorded by the video camera 100. The recording unit is a bundle of video data recorded between the Rec Start 303 and the Rec Stop 308. It should be noted that this is not synonymous with a file (File) 307 to be described later. In view of the file system of the recording medium A104, if the data recorded on the recording medium A104 has a data size that exceeds the file upper limit capacity of the file system, it is necessary to divide the file. This operation is called a file break 310. The scene 306 is a definition that is handled as one including the file 307 having the file break. The scene 306 is assigned a number every time the Rec Start 303 is instructed, and is used as a scene # 1, a scene # 2,.

  The file 307 is a video data file recorded on the recording medium A104. When the data accumulated in the RAM 109 reaches an arbitrary capacity triggered by the Rec Start 303, it starts to be stored as the file 307 in the recording medium A104. Since the video data is sequentially written to the RAM 109 in the recording state, the data stored in the file 307 also increases. Until the file close 309 or the file break 310 occurs, the file 307 is in an incomplete state and cannot be read from other processes. When the file close 309 or the file break 310 occurs, the file 307 is completed. A number is assigned each time the file 307 is completed, and the file # 1, file # 2,.

The file close 309 is a file operation for completing the file 307 sequentially recorded on the recording medium A104 by the recording operation of the video camera 100 in response to the Rec Stop 308 being instructed. When this operation is performed, the file 307 can be read or edited from other processes.
In consideration of the file system of the recording medium A104, the file break 310 is a file operation when a file having a specific size or larger is stored separately when the file is stored in the recording medium A104. This file operation is automatically performed in the video camera 100 by the CPU 113 identifying the file system of the recording medium A104. Therefore, if the user inputs Rec Start 303 only once from the operation unit 106, the file 307 is written by the file break 310 when the recording time continues for a certain time and the file 307 is written up to the upper limit of the file system of the recording medium A 104. Along with the completion state, generation of a new file 307 is started.

4A and 4B are diagrams illustrating an example of a relationship between a recording operation, a scene, a file, and a transfer instruction in the video camera 100 according to the first embodiment.
FIG. 4A (a) shows a recording state (REC 304) of the video camera 100 in which a transfer instruction has been given to transfer the scene being recorded to an external device.
The scene # 1 (306 (1)) is assumed to be initially recorded on the recording medium A104, and the assigned number is “# 1”.
The file # 1 (307 (1)) is assumed to be initially recorded on the recording medium A104, similarly to the scene # 1 (306 (1)), and the assigned number is “# 1”.
Transfer Req 401 indicates an input operation by the operation unit 106 that instructs to transfer the scene # 1 (306 (1)) being recorded to an external device.
When the Rec Stop 308 is instructed, the file close 309 completes the file # 1 (307 (1)) that is in an incomplete recording state as a file.

FIG. 4A (b) shows a recording preparation state (Rec Pause 302) after the recording state of the video camera 100, and a state in which a transfer instruction is made to transfer the recorded scene to an external device. In FIG. 4A (b), it is assumed that the file break 310 has not occurred.
The scene # 2 (306 (2)) is assumed to be a scene when the second Rec Start 303 is instructed, and the number assigned is “# 2”.
File # 2 (307 (2)) is assumed to record the second file on recording medium A104, similarly to scene # 2 (306 (2)), and the number assigned is “# 2”. Yes.
When the Rec Stop 308 is instructed, the file close 309 completes the file # 2 (307 (2)) that is in an incomplete recording state as a file.
Transfer Req 401 indicates an input operation by the operation unit 106 that instructs to transfer scene # 2 (306 (2)) for which recording has been completed to an external device.

FIG. 4A (c) shows a recording state (REC 304) of the video camera 100 and a state in which a transfer instruction is given to transfer the recording scene to the external device before the file break 310 occurs.
The scene # 3 (306 (3)) is assumed to be a scene when the third Rec Start 303 is instructed, and the number assigned is “# 3”. In the scene # 3 (306 (3)), a file break 310 occurs for the file # 3 (307 (3)), and after the file # 3 (307 (3)) is completed, a new file # 4 is created. (307 (4)) is generated.
The file # 3 (307 (3)) is assumed to be recorded in the third file on the recording medium A104, and the number assigned is “# 3”. The file # 4 (307 (4)) is a file generated to continuously record the scene # 3 after the file break 310 occurs for the file # 3 (307 (3)).
Transfer Req 401 indicates an input operation by the operation unit 106 instructing to transfer the scene # 3 (306 (3)) being recorded to an external device.

FIG. 4B (a) shows a recording state (REC 304) of the video camera 100 and a state in which a transfer instruction has been made to transfer the scene being recorded to an external device after the occurrence of the file break 310.
Scene # 4 (306 (4)) is assumed to be a scene when the fourth Rec Start 303 is instructed, and the number assigned is “# 4”. In the scene # 4 (306 (4)), a file break 310 occurs for the file # 5 (307 (5)), and after completing the file # 5 (307 (5)), a new file # 6 is created. (307 (6)) is generated.
The file # 5 (307 (5)) is assumed to be recorded in the fifth file on the recording medium A104, and the number assigned is “# 5”. The file # 6 (307 (6)) is a file generated to continuously record the scene # 4 after the file break 310 occurs for the file # 5 (307 (5)).
Transfer Req 401 indicates an input operation by the operation unit 106 instructing to transfer the scene # 4 (306 (4)) being recorded to the external device.

FIG. 4B (b) shows a recording preparation state (Rec Pause 302) that has passed through the recording state of the video camera 100 and a transfer instruction for transferring the recorded scene to an external device. In FIG. 4B (b), it is assumed that a file break 310 has occurred.
Scene # 5 (306 (5)) assumes a scene in which the fifth Rec Start 303 is instructed, and the number assigned is “# 5”. In the scene # 5 (306 (5)), a file break 310 occurs for the file # 7 (307 (7)), and after the file # 7 (307 (7)) is completed, a new file # 8 is created. (307 (8)) is generated.
File # 7 (307 (7)) is assumed to be recorded in the seventh file on recording medium A104, and the number assigned is "# 7". The file # 8 (307 (8)) is a file generated to continuously record the scene # 5 after the file break 310 occurs for the file # 7 (307 (7)).
When the Rec Stop 308 is instructed, the file close 309 completes the file # 8 (307 (8)) that is in an incomplete recording state as a file.
Transfer Req 401 indicates an input operation by the operation unit 106 that instructs to transfer the scene # 5 (306 (5)) for which recording has been completed to an external device.

FIG. 5 is a diagram for explaining a transfer list and a registration method thereof according to the first embodiment.
The configuration of the transfer list 500 will be described with reference to FIG. The transfer list 500 is configured to register scene information and file information.
Lists 510, 520, 530,... Are scene information registration tables, in which scene numbers for which transfer has been instructed are registered. The number of tables in this table is determined by the number of registered scenes for which transfer instructions have been issued. In this example, there are five scene number registration tables [0] to [4]. That is, the number of scenes that can be instructed to transfer is five. However, when the transfer of the registered scene is completed, the table becomes empty, and it becomes possible to instruct transfer again.
Lists 511, 512,... Are file information registration tables, in which file numbers constituting scenes registered in the list 510 are registered. Similarly, lists 521, 522,... Are file information registration tables, in which file numbers constituting scenes registered in the list 520 are registered. The same applies to the subsequent lists 530,. The number of tables is determined according to the maximum number of files constituting one scene. In this example, there are three file information registration tables, and three files can be registered for one scene.
Note that the number of scene information registration tables and the number of file information registration tables can be operated in accordance with the number of systems.

FIG. 6 is a flowchart showing transfer list registration processing of the video camera 100 according to the first embodiment.
As shown in FIGS. 4A and 4B, the video camera 100 confirms the recording operation when the Transfer Req 401, which is a transfer instruction, is input, and the presence or absence of the file break 310, and registers the transfer list 500.
Hereinafter, the operation of the video camera 100 when Transfer Req 401 is input will be described with reference to FIGS. 4A, 4B, and 5. FIG. Asynchronously with the processing of FIG. 6, the user can arbitrarily change the video camera 100 to the recording preparation state and the recording state via the operation unit 106. 4A and 4B, the transition to the recording preparation state corresponds to Mode Start 301 in each figure, the transition to the recording state corresponds to Rec Start 303, and the transition to the recording preparation state corresponds to Rec Stop 308.

In step S601, the CPU 113 confirms whether or not the video camera 100 is in a recording state or a recording preparation state. In a state other than the recording state and the recording preparation state, this process is not performed and step S601 is repeated. If it is in the recording state or the recording preparation state, the process proceeds to step S602.
In step S602, the CPU 113 confirms whether Transfer Req 401 has been input. If Transfer Req 401 is not input, step S602 is continued. When Transfer Req 401 is input, the process proceeds to step S603.
In step S603, the CPU 113 confirms whether or not the video camera 100 is in a recording state. If it is in the recording state, the process proceeds to step S604, and if it is not in the recording state, the process proceeds to step S650.

Steps S604 to S613 are processing performed when Transfer Req 401 is input in the recording state, as shown in FIGS. 4A (a), 4A (c), and 4B (a).
In step S604, the CPU 113 registers the scene to be transferred in the transfer list 500. The process of step S604 will be described with reference to FIGS. 4A (a) and 5 (b). This is the first scene recording at the time of input of Transfer Req 401 in FIG. 4A (a), and the lists 510 to 550 are all unregistered. The CPU 113 that has detected the input of Transfer Req 401 in step S 602 acquires the scene number instructed to transfer by Transfer Req 401 and registers it in the list 510. In this example, scene # 1 (306 (1)) corresponds, and as shown in FIG. 5B, scene # 1 is registered in the list 510. 4A (c) and 4B (a), there is also a scene information registration process for the transfer list 500 in this step, and each scene # 3 (306 (3 (3)) is included in the list 530 as shown in FIG. 5 (d). )) Is registered, and the scene # 4 (306 (4)) is registered in the list 540 as shown in FIG.

  In step S <b> 605, the CPU 113 confirms whether there is a file that can be registered in the transfer list 500. The CPU 113 manages information on the scene currently being recorded. The information on the scene includes information on the files that make up the scene, and it is possible to determine whether the scene is composed of a plurality of files by the file break 310. In FIG. 4A (a), file # 1 (307 (1)) is in an incomplete state when Transfer Req 401 is input, and cannot be registered in the transfer list 500. The same applies to the file # 3 (307 (3)) in FIG. 4A (c). In this case, the process proceeds to step S608. On the other hand, in FIG. 4B (a), file # 6 (307 (6)) is in an incomplete state when Transfer Req 401 is input, but file # 5 (307 (5)) is in a completed state by file break 310. Yes, it can be registered in the transfer list 500. In this case, the process proceeds to step S606, and registration processing of the transfer list 500 is performed.

In step S606, the CPU 113 registers the file to be transferred in the transfer list 500. The process of step S606 will be described with reference to FIGS. 4B (a) and 5 (f). In FIG. 4B (a), scenes # 1 to # 3 are already registered in the lists 510, 520, and 530 as shown in FIG. 5 (f). As shown in FIG. 5F, file # 5 (307 (5)) is registered in the list 541 of scene # 4 which has not been registered before execution of step S606. When step S606 ends, the process proceeds to step S607.
In step S <b> 607, the CPU 113 confirms whether all the files that can be registered are registered in the transfer list 500. In FIG. 4B (a), only the file # 5 (307 (5)) is in a completed state at the time of input of Transfer Req 401, but a case where a plurality of files are generated by the file break 310 is also assumed. . In that case, it is checked in step S607 whether all files have been registered in the transfer list 500. If there is a file to be registered, the process returns to step S606. When all the files have been registered, the process proceeds to step S608.

In step S <b> 608, the CPU 113 receives the Transfer Req 401 and notifies the user that it has been registered in the transfer list 500 on the display unit 112. When the display ends, the process proceeds to step S609.
In step S609, the CPU 113 checks whether a file break 310 has occurred for a file included in the scene being recorded. In FIG. 4A (c) and FIG. 4B (a), file # 3 (307 (3)) and file # 6 (307 (6)) are in an incomplete state when Transfer Req 401 is input. A break 310 may occur and may be in a completed state. When the file break 310 is detected, the process proceeds to step S610. If the file break 310 is not detected, the process proceeds to step S611.
In step S610, the CPU 113 updates the transfer list 500. In FIG. 4A (c), the CPU 113 detecting the file break 310 registers the file # 3 (307 (3)) in the transfer list 500. That is, when file # 3 (307 (3)) is completed by file break 310 in FIG. 4A (c), file # 3 is registered in list 531 as shown in FIG. 5 (d). Thereafter, when a file break 310 further occurs, file # 4 (307 (4)) is registered in the list 532 as shown in FIG. Similarly, when file # 6 (307 (6)) is completed by file break 310 in FIG. 4B (a), file # 6 is registered in list 542 as shown in FIG. 5 (g). .

In step S611, the CPU 113 checks whether a file close 309 has occurred for the scene being recorded. When Rec Stop 308 is input from the operation unit 106, the CPU 113 closes the file. In FIG. 4A (a), file # 1 (307 (1)) is in an incomplete state at the time when Transfer Req 401 is input, and the process waits for file close 309 to occur. When the file close 309 is detected, the process proceeds to step S612. If the file close 309 is not detected, the process returns to step S609, and the occurrence of the file break 310 is detected again.
In step S 612, the CPU 113 registers the file that has been completed by the file close 309 in the transfer list 500. In FIG. 4A (a), file # 1 (307 (1)) is completed by file close 309 and can be registered in the transfer list 500. As shown in FIG. 5B, file # 1 (307 (1)) is registered in the list 511, and the process proceeds to step S613.
In step S <b> 613, the CPU 113 performs file close registration in which data indicating that the scene is completed is written in the transfer list 500. The CPU 113 detects the file close 309, registers the file in the transfer list 500, and then registers in the transfer list 500 that the scene is complete. In FIG. 5B, it is registered in the list 512 that the file is closed. When step S613 ends, the transfer list registration process is completed.

In step S650, the CPU 113 checks whether the video camera 100 is in a recording preparation state. If it is in the recording preparation state, the process proceeds to step S651. If it is not in the recording preparation state, the process proceeds to step S657.
Steps S651 to S656 are processes performed when Transfer Req 401 is input in the recording preparation state as shown in FIGS. 4A (b) and 4B (b).
In step S <b> 651, the CPU 113 confirms whether there is a scene that can be registered in the transfer list 500. The CPU 113 determines whether there is a scene recorded immediately before. Since the CPU 113 performs recording control on the recording medium A104, it is possible to determine the presence or absence of recording. If there is a scene that can be added to the transfer list 500, the process proceeds to step S652. If there is no scene that can be added to the transfer list 500, the process proceeds to step S657.
In step S652, the CPU 113 registers the scene to be transferred in the transfer list 500. The process of step S652 will be described with reference to FIGS. 4A (b) and 5 (c). In FIG. 4A (b), scene # 1 is already registered in the list 510 as shown in FIG. 5C. The CPU 113 that has detected the input of Transfer Req 401 in step S602 acquires the scene number instructed to transfer by Transfer Req 401 and registers it in the list 520. In this example, scene # 2 (306 (2)) corresponds, and as shown in FIG. 5C, scene # 2 is registered in the list 520. Also in FIG. 4B (b), there is a scene information registration process for the transfer list 500 in this step, and scene # 5 (306 (5)) is registered in the list 550 as shown in FIG. 5 (h).

  In step S653, the CPU 113 registers the file to be transferred in the transfer list 500 as in step S606. The process of step S653 will be described with reference to FIGS. 4A (b) and 5 (c). As shown in FIG. 5C, the file # 2 (307 (2)) is registered in the list 521 of the scene # 2 that has not been registered before the execution of step S653. In FIG. 4B (b) as well, there is a file information registration process for the transfer list 500 in this step. As shown in FIG. 5 (h), file # 7 (307 (7)), file # 8 (307 (8)) are added to the list 551, 552 of the unregistered scene # 5 before execution of step S653. Register. When step S653 ends, the process proceeds to step S654.

In step S654, the CPU 113 confirms whether all files that can be registered are registered in the transfer list 500. If registered, the process proceeds to step S655, and if there is an unregistered file, the process returns to step S653. In FIG. 4B (b), file # 7 (307 (7)) is registered in the first step S653. Thereafter, when it is detected in step S654 that file # 8 (307 (8)) is not registered, file # 8 (307 (8)) is registered again in step S653, and the process proceeds to step S655.
In step S655, the CPU 113 performs file close registration in which data indicating that the scene is completed is written in the transfer list 500. In step S655, since the video camera 100 is preparing for recording and there are only scenes in which the file has already been closed, processing for monitoring the file close is not necessary. In FIG. 4A (b), it is registered that the file is closed in the list 522 as shown in FIG. 5 (c). Further, in FIG. 4B (b), it is registered that the file is closed in the list 553 as shown in 5 (h). After the end of this step, the process proceeds to step S656.
In step S <b> 656, the CPU 113 receives the Transfer Req 401 and notifies the user on the display unit 112 that it has been registered in the transfer list 500. When step S656 ends, the transfer list registration process is completed.

  In step S657, the CPU 113 notifies the user that the transfer list registration process has failed. Although a transfer instruction is given from the operation unit 106, the display unit 112 notifies the user because there is no scene to be registered in the transfer list 500 and transfer processing is not performed. When step S657 ends, the transfer list registration process ends.

The video camera 100 transfers the scene to the external device according to the transfer list 500 registered by the transfer list registration process shown in FIG. FIG. 7 is a flowchart showing transfer control processing of the video camera 100 according to the first embodiment.
In step S701, the CPU 113 initializes a scene pointer indicating a scene to be registered in the transfer list 500, and the process proceeds to step S702.
In step S702, the CPU 113 initializes a file pointer indicating a file to be registered in the transfer list 500, and the process proceeds to step S703.
In step S <b> 703, the CPU 113 checks whether there is a file registered in the transfer list 500. If there is a file registered in the transfer list 500, the process proceeds to step S704. If there is no file registered in the transfer list 500, the confirmation is continued until the registered file is found.
In step S704, the CPU 113 checks whether there is a file registered in the transfer list 500 that can be transferred to an external device. If there is a transferable file, the process proceeds to step S705. If there are no transferable files, continue checking until a transferable file is found.

In step S705, the CPU 113 starts transferring a file registered in the transfer list 500 and transferable to the external device, and the process proceeds to step S706.
In step S706, the CPU 113 confirms whether a transfer error has occurred. If there is a transfer error, the process proceeds to step S707. If there is no transfer error, the process proceeds to step S708.
In step S707, the CPU 113 confirms whether or not the file having the transfer error can be retransmitted. If resending is possible, the process proceeds to step S705, and the transfer of the file to the external device is started again. If re-sending is not possible, exit this process.

In step S708, the CPU 113 confirms whether or not the transfer of the file started in step S705 is completed. If the transfer has been completed, the process proceeds to step S709. If the transfer is not completed, the process advances to step S706 to monitor whether a transfer error occurs during the transfer.
In step S709, the CPU 113 updates the file pointer in the transfer list 500 because there is a file that has been transferred in step S708, and the process proceeds to step S710.
In step S <b> 710, the CPU 113 confirms whether all files related to the scene being referred to on the transfer list 500 have been transferred and whether the file pointer on the transfer list 500 refers to “File Close”. If the file pointer refers to “File Close”, the process proceeds to step S711. If the file pointer does not refer to “File Close”, the process returns to step S704.
In step S711, the CPU 113 updates the scene pointer on the transfer list 500, and the process returns to step S703.

<Second Embodiment>
In the second embodiment, the video camera 100 records high-quality video data on the recording medium A104 (hereinafter referred to as main recording), and simultaneously records video data at a lower bit rate than the main recording on the recording medium B117. An example (hereinafter referred to as proxy recording) is shown.
Note that the configuration and basic operation of the video camera 100 are the same as those described in the first embodiment, and the following description will focus on differences from the first embodiment.
The operation unit 106 can switch to a simultaneous recording mode in which main recording is performed on the recording medium A104 and proxy recording is performed on the recording medium B117. In the simultaneous recording mode, two types of data for main recording and proxy recording data are simultaneously output from the CODEC 110, and the main recording data is recorded on the recording medium A104 and the proxy recording data is recorded on the recording medium B117.

FIGS. 8A and 8B are diagrams illustrating an example of a relationship between a recording operation, a scene, a file, and a transfer instruction in the video camera 100 according to the second embodiment. A file to be recorded on the recording medium A104 is referred to as file_A, and a file to be recorded on the recording medium B117 is referred to as file_B.
FIG. 8A shows a recording state (REC 304) of the video camera 100 in which a transfer instruction is given to transfer the scene being recorded to an external device.
The scene # 1 (306 (1)) is assumed to be initially recorded on the recording medium A104, and the assigned number is “# 1”.
File_A # 1 (307a (1)) is assumed to be initially recorded on recording medium A104, similarly to scene # 1 (306 (1)), and the assigned number is “# 1”. Similarly to scene # 1 (306 (1)), file_B # 1 (307b (1)) is assumed to be initially recorded on recording medium B117, and the number assigned is “# 1”. Yes.
Transfer Req 401 indicates an input operation by the operation unit 106 that instructs to transfer the scene # 1 (306 (1)) being recorded to an external device.
In this case, in order to immediately transfer the file _B # 1 (307b (1)) recorded on the recording medium B117, a file break 310 is generated with Transfer Req 401 as a trigger. As a result, the file _B # 1 (307b (1)) at the time of receiving the transfer instruction is completed, and a new file _B # 2 (307b (2)) for continuously recording the scene # 1 is generated. To do. On the other hand, the file _A # 1 (307a (1)) recorded on the recording medium A104 is continuously recorded.
When Rec Stop 308 is instructed, the file close 309 completes the file _A # 1 (307a (1)) and file _B # 2 (307b (2)) which are in an incomplete recording state as files.

FIG. 8B shows a recording state (REC 304) of the video camera 100 in which a transfer instruction is given to transfer the scene being recorded to an external device.
The scene # 2 (306 (2)) is assumed to be a scene when the second Rec Start 303 is instructed, and the number assigned is “# 2”.
File_A # 2 (307a (2)) is assumed to record a second file on the recording medium A104, similarly to scene # 2 (306 (2)). " In addition, file_B # 3 (307b (3)) is assumed to be recorded in the third file on the recording medium B117, and the assigned number is “# 3”.
Transfer Req 401 indicates an input operation by the operation unit 106 instructing to transfer the scene # 2 (306 (2)) being recorded to an external device.
In this case, in order to immediately transfer the file _B # 3 (307b (3)) recorded on the recording medium B117, a file break 310 is generated with Transfer Req 401 as a trigger. As a result, the file _B # 3 (307b (3)) at the time of receiving the transfer instruction is completed, and a new file _B # 4 (307b (4)) for continuously recording the scene # 2 is generated. To do. In FIG. 8B, a file break 310 is further generated for the file _B # 4 (307b (4)), the file _B # 4 (307b (4)) is brought into a completed state, and the scene # 2 is displayed. A new file _B # 5 (307b (5)) for continuously recording is generated. On the other hand, the file _A # 2 (307a (2)) recorded on the recording medium A104 is continuously recorded.

Here, for example, in the recording medium B117, when the file_B reaches a predetermined file size, the file break 310 is generated. In this case, after the file break 310 is generated with Transfer Req 401 as a trigger, the predetermined file size is changed to a smaller size. Normally, a file break is executed when the file size reaches the upper limit capacity of the file system of the recording medium that records the file. For example, when the file system of the recording medium is FAT32 (File Allocation Table 32), the upper limit capacity is 4 GB, so the file break is executed so that the file size does not exceed 4 GB. In this embodiment, when a file break is executed so that the file size does not exceed 4 GB, after the file break 310 is generated with Transfer Req 401 as a trigger, the file size does not exceed 1 GB. Then, the file break 310 is generated to complete the files after the file _B # 4 (307b (4)).
Note that the file break 310 may be generated when the recording time of the file reaches a predetermined time instead of the file size. Normally, a file break is executed when an arbitrary time elapses due to the file format limitation of the recorded file. For example, when the file format is limited to recording for one hour, a file break is executed at a timing not exceeding one hour. Also in this case, after the file break 310 is generated using Transfer Req 401 as a trigger, the time is changed to a time shorter than one hour.

FIG. 9 is a flowchart illustrating file generation control processing and transfer list registration processing of the video camera 100 according to the second embodiment.
As shown in FIGS. 8A and 8B, the video camera 100 generates a file break 310 and registers the transfer list 500 when Transfer Req 401, which is a transfer instruction, is input. The video camera 100 transfers the scene to the external device according to the transfer list 500.
In step S901, the CPU 113 confirms whether or not the video camera 100 is in a recording state. This process is not performed in a state other than the recording state, and step S901 is repeated. If it is in the recording state, the process proceeds to step S902.
In step S902, the CPU 113 checks whether Transfer Req 401 has been input. If Transfer Req 401 is not input, the process continues to step S910. When Transfer Req 401 is input, the process proceeds to step S903.

In step S903, the CPU 113 generates a file break 310 for proxy recording in the recording medium B117. As a result, in FIG. 8A, the file _B # 1 (307b (1)) at the time of receiving the transfer instruction is completed, and a new file _B # 2 (sequentially recording the scene # 1) 307b (2)) is generated. Further, in FIG. 8B, the file _B # 3 (307b (3)) at the time when the transfer instruction is received is set to a completed state, and a new file _B # 4 (307b) in which the scene # 2 is continuously recorded. (4)) is generated.
In step S914, the CPU 113 changes the file break timing. In the present embodiment, as described above, after generating the file break 310 using Transfer Req 401 as a trigger, the file break 310 is generated so that the file size does not exceed 1 GB.

In step S <b> 904, the CPU 113 confirms whether the scene being recorded is registered in the transfer list 500. When there is registration in the transfer list 500, the process proceeds to step S906. When there is no registration in the transfer list 500, the process proceeds to step S905.
In step S905, the CPU 113 registers the scene to be transferred in the transfer list 500. The CPU 113 that has detected the input of Transfer Req 401 in step S 902 acquires the scene number instructed to transfer by Transfer Req 401 and registers it in the transfer list 500.

  In step S <b> 906, the CPU 113 confirms whether there is a file that can be registered in the transfer list 500. The CPU 113 manages information on the scene currently being recorded. The information on the scene includes information on the files that make up the scene, and it is possible to determine whether the scene is composed of a plurality of files by the file break 310. In FIG. 8A, since the file break 310 is generated when Transfer Req 401 is input, the file _B # 1 (307b (1)) is completed and can be registered in the transfer list 500. The same applies to the file _B # 3 (307b (3)) in FIG. In this case, the process proceeds to step S907, and the transfer list 500 registration process is performed. On the other hand, if there is no file that can be registered in the transfer list 500, the process proceeds to step S909.

In step S907, the CPU 113 registers the file to be transferred in the transfer list 500. In FIG. 8A, the completed file _B # 1 (307b (1)) is registered in the transfer list 500. In FIG. 8B, the file _B # 3 (307b (3)) in the completed state is registered in the transfer list 500.
In step S <b> 908, the CPU 113 confirms whether all files that can be registered are registered in the transfer list 500. 8A and 8B, there are no other files to be registered in the transfer list 500. If there is a file to be registered, the process returns to step S907. When all the files have been registered, the process proceeds to step S909.

In step S <b> 909, the CPU 113 receives the Transfer Req 401 and notifies the user that it is registered in the transfer list 500 on the display unit 112. When the display ends, the process proceeds to step S910.
In step S910, the CPU 113 checks whether a file break 310 has occurred for a file included in the scene being recorded. In FIGS. 8A and 8B, file _B # 2 (307b (2)) and file _B # 4 (307b (4)) are generated using Transfer Req 401 as a trigger, and FIG. As shown, a file break 310 occurs when the file size of the file _B # 4 (307b (4)) reaches 1 GB. When the file break 310 is detected, the process proceeds to step S911. If the file break 310 is not detected, the process proceeds to step S913. When the file break 310 is detected, the process proceeds to step S911.

In step S911, the CPU 113 confirms whether Transfer Req 401 has been input. When Transfer Req 401 is not input, the process proceeds to step S913. When Transfer Req 401 is input, the process proceeds to step S912.
In step S912, the CPU 113 updates the transfer list 500. In FIG. 8B, the CPU 113 detecting the file break 310 registers file # 4 (307 (4)) in the transfer list 500.
In step S913, the CPU 113 checks whether a file close 309 has occurred for the scene being recorded. When Rec Stop 308 is input from the operation unit 106, the CPU 113 closes the file. In FIG. 8A, the file _A # 1 (307a (1)) and the file _B # 2 (307b (2)) are completed by the file close 309, and the file _B # 2 (307b (2)) is completed. ) Can be registered in the transfer list 500. In FIG. 8B, the file _A # 2 (307a (2)) and the file _B # 5 (307b (5)) are completed by the file close 309, and the file _B # 5 (307b (307) 5)) can be registered in the transfer list 500. When the file close 309 is detected, the process proceeds to step S915. If the file close 309 is not detected, the process returns to step S902.

In step S915, the CPU 113 confirms whether all the files registered in the transfer list 500 have been transferred. The transfer process according to the transfer list 500 is as described in the first embodiment, and the description thereof is omitted here. When all the files registered in the transfer list 500 are transferred, the process proceeds to step S916.
In step S916, the CPU 113 restores the file break timing changed in step S914. In this embodiment, the setting for generating the file break 310 so that the file size does not exceed 1 GB is set to the normal setting (the file break 310 is generated so that the file size does not exceed 4 GB). Return to

  As described above, when a transfer instruction is received during recording of image data of a scene, the file at the time when the transfer instruction is received is set to a completed state, and a new file for continuously recording the scene is generated and completed. The state file was transferred. Thereby, when there is a transfer instruction during the recording of the image data, the image data being recorded can be immediately transferred to the external device.

<Third Embodiment>
In the third embodiment, a modification example of the second embodiment will be described. In this embodiment, the difference from the second embodiment will be mainly described, and the description of the common points with the first embodiment and the second embodiment will be omitted.
In FIG. 8B, a file break 310 is generated with Transfer Req 401 as a trigger, thereby completing the file _B # 3 (307b (3)) at the time when the transfer instruction is received, and setting the scene # 2 A new file _B # 4 (307b (4)) to be continuously recorded is generated. Thereafter, a file break 310 is further generated for the file _B # 4 (307b (4)), the file _B # 4 (307b (4)) is completed, and the scene # 2 is continuously recorded. File _B # 5 (307b (5)) is generated.
Here, in the second embodiment, after the file break 310 is generated using Transfer Req 401 as a trigger, the file break timing is changed.
In contrast, in the third embodiment, if the transfer of the file _B # 3 (307b (3)) is completed during the recording of the file _B # 4 (307b (4)), the file break 310 is set. The file _B # 4 (307b (4)) is completed, and a new file _B # 5 (307b (5)) for continuously recording the scene # 2 is generated.

FIG. 10 is a flowchart showing file generation control processing and transfer list registration processing of the video camera 100 according to the third embodiment. Steps similar to those in FIG. 9 described in the second embodiment are denoted by the same reference numerals, and description thereof is omitted.
In step S909, after receiving Transfer Req 401 and notifying the user that it has been registered in the transfer list 500 on the display unit 112, in step S1001, the CPU 113 has transferred all the files registered in the transfer list 500. Confirm whether or not. The transfer process according to the transfer list 500 is as described in the first embodiment, and the description thereof is omitted here. When all the files registered in the transfer list 500 are transferred, the process proceeds to step S1002.
In step S1002, the CPU 113 generates a file break 310 for proxy recording on the recording medium B117. Thus, in FIG. 8B, the file _B # 4 (307b (4)) is completed, and a new file _B # 5 (307b (5)) for continuously recording the scene # 2 is generated. To do. Thus, when the transfer of the previous file is completed, the next file is actively closed to be in a completed state, whereby the next file can be transferred continuously.

Although the present invention has been described together with the embodiments, the above-described embodiments are merely examples of implementation in carrying out the present invention, and the technical scope of the present invention is interpreted in a limited manner by these. It must not be. That is, the present invention can be implemented in various forms without departing from the technical idea or the main features thereof.
For example, in the second embodiment, an example in which high-quality video data is recorded on the recording medium A104 and video data having a lower bit rate than the main recording is simultaneously recorded on the recording medium B117 has been described. Absent. For example, video data equivalent to the recording medium A104 may be recorded on the recording medium B117.
(Other embodiments)
The present invention supplies a program that realizes one or more functions of the above-described embodiments to a system or apparatus via a network or a storage medium, and one or more processors in a computer of the system or apparatus read and execute the program This process can be realized. It can also be realized by a circuit (for example, ASIC) that realizes one or more functions.

  DESCRIPTION OF SYMBOLS 100: Video camera, 101: Lens, 102: CMOS, 103: Camera signal processing part, 104: Recording medium A, 105: Power supply, 106: Operation part, 107: Input interface, 108: ROM, 109: RAM, 110: CODEC, 111: output interface, 112: display unit, 113: CPU, 114: communication control unit, 115: communication module, 116: communication interface, 117: recording medium B, 118: data bus

Claims (10)

An image recording apparatus for recording image data on a recording medium and transferring the image data recorded on the recording medium to an external device,
When the transfer instruction is received during the recording of the scene image data from when the recording start instruction is received until when the recording end instruction is received, the first file that is the file at the time of receiving the transfer instruction is set to a completed state, File generation control means for generating a new second file for continuously recording the scene;
An image recording apparatus comprising transfer control means for transferring a file in a completed state. It is configured to record image data simultaneously on the first recording medium and the second recording medium,
When the file generation control unit receives a transfer instruction during recording of the image data of the scene, the file generation control unit sets the first file to a completed state and generates the second file on the first recording medium. The image recording apparatus according to claim 1, wherein:   The image recording apparatus according to claim 2, wherein the first recording medium records image data having a lower bit rate than image data to be recorded on the second recording medium. During recording of the scene image data, when the file for recording the scene reaches a predetermined file size, the file is completed, and a file break means for generating a new file for continuously recording the scene,
4. The file break means changes the predetermined file size to a smaller size after receiving the transfer instruction and setting the first file to a completed state. The image recording apparatus described. When the recording time of the file for recording the scene reaches a predetermined time during the recording of the image data of the scene, a file break means for generating a new file for continuously recording the scene with the file as a completed state Prepared,
The file break means changes the predetermined time to a short time after receiving the transfer instruction and setting the first file to a completed state. Image recording device.   The image recording apparatus according to claim 4, wherein the file break unit returns the predetermined file size to the original size when transfer of all files constituting the scene is completed.   The image recording apparatus according to claim 5, wherein the file break unit returns the predetermined time to the original time when transfer of all the files constituting the scene is completed.   When the transfer of the first file is completed, the file generation control unit sets the second file to a completed state and continues the scene if the second file is not in a completed state. The image recording apparatus according to claim 1, wherein a new third file to be recorded is generated. An image recording apparatus control method for recording image data on a recording medium and transferring the image data recorded on the recording medium to an external device,
When the transfer instruction is received during the recording of the scene image data from when the recording start instruction is received until when the recording end instruction is received, the first file that is the file at the time of receiving the transfer instruction is set to a completed state, Generating a new second file to continue recording the scene;
And a step of transferring a file in a completed state. A program for controlling an image recording apparatus that records image data on a recording medium and transfers the image data recorded on the recording medium to an external device,
When the transfer instruction is received during the recording of the scene image data from when the recording start instruction is received until when the recording end instruction is received, the first file that is the file at the time of receiving the transfer instruction is set to a completed state, Processing to generate a new second file for continuously recording the scene;
A program that causes a computer to execute a process of transferring a completed file.

Images