JP2024099141A - Video recording device, video recording device control method, and program - Google Patents

Abstract

To restore metadata in a more suitable manner even in a situation where the metadata associated with a video image is lost.SOLUTION: A control unit 10 acquires one piece of planning data from multiple pieces of planning data. The control unit 10 extracts camera recording information from a video file. The control unit 10 generates an XML file on the basis of the acquired planning data and the extracted camera recording information, and records the XML file in association with the video. The control unit 10 records location information of the planning data in association with the video. When the XML file associated with the video is lost, the control unit 10 reads out the planning data on the basis of the location information, and generates an XML file on the basis of the planning data and the camera recording information.SELECTED DRAWING: Figure 1

Description

This disclosure relates to a video recording device, a control method for a video recording device, and a program.

In the news workflow at broadcasting stations and news agencies, the content editing and management of captured video is made more efficient by utilizing additional information (hereinafter referred to as metadata) that is attached to the video content captured during reporting.

On the other hand, the above metadata is generated when a moving image recording device (in other words, an imaging device) such as a video camera captures an image, but it may be deleted by a user's mistake or lost due to a software malfunction. In view of this situation, Patent Document 1 discloses a method of restoring the metadata by recording a backup of a content attribute file, which is metadata, in advance in an external storage device and reacquiring the content attribute file upon request.

JP 2005-107770 A

On the other hand, video recording devices such as video cameras are often used in situations where they are not connected to an external storage device for taking backups. In such cases, it is conceivable that metadata may be lost before a backup of the metadata is recorded. In such a situation, it may be difficult to restore the lost metadata, which may affect content management.

In consideration of the above problems, the present invention aims to make it possible to recover metadata associated with a video in a more suitable manner even in a situation where the metadata has been lost.

The video recording device according to the present invention includes an acquisition means for acquiring one first metadata from among a plurality of first metadata, an extraction means for extracting information related to the recorded contents from the video, a first generation means for generating second metadata from the first metadata acquired by the acquisition means and the information related to the recorded contents extracted by the extraction means, a first recording means for recording the video and the second metadata in association with each other, and a second recording means for recording location information indicating a location where the first metadata used to generate the second metadata is stored in association with the video with which the second metadata is associated, and is characterized in that, when the second metadata associated with the video is lost, the first generation means reads out the first metadata based on the location information and generates the second metadata from the first metadata and the information related to the recorded contents extracted by the extraction means.

According to the present invention, even in a situation where metadata associated with a video image is lost, it is possible to restore the metadata in a more suitable manner.

FIG. 1 is a diagram illustrating an example of a configuration of an imaging device. FIG. 2 is a diagram showing an example of a folder configuration related to management of planning data. FIG. 2 is a diagram showing an example of a folder configuration relating to management of moving images and additional information. FIG. 2 is a diagram showing an example of the configuration of a moving image file. FIG. 11 is a diagram illustrating an example of metadata. 11 is a flowchart showing an example of processing performed by the imaging device. 11 is a flowchart showing an example of processing performed by the imaging device. 11 is a flowchart showing an example of processing performed by the imaging device. FIG. 11 is a diagram showing an example of a menu screen. 11 is a flowchart showing an example of processing performed by the imaging device. FIG. 13 is a diagram showing an example of a screen used for notifying information. FIG. 2 is a diagram illustrating an example of a configuration of a mobile terminal. FIG. 11 is a sequence diagram showing an example of processing performed by the imaging device and the mobile terminal. 10 is a flowchart showing an example of a process of a mobile terminal. FIG. 13 is a diagram showing an example of an operation screen. FIG. 13 is a diagram showing an example of an operation screen. 11 is a flowchart showing an example of processing performed by the imaging device. FIG. 11 is a diagram illustrating an example of metadata. 11 is a flowchart showing an example of processing performed by the imaging device. 11 is a flowchart showing an example of processing performed by the imaging device. 11 is a flowchart showing an example of a process of a mobile terminal. FIG. 13 is a diagram showing an example of a screen used for notifying information.

A preferred embodiment of the present disclosure will be described in detail below with reference to the attached drawings. Note that in this specification and drawings, components having substantially the same functional configuration are designated by the same reference numerals to avoid redundant description.

First Embodiment
A first embodiment of the present disclosure will be described below. First, an example of the configuration of an image capture device according to the present embodiment will be described with reference to Fig. 1. The image capture device 100 according to the present embodiment is realized by a so-called digital camera such as a camcorder.
The imaging device 100 includes a control unit 10, a ROM (Read Only Memory) 17, a RAM (Random Access Memory) 18, an image compression/expansion unit 11, an imaging unit 12, and an image processing unit 13. The imaging device 100 also includes a wireless communication unit 14, a display unit 15, an operation unit 16, and a removable recording medium I/F 19. The control unit 10 and each of the components other than the control unit 10 exemplified above are connected to each other via a bus or the like so as to be able to transmit and receive data to and from each other.

The control unit 10 is a system control unit that controls the entire system of the imaging device 100. The control unit 10 also controls the operation of each component. The control unit 10 can be realized, for example, by a CPU (Central Processing Unit). The ROM 17 is a non-volatile recording medium that stores a program executed by the control unit 10. The RAM 18 is a volatile recording medium used as a work memory for the control unit 10. The processing described later with reference to Figures 3A to 3C, 5, 8, 9D, 11, and 12A is realized, for example, by a program recorded in the ROM 17 being expanded in the RAM 18 and executed by the control unit 10.
The RAM 18 is also used as a temporary storage area when the image compression/expansion unit 11 performs compression or expansion processing on image data captured by the imaging unit 12 and processed by the image processing unit 13, or image data read from the removable recording medium 20. The RAM 18 is also used as a temporary storage area for holding image data such as those exemplified above when an image represented by the image data is displayed on the display unit 15.

The removable recording medium I/F 19 is an interface for connecting a recording medium for recording various data to the imaging device 100. For example, the recording medium may be used to record image data. The removable recording medium I/F 19 may be realized as a slot into which a removable recording medium such as a memory card can be inserted. In the example shown in FIG. 1, it is assumed that a removable recording medium 20 is attached to the removable recording medium I/F 19. The recording medium used to record image data is not necessarily limited to a recording medium that is removable from the imaging device 100. For example, image data may be recorded on a recording medium (e.g., a memory) built into the imaging device 100.

The image processing unit 13 performs various image processing such as predetermined pixel interpolation processing, resizing processing, and color conversion processing on image data corresponding to the imaging result by the imaging unit 12. The image processing unit 13 may also execute predetermined arithmetic processing using image data corresponding to the imaging result and notify the control unit 10 of the result of the arithmetic processing. This allows the control unit 10 to perform various controls (e.g., exposure control, auto white balance control, etc.) related to imaging by the imaging unit 12 based on the result of the arithmetic processing by the image processing unit 13, for example.
The image compression/expansion unit 11 performs compression processing in a predetermined format on the image data that has been subjected to image processing by the image processing unit 13. The image compression/expansion unit 11 may also perform expansion processing on the compressed image data in accordance with a predetermined format. As a specific example, the image compression/expansion unit 11 may perform expansion processing on image data (compressed image data) read from the removable recording medium 20.

The imaging unit 12 has an imaging lens (including, for example, a zoom lens and a focus lens) and an imaging element, captures an image of a subject based on the control of the control unit 10, and generates image data of a still image or a moving image based on the imaging result. In the following description, when there is no particular distinction between a still image and a moving image, they may simply be referred to as images.

The display unit 15 is an output interface that presents various information to the user by displaying the information as an image based on the control of the control unit 10. As a specific example, the display unit 15 may display various setting states, an image corresponding to the image capture result by the imaging unit 12, an image reproduced based on image data read from a removable recording medium, etc. The display unit 15 may be realized, for example, by a display inside a peer-type viewfinder, a vari-angle LCD monitor, etc.

The operation unit 16 is an input interface that accepts various operations from a user for the imaging device 100. The operation unit 16 may include, for example, a power switch for supplying power to the imaging device 100, a shooting start button, and a mode switching button for switching to an operation mode such as a camera mode (shooting mode) or a playback mode.
The operation unit 16 may also include a touch panel. In this case, the control unit 10 may detect operations on the touch panel, as exemplified below. Specifically, the control unit 10 may detect that an operating object such as a finger or a pen has touched the touch panel (hereinafter also referred to as touch down) or that the operating object is touching the touch panel (hereinafter also referred to as touch on). The control unit 10 may also detect that the operating object is moving while touching the touch panel (hereinafter also referred to as move). The control unit 10 may also detect that the operating object is moving away from the touch panel (hereinafter also referred to as touch up) or that the operating object is not touching the touch panel (hereinafter also referred to as touch off). The control unit 10 determines what kind of operation has been performed via the touch panel based on these operations and the position coordinates on the touch panel that the operating object is touching. In addition, when detecting a move, the control unit 10 may determine the moving direction of the operating object moving on the touch panel for each of the vertical component and horizontal component on the touch panel based on the change in the position coordinates on the touch panel that the operating object is touching.
Furthermore, the control unit 10 may recognize that a stroke has been drawn when a touch-up is performed on the touch panel after a certain amount of movement from touch-down. The operation of quickly drawing a stroke is also called a flick. A flick is an operation of quickly moving a finger on the touch panel for a certain distance while keeping the finger in contact with the touch panel, and then releasing the finger; in other words, an operation of quickly tracing the touch panel with the finger as if flicking the finger. For example, the control unit 10 may determine that a flick has been performed when it detects a movement of a certain distance or more at a certain speed or more, and then detects a touch-up.
Furthermore, the control unit 10 may determine that a drag has been performed when it detects that a move has been made over a predetermined distance or more at less than a predetermined speed.
As the touch panel, various types of touch panels can be applied, such as a resistive film type, a capacitive type, a surface acoustic wave type, an infrared type, an electromagnetic induction type, an image recognition type, an optical sensor type, and the like.

The wireless communication unit 14 transmits and receives data to and from external devices such as an external camera or a personal computer via a wireless communication path under the control of the control unit 10. As a specific example, the wireless communication unit 14 transmits data including setting information and operation information of the imaging device 100 to the external device, and receives additional information linked to various commands and image data from the external device. Of course, the data transmitted and received by the wireless communication unit 14 between the external device is not particularly limited. For example, the data transmitted and received by the wireless communication unit 14 between the external device may include digital image data, analog video signals, additional information, etc. Also, the additional information may be acquired from the external device. In this embodiment, for convenience, the additional information is managed by a file (hereinafter also referred to as an XML file) written in XML (Extensible Markup Language), which is a markup language. Of course, the method of managing the additional information is not limited to the method of using an XML file, and various methods can be applied.

Next, an example of a folder configuration for managing planning data files by the imaging device 100 according to this embodiment will be described with reference to FIG. 2A.
In this embodiment, planning data is data that is added to a moving image according to the imaging result by the imaging device 100 and is used to manage additional information used to manage the moving image. The additional information managed by the planning data may include additional information set by the user, such as clip title, shooting information, photographer, keywords, category, genre, language information, contributors, rights information, etc. It is possible to generate multiple pieces of planning data, and it is also possible to appropriately switch between the planning data to be applied depending on the situation at hand. The planning data corresponds to an example of "first metadata."

In this embodiment, a management folder is generated on the removable recording medium 20 connected via the removable recording medium I/F 19, and planning data files are stored in this folder. In the example shown in FIG. 2A, an XMLTAG folder 271 is generated directly under the ROOT folder, and files 272 to 275 corresponding to individual planning data (hereinafter also referred to as planning data files) are stored in this XMLTAG folder.

Next, referring to FIG. 2B, an example of a folder configuration for managing moving image files corresponding to the imaging results and files of additional information added to the moving images by the imaging device 100 according to this embodiment will be described.
In this embodiment, the case where compressed video frames, management information such as time codes and audio data are recorded in a container structure called MP4 (MPEG-4 Part 14 or ISO/IEC 14496-14:2003) will be described as an example. On the other hand, the format used to record moving images is not limited to MP4, and various formats can be applied. Examples of such formats include AVCHD (Advanced Video Codec High Definition) and MXF (Material eXchange Format).

When the control unit 10 initializes the removable recording medium 20 based on an instruction from the user via the operation unit 16, the control unit 10 generates a DCIM folder 201 in the removable recording medium 20 to be used for managing files of moving images and files of additional information. When the recording of a moving image is started, the control unit 10 generates a folder for each management unit of the files of the moving images, and stores the files of the moving images and files of additional information according to the imaging results in the folder. For example, the folder 202 named "100_0218" in the example shown in FIG. 2B shows an example of a folder generated for each management unit of the files of the moving images. In this case, the 100 in the folder name represents a directory number, which is assigned in order from 100 and increases up to a maximum of 999. In addition, the 0128 in the folder name indicates the date on which the target folder was created, and indicates that the folder was created on January 28th. That is, in the example shown in FIG. 2B, the files of the moving images and the files of additional information are managed by the date on which the moving images were recorded. In the example shown in FIG. 2B, the folder 202 stores a video stream file 203 indicated as MVI_0001.MP4 and an additional information file 204 indicated as MVI_0001.XML.
When a plurality of video files are recorded, the file names of the MP4 files and XML files are successively adjusted, for example by incrementing the numbers.
The time code set for each frame and the like are recorded in an MP4 file (for example, MPV_0001.MP4), while the tag information and the like are recorded in an XML file (for example, MVI_0001.XML).

Next, an example of the configuration of a moving image file according to this embodiment will be described with reference to FIG. 2C.
The ftype box 210 is information indicating compatibility of the file format.
The moov box 211 stores management information and thumbnail images necessary for playback.
The XMP box 212 stores XMP (Extensible Metadata Platform) and allows any metadata to be set.
Any information can be added to the uuid box 213. For example, a preview image can be stored in the uuid box 213.
The mdat box 214 stores encoded video data, audio data, time code data, and metadata for each frame.

Next, an example of the configuration of the moov box 211 will be described.
Any information can be added to the uuid box 221, and a thumbnail image 225 that is displayed during playback and management information 226 that is used during playback can be stored therein.
The track boxes 215 to 217 store management information relating to video data, audio data, and time code data.
The stsz boxes 218 to 220 store the data sizes of the video data, audio data, time code data, and metadata in units of frames for each coding unit.
The stco boxes 222 to 224 are stored in a track box, and store information indicating the storage positions of the video data, audio data, time code data, and mdat 214, which is metadata in frame units.
Each piece of data is stored in the mdat box 214 in units called chunks, each chunk being made up of one or more coding units.

Next, an example of the configuration of the mdat box 214 will be described.
Data 230 to 238 indicate video data, audio data, time code data, and metadata for each frame stored in the mdat box 214 .
Each piece of data can be accessed in chunk units by the value written in the stco box. For example, data 230 (CV1) can be traced back to the value 250 in the stco box 222.

Next, an example of the contents of metadata in each of the video file and the additional information file according to this embodiment will be described with reference to FIG. 2D.
Metadata 260 shows an example of the contents of metadata in a moving image file, which are stored in management information 226 .
The management information 226 records information such as the shutter speed when the imaging device 100 captures an image, the F-number indicating the lens brightness, the recording frame rate, the playback frame rate, the recording time, and planning data location information. The management information 226 also records an XML file, which is an additional information file, in association with the moving image file, and may also record information including type information of the XML file. The management information 226 corresponds to an example of an additional information area for a moving image.
The type information 261 indicates an example of the contents of the XML file type information described in the metadata 260, and is stored in the management information 226. As the type information 261, for example, information indicating whether or not an XML file has been recorded, information indicating an original format in which the XML file has tag information specific to the imaging device 100, information indicating news metadata which is a format specialized for news reporting, and the like are recorded.
Metadata 262 shows an example of the contents of the metadata when the XML file is recorded in an original format having tag information specific to the imaging device 100. As the metadata 262, for example, the title, photographer, shooting information, the product name of the imaging device 100, firmware version information, serial number, lens name, etc. are recorded.
Metadata 263 shows an example of the contents of news metadata when the XML file is recorded in the original format for news reporting purposes. The metadata 263 includes the title, photographer, shooting information, keywords, category, genre, date and time information, language information, contributors, rights information, information about the video file (file name, recording time, identification information, file format, audio information), etc.
The planning data location information 264 indicates an example of the contents of the planning data location information described in the metadata 260, and these are stored in the management information 226. The planning data location information 264 records the file path and slot information of the planning data. In this way, the planning data location information is information that indicates the location where the target planning data is held. In other words, the planning data location information corresponds to an example of location information that indicates the location where the first metadata is held.

Next, an example of processing by the imaging device 100 according to this embodiment will be described with reference to FIGS.
First, an example of a process in which the control unit 10 selects planning data to be applied when recording a moving image based on an instruction via the operation unit 16 will be described with reference to FIG. 3A.
In S330, the control unit 10 determines whether the XML file type selected via the operation unit 16 is news metadata.
If the control unit 10 determines in S330 that the selected XML file type is news metadata, the control unit 10 advances the process to S331.
On the other hand, if the control unit 10 determines in S330 that the XML file type selected is not news metadata, the control unit 10 ends the series of processes shown in FIG. 3A.

In S331, the control unit 10 determines whether or not a planning data file is stored in the SD card (removable recording medium 20).
If the control unit 10 determines in S331 that a planning data file is stored in the SD card, the control unit 10 advances the process to S332.
On the other hand, if the control unit 10 determines in S331 that no planning data file is stored in the SD card, the control unit 10 ends the series of processes shown in FIG. 3A.

In S332, the control unit 10 accepts the selection of planning data via the operation unit 16. As a specific example, when a menu button included in the operation unit 16 is operated, the menu 404 shown in FIG. 4(a) is displayed, and the user can select the planning data 405 to be used for recording from among the menu items.

In S333, the control unit 10 reads planning data from the planning data file in the SD card associated with the item selected in S332, and stores the planning data in RAM 18.

Next, an example of a process in which the control unit 10 accepts a recording start request via the operation unit 16 and starts recording of a moving image will be described with reference to FIG. 3B.
In S300, the control unit 10 generates metadata to be used when recording a moving image on the removable recording medium 20, and stores the metadata in the RAM 18. As a specific example, the control unit 10 generates metadata 260 in the moving image file, original metadata 262, and news metadata 263, as shown in FIG. 2D, as metadata to be used when recording the moving image. At this time, the control unit 10 may set provisional values at the time of S300 for information such as recording time and update date and time that are determined after the moving image is captured (in other words, after the clip is created). The metadata 260 and 262 correspond to an example of information on the recorded contents of the moving image, and the information is hereinafter also referred to as camera recording information. The control unit 10 extracts the generated camera recording information from the moving image file, and stores the camera recording information in the RAM 18.

In S301, the control unit 10 judges whether or not the XML file recording setting specified via the operation unit 16 is ON (i.e., whether or not recording of XML files is enabled). The XML file recording setting is set according to an item specified via the menu 400 shown in Fig. 4(b), for example. In the example shown in Fig. 4(b), when the item 401 is selected, the XML file recording setting is set to ON.
If the control unit 10 determines in S301 that the XML file recording setting is ON, the control unit 10 advances the process to S302.
On the other hand, if the control unit 10 determines in S301 that the XML file recording setting is not ON, the control unit 10 advances the process to S305.

In S302, the control unit 10 determines whether the XML file type setting specified via the operation unit 16 is news report metadata. The XML file type setting is set according to an item specified via the menu 400 shown in Fig. 4(c), for example. In the example shown in Fig. 4(c), when the item 403 is specified, the XML file type setting is set to news report metadata.
If the control unit 10 determines in S302 that the XML file type setting is news metadata, the control unit 10 advances the process to S303.
On the other hand, if the control unit 10 determines in S302 that the XML file type setting is not news metadata, the control unit 10 advances the process to S304.

In S303, the control unit 10 reads the metadata stored in the RAM 18 in S300, and instructs the removable recording medium I/F 19 to record the metadata. As a result, the news metadata 263 is recorded in an XML file (a file that stores metadata), and the XML file is written to the removable recording medium 20.

In S304, the control unit 10 reads the metadata stored in the RAM 18 in S300, and instructs the removable recording medium I/F 19 to record the metadata. As a result, the original, non-standardized metadata 262 is recorded in an XML file (a file that stores metadata), and the XML file is written to the removable recording medium 20.

In S305, the control unit 10 writes, in the RAM 10, the XML file type information to be written in the management information 226 of the video file.
In S306, the control unit 10 reads out the metadata stored in the RAM 18 in S300 and S305, converts it into the format of management information 226 for the video file, and instructs the removable recording medium I/F 19 to record the metadata. As a result, the metadata 260 is recorded as management information for the video file, and the video file is stored in the removable recording medium 20. Then, the control unit 10 writes planning data location information (planning data location information 264 shown in FIG. 2D) indicating the location where the planning data is stored into the RAM 18.

In S307, the control unit 10 converts the video data, audio data, and time code data stored in the RAM 18 into the format illustrated in FIG. 2C, and instructs the removable recording medium I/F 19 to record the metadata. As a result, the video data, audio data, and time code data are written to the removable recording medium 20 as a video file.

Next, an example of a process in which the control unit 10 accepts a recording stop request via the operation unit 16 and stops recording of a moving image will be described with reference to FIG. 3C.
In S<b>320 , the control unit 10 generates metadata to be used when stopping recording of a moving image on the removable recording medium 20 , and stores the generated metadata in the RAM 18 .

In S321, the control unit 10 determines whether or not the XML file recording setting specified via the operation unit 16 is ON (that is, whether or not recording of the XML file is enabled).
If the control unit 10 determines in S321 that the XML file recording setting is ON, the control unit 10 advances the process to S322.
On the other hand, if the control unit 10 determines in S321 that the XML file recording setting is not ON, the control unit 10 advances the process to S324.

In S322, the control unit 10 determines whether the XML file type setting specified via the operation unit 16 is news metadata.
If the control unit 10 determines in S322 that the XML file type setting is news metadata, the control unit 10 advances the process to S323.
On the other hand, if the control unit 10 determines in S322 that the XML file type setting is not news metadata, the control unit 10 advances the process to S324.

In S323, the control unit 10 issues an instruction to the removable recording medium I/F 19 to read out the XML file that was written from the removable recording medium 20 at the start of recording into the RAM 18. The control unit 10 then updates the XML file by reflecting the recording time and update date and time information of the video file generated in S320 in the XML file read out to the RAM 18. The control unit 10 then instructs the removable recording medium I/F 19 to record the updated XML file. As a result, the updated XML file is written to the removable recording medium 20.

In S324, the control unit 10 puts the video data, audio data, and time code data held in the RAM 18 up until the time the recording stop request was received into the format shown in FIG. 2(c), and instructs the removable recording medium I/F 19 to record this data. As a result, the video data, audio data, and time code data are written to the removable recording medium 20 as a video file, and the series of processes shown in FIG. 3C ends.

With reference to FIG. 5, an example of a process for recovering metadata by regenerating the metadata when the metadata has been lost due to erroneous erasure or loss will be described.
In S501, the control unit 10 determines whether or not the XML file associated with the clip in the SD card is damaged (for example, whether or not it has been lost due to erroneous erasure or the like).
If the control unit 10 determines in S501 that the XML file is damaged, the process proceeds to S502.
On the other hand, if the control unit 10 determines in S501 that the XML file is not damaged, the control unit 10 ends the series of processes shown in FIG.

In S502, the control unit 10 notifies the user of the information by displaying information indicating a warning on the display unit 15. For example, FIG. 6(a) is a diagram showing an example of a method of notifying the user of the information indicating a warning. In the example shown in FIG. 6(a), an exclamation mark indicating a warning is displayed in a format superimposed on a thumbnail of the content whose XML file has been determined to be damaged.

In S503, the control unit 10 determines whether or not planning data location information is included in the management information 226 of the moving image file.
If the control unit 10 determines in S503 that planning data location information is included in the management information 226 of the moving image file, it advances the process to S504.
On the other hand, if the control unit 10 determines in S503 that the management information 226 of the video file does not contain planning data location information, the control unit 10 ends the series of processes shown in Fig. 5. In this case, the control unit 10 may prompt the user to perform a recovery operation by displaying a message such as that shown in Fig. 6(c) on the display unit 15.

In S504, the control unit 10 confirms with the user whether or not to restore the lost metadata. As a specific example, the control unit 10 may display a dialog box as shown in Fig. 6B on the display unit 15 and then accept an instruction from the user via the dialog box as to whether or not to restore the metadata.
If the control unit 10 determines in S504 that the user has instructed to restore the metadata, the control unit 10 advances the process to S505.
On the other hand, if the control unit 10 determines in S504 that the user has not instructed to restore the metadata, the control unit 10 ends the series of processes shown in FIG.

In S505, the control unit 10 stores in the RAM 18 the planning data restored from the planning data location information.
In S<b>506 , the control unit 10 restores the camera record information from the moving image file, and stores the camera record information in the RAM 18 .
In S508, the control unit 10 restores the XML file based on the planning data and camera recording information stored in the RAM 18. When the restoration of the XML file is completed, the control unit 10 presents a message indicating that the restoration of the XML file has been completed to the user by displaying the message on the display unit 15, and ends the series of processes shown in Fig. 5. For example, Fig. 6(d) shows an example of a message displayed when the restoration of the XML file is completed.

By applying the above-described control, even if the XML file (metadata) linked to a video file is lost due to damage or the like, it is possible to restore the XML file based on the planning data location information and camera recording information.
In this embodiment, the XML file (metadata) to be restored corresponds to an example of the second metadata. Also, the planning data used to restore the XML file corresponds to an example of the first metadata. That is, the planning data location information indicating the location where the planning data corresponding to the first metadata is stored corresponds to an example of the location information indicating the location where the first metadata is stored.
In the above embodiment, an example of the case where the planning data location information is recorded in a video file has been described, but the method is not particularly limited as long as it is possible to manage the planning data location information in association with the video. As a specific example, the planning data location information may be managed by recording the planning data location information in an additional data file added to the video.

Second Embodiment
A second embodiment of the present disclosure will be described below. In the above-described embodiment, an example of a case where an XML file (metadata) is lost due to damage or the like and the XML file is restored using planning data stored in the imaging device 100. In contrast, in the present embodiment, an example of a case where planning data is stored in an external device different from the imaging device 100 and the XML file is restored using the planning data will be described.

First, an example of the configuration of the imaging device 100 and a portable terminal 700, which is an external device, will be described with reference to Fig. 7. Note that the configuration of the imaging device 100 is substantially similar to the example shown in Fig. 1, and therefore detailed description thereof will be omitted.
The portable terminal 700 includes a control unit 71, a display unit 72, an operation unit 73, a wireless communication unit 74, a ROM 75, a RAM 76, and a file control unit 77. The control unit 70 and each of the components other than the control unit 70 exemplified above are connected to each other via a bus or the like so as to be able to transmit and receive data to and from each other.

The control unit 71 is a system control unit that controls the overall system of the mobile terminal 700. The control unit 71 also controls the operation of each component. The control unit 71 can be realized, for example, by a CPU. The ROM 75 is a non-volatile recording medium that stores the program executed by the control unit 71. The RAM 76 is a volatile recording medium used as a work memory for the control unit 71. The processing described below with reference to Figures 9A and 12B is realized, for example, by a program recorded in the ROM 75 being expanded into the RAM 76 and executed by the control unit 71.

The display unit 72 is an output interface that displays various information as images based on the control of the control unit 71, thereby presenting the information to the user. As a specific example, the display unit 72 may display various setting states, data received by the wireless communication unit 74 (including, for example, digital image data, analog video signals, and additional information), and the like. The display unit 72 may be realized, for example, by a display or the like.

The operation unit 73 is an input interface that accepts various operations for the mobile terminal 700 from the user. The operation unit 73 may include, for example, a power switch for supplying power to the mobile terminal 700. The operation unit 73 may also include a touch panel, similar to the operation unit 16 of the imaging device 100.

Based on the control of the control unit 71, the wireless communication unit 74 transmits and receives data to and from external devices such as an external camera or a personal computer via a wireless communication path. As a specific example, the wireless communication unit 74 receives setting information, operation information, and the like from the imaging device 100, and transmits to the imaging device 100 commands for operating the imaging device 100 and additional information that is linked to and recorded with image data. Data that is the subject of transmission and reception by the wireless communication unit 74 may include, for example, digital image data, analog video signals, additional information, and the like.

The file control unit 77 can analyze data such as video files and additional information received by the wireless communication unit 74, and control the generation of thumbnail images, etc.

Next, an example of a sequence when imaging device 100 (for example, a camcorder) and portable terminal 700 are connected via a wireless communication path will be described with reference to FIG.
In S801, when the control unit 10 of the imaging device 100 receives an instruction for wireless connection with the portable terminal 700 via the operation unit 16, the control unit 10 instructs the wireless communication unit 14 to establish a wireless connection with the portable terminal 700.
In S<b>802 , when the control unit 71 of the portable terminal 700 receives an instruction to establish a wireless connection with the imaging device 100 via the operation unit 73 , the control unit 71 instructs the wireless communication unit 74 to establish a wireless connection with the imaging device 100 .

In S803, the wireless communication unit 14 of the imaging device 100 and the wireless communication unit 74 of the portable terminal 700 execute a predetermined communication sequence with each other, thereby establishing a wireless connection between the imaging device 100 and the portable terminal 700.
At this time, the control unit 10 of the imaging device 100 acquires the MAC address of the portable terminal 700 through the wireless communication unit 14 using ARP (Address Resolution Protocol) based on the IP address of the portable terminal 700. The control unit 10 holds the acquired MAC address in the RAM 18. After the wireless connection is established, the imaging device 100 and the portable terminal 700 can transmit and receive control commands, setting information, digital image data, analog video signals, additional information, and the like between them by using the wireless connection. In this embodiment, an example of the case where the control unit 10 of the imaging device 100 acquires a MAC address as information for identifying the portable terminal 700 has been described, but as long as it is possible to identify the portable terminal 700, the information used for this purpose is not particularly limited. As a specific example, a serial number or the like may be used to identify the portable terminal 700.

Next, an example of a process in which the portable terminal 700 transmits planning data to the imaging device 100 in response to an instruction from a user will be described with reference to FIG. 9A.
In S901, the control unit 71 determines whether or not a selection of planning data has been received from the user via the operation unit 73. As a specific example, the control unit 71 may display a menu screen shown in Fig. 9B on the display unit 72, and receive the selection of planning data from the user via the menu screen.
When the control unit 71 determines in S901 that the selection of planning data has been accepted, the control unit 71 stores the target planning data in the RAM 76 and then advances the process to S902.
On the other hand, if the control unit 71 determines in S901 that the selection of planning data has not been accepted (for example, if the cancel button is pressed on the menu screen), it ends the series of processes shown in FIG. 9A.

In S902, the control unit 71 determines whether or not to transmit the planning data to the imaging device 100, based on an instruction from the user via the operation unit 73. As a specific example, the control unit 71 may display a menu screen shown in Fig. 9C on the display unit 72, and receive an instruction from the user regarding whether or not to transmit the planning data via the menu screen.
If the control unit 71 determines in S902 that an instruction to transmit the planning data to the imaging device 100 has been received, the control unit 71 advances the process to S903.
On the other hand, if the control unit 71 determines in S902 that an instruction not to transmit the planning data to the imaging device 100 has been received, the control unit 71 ends the series of processes shown in FIG. 9A.

In S903, the control unit 71 transmits, via the wireless communication unit 74, to the imaging device 100 the planning data stored in the RAM 76 in S901 and location information indicating where the planning data is stored (e.g., directory name and file name).

Next, an example of processing by the imaging device 100 when the imaging device 100 receives planning data and planning data location information from the mobile terminal 700 will be described with reference to FIG. 9D.
In S911, the control unit 10 waits for transmission of the planning data and the location information of the planning data from the mobile terminal 700. Then, when the control unit 10 determines that the planning data and the location information of the planning data have been received from the mobile terminal 700 via the wireless communication unit 14, the control unit 10 proceeds to the process of S912.
In S912, the control unit 10 stores in the RAM 18 the planning data received from the portable terminal 700. In addition, the control unit 10 stores in the RAM 18 location information (e.g., directory name and file name) of the planning data received from the portable terminal 700 in association with the Mac address of the portable terminal 700 already stored in the RAM 18.

Next, an example of a folder configuration related to management of video files and additional information will be described with reference to Fig. 10. In this embodiment, the contents of planning data location information 1040 are different from the contents of planning data location information 264 in the first embodiment described above.
In this embodiment, when restoring an XML file, the planning data used for the restoration is held on the mobile terminal 700. Therefore, the planning data location information 1040 stores mobile phone individual information (such as a Mac address or serial number) unique to the mobile terminal 700, and information indicating the location in the mobile terminal 700 where the planning data is held (directory name and file name).

Next, referring to FIG. 11, an example of the process in which the control unit 10 accepts a recording start request via the operation unit 16 and starts recording of a moving image will be described. In the example shown in FIG. 11, the process of S1151 differs from the example shown in FIG. 3B. That is, in S1151, the control unit 10 applies the planning data location information 1040 described with reference to FIG. 10 as the planning data location information to be written to RAM 18. Note that other processes are substantially similar to the example shown in FIG. 3B, and therefore detailed description will be omitted.

Next, referring to FIG. 12A, an example of a process for recovering metadata by regenerating the metadata when the metadata has been lost due to erroneous deletion, loss, or the like will be described. Note that in this embodiment, as described above, the planning data used to recover the metadata is held on the mobile terminal 700 side. That is, the imaging device 100 receives the planning data from the mobile terminal 700 and then recovers the metadata using the planning data. Therefore, in the example shown in FIG. 12A, the processes of S1204 to S1206 and S1209 are different from the example shown in FIG. 5, but the other processes are substantially similar to the example shown in FIG. 5. Therefore, hereinafter, the description will focus on the parts that are different from the example shown in FIG. 5, and detailed descriptions of the parts that are substantially similar to the example shown in FIG. 5 will be omitted.

In S1204, the control unit 10 determines whether the Mac address of the connected mobile terminal 700 matches the Mac address indicated in the planning data location information in the video file corresponding to the XML file (metadata) to be restored.
Specifically, the Mac address of the connected portable terminal 700 is held in RAM 18 when a wireless connection is established between the imaging device 100 and the portable terminal 700. Furthermore, the control unit 10 reads out the planning data location information recorded in the moving image file from the removable recording medium 20 and loads it in RAM 18. Then, the control unit 10 compares the Mac address of the connected portable terminal 700 held in RAM 18 with the Mac address included in the planning data location information loaded in RAM 18.
If the control unit 10 determines in S1204 that the Mac address of the connected mobile terminal 700 matches the Mac address indicated in the target planning data location information, the control unit 10 advances the process to S1205.
On the other hand, if the control unit 10 determines in S1204 that the Mac address of the connected mobile terminal 700 does not match the Mac address indicated in the target planning data location information, the control unit 10 advances the process to S1209.

In S1205, the control unit 10 transmits, via the wireless communication unit 14, to the connected mobile terminal 700, the planning data location information (directory name and file name) stored in the video file corresponding to the XML file to be restored. The control unit 10 then requests the mobile terminal 700 to transmit the planning data.

In S<b>1206 , the control unit 10 determines whether or not recovery planning data has been received from the mobile terminal 700 via the wireless communication unit 14 .
If the control unit 10 determines in S1206 that the planning data for recovery has been received from the mobile terminal 700, the control unit 10 advances the process to S506.
On the other hand, if the control unit 10 determines in S1206 that the recovery planning data has not been received from the mobile terminal 700, the control unit 10 advances the process to S1209.

In S1209, the control unit 10 prompts the user to rearrange the planning data used to recover the XML file by displaying a screen such as that shown in FIG. 13 on the display unit 15. Specifically, the screen shown in FIG. 13 displays a message indicating that a recovery file is required, information indicating the location to which the planning data will be rearranged, and a message prompting the user to perform recovery work.

Next, with reference to FIG. 12B, an example of processing performed by the portable terminal 700 when the portable terminal 700 receives a transmission request for planning data from the imaging device 100 will be described.
In S1211, the control unit 71 waits for a transmission request for planning data from the imaging device 100. Then, when the control unit 71 determines that a transmission request for planning data has been received from the imaging device 100 via the wireless communication unit 74, it loads the planning data location information transmitted together in the RAM 76, and proceeds to the process of S1212. At this time, if the planning data location information has not been transmitted, the control unit 71 may determine that the transmission request for the corresponding planning data is invalid.

In S1212, the control unit 71 determines whether or not the planning data is held in the location indicated by the planning data location information (directory name and file name) expanded in the RAM 76.
If the control unit 71 determines that the planning data is stored in the location indicated by the planning data location information, the control unit 71 advances the process to S1213.
On the other hand, if the control unit 71 determines that the planning data is not stored in the location indicated by the planning data location information, the control unit 71 advances the process to S1214.

In S1213, the control unit 71 transmits the planning data held in the location indicated by the planning data location information to the imaging device 100 via the wireless communication unit 14.
On the other hand, in S1214, the control unit 71 notifies the imaging device 100 via the wireless communication unit 14 of information indicating that the target planning data does not exist.

<Other embodiments>
Although the present invention has been described in detail above based on the preferred embodiments, the present invention is not limited to these specific embodiments, and various forms within the scope of the gist of the present invention are also included in the present invention. Parts of the above-described embodiments may be combined as appropriate.
The present invention also includes cases where a software program that realizes the functions of the above-described embodiments is supplied to a system or device having a computer capable of executing the program directly from a recording medium or via wired/wireless communication, and the program is executed.
Therefore, the program code itself that is supplied to and installed in a computer to realize the functional processing of the present invention also realizes the present invention. In other words, the computer program itself for realizing the functional processing of the present invention is also included in the present invention.
In this case, so long as the program has the functions of a program, the program may be in any form, such as object code, a program executed by an interpreter, or script data supplied to an OS.
The recording medium for supplying the program may be, for example, a hard disk, a magnetic recording medium such as a magnetic tape, an optical/magneto-optical storage medium, or a non-volatile semiconductor memory.
As a method for supplying the program, a method is also conceivable in which the computer program forming the present invention is stored in a server on a computer network, and a connected client computer downloads the computer program.

In addition, in each of the above-mentioned embodiments, the present invention has been described as being applied to a digital camera, but this does not necessarily limit the scope of application of the present invention. In other words, the present invention may be applied to any device equipped with an image sensor. In other words, the present invention is applicable to any device capable of capturing images, such as a mobile phone terminal, a portable image viewer, a television equipped with a camera, a digital photo frame, a music player, a game console, or an e-book reader. Furthermore, the invention relating to the configuration for playing video in each of the above-mentioned embodiments can also be applied to image processing devices that do not have the function of capturing images.

The disclosure of this embodiment also includes the following configurations, methods, and programs.
(Configuration 1) A video recording device comprising: an acquisition means for acquiring one first metadata from a plurality of first metadata; an extraction means for extracting information related to recorded contents from a video; a first generation means for generating second metadata from the first metadata acquired by the acquisition means and the information related to the recorded contents extracted by the extraction means; a first recording means for recording the video and the second metadata in association with each other; and a second recording means for recording location information indicating a location where the first metadata used to generate the second metadata was stored in association with the video with which the second metadata is associated, wherein when the second metadata associated with the video is lost, the first generation means reads out the first metadata based on the location information, and generates the second metadata from the first metadata and the information related to the recorded contents extracted by the extraction means.
(Configuration 2) The moving image recording device according to configuration 1, wherein the second recording means records the location information in an additional information area of the moving image.
(Configuration 3) The moving image recording device described in Configuration 1, further comprising a second generating means for generating additional data to be added to the moving image, and the second recording means for recording the location information in the additional data generated by the second generating means.
(Configuration 4) The video recording device described in any one of configurations 1 to 3, characterized in that the acquisition means acquires from the external device one first metadata among the multiple first metadata stored in the external device and location information indicating a location where the first metadata is stored in the external device, and the second recording means records the location information acquired from the external device by the acquisition means.
(Configuration 5) A video recording device as described in any one of configurations 1 to 4, further comprising a first receiving means for receiving an instruction to generate the second metadata, wherein the first generating means generates the second metadata when the first receiving means receives the instruction.
(Configuration 6) The moving image recording device described in Configuration 5, further comprising a playback means for playing back the moving image, wherein the first generation means generates the second metadata for the moving image that is to be played back by the playback means when the first reception means receives the instruction.
(Configuration 7) A video recording device as described in any one of configurations 1 to 6, further comprising a second receiving means for receiving designation of first metadata to be applied when the first metadata is not stored in the location indicated by the location information, and the first generation means, when the second receiving means receives designation of first metadata, generates second metadata from the first metadata and information relating to the recorded content extracted by the extraction means.
(Configuration 8) A moving image recording device as described in any one of configurations 1 to 7, characterized in that the second recording means records the location information indicating the location where the first metadata used to generate the second metadata associated with the moving image is stored when recording of the moving image is started.
(Method 1) A control method for a video recording device, comprising: an acquisition step of acquiring one first metadata from a plurality of first metadata; an extraction step of extracting information related to the recorded contents from a video; a first generation step of generating second metadata from the first metadata acquired in the acquisition step and the information related to the recorded contents extracted in the extraction step; a first recording step of recording the video and the second metadata in association with each other; and a second recording step of recording location information indicating a location where the first metadata used to generate the second metadata was stored in association with the video with which the second metadata is associated, wherein the first generation step reads out the first metadata based on the location information when the second metadata associated with the video is lost, and generates the second metadata from the first metadata and the information related to the recorded contents extracted in the extraction step.
(Program 1) A program for causing a computer to function as a video recording device comprising: an acquisition means for acquiring one first metadata from a plurality of first metadata; an extraction means for extracting information related to the recorded contents from a video; a first generation means for generating second metadata from the first metadata acquired by the acquisition means and the information related to the recorded contents extracted by the extraction means; a first recording means for recording the video and the second metadata in association with each other; and a second recording means for recording location information indicating a location where the first metadata used to generate the second metadata was stored in association with the video with which the second metadata is associated, wherein the first generation means reads out the first metadata based on the location information when the second metadata associated with the video is lost, and generates the second metadata from the first metadata and the information related to the recorded contents extracted by the extraction means.

100 Imaging device 10 Control unit

Claims (10)

An acquisition means for acquiring one piece of first metadata from among the plurality of first metadata;
An extraction means for extracting information relating to the recorded contents from the moving image;
a first generating means for generating second metadata from the first metadata acquired by the acquiring means and information related to the recording content extracted by the extracting means;
a first recording means for recording the video and the second metadata in association with each other;
a second recording means for recording location information indicating a location where the first metadata used to generate the second metadata is stored, in association with the video image with which the second metadata is associated;
having
said first generating means, when the second metadata associated with the video is lost, reads out the first metadata based on the location information, and generates second metadata from the first metadata and information relating to the recorded content extracted by said extracting means. The video recording device according to claim 1, characterized in that the second recording means records the location information in an additional information area of the video. a second generating means for generating additional data to be added to the moving image;
The video image recording device according to claim 1 , wherein the second recording means records the location information in the additional data generated by the second generating means. the acquiring means acquires, from the external device, one first metadata among the plurality of first metadata stored in the external device, and location information indicating a location where the first metadata is stored in the external device;
2. The video recording device according to claim 1, wherein the second recording means records the location information acquired from the external device by the acquisition means. a first reception means for receiving an instruction to generate the second metadata,
The video recording device according to claim 1 , wherein the first generating means generates the second metadata when the first accepting means accepts the instruction. a playback means for playing back the moving image,
6. The video recording device according to claim 5, wherein the first generating means generates the second metadata for the video being played back by the playback means when the first receiving means receives the instruction. a second receiving means for receiving designation of the first metadata to be applied when the first metadata is not stored in the location indicated by the location information;
2. The video recording device according to claim 1, wherein when the second receiving means receives a designation of first metadata, the first generating means generates second metadata from the first metadata and information relating to the recording content extracted by the extracting means. The video recording device according to claim 1, characterized in that the second recording means records the location information indicating the location where the first metadata used to generate the second metadata associated with the video is stored when video recording is started. A method for controlling a moving image recording device, comprising:
An acquisition step of acquiring one piece of first metadata from the plurality of first metadata;
An extraction step of extracting information related to the recorded content from the moving image;
a first generation step of generating second metadata from the first metadata acquired in the acquisition step and information related to the recording content extracted in the extraction step;
a first recording step of recording the video and the second metadata in association with each other;
a second recording step of recording location information indicating a location where the first metadata used to generate the second metadata is stored, in association with the video associated with the second metadata;
having
a first generation step of reading the first metadata based on the location information when the second metadata associated with the video is lost, and generating second metadata from the first metadata and information related to the recorded content extracted in the extraction step. Computer,
An acquisition means for acquiring one piece of first metadata from among the plurality of first metadata;
An extraction means for extracting information relating to the recorded contents from the moving image;
a first generating means for generating second metadata from the first metadata acquired by the acquiring means and information related to the recording content extracted by the extracting means;
a first recording means for recording the video and the second metadata in association with each other;
a second recording means for recording location information indicating a location where the first metadata used to generate the second metadata is stored, in association with the video image with which the second metadata is associated;
having
The first generating means, when the second metadata associated with the video is lost, reads the first metadata based on the location information, and generates second metadata from the first metadata and information related to the recorded content extracted by the extracting means.

Images