Patent Grant
11546566
The systems and methods described herein generally relate to presenting and viewing a spherical video segment.
Captured video segments may include content captured in multiple views with multiple perspectives. If users are able to choose their view point within the captured video segments during playback, they may miss content available in other views and/or areas of the captured video segments. Missing content may cause the user to have a less than satisfactory experience.
The disclosure herein relates to presenting and viewing a spherical video segment. A spherical video segment may include digital content presented in a three dimensional view including a 360-degree horizontal field of view and/or a 180-degree vertical field of view. The system and/or method described herein may be configured to obtain the spherical video segment from a repository of video segments. The system and/or method may determine an orientation of a two dimensional display based upon output signals generated via a sensor. The output signals may convey information related to the orientation of the display. A display field of view within the spherical video segment may be determined. The display field of view may be presented on the display based on the orientation of the display. For example, the display field of view may follow a portion of the 360-degree horizontal field of view (e.g., 90-degrees of the 360-degrees, such that the other 270-degrees of the horizontal field of view may not be within the display field of view) and a portion of the 180-degree vertical field of view (e.g., 45-degrees of the 180-degrees, such that the other 135-degrees of the vertical field of view may not be within the display field of view) based upon how the display is moved and/or oriented (e.g., if the display is angled up by a certain number of degrees, the display field of view may be determined to be angled up by the same number of degrees). The display field of view of the spherical video segment may be presented on the display for a user to view different angles and/or perspectives at any given point in time of the spherical video segment by moving the display in different directions and/or angles. The three dimensional view may include depth information associated with the spherical video segment. Zoom controls may be provided which may allow for the increase and/or decrease of visible degrees during playback within the display field of view of the spherical video segment.
In some embodiments, the display field of view may be captured and/or recorded as a two dimensional video segment. User controls may be provided via the display and/or an application associated with presentation of the spherical video segment on the display that may allow the user viewing and/or consuming the spherical video segment to record the presented display field of view. For example, the user may choose to make a recording of the content of the two dimensional display of the display field of view as the user moves the display in different directions and/or orients the display at different angles. This may be referred to as a virtual camera, as the user may make as many recordings of the two dimensional display as the user wishes. The user controls may allow the user to start, pause, stop, and/or allow for other controls to control capture of the display field of view as the two dimensional video segment (e.g., record in slow motion, etc.). In this manner, the user may capture highlights and/or events of interest within the spherical video segment in a single two dimensional video segment. The two dimensional video segment may be stored as a separate video segment than the spherical video segment. The two dimensional video segment may be shared with other users and/or consumers to view, such that the user and/or other consumers of the spherical video segment and/or the two dimensional video segment may not have to search for the highlights and/or events of interest on their own within the spherical video segment.
In some embodiments, one or more events of interest may be tagged and/or presented within the spherical video segment. Events of interest may include one or more of a highlight or a climax of the spherical video segment, something occurring within the spherical video segment apart from a focal (e.g., action) point of the spherical video segment, and/or other event of interest within the spherical video segment. The system and/or method may obtain tag information associated with the event of interest within the spherical video segment. The information may identify a point in time in the spherical video segment and a viewing angle within the spherical video segment at which the event of interest is viewable in the spherical video segment. While presenting the spherical video segment via the display, the system and/or method may determine, proximate to the point in time, whether the viewing angle of the event of interest is located within the display field of view. If the event of interest is outside the display field of view (e.g., with reference to the example above, if the event of interest is located within the 270-degrees of the horizontal field of view not within the display field of view and/or the 135-degrees of the vertical field of view not within the display field of view), alert information may be generated indicating that the event of interest for the spherical video segment may be located outside the field of view. A notification may be generated and presented within the display field of view to alert the user which direction to move and/or orient the display at which time during the spherical video segment in order to view the event of interest. The notification may be graphical (e.g., arrows, etc.), audible (e.g., spoken directions), and/or in any other form. Users may tag and/or mark the spherical video segment with their own events of interest to be stored and shared for future reference of the spherical video segment, either by the users themselves or for other consumers to view.
A system configured to present and view a spherical video segment may include one or more client computing platform(s). The server(s) and the client computing platform(s) may communicate in a client/server configuration, and/or via another configuration. The client computing platform(s) may include one or more processors configured by machine-readable instructions to execute computer program components. The computer program components may include a spherical segment component, an authentication component, an orientation component, a field of view component, a presentation component, a capture component, a notification component, and/or other components.
The spherical segment component may be configured to obtain the spherical video segment. The spherical video segment may be included within a repository of video segments. A repository of images and/or video segments may be available via the system. The repository of images and/or video segments may be stored within an electronic storage, one or more server(s), external resources, a cloud, and/or any other storage location. Individual images and/or video segments of the repository of images and/or video segments may be stored in different locations. The repository of images and/or video segments may be associated with different users. The video segments may include a compilation of videos, video segments, video clips, and/or still images.
In some embodiments, the spherical video segment may include tag information associated with an event of interest within the spherical video segment. The tag information may identify a point in time within the spherical video segment and a viewing angle within the spherical video segment at which the event of interest is viewable in the spherical video segment. The event of interest may include any occurrence within the spherical video segment such as a notable moment and/or interesting point in time within the spherical video segment duration. The event of interest may be a moment that a user wishes to share with other viewers and/or consumers of the spherical video segment (e.g., the user and/or other users may be interested in the moment and/or event of interest). For example, the event of interest may include one or more of a highlight or a climax of the spherical video segment, something occurring within the spherical video segment apart from a focal (e.g., action) point of the spherical video segment, and/or other event of interest within the spherical video segment.
The authentication component may be configured to authenticate a user associated with client computing platform(s) accessing the repository of images and/or video segments via the system. The authentication component may manage accounts associated with users and/or consumers of the system. The user accounts may include user information associated with users and/or consumers of the user accounts. User information may include information stored by client computing platform(s), server(s), and/or other storage locations.
The orientation component may be configured to determine the orientation of a display based on output signals of a sensor of client computing platform(s). For example, if one of client computing platform(s) is a mobile device (e.g., a smartphone), the orientation component may be configured to determine the orientation of the display based on the output signals of the client computing device when the user moves the smartphone in one or more directions (e.g., up, down, left, right, etc.). The orientation of the display may be indicated by a number of degrees in one or more directions. For example, the orientation may be defined in one or more of a Cartesian coordinate system, a cylindrical and/or polar coordinate system, a spherical and/or polar coordinate system.
The field of view component may be configured to determine a display field of view within the spherical video segment to be presented on the display based on the orientation of the display. The field of view component may be configured to determine the field of view within the spherical video segment to be presented on the display based on the orientation of the display including determining a viewing angle in the spherical video segment that corresponds to the orientation of the display. The field of view component may be configured to determine the field of view within the spherical video segment to be presented on the display based on the orientation of the display including identifying the display field of view within the spherical video segment that is present at the viewing angle. The display field of view may include a horizontal field of view (e.g., left and/or right), a vertical field of view (e.g., up and/or down), and/or other field of views.
The field of view component may be configured to, proximate to the point in time, determine whether the viewing angle of the event of interest is located within the display field of view. Proximate to the point in time at which the event of interest is viewable may include one or more of a predefined time period prior to the point in time at which the event of interest is viewable, a predefined time period after the point in time at which the event if viewable, and/or the point in time at which the event of interest is viewable. As discussed above, the display field of view may be determined on a recurring or ongoing basis. The display field of view may indicate a current field of view determined based upon the orientation of the display associated with client computing platform(s) during presentation of the spherical video segment. The display field of view may change one or more times over the course of presentation of the spherical video segment via the display. The display field of view may include the viewing angle visible to the user via the display at a current point in time, as numerous fields of view that are not visible to the user may be available at the current point in time (e.g., 180-degrees to the left or right of the display field of view may not be visible to the user via the display field of view unless the display is moved to the left or right). The field of view component may automatically alter the display field of view for the user automatically to display the event of interest and/or the user may alter the display field of view based upon the movements of the client computing platform(s).
The capture component may be configured to capture the display field of view as a two dimensional video segment. Capturing the display field of view as the two dimensional video segment may include recording the display field of view as the two dimensional video segment such that as the user is using the display associated with client computing platform(s) as a viewfinder for visual content included within the spherical video segment, the capture component may record and/or capture the user's actions and/or movements (e.g., the display field of view) throughout the spherical video segment via client computing platform(s). For example, as the user is viewing the spherical video segment via the display associated with client computing platform(s), the capture component may record the display field of view (e.g., the visual content being displayed on the display associated with client computing platform(s)), including any movements of the display field of view including when the user may move the display associated with client computing platform(s) to the left, right, up, and/or down, resulting in movement of the display field of view within the spherical video segment.
The notification component may be configured to, responsive to a determination proximate to the point in time that the viewing angle is outside the display field of view, generate alert information indicating the event of interest for the spherical video segment is located outside the display field of view. The alert information may indicate the location of the event of interest within the spherical video segment indicated by the tag information. The alert information may include the viewing angle associated with the tag information, the point in time associated with the tag information, and/or other information related to the event of interest indicated by and/or associated with the tag information.
The notification component may be configured to effectuate presentation of a notification based upon the alert information. The notification may include one or more of a graphical notification, an audible notification, a sensory notification, and/or other types of notifications. For example, the notification may include an alert message presented within the display field of view of the spherical video segment. The notification, for example, may include an alert sound audible to the user. An example sensory notification may include a vibration and/or light notification. The notification may indicate to the user that the user may be missing, has missed, and/or may be about to miss the event of interest of the spherical video segment that may be occurring outside the display field of view.
These and other objects, features, and characteristics of the present disclosure, as well as the methods of operation and functions of the related components of structure and the combination of parts and economies of manufacture, will become more apparent upon consideration of the following description and the appended claims with reference to the accompanying drawings, all of which form a part of this specification, wherein like reference numerals designate corresponding parts in the various figures. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of the any limits. As used in the specification and in the claims, the singular form of “a”, “an”, and “the” include plural referents unless the context clearly dictates otherwise.
In some embodiments, the display field of view may be captured and/or recorded as a two dimensional video segment. User controls may be provided via the display and/or an application associated with presentation of the spherical video segment on the display that may allow the user viewing and/or consuming the spherical video segment to record the presented display field of view. For example, the user may choose to make a recording of the content of the two dimensional display of the display field of view as the user moves the display in different directions and/or orients the display at different angles. This may be referred to as a virtual camera, as the user may make as many recordings of the two dimensional display as the user wishes. The user controls may allow the user to start, pause, stop, and/or allow for other controls to control capture of the display field of view as the two dimensional video segment (e.g., record in slow motion, etc.). In this manner, the user may capture highlights and/or events of interest within the spherical video segment in a single two dimensional video segment. The two dimensional video segment may be stored as a separate video segment than the spherical video segment. The two dimensional video segment may be shared with other users and/or consumers to view, such that the user and/or other consumers of the spherical video segment and/or the two dimensional video segment may not have to search for the highlights and/or events of interest on their own within the spherical video segment.
In some embodiments, one or more events of interest may be tagged and/or presented within the spherical video segment. Events of interest may include one or more of a highlight or a climax of the spherical video segment, something occurring within the spherical video segment apart from a focal (e.g., action) point of the spherical video segment, and/or other event of interest within the spherical video segment. The system and/or method may obtain tag information associated with the event of interest within the spherical video segment. The information may identify a point in time in the spherical video segment and a viewing angle within the spherical video segment at which the event of interest is viewable in the spherical video segment. While presenting the spherical video segment via the display, the system and/or method may determine, proximate to the point in time, whether the viewing angle of the event of interest is located within the display field of view. If the event of interest is outside the display field of view (e.g., with reference to the example above, if the event of interest is located within the 270-degrees of the horizontal field of view not within the display field of view and/or the 135-degrees of the vertical field of view not within the display field of view), alert information may be generated indicating that the event of interest for the spherical video segment may be located outside the field of view. A notification may be generated and presented within the display field of view to alert the user which direction to move and/or orient the display at which time during the spherical video segment in order to view the event of interest. The notification may be graphical (e.g., arrows, etc.), audible (e.g., spoken directions), and/or in any other form. Users may tag and/or mark the spherical video segment with their own events of interest to be stored and shared for future reference of the spherical video segment, either by the users themselves or for other consumers to view.
As illustrated in
One or more physical processor(s) 124 may be configured to execute machine-readable instructions. Executing machine-readable instructions 105 may cause the one or more physical processor(s) 124 to effectuate presentation of the spherical video segment. Machine-readable instructions 105 may include one or more computer program components such as spherical segment component 106, authentication component 108, orientation component 110, field of view component 112, presentation component 114, capture component 116, notification component 118, and/or other components.
In some implementations, client computing platform(s) 102 may be configured to provide remote hosting of the features and/or function of machine-readable instructions 105 to one or more server(s) 104 that may be remotely located from client computing platform(s) 102. However, in some implementations, one or more features and/or functions of client computing platform(s) 102 may be attributed as local features and/or functions of one or more server(s) 104. For example, individual ones of server(s) 104 may include machine-readable instructions (not shown in
Client computing platform(s) 102 may include one or more of a cellular telephone, a smartphone, a digital camera, a laptop, a tablet computer, a desktop computer, a television set-top box, smart TV, a gaming console, and/or other computing platforms.
Client computing platform(s) 102, server(s) 104, and/or external resources 120 may be operatively linked via one or more electronic communication links. For example, such electronic communication links may be established, at least in part, via a network such as the Internet and/or other networks. It will be appreciated that this is not intended to be limiting and that the scope of this disclosure includes implementations in which client computing platform(s) 102, server(s) 104, and/or external resources 120 may be operatively linked via some other communication media.
Spherical segment component 106 may be configured to obtain the spherical video segment. The spherical video segment may be included within a repository of video segments. A repository of images and/or video segments may be available via system 100. The repository of images and/or video segments may be stored within electronic storage 122, one or more server(s) 104, external resources 120, a cloud, and/or any other storage location. Individual images and/or video segments of the repository of images and/or video segments may be stored in different locations. The repository of images and/or video segments may be associated with different users. The video segments may include a compilation of videos, video segments, video clips, and/or still images. While the present disclosure may be directed to previously captured spherical video and/or spherical video segments captured by one or more image capturing devices, one or more other implementations of system 100, client computing platform(s) 102, and/or server(s) 104 may be configured for other types of media items. Other types of media items may include one or more of audio files (e.g., music, podcasts, audio books, and/or other audio files), multimedia presentations, photos, slideshows, and/or other media files. The spherical video segment may be received from one or more storage locations associated with client computing platform(s) 102, server(s) 104, and/or other storage locations where spherical video segments may be stored.
Authentication component 108 may be configured to authenticate a user associated with client computing platform(s) 102 accessing the repository of images and/or video segments via system 100. Authentication component 108 may manage accounts associated with users and/or consumers of system 100. The user accounts may include user information associated with users and/or consumers of the user accounts. User information may include information stored by client computing platform(s) 102, server(s) 104, and/or other storage locations.
User information may include one or more of information identifying users and/or consumers (e.g., a username or handle, a number, an identifier, and/or other identifying information), security login information (e.g., a login code or password, a user ID, and/or other information necessary for the user to access server(s) 104), system usage information, external usage information (e.g., usage of one or more applications external to system 100 including one or more of online activities such as in social networks and/or other external applications), subscription information, a computing platform identification associated with the user and/or consumer, a phone number associated with the user and/or consumer, privacy settings information, and/or other information related to users and/or consumers.
Authentication component 108 may be configured to obtain user information via one or more client computing platform(s) 102 (e.g., user input via a user interface, etc.). If a user and/or consumer does not have a preexisting user account associated with system 100, a user and/or consumer may register to receive services provided by system 100 via a website, web-based application, mobile application, and/or user application. Authentication component 108 may be configured to create a user ID and/or other identifying information for a user and/or consumer when the user and/or consumer registers. The user ID and/or other identifying information may be associated with one or more client computing platform(s) 102 used by the user and/or consumer. Authentication component 108 may be configured to store such association with the user account of the user and/or consumer. A user and/or consumer may associate one or more accounts associated with social network services, messaging services, and the like with an account provided by system 100.
If the spherical video segment is stored in a storage location external to client computing platform(s) 102 and/or is spherical segment component is located within one or more server(s) 104, spherical segment component 106 may effectuate transmission of the spherical video segment to client computing platform(s) 102 associated with the user and/or consumer. The spherical video segment may be transmitted to client computing platform(s) 102 on which users may consume the spherical video segment. Spherical segment component 106 may be configured to host the spherical video segment over a network. For example, the spherical video segment may be hosted over the internet such that users may access the spherical video segment via the internet. Hosting the spherical video segment over the internet may include uploading and/or storing the spherical video segment on one or more server(s) 104 wherein the servers process requests and/or deliver the spherical video segment to client computing platform(s) 102. This may include serving separate digital files for the spherical video segment, streaming the spherical video segment, and/or other delivery mechanisms. Spherical segment component 106 may be configured to host the spherical video segment over a network by communicating information (e.g., via streaming digital content data, and/or other visual information) from server(s) 104 to client computing platform(s) 102 for presentation on one or more displays associated with client computing platform(s) 102. The digital content transmitted to a given client computing platform 102 may correspond to the spherical video segment being presented for consumption by user at the given client computing platform 102.
Users may consume the spherical video segment by viewing the spherical video segment via client computing platform(s) 102 and/or an associated display device. Client computing platform(s) 102 may include one or more display devices configured to display the spherical video segment. Client computing platform(s) 102 may include a two dimensional display configured to present two dimensional images. For example, the spherical video segment may be presented via the two dimensional display in a two dimensional format, rather than a three dimensional format such that the user associated with client computing platform(s) 102 may view the spherical video segment in the two dimensional format. Client computing platform(s) 102 may include a sensor configured to generate output signals conveying information related to an orientation of the display. The orientation of the display may refer to a relative position of the display. The orientation of the display may be indicated by a number of degrees in one or more directions. For example, the orientation may be defined in one or more of a Cartesian coordinate system, a cylindrical and/or polar coordinate system, a spherical and/or polar coordinate system.
A spherical video segment may include a captured three dimensional video segment that may be viewed, tagged, edited, and/or distributed. For example, the spherical video segment may include a playback of a live captured video (e.g., captured via one or more cameras). The spherical video segment may include multiple views such that at least a portion of the spherical video segment is outside a display field of view of a user viewing the spherical video segment at a given point in time via the display associated with client computing platform(s) 102. For example, the spherical video segment may include one or more of a 360-degree horizontal field of view, a 180-degree vertical field of view, and/or other views. The display associated with client computing platform(s) 102 may display only a portion of the spherical video segment (e.g., the display may only display a portion of the 360-degree horizontal field of view and/or a portion of the 180-degree vertical field of view). As such, other portions of the spherical video segment that are not displayed via the display associated with client computing platform(s) 102 at a given point in time may still be available to view.
Orientation component 108 may be configured to determine the orientation of the display based on the output signals of the sensor of client computing platform(s) 102. For example, if one of client computing platform(s) 102 is a mobile device (e.g., a smartphone), orientation component 108 may be configured to determine the orientation of the display based on the output signals of client computing device 102 when the user moves the smartphone in one or more directions (e.g., up, down, left, right, etc.). As discussed above, the orientation of the display may be indicated by a number of degrees in one or more directions. For example, the orientation may be defined in one or more of a Cartesian coordinate system, a cylindrical and/or polar coordinate system, a spherical and/or polar coordinate system.
Field of view component 112 may be configured to determine a display field of view within the spherical video segment to be presented on the display based on the orientation of the display. Field of view component 112 may be configured to determine the field of view within the spherical video segment to be presented on the display based on the orientation of the display including determining a viewing angle in the spherical video segment that corresponds to the orientation of the display. Field of view component 112 may be configured to determine the field of view within the spherical video segment to be presented on the display based on the orientation of the display including identifying the display field of view within the spherical video segment that is present at the viewing angle. The display field of view may include a horizontal field of view (e.g., left and/or right), a vertical field of view (e.g., up and/or down), and/or other field of views.
Field of view component 112 may be configured to determine the display field of view within the spherical video segment based on how the user is holding and/or moving the display associated with client computing platform(s) 102. For example, the user may move, turn, and/or orient the display of client computing platform(s) 102 to change his or her field of view based on an angle and/or direction of the orientation of the display associated with client computing platform(s) 102. The orientation of the display may reflect the viewing angle in the spherical video segment. For example, if the user holds the display associated with client computing platform(s) 102 straight ahead such that the display associated with client computing platform(s) 102 is oriented at a 90-degree vertical angle relative to a surface level (e.g., the ground at 0-degrees and/or the X-axis), the display field of view within the spherical video segment to be presented on the display may be a 90-degree vertical display field of view. The viewing angle in the spherical video segment that corresponds to the orientation of the display may then be the 90-degree vertical viewing angle. If the user orients the display associated with client computing platform(s) 102 at a 75-degree vertical angle relative to the surface level (e.g., the ground at 0-degrees and/or the X-axis) while moving the display associated with client computing platform(s) 102 100-degrees to the right from an initial point (e.g., the initial point may be 0-degrees horizontally), the display field of view within the spherical video segment to be presented on the display may be a 75-degree vertical angle display field of view (e.g., the display field of view may be tilted down towards the surface level) and 100-degrees to the right from the initial point. The viewing angle in the spherical video segment that corresponds to the orientation of the display may then be the 75-degree vertical viewing angle, turned 100-degrees to the right.
Presentation component 114 may be configured to effectuate presentation of the display field of view of the spherical video segment on the display. The user associated with client computing platform(s) 102 may view the spherical video segment on the display of client computing platform(s) 102. The determination of the orientation of the display and the determination of the display field of view within the spherical video segment for presentation on the display may occur recursively during playback of the spherical video segment. In this manner, whichever direction client computing platform(s) 102 moves and/or is oriented, presentation component 114 may be configured to effectuate presentation of the display field of view of the spherical video segment on the display in real-time. For example, if at 30 seconds into the spherical video segment, the user associated with client computing platform(s) 102 moves the display associated with client computing platform(s) 102 to the right by 30-degrees (e.g., 30-degrees horizontally) relative to a starting position and/or starting orientation of the display associated with client computing platform(s) 102, the spherical video segment may be displayed on the display associated with client computing platform(s) 102 to present the spherical video segment at 30-degrees to the right (e.g., horizontally) relative to an initial viewing angle in the spherical video segment. This may occur recursively such that the user may move the display associated with client computing platform(s) 102 in any direction to view different angles and/or perspectives of the spherical video segment at any given point in time.
Recursive determinations of the orientation of the display and the display field of view within the spherical video segment for presentation on the display may facilitate use of the display by the user as a viewfinder for visual content included within the spherical video segment. The viewfinder for the spherical video segment may represent the ability for the user to move the display associated with client computing platform(s) 102 on which the spherical video segment is displayed in order to view different angles and/or perspectives at any given point in time during the spherical video segment. For example, at each point in time during the spherical video segment, the 360-degree horizontal field of view and the 180-degree vertical field of view may be available for the user to view via the display associated with client computing platform(s) 102 by moving, rotating, and/or otherwise orienting the display associated with client computing platform(s) 102 in various directions and/or angles to view different moments and/or events within the spherical video segment. While the user is viewing the spherical video segment at a current position (e.g., an initial position), an event may be taking place 180-degrees to the right or left (e.g., horizontally) of the current position at that moment in time (e.g., 25 seconds into the spherical video segment). The user may move the display associated with client computing platform(s) 102 to explore other areas of the spherical video segment at the 25-second mark of the spherical video segment. The user may pause the spherical video segment at a particular point in time (e.g., 2 seconds into the spherical video segment) via one or more user controls, as will be discussed in further detail below, in order to move the display associated with client computing platform(s) 102 in various directions to explore the visual content captured within the spherical video segment in part and/or its entirety at the particular point in time (e.g., 2 seconds into the spherical video segment). Visual content and/or events included within the spherical video segment may include capture of particular objects (e.g., people, animals, landmarks, etc.), actions (e.g., a sporting event, riding a bicycle, etc.), landscapes (e.g., scenery, etc.), and/or other visual content and/or events that may be captured. In this manner, the user may facilitate use of the display as the viewfinder for visual content and/or events included within the spherical video segment.
By way of illustration,
Returning to
Capture component 116 may be configured to capture a single field of view over a span of time. For example, even if the display associated with client computing platform(s) 102 is moved and/or oriented in different directions, capture component 116 may record and/or capture only a single field of view. If the initial vertical field of view is a 90-degree vertical field of view and the initial horizontal field of view is 0-degrees, then capture component 116 may be configured to capture that field of view for the entire length of the spherical video segment and/or a particular length of time. User controls, as will be discussed in further detail below, may be used to configure recording and/or editing of the two dimensional video segment and/or post-capture of the two dimensional video segment.
As discussed above, the spherical video segment may be a three dimensional video segment, while the display associated with client computing platform(s) 102 may be a two dimensional display. As such, capture component 116 may be configured to capture and/or record the display field of view and create a separate video segment as the two dimensional video segment other than the spherical video segment.
Capture component 116 may be configured to store the two dimensional video segment. The two dimensional video segment may be stored via electronic storage 122, a cloud, and/or other storage device associated with system 100 and/or server(s) 104. The two dimensional video segment may be included within the repository of video segments discussed above. In this manner, the two dimensional video segment may be available for playback to view by other users and/or consumers. System 100 may effectuate presentation of the two dimensional video segment on the display associated with client computing platform(s) 102 for playback. System 100 may effectuate transmission of the two dimensional video segment to one or more client computing platform(s) 102 associated with the user and/or other viewers and/or consumers. In this manner, a user may capture moments and/or events of interest within the spherical video segment as the two dimensional video segment and share the two dimensional video segment with other viewers and/or consumers. The two dimensional video segment may include moments and/or events of interest which the user preferred in order to view the spherical video segment in the future in an easier and more efficient manner, such that the user and/or other viewers may not be required to search through the entirety of the spherical video segment (e.g., the three dimensional video segment) to view such moments and/or events of interest at a particular point in time.
As discussed above, the display may include use by the user as the viewfinder for visual content included within the spherical video segment. The display and/or the viewfinder may include one or more user controls configured to be actuated by the user to control capture of the display field of view as the two dimensional video segment. The one or more user controls may include one or more of a record control, a stop control, a play control, a pause control, controls to fast forward and/or rewind through the spherical video segment and/or the two dimensional video segment, a save control, and/or other user controls that may be used to control capture of the two dimensional video segment (e.g., a control to record the two dimensional video segment in slow motion, etc.). The one or more user controls may be included within the display, within the viewfinder (e.g., associated with display of the spherical video segment), on client computing platform(s) 102, and/or may be included within and/or on other devices and/or applications capable of displaying the spherical video segment and/or recording the two dimensional video segment. The one or more user controls may include one or more buttons associated with client computing platform(s) 102 and/or an application capable of displaying the spherical video segment, levers, switches, and/or any other actuator that may be actuated by the user to control capture of the two dimensional video segment.
By way of illustration,
Referring back to
The tag information may include one or more of a tag, a comment including text, an emoji, and/or an image, and/or other information associated with the tag information and/or the event of interest. In some implementations, users may submit tag information associated with the event of interest via a force touch and/or other inputs. The tag information may be inputted on and/or via one or more user interfaces via the display associated with client computing platform(s) 102. For example, a user may tap and/or touch the display associated with client computing platform(s) 102 while viewing the spherical video segment to mark and/or tag the point in time and the viewing angle (e.g., location) of the event of interest within the spherical video segment. The user may simply tap the display to mark and/or tag the event of interest and/or may enter a comment associated with the mark and/or tag using a keypad and/or other input device associated with client computing platform(s) 102. System 100 may receive the tag information from client computing platform(s) 102.
The tag information may identify the point in time in the spherical video segment at which the event of interest is viewable in the spherical video segment. System 100 may receive the point in time from the user such that the user may select and/or choose where in the spherical video segment the event of interest occurs, begins, and/or is about to begin. For example, the user may select the point in time within the spherical video segment such that a timestamp may be associated with the event of interest. The point in time may include a single point in time, a range of time, multiple points in time, and/or other point in time indications.
The tag information may identify a viewing angle within the spherical video segment at which the event of interest is viewable in the spherical video segment. The viewing angle may reference a location within the spherical video segment in which the event of interest is viewable. System 100 may receive the viewing angle from the user such that the user may select and/or choose where in the spherical video segment the event of interest occurs, begins, and/or is about to begin. For example, the user may select the viewing angle within the spherical video segment such that a location within the spherical video segment may be associated with the event of interest. The viewing angle may include a number of degrees in a horizontal field of view and/or a number of degrees in a vertical field of view. The viewing angle may include one or more of a range of viewing angles, an individual view point based upon the viewing angle, a view point and its vicinity, and/or other viewing angles associated with the event of interest. The viewing angle may be relative to the display field of view.
The viewing angle may include one or more dimensions identifying where within the spherical video segment the event of interest is located, and/or what field(s) of view will be able to observe the portion of the spherical video segment at which the event of interest is viewable. For example, the viewing angle may include one or more of a horizontal field of view (e.g., left to right), a vertical field of view (e.g., height, up, and/or down), and/or other location information. The viewing angle and/or information associated with the viewing angle may be defined by one or more of a Cartesian coordinate system, a cylindrical and/or polar coordinate system, a spherical and/or polar coordinate system, other coordinate system, and/or other data.
The tag information including the point in time and the viewing angle at which the event of interest is viewable may be stored within electronic storage 122 and/or may be stored within an electronic storage associated with server(s) 104. Spherical segment component 106 may be configured to obtain the tag information associated with the event of interest. If stored on one or more server(s) 104, the tag information may be transmitted over the network to one or more client computing platform(s) 102 such that it may be received by spherical segment component 106.
Upon presentation component 114 presenting the display field of view of the spherical video segment on the display, as discussed above, field of view component 112 may be configured to, proximate to the point in time, determine whether the viewing angle of the event of interest is located within the display field of view. Proximate to the point in time at which the event of interest is viewable may include one or more of a predefined time period prior to the point in time at which the event of interest is viewable, a predefined time period after the point in time at which the event if viewable, and/or the point in time at which the event of interest is viewable. As discussed above, the display field of view may be determined on a recurring or ongoing basis. The display field of view may indicate a current field of view determined based upon the orientation of the display associated with client computing platform(s) 102 during presentation of the spherical video segment. The display field of view may change one or more times over the course of presentation of the spherical video segment via the display. The display field of view may include the viewing angle visible to the user via the display at a current point in time, as numerous fields of view that are not visible to the user may be available at the current point in time (e.g., 180-degrees to the left or right of the display field of view may not be visible to the user via the display field of view unless the display is moved to the left or right). Field of view component 114 may automatically alter the display field of view for the user automatically to display the event of interest and/or the user may alter the display field of view based upon the movements of the client computing platform(s).
The display field of view may include one or more visible ranges of viewing angles within the spherical video segment for a window in time within the spherical video segment. The window of time within the spherical video segment may include and/or correspond to the proximate point in time associated with the point in time. The window of time may correspond to the point in time and/or range of time relevant to the event of interest. The window of time within the spherical video segment may include a separate or partially separate window of time, a period of time associated with the tag information, the segment duration, and/or another point in time, portion of time, and/or range of time within the spherical video segment. For example, the window of time may include a portion of the duration of the spherical video segment that begins prior to the period of time begins such that the viewing angle may indicate the display field of view for the user prior to the beginning of the period of time for the event of interest indicated by the tag information. The window of time may be determined by field of view component 112, and/or selected and/or otherwise indicated by a user.
Field of view component 112 may be configured to determine whether the field of view associated with the tag information is located within and/or outside the display field of view proximate to the point in time. In some implementations, within the display field of view may include completely and/or partially within the display field of view. Outside the display field of view may include completely and/or partially outside, and/or off-centered within the display field of view. In some implementations, the determination of whether the viewing angle associated with the tag information is located within and/or outside the display field of view may be determined in an ongoing and/or reoccurring manner for the duration of the spherical video segment.
Notification component 118 may be configured to, responsive to a determination proximate to the point in time that the viewing angle is outside the display field of view, generate alert information indicating the event of interest for the spherical video segment is located outside the display field of view. The alert information may indicate the location of the event of interest within the spherical video segment indicated by the tag information. The alert information may include the viewing angle associated with the tag information, the point in time associated with the tag information, and/or other information related to the event of interest indicated by and/or associated with the tag information. If notification component 118 is on one or more server(s) 104, notification component 118 may be configured to effectuate transmission of the alert information over the network to one or more client computing platform(s) 102 associated with the display on which the spherical video segment may be presented.
Notification component 118 may be configured to effectuate presentation of a notification based upon the alert information. The notification may include one or more of a graphical notification, an audible notification, a sensory notification, and/or other types of notifications. For example, the notification may include an alert message presented within the display field of view of the spherical video segment. The notification, for example, may include an alert sound audible to the user. An example sensory notification may include a vibration and/or light notification. The notification may indicate to the user that the user may be missing, has missed, and/or may be about to miss the event of interest of the spherical video segment that may be occurring outside the display field of view.
A visible notification may be presented at and/or near the center of the display field of view, in the periphery of the display field of view, and/or at other locations within the display field of view of spherical video segment. An audible notification may include a notification sound played by a speaker, within one or more earphones, within one or both sides of headphones, and/or other audible notifications. A sensory notification may be delivered via client computing platform(s) 102, one or more display devices associated with client computing platform(s) 102, one or more control (e.g., user interfacing) devices associated with client computing platform(s) 102, and/or other devices.
The notification may include a direction to orient the display to include the viewing angle within the display field of view. The notification may indicate where within the spherical video segment the event of interest is taking and/or is about to take place. The notification may include a direction to orient the display to include the viewing angle associated with the tag information within the display field of view. The notification may include a number of degrees to angle and/or move the display such that the event of interest may be displayed within the display field of view. For example, proximate to the point in time associated with the tag information, a graphical notification may include “Look to your left to see something cool!” The graphical notification may include an arrow pointing in the direction to move the display such that the event of interest may be displayed within the display field of view. An audible notification, for example, may include a spoken message of “Don't miss what is happening to your right” and/or a sound may be played in the right ear of the user to indicate to the user that the user should look to the right. The sound may be played in the left ear of the user to indicate to the user that the user should look to the left.
The notification may include the point in time at which the event of interest is viewable. The notification may indicate the point in time within the spherical video segment the event of interest is taking place, is about to take place, and/or did take place. For example, the graphical notification may include “Look to your left to see something cool at 2 minutes and 8 seconds!” The graphical notification may include a timer that counts down until the point in time. The audible notification, for example, may include a spoken message of “Don't miss what is happening to your right in 10 seconds.” Notification component 118 may be configured to effectuate presentation of the notification after the point in time has passed. System 100 may provide user controls, as discussed above, to allow the user associated with client computing platform(s) 102 to fast forward, rewind, view in slow motion, and/or other user controls to control display and/or manipulation of the spherical video segment.
By way of illustration,
As discussed above, system 100 may receive, via client computing platform(s) 102 associated with the display, the tag information associated with the event of interest such that the user may be reminded of the event of interest next time the user views the spherical video segment and/or so other viewers and/or consumers may not miss the event of interest while viewing the spherical video segment. While the consumer other than the user views the spherical video segment, the consumer may wish to mark and/or tag, in a similar manner as discussed above, a second event of interest within the spherical video segment for his or her reference and/or for other viewers and/or consumers. The tag information associated with the second event of interest may identify a second point in time in the spherical video segment and a second viewing angle within the spherical video segment at which the second event of interest may be viewable within the spherical video segment. The tag information associated with the second event of interest may be stored within electronic storage 122 and/or other storage device. In a similar manner as discussed above, system 100 may effectuate transmission of the tag information associated with the second event of interest to a second client computing platform associated with a second consumer, such that the second consumer may view the spherical video segment via a display associated with the second client computing platform. Notifications may be presented for the event of interest and/or the second event of interest as the second consumer views the spherical video segment. The spherical video segment may include any number of events of interest via the tag information, which may be received by the same user and/or other users. Any number of notifications for individual events of interest may be presented for future viewers of the spherical video segment.
In some implementations, the tag information may be used for editing the spherical video segment. For example, editing the spherical video segment may include one or more of: selecting and/or compiling a two dimensional video segment of the spherical video segment; augmenting (e.g., removing content, etc.), enhancing (e.g., color correcting, etc.), and/or otherwise refining one or more portions and/or sections (e.g., frames, and/or other portions and/or sections) of the spherical video segment; and/or otherwise editing one or more portions and/or sections (e.g., frames, and/or other portions and/or sections) of the spherical video segment. The tag information for the spherical video segment may indicate one or more portions and/or sections (e.g., frames, and/or other portions and/or sections) of the spherical video segment that should be edited. The tag information may be used to select portions and/or sections from the spherical video segment to edit.
Returning to
The external resources 120 may include sources of information, hosts and/or providers of virtual spaces outside of system 100, external entities participating with system 100, external entities for digital content and/or digital content platforms, and/or other resources. In some implementations, some or all of the functionality attributed herein to external resources 120 may be provided by resources included in system 100.
The client computing platform(s) 102 may include electronic storage 122, one or more processor(s) 124, and/or other components. The client computing platform(s) 102 may include communication lines or ports to enable the exchange of information with a network and/or other servers and/or computing platforms. Illustration of client computing platform(s) 102 in
One or more server(s) 104 may include an electronic storage, one or more processors, computer readable instructions configured to execute components 106-118.
Electronic storage 122 may comprise electronic storage media that electronically stores information. The electronic storage media of electronic storage 122 may include one or both of system storage that is provided integrally (i.e., substantially non-removable) with client computing platform(s) 102 and/or removable storage that is removably connectable to client computing platform(s) 102 via, for example, a port or a drive. A port may include a USB port, a firewire port, and/or other port. A drive may include a disk drive and/or other drive. Electronic storage 122 may include one or more of optically readable storage media (e.g., optical disks, etc.), magnetically readable storage media (e.g., magnetic tape, magnetic hard drive, floppy drive, etc.), electrical charge-based storage media (e.g., EEPROM, RAM, etc.), solid-state storage media (e.g., flash drive, etc.), and/or other electronically readable storage media. The electronic storage 122 may include one or more virtual storage resources (e.g., cloud storage, a virtual private network, and/or other virtual storage resources). Electronic storage 122 may store software algorithms, information determined by processor(s) 124, information received from client computing platform(s) 102, information received from server(s) 104, and/or other information that enables client computing platform(s) 102 to function as described herein.
Processor(s) 124 are configured to provide information processing capabilities in client computing platform(s) 102. As such, processor(s) 124 may include one or more of a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information. Although processor(s) 124 are shown in
It should be appreciated that although components 106-118 are illustrated in
One or more of the components of system 100 may be configured to present and/or provide a user interface to provide an interface between system 100 and a user (e.g. a controlling entity, and/or other users using a graphical user interface) through which the user can provide information to and receive information from system 100. This enables data, results, and/or instructions (e.g., determinations, selections, and/or other indications) and any other communicable items, collectively referred to as “information,” to be communicated between the user and system 100. An example of information that may be conveyed by a user and/or controlling entity is a selected time indication, a selected location indication, a user comment and/or comment information, and/or other information. Examples of interface devices suitable for inclusion in a user interface include one or more of those associated with a computing platform, a keypad, buttons, switches, a keyboard, knobs, levers, a display screen, a touch screen, a mouse, speakers, a microphone, an indicator light, an audible alarm, and/or a printer. Information may be provided to a user by the user interface in the form of a graphical user interface.
It is to be understood that other communication techniques, either hard-wired or wireless, are also contemplated herein as a user interface. For example, in one embodiment, the user interface may be integrated with a removable storage interface provided by electronic storage 122. In this example, information is loaded into system 100 from removable storage (e.g., a smart card, a flash drive, a removable disk, etc.) that enables the user(s) to customize system 100. Other exemplary input devices and techniques adapted for use with system 100 as the user interface include, but are not limited to, an RS-232 port, RF link, an IR link, modem (telephone, cable, Ethernet, internet or other). In short, any technique for communicating information with system 100 is contemplated as the user interface.
In certain implementations, methods 500 and/or 600 may be implemented in one or more processing devices (e.g., a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, and/or other mechanisms for electronically processing information). The one or more processing devices may include one or more devices executing some or all of the operations of methods 500 and/or 600 in response to instructions stored electronically on an electronic storage medium. The one or more processing devices may include one or more devices configured through hardware, firmware, and/or software to be specifically designed for execution of one or more of the operations of method 500.
Regarding method 500, at an operation 502, a spherical video segment may be obtained. In some implementations, operation 502 may be performed by a spherical segment component that is the same as or similar to spherical segment component 106 (shown in
At an operation 504, an orientation of a two dimensional display may be determined based upon output signals of a sensor. The two dimensional display may be configured to present two dimensional images. The sensor may be configured to generate output signals conveying information related to the orientation of the display. In some implementations, operation 504 may be performed by an orientation component that is the same as or similar to orientation component 108 (shown in
At an operation 506, a display field of view within the spherical video segment to be presented on the display may be determined based upon the orientation of the display. In some implementations, operation 506 may be performed by a field of view component that is the same as or similar to field of view component 112 (shown in
At an operation 508, the display field of view of the spherical video segment may be presented on the display. In some implementations, operation 508 may be performed by a presentation component that is the same as or similar to presentation component 114 (shown in
At an operation 510, the display field of view may be captured as a two dimensional video segment. In some implementations, operation 510 may be performed by a capture component that is the same as or similar to capture component 116 (shown in
Regarding method 600, at an operation 602, a spherical video segment may be obtained. The spherical video segment may include tag information associated with an event of interest in the spherical video segment. The tag information may identify a point in time in the spherical video segment and a viewing angle in the spherical video segment at which the event of interest is viewable in the spherical video segment. In some implementations, operation 502 may be performed by a spherical segment component that is the same as or similar to spherical segment component 106 (shown in
At an operation 604, an orientation of a two dimensional display may be determined based upon output signals of a sensor. The two dimensional display may be configured to present two dimensional images. The sensor may be configured to generate output signals conveying information related to the orientation of the display. In some implementations, operation 604 may be performed by an orientation component that is the same as or similar to orientation component 108 (shown in
At an operation 606, a display field of view within the spherical video segment to be presented on the display may be determined based upon the orientation of the display. In some implementations, operation 606 may be performed by a field of view component that is the same as or similar to field of view component 112 (shown in
At an operation 608, the display field of view of the spherical video segment may be presented on the display. In some implementations, operation 608 may be performed by a presentation component that is the same as or similar to presentation component 114 (shown in
At an operation 610, whether the viewing angle is located within the display field of view proximate to the point in time may be determined. In some implementations, operation 610 may be performed by a field of view component that is the same as or similar to field of view component 112 (shown in
At an operation 612, responsive to a determination proximate to the point in time that the viewing angle is outside the display field of view, alert information may be generated. The alert information may indicate the event of interest for the spherical video segment is located outside the display field of view. In some implementations, operation 612 may be performed by a notification component that is the same as or similar to notification component 118 (shown in
At an operation 614, a notification may be presented based upon the alert information. The notification may include the alert information and may be presented within the display field of view. In some implementations, operation 614 may be performed by a notification component that is the same as or similar to notification component 118 (shown in
Although the disclosed technology has been described in detail for the purpose of illustration based on what is currently considered to be the most practical and preferred implementations, it is to be understood that such detail is solely for that purpose and that the disclosure is not limited to any particular implementations, but, on the contrary, is intended to cover modifications and equivalent arrangements that are within the spirit and scope of the appended claims. For example, it is to be understood that the present disclosure contemplates that, to the extent possible, one or more features of any embodiment can be combined with one or more features of any other embodiment.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5260779 | Wasserman | Nov 1993 | A |
| 5555895 | Ulmer | Sep 1996 | A |
| 6369812 | Iyriboz | Apr 2002 | B1 |
| 6434265 | Xiong | Aug 2002 | B1 |
| 6486908 | Chen | Nov 2002 | B1 |
| 6710740 | Needham | Mar 2004 | B2 |
| 6711293 | Lowe | Mar 2004 | B1 |
| 6788333 | Uyttendaele | Sep 2004 | B1 |
| 7057663 | Lee | Jun 2006 | B1 |
| 7403224 | Fuller | Jul 2008 | B2 |
| 7983502 | Cohen | Jul 2011 | B2 |
| 8411166 | Miyata | Apr 2013 | B2 |
| 8606073 | Woodman | Dec 2013 | B2 |
| 8670030 | Tanaka | Mar 2014 | B2 |
| 8842197 | Singh | Sep 2014 | B2 |
| 8890954 | ODonnell | Nov 2014 | B2 |
| 8896694 | O'Donnell | Nov 2014 | B2 |
| 9019396 | Kiyoshige | Apr 2015 | B2 |
| 9158304 | Fleck | Oct 2015 | B2 |
| 9342534 | Singh | May 2016 | B2 |
| 9409646 | Fleck | Aug 2016 | B2 |
| 9473758 | Long | Oct 2016 | B1 |
| 9570113 | Campbell | Feb 2017 | B2 |
| 9602795 | Matias | Mar 2017 | B1 |
| 9743060 | Matias | Aug 2017 | B1 |
| 9781342 | Turley | Oct 2017 | B1 |
| 9973746 | Matias | May 2018 | B2 |
| 10084961 | Macmillan | Sep 2018 | B2 |
| 10129516 | Matias | Nov 2018 | B2 |
| 10250839 | Han | Apr 2019 | B2 |
| 10319103 | Bendall | Jun 2019 | B2 |
| 10536683 | Matias | Jan 2020 | B2 |
| 10880522 | McCutchen | Dec 2020 | B2 |
| 20020112005 | Namias | Aug 2002 | A1 |
| 20020122113 | Foote | Sep 2002 | A1 |
| 20020191087 | Hashimoto | Dec 2002 | A1 |
| 20030085992 | Arpa | May 2003 | A1 |
| 20030098954 | Amir | May 2003 | A1 |
| 20030160862 | Charlier | Aug 2003 | A1 |
| 20040010804 | Hendricks | Jan 2004 | A1 |
| 20040021780 | Kogan | Feb 2004 | A1 |
| 20040047606 | Mikawa | Mar 2004 | A1 |
| 20040075738 | Burke | Apr 2004 | A1 |
| 20040135900 | Pyle | Jul 2004 | A1 |
| 20040169724 | Ekpar | Sep 2004 | A1 |
| 20050033760 | Fuller | Feb 2005 | A1 |
| 20050062869 | Zimmermann | Mar 2005 | A1 |
| 20050104976 | Currans | May 2005 | A1 |
| 20050134707 | Perotti | Jun 2005 | A1 |
| 20050289111 | Tribble | Dec 2005 | A1 |
| 20060050997 | Imamura | Mar 2006 | A1 |
| 20070030358 | Aoyama | Feb 2007 | A1 |
| 20070053659 | Kiyama | Mar 2007 | A1 |
| 20070120986 | Nunomaki | May 2007 | A1 |
| 20070140662 | Nunomaki | Jun 2007 | A1 |
| 20070300249 | Smith | Dec 2007 | A1 |
| 20080094499 | Ueno | Apr 2008 | A1 |
| 20080118100 | Hayashi | May 2008 | A1 |
| 20090210707 | De Lutiis | Aug 2009 | A1 |
| 20090251558 | Park | Oct 2009 | A1 |
| 20090262206 | Park | Oct 2009 | A1 |
| 20090271447 | Shin | Oct 2009 | A1 |
| 20100045773 | Ritchey | Feb 2010 | A1 |
| 20100097443 | Lablans | Apr 2010 | A1 |
| 20100238304 | Miyata | Sep 2010 | A1 |
| 20100250022 | Hines | Sep 2010 | A1 |
| 20100289924 | Koshikawa | Nov 2010 | A1 |
| 20100299630 | McCutchen | Nov 2010 | A1 |
| 20110013778 | Takumai | Jan 2011 | A1 |
| 20110115883 | Kellerman | May 2011 | A1 |
| 20110141300 | Stec | Jun 2011 | A1 |
| 20110261227 | Higaki | Oct 2011 | A1 |
| 20120206565 | Villmer | Aug 2012 | A1 |
| 20120242798 | Mcardle | Sep 2012 | A1 |
| 20130021450 | Yoshizawa | Jan 2013 | A1 |
| 20130058532 | White | Mar 2013 | A1 |
| 20130058619 | Miyakawa | Mar 2013 | A1 |
| 20130127903 | Paris | May 2013 | A1 |
| 20130176403 | Varga | Jul 2013 | A1 |
| 20130177168 | Inha | Jul 2013 | A1 |
| 20130182177 | Furlan | Jul 2013 | A1 |
| 20130210563 | Hollinger | Aug 2013 | A1 |
| 20130235226 | Karn | Sep 2013 | A1 |
| 20130330054 | Lokshin | Dec 2013 | A1 |
| 20140037268 | Shoji | Feb 2014 | A1 |
| 20140039884 | Chen | Feb 2014 | A1 |
| 20140184821 | Taneichi | Jul 2014 | A1 |
| 20140240122 | Roberts | Aug 2014 | A1 |
| 20150055937 | Van Hoff | Feb 2015 | A1 |
| 20150058102 | Christensen | Feb 2015 | A1 |
| 20150113581 | Mcardle | Apr 2015 | A1 |
| 20150142211 | Shehata | May 2015 | A1 |
| 20150142742 | Hong | May 2015 | A1 |
| 20150166476 | Chen | Jun 2015 | A1 |
| 20150186073 | Pacurariu | Jul 2015 | A1 |
| 20150189221 | Nakase | Jul 2015 | A1 |
| 20150243085 | Newhouse | Aug 2015 | A1 |
| 20150287435 | Land | Oct 2015 | A1 |
| 20150288754 | Mosko | Oct 2015 | A1 |
| 20150304532 | Bart | Oct 2015 | A1 |
| 20150336015 | Blum | Nov 2015 | A1 |
| 20150350614 | Meier | Dec 2015 | A1 |
| 20150363648 | Li | Dec 2015 | A1 |
| 20150367958 | Lapstun | Dec 2015 | A1 |
| 20150370250 | Bachrach | Dec 2015 | A1 |
| 20160005435 | Campbell | Jan 2016 | A1 |
| 20160018822 | Nevdahs | Jan 2016 | A1 |
| 20160031559 | Zang | Feb 2016 | A1 |
| 20160054737 | Soll | Feb 2016 | A1 |
| 20160076892 | Zhou | Mar 2016 | A1 |
| 20160098469 | Allinson | Apr 2016 | A1 |
| 20160101856 | Kohstall | Apr 2016 | A1 |
| 20160112713 | Russell | Apr 2016 | A1 |
| 20160129999 | Mays | May 2016 | A1 |
| 20160139596 | Na | May 2016 | A1 |
| 20160139602 | Kohstall | May 2016 | A1 |
| 20160165563 | Jang | Jun 2016 | A1 |
| 20160179096 | Bradlow | Jun 2016 | A1 |
| 20160189101 | Kantor | Jun 2016 | A1 |
| 20160234438 | Satoh | Aug 2016 | A1 |
| 20160239340 | Chauvet | Aug 2016 | A1 |
| 20160269621 | Cho | Sep 2016 | A1 |
| 20160295108 | Cao | Oct 2016 | A1 |
| 20160304198 | Jourdan | Oct 2016 | A1 |
| 20160306351 | Fisher | Oct 2016 | A1 |
| 20160313734 | Enke | Oct 2016 | A1 |
| 20160327950 | Bachrach | Nov 2016 | A1 |
| 20160336020 | Bradlow | Nov 2016 | A1 |
| 20160366290 | Hoshino | Dec 2016 | A1 |
| 20170110151 | Matias | Apr 2017 | A1 |
| 20170237976 | Matias | Aug 2017 | A1 |
| 20170244945 | Matias | Aug 2017 | A1 |
| 20170244946 | Matias | Aug 2017 | A1 |
| 20170249745 | Fiala | Aug 2017 | A1 |
| 20190082155 | Matias | Mar 2019 | A1 |
| Number | Date | Country |
|---|---|---|
| 0605045 | Jul 1994 | EP |
| 0650299 | Apr 1995 | EP |
| 0661672 | Jul 1995 | EP |
| 2009047572 | Apr 2009 | WO |
| 2014090277 | Jun 2014 | WO |
| Entry |
|---|
| “Spatial Audio Lecture Series,” Regents of the University of California at Berkeley, Center for New Music and Audio Technologies, 2015, 1 Page, [online] [retrieved on Aug. 20, 2015] Retrieved from the internet <URL:http:l/cnmat.berkelev.edu/spatialaudiolectures>. |
| Benjamin Meyer et al., ‘Real-time Free-Viewpoint Navigation from Compressed Multi-Video Recordings’, Proc. 3D Data Processing, Visualization and Transmission (3DPVT), (May 31, 2010), pp. 1-6, URL: http://www.cg.cs.tu-bs.de/media/publications/meyer2010realtime.pdf, (May 31, 2013), XP055091261. |
| EESR for EP17753994.7 dated Jun. 18, 2019, 9 pages. |
| Farin et al., “Shortest Circular Paths on Planar Graphs,” In 27th Symposium on Information Theory in the Benelux 2006, 8 pgs. |
| Felix Klose et al., ‘Stereoscopic 3D View Synthesis From Unsynchronized Multi-view Video’, Proc. European Signal Processing Conference (EUSIPCO), Barcelona, Spain, (Sep. 2, 2011), pp. 1904-1909, URL: http://www.cg.cs.tu-bs.de/media/publications/eusipco2011_3d_synth.pdf, (Dec. 3, 2013), XP055091259. |
| Foote J et al., ‘FlyCam: practical panoramic video and automatic camera control’, Multimedia and Expo, 2000. ICME 2000. 2000 IEEE International Conference on New York, NY, USA Jul. 30-Aug. 2, 2000, Piscataway, NJ, USA,IEEE, US, (Jul. 30, 2000), vol. 3, doi:10.1109/ICME.2000.871033, ISBN 978-0-7803-6536-0, pp. 1419-1422, XP010512772. |
| Hossein Afshari et al: ‘The PANOPTIC Camera: A Plenoptic Sensor with Real-Time Omnidirectional Capability’, Journal of Signal Processing Systems, vol. 70, No. 3, Mar. 14, 2012 (Mar. 14, 2012), pp. 305-328, XP055092066, ISSN: 1939-8018, DOI: 10.1007/S11265-012-0668-4. |
| Lipski, C.: ‘Virtual video camera’, SIGGRAPH '09: Posters On, SIGGRAPH '09, vol. 0, Jan. 1, 2009 (Jan. 1, 2009), pp. 1-1, XP055091257, New York, New York, USA DOI: 10.1145/1599301.1599394. |
| Mai Zheng et al, Stitching Video from Webcams, Advances in Visual Computing: 4th International Symposium, ISVC 2008, Las Vegas, NV, USA, Dec. 1-3, 2008. Proceedings, Part II, Springer Berlin Heidelberg, Berlin, Heidelberg, pp. 420-429, ISBN 978-3-540-89645-6, XP019112243. |
| O'Donovan, A., et al., “Audio-Visual Panoramas and Spherical Audio Analysis using the Audio Camera,” C1 Proceedings of the 16th International Conference on Auditory Display, Jun. 9-15, 2010, pp. ICAD-167-168, can be retrieved at <URL: https://smartech.gatech.edu/bitstream/handle/1853/49858/0%27DonovanDuraiswami201 O.pdf?sequence=1 >. |
| O'Donovan, A., et al., “Real Time Capture of Audio Images and their Use with Video,” 2007 IEEE Workshop on Applications of Signal Processing to Audio and Acoustics, Oct. 21-24, 2007, pp. 10-13. |
| PCT International Search Report and Written Opinion for PCT/US15/38913, dated Sep. 29, 2015, 15 Pages. |
| PCT International Search Report and Written Opinion for PCT/US17/18508 dated Mar. 23, 2017 (13 pages). |
| PCT International Search Report for PCT/EP2014/057352 dated Jun. 27, 2014, 3 pages. |
| PCT International Search Report for PCT/EP2014/058008 dated May 26, 2014, 3 pages. |
| PCT International Search Report for PCT/EP2014/061897 dated Sep. 15, 2014, 3 pages. |
| Perazzi et al., “Panoramic Video from Unstructured Camera Arrays,” Eurographics, vol. 34 (2015), No. 2, 12pgs. |
| Ryan Jackson: ‘Shooting 360-degree video with four GoPro HD Hero cameras / Ryan Jackson Photography’ Feb. 8, 2011 (Feb. 8, 2011), XP055099926, Extrait de l'lnternet: URL:http://punkoryan.com/2011/02/08/shooting-360-degree-video-with-four-gopro-hd-hero-cameras [extrait le Feb. 3, 2014] 37 pages. |
| U.S. Appl. No. 14/920,427, filed Oct. 22, 2015, entitled “Apparatus and Methods for Embedding Metadata Into Video Stream” 62 pages. |
| U.S. Appl. No. 14/927,343, filed Oct. 29, 2015, entitled “Apparatus and Methods for Rolling Shutter Compensation for Multi-Camera Systems” 45 pages. |
| U.S. Appl. No. 14/949,786, filed Nov. 23, 2015, entitled “Apparatus and Methods for Image Alignment” 67 pages. |
| U.S. Appl. No. 15/001,038, filed Jan. 19, 2016, entitled “Metadata Capture Apparatus and Methods” 54 pages. |
| Zhi et al., “Toward Dynamic Image Mosaic Generation With Robustness to Parallax,” IEEE Transactions on Image Processing, vol. 21, No. 1, Jan. 2012, pp. 366-378. |
| Number | Date | Country | |
|---|---|---|---|
| 20200128223 A1 | Apr 2020 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16185956 | Nov 2018 | US |
| Child | 16721595 | US | |
| Parent | 15458253 | Mar 2017 | US |
| Child | 16185956 | US | |
| Parent | 15050297 | Feb 2016 | US |
| Child | 15458253 | US |
