Image recording apparatus, control method of the same, and recording medium

An image recording apparatus that can communicate with an external apparatus includes a recording unit, a completion unit, a first input unit, and a transmission unit. The recording unit records movie data on at least one recording medium. The completion unit completes a movie file based on recorded movie data. The first input unit receives a predetermined instruction for transmitting at least part of movie data, recorded by the recording unit, to the external apparatus. The transmission unit transmits, via the communication interface, at least one of movie files completed by the completion unit, based on the predetermined instruction. Where the first input unit receives the predetermined instruction while the recording unit is recording the movie data, the completion unit completes a recorded part of the movie data being recorded, as a movie file, and the transmission unit automatically transmits the completed movie file via the communication interface.

BACKGROUND OF THE INVENTION

Field of the Invention

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 apparatus, a control method of the same, and a recording medium.

Description of the Related Art

A digital video camera (hereinafter, simply referred to as a “video camera”) converts an optical image into an electrical signal using an image sensor, and records the electrical signal as digital image data on an internal memory of the camera or a removable recording medium such as a CF card and an SD memory card. The recorded digital image data can be transferred to an external device such as a personal computer (PC) and a mobile terminal (smartphone, tablet terminal, etc.) using various communication units including a universal serial bus (USB) and a wireless local area network (LAN).

In recent years, a function of transferring data via a wireless LAN has been widespread in particular. Such a function realizes data transfer between a video camera that has acquired authentication of the Wireless Fidelity (Wi-Fi), and a PC or a mobile terminal. General data transfer methods include a File Transfer Protocol (FTP), a HyperText Transfer Protocol (HTTP), a Real-time Transport Protocol (RTP), and the like. In transferring digital image data such as movie data obtained through image capturing performed by the video camera, the FTP is often used. The FTP is often used as a file transfer protocol functioning on a higher layer of a Transmission Control Protocol/Internet Protocol (TCP/IP). The video camera operates as an FTP client, and transfers image data to an external device such as a PC and a mobile terminal that has an FTP server function, via an FTP command.

In particular, many of video data handled in Electronic News Gathering (ENG) require immediacy. It is therefore required that digital image data can be promptly transferred via a network.

Japanese Patent Laid-Open No. 2009-225116 discloses a video recording apparatus that transfers, through network transmission, recorded video to an apparatus located at a remote place. The video recording apparatus searches a keyword-weight correspondence dictionary for a keyword that has been input from a keyword input unit during the recording of a movie file, and records a corresponding weight in association with a time on the movie file. When transferring the movie file through a network, the video recording apparatus divides the movie file as a separate movie file for transfer, every certain period of time. The video recording apparatus sequentially transfers the obtained movie files for transfer from movie files having larger total weights associated with the respective times. If the transfer of all the movie files for transfer is ended, a playlist generation unit generates a playlist in which the transferred files are rearranged in the order of record times. The video recording apparatus then transfers the generated playlist.

In addition, Japanese Patent Laid-Open No. 2005-328154 discloses a recording apparatus that records video data obtained by an imaging unit, on a randomly-accessible recording medium. The recording apparatus records video data output from an image sensor, on a first file provided in the recording medium. If a division instruction unit receives, during the image capturing performed by the image sensor, a division instruction input from a user, the recording apparatus records video data that has been output from the image sensor from the time point when the division instruction had been received, on a second file provided in the recording medium.

SUMMARY OF THE INVENTION

According to an aspect of the present invention, an image recording apparatus that can communicate with an external apparatus includes a processor and a communication interface, wherein the processor functions at least as a recording unit, a completion unit, a first input unit, and a transmission unit, wherein the recording unit is configured to record movie data on at least one recording medium, wherein the completion unit is configured to complete a movie file based on movie data recorded by the recording unit, wherein the first input unit is configured to receive a predetermined instruction for transmitting at least part of movie data, recorded by the recording unit, to the external apparatus, wherein the transmission unit is configured to transmit, via the communication interface, at least one of movie files completed by the completion unit, based on the predetermined instruction, and wherein, in a case in which the first input unit receives the predetermined instruction while the recording unit is recording the movie data, the completion unit completes a recorded part of the movie data being recorded, as a movie file, and the transmission unit automatically transmits the completed movie file via the communication interface.

DESCRIPTION OF THE EMBODIMENTS

First Exemplary Embodiment

FIG. 1is a block diagram illustrating a schematic configuration of a video camera100according to a first exemplary embodiment that functions as an image recording apparatus to which the present invention is applied. The video camera100includes a lens101, a complementary metal oxide semiconductor (CMOS)102, a camera signal processing unit103, a recording medium104, a power source105, an operation unit106, an input interface (I/F)107, a read-only memory (ROM)108, a random access memory (RAM)109, a coder decoder (CODEC)110, an output I/F111, a display unit112, a central processing unit (CPU)113, a communication control unit114, a communication module115, and a communication I/F116. The video camera100performs data input and output via a data bus118.

The lens101is an imaging lens including a focus mechanism, a diaphragm mechanism, and the like, and forms an optical image of a subject.

The CMOS102is an image sensor, and includes an analog-to-digital (A/D) converter. After converting an optical image into an analog electrical signal, the CMOS102converts the analog electrical signal into a digital signal. In addition, an image sensor is not limited to the CMOS image sensor, and may be an image sensor such as a charge coupled device (CCD) image sensor.

The camera signal processing unit103performs resizing processing such as predetermined pixel interpolation/reduction, color conversion, various types of correction processing, and the like, on the digital signal converted by the CMOS102.

The recording medium104is a flash memory such as an SD memory card and an internal memory, and records video data and audio data that are obtained through image capturing, and information necessary for the control of the CPU113.

The power source105is an alternating-current (AC) power source or a battery, and supplies necessary power to each unit in the video camera100.

The operation unit106receives an operation from the user. Information of the received operation is input to the data bus118via the input I/F107. For example, via the operation unit106, the user selects encoded video data recorded on the recording medium104, and issues a transfer instruction for transferring the selected video data to an external device (not illustrated), with which the communication control unit114performs communication. If the transfer instruction is issued, numbers of transfer target encoded files and numbers of scenes each collectively including a group of transfer target encoded files are saved into the RAM109via the CPU113according to the format of a transfer list500illustrated inFIG. 5A, which will be described later.

The ROM108stores a program for starting up the video camera100. When an electrical signal is supplied from the power source105via the operation unit106, the program is loaded into the RAM109by the CPU113.

The RAM109functions as a work area of the CPU113. In addition, the work area of the CPU113is not limited to the RAM109, and may be an external recording device (not illustrated) such as a hard disc device.

The CODEC110reproduces video data and audio data that are recoded on the RAM109and the recording medium104. The reproduced video data is displayed on the display unit112. In addition, the reproduced audio data is supplied to a loudspeaker (not illustrated) to be output therefrom. The CODEC110performs compression encoding at a predetermined bit rate and in a predetermined format, or decoding of video compression encoded data. In addition, although audio is not especially illustrated in the drawing, an audio signal can also be handled through similar processing by using the lens101and the CMOS102as a microphone, and using the display unit112as a loudspeaker. When a video is recorded, audio is simultaneously recorded together with the video. By multiplexing the video and the audio in the CODEC110, video data with audio can be generated.

Based on display data such as a graphical user interface (GUI) that is generated by the CPU113according to a program, the output I/F111outputs a display signal for performing display on the display unit112.

The CPU113executes a program loaded from the ROM108into the RAM109. The CPU113manages information about the recording of scenes and files in the recording of videos. The CPU113executes processing such as file operation processing including file break and file close, which will be described later, and acquisition of information thereof, control of a recording operation of the video camera (change of a recording state and a recording preparation state), transfer list management, and the like.

The communication control unit114transmits and receives control data, video data, and audio data with an external device (not illustrated) such as an FTP server via the communication module115and the communication I/F116.

FIGS. 2A and 2Bare diagrams each illustrating a connection example of the video camera100and an external device according to the first exemplary embodiment. The video camera100can be connected to the external device via at least either wired connection or wireless connection, which will be described below.

FIG. 2Ais a schematic diagram illustrating an example in which the video camera100and an external device200aare connected in a wired manner. The external device200ais an external device that performs communication with the video camera100via a cable201. In addition, the external device200amay be a device that directly performs communication with the video camera100, or may be a device connected to the video camera100via a relay device such as a network hub. The present invention can be applied as long as the communication performed therebetween is communication that uses a wired medium such as a wired LAN and a USB.

FIG. 2Bis a schematic diagram illustrating an example in which the video camera100and an external device200bare wirelessly connected. The external device200bis an external device that performs communication with the video camera100via wireless communication202. In addition, the external device200bmay be a device that directly performs wireless communication with the video camera100, or may be a device connected to the video camera100via a wireless relay device such as an access point. The present invention can be applied as long as the connection established therebetween is connection that uses wireless communication such as the Wi-Fi and Bluetooth (registered trademark).

FIG. 3is a schematic diagram illustrating a relationship between a recording operation, scenes, and files in the video camera100according to the first exemplary embodiment. A horizontal axis300represents a time axis and indicates that time elapses toward the right side inFIG. 3.

Mode Start301indicates an input operation performed via the operation unit106for shifting the video camera100to the recording preparation state. When this input operation is executed, the video camera100shifts to the recording preparation state. Rec Pause302indicates the recording preparation state of the video camera100. The recording preparation state is a state in which the video camera100can promptly enter the recording state upon Rec Start303being instructed.

The Rec Start303indicates an input operation of a recording start instruction that is executed via the operation unit106for shifting the video camera100to the recording state. When this input operation is executed in the recording preparation state, the video camera100shifts to the recording state. Rec304indicates the recording state of the video camera100. In the recording state, the CODEC110encodes signals input via the lens101and the CMOS102, in a file format for recording the signals on the recording medium104, and the encoded signals are sequentially stored into the RAM109. If the sizes of files stored in the RAM109reach an arbitrary capacity, the files are recorded on the recording medium104. The processing is sequentially executed until Rec Stop308is issued.

The Rec Stop308indicates an input operation of a recording end instruction that is executed via the operation unit106for stopping the recording state and shifting the video camera100to the recording preparation state.

Mode Stop311indicates an input operation performed via the operation unit106for shifting the recording operation of the video camera100to an end state.

Rec Delay305indicates a time lag between a time point when the video camera100enters the recording state upon the Rec Start303being instructed, and a time point when video data actually starts to be recorded onto the recording medium104. This time lag varies depending on a bit rate of a video to be recorded, and the arbitrary capacity set for storing on the RAM109. In addition, a similar time lag is generated between a time point when the Rec Stop308is instructed and a time point when the recording is actually ended.

A scene306is a recording unit used when the video camera100records a video. The recording unit is a unit of video data recorded between the Rec Start303and the Rec Stop308. It should be noted that the scene306is not synonymous with a file307to be described later. In view of a file format of the recording medium104, if the size of data to be recorded on the recording medium104becomes a data size equal to or larger than a file upper limit capacity of the file format, the file needs to be divided. Such a dividing operation is referred to as file break310. The scene306is defined as one scene including the files307obtained through the file break. A number is allocated to the scene306every time the Rec Start303is instructed, so that the scenes306are operated as scene #1, scene #2, and so on.

The file307is a video data file recorded on the recording medium104. If the size of data accumulated in the RAM109in response to the Rec Start303reaches the arbitrary capacity, the data starts to be stored into the recording medium104as the file307. In the recording state, since video data are sequentially written into the RAM109, data stored as the files307also sequentially increase. Until file close309or the file break310occurs, the files307are in an uncompleted state and in a state of being unable to be read out for other types of processing. If the file close309or the file break310occurs, the files307enter a completed state. A number is allocated to the file307every time the file307is completed, so that the files307are operated as file #1, file #2, and so on.

The file close309is a file operation for bringing the files307sequentially recorded on the recording medium104by the recording operation of the video camera100, into the completed state in response to the Rec Stop308being instructed. If this operation is executed, the files307become readable and editable for other types of processing.

The file break310is a file operation performed for recording a file in a divided manner when a file having a size equal to or larger than a specific size is stored into the recording medium104, in view of the file format of the recording medium104. This file operation is automatically performed within the video camera100by the CPU113identifying the file format of the recording medium104. Thus, if the user inputs the Rec Start303via the operation unit106only once, when a record time continues for a certain time or more and the file307is written up to the upper limit of the file format of the recording medium104, the file307enters the completed state by the file break310, and the generation of a new file307is started.

FIGS. 4A and 4Bare diagrams each illustrating an example of a relationship between a recording operation, scenes, files, and a transfer instruction in the video camera100according to the first exemplary embodiment.

FIG. 4A(a) illustrates a state in which a transfer instruction has been issued so as to transfer a scene being recorded, to an external device, in the recording state (the Rec304) of the video camera100.

A scene ∩1(306(1)) is assumed to be initially recorded onto the recording medium104, and has an allocated number “#1”.

Similarly to the scene #1(306(1)), a file #1(307(1)) is assumed to be initially recorded onto the recording medium104, and has an allocated number “#1”.

Transfer Req401indicates an input operation performed via the operation unit106for instructing the transfer of the scene #1(306(1)) being recorded, to the external device.

If the Rec Stop308is instructed, the file ∩1(307(1)) being recorded and being in the uncompleted state is completed by the file close309as a file.

FIG. 4A(b) illustrates a state in which a transfer instruction has been issued so as to transfer a recorded scene to the external device, in the recording preparation state (the Rec Pause302) caused after the recording state of the video camera100. InFIG. 4A(b), it is assumed that the file break310has not occurred.

A scene ∩2(306(2)) is assumed to be a scene started to be recorded upon the second Rec Start303being instructed, and has an allocated number “#2”.

Similarly to the scene #2(306(2)), a file #2(307(2)) is assumed to be a file to be secondly recorded onto the recording medium104, and has an allocated number “#2”.

If the Rec Stop308is instructed, the file #2(307(2)) being recorded and being in the uncompleted state is completed by the file close309as a file.

The Transfer Req401indicates an input operation performed via the operation unit106for instructing the transfer of the scene #2(306(2)) of which the recording has been ended, to the external device.

FIG. 4A(c) illustrates a state in which a transfer instruction has been issued so as to transfer a scene being recorded, to the external device, in the recording state (the Rec304) of the video camera100, and before the file break310occurs.

A scene #3(306(3)) is assumed to be a scene started to be recorded upon the third Rec Start303being instructed, and has an allocated number “#3”. In the scene #3(306(3)), the file break310occurs for a file #3(307(3)), and after the file #3(307(3)) has been completed, a new file #4(307(4)) is generated.

The file #3(307(3)) is assumed to be a file to be thirdly recorded onto the recording medium104, and has an allocated number “#3”. The file #4(307(4)) is a file generated for continuously recording the scene #3after the file break310has occurred for the file #3(307(3)).

The Transfer Req401indicates an input operation performed via the operation unit106for instructing the transfer of the scene #3(306(3)) being recorded, to the external device.

FIG. 4B(a) illustrates a state in which a transfer instruction has been issued so as to transfer a scene being recorded, to the external device, in the recording state (the Rec304) of the video camera100, and after the file break310has occurred.

A scene #4(306(4)) is assumed to be a scene started to be recorded upon the fourth Rec Start303being instructed, and has an allocated number “#4”. In the scene #4(306(4)), the file break310occurs for a file #5(307(5)), and after the file #5(307(5)) has been completed, a new file #6(307(6)) is generated.

The file #5(307(5)) is assumed to be a file to be recorded fifth onto the recording medium104, and has an allocated number “#5”. The file #6(307(6)) is a file generated for continuously recording the scene #4after the file break310has occurred for the file #5(307(5)).

The Transfer Req401indicates an input operation performed via the operation unit106for instructing the transfer of the scene #4(306(4)) being recorded, to the external device.

FIG. 4B(b) illustrates a state in which a transfer instruction has been issued so as to transfer a recorded scene to the external device, in the recording preparation state (the Rec Pause302) caused after the recording state of the video camera100. InFIG. 4B(b), it is assumed that the file break310has occurred.

A scene #5(306(5)) is assumed to be a scene started to be recorded upon the fifth Rec Start303being instructed, and has an allocated number “#5”. In the scene (306(5)), the file break310occurs for a file #7(307(7)), and after the file #7(307(7)) has been completed, a new file #8(307(8)) is generated.

The file #7(307(7)) is assumed to be a file to be recorded seventh onto the recording medium104, and has an allocated number “#7”. The file #8(307(8)) is a file generated for continuously recording the scene #5after the file break310has occurred for the file #7(307(7)).

If the Rec Stop308is instructed, the file #8(307(8)) being recorded and being in the uncompleted state is completed by the file close309as a file.

The Transfer Req401indicates an input operation performed via the operation unit106for instructing the transfer of the scene #5(306(5)) of which the recording has been ended, to the external device.

FIGS. 5A to 5Hare diagrams for illustrating transfer lists according to the first exemplary embodiment and a registration method thereof.

The configuration of the transfer list500will be described with reference toFIG. 5A. The transfer list500has a configuration in which scene information and file information are registered.

Lists510,520,530, and so on are scene information registration tables, in which scene numbers instructed to be transferred are registered. The number of these tables is determined according to the number of registered scenes instructed to be transferred. In this example, 5 scene number registration tables [0] to [4] exist. In other words, the number of scenes that can be instructed to be transferred is 5. Nevertheless, if the transfer of a registered scene is completed, the table enters an unoccupied state, and it becomes possible to issue a transfer instruction again. Lists511,512, and so on are file information registration tables, in which file numbers constituting a scene registered in the list510are registered. Similarly, lists521,522, and so on are file information registration tables, in which file numbers constituting a scene registered in the list520are registered. The same applies to subsequent lists530and so on. The number of tables is determined in accordance with the maximum number of files constituting 1 scene. In this example, the number of file information registration tables is 3, and 3 files can be registered for 1 scene.

In addition, an operation can be performed using the number of scene information registration tables and the number of file information registration tables that are suitable for a system.

FIGS. 6A and 6Bare flowcharts illustrating transfer list registration processing of the video camera100according to the first exemplary embodiment.

The video camera100checks a recording operation performed when the Transfer Req401serving as a transfer instruction is input as illustrated inFIGS. 4A and 4B, and the presence or absence of the file break310, and registers the transfer list500.

An operation performed by the video camera100when the Transfer Req401is input will be described below with reference toFIGS. 4A, 4B, and 5A to 5H. In addition, asynchronously with the processing inFIGS. 6A and 6B, the user can arbitrarily shift the video camera100to the recording preparation state or the recording state via the operation unit106. InFIGS. 4A and 4B, the transition to the recording preparation state corresponds to the Mode Start301in each drawing, the transition to the recording state corresponds to the Rec Start303, and the transition to the recording preparation state corresponds to the Rec Stop308.

In step S601, the CPU113checks whether the video camera100is in the recording state or the recording preparation state. The processing is not executed in states other than the recording state and the recording preparation state (NO in step S601), and step S601is repeated. If the video camera100is in the recording state or the recording preparation state (YES in step S601), the processing proceeds to step S602.

In step S602, the CPU113checks whether the Transfer Req401has been input. If the Transfer Req401has not been input (NO in step S602), step S602is continued. If the Transfer Req401has been input (YES in step S602), the processing proceeds to step S603.

In step S603, the CPU113checks whether the video camera100is in the recording state. If the video camera100is in the recording state (YES in step S603), the processing proceeds to step S604. If the video camera100is not in the recording state (NO in step S603), the processing proceeds to step S650.

Steps S604to S613correspond to processing performed when the Transfer Req401has been input in the recording state as illustrated inFIGS. 4A(a),4A (c) and4B (a).

In step S604, the CPU113registers a scene to be transferred, in the transfer list500. The processing in step S604will be described with reference toFIGS. 4A(a) and5B. At the time point when the Transfer Req401is input inFIG. 4A(a), the first scene recording is being performed, and lists510to550are all in an unregistered state. The CPU113that has detected the input of the Transfer Req401in step S602acquires a scene number instructed via the Transfer Req401to be transferred, and registers the acquired scene number in the list510. In this example, the scene corresponds to the scene #1(306(1)), and the scene #1is registered in the list510as illustrated inFIG. 5B. InFIGS. 4A(c) and4B (a), the scene information registration processing of the transfer list500is similarly performed through this step. As a result, the scene #3(306(3)) is registered in the list530as illustrated inFIG. 5D, and the scene #4(306(4)) is registered in the list540as illustrated inFIG. 5F.

In step S605, the CPU113checks whether there is a file registerable in the transfer list500. The CPU113manages information of a scene currently being recorded. The scene information includes information of files constituting the scene. Based on the scene information, it can be determined whether the scene is constituted by a plurality of files using the file break310. InFIG. 4A(a), at the time point when the Transfer Req401is input, the file #1(307(1)) is in the uncompleted state and cannot be registered in the transfer list500. The same applies to the file #3(307(3)) inFIG. 4A(c). In this case (NO in step S605), the processing proceeds to step S608. On the other hand, inFIG. 4B(a), at the time point when the Transfer Req401is input, the file #6(307(6)) is in the uncompleted state, whereas the file #5(307(5)) has been brought into the completed state by the file break310and can be registered in the transfer list500. In this case (YES in step S605), the processing proceeds to step S606, and the registration processing of the transfer list500is executed.

In step S606, the CPU113registers a file to be transferred, in the transfer list500. The processing in step S606will be described with reference toFIGS. 4B(a) and5F. InFIG. 4B(a), the scenes #1to #3are in a registered state in the respective lists510,520, and530as illustrated inFIG. 5F. As illustrated inFIG. 5F, the CPU113registers the file #5(307(5)) in a list541of scene #4, which had been in the unregistered state before the execution of step S606. When step S606is ended, the processing proceeds to step S607.

In step S607, the CPU113checks whether all registrable files have been registered in the transfer list500. InFIG. 4B(a), only the file #5(307(5)) is in the completed state at the time point when the Transfer Req401is input. Nevertheless, a case in which a plurality of files is generated using the file break310is assumed. In this case, in step S607, it is checked whether all the files have been registered in the transfer list500. If there is a file to be registered (NO in step S607), the processing returns to step S606. If the registration of all the files has been ended (YES in step S607), the processing proceeds to step S608.

In step S608, the CPU113notifies, using the display unit112, the user that the registration in the transfer list500has been performed in response to the Transfer Req401. If the display is ended, the processing proceeds to step S609.

In step S609, the CPU113checks whether the file break310has occurred for the files included in the scene being recorded. InFIGS. 4A(c) and4B (a), at the time point when the Transfer Req401is input, the file #3(307(3)) and the file #6(307(6)) are in the uncompleted state, but the file break310may occur thereafter, and the files may enter the completed state. If the file break310has been detected (YES in step S609), the processing proceeds to step S610. If the file break310has not been detected (NO in step S609), the processing proceeds to step S611.

In step S610, the CPU113updates the transfer list500. InFIG. 4A(c), the CPU113that has detected the file break310registers the file #3(307(3)) in the transfer list500. More specifically, if the file #3(307(3)) is brought into the completed state by the file break310inFIG. 4A(c), as illustrated inFIG. 5D, the file #3is registered in a list531. Then, if the file break310further occurs, as illustrated inFIG. 5E, the file #4(307(4)) is registered in a list532. Similarly, if the file #6(307(6)) is brought into the completed state by the file break310inFIG. 4B(a), as illustrated inFIG. 5G, the file #6is registered in a list542.

In step S611, the CPU113checks whether the file close309has occurred for the scene being recorded. The CPU113performs file close if the Rec Stop308is input via the operation unit106. InFIG. 4A(a), at the time point when the Transfer Req401is input, the file #1(307(1)) is in the uncompleted state, so CPU113waits for the occurrence of the file close309. If the file close309has been detected (YES in step S611), the processing proceeds to step S612. If the file close309has not been detected (NO in step S611), the processing returns to step S609, in which the occurrence of the file break310is detected again.

In step S612, the CPU113registers a file that has been brought into the completed state by the file close309, in the transfer list500. InFIG. 4A(a), the file #1(307(1)) is brought into the completed state by the file close309, and becomes registerable in the transfer list500. As illustrated inFIG. 5B, the file #1(307(1)) is registered in the list511, and the processing proceeds to step S613.

In step S613, the CPU113performs file close registration for writing data indicating scene completion, in the transfer list500. After detecting the file close309and registering the file in the transfer list500, the CPU113registers the completion of the scene in the transfer list500. InFIG. 5B, the CPU113registers the file close in the list512. If step S613is ended, the transfer list registration processing is completed.

In step S650, the CPU113checks whether the video camera100is in the recording preparation state. If the video camera100is in the recording preparation state (YES in step S650), the processing proceeds to step S651. If the video camera100is not in the recording preparation state (NO in step S650), the processing proceeds to step S657.

Steps S651to S656correspond to processing performed when the Transfer Req401has been input in the recording preparation state as illustrated inFIGS. 4A(b) and4B (b).

In step S651, the CPU113checks whether there is a scene registerable in the transfer list500. The CPU113determines the presence or absence of a last-recorded scene. The CPU113can determine the presence or absence of the recording for controlling the recording performed on the recording medium104. If there is a scene that can be added to the transfer list500(YES in step S651), the processing proceeds to step S652. If there is no scene that can be added to the transfer list500(NO in step S651), the processing proceeds to step S657.

In step S652, the CPU113registers a scene to be transferred, in the transfer list500. The processing in step S652will be described with reference toFIGS. 4A(b) and5C. InFIG. 4A(b), the scene #1is in the registered state in the list510as illustrated inFIG. 5C. The CPU113that has detected the input of the Transfer Req401in step S602acquires a scene number instructed via the Transfer Req401to be transferred, and registers the acquired scene number in the list520. In this example, the scene corresponds to the scene #2(306(2)), and the scene #2is registered in the list520as illustrated inFIG. 5C. InFIG. 4B(b), the scene information registration processing of the transfer list500is similarly performed through this step. As a result, the scene #5(306(5)) is registered in the list550as illustrated inFIG. 5H.

In step S653, similarly to step S606, the CPU113registers a file to be transferred, in the transfer list500. The processing in step S653will be described with reference toFIGS. 4A(b) and5C. As illustrated inFIG. 5C, the CPU113registers the file #2(307(2)) in the list521of the scene #2, which had been in the unregistered state before the execution of step S653. InFIG. 4B(b), the file information registration processing of the transfer list500is similarly performed through this step. As illustrated inFIG. 5H, the CPU113registers the file #7(307(7)) and the file #8(307(8)) in respective lists551and552of the scene #5, which had been in the unregistered state before the execution of step S653. If step S653is ended, the processing proceeds to step S654.

In step S654, the CPU113checks whether all registrable files have been registered in the transfer list500. If all the registrable files have been registered (YES in step S654), the processing proceeds to step S655. If there is an unregistered file (NO in step S654), the processing returns to step S653. InFIG. 4B(b), the file #7(307(7)) is registered in step S653performed first. Then, if it is detected in step S654that the file #8(307(8)) has not been registered, the file #8(307(8)) is registered in step S653performed again, and the processing proceeds to step S655.

In step S655, the CPU113performs file close registration for writing data indicating scene completion, in the transfer list500. In step S655, the video camera100is in the recording preparation state, and there are only scenes on which the file close has already been performed. Thus, there is no need to perform processing of monitoring the file close. InFIG. 4A(b), the CPU113registers the file close in the list522as illustrated inFIG. 5C. In addition, inFIG. 4B(b), the CPU113registers the file close in a list553as illustrated inFIG. 5H. After this step is ended, the processing proceeds to step S656.

In step S656, the CPU113notifies, using the display unit112, the user that the registration in the transfer list500has been performed in response to the Transfer Req401. If step S656is ended, the transfer list registration processing is completed.

In step S657, the CPU113notifies the user that the transfer list registration processing has failed. Although a transfer instruction has been issued via the operation unit106, there is no scene to be registered in the transfer list500, and the transfer processing is not executed. Thus, the CPU113notifies the user of this using the display unit112. If step S657is ended, the transfer list registration processing is completed.

The video camera100transfers a scene to the external device according to the transfer list500registered through the transfer list registration processing illustrated inFIGS. 6A and 6B.FIG. 7is a flowchart illustrating transfer control processing of the video camera100according to the first exemplary embodiment.

In step S701, the CPU113initializes a scene pointer indicating a scene to be registered in the transfer list500, and the processing proceeds to step S702.

In step S702, the CPU113initializes a file pointer indicating a file to be registered in the transfer list500, and the processing proceeds to step S703.

In step S703, the CPU113checks the presence or absence of a file registered in the transfer list500. If there is a file registered in the transfer list500(YES in step S703), the processing proceeds to step S704. If there is no file registered in the transfer list500(NO in step S703), the CPU113continues to check until a registered file is found.

In step S704, the CPU113checks whether there is a file that is registered in the transfer list500and transferable to the external device. If there is a transferable file (YES in step S704), the processing proceeds to step S705. If there is no transferable file (NO in step S704), the CPU113continues to check until a transferable file is found.

In step S705, the CPU113starts transferring the file that is registered in the transfer list500and transferable to the external device, and the processing proceeds to step S706.

In step S706, the CPU113checks whether a transfer error has occurred. If a transfer error has occurred (YES in step S706), the processing proceeds to step S707. If no transfer error has occurred (NO in step S706), the processing proceeds to step S708.

In step S707, the CPU113checks whether the file with the transfer error can be retransmitted. If the file can be retransmitted (YES in step S707), the processing returns to step S705, in which the CPU113starts transferring the file to the external device again. If the file cannot be retransmitted (NO in step S707), the processing is completed.

In step S708, the CPU113checks whether the transfer of the file started to be transferred in step S705has been completed. If the transfer has been completed (YES in step S708), the processing proceeds to step S709. If the transfer has not been completed (NO in step S708), the processing returns to step S706, in which the CPU113monitors a transfer error that occurs during the transfer.

In step S709, the CPU113updates the file pointer in the transfer list500because there is the file of which the transfer has been completed in step S708, and the processing proceeds to step S710.

In step S710, the CPU113checks whether all files related to the scene being referred to on the transfer list500have been transferred, and the file pointer on the transfer list500is referring to “File Close”. If the file pointer is referring to “File Close” (YES in step S710), the processing proceeds to step S711. If the file pointer is not referring to “File Close” (NO in step S710), the processing returns to step S704.

In step S711, the CPU113updates the scene pointer on the transfer list500, and the processing returns to step S703.

Second Exemplary Embodiment

Next, a second exemplary embodiment will be described. In addition, the configuration and basic operations of a video camera100are the same as those described in the first exemplary embodiment. The following description will be given mainly of a difference from the first exemplary embodiment.

FIGS. 8A to 8Care diagrams illustrating an example of a relationship between a recording operation, scenes, files, and a transfer instruction in the video camera100according to the second exemplary embodiment.

FIG. 8Aillustrates a state in which a transfer instruction has been issued so as to transfer a scene being recorded, to an external device, in the recording state (the Rec304) of the video camera100.

A scene #1(306(1)) is assumed to be initially recorded onto the recording medium104, and has an allocated number “#1”.

Similarly to the scene #1(306(1)), a file #1(307(1)) is assumed to be initially recorded onto the recording medium104, and has an allocated number “#1”.

Transfer Req401indicates an input operation performed via the operation unit106for instructing the transfer of the scene #1(306(1)) being recorded, to the external device.

In this case, for promptly transferring the file #1(307(1)) being recorded on the recording medium104, the file break310is triggered by the Transfer Req401. In response to this, the file #1(307(1)) at the time point when the transfer instruction has been received is brought into the completed state, and a new file #2(307(2)) for continuously recording the scene #1is generated.

If the Rec Stop308is instructed, the file #2(307(2)) being recorded and being in the uncompleted state is completed by the file close309as a file.

FIG. 8Billustrates a state in which a transfer instruction has been issued so as to transfer a scene being recorded, to the external device, in the recording state (the Rec304) of the video camera100.

A scene #2(306(2)) is assumed to be a scene started to be recorded upon the second Rec Start303being instructed, and has an allocated number “#2”.

A file #3(307(3)) is assumed to be a file to be thirdly recorded onto the recording medium104, and has an allocated number “#3”.

The Transfer Req401indicates an input operation performed via the operation unit106for instructing the transfer of the scene #2(306(2)) being recorded, to the external device.

In this case, for promptly transferring the file #3(307(3)) being recorded on the recording medium104, the file break310is triggered by the Transfer Req401. In response to this, the file #3(307(3)) at the time point when the transfer instruction has been received is brought into the completed state, and a new file #4(307(4)) for continuously recording the scene #2is generated.

Then, if the total file size of the file #3(307(3)) and the file #4(307(4)) reaches the file upper limit capacity of the file format, the file break310occurs for the file #4(307(4)). In response to this, the file #4(307(4)) is brought into the completed state, and a new file #5(307(5)) for continuously recording the scene #2is generated. As for files following the file #5(307(5)), if the file size of a corresponding file reaches the file upper limit capacity of the file format, the file break310occurs. InFIG. 8B, the file break310occurs for the file #5(307(5)). The file #5(307(5)) is accordingly brought into the completed state, and a new file #6(307(6)) for continuously recording the scene #2is generated.

If the Rec Stop308is instructed, the file #6(307(6)) being recorded and being in the uncompleted state is completed by the file close309as a file.

FIG. 8Cillustrates a state in which a transfer instruction has been issued so as to transfer a scene being recorded, to the external device, in the recording state (the Rec304) of the video camera100.

A scene #3(306(3)) is assumed to be a scene started to be recorded upon the third Rec Start303being instructed, and has an allocated number “#3”.

A file #7(307(7)) is assumed to be a file to be recorded seventh onto the recording medium104, and has an allocated number “#7”.

The Transfer Req401indicates an input operation performed via the operation unit106for instructing the transfer of the scene #3(306(3)) being recorded, to the external device.

In this case, for promptly transferring the file #7(307(7)) being recorded on the recording medium104, the file break310is triggered by the Transfer Req401. In response to this, the file #7(307(7)) at the time point when the transfer instruction has been received is brought into the completed state, and a new file #8(307(8)) for continuously recording the scene #3is generated.

Then, if the total file size of the file #7(307(7)) and the file #8(307(8)) reaches the file upper limit capacity of the file format, the file break310occurs for the file #8(307(8)). In response to this, the file #8(307(8)) is brought into the completed state, and a new file #9(307(9)) for continuously recording the scene #3is generated. As for files following the file #9(307(9)), if the file size of a corresponding file reaches the file upper limit capacity of the file format, the file break310occurs. InFIG. 8C, the file break310occurs for the file #9(307(9)). The file #9(307(9)) is accordingly brought into the completed state, and a new file #10(307(10)) for continuously recording the scene #3is generated.

If the Rec Stop308is instructed, the file #10(307(10)) being recorded and being in the uncompleted state is completed by the file close309as a file.

At this time, the execution of file mergence801is triggered by the Rec Stop308. In the file mergence801, files obtained by the division performed using the file break310triggered by the Transfer Req401, i.e., the file #7(307(7)) and the file #8(307(8)) in this example are merged, and a file #11(307(11)) is generated. This can avoid an unnecessary increase in the number of files. In addition, in this example, the merged file is renamed as the file #11so as to be a sequential number following the last-recorded file. Nevertheless, the name of the merged file is not limited thereto. For avoiding discontinuity in file numbers, the merged file may be renamed as the file #7, and the file #9(307(9)) and the file #10(307(10)) may be respectively renamed as the file #8and the file #9.

FIGS. 9A and 9Bare flowcharts illustrating file generation control processing and transfer list registration processing of the video camera100according to the second exemplary embodiment.

If the Transfer Req401serving as a transfer instruction is input as illustrated inFIGS. 8A to 8C, the video camera100causes the file break310and registers the transfer list500. According to the transfer list500, the video camera100transfers a scene to the external device. In step S901, the CPU113checks whether the video camera100is in the recording state. The processing is not executed in states other than the recording state (NO in step S901), and step S901is repeated. If the video camera100is in the recording state (YES in step S901), the processing proceeds to step S902.

In step S902, the CPU113checks whether the Transfer Req401has been input. If the Transfer Req401has not been input (NO in step S902), the processing proceeds to step S910. If the Transfer Req401has been input (YES in step S902), the processing proceeds to step S903.

In step S903, the CPU113causes the file break310. In response to this, inFIG. 8A, the file #1(307(1)) at the time point when the transfer instruction has been received is brought into the completed state, and the new file #2(307(2)) for continuously recording the scene #1is generated. In addition, inFIG. 8B, the file #3(307(3)) at the time point when the transfer instruction has been received is brought into the completed state, and the new file #4(307(4)) for continuously recording the scene #2is generated. In addition, inFIG. 8C, the file #7(307(7)) at the time point when the transfer instruction has been received is brought into the completed state, and the new file #8(307(8)) for continuously recording the scene #3is generated.

In step S904, the CPU113checks whether a scene being recorded is registered in the transfer list500. If there is registration in the transfer list500(YES in step S904), the processing proceeds to step S906. If there is no registration in the transfer list500(NO in step S904), the processing proceeds to step S905.

In step S905, the CPU113registers a scene to be transferred, in the transfer list500. The CPU113that has detected the input of the Transfer Req401in step S902acquires a scene number instructed via the Transfer Req401to be transferred, and registers the acquired scene number in the transfer list500.

In step S906, the CPU113checks whether there is a file registerable in the transfer list500. The CPU113manages information of a scene currently being recorded. The scene information includes information of files constituting the scene. Based on the scene information, it can be determined whether the scene is constituted by a plurality of files using the file break310. InFIG. 8A, since the file break310is caused at the time point when the Transfer Req401is input, the file #1(307(1)) enters the completed state and can be registered in the transfer list500. The same applies to the file #3(307(3)) inFIG. 8B, and the file #7(307(7)) inFIG. 8C. In this case (YES in step S906), the processing proceeds to step S907, and the registration processing of the transfer list500is executed. On the other hand, if there is no file registerable in the transfer list500(NO in step S906), the processing proceeds to step S909.

In step S907, the CPU113registers a file to be transferred, in the transfer list500. InFIG. 8A, the CPU113registers the file #1(307(1)) in the completed state, in the transfer list500. In addition, inFIG. 8B, the CPU113registers the file #3(307(3)) in the completed state, in the transfer list500. In addition, inFIG. 8C, the CPU113registers the file #7(307(7)) in the completed state, in the transfer list500.

In step S908, the CPU113checks whether all registerable files have been registered in the transfer list500. InFIGS. 8A to 8C, no other file to be registered in the transfer list500exists. If there is a file to be registered (NO in step S908), the processing returns to step S907. If the registration of all the files has been ended (YES in step S908), the processing proceeds to step S909.

In step S909, the CPU113notifies, using the display unit112, the user that the registration in the transfer list500has been performed in response to the Transfer Req401. If the display is ended, the processing proceeds to step S910.

In step S910, the CPU113checks whether the file break310has occurred for the files included in the scene being recorded. If the file size of a file to be recorded on the recording medium104reaches a file upper limit capacity of the file format, the file is divided according to the control of the CPU113. InFIG. 8B, if the total file size of the file #3(307(3)) and the file #4(307(4)) reaches the file upper limit capacity of the file format, the file break310occurs for the file #4(307(4)). As for subsequent files, if the file size of a corresponding file reaches the file upper limit capacity of the file format, the file break310occurs. In addition, inFIG. 8C, if the total file size of the file #7(307(7)) and the file #8(307(8)) reaches the file upper limit capacity of the file format, the file break310occurs for the file #8(307(8)). As for subsequent files, if the file size of a corresponding file reaches the file upper limit capacity of the file format, the file break310occurs. If the file break310has been detected (YES in step S910), the processing proceeds to step S911. If the file break310has not been detected (NO in step S910), the processing proceeds to step S913.

In step S911, the CPU113checks whether the Transfer Req401has been input. If the Transfer Req401has not been input (NO in step S911), the processing proceeds to step S913. If the Transfer Req401has been input (YES in step S911), the processing proceeds to step S912.

In step S912, the CPU113updates the transfer list500. InFIG. 8B, the CPU113registers the file #4(307(4)) and the file #5(307(5)) in the transfer list500. In addition, inFIG. 8C, the CPU113registers the file #9(307(9)) in the transfer list500.

In step S913, the CPU113checks whether the file close309has occurred for the scene being recorded. The CPU113performs file close if the Rec Stop308is input via the operation unit106. InFIG. 8A, the file #2(307(2)) is brought into the completed state by the file close309, and becomes registerable in the transfer list500. In addition, inFIG. 8B, the file #6(307(6)) is brought into the completed state by the file close309, and becomes registerable in the transfer list500. In addition, inFIG. 8C, the file #10(307(10)) is brought into the completed state by the file close309, and becomes registerable in the transfer list500. If the file close309has been detected (YES in step S913), the processing proceeds to step S914. If the file close309has not been detected (NO in step S913), the processing returns to step S902.

In step S914, the CPU113checks whether the Transfer Req401has been input. If the Transfer Req401has not been input (NO in step S914), the processing is ended. If the Transfer Req401has been input (YES in step S914), the processing proceeds to step S915.

In step S915, the CPU113updates the transfer list500. InFIG. 8A, the CPU113registers the file #2(307(2)) that has been brought into the completed state by the file close309, in the transfer list500. In addition, inFIG. 8B, the CPU113registers the file #6(307(6)) that has been brought into the completed state by the file close309, in the transfer list500. In addition, inFIG. 8C, the CPU113registers the file #10(307(10)) that has been brought into the completed state by the file close309, in the transfer list500.

In step S916, the CPU113merges files obtained by the file break caused according to the Transfer Req401. InFIG. 8C, the CPU113generates a file by merging the file #7(307(7)) and the file #8(307(8)). For example, the merged file is renamed as the file #11(307(11)) so as to be a sequential number following the last-recorded file.

In step S917, the CPU113updates the transfer list500. InFIG. 8C, the CPU113registers the file #11(307(11)) obtained by the mergence in step S916, in the transfer list500.

In step S918, the CPU113performs file close registration for writing data indicating scene completion, in the transfer list500. After detecting the file close309and registering the file in the transfer list500, the CPU113registers the completion of the scene in the transfer list500.

In step S919, the CPU113stores the numbers of the merged files into the RAM109. InFIG. 8C, the numbers #7and #8of the file #7and the File #8are stored. In addition, an example of the numbers of files has been described here. Nevertheless, other items may be stored instead of the numbers as long as the files can be identified.

In step S920, the CPU113checks whether all the files registered in the transfer list500have been transferred. The transfer processing performed according to the transfer list500is as described in the first exemplary embodiment, and is performed asynchronously with the processing in this flowchart. If all the files registered in the transfer list500have been transferred (YES in step S920), the processing proceeds to step S921.

In step S921, the CPU113deletes the files corresponding to the file numbers stored in step S919, from a transfer destination FTP server.

In the present exemplary embodiment, the processing in steps S916to S921is performed for ensuring the consistency between the structure of files recorded on the recording medium104of the video camera100and the structure of files in the transfer destination FTP server. Nevertheless, the CPU113does not necessarily have to perform the deletion processing step S921. For example, if the CPU113does not perform the deletion processing in step S921, the CPU113may perform processing of transmitting information about the mergence to the FTP server as meta-information.

Third Exemplary Embodiment

Next, a third exemplary embodiment will be described. In addition, the configuration and basic operations of a video camera100are the same as those described in the first and second exemplary embodiments. The following description will be given mainly of a difference from the first and second exemplary embodiments.

FIG. 10is a diagram illustrating an example of a relationship between a recording operation, scenes, files, and a transfer instruction in the video camera100according to the third exemplary embodiment.

FIG. 10illustrates a state in which a transfer instruction has been issued so as to transfer a scene being recorded, to an external device, in the recording state (the Rec304) of the video camera100.

A scene #1(306(1)) is assumed to be initially recorded onto the recording medium104, and has an allocated number “#1”.

Similarly to the scene #1(306(1)), a file #1(307(1)) is assumed to be initially recorded onto the recording medium104, and has an allocated number “#1”.

Transfer Req401indicates an input operation performed via the operation unit106for instructing the transfer of the scene #1(306(1)) being recorded, to the external device.

Cancel Transfer Req1001indicates an input operation performed via the operation unit106for instructing the transfer stop of the scene #1(306(1)) being recorded and instructed via the Transfer Req401to be transferred.

In this case, for setting up to the file #1(307(1)) being recorded on the recording medium104, as a transfer target, and stopping the transfer of subsequent files, the file break310is triggered by the Cancel Transfer Req1001. In response to this, the file #1(307(1)) at the time point when a transfer stop instruction has been received is brought into the completed state, and a new file #2(307(2)) for continuously recording the scene #1is generated. Since the transfer stop instruction has been issued for the file #2(307(2)), even if the file close309occurs for the file #2(307(2)) thereafter, the file #2(307(2)) is not registered in the transfer list500.

If the Rec Stop308is instructed, the file #2(307(2)) being recorded and being in the uncompleted state is completed by the file close309as a file.

In addition, the file break310that occurs for files following the file #2(307(2)), and file mergence performed after the Rec Stop308are similar to the processing in the second exemplary embodiment. Thus, the description thereof will be omitted.

FIGS. 11A and 11Bare flowcharts illustrating file generation control processing and transfer list registration processing of the video camera100according to the third exemplary embodiment.

If the Cancel Transfer Req1001serving as a transfer stop instruction is input as illustrated inFIG. 10, the video camera100causes the file break310and registers the transfer list500. According to the transfer list500, the video camera100transfers a scene to the external device.

In step S1101, the CPU113checks whether the video camera100is in the recording state. The processing is not executed in states other than the recording state (NO in step S1101), and step S1101is repeated. If the video camera100is in the recording state (YES in step S1101), the processing proceeds to step S1102.

In step S1102, the CPU113checks whether the Transfer Req401has been input. If the Transfer Req401has not been input (NO in step S1102), the processing proceeds to step S1109. If the Transfer Req401has been input (YES in step S1102), the processing proceeds to step S1103.

In step S1103, the CPU113checks whether a scene being recorded is registered in the transfer list500. If there is registration in the transfer list500(YES in step S1103), the processing proceeds to step S1105. If there is no registration in the transfer list500(NO in step S1103), the processing proceeds to step S1104.

In step S1104, the CPU113registers a scene to be transferred, in the transfer list500. The CPU113that has detected the input of the Transfer Req401in step S1102acquires a scene number instructed via the Transfer Req401to be transferred, and registers the acquired scene number in the transfer list500.

In step S1105, the CPU113checks whether there is a file registerable in the transfer list500. The CPU113manages information of a scene currently being recorded. The scene information includes information of files constituting the scene. Based on the scene information, it can be determined whether the scene is constituted by a plurality of files using the file break310. InFIG. 10, at the time point when the Transfer Req401is input, the file #1(307(1)) is in the uncompleted state and cannot be registered in the transfer list500. In this case (NO in step S1105), the processing proceeds to step S1108, and the registration processing of the transfer list500is executed. On the other hand, if there is a file registerable in the transfer list500(YES in step S1105), the processing proceeds to step S1106.

In step S1106, the CPU113registers a file to be transferred, in the transfer list500.

In step S1107, the CPU113checks whether all registerable files have been registered in the transfer list500. If there is a file to be registered (NO in step S1107), the processing returns to step S1106. If the registration of all the files has been ended (YES in step S1107), the processing proceeds to step S1108.

In step S1108, the CPU113notifies, using the display unit112, the user that the registration in the transfer list500has been performed in response to the Transfer Req401. If the display is ended, the processing proceeds to step S1109.

In step S1109, the CPU113checks whether the Cancel Transfer Req1001has been input. If the Cancel Transfer Req1001has not been input (NO in step S1109), the processing proceeds to step S1116. If the Cancel Transfer Req1001has been input (YES in step S1109), the processing proceeds to step S1110.

In step S1110, the CPU113checks whether a scene being recorded is registered in the transfer list500. InFIG. 10, the CPU113checks whether the scene #1(306(1)) is registered in the transfer list500. If the scene is not registered (NO in step S1110), the processing proceeds to step S1116. If the scene is registered (YES in step S1110), the processing proceeds to step S1111.

In step S1111, the CPU113causes the file break310. In response to this, inFIG. 10, the file #1(307(1)) at the time point when the transfer stop instruction has been received is brought into the completed state, and the new file #2(307(2)) for continuously recording the scene #1is generated.

In step S1112, the CPU113checks whether there is a file registerable in the transfer list500. The CPU113manages information of a scene currently being recorded. The scene information includes information of files constituting the scene. Based on the scene information, it can be determined whether the scene is constituted by a plurality of files using the file break310. InFIG. 10, since the file break310is caused at the time point when the Cancel Transfer Req1001is input, the file #1(307(1)) enters the completed state and can be registered in the transfer list500. In this case (YES in step S1112), the processing proceeds to step S1113, and the registration processing of the transfer list500is executed. On the other hand, if there is no file registerable in the transfer list500(NO in step S1112), the processing proceeds to step S1115.

In step S1113, the CPU113registers a file to be transferred, in the transfer list500. InFIG. 10, the CPU113registers the file #1(307(1)) in the completed state, in the transfer list500.

In step S1114, the CPU113checks whether all registerable files have been registered in the transfer list500. InFIG. 10, no other file to be registered in the transfer list500exists. If there is a file to be registered (NO in step S1114), the processing returns to step S1113. If the registration of all the files has been ended (YES in step S1114), the processing proceeds to step S1115.

In step S1115, the CPU113notifies, using the display unit112, the user that the registration in the transfer list500has been cancelled in response to the Cancel Transfer Req1001. If the display is ended, the processing proceeds to step S1116.

In step S1116, the CPU113checks whether the file break310has occurred for the files included in the scene being recorded. If the file size of a file to be recorded on the recording medium104reaches a file upper limit capacity of the file format, the file is divided according to the control of the CPU113. If the file break310has been detected (YES in step S1116), the processing proceeds to step S1117. If the file break310has not been detected (NO in step S1116), the processing proceeds to step S1119.

In step S1117, the CPU113checks whether the Transfer Req401has been input. The input in this step means that the registration in the transfer list500has not been cancelled in response to the Cancel Transfer Req1001. If the Transfer Req401has not been input (NO in step S1117), the processing proceeds to step S1119. If the Transfer Req401has been input (YES in step S1117), the processing proceeds to step S1118.

In step S1118, the CPU113updates the transfer list500.

In step S1119, the CPU113checks whether the file close309has occurred for the scene being recorded. The CPU113performs file close if the Rec Stop308is input via the operation unit106. InFIG. 10, the file #2(307(2)) is brought into the completed state by the file close309, and becomes registerable in the transfer list500. If the file close309has been detected (YES in step S1119), the processing proceeds to step S1120. If the file close309has not been detected (NO in step S1119), the processing returns to step S1102.

In step S1120, the CPU113checks whether the Transfer Req401has been input. The input in this step means that the registration in the transfer list500has not been cancelled in response to the Cancel Transfer Req1001. If the Transfer Req401has not been input (NO in step S1120), the processing is ended. If the Transfer Req401has been input (YES in step S1120), the processing proceeds to step S1121.

In step S1121, the CPU113updates the transfer list500. InFIG. 10, the CPU113registers the file (307(2)) that has been brought into the completed state by the file close309, in the transfer list500.

In step S1122, the CPU113performs file close registration for writing data indicating scene completion, in the transfer list500. After detecting the file close309and registering the file in the transfer list500, the CPU113registers the completion of the scene in the transfer list500.

In step S1123, the CPU113stores the numbers of the merged files into the RAM109.

In step S1124, the CPU113checks whether all the files registered in the transfer list500have been transferred. The transfer processing performed according to the transfer list500is as described in the first exemplary embodiment, and is performed asynchronously with the processing in this flowchart. If all the files registered in the transfer list500have been transferred (YES in step S1124), the processing proceeds to step S1125.

In step S1125, the CPU113deletes the files corresponding to the file numbers stored in step S1123, from a transfer destination FTP server.

In the present exemplary embodiment, the processing in steps S1122to S1125is performed for ensuring the consistency between the structure of files recorded on the recording medium104of the video camera100and the structure of files in the transfer destination FTP server. Nevertheless, the CPU113does not necessarily have to perform the deletion processing step S1125. For example, if the CPU113does not perform the deletion processing in step S1125, the CPU113may perform processing of transmitting information about the mergence to the FTP server as meta-information.

In addition, in the third exemplary embodiment, the description has been given of the configuration in which the file break310is not triggered by the Transfer Req401. Nevertheless, as in the second exemplary embodiment, the file break310may be triggered by the Transfer Req401.

Fourth Exemplary Embodiment

In a fourth exemplary embodiment, the description will be given of an example in which a video camera100records high image quality video data on a recording medium A104(hereinafter, referred to as main recording), and simultaneously records video data with lower bit rate than that of the main recording on a recording medium B117(hereinafter, referred to as proxy recording).

In addition, the configuration and basic operations of the video camera100are the same as those described in the first exemplary embodiment. The following description will be given mainly of a difference from the first exemplary embodiment.

A recording mode can be switched using the operation unit106to a simultaneous recording mode in which the main recording is performed on the recording medium A104and the proxy recording is performed on the recording medium B117. In the simultaneous recording mode, 2 types of recording data, i.e., main recording data and proxy recording data are simultaneously output from the CODEC110, and then, the main recording data is recorded on the recording medium A104and the proxy recording data is recorded on the recording medium B117.

FIGS. 12A and 12Bare diagrams illustrating an example of a relationship between a recording operation, scenes, files, and a transfer instruction in the video camera100according to the fourth exemplary embodiment. A file to be recorded on the recording medium A104is set as a file_A and a file to be recorded on the recording medium B117is set as a file_B.FIG. 12Aillustrates a state in which a transfer instruction has been issued so as to transfer a scene being recorded, to an external device, in the recording state (the Rec304) of the video camera100.

A scene #1(306(1)) is assumed to be initially recorded onto the recording medium A104, and has an allocated number “#1”.

Similarly to the scene #1(306(1)), a file_A#1(307a(1)) is assumed to be initially recorded onto the recording medium A104, and has an allocated number “#1”. In addition, similarly to the scene #1(306(1)), a file_B#1(307b(1)) is assumed to be initially recorded onto the recording medium B117, and has an allocated number “#1”.

Transfer Req401indicates an input operation performed via the operation unit106for instructing the transfer of the scene #1(306(1)) being recorded, to the external device.

In this case, for promptly transferring the file_B#1(307b(1)) being recorded on the recording medium B117, the file break310is triggered by the Transfer Req401. In response to this, the file_B#1(307b(1)) at the time point when the transfer instruction has been received is brought into the completed state, and a new file_B#2(307b(2)) for continuously recording the scene #1is generated. On the other hand, the file_A#1(307a(1)) being recorded on the recording medium A104continues to be recorded without the file break310.

If the Rec Stop308is instructed, the file_A#1(307a(1)) and the file_B#2(307b(2)) being recorded and being in the uncompleted state are completed by the file close309as files.

FIG. 12Billustrates a state in which a transfer instruction has been issued so as to transfer a scene being recorded, to the external device, in the recording state (the Rec304) of the video camera100.

A scene #2(306(2)) is assumed to be a scene started to be recorded upon the second Rec Start303being instructed, and has an allocated number “#2”.

Similarly to the scene #2(306(2)), a file_A#2(307a(2)) is assumed to be a file to be secondly recorded onto the recording medium A104, and has an allocated number “#2”. In addition, a file_B#3(307b(3)) is assumed to be a file to be thirdly recorded onto the recording medium B117, and has an allocated number “#3”.

The Transfer Req401indicates an input operation performed via the operation unit106for instructing the transfer of the scene #2(306(2)) being recorded, to the external device.

In this case, for promptly transferring the file_B#3(307b(3)) being recorded on the recording medium B117, the file break310is triggered by the Transfer Req401. In response to this, the file_B#3(307b(3)) at the time point when the transfer instruction has been received is brought into the completed state, and a new file_B#4(307b(4)) for continuously recording the scene #2is generated. InFIG. 12B, the file break310further occurs for the file_B#4(307b(4)). The file_B#4(307b(4)) is accordingly brought into the completed state, and a new file_B#5(307b(5)) for continuously recording the scene #2is generated. On the other hand, the file_A#2(307a(2)) being recorded on the recording medium A104continues to be recorded without the file break310.

Here, for example, suppose that the file break310is caused upon the size of a file_B reaching a predetermined file size in the recording medium B117. In this case, after the file break310is triggered by the Transfer Req401, the predetermined file size is changed to a small size. Normally, the file break is executed upon a file size reaching an upper limit capacity of a file system of a recording medium on which the file is being recorded. For example, if the file system of the recording medium is the File Allocation Table32 (FAT32), the upper limit capacity is 4 GB. Thus, the file break is executed so that the file size becomes a size not exceeding 4 GB. In the present exemplary embodiment, if the file break is executed so that the file size becomes a size not exceeding 4 GB, after the file break310is triggered by the Transfer Req401, the file break310is caused so that the file size becomes a size not exceeding 1 GB, and files following the file_B#4(307b(4)) are completed.

In addition, the file break310may be caused upon a record time of a file reaching a predetermined time, instead of the file size reaching the predetermined file size. Normally, the file break is executed upon the lapse of an arbitrary time due to restrictions on the file format of a file being recorded, and the like. For example, if the restrictions on the file format are set so that the recording up to 1 hour is allowed, the file break is executed at a timing not exceeding 1 hour. Also in this case, after the file break310is triggered by the Transfer Req401, the predetermined time is changed to a time shorter than 1 hour.

FIGS. 13A and 13Bare flowcharts illustrating file generation control processing and transfer list registration processing of the video camera100according to the fourth exemplary embodiment.

If the Transfer Req401serving as a transfer instruction is input as illustrated inFIGS. 12A and 12B, the video camera100causes the file break310and registers the transfer list500. According to the transfer list500, the video camera100transfers a scene to the external device.

In step S1301, the CPU113checks whether the video camera100is in the recording state. The processing is not executed in states other than the recording state (NO in step S1301), and step S1301is repeated. If the video camera100is in the recording state (YES in step S1301), the processing proceeds to step S1302.

In step S1302, the CPU113checks whether the Transfer Req401has been input. If the Transfer Req401has not been input (NO in step S1302), the processing proceeds to step S1310. If the Transfer Req401has been input (YES in step S1302), the processing proceeds to step S1303.

In step S1303, the CPU113causes the file break310for the proxy recording performed on the recording medium B117. In response to this, inFIG. 12A, the file_B#1(307b(1)) at the time point when the transfer instruction has been received is brought into the completed state, and the new file_B#2(307b(2)) for continuously recording the scene #1is generated. In addition, inFIG. 12B, the file_B#3(307b(3)) at the time point when the transfer instruction has been received is brought into the completed state, and the new file_B#4(307b(4)) for continuously recording the scene #2is generated.

In step S1314, the CPU113changes the timing of the file break. In the present exemplary embodiment, as already described, after the file break310is triggered by the Transfer Req401, the file break310is caused so that the file size becomes a size not exceeding 1 GB.

In step S1304, the CPU113checks whether a scene being recorded is registered in the transfer list500. If there is registration in the transfer list500(YES in step S1304), the processing proceeds to step S1306. If there is no registration in the transfer list500(NO in step S1304), the processing proceeds to step S1305.

In step S1305, the CPU113registers a scene to be transferred, in the transfer list500. The CPU113that has detected the input of the Transfer Req401in step S1302acquires a scene number instructed via the Transfer Req401to be transferred, and registers the acquired scene number in the transfer list500.

In step S1306, the CPU113checks whether there is a file registerable in the transfer list500. The CPU113manages information of a scene currently being recorded. The scene information includes information of files constituting the scene. Based on the scene information, it can be determined whether the scene is constituted by a plurality of files using the file break310. InFIG. 12A, since the file break310is caused at the time point when the Transfer Req401is input, the file_B#1(307b(1)) enters the completed state and can be registered in the transfer list500. The same applies to the file_B#3(307b(3)) inFIG. 12B. In this case (YES in step S1306), the processing proceeds to step S1307, and the registration processing of the transfer list500is executed. On the other hand, if there is no file registerable in the transfer list500(NO in step S1306), the processing proceeds to step S1309.

In step S1307, the CPU113registers a file to be transferred, in the transfer list500. InFIG. 12A, the CPU113registers the file_B#1(307b(1)) in the completed state, in the transfer list500. In addition, inFIG. 12B, the CPU113registers the file_B#3(307b(3)) in the completed state, in the transfer list500.

In step S1308, the CPU113checks whether all registerable files have been registered in the transfer list500. InFIGS. 12A and 12B, no other file to be registered in the transfer list500exists. If there is a file to be registered (NO in step S1308), the processing returns to step S1307. If the registration of all the files has been ended (YES in step S1308), the processing proceeds to step S1309.

In step S1309, the CPU113notifies, using the display unit112, the user that the registration in the transfer list500has been performed in response to the Transfer Req401. If the display is ended, the processing proceeds to step S1310.

In step S1310, the CPU113checks whether the file break310has occurred for the files included in the scene being recorded. InFIGS. 12A and 12B, after the generation of the file_B#2(307b(2)) and the file_B#4(307b(4)) is triggered by the Transfer Req401, as illustrated inFIG. 12B, the file break310occurs upon the file size of the file_B#4(307b(4)) reaching 1 GB. If the file break310has been detected (YES in step S1310), the processing proceeds to step S1311. If the file break310has not been detected (NO in step S1310), the processing proceeds to step S1313.

In step S1311, the CPU113checks whether the Transfer Req401has been input. If the Transfer Req401has not been input (NO in step S1311), the processing proceeds to step S1313. If the Transfer Req401has been input (YES in step S1311), the processing proceeds to step S1312.

In step S1312, the CPU113updates the transfer list500. InFIG. 12B, the CPU113that has detected the file break310registers the file #4(307(4)) in the transfer list500.

In step S1313, the CPU113checks whether the file close309has occurred for the scene being recorded. The CPU113performs file close if the Rec Stop308is input via the operation unit106. InFIG. 12A, the file_A#1(307a(1)) and the file_B#2(307b(2)) are brought into the completed state by the file close309, and the file_B#2(307b(2)) becomes registerable in the transfer list500. In addition, inFIG. 12B, the file_A#2(307a(2)) and the file_B#5(307b(5)) are brought into the completed state by the file close309, and the file_B#5(307b(5)) becomes registerable in the transfer list500. If the file close309has been detected (YES in step S1313), the processing proceeds to step S1315. If the file close309has not been detected (NO in step S1313), the processing returns to step S1302.

In step S1315, the CPU113checks whether all the files registered in the transfer list500have been transferred. The transfer processing performed according to the transfer list500is as described in the first exemplary embodiment, and the description thereof will be omitted here. If all the files registered in the transfer list500have been transferred (YES in step S1315), the processing proceeds to step S1316.

In step S1316, the CPU113changes the timing of the file break that has been changed in step S1314, to the original timing. In the present exemplary embodiment, the setting for causing the file break310so that the file size becomes a size not exceeding 1 GB is changed back to the normal setting (for causing the file break310so that the file size becomes a size not exceeding 4 GB).

As described above, when a transfer instruction has been received during the recording of image data of a scene, a file at the time point when the transfer instruction has been received is brought into the completed state, and a new file for continuously recording the scene is generated, so that the file brought into the completed state is transferred. With this configuration, when a transfer instruction is issued during the recording of image data, the image data being recorded can be promptly transferred to an external device.

Fifth Exemplary Embodiment

In a fifth exemplary embodiment, a modified example of the fourth exemplary embodiment will be described. In the present exemplary embodiment, the description will be mainly given of a difference from the fourth exemplary embodiment, and the description of the same parts as those in the other exemplary embodiments will be omitted.

InFIG. 12B, if the file break310is triggered by the Transfer Req401, the file_B#3(307b(3)) at the time point when the transfer instruction has been received is brought into the completed state, and the new file_B#4(307b(4)) for continuously recording the scene #2is generated. Then, the file break310further occurs for the file_B#4(307b(4)). The file_B#4(307b(4)) is accordingly brought into the completed state, and the new file_B#5(307b(5)) for continuously recording the scene #2is generated.

At this time, in the fourth exemplary embodiment, after the file break310is triggered by the Transfer Req401, the timing of the file break is changed.

In contrast, in the fifth exemplary 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 break310is caused. The file_B#4(307b(4)) is accordingly brought into the completed state, and the new file_B#5(307b(5)) for continuously recording the scene #2is generated.

FIGS. 14A and 14Bare flowcharts illustrating file generation control processing and transfer list registration processing of a video camera100according to the fifth exemplary embodiment. Steps similar to steps inFIGS. 13A and 13Bthat have been described in the fourth exemplary embodiment are assigned the same step numbers, and the description thereof will be omitted.

In step S1309, the CPU113notifies, using the display unit112, the user that the registration in the transfer list500has been performed in response to the Transfer Req401, and then in step S1401, the CPU113checks whether all the files registered in the transfer list500have been transferred. The transfer processing performed according to the transfer list500is as described in the first exemplary embodiment, and the description thereof will be omitted here. If all the files registered in the transfer list500have been transferred (YES in step S1401), the processing proceeds to step S1402.

In step S1402, the CPU113causes the file break310for the proxy recording performed on the recording medium B117. In response to this, inFIG. 12B, the file_B#4(307b(4)) is brought into the completed state, and the new file_B#5(307b(5)) for continuously recording the scene #2is generated. In this manner, by actively closing the next file and bringing the file into the completed state when the transfer of a preceding file is completed, the next file can be made successively-transferable.

As described above, the present invention has been described together with the exemplary embodiments. The above-described exemplary embodiments merely indicate example embodiments for executing the present invention. The technical scope of the present invention is not to be construed in a limited manner by these exemplary embodiments. In other words, the present invention can be executed in various forms without departing from the technical idea or the major features thereof.

For example, in the fourth exemplary embodiment, the description has been given of the example in which high image quality video data is recorded on the recording medium A104, and video data with lower bit rate than that of the main recording is simultaneously recorded on the recording medium B117. The configuration is not limited to this example. For example, video data equivalent to the data recorded on the recording medium A104may be recorded on the recording medium B117.

Other Embodiments

This application claims the benefit of Japanese Patent Application Nos. 2015-158532, filed Aug. 10, 2015, and 2015-164980, filed Aug. 24, 2015, which are hereby incorporated by reference herein in their entirety.