Image file creation devices, image file creation methods, and storage media

Abstract

An image file creation device is used to create an image file according to a predetermined image file format comprising an image data region and a metadata region. The image data region is used to store images, and the metadata region is used to store metadata as information related to the images. The image file creation device is used to: determine multiple images to be displayed consecutively from the images stored in the image data region; and to create identification information for each of the multiple images and information in the image data region storing the positions of the images corresponding to the identification information, store the created information in the metadata region, and also store information for indicating the display order of the multiple images and information for indicating the display time of each of the multiple images in the metadata region.

Description

Technical Field

[0001] This invention relates to a technique for storing one or more image data in an image file. Background Technology

[0002] In MPEG (Moving Picture Experts Group), standardization was carried out for storing a single still image, multiple still images, or a sequence of images (a series of still images, etc.) in a single file. This standard is called HEIF (High Efficiency Image File Format) and allows for the replacement, editing, and display of images and image sequences. HEIF is a storage format extended from tools defined in ISO BMFF (ISO Basic Media File Format). HEIF has been standardized in ISO / IEC 23008-12 (Part 12) under the name "Image File Format." HEIF defines a model structure including metadata and defines methods for associating images with metadata, as well as the structure of metadata in a specific format. Patent Document 1 describes a technique for storing derived images in an HEIF-compliant image file.

[0003] On the other hand, in recent years, image generation devices with image generation capabilities, such as cameras or smartphones, have various functions. They can generate not only the shooting date / time, image size, and image quality, but also various information such as information about the time of shooting and metadata of the captured image data. For example, information used to identify the subject or scene at the time of shooting, as well as various shooting settings, are generated along with the image data. This information related to the image data can be stored as metadata along with the image data in the HEIF file. Applications also provide the function of automatically and sequentially switching between multiple images while displaying them. In many applications, this function is called a slideshow. In HEIF, it is also possible to create image files intended for display in a slideshow by storing multiple image data.

[0004] Existing technical documents

[0005] Patent documents

[0006] Patent Document 1: U.S. Patent Application Publication No. 2016-371265 Summary of the Invention

[0007] The problem the invention aims to solve

[0008] In the HEIF specification, when storing temporally consecutive still images (e.g., a series of photographs obtained through burst shooting), these images can be stored as an image sequence. Similar to moving images, in an HEIF file containing an image sequence, the temporally consecutive still images need to be defined as a video track within the HEIF file so that applications displaying the images can perform continuous display processing. Therefore, the creation of HEIF files that store settings for automatically displaying arbitrary images sequentially by assigning display times (time intervals) can be complex.

[0009] The present invention was made in view of the above-mentioned problems and provides a technique for efficiently performing the processing of storing information required for the sequential display of multiple images in an image file.

[0010] Solution for solving the problem

[0011] As a means to solve the above-mentioned problems, the image file creation apparatus according to the present invention has the following configuration. That is, an image file creation apparatus is provided for creating an image file according to a predetermined image file format comprising an image data region and a metadata region, wherein the image data region is used to store images, and the metadata region is used to store metadata as information related to the images. The image file creation apparatus includes: a determining unit for determining, from the images stored in the image data region, a plurality of images to be displayed consecutively; and a metadata processing unit for creating identification information for each of the plurality of images and information in the image data region storing the positions of images corresponding to the identification information, storing the created information in the metadata region, and also storing information for indicating the display order of the plurality of images and information for indicating the display time of each of the plurality of images in the metadata region.

[0012] The effects of the invention

[0013] It can efficiently store the information needed to display multiple images consecutively in an image file.

[0014] Other features and advantages of the invention will become apparent from the following description taken in conjunction with the accompanying drawings. Note that throughout the drawings, the same reference numerals denote the same or similar components. Attached Figure Description

[0015] The accompanying drawings, which are included in and form part of this specification, illustrate embodiments of the invention and, together with the specification, serve to explain the principles of the invention.

[0016] Figure 1This is a block diagram illustrating the configuration of the device used to create image files;

[0017] Figure 2 This is a flowchart of the image file creation and processing.

[0018] Figure 3 This is a flowchart of the metadata creation process for a slideshow based on the first embodiment;

[0019] Figure 4 This is a diagram illustrating an example of the data format for descriptive information of a derived image according to the first embodiment;

[0020] Figure 5 This is a diagram illustrating another example of the data format for descriptive information of a derived image according to the first embodiment;

[0021] Figure 6 This is a diagram illustrating the structure of the HEIF file created according to the first embodiment;

[0022] Figure 7 This is a diagram illustrating an example of the HEIF file output according to the first embodiment;

[0023] Figure 8 This is a flowchart of the metadata creation process for a slideshow according to the second embodiment;

[0024] Figure 9 This is a diagram illustrating an example of the data format for SlideshowEntityToGroupBox.

[0025] Figure 10 It is a graph showing the data format of ImageDurationProperty (image duration property);

[0026] Figure 11 It is a diagram illustrating the data format of ImageLocationProperty.

[0027] Figure 12 This is a diagram illustrating an example of the data format for TransitionEffectProperty.

[0028] Figure 13 This is a diagram showing the data format of SlideShowProperty.

[0029] Figure 14 This is a diagram illustrating the structure of the HEIF file created according to the second embodiment;

[0030] Figure 15This is a diagram illustrating an example of the HEIF file output according to the second embodiment;

[0031] Figure 16 This is a diagram showing the data format of a PrimaryItemBox that conforms to the HEIF standard;

[0032] Figure 17 This is a diagram illustrating an example of the data format for PrimaryItemBox;

[0033] Figure 18 This is another example of the data format for PrimaryItemBox;

[0034] Figure 19 This is a diagram illustrating an example of the HEIF file output according to the third embodiment;

[0035] Figure 20 This is a flowchart of the slideshow playback process for image files;

[0036] Figure 21 This is another example of the data format for SlideshowEntityToGroupBox;

[0037] Figure 22 This is a diagram illustrating an example of the data format for descriptive information of an ImageOverlay derived image;

[0038] Figure 23 This is a diagram showing the data format of SlideShowTimingProperty.

[0039] Figure 24 This is a diagram illustrating another example of the data format for TransitionEffectProperty;

[0040] Figure 25 This is a diagram illustrating the data format of ImageScalingProperty;

[0041] Figure 26 This is another example of the data format for ImageScalingProperty;

[0042] Figure 27 It is a diagram illustrating the data format of ImageSpatialExtentProperty;

[0043] Figure 28This is a diagram illustrating another example of the data format for TransitionEffectProperty;

[0044] Figure 29 This is a diagram illustrating an example of the data format for WipeTransitionEffectProperty.

[0045] Figure 30 This is a diagram illustrating an example of the data format for ZoomTransitionEffectProperty; and

[0046] Figure 31 This is a diagram illustrating an example of the data format for the FadeInTransitionEffectProperty. Detailed Implementation

[0047] The embodiments will now be described in detail with reference to the accompanying drawings. Note that the following embodiments are not intended to limit the scope of the claimed invention. Multiple features are described in the embodiments, but the invention is not limited to requiring all of these features, and multiple such features can be appropriately combined. Furthermore, in the drawings, the same reference numerals are given to the same or similar structures, and redundant descriptions thereof are omitted.

[0048] <First Embodiment>

[0049] [Hardware Configuration]

[0050] Figure 1 An example configuration of an image file creation device 100 is shown. In the image file creation device 100, a CPU 102, RAM 103 serving as temporary storage for executing system programs, and ROM 104 serving as non-volatile storage for storing the system program are connected to a system bus 101. The system program or application program is loaded from ROM 104 into RAM 103 and executed by the CPU 102. Furthermore, an encoding / decoding unit 105, a metadata processing unit 106, a display unit 107, a user interface unit 108, and a communication control unit 109 are connected to the system bus 101. The system bus 101 transfers data between these blocks. RAM 103 includes an output buffer and serves as a data buffer for image file creation processing or as an output destination for data stored in an image file.

[0051] The encoding / decoding unit 105 is a video codec conforming to H.265 (HEVC), H.264 (AVC), AV1, or JPEG, etc., for moving or still images, and performs encoding and decoding processing on the still or moving image data. The metadata processing unit 106 acquires the data (encoded data) encoded by the encoding / decoding unit 105 and generates an image file conforming to a predetermined file format (e.g., HEIF). More specifically, the metadata processing unit 106 performs analysis processing on the metadata stored in the still or moving image file to generate information related to the still or moving image and acquire parameter information related to the encoded data. Then, the metadata processing unit 106 performs processing to store this information as metadata along with the encoded data in the file. Furthermore, the metadata processing unit 106 performs metadata processing for the reproduction of still or moving images by analyzing the metadata stored in the file.

[0052] Display unit 107 is intended to be used for displaying a screen of the image file creation device 100 application, and is, for example, a liquid crystal display device. Display unit 107 may include a screen touch sensor to enable a user to operate the application via a GUI (Graphical User Interface). Display unit 107 can reproduce a file used to confirm the generated file. User interface unit 108 is an interface for accepting user operations (input) to the image file creation device 100, and is constituted, for example, a physical operation interface such as a button or switch.

[0053] The communication control unit 109 is a network interface used to send / receive transmission frames by establishing a connection to a network. The communication control unit 109, for example, is compatible with a wired LAN. The Ethernet PHY and MAC (Transmission Media Control Processing) correspond to each other. Optionally, if the image file creation device 100 can be connected to a wireless LAN, the communication control unit 109 includes a controller, RF circuitry, and an antenna for performing wireless LAN control compliant with IEEE 802.11a / b / g / n / ac / ax, etc.

[0054] [Image File Creation and Processing]

[0055] Next, refer to Figure 2 , Figure 6 and Figure 7 This will explain the image file creation process of the image file creation device 100. Figure 2 This is a flowchart of the image file creation process. More specifically, Figure 2 This illustrates the process for creating a file that stores one or more still images according to the HEIF file format. Figure 2The steps in the flowchart shown indicate the processing performed by one of the following: the software of CPU 102, the encoding / decoding unit 105, and the metadata processing unit 106. Note that in the following description, "CPU 102" refers to the software processing performed by CPU 102. Figure 6 The structure of an HEIF file 600, which is an example of an HEIF file created by the image file creation device 100 according to this embodiment, is shown. The HEIF file 600 includes a metadata storage area 602 (MetaBox)(meta) (metadata area) and an encoded data storage area 611 (MediaDataBox)(mdat) (image data area). Figure 7 This is a diagram illustrating an example of the HEIF file output according to this embodiment. Figure 7 Examples are shown of storing one or more still images and derived images that constitute a slideshow, according to the HEIF file format.

[0056] The image file creation process begins at step S201. In step S202, the CPU 102 retrieves (selects) the image data to be stored in the HEIF file from the image data stored in RAM 103 or ROM 104. This retrieval process can be based on information pre-set for the image file creation device 100, or via user operation through the user interface unit 108. The image data can be an HEIF file storing a still image or another still image file such as a JPEG. Optionally, if the image data is still image data, it is not necessary to store the image data as a file. Next, in step S203, the CPU 102 determines whether the image data retrieved in step S202 needs to be decoded (that is, whether the image data is an HEIF file). If decoding of the acquired image data is not required (the acquired image data is an HEIF file) (No in step S203), the process proceeds to step S207; otherwise (if the acquired image data is a file other than an HEIF file) (Yes in step S203), the process proceeds to step S204.

[0057] The processing in steps S204 to S206 is performed by the encoding / decoding unit 105. In step S204, the encoding / decoding unit 105 decodes the acquired image data. Next, in step S205, the encoding / decoding unit 105 analyzes the decoded image data to obtain image attribute information. Image attribute information includes, for example, the image width and height, the number of color components, and the bit length. In step S206, the encoding / decoding unit 105 performs HEVC encoding on the decoded image data. Next, in step S207, the metadata processing unit 106 obtains the parameter set required to decode the encoded data generated in step S206. More specifically, this parameter set is a video parameter set (VPS), a sequence parameter set (SPS), or a picture parameter set (PPS), etc. However, if the processing proceeds directly from step S203 to step S207, the image data obtained in step S202 is an HEIF file; therefore, the metadata processing unit 106 extracts the HEVC parameter set from the HEIF file and obtains the HEVC parameter set. In step S208, the encoding / decoding unit 105 transfers the encoded data to the output buffer of RAM 103 and saves the encoded data. This encoded data is one of the encoded data stored in the encoded data storage area 611. Note that in the following description, the image data / encoded data saved in step S208 (stored in the HEIF file) will be collectively referred to as image data.

[0058] Step S209 involves creating metadata related to the image data stored in the HEIF file, and this process is performed by the metadata processing unit 106. The metadata created in step S209 includes image item information and image attribute information. The image item information is... Figure 6 The entry data is stored in area 606 (ItemInfoBox (iinf)). The entry data in the iinf sets the item ID (identification information) used to identify image data in the file and indicates the item type of the HEVC-encoded image. On the other hand, image attribute information is... Figure 6 The data stored in region 608 (ItemPropertiesBox (iprp)). The image attribute information created in step S209 includes... Figure 6 The item data stored in area 609 (ItemPropertyContainerBox (ipco)) and Figure 6The item data stored in region 610 (ItemPropertyAssociationBox (ipma)) is used to store attribute information such as item data indicating the HEVC parameter set obtained in step S207 and item data indicating the width and height of the selected image. The item data in ipma creates associations between item IDs and item data in ipma. The image attribute information created in step S209 is used as... Figure 6 A portion of the metadata stored in the metadata storage area 602 (MetaDataBox) is stored in the output buffer of RAM 103.

[0059] When the process proceeds to step S210 after step S209, CPU 102 checks whether another image data should be stored in the HEIF file being created. If another image exists to be stored, the process returns to step S202; otherwise, the process proceeds to step S211. If the process returns from step S210 to step S202, CPU 102 acquires (selects) the other image data and executes the processing described in steps S203 to S209 above.

[0060] In step S211, CPU 102 determines whether to store the slideshow (continuous image display processing) settings in the HEIF file being created. This determination can be based on information pre-set for the image file creation device 100 or via user operation through the user interface unit 108. If the slideshow settings are stored in the HEIF file ("Yes" in step S211), the slideshow metadata creation processing in step S212 is executed. Note that the processing of step S212 will be explained later.

[0061] In step S213, the metadata processing unit 106 determines a representative image from the images stored in the HEIF file and creates metadata for the main image item information (setting the main image item information in the metadata). This representative image determination process can be performed based on information pre-set for the image file creation device 100, or via user operation through the user interface unit 108, etc. The metadata created in step S213 is stored in... Figure 6 In area 604(PrimaryItemBox(pitm)). Figure 16 This shows the data format of PrimaryItemBox in the HEIF standard. For example... Figure 16 As shown, the data format of pitm only specifies the item ID representing the image. The metadata created in step S213 is stored in the output buffer of RAM 103.

[0062] The final processing in step S214 is performed by the metadata processing unit 106. In step S214, the metadata processing unit 106 creates metadata to be stored. Figure 6 The data in area 601 (FileTypeBox (ftyp)) and area 603 (HandlerBox (hdlr)). Note that, as Figure 7 As shown, the handler type of the MetaDataBox(meta) specified in the HDLR can be "pict". Then, the metadata processing unit 106 combines the metadata of the created FTYP and HDLR, the metadata stored in the metadata storage area 602 (MetaBox(meta)) in RAM 103, and the encoded data stored in the encoded data storage area 611 (MediaDataBox(mdat)). The metadata processing unit 106 forms on RAM 103... Figure 6 The data of the structure shown is processed and completed as a HEIF file, and then output. Afterwards, the process proceeds to step S215, thus ending the processing sequence (S215). The CPU 102 can write the data of the created HEIF file from RAM 103 and save it to ROM 104.

[0063] Note that if the metadata creation process for the slideshow is skipped in step S212 (which is "No" in step S211), then the metadata creation process will not be generated. Figure 6 The metadata processing unit 106 may exclude the iref (item reference box) from the metadata of the HEIF file, particularly if the stored image data includes related image data such as captured images and their thumbnails. However, if the stored image data includes related image data such as captured images and their thumbnails, the metadata processing unit 106 creates entry data for irefs indicating the associations between the image data in step S209. Therefore, the metadata of the ultimately created HEIF file may include irefs.

[0064] Reference Figure 7Here's an example illustrating the values ​​(data) stored in the internal structure of the HEIF file according to the sequence described above. In the PrimaryItemBox (pitm) indicated by description 701 (corresponding to area 604), 1 is stored as item_ID. The ItemInfoBox (iinf) indicated by description 702 (corresponding to area 606) indicates information representing the type of each image item identified by its item_ID. An image item with item_ID 1 is "slid" and indicates a derived image constituting a slideshow. Image items with item_ID 2 or greater are "hvc1" and indicate HEVC-encoded images. The ItemLocationBox (iloc) indicated by description 703 (corresponding to area 605) indicates the storage location of each image data bitstream in the file. An image item with item_ID 1 indicates that construction_method is 1, which means that data exists in the ItemDataBox (idat) indicated by description 707 (corresponding to area 616). Regarding other images, the location of the data in the MediaDataBox (corresponding to the encoded data storage area 611) indicated by description 708 can be specified. The ItemReferenceBox (iref) (corresponding to area 607) indicated by description 704 is the area indicating the reference relationship between image items. In this example, reference_type is "dimg", which indicates the derived image constituting the slideshow, that is, the derived image used to reference multiple images to be displayed in the slideshow. Furthermore, description 704 indicates referencing each image item with item_ID 2 or greater from item_ID 1, which is a derived image item. In the ItemPropertyContainerBox (ipco) (corresponding to area 609) within the ItemPropertyBox (iprp) (corresponding to area 608) indicated by description 705, ItemProperty (item properties) representing the image's attribute information is stored. hvcC indicates HEVC encoding parameters, and ispe indicates attribute information representing the image's size. Description 706 indicates the ItemPropertyAssociationBox (ipma) (corresponding to area 610) that represents the association between each image item and attribute information. Each image item is sequentially associated with the attribute information in ipma.

[0065] [Metadata creation and processing for slideshows]

[0066] Next, refer to Figure 3 , Figure 4 , Figure 5 and Figure 6 To explain Figure 2 The metadata creation process for the slideshow in step S212. In this embodiment, the images constituting the slideshow are stored as derived images in the HEIF file. Figure 3 A flowchart of the metadata creation process according to this embodiment is shown. The process begins at step S301. First, in steps S302 and S303, the CPU 102 selects one or more image data to be displayed in the slideshow from the image data stored in the HEIF file, and determines the display order. Next, the CPU 102 determines the display time (time period) for each selected image. The display time (time period) can be constant for all images or different for each image. It is not necessary to specify a value when the file is created, and any value can be determined during playback. The selection and determination processes in steps S302 and S303 can be based on information pre-set for the image file creation device 100, or via user operation through the user interface unit 108, etc.

[0067] The subsequent processing in steps S304 to S307 is performed by the metadata processing unit 106. In step S304, the metadata processing unit 106 creates image item information to set the item ID of the derived images constituting the slideshow. That is, similar to the above... Figure 2 Similar to step S209, the metadata processing unit 106 creates the metadata to be stored Figure 6 The entry data in region 606 (ItemInfoBox(iinf)). In this example, the metadata processing unit 106 designates an ID that does not duplicate the item ID of the image data stored in the HEIF file as the item ID of the entry data, and designates "slid" indicating the derived image constituting the slideshow as the item type (see [link]). Figure 7 Description 702).

[0068] In step S305, the metadata processing unit 106 creates image reference information to specify the images to be displayed in the slideshow. This image reference information is created to be stored... Figure 6 The item data in region 607 (ItemReferenceBox(iref)). This item data is assigned the type "dimg" representing the derived image, and the item ID of the image data referenced by the item ID of the derived image is specified in list format. The item IDs of the image data used as reference destinations are specified in list format according to the display order determined in step S302.

[0069] In step S306, the metadata processing unit 106 sets descriptive information for the derived images constituting the slideshow. This descriptive information is... Figure 6The data stored in area 616(ItemDataBox(idat)). Figure 4 This example shows the data format for the descriptive information of derived images in a slideshow. The descriptive information (ImageSlideshow) specifies the display time (time period) for each image to be shown in the slideshow. Figure 4 In the example shown, if the display time (time period) is constant for the image (i.e., flags&1 is 1), then as described in description 401, only one duration parameter is specified. Alternatively, if flags&1 is 0, then as described in description 402, duration parameters are specified in display order from a list of duration parameters used to specify the display time (time period) for each image data. The duration parameter has a numerical value indicating the time for displaying the corresponding image item. The unit of time set as the display time (time period) is assumed to be sec (seconds) or msec (milliseconds). However, the invention is not limited to this, and any unit that can specify time can be used. Optionally, a relative time parameter used by the reproduction device (i.e., display unit 107) to determine the display time (time period) can be used. Furthermore, Figure 4 The data format shown may include parameters such as `time_unit` to specify units. These units can be configured to be valid based on the value of `version` or `flags`. The `duration` parameter can specify the time unit. For example, specifying 10 in the `duration` parameter sets it to 10 seconds when a value indicating sec is specified in `time_unit`, and to 10 msec when a value indicating msec is specified in `time_unit`. Other methods that can uniquely identify μsec, min, or other time units can be used. Note that if no display time (time period) is specified when the file is created, information can be stored indicating that an arbitrary time (time period) is specified when the file is reproduced by specifying a value such as 0.

[0070] In step S307, the metadata processing unit 106 sets image attribute information for the derived images constituting the slideshow. An example of this image attribute information is information indicating the width / height of the screen displaying the slideshow. If the size of each image specified for the slideshow differs from the size of the derived images, the images displayed in the slideshow can be enlarged or reduced and displayed, or only the portion of the image falling within the screen size can be displayed. If the screen size is large, attribute information can be described to specify the display of blank areas. However, image attribute information for derived images is not always necessary and does not need to be set.

[0071] The format of the descriptive information of the derived images that make up a slideshow can be... Figure 5 The format shown. Figure 5 This is another example of the data format for describing the derived images in a slideshow. Figure 5 The description information shown (ImageSlideshowWithinCnvas) has a data format that can specify the canvas (the image area displayed on display unit 107 where the reconstructed image of the input image is arranged) for displaying the slideshow. The canvas_fill_value parameter indicated by description 501 represents the pixel value of each channel used when the pixels of the input image are not at a specific pixel position. This pixel value is specified as an RGBA value (R, G, B, and A each correspond to a loop counter j equal to 0, 1, 2, or 3). The RGB values ​​are in the sRGB color space defined in IEC 61996-2-1. The A value is a linear opacity value ranging from 0 (completely transparent) to 65535 (completely opaque). The output_width and output_height parameters indicated by description 502 specify the width and height of the reconstructed image where the input image is arranged, respectively. If flags&1 is 0, the output_width and output_height parameters each have a value represented by 16 bits. On the other hand, if flags&1 is 1, then the output_width and output_height parameters each have a value represented by 32 bits. The reference_count parameter, indicated by description 503, is the ItemTypeReferenceBox (item type reference box) from the ItemTypeReferenceBox whose type is identified by the from_item_ID field as "dimg". Figure 7 The image is obtained as shown in description 704. The horizontal_offset and vertical_offset parameters, indicated by description 503, specify the offset of the input image from the top left corner of the canvas. Pixel positions with negative offset values ​​are not included in the reconstructed image. Horizontal pixel positions equal to or greater than the output_width parameter are not included in the reconstructed image. Vertical pixel positions equal to or greater than the output_height parameter are not included in the reconstructed image. If flags&2 is 1, then... Figure 1Similar to description 401, a common duration parameter is specified. If flags&2 is 0, then as shown in description 504, duration parameters are specified in display order from a list of duration parameters used to individually specify the display time (time period) for each image data. The duration parameter has a numerical value indicating the time for displaying the corresponding image item. The unit of time set as the display time (time period) is assumed to be sec or msec. However, the invention is not limited to this, and any unit that can specify time can be used. Optionally, a relative time parameter used by the reproduction device to determine the display time (time period) can be used. Furthermore, similar to... Figure 4 Similarly, data formats can include parameters such as `time_unit` to specify units. These unit-specifying parameters can be configured to be valid based on the value of `version` or `flags`. The `duration` parameter can specify the time unit. Methods that can uniquely identify min, sec, msec, μsec, or other time units are possible as specified values. Note that if no display time (time period) is specified when the file is created, information can be stored indicating that an arbitrary time (time period) should be specified when the file is reproduced by specifying a value such as 0.

[0072] If image attribute information is set in step S307, then similar to step S209 above, the metadata processing unit 106 creates the metadata to be stored. Figure 6 The entry data in region 609 (ItemPropertyContainerBox(ipco)). Additionally, the metadata processing unit 106 creates the data to be stored... Figure 6 The entry data in region 610 (ItemPropertyAssociationBox(ipma)) is then processed to step S308, thereby ending the processing sequence.

[0073] Note that the metadata created in steps S304 to S307 is used as... Figure 6 A portion of the metadata stored in region 602 (MetaDataBox(meta)) is written to the location in the output buffer of RAM 103 where the data is to be stored. Furthermore, the item ID of the derived image set in step S213 can be specified as the item ID of the representative image in the processing described in step S213.

[0074] [Slideshow playback processing]

[0075] Next, refer to Figure 20 This illustrates the reproduction process of slideshows stored in image file format. Figure 20This is a flowchart of the image file slideshow playback process. More specifically, Figure 20 This illustrates the process of reproducing one or more still images stored as a slideshow file according to the HEIF file format. Figure 20 The steps in the flowchart shown indicate the processing performed by one of the following: the software of CPU 102, the encoding / decoding unit 105, and the metadata processing unit 106. Note that in the following description, "CPU 102" refers to the software processing performed by CPU 102.

[0076] The slideshow playback process in image file reproduction begins at step S2001. Then, in step S2002, CPU 102 retrieves the metadata stored in the metadata storage area 602 (MetaBox(meta)) from the HEIF file stored in RAM 103 or ROM 104. Next, in step S2003, CPU 102 analyzes the metadata retrieved in step S2002, and in step S2004, as a result of the analysis, determines whether metadata related to the slideshow is stored in that metadata. If the metadata related to the slideshow is stored in that metadata ("Yes" in step S2004), the process proceeds to step S2005; otherwise ("No" in step S2004), the process proceeds to step S2010. If the process proceeds to step S2010, the image file creation device 100 performs playback processing of the HEIF file other than the slideshow.

[0077] In step S2005, the metadata processing unit 106 acquires metadata for the image items associated with the slideshow display. More specifically, the metadata processing unit 106 acquires item information, image attribute information, and position information in the image file for each image item that constitutes the derived image reference of the slideshow. In step S2006, the encoding / decoding unit 105 acquires image data in the order of the slideshow display. Each image data is acquired by specifying its position in the encoded data storage area 611 (MediaDataBox(mdat)) based on the position information in the image file stored in the metadata. In step S2007, the encoding / decoding unit 105 decodes the image data to be displayed, and in step S2008, temporarily stores the decoded image data in a buffer. Subsequently, in step S2009, the CPU 102 displays the image on the display unit 107 according to the display time (time period) and attribute information described in the metadata. Note that if information such as 0, indicating that an arbitrary time (time period) is specified during file reproduction, is stored, the display time (time period) is determined by the processing of the reproduction device. By repeatedly executing steps S2005 to S2009, the images stored in the HEIF file are sequentially displayed on the display unit 107. Note that, although not shown in this embodiment, the CPU 102 can control the display unit 107 to repeat the display of images starting from the first image or to end the slideshow display after the display of all images stored as a slideshow has ended.

[0078] According to this embodiment, by forming and storing multiple images stored in an HEIF file as derived images, images constituting a slideshow using derived images can be stored. Therefore, it becomes easy to save an HEIF file containing a collection of multiple still images as a file intended for slideshow display. Furthermore, even when processing images of different sizes, events causing display size changes each time an image is displayed can be prevented by defining canvas information in the description information of the derived images. The display position can be specified by maintaining canvas position information as a parameter in the description information of the derived images. The image to be prioritized in the slideshow can also be switched by adapting the derived image item to the main image item. Note that this embodiment describes a configuration for storing metadata used to implement a slideshow using derived images in an HEIF file. Different configurations can be used, as long as a slideshow is formed using derived images.

[0079] <Second Embodiment>

[0080] The image file creation device according to the second embodiment has the same reference as in the first embodiment. Figure 1 The configuration is the same as described above. Figure 2The sequence of image file creation and processing shown Figure 20 The slideshow playback processing of the image files shown is similarly applicable to this embodiment. However, Figure 2 The metadata creation process (S212) for the slideshow in this embodiment differs from the first embodiment. Therefore, this embodiment will mainly refer to... Figure 8 , Figure 9 , Figure 10 , Figure 11 , Figure 12 , Figure 13 , Figure 14 , Figure 15 , Figure 21 , Figure 22 , Figure 23 , Figure 24 , Figure 25 , Figure 26 , Figure 27 , Figure 28 , Figure 29 , Figure 30 and Figure 31 Let's explain the process in step S212.

[0081] Figure 8 This is a flowchart illustrating the process of creating metadata for a slideshow according to this embodiment. Figure 14 The structure of an HEIF file 1400, which is an example of an HEIF file created by the image file creation device 100 according to this embodiment, is shown. The HEIF file 1400 includes a metadata storage area 1402 (MetaBox(meta)) and an encoded data storage area 1411 (MediaDataBox(mdat)).

[0082] refer to Figure 8 The metadata creation process for the slideshow begins in step S801. First, in steps S802 and S803, [the process involves...]. Figure 3 Steps S302 and S303 are similar; the CPU 102 selects the images to be displayed in the slideshow, determines the display order, and determines the display time (segment) for each selected image. The unit for the time set as the display time (segment) is assumed to be sec or msec. However, the invention is not limited to this, and any unit that can specify time can be used. Optionally, a relative time parameter used by the playback device to determine the display time (segment) can be used. Where it is not necessary to specify the display time (segment) when the file is created, any time (segment) can be specified during file playback.

[0083] Next, in step S804, the metadata processing unit 106 sets the groups of images to be displayed in the slideshow. More specifically, the metadata processing unit 106 creates information (group information) for grouping the images to be displayed in the slideshow. This group information is to be stored... Figure 14 The metadata is located in region 1416 (GroupsListBox (grpl)). In HEIF, group information for items such as image data is stored in grpl. This group information is assigned as the group ID and group type for group identification information and is identified in the HEIF file. In this embodiment, in step S804, the metadata processing unit 106 creates slideshow group information (SlideshowEntityToGroupBox) as group information. Figure 9 This shows the data format of SlideshowEntityToGroupBox. Metadata processing unit 106 creates... Figure 9 The data is in the format shown, and this data is stored in grpl (see...). Figure 14 (Region 1417). The SlideshowEntityToGroupBox is a box used to identify a group of entities intended for a slideshow display of a collection of multiple images on a large canvas. The group type of the SlideshowEntityToGroupBox is "slid," and it indicates the group of items used in the slideshow. Because... Figure 9 The data format shown is obtained by extending EntityToGroupBox, thus additionally specifying group_id for storing the group ID and num_entries_in_group for indicating the number of items included in the group. As item IDs, the item IDs of the selected images to be displayed in the slideshow are specified in the order they are displayed.

[0084] Note that since SlideshowEntityToGroupBox is obtained by extending EntityToGroupBox, tracks can also be stored as groups, but this embodiment only targets image items and prohibits the storage of tracks and items other than images. However, in another form, a structure including tracks can be adopted. If, for example, track IDs are included, the number of track IDs can be limited to 1, and parameters related to the display time (time period) of each sample can be specified in the track. It is assumed that a switching (transition) effect (described later) can be specified for each sample through a sample group. Similarly, in other forms, the number of track IDs is limited to 1, and the display time period of each sample is specified in the track. Then, a method is provided that can use a derived track that is in progress as "MPEG-B Part 16 Derived visual tracks in the ISO baseMedia file format" to specify (described later) the canvas and switching (transition) effects.

[0085] As another approach, consider methods that do not impose restrictions on the entities stored in the SlideshowEntityToGroupBox. Alternatively, consider methods that can store either an image item ID or a track ID. In this case, for example, there are methods that specify a common display time (time period) for the display time (time period) and methods that specify tracks based on tracks and items based on image attribute information.

[0086] refer to Figure 9 Descriptions 901 and 902 are similar to those described in the first embodiment. Figure 5Descriptions 501 and 502 are identical and will not be described further. Part of description 903 is optional and is specified when setting the default display time (time period) for the slideshow. If a default display time (time period) is specified, it is specified in the `default_entity_duration` parameter. `default_entity-duration-present` is a value of 0x000002. If `flags&default_entity-duration-present` is 1, the `default_entity_duration` parameter is specified as the default display time (time period). If `flags&default_entity-duration-present` is 0, the display time (time period) is specified individually for each image data, thus using image attributes to specify the display time (time period). The `default_entity_duration` parameter has a numerical value indicating the time (time period) for displaying the corresponding image item. The unit of time set as the display time (time period) is assumed to be sec or msec. However, the invention is not limited to this, and any unit that can specify time can be used. Optionally, a relative time parameter used by the playback device to determine the display time (time period) can be used. In addition, the data format can include parameters such as `time_unit` to specify units. These unit-specifying parameters can be configured to be valid based on the value of `version` or `flags`. The time unit for the `default_entity_duration` parameter can be specified. As a possible value, methods that can uniquely identify min, sec, msec, μsec, or other time units are feasible. Note that if no display time (time period) is specified when the file is created, information indicating that any time (time period) should be specified during file reproduction can be provided by specifying a value such as 0.

[0087] Note that even when `flags&default_entity-duration-present` is 1 and the `default_entity_duration` parameter is specified, the display time (time period) of the image attribute information takes precedence when a display time (time period) is specified in the image attribute information. This embodiment uses a method to determine whether to optionally specify a default display time (time period) via `flags`. However, instead of optionally setting a default display time, the `default_entity_duration` parameter can be set. In this case, for example, the `default_entity_duration` parameter specified in `SlideshowEntityToGroupBox` can be used as the default value and can be treated as the display time (time period) used when no attribute information is specified individually for each image item. Furthermore, even if flags are additionally set and a flag indicating a value commonly used for all image items is used to specify the display time (time period) in the attribute information, a common display time (time period) can be used.

[0088] As the data format for SlideshowEntityToGroupBox, it can be used Figure 21 The structure shown is described. In this case, the metadata processing unit 106 creates... Figure 9 The data is in the format shown, and this data is stored in grpl (see...). Figure 14 (Region 1417). The SlideshowEntityToGroupBox is a box used to identify a group of entities intended for display in a slideshow of a collection of multiple images. The group type of the SlideshowEntityToGroupBox is "slid," and it indicates the group of items used in the slideshow. Because... Figure 21 The data format shown is obtained by extending EntityToGroupBox, therefore additionally specifying `group_id` for storing the group ID and `num_entries_in_group` indicating the number of items included in the group. As item IDs, the item IDs of the selected images to be displayed in the slideshow are specified in the order they are displayed. Figure 21 In the structure shown, `SlideshowEntityToGroupBox` is used to identify the group of images to be displayed in the slideshow and their display order. Figure 21The structure shown does not contain the special parameters used by SlideshowEntityToGroupBox. In this case, the parameters are specified using the item data (group IDs) stored in the ItemPropertyContainerBox (ipco) and ItemPropertyAssociationBox (ipma) within the ItemPropertiesBox (iprp) (explained later). Note that even... Figure 9 The structure shown can also be associated with properties specified for groups. Assume the entity stored in `SlidshowEntityToGroupBox` stores the item IDs of coded image items and derived image items that can be displayed. As derived images, for example, a defined identifier, grid image, or iovl image can be specified, thus enabling the derived images to be displayed on the canvas as an advanced slideshow. Optionally, other group IDs can be stored. For example, consider displaying images grouped into a shooting group at the same time. For example, consider storing images taken for HDR (High Dynamic Range) rendering or for display as panoramic photos as a group, and specifying the group ID as an entity of `SlideshowEntityToGroup`. This enables the display of an advanced slideshow.

[0089] On the other hand, a structure can be used to store data by restricting it to images of a specific item_type. For example, in Figure 21The structure of the EntityToGroupBox shown does not retain canvas information. Therefore, consider using an overlay image defined as a derived image. If a canvas is needed, specify the overlay's iovl in the item_type of the entities that can be stored. Then, consider that all items stored in the EntityToGroupBox are overlay derived images. In this case, it is expected that the same output_width and output_height parameters be set for all overlay derived images stored in SlideshowEntityToGroup. Furthermore, consider specifying only encoded images when specifying encoded images. In this case, common ispe image properties are expected to be associated with each image. On the other hand, without setting this restriction, the property used to specify the overall size of the slideshow display can be associated with the group ID in the EntityToGroupBox. This assumes the property of the extended structure of the ispe property. That is, the ispe property can be applied to the entity group. Optionally, the size of the image specified in the first entity in the SlideshowEntityToGroupBox can be used as the overall size of the slideshow display. In addition, the image sizes of the entities stored in the SlideshowEntityToGroupBox can be restricted to be the same. If an image with a size different from the display size or limits is specified, the image can be enlarged / reduced or cropped to fit within the display size before being displayed. If the image is small, the remaining area can be displayed by additionally specifying default canvas information or predefining a specific canvas. However, the overall size of the slideshow display can be switched for each displayed image.

[0090] Figure 25The ImageScalingProperty shown has a data format including a ratio parameter describing 2501, and is a transform property used to scale (enlarge / reduce) the display size of an image. This property allows the image size to be enlarged / reduced while maintaining the aspect ratio. The ratio parameter describing 2501 is an 8-bit integer and represents a ratio that is a multiple of 2: 16, 8, 4, 2, 1 / 2, 1 / 4, 1 / 8, or 1 / 16. The high 4 bits indicate the operation used for enlargement. If the most significant bit is 1, this indicates a ratio of 16; if the second most significant bit is 1, this indicates a ratio of 8; if the third most significant bit is 1, this indicates a ratio of 4; and if the fourth most significant bit is 1, this indicates a ratio of 2. The low 4 bits indicate the operation used for reduction. If the least significant bit is 1, the ratio is 1 / 16; if the second bit from the least significant bit is 1, the ratio is 1 / 8; if the third bit from the least significant bit is 1, the ratio is 1 / 4; and if the fourth bit from the least significant bit is 1, the ratio is 1 / 2. Note that this embodiment uses the above structure as the data format for ImageScalingProperty. However, more detailed specification is allowed. This property can be represented by a variation of the clap property. That is, the numerator and denominator can be specified separately. Furthermore, instead of specifying a ratio, the target size can be specified for scaling up / down. In this case, for example, scaling up / down can be performed by specifying either the width or the height while maintaining the aspect ratio. On the other hand, scaling up / down can be performed by specifying both the width and the height without maintaining the aspect ratio. If the aspect ratio is not maintained, methods for specifying vertical and horizontal scaling can be used. These specification methods can be combined, and flags, etc., can be used to switch specification methods to enable arbitrary specification.

[0091] Figure 26The ImageScalingProperty shown has a data format including the target_width parameter (described in 2601) and the target_height parameter (described in 2602), and is a transform property used to scale up / down an image by specifying a target display size. This property allows scaling up / down by directly specifying the width and height in pixels. The target_width parameter (described in 2601) specifies the width of the image after the size change in pixels. The target_height parameter (described in 2602) specifies the height of the image after the size change in pixels. Note that scaling up / down can be performed while maintaining the aspect ratio by specifying only one of the sizes and specifying a value such as 0 for another size so that one of the sizes after the size change is not specified. Only one or both of the sizes can be used; values ​​of version or flags are valid for this data format.

[0092] ImageScalingProperty can be defined by extending the already defined ImageSpatialExtentsProperty (image spatial extent property). For example, consider a method to change the meaning of ImageSpatialExtentsProperty without altering the defined data structure. In this case, the extension is made to specify ImageSpatialExtentsProperty as a transformation property, instead of a descriptive property. If ImageSpatialExtentsProperty is treated as a transformation property, it can be identified whether the property is associated with the image item defined as an identifier (iden) derived image item by associating the property with that image item. More specifically, if the ImageSpatialExtentsProperty associated with an iden-derived image item differs from the ImageSpatialExtentsProperty associated with the image item that is the source of the derived image, it is interpreted as requiring an image size scaling operation. In this case, the width of the resized image is specified in pixels as the image_width parameter. Similarly, the `image_height` parameter specifies the height of the image after the size change, in pixels. Note that a restriction is imposed that the image size cannot be directly changed if a derived image item is not defined.

[0093] on the other hand, Figure 27The ImageSpatialExtentsProperty shown is an extension with a modified data structure. This is a data format including the image_width parameter (description 2701), the image_height parameter (description 2702), the target_width parameter (description 2703), and the target_height parameter (description 2704). This data format is used to describe image size information, as well as scaling and transformation properties, by specifying the reconstructed size and display target size of the encoded image data. In ImageSpatialExtentsProperty, the width and height of the associated image item are described. All image items are associated with one property of this type. The image_width parameter (description 2701) and the image_height parameter (description 2702) indicate, in pixels, the original size of the reconstructed image of the associated image item before the transformation. If flags&1 is 1, the reconstructed image is resized from the pixel size specified by the image_width and image_height parameters to the pixel size specified by the target_width and target_height parameters. The image_width parameter specifies, in pixels, the width of the reconstructed image before the size change. The `image_height` parameter specifies the height of the reconstructed image in pixels before resizing. The `target_width` parameter specifies the width of the reconstructed image in pixels after resizing. The `target_height` parameter specifies the height of the reconstructed image in pixels. Figure 27 The extension allows the property used for scaling up / down to be directly associated with the image item even if ImageSpatialExtentsProperty is not defined as an iden-derived image item. On the other hand, by defining ImageSpatialExtentsProperty as an iden-derived image item, the property can be associated with the image item.

[0094] The metadata processing unit 106 stores the metadata of the group information created in step S804 in the output buffer of RAM 103.

[0095] The subsequent processing in steps S805 and S806 is also performed by the metadata processing unit 106. In step S805, the metadata processing unit 106 determines whether a portion of the display time (time period) of the images in the slideshow is the same and can be assigned as a default value. If a default value can be assigned ("Yes" in step S805), the processing proceeds to step S806; otherwise ("No" in step S805), the processing proceeds to step S807. In step S806, the metadata processing unit 106 sets the default display time (time period) parameter in the group set in step S804. More specifically, the metadata processing unit 106 sets the default display time (time period) in the default_entity_duration parameter of the data of the created group information (SlideshowEntityToGroupBox) (see...). Figure 9 In the description of 903). Optionally, in Figure 21 In the case of the EntityToGroupBox structure shown, a value is set in the slide_show_timing parameter of SlideShowTimingProperty (described later), and this value is associated with the image group as an image group attribute. In step S807, the metadata processing unit 106 sets image attribute information to specify the display time (time period) of each image to individually set the display time (time period) of each image in the slideshow. Note that if a default display time (time period) is set, it is not necessary to specify the display time (time period) as the image attribute information for images with a default display time (time period). As described above in the first embodiment, this image attribute information is Figure 14 The metadata stored in region 1408 (ItemPropertiesBox(iprp)). The image attribute information created in step S807 includes... Figure 14 The item data stored in area 1409 (ItemPropetyContainerBox(ipco)) and Figure 14 The entry data is stored in area 1410 (ItemPropertyAssociationBox(ipma)). The metadata processing unit 106 creates data indicating the display time (time period) as entry data to be stored in ipco. Note that if no display time (time period) is specified when the file is created, the property used to specify the display time may not be stored, or the property may simply not be associated with an image for which no display time is specified. Optionally, information indicating that an arbitrary time (time period) is specified when the file is reproduced may be stored to associate the property by specifying a value such as 0.

[0096] Note that a structure can be adopted that prohibits specifying the slideshow display time (time period) for each image item and allows specifying only one time (time period) for the group. In this case, the processing in steps S805 and S807 is not required, and only the processing in step S806 is performed. In this case, for the item data stored in area 1410 (ItemPropertyAssociationBox(ipma)), the group ID can be directly specified as the group identification information for SlideshowEntityToGroup. In this case, the group ID needs to be in a unified ID space, in which the ID can be uniquely identified relative to other item IDs or track IDs. On the other hand, if the same display time (time period) is specified for each item, the same properties can be applied to all items stored in the group.

[0097] Figure 10 The data format of ImageDurationProperty is shown as an attribute that specifies the display time (time period) of an image in a slideshow. Figure 10The illustrated ImageDurationProperty has a data format including an image_duration parameter described as 1001, in which the display time (time period) is set. The unit of time set as the display time (time period) is assumed to be sec or msec. However, the invention is not limited to this, and any unit that can specify the time can be used. Optionally, a relative time parameter used by the reproduction device to determine the display time (time period) can be used. As a relative parameter, for example, a percentage or multiple of the value specified as the default display time (time period) can be specified. The data format can include a parameter for specifying units such as time_unit. This parameter for specifying units can be configured to be valid based on the value of version or flags. The parameter specification can specify the time unit of the image_duration parameter. As a possible value, a method capable of uniquely identifying min, sec, msec, μsec, or other time units is feasible. If the display time (time period) is different for each displayed image, ImageDurationProperty data with different parameter values ​​equal to the number of displayed images is stored in the ipco. Then, to specify the display time (time period) for each displayed image, entry data for the IPMA (ImageDuration Property) is created and stored to associate the item ID of the displayed image with the entry data of the created ImageProperty. Additionally, when each image is displayed, data related to the display position indicating the location of each image on the canvas is created. For the displayed image associated with the ImageDurationProperty, the display time (time period) is specified as taking precedence over the default_entity_duration parameter of SlideshowEntityToGroupBox. Figure 21 In the case of SlideshowEntityToGroupBox shown, the specified display time (time period) takes precedence over the default display time associated with the group. Note that if no display time (time period) is specified when the file is created, the property used to specify the display time may not be stored, or the property may simply not be associated with images for which no display time is specified. Optionally, a property can be associated to store information indicating that an arbitrary time (time period) is specified during file reproduction by specifying a value such as 0.

[0098] Figure 23 This shows the data format of SlideShowTimingProperty used to specify the default image display time (time period) in a slideshow. Figure 23The SlideShowTimingProperty shown has a data format including the slide_show_timing parameter described in 2301, in which a default display time (time period) is set. The unit of time set as the display time (time period) is assumed to be sec or msec. However, the invention is not limited to this, and any unit that can specify time can be used. Optionally, a relative time parameter used by the playback device to determine the display time (time period) can be used. The data format can include a parameter for specifying units, such as time_unit. The parameter for specifying units can be configured to be valid based on the value of version or flags. The parameter specification can specify the time unit of the default_entity_duration parameter. As a possible specified value, a method capable of uniquely identifying min, sec, msec, μsec, or other time units is feasible. This property is specified in the specification Figure 21 The default image display time (time period) in the SlideshowEntityToGroupBox shown is preferred. This property is used to specify the duration between two consecutive image items in the EntityToGroupBox. This property is associated only with an entity group. It is assumed that this property is associated with SlideshowEntityToGroupBox, but the invention is not limited thereto. That is, this property can be used for other types of EntityToGroupBox. Note that this embodiment specifies the display time (time period) specified in the slide_show_timing parameter. In other words, it can be interpreted as the timing obtained by multiplying the respective sequential indices of the item IDs stored in the SlideshowEntityToGroupBox by the value of the parameter, indicating the timing of displaying the image of the item ID after the elapsed time since the start of the slideshow. Note that if no display time (time period) is specified when the file is created, the property for specifying the display time may not be stored, or the property may simply not be associated with groups or images for which no display time is specified. Alternatively, a property for storing information indicating that an arbitrary time (time period) is specified when the file is reproduced may be associated by specifying a value such as 0.

[0099] Note that in this embodiment, the ImageDurationProperty, used to specify the display time (time period) for each item individually, and the SlideShowTimingProperty, used to specify the default display time (time period) for a group, have different frame structures, but they can also have a common frame structure. In this case, if the property is associated with an item, it indicates the individual display time (time period), and if the property is associated with a group, it indicates the default display time (time period) for the entire group. In this case, the display time (time period) specified for each item individually is preferred. On the other hand, as mentioned above, the property can be configured to disable specification for each item and apply only to groups. This simplifies the processing used for slideshow display. Additionally, this clearly distinguishes it from the case where images are stored as tracks.

[0100] Figure 11 The data format of ImageLocationProperty, which displays the configuration information for a specified image. Figure 11The ImageLocationProperty shown includes an alignment_position parameter 1101, which represents the relative position of the image relative to the canvas when version 1 is specified in the box identified by imlo. This alignment_position parameter is determined by a value specifying the relative position relative to the canvas. If the alignment_position parameter is 0, the image is displayed with the top left of the canvas aligned to the top left of the canvas. That is, the image is displayed by aligning the top left of the image to the top left of the canvas. In this case, if the image is small, the color determined by the canvas_fill_value parameter specified in SlideshowEntityToGroupBox is displayed. If the image is large, only the portion of the image falling within the canvas is displayed. In this embodiment, the image is displayed in this manner, but methods for zooming in / out of the image can be used. Similarly, if the alignment_position parameter is 1, the image is displayed by aligning the top center of the image to the top center of the canvas. If the alignment_position parameter is 2, the image is displayed by aligning the top right of the image to the top right of the canvas. If the `alignment_position` parameter is 3, the image is displayed by aligning the left center of the image to the left center of the canvas. If the `alignment_position` parameter is 4, the image is displayed by aligning the center of the image to the center of the canvas. If the `alignment_position` parameter is 5, the image is displayed by aligning the right center of the image to the right center of the canvas. If the `alignment_position` parameter is 6, the image is displayed by aligning the bottom left of the image to the bottom left of the canvas. If the `alignment_position` parameter is 7, the image is displayed by aligning the bottom center of the image to the bottom center of the canvas. If the `alignment_position` parameter is 8, the image is displayed by aligning the bottom right of the image to the bottom right of the canvas. Note that values ​​of 9 or greater for the `alignment_position` parameter are reserved. Note that in this embodiment, the `alignment_position` parameter is represented by a numerical value, but it can be represented by assigned bits. If, for example, all bits are 0, the image is displayed with the top left of the canvas aligned with the canvas. If only the first bit is 1, the image is displayed by aligning the top center of the image to the top center of the canvas. If only the second bit is 2, the image is displayed by aligning the top right of the image with the top right of the canvas. This definition is possible. In this case, it is assumed that setting multiple bits to 1 is prohibited.

[0101] If version is not 1, the position is specified by the offset values ​​of the horizontal_offset and vertical_offset parameters relative to the top left of the canvas (Description 1102). Note that if 0 is specified for each offset value, this setting is equivalent to specifying the top left of the image when version is 1. Pixel positions with negative offset values ​​are not included. Note that pixel positions in the horizontal direction should not be specified beyond the output_width parameter specified in SlideshowEntityToGroupBox. Similarly, pixel positions in the vertical direction should not be specified beyond the output_height parameter specified in SlideshowEntityToGroupBox. In this embodiment, ImageLocationProperty is used to specify the display position relative to the canvas when the slideshow is displayed, but it can be used in other applications. For example, images are typically displayed at a specified image size so that when displayed in full screen on a monitor (any screen), the image is centered on the monitor. However, if image attribute information is specified, ImageLocationProperty can be used to specify the position where the image is displayed on the monitor screen. Furthermore, in this embodiment, image attribute information is added to specify the display position. However, as mentioned above, image attribute information can be specified to zoom in / out on the image and display the image.

[0102] ImageLocationProperty is a property used to determine the position of an image on the canvas. On the other hand, it can be used... Figure 22 The image shown is an ImageOverlay derived image. In the current structure of ImageOverlay derived images as defined in ISO / IEC 23008-12 (Part 12), the image can be aligned by indicating pixel positions, but as... Figure 11 As shown in the ImageLocationProperty, alignment cannot be achieved using defined values ​​that indicate relative position to the canvas. To address this issue, by using... Figure 22The structure shown is replaced, making the aforementioned relative alignment possible. Items with an `item_type` value of "iovl" define derived image items by overlaying one or more input images in a specified layer order within the large canvas. In the `ItemReferenceBox` of a derived image item of type `dimg`, a list of input images is displayed in layer order, with the bottom input image shown first and the top input image shown last. If `version` is 0, this position is represented by the pixel position from the top-left corner of the canvas. As already defined, Figure 22 The `horizontal_offset` and `vertical_offset` parameters (description 2202) store pixel offset information from the top-left corner. If `version` is 1, it defines information indicating a predefined relative position to the canvas. Figure 22 The alignment_position parameter (description 2201) and Figure 11 The `alignment_position` parameter in the `ImageLocationProperty` shown is the same. This is achieved by storing the item ID of `ImageOverlay` as an entity in `SlideshowEntityToGroup`, even though... Figure 21 In the case of SlideshowEntityToGroup, the canvas can also be specified.

[0103] Next, the metadata processing unit 106 creates image attribute information to specify the image transition effects during slideshow display, as a specification for other image attribute information. Figure 12 The TransitionEffectProperty data format shows the property information used to specify the transition effect in a slideshow. Figure 24 The data format of TransitionEffectProperty shown is achieved by enabling... Figure 12 The data format shown specifies the version obtained. Figure 24In the format shown, when version is 1, the transition_duration parameter can be specified (explained later). If version is 0, a predefined default value is used for the transition_duration parameter. In another form, an item property without a transition_duration parameter can be formed. This property defines the switching (transition) effect applied between the display operations of two consecutive items in the EntityToGroupBox. This property can be associated with an item or a group of entities. If the same image is stored in one or different slideshow groups and different switching (transition) effects are applied, consider using a derived image item defined as an identifier (iden). A method for assigning different item_id values ​​to the same image data is also considered. In this case, different item_id values ​​can be specified for the same image data by specifying that two or more image items with different item_id values ​​specified in the itemInformationBox (iinf) have the same offset and size in the ItemLocationBox (iloc). Furthermore, a structure that can be specified by extending the ItemPropertyAssociationBox to a newly defined box is considered. These specification methods can be used not only to specify item properties in a slideshow, but also to specify other item properties. Figure 12 or Figure 24The `TransitionEffectProperty` shown consists of a `transition_effect` parameter (description 1201 or 2401) that specifies the transition effect, and a `transition_duration` parameter (description 1202 or 2402) that indicates the duration of the transition effect. The `transition_effect` parameter specifies the effect when the image is displayed by assigning a value. For example, specifying 0 for `transition_effect` results in a cut transition effect. A `transition_effect` value of 1 results in a fade-in / fade-out transition effect. A `transition_effect` value of 2 results in a wipe transition effect. A `transition_effect` value of 3 results in a split transition effect. This allows you to specify values ​​that identify a predetermined effect. Furthermore, a `transition_effect` value of 4 results in a dissolve-in transition effect. If the `transition_effect` parameter is 5, a zoom transition effect is performed. This specifies a value used to identify a predetermined effect. Other values ​​can be undefined, and definitions can be added to identify predetermined effects. The `transition_duration` parameter specifies the duration (time period) for the transition effect specified by the `transition_effect` parameter. The unit of time for the transition effect is assumed to be sec or msec. However, the invention is not limited to this, and any unit of time can be used. Optionally, a relative time parameter used by the playback device to determine the display time (time period) can be used. As a relative time parameter, for example, a specified percentage or multiple of the specified display time (time period) can be specified.

[0104] The data format can include parameters for specifying units such as `time_unit`. The parameter for specifying units can be configured to be valid based on the value of `version` or `flags`. The parameter specification can specify the time unit for the `default_entity_duration` parameter. As a possible value, methods that can uniquely identify min, sec, msec, μsec, or other time units are feasible. It can be configured to switch between any time unit or the specification of a percentage or multiple via parameters. It is assumed that the time specified by the parameter is not included in... Figure 9 The duration parameter (description 903) Figure 10 The image_duration parameter (description 1001) and Figure 23 The time in the slide_show_timing (description 2301). However, the invention is not limited thereto.

[0105] In this context, the total display time during a slideshow is the sum of the display time (time period) specified for each individual item or group and the time required for transition effects (changes) specified for each individual item or group. For example, if Figure 23 The SlideShowTimingProperty shown is applied only to groups, and the TransitionEffectProperty is applied only to groups. The time is the time (time period) obtained by adding the following two values: the value obtained by multiplying the value of the slide_show_timing parameter of SlideShowTimingProperty by the number of items included in the group; and the value obtained by multiplying the value of the transition_duration value by the number of items included in the group.

[0106] Optionally, if time is included in these times, the total display time is the sum of the display times (time periods) specified for individual items or groups. In this case, a time (time period) shorter than each display time (time period) should be specified. However, if a larger value is specified, a switching (transition) effect is not required, or a switching (transition) effect can be performed based on the image display. Optionally, a switching effect for the next image can be performed during the image display effect. On the other hand, if the specified percentage of time (time period) is specified as a relative time parameter, it is not necessary to consider the size relationship with the display time (time period) of each image. Note that in this embodiment, the data format consists of two parameters, but each parameter can be defined as different image attribute information. Furthermore, this embodiment assumes that the effect is specified when displaying image items for which image attribute information has been applied, but the effect when displaying the final image can be additionally specified. In this case, the effect when displaying the final image and the effect when displaying the next image can be specified separately, or only one of these effects can be specified as a limitation. Furthermore, if the `transition_duration` parameter of the property is included in the display time (time period) of each image item, the case where the `transition_duration` parameter is only included in the display time (time period) of the first image in the display time (time period) of two consecutive images is considered. It is also possible to symmetrically include 50% of the value of the `transition_duration` parameter in each display time (time period) of two consecutive images. Optionally, a parameter such as the `cross_item_effect_ratio` parameter can be defined in the data format, and this parameter can be used to specify the percentage or time of each of the first and second images to be included. In this case, if the specified value is a percentage, a value equal to or less than 100% needs to be specified. The specified percentage of time is included in the display time (time period) of the first image, and 100% (specified percentage) of time (time period) is included in the display time (time period) of the second image. Note that if the `cross_item_effect_ratio` parameter is defined, this parameter can be configured to be effective based on the specification of `version` or `flags`, etc. If no value is specified, a pre-specified percentage of time, such as 50%, can be included as a default value in the display time (time period) of each image.

[0107] Parameters can be defined in the item properties of each toggle (transition) effect, thereby specifying the operation of the toggle (transition) effect. Figure 28The `TransitionEffectProperty` shown is a property that allows you to specify a toggle (transition) effect in the property description. `TransitionEffectProperty` consists of the `transition_effect` parameter (description 2801) for specifying the toggle (transition) effect and the `transition_direction` parameter (description 2802) for indicating the toggle (transition) direction. Figure 12 or Figure 24 Similarly, this property defines the toggle (transition) effect applied between the display operations of two consecutive items in an EntityToGroupBox. This property can be associated with an item or a group of entities, and can be changed through... Figure 12 or Figure 24 The same method can be used to specify different transition effects for an image. If (flags&1) equals 1, the recommended transition direction applied according to the transition effect specified by the transition_effect parameter (description 2801) is specified by the transition_direction parameter (description 2802). If (flags&1) does not equal 1, this parameter is not applied. Note that this parameter can be defined as any specified parameter that is applied to the transition effect regardless of the transition direction.

[0108] The `transition_effect` parameter (description 2801) is used to specify the effect when the image is displayed by specifying a value. For example, if 0 is specified for the `transition_effect` parameter, a cut transition effect is performed. In this case, the `transition_direction` parameter (description 2802) is ignored even if it is specified. If the `transition_effect` parameter is 1, a fade-in / fade-out or fade-in transition effect is performed. If the `transition_effect` parameter is 2, a dissolve transition effect is performed. In these cases, the value of the `transition_direction` parameter is similarly ignored. If the `transition_effect` parameter is 3, a wipe transition effect is performed, and only values ​​6 to 13 (described later) specified by each individual `transition_direction` parameter are recognized as valid values. If the `transition_effect` parameter is 4, a split transition effect is performed, and only values ​​2 to 5 (described later) specified by each individual `transition_direction` parameter are recognized as valid values. If the `transition_effect` parameter is 5, a scaling transition effect is applied, and only values ​​from 0 to 1 specified by the individual `transition_direction` parameters (described later) are recognized as valid. If the `transition_effect` parameter is 6, a push transition effect is applied, and only values ​​from 6 to 13 specified by the individual `transition_direction` parameters (described later) are recognized as valid. This specifies the value used to specify the predetermined effect. Other values ​​can be undefined, and definitions can be added to identify the predetermined effect. The `transition_direction` parameter in description 2802 is a parameter indicating the direction of the transition to be applied, and one of the following values ​​is specified.In other words, the definitions are as follows: 0 is in, 1 is out, 2 is horizontal-in, 3 is horizontal-out, 4 is vertical-in, 5 is vertical-out, 6 is from-left, 7 is from-right, 8 is from-top, 9 is from-bottom, 10 is from-left-top, 11 is from-right-top, 12 is from-left-bottom, and 13 is from-right-bottom. Other values ​​are undefined. If the `transition_direction` value exceeds the allowed range for the `transition_effect` parameter, the value is ignored.

[0109] The transition effect is specified using a combination of the `transition_effect` and `transition_direction` parameters. For example, if a transition effect of 3 is specified for the `transition_effect` parameter, then one of a value between 6 and 13 can be specified for the `transition_direction` parameter. If a value of 6 is specified, the transition operation is specified from left to right. Additionally, for transition effects, operations can be specified from right, top, bottom, top left, top right, bottom left, or bottom right. This also applies to the remaining transition effects. Parameters for specifying detailed operations for each transition effect can be defined and specified in the item properties.

[0110] In this embodiment, the `transition_effect` parameter (described as 1201, 2401, or 2801) is used to specify the type of transition effect. However, for each transition effect, the properties of each transition effect can be represented as other properties using 4CC. Figure 29 , Figure 30 and Figure 31 Examples are shown for each. Figure 29The WipeTransitionEffectProperty shown indicates the property that applies a wipe transition effect between the display operations of two consecutive items in an entity group. It describes the effect of outputting the next image by wiping from the first image to the second. This property is associated with the first of the two consecutive items. For the transition_direction parameter describing 2901, specify one of the following values. As the transition direction, the following are applied: 0 for from-left, 1 for from-right, 2 for from-top, 3 for from-bottom, 4 for from-left-top, 5 for from-right-top, 6 for from-left-bottom, or 7 for from-right-bottom. Other values ​​are undefined. Note that flags, etc., can be used to toggle whether the parameter is valid.

[0111] Figure 30 The ZoomTransitionEffectProperty shown indicates the property that applies a zoom transition effect between the display operations of two consecutive items in an entity group. It describes the effect of outputting the next image by zooming in or out from the first image to the second. This property is associated with the first of the two consecutive items. The transition_direction parameter, described as 3001, specifies one of the following values. As the transition direction, the following applies: in in case 1, or out in case 2. Other values ​​are undefined. Note that flags, etc., can be used to toggle whether the parameter is valid.

[0112] Figure 31 The FadeInTransitionEffectProperty shown is a property that indicates the fade-in transition effect applied between the display operations of two consecutive items in an entity group. It describes the effect of outputting the next image by fading in from the first image to the second image. This property is associated with the first of the two consecutive items. Since there is no specifyable transition direction in this property, no parameters are retained.

[0113] Additionally, the concept of defining a `DissolveTransitionEffectItemProperty` for dissolve (smooth, gradual transition from the first image to the second image) transition effects is considered. Different item properties can be defined similarly for the remaining transition effects. For example, `cutTransitionEffectItemProperty` can be defined as a cut (instantaneous transition from the first image to the second image) effect, `splitTransitionEffectItemProperty` as a split (transition to the second image by vertically or horizontally splitting the image) effect, and `pushTransitionEffectITemProperty` as a push (transition by pushing the first image with the second image) effect. If a specifyable `transition_direction` parameter exists for each of these effects, the corresponding parameter is defined as a specifyable value.

[0114] The `transition_effect` parameter (described as 1201, 2401, or 2801) allows for the definition of new item properties for transition effects that are reserved as undefined values. This property can be specified individually for image items or groups. However, if individual item properties are defined, at most one of the intended transition effects must be associated with the item. In other words, a restriction is defined that only at most one of the transition effects can be associated. On the other hand, multiple transition effects can be applied, and the transition effect obtained by blending these effects can be represented. Furthermore, transition effects can be defined by the user using UUIDs, etc. If a transition effect is defined using a UUID, it must be supported on both the file generation and reproduction sides.

[0115] Notice, Figure 12 , Figure 24 or Figure 28 The TransitionEffectProperty shown is associated with other descriptive and transformation properties.

[0116] Can Figure 10 ImageDurationProperty or Figure 23 SlideShowTimingProperty and Figure 12 or Figure 24The TransitionEffectProperty is summarized as an image attribute information. Figure 13 Shown as a summary Figure 10 ImageDurationProperty and Figure 12 The data format of SlideShowProperty, which obtains image attribute information from TransitionEffectProperty. Figure 13 In the structure shown, image attribute information related to the slideshow can be specified jointly. Similarly, image attribute information can be obtained by combining image attribute information indicating the display time (time period) and image attribute information indicating the transition effect. This image attribute information can be applied to image groups.

[0117] The metadata of the image attribute information created in step S807 is stored in the output buffer of RAM 203. Then, after the processing in step S806 or S807, the processing proceeds to step S808, thereby ending the metadata processing sequence of the slideshow.

[0118] Figure 15 This is a diagram illustrating an example of a HEIF file output according to this embodiment. Figure 15Description 1501 indicates that the PrimaryItemBox (pitm) stores 1 as the item_ID. Note that the PrimaryItemBox can be extended to specify the group ID used to identify the SlideshowEntityToGroup mentioned above as the ID specified in this box. In this case, 1001, which will be used as the group_id (explained later), will be specified as the ID. Description 1502 indicates that the ItemInfoBox allows each image item to be identified by its item_ID and indicates the type of the image item identified by its item_ID. The image item with item_ID 1 is "hvc1", which indicates an HEVC encoded image. Similarly, all image items up to the image item with item_ID 48 are stored as HEVC encoded images. Description 1503 indicates that the ItemLocationBox indicates the storage location of each image data bitstream in the file. The location where the data for each image exists in the MediaDataBox can be specified. Description 1504 indicates that the ItemPropertyContainerBox in the ItemPropertiesBox stores the ItemProperty, which indicates the attribute information of the image. “hvcC” indicates the HEVC encoding parameters. “ispe” is the attribute information indicating the image size. “dura” is the ImageDurationPropertyBox mentioned above. “imlo” is the ImageLocationPropertyBox. “teff” is the TransitionEffectPropertyBox. ItemPropertyAssociationBox1505 indicates the association between each image item and its attribute information. Each image item is sequentially associated with the attribute information in “ipco”. For example, a common ispe is associated with item_ID 1 and item_ID 2, indicating a common image size. On the other hand, applying a different “ispe” to item_ID 3 indicates a different image size. Furthermore, since dura is not associated with item_ID 1, the default display duration is applied. Different display time periods are applied to item_ID 2 and item_ID 3. Description 1507 indicates the SlideshowEntityToGroupBox. Specify 1001 as the group_id, 48 as the number of items in the group, opaque black as the canvas fill value, and 4032 width and 3024 height as the canvas size. Specify 1 and 2 through 48 as item IDs for each image in the entity_id according to the slideshow display order. This stores the information used for the slideshow display.

[0119] As described above, if the metadata creation process for the slideshow described in this embodiment is performed, the created HEIF image file will have... Figure 14 The internal structure is shown. Note that in the first embodiment, derived images of a slideshow are described. Therefore, Figure 6 Region 606 (ItemInfoBox(iinf)) stores entries with item IDs that have derived images. However, in this embodiment, it is clear that... Figure 14 Region 1406 (iinf) does not include entries indicating derived images for a slideshow. In the first embodiment, image attribute information and item reference information for creating derived images for a slideshow are stored as entry data respectively. Figure 6 In regions 607 (ItemReferenceBox(iref)) and 608 (ItemProptiesBox(iprp)). However, in this embodiment, it is clear that... Figure 14 Regions 1407 (iref) and 1408 (iprp) do not include entries related to derived images in a slideshow.

[0120] In this embodiment, a method is used to group the images to be displayed in the slideshow in the above structure and apply attribute information of each image when the slideshow is displayed to each image. However, any method for grouping images and maintaining associated attributes as parameters or properties of the group can be used.

[0121] According to this embodiment, by grouping the images used for slideshow display, images intended for slideshow display among multiple images stored in the HEIF file can be easily identified and stored. By storing canvas-related information as group parameters, the size of the slideshow display can be standardized and processed. By maintaining information related to display time (time period) as group parameters, group attribute information, or individual image attribute information, the slideshow display time can be arbitrarily specified. By maintaining canvas position information during image display as image attribute information or parameters of grouped derived images, the display position can be specified. Furthermore, by enabling the image transition effects during slideshow display to be specified as image attribute information, more flexible slideshows can be performed. By specifying the identifier (iden) defined as a derived image, grid image, or iovl image as the image stored in SlideshowEntityToGroupBox, derived images can be displayed as a slideshow. Multiple boxes of SlideshowEntityToGroupBox can also be stored in one file using different group IDs, and multiple slideshow representations can be stored in one file.

[0122] [Third Embodiment]

[0123] The image file creation device according to the third embodiment has the same features as the reference in the first embodiment. Figure 1 The configuration is the same as described above. Figure 2 The sequence of image file creation and processing shown Figure 20 The slideshow playback sequence shown can be similarly applied to this embodiment. However, in this embodiment, Figure 2 The metadata creation process (S212) and the process for setting the main image item information in this embodiment differ from the first embodiment. Therefore, this embodiment will mainly refer to... Figure 16 , Figure 17 , Figure 18 and Figure 19 Let's explain the processing in steps S212 and S213.

[0124] Figure 16 This is a diagram illustrating the data format of PrimaryItemBox(pitm) in the HEIF standard. In this embodiment, it uses an extension... Figure 16 The data format obtained from the specifications shown in Pitm. Figure 17An example of the PrimaryItemBox data format obtained by extending the specifications of pitm is shown. This extension is intended to allow one or more image items to be specified as primary image item information. In the processing of step S212, the metadata processing unit 106 selects the images to be displayed in the slideshow and creates a list of item IDs in the display order. Then, a list of item IDs is created to specify one or more item IDs to be displayed in the slideshow as one or more primary image items. In step S213, the metadata processing unit 106 stores the image item IDs in the list order based on the list of item IDs created in step S212. Figure 17 In a portion of description 1701 or 1702, the number of stored item IDs is set in the item_count parameter. This allows specifying one or more images as one or more main image items for the HEIF file to be created. In this embodiment, in step S212, the metadata processing unit 106 creates image attribute information to individually set the display time (time period) of each image in the slideshow. This process of setting image attribute information is similar to that described in the second embodiment above. Figure 8 The process in step S807 is the same, and the metadata processing unit 106 creates the metadata of the ItemPropertiesBox(iprp) and saves the metadata in RAM 203. Alternatively, while the HEIF standard currently allows specifying only one box for the PrimaryItemBox, a method can be used to enable specifying multiple boxes for the PrimaryItemBox and storing these boxes in the order they are displayed in a slideshow.

[0125] Figure 18 This shows another example of the data format for PrimaryItemBox obtained by extending the specifications of pitm. Figure 18 In the data format shown, the group_id (description 1801) of the SlideshowEntityToGroupBox described in the second embodiment can be specified in the PrimaryItemBox.

[0126] Figure 19 An example of an HEIF file output according to this embodiment is shown. Figure 19 This shows an example of a file where a group_id can be specified. (Reference) Figure 19 The group_id 1001 specified in SlideshowEntityToGroupBox (description 1507) is specified in the PrimaryItemBox (pitm) indicated by description 1901. Figure 19Descriptions 1902 to 1907 in the second embodiment are similar to those described in the second embodiment. Figure 15 The descriptions in 1502 to 1507 are the same.

[0127] As described above, according to this embodiment, by specifying the image used for slideshow display in the extended PrimaryItemBox, the image intended for slideshow display among multiple images stored in the HEIF file can be easily identified and stored. By allowing the group ID obtained through grouping in the EntityToGroupBox to be specified in the PrimaryItemBox, multiple images can be processed as a highest-priority image group. By maintaining information related to the display time (time period) as parameters of the group or attribute information of each image, the slideshow display time can be arbitrarily specified. By maintaining the canvas position information when the image is displayed as image attribute information, the display position can be specified. Furthermore, by allowing the image transition (transition) effect during slideshow display to be specified as image attribute information, a more flexible slideshow display can be achieved. Note that in this embodiment, file storage intended for slideshow display is enabled by extending the PrimaryItemBox. However, any different extension method can be used, as long as it can store slideshows.

[0128] The embodiments illustrate examples of image file creation processing and the creation processing of metadata for a slideshow stored in the image file. For example... Figure 6 or Figure 14 As shown, the HEIF image files created in each embodiment have ftyp, meta, and mdat ( Figure 6 The metadata storage area 602 (MetaBox(meta)) and the encoded data storage area 611 (MediaDataBox(mdat)) are arranged in the top-level structure. However, the HEIF file created by the image file creation device is not limited to this internal structure. For example, any of the embodiments described above can be performed, thereby enabling the creation of HEIF files using the metadata of the MovieBox (moov) and also storing motion image data.

[0129] In HEIF, an HEIF file containing a sequence of image still images that are sequentially continuous in time requires defining the continuous still images as video tracks within itself, enabling applications that display the images to perform continuous display processing. In addition to the meta tag, the file structure may also require MOOV metadata. In the various embodiments described above, an HEIF file is created that includes information about a slideshow of multiple image data within the meta tag. That is, in the creation of image files that include settings for a slideshow (where the user selects multiple arbitrary images and determines an arbitrary order and display time (time period)), an HEIF file can be created more efficiently compared to generating an HEIF file that stores an image sequence.

[0130] Furthermore, in the various embodiments described above, HEIF was exemplified as a file format. However, such a file, capable of storing multiple image files and maintaining metadata associated with the image files, can be applied to other formats.

[0131] (Other embodiments)

[0132] This invention can be implemented by supplying a program for implementing one or more functions of the above embodiments to a system or device via a network or storage medium, and causing one or more processors in the computer of the system or device to read and execute the program. This invention can also be implemented by a circuit (e.g., an ASIC) for implementing one or more functions.

[0133] In the descriptions of the various embodiments above, the process of creating image files has been described. Figure 2 And the processing of the created image files (etc.) and reproduction. Figure 20 Examples of processing (e.g., image file creation device 100) performed by the same device, but these processes can be performed by different devices. That is, an image file reproduction device that receives an image file created by the image file creation device 100 via wired or wireless communication can analyze the received image file and perform... Figure 20 The image file is then reproduced through processing.

[0134] This invention is not limited to the embodiments described above, and various changes and modifications can be made within the spirit and scope of this invention. Therefore, the appended claims are included to inform the public of the scope of this invention.

[0135] This application claims priority to Japanese Patent Application No. 2019-123136, filed July 1, 2019; Japanese Patent Application No. 2019-180721, filed September 30, 2019; and Japanese Patent Application No. 2020-000990, filed January 7, 2020, which are incorporated herein by reference.

Claims

1. An image file generation device for generating image files conforming to the ISO base media file format, i.e., ISOBMFF, wherein the image file includes a data area for storing multiple still images and a metadata area for storing metadata as information related to the multiple still images, the image file generation device comprising: A selection component is used to select, from the plurality of still images stored in the data area of ​​the image file, a slideshow target image to be displayed sequentially via a slideshow. The first generating component is used to generate a first frame including recognition information for each of the plurality of still images and a second frame including information in the data area storing the position of the image corresponding to the recognition information; The second generation component is configured to generate a third frame including recognition information for each image in the slideshow target image selected from the plurality of still images, wherein the recognition information for each image in the slideshow target image is described in the first frame; and The third generation component is used to generate an image file that stores the first frame, the second frame, and the third frame in the metadata area, and also stores the position information and information indicating the display order of the target images in the slideshow in the metadata area. The image file will also include multiple still images of the target image for the slideshow stored in the data area, and The second box indicates that the slideshow target image selected from the plurality of still images is a group of items for the slideshow.

2. The image file generating device according to claim 1, wherein, The first generating component sets a derived image referencing the target image of the slideshow in the first frame, and The third generation component generates an image file in the metadata area that stores information indicating the display order of the target images in the slideshow as descriptive information of the derived images.

3. The image file generation device according to claim 2, wherein, The third generation component generates an image file in the metadata area that stores information used to associate the identification information with the attribute information of the image corresponding to the identification information as the attribute information of the derived image.

4. The image file generating device according to claim 1, wherein, The second generating component generates the third frame, which includes information indicating the display order of the target images in the slideshow.

5. The image file generation device according to claim 1, It also includes a fourth generation component for generating a fourth frame that includes attribute information of an image corresponding to the identification information and information for associating the identification information with the attribute information of the image corresponding to the identification information.

6. The image file generation device according to claim 1, It also includes a fourth generation component for generating a fourth frame containing attribute information of the group of target images for the slideshow obtained by grouping, and information for associating the group's identification information with the attribute information of the group corresponding to the identification information of the group.

7. The image file generating device according to claim 1, wherein, The third generation component also stores information used to indicate the display time of each image in the target image of the slideshow in the metadata area.

8. The image file generating device according to claim 1, wherein, The image file is in the High Efficiency Image File Format (HEIF).

9. The image file generating device according to claim 8, wherein, The image file also includes information for specifying the target image for the slideshow in the PrimaryItemBox area of ​​the metadata area.

10. The image file generating device according to claim 9, wherein, The information used to specify the target image of the slideshow is group identification information used to identify the group of the target image of the slideshow.

11. The image file generating apparatus according to claim 8, wherein, The third box is an EntityToGroupBox used to describe a group of entities used to identify the target image of the slideshow. The EntityToGroupBox includes group type information of the slideshow group used to identify the target image of the slideshow and the generated identification information.

12. The image file generating apparatus according to claim 11, wherein, The EntityToGroupBox indicates that the group type of the EntityToGroupBox is "slid".

13. The image file generating apparatus according to claim 11, wherein, The EntityToGroupBox is included in the top layer of the meta box (MetaBox) in the image file.

14. The image file generating device according to claim 1, wherein, The third generation component stores information related to the image region in the image file in the metadata region when the target image of the slideshow is displayed.

15. The image file generating device according to claim 1, wherein, The third generation component stores information about the effect of image switching when displaying the target image of the slideshow in the metadata area of ​​the image file.

16. The image file generating device according to claim 1, wherein, The third generation component stores information about the display position of each image in the metadata area of ​​the image file when the target image of the slideshow is displayed.

17. The image file generating device according to claim 1, wherein, It also includes a setting component for setting information based on user operations to indicate the display order of target images in the slideshow.

18. A computer-readable storage medium storing a program for causing a computer to function as an image file generating device according to any one of claims 1 to 17.

19. An image file generation method for generating an image file conforming to the ISO base media file format, i.e., ISOBMFF, wherein the image file includes a data area for storing multiple still images and a metadata area for storing metadata as information related to the multiple still images, the image file generation method comprising: Select the target image for the slideshow to be displayed sequentially in the slideshow from the plurality of still images stored in the data area of ​​the image file; Generate a first bounding box including recognition information for each of the plurality of still images and a second bounding box including information in the data area storing the location of the image corresponding to the recognition information; Generate a third frame including recognition information for each image in the slideshow target image selected from the plurality of still images, wherein the recognition information for each image in the slideshow target image is described in the first frame; and An image file is generated that stores the first box, the second box, and the third box in the metadata area, and also stores the location information and information indicating the display order of the target images for the slideshow in the metadata area. The image file will also include a plurality of still images of the target image of the slideshow stored in the data area, and The second box indicates that the slideshow target image selected from the plurality of still images is a group of items for the slideshow.

20. An image file processing apparatus for processing image files conforming to the ISO base media file format, i.e., ISOBMFF, the image file including a data area for storing a plurality of still images and a metadata area for storing metadata as information related to the plurality of still images, the image file processing apparatus comprising: The first acquisition component is used to acquire from the image file the recognition information of each image in the slide show target image among the plurality of still images to be displayed continuously by a slide show, as well as the information in the data area that stores the position of the image corresponding to the recognition information; The identification information is obtained from boxes in the metadata area, and information for indicating the display order of the target images in the slideshow is also obtained from the metadata area; The second acquisition component is configured to acquire the slideshow target image from the data area based on the identification information and the location information; and A display component is used to display the acquired slideshow target images according to the display order. The box indicates that the slideshow target image selected from the plurality of still images is a group of items for the slideshow.

21. An image file processing method for processing image files conforming to the ISO base media file format, i.e., ISOBMFF, wherein the image file includes a data area for storing multiple still images and a metadata area for storing metadata as information related to the multiple still images, the image file processing method comprising: From the image file, obtain the identification information of each image in the slideshow target image among the plurality of still images to be displayed continuously in a slideshow, as well as the information in the data area that stores the position of the image corresponding to the identification information; The identification information is obtained from boxes in the metadata area, and information for indicating the display order of the target images in the slideshow is also obtained from the metadata area; Based on the identification information and the location information, the target image for the slideshow is obtained from the data area; and The acquired slideshow target images are displayed according to the specified display order. The box indicates that the slideshow target image selected from the plurality of still images is a group of items for the slideshow.

22. A computer-readable storage medium storing a program for causing a computer to function as an image file processing device according to claim 20.

Images