Display method and related apparatus

Abstract

The present application provides a display method and a related apparatus. The method is applied to an electronic device. The method comprises: displaying a playback progress bar of a first audio-video, and displaying the identifier of a first audio event on a first time segment on the playback progress bar, wherein the first audio event is used to mark first audio within the first time segment on the playback progress bar, and the first audio is a first type of audio recognized by the electronic device from audio of the first audio-video, or the first audio is determined by the electronic device on the basis of a user input; and displaying information of the first audio event. In the present application, identifiers of one or more audio events can be displayed on a playback progress bar of an audio-video, and information of the one or more audio events can be displayed. In this way, a user can quickly acquire information of audio marked by an audio event, thereby improving the efficiency of users in acquiring audio information.

Description

Display method and related devices

[0001] This application claims priority to Chinese Patent Application No. 202510183519.6, filed on February 18, 2025, entitled “Display Method and Related Apparatus”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of computer technology, and in particular to a display method and related apparatus. Background Technology

[0003] Mobile phones and other electronic devices can store audio and video. For example, after a user records audio and video using the system application on the electronic device, the device stores the recorded audio and video. If the user wants to obtain the audio information from the audio and video stored on the electronic device, they need to listen to the entire audio and video, or even repeatedly drag the playback progress bar to listen to a certain segment of audio. This makes obtaining audio information very inefficient. Summary of the Invention

[0004] This application discloses a display method and related apparatus that can display the identifiers of one or more audio events of an audio or video on the playback progress bar, and can also display the information of these one or more audio events. In this way, users can quickly obtain the audio information marked by the audio events, thereby improving the efficiency of users in obtaining audio information.

[0005] In a first aspect, this application provides a display method applied to an electronic device. The method includes: displaying a playback progress bar of a first audio / video, and displaying an identifier of a first audio event on a first time segment of the playback progress bar, wherein the first audio event is used to mark a first audio on the first time segment of the playback progress bar, and the first audio is a first type of audio identified by the electronic device from the audio of the first audio / video, or the first audio is determined by the electronic device based on user input; and displaying information about the first audio event.

[0006] In some examples, the initial audio and video are recorded by the electronic device itself, such as through a system application. This allows the electronic device to obtain the initial audio and video using its own built-in functions, without requiring the device to download any specific applications or connect and communicate with other devices such as cloud servers. In other examples, the initial audio and video are received by the electronic device from other devices (such as cloud servers). Thus, there are various ways to obtain the initial audio and video, leading to a wider range of applications.

[0007] In some examples, the first audio segment on the playback progress bar marked by the first audio event may not belong to the first audio / video, or it may belong partially or entirely to the first audio / video. Therefore, the audio of the first audio / video includes all the audio in the first audio; or, the audio of the first audio / video includes a portion of the audio in the first audio; or, the audio of the first audio / video does not include the first audio. Where the audio of the first audio / video does not include the first audio, the first audio is the audio of the first segment on the corresponding playback progress bar determined by the electronic device based on user input. For example, the first audio is the audio of the first audio region captured by the electronic device during the recording of the first audio / video based on user input in the first segment, or the first audio is the audio added by the electronic device to the first segment on the playback progress bar by the user's input. Thus, the first audio marked by the first audio event is not limited to the first audio / video; it can also be user-defined, thereby meeting users' personalized needs, broadening the application scope, and improving the user experience.

[0008] In the above method, users can quickly obtain the position of the audio event marked on the playback progress bar by observing the audio event identifiers displayed on the first audio / video playback progress bar. Furthermore, they can quickly obtain detailed information about the audio event marked by the displayed audio event information. Therefore, users can intuitively obtain audio information from the audio / video through the displayed content, without having to listen to the entire audio / video every time they need to obtain audio information, or repeatedly drag the playback progress bar to obtain information about the audio segment indicated by the audio information. This reduces user operations and effectively improves the efficiency of users in obtaining audio information from the audio / video. Moreover, users can perform operations such as audio editing, categorization, and forwarding on the first audio / video based on the quickly obtained audio events, thereby improving the efficiency of users in processing audio / video.

[0009] In one possible implementation, the second segment of the playback progress bar of the first audio and video is marked with an identifier of a second audio event. The second audio event is used to mark the second audio of the second segment of the playback progress bar. The first audio marked by the first audio event is a first type of audio recognized by the electronic device from the audio of the first audio and video. The second audio marked by the second audio event is determined by the electronic device based on user input.

[0010] In some examples, the electronic device displays information about a second audio event.

[0011] In some examples, the identifiers of the first and second audio events are displayed differently, for example, in terms of color, shape, size, or text.

[0012] In the above method, the electronic device can display different audio events obtained through different acquisition methods on the playback progress bar of the first audio and video. For example, the electronic device can automatically identify the first audio event of the first audio from the first audio and video, and the electronic device can display the second audio event of the second audio determined by the user input. Furthermore, the display methods for the different audio events obtained through different acquisition methods can be different. This allows users to quickly obtain the position of the various audio event markers on the playback progress bar of the first audio and video, eliminating the need to listen to the entire audio and video every time audio information is needed and to mentally determine the source of the audio based on what is heard, effectively improving the efficiency of users in obtaining audio information from audio and video.

[0013] In one possible implementation, the information of the first audio event includes one or more of the following: the name of the first audio event, the type of the first audio event, the type of the first audio, the first time segment on the playback progress bar corresponding to the first audio, one or more moments in the first time segment, audio track indication information or remarks information, wherein the type of the first audio event includes a first event type and a second event type. When the first audio is a first type of audio identified by the electronic device from the audio of the first audio and video, the type of the first audio event is the first event type. When the first audio is determined by the electronic device according to user input, the type of the first audio event is the second event type. The audio track indication information is used to indicate whether the audio of the first audio and video includes the first audio.

[0014] In some examples, the type of the first audio includes one or more of the following: animal sounds, human voices, or ambient sounds. Animal sounds can include the sounds of different animals, such as cats meowing, dogs barking, and birdsong. Human voices can include the voices of different people, such as children's voices, elderly people's voices, women's voices, and men's voices, and can also include sounds from different scenarios, such as singing, laughter, and crying. Ambient sounds can include sounds from different environments, such as concert sounds, fireworks sounds, applause sounds, and wind sounds.

[0015] In some examples, one or more moments in the first time period may include, for example, the start moment, the end moment, or the midpoint moment.

[0016] In some examples, the notes are notes received by the electronic device from the user regarding the first audio input.

[0017] In the above method, the electronic device can display event information of the first audio event, as well as audio information of the first audio tagged by the first audio event, with a variety of displayed information. Users can intuitively and quickly obtain detailed information about the first audio event through the interface display, greatly improving the efficiency of users in obtaining audio information from audio and video.

[0018] In one possible implementation, the first audio is determined by the electronic device based on user input, including: the first audio being the audio of a first audio region collected by the electronic device during a first time period during the recording of the first audio and video; or, the first audio being the audio of a first time period determined by the electronic device from the audio of the first audio and video based on user input after acquiring the first audio and video; or, the first audio being the audio input by the user received by the electronic device after acquiring the first audio and video (for example, the first audio being the audio added by the user to the first time period input on the playback progress bar received by the electronic device).

[0019] In the above methods, users can customize the first audio in various ways. For example, they can customize it when recording the first audio and video, or they can select a certain audio segment in the first audio and video after obtaining it, or they can manually input and add it, which effectively meets the user's personalized needs and greatly improves the user experience.

[0020] In one possible implementation, the playback progress bar used to display the identifier of the audio event is the audio playback progress bar of the first audio / video. Therefore, displaying the playback progress bar of the first audio / video and displaying the identifier of the first audio event on the playback progress bar for a first time period includes: if the first audio / video is first audio, then displaying the audio playback progress bar of the first audio and displaying the identifier of the first audio event on the first audio playback progress bar for a first time period, wherein the audio playback progress bar of the first audio is used to indicate the playback progress of the first audio; if the first audio / video is first video, then displaying the video playback progress bar and the audio playback progress bar of the first video, and displaying the identifier of the first audio event on the audio playback progress bar of the first video for a first time period, wherein the video playback progress bar of the first video is used to indicate the playback progress of the images in the first video, and the audio playback progress bar of the first video is used to indicate the playback progress of the audio in the first video.

[0021] In the above method, if the first audio / video is video, a video playback progress bar indicating the playback progress of the video image and an audio playback progress bar indicating the playback progress of the video audio can be displayed simultaneously, with audio event identifiers displayed on the audio playback progress bar. This allows users to intuitively see the audio playback progress and the displayed identifiers as audio event identifiers (i.e., event identifiers used to characterize audio information in the video), avoiding user confusion about the meaning of the displayed identifiers and further improving the efficiency of users obtaining audio information from the audio / video.

[0022] In one possible implementation, displaying the information of the first audio event includes: displaying the information of the first audio event after receiving input from the user identifying the first audio event.

[0023] In some examples, the electronic device displays information about the second audio event after receiving input from the user identifying the second audio event.

[0024] In the above method, the information of the first audio event can be displayed by default when the electronic device displays the identifier of the audio event, or it can be displayed after the electronic device receives the user's input of the identifier of the first audio event, which can meet the user's personalized needs.

[0025] In one possible implementation, the method further includes: receiving user input on the first audio event; and performing a first operation on the first audio event. For example, the first operation may include one or more of the following: playing the audio marked by the first audio event, editing the audio marked by the first audio event, editing information about the first audio event, or deleting the first audio event.

[0026] In the above method, the electronic device can operate the first audio event according to the user's input, providing the user with the operability of the audio event. The user can choose how to operate the audio event according to their own needs, further satisfying the user's personalized needs.

[0027] In one possible implementation, receiving user input on the first audio event includes: receiving first user input on the playback control when displaying the playback control corresponding to the first audio event; performing the first operation on the first audio event includes: playing the first audio marked by the first audio event in response to the first input.

[0028] In the above method, users can play the first audio marked by the first audio event individually through the playback control corresponding to the first audio event. In this way, when users want to listen to the first audio, they do not need to drag the playback progress bar. In particular, when they want to listen to the first audio multiple times, they do not need to drag the playback progress bar repeatedly, which effectively reduces user operations and improves the efficiency of users to obtain specific audio segments.

[0029] In one possible implementation, receiving user input for the first audio event includes: receiving a second input from the user for an identifier of the first audio event, the second input being used to move the position of the identifier of the first audio event on the playback progress bar from a first time period to a third time period; performing a first operation for the first audio event includes: in response to the second input, moving the identifier of the first audio event to the third time period on the playback progress bar, and setting the audio marked by the first audio event as the audio of the third time period on the playback progress bar.

[0030] In the above method, users can modify the audio marked by the first audio event by changing the position of the first audio event identifier on the playback progress bar. This not only provides users with a way to modify the audio segment they want to mark, but also makes the modification simple and convenient, effectively improving the user experience.

[0031] In one possible implementation, the information of the first audio event is editable information; receiving user input on the first audio event includes receiving third input from the user regarding the first information of the first audio event; performing the first operation on the first audio event includes modifying the first information of the first audio event in response to the third input. The first information can be any piece of information from the first audio event.

[0032] In some examples, where the first information includes a first time segment on the playback progress bar corresponding to the first audio, and / or one or more moments within the first time segment, the electronic device modifies the audio marked by the first audio event in response to a third input.

[0033] In some examples, where the first information is an audio track indication, if the audio track indication indicates that the audio of the first audio / video includes the first audio, then in response to the third input, the electronic device modifies the first audio from being within the main audio track of the first audio / video to being outside the main audio track of the first audio / video; for example, the first audio is now stored in the audio tag track. In other examples, where the first information is an audio track indication, if the audio track indication indicates that the audio of the first audio / video does not include the first audio, then in response to the third input, the electronic device modifies the first audio from being outside the main audio track of the first audio / video to being within the main audio track of the first audio / video; in this case, the first audio is now stored in the main audio track of the first audio / video.

[0034] In the above method, users can modify any information of the first audio event, such as the type of the audio event, the type of the audio marked by the audio event, the audio of the audio event, and whether the audio of the audio event is within the main audio track. There are many ways to edit, which can meet various editing needs of users and improve the user experience.

[0035] In one possible implementation, the first audio is the audio of a first audio region captured by the electronic device during a first time period during the recording of the first audio and video; the method further includes: displaying a recording interface for the first audio and video, the recording interface including a first control with an audio tag function; receiving a fourth input from the user to the first control at a first moment, and in response to the fourth input, enabling the audio tag function; receiving a fifth input from the user to the first control at a second moment, and in response to the fifth input, disabling the audio tag function, wherein the difference between the second moment and the first moment is the length of the first time period; between the first moment and the second moment, capturing the first audio of the first audio region and storing it in the audio tag track, and capturing the third audio of the second audio region and storing it in the main audio track of the first audio and video, wherein the first audio region and the second audio region are different, the main audio track of the first audio and video does not include the first audio in the audio tag track, and the audio of the first audio and video does not include the first audio.

[0036] In the above method, users can activate the audio tagging function at any time during the recording of the first audio / video file to record / mark audio in specific audio ranges. The electronic device can then create audio events indicating these audio tracks and store information about these events. The audio recorded by the audio tagging function can serve as additional audio identifiers for the first audio / video file, for example, recording its status, content, or other information. This allows users to quickly access information about the audio they tagged during the recording process by reviewing the audio events recorded by the audio tagging function. Furthermore, the first audio track in the audio tagging track can be excluded from the main audio track of the first audio / video file. This allows users to mask specific audio ranges within the first audio / video file, such as the sound of the person filming (i.e., the sound emitted by the filmer), thus meeting their personalized needs.

[0037] In one possible implementation, the method further includes: displaying a second control in the recording interface, the second control being used to set the audio region of the audio tagged by the audio tag function; receiving a sixth input from the user to the second control; and, in response to the sixth input, setting the direction and / or range of the first audio region.

[0038] In the above method, users can customize the audio region marked by the audio tag function. For example, in some scenarios, it is necessary to block the sound made by the photographer, so the above-mentioned audio region can be set to the photographer's audio region. In other scenarios, it is necessary to block the sound made by the subject, so the above-mentioned audio region can be set to the subject's audio region. In this way, the audio tag function can further meet the user's personalized needs.

[0039] In one possible implementation, the above method further includes: the electronic device displaying a settings interface for the audio tagging function; receiving a seventh input from the user to the settings interface; and in response to the seventh input, not storing all audio of the audio tagged by the audio tagging function in the main audio track of the recorded audio and video, or not storing the second type of audio (e.g., human voice audio) of the audio tagged by the audio tagging function in the main audio track of the recorded audio and video.

[0040] In the above method, users are provided with the ability to set the range of audio tags marked by the audio tag function. That is, users can choose to block only specific second-type audio (i.e., second-type audio in the audio tagged by the audio tag function is not stored in the main audio track of the recorded audio and video), or they can choose to block all audio (i.e., all audio in the audio tagged by the audio tag function is not stored in the main audio track of the recorded audio and video). In this way, the audio tag function can further meet the personalized needs of users.

[0041] In one possible implementation, the method further includes: displaying a first interface (e.g., an application interface for a photo album or recording), the first interface including a first category and a second category, the first category indicating a first audio scene, the second category indicating a second audio scene, the first category including one or more second audio / video files, the second category including one or more third audio / video files, the first category being determined based on the audio content in one or more second audio / video files, the second category being determined based on the audio content in one or more third audio / video files, and the one or more second audio / video files including the first audio / video file; the above-mentioned display of the playback progress bar of the first audio / video file includes: after receiving the user's eighth input on the first audio / video file in the first category, displaying the second interface, the second interface being used to display the first audio / video file, the second interface including the playback progress bar of the first audio / video file.

[0042] In some examples, the first category is determined based on audio events from one or more second audio / video sources, and the second category is determined based on audio events from one or more third audio / video sources.

[0043] In the above method, electronic devices can classify audio and video according to the audio content (e.g., audio events), grouping audio and video of the same audio scene into the same category and audio and video of different audio scenes into different categories. Users can select the audio and video of the audio scene they need (e.g., the first audio and video of the first audio scene under the first category) through the classification interface to view, thereby improving the efficiency of users in processing audio and video.

[0044] In one possible implementation, the initial audio and video are recorded by the electronic device using a system application. This eliminates the need for the user to download a specific application on the electronic device, reducing user interaction.

[0045] Secondly, this application provides an electronic device, including a processor and a memory; the memory is used to store a computer program, and the processor calls the computer program to execute the display method provided in the first aspect and any implementation thereof.

[0046] Thirdly, this application provides a computer storage medium storing a computer program, which, when executed by a processor, is used to perform the display method provided by the first aspect and any implementation thereof.

[0047] Fourthly, this application provides a computer program product, including a computer program that, when run on a processor, implements the display method provided by the first aspect and any implementation thereof.

[0048] Fifthly, this application provides a chip system including a processing circuit and an interface circuit. The interface circuit is used to receive code instructions and transmit them to the processing circuit. The processing circuit is used to execute the code instructions to perform the display method provided in the first aspect and any implementation thereof.

[0049] Sixthly, this application provides an electronic device that includes the methods or apparatus described in any aspect or embodiment of this application. The aforementioned electronic device is, for example, a chip.

[0050] It should be understood that the descriptions of technical features, technical solutions, beneficial effects, or similar language in this application do not imply that all features and advantages can be achieved in any single implementation. Rather, it is understood that the description of a feature or beneficial effect means that a specific technical feature, technical solution, or beneficial effect is included in at least one implementation. Therefore, the descriptions of technical features, technical solutions, or beneficial effects in this application do not necessarily refer to the same implementation. Furthermore, the technical features, technical solutions, and beneficial effects described in this application can be combined in any suitable manner. Those skilled in the art will understand that this application can be implemented without one or more specific technical features, technical solutions, or beneficial effects of a particular implementation. In other implementations, additional technical features and beneficial effects may be identified in specific implementations that do not embody all implementations. Attached Figure Description

[0051] The following describes the accompanying drawings used in this application.

[0052] Figure 1 is a schematic diagram of the hardware structure of an electronic device provided in this application;

[0053] Figure 2 is a schematic diagram of the software architecture of an electronic device provided in this application;

[0054] Figures 3A-3D are schematic diagrams of a user interface for entering the post-editing mode of a video provided in this application;

[0055] Figures 4A-4D are schematic diagrams of a user interface for entering a post-editing mode of video provided in this application;

[0056] Figures 5A-5D are schematic diagrams of a user interface for displaying audio events provided in this application;

[0057] Figures 6A and 6B are schematic diagrams of a user interface for playing audio indicating an audio event, provided in this application.

[0058] Figures 7A-7C are schematic diagrams of a user interface for modifying the timing information of an audio event provided in this application;

[0059] Figures 8A-8F are schematic diagrams of a user interface for modifying audio event information provided in this application;

[0060] Figures 9A-9C are schematic diagrams of a user interface for deleting audio events provided in this application;

[0061] Figures 10A-10C are schematic diagrams of an audio editing interface corresponding to an audio event indicator provided in this application;

[0062] Figures 11A-11C are schematic diagrams of a user interface for creating a new audio event in a video post-editing interface provided by this application;

[0063] Figures 12A and 12B are schematic diagrams of a video shooting scenario provided in this application;

[0064] Figures 13A-13J are schematic diagrams of a user interface for creating a new audio event during video recording provided in this application;

[0065] Figure 14 is a schematic diagram of another user interface for displaying audio events provided in this application;

[0066] Figures 15A-15C are schematic diagrams of a settings interface provided in this application;

[0067] Figures 16A-16E are schematic diagrams of another user interface for displaying audio events provided in this application;

[0068] Figure 17 is a flowchart illustrating the audio event acquisition process provided in this application;

[0069] Figure 18 is a flowchart illustrating another audio event acquisition process provided in this application;

[0070] Figure 19 is a flowchart illustrating another audio event acquisition process provided in this application;

[0071] Figure 20 is a flowchart illustrating a display method provided in this application. Detailed Implementation

[0072] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings. The terminology used in the implementation section of this application is only for explaining specific embodiments of this application and is not intended to limit this application.

[0073] In the description of the embodiments of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. The "and / or" in the text is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of this application, "multiple" means two or more.

[0074] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as implying or suggesting relative importance or implicitly indicating the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature, and in the description of the embodiments of this application, unless otherwise stated, "multiple" means two or more.

[0075] The term "user interface (UI)" used in the following embodiments of this application refers to the medium interface through which an application or operating system interacts and exchanges information with the user. It realizes the conversion between the internal form of information and the form that the user can accept. The user interface is source code written in a specific computer language such as Java or Extensible Markup Language (XML). The interface source code is parsed and rendered on the electronic device, ultimately presenting content that the user can recognize. A common form of user interface is the graphical user interface (GUI), which refers to a user interface related to computer operation displayed graphically. It can be visible interface elements such as text, icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, and widgets displayed on the screen of an electronic device.

[0076] Currently, mobile phones and other electronic devices can store audio and video. This audio and video can be recorded by the user through an application on the device or downloaded to the device. If a user wants to retrieve the audio information from a stored audio or video, they need to listen to the entire video. Furthermore, the information obtained is "one-time"; for example, after listening to the entire video and obtaining the audio information, if the user wants to retrieve the audio information again after a period of time, they need to listen to the entire video again. Moreover, if a user wants to obtain detailed information about a specific audio segment, they need to repeatedly drag the playback progress bar to listen to that audio segment multiple times. This process is cumbersome for users and results in very low efficiency in retrieving audio information from videos.

[0077] Users may acquire audio information for purposes such as audio editing, categorization, and forwarding. Low efficiency in acquiring audio information leads to reduced efficiency in processing audio and video. For example, when users want to edit audio in an audio-visual program, they often need to obtain detailed information on multiple audio segments within the entire program within a short period of time. This allows them to select the desired audio segments for trimming, replacement, adding sound effects, and audio extraction. However, for each audio segment, users need to repeatedly drag the playback progress bar to listen to that segment multiple times, resulting in very low efficiency in audio editing.

[0078] This application provides a display method applied to an electronic device 100. The electronic device 100 can store information about a first audio / video file and one or more audio events of the first audio / video file. When displaying the first audio / video file, the electronic device 100 can display a playback progress bar for the first audio / video file, and display identifiers of one or more audio events of the first audio / video file during one or more time periods on the playback progress bar. Each audio event is used to indicate / mark the audio of the corresponding time period on the playback progress bar. For example, the identifier of the first audio event is displayed during the first time period on the playback progress bar, and the identifier of the second audio event is displayed during the second time period on the playback progress bar. The first audio event indicates / marks the audio of the first time period on the playback progress bar, and the second audio event indicates / marks the audio of the second time period on the playback progress bar. Furthermore, when displaying the first audio / video file, the electronic device 100 can display information about one or more audio events of the first audio / video file, including, but not limited to, one or more of the following: the type of audio indicated by the audio event, the type of audio event (e.g., whether it is user-defined), the time period corresponding to the audio event (i.e., the time period of the audio indicated by the audio event), and the time of the audio event (e.g., start time, end time, or time point). In some embodiments, the electronic device 100 may also display playback controls corresponding to one or more audio events of the first audio / video, wherein the playback control corresponding to any one audio event is used to play the audio indicated by that audio event. An audio event can be understood as an annotation / note to the indicated audio.

[0079] In this way, users can quickly determine the position of the audio event indicated by the audio event on the playback progress bar through the audio event identifier displayed on the first audio / video playback progress bar. Furthermore, they can quickly obtain detailed information about the audio event indicated by the displayed audio event information and playback controls. Therefore, users can intuitively obtain audio information from the audio / video through the displayed content, without having to listen to the entire audio / video every time they need to obtain audio information, or repeatedly drag the playback progress bar to obtain information about the audio segment indicated by the audio event. This reduces user operations and effectively improves the efficiency of users obtaining audio information from the audio / video. Moreover, users can perform operations such as audio editing, categorization, and forwarding on the first audio / video based on the quickly obtained audio events, thereby improving the efficiency of users processing audio / video.

[0080] The audio indicated by the audio event can be a specific type of audio recognized by the electronic device 100 from the audio of the first audio and video, such as clapping, singing, or laughter. This can be understood as the device automatically recognizing audio events. Alternatively, the audio indicated by the audio event can be determined by the electronic device 100 based on user input during or after recording the first audio and video, and can be understood as a user-defined audio event. The audio of the first audio and video may or may not include the audio indicated by the audio event. The audio indicated by the audio event can be understood as "valid audio" related to the first audio and video. In this way, users can intuitively obtain the "valid audio" related to the first audio and video through the relevant content of the audio events displayed on the interface, while the device automatically filters out "invalid audio" from the first audio and video, improving the efficiency of users obtaining audio information from the audio and video.

[0081] In some embodiments, the electronic device 100 may, in response to user input, perform one or more of the following: modify audio event information, delete audio event, or create new audio event. Modifying audio event information may include one or more of the following: modifying the time period corresponding to the audio event (actually modifying the audio indicated by the audio event), modifying the type of audio event, or modifying the type of audio indicated by the audio event. This can meet the user's personalized needs and improve the user experience.

[0082] The audio and video in this application embodiment can be multimedia content that includes sound but does not include images (i.e., audio, also referred to as sound), or multimedia content that includes both sound and images (e.g., video or audio-visual photographs, which will be collectively referred to as video for ease of explanation). The audio portion of the audio and video can include audio signals / sound signals, such as human voices, music, sound effects, etc.

[0083] The following is an exemplary description of the electronic device 100 provided in an embodiment of this application.

[0084] In this application embodiment, the electronic device 100 can be any of the following: mobile phone, tablet computer, handheld computer, desktop computer, laptop computer, ultra-mobile personal computer (UMPC), netbook, cellular phone, personal digital assistant (PDA), as well as smart home devices such as smart screens and smart speakers, wearable devices such as smart bracelets, smartwatches, and smart glasses, extended reality (XR) devices such as augmented reality (AR), virtual reality (VR), and mixed reality (MR), in-vehicle devices, or smart city devices.

[0085] It should be understood that the electronic device 100 illustrated in the embodiments of this application is merely an example, and the electronic device 100 may have more or fewer components than those illustrated in the embodiments of this application, may combine two or more components, or may have different component configurations. The various components shown in the figures may be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application-specific integrated circuits.

[0086] Figure 1 is a schematic diagram of the hardware structure of an electronic device 100 provided in an embodiment of this application.

[0087] As shown in Figure 1, the electronic device 100 may include a processor 110, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a microphone 170B, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a humidity sensor 180I, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a heart rate sensor 180M, and an electrocardiogram sensor 180N, etc.

[0088] Processor 110 may include one or more processing units, such as: application processor (AP), microcontroller unit (MCU), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU), etc. The different processing units may be independent devices or integrated into one or more processors. For example, the application processor may include a graphics processor and a digital signal processor, and the microcontroller unit may include a graphics processor.

[0089] The controller can generate operation control signals based on the instruction opcode and timing signals to complete the control of instruction fetching and execution.

[0090] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0091] In some embodiments, the processor 110 may include one or more interfaces. Interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0092] Internal memory 121 may include one or more random access memory (RAM) and one or more non-volatile memory (NVM). The RAM can be directly read and written by the processor 110 and can be used to store executable programs (e.g., machine instructions) of the operating system or other running programs, as well as user and application data. The NVM can also store executable programs and user and application data, and can be pre-loaded into the RAM for direct read and write operations by the processor 110.

[0093] The charging management module 140 is used to receive charging input from the charger. The charger can be a wireless charger or a wired charger.

[0094] The power management module 141 is used to connect the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140 to power the processor 110, internal memory 121, display 194, wireless communication module 160, and sensor module 180, etc.

[0095] The wireless communication function of electronic device 100 can be implemented through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor, and baseband processor.

[0096] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with tuning switches.

[0097] The mobile communication module 150 can provide wireless communication solutions for applications on the electronic device 100, including second-generation (2G), third-generation (3G), fourth-generation (4G), fifth-generation (5G), and sixth-generation (6G) mobile communication technologies. The mobile communication module 150 may include at least one filter, switch, power amplifier, low-noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some functional modules of the mobile communication module 150 may be housed in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be housed in the same device.

[0098] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal is transmitted to an application processor or microcontroller unit. The application processor or microcontroller unit outputs sound signals through an audio device (not limited to speaker 170A, microphone 170B, etc.) or displays images or videos through a display screen 194. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 110 and housed within the same device as the mobile communication module 150 or other functional modules.

[0099] The wireless communication module 160 can provide solutions for wireless communication applications on the electronic device 100, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), Sparklink Alliance-specific wireless communication technologies (such as Sparklink Low Energy (SLE) and Sparklink Basic (SLB)), and intrabody communication (IBC). The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0100] In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, enabling electronic device 100 to communicate with networks and other devices via wireless communication technology. The wireless communication technology may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time-Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, IR, Starflash, and / or IBC technology, etc. The GNSS may include the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou Navigation Satellite System (BDS), the Quasi-Zenith Satellite System (QZSS), and / or satellite-based augmentation systems (SBAS).

[0101] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a miniature LED, a microLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, electronic device 100 may include one or N displays 194, where N is a positive integer greater than 1.

[0102] Electronic device 100 can perform shooting functions through ISP, camera 193, video codec, GPU, display 194 and application processor.

[0103] The ISP (Image Signal Processor) is used to process data fed back from the camera 193. For example, when taking a picture, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, and the camera's photosensitive element transmits the electrical signal to the ISP for processing, transforming it into an image visible to the naked eye. The ISP can also perform algorithmic optimization of image noise, brightness, and color. The ISP can also optimize parameters such as exposure and color temperature of the shooting scene. In some embodiments, the ISP can be set in the camera 193.

[0104] Camera 193 is used to capture still images or videos. An object is projected onto a photosensitive element by generating an optical image through the lens. The photosensitive element can be a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, which is then passed to an ISP for conversion into a digital image signal. The ISP outputs the digital image signal to a DSP for processing. The DSP converts the digital image signal into image signals in standard RGB, YUV, or other formats. In some embodiments, the electronic device 100 may include one or N cameras 193, where N is a positive integer greater than 1.

[0105] A digital signal processor is used to process digital signals.

[0106] Video codecs are used to compress or decompress digital video. Electronic device 100 may support one or more video codecs. Thus, electronic device 100 can play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

[0107] An NPU (Neural Processing Unit) is a computational processor for neural networks (NNs). By borrowing the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it can rapidly process input information and continuously learn on its own. NPUs enable intelligent cognitive applications in electronic devices, such as image recognition, facial recognition, speech recognition, and text understanding.

[0108] Electronic device 100 can implement audio functions such as music playback and recording through audio module 170, speaker 170A, microphone 170B, and processor 110.

[0109] The audio module 170 is used to convert digital audio information into analog audio signals for output, and also to convert analog audio input into digital audio signals. The audio module 170 can also be used for encoding and decoding audio signals. In some embodiments, the audio module 170 may be located in the processor 110, or some functional modules of the audio module 170 may be located in the processor 110.

[0110] The speaker 170A, also known as a "loudspeaker," is used to convert audio electrical signals into sound signals. The electronic device 100 can listen to music or make hands-free calls through the speaker 170A.

[0111] Microphone 170B, also known as a "microphone" or "voice transducer," is used to convert sound signals into electrical signals. When recording audio or video, microphone 170B can capture sound signals such as human voices and ambient sounds. Electronic device 100 can be equipped with one or more microphones 170B. In some embodiments, electronic device 100 can be equipped with two microphones 170B, which, in addition to capturing sound signals, can also perform noise reduction. In some embodiments, electronic device 100 can also be equipped with three, four, or more microphones 170B, enabling sound signal capture, noise reduction, sound source identification, and directional recording, among other functions.

[0112] In some embodiments, when recording audio, the electronic device 100 can acquire sound signals from one or more sound zones through one or more microphones 170B, and store some or all of the acquired sound signals into the main audio track to obtain the recorded audio. The different sound zones can be located at different positions on the electronic device 100.

[0113] In some embodiments, when playing audio, the electronic device 100 can play the sound signal within the main audio track through, for example, a speaker 170A or other module.

[0114] In some embodiments, when recording video, the electronic device 100 can acquire image signals through the camera 193 and acquire sound signals from one or more audio ranges through one or more microphones 170B, and use some or all of the acquired image signals as the image content of the video, and store some or all of the acquired sound signals into the main audio track of the video as the audio content of the video, thereby obtaining the recorded video.

[0115] In some embodiments, when playing a video, the electronic device 100 can display the image signal of the video through the display screen 194 and play the sound signal in the main audio track of the video through, for example, the speaker 170A or other modules.

[0116] Pressure sensor 180A is used to sense pressure signals and convert them into electrical signals. In some embodiments, pressure sensor 180A may be disposed on display screen 194. When a touch operation is applied to display screen 194, electronic device 100 detects the intensity of the touch operation based on pressure sensor 180A. Electronic device 100 may also calculate the touch position based on the detection signal from pressure sensor 180A. In some embodiments, touch operations applied to the same touch position but with different touch operation intensities may correspond to different operation commands. For example: when a touch operation with an intensity less than a first pressure threshold is applied to the SMS application icon, a command to view an SMS message is executed. When a touch operation with an intensity greater than or equal to the first pressure threshold is applied to the SMS application icon, a command to create a new SMS message is executed.

[0117] The gyroscope sensor 180B can be used to determine the motion attitude of the electronic device 100. In some embodiments, the angular velocity of the electronic device 100 about three axes (i.e., the x, y, and z axes) can be determined by the gyroscope sensor 180B. The gyroscope sensor 180B can be used in scenarios such as image stabilization, navigation, and motion-sensing games.

[0118] The 180C barometric pressure sensor is used to measure barometric pressure.

[0119] The magnetic sensor 180D includes a Hall sensor. In some embodiments, when the electronic device 100 is a flip phone, the electronic device 100 can detect the opening and closing of the flip based on the magnetic sensor 180D. In some embodiments, when the electronic device 100 is a wearable device, the electronic device 100 can detect the wearing status of the electronic device 100 based on the magnetic sensor 180D.

[0120] The accelerometer 180E can detect the magnitude of acceleration of electronic device 100 in various directions (generally three axes).

[0121] A distance sensor 180F is used to measure distance. In some embodiments, during a shooting scene, the electronic device 100 can utilize the distance sensor 180F to measure distance for fast focusing.

[0122] The proximity light sensor 180G may include, for example, a light-emitting diode (LED) and a light detector. The light detector may be, for example, a photodiode, and the light emitter may be, for example, a light-emitting diode.

[0123] The fingerprint sensor 180H is used to collect fingerprints. The electronic device 100 can utilize the characteristics of the collected fingerprints to achieve fingerprint unlocking, fingerprint photography, etc.

[0124] The humidity sensor 180I is used to detect humidity.

[0125] The 180J temperature sensor is used to detect temperature.

[0126] Touch sensor 180K, also known as a "touch device," can be located on display screen 194. The touch sensor 180K and display screen 194 together form a touchscreen, also known as a "touchscreen." Touch sensor 180K detects touch operations applied to or near it. The touch sensor can transmit the detected touch operation to processor 110 (such as an application processor or microcontroller unit) to determine the type of touch event. Visual output related to the touch operation can be provided through display screen 194. In other embodiments, touch sensor 180K may also be located on the surface of electronic device 100, in a different position than display screen 194.

[0127] The ambient light sensor 180L is used to sense the ambient light intensity. The electronic device 100 can adaptively adjust the brightness of the display screen 194 according to the sensed ambient light intensity. The ambient light sensor 180L can also be used to automatically adjust the white balance when taking pictures.

[0128] The 180M heart rate sensor can be used for heart rate detection. The 180N electrocardiogram (ECG) sensor can be used for ECG detection.

[0129] Buttons 190 include a power button, volume buttons, etc. Buttons 190 can be mechanical buttons or touch-sensitive buttons. Electronic device 100 can receive button input and generate key signal inputs related to user settings and function control of electronic device 100.

[0130] Motor 191 can generate vibration alerts. Motor 191 can be used for incoming call vibration alerts or for touch vibration feedback. For example, different vibration feedback effects can be corresponding to touch operations applied to different applications (such as taking photos, playing audio, etc.).

[0131] Indicator 192 can be an indicator light, used to indicate charging status, power changes, or to indicate messages, missed calls, notifications, etc.

[0132] The SIM card interface 195 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to make contact with and detach from the electronic device 100. The electronic device 100 can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, etc. In some embodiments, the electronic device 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from it.

[0133] The electronic device 100 provided in this application embodiment can run an operating system (OS). This operating system can be various operating systems used in industry, such as an operating system based on OpenHarmony, like HarmonyOS; or other operating systems such as Android. TM An operating system can be the iOS mobile operating system; it can also be various open-source operating systems or their derivatives, such as Linux OS, and other embedded operating systems; it can also be a future new type of operating system, such as an AI operating system based on artificial intelligence. An operating system is a set of interconnected system software programs that manage and control the operation of electronic devices, utilize and run hardware and software resources, and provide public services to organize user interaction. In an electronic device 100, the operating system connects downwards to the physical devices at the hardware layer and provides a runtime environment for application software upwards.

[0134] An operating system typically includes a kernel layer, a middleware layer, and an application layer. The application layer includes applications, which can include system applications and third-party applications. The middleware layer includes a suite of software providing various services to application developers, or frameworks providing services such as databases, multimedia, and graphics, or capabilities such as distributed scheduling and system scaling. For example, the middleware layer may include a framework layer and / or a system service layer. The framework layer provides application programming interfaces (APIs) and programming frameworks for applications in the application layer. The system service layer includes the system's core capabilities, providing services to applications through the framework layer. The kernel layer is the layer between hardware and software. The kernel layer may include hardware drivers and the operating system kernel. In addition to providing hardware drivers, the kernel layer also supports functions such as memory management and system process management.

[0135] The electronic devices we use in our daily lives come in various types and forms, and are applied in a wide range of scenarios. Therefore, based on the different forms and functions of electronic devices, different application scenarios, and different user needs, the operating systems used in these devices may also differ. The basic functions implemented by the electronic device 100 provided in this application can be implemented using a general-purpose operating system or a dedicated operating system. To more clearly illustrate the implementation of the embodiments of this application under a specific operating system, the architecture of HarmonyOS is shown below. Those skilled in the art can deduce the implementation of the embodiments of this application under other specific operating systems, such as Android. TM Implementation under operating systems, etc.

[0136] Figure 2 is a schematic diagram of the software architecture of an electronic device 100 provided in an embodiment of this application.

[0137] As shown in Figure 2, the software architecture of the electronic device 100 can be divided into several layers. In some embodiments, from bottom to top, these layers are: kernel layer, system service layer, framework layer, and application layer. Layers communicate with each other through software interfaces. System functions can be tailored, added, or combined at the subsystem granularity in different device deployment scenarios, and each subsystem can also be tailored, added, or combined at the functional granularity.

[0138] The kernel layer can include: Kernel Abstract Layer (KAL), kernel subsystem, driver subsystem, etc.

[0139] Kernel Abstraction Layer: By shielding the differences between multiple kernels, it provides basic kernel capabilities to the upper layers, including but not limited to process / thread management, memory management, file system, network management, and peripheral device management.

[0140] Kernel Subsystem: Supports the selection of a suitable OS kernel for different resource-constrained devices, including but not limited to Linux kernel, HarmonyOS kernel, LiteOS (Lite Operating System), etc.

[0141] Driver Subsystem: The driver framework is the foundation for the open system hardware ecosystem, providing unified peripheral access capabilities and a framework for driver development and management. The driver framework includes: display drivers, camera drivers, audio drivers, Bluetooth drivers, sensor drivers, etc.

[0142] The system service layer may include the core capabilities of the system, providing services to applications through the framework layer. This layer includes, but is not limited to, the following subsystems:

[0143] The system's basic capability subsystem set provides the foundational capabilities for the operation, scheduling, and migration of distributed applications across multiple devices. This set may include distributed soft bus, distributed data management, distributed task scheduling, and Ark multi-language runtime; it may also include multi-modal input subsystem, graphics subsystem, security subsystem, and artificial intelligence (AI) business subsystem.

[0144] Basic software service subsystem set: provides public and general software services; the basic software service subsystem set may include event notification subsystem, telephone service subsystem, multimedia subsystem, audio framework system, etc.

[0145] Enhanced software service subsystem suite: Provides differentiated enhanced software services for different devices; the enhanced software service subsystem suite may include smart screen proprietary business subsystem, wearable proprietary business subsystem, IoT proprietary business subsystem, etc.

[0146] Hardware service subsystem set: Provides hardware services; the hardware service subsystem set may include location service subsystem, user IAM (identity and access management) subsystem, wearable proprietary hardware service subsystem, biometric identification, IoT proprietary hardware service subsystem, etc.

[0147] Distributed task scheduling enables distributed service management (discovery, synchronization, registration, and invocation), supporting remote startup, remote invocation, remote connection, and migration of applications across devices.

[0148] Distributed data management enables data synchronization, data storage, data sharing, and data access across all scenarios and devices.

[0149] The distributed soft bus provides communication-related capabilities for seamless interconnection between multiple devices, including: WLAN service capabilities, Bluetooth service capabilities, soft bus, inter-process communication RPC (Remote Procedure Call), and StarFlash communication capabilities.

[0150] Ark Multilingual Runtime is a unified compilation runtime platform designed to support the joint compilation and execution of multiple programming languages ​​and multiple chip platforms.

[0151] The framework layer provides application programming interfaces (APIs) and programming frameworks for applications in the application layer. The framework layer includes: the ArkUI framework (which provides a complete infrastructure for UI development of system applications, including UI functions such as components, layouts, animations, and interactive events, as well as a real-time interface preview tool), the user application framework, and the Ability framework (an Ability is a lightweight application; the Ability framework schedules and manages the operation and lifecycle of Abilities). Different devices may have different operating systems, and therefore support different APIs.

[0152] The HarmonyOS API is a series of open capabilities provided to support HarmonyOS application development. The HarmonyOS API can be set at the framework layer or independently of the framework layer. The HarmonyOS API includes the Audio API (audio service), Push API (push service), and Account API (account service), among others.

[0153] Applications can include system applications (APPs) and extended / third-party apps. System applications can include desktop, settings, recorder, camera, gallery, audio and video editing, etc., while extended / third-party apps can include video editing, social networking, etc.

[0154] In some embodiments, when displaying the first audio / video in system applications such as recorders, gallery apps, and audio / video editors, the playback progress bar of the first audio / video can display an identifier for one or more audio events, and information about these audio events can also be displayed. Furthermore, audio event editing functions can be provided in system applications such as recorders, gallery apps, and audio / video editors, such as modifying audio event information, deleting audio events, and creating new audio events. Not limited to this, in other embodiments, the above functions can also be implemented in extended apps / third-party apps.

[0155] Understandably, multiple applications can be integrated into one application, or one application can be divided into multiple applications. For example, audio and video editing can be integrated into a recorder to provide audio editing functions, and audio and video editing can also be integrated into a gallery to provide video editing functions. The application in the embodiments of this application can also be replaced with other forms of software such as applets or atomic services.

[0156] In some embodiments, the middleware layer can provide a simple and easy-to-understand interface, such as the HarmonyOS API, which applications can call to provide functions such as displaying and editing audio events.

[0157] The following describes, by way of example, the application scenarios and user interface diagrams of the embodiments of this application.

[0158] Figures 3A-3D are schematic diagrams of a user interface for entering the post-editing mode of a video according to an embodiment of this application.

[0159] As shown in Figure 3A, the electronic device 100 can display a desktop 310, which may include icons for multiple applications, such as an icon 311 for a gallery application, an icon for a voice recorder application, an icon for a camera application, and so on. In some embodiments, the electronic device 100 can receive user input (e.g., a touch click) applied to the icon 311 of the gallery application on the desktop 310. In response to the user input, the electronic device 100 can launch the gallery application and display its user interface. A specific example can be found in Figure 3B.

[0160] As shown in Figure 3B, the electronic device 100 can display a user interface 320 for a gallery application. The user interface 320 can include multiple categories 321 under "Albums," such as a "Camera" category (including still images and videos taken via the camera application), a "All Photos" category (including still images stored by the electronic device 100), a "Videos" category 321A (including videos stored by the electronic device 100), a "Screenshot / Screen Recording" category (including still images captured using the screenshot function of the electronic device 100 and videos recorded using the screen recording function of the electronic device 100), and a "Social" category (including still images and videos from social applications). The user interface 320 can also include a display bar 322 at the bottom, which includes, for example, "Photos," "Albums," "Moments," and "Discover" options. The "Albums" option can be selected, indicating that the user interface 320 is the display interface corresponding to the "Albums" option. In some embodiments, electronic device 100 may receive user input (e.g., touch click operation) applied to “video” category 321A. In response to the user input, electronic device 100 may display the user interface of “video” category 321A. For a specific example, see Figure 3C.

[0161] As shown in Figure 3C, the electronic device 100 can display a user interface 330 for a gallery application. The user interface 330 can display a list of videos under the "Videos" category 321A shown in Figure 3B. This video list can include one or more videos stored by the electronic device 100, such as video 331 (duration "00:10"), video 332 (duration "00:30"), video 333 (duration "00:08"), and video 334 (duration "00:42"). In some embodiments, the electronic device 100 can receive user input (e.g., a touch click) applied to any of the videos displayed on the user interface 330 (video 333 is used as an example). In response to this user input, the electronic device 100 can display information about video 333. A specific example can be found in Figure 3D.

[0162] As shown in Figure 3D, the electronic device 100 can display the user interface 340 of the gallery application. The user interface 340 can include information about the video 333 shown in Figure 3C: the recording time 341 of the video 333 (e.g., "December 15, 2024, 14:15"), the playback area 342 of the video 333 (for displaying the image of the video 333), the playback control 343 of the video 333 (for controlling the playback and pausing of the video 333), the playback time information 344 of the video 333 (including the playback time point "00:00" and the total duration "00:08"), the playback progress bar 345 of the video 333, and the playback node 346 of the video 333. The playback progress bar 345 may include multiple image frames displayed in the order of video playback, such as from early to late and from left to right in the order of video playback. The multiple image frames displayed on the playback progress bar 345 may be some or all of the image frames in video 333, and the display format of each image frame may be the image content of that image frame. Different positions of the playback progress bar 345 correspond to / represent different time points (time points are moments) in video 333. For example, the starting point of the playback progress bar 345 corresponds to / represents the starting time point "00:00" of video 333, and the ending point of the playback progress bar 345 corresponds to / represents the ending time point "00:08" of video 333. The display position of the playback node 346 on the playback progress bar 345 represents / corresponds to the time point when video 333 is currently playing (i.e., the playback time point in playback time information 344). When video 333 has not started playing, the playback time point in playback time information 344 is "00:00", and playback node 346 is located at the starting point of the playback progress bar 345. When video 333 is played in playback area 342, the playback time point in playback time information 344 will increase (maximum "00:08"), and playback node 346 will move from the starting point of playback progress bar 345 (at most to the end point of video playback progress bar 345), for example, moving to the right on playback progress bar 345.

[0163] As shown in Figure 3D, the user interface 340 may also include an operation bar 347 for the video 332. The operation bar 347 may include one or more operation controls for the video 333, such as a share control, a favorite control, an edit control 347A, a delete control, and a more control (used to trigger the display of more operation controls for the video 333). The edit control 347A can be used to trigger entry into the post-editing mode of the video 333. In some embodiments, the electronic device 100 may receive user input (e.g., a touch click) applied to the edit control 347A. In response to this user input, the electronic device 100 may display the post-editing interface of the video 333. A specific example can be seen in Figure 5A below, which will not be detailed further.

[0164] Figures 4A-4D are schematic diagrams of a user interface for entering the post-editing mode of a video, as provided in the embodiments of this application.

[0165] As shown in Figure 4A, the electronic device 100 can display a user interface 410 for a gallery application. In some embodiments, the electronic device 100 can display the user interface 410 in response to user input (e.g., a touch click) acting on the gallery application icon 311 on the desktop 310 shown in Figure 3A. The user interface 410 may include multiple categories 321 under "Albums", multiple folders 411 under "Smart Categories", content under "Recently Deleted" (not shown), and a display bar 322 at the bottom. The multiple categories 321 under "Albums" and the display bar 322 at the bottom are described in Figure 3B. The multiple folders 411 under "Smart Categories" include, for example, a folder 411A for "People" (e.g., containing 28 images), a folder 411B for "Locations" (e.g., containing 8 images), and a folder 411C for "Sounds" (e.g., containing 6 images). The images (including still images and / or videos) under folder 411A can be categorized according to the people in the images. The images under folder 411B can be categorized according to the location of the images. Images in folder 411C can be categorized according to image-related audio (hereinafter referred to as image audio), which can be understood as categorizing them according to the audio scene in which the image is located. In some embodiments, images in folder 411C can be categorized according to the audio events of the image audio. In some embodiments, images in folder 411C can be categorized according to image audio and image content. Wherein, if the image is a still image (in this case, a photo with sound), the image audio is the audio recorded when the photo with sound was taken; if the image is a video, the image audio is the audio in the video. Hereafter, photos with sound and videos will be collectively referred to as videos for explanation.

[0166] In some embodiments, the electronic device 100 may receive user input (e.g., a touch click operation) applied to the "sound" folder 411C. In response to the user input, the electronic device 100 may display a user interface for the "sound" folder 411C. For a specific example, see Figure 4B.

[0167] As shown in Figure 4B, the electronic device 100 can display a user interface 420 for a gallery application. The user interface 420 can display multiple categories under the "Sound" folder 411C. These categories categorize videos according to different sound types, or in other words, according to the audio context in which they are played. For example, these categories include "Concert" category 421 (videos in this category contain concert-type audio, and this category includes, for example, two images), "Fireworks" category 422 (videos in this category contain fireworks-type audio, and this category includes, for example, one image), "Wind Sound" category 423 (videos in this category contain wind-type audio, and this category includes, for example, three images), "Voice 1" category 424 (videos in this category contain one type of voice (Voice 1), and this category includes, for example, two images), and "Voice 2" category 425 (videos in this category contain another type of voice (Voice 2), and this category includes, for example, one image). For instance, the voices of Voice 1 and Voice 2 may be the voices of different users. Understandably, the audio in a video can include multiple types of sounds, so a video can be categorized into multiple categories. For example, the audio in video 1 includes concert-type sounds and vocal-type 1 sounds; therefore, video 1 can be categorized under both "Concert" category 421 and "Voice 1" category 424. Because a video can be categorized into multiple categories, the number of images displayed in the "Sound" folder 411C shown in Figure 4A (i.e., 6) is less than the sum of the number of images displayed in the multiple categories shown in Figure 4B (i.e., 2+1+3+2+1=9).

[0168] In some embodiments, the electronic device 100 may receive user input (e.g., touch click operation) acting on any category displayed on the user interface 420 (taking “wind sound” category 423 as an example). In response to the user input, the electronic device 100 may display the user interface of “wind sound” category 423. For a specific example, see Figure 4C.

[0169] As shown in Figure 4C, the electronic device 100 can display a user interface 430 for a gallery application. The user interface 430 can display a video list under the "Wind Sound" category 423 shown in Figure 4B. This video list can include one or more videos with wind sounds in the audio, such as video 431 (duration "00:30"), video 432 (duration "00:42"), and video 433 (duration "00:08"). In some embodiments, the electronic device 100 can receive user input (e.g., a touch click) applied to any of the videos displayed on the user interface 430 (video 433 is used as an example). In response to this user input, the electronic device 100 can display information about video 433. A specific example can be found in the user interface 340 shown in Figure 4D. Since video 433 is the same as video 333 in the user interface 330 shown in Figure 3C, the user interface used to display information about video 433 is the same as the user interface 340 shown in Figure 3D. The editing control 347A in the user interface 340 can be used to trigger the display of the post-editing interface of video 433 (i.e., video 333). An example of the post-editing interface can be seen in Figure 5A below, which will not be described in detail here.

[0170] Figures 5A-5D are schematic diagrams of a user interface for displaying audio events provided in an embodiment of this application.

[0171] As shown in Figure 5A, the electronic device 100 can display a user interface 510, which can be the post-editing interface of the video 333 shown in Figures 3C and 3D. The video 333 shown in Figures 3C and 3D is the same as the video 433 shown in Figures 4C and 4D; the following description will directly use video 433 as an example. In some embodiments, the user interface 510 can be the user interface of a gallery application or an audio / video editing application. In some embodiments, the electronic device 100 can display the user interface 510 in response to user input (e.g., touch click) acting on the editing control 347A in the user interface 340 shown in Figures 3D / 4D. The user interface 510 can include a return control 511 and a save control 512. The return control 511 can trigger a return to the interface used to display information about the video 433 (i.e., the user interface 340 shown in Figures 3D / 4D), and the save control 512 can be used to save the video 433 after editing in the post-editing interface.

[0172] As shown in Figure 5A, the user interface 510 may include a playback area 513 for video 433, playback controls 514 for video 433, playback time information 515 for video 433, a video playback progress bar 516 for video 433, an audio playback progress bar 517 for video 433, playback nodes 518 for video 433, and a display bar 519 at the bottom. The playback area 513 can be used to display the image content of video 433. The playback controls 514 can be used to control the playback and pause of video 433. The playback time information 515 may include the playback time point of video 433 ("00:00" when video 433 is not playing) and the total duration (i.e., "00:08"), for example, displayed as "00:00 / 00:08". The playback time point of video 433 is the time point at which video 433 is currently playing. This playback time point is greater than or equal to 0 and less than or equal to the total duration of video 433, that is, the value range of this playback time point is "00:00" to "00:08". Different positions of the video playback progress bar 516 correspond to / represent different time points of video 433. Different positions of the audio playback progress bar 517 correspond to / represent different time points of video 433. The display position of playback node 518 on the video playback progress bar 516 and the display position of playback node 518 on the audio playback progress bar 517 can be used to represent / correspond to the time point at which video 433 is currently playing (i.e., the playback time point in playback time information 515). Display bar 519 may include one or more options, such as "Video" option 519A, "Audio" option 519B, "Filter" option 519C (for providing the function of adding filters to video 433) and "Crop" option 519D (for providing the function of cropping the image size of video 433), etc., wherein "Video" option 519A is selected, indicating that user interface 510 is the display interface corresponding to "Video" option 519A. Optionally, user interface 510 may also display video editing options for video 433 (user interface 510 is not shown).

[0173] As shown in Figure 5A, the video playback progress bar 516 may include multiple image frames displayed in the order of video playback, such as displaying image frames in video 433 sequentially from morning to evening and from left to right. The multiple image frames displayed by the video playback progress bar 516 may be some or all of the image frames in video 433, and the display format of each image frame may be the image content of that image frame. The audio playback progress bar 517 may include multiple audio frames displayed in the order of video playback, such as displaying audio frames in video 433 sequentially from morning to evening and from left to right. The multiple audio frames displayed by the audio playback progress bar 517 may be some or all of the audio frames in video 433, and the display format of each audio frame may be the audio waveform of that audio frame (e.g., the frequency spectrum of the audio). Therefore, the video playback progress bar 516 can be understood as a playback progress bar for the images in video 433, and different positions of the video playback progress bar 516 can specifically correspond to / represent image frames at different time points in video 433. The audio playback progress bar 517 can be understood as the audio playback progress bar in video 433. Therefore, different positions of the audio playback progress bar 517 can specifically correspond to / represent audio frames at different time points in video 433.

[0174] As shown in Figure 5A, for any given time point in video 433, the positions corresponding to that time point in the video playback progress bar 516 and the corresponding time point in the audio playback progress bar 517 can be aligned. This time point can be the starting point of video 433; for example, the starting points of video playback progress bar 516 and audio playback progress bar 517 can be aligned, corresponding to / representing the start time point "00:00" of video 433. This time point can also be the ending point of video 433; for example, the ending points of video playback progress bar 516 and audio playback progress bar 517 can be aligned, corresponding to / representing the end time point "00:08" of video 433. This time point can also be any time point between the start and end points of video 433; for example, the end position of the first image frame of video playback progress bar 516 and the end position of the first audio frame of audio playback progress bar 517 can be aligned, corresponding to / representing the time point "00:01" of video 433. The display positions of playback node 518 on the video playback progress bar 516 and the audio playback progress bar 517 can be aligned, corresponding to / representing the current playback time of video 433 (i.e., the playback time point in playback time information 515). Specifically, when video 433 is not playing, the playback time point in playback time information 515 is "00:00", and playback node 518 is located at the starting point of both the video playback progress bar 516 and the audio playback progress bar 517. When video 433 is playing in playback area 513, the playback time point in playback time information 515 increases from 0 (maximum "00:08"), and playback node 518 moves synchronously from the starting points of both the video playback progress bar 516 and the audio playback progress bar 517 (moving at most to the ending points of both), for example, moving synchronously to the right on both the video playback progress bar 516 and the audio playback progress bar 517.

[0175] For example, the electronic device 100 can receive user input applied to the playback node 518, which is used to move the playback node 518 to position 1. Position 1 is the position corresponding to time point 1 on the video playback progress bar 516 and also the position corresponding to time point 1 on the audio playback progress bar 517. For example, the user input is a touch drag operation. In response to the user input, the electronic device 100 can move the playback node 518 to position 1 and display the image content corresponding to time point 1 in the playback area 513. At this time, the playback time point in the playback time information 515 also becomes time point 1. Optionally, in response to the input, the electronic device 100 can also start playing video 433 from time point 1, that is, display the image of video 433 at time point 1 and later in the playback area 513, and play the audio of video 433 at time point 1 and later through a speaker or other module. Specific examples can be seen in Figures 7A-7B below, which will not be described in detail here.

[0176] As shown in Figure 5A, the audio playback progress bar 517 can display identifiers for one or more audio events of video 433. Any one of these audio events indicates a specific segment of audio on the audio playback progress bar 517, and different audio events may indicate different audio segments. The audio indicated by the audio events of video 433 may or may not be within the main audio track of video 433. The display position of the audio event identifier on the audio playback progress bar 517 can represent / correspond to the segment of audio indicated by the audio event, or represent / correspond to any point in time within that segment (e.g., the start or end time). The following explanation uses the representation / correspondence to the start time as an example. For example, as shown in Figure 5A, the audio playback progress bar 517 displays the identifier 517A (including the number 1) for audio event 1 and the identifier 517B (including the number 2) for audio event 2. The identifier 517A for audio event 1 is displayed at the position corresponding to the time point "00:00" on the audio playback progress bar 517, indicating that the starting time point of the audio indicated by audio event 1 is "00:00". The identifier 517B for audio event 2 is displayed at the position corresponding to "00:01" on the audio playback progress bar 517, indicating that the starting time point of the audio indicated by audio event 2 is "00:01". It is understood that the user interface 510 shown in Figure 5A only shows a portion of the audio playback progress bar 517 and the video playback progress bar 516; the unshown portion of the audio playback progress bar 517 may also display the identifiers of the audio events of video 433.

[0177] In some embodiments, the display methods of the identifiers for different types of audio events can be different. For example, as shown in Figure 5A, audio event 1 is automatically identified by the electronic device 100, and the audio indicated by audio event 1 is a specific type of audio identified by the electronic device 100 from the audio of video 433. Audio event 2, on the other hand, is user-defined, and the audio indicated by audio event 2 is determined by the electronic device 100 based on user input. The colors of the identifiers for audio event 1 and audio event 2 are different. However, this is not a limitation. In other examples, the shape, size, etc., of the identifiers may also be different, as may the color, font, and content of the characters displayed in the identifiers. This application embodiment does not limit the display method of the audio event identifiers.

[0178] In some embodiments, the electronic device 100 may receive user input (e.g., a touch click operation) acting on the identifier of any audio event on the audio playback progress bar 517 shown in the user interface 510, and display information about the audio event in response to the user input. For example, the electronic device 100 may receive user input acting on the identifier 517A of audio event 1 in the user interface 510 shown in FIG. 5A, and display information about audio event 1 in response to the user input; a specific example can be seen in the display bar 521 in the user interface 520 shown in FIG. 5B.

[0179] As shown in Figure 5B, the user interface 520 is similar to the user interface 510 shown in Figure 5A, and also includes a display bar 521. The display bar 521 displays information about audio event 1, including, for example, a name 521A (“Audio Event 1”), type information 521B, time information 521C, playback controls 521D, and track marker 521E. The type information 521B characterizes the type of audio event 1 and / or the type of audio indicated by audio event 1. For example, if the type information 521B is “clapping,” it indicates that audio event 1 is an audio event automatically recognized by the electronic device 100, and the audio indicated by audio event 1 is “clapping” type audio recognized by the electronic device 100. The time information 521C displays any point in time of the audio indicated by audio event 1. Optionally, this point in time can be the time corresponding to the display position of the identifier of audio event 1 on the audio playback progress bar 517, for example, the starting time point of the audio indicated by audio event 1, “00:00.” The playback controls 521D play the audio indicated by audio event 1. The audio track flag 521E is used to indicate whether the audio indicated by audio event 1 is within the main audio track of video 433. The audio track flag 521E shown in the user interface 520 indicates that the audio indicated by audio event 1 is within the main audio track of video 433. Therefore, when playing video 433, the audio indicated by audio event 1 will be played. For example, during the playback of video 433, if the playback reaches the time period indicated by audio event 1, the audio indicated by audio event 1 will be played within that time period.

[0180] In some embodiments, the electronic device 100 may receive user input that acts on the identifier 517B of audio event 2 in the user interface 520 shown in FIG. 5B, and in response to the user input, display information about audio event 2. For a specific example, see the display bar 531 in the user interface 530 shown in FIG. 5C.

[0181] As shown in Figure 5C, the user interface 530 is similar to the user interface 520 shown in Figure 5B, and also includes a display bar 531. The display bar 531 displays information about audio event 2, including, for example, a name 531A (“Audio Event 2”), type information 531B, time information 531C, playback controls 531D, and track marker 531E. The type information 531B characterizes the type of audio event 2. For example, if type information 531B is “custom,” it indicates that audio event 2 is user-defined, and therefore the electronic device 100 does not recognize the type of audio indicated by audio event 2. The time information 531C displays any point in time of the audio indicated by audio event 2. Optionally, this point in time can be the time corresponding to the display position of the identifier 517B of audio event 2 on the audio playback progress bar 517, for example, the starting time “00:01” of the audio indicated by audio event 2. The playback controls 531D play the audio indicated by audio event 2. The audio track flag 531E is used to indicate whether the audio indicated by audio event 2 is in the main audio track of video 433. The audio track flag 531E shown in the user interface 530 indicates that the audio indicated by audio event 2 is not in the main audio track of video 433, so the audio indicated by audio event 2 will not be played when video 433 is played.

[0182] In some embodiments, the electronic device 100 may receive user input (e.g., a touch click operation) applied to the “audio” option 519B in the user interface 530 shown in FIG5C. In response to the user input, the electronic device 100 may display the user interface corresponding to the “audio” option 519B. For a specific example, see the user interface 540 shown in FIG5D.

[0183] As shown in Figure 5D, the user interface 540 is similar to the user interface 530 shown in Figure 5C, but the "Video" option 519A in the display bar 519 of the user interface 540 is not selected, while the "Audio" option 519B is selected, indicating that the user interface 540 is the display interface corresponding to the "Audio" option 519B. The user interface 540 may also include an audio editing bar 541, which may include one or more audio editing function options, such as "trimming audio," "adding audio," "adjusting pitch," "adjusting speed," etc. Based on the audio event identifiers on the audio playback progress bar 517 shown in the user interface 540, the information of audio event 1 shown in the display bar 521, and the information of audio event 2 shown in the display bar 531, the user can quickly obtain the audio information in the video 433, and thus perform audio editing operations on the audio in the video 433 based on the audio editing bar 541, improving the efficiency of audio editing.

[0184] Not limited to the embodiments shown in Figures 5A-5D, in other embodiments, instead of displaying information about an audio event upon receiving user input identifying an audio event, information about all audio events of the current video may be displayed upon receiving user input identifying any audio event. In other embodiments, information about all audio events of the current video may be displayed upon receiving other user input. For example, electronic device 100 may receive user input acting on the "Audio" option 519B in the user interface 510 shown in Figure 5A, and in response to the user input, display the user interface corresponding to the "Audio" option 519B, which is used to display information about all audio events of the current video. In other embodiments, information about all audio events of the current video may be displayed directly without user input. For example, when entering the post-editing mode of the video, the identifier of the audio event and information about all audio events are displayed, that is, information about all audio events of video 433 is displayed in the user interface 510 shown in Figure 5A. In this way, users can obtain information about all audio events of the current video with a single user input or without any user input, further improving the efficiency of users obtaining audio information. This application does not limit the triggering method for displaying audio event information.

[0185] Not limited to the embodiments shown in Figures 5A-5D, in other embodiments, in user interfaces such as the user interface 520 shown in Figure 5B and the user interface 530 shown in Figure 5C used to display information about audio events, the “Video” option 519A shown in the display bar 519 may not be selected, while the “Audio” option 519B may be selected. It can be understood that the user interface corresponding to the “Audio” option 519B is used to display information about audio events, and optionally displays an audio editing bar (e.g., displays an audio editing bar in response to user input).

[0186] Not limited to the embodiments shown in Figures 5A-5D, in other embodiments, when the type of the audio event is user-defined, the electronic device 100 can also identify the type of audio indicated by the audio event and display the type of audio indicated by the audio event when displaying information about the audio event. For example, the display bar 531 in the user interface 530 shown in Figure 5C can also include the type information of the audio indicated by audio event 2 (such as human voice 1).

[0187] Not limited to the embodiments shown in Figures 5A-5D, in other embodiments, the electronic device 100 may display more or less information when displaying audio event information. In some examples, the electronic device 100 may use two display pieces of information to characterize the type of the audio event and the type of audio indicated by the audio event. For example, the display bar 521 in the user interface 520 shown in Figure 5B includes not only type information 521B (used to characterize the type of audio indicated by audio event 1 as "clapping"), but also audio event type information, which can be "automatically recognized," to characterize that audio event 1 is an audio event automatically recognized by the electronic device 100. In some examples, the electronic device 100 may also display the time period of the audio indicated by the audio event. In some examples, the electronic device 100 may also display the end time point of the audio indicated by the audio event, but not the start time point. The embodiments of this application do not limit the specific content of the information displayed for the audio event.

[0188] Not limited to the above embodiments, in other embodiments, instead of displaying the audio playback progress bar, the audio event identifier, and the audio event information on the audio playback progress bar in the video's post-editing interface, these contents may be displayed when displaying video information (e.g., displaying the video playback interface / preview interface). For example, in the user interface 340 for displaying information of video 433 shown in FIG3D / FIG4D, the video playback progress bar 516, the audio playback progress bar 517, and the playback node 518 shown in FIG5A-FIG5D are displayed. Among them, the identifier of one or more audio events of video 433 is displayed on the audio playback progress bar 517, and the information of these one or more audio events is displayed in the user interface 340.

[0189] Figures 6A and 6B are schematic diagrams of a user interface for playing audio indicating an audio event, provided in an embodiment of this application.

[0190] As shown in Figure 6A, the electronic device 100 can display the user interface 530 shown in Figure 5C. The electronic device 100 can receive user input (e.g., touch click operation) applied to the playback control 521D in the display bar 521 shown in the user interface 530. In response to the user input, the electronic device 100 can play the audio 1 indicated by the audio event 1 shown in the display bar 521 and can display the corresponding playback interface. For a specific example, see the user interface 610 shown in Figure 6B.

[0191] As shown in Figure 6B, the user interface 610 is similar to the user interface 530 shown in Figure 6A. The display bar 521 shown in the user interface 610 also includes a playback progress bar 611, a playback node 612, a playback time point 613, and an end time point 614 for audio 1 indicated by audio event 1. Different positions on the playback progress bar 611 can represent / correspond to different time points of audio 1. The starting point of the playback progress bar 611 represents / corresponds to the starting time point of audio 1 on the audio playback progress bar 517 in the user interface 610. The ending point of the playback progress bar 611 represents / corresponds to the ending time point of audio 1 on the audio playback progress bar 517 in the user interface 610, i.e., the end time point 614. The display position of the playback node 612 on the playback progress bar 611 can be used to represent / correspond to the time point when audio 1 is currently playing, i.e., the playback time point 613. Playback time point 613 is greater than or equal to the start time of audio 1 on the audio playback progress bar 517 in the user interface 610, and less than or equal to the end time of audio 1 on the audio playback progress bar 517 in the user interface 610. Therefore, the value range of playback time point 613 is from "00:00" to "00:01". When audio 1 has not started playing, playback node 612 can be located at the starting point of playback progress bar 611, and playback time point 613 is the start time of audio 1 on the audio playback progress bar 517 in the user interface 610, that is, the time information 521C ("00:00") in the display bar 521 shown in the user interface 610. When audio 1 begins playback, playback node 612 moves from the starting point of playback progress bar 611 (up to the ending point of playback progress bar 611, for example, moving from left to right). Playback time point 613 increases from the value "00:00" of time information 521C (up to the value "00:01" of end time point 614). For example, in the display bar 521 shown in user interface 610, playback node 612 is located at the midpoint of playback progress bar 611, and playback time point 613 is half the duration of audio 1, i.e., "00:01.5". In the playback interface of audio 1 indicated by audio event 1, playback control 521D is used to control the pause playback of audio 1.

[0192] Not limited to the embodiment shown in Figure 6B, in other embodiments, the starting point of the playback progress bar 611 can also represent / correspond to "00:00", and the ending point of the playback progress bar 611 can also represent / correspond to the total duration of audio 1 (i.e., "00:01"). Therefore, the playback time point 613 is greater than or equal to "00:00" and less than or equal to the total duration of audio 1. This application embodiment does not limit the display method of the audio playback interface indicated by the audio event.

[0193] Not limited to the above embodiments, in other embodiments, when the electronic device 100 displays the information of audio event 1 in the display bar 521, it can also display by default the playback progress bar 611, playback node 612, playback time point 613 and end time point 614 of the audio indicated by audio event 1, without requiring user input to trigger the display.

[0194] Figures 7A-7C are schematic diagrams of a user interface for modifying the time information of an audio event according to an embodiment of this application.

[0195] It's understandable that the timing information of an audio event refers to the time segment or moment within the audio playback progress bar that the audio event indicates. Therefore, modifying the timing information of an audio event actually modifies the audio that the audio event indicates. This provides users with the ability to manually correct the range of the audio indicated by the audio event.

[0196] As shown in Figure 7A, the electronic device 100 can display a user interface 710, which is similar to the user interface 610 shown in Figure 6B. The display bar 521 shown in the user interface 710 is used to display information about audio event 1, wherein the playback node 612 is located at the starting point of the playback progress bar 611, and the playback control 521D can be used to trigger the playback of audio 1 indicated by audio event 1. In some embodiments, the user interface 710 can be the user interface displayed after the playback of audio 1 indicated by audio event 1 has finished. An example of the user interface during the playback of audio 1 can be found in the user interface 610 shown in Figure 6B. In some embodiments, the electronic device 100 can receive user input acting on the playback node 518 in the user interface 710, for example, the user input is a touch drag operation, assuming that the user input is used to move the playback node 518 to the position corresponding to the time point "00:02" in the video playback progress bar 516 / audio playback progress bar 517. In response to this user input, the electronic device 100 can display the user interface 720 shown in Figure 7B.

[0197] As shown in Figure 7B, the user interface 720 is similar to the user interface 710 shown in Figure 7A. Compared to the video playback progress bar 516 / audio playback progress bar 517 in user interface 710, which is over 2 seconds long, the video playback progress bar 516 / audio playback progress bar 517 in user interface 720 is over 4 seconds long. The playback node 518 in user interface 720 is located at the position corresponding to the time point "00:02" in the video playback progress bar 516 / audio playback progress bar 517. The playback time point in the playback time information 515 shown in user interface 720 is "00:02," and the playback area 513 currently displays the image content of the video 433 at the playback time point "00:02." In some embodiments, the electronic device 100 can receive user input acting on the identifier 517A of audio event 1, which is used to move the identifier 517A of audio event 1 to position 2 on the audio playback progress bar 517, where position 2 is the position corresponding to time point 2 on the audio playback progress bar 517. For example, the user input is a touch drag operation. In response to the user input, the electronic device 100 can move the identifier 517A of audio event 1 to position 2 and modify the time information of audio event 1 to time point 2. Therefore, the audio indicated by audio event 1 also becomes the audio corresponding to time point 2 on the audio playback progress bar 517 (which can be called audio 3). An example of the interface at this time can be seen in the user interface 730 shown in Figure 7C (taking time point 2 as "00:03" as an example).

[0198] As shown in Figure 7C, the user interface 730 is similar to the user interface 720 shown in Figure 7B, but the information displayed in the display bar 521 for audio event 1 is different, and the display position of the identifier 517A of audio event 1 is different. Specifically, the playback node 612 displayed in the display bar 521 is currently located at the starting point of the playback progress bar 611. Therefore, the playback time point 613 represents the starting point of the audio 3 indicated by audio event 1, and the value of playback time point 613 is "00:03". The display position of the identifier 517A of audio event 1 on the audio playback progress bar 517 is the display position corresponding to the time point "00:03" (i.e., the aforementioned time point 2). The time information 521C of audio event 1 displayed in the display bar 521 is "00:03". Therefore, it can be represented that the starting time point of the audio 3 indicated by audio event 1 is the time point "00:03" on the audio playback progress bar 517. Assuming that the duration of audio 3 indicated by audio event 1 is the same as the duration of the previously indicated audio 1, which is 1 second, the end time of audio 3 is the time point "00:04" on the audio playback progress bar 517, and the value of the end time point 614 displayed in the display bar 521 is "00:04".

[0199] Not limited to the embodiments shown in Figures 7A-7C, in other embodiments, when the electronic device 100 responds to the user's input to modify the time point (e.g., the start time point) of the audio indicated by audio event 1, it can automatically identify the time period of the audio indicated by the modified audio event 1. For example, based on the audio type information (e.g., "clapping") in the information of audio event 1, it can automatically identify the time period of the audio belonging to the "clapping" type. In other embodiments, the electronic device 100 may also prompt the user to select the time period of the audio indicated by the modified audio event 1, that is, prompt the user to select the end time point of the audio indicated by the modified audio event 1. The specific determination method is not limited in the embodiments of this application.

[0200] Figures 8A-8F are schematic diagrams of a user interface for modifying audio event information provided in an embodiment of this application.

[0201] Figures 8A and 8B are schematic diagrams of a user interface for modifying the time information of an audio event according to an embodiment of this application. Modifying the time information of an audio event actually modifies the audio indicated by the audio event. This provides the user with the ability to manually correct the range of the audio indicated by the audio event.

[0202] As shown in Figure 8A, the electronic device 100 can display a user interface 810, which can be the same as the user interface 710 shown in Figure 7A. In some embodiments, the electronic device 100 can receive user input (e.g., a touch click operation) that acts on the time information 521C of audio event 1 in the display bar 521 shown in the user interface 810. In response to the user input, the electronic device 100 can set the time information 521C to an edit state. For a specific example, see the time information 521C displayed in the display bar 521 of the user interface 820 shown in Figure 8B.

[0203] As shown in Figure 8B, the time information 521C displayed in the display bar 521 of the user interface 820 may include an edit box. This edit box can be used to display the value of the time information 521C, such as "00:00". This edit box can be used to receive a time value input by the user, and the electronic device 100 can set the time value in the edit box as the value of the time information 521C. However, this is not a limitation. In other embodiments, the user may not manually input the time value in the edit box of the time information 521C. The electronic device 100 can display one or more modifiable time values, from which the user can select one and input it into the edit box of the time information 521C. In other embodiments, the user can also manually select a time point on the audio playback progress bar 517, and the electronic device 100 can automatically input the selected time point into the edit box of the time information 521C. This application embodiment does not limit the specific method of modifying the value of the time information 521C.

[0204] Figure 8C is a schematic diagram of a user interface for modifying the type information of an audio event according to an embodiment of this application. This provides users with the ability to manually correct the type of audio indicated by the audio event.

[0205] In some embodiments, the electronic device 100 may receive user input (e.g., a touch click operation) that acts on the type information 521B of the audio event 1 in the display bar 521 shown in FIG8A. In response to the user input, the electronic device 100 may set the type information 521B to an edit state. For a specific example, see the type information 521B displayed in the display bar 521 of the user interface 830 shown in FIG8C.

[0206] As shown in Figure 8C, the type information 521B displayed in the display bar 521 of the user interface 830 may include an edit box. This edit box can be used to display the content of the type information 521B, such as the current type "clapping". This edit box can be used to receive the type content of the audio indicated by the user's input audio event 1. The electronic device 100 can set the type content in the edit box as the content of the type information 521B. Not limited to this, in some other embodiments, the user may not manually input the type content in the edit box of the type information 521B. The electronic device 100 can display one or more modifiable type contents, and the user can select one from these one or more modifiable type contents to input the type content into the edit box of the type information 521B. This application embodiment does not limit the specific method of modifying the content of the type information 521B.

[0207] Figure 8D is a schematic diagram of a user interface for modifying the name of an audio event according to an embodiment of this application. This provides users with the function of customizing the name of audio events.

[0208] In some embodiments, the electronic device 100 may receive user input (e.g., a touch click operation) on the name 521A of the audio event 1 in the display bar 521 shown in FIG8A. In response to the user input, the electronic device 100 may set the name 521A to an edit state. For a specific example, see the name 521A displayed in the display bar 521 of the user interface 840 shown in FIG8D.

[0209] As shown in Figure 8D, the name 521A displayed in the display bar 521 of the user interface 840 may include an edit box. This edit box can be used to display the content of name 521A, such as "Audio Event 1". This edit box can be used to receive name content input by the user, and the electronic device 100 can set the name content in the edit box as the content of name 521A. However, in some embodiments, the user may not manually input the name content in the edit box of name 521A. The electronic device 100 can display one or more modifiable name contents, and the user can select one from these modifiable name contents to input into the edit box of name 521A. This application embodiment does not limit the specific method of modifying the content of name 521A.

[0210] Figure 8E is a schematic diagram of a user interface for modifying the end time point of audio indicating an audio event, according to an embodiment of this application. This provides the user with the ability to manually correct the range of audio indicating an audio event.

[0211] In some embodiments, the electronic device 100 may receive user input (e.g., a touch click operation) acting on the audio event 1 indicated by the audio event 1 in the display bar 521 shown in FIG8A. In response to the user input, the electronic device 100 may set the end time point 614 to an edit state. For a specific example, see the end time point 614 displayed in the display bar 521 of the user interface 850 shown in FIG8E.

[0212] As shown in Figure 8E, the end time point 614 displayed in the display bar 521 of the user interface 850 may include an edit box. This edit box can be used to display the value of the end time point 614, such as "00:01". This edit box can be used to receive a time value input by the user, and the electronic device 100 can set the time value in the edit box as the value of the end time point 614. Not limited to this, in some embodiments, the user may not manually input the time value in the edit box of the end time point 614. The electronic device 100 can display one or more modifiable time values, and the user can select one of these modifiable time values ​​to input into the edit box of the end time point 614. In other embodiments, the user can also manually select a time point on the audio playback progress bar 517, and the electronic device 100 can automatically input the user-selected time point into the edit box of the end time point 614. This application embodiment does not limit the specific method of modifying the value of the end time point 614.

[0213] The above embodiments are illustrated by setting the start and end times of audio 1 indicated by audio event 1. In other embodiments, the time period of the audio indicated by the audio event can be set directly. For example, electronic device 100 can receive user input applied to the display bar 521 shown in FIG8A. In response to the user input, electronic device 100 can prompt the user to select the time period of the audio on the audio playback progress bar 517 and set the audio of the time period selected by the user as the audio indicated by audio event 1.

[0214] Figure 8F is a schematic diagram of a user interface for setting whether the audio of an audio event indicator is within the main audio track of a video, according to an embodiment of this application. This provides users with the function of preserving or muting the audio of the audio event indicator in the video.

[0215] In some embodiments, the electronic device 100 may receive user input (e.g., a touch click) applied to the audio track indicator 521E in the display bar 521 shown in FIG8A. In response to the user input, the electronic device 100 may modify the audio indicated by audio event 1 from being within the main audio track of video 433 to being outside the main audio track of video 433. A specific example can be seen in the audio track indicator 521E displayed in the display bar 521 of the user interface 860 shown in FIG8F. As shown in FIG8F, the audio track indicator 521E displayed in the display bar 521 of the user interface 860 indicates that the audio indicated by audio event 1 is not within the main audio track of video 433, therefore the audio indicated by audio event 1 will not be played when video 433 is played.

[0216] Figures 9A-9C are schematic diagrams of a user interface for deleting audio events provided in an embodiment of this application.

[0217] As shown in Figure 9A, the electronic device 100 can display a user interface 910, which can be the same as the user interface 710 shown in Figure 7A. The display bar 521 in the user interface 910 is used to display information about audio event 1. In some embodiments, the electronic device 100 can receive user input (e.g., a long press operation) applied to the display bar 521 in the user interface 910. In response to the user input, the electronic device 100 prompts the user whether to delete the audio event 1 displayed in the display bar 521. A specific example can be found in the user interface 920 shown in Figure 9B.

[0218] As shown in Figure 9B, the electronic device 100 can display a user interface 920. The user interface 920 may include a window 921, which may include a prompt message 922 "Delete audio event 1?", a delete control 923, and a cancel control 924. The delete control 923 can be used to delete audio event 1, and the cancel control 924 can be used to cancel the deletion of audio event 1. In some embodiments, the electronic device 100 can receive user input (e.g., a touch click) applied to the delete control 923 in the user interface 920. In response to this user input, the electronic device 100 can delete audio event 1, at which point the electronic device 100 can display the user interface 930 shown in Figure 9C. As shown in Figure 9C, the user interface 930 is similar to the user interface 910 shown in Figure 9A. Since audio event 1 is deleted, the user interface 930 does not display the identifier 517A of audio event 1, nor does it display the display bar 521 (used to display information about audio event 1).

[0219] Figures 10A-10C are schematic diagrams of an audio editing interface corresponding to the audio of an audio event indication provided in an embodiment of this application.

[0220] As shown in Figure 10A, the electronic device 100 can display a user interface 1010, which is the same as the user interface 710 shown in Figure 7A. The display bar 521 in the user interface 1010 is used to display information about audio event 1. In some embodiments, the electronic device 100 can receive user input (e.g., a double-touch operation) applied to the display bar 521 in the user interface 1010. In response to the user input, the electronic device 100 can enter the editing mode of audio 1 indicated by audio event 1. A specific example can be found in the user interface 1020 shown in Figure 10B.

[0221] As shown in Figure 10B, the user interface 1020 is similar to the user interface 1010 shown in Figure 10A. The display bar 521 in the user interface 1020 is used to display information about audio event 1. In the display bar 519 included in the user interface 1020, the "Video" option 519A is not selected, while the "Audio" option 519B is selected, indicating that the user interface 1020 is the display interface corresponding to the "Audio" option 519B. The user interface 1020 is used to provide audio editing functions for the audio 1 indicated by audio event 1. The user interface 1020 also includes an editing bar 1021 for the audio 1 indicated by audio event 1. This editing bar 1021 may include the name of the audio event "Audio Event 1", a playback progress bar 1022 for the audio 1 indicated by audio event 1, playback controls 1023 for the audio 1, a playback node 1024 for the audio 1, playback time information 1025 for the audio 1, and an audio editing bar 1026 for the audio 1. The name shown in the editing bar 1021 is the same as the name 521A shown in the display bar 521 in the user interface 1020. Both the playback progress bar 1022 and the playback progress bar 611 shown in the display bar 521 of the user interface 1020 are playback progress bars for audio 1, but they are displayed differently. The playback progress bar 1022 can include multiple audio frames of audio 1 displayed in the order of audio playback, such as displaying the audio frames of audio 1 sequentially from early to late and from left to right. The multiple audio frames displayed in the playback progress bar 1022 can be some or all of the audio frames of audio 1, and the display form of each audio frame can be the audio waveform of that audio frame (e.g., the frequency spectrum of the audio). The playback control 1023 is used to control the playback of audio 1 indicated by audio event 1 on the playback progress bar 1022. The playback time information 1025 can include the playback time point of audio 1 on the playback progress bar 1022 (e.g., "00:00" when not playing), and the end time point of audio 1 (the same as the end time point 614 "00:01" shown in the display bar 521 of the user interface 1020), for example, displayed as "00:00 / 00:01". The display position of playback node 1024 on the playback progress bar 1022 can be used to represent / correspond to the time point when audio 1 is playing, that is, the playback time point in the playback time information 1025.

[0222] As shown in Figure 10B, the audio editing bar 1026 of audio 1 indicated by audio event 1 may include one or more audio editing function options for audio 1, such as a "compress" function option (for compressing audio 1), a "export" function option (for exporting audio 1), a "replace" function option (for replacing the audio indicated by audio event 1 from audio 1 with other audio), and a "more" function option (for displaying more audio editing function options for audio 1). Exemplarily, the electronic device 100 may receive user input (e.g., a touch click operation) acting on any of the function options in the audio editing bar 1026, and in response to the user input, perform the audio editing operation corresponding to that function option on audio 1.

[0223] In some embodiments, the electronic device 100 can receive user input applied to the playback progress bar 1022 in the edit bar 1021 shown in FIG. 10B. For example, the user input is a two-finger swipe operation as shown in FIG. 10C. This two-finger swipe operation can be a two-finger swipe from the outside in or from the inside out. In response to the user input, the electronic device 100 can determine the audio segment of the audio 1 selected by the user input from the playback progress bar 1022 and select the audio segment in the playback progress bar 1022. A specific example can be seen in the playback progress bar 1022 in the user interface 1030 shown in FIG. 10C. As shown in FIG. 10C, the user interface 1030 is similar to the user interface 1020, both including an edit bar 1021 for the audio 1 indicated by audio event 1. In the edit bar 1021 shown in the user interface 1030, a selection box 1031 is displayed on the playback progress bar 1022, and the audio segment within the selection box 1031 is the audio segment of the audio 1 selected by the user. The editing bar 1021 shown in the user interface 1030 also includes time information 1032 for the audio segment within the selected box 1031. The time information 1032 includes the start and end times of the audio segment, for example, "00:00.2-00:00.6". The editing bar 1021 shown in the user interface 1030 also includes an audio editing bar 1033 for the audio segment within the selected box 1031. The audio editing bar 1033 may include one or more audio editing function options for the audio segment within the selected box 1031, such as the "Replace" function option (used to replace the audio segment within the selected box 1031 with other audio segments), the "Pitch" function option (used to adjust the pitch of the audio segment within the selected box 1031), the "Add Audio" function option (used to add other audio to the time period within the selected box 1031, i.e., to achieve the mixing function of the audio within the selected box 1031 and other audio), and the "More" function option (used to display more audio editing function options for the audio segment within the selected box 1031). For example, the electronic device 100 can receive user input (e.g., touch click operation) applied to any function option in the audio editing bar 1033, and in response to the user input, perform audio editing operation corresponding to the function option on the audio segment in the selected box 1031.

[0224] Figures 11A-11C are schematic diagrams of a user interface for creating a new audio event in the video post-editing interface provided in this application.

[0225] As shown in Figure 11A, the electronic device 100 can display a user interface 1110, which is the same as the user interface 720 shown in Figure 7B. The electronic device 100 can receive user input applied to the audio playback progress bar 517 of the video 433 in the user interface 1110. For example, the user input may be a touch swipe operation as shown in Figure 11A, which can be a swipe from left to right or from right to left. Alternatively, the user input may be a two-finger swipe operation, which can be a two-finger swipe from the outside in or from the inside out. Based on the user input, the electronic device 100 can determine the audio segment selected by the user in the video 433 from the audio playback progress bar 517 and select the audio segment within the audio playback progress bar 517. Specifically, see the selection box 1111 displayed on the audio playback progress bar 517 in the user interface 1110; the audio segment within the selection box 1111 is the audio segment in the video 433 selected by the user. When the above user input is completed, for example, when the user leaves the screen of the electronic device 100 after performing a touch swipe operation or a two-finger swipe operation, the electronic device 100 can prompt the user to create a new audio event for the audio segment in the selected box 1111. For a specific example, see the display bar 1121 in the user interface 1120 shown in Figure 11B.

[0226] As shown in Figure 11B, the user interface 1120 is similar to the user interface 1110 shown in Figure 11A. The audio playback progress bar 517 of the video 433 in user interface 1120 displays a checkbox 1111, and user interface 1120 also includes a display bar 1121. The display bar 1121 can be used to create a new audio event 3, where the audio event 3 indicates the audio segment within the checkbox 1111. The display bar 1121 may include an edit box 1121A for the type information of audio event 3, edit boxes 1121B and 1121C for the start and end times of the audio segment indicated by audio event 3 on the audio playback progress bar 517, a setting option 1121D for the track flag of audio event 3, and a confirmation control 1121E. Edit box 1121A is used to edit the type information of audio event 3, for example, the default is "custom". Edit box 1121B is used to edit the start time of the audio segment indicated by audio event 3 on the audio playback progress bar 517. This start time is the time corresponding to the starting point of selection box 1111 on the audio playback progress bar 517, for example, "00:03". Edit box 1121C is used to edit the end time of the audio segment indicated by audio event 3 on the audio playback progress bar 517. This end time is the time corresponding to the ending point of selection box 1111 on the audio playback progress bar 517, for example, "00:04". Therefore, edit boxes 1121B and 1121C can be used by the user to set which segment of the audio playback progress bar 517 the audio indicated by audio event 3 belongs to. Setting option 1121D can be used to determine whether the audio segment indicated by audio event 3 is within the main audio track of video 433. For example, the default setting is that the audio segment indicated by audio event 3 is within the main audio track of video 433. In this case, setting option 1121D can display the prompt message "Current audio has been preserved in the video" and display the track marker indicating that it is within the main audio track. The confirmation control 1121E is used to confirm the audio event 3 shown in the newly created display bar 1121.

[0227] In some examples, the user can not only set which segment of the audio on the audio playback progress bar 517 the audio indicated by audio event 3 is, through edit boxes 1121B and 1121C, but also by adjusting the position of the selection box 1111 on the audio playback progress bar 517. The electronic device 100 can receive user input to move the selection box 1111 to position 3 on the audio playback progress bar 517, for example, a touch drag operation. In response to this user input, the electronic device 100 can move the selection box 1111 to position 3 and modify the value in edit box 1121B to the time point corresponding to the starting point of the selection box 1111 at position 3 on the audio playback progress bar 517, and modify the value in edit box 1121C to the time point corresponding to the ending point of the selection box 1111 at position 3, that is, modify the audio indicated by audio event 3 to the audio segment within the selection box 1111 at position 3.

[0228] In some embodiments, the electronic device 100 may receive user input (e.g., a touch click operation) acting on the determination control 1121E in the user interface 1120. In response to the user input, the electronic device 100 may create an audio event 3 as shown in the display bar 1121 in the user interface 1120, at which time the user interface 1130 shown in FIG11C may be displayed.

[0229] As shown in Figure 11C, the user interface 1130 is similar to the user interface 1110 shown in Figure 11A. The user interface 1130 does not include a checkbox 1111, but includes a display bar 1131 and an identifier 1132 for audio event 3 displayed on the audio playback progress bar 517. The display bar 1131 displays information about audio event 3, including, for example, a name 1131A (“Audio Event 3”), type information 1131B, time information 1131C, playback controls 1131D, and track marker 1131E. The type information 1131B characterizes the type of audio event 3. For example, if the type information 1131B is the content of the edit box 1121A shown in Figure 11B, “Custom,” it indicates that audio event 3 is user-defined. The time information 1131C is used to display the time point of the audio indicated by audio event 3. This time point can be the time point corresponding to the display position of the identifier 1132 of audio event 3 on the audio playback progress bar 517, such as the content "00:01" in the edit box 1121B shown in Figure 11B, which is the start time point of the audio indicated by audio event 3. The playback control 1131D is used to play the audio indicated by audio event 3. The audio track flag 1131E is used to indicate whether the audio indicated by audio event 3 is within the main audio track of video 433. The audio track flag 1131E shown in the user interface 1130 corresponds to the setting option 1121D shown in Figure 11B, indicating that the audio indicated by audio event 3 is within the main audio track of video 433. Therefore, when playing video 433, the audio indicated by audio event 3 will be played. For example, during the playback of video 433, if the playback reaches the time period indicated by audio event 3, the audio indicated by audio event 3 will be played.

[0230] In addition to this, in other examples, audio events can also be created when video information is displayed (such as when the video playback interface / preview interface is displayed).

[0231] Not limited to the embodiments shown in Figures 11A-11C, in other embodiments, when the electronic device 100 displays audio and video, such as when displaying a post-editing interface or preview interface for audio and video, it can receive input from the user for creating a new audio event. In response to this input, a settings bar for setting information for the newly created audio event is displayed. This settings bar is similar to the display bar 1121 in the user interface 1120 shown in Figure 11B, but this settings bar can provide the user with the function of customizing audio, that is, the user can input the audio indicated by the currently created audio event through the settings bar. For example, the electronic device 100 can receive the audio input by the user based on the settings bar, such as the user inputting through a microphone or the user importing existing audio, and set the audio input by the user as the audio indicated by the currently created audio event. Any other information of the audio event can be set by the electronic device 100 itself (e.g., default settings or automatic recognition), or it can be input by the user. For example, the electronic device 100 can determine the time information of the newly created audio event (i.e., the display position of the audio indicated by the audio event on the audio playback progress bar) according to the default settings, such as the start time point of the audio playback progress bar or the current playback time point. Alternatively, the electronic device 100 can also determine the time information of the newly created audio event according to user input.

[0232] In addition to creating audio events in the video post-editing interface as shown in Figures 11A-11C, in some other embodiments, audio events can also be created during video recording. The video recording scenario is illustrated below with Figures 12A-12B, and the creation of audio events during video recording is illustrated below with Figures 13A-13J.

[0233] Figures 12A and 12B are schematic diagrams of a video shooting scenario provided in this application.

[0234] As shown in Figure 12A, in a video shooting scenario, the photographer can use electronic device 100 to photograph the subject, thereby recording video. When recording video, electronic device 100 can detect and collect sound from various directions centered on it. Taking four directions as an example, these four directions can include: direction 1 (front of electronic device 100), direction 2 (rear of electronic device 100), direction 3 (left of electronic device 100), and direction 4 (right of electronic device 100). The front of electronic device 100 can be the side where the display screen is located, and the rear of electronic device 100 can be the side where the back cover is located. The photographer can be positioned at direction 1 (front of electronic device 100), and the subject can be positioned at direction 2 (rear of electronic device 100). The sound detected and collected from various directions when electronic device 100 records video can be considered as sound in different sound zones; a diagram of these sound zones can be found in Figure 12B.

[0235] As shown in Figure 12B, when the electronic device 100 records video, it can detect and capture sound from multiple sound zones (also known as sound fields). These sound zones can be located at different positions on the electronic device 100 (center point). Taking four sound zones as an example, these four sound zones can include: sound zone 1 located at position 1 in front of the electronic device 100, sound zone 2 located at position 2 behind the electronic device 100, sound zone 3 located at position 3 to the left of the electronic device 100, and sound zone 4 located at position 4 to the right of the electronic device 100. The sound zones can be understood as sectors within a circle centered on the electronic device 100; therefore, the angle of the sector can be used to characterize the range of the sound zone. The angle of sound zone 1 can be 'a', the angle of sound zone 2 can be 'b', the angle of sound zone 3 can be 'c', and the angle of sound zone 4 can be 'd'. Where a+b+c+d = 360 degrees, but not limited to this, in some other examples, the value of (a+b+c+d) can also be less than 360 degrees, which can be understood as the electronic device 100 not collecting sound from certain directions. In other examples, the value of (a+b+c+d) can also be greater than 360 degrees, which can be understood as the ranges of any two sound zones overlapping. The embodiments of this application do not limit the range of sound zones.

[0236] In some embodiments of this application, when the electronic device 100 records video, it can store some or all of the audio from multiple audio regions into the main audio track of the video. For example, when the electronic device 100 records video, it can capture the audio from four audio regions: region 1, region 2, region 3, and region 4, and store the audio from one or more of these four regions into the main audio track of the video. The audio from regions not stored in the main audio track can be stored in other audio tracks for later use.

[0237] Figures 13A-13J are schematic diagrams of a user interface for creating a new audio event during video recording, according to an embodiment of this application. Figures 13A-13J can be applied to the video recording scenarios shown in Figures 12A-12B.

[0238] As shown in Figure 13A, the electronic device 100 can display a user interface 1310 for a camera application. The user interface 1310 may include an image acquisition area 1311, a shooting mode selection bar 1312, and a shooting control 1313. The image acquisition area 1311 can be used to display image content captured by the electronic device 100 through the front-facing camera and / or the rear-facing camera. The following explanation uses the display of image content captured by the rear-facing camera as an example. The selection bar 1312 may include one or more shooting mode options, such as option 1312A for "photo" mode, option 1312B for "video" mode, and option 1312C for "more" (used to trigger the display of more shooting mode options). Option 1312B is selected, indicating that the currently used shooting mode is video mode. The shooting control 1313 can be used to trigger the start of the video recording function. In some embodiments, the electronic device 100 can receive user input (e.g., touch click operation) applied to the shooting control 1313 in the user interface 1310. In response to the user input, the electronic device 100 can activate the recording function, that is, start video recording, and at this time the user interface 1320 shown in FIG13B can be displayed.

[0239] As shown in Figure 13B, the user interface 1320 is similar to the user interface 1310 shown in Figure 13A. User interface 1310 represents the interface before video recording begins, while user interface 1320 represents the interface during video recording. Therefore, the display method of the shooting control 1313 in user interface 1310 differs from that in user interface 1320, for example, in shape and / or color. The shooting control 1313 in user interface 1320 is used to trigger the closing of the recording function, i.e., to end video recording. The image acquisition area 1311 in user interface 1320 displays time information 1321, which is used to display the duration of video recording, such as "00:01" as shown in user interface 1320. User interface 1320 also includes a photo-taking control 1322, which can be used to take photos during video recording. The user interface 1320 also includes an audio tag control 1323, which can be used to enable the audio tagging function. The audio tagging function can be used to mark / record audio in a target audio region within a target time period (which may be referred to as target audio). It can also be understood as the audio tagging function being used to create a target audio event that indicates the target audio. In some embodiments, the electronic device 100 can receive user input (e.g., a touch click operation) applied to the audio tagging control 1323 in the user interface 1320. In response to the user input, the electronic device 100 can enable the audio tagging function, at which time the user interface 1330 shown in FIG13C can be displayed.

[0240] As shown in Figure 13C, the user interface 1330 is similar to the user interface 1320 shown in Figure 13B. User interface 1320 is the user interface with the audio tagging function disabled, while user interface 1330 is the user interface with the audio tagging function enabled. Therefore, the display method of the audio tag control 1323 in user interface 1320 is different from that in user interface 1330, for example, their shape and / or color are different. The audio tag control 1323 in user interface 1330 is used to trigger the disabling of the audio tagging function. The image acquisition area 1311 in user interface 1330 displays a register adjustment control 1331 with the audio tagging function. The register adjustment control 1331 is used to provide the direction and / or range of the target register where the target audio is located, which is marked / recorded by the audio tagging function. In some embodiments, the electronic device 100 can receive user input acting on the register adjustment control 1331 in the user interface 1330. The electronic device 100 can adjust the direction of the target register to the direction indicated by the user input. For example, if the user input is a touch swipe operation, the electronic device 100 can adjust the direction of the target register to the swipe direction of the touch swipe operation. FIG13C illustrates this with the swipe direction of the touch swipe operation being a downward swipe. The electronic device 100 can adjust the direction of the target register to position 1 as shown in FIG12A according to the downward swipe touch swipe operation shown in FIG13C, that is, set the target register to register 1 located at position 1 as shown in FIG12B. In some embodiments, after the electronic device 100 adjusts the direction of the target register, a schematic diagram of the adjusted target register can be displayed through the register adjustment control 1331. For a specific example, see the register adjustment control 1331 in the user interface 1340 shown in FIG13D.

[0241] As shown in Figure 13D, the user interface 1340 is similar to the user interface 1330 shown in Figure 13C. Compared to the time information 1321 "00:01" in user interface 1330, the time information 1321 in user interface 1340 can be increased to "00:02", indicating that the video recording duration is 2 seconds. The display method of the audio range adjustment control 1331 in user interface 1330 and the display method of the audio range adjustment control 1331 in user interface 1340 can be different. The audio range adjustment control 1331 in user interface 1340 can be used to display a schematic diagram of the target audio range after adjustment. For example, the area 1331A between the two arrows shown in the audio range adjustment control 1331 is the adjusted target audio range, which corresponds to audio range 1 shown in Figure 12B. In some embodiments, the electronic device 100 can receive user input acting on the register adjustment control 1331 in the user interface 1340. The electronic device 100 can adjust the range of the target register to the range indicated by the user input. For example, if the user input is a two-finger swipe operation, the electronic device 100 can select to increase or decrease the range of the target register according to the swiping direction of the two-finger swipe operation, and can select the adjustment value of the range of the target register according to the swiping amplitude of the two-finger swipe operation. Figure 13D illustrates this using a two-finger swipe operation with an inward swiping amplitude of 1 as an example. The electronic device 100 can determine to decrease the range of the target register based on the inward swiping operation, and the adjustment value is determined based on the amplitude of 1 (e.g., proportionally). As shown in Figure 12B, the range of the target register (i.e., register 1) can be characterized by the angle a of the target register. Therefore, adjusting the range of the target register can be done by adjusting the angle a. The electronic device 100 can decrease the angle a based on the user input of the inward swiping amplitude of 1 shown in Figure 13D. Optionally, it can also increase the angles c and / or d so that a+b+c+d = 360 degrees. In some embodiments, after the electronic device 100 adjusts the range of the target audio range, a schematic diagram of the adjusted target audio range can be displayed through the audio range adjustment control 1331. For a specific example, please refer to the audio range adjustment control 1331 in the user interface 1350 shown in FIG13E.

[0242] As shown in Figure 13E, user interface 1350 is similar to user interface 1340 shown in Figure 13D. The display method of the register adjustment control 1331 in user interface 1340 can differ from that in user interface 1350. The register adjustment control 1331 in user interface 1350 can be used to display a schematic diagram of the target register after adjustment. For example, the area 1331A between the two arrows shown in register adjustment control 1331 is the adjusted target register. The angle of the area 1331A between the two arrows shown in register adjustment control 1331 in user interface 1350 is smaller than the angle of the area 1331A between the two arrows shown in register adjustment control 1331 in user interface 1340. Therefore, the range of the target register indicated by register adjustment control 1331 in user interface 1350 is smaller than the range of the target register indicated by register adjustment control 1331 in user interface 1340.

[0243] Following Figure 13E, as shown in Figure 13F, the electronic device 100 can display a user interface 1360, which is similar to the user interface 1350 shown in Figure 13E. Compared to the time information 1321 "00:02" in user interface 1350, the time information 1321 in user interface 1360 can be increased to "00:05", representing a video recording duration of 5 seconds. In some embodiments, the electronic device 100 can receive user input (e.g., touch click operation) applied to the audio tag control 1323 in user interface 1360. In response to this user input, the electronic device 100 can disable the audio tag function. Furthermore, the electronic device 100 can store the target audio of the target audio region acquired during the period when the audio tag function is enabled (i.e., within the target time period) in a preset audio tag track and obtain a target audio event indicating the target audio. The process from displaying the user interface 1320 shown in Figure 13B (time information 1321 is "00:01") to displaying the user interface 1360 shown in Figure 13F (time information 1321 is "00:05") is the process when the audio tag function is enabled. Therefore, the target time period is "00:01" to "00:05" in the currently recorded target video. The target audio region is the user-adjusted target audio region in the user interface 1350 shown in Figure 13E, that is, the target audio region represented by the area 1331A between the two arrows shown in the audio region adjustment control 1331 in the user interface 1350. The target audio in the audio tag track can be stored in the main audio track of the currently recorded target video, or it can be not stored in the main audio track of the currently recorded target video. This embodiment of the application will be described using the default example of not storing it in the main audio track.

[0244] For example, the target audio region corresponding to the audio tagging function is audio region 1 as shown in Figure 12B. The photographer belongs to the audio source within audio region 1. The photographer can simultaneously input voice during video recording using the audio tagging function. The electronic device 100 can collect and record the sound emitted by the photographer within audio region 1 and store it in the audio tag track. Since the target audio in the audio tag track may not be stored in the main audio track of the target video, the photographer can use the audio tagging function to mask the sound emitted by the photographer in the target video. Not limited to this, in other examples, the target audio in the audio tag track can also be stored in the main audio track of the target video, and the photographer can use the audio tagging function to mark the sound emitted by the photographer in the target video. Not limited to this, in other examples, the target audio region can also be audio region 2 as shown in Figure 12B, and the subject belongs to the audio source within audio region 2. This also allows marking the sound emitted by the subject during video recording. Based on the above description, it can be seen that the audio tagging function provided in this application embodiment can meet the personalized needs of users.

[0245] Following Figure 13F, as shown in Figure 13G, the electronic device 100 can display a user interface 1370. User interface 1370 is similar to user interface 1360 shown in Figure 13F, except that user interface 1360 is the user interface with the audio tag function enabled, while user interface 1370 is the user interface with the audio tag function disabled. Therefore, user interface 1370 does not include the zone adjustment control 1331 found in user interface 1360. The display method of the audio tag control 1323 in user interface 1370 differs from that in user interface 1360, for example, in shape and / or color. The audio tag control 1323 in user interface 1370 is used to trigger the re-enabling of the audio tag function.

[0246] Following Figure 13G, as shown in Figure 13H, the electronic device 100 can display a user interface 1380, which is similar to the user interface 1370 shown in Figure 13G. Compared to the time information 1321 "00:05" in user interface 1370, the time information 1321 in user interface 1380 can be increased to "00:20", indicating that the video recording duration is 20 seconds. In some embodiments, the electronic device 100 can receive user input (e.g., touch click operation) applied to the shooting control 1313 in user interface 1380. In response to this user input, the electronic device 100 can turn off the recording function, i.e., end the video recording, and obtain the recorded target video. The target video duration is 20 seconds. An example of the post-editing interface for the target video can be seen in Figure 14, and will not be detailed here.

[0247] Not limited to the embodiments shown in Figures 13A-13H, in other embodiments, the electronic device 100 may also activate the audio tagging function in response to a user input, and set the direction and / or range of the target audio region where the audio tagging function marks / records the target audio. For example, as shown in Figure 13I, the electronic device 100 may display the user interface 1320 shown in Figure 13B. The electronic device 100 may receive user input acting on the audio tagging control 1323 in the user interface 1320, which is a touch-slide operation. In response to this user input, the electronic device 100 may activate the audio tagging function and set the direction of the target audio region where the audio tagging function marks / records the target audio region to the sliding direction of the touch-slide operation. Figure 13I illustrates this using a downward sliding direction as an example. The electronic device 100 can adjust the direction of the target audio region to orientation 1 as shown in Figure 12A based on the downward sliding touch-slide operation. Therefore, the target audio region can be the audio region 1 located at orientation 1 as shown in Figure 12B. At this time, the electronic device 100 can display the user interface 1390 shown in Figure 13J. The user interface 1390 is similar to the user interface 1340 shown in Figure 13D. The pitch range adjustment control 1331 in the user interface 1390 can be used to display a schematic diagram of the target pitch range. For example, the area 1331A between the two arrows shown in the pitch range adjustment control 1331 is the target pitch range, which is determined according to the user input mentioned above. This target pitch range corresponds to pitch range 1 shown in Figure 12B. Furthermore, the time information 1321 in the user interface 1390 is smaller than the time information 1321 in the user interface 1340, that is, "00:01". This can reduce the user operations performed when creating a new audio event, reduce the time spent performing user operations, and thus improve the efficiency of creating a new audio event.

[0248] In some embodiments, the electronic device 100 may be configured with an audio tagging function to mark / record the target audio in a default target audio zone. This allows the target audio to be marked / recorded even if no user input for setting the target audio zone is received. For example, the default target audio zone is zone 1 or zone 2 as shown in Figure 12B.

[0249] The register adjustment control 1331 shown in Figures 13A-13J is for illustrative purposes only and should not be construed as limiting. For example, the register adjustment control 1331 in the user interface 1330 shown in Figure 13C can display a schematic diagram of the default target register, such as register 1 shown in Figure 12B.

[0250] The above embodiments illustrate the use of enabling the audio tag function once during a video recording process (i.e., creating a new audio event). In other embodiments, the audio tag function can be enabled multiple times during a video recording process, and each time the audio tag function is enabled, a new audio event can be created.

[0251] Figure 14 is a schematic diagram of a user interface for displaying audio events provided in an embodiment of this application. The audio events shown in Figure 14 can be audio events created in the processes shown in Figures 13A-13H.

[0252] As shown in Figure 14, the electronic device 100 can display a user interface 1400. In some embodiments, the user interface 1400 can be a post-editing interface for the target video (referred to as Video 2) recorded in the process shown in Figures 13A-13H. Similar to the user interface 530 shown in Figure 5C, the user interface 1400 can include a playback area 1401 for Video 2, playback time information 1402 for Video 2, an audio playback progress bar 1403 for Video 2, and a display bar 1404. The playback area 1401 is used to display the image content of Video 2. The playback time information 1402 can include the playback time point of Video 2 (“00:00” when Video 2 is not playing) and the total duration (i.e., “00:20”), for example, displayed as “00:00 / 00:20”. The audio playback progress bar 1403 can display identifiers of one or more audio events of Video 2, such as the identifier 1403A (including the letter A) for audio event A. The audio event A can be the target audio event created in the process shown in Figures 13A-13H. Therefore, the audio 4 indicated by the audio event A can be the target audio of the target sound range collected in the process shown in Figures 13B-13F (i.e., within the target time period "00:01" to "00:05"). An example of the schematic diagram of the target sound range can be seen in the target sound range (i.e., the area 1331A between the two arrows shown in the sound range adjustment control 1331) displayed in the user interface 1360 shown in Figure 13F.

[0253] As shown in Figure 14, the display bar 1404 in the user interface 1400 is used to display information about audio event A, including, for example, name 1404A (“Audio Event A”), type information 1404B, time information 1404C, playback controls 1404D, and track marker 1404E. Furthermore, the display bar 1404 can also display the playback progress bar 1404F, playback node 1404G, playback time point 1404H, and end time point 1404I of the audio 4 indicated by audio event A. The type information 1404B is used to characterize the type of audio event A; for example, if type information 1404B is “custom”, it indicates that audio event A is user-defined. The time information 1404C is used to display the time point of the audio 4 indicated by audio event A. This time point can be the time point corresponding to the display position of the identifier 1403A of audio event A on the audio playback progress bar 1403, for example, the start time point of the audio 4 indicated by audio event A, “00:01”. Playback control 1404D is used to play and / or pause audio 4 indicated by audio event A. Track flag 1404E indicates whether audio 4 indicated by audio event A is within the main audio track of video 2. The track flag 1404E shown in user interface 1400 indicates that the audio indicated by audio event A is not within the main audio track of video 2; therefore, audio 4 indicated by audio event A will not be played when video 2 is played. The display position of playback node 1404G on the playback progress bar 1404F can be used to indicate / correspond to the time point when audio 4 is playing, i.e., playback time point 1404H. For example, when audio 4 is not playing, playback node 1404G is located at the starting point of the playback progress bar 1404F, and playback time point 1404H is the starting time point of audio 4 on the audio playback progress bar 1403, i.e., "00:01" as shown in time information 1404C. End time point 1404I is the ending time point of audio 4 on the audio playback progress bar 1403, i.e., "00:05". In some embodiments, the electronic device 100 can provide editing functions for audio event A shown in FIG14, such as modifying the time information of audio event A by moving the identifier 1403A of audio event A, modifying any information of audio event A shown in the display bar 1404, or deleting audio event A. In some embodiments, the electronic device 100 can provide the function of adding audio events to the video 2 shown in FIG14, such as creating a new audio event in FIG14 that indicates a certain period of audio on the audio playback progress bar 1403.

[0254] Figures 15A-15C are schematic diagrams of a settings interface provided in an embodiment of this application.

[0255] As shown in Figure 15A, the electronic device 100 can display a user interface 1510 for a camera application. The user interface 1510 is similar to the user interface 1310 shown in Figure 13A, and the user interface 1510 may also include a settings control 1511. In some embodiments, the electronic device 100 can receive user input (e.g., a touch click operation) applied to the settings control 1511 in the user interface 1510. In response to the user input, the electronic device 100 can display a settings interface. A specific example can be found in the user interface 1520 shown in Figure 15B.

[0256] As shown in Figure 15B, the user interface 1520 may include a photo settings bar 1521 and a video settings bar 1522. The photo settings bar 1521 may include one or more photo setting options (which can also be understood as photo shooting mode setting options), such as photo aspect ratio settings, smart shooting settings, high-quality mode settings, etc. The video settings bar 1522 may include one or more video setting options (which can also be understood as video recording mode setting options), such as video resolution settings, video frame rate settings, and audio tag settings 1522A. In some embodiments, the electronic device 100 may receive user input (e.g., touch click operation) applied to the settings option 1522A in the user interface 1520. In response to the user input, the electronic device 100 may display the audio tag function settings interface; a specific example can be found in the user interface 1530 shown in Figure 15C.

[0257] As shown in Figure 15C, the user interface 1530 may include a settings bar 1531 for the audio tag function. The settings bar 1531 may include a prompt message 1531A and a switch control 1531B for the audio tag function. The prompt message 1531A may include the text "An event where audio tags can be manually set during video recording to add audio from a specific audio region to the video," explaining the audio tag function. The switch control 1531B can be used to control whether the audio tag function is enabled. For example, if the switch control 1531B shown in the user interface 1530 is in an "on" state, it indicates that the audio tag function is enabled. For example, when the audio tag function is enabled, during video recording, the electronic device 100 may display an audio tag control for enabling the audio tag function, such as the audio tag control 1323 in the user interface 1320 shown in Figure 13B.

[0258] As shown in Figure 15C, when the audio tag function is enabled, the user interface 1530 may also include a settings bar 1532 related to the audio tag function. The settings bar 1532 may include a prompt message 1532A and a corresponding switch control 1532B. The prompt message 1532A may include the characters "Block audio tags in video," indicating that the switch control 1532B controls whether to block the audio tags' audio (i.e., the audio of a specific audio range indicated by an audio event) in the recorded video. For example, if the switch control 1532B shown in the user interface 1530 is in the enabled state, it indicates that the audio tags' audio is blocked in the recorded video. For example, when the switch control 1532B is in the enabled state, during video recording, the electronic device 100 may not save the target audio recorded by the audio tag function (i.e., the target audio indicated by a newly created target audio event) into the main audio track of the recorded video. When the switch control 1532B is in the disabled state, the electronic device 100 will save the target audio recorded by the audio tag function into the main audio track of the recorded video.

[0259] As shown in Figure 15C, when the switch control 1532B shown in the user interface 1530 is in the on state, the user interface 1530 may also include a settings bar 1533. The settings bar 1533 may include a prompt message 1533A and a corresponding switch control 1533B. The prompt message 1533A may include the characters "Mute only human voices," indicating that the switch control 1533B is used to control whether to mute only human voices in the audio of the audio tag in the recorded video. For example, if the switch control 1533B shown in the user interface 1530 is in the off state, it indicates that all audio of the audio tag is mute in the recorded video. For example, when the switch control 1533B is in the off state, during the video recording process, the electronic device 100 will not store the target audio recorded by the audio tag function (i.e., the target audio indicated by the newly created target audio event) into the main audio track of the recorded video. When the switch control 1533B is in the on state, for the target audio recorded by the audio tag function, the electronic device 100 will not store the human voice in the target audio into the main audio track of the recorded video, but will store other sounds in the target audio besides the human voice into the main audio track of the recorded video.

[0260] Not limited to the embodiments shown in Figures 15A-15C, in other embodiments, a function setting bar can also be provided for users to block other types of sounds (such as background noise) in the target audio. The display example is similar to setting bar 1533. The embodiments of this application do not limit the setting functions related to the audio tag function.

[0261] Not limited to the embodiments shown in Figures 15A-15C, in some embodiments, one or more settings bars in the user interface 1530 shown in Figure 15C may also be displayed during video recording. In other embodiments, one or more settings bars in the user interface 1530 shown in Figure 15C may also be displayed in the post-editing interface of the video. The specific display location of the settings function is not limited in the embodiments of this application.

[0262] The above embodiments use video audio events as an example for illustration. In other embodiments, the electronic device 100 can also display one or more audio events and provide related functions similar to those for video audio events, such as playing the audio indicated by the audio event, editing the information of the audio event, deleting the audio event, creating a new audio event, and performing audio editing operations on the audio indicated by the audio event, etc. The following description uses the display of audio events as an example; other scenarios will not be elaborated upon.

[0263] Figures 16A-16E are schematic diagrams of another user interface for displaying audio events provided in the embodiments of this application.

[0264] As shown in Figure 16A, the electronic device 100 can display a desktop 1610, which is the same as the desktop 310 shown in Figure 3A. In some embodiments, the electronic device 100 can receive user input (e.g., a touch click operation) applied to the icon 1611 of the recorder application on the desktop 1610. In response to the user input, the electronic device 100 can launch the recorder application and display the user interface of the recorder application. A specific example can be found in Figure 16B.

[0265] As shown in Figure 16B, the electronic device 100 can display a user interface 1620 for a recorder application. The user interface 1620 can include an audio list 1621 for the recorder application. The audio list 1621 can include one or more stored audio files, such as audio 1621A and audio 1621B. The user interface 1620 can also include a category list 1622 under "Smart Categorization." The category list 1622 can include one or more categories that categorize audio according to different sound types (or, in other words, categorize video according to the audio context). For example, it could include a "Dialogue 1" category 1622A, a "Cat" category 1622B, and an "Outdoor" category 1622C. Specifically, the audio under the "Dialogue 1" category 1622A includes type 1 dialogues, and this category may include one audio file. The audio under the "Cat" category 1622B includes cat sounds, and this category may include one audio file. The audio under the "Outdoor" category 1622C includes outdoor sounds, and this category may include two audio files. For example, different types of dialogues may include different types of human voices, or they may be in different scenarios. This application embodiment does not limit the classification method for different dialogues. Understandably, an audio file may include multiple types of sounds, and therefore an audio file can be divided into multiple categories. For example, audio 1621A includes cat sounds and outdoor sounds, so audio 1621A can be under both the "cat" category 1622B and the "outdoor" category 1622C. Since an audio file can be divided into multiple categories, the number of audio files included in audio list 1621 (i.e., 2) is less than the sum of the number of audio files under each category included in category list 1622 (i.e., 1+1+2=4).

[0266] In some embodiments, the electronic device 100 may receive user input (e.g., touch click operation) acting on any category displayed on the user interface 1620 (taking the "cat" category 1622B as an example). In response to the user input, the electronic device 100 may display the user interface of the "cat" category 1622B. For a specific example, see Figure 16C.

[0267] As shown in Figure 16C, the electronic device 100 can display a user interface 1630 for a recorder application. The user interface 1630 can display an audio list under the "Cat" category 1622B shown in Figure 16B. This audio list can include one or more audio recordings containing cat sounds, such as audio 1631, which is audio 1621A shown in Figure 16B. Audio 1631 can include name information 1631A, date information 1631B, and time information 1631C. The date information 1631B displays the time when audio 1631 was recorded or stored, for example, "2024 / 12 / 20". The name of audio 1631 displayed in the name information 1631A can be related to the time when audio 1631 was recorded or stored, for example, "20241220_1000". It is not limited to this; it can also be related to the recording or storage method. For example, the name of audio obtained from a telephone recording can include "call". This embodiment of the application does not limit the naming method for audio and video. Time information 1631C is used to display the total duration of audio 1631, for example, "00:02:28". In some embodiments, electronic device 100 may receive user input (e.g., touch click operation) applied to audio 1631 in user interface 1630. In response to the user input, electronic device 100 may display information about audio 1631, as shown in Figure 16D for a specific example.

[0268] As shown in Figure 16D, the electronic device 100 can display a user interface 1640 for a recorder application. The user interface 1640 can be used to display information about the audio 1631 shown in Figure 16C. The user interface 1640 may include a playback progress bar 1641 (also called an audio playback progress bar 1641), playback nodes 1642, playback time points 1643, total duration 1644, and playback controls 1645. The playback progress bar 1641 may include multiple audio frames displayed in the order of audio playback, for example, from early to late, and from left to right. The multiple audio frames displayed on the playback progress bar 1641 may be some or all of the audio frames of the audio 1631, and each audio frame can be displayed as its audio waveform (e.g., the frequency spectrum of the audio). Different positions on the playback progress bar 1641 correspond to / represent different time points in the audio 1631. The display position of playback node 1642 on the playback progress bar 1641 can be used to represent / correspond to the current playback time point of audio 1631, i.e., playback time point 1643, for example, "00:00:00" when not playing. The total duration 1644 is the same as the time information 1631C shown in Figure 16C, representing the total duration of audio 1631 as "00:02:28". The value range of playback time point 1643 is from "00:00:00" to "00:02:28". Playback control 1645 is used to trigger the playback of audio 1631.

[0269] As shown in Figure 16D, the playback progress bar 1641 of audio 1631 can display identifiers of one or more audio events of audio 1631, where any one audio event is used to indicate a certain segment of audio on the playback progress bar 1641. The audio indicated by the audio event of audio 1631 may or may not be within the main audio track of audio 1631. The display position of the identifier of the audio event of audio 1631 on the playback progress bar 1641 can represent / correspond to the segment of audio indicated by the audio event, or represent / correspond to any point in time within the segment of audio indicated by the audio event (e.g., the start time point or the end time point). The following explanation uses the representation / correspondence to the start time point as an example. For example, as shown in Figure 16D, the playback progress bar 1641 displays the identifier 1641A (including the number 11) for audio event 11 and the identifier 1641B (including the number 22) for audio event 22. The identifier 1641A for audio event 11 is displayed at the position corresponding to the time point "00:01" on the playback progress bar 1641, indicating that the starting time point of the audio indicated by audio event 11 is "00:01". The identifier 1641B for audio event 22 is displayed at the position corresponding to the time point "00:02" on the playback progress bar 1641, indicating that the starting time point of the audio indicated by audio event 22 is "00:02". It is understood that the user interface 1640 shown in Figure 16D only shows a portion of the playback progress bar 1641; the unshown portion of the playback progress bar 1641 may also display the identifiers of the audio events of audio 1631.

[0270] For example, as shown in FIG16D, the colors and other display methods of the identifier 1641A of audio event 11 and the identifier 1641B of audio event 22 are different, thus representing different types of audio event 11 and audio event 22. Audio event 11 is user-defined, and the audio indicated by audio event 11 is determined by electronic device 100 according to user input. Audio event 22 is automatically recognized by electronic device 100, and the audio indicated by audio event 22 is a specific type of audio recognized by electronic device 100 from audio 1631.

[0271] In some embodiments, the electronic device 100 may receive user input (e.g., a touch click operation) that identifies one or more audio events on the playback progress bar 1641 shown on the user interface 1640. In response to the user input, the electronic device 100 may display information about one or more audio events of the audio 1631. For a specific example, see the user interface 1650 shown in FIG16E.

[0272] As shown in Figure 16E, the user interface 1650 is similar to the user interface 1640 shown in Figure 16D. The user interface 1650 also includes display bars 1651 and 1652. Display bar 1651 displays information about audio event 11, such as name 1651A (“Audio Event 11”), type information 1651B, time information 1651C, playback controls 1651D, and track marker 1651E. The type information 1651B characterizes the type of audio event 11; for example, if type information 1651B is “custom,” it indicates that audio event 11 is user-defined. The time information 1651C displays the time point of the audio indicated by audio event 11. This time point can be the time point corresponding to the display position of the identifier 1641A of audio event 11 on the playback progress bar 1641, for example, the start time point of the audio indicated by audio event 11, “00:01.” Playback controls 1651D play the audio indicated by audio event 11. The audio track flag 1651E is used to indicate whether the audio indicated by audio event 11 is within the main audio track of audio 1631. The audio track flag 1651E shown in the user interface 1650 indicates that the audio indicated by audio event 11 is not within the main audio track of audio 1631, so the audio indicated by audio event 11 will not be played when audio 1631 is played.

[0273] As shown in Figure 16E, the display bar 1652 is used to display information about the audio event 22, including, for example, a name 1652A (“Audio Event 22”), type information 1652B, time information 1652C, playback controls 1652D, and track markers 1652E. The type information 1652B characterizes the type of audio event 22 and the type of audio indicated by the audio event 22. For example, if the type information 1652B is “cat,” it indicates that the audio event 22 is an audio event automatically recognized by the electronic device 100, and the audio indicated by the audio event 22 is “cat” type audio recognized by the electronic device 100. The time information 1652C displays the time point of the audio indicated by the audio event 22. This time point can be the time point corresponding to the display position of the identifier 1641B of the audio event 22 on the playback progress bar 1641, for example, the start time point of the audio indicated by the audio event 22, “00:02.” The playback controls 1652D are used to play the audio indicated by the audio event 22. The audio track flag 1652E is used to indicate whether the audio indicated by audio event 22 is within the main audio track of audio 1631. The audio track flag 1652E shown in the user interface 1650 indicates that the audio indicated by audio event 22 is within the main audio track of audio 1631. Therefore, when playing audio 1631, the audio indicated by audio event 22 will not be played. For example, during the playback of audio 1631, if the playback reaches the time period of the audio indicated by audio event 22, the audio indicated by audio event 22 will be played within that time period.

[0274] In some embodiments, the electronic device 100 can provide editing functionality for any of the audio events shown in FIG16D / FIG16E, such as modifying the time information of the audio event by moving the identifier of the audio event shown in FIG16D / FIG16E, such as modifying the information of the audio event shown in FIG16E, such as deleting one or more audio events shown in FIG16D / FIG16E. In some embodiments, the electronic device 100 can provide the functionality to add audio events to the audio 1631 shown in FIG16C / FIG16D / FIG16E, such as creating a new audio event in FIG16D / FIG16E that indicates a certain period of audio on the playback progress bar 1641.

[0275] The content and display method of the audio events shown in the above embodiments are for illustrative purposes only and should not be construed as limiting. For example, users can also manually add notes to the audio events.

[0276] The user inputs shown in the above embodiments are for illustrative purposes only and should not be construed as limiting.

[0277] The following is a flowchart illustrating the audio event acquisition process. This acquisition process can be applied to the electronic device 100 shown in Figure 1, and also to the electronic device 100 shown in Figure 2.

[0278] Figure 17 is a flowchart illustrating an audio event acquisition process according to an embodiment of this application. Figure 17 uses a user customizing an audio event during audio / video recording as an example for illustration.

[0279] The process shown in Figure 17 may include, but is not limited to, the following steps:

[0280] S101: Electronic device 100 receives input from the user at time 1 to start recording the first audio and video.

[0281] For example, an example of an electronic device 100 receiving input from a user to start recording the first audio and video can be seen in Figure 13A.

[0282] In some embodiments, the first audio and video may be recorded via a system application of the electronic device 100, such as recording video via a camera application of the electronic device 100, or recording audio via a recorder application of the electronic device 100. In other embodiments, the first audio and video may also be recorded via a third-party application of the electronic device 100.

[0283] In some embodiments, at time 1, the electronic device 100, in response to received user input, begins recording the first audio and video. During the recording of the first audio and video, the electronic device 100 can acquire audio from one or more audio regions through a microphone and / or other modules such as sensors, and store some or all of the audio from these one or more audio regions into the main audio track of the first audio and video. For ease of explanation, this embodiment of the application assumes that the electronic device 100 defaults to storing all the audio from one or more audio regions into the main audio track of the first audio and video. For example, in the video shooting scenario shown in Figures 12A and 12B, the electronic device 100 can acquire audio from four audio regions: audio region 1, audio region 2, audio region 3, and audio region 4, and defaults to storing the audio from these four audio regions into the main audio track of the video. Optionally, if the recorded first audio and video is a video, the electronic device 100 can also acquire image content as the image content of the video through a camera and / or other modules such as sensors.

[0284] S102: Electronic device 100 receives input from the user to enable the audio tag function at time 2 after time 1, and receives input from the user to disable the audio tag function at time 3 after time 2. Furthermore, it acquires the first target audio of the first target audio zone between time 2 and time 3, and obtains a first target audio event indicating the first target audio.

[0285] For example, an example of electronic device 100 receiving input from a user to enable the audio tag function can be seen in Figure 13B, and an example of electronic device 100 receiving input from a user to disable the audio tag function can be seen in Figure 13F.

[0286] In some embodiments, during the recording of the first audio and video, the electronic device 100 can determine, based on received user input, to activate the audio tagging function between time 2 and time 3. Therefore, between time 2 and time 3, the electronic device 100 can detect and judge audio in different frequency ranges. When audio in the first target frequency range is detected, the electronic device 100 can acquire the first target audio in the first target frequency range and store it in the audio tagging track, and obtain the first target audio event indicating the first target audio. Here, the first target audio is the audio in the first target frequency range within time 2 to time 3 (which can be referred to as the target time period), and can also be understood as the audio corresponding to the time period between time 2 and time 3 in the first audio and video.

[0287] During time 2 to time 3, the electronic device 100 will collect audio from one or more audio regions and store it in the main audio track of the first audio and video. In some embodiments, the audio from these one or more audio regions does not include the first target audio from the first target audio region. This can be understood as the first target audio in the audio tag track being independent of the audio in the main audio track of the first audio and video. For example, in the video shooting scenario shown in Figures 12A and 12B, the first target audio region is audio region 1. During time 2 to time 3, the electronic device 100 can collect the audio from audio region 1 (i.e., the first target audio) and store it in the audio tag track, and collect the audio from audio regions 2, 3, and 4 and store it in the main audio track of the first audio and video. In other embodiments, the audio of one or more audio zones includes the first target audio of the first target audio zone. This can be understood as the audio in the main audio track of the first audio and video being superimposed with the first target audio in the audio tag track. For example, in the video shooting scenario shown in Figures 12A and 12B, the first target audio zone is audio zone 1. Between time 2 and time 3, the electronic device 100 can collect the sound of the four audio zones: audio zone 1, audio zone 2, audio zone 3, and audio zone 4, and store the audio of audio zone 1 in the audio tag track, as well as store the audio of these four audio zones (including the audio of audio zone 1 in the audio tag track) in the main audio track of the video.

[0288] In some embodiments, the electronic device 100 may select whether to store the first target audio in the main audio track of the first audio and video according to the default settings. For example, the target audio recorded / marked by the audio tag function during the audio and video recording process may not be stored in the main audio track of the first audio and video by default.

[0289] In some embodiments, the electronic device 100 can receive user input and select, based on the user input, whether to store the first target audio into the main audio track of the first audio / video. In some examples, the user input may be input applied to a settings interface, as shown in Figures 15A-15C. In other examples, the user input may be input applied to a recording interface of the first audio / video.

[0290] In some embodiments, the electronic device 100 may select, according to default settings or user input, to store a portion of the audio types in the first target audio into the main audio track of the first audio and video, while other types of audio are not stored in the main audio track of the first audio and video. For example, the settings bar 1533 shown in FIG15C provides a setting option for whether to store human voices in the main audio track.

[0291] In some embodiments, the electronic device 100 may have a preset default target audio region corresponding to the audio tag function, and the first target audio region may be the default target audio region.

[0292] In some embodiments, the electronic device 100 may receive input from a user setting a first target audio region, and in response to the user input, determine the first target audio region, for example, determining the direction and / or range of the first target audio region. Optionally, the input from the user setting the first target audio region may be an input to modify the default audio region to the first target audio region. Therefore, in response to the user input, the electronic device determines to modify the default audio region to the first target audio region, for example, by modifying the direction and / or range of the default audio region to obtain the first target audio region.

[0293] In some examples, the electronic device 100 can receive user input to set a first target audio region during the recording of the first audio / video. Examples include the direction of setting the first target audio region shown in Figures 13C-13D, the range of setting the first target audio region shown in Figures 13D-13E, and the direction of activating the audio tag function and setting the first target audio region shown in Figures 13I-13J. The first target audio region determined above may only apply to this specific audio tag function (i.e., the audio tag function activated between time 2 and time 3). Therefore, if the user activates the audio tag function again after time 3 during the recording of the first audio / video, or activates the audio tag function during the recording of other audio / video content, the target audio region corresponding to the audio tag function at this time will not be the first target audio region; for example, it may be the default target audio region. This can be understood as the user-set target audio region being instantaneous. Not limited to this, in other examples, during the recording of the first audio and video, if the user re-activates the audio tag function after time 3, the target audio region corresponding to the audio tag function at this time can also be defaulted to the first target audio region, which can be understood as recording the target audio region of the user's last operation. The embodiments of this application do not limit the method of determining the initial target audio region corresponding to any audio tag function.

[0294] S103: Electronic device 100 receives input from the user at time 4 after time 3, indicating that the recording of the first audio and video has ended.

[0295] S104: Electronic device 100 stores the main audio file of the first audio and video (time 1 to time 4), information of the first target audio event, and the file of the first target audio (time 2 to time 3).

[0296] For example, an example of the electronic device 100 receiving input from the user indicating that the recording of the first audio and video has ended can be seen in Figure 13H.

[0297] In some embodiments, at time 4 after time 3, the electronic device 100, in response to the received user input, ends the recording of the first audio and video, i.e., the first audio and video is recorded. The electronic device 100 may store related files of the first audio and video: the main audio file of the first audio and video, information about the first target audio event, and the file of the first target audio. Optionally, if the first audio and video is a video, it may also store the image file of the first audio and video. The main audio file of the first audio and video is the audio file within the main audio track of the first audio and video, and the audio within the main audio track of the first audio and video is the audio of one or more sound zones captured between time 1 and time 4. The first target audio is the audio of the first target sound zone captured between time 2 and time 3. The first target audio event is an audio event indicating the first target audio.

[0298] In some embodiments, the main audio file of the first audio / video file does not include the file containing the first target audio; that is, the first target audio is not stored in the main audio track of the first audio / video file. For example, the first target audio is stored in the audio tag track, and the first target audio in the audio tag track is independent of the audio in the main audio track of the first audio / video file. Therefore, the first target audio is not played when the first audio / video file is played. In other embodiments, the main audio file of the first audio / video file includes the file containing the first target audio; that is, the first target audio is stored in the main audio track of the first audio / video file. For example, the first target audio is stored in the audio tag track, and the audio in the main audio track of the first audio / video file is superimposed with the first target audio in the audio tag track. Therefore, the first target audio is played when the first audio / video file is played, that is, the first target audio is played at times 2 to 3 during the playback of the first audio / video file.

[0299] In some embodiments, the information of the first target audio event may include, but is not limited to, one or more of the following: the name of the first target audio event, the type of the first target audio event (e.g., the type of audio event obtained by the process shown in FIG17 is "custom" by default), the type of the first target audio (e.g., input by the user or automatically identified by the electronic device 100), the time period of the first target audio (i.e., time 2 to time 3), the track indication information of whether the first target audio is in the main audio track of the first audio and video, and the remarks information.

[0300] Examples of the electronic device 100 displaying the first target audio event can be found in the identification and information of the audio event 2 shown in Figures 5A-5D, the identification and information of the audio event A shown in Figure 14, and the identification and information of the audio event 11 shown in Figures 16D-16E.

[0301] For example, examples of the audio event acquisition process shown in Figure 17 can be found in Figures 13A-13J. For instance, an example of S101 can be found in Figure 13A, an example of S102 can be found in Figures 13B-13G (or Figures 13B-13D can be replaced with Figures 13I-13J), and an example of S103 can be found in Figure 13H. Assume the first target audio region is region 1 as shown in Figure 12B. Therefore, the first audio-video obtained in S104 is the video recorded from time point "00:00" to time point "00:20". The first target audio is the audio of region 1 recorded from time point "00:01" to time point "00:05". Assuming the first target audio is not stored in the main audio track of the first audio / video system, the main audio file of the first audio / video system specifically includes: audio from time point "00:00" to time point "00:01" in audio regions 1, 2, 3, and 4; audio from time point "00:01" to time point "00:05" in audio regions 2, 3, and 4; and audio from time point "00:05" to time point "00:20" in audio regions 1, 2, 3, and 4. Information about the first target audio event may include: the type of the first target audio event is "custom," the time period of the first target audio is "00:01-00:05," and track indication information indicating that the first target audio is not in the main audio track of the first audio / video system. An example of the electronic device 100 displaying the first target audio event can be found in Figure 14, showing the identifier and information for displaying audio event A.

[0302] Figure 17 illustrates the example of a user-defined audio event created during the recording of the first audio and video. In practice, multiple audio events can also be created.

[0303] In the method shown in Figure 17, the user can activate the audio tagging function at any time during the recording of the first audio / video, thereby recording / marking audio in a specific audio region (e.g., the first target audio in the first target audio region). The electronic device 100 can create audio events indicating the audio and store information about the audio events. The audio recorded by the audio tagging function can serve as additional audio identifiers for the first audio / video, for example, the audio used to record the status, content, or other information of the first audio / video. In this way, the user can quickly obtain relevant information about the audio marked by the user through the audio tagging function during the recording of the first audio / video by viewing the audio events recorded by the audio tagging function. The audio events recorded by the audio tagging function can be understood as notes / remarks added by the user during the recording of the first audio / video, greatly improving the efficiency of obtaining audio information and facilitating subsequent operations such as editing of the first audio / video.

[0304] Figure 18 is a flowchart illustrating another audio event acquisition process provided in an embodiment of this application. Figure 18 uses a user-defined audio event after the electronic device 100 acquires audio and video as an example for illustration.

[0305] The process shown in Figure 18 may include, but is not limited to, the following steps:

[0306] S201: Electronic device 100 acquires first audio and video.

[0307] In some embodiments, the electronic device 100 can record the first audio and video, as illustrated in Figure 17 (where the audio tagging function may not be enabled). In other embodiments, the electronic device 100 can receive the first audio and video from other devices, such as downloading it from a cloud server. This application does not limit the specific method by which the electronic device 100 acquires audio and video.

[0308] S202: When the electronic device 100 displays the first audio and video, it receives input from the user to select the second target audio in the first audio and video, and obtains a second target audio event indicating the second target audio.

[0309] In some embodiments, the electronic device 100 can receive input from a user selecting an audio segment in a first audio / video file, determine the audio segment as a second target audio based on the input, and trigger a second target audio event indicating the second target audio. The electronic device 100 can extract a file of the second target audio from the first audio / video file.

[0310] For example, as shown in Figures 11A and 11B, the electronic device 100 can receive user input (e.g., a touch swipe operation) applied to an audio segment within a selection box 1111 displayed on the audio playback progress bar 517 in the user interface 1110, and determine the second target audio as the audio segment within the selection box 1111 (i.e., the audio between time point "00:03" and time point "00:04") based on the user input. Then, the electronic device 100 can receive user input applied to a determination control 1121E in the display bar 1121 shown in the user interface 1120, and determine the creation of a second target audio event indicating the second target audio based on the user input. The second target audio event can be audio event 3 shown in the display bar 1121 of the user interface 1120.

[0311] In some embodiments, when the electronic device 100 acquires a second target audio event indicating a second target audio, it can receive user input to edit the second target audio event and acquire information about the edited second target audio event. For example, as shown in FIG11B, the electronic device 100 can receive user input applied to the display bar 1121 in the user interface 1110, and edit the information of the audio event 3 shown in the display bar 1121 according to the user input. Then, in response to user input applied to the determination control 1121E in the display bar 1121, the electronic device 100 can acquire the information of the audio event 3 shown in the display bar 1121, i.e., acquire the information of the second target audio event.

[0312] S203: Electronic device 100 stores the main audio file of the first audio / video, information of the second target audio event, and the file of the second target audio.

[0313] S203 in Figure 18 is similar to S104 in Figure 17.

[0314] In some embodiments, the main audio file of the first audio / video includes a file containing the second target audio, i.e., the second target audio is stored in the main audio track of the first audio / video. In other embodiments, the main audio file of the first audio / video does not include a file containing the second target audio, i.e., the second target audio is not stored in the main audio track of the first audio / video.

[0315] In some embodiments, the electronic device 100 may select whether to store the second target audio in the main audio track of the first audio and video according to the default settings. For example, the second target audio determined by the user input after acquiring the audio and video may be stored in the main audio track of the first audio and video by default.

[0316] In some embodiments, the electronic device 100 can receive user input and select, based on the user input, whether to store the second target audio into the main audio track of the first audio / video. In some examples, the user input can be input applied to a settings interface, as shown in Figures 15A-15C. In other examples, the user input can be received in S202, for example, as shown in Figure 11B, where the electronic device 100 can receive user input applied to settings options 1121D in the display bar 1121 shown in the user interface 1120.

[0317] In some embodiments, the electronic device 100 may select, according to default settings or user input, to store a portion of the audio from the second target audio into the main audio track of the first audio and video, while other types of audio are not stored in the main audio track of the first audio and video. For example, the settings bar 1533 shown in FIG15C provides a setting option for whether to store human voices in the main audio track.

[0318] In some embodiments, the information of the second target audio event may include, but is not limited to, one or more of the following: the name of the second target audio event, the type of the second target audio event (e.g., the type of audio event obtained by the process shown in FIG18 is "custom" by default), the type of the second target audio (e.g., input by the user or automatically identified by the electronic device 100), the time period of the second target audio, the track indication information of whether the second target audio is in the main audio track of the first audio and video, and remarks information.

[0319] Examples of the electronic device 100 displaying the second target audio event can be found in the identification and information of the audio event 2 shown in Figures 5A-5D, the identification and information of the audio event 3 shown in Figure 11C, and the identification and information of the audio event 11 shown in Figures 16D-16E.

[0320] Not limited to the embodiment shown in Figure 18, in other embodiments, the second target audio may not be the audio segment selected by the user from the first audio and video, but rather other audio input by the user through the electronic device 100, besides the first audio and video. For example, the electronic device 100 can capture the second target audio input by the user through a microphone, or the electronic device 100 can receive the second target audio imported by the user. Optionally, the second target audio determined in this way may not be stored in the main audio track of the first audio and video by default. Optionally, any information indicating the second target audio event determined in this way can be set by the electronic device 100 itself, or it can be input / edited by the user through the electronic device 100. For example, after the user inputs a second target audio of duration 1, time point 3 in the first audio and video can be set as the start time point corresponding to the second target audio, and the end time point corresponding to the second target audio can be time point 4 after duration 1 following time point 3 in the first audio and video. Therefore, the time period of the second target audio in the second target audio event is from time point 3 to time point 4 in the first audio and video.

[0321] Figure 18 illustrates the example of a user-defined audio event created after the first audio and video are acquired. In the actual implementation, multiple audio events can also be created.

[0322] In the method shown in Figure 18, the user can mark audio segments (e.g., second target audio) in the first audio / video stored in the electronic device 100 at any time, and the electronic device 100 can create audio events indicating the audio segments and store information about the audio events. In this way, the user can quickly obtain relevant information about the audio segments previously marked by the user by viewing the information of the audio events. User-defined audio events can be understood as notes / annotations added by the user in the post-editing scenario of the first audio / video. When the user wants to obtain information about the audio indicated by the audio event, they do not need to listen to the entire first audio / video every time, or even repeatedly drag the playback progress bar of the first audio / video, greatly improving the efficiency of obtaining audio information and facilitating subsequent operations such as editing of the first audio / video.

[0323] Figure 19 is a flowchart illustrating another audio event acquisition process provided in an embodiment of this application. Figure 19 illustrates the process by which the electronic device 100 automatically identifies audio events after acquiring audio and video.

[0324] The process shown in Figure 19 may include, but is not limited to, the following steps:

[0325] S301: Electronic device 100 acquires first audio and video.

[0326] S301 in Figure 19 is similar to S201 in Figure 18. For details, please refer to the description of S201 in Figure 18.

[0327] S302: Electronic device 100 uses an audio event detection algorithm to identify a third target audio of the first target type from the audio of the first audio and video, and obtains a third target audio event indicating the third target audio.

[0328] In some embodiments, after acquiring the first audio and video, the electronic device 100 can automatically run an audio event detection algorithm to identify a third target audio of a first target type from the audio of the first audio and video, and obtain a third target audio event indicating the third target audio. The electronic device 100 can extract the file of the third target audio from the first audio and video.

[0329] In some embodiments, the first target type can be a preset audio type in the audio event detection algorithm, or it can be an unpreset audio type obtained through analysis by the audio event detection algorithm. The first target type may include, but is not limited to, animal sounds, human voices, and environmental sounds. Animal sounds can be further subdivided into the sounds of various animals, such as cat meows, dog barks, bird calls, etc. Human voices can be subdivided into the voices of different people, such as children's voices, elderly people's voices, women's voices, men's voices, etc. Environmental sounds can be subdivided into sounds in different environments, such as concert sounds, fireworks sounds, etc. This is not limited to these examples. In other examples, human voices can also be subdivided into human voices in different scenarios, such as singing, laughter, crying, etc. In other examples, environmental sounds may also include clapping sounds, wind sounds, etc. The specific content of the audio type is not limited in the embodiments of this application.

[0330] S303: Electronic device 100 stores the main audio file of the first audio / video, information of the third target audio event, and the file of the third target audio.

[0331] S303 in Figure 19 is similar to S104 in Figure 17.

[0332] In some embodiments, the main audio file of the first audio / video includes a file containing a third target audio, i.e., the third target audio is stored in the main audio track of the first audio / video. In other embodiments, the main audio file of the first audio / video does not include a file containing the third target audio, i.e., the third target audio is not stored in the main audio track of the first audio / video.

[0333] In some embodiments, the electronic device 100 may select whether to store the third target audio in the main audio track of the first audio and video according to the default settings. For example, a specific type of third target audio automatically identified by the electronic device 100 from the first audio and video may be stored in the main audio track of the first audio and video by default.

[0334] In some embodiments, the electronic device 100 can receive user input and select, based on the user input, whether to store the third target audio into the main audio track of the first audio / video. In some examples, the user input may be input applied to a settings interface, with specific examples similar to those in Figures 15A-15C. In other examples, the user input may be received by the electronic device 100 after prompting the user to make a selection in S302.

[0335] In some embodiments, the electronic device 100 may, according to default settings or user input, select to store some types of audio from the third target audio into the main audio track of the first audio and video, while other types of audio are not stored into the main audio track of the first audio and video. For example, the settings bar 1533 shown in FIG15C provides a setting option for whether to store human voices into the main audio track.

[0336] In some embodiments, the information of the third target audio event may include, but is not limited to, one or more of the following: the name of the third target audio event, the type of the third target audio event (e.g., the type of audio event obtained by the process shown in FIG19 is "automatically identified" by default), the type of the third target audio (e.g., the first target type identified by the electronic device 100, or the audio type input by the user), the time period of the third target audio, the track indication information of whether the third target audio is in the main audio track of the first audio and video, and the remarks information.

[0337] Examples of the display of a third target audio event by the electronic device 100 can be found in the identification and information of the audio event 1 shown in Figures 5A-5D, and in the identification and information of the audio event 22 shown in Figures 16D-16E.

[0338] Figure 19 illustrates the identification of an audio event from the first audio and video. In a specific implementation, multiple audio events can also be identified.

[0339] Not limited to the embodiment shown in FIG19, in other embodiments, the electronic device 100 may also perform S302-S303 in response to user input.

[0340] In the method shown in Figure 19, the electronic device 100 can automatically identify specific types of audio segments from the first audio and video, and create audio events indicating those audio segments and store information about those audio events. In this way, users can quickly obtain relevant information about specific types of audio segments by viewing the information of the audio events. Users do not need to listen to the entire first audio and video every time they want to obtain audio information, or even repeatedly drag the playback progress bar, greatly improving the efficiency of obtaining audio information and facilitating subsequent operations such as editing of the first audio and video.

[0341] The following describes the display method provided in the embodiments of this application. This display method can be applied to the electronic device 100 shown in FIG1, and also to the electronic device 100 shown in FIG2.

[0342] Figure 20 is a flowchart illustrating a display method provided in an embodiment of this application.

[0343] The process shown in Figure 20 may include, but is not limited to, the following steps:

[0344] S401: After acquiring the first audio and video, the electronic device 100 receives user input on the first audio and video.

[0345] The description of acquiring the first audio and video in S401 of Figure 20 is similar to that in S201 of Figure 18. For details, please refer to the description of S201 in Figure 18.

[0346] In some embodiments, the user input to the first audio / video shown in S401 can be used to trigger the display of information about the first audio / video. Examples of the process by which the electronic device 100 triggers the display of information about the first audio / video can be found in Figures 3A-3D, 4A-4D, and 16A-16C.

[0347] S402: Electronic device 100 displays a playback progress bar for a first audio / video, wherein the playback progress bar for the first audio / video displays identifiers of one or more audio events of the first audio / video.

[0348] S403: Electronic device 100 displays information about one or more audio events of the first audio / video.

[0349] In some embodiments, in response to the user input shown in S401, the electronic device 100 may display a playback progress bar for the first audio / video, and display identifiers of one or more audio events of the first audio / video on the playback progress bar. If the first audio / video is audio, an audio playback progress bar for the audio may be displayed, and identifiers of audio events may be displayed on the audio playback progress bar. A specific example can be seen in the playback progress bar 1641 in the user interface 1640 shown in FIG. 16D, and the identifiers of audio events displayed on the playback progress bar 1641. If the first audio / video is video, a video playback progress bar and an audio playback progress bar for the video may be displayed, and identifiers of audio events may be displayed on the audio playback progress bar. A specific example can be seen in the video playback progress bar 516 and an audio playback progress bar 517 in the user interface 510 shown in FIG. 5A, and the identifiers of audio events displayed on the audio playback progress bar 517. Not limited thereto, in other examples, the electronic device 100 may also display identifiers of audio events on the video playback progress bar of the video.

[0350] In some embodiments, any one of one or more audio events in the first audio / video can be referred to as the first audio event. The electronic device 100 can display an identifier of the first audio event on a first time segment of the playback progress bar of the first audio / video. The first audio event is used to mark / indicate the first audio of the first time segment on the playback progress bar. The display position of the identifier of the first audio event on the playback progress bar can be the position of the first time segment or the position of any moment within the first time segment.

[0351] In some embodiments, the first audio event is determined by the electronic device 100 based on user input, i.e., a user-defined audio event. In some examples, the first audio event is determined by the electronic device 100 based on user input during the recording of the first audio and video. The first audio event indicates that the first audio is the audio of a specific sound range collected by the electronic device 100 during the recording of the first audio and video of the first time segment. The specific acquisition process can be seen in Figure 17. In other examples, the first audio event is determined by the electronic device 100 based on user input after acquiring the first audio and video. The first audio indicated by the first audio and video is the audio segment of the first time segment determined by the electronic device 100 from the first audio and video based on user input. The specific acquisition process can be seen in Figure 18.

[0352] In other embodiments, the first audio event is an audio event that the electronic device 100 identifies from the first audio and video, that is, an audio event that the device automatically identifies. The first audio event indicates a specific type of audio that the electronic device 100 identifies from the audio of the first audio and video. The specific acquisition process can be seen in Figure 19.

[0353] In some embodiments, the electronic device 100 may receive user input acting on an identifier of an audio event after S402, and in response to the user input, display information about the audio event, i.e., execute S403. Specific examples can be found in Figures 5A-5D. In other embodiments, the electronic device 100 may automatically display information about the audio event while displaying the identifier of the audio event; that is, S402 and S403 may be executed simultaneously.

[0354] In some embodiments, the information of the first audio event may include, but is not limited to, one or more of the following: the name of the first audio event, the type of the first audio event, the type of the first audio indicated by the first audio event, the first time segment of the first audio and / or any moment within the first time segment, track indication information regarding whether the first audio is within the main audio track of the first audio / video, and remarks. The type of the first audio event may indicate that the first audio event is an audio event automatically recognized by the device or a user-defined audio event. The type of the first audio can be automatically recognized by the electronic device 100 or input by the user; a specific example can be found in the first target type in Figure 19. The first time segment of the first audio can be a time segment on the playback progress bar of the first audio / video corresponding to the first audio. The start time / start point of the first time segment can be the moment / time point on the playback progress bar of the first audio / video corresponding to the start point of the first audio. The end time / end point of the first time segment can be the moment / time point on the playback progress bar of the first audio / video corresponding to the end point of the first audio. The length of the first time segment is the same as the duration of the first audio. The first audio file can be stored in the main audio track of the first audio / video system, or it can be left out. Optionally, some audio from the first audio file can be stored in the main audio track of the first audio / video system, while other audio can be left out. The remarks information can be manually entered by the user or determined by the electronic device 100. Examples of information for the first audio event can be found in Figures 17, 18, and 19, which show the audio event information.

[0355] Examples of displaying the identifier of the audio event and displaying the information of the audio event in S402 and S403 can be found in: Figures 5B-5C, 6A-6B, 7A-7C, 8A-8F, 9A, 9C, 10A, 10C, 11A, 11C, 14, and 16D-16E.

[0356] In some embodiments, when the electronic device 100 displays the identifier and / or information of the audio event, it may display editing controls for the first audio and video, such as audio editing controls and / or video editing controls. A specific interface example can be found in Figure 5D. In this way, the user can combine the identifier and / or information of the audio event to assist in performing editing operations such as audio editing on the first audio and video.

[0357] S404: Electronic device 100 receives user input for a first audio event.

[0358] S405: Electronic device 100 performs a first operation in response to the first audio event.

[0359] S404 and S405 are optional steps.

[0360] In some embodiments, in response to the user input shown in S404, the electronic device 100 may perform a corresponding first operation in response to a first audio event. Some examples of the first operations are shown below.

[0361] In some examples, when the electronic device 100 displays information about the first audio event, it can also display a playback control corresponding to the first audio event. This playback control is used to play the first audio indicated by the first audio event. S404 can be user input applied to the playback control. Therefore, S405 can play the first audio indicated by the first audio event for the electronic device 100. For specific implementation examples, please refer to Figures 6A-6B.

[0362] In some examples, S404 can be user input for the identifier of the first audio event, which is used to move the identifier of the first audio event from the first time segment on the playback progress bar of the first audio and video to the second time segment. Therefore, S405 can modify the audio indicated by the first audio event on the first time segment on the playback progress bar to the second audio of the second time segment on the playback progress bar. For specific implementation examples, please refer to Figures 7A-7C.

[0363] In some examples, S404 can be input by the user for any one of the information in the first audio event (which may be called the target information). Therefore, S405 can modify the target information of the first audio event for the electronic device 100. For specific implementation examples, please refer to Figures 8A-8F.

[0364] In some examples, S404 can delete the input of the first audio event for the user. Therefore, S405 can delete the first audio event for the electronic device 100. For example, the electronic device 100 can delete the information of the first audio event and / or the file of the first audio indicated by the first audio event. Optionally, if the first audio indicated by the first audio event is not stored in the main audio track of the first audio / video, the electronic device 100 can store the first audio in the main audio track of the first audio / video when deleting the first audio event to avoid audio loss. Examples of implementing the deletion of audio events can be found in Figures 9A-9C.

[0365] Not limited to the embodiment shown in FIG20, in other embodiments, the electronic device 100 may also receive user input of a first audio signal indicated by a first audio event, and in response to the user input, perform a corresponding operation on the first audio. For example, an audio editing operation may be performed on the entire first audio, as shown in FIG10B, or an audio editing operation may be performed on an audio segment of the first audio, as shown in FIG10C.

[0366] This application also provides an apparatus including a processor, a memory, and optionally a transceiver. The memory stores a computer program that runs on the processor and enables the apparatus to perform the steps performed by the electronic device 100 in the various embodiments described above.

[0367] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, can implement the steps performed by the electronic device 100 in the above embodiments.

[0368] This application also provides a computer program product, including a computing program, which, when run on a computer, enables the computer to perform the steps executed by the electronic device 100 in the above embodiments.

[0369] This application also provides a chip system, which includes a processing circuit interface circuit. The interface circuit receives code instructions and transmits them to the processing circuit. The processing circuit executes the code instructions to enable the chip system to perform the steps executed by the electronic device 100 in any embodiment of this application. The chip system can be a single chip or a chip module composed of multiple chips.

[0370] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit it. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A display method applied to an electronic device, characterized in that, include: Display a playback progress bar for the first audio and video, and display an identifier for a first audio event on the first time segment of the playback progress bar. The first audio event is used to mark the first audio on the first time segment of the playback progress bar. The first audio is a first type of audio identified by the electronic device from the audio of the first audio and video, or the first audio is determined by the electronic device based on user input. Display information about the first audio event.

2. The method as described in claim 1, characterized in that, The second time segment on the playback progress bar displays an identifier for a second audio event. The second audio event is used to mark the second audio of the second time segment on the playback progress bar. The first audio marked by the first audio event is the first type of audio recognized by the electronic device from the audio of the first audio and video. The second audio marked by the second audio event is determined by the electronic device based on user input.

3. The method as described in claim 1 or 2, characterized in that, The information of the first audio event includes one or more of the following: the name of the first audio event, the type of the first audio event, the type of the first audio, the first time period on the playback progress bar corresponding to the first audio, one or more times in the first time period, audio track indication information or remarks information, wherein the type of the first audio event includes a first event type and a second event type. When the first audio is the first type of audio identified by the electronic device from the audio of the first audio and video, the type of the first audio event is the first event type. When the first audio is determined by the electronic device according to user input, the type of the first audio event is the second event type. The audio track indication information is used to indicate whether the audio of the first audio and video includes the first audio.

4. The method according to any one of claims 1-3, characterized in that, The first audio is determined by the electronic device based on user input, and includes: The first audio is the audio from the first audio region captured by the electronic device during the first audio-visual recording process within the first time period; or, The first audio is the audio of the first time segment determined from the audio of the first audio and video based on user input after the electronic device acquires the first audio and video; or, The first audio is the audio input from the user received by the electronic device after acquiring the first audio and video.

5. The method according to any one of claims 1-4, characterized in that, The audio of the first audio / video recording includes all the audio in the first audio; or, the audio of the first audio / video recording includes a portion of the audio in the first audio; or, the audio of the first audio / video recording does not include the first audio.

6. The method according to any one of claims 1-5, characterized in that, The playback progress bar is the audio playback progress bar of the first audio and video. Displaying the playback progress bar of the first audio and video, and displaying the identifier of the first audio event on the playback progress bar during a first time period, includes: If the first audio / video is the first audio, then the audio playback progress bar of the first audio is displayed, and the identifier of the first audio event is displayed on the first time period on the audio playback progress bar of the first audio, wherein the audio playback progress bar of the first audio is used to indicate the playback progress of the first audio; If the first audio / video is a first video, then the video playback progress bar and the audio playback progress bar of the first video are displayed, and the identifier of the first audio event is displayed on the first time period of the audio playback progress bar of the first video. The video playback progress bar of the first video is used to indicate the playback progress of the images in the first video, and the audio playback progress bar of the first video is used to indicate the playback progress of the audio in the first video.

7. The method according to any one of claims 1-6, characterized in that, The information displayed for the first audio event includes: After receiving the user's input of the identifier of the first audio event, the information of the first audio event is displayed.

8. The method according to any one of claims 1-7, characterized in that, The method further includes: Receive user input for the first audio event; Perform the first operation in response to the first audio event.

9. The method as described in claim 8, characterized in that, Receiving user input on the first audio event includes: When displaying the playback control corresponding to the first audio event, receive the user's first input to the playback control; The execution of the first operation in response to the first audio event includes: In response to the first input, the first audio signal marked by the first audio event is played.

10. The method as described in claim 8, characterized in that, Receiving user input on the first audio event includes: Receive a second input from the user regarding the identifier of the first audio event, the second input being used to move the position of the identifier of the first audio event on the playback progress bar from the first time period to the third time period; The execution of the first operation in response to the first audio event includes: In response to the second input, the identifier of the first audio event is moved to the third time segment on the playback progress bar, and the audio marked by the first audio event is set to the audio of the third time segment on the playback progress bar.

11. The method as described in claim 8, characterized in that, The information of the first audio event is editable; receiving user input on the first audio event includes: Receive a third input from the user regarding the first information of the first audio event; The execution of the first operation in response to the first audio event includes: In response to the third input, the first information of the first audio event is modified.

12. The method according to any one of claims 1-11, characterized in that, The first audio is the audio from the first audio region collected by the electronic device during the first time period during the recording of the first audio and video; The method further includes: The recording interface for the first audio and video is displayed, and the recording interface includes a first control for audio tagging functionality; The system receives a fourth input from the user to the first control at the first moment, and in response to the fourth input, activates the audio tag function. At a second moment, the user receives a fifth input to the first control, and in response to the fifth input, the audio tag function is turned off, wherein the difference between the second moment and the first moment is the length of the first time period; Between the first time point and the second time point, the first audio in the first audio region is collected and stored in the audio tag track, and the third audio in the second audio region is collected and stored in the main audio track of the first audio and video. The first audio region and the second audio region are different. The main audio track of the first audio and video does not include the first audio in the audio tag track, and the audio of the first audio and video does not include the first audio.

13. The method as described in claim 12, characterized in that, The method further includes: A second control is displayed in the recording interface. The second control is used to set the audio region of the audio marked by the audio tag function. Receive the user's sixth input to the second control; In response to the sixth input, the direction and / or range of the first pitch range are set.

14. The method as described in claim 12 or 13, characterized in that, The method further includes: Displays the settings interface for the audio tag function; Receive the user's seventh input on the settings interface; In response to the seventh input, all audio of the audio marked by the audio tag function is not stored in the main audio track of the recorded audio and video, or the second type of audio of the audio marked by the audio tag function is not stored in the main audio track of the recorded audio and video.

15. The method according to any one of claims 1-14, characterized in that, The method further includes: The first interface is displayed, which includes a first category and a second category. The first category indicates a first audio scene, and the second category indicates a second audio scene. The first category includes one or more second audio and video files, and the second category includes one or more third audio and video files. The first category is determined based on the audio content in the one or more second audio and video files, and the second category is determined based on the audio content in the one or more third audio and video files. The one or more second audio and video files include the first audio and video files. The playback progress bar displaying the first audio and video includes: After receiving the user's eighth input on the first audio / video in the first category, a second interface is displayed. The second interface is used to display the first audio / video and includes the playback progress bar of the first audio / video.

16. The method as described in claim 15, characterized in that, The first classification is determined based on the audio events of the one or more second audio / video recordings, and the second classification is determined based on the audio events of the one or more third audio / video recordings.

17. The method according to any one of claims 1-16, characterized in that, The first audio and video are recorded by the electronic device through a system application.

18. An electronic device, characterized in that, It includes a processor and a memory, the memory being used to store a computer program, the processor calling the computer program to perform the steps in the method as described in any one of claims 1-17.

19. A computer storage medium, characterized in that, The computer storage medium stores a computer program, which, when executed by a processor, implements the method as described in claims 1-17.

20. A computer program product, characterized in that, Includes a computer program, which, when run on a processor, is used to implement the method as described in claims 1-17.

21. A chip system, characterized in that, It includes a processing circuit and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processing circuit, and the processing circuit is used to execute the code instructions to perform the method as described in claims 1-17.

Images