JP2010154116A - Information recorder, information recording method, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To reduce loads and costs accompanying input work by applying one file metadata to another file with respect to a file recorded to a plurality of different devices. <P>SOLUTION: An information recorder for recording additional information accompanying a file in recording the file has: an acquisition means for acquiring prescribed information from the additional information in the file; a comparison means for comparing first information acquired from a first file by the acquisition means with second information acquired from a second file; and a recording means for recording the additional information in the first file as additional information in the second file when the first information and the second information are in a prescribed relationship as a result of comparison by the comparison means. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to an information recording technique for recording additional information accompanying a file.

  In recent years, video-based recording media using a hard disk or a flash memory have become mainstream from conventional magnetic tapes. As a result, since video data can be handled as a file, it is possible to archive the file in a large-scale storage such as a file server, or to retrieve and retrieve it when necessary. In order to search for a necessary file from a large number of archived files, a search key is required. Therefore, it is common to record the content such as video files with metadata describing information unique to the content. Examples of the metadata include a title, a shooting location, shooting contents, and performers (see, for example, Patent Document 1).

  Also, MXF (Material eXchange Format) standardized by SMPTE (Society of Motion Picture & Television Engineers) is widely used as a file format for broadcast video and the like. The MXF standard is composed of a plurality of standard groups, such as a format for making video data and audio data into a file, and a definition of metadata. As a standard of metadata, DMS-1 (Descriptive Metadata Scheme-1) is standardized.

In DMS-1, a property that represents a metadata item, a set in which related metadata items are grouped (a set may include other metadata sets as a metadata item), and the range of influence of the set and property A framework is defined. For example, a video title can be recorded as a Main Title property of a Title set defined by a Clip Framework related to the entire file. By sharing the format of the video file including metadata in this way, video files and metadata shot with different shooting devices can be handled in common with other devices.
JP 2004-31264 A

  As described above, even when the format of a video file including metadata is made common, the metadata itself needs to be added for each device. For example, when shooting the same event with multiple video cameras, the shooting location and event contents are the same for each video camera. However, to record this information as metadata, you must input for each video camera. is necessary. For this reason, the input operation becomes complicated, and preparing a metadata input terminal or operator for each video camera causes an increase in cost.

  In order to solve the above problems, an information recording apparatus of the present invention is an information recording apparatus that records additional information accompanying a file when the file is recorded, and acquires predetermined information from the additional information of the file. Obtaining means, comparing means for comparing the first information obtained from the first file by the obtaining means with the second information obtained from the second file, and as a result of the comparison by the comparing means, And recording means for recording additional information of the first file as additional information of the second file when the first information and the second information satisfy a predetermined relationship.

  The information recording method of the present invention is an information recording method for recording additional information associated with the file when the file is recorded, the obtaining step of acquiring predetermined information from the additional information of the file, A comparison step of comparing the first information acquired from the first file by the acquisition step with the second information acquired from the second file; and, as a result of the comparison by the comparison step, the first information and the first information A recording step of recording additional information of the first file as additional information of the second file when the second information satisfies a predetermined relationship.

  According to the present invention, for files recorded on a plurality of different devices, the metadata of one file can be applied to other files, and the load and cost increase associated with input work can be reduced. .

  The best mode for carrying out the present invention will be described below in detail with reference to the accompanying drawings. The embodiment described below is an example for realizing the present invention, and should be appropriately modified or changed according to the configuration and various conditions of the apparatus to which the present invention is applied. It is not limited to the embodiment.

[Embodiment 1]
In the present embodiment, a case will be described in which processing is performed on video files shot by two video cameras. In this embodiment, an MXF file is created and recorded at the time of shooting.

  FIG. 1 is a block diagram showing a schematic configuration of a video camera according to Embodiment 1 to which the information recording apparatus of the present invention is applied. In FIG. 1, reference numeral 101 denotes a control unit for controlling the entire video camera (hereinafter, camera). Reference numeral 102 denotes a setting storage unit for storing various setting information set by the user. An imaging unit 103 includes a lens, a CMOS sensor, and the like for capturing a still image or a moving image of the subject. An image encoding unit 104 compresses and encodes video data output from the imaging unit 103 for each frame. Reference numeral 105 denotes a microphone for detecting sound. An audio encoding unit 106 digitally encodes an audio signal output from the microphone 105.

  Reference numeral 107 denotes a multiplexing unit that creates a video file in which video data, audio data, and additional data output from the image encoding unit 104 and the audio encoding unit 106 are multiplexed. Reference numeral 108 denotes a recording medium for recording multiplexed file data. In the recording medium 108, a management file for managing files recorded on the recording medium 108 and information related to the recording medium 108 is also recorded. In the present embodiment, an SD (registered trademark) memory card or a CF (registered trademark) memory card that can be attached to and detached from the camera is applicable as the recording medium 108, but is not limited thereto.

  Reference numeral 109 denotes a metadata buffer for temporarily storing metadata as additional information attached to a file recorded on the recording medium 108. Reference numeral 110 denotes a GPS (Global Positioning System) for acquiring camera position information. Reference numeral 111 denotes a wireless LAN for communicating with an external device such as a PC. In the present embodiment, the control unit 101 has an HTTP server function, and an external device such as another camera can access the HTTP server via the wireless LAN 111 and perform camera settings and metadata input.

  Next, metadata input processing and various information setting processing for the video camera will be described with reference to FIG. In FIG. 2, when the user activates the camera in the shooting mode, the control unit 101 activates the HTTP server function in S201. In S202, the control unit 101 determines whether recording is in progress. If the recording is not in progress, the process proceeds to S203, and it is determined whether or not a recording start request is received from the user by a recording start button or the like. When there is a recording start request, the image encoding unit 104, the audio encoding unit 106, the multiplexing unit 107, and the metadata buffer 109 are initialized in S204, and a new file is created on the recording medium 108. Further, the position information is acquired from the GPS 110 in the recording medium 108, and metadata common to the position information and a recording file stored in the setting storage unit 102 described later is recorded. The camera also has a clock function (not shown), and records the recording start time as metadata added to a file. After recording the metadata, recording of video data and audio data is started.

  On the other hand, if there is no recording start request in S203, the process proceeds to S205, in which it is determined whether an HTTP request has been received from an external device via the wireless LAN 111. If an HTTP request has not been received, the process returns to S202. If an HTTP request is received, the process advances to step S206 to determine whether the received HTTP request is a setting page transmission request. If it is a request for transmission of a setting page, the process proceeds to S209, where data of the setting page for setting the camera is transmitted to the external device via the wireless LAN 111, and the process returns to S202. The contents of this setting page will be described later.

  If the HTTP request received in S206 is not a setting page transmission request, it is determined in S207 whether the HTTP request is a setting request using a setting input form. If it is a setting request, the process proceeds to S208, where setting data is detected from the setting input form and stored in the setting storage unit 102, and the setting is recorded in the management file of the recording medium 108. After the setting is saved in S208, the setting page data reflecting the setting content is transmitted to the external device via the wireless LAN 111 in S209, and the process returns to S202. If it is not a setting input request in S207, data indicating an error page is transmitted in S210, and the process returns to S202.

  FIG. 3 illustrates a setting page for setting the metadata transmitted in step S209. In FIG. 3, the setting page is divided into a part 31 for setting metadata common to all shooting files and a part 32 for setting individual metadata different for each shooting file. Reference numeral 311 denotes a text box for setting the title of the shooting file. Reference numeral 312 denotes a text box for setting the name of the photographer. Reference numeral 321 denotes a check box for setting whether to use metadata recorded by the camera as master data. Reference numerals 322, 324, 326, and 328 are check boxes for setting whether or not to input a shooting location, shooting content, performer, and event memo to the shooting file. 323, 325, 327, and 329 apply the individual metadata of input shooting location, shooting content, performers, and event memo only to files shot with this camera, or apply to files shot with other devices It is a check box for setting whether to do.

  The shooting location, shooting content, and performer items are items that can only be entered for one shooting file at a maximum. Each event memo can contain multiple data for one shooting file. This item can be set together with information. Reference numeral 33 denotes a button for reflecting the input setting on the camera. If the above items have not been set, data in which all items are blank or not selected is transmitted as shown in FIG. 3, and if there are items that have been set, each item has already been set. Data with the contents set is transmitted. An external device that has accessed the HTTP server of the camera and received the setting page data can input the setting data by a user operation after displaying the setting page.

  FIG. 4 illustrates a state where metadata is input to the setting page of FIG. In FIG. 4, each piece of information regarding the title and the photographer is set in the common metadata column. In the individual metadata column, the metadata set by the camera is set to be used as master data. Also, the shooting location, shooting content, and event memo are input to the shooting file. Furthermore, the setting is such that the metadata of the shooting location and the event memo is also applied in common to files shot by other cameras. After entering the settings as shown in the figure, when the user clicks the setting button 33, the entered form data is transmitted to another camera. The camera that has received the form data analyzes the form data and stores the setting contents in the setting storage unit 102. The management file of the recording medium 108 records information indicating whether or not to use as master data and information indicating the metadata item of the sharing setting.

  FIG. 5 illustrates information recorded in the management file. In FIG. 5, the first line is information indicating that it is used as master data. Whether the second to fifth lines apply the shooting location, shooting details, performers, and event memo metadata items only to files shot with this camera or to files shot with other cameras. It is information which shows. The item set as “COMMON” is also an item applied to a file shot by another camera.

  Next, the video camera recording process will be described with reference to FIG. In FIG. 2, when the recording process is started in S204, it is determined that the recording is being performed in S202, and the process proceeds to S211. In S211, it is determined whether or not a recording stop request has been made. If there is a recording stop request, the process proceeds to S212, the recording of video / audio on the recording medium 108 is terminated, the metadata stored in the metadata buffer 109 is added to the file, and the recording process is terminated.

  If there is no recording stop request in S211, it is determined in S213 whether an HTTP request is received from an external device via the wireless LAN 111. If an HTTP request has not been received, the process returns to S202. If an HTTP request has been received, it is determined whether or not the HTTP request received in S214 is a transmission request for a metadata input page. If the transmission request is for the metadata input page, the metadata input page data is transmitted to the external device via the wireless LAN 111 in S217, and the process returns to S202. The contents of this metadata input page will be described later.

  If the HTTP request received in S214 is not a request for transmitting a metadata input page, it is determined in S215 whether or not the HTTP request is a metadata input using a metadata input form. If the input is metadata, the metadata is detected from the input form data in S216 and stored in the metadata buffer 109. At this time, if the input metadata item is an event memo, the position information (frame number of the recorded video) of the file being recorded at the time when the metadata is detected is stored together with the event memo metadata. After storing the metadata in S216, the metadata input page data is transmitted to the external device via the wireless LAN 111 in S217, and the process returns to S202. If it is not metadata input in S215, data indicating an error page is transmitted in S210, and the process returns to S202.

  FIG. 6 illustrates the metadata input page transmitted in S214 when the metadata setting shown in FIG. 4 is performed. In FIG. 4, since three items of shooting location, shooting content, and event memo are selected as individual metadata, page data for inputting the three items is created and transmitted in S214. In FIG. 6, reference numerals 601, 603, and 605 denote text boxes for inputting shooting location, shooting content, and event memo data, respectively. Reference numerals 602, 604, and 606 denote buttons for causing the camera to store the shooting location, shooting contents, and event memo contents input in the text boxes 601, 603, and 605. When two items of the shooting location and the shooting content are not input to the file currently being recorded, data is transmitted with the text box of each item blank as shown in FIG. If there is an input item, the data is transmitted in a state where the input content is set in each item. When accessing the HTTP server of the camera during recording, the accessing external device receives and displays the data of the input page, and the user inputs metadata for the displayed page. To send to the camera.

  Below, the case where the play situation of a specific player is image | photographed on a soccer field is demonstrated. 7 to 9 illustrate the state in which metadata is input to a file being recorded. When the user inputs the shooting location metadata into the text box 601 and clicks the setting button 602 as shown in FIG. 7, the form data of the shooting location metadata is transmitted to the camera. The camera detects the metadata form data in S215 of FIG. 2, and stores the shooting location metadata in the metadata buffer 109 in S216. In S217, metadata input page data in which the metadata of the stored shooting location is set in the text box 601 is generated and transmitted to the external device.

  Next, as shown in FIG. 8, when the user inputs the metadata of the shooting content into the text box 603 and clicks the setting button 604, the form data of the metadata of the shooting content is transmitted to the camera. The camera detects the metadata form data in S215 of FIG. 2, and stores the metadata of the captured content in the metadata buffer 109 in S216. In S217, metadata of the metadata input page in which the metadata of the saved shooting location and shooting content is set in the text boxes 601 and 603 is generated and transmitted to the external device.

  Next, when an event that a goal has been determined during recording occurs, the user inputs the event memo metadata shown in FIG. 9 into the text box 605 and clicks the setting button 606 to form the event memo metadata form data. Is sent to the video camera. The camera detects the metadata form data in S215 of FIG. 2, and stores the event memo metadata in the metadata buffer 109 in S216. When the event memo is stored, the position information (frame number of the recorded video) of the file being recorded at the time when the metadata is detected is stored together with the event memo metadata.

  If another event occurs during recording after the event memo is input, the metadata is stored in the metadata buffer 109 by inputting the metadata in the same manner. After that, when the user stops recording, the metadata stored in the metadata buffer 109 is added to the recording file and recorded in S212 of FIG. Position information from GPS recorded at the start of recording, title and photographer metadata, and shooting location, shooting content, and event memo metadata input during recording are MXS file description metadata standards DMS Recorded according to -1.

  Table 1 illustrates the correspondence between each metadata item and the item of DMS-1. Each DMS-1 item in Table 1 is shown in the format of (framework) / (set) / (property). The metadata of “GPS location information” is recorded as the Geometric Coordinate property of the Address set defined by the Location set defined by the Clip Framework related to the entire file.

  The metadata of “cameraman” is recorded using a plurality of properties, and the content “Shooter” is recorded in the Job Function property of the Participant set of Clip Framework. The name of the photographer is recorded in the Family Name and First Given Name properties of the Person set of the Participant set of the Clip Framework. In the metadata of “event memo”, the position on the file where the event has occurred is recorded in the Keypoint Position property of the Keypoint set of the Shot set of the Clip Framework. Also, the event content is recorded in the Keypoint Value property of the Keypoint set of the Shot set of the Clip Framework.

  Next, setting of metadata related to shooting with the first video camera and the second video camera will be described. The configuration and flow of the first and second video cameras are the same as those in FIGS. FIG. 10 is an example of metadata setting input to the second video camera in S207 of FIG. In FIG. 10, each piece of information regarding the title and the photographer is set in the common metadata column. In the individual metadata column, the metadata set by this camera is not used as master data, and any metadata item is not set by the second video camera. For this reason, only the positional information from GPS, the title, and the metadata of the cameraman are added and recorded in the recording file shot by the second video camera.

  FIG. 11 shows an example of settings related to metadata recorded in the management file of the second camera. In FIG. 11, the first line is information indicating that it is not used as master data. In the second to fifth lines, whether the shooting location, shooting contents, performers, and event memo items are applied only to files shot with this camera, or to files shot with other cameras It is information which shows. “PRIVATE” is set for all, and it is set as an item that does not apply to files shot with other cameras.

  Through the processing described above, metadata including individual metadata is added and recorded in the recording file shot by the first video camera. In addition, only the position information and the title metadata, which is common metadata, and the cameraman metadata are added and recorded in the recording file shot by the second video camera.

  Next, a process for applying the individual metadata recorded in the recording file photographed by the first camera to the recording file photographed by the second camera will be described. FIG. 12 exemplifies files taken by the first and second cameras, respectively. In this embodiment, the first and second cameras shoot at different locations in the same soccer field, and the second video camera moves to another location on the way and has completely different contents from the first video camera. A case of shooting will be described.

  In FIG. 12, reference numeral 1210 denotes a first file photographed by the first camera, and reference numeral 1220 denotes a second file photographed by the second camera. Two files 1211 and 1212 are stored in the first video camera. The second video camera stores three files 1221, 1222, and 1223, and metadata shown in each file is recorded during recording.

  The arrow t in the center of FIG. 12 represents the passage of time. For example, metadata of “title” and “cameraman” set on the metadata setting page of FIG. 4 is recorded in the file 1211 photographed by the first video camera. The file 1211 records metadata of “shooting location” and “shooting content” input using the metadata input page of FIGS. 7 and 8. Further, metadata of “event memo” input through the metadata input page of FIG. 9 is recorded as event metadata at the video frame position t11 of the file 1211.

  In the files 1221 and 1222 photographed by the second camera, only the metadata of “title” and “cameraman” set using the metadata setting page of FIG. 10 is recorded. The file 1223 is a file that is taken after the file 1222 is photographed and moved to another location, and is recorded with the title setting changed.

  FIG. 30 is a block diagram illustrating a configuration of the recording apparatus 3000 according to the present embodiment.

  As described above, two memory cards M1 and M2 on which data captured by two cameras are recorded are mounted on the recording device 3000. The recording device 3000 processes image files and metadata recorded on these memory cards as follows.

  In FIG. 30, the first recording / reproducing unit 3001 and the second recording / reproducing unit 3002 respectively perform various operations such as image files and metadata files on the mounted memory cards M1, M2 in accordance with instructions from the control unit 3004. Record and play back data. The first recording / reproducing unit 3001 and the second recording / reproducing unit 3002 each include a mechanism such as a card slot in which the memory cards M1 and M2 can be freely inserted and ejected, a connection terminal, and the like.

  The signal processing unit 3003 processes moving image data and still image data included in image files reproduced from the memory cards M1 and M2. Specifically, processing such as decoding the image data reproduced from the memory card and displaying it on the display unit 3007 is executed.

  The control unit 3004 controls the operation of the recording device 3000 according to instructions from the operation unit 3005. Further, the control unit 3004 performs control when copying metadata between the memory cards M1 and M2, as will be described later.

  The operation unit 3005 includes various operation switches for inputting an operation by the user. The memory 3006 temporarily stores metadata read from the memory cards M1 and M2, as will be described later. The display unit 3007 displays moving images, still images, metadata, and the like recorded on the memory cards M1 and M2, and displays various types of information as necessary.

  Each block in FIG. 30 exchanges data through the bus 3008.

  FIG. 13 is a flowchart showing a process for applying individual metadata recorded in a recording file photographed by the first camera to a recording file photographed by the second camera. In FIG. 13, the first file photographed by the first camera is stored on the first memory card (first recording medium), and the second file photographed by the second camera is stored on the second memory card. It is assumed that each is recorded on (second recording medium). This flow is executed by the control unit 3004 of the recording apparatus 3000 shown in FIG. The recording device may be a PC or a video camera having a plurality of card slots.

  In FIG. 13, in S1301 and S1302, the first recording / reproducing unit 3001 and the second recording / reproducing unit 3002 store the second memory card that is the recording destination of the individual metadata and the first recording source of the individual metadata. Detects whether a memory card is inserted. If a memory card is detected from the card slot status, read the memory card management file and check the settings. When the metadata recording destination and the recording source memory card are detected, the management file of the first memory card is read in S1303, and it is detected whether or not the setting of each individual metadata item is the sharing setting. In the management file recorded on the first memory card, two items of shooting location and event memo are recorded as shared settings as described in FIG.

  Next, in S1304, it is determined whether or not the processing has been completed for all of the recording files (hereinafter referred to as master files) that are recorded in the first memory card and that are metadata recording sources. If the processing for all master files has been completed, this processing ends. If there is an unprocessed master file, the next unprocessed master file is read in S1305, and shooting time information and position information (first information) recorded in the master file are acquired in S1306 and S1307.

  In the process for the first master file, the file 1211 in FIG. 12 is read as a master file, and the recording start time and the file length (number of video frames) are acquired as shooting time information, and the position information is acquired from the GPS. In S1308, based on the sharing setting information read in S1303, the shared file metadata related to the entire file recorded in the master file is read. In the case of the file 1211, the shooting location data is read as shared file metadata.

  In S1309, it is determined whether or not the processing has been completed for all the recording files (hereinafter referred to as target files) that are recorded in the second memory card and that are metadata recording destinations. If all of the target files have been processed, the process returns to S1304 to process the next unprocessed master file on the first memory card. If an unprocessed target file exists, the next unprocessed target file is read in S1310.

  In step S1311, position information (second information) recorded in the target file is acquired. In the process for the first target file, the file 1221 in FIG. 12 is read as the target file, and position information is acquired. In S1312, the master file position information acquired in S1307 and the target file position information acquired in S1311 are compared to determine whether a predetermined relationship is satisfied. Specifically, it is determined whether or not the shooting location of the target file is within a predetermined range with respect to the shooting location of the master file. This determination can be made based on whether or not the distance between the two points indicated by the position information of the master file and the target file is equal to or less than a certain distance. The distance between the two points can be obtained by the “Hyubeni distance calculation formula” shown in the following formula 1 using the respective latitude / longitude information.

  If the determination result of S1312 is not within the predetermined range, it is considered that the shooting contents of the master file and the target file have little or no commonality. Therefore, the shared metadata is not applied to the target file, and the process returns to S1309 to process the next unprocessed target file. If the determination result in S1312 is within the predetermined range, shooting time information (second information) recorded in the target file is acquired in S1313. Recording start time and file length (number of video frames) are acquired as shooting time information. In S1314, the shooting time information of the master file acquired in S1306 and the shooting time information of the target file acquired in S1313 are compared to determine whether a predetermined relationship is satisfied. Specifically, it is determined whether or not the shooting time of the target file is within a predetermined time from the shooting time of the master file.

  Formula 2 above illustrates a determination formula for determining whether or not the time is within a predetermined time.

  In this example, the recording start time (S1) of the master file, the recording end time (E1) of the master file, the recording start time (S2) of the target file, the recording end time (E2) of the target file, and a predetermined time (Δt). Use. That is, the determination is made based on whether or not any of (a), (b), and (c) of Equation 2 is satisfied using S1, S2, E1, and E2. Note that the recording end time (E1) of the master file is calculated from the recording start time (S1) of the master file and the length of the master file. The recording end time (E2) of the target file is calculated from the recording start time (S2) of the target file and the length of the target file.

  FIG. 14 is a diagram for explaining the correspondence between the shooting times of the master file and the target file. In FIG. 14, the master file starts shooting at time S1, and ends shooting at time E1. Since the recording start times of the files of target 1, target 2, target 3, and target 4 are all included before the predetermined time Δt of S1 and after the predetermined time Δt of E1, they conform to equation (a). . Since the recording end time of each file of the target 5 and the target 6 is included between the predetermined time Δt before S1 and after the predetermined time Δt of E1, it conforms to Equation (b). Regarding the file of the target 7, since the recording start time of the master file is included between the recording start time and the recording end time of the target 7, it conforms to (c) of Equation 2. Regarding the target 8, none of the formulas 2 is applicable.

  The files of target 1 to target 7 conforming to Equation 2 are considered to be close in time to the shooting time of the master file and have high commonality of shooting contents, and target 8 is far from the shooting time of the master file in time. The commonality of shooting contents is considered low. Therefore, in S1314, it is possible to determine whether or not the shooting content of the target file being processed is highly common with the shooting content of the master file using Equation 2.

  If it is determined in S1314 that it is not within the predetermined time, it is considered that the shooting contents of the master file and the target file have little or no commonality. Therefore, the shared metadata is not applied to the target file, and the process returns to S1309 to process the next unprocessed target file. If the determination result in S1314 is within the predetermined time, it is determined in S1315 whether or not the metadata items related to the entire file read from the master file are recorded in the target file. In this embodiment, the metadata item is the shooting location metadata. If the shooting location metadata has already been recorded in the target file, the process advances to step S1317 without overwriting. If the metadata is not recorded, the shooting location metadata, which is the shared file metadata read from the master file, is recorded in the target file.

  Next, in S1317, it is determined whether or not the processing has been completed for all of the shared event metadata recorded in the master file. If all shared event metadata has been processed, the process returns to S1309 to process the next unprocessed target file on the second memory card. If unprocessed shared event metadata exists, in S1318, the next unprocessed shared event metadata and location information on the file where the event occurred are read.

  In step S1319, the time when the event occurred is calculated from the recording start time of the master file and the position information on the read shared event metadata file, and it is determined whether the event occurrence time is included in the shooting time of the target file. To do. If it is not within the shooting time, the process returns to S1317 to process the next unprocessed event metadata. If it is within the shooting time, the frame number of the target file in which the event has occurred is calculated from the recording start time and event occurrence time of the target file, and event metadata is recorded in the target file together with the frame number. Return.

  FIG. 15 is an example in which shared metadata is applied from the master file of the first memory card of FIG. 12 to the target file of the second memory card according to the flow of FIG. In FIG. 15, first, the master file 1211 is read, and the processing of the target file 1221 is performed. Since the shooting position and shooting time of the target file 1221 are both close to the master file 1211, the shooting location that is shared file metadata is copied to the target file 1221.

  Next, since the file position t21 corresponding to the file position t11 of the master file 1211 exists in the target file 1221, the event memo associated with the file position t11 is copied to the target file 1221. Similarly, in the processing of the target file 1222, since the shooting position and shooting time are both close to the master file 1211, the shooting location that is shared file metadata is copied to the target file 1222. The event memo is not copied because the file position corresponding to t11 does not exist in the target file 1222. In the processing of the target file 1223, the second camera moves to a shooting location different from that of the first camera and the shooting position is outside the predetermined range, so that the metadata is not copied.

  Next, the master file 1212 is read, and the processing of the target file 1221 is performed again. Since the target file 1221 is far from the master file 1212, the metadata copy process is not performed. Next, processing of the target file 1222 is performed, and since the shooting position and shooting time are both close to the master file 1212, metadata copy processing is performed. However, since the shooting location metadata has already been copied from the master file 1211, the file metadata is not copied.

  Next, since the file position t22 corresponding to the file position t12 of the master file 1212 exists in the target file 1222, the event memo associated with the file position t12 is copied to the target file 1222. Since the file position corresponding to the file position t13 of the master file 1212 does not exist in the target file 1222, the event memo associated with the file position t13 is not copied. Finally, in the processing of the target file 1223, the second camera moves to a shooting location different from that of the first camera and the shooting position is out of the predetermined range, so that the metadata is not copied.

  Through the processing described above, it is possible to apply metadata for which sharing settings have been made to a highly relevant file for shooting.

[Embodiment 2]
In the following, as in the first embodiment, a case where processing is performed on files photographed by two cameras will be described. Each configuration of the video camera and the recording apparatus according to the second embodiment is the same as that shown in FIGS. FIG. 16 is a flowchart showing metadata input processing and various information setting processing for the video camera according to the second embodiment. The same processing as in FIG. 2 is denoted by the same reference numeral. The setting page data transmitted in S1602, the setting contents saved in S1601, the metadata input page data sent in S1604, and the metadata contents saved in S1603 are different from FIG. 2 of the first embodiment. ing.

  FIG. 17 shows an example of the setting page transmitted in S1602 of FIG. In FIG. 17, the metadata setting page is divided into a part 31 for setting metadata common to all shooting files and a part 1701 for setting individual metadata different for each shooting file, as in the first embodiment. ing. However, each item in the individual metadata column 1701 is page data that does not have a check box for performing sharing setting.

  FIG. 18 illustrates a state where metadata is input to the setting page of FIG. In FIG. 18, title and photographer information are set in the common metadata column. In the individual metadata column, metadata recorded by the camera is used as master data, and the shooting location, shooting content, and event memo are input to the shooting file. After the setting is input, when the user clicks the setting button 33, the input form data is transmitted to the camera. The camera that has received the form data in S1601 analyzes the form data and stores the setting contents in the setting storage unit 102. In addition, information on whether to use as master data is recorded in the management file of the recording medium 108.

  FIG. 19 shows a setting example regarding metadata recorded in the management file. In FIG. 19, information indicating use as master data is recorded in the management file, and information indicating whether each metadata item is also applied to a file shot by another camera is not recorded.

  FIG. 20 exemplifies the metadata input page transmitted in S1604 of FIG. 16, and the portions denoted by the same reference numerals as those in FIG. 6 are the same as the items described in the first embodiment, and thus the description thereof is omitted. In FIG. 20, reference numerals 2001 to 2003 denote check boxes for setting whether to apply the input metadata to a file shot by another camera. When metadata is input to each item 601, 603, 605 and the setting buttons 602, 604, 606 are clicked, a check box is checked to set whether to apply for each input metadata. be able to.

  21 to 23 are examples in which metadata is input to a file being recorded. In FIG. 21, the user inputs the metadata of the shooting location in the text box 601 and checks the check box 2001 to apply the metadata to a file shot by another camera shooting at the same soccer field. Click the setting button 602. Then, the form data of the shooting location metadata is transmitted to the camera, and the camera stores the shooting location metadata in the metadata buffer 109 together with the sharing setting information in S1603 of FIG.

  Next, as shown in FIG. 22, the user inputs the metadata of the shooting content into the text box 603, and since the shooting content is specific to the camera being shot, the user clicks the setting button 604 without checking the check box 2002. . Then, the form data of shooting content metadata is transmitted to the camera, and the camera stores the shooting content metadata in the metadata buffer 109 together with the sharing setting information in S1603 of FIG.

  Next, when an event occurs that the goal of the player to be imaged is determined during recording, the user inputs the contents of the event into a text box 605 as shown in FIG. Since the event content is unique to the camera being photographed, the setting button 606 is clicked without checking the check box 2003. Then, event memo metadata form data is transmitted to the camera, and the camera stores the event memo metadata in the metadata buffer 109 together with the shared setting information in S1603 of FIG.

  When the event memo metadata is saved, the position information (frame number of the recorded video) of the file being recorded at the time of the metadata detection is saved together with the event memo metadata. Thereafter, when the user stops the recording, the metadata stored in the metadata buffer 109 is added to the recording file and recorded in S212 of FIG. The recording process of each metadata is executed according to DMS-1 described in the first embodiment. The shared setting information of each metadata is also recorded at the same time. A 16-byte unique ID (UID) generated for each device is assigned to each metadata recorded in the DMS-1. A field related to sharing settings can be provided in the UID and recorded.

  Next, setting of metadata related to shooting with the first video camera and the second video camera will be described. The configuration and flow of the first and second video cameras are the same as those in FIGS. FIG. 24 is an example of metadata setting input to the second video camera in S207 of FIG. Title and photographer information are set in the common metadata column. The individual metadata column does not use the metadata recorded by this camera as master data, and does not set any metadata items on the second camera. For this reason, only the positional information from GPS, the title, and the metadata of the cameraman are recorded in the recording file photographed by the second video camera. FIG. 25 is a setting example related to metadata recorded in the management file of the second camera, and information indicating that it is not used as master data is recorded.

  Through the processing described above, metadata including individual metadata is recorded in the recording file captured by the first camera. Only the GPS position information, the title which is common metadata, and the cameraman's metadata are recorded in the recording file photographed by the second camera.

  Next, a process for applying the individual metadata recorded in the recording file photographed by the first camera to the recording file photographed by the second camera will be described. FIG. 26 exemplifies files photographed by the first and second cameras. Below, the case where it image | photographed in the different place in the same soccer field with the 1st and 2nd camera is demonstrated. In FIG. 26, 2610 is a file photographed by the first camera, and 2620 is a file photographed by the second camera. Two files 2611 and 2612 are recorded in the first camera. Three files 2621, 2622, and 2623 are recorded in the second camera. Each file stores the illustrated metadata at the time of shooting. [◯] and [×] attached to the left side of each metadata item indicate whether or not the recorded metadata is set to be shared.

  The arrow t described in the center of FIG. 26 represents the passage of time. For example, in the file 2611 photographed by the first camera, metadata of “title” and “cameraman” set using the metadata setting page of FIG. 18 is recorded. The file 2611 records metadata of “shooting location” and “shooting content” input using the metadata input pages of FIGS. 21 and 22. Further, the metadata of “event memo” input using the metadata input page of FIG. 23 is recorded as event metadata at the video frame position t11 of the file 2611. In the file 2612, metadata of “title” and “cameraman”, which are common metadata, and metadata of “shooting location” and “shooting content” recorded during shooting are recorded as metadata of the entire file. Yes.

  Further, metadata of “event memo” is recorded as event metadata at video frame positions t12 and t13 of the file 2612. The event metadata recorded in association with the file positions t11 and t13 is data recorded without checking the shared setting check box at the time of recording because it is unique to the shooting contents of the first camera. The event metadata recorded in association with the file position t12 is data that is recorded by checking the sharing setting check box at the time of recording because the event metadata is common to the contents captured by other cameras. Further, in the files 2621, 2622, and 2623 photographed by the second camera, only the metadata of “title” and “cameraman” set by using the metadata setting page of FIG. 24 is recorded.

  FIG. 27 is a flowchart showing a process for applying the individual metadata recorded in the recording file photographed by the first camera to the recording file photographed by the second camera. Are denoted by the same reference numerals and description thereof is omitted. This flow is executed by the control unit 3004 of the recording apparatus 3000 shown in FIG. The recording device may be a PC or a video camera having a plurality of card slots.

  The flow in FIG. 13 is that the sharing setting is not recorded in the management file, so that the sharing setting reading process in S1303 in FIG. 13 does not exist, the shared file metadata reading process in S2701 and the shared event metadata reading process in S2702 Is different.

  After obtaining the position information recorded in the master file in S1307, the file metadata recorded in the master file is searched in S2701. Then, the sharing setting information recorded in the metadata is determined, and the file metadata recorded in the sharing setting is read. In the case of the file 2611, shooting location data is read as shared file metadata. Thereafter, the processing described in the first embodiment is executed from S1309 to S1317. In S2702, the event metadata recorded in the master file is searched, the sharing setting information recorded in the metadata is determined, and the event metadata recorded in the sharing setting is read. The processing after S1319 is the same as the processing described in the first embodiment.

  FIG. 28 is an example in which shared metadata is applied from the master file of the first memory card of FIG. 26 to the target file of the second memory card according to the flowchart of FIG. In FIG. 28, the master file 2611 is first read and the target file 2621 is processed. Since the shooting position and shooting time of the target file 2621 are both close to the master file 2611, the shooting location as shared file metadata is copied to the target file 2621. Next, the event metadata of the master file 2611 is processed. However, the event metadata associated with the file position t11 is metadata unique to the shooting file of the first camera, and is not copied. Similarly, since the shooting position and shooting time of the target file 2622 are both close to the master file 2611, the shooting location that is the shared file metadata is copied to the target file, and the event memo associated with the file position t11 is not copied. In the processing of the target file 2623, the metadata is not copied because the shooting time is not within the predetermined time of the shooting time of the master file 2611.

  Next, the master file 2612 is read, and the target file 2621 is processed again. Since the shooting time of the target file 2621 is far from the master file 2612, the metadata copy process is not performed. Next, processing of the target file 2622 is performed, and since the shooting position and shooting time are both close to the master file 2612, the metadata is copied. However, since the shooting location metadata has already been copied from the master file 2611, the file metadata is not copied.

  Next, processing of event metadata recorded in association with the file position t12 of the master file 2612 recorded in the sharing setting is performed. Since the file position t22 corresponding to the file position t12 exists in the target file 2622, the event memo associated with the file position t12 is copied to the target file 2622. Since the event metadata associated with the file position t13 of the master file 2612 is metadata unique to the shooting file of the first camera, copying is not performed.

  Finally, in the processing of the target file 1223, since the shooting position and the shooting time are both close to the master file 2612, the metadata is copied and the metadata of the shooting location is copied. The event metadata recorded with the sharing setting of the master file 2612 is not copied because the file position corresponding to the file position t12 does not exist in the target file 2623.

  Through the processing described above, it is possible to apply metadata that has been individually set for sharing during recording to a highly relevant file.

[Embodiment 3]
Hereinafter, a case will be described in which files shot by two video cameras are copied to an archive system. The configuration and recording processing of the video camera of the third embodiment are the same as those described in FIGS. 1 to 11 of the first embodiment, and files having the contents shown in FIG. 12 are recorded in the respective cameras. The archive system functions as a file server. For example, in addition to the recording device 3000 in FIG. 30, a large-scale storage device is mounted, and the control unit 3004 manages the database and copies files to the storage device via the network. FIG. 29 is a flowchart showing a process of copying a file recorded by the camera to the archive system. This flow is executed by the control unit of the archive system.

  In FIG. 29, in S2901, it is detected whether or not a memory card in which a recording file is recorded is inserted into a card slot of the archive system. If the status of the card slot is determined and a memory card is detected, the management file on the memory card is read in S2902, and it is detected whether the individual metadata setting of each item is a shared setting.

  Next, in S2903, it is determined whether or not the processing has been completed for all the recording files recorded on the memory card. If the processing for all the recorded files has been completed, the processing ends. If there is an unprocessed recording file, the next unprocessed recording file is read in S2904, and the shooting time information and position information recorded in the recording file are acquired in S2905 and 2906. The recording start time and the file length (number of video frames) are acquired as shooting time information, and the position information is acquired from the GPS. In step S2907, file metadata and event metadata recorded in the recording file are read and stored in the processing buffer together with shooting time information and position information.

  Next, in S2908, the database of the recording file managed by the archive system is read, and it is searched whether there is metadata applicable to the recording file using the shooting time information and position information acquired in S2905 and 2906. To do. Table 2 exemplifies records registered in the database for one recording file. The path name of the recording file recorded in the archive system and the metadata described in the first embodiment are recorded as one record.

  In step S2909, the recording start time, file length, and position information are read from the records recorded in the database, and a record in which the shooting time information and position information acquired in steps S2905 and 2906 are within a predetermined time and within a predetermined range is searched. . When the corresponding record is detected, the file metadata set as sharing is read and added to the processing buffer holding the metadata of the recording file in S2910. In addition, the sharing setting and file position of the event memo in the record are also determined, and if the position information corresponding to the recording file exists, the event metadata set to the sharing setting is added to the processing buffer.

  In the present embodiment, the case has been described where the shooting time information and the position information are searched for within a predetermined time and within a predetermined range in S2908. However, if the shooting time information is within the predetermined time and the position information is not within the predetermined range, the metadata relating to the position information, that is, the metadata of the shooting location is not added to the processing buffer in S2910, and other It is also possible to add only the metadata.

  When the database search process is completed, the recorded file is copied to the storage device of the archive system in S2911. In S2912, the file path of the copy result and the metadata held in the processing buffer are registered in the database, and the process returns to S2903.

  When the recording file of the memory card 1210 in FIG. 12 is processed by the archive system, the files 1211 and 1212 are copied to the storage device of the archive system, and information and metadata of each file are registered in the management database. Next, when the memory card 1220 is processed, metadata is copied from the record information of the registered files 1211 and 1212, and the metadata shown in FIG. 15 is copied as metadata of the files 1221 and 1222 and registered in the database. The

  In the present embodiment, metadata is not recorded on the file itself captured by the second camera. However, the metadata of the file photographed by the first camera at the time of registration in the archive system can be registered in the database as the metadata of the file photographed by the second camera, and can be used for searching and the like. .

[Other Embodiments]
The object of the present invention can also be achieved by supplying a storage medium storing software program codes for realizing the functions of the above-described embodiments to a system or apparatus. That is, it goes without saying that this can also be achieved by the computer (CPU or MPU) of the system or apparatus reading and executing the program code stored in the storage medium. In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiments, and the storage medium storing the program code constitutes the present invention.

  As a storage medium for supplying the program code, for example, a flexible disk, hard disk, optical disk, magneto-optical disk, CD-ROM, CD-R, magnetic tape, nonvolatile semiconductor memory card, ROM, or the like can be used. . Further, the functions of the above-described embodiments may be realized by executing the program code read by the computer. However, an OS (operating system) running on the computer may perform part or all of the actual processing based on the instruction of the program code, and the functions of the above-described embodiments may be realized by the processing. Needless to say, it is included.

  Furthermore, the program code read from the storage medium may be written to a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer. Thereafter, the CPU of the function expansion board or function expansion unit performs part or all of the actual processing based on the instruction of the program code, and the function of the above-described embodiment is realized by the processing. Needless to say.

1 is a block diagram illustrating a schematic configuration of a video camera according to Embodiment 1. FIG. 4 is a flowchart illustrating metadata input processing and various information setting processing for the video camera according to the first exemplary embodiment. FIG. 6 is a diagram illustrating a display example of a page for setting metadata according to the first exemplary embodiment. FIG. 4 is a diagram illustrating an example of metadata setting of the first video camera according to the first embodiment. FIG. 4 is a diagram illustrating a management file of the first video camera according to the first embodiment. FIG. 5 is a diagram illustrating a display example of a page for inputting metadata according to the first exemplary embodiment. 6 is a diagram illustrating an input example of a page for inputting metadata according to the first exemplary embodiment. FIG. 6 is a diagram illustrating an input example of a page for inputting metadata according to the first exemplary embodiment. FIG. 6 is a diagram illustrating an input example of a page for inputting metadata according to the first exemplary embodiment. FIG. 6 is a diagram illustrating a metadata setting example of the second video camera according to the first embodiment. FIG. FIG. 6 is a diagram illustrating a management file of a second video camera according to the first embodiment. FIG. 3 is a diagram illustrating a file shot by the first and second video cameras of the first embodiment. 3 is a flowchart illustrating processing for applying metadata according to the first exemplary embodiment. It is a figure for demonstrating the time-sequential correspondence between imaging | photography files. 6 is a diagram illustrating an example in which metadata is applied to a shooting file of the second video camera according to the first embodiment. FIG. 10 is a flowchart illustrating metadata input processing and various information setting processing for the video camera according to the second exemplary embodiment. FIG. 10 is a diagram illustrating a display example of a page for setting metadata according to the second exemplary embodiment. 10 is a diagram illustrating an example of metadata setting of the first video camera according to the second embodiment. FIG. 6 is a diagram illustrating a management file of a first video camera according to Embodiment 2. FIG. FIG. 10 is a diagram illustrating a display example of a page for inputting metadata according to the second exemplary embodiment. It is a figure which shows the example of an input of the page which inputs the metadata of Embodiment 2. It is a figure which shows the example of an input of the page which inputs the metadata of Embodiment 2. It is a figure which shows the example of an input of the page which inputs the metadata of Embodiment 2. 10 is a diagram illustrating a metadata setting example of a second video camera according to Embodiment 2. FIG. FIG. 10 is a diagram illustrating a management file of a second video camera according to the second embodiment. FIG. 6 is a diagram illustrating a file shot with the first and second video cameras of the second embodiment. 10 is a flowchart illustrating processing for applying metadata according to the second exemplary embodiment. FIG. 10 is a diagram illustrating an example in which metadata is applied to a shooting file of a second video camera according to the second embodiment. 14 is a flowchart illustrating a recording file archiving process according to the third embodiment. It is a block diagram which shows the structure of the recording device in this embodiment.

Claims (12)

An information recording apparatus for recording additional information accompanying the file when recording the file,
Obtaining means for obtaining predetermined information from the file;
Comparing means for comparing the first information acquired from the first file by the acquiring means with the second information acquired from the second file;
Recording means for recording additional information of the first file as additional information of the second file when the first information and the second information satisfy a predetermined relationship as a result of the comparison by the comparing means And an information recording apparatus. The additional information includes information unique to each file and information common to the files,
The information recording apparatus according to claim 1, wherein the recording unit records only the additional information of the first file including the common information as the additional information of the second file. A setting unit for setting the additional information;
The information recording apparatus according to claim 2, wherein the setting unit can set whether the unique information is shared among a plurality of files. The predetermined information includes time information and position information when the file is recorded,
The acquisition means acquires at least one of time information and position information when a file is recorded as the predetermined information,
4. The method according to claim 1, wherein the comparison unit determines whether the time information is within a predetermined time and the position information is within a predetermined range as the predetermined relationship. 5. The information recording device described in 1.   5. The information recording apparatus according to claim 1, wherein the first file and the second file are recorded in different apparatuses.   The information recording apparatus according to any one of claims 1 to 4, wherein the first file and the second file are recorded on different recording media. A database in which additional information of the first file is registered;
When the second information acquired from the second file by the acquisition means and the first information acquired from the first file registered in the database satisfy the predetermined relationship, 5. The information recording apparatus according to claim 1, further comprising registration means for registering additional information of one file in the database as additional information of the second file. In the recording medium, information indicating whether or not the first file and the second file are recording sources of additional information is recorded,
The information recording apparatus according to claim 6, further comprising a determination unit that determines information indicating whether or not the recording source is the recording source. An image capturing means for capturing an image of the subject to generate a video file;
4. The information recording apparatus according to claim 3, wherein when recording the video file, the recording unit records additional information of the video file and information indicating whether to share the video file.   10. The information recording apparatus according to claim 9, wherein when recording the video file, the recording unit records information indicating whether or not the video file is used as a recording source of additional information. An information recording method for recording additional information accompanying the file when recording the file,
An acquisition step of acquiring predetermined information from the additional information of the file;
A comparison step of comparing the first information acquired from the first file by the acquisition step with the second information acquired from the second file;
A recording step of recording additional information of the first file as additional information of the second file when the first information and the second information satisfy a predetermined relationship as a result of the comparison in the comparison step And an information recording method.   A program for causing a computer of an information recording apparatus to execute the information recording method according to claim 11.

Images