Camera device setup and effect shortcut

By providing shortcuts for camera device effects in social network applications, users can select and apply them to personal video capture, solving the problem of camera device settings and AR effects when copying and sharing videos, and improving user experience and interactivity.

CN119096535AActive Publication Date: 2024-12-06SNAP INC
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
CN202380036381.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-10-04
Filing Date
2023-04-06
Publication Date
2024-12-06
Estimated Expiration
2043-04-06

AI Technical Summary

Technical Problem

When existing social networking applications share and view videos, it is difficult to copy and apply the camera device settings and augmented reality (AR) effects in personal video capture, resulting in inconvenient user experience.

Method used

By providing a system and method on a mobile device, users allow users to select and apply shortcuts for camera effects, apply corresponding camera settings and AR effects when displaying videos, and allow users to capture and share these effects.

Benefits of technology

It enables users to easily copy and apply the camera device settings and AR effects in personal video capture, improves the video sharing and viewing experience, and enhances user interactivity.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119096535A_ABST
    Figure CN119096535A_ABST
Patent Text Reader

Abstract

A method for providing custom visual settings on a device comprising a display and at least one camera is disclosed. The method includes displaying a video on a display of a device, the video including data specifying a camera setting and a visual effect applied during capture of the video; displaying an effect shortcut of the camera device; receiving a user selection of a camera device effect shortcut; and based on receiving the user selection of the camera effect shortcut, displaying a video feed from the at least one camera on the display, the video feed having the visual effect specified by the data and the camera settings.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Related application data

[0002] This application claims priority to U.S. patent application serial number 17 / 937,980 filed on October 4, 2022, which claims priority to U.S. provisional patent application serial number 63 / 334,873 filed on April 26, 2022, all of which are incorporated herein by reference in their entirety. Background Art

[0003] Social networking applications provide tools for sharing user content such as photos or videos. In some instances, the photos or videos can be supplemented by augmented reality or other effects that are generated live on the camera feed and displayed on the display of the mobile device for preview. The user can be able to select and manipulate the effects to be applied to the live camera feed, and when satisfied, capture an image including the effects or record a video including the effects. The captured video or photo can then be shared on the social networking platform. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] In the drawings, which are not necessarily drawn to scale, similar reference numerals may describe similar components in different views. To easily identify the discussion of any particular element or action, the highest digit or digits in the reference numeral refer to the figure number in which the element is first introduced. Some non-limiting examples are shown in the figures of the accompanying drawings, in which:

[0005] Figure 1 is a diagrammatic representation of a networked environment in which the present disclosure may be deployed, according to some examples.

[0006] Figure 2 is a diagrammatic representation of a messaging system having both client-side and server-side functionality according to some examples.

[0007] Figure 3 A mobile device user interface is shown according to some examples.

[0008] Figure 4 A mobile device user interface is shown according to some examples.

[0009] Figure 5A and Figure 5B A mobile device user interface is shown according to some examples.

[0010] Fig. 6A and Figure 6B A mobile device user interface is shown according to some examples.

[0011] Figure 7A mobile device user interface is shown according to some examples.

[0012] Figure 8 A mobile device user interface is shown according to some examples.

[0013] Fig. 9 is a flow chart illustrating camera and effects shortcut operations according to some examples.

[0014] Fig.10 A series of screens representing a mobile device user interface are shown according to some examples.

[0015] Fig.11 A mobile device user interface is shown according to some examples.

[0016] Fig.12 A mobile device user interface is shown according to some examples.

[0017] Fig.13 A series of screens representing a mobile device user interface are shown according to some examples.

[0018] Fig.14 is a flow chart illustrating camera and effects shortcut operations according to some examples.

[0019] Fig.15 A mobile device user interface is shown according to some examples.

[0020] Fig.16 is a block diagram illustrating a software architecture in which examples may be implemented.

[0021] Fig.17 is a diagrammatic representation of a machine in the form of a computer system according to some examples within which a set of instructions may be executed for causing the machine to perform any one or more of the methodologies discussed herein. DETAILED DESCRIPTION

[0022] Systems and methods are disclosed for providing a quick method and interface by which users of messaging or social media applications on portable devices can apply camera settings and effects (e.g., augmented reality (AR) effects) to the camera feed on their devices.

[0023] As referred to herein, the term "augmented reality experience" includes or refers to various image processing operations corresponding to image modification, filtering, media overlays, transformations, and the like. In some examples, these image processing operations provide an interactive experience of a real-world environment in which objects, surfaces, backgrounds, lighting, and the like in the real world are enhanced by computer-generated perceptual information. The augmented reality experience may also include associated audio, such as a soundtrack or effect sounds. In this case, the "AR effect" includes a collection of data, parameters, and other assets required to apply the selected augmented reality experience to an image or video feed. In some examples, the augmented reality effects are provided by Snap Inc. under the registered trademark LENSES.

[0024] Messaging or social media applications are increasingly being used to browse and view content created by other users of the application. In some examples, short videos captured, generated, or modified by users of the application can be presented in a public collection of such videos, which can then be viewed, liked, collected, and forwarded by users of the messaging or social media application. In one example, a collection of such videos is provided by Snap Inc. in the Snapchat application under the trademark SPOTLIGHT.

[0025] Users can post videos to a public collection, or can forward videos to others for viewing on messaging apps. Any particular video may have been captured using specific camera settings and one or more AR effects. The transmitted video includes identification of the camera settings and associated effects as metadata. By providing shortcuts to viewers of the video, users can apply corresponding camera settings and AR effects to the video feed generated by the camera in their device. This allows users to copy the effects and settings used when creating the viewed video for use when capturing their own videos.

[0026] Although the examples described herein refer to videos published to a public collection for viewing, it should be understood that the methods described herein can be used for images, user stories, or any other type of content created and published or shared, and including specific camera settings or AR effects.

[0027] In some examples, a method performed by one or more processors for providing enhancements on a device including a display and at least one camera is provided, the method comprising: displaying a video on the display of the device, the video including data specifying camera settings and enhancements applied to the video; displaying a camera effects shortcut; receiving a user selection of the camera effects shortcut; and based on receiving the user selection of the camera effects shortcut, displaying on the display a video feed from at least one camera with the enhancements and camera settings specified by the data applied to the video feed.

[0028] The method may also include displaying an effect indicator with the video, the effect indicator identifying the name and creator of the enhancement effect. The method may also include: receiving a selection of the effect indicator; displaying information about the enhancement effect; and displaying an action call user interface element for a user to apply the enhancement effect to the video feed. Selection of the action call user interface element may result in the enhancement effect being applied to the video feed but without applying the camera setting.

[0029] The method may also include: displaying a context indicator with the video, the context indicator identifying an audio track played with the video; receiving a user selection of the context indicator; and based on receiving the user selection of the context indicator, displaying other information related to the audio track. Before displaying the video feed from at least one camera with the enhancements and camera settings, a confirmation user interface item may be displayed; and the method may also include: receiving a selection of the confirmation user interface item; and based on receiving the selection of the confirmation user interface item, displaying the video feed from at least one camera with the enhancements and camera settings. In some examples, displayed with the video is a context indicator identifying an audio track played with the video.

[0030] In some examples provided, a computing device includes at least one camera, a display, and one or more processors. The computing device also includes: a memory storing instructions that, when executed by the one or more processors, configure the device to perform operations for providing enhancements according to any of the above method steps, including but not limited to: displaying a video on a display of the device, the video including data specifying camera settings and enhancements applied to the video; displaying a camera effect shortcut; receiving a user selection of the camera effect shortcut; and based on receiving the user selection of the camera effect shortcut, displaying on the display a video feed from at least one camera with the enhancements and camera settings specified by the data applied to the video feed.

[0031] In one aspect, a non-transitory computer-readable storage medium includes instructions that, when executed by a computer, cause the computer to perform operations for providing augmented effects on a device including a display and at least one camera, the operations being performed according to any of the above method steps, including but not limited to: displaying a video feed on the display of the device, the video feed being captured by at least one camera; displaying a camera effects shortcut, the camera effects shortcut being associated with a set of augmented reality effects and camera settings; receiving a user selection of the camera effects shortcut, and based on receiving the user selection of the camera effects shortcut, displaying a modified video feed from the at least one camera on the display, in which the augmented reality effects and camera settings associated with the camera effects shortcut have been applied.

[0032] Other technical features may be readily apparent to those skilled in the art from the accompanying drawings, descriptions and claims.

[0033] Figure 1 1 is a block diagram illustrating an example of a messaging system 100 for exchanging data (e.g., messages, media, and associated content) over a network. The messaging system 100 includes multiple instances of a user device 102, each of which hosts several applications, including a messaging client 104 and other applications 106. Each messaging client 104 is communicatively coupled to other instances of the messaging client 104 (e.g., hosted on respective other client devices 102), a messaging server system 108, and a third-party server 110 via a network 112 (e.g., the Internet). The messaging client 104 may also communicate with a local host application 106 using an application program interface (API).

[0034] The messaging clients 104 are able to communicate and exchange data with other messaging clients 104 and messaging server systems 108 via the network 112. The data exchanged between the messaging clients 104 and between the messaging clients 104 and messaging server systems 108 include functions (e.g., commands for activating functions) and payload data (e.g., text, audio, video, or other multimedia data).

[0035] The messaging server system 108 provides server-side functionality to specific messaging clients 104 via the network 112. Although certain functions of the messaging system 100 are described herein as being performed by the messaging client 104 or by the messaging server system 108, it may be a design choice whether certain functions are located within the messaging client 104 or within the messaging server system 108. For example, it may be technically preferred to initially deploy certain technologies and functions within the messaging server system 108, but later migrate the technologies and functions to the messaging client 104 where the user device 102 has sufficient processing power.

[0036] The messaging server system 108 supports various services and operations provided to the messaging clients 104. Such operations include sending data to the messaging clients 104, receiving data from the messaging clients 104, and processing data generated by the messaging clients 104. As examples, the data may include message content, client device information, geolocation information, media enhancements and overlays, message content persistence conditions, social network information, and live event information. The data exchange within the messaging system 100 is stimulated and controlled by functions available via the user interface (UI) of the messaging client 104.

[0037] Turning now specifically to the messaging server system 108, an application program interface (API) server 116 is coupled to the application server 114 and provides a programming interface to the application server 114. The application server 114 is communicatively coupled to a database server 120, which facilitates access to a database 126 that stores data associated with messages processed by the application server 114. Similarly, a web server 128 is coupled to the application server 114 and provides a web-based interface to the application server 114. To this end, the web server 128 processes incoming network requests via the Hypertext Transfer Protocol (HTTP) and several other related protocols.

[0038] The application program interface (API) server 116 receives and sends message data (e.g., commands and message payloads) between the user device 102 and the application server 114. Specifically, the application program interface (API) server 116 provides a set of interfaces (e.g., routines and protocols) that can be called or queried by the messaging client 104 to activate the functions of the application server 114. An application program interface (API) server 116 exposes various functions supported by application server 114, including: account registration; login functionality; sending messages from a particular messaging client 104 to another messaging client 104 via application server 114; sending media files (e.g., images or videos) from a messaging client 104 to messaging server 118 and for possible access by another messaging client 104; setting up a collection of media data (e.g., a story); retrieving a friend list of a user of user device 102; retrieving such a collection; retrieving messages and content; adding and removing entities (e.g., friends) from an entity graph (e.g., a social graph); locating friends within a social graph; and opening application events (e.g., related to messaging client 104).

[0039] The application server 114 hosts several server applications and subsystems, including, for example, a messaging server 118, an image processing server 122, and a social networking server 124. The messaging server 118 implements several messaging processing techniques and functions, particularly those related to the aggregation and other processing of content (e.g., text and multimedia content) included in messages received from multiple instances of the messaging client 104. Text and media content from multiple sources can be aggregated into collections of content (e.g., referred to as stories or galleries). These collections are then made available to the messaging client 104. Given the hardware requirements for other processor and memory intensive data processing, other processor and memory intensive data processing can also be performed on the server side by the messaging server 118.

[0040] The application server 114 also includes an image processing server 122 that is dedicated to performing various image processing operations, typically with respect to images or videos within the payload of messages sent from the messaging server 114 or received at the messaging server 118 .

[0041] The social network server 124 supports various social networking functions and services and makes them available to the messaging server 118. To this end, the social network server 124 maintains and accesses an entity graph within the database 126. Examples of functions and services supported by the social network server 124 include identifying other users in the messaging system 100 who have a relationship with a particular user or who the particular user is "following," and identifying interests and other entities of a particular user.

[0042] Figure 2 1 is a block diagram showing additional details about the messaging system 100 according to some examples. Specifically, the messaging system 100 is shown to include a messaging client 104 and an application server 114. The messaging system 100 contains several subsystems that are supported on the client side by the messaging client 104 and on the server side by the application server 114. These subsystems include, for example, a user interface 202, a collection management system 204, an enhancement system 208, a mapping system 210, and a gaming system 212.

[0043] The user interface 202 is responsible for providing output to and receiving input from a user of the messaging client 104 on the user device 102. As is known in the art, the user interface provides a user-manipulatable display output on the display of the user device 102 (see further Fig.17 In one example, the user interface includes a chat interface whereby a user can send and receive messages and associated content to and from one or more remote users. The user interface 202 also allows the user to manipulate live or captured media, such as by providing augmented reality effects on captured photos or videos, or on a live video feed from a camera of the user device.

[0044] The collection management system 204 is responsible for managing collections or collections of media (e.g., collections of text, images, video, and audio data). Collections of content (e.g., messages, including images, videos, text, and audio) may be organized into "event galleries" or "event stories." Such collections may be made available for a specified period of time (e.g., the duration of the event to which the content relates). For example, content related to a concert may be made available as a "story" for the duration of the concert. The collection management system 204 may also be responsible for publishing an icon to the user interface of the messaging client 104 that provides notification of the existence of a particular collection.

[0045] In addition, the collection management system 204 also includes a curation interface 206, which enables collection managers to manage and curate specific content collections. For example, the curation interface 206 enables event organizers to curate collections of content related to specific events (e.g., deleting inappropriate content or redundant messages). In addition, the collection management system 204 uses machine vision (or image recognition technology) and content rules to automatically curate content collections. In some examples, compensation can be paid to users for including user-generated content in a collection. In such a case, the collection management system 204 operates to automatically pay such users for using their content.

[0046] The enhancement system 208 provides various functions that enable users to enhance (e.g., annotate or otherwise modify or edit) media content associated with a message. For example, the enhancement system 208 provides functions related to generating and publishing media overlays (media overlays) for messages processed by the messaging system 100. The enhancement system 208 is operable to provide media overlays or enhancements (e.g., image filters) to the messaging client 104 based on the geolocation of the user device 102. In another example, the enhancement system 208 is operable to provide media overlays to the messaging client 104 based on other information such as social network information of the user of the user device 102. Media overlays can include audio and visual content and visual effects. Examples of audio and visual content include pictures, text, logos, animations, and sound effects. Examples of visual effects include color overlays. Audio and visual content or visual effects can be applied to media content items (e.g., photos) at the user device 102. For example, media overlays can include text or images that can be superimposed on top of photos taken by the user device 102. In another example, the media overlay includes a location identification (e.g., Venice Beach) overlay, the name of a live event, or a business name (e.g., Beach Cafe) overlay. In another example, the augmentation system 208 uses the geolocation of the user device 102 to identify a media overlay that includes the name of a business at the geolocation of the user device 102. The media overlay may include other logos associated with the business. The media overlay may be stored in the database 120 and accessed by the database server 120.

[0047] The mapping system 210 provides various geolocation functions and supports the presentation of map-based media content and messages by the messaging client 104. For example, the mapping system 210 enables the display of user icons or avatars on a map to indicate the current or past locations of the user's "friends" in the context of the map, as well as media content (e.g., a collection of messages including photos and videos) generated by such friends. For example, on the map interface of the messaging client 104, messages posted by the user to the messaging system 100 from a particular geolocation can be displayed to the "friends" of the particular user within the context of that particular location on the map. The user can also share his or her location and status information with other users of the messaging system 100 (e.g., using appropriate status avatars) via the messaging client 104, where the location and status information is similarly displayed to selected users within the context of the mapping interface of the messaging client 104.

[0048] The gaming system 212 provides various gaming functions within the context of the messaging client 104. The messaging client 104 provides a gaming interface that provides a list of available games that can be launched by a user within the context of the messaging client 104 and played with other users of the messaging system 100. The messaging system 100 also enables a particular user to invite other users to participate in playing a particular game by sending an invitation to such other users from the messaging client 104. The messaging client 104 also supports both voice messaging and text messaging within the context of game play (e.g., chatting), provides leaderboards for games, and also supports providing in-game rewards (e.g., game coins and items).

[0049] Figure 3 A mobile device user interface 300 according to some examples is shown. The user interface 300 is presented on a touch screen of a mobile device (e.g., user device 102). In some examples, the user interface 300 shows a presentation of a short video of a man 302 performing a hula hoop, which is being played for viewing by a user of the user device 102. As indicated by the SPOTLIGHT banner 304, the video is part of a collection of publicly available videos that can be viewed and accessed. Displayed with the video is a title 306, the user name 308 of the user who posted the video, and user interface options such as a like or favorite button 310, a forward button 312, and an overflow indicator icon 314 indicating that additional user interface options related to the video are available.

[0050] User interface 300 also includes one or more context indicators 316 that provide additional context information for the video. In this example, context indicator 316 is associated with the audio track of the video and describes the name of the audio track and the artist or composer. Selecting context indicator 316 switches to displaying, for example, Figure 7 As shown in Figure 7 In the case of an audio track, selecting context indicator 316 may display information about the artist and song, provide options to play or favorite the song, capture video while the song is playing in the background, and the like.

[0051] exist Figure 3 Also shown is a call to action (CTA) camera effects shortcut button 318, which includes a camera icon 320 and CTA text 322. The video shown on the user device 102 will be captured by the original creator using various camera settings, and may have various visual or audio effects, such as Snap's LENSES augmented reality (AR) effects. When the video is streamed or downloaded from a remote location (e.g., database server 120), the video will include metadata including the camera settings used when captured, and the identity, timing, and parameters (if any) of any AR effects applied when or after the video is captured.

[0052] If the user of the user device 102 likes the overall experience provided by these camera settings and AR effects, they can select the camera effects shortcut button 318 to use these camera settings and AR effects in their own video or image capture. Upon receipt of the selection of the camera effects shortcut button 318 by the user device 102 and the messaging client 104, the user interface 300 transitions to Figure 4 User interface 400.

[0053] Figure 4 A mobile device user interface 400 is shown according to some examples. Figure 3 After clicking the camera effects shortcut button 318 in the video, the user interface 400 is displayed. In the user interface 400, the user device 102 has changed from a mode in which a short video is being viewed to a mode in which the user of the user device 102 can capture a video or image of himself. Presented on the touch screen of the user device 102 is a live video feed from one of the cameras on the client device. As shown, a person 402 is depicted in the live video feed. For example, this can be a user captured by the front camera of the user device 102, or it can be someone in the field of view of the rear camera of the user device 102.

[0054] User interface 400 includes a banner 404 having text 406 indicating that Figure 34 and 5. A "camera shortcut" corresponding to the camera settings and AR effects associated with the camera is shown, and the associated camera settings and AR effects are being applied to the displayed real-time video feed of the relevant camera from the user device 102. A trash icon 408 is also included, the selection of which will close the banner 404, remove any applied AR effects and restore the camera to its previous settings. A close icon 410 will close the banner 404, but leave the AR effects and camera settings corresponding to the camera shortcut in place.

[0055] In cases where multiple AR effects are applied to the original video, the AR effects applied to the video feed are applied (or "stacked") in the same order as the underlying content. In some cases, the order in which the AR effects are applied to the images or videos may produce slightly different end results. An additional button or icon may be provided in the user interface 400, which, when selected, displays a list of applied AR effects in the order in which the AR effects were applied. The list or stack may then be reordered, or individual AR effects may be removed, or additional AR effects may be added.

[0056] The user may select capture icon 412 at any time to capture a video or image with or without the camera setup and AR effects (as appropriate) in place.

[0057] Figure 5A and Figure 5B A mobile device user interface according to some examples is shown. Figure 3 The user interface 300 is the same as that of Figure 5A The user interface 500a and Figure 5B The user interface 500b of includes a short video that is part of a collection of publicly available videos that can be viewed and accessed, as indicated by the SPOTLIGHT banner 304. In both cases, a single contextual indicator 502 is provided, but in Figure 5A , the camera effect shortcut button 318 is expanded and includes both a camera icon 320 and a CTA text 322; and Figure 5B , the camera effects shortcut button 318 is collapsed and includes only the camera icon 320.

[0058] Fig. 6A and Figure 6B A mobile device user interface according to some examples is shown. Figure 3 The user interface 300 is the same as that of Fig. 6A The user interface 600a and Figure 6BThe user interface 600b includes a short video that is part of a collection of publicly available videos that can be viewed and accessed, as indicated by the SPOTLIGHT banner 304.

[0059] Fig. 6A and Figure 6B The use of multiple context indicators is shown, including a first context indicator 502 and a second context indicator, the first context indicator 502 is related to the audio track of the video and describes the name of the audio track and the artist or composer, and the second context indicator includes an effect indicator 602, and the effect indicator 602 is related to the AR effect applied to the video when the video is captured. In particular, the effect indicator 602 includes the name of the AR effect ("Lens") and the name of its creator ("Jim") and an AR effect icon 604, which can be a feature of a specific AR effect or AR effect creator. In this regard, the creator of the AR effect may not actually be the original author of the specific effect or multiple effects, but may have selected a specific AR effect or a combination of AR effects from the AR effect library for use with the video. As used herein, the term creator is understood to mean both: the original author of the effect, and someone who has selected one or more AR effects for use with the displayed video.

[0060] As before, in Fig. 6A , the camera effect shortcut button 318 is expanded and includes both the camera icon and the CTA text, while in Figure 6B , the camera effects shortcut button 318 is collapsed and includes only the camera icon.

[0061] User selection of effect indicator 602 will cause the user interface to transition to Figure 7 User interface 700.

[0062] Figure 7 A mobile device user interface 700 is shown according to some examples. Fig. 6A or Figure 6B After user input of effect indicator 602 in FIG. 7 , user interface 700 is displayed.

[0063] The user interface 700 provides more information and options related to the AR effect identified by the effect indicator 602. The user interface 700 includes an AR effect icon 604, text 702 identifying the name of the AR effect and the name of the creator of the AR effect, and a favorites icon 704 that a user of the user device 102 can select to include the AR effect in their collection of favorite AR effects. A CTA button 706 is also provided, inviting the user to try a particular AR effect. Selecting the CTA button 706 (with any confirmation steps as follows) will apply the corresponding AR effect to a video feed from one of the cameras in the user device 102, but will not apply the camera settings associated with the camera shortcut button 318 included in the video. User selection of the CTA button 706 will transition to Figure 8 User interface 800.

[0064] Figure 7 Also shown is a grid 708 of thumbnails of publicly available videos, which can be selected to view the video identified by the corresponding thumbnail. The publicly available videos may be related to the creator of the AR effect in some way, or may be based on the popularity or sponsorship of the publicly available videos, based on the preferences or viewing history of the user of the user device 102, etc.

[0065] Figure 8 A mobile device user interface 800 is shown according to some examples. Figure 7 , user interface 800 is displayed. In response, user device 102 transitions to a mode in which a video feed from one of the cameras of user device 102 is displayed on the touch screen of user device 102. Banner 802 with AR effect icon 604 and text prompt 806 invites the user to apply the AR effect corresponding to effect indicator 602. If the user selects banner 802, the corresponding effect is applied to the video feed. The user can then choose to capture a video or image with the AR effect in place by pressing capture icon 412. A close icon 804 is also provided, which will close banner 802 without applying the AR effect corresponding to banner 802.

[0066] Alternatively, upon selection of CTA button 706, the effect corresponding to effect indicator 602 may be immediately applied to the video feed, in which case banner 802 would include effect text indicating that the effect was applied and an option to remove the effect.

[0067] Fig. 9 A flow chart 900 is shown illustrating camera and effects shortcut operations according to some examples. Fig. 9The operations shown in will typically be performed in the form of an application (e.g., messaging client 104) on user device 102. Various implementations are of course possible, where some of the operations occur in application server 114, or where one application calls another application or calls an SDK to obtain the desired functionality.

[0068] Flowchart 900 begins in operation 902, where a video is displayed. This can be a short video provided as part of a collection of short videos, but can also be any previously captured video. The video is accompanied by metadata that specifies the camera settings and any AR or other visual or audio effects applied during the capture or creation of the video.

[0069] In operation 904, a camera effects shortcut button or banner corresponding to the camera settings and any AR or other visual or audio effects applied during the capture or creation of the video is simultaneously displayed. In operation 906, when a user selection of the camera effects shortcut button is received, in operation 908, the camera feed is displayed on the client device with the AR or other visual or audio effects from the video and the camera settings applied thereon.

[0070] In operation 910, if a capture user input is received, then in operation 912, a video or image with the camera effects and AR effects applied is captured by the user device 102 and the messaging client 104. If a close user input is received, then in operation 914, the messaging client 104 returns to another user interface screen, which may be, for example, a display of the original video in operation 902, or may be a video or image capture screen displaying a video feed without the camera settings and AR effects applied.

[0071] Fig.10 A series of screens representing a mobile device user interface 1000 is shown according to some examples. The screens of the user interface 1000 are presented on a touch screen of a mobile device, such as the user device 102. In some examples, the user interface 1000 shows the presentation of a first camera user interface 1002, a camera options interface 1004, and a second camera user interface 1006.

[0072] Camera user interface 1002 shows a video feed of a person 1008 captured by one of the cameras of user device 102 on a display of user device 102. Also included are several user interface elements 1010 that, upon receiving user input, provide various functions, such as capturing video or still images, switching between front and rear cameras, selecting AR effects, etc. Also shown are application user interface elements 1012 that may be related to other UI functions not directly related to the camera.

[0073] Included in user interface element 1010 is a camera options icon 1014. When a user selects camera options icon 1014, camera user interface 1002 transforms into camera options interface 1004, in which a menu 1016 of items related to camera functions and modes is provided for selection by the user, and desired items can be added to user interface element 1010 in camera user interface 1002 by selecting an "add" user interface element 1020 next to the desired item in menu 1016. In some examples, these may include setting a timer, recording in slow motion, adding a background song, adding a grid for alignment, or creating a sequence (or "timeline") of recordings.

[0074] Selecting an item from menu 1016 in camera options interface 1004 or user interface element 1010 in camera user interface 1002 transitions to camera user interface 1006 where the option is applied or additional options are presented. A pop-up window 1018 is shown in camera user interface 1006 which provides additional options after the “Set Timer” option is selected in camera user interface 1002 or camera options interface 1004.

[0075] Fig.11 A mobile device user interface 1100 is shown according to some examples. The user interface 1100 is presented on a touch screen of a mobile device (e.g., user device 102). In some examples, upon receiving a selection Fig.10 After user input of the camera options icon 1014 in the camera user interface 1002, the user interface 1100 is displayed.

[0076] As can be seen, the user interface 1100 also includes a menu 1102 or user selections related to camera functions and modes that can be added to the camera user interface 1102. However, in this case, the menu includes a display of one or more selectable camera shortcuts 1104 corresponding to a set of camera settings and AR effects that can be applied to the video feed displayed in the user interface 1100, as discussed above. Fig.12 As shown in , selecting the camera shortcut 1104 will transition to a user interface screen in which the camera shortcut has been applied.

[0077] As shown below Fig.13 and Fig.14 As described, in some examples, camera shortcut 1104 is selected by the messaging application for display in user interface 1100 based on a scan of the video feed.

[0078] Fig.12 A mobile device user interface 1200 is shown according to some examples. The user interface 1200 is presented on a touch screen of a mobile device (e.g., user device 102). In some examples, the user interface 1200 shows that when selecting Fig.11 1200 is shown after the “Help Your Pet Go Red” camera shortcut 1104 in the example.

[0079] Fig.12 1 is a video feed of a dog 1202 captured by one of the cameras on the user device 102. The video feed is enhanced by applying AR effects (visual and audio) and any associated camera settings (e.g., a shooting star visual AR effect 1214 associated with the "Help Your Pet Go Red" camera shortcut 1104). Also included in the user interface 1200 is a banner 1204 that includes an AR effect icon 1206 corresponding to the camera shortcut 1104, text 1212 indicating that the camera shortcut has been applied and the title of the camera shortcut, and status text 1208 confirming that the camera shortcut has been enabled. The user of the client device can then initiate the capture of an image or video to which the camera shortcut 1104 has been applied by selecting the capture icon 1216. In some examples, a short press will capture an image, while a long press will capture a video. A return icon 1210 is also provided, which, when selected by the user, returns to the previous user interface, such as the camera user interface 1002 or the user interface 1100 .

[0080] Fig.13A series of screens representing a mobile device user interface 1300 is shown according to some examples. The user interface 1300 is presented on a touch screen of a mobile device (e.g., user device 102). In some examples, the user interface 1300 shows the presentation of a first camera user interface 1302, a scan user interface 1304, and a scan results user interface 1306.

[0081] Camera user interface 1302 includes various user interface elements, including a scan icon 1308, which is selected to initiate a scan function performed by messaging client 104 and user device 102 together with messaging server system 108. The scan function uses known image and object detection techniques to identify a subject or object in a video feed. Then, the identification of an object or subject in a video feed can be used to provide information or options related to the identified subject or object. User selection of scan icon 1308 converts camera user interface 1302 into a scan user interface 1304, in which the scanning process is indicated by banner 1310. Banner 1310 includes a thumbnail of dog 1202 in a video feed (image scan being performed on it), text indicating that a scan is in progress, and a close icon 1312 that can be used to return to camera user interface 1302.

[0082] When the scan is complete, the scan results user interface 1306 is presented. The scan results 1314 are presented, including related information 1316. In this case, the scan identified the subject as a dog, with an 87% match with a pug. The application 106 uses the results of the scan and related information associated with the results, such as type, genre, and category, to search for related camera shortcuts. In this case, the related search terms may be "dog," "pet," and "pug," which are used to identify and retrieve one or more camera effects shortcuts 1318 that the user may want to apply. In this example, the search based on the scan results has identified and included a shortcut for the "Make Your Pet Go Viral" camera shortcut, which, when selected by the user, will transition from the results user interface 1306 to Fig.12 User interface 1200.

[0083] Based on matching the scanned results with the title or metadata of the category or specific identifier or other identifying or contextual information (associated with the camera shortcut), the messaging system 100 automatically selects the "Make Your Pet Go Viral" camera shortcut for inclusion in the scan results 1314. In this case, the scan results identify the subject in the video feed as a dog (pet), which matches the title or metadata (associated with the camera effects shortcut), and thus the "Make Your Pet Go Viral" camera effects shortcut 1318 is included in the scan results 1314.

[0084] Fig.14 A flow chart 1400 is shown illustrating camera and effects shortcut operations according to some examples. Fig.14 The operations shown in will typically be performed in the form of an application (e.g., messaging client 104) on user device 102. Various implementations are of course possible, where some of the operations occur in application server 114, or where one application calls another application or calls an SDK to obtain the desired functionality.

[0085] Flowchart 1400 begins in operation 1402, where a video feed from one of the cameras in user device 102 is displayed on a client user device 102. Then, in operation 1404, a scan of the video feed is performed by the messaging client 104. This may be done automatically based on a user selecting a camera function on user device 102 or in messaging client 104, or in response to receiving a user selection of a scan function in messaging client 104 if the camera function is enabled. Then, as discussed above, the scan results of the video feed are used to search for camera effect shortcuts associated with a subject or object.

[0086] Then, in operation 1408, one or more camera effects shortcut buttons, banners, or other user interface elements are displayed that correspond to the camera settings and any AR or other visual or audio effects specified in the camera effects shortcuts returned in the search performed in operation 1406. In operation 1410, when a user selection of a camera effects shortcut button is received, then in operation 1412, the displayed camera feed is modified using the AR or other visual or audio effects and camera settings specified in or associated with the selected camera effects shortcut.

[0087] In operation 1414, if a capture user input is received, then in operation 1416, a video or image with the camera effects and AR effects applied thereto is captured by the user device 102 and the messaging client 104. If a close user input is received, then in operation 1418, the messaging client 104 returns to another user interface screen, which may be, for example, the camera user interface 1302 displaying a video feed without camera settings and AR effects applied, or may be a scan results user interface 1306 displaying the results of a scan.

[0088] Fig.15 Several camera shortcut camera effects shortcut user interface elements 1502 corresponding to different camera shortcuts are shown. As can be seen, the user interface elements 1502 each include: a title 1504, a CTA button 1506 inviting user input to enable the camera shortcut, a camera shortcut icon 1508 corresponding to a particular camera shortcut, and a LENS icon 1510 corresponding to a particular set of AR effects used with the particular camera shortcut. Additional information is also included, such as an image icon 1512 indicating that the camera shortcut is intended for batch image capture, a music icon 1514 indicating that the camera shortcut includes audio, and a video icon 1516 indicating that the camera shortcut is intended for video or video timeline capture.

[0089] Fig.16 1600 is a block diagram illustrating a software architecture 1604 that may be installed on any one or more of the devices described herein. The software architecture 1604 is supported by hardware such as a machine 1602 including a processor 1620, a memory 1626, and an I / O component 1638. In this example, the software architecture 1604 may be conceptualized as a stack of layers, where each layer provides specific functionality. The software architecture 1604 includes layers such as an operating system 1612, a library 1610, a framework 1608, and an application 1606. In operation, the application 1606 invokes an API call 1650 through the software stack and receives a message 1652 in response to the API call 1650.

[0090] The operating system 1612 manages hardware resources and provides public services. The operating system 1612 includes, for example, a kernel 1614, a service 1616, and a driver 1622. The kernel 1614 serves as an abstraction layer between the hardware and other software layers. For example, the kernel 1614 provides functions such as memory management, processor management (e.g., scheduling), component management, networking, and security settings. The service 1616 can provide other public services to other software layers. The driver 1622 is responsible for controlling the underlying hardware or interfacing with the underlying hardware. For example, the driver 1622 may include a display driver, a camera driver, or Low-power drivers, Flash drivers, Serial communication drivers (e.g., USB drivers), Drivers, audio drivers, power management drivers, etc.

[0091] The libraries 1610 provide a common low-level infrastructure used by the applications 1606. The libraries 1610 may include a system library 1618 (e.g., a C standard library) that provides functions such as memory allocation functions, string manipulation functions, mathematical functions, etc. In addition, the libraries 1610 may include an API library 1624, such as a media library (e.g., a library for supporting presentation and manipulation of various media formats, such as Moving Picture Experts Group-4 (MPEG4), Advanced Video Coding (H.264 or AVC), Moving Picture Experts Group Layer-3 (MP3), Advanced Audio Coding (AAC), Adaptive Multi-Rate (AMR) audio codec, Joint Photographic Experts Group (JPEG or JPG), or Portable Network Graphics (PNG)), a graphics library (e.g., an OpenGL framework for presentation in two dimensions (2D) and three dimensions (3D) in graphics content on a display), a database library (e.g., SQLite providing various relational database functions), a web library (e.g., WebKit providing web browsing functions), etc. The library 1610 may also include various other libraries 1628 to provide many other APIs to the application 1606 .

[0092] The framework 1608 provides a common high-level infrastructure used by the applications 1606. For example, the framework 1608 provides various graphical user interface (GUI) functions, high-level resource management, and high-level positioning services. The framework 1608 can provide a wide range of other APIs that can be used by the applications 1606, some of which can be specific to a particular operating system or platform.

[0093] In an example, applications 1606 may include a home application 1636, a contacts application 1630, a browser application 1632, a book reader application 1634, a positioning application 1642, a media application 1644, a messaging application 1646 (e.g., a messaging client 104), a game application 1648, and a variety of other applications such as third-party applications 1640. Application 1606 is a program that performs the functions defined in the program. Various programming languages ​​can be used to create one or more of the applications 1606 constructed in various ways, such as an object-oriented programming language (e.g., Objective-C, Java, or C++) or a procedural programming language (e.g., C or assembly language). In a specific example, third-party applications 1640 (e.g., provided by an entity other than the vendor of a particular platform using ANDROID TM or IOS TM Software Development Kit (SDK) can be used for mobile operating systems, such as IOS TM ANDROID TM , Phone, or other mobile operating system running on the mobile software. In this example, the third-party application 1640 can activate the API call 1650 provided by the operating system 1612 to facilitate the functions described in this article.

[0094] Fig.17The illustrative embodiment of the present invention is a diagrammatic representation of a machine 1700 (e.g., user device 102) within which instructions 1710 (e.g., software, programs, applications, applet, app, or other executable code) may be executed for causing the machine 1700 to perform any one or more of the methodologies discussed herein. For example, the instructions 1710 may cause the machine 1700 to perform any one or more of the methodologies described herein. The instructions 1710 convert a general purpose, unprogrammed machine 1700 into a specific machine 1700 that is programmed to perform the functions described and illustrated in the manner described. The machine 1700 may operate as a standalone device or may be coupled (e.g., networked) to other machines. In a network deployment, the machine 1700 may operate as a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine 1700 may include, but is not limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a personal digital assistant (PDA), an entertainment media system, a cellular phone, a smart phone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance), other smart devices, a web appliance, a network router, a network switch, a network bridge, or any machine capable of sequentially or otherwise executing instructions 1710 specifying actions to be taken by the machine 1700. In addition, although only a single machine 1700 is shown, the term "machine" should also be taken to include a collection of machines that individually or jointly execute instructions 1710 to perform any one or more of the methods discussed herein. For example, the machine 1700 may include any of the user device 102 or a number of server devices that form part of the messaging server system 108. In some examples, the machine 1700 may also include both a client system and a server system, wherein certain operations of a particular method or algorithm are performed on the server side, and certain operations of the particular method or algorithm are performed on the client side.

[0095] The machine 1700 may include a processor 1704, a memory 1706, and an input / output I / O component 1702, which may be configured to communicate with each other via a bus 1740. In an example, the processor 1704 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, a processor 1708 that executes instructions 1710 and a processor 1712. The term "processor" is intended to include multi-core processors, which may include two or more independent processors (sometimes referred to as "cores") that can execute instructions simultaneously. Although Fig.17 Multiple processors 1704 are shown, but the machine 1700 may include a single processor with a single core, a single processor with multiple cores (e.g., a multi-core processor), multiple processors with a single core, multiple processors with multiple cores, or any combination thereof.

[0096] The memory 1706 includes a main memory 1714, a static memory 1716, and a storage unit 1718, which are all accessible by the processor 1704 via a bus 1740. The main memory 1706, the static memory 1716, and the storage unit 1718 store instructions 1710 that implement any one or more of the methods or functions described herein. The instructions 1710 may also reside, completely or partially, within the main memory 1714, within the static memory 1716, within the machine-readable medium 1720 within the storage unit 1718, within at least one of the processors 1704 (e.g., within a cache memory of a processor), or within any suitable combination thereof during execution thereof by the machine 1700.

[0097] I / O components 1702 may include various components that receive input, provide output, generate output, send information, exchange information, capture measurements, etc. The specific I / O components 1702 included in a particular machine will depend on the type of machine. For example, a portable machine such as a mobile phone may include a touch input device or other such input mechanism, while a headless server machine will be less likely to include such a touch input device. It should be appreciated that I / O components 1702 may include Fig.171702. In various examples, the I / O components 1702 may include a user output component 1726 and a user input component 1728. The user output component 1726 may include a visual component (e.g., a display such as a plasma display panel (PDP), a light emitting diode (LED) display, a liquid crystal display (LCD), a projector, or a cathode ray tube (CRT)), an acoustic component (e.g., a speaker), a tactile component (e.g., a vibration motor, a resistance mechanism), other signal generators, etc. The user input component 1728 may include an alphanumeric input component (e.g., a keyboard, a touch screen configured to receive alphanumeric input, an optical keyboard, or other alphanumeric input component), a point-based input component (e.g., a mouse, a touch pad, a trackball, a joystick, a motion sensor, or other pointing instrument), a tactile input component (e.g., a physical button, a touch screen or other tactile input component that provides location and force of a touch or touch gesture), an audio input component (e.g., a microphone), etc.

[0098] In other examples, the I / O component 1702 may include a biometric component 1730, a motion component 1732, an environmental component 1734, or a position component 1736, as well as a wide range of other components. For example, the biometric component 1730 includes components for detecting expressions (e.g., hand expressions, facial expressions, voice expressions, body postures, or eye tracking), measuring biosignals (e.g., blood pressure, heart rate, body temperature, sweat, or brain waves), identifying people (e.g., voice recognition, retinal recognition, facial recognition, fingerprint recognition, or EEG-based recognition), etc. The motion component 1732 includes an acceleration sensor component (e.g., an accelerometer), a gravity sensor component, and a rotation sensor component (e.g., a gyroscope).

[0099] Environmental components 1734 include, for example, one or more cameras (with still image / photo and video capabilities), lighting sensor components (e.g., a photometer), temperature sensor components (e.g., one or more thermometers that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., a barometer), acoustic sensor components (e.g., one or more microphones that detect background noise), proximity sensor components (e.g., an infrared sensor that detects nearby objects), gas sensors (e.g., a gas detection sensor for detecting concentrations of hazardous gases for safety purposes or for measuring pollutants in the atmosphere), or other components that can provide indications, measurements, or signals corresponding to the surrounding physical environment.

[0100] With respect to cameras, user device 102 may have a camera system including, for example, a front-facing camera on a front surface of user device 102 and a rear-facing camera on a rear surface of user device 102. The front-facing camera may, for example, be used to capture still images and videos of a user of user device 102 (e.g., a "selfie"), which may then be enhanced with the enhancement data (e.g., filters) described above. The rear-facing camera may, for example, be used to capture still images and videos in a more traditional camera mode, where the images are similarly enhanced using the enhancement data. In addition to the front-facing camera and the rear-facing camera, user device 102 may also include a 360° camera for capturing 360° photos and videos.

[0101] Additionally, the camera system of user device 102 may include dual rear cameras (e.g., a main camera and a depth sensing camera), or even triple, quad, or quintuple rear camera configurations on the front and back sides of user device 102. For example, these multi-camera systems may include a wide-angle camera, an ultra-wide-angle camera, a telephoto camera, a macro camera, and a depth sensor.

[0102] The location component 1736 includes a positioning sensor component (e.g., a GPS receiver component), an altitude sensor component (e.g., an altimeter or barometer that detects air pressure, from which the altitude can be obtained), an orientation sensor component (e.g., a magnetometer), etc.

[0103] A variety of technologies may be used to achieve communication. The I / O components 1702 also include a communication component 1738 that is operable to couple the machine 1700 to the network 1722 or device 1724 via a corresponding coupling or connection. For example, the communication component 1738 may include a network interface component or another suitable device that interfaces with the network 1722. In other examples, the communication component 1738 may include a wired communication component, a wireless communication component, a cellular communication component, a near field communication (NFC) component, Parts (e.g. Low energy consumption), Device 1724 may be another machine or any of a variety of peripheral devices (eg, a peripheral device coupled via USB).

[0104] In addition, the communication component 1738 can detect the identifier or include a component operable to detect the identifier. For example, the communication component 1738 can include a radio frequency identification (RFID) tag reader component, an NFC smart tag detection component, an optical reader component (e.g., an optical sensor for detecting one-dimensional bar codes such as Universal Product Code (UPC) bar codes, multi-dimensional bar codes such as Quick Response (QR) codes, Aztec codes, Data Matrix, Dataglyph, MaxiCode, PDF417, UltraCode, UCC RSS-2D bar codes, and other optical codes) or an acoustic detection component (e.g., a microphone for identifying an audio signal of a tag). In addition, various information can be derived via the communication component 1738, such as location via Internet Protocol (IP) geolocation, location information ... Positioning via signal triangulation, positioning via detection of NFC beacon signals that can indicate a specific position, etc.

[0105] Various memories (e.g., main memory 1714, static memory 1716, and memory of processor 1704) and storage unit 1718 may store one or more sets of instructions and data structures (e.g., software) used by or implementing any one or more of the methods or functions described herein. When executed by processor 1704, these instructions (e.g., instructions 1710) cause various operations to implement the disclosed examples.

[0106] The instructions 1710 may be sent or received via a network interface device (e.g., a network interface component included in the communication component 1738) using a transmission medium and using any of several well-known transmission protocols (e.g., Hypertext Transfer Protocol (HTTP)) over the network 1722. Similarly, the instructions 1710 may be sent or received via a coupling (e.g., a peer-to-peer coupling) to the device 1724 using a transmission medium.

[0107] Glossary

[0108] "Carrier signal" refers to any intangible medium that can store, encode or carry instructions for execution by a machine and includes digital or analog communications signals or other intangible media that facilitates communication of such instructions. Instructions may be sent or received over a network using a transmission medium via a network interface device.

[0109] "Client Device" refers to any machine that interfaces with a communications network to obtain resources from one or more server systems or other client devices. A client device may be, but is not limited to, a mobile phone, a desktop computer, a laptop computer, a portable digital assistant (PDA), a smart phone, a tablet computer, an ultrabook, a netbook, a laptop computer, a multiprocessor system, a microprocessor-based or programmable consumer electronics product, a game console, a set-top box, or any other communications device that a user may use to access a network.

[0110] "Communications network" means one or more parts of a network, which may be an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a part of the Internet, a part of the public switched telephone network (PSTN), a plain old telephone service (POTS) network, a cellular telephone network, a wireless network, A network, other type of network, or a combination of two or more such networks. For example, the network or a portion of the network may include a wireless network or a cellular network, and the coupling may be a code division multiple access (CDMA) connection, a global system for mobile communications (GSM) connection, or other type of cellular or wireless coupling. In this example, the coupling may implement any of various types of data transmission technologies, such as single carrier radio transmission technology (1xRTT), evolution data optimized (EVDO) technology, general packet radio service (GPRS) technology, enhanced data rate for GSM evolution (EDGE) technology, the third generation partnership project (3GPP) including 3G, fourth generation wireless (4G) network, universal mobile telecommunications system (UMTS), high speed packet access (HSPA), world wide interoperability for microwave access (WiMAX), long term evolution (LTE) standards, other data transmission technologies defined by various standard setting organizations, other long distance protocols, or other data transmission technologies.

[0111] "Component" refers to a device, a physical entity, or logic with boundaries defined by function or subroutine calls, branch points, APIs, or other techniques that provide partitioning or modularization for specific processing or control functions. Components can be combined with other components via their interfaces to perform machine processing. Components can be packaged functional hardware units designed for use with other components and can be part of a program that generally performs specific functions in related functions. Components can constitute software components (e.g., codes implemented on machine-readable media) or hardware components. "Hardware components" are tangible units that can perform certain operations and can be configured or arranged in a certain physical manner. In various examples, one or more computer systems (e.g., independent computer systems, client computer systems, or server computer systems) or one or more hardware components (e.g., processors or processor groups) of a computer system can be configured by software (e.g., applications or application parts) to perform hardware components that operate to perform certain operations described herein. Hardware components can also be implemented mechanically, electronically, or any suitable combination thereof. For example, a hardware component may include a dedicated circuit or logic that is permanently configured to perform certain operations. The hardware component may be a dedicated processor, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). The hardware component may also include a programmable logic or circuit system that is temporarily configured to perform certain operations by software. For example, the hardware component may include software executed by a general-purpose processor or other programmable processor. Once configured by such software, the hardware component becomes a specific machine (or a specific component of a machine) that is uniquely customized to perform the configured function, and is no longer a general-purpose processor. It should be understood that it can be decided whether to mechanically implement the hardware component in a dedicated and permanently configured circuit or in a circuit temporarily configured (for example, configured by software) for cost and time considerations. Therefore, the phrase "hardware component" (or "hardware-implemented component") should be understood to include a tangible entity, that is, an entity that is physically constructed, permanently configured (for example, hardwired) or temporarily configured (for example, programmed) to operate in some way or perform certain operations described herein. Considering an example in which a hardware component is temporarily configured (for example, programmed), it is not necessary to configure or instantiate each of the hardware components at any time. For example, in the case where a hardware component includes a general-purpose processor that is configured by software to become a special-purpose processor, the general-purpose processor can be respectively configured as different special-purpose processors (e.g., including different hardware components) at different times. Software accordingly configures one or more specific processors to, for example, constitute a specific hardware component at one time, and to constitute different hardware components at different times. Hardware components can provide information to other hardware components and receive information from other hardware components. Accordingly, the described hardware components can be considered to be coupled in communication.In the case of multiple hardware components being present at the same time, communication can be achieved by signal transmission (e.g., by appropriate circuits and buses) between or among two or more hardware components. In examples where multiple hardware components are configured or instantiated at different times, communication between such hardware components can be achieved, for example, by storing information in a memory structure accessible to multiple hardware components and retrieving information in the memory structure. For example, a hardware component can perform an operation, and the output of the operation is stored in a memory device coupled to it in communication. Then, another hardware component can access the memory device at a subsequent time to retrieve the stored output and process it. The hardware component can also initiate communication with an input device or an output device, and can operate on resources (e.g., a collection of information). The various operations of the example methods described herein can be performed at least in part by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform related operations. Whether it is temporarily configured or permanently configured, such a processor can constitute a processor-implemented component that operates to perform one or more operations or functions described herein. As used herein, "processor-implemented components" refer to hardware components implemented using one or more processors. Similarly, the method described in this article can be implemented at least in part by a processor, wherein one or more specific processors are examples of hardware. For example, at least some operations in the operation of the method can be performed by one or more processors 1704 or the parts implemented by the processor. In addition, one or more processors can also operate to support the execution of related operations in a "cloud computing" environment or as a "software as a service" (SaaS) operation. For example, at least some operations in the operation can be performed by a group of computers (as an example of a machine including a processor), wherein these operations can be accessed via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., API). The execution of some operations in the operation can be distributed between processors, not only can reside in a single machine, but also can be deployed across several machines. In some examples, a processor or a part implemented by a processor can be located in a single geographic location (e.g., in a home environment, an office environment, or a server cluster). In other examples, a processor or a part implemented by a processor can be distributed across several geographic locations.

[0112] "Computer-readable storage media" refers to both machine storage media and transmission media. Therefore, these terms include storage devices / media and carrier / modulated data signals. The terms "machine-readable medium", "computer-readable medium" and "device-readable medium" mean the same thing and can be used interchangeably in this disclosure.

[0113] "Transient messages" are messages that are accessible for a limited duration. Transient messages can be text, images, videos, etc. The access time for transient messages can be set by the sender of the message. Alternatively, the access time can be a default setting or a setting specified by the recipient. Regardless of the setting technique, the message is transient.

[0114] "Machine storage media" refers to a single or multiple storage devices and media (e.g., centralized or distributed databases, and associated caches and servers) that store executable instructions, routines, and data. Thus, the term should be considered to include, but is not limited to, solid-state memory and optical and magnetic media, including memory internal or external to the processor. Specific examples of machine storage media, computer storage media, and device storage media include: non-volatile memory, including, for example, semiconductor memory devices such as erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), FPGA, and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The terms "machine storage media", "device storage media", and "computer storage media" mean the same thing and may be used interchangeably in this disclosure. The terms "machine storage media", "computer storage media", and "device storage media" expressly exclude carrier waves, modulated data signals, and other such media (at least some of which are encompassed by the term "signal media").

[0115] “Non-transitory computer-readable storage medium” refers to tangible media capable of storing, encoding, or carrying instructions to be executed by a machine.

[0116] "Signal medium" refers to any intangible medium that is capable of storing, encoding or carrying instructions executed by a machine and includes digital or analog communication signals or other intangible media that facilitate the communication of software or data. The term "signal medium" should be deemed to include any form of modulated data signals, carrier waves, etc. The term "modulated data signal" refers to a signal that has one or more of its various characteristics set or changed in such a manner as to encode information in the signal. The terms "transmission medium" and "signal medium" mean the same thing and may be used interchangeably in this disclosure.

Claims

1. A method executed by one or more processors for providing an augmented effect on a device including a display and at least one camera, the method comprising: displaying a video on the display of the device, the video including data specifying camera settings and enhancements applied to the video; displaying a camera effects shortcut along with display of the video; receiving a user selection of the camera effect shortcut; and Based on receiving a user selection of the camera effect shortcut, displaying on the display a video feed from the at least one camera having the enhancement effect and camera settings specified by the data applied to the video feed.

2. The method according to claim 1, further comprising: An effect indicator is displayed with the video, the effect indicator identifying the name and creator of the enhancement effect.

3. The method according to claim 2, further comprising: receiving a selection of the effect indicator; displaying information about the enhancement effect; as well as The display action invokes a user interface element for the user to apply the enhancement effect to the video feed.

4. The method according to claim 3, wherein: Selection of the action-invoking user interface element results in application of the enhancement effect to the video feed but without application of the camera setting.

5. The method according to claim 1, further comprising: displaying a context indicator with the video, the context indicator identifying an audio track to play with the video; receiving a user selection of the context indicator; as well as Based on receiving a user selection of the context indicator, additional information related to the audio track is displayed.

6. The method according to claim 1, further comprising: displaying a confirmation user interface item prior to displaying the video feed from the at least one camera with the enhancements and camera settings; receiving a selection of the confirmation user interface item; as well as Based on receiving a selection of the confirmation user interface item, the video feed from the at least one camera is displayed with the enhancements and camera settings.

7. The method according to claim 2, further comprising: A contextual indicator is displayed with the video, the contextual indicator identifying an audio track to play with the video.

8. A computing device comprising: at least one camera device; monitor; one or more processors; as well as a memory storing instructions that, when executed by the one or more processors, configure the device to perform operations for providing an augmented effect, the operations comprising: displaying a video on the display of the device, the video including data specifying camera settings and enhancements applied to the video; Display camera effect shortcuts; receiving a user selection of the camera effect shortcut; and Based on receiving a user selection of the camera effect shortcut, displaying on the display a video feed from the at least one camera having the enhancement effect and camera settings specified by the data applied to the video feed.

9. The computing device of claim 8, wherein: The operations also include: An effect indicator is displayed with the video, the effect indicator identifying the name and creator of the enhancement effect.

10. The computing device of claim 9, wherein: The operations also include: receiving a selection of the effect indicator; displaying information about the enhancement effect; and The display action invokes a user interface element for the user to apply the enhancement effect to the video feed.

11. The computing device of claim 10, wherein: Selection of the action-invoking user interface element results in application of the enhancement effect to the video feed but without application of the camera setting.

12. The computing device of claim 8, wherein: The operations also include: displaying a context indicator with the video, the context indicator identifying an audio track to play with the video; receiving a user selection of the context indicator; and Based on receiving a user selection of the context indicator, additional information related to the audio track is displayed.

13. The computing device of claim 8, wherein: The operations also include: displaying a confirmation user interface item prior to displaying the video feed from the at least one camera with the enhancements and camera settings; receiving a selection of the confirmation user interface item; and Based on receiving a selection of the confirmation user interface item, the video feed from the at least one camera is displayed with the enhancements and camera settings.

14. The computing device of claim 9, wherein: The operations also include: A contextual indicator is displayed with the video, the contextual indicator identifying an audio track to play with the video.

15. A non-transitory computer-readable storage medium comprising instructions that, when executed by a computer, cause the computer to perform operations for providing an augmented effect on a device comprising a display and at least one camera, the operations comprising: displaying a video feed on the display of the device, the video feed captured by the at least one camera; displaying a camera effects shortcut associated with a set of augmented reality effects and camera settings; receiving a user selection of the camera effect shortcut; and Based on receiving a user selection of the camera effects shortcut, displaying on the display a modified video feed from the at least one camera in which the augmented reality effect and camera settings associated with the camera effects shortcut have been applied.

16. The computer-readable storage medium device according to claim 15, wherein: The operations also include: An effect indicator is displayed with the video, the effect indicator identifying the name and creator of the enhancement effect.

17. The computer-readable storage medium of claim 16, wherein: The operations also include: receiving a selection of the effect indicator; displaying information about the enhancement effect; and The display action invokes a user interface element for the user to apply the enhancement effect to the video feed.

18. The computer-readable storage medium of claim 17, wherein: Selection of the action-invoking user interface element results in application of the enhancement effect to the video feed but without application of the camera setting.

19. The computer-readable storage medium of claim 15, wherein: The operations also include: displaying a context indicator with the video, the context indicator identifying an audio track to play with the video; receiving a user selection of the context indicator; and Based on receiving a user selection of the context indicator, additional information related to the audio track is displayed.

20. The computer-readable storage medium of claim 15, wherein: The operations also include: displaying a confirmation user interface item prior to displaying the video feed from the at least one camera with the enhancements and camera settings; receiving a selection of the confirmation user interface item; and Based on receiving a selection of the confirmation user interface item, the video feed from the at least one camera is displayed with the enhancements and camera settings.

Citation Information

Patent Citations

  • Method for enhancing visual ability of human eyes based on MR glasses, system and equipment

    CN113709410A

  • Collaborative achievement interface

    US11455082B2

  • DIY effects image modification

    US20210258511A1

  • Displaying augmented reality content in messaging application

    US20210304505A1

  • Generating personalized map interface with enhanced icons

    WO2020197766A1