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

Description

  The present invention relates to 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, and a control method and program thereof.

  A digital video camera (hereinafter simply referred to as a video camera) converts an optical image into an electrical signal by an imaging device, and records it as digital image data on a removable recording medium such as a built-in memory of the camera or 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 portable terminal (smartphone, tablet terminal, etc.) using various communication units such as USB and wireless LAN.

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

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

  Further, Patent Document 2 discloses a recording apparatus for recording video data obtained by a photographing unit on a recording medium which can be randomly accessed. The recording device records the video data output from the imaging device in a first file provided in the recording medium. When the division instruction unit receives a division instruction input from the user during photographing by the imaging element, the second image processing apparatus is provided with video data output from the imaging element from the time of receiving the division instruction 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 prioritized and transferred. However, the moving image file is not transferred during recording, and the recording must be stopped when it is desired to transfer the moving image file.

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

  The present invention has been made in consideration of the above-described points, and has an object of enabling image data of a scene being recorded to be transferred to an external device in accordance with a user's instruction.

  The image recording apparatus according to 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 an instruction to start recording after receiving an instruction to start recording. When receiving a transfer instruction during recording of image data of up to scenes, a new second file for making the first file, which is the file at the time of receiving the transfer instruction, complete, and continuously recording the scene File generation control means for generating a file, transfer control means for transferring a file in a completed state to a transfer destination, and combining means for combining the first file and the second file. Do.

  According to the present invention, when a transfer instruction is received during recording of image data of a scene, or when a transfer interruption instruction is received after receiving the transfer instruction, the file at the time of receiving the instruction is completed. At the same time, a new file was created to continue recording the scene, and the completed file was transferred. As a result, the image data of the scene being recorded can be transferred to the external device in accordance with the user's instruction.

FIG. 1 is a block diagram showing a schematic configuration of a video camera according to a first embodiment. FIG. 2 is a diagram showing an example of connection between a video camera according to the first embodiment and an external device. FIG. 6 is a conceptual diagram showing the relationship between the recording operation and scenes and files in the video camera according to the first embodiment. FIG. 7 is a diagram showing an example of the relationship between the recording operation, the scene, the file, and the transfer instruction in the video camera according to the first embodiment. FIG. 7 is a diagram showing an example of the relationship between the recording operation, the scene, the file, and the transfer instruction in the video camera according to the first embodiment. It is a figure for demonstrating the transfer list in 1st Embodiment. 7 is a flowchart showing transfer list registration processing of the video camera according to the first embodiment. 5 is a flowchart showing transfer control processing of the video camera according to the first embodiment. FIG. 14 is a view showing an example of the relationship between a recording operation, a scene, a file and a transfer instruction in the video camera according to the second embodiment. 10 is a flowchart showing file generation control processing and transfer list registration processing of the video camera according to the second embodiment. FIG. 14 is a view showing an example of the relationship between a recording operation, a scene, a file and a transfer instruction in the video camera according to the third embodiment. It is a flowchart which shows the file generation control processing and transfer list registration processing of the video camera which concern on 3rd Embodiment.

Hereinafter, preferred embodiments of the present invention will be described 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 which 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 104, a power supply 105, an operation unit 106, an input interface (I / F) 107, a ROM 108, a RAM 109, a CODEC 110, an output I / F 111, and a display unit 112. , CPU 113, communication control unit 114, communication module 115, and communication I / F 116, and performs data input / output via the data bus 118.

The lens 101 is a photographing lens including a focus, an aperture mechanism, and the like, and forms an optical image of a subject.
A complementary metal oxide semiconductor (CMOS) 102 is an imaging device, includes an A / D converter, and converts an optical image into an analog electrical signal and then converts it into a digital signal. The present invention is not limited to the CMOS, and may be an imaging device such as a charge coupled device image sensor (CCD).
The camera signal processing unit 103 performs predetermined pixel interpolation / reduction resizing processing, color conversion, various correction processing, and the like on the digital signal converted by the CMOS 102.
The recording medium 104 is a flash memory such as an SD memory card or a built-in memory, and records captured video data and audio data, and information necessary for control of the CPU 113.

A 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 in the recording medium 104 is selected via the operation unit 106, and a transfer instruction to transfer the selected video data to an external device (not shown) with which the communication control unit 114 communicates is performed. . When a transfer instruction is issued, the numbers of encoded files to be transferred and the groups of encoded files to be transferred are grouped together according to the format of a transfer list 500 shown in FIG. 5A described later via the CPU 113. The scene number is stored in the RAM 109.
The ROM 108 stores a program for activating the video camera 100. When an electric signal is supplied from the power source 105 by the operation unit 106, the program is read by the CPU 113 into the RAM 109.
The RAM 109 functions as a work area of 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 drive (not shown).

The CODEC 110 reproduces video data and audio data recorded in the RAM 109 or the recording medium 104, and the reproduced video data is displayed on the display unit 112. Also, the reproduced audio data is supplied to and output from a speaker (not shown). The CODEC 110 performs compression coding or decoding of video compression coding data at a predetermined bit rate and format. Although the audio is not particularly illustrated, by using the lens 101 and the CMOS 102 as a microphone and the display unit 112 as a speaker, it is possible to handle an audio signal by similar processing. At the time of video recording, audio is also recorded simultaneously with the video, and by multiplexing the video and audio by the CODEC 110, it is possible to generate video data with audio.
The output I / F 111 outputs a display signal to be displayed on the display unit 112 based on display data such as a GUI (Graphical User Interface) generated by the CPU 113 according to a program.

The CPU 113 executes the program loaded from the ROM 108 to the RAM 109. The CPU 113 manages information related to the recording of scenes and files when recording video. The CPU 113 executes 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), and management of transfer list.
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 showing an example of connection between the video camera 100 and an external device according to the first embodiment. The video camera 100 can be connected to an external device by at least one of wired connection and wireless connection described below.
FIG. 2A is a schematic view 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 connected via a relay device such as a network hub. The present invention can be applied to communication using a wired medium such as a wired LAN or USB.
FIG. 2B is a schematic view 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 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 view showing the relationship between the recording operation, the scene and the file in the video camera 100 according to the first embodiment. The horizontal axis 300 represents a time axis, and indicates that time goes to 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 the recording preparation state. Rec Pause 302 indicates the recording preparation state of the video camera 100. The recording preparation state is a state in which the recording state is immediately entered when Rec Start 303 is instructed.

  A 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 the recording state. When the main 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, the signal input via the lens 101 and the CMOS 102 is encoded as a file format to be recorded on the recording medium 104 by the CODEC 110 and sequentially stored in the RAM 109. When the file stored in the RAM 109 has an arbitrary capacity, the file is recorded on the recording medium 104. This process is sequentially performed until Rec Stop 308 is instructed.

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

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

  A 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. The point to be noted here is that it is not synonymous with the file (File) 307 described later. In view of the file format of the recording medium 104, when the data recorded on the recording medium 104 has a data size equal to or larger than the file upper limit capacity of the file format, it is necessary to divide the file. This work is called File Break 310. The scene 306 is a definition that handles the file 307 including the file break as one. The scene 306 is assigned a number each time the Rec Start 303 is instructed, and is operated as a scene # 1, a scene # 2, and so on.

  The file 307 is a video data file recorded on the recording medium 104. When the data stored in the RAM 109 reaches an arbitrary capacity triggered by the Rec Start 303, the data starts to be stored in the recording medium 104 as a file 307. In the recording state, since the video data is sequentially written to the RAM 109, the data stored in the file 307 also sequentially increases. Until the file close 309 or the file break 310 occurs, the file 307 is in an unfinished state and can not be read from other processes. When the file close 309 or the file break 310 occurs, the file 307 is completed. Each time the file 307 is completed, a number is assigned, and the file # 1, the file # 2,.

The file close 309 is a file operation for setting the files 307 sequentially recorded on the recording medium 104 by the recording operation of the video camera 100 to a completed state 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.
The file break 310 is a file operation when the file is divided and recorded when the file of the specific size or more is stored in the recording medium 104 in view of the file format of the recording medium 104. The CPU 113 identifies the file format of the recording medium 104 and automatically performs this file operation in the video camera 100. For this reason, if the user inputs Rec Start 303 only once from the operation unit 106, the file 307 is output by the file break 310 when the recording time continues for a predetermined period or more and the file 307 is written up to the upper limit of the file format of the recording medium 104 While being completed, generation of a new file 307 is started.

FIGS. 4A and 4B are diagrams showing an example of the relationship between the recording operation, the scene, the file, and the transfer instruction in the video camera 100 according to the first embodiment.
FIG. 4A (a) shows a state in which a transfer instruction has been made to transfer a scene being recorded to an external device in the recording state (REC 304) of the video camera 100.
Scene # 1 (306 (1)) assumes initial recording on the recording medium 104, and the assigned number is “# 1”.
File # 1 (307 (1)), like scene # 1 (306 (1)), assumes initial recording on the recording medium 104, and the assigned number is “# 1”.
Transfer Req 401 shows an input operation by the operation unit 106 instructing transfer of the scene # 1 (306 (1)) being recorded to an external device.
When the Rec Stop 308 is instructed, the file close 309 completes the unfinished file # 1 (307 (1)) as a file during recording.

FIG. 4A (b) shows a state in which a transfer instruction has been made to transfer a recorded scene to an external device in a recording preparation state (Rec Pause 302) after the recording state of the video camera 100. In FIG. 4A (b), it is assumed that the file break 310 has not occurred.
Scene # 2 (306 (2)) assumes a scene where the second Rec Start 303 is instructed, and the assigned number is "# 2".
File # 2 (307 (2)), like scene # 2 (306 (2)), assumes recording of the second file on the recording medium 104, and the assigned number is "# 2". There is.
When the Rec Stop 308 is instructed, the file close 309 completes the unfinished file # 2 (307 (2)) in the recording state as a file.
Transfer Req 401 indicates an input operation by the operation unit 106 instructing transfer of the scene # 2 (306 (2)) for which recording has ended to an external device.

FIG. 4A (c) shows a recording state (REC 304) of the video camera 100, in which a transfer instruction has been issued to transfer a scene being recorded to an external device before the occurrence of the file break 310.
Scene # 3 (306 (3)) assumes a scene where the third Rec Start 303 is instructed, and the assigned number is “# 3”. In scene # 3 (306 (3)), a file break 310 occurs for file # 3 (307 (3)) and file # 3 (307 (3)) is completed, and then new file # 4 is generated. (307 (4)) is generated.
File # 3 (307 (3)) assumes recording of the third file on the recording medium 104, and the assigned number is “# 3”. File # 4 (307 (4)) is a file generated to continue recording scene # 3 after file break 310 occurs for file # 3 (307 (3)).
Transfer Req 401 indicates an input operation by the operation unit 106 instructing transfer of 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, in which a transfer instruction has been issued to transfer a scene being recorded to an external device after the occurrence of the file break 310.
Scene # 4 (306 (4)) assumes a scene due to the fourth Rec Start 303 being instructed, and the assigned number is “# 4”. In scene # 4 (306 (4)), a file break 310 occurs for file # 5 (307 (5)) and file # 5 (307 (5)) is completed, and then new file # 6 is generated. (307 (6)) is generated.
File # 5 (307 (5)) assumes recording of the fifth file on the recording medium 104, and the assigned number is “# 5”. File # 6 (307 (6)) is a file generated to continue recording scene # 4 after file break 310 occurs for file # 5 (307 (5)).
Transfer Req 401 indicates an input operation by the operation unit 106 instructing transfer of the scene # 4 (306 (4)) being recorded to an external device.

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

FIG. 5 is a diagram for explaining the transfer list in the first embodiment and the method of registration thereof.
The configuration of the transfer list 500 will be described with reference to FIG. 5 (a). The transfer list 500 is configured to register scene information and file information.
Lists 510, 520, 530,... Are scene information registration tables, which register scene numbers for which transfer is instructed. In this table, the number of tables is determined by the number of registrations of the scene instructed to be transferred. 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, which register file numbers that make up a scene registered in the list 520. The same applies to the subsequent lists 530, and so on. Determine the number of tables according to the maximum number of files that make up one scene. In this example, there are three file information registration tables, and three files can be registered for one scene.
The number of scene information registration tables and the number of file information registration tables can be operated with the number according to the system.

FIG. 6 is a flowchart showing transfer list registration processing of the video camera 100 according to the first embodiment.
As shown in FIG. 4A and FIG. 4B, the video camera 100 confirms the recording operation when Transfer Req 401 which is the transfer instruction is input, and the presence or absence of the file break 310, and registers the transfer list 500.
The operation of the video camera 100 when Transfer Req 401 is input will be described below with reference to FIGS. 4A, 4 B, and 5. Note that, asynchronously to the processing of FIG. 6, the user can arbitrarily transition 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 drawing, 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 the video camera 100 is in the recording state or the recording preparation state. In the states other than the recording state and the recording preparation state, this process is not performed, and step S601 is repeated. If it is 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. If Transfer Req 401 is input, the process proceeds to step S603.
In step S603, the CPU 113 confirms whether the video camera 100 is in the recording state. If it is in the recording state, the process proceeds to step S604. If it is not the recording state, the process proceeds to step S650.

Steps S604 to S613 are processes 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). The scene is recorded for the first time at the time of input of the Trasfer Req 401 in FIG. 4A (a), and all the lists 510 to 550 are unregistered. The CPU 113 that has detected the input of the Processor Req 401 in step S 602 acquires the scene number instructed to be transferred by the Transfer Req 401, and registers the acquired scene number in the list 510. In this example, the scene # 1 (306 (1)) corresponds, and as shown in FIG. 5B, the scene # 1 is registered in the list 510. Also in FIG. 4A (c) and FIG. 4B (a), there is scene information registration processing of the transfer list 500 according to this step, and as shown in FIG. 5 (d), the scene # 3 (306 (3 (3 ) Is registered, and scene # 4 (306 (4)) is registered in list 540, as shown in FIG. 5 (f).

  In step S 605, the CPU 113 confirms whether there is a file that can be registered in the transfer list 500. The CPU 113 manages information of the scene currently being recorded. The information on the scene includes information on files that make up the scene, and the file break 310 makes it possible to determine whether the scene is composed of a plurality of files. In FIG. 4A (a), file # 1 (307 (1)) is in an incomplete state at the time of input of Transfer Req 401, and can not be registered in the transfer list 500. The same applies to 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 unfinished at the time of Transfer Req 401, but file # 5 (307 (5)) is completed by file break 310. Yes, and can be registered in the transfer list 500. In this case, the process transitions to step S606, and registration processing of the transfer list 500 is performed.

In step S 606, 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), as shown in FIG. 5 (f), the scenes # 1 to # 3 have already been registered in the lists 510, 520, and 530. As shown in FIG. 5F, the file # 5 (307 (5)) is registered in the list 541 of the scene # 4 which has not been registered before the execution of step S606. When step S606 ends, the process moves to step S607.
In step S 607, the CPU 113 confirms whether all the registrable files have been registered in the transfer list 500. In FIG. 4B (a), only file # 5 (307 (5)) is in the completed state at the time of input of Transfer Req 401, but it is also assumed that a plurality of files are generated by file break 310. . 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. If 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 of the fact that it has been registered in the transfer list 500 from the display unit 112. When the display is completed, the process proceeds to step S609.
In step S609, the CPU 113 confirms whether or not the file break 310 has occurred for the 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 unfinished at the time of Transfer Req 401 input, but then the file A break 310 may occur and become complete. If 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 having detected the file break 310 registers the file # 3 (307 (3)) in the transfer list 500. That is, when the file # 3 (307 (3)) is completed due to the file break 310 in FIG. 4A (c), the file # 3 is registered in the list 531 as shown in FIG. 5 (d). Thereafter, if file break 310 occurs further, file # 4 (307 (4)) is registered in list 532 as shown in FIG. 5 (e). Similarly, when file # 6 (307 (6)) is completed due to 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 confirms whether the file close 309 has occurred for the scene being recorded. When the Rec Stop 308 is input from the operation unit 106, the CPU 113 closes the file. In FIG. 4A (a), at the time of input of Transfer Req 401, the file # 1 (307 (1)) is in an unfinished state, and waits for the file close 309 to occur. If 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 completed by the file close 309 in the transfer list 500. In FIG. 4A (a), the file # 1 (307 (1)) is completed by the file close 309 and can be registered in the transfer list 500. As shown in FIG. 5B, the file # 1 (307 (1)) is registered in the list 511, and the process proceeds to step S613.
In step S613, the CPU 113 performs file close registration in which data that the scene is completed is written in the transfer list 500. After detecting the file close 309 and registering the file in the transfer list 500, the CPU 113 registers in the transfer list 500 that the scene is completed. 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 confirms whether the video camera 100 is in a recording preparation state. If it is in the recording preparation state, the process goes to step S651. If it is not the recording preparation state, the process goes to step S657.
Steps S651 to S656 are processes when Transfer Req 401 is input in the recording preparation state, as shown in FIGS. 4A (b) and 4B (b).
In step S 651, the CPU 113 confirms whether there is a scene that can be registered in the transfer list 500. The CPU 113 determines the presence or absence of the scene recorded immediately before. Since the CPU 113 performs recording control on the recording medium 104, 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), as shown in FIG. 5 (c), the scene # 1 has been registered in the list 510. The CPU 113 that has detected the input of the Processor Req 401 in step S 602 acquires the scene number instructed to be transferred by the Transfer Req 401, and registers the scene number in the list 520. In this example, the scene # 2 (306 (2)) corresponds, and as shown in FIG. 5C, the scene # 2 is registered in the list 520. Also in FIG. 4B (b), there is scene information registration processing of the transfer list 500 according to this step, and as shown in FIG. 5 (h), the scene # 5 (306 (5)) is registered in the list 550.

  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 S 653 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 which has not been registered before the execution of step S653. Also in FIG. 4B (b), there is a file information registration process of the transfer list 500 by this step. As shown in FIG. 5H, files # 7 (307 (7)) and # 8 (307 (8)) are displayed in the lists 551 and 552 of the scene # 5 which has not been registered before step S653. Register When step S653 ends, the process moves to step S654.

In step S 654, the CPU 113 confirms whether all the registrable files have been registered in the transfer list 500. If the file has already been registered, the process proceeds to step S655. If there is an unregistered file, the process returns to step S653. In FIG. 4B (b), the file # 7 (307 (7)) is registered in the first step S653. Thereafter, when it is detected in step S654 that the file # 8 (307 (8)) is not registered, the 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 that the scene is completed is written in the transfer list 500. In step S655, since the video camera 100 is in preparation for recording and there is only a scene whose file has already been closed, processing for monitoring the file close is not necessary. In FIG. 4A (b), the file close is registered in the list 522 as shown in FIG. 5 (c). Also, in FIG. 4B (b), the file close is registered in the list 553 as shown in FIG. 5 (h). After the end of this step, the process moves to step S656.
In step S 656, the CPU 113 receives the Transfer Req 401 and notifies the user of the fact that it has been registered in the transfer list 500 through the display unit 112. When step S656 is completed, 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 has been issued from the operation unit 106, a scene to be registered in the transfer list 500 does not exist, and the transfer process is not performed. The user is notified by the display unit 112. When step S657 is completed, the transfer list registration process is completed.

The video camera 100 transfers the scene to the external device in accordance with 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 transitions 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 transitions to step S703.
In step S703, the CPU 113 confirms the presence or absence of 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, confirmation is continued until the registered file is found.
In step S704, the CPU 113 confirms whether there is a file that can be transferred to the external device among the files registered in the transfer list 500. If there is a transferable file, the process proceeds to step S 705. If there is no transferable file, the check is continued until a transferable file is found.

In step S705, the CPU 113 starts transfer of a file registered in the transfer list 500 and transferable to an 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 S 707. If there is no transfer error, the process proceeds to step S 708.
In step S 707, the CPU 113 confirms whether the file in which the transfer error has occurred can be retransmitted. If the file can be retransmitted, the process proceeds to step S 705, and the file transfer to the external device is started again. If retransmission is not possible, this processing is completed.

In step S 708, the CPU 113 confirms whether transfer of the file whose transfer has been started in step S 705 is completed. If the transfer is 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 transfer.
In step S709, the CPU 113 updates the file pointer in the transfer list 500 because there is a file for which transfer has been completed in step S708, and the process proceeds to step S710.
In step S 710, the CPU 113 confirms whether all files related to the scene referred to on the transfer list 500 have been transferred, and 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 returns to step S703.

Second Embodiment
Next, a second embodiment will be described. The configuration and basic operation of the video camera 100 are the same as those described in the first embodiment, and in the following, differences from the first embodiment will be mainly described.
FIG. 8 is a view showing an example of the relationship between the recording operation, the scene, the file, and the transfer instruction in the video camera 100 according to the second embodiment.
FIG. 8A shows a state in which a transfer instruction has been issued to transfer a scene being recorded to an external device in the recording state (REC 304) of the video camera 100.
Scene # 1 (306 (1)) assumes initial recording on the recording medium 104, and the assigned number is “# 1”.
File # 1 (307 (1)), like scene # 1 (306 (1)), assumes initial recording on the recording medium 104, and the assigned number is “# 1”.
Transfer Req 401 shows an input operation by the operation unit 106 instructing transfer of the scene # 1 (306 (1)) being recorded to an external device.
In this case, in order to immediately transfer the file # 1 (307 (1)) recorded on the recording medium 104, a file break 310 is generated using Transfer Req 401 as a trigger. As a result, the file # 1 (307 (1)) at the time of receiving the transfer instruction is completed, and a new file # 2 (307 (2)) is generated to continue recording the scene # 1.
When the Rec Stop 308 is instructed, the file close 309 completes the unfinished file # 2 (307 (2)) in the recording state as a file.

FIG. 8B shows a state in which a transfer instruction has been made to transfer a scene being recorded to an external device in the recording state (REC 304) of the video camera 100.
Scene # 2 (306 (2)) assumes a scene where the second Rec Start 303 is instructed, and the assigned number is "# 2".
File # 3 (307 (3)) assumes recording of the third file on the recording medium 104, and the assigned number is “# 3”.
Transfer Req 401 indicates an input operation by the operation unit 106 instructing transfer of the scene # 2 (306 (2)) being recorded to an external device.
In this case, in order to immediately transfer the file # 3 (307 (3)) recorded on the recording medium 104, a file break 310 is generated using Transfer Req 401 as a trigger. As a result, the file # 3 (307 (3)) at the time of receiving the transfer instruction is completed, and a new file # 4 (307 (4)) is generated to continue recording the scene # 2.
When the combined file size of file # 3 (307 (3)) and file # 4 (307 (4)) reaches the file format upper limit of file capacity, file # 4 (307 (4)) is processed. File break 310 occurs. As a result, the file # 4 (307 (4)) is brought into a completed state, and a new file # 5 (307 (5)) is generated to continue recording the scene # 2. After the file # 5 (307 (5)), the file break 310 is generated when the file size of its own reaches the file capacity limit of the file format. In FIG. 8B, the file break 310 occurs for the file # 5 (307 (5)), and the file # 5 (307 (5)) is completed, and the scene # 2 is continuously recorded. File # 6 (307 (6)) is generated.
When the Rec Stop 308 is instructed, the file close 309 completes the unfinished file # 6 (307 (6)) as a file during recording.

FIG. 8C shows a state in which a transfer instruction has been made to transfer a scene being recorded to an external device in the recording state (REC 304) of the video camera 100.
Scene # 3 (306 (3)) assumes a scene where the third Rec Start 303 is instructed, and the assigned number is “# 3”.
File # 7 (307 (7)) assumes recording of the seventh file on the recording medium 104, and the assigned number is “# 7”.
Transfer Req 401 indicates an input operation by the operation unit 106 instructing transfer of the scene # 3 (306 (3)) being recorded to an external device.
In this case, in order to immediately transfer the file # 7 (307 (7)) recorded on the recording medium 104, a file break 310 is generated using Transfer Req 401 as a trigger. As a result, the file # 7 (307 (7)) at the time of receiving the transfer instruction is completed, and a new file # 8 (307 (8)) is generated to continue recording the scene # 3.
Then, when the file size obtained by adding file # 7 (307 (7)) and file # 8 (307 (8)) reaches the file maximum capacity of the file format, file # 8 (307 (8)) is processed. File break 310 occurs. As a result, file # 8 (307 (8)) is brought into a completed state, and new file # 9 (307 (9)) is generated to continue recording scene # 3. After the file # 9 (307 (9)), the file break 310 is generated when the file size of its own reaches the file capacity limit of the file format. In FIG. 8C, a file break 310 occurs for file # 9 (307 (9)), and file # 9 (307 (9)) is completed, and scene # 3 is continuously recorded. File # 10 (307 (10)) is generated.
When the Rec Stop 308 is instructed, the file close 309 completes the unfinished file # 10 (307 (10)) as a file during recording.
Here, the file combination 801 is executed with the Rec Stop 308 as a trigger. In file combination 801, files divided by file break 310 triggered by Transfer Req 401, in this example, files # 7 (307 (7)) and # 8 (307 (8)) are combined, and file # 11 is generated. (307 (11)) is generated. This avoids an unnecessary increase in the number of files. Here, although the combined file is renamed as file # 11 so as to be the same as the file recorded last, it is not limited thereto. The combined file is named file # 7, and file # 9 (307 (9)) and file # 10 (307 (10)) are renamed as file # 8 and file # 9, respectively, so that there is no discontinuity in the file numbers. You may do it.

FIG. 9 is a flowchart showing file generation control processing and transfer list registration processing of the video camera 100 according to the second embodiment.
When Transfer Req 401, which is a transfer instruction, is input as shown in FIG. 8, the video camera 100 generates a file break 310 and registers the transfer list 500. The video camera 100 transfers the scene to an external device according to the transfer list 500.
In step S901, the CPU 113 confirms whether the video camera 100 is in the recording state. In a state other than the recording state, this process is not performed, and step S901 is repeated. If in the recording state, the process proceeds to step S902.
In step S902, the CPU 113 confirms whether Transfer Req 401 has been input. If Transfer Req 401 is not input, the process proceeds to step S 910. If Transfer Req 401 is input, the process proceeds to step S 903.

  In step S 903, the CPU 113 generates a file break 310. Thus, in FIG. 8A, while the file # 1 (307 (1)) at the time of receiving the transfer instruction is completed, a new file # 2 (307 (2) for continuously recording the scene # 1 is obtained. Generate). Also, in FIG. 8B, file # 3 (307 (3)) at the time of receiving the transfer instruction is made complete, and new file # 4 (307 (4)) continues recording scene # 2. Generate Also, in FIG. 8C, file # 7 (307 (7)) at the time of receiving the transfer instruction is made complete, and new file # 8 (307 (8)) continues recording scene # 3. Generate

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

  In step S 906, the CPU 113 confirms whether there is a file that can be registered in the transfer list 500. The CPU 113 manages information of the scene currently being recorded. The information on the scene includes information on files that make up the scene, and the file break 310 makes it possible to determine whether the scene is composed of a plurality of files. In FIG. 8A, the file break 310 is generated at the input time of the Transfer Req 401, so the file # 1 (307 (1)) is completed and can be registered in the transfer list 500. The same applies to file # 3 (307 (3)) in FIG. 8 (b) and file # 7 (307 (7)) in FIG. 8 (c). In this case, the process transitions to step S 907, and registration processing of the transfer list 500 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 S 907, the CPU 113 registers the file to be transferred in the transfer list 500. In FIG. 8A, file # 1 (307 (1)) in the completed state is registered in transfer list 500. Further, in FIG. 8B, file # 3 (307 (3)) in the completed state is registered in transfer list 500. Further, in FIG. 8C, file # 7 (307 (7)) in the completed state is registered in transfer list 500.
In step S 908, the CPU 113 confirms whether all the registrable files have been registered in the transfer list 500. In FIG. 8, there are no other files registered in the transfer list 500. If there is a file to be registered, the process returns to step S 907. If all the files have been registered, the process proceeds to step S909.
In step S 909, the CPU 113 receives the Transfer Req 401 and notifies the user of the fact that it has been registered in the transfer list 500 through the display unit 112. When the display ends, the process transitions to step S910.

  In step S 910, the CPU 113 confirms whether or not the file break 310 has occurred for the file included in the scene being recorded. When the file size of the file recorded on the recording medium 104 reaches the file format upper limit file capacity, the file is divided by the control of the CPU 113. In FIG. 8B, when the combined file size of file # 3 (307 (3)) and file # 4 (307 (4)) reaches the file format upper limit file capacity, file # 4 (307 (307 (3)). A file break 310 occurs for 4). Thereafter, when the file size of the file reaches the file format upper limit file capacity, the file break 310 occurs. Also, in FIG. 8C, when the file size obtained by adding file # 7 (307 (7)) and file # 8 (307 (8)) reaches the file format upper limit of file capacity, file # 8 ( A file break 310 occurs with respect to 307 (8). Thereafter, when the file size of the file reaches the file format upper limit file capacity, the file break 310 occurs. If 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 S 913.

In step S 911, the CPU 113 confirms whether Transfer Req 401 has been input. If Transfer Req 401 is not input, the process proceeds to step S 913. If Transfer Req 401 is input, the process proceeds to step S 912.
In step S912, the CPU 113 updates the transfer list 500. In FIG. 8B, file # 4 (307 (4)) and file # 5 (307 (5)) are registered in transfer list 500. Further, in FIG. 8C, file # 9 (307 (9)) is registered in transfer list 500.

  In step S 913, the CPU 113 confirms whether the file close 309 has occurred for the scene being recorded. When the Rec Stop 308 is input from the operation unit 106, the CPU 113 closes the file. In FIG. 8A, file # 2 (307 (2)) is completed by file close 309 and can be registered in transfer list 500. Further, in FIG. 8B, file # 6 (307 (6)) is completed by file close 309 and can be registered in transfer list 500. Further, in FIG. 8C, file # 10 (307 (10)) is completed by file close 309 and can be registered in transfer list 500. If the file close 309 is detected, the process proceeds to step S914. If the file close 309 is not detected, the process returns to step S902.

In step S 914, the CPU 113 confirms whether Transfer Req 401 has been input. If Transfer Req 401 is not input, this process ends. If Transfer Req 401 is input, the process proceeds to step S 915.
In step S 915, the CPU 113 updates the transfer list 500. In FIG. 8A, file # 2 (307 (2)) that has been completed by file close 309 is registered in transfer list 500. Further, in FIG. 8B, file # 6 (307 (6)) that has been completed by file close 309 is registered in transfer list 500. Further, in FIG. 8C, file # 10 (307 (10)) that has been completed by file close 309 is registered in transfer list 500.

In step S916, the CPU 113 integrates the file which has been subjected to the file break by Transfer Req 401. In FIG. 8C, file # 7 (307 (7)) and file # 8 (307 (8)) are combined to generate a file. For example, the combined file is renamed as file # 11 (307 (11)) so as to be sequential with the file recorded last.
In step S917, the CPU 113 updates the transfer list 500. In FIG. 8C, file # 11 (307 (11)) combined in step S916 is registered in transfer list 500.
In step S 918, the CPU 113 performs file close registration in which data that the scene is completed is written in the transfer list 500. After the file close 309 is detected by the CPU 113 and the file is registered in the transfer list 500, the fact that the scene is completed is registered in the transfer list 500.

In step S919, the CPU 113 stores the number of the coupled file in the RAM 109. In FIG. 8C, files # 7 and # 8, which are the numbers of files # 7 and # 8, are stored. Although the file number is given as an example here, it may not be the number as long as the file can be identified.
In step S920, the CPU 113 confirms whether all the files registered in the transfer list 500 have been transferred. The transfer processing according to the transfer list 500 is as described in the first embodiment, and is performed asynchronously with the processing of this flowchart. When all the files registered in the transfer list 500 are transferred, the process proceeds to step S921.
In step S921, the CPU 113 deletes the file corresponding to the file number stored in step S919 from the transfer destination FTP server.
In this embodiment, in order to maintain consistency between the file structure recorded in the recording medium 104 of the video camera 100 and the file structure in the transfer destination FTP server, the processes in steps S916 to S921 are performed. However, the deletion process in step S921 does not necessarily have to be performed. For example, when the deletion process in step S 921 is not performed, a process may be performed such that information on connection is sent to the FTP server as meta information.

Third Embodiment
Next, a third embodiment will be described. The configuration and basic operation of the video camera 100 are the same as those described in the first and second embodiments, and in the following, differences from the first and second embodiments will be mainly described.
FIG. 10 is a diagram showing an example of the relationship between the recording operation, the scene, the file, and the transfer instruction in the video camera 100 according to the third embodiment.
FIG. 10 shows a state in which a transfer instruction has been issued to transfer a scene being recorded to an external device in the recording state (REC 304) of the video camera 100.
Scene # 1 (306 (1)) assumes initial recording on the recording medium 104, and the assigned number is “# 1”.
File # 1 (307 (1)), like scene # 1 (306 (1)), assumes initial recording on the recording medium 104, and the assigned number is “# 1”.
Transfer Req 401 shows an input operation by the operation unit 106 instructing transfer of the scene # 1 (306 (1)) being recorded to an external device.
A Cancel Transfer Req 1001 indicates an input operation by the operation unit 106 instructing to interrupt the transfer of the scene # 1 (306 (1)) being recorded, which is instructed to be transferred by the Transfer Req 401.
In this case, up to file # 1 (307 (1)) recorded in the recording medium 104 is targeted for transfer, and file transfer 310 is triggered by Cancel Transfer Req 1001 to stop transfer of the subsequent files. . As a result, the file # 1 (307 (1)) at the time of receiving the transfer interruption instruction is made complete, and a new file # 2 (307 (2)) for continuously recording the scene # 1 is generated. Since the file # 2 (307 (2)) is instructed to interrupt the transfer, the file is not registered in the transfer list 500 even if there is a file close 309 thereafter.
When the Rec Stop 308 is instructed, the file close 309 completes the unfinished file # 2 (307 (2)) in the recording state as a file.
The file break 310 after the file # 2 (307 (2)) and the file combination after the Rec Stop 308 are the same processes as in the second embodiment, and thus the description thereof is omitted.

FIG. 11 is a flowchart showing file generation control processing and transfer list registration processing of the video camera 100 according to the third embodiment.
When Cancel Transfer Req 1001 which is a transfer interruption instruction is input as shown in FIG. 10, the video camera 100 generates a file break 310 and registers the transfer list 500. The video camera 100 transfers the scene to an external device according to the transfer list 500.
In step S1101, the CPU 113 confirms whether the video camera 100 is in the recording state. In a state other than the recording state, this process is not performed, and step S1101 is repeated. If in the recording state, the process proceeds to step S1102.
In step S1102, the CPU 113 confirms whether Transfer Req 401 has been input. If Transfer Req 401 is not input, the process proceeds to step S1109. If Transfer Req 401 is input, the process proceeds to step S1103.

In step S 1103, the CPU 113 confirms whether the scene being recorded is registered in the transfer list 500. If the transfer list 500 is registered, the process proceeds to step S1105. If the transfer list 500 is not registered, the process proceeds to step S1104.
In step S1104, the CPU 113 registers the scene to be transferred in the transfer list 500. In step S 1102, the CPU 113, which has detected the input of the Processor Req 401, acquires the scene number instructed to be transferred by the Transfer Req 401, and registers the acquired scene number in the transfer list 500.

  In step S1105, the CPU 113 confirms whether there is a file that can be registered in the transfer list 500. The CPU 113 manages information of the scene currently being recorded. The information on the scene includes information on files that make up the scene, and the file break 310 makes it possible to determine whether the scene is composed of a plurality of files. In FIG. 10, file # 1 (307 (1)) is in an incomplete state at the time of input of Transfer Req 401, and can not be registered in transfer list 500. In this case, the process transitions to step S1108, and registration processing of the transfer list 500 is performed. On the other hand, if there is a file that can be registered in the transfer list 500, the process proceeds to step S1106.

In step S1106, the CPU 113 registers the file to be transferred in the transfer list 500.
In step S1107, the CPU 113 confirms whether all the registrable files have been registered in the transfer list 500 or not. If there is a file to be registered, the process returns to step S1106. If all the files have been registered, the process proceeds to step S1108.
In step S1108, the CPU 113 receives the Transfer Req 401 and notifies the user of the fact that it has been registered in the transfer list 500 by the display unit 112. When the display ends, the process transitions to step S1109.

In step S1109, the CPU 113 confirms whether Cancel Transfer Req 1001 has been input. If Cancel Transfer Req 1001 is not input, the process proceeds to step S1116. If Cancel Transfer Req 1001 is input, the process proceeds to step S1110.
In step S 1110, the CPU 113 confirms whether the scene being recorded is registered in the transfer list 500. In FIG. 10, it is confirmed whether the scene # 1 (306 (1)) is registered in the transfer list 500 or not. If not registered, the process proceeds to step S1116. If registered, the process proceeds to step S1111.

At step S 1111, the CPU 113 generates a file break 310. Thus, in FIG. 10, while the file # 1 (307 (1)) at the time of receiving the transfer interruption instruction is made complete, a new file # 2 (307 (2)) in which the scene # 1 is continuously recorded is created. Generate
In step S1112, the CPU 113 confirms whether there is a file that can be registered in the transfer list 500. The CPU 113 manages information of the scene currently being recorded. The information on the scene includes information on files that make up the scene, and the file break 310 makes it possible to determine whether the scene is composed of a plurality of files. In FIG. 10, since the file break 310 is generated at the time of input of Cancel Transfer Req 1001, the file # 1 (307 (1)) is completed and can be registered in the transfer list 500. In this case, the process transitions to step S1113 and registration processing of the transfer list 500 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 S1115.

In step S1113, the CPU 113 registers the file to be transferred in the transfer list 500. In FIG. 10, file # 1 (307 (1)) in the completed state is registered in transfer list 500.
In step S1114, the CPU 113 confirms whether all the registrable files have been registered in the transfer list 500 or not. In FIG. 10, there are no other files registered in the transfer list 500. If there is a file to be registered, the process returns to step S1113. If all the files have been registered, the process proceeds to step S1115.
In step S1115, the CPU 113 receives the Cancel Transfer Req 1001, and notifies the user of the fact that the registration in the transfer list 500 has been cancelled. When the display ends, the process transitions to step S1116.

  In step S1116, the CPU 113 confirms whether or not the file break 310 has occurred in the file included in the scene being recorded. When the file size of the file recorded on the recording medium 104 reaches the file format upper limit file capacity, the file is divided by the control of the CPU 113. If the file break 310 is detected, the process proceeds to step S1117. If the file break 310 is not detected, the process proceeds to step S1119.

In step S1117, the CPU 113 confirms whether Transfer Req 401 has been input. The input here means that Cancel Transfer Req 1001 has not canceled the registration to the transfer list. If Transfer Req 401 is not input, the process proceeds to step S1119. If Transfer Req 401 is input, the process proceeds to step S1118.
In step S1118, the CPU 113 updates the transfer list 500.
In step S1119, the CPU 113 confirms whether the file close 309 has occurred for the scene being recorded. When the Rec Stop 308 is input from the operation unit 106, the CPU 113 closes the file. In FIG. 10, file # 2 (307 (2)) is completed by file close 309 and can be registered in transfer list 500. If the file close 309 is detected, the process proceeds to step S1120. If the file close 309 is not detected, the process returns to step S1102.

In step S1120, the CPU 113 confirms whether Transfer Req 401 has been input. The input here means that Cancel Transfer Req 1001 has not canceled the registration to the transfer list. If Transfer Req 401 is not input, this process ends. If Transfer Req 401 is input, the process proceeds to step S1121.
In step S1121, the CPU 113 updates the transfer list 500. In FIG. 10, file # 2 (307 (2)) that has been completed by file close 309 is registered in transfer list 500.

  In step S1122, the CPU 113 performs file close registration in which data that the scene is completed is written in the transfer list 500. After the file close 309 is detected by the CPU 113 and the file is registered in the transfer list 500, the fact that the scene is completed is registered in the transfer list 500.

In step S1123, the CPU 113 stores the number of the coupled file in the RAM 109.
In step S1124, the CPU 113 confirms whether all the files registered in the transfer list 500 have been transferred. The transfer processing according to the transfer list 500 is as described in the first embodiment, and is performed asynchronously with the processing of this flowchart. When all the files registered in the transfer list 500 are transferred, the process proceeds to step S1125.
In step S1125, the CPU 113 deletes the file corresponding to the file number stored in step S1123 from the transfer destination FTP server.
In this embodiment, in order to maintain consistency between the file structure recorded in the recording medium 104 of the video camera 100 and the file structure in the transfer destination FTP server, the processes in steps S1122 to S1125 are performed. However, the deletion process in step S1125 does not necessarily have to be performed. For example, when the deletion process in step S1125 is not performed, a process may be performed such that information on connection is sent to the FTP server as meta information.
In the third embodiment, the form in which the file break 310 is not generated with Transfer Req 401 as a trigger has been described. However, as in the second embodiment, the file break 310 is generated with Transfer Req 401 as a trigger. It is also good.

As mentioned above, although the present invention was explained with an embodiment, the above-mentioned embodiment shows only an example of the embodiment in the case of carrying out the present invention, and the technical scope of the present invention is interpreted restrictively by these. It is a must-have. That is, the present invention can be implemented in various forms without departing from the technical concept or the main features thereof.
(Other embodiments)
The present invention supplies a program that implements one or more functions of the above-described embodiments to a system or apparatus via a network or storage medium, and one or more processors in a computer of the system or apparatus read and execute the program. Can also be realized. It can also be implemented by a circuit (eg, an ASIC) that implements one or more functions.

  100: Video camera, 101: Lens, 102: CMOS, 103: Camera signal processing unit, 104: Recording medium, 105: Power supply, 106: Operation unit, 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, 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 recording of the image data of the scene from the reception of the recording start instruction to the reception of the recording end instruction, the first file, which is the file at the time of receiving the transfer instruction, is completed. File generation control means for generating a new second file for continuously recording the scene;
Transfer control means for transferring a completed file to a transfer destination;
An image recording apparatus comprising: combining means for combining the first file and the second file.   The image recording apparatus according to claim 1, wherein the combining unit combines the first file and the second file after stopping recording of the image data of the scene.   3. The image recording apparatus according to claim 1, wherein at least one of the file combined by the combining unit and information on the combination is transferred to the transfer destination.   4. The image recording apparatus according to claim 3, wherein the first file and the second file are deleted from the transfer destination. 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,
The file is a file at the time when the transfer interruption instruction is received when the transfer interruption instruction is received after receiving the transfer instruction during recording of the image data of the scene from the reception of the recording start instruction to the reception of the recording end instruction. File generation control means for generating a new second file for recording the scene continuously while setting the first file as a complete state;
An image recording apparatus comprising: transfer control means for transferring a completed file to a transfer destination. The file generation control means generates a file break each time a predetermined file size is reached while recording the image data of the scene, and completes the file reaching the predetermined file size, and the scene Create a new file to continue recording
6. A file break is generated when a file size obtained by adding together the first file and the second file reaches the predetermined file size. Image recording apparatus as described. A control method of an image recording apparatus which 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 recording of the image data of the scene from the reception of the recording start instruction to the reception of the recording end instruction, the first file, which is the file at the time of receiving the transfer instruction, is completed. Generating a new second file that continues to record the scene;
Transferring the completed file to a transfer destination;
And c. Combining the first file and the second file. A control method of an image recording apparatus which records image data on a recording medium and transfers the image data recorded on the recording medium to an external device,
The file is a file at the time when the transfer interruption instruction is received when the transfer interruption instruction is received after receiving the transfer instruction during recording of the image data of the scene from the reception of the recording start instruction to the reception of the recording end instruction. Creating a new second file for recording the scene while making the one file complete;
And c. Transferring the completed file to a transfer destination. A program for controlling 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 recording of the image data of the scene from the reception of the recording start instruction to the reception of the recording end instruction, the first file, which is the file at the time of receiving the transfer instruction, is completed. Generating a new second file that continues to record the scene;
Processing of transferring a completed file to a transfer destination,
A program for causing a computer to execute a process of combining the first file and the second file. A program for controlling 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,
The file is a file at the time when the transfer interruption instruction is received when the transfer interruption instruction is received after receiving the transfer instruction during recording of the image data of the scene from the reception of the recording start instruction to the reception of the recording end instruction. A process of generating a new second file for recording the scene while making the file of 1 complete;
A program for causing a computer to execute a process of transferring a completed file to a transfer destination.

Images