CN116546130A - Multimedia data control method, device, terminal and storage medium - Google Patents

Multimedia data control method, device, terminal and storage medium Download PDF

Info

Publication number
CN116546130A
CN116546130A CN202210095172.6A CN202210095172A CN116546130A CN 116546130 A CN116546130 A CN 116546130A CN 202210095172 A CN202210095172 A CN 202210095172A CN 116546130 A CN116546130 A CN 116546130A
Authority
CN
China
Prior art keywords
application
user interface
multimedia recording
recording data
capture
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202210095172.6A
Other languages
Chinese (zh)
Inventor
王绪四
梁小容
林小燕
刘洋
郑培升
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Samsung Guangzhou Mobile R&D Center
Samsung Electronics Co Ltd
Original Assignee
Samsung Guangzhou Mobile R&D Center
Samsung Electronics Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Samsung Guangzhou Mobile R&D Center, Samsung Electronics Co Ltd filed Critical Samsung Guangzhou Mobile R&D Center
Priority to CN202210095172.6A priority Critical patent/CN116546130A/en
Publication of CN116546130A publication Critical patent/CN116546130A/en
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/7243—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages
    • H04M1/72433—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages for voice messaging, e.g. dictaphones
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/7243—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages
    • H04M1/72439—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages for image or video messaging
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72469—User interfaces specially adapted for cordless or mobile telephones for operating the device by selecting functions from two or more displayed items, e.g. menus or icons

Landscapes

  • Engineering & Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Multimedia (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

The disclosure relates to a multimedia data control method, a device, a terminal and a storage medium. The method comprises the following steps: providing at least one application with a user interface element for controlling capturing of multimedia recording data when the at least one application is in a multimedia recording state, wherein one user interface element corresponds to one application; in response to a user operation on the user interface element, controlling an application corresponding to the user interface element to capture or not capture the multimedia recording data. By adopting the method, a user can control a certain/some/all of the corresponding applications to capture the multimedia recording data according to the needs, or control a certain/some/all of the corresponding applications to not capture the multimedia recording data, so that more control requirements of the user can be met, and control and state switching can be realized only by operating user interface elements, and the multimedia recording state of the application is not required to be started or closed by operation, or the application is switched to a foreground or a background, so that the convenience of operation can be improved.

Description

Multimedia data control method, device, terminal and storage medium
Technical Field
The present disclosure relates to the field of electronic technologies, and in particular, to a method, an apparatus, a terminal, and a storage medium for controlling multimedia data.
Background
With the development of electronic technology, the development of new demands of users for more and more communication functions of terminals such as mobile phones, tablet computers, etc., for example, live broadcasting, games, online conferences, etc., and more applications (Application, APP) are also provided to meet these demands. These demands often require interactive communication between users, and users often require the use of voice communication functions or video communication functions of the terminal through applications.
The terminal makes a corresponding restriction on the application-based voice communication function or the video communication function in consideration of privacy sensitivity of communication. For example, when a user communicates using a voice communication function that is indispensable in a terminal, a recording function to the terminal is required. For the requirement of single application recording, a terminal system (such as an Android system) can be generally supported; for recording requirements of multiple applications, conventional terminals only support a manner of switching recording among the multiple applications running with a set priority scheme.
In implementing the solution of the present disclosure, the inventor finds that the conventional recording control solution of the general application (or the common application) has at least the following problems: only a single application is supported to capture audio recording data at the same time; and the priority switching mode is complex: the state switching may be implemented by changing the priority of the application by starting the recording state of the application or stopping the recording state of the application, or switching the application to the foreground or background. Similar problems exist with conventional video control schemes.
Disclosure of Invention
According to certain exemplary embodiments of the present disclosure, a dialog generation method and dialog generation device are provided to address at least the above-mentioned problems.
According to a first aspect of certain exemplary embodiments of the present disclosure, there is provided a multimedia data control method, the method comprising: providing at least one application with a user interface element for controlling capturing of multimedia recording data when the at least one application is in a multimedia recording state, wherein one user interface element corresponds to one application; in response to a user operation on the user interface element, controlling an application corresponding to the user interface element to capture or not capture the multimedia recording data.
Optionally, the capturing or not capturing the multimedia recording data by the application corresponding to the control user interface element includes: when the application is controlled by the user interface element to not capture the multimedia recording data, the multimedia recording state of the application which does not capture the multimedia recording data is not exited; and/or, when the application is controlled to capture the multimedia recording data through the user interface element, a plurality of applications are supported to capture the multimedia recording data simultaneously.
Optionally, the user interface element includes a user interface control having an identification of the corresponding application.
Optionally, the above-mentioned identification includes an icon pattern of the corresponding application.
Optionally, the above-mentioned user interface element is further configured to present state information of the corresponding application, where the state information includes information that the corresponding application is in a state of capturing or not capturing the multimedia recording data and/or information that the captured or not captured state information of the application is set by a system or by a user operation.
Optionally, the user interface elements present different status information in different display manners.
Optionally, the different display modes include one or a combination of displaying in different subareas, displaying in different brightness degrees, displaying in different sizes, displaying in different colors and adding different identifications.
Optionally, the user interface elements described above are provided in a notification bar.
Alternatively, an application that is controlled to capture multimedia recording data in response to a user operation does not preempt other applications to exit the capture state unless controlled again by the user operation to not capture multimedia recording data or to exit the multimedia recording state in response to an exit event.
Optionally, the method further comprises: when the preset application captures multimedia recording data, the application controlled to capture the multimedia recording data in response to a user operation maintains a capturing state of the multimedia recording data.
Optionally, the preset application is an application with a highest system priority for capturing multimedia recording data.
Optionally, the multimedia recording data includes audio and/or video data collected by the multimedia component.
According to a second aspect of certain exemplary embodiments of the present disclosure, there is provided a multimedia data control apparatus, the apparatus comprising: an element providing module configured to provide at least one application with a user interface element for controlling capturing of multimedia recording data when the at least one application is in a multimedia recording state, wherein one user interface element corresponds to one application; and the control module is configured to respond to the user operation of the user interface element and control the application corresponding to the user interface element to capture or not capture the multimedia recording data.
Optionally, the control module is configured to control, through the user interface element, the application not to capture the multimedia recording data, without exiting the multimedia recording state of the application not capturing the multimedia recording data; and/or the control module is configured to support a plurality of applications to capture the multimedia recording data simultaneously when the application captures the multimedia recording data through the user interface element control.
Optionally, the user interface element includes a user interface control having an identification of the corresponding application.
Optionally, the above-mentioned identification includes an icon pattern of the corresponding application.
Optionally, the above-mentioned user interface element is further configured to present state information of the corresponding application, where the state information includes information that the corresponding application is in a state of capturing or not capturing the multimedia recording data and/or information that the captured or not captured state information of the application is set by a system or by a user operation.
Optionally, the user interface elements present different status information in different display manners.
Optionally, the different display modes include one or a combination of displaying in different subareas, displaying in different brightness degrees, displaying in different sizes, displaying in different colors and adding different identifications.
Optionally, the user interface elements described above are provided in a notification bar.
Alternatively, an application that is controlled to capture multimedia recording data in response to a user operation does not preempt other applications to exit the capture state unless controlled again by the user operation to not capture multimedia recording data or to exit the multimedia recording state in response to an exit event.
Optionally, the control module is further configured to maintain a capture state of the multimedia recording data in response to the user operation of the application controlled to capture the multimedia recording data when the preset application captures the multimedia recording data.
Optionally, the preset application is an application with a highest system priority for capturing multimedia recording data.
Optionally, the multimedia recording data includes audio and/or video data collected by the multimedia component.
According to a third aspect of certain exemplary embodiments of the present disclosure, there is provided a terminal comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the method for controlling multimedia data of the present disclosure when the computer program is executed.
According to a fourth aspect of certain exemplary embodiments of the present disclosure, there is provided a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the multimedia data control method of the present disclosure.
According to the multimedia data control method, device, terminal and storage medium, as at least one application is in the multimedia recording state, a user interface element for controlling capturing of multimedia recording data is provided for the at least one application, wherein one user interface element corresponds to one application, and the application corresponding to the user interface element is controlled to capture or not capture the multimedia recording data in response to user operation of the user interface element, so that a user can control some/all of the applications in the multimedia recording state to capture the multimedia recording data as required, can also control some/all of the applications in the multimedia recording state not to capture the multimedia recording data, can meet more control requirements of the user, can realize control and state switching only by operating the user interface element, does not need to operate the multimedia recording state of starting or closing the application, or switches the application to the foreground or the background, and can improve convenience of operation.
Drawings
The foregoing and other objects and features of certain exemplary embodiments of the present disclosure will become more apparent from the following description taken in conjunction with the accompanying drawings which illustrate the embodiments by way of example, in which:
FIG. 1 is a block diagram of a terminal in some exemplary embodiments;
fig. 2 is a flow chart of a method of controlling multimedia data in some exemplary embodiments;
FIG. 3 is a schematic diagram of providing user interface elements at a notification bar in some demonstrative embodiments;
FIG. 4 is an interface schematic diagram of a set "designated application uses microphone" switch in some exemplary embodiments;
FIG. 5 is a flow chart of a method of controlling multimedia data in some other exemplary embodiments;
FIG. 6 is a diagram of an interface diagram of a notification bar in some example embodiments;
FIG. 7 is a second interface diagram of a notification bar in some demonstrative embodiments;
FIG. 8 is a diagram of an interface diagram III of a notification bar in some exemplary embodiments;
FIG. 9 is a diagram of an interface fourth of a notification bar in some demonstrative embodiments;
FIG. 10 is a schematic diagram of a user interaction process in certain exemplary embodiments;
FIG. 11 is a schematic diagram of a user interaction process in some further exemplary embodiments;
fig. 12 is a block diagram of a multimedia data control apparatus in some embodiments.
Detailed Description
The following detailed description is provided to assist the reader in obtaining a thorough understanding of the methods, apparatus, terminals and/or storage media described herein. However, various changes, modifications and equivalents of the methods, apparatus, terminals and/or storage media described herein will be apparent after understanding the present disclosure. For example, the order of operations described herein is merely an example and is not limited to those set forth herein, but may be altered as will be apparent after an understanding of the disclosure of the present application, except for operations that must occur in a particular order. Furthermore, descriptions of features known in the art may be omitted for clarity and conciseness.
The features described herein may be embodied in different forms and should not be construed as limited to the examples described herein. Rather, the examples described herein have been provided to illustrate only some of the many possible ways to implement the methods, terminals, and/or storage media described herein, many of which will be apparent after an understanding of the present disclosure.
The terminology used herein is for the purpose of describing various examples only and is not intended to be limiting of the disclosure. Singular forms also are intended to include plural forms unless the context clearly indicates otherwise. The terms "comprises," "comprising," and "having" specify the presence of stated features, amounts, operations, components, elements, and/or combinations thereof, but do not preclude the presence or addition of one or more other features, amounts, operations, components, elements, and/or combinations thereof. Unless otherwise indicated, "/" means or, e.g., A/B may represent A or B; the text "and/or" is merely an association relation describing the associated object, and indicates that three relations may exist, for example, a and/or B may indicate: the three cases where a exists alone, a and B exist together, and B exists alone, and furthermore, in the description of the embodiments of the present invention, "plural" means two or more than two.
Unless defined otherwise, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs after understanding this disclosure. Unless explicitly so defined herein, terms (such as those defined in a general dictionary) should be construed to have meanings consistent with their meanings in the context of the relevant art and the present disclosure, and should not be interpreted idealized or overly formal.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the foregoing figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the disclosure described herein may be capable of operation in sequences other than those illustrated or described herein. The implementations described in certain exemplary embodiments below are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.
In addition, in the description of the examples, when it is considered that detailed descriptions of well-known related structures or functions will cause a ambiguous explanation of the present disclosure, such detailed descriptions will be omitted.
Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. However, the embodiments may be implemented in various forms and are not limited to the examples described herein.
In order to facilitate understanding of the solution of the exemplary embodiment of the present disclosure, the following first takes an Android system-based recording function as an example, to describe the problems existing in the conventional technology. At present, equipment based on an Android system is very wide, and a plurality of users live broadcast, games, online conferences and the like through the Android equipment, and voice serving as one of main media of interaction communication is an indispensable function. When users communicate through the Android device, the recording function is needed, and when a single application is recorded, the Android system can be supported in a friendly mode, and the user requirements are basically met. However, when a plurality of applications are switched to record, the Android system (described by Android R OS and Android S OS) adopts a priority scheme to switch the input audio stream between the running applications. Applications focused and used by users are basically common applications (the following description is directed to common applications as well, and the applications described below refer to common applications unless otherwise specified), such as voice communication programs (e.g., "WeChat", "QQ", etc.), live applications (e.g., "tiger", "fighting fish", etc.), and game applications (e.g., "peaceful elite", etc.), etc.
In the Android R OS, for recording of multiple common applications, when multiple applications are in a recording state at the same time, only one application receives audio, and other applications are in a mute state. I.e. two common applications cannot capture audio at the same time. Generally, if none of the plurality of recording applications (applications in a recording state, i.e., applications in an audio recording state) has privacy sensitivity, audio is received by the application at the top of the interface. If none of the plurality of recording applications has a display interface, audio is received by the application that later begins recording. Wherein the privacy sensitivity of the recording application is determined by the audio source used, for example: the audio sources used for WeChat VOICE calls, QQ VOICE calls, game VOICEs of some game applications (such as "peaceful elite") and the like are VOICE_COMMUNICATION (7), which belongs to privacy sensitive audio sources, while the audio sources used for some live applications (such as "tiger teeth", "fighting fish" and the like) are MIC (1), which belongs to non-privacy sensitive audio sources. If one of the recording applications has privacy sensitivity, the recording application receives audio, and the other applications are in a mute state even if the interface in the recording application which is not privacy sensitive is positioned at the top or the capturing is started later. It is true that applications with privacy sensitivity have a higher priority than applications with non-privacy sensitivity. If there are multiple recording applications that are privacy sensitive, audio is received by the application with the interface on top. If both are in the background, audio is received by an application that begins recording later. The other applications are in a mute state.
The priority determinants mainly include the following two aspects:
1) Privacy sensitive audio sources such as camera video (CAMCORDER) and VOICE over WeChat (VOICE_ COMMUNICATION, voIP) are provided.
2) Whether top (or top layer) or later.
The latest operating system of Android is Android S OS at present. The Android S OS and the Android R OS are almost consistent in basic strategies and rules related to audio input. However, the Android S OS supplements the priority that the normal application allows to use the microphone, and adds an attribute value of "Audio mode wner", and the application with the attribute will have the highest priority to use the microphone, specifically as follows:
priority determining factors of microphones:
android R OS: privacy sensitivity > TOP > Latest, i.e., prioritizing whether there is privacy sensitivity, then considering whether it is on TOP, and finally considering whether it is the Latest onset of capturing audio.
Android S OS: audio mode owner > privacy sensitivity > TOP > Latest, i.e., prioritizing whether the attribute value is added: "Audio mode wner" again considers whether there is privacy sensitivity, then considers whether it is on top, and finally considers whether it is the latest onset of capturing Audio.
By applying control scheme analysis to conventional recordings, two disadvantages of conventional techniques are found: first, only a single application is supported to capture audio recording data; secondly, the priority switching mode is complex: the multiple recording applications need to change the priority of the recording application by starting recording or stopping recording or switching the recording application to the foreground or background.
The multimedia data control method provided by the disclosure can be applied to a terminal, and the terminal can be any terminal equipment such as a mobile phone, a tablet computer, a notebook computer, a desktop computer, a PDA (Personal Digital Assistant ), a POS (Point of sales), a vehicle-mounted computer, a wearable device and the like. In one embodiment, as shown in FIG. 1, a terminal is provided that includes a processor, memory, a display screen, and an input device connected by a system bus. Wherein the processor may comprise one or more processing units. The processor may be a CPU (Central Processing Unit ) or DSP (Digital Signal Processing, digital signal processor), etc. The memory may include a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The computer program may be executable by a processor for implementing a multimedia data control method provided by certain exemplary embodiments below. The internal memory provides a cached operating environment for operating system computer programs in the non-volatile storage medium. The display screen of the terminal can be a liquid crystal display screen or an electronic ink display screen, the input device of the terminal can be a touch layer covered on the display screen, can be a key, a track ball or a touch pad arranged on a terminal shell, and can also be an external keyboard, a touch pad or a mouse and the like.
It will be appreciated by those skilled in the art that the structure shown in fig. 1 is merely a block diagram of a portion of the structure associated with the disclosed aspects and is not limiting of the terminal to which the disclosed aspects may be applied, and that a particular terminal may include more or fewer components than shown, or may combine certain components, or may have a different arrangement of components.
In one embodiment, as shown in fig. 2, a multimedia data control method is provided, and the method is applied to the terminal in fig. 1 for illustration, and includes the following steps:
step 202, when at least one application is in a multimedia recording state, providing a user interface element for controlling capturing of multimedia recording data for the at least one application, wherein one of the user interface elements corresponds to one of the applications.
Here, the multimedia may be audio and video, and for the case that the multimedia is audio, the multimedia recording state herein may refer to an audio recording state, that is, a recording state; in the case that the multimedia is video, the multimedia recording status herein may refer to a video recording status, that is, a video recording status. In certain exemplary embodiments of the present disclosure, the multimedia recording data herein may include audio data and/or video data collected by a multimedia component. Here, the multimedia component may include an audio component (e.g., a microphone) and/or a video component (e.g., a camera).
Here, the user interface element may include a user interface control corresponding to an application in a multimedia recording state. To facilitate a user in distinguishing between user interface elements of different applications, in certain exemplary embodiments of the present disclosure, the user interface elements may include user interface controls having identifications of the corresponding applications. Here, the identification may be text, graphics, or any combination thereof. Accordingly, the user interface element may include user interface controls composed of text, graphics, or any combination thereof that distinguish between different applications, e.g., the user interface controls may include controls composed of text, controls composed of graphics, or any combination of text and graphics. To promote intuitiveness for user recognition, in certain exemplary embodiments of the present disclosure, the identification may include an icon pattern of a corresponding application, and accordingly, the user interface element may include a user interface control having an icon pattern of a corresponding application.
Here, the user interface element and the application in the multimedia recording state are in one-to-one correspondence. When the number of applications is one or more, the user interface element is also correspondingly one or more.
In particular, the terminal may provide at least one application with a user interface element for controlling capturing of multimedia recording data and corresponding to the at least one application one-to-one when the at least one application is in a multimedia recording state. In certain exemplary embodiments of the present disclosure, the user interface element may be provided in a preset user interface. As a non-limiting example, the user interface may be displayed by at least one of: a user interface is displayed in a floating mode in a card form; a user interface is displayed in a split screen mode; shrinking the call window and displaying the user interface on a screen with a preset proportion; displaying a user interface in a notification bar mode; the user interface is displayed in a message pop-up manner. In some exemplary embodiments of the present disclosure, the user interface element may be provided in a notification bar that, on the one hand, facilitates user operation and, on the other hand, does not contend with or obscure the display area of the display interface of the corresponding application.
For example, as shown in FIG. 3, the user interface element 322 may be provided in a notification bar 320. In some exemplary embodiments of the present disclosure, one or more visual cues 324 may also be provided in the notification bar 320 that prompt the user to manipulate the user interface element 322 to control whether the corresponding application captures or does not capture multimedia recording data. The one or more visual cues 324 may provide cues or reminders to the user of the control action. The visual cues may be text, graphics, or any combination thereof. Taking control of audio data as an example, the visual cue 324 may be "microphone in use" in fig. 3. You can click on the application to turn off the microphone. "
In step 204, in response to a user operation on the user interface element, the application corresponding to the user interface element is controlled to capture or not capture the multimedia recording data.
Here, the user operation may be a touch operation on the user interface element by a user touching a touch layer covered on a display screen of the terminal, or an operation on the user interface element by a user manipulating an input device of the terminal such as a keyboard, a touch pad, or a mouse. The touch operation may be any one of a click operation, a slide operation, a press operation, and the like.
Here, the control of capturing or not capturing the multimedia recording data by the application corresponding to the user interface element may be control of capturing the multimedia recording data by the application corresponding to all the user interface elements, may control not capturing the multimedia recording data by the application corresponding to all the user interface elements, may control capturing the multimedia recording data by the application corresponding to some of the user interface elements, and control not capturing the multimedia recording data by the application corresponding to the rest of the user interface elements.
Here, controlling the corresponding application to capture the multimedia recording data may mean that the corresponding application is allowed to use the multimedia component, and similarly controlling the corresponding application not to capture the multimedia recording data may mean that the corresponding application is prohibited from using the multimedia component. For example, taking control of audio data as an example, controlling a corresponding application to capture audio data may refer to the corresponding application being allowed to use a microphone, controlling the corresponding application not to capture audio data, may refer to the corresponding application being prohibited from using the microphone (otherwise referred to as turning off its microphone).
Specifically, the terminal may monitor a user operation on the user interface element, and after the user operation is monitored, control the application corresponding to the user interface element to capture or not capture the multimedia recording data in response to the user operation.
In some exemplary embodiments of the present disclosure, the controlling the application corresponding to the user interface element to capture or not capture the multimedia recording data may include: and controlling the application not to capture the multimedia recording data through the user interface element, and not exiting the multimedia recording state of the application not capturing the multimedia recording data. Therefore, when a user controls an application to not capture the multimedia recording data, the mute aim is achieved at the user side, the other party communicating with the user does not feel, and the quick switching can be performed when the multimedia recording data is required to be captured.
In some exemplary embodiments of the present disclosure, the controlling the application corresponding to the user interface element to capture or not capture the multimedia recording data may include: when the user interface element controls the application to capture the multimedia recording data, a plurality of applications are supported to capture the multimedia recording data simultaneously. Thus, the user can designate one or more applications to capture the multimedia recording data simultaneously with the application currently capturing the multimedia recording data according to the requirements, and the user requirements in more scenes can be met.
In the above method for controlling multimedia data, since at least one application is in a multimedia recording state, a user interface element for controlling capturing of multimedia recording data is provided for the at least one application, where one user interface element corresponds to one application, and because the application corresponding to the user interface element is controlled to capture or not capture the multimedia recording data in response to a user operation on the user interface element, a user can control some/all of the applications in the multimedia recording state to capture the multimedia recording data as required, or control some/all of the applications in the multimedia recording state not to capture the multimedia recording data, so that more control requirements of the user can be satisfied, and control and state switching can be realized only by operating the user interface element, starting or closing of the multimedia recording state of the application is not required, or switching the application to a foreground or a background is required, and convenience of operation can be improved. Meanwhile, the application which is capturing the multimedia recording data does not need to be closed or switched to the background, and the other application can capture the multimedia recording data through the user operation, so that the influence on the application which is currently being used can be reduced.
In certain exemplary embodiments of the present disclosure, the above-described user interface element may also be used to present state information of a corresponding application, including information (hereinafter referred to as first state information) of whether the corresponding application is in a state of capturing or not capturing multimedia recording data and/or information (hereinafter referred to as second state information) of whether the captured or not captured state information of the application is set by a system or by a user operation. That is, the user interface element may present the first state information alone, the second state information alone, and both the first state information and the second state information. In this way, the user can learn the state information of the corresponding application from the user interface element.
In certain exemplary embodiments of the present disclosure, the above-described user interface elements may present different status information in different display manners. As non-limiting examples, the different display modes may include one or a combination of modes of displaying in different sub-areas, displaying in different levels of darkness, displaying in different sizes, displaying in different colors, and adding different logos.
To present the first state information, illustrate:
In one mode, the user interface element corresponding to the application capturing the multimedia recording data and the user interface element corresponding to the application not capturing the multimedia recording data can be displayed in different sub-areas.
For example, a user interface element corresponding to an application capturing multimedia recording data is displayed in an upper area (referred to as a sub-area) of a preset user interface, and a user interface element corresponding to an application not capturing multimedia recording data is displayed in a lower area (referred to as another sub-area) of the preset user interface.
Displaying user interface elements corresponding to applications capturing the multimedia recording data and user interface elements corresponding to applications not capturing the multimedia recording data in different brightness degrees;
for example, a user interface element corresponding to an application capturing multimedia recording data is displayed as a "bright" user interface element; the user interface element corresponding to the application that does not capture the multimedia recording data is displayed as a "dark" user interface element. It should be noted that "bright" and "dark" may refer to relative shades.
And in a third mode, displaying user interface elements corresponding to applications capturing the multimedia recording data and user interface elements corresponding to applications not capturing the multimedia recording data in different sizes.
For example, a user interface element corresponding to an application capturing multimedia recording data is displayed as a "large" user interface element; displaying user interface elements corresponding to applications that do not capture multimedia recording data as "small" user interface elements; it should be noted that "large" and "small" refer to relative sizes.
And fourthly, displaying the user interface elements corresponding to the applications capturing the multimedia recording data and the user interface elements corresponding to the applications not capturing the multimedia recording data in different colors.
For example, displaying a user interface element corresponding to an application capturing multimedia recording data as a first color; and displaying the user interface element corresponding to the application which does not capture the multimedia recording data as a second color.
In a fifth mode, different identifications are added for user interface elements corresponding to applications capturing multimedia recording data and user interface elements corresponding to applications not capturing multimedia recording data. The different identifiers herein may be text, graphics, or any combination thereof. The identification may be added on or around the user interface element.
For example, a "allow capture" identifier is added for a user interface element corresponding to an application that captures multimedia recording data, and a "mute" identifier is added for a user interface element corresponding to an application that does not capture multimedia recording data. In addition, the identification information is not added, and may be considered as an identification, for example, only the "capture permission" identification is added to the user interface element corresponding to the application capturing the multimedia recording data, and then the application corresponding to the user interface element to which the "capture permission" identification is not added defaults to the application not capturing the multimedia recording data.
It should be understood by those skilled in the art that the manner of distinguishing the display is not limited to the above five manners, and may be a combination of a plurality of manners of distinguishing the display, for example, the above-described manner one and the above-described manner two. In addition, it should be understood by those skilled in the art that the second state information may be presented in one of the above five manners or in a combination of the above five manners, which is not described herein. The number and/or variety of ways of presenting the first state information and the second state information may be the same or different.
Furthermore, all or part of the above-mentioned user interface elements may present the first state information and/or the second state information. It is considered that an application in a state of capturing multimedia recording data, which is often of greater concern to a general user, is set by a system or by a user operation, and an application in a state of not capturing multimedia recording data, which is often of lesser concern, is set by a system or by a user operation. In certain exemplary embodiments of the present disclosure, the second state information may be presented only to the application in a state in which the multimedia recording data is captured, so that presentation information of a portion of the user interface elements may be simplified.
In certain exemplary embodiments of the present disclosure, the capture state may be exited without being preempted by other applications at an application that is controlled to capture multimedia recording data in response to a user operation unless controlled again by the user operation to not capture multimedia recording data or to exit the multimedia recording state in response to an exit event. In this way, it is possible to make the application for capturing the multimedia recording data set by the user operation, always maintain the capturing state, and the capturing state is not preempted by other applications unless the user operates the application for setting it as an application for not capturing the multimedia recording data or exits the multimedia recording state of the application.
In certain exemplary embodiments of the present disclosure, the above-described method may further comprise: when the preset application captures multimedia recording data, the application controlled to capture the multimedia recording data in response to a user operation maintains a capturing state of the multimedia recording data.
Here, the preset application may be an application for capturing multimedia recording data set by the system, for example, the preset application is an application having the highest system priority for capturing multimedia recording data. In some exemplary embodiments, the preset application may share the multimedia recording data with an application for capturing the multimedia recording data set by a user operation, but may not cause the application for capturing the multimedia recording data set by the user operation to exit the capturing state.
It is considered that there is a need to use a conventional multimedia data control scheme in a part of the scene, i.e., a scheme of determining by which application to capture multimedia recording data based on a set priority rule. In order to meet the needs of multiple aspects of users, a switch can be arranged on a setting interface, a user can start a designated application to use the multimedia component function according to needs, when the designated application uses the multimedia component function to be in an on state, the scheme of certain exemplary embodiments of the present disclosure is adopted to control multimedia data, and when the designated application uses the multimedia component function to be in an off state, a traditional multimedia recording control scheme is adopted to control multimedia data. Taking control of audio data as an example, a switch for "designating application use microphone" may be provided at the setting interface as shown in fig. 4. The scheme of certain exemplary embodiments of the present disclosure is employed for audio data control when the "designated application uses microphone" is in an on state, and conventional audio data control schemes are employed for audio data control when the "designated application uses microphone" is in an off state.
In an exemplary embodiment of the present disclosure, a multimedia data control method is provided. The exemplary embodiment is described taking the above-mentioned preset application as an application having the highest system priority for capturing multimedia recording data as an example. As shown in fig. 5, the multimedia data control method may include the steps of:
Step 502 provides a user interface element for controlling capturing of multimedia recording data for an application in a first application list, which is a list of applications in a multimedia recording state.
Step 504, monitor the trigger event of updating the first application list, and when any trigger event is monitored, go to step 506.
In general, when an application in a multimedia recording state is added or reduced, or when the state of the application in the multimedia recording state changes, a trigger event for updating the application to use the multimedia component is generated. The conventional multimedia data control scheme generally monitors the following two types of events:
1) The first type of event is an event that starts or stops the multimedia recording state of the application, for example, an event that starts the multimedia recording state of the application a, or an event that stops the multimedia recording state of the application B.
2) The second type of event is an event that switches an application currently in a multimedia recording state to the foreground or the background, for example, an event that switches application C from the foreground to the background or an event that switches application D from the background to the foreground is an application currently in a multimedia recording state.
After the multimedia data control method disclosed by the disclosure is adopted, the triggering event can further comprise the following third type of event:
3) The third type of event is an event in which capturing or not capturing of the multimedia recording data is set by a user operation, that is, an event generated by performing a user operation on the above-mentioned user interface element. For example, the application E and the application F are both applications in a multimedia recording state, and may be an event in which a user operates an application that sets the application E as an application that captures multimedia recording data, or an event in which a user operates an application that sets the application F as an application that does not capture multimedia recording data.
Taking audio data control as an example, the triggering event may include: an event that starts an audio recording state of an application, an event that stops an audio recording state of an application, an event that switches a recording application to a foreground, an event that switches a recording application to a background, an event that a user operation sets an application to an application that captures audio data, and an event that a user operation sets an application to an application that does not capture audio data.
Step 506, updating the first application list and the state information of the corresponding application in the first application list, and proceeding to step 508 and step 512.
Here, the state information of the corresponding application may include information whether the corresponding application is in a state of capturing or not capturing multimedia recording data and/or whether the captured or not captured state information of the application is set by a system or by a user operation.
Step 508 determines a second list of applications that are user-specified applications that capture or not capture multimedia recording data.
Specifically, the second application list may be determined according to the first application list and state information of the corresponding application therein. For example, the applications in the first application list are application 1, application 2, application 3, application 4, and application 5. In the case that the user has not designated that the application captures or does not capture the multimedia recording data, the triggering event of this time is that the user designates (i.e. is set by the user operation) that the application 3 captures the multimedia recording data, the second application list includes the application 3. If the next trigger event user specifies that application 4 does not capture the multimedia recording data again, the second application list includes application 3 and application 4.
Step 510, control the application in the second application list to capture or not capture the multimedia recording data, and after successful control, go to step 518.
Specifically, the terminal may control the application corresponding to the user interface element to capture or not capture the multimedia recording data in response to a user operation on the user interface element.
Step 512, determining a third application list, which is a list of applications in the first application list except for the application specified by the user and not capturing the multimedia recording data, and proceeding to step 514.
Wherein it is considered that there is a case where the user does not designate an application that does not capture the multimedia recording data, and in this case, the third application list is identical to the first application list. There are also cases where the user designates all applications in the first application list as applications that do not capture multimedia recording data. In this case, the third application list is empty and step 514 may not be entered.
Step 514, judging the priority of each application in the third application list according to the set priority rule, and determining the application with the highest system priority for capturing the multimedia recording data;
step 516, the application determined in step 514 captures the multimedia recording data, and after successful control, step 518 is entered;
and 518, updating the user interface elements corresponding to the applications in the first application list.
Here, updating the user interface element may be adding or subtracting the user interface element, or may change the state information of the corresponding application presented by the user interface element.
Hereinafter, a multimedia data control method of an exemplary embodiment of the present disclosure will be described in detail taking the above audio data as an example. In this case, the above-described application in the multimedia recording state is referred to as a recording application in the following description.
In operation, displaying a user interface element of the sound recording application in an area corresponding to the position of the notification bar, wherein the user interface element of the sound recording application in an upper area of the area is in a bright state, which indicates that the application is using the microphone, i.e. in a state of capturing audio data of the microphone (corresponding to the audio recording data described above); the user interface element of the audio recording application in the lower region of the region is marked as a "dark" state, indicating that this application is in a state in which audio data of the microphone is not captured. By clicking on the user interface element of the recording application, the state of the user interface element may change, e.g. "bright" < = > "dark", and the position may change accordingly, e.g. switch from the upper region of the region to the lower region of the region.
The following description will take the recording application as application 1, application 2, and application 3 in fig. 6 to 9 as an example. For example, application 1, application 2, and application 3 may be "QQ", "WeChat", and "peaceful elite", respectively. As shown in fig. 6, in the notification bar, the user is not set, the application 1 of the highest system priority is capturing audio data of the microphone, the user interface element corresponding to the application 1 is displayed in the upper area of the area, and the status display "system selection" (corresponding to one of the above second status information); application 2 and application 3 are not capturing audio data of the microphone, and user interface elements corresponding to application 2 and application 3 are displayed in a lower region of the region.
As shown in fig. 7, the user clicks on the user interface element of the application 3, the application 1 of the highest system priority is using the microphone, the status display "system select" is capturing audio data of the microphone, the status display "user select" (corresponding to another of the above-described second status information), and the user interface elements corresponding to the application 1 and the application 3 are displayed in the upper area of the area; application 2 is not capturing audio data of the microphone and the user interface element corresponding to application 2 is displayed in the lower region of the region.
As in fig. 8, the user then clicks on the user interface element of application 2, application 1 of the highest system priority is using the microphone, status displays "system select", application 2 and application 3 are capturing audio data of the microphone, status displays "user select". User interface elements of application 1, application 2, and application 3 are displayed in the upper region of the area. When all recording applications are in a state of capturing audio data of the microphone, a lower region of the region is not displayed to save a display region.
As shown in fig. 9, after all the recording applications are in a state of not capturing audio data of the microphone, an upper region of the region is not displayed to save a display region.
In order to facilitate understanding of aspects of exemplary embodiments of the present disclosure and their benefits, the following description is made by way of two specific examples.
Example one (Voice live broadcast scene)
Before the embodiment of the disclosure is adopted, the user A is used as a host, and voice live broadcast is often required to be carried out on the live broadcast application A and the live broadcast application B through mobile phones. However, when live broadcasting is performed by using the Android mobile phone, the user a finds that voice output cannot be performed on the live broadcasting application a and the live broadcasting application B at the same time, and only one live broadcasting application (for example, the live broadcasting application a) can enter the other live broadcasting application (for example, the live broadcasting application B) after live broadcasting is finished, so that the workload of the user a can be increased. Or, people and objects are sometimes seen, suddenly feel and want to share in time, and only can be selected and replaced in the live broadcast application A and the live broadcast application B.
After the scheme of the exemplary embodiment of the present disclosure is adopted, when the user a needs to live voice, the live broadcast application a and the live broadcast application B are opened, and when the application recording is monitored, the user interface element of the application currently using the recording (i.e., currently in the audio recording state) is displayed in the notification bar, and after the user a selects the live broadcast application a and the live broadcast application B which need to be shared by the recording, the vermicelli of the live broadcast application a and the live broadcast application B can hear the sound of the user a.
Specifically, after the user a opens the switch for designating the microphone to be used by the application, as shown in fig. 10, if the user opens the live application a, and then displays the user interface element of the current recording application in the notification bar, as shown in the list 1002, only the single application (i.e., the live application a) is currently in a state of capturing the audio data collected by the microphone, and only the user interface element of the live application a is displayed at this time. After the user reopens the live application B, user interface elements of the live application a and the live application B are displayed in the notification bar, as shown in the list 1004, and the user interface elements present that the live application a and the live application B are in an audio recording state. Live application B is on top (or later recorded), with higher priority, in a state of capturing audio data collected by the microphone; the live application a is in a state where audio data collected by the microphone is not captured.
And switching to the voice live broadcast of the live broadcast application A again, wherein the live broadcast application A is a foreground application. As shown in list 1006, live application a and live application B are shown in the notification bar in an audio recording state. The live broadcast application A is positioned at the top and has higher priority, and is in a state of capturing audio data acquired by the microphone; the live application B is in a state where the audio data collected by the microphone is not captured. At the notification bar, the user may set the application to capture or not capture audio data captured by the microphone by clicking on a user interface element of the recording application.
For example: the user clicks the live application B, and the live application B is designated as a recording application for capturing audio data collected by the microphone. In response to the user's operation, the user sets the live application B as a recording application capturing audio data collected by the microphone through the notification bar, at this time, as shown in the list 1008, the live application B can receive the audio data collected by the microphone, and since the live application B is allowed to use the microphone through the user's setting, the identification state under the application icon of the live application B is "user selection". The live broadcast application A is a recording application with the highest system priority at present and is also in a state of capturing audio data collected by a microphone, and the identification state below an application icon is "system selection".
Example two (immersive game voice experience scene)
Before adopting the embodiment of the disclosure, the user B enjoys playing the hand tour when resting, but sometimes has the need to play the hand tour and conduct voice communication, for example, communication through QQ/WeChat voice. For example, when user B plays a certain game, user C utters "QQ"/"WeChat" to user B, and after user B turns on "QQ"/"WeChat" voice, other game players (e.g., user D and user E) in voice communication with user B cannot hear the voice of user B. And when user B cuts back to the game application, user C is found to be inaudible to his own voice.
After the embodiment of the disclosure is adopted, after a user B starts a game voice of a certain game application and a certain voice communication application (for example, QQ/WeChat) voice, when the user B needs to communicate with a teammate of a game, the user B pulls down a notification bar, provides a user interface element corresponding to a current recording application in the notification bar, and when the user B hopes that other game players can hear own voice, the user B can operate the voice communication application and/or the user interface element corresponding to the game application and switch to the audio data acquired by a game application acquisition microphone. For example, when the voice communication application is controlled to capture audio data captured by a microphone and the gaming application is controlled to capture audio data captured by a microphone, the user interface element corresponding to the voice communication application may be clicked first to control not to capture audio data captured by a microphone, and then the user interface element corresponding to the gaming application may be clicked to control to capture audio data captured by a microphone; or when the voice communication application and the game application are controlled not to capture the audio data collected by the microphone, the user interface element corresponding to the game application can be clicked to control the audio data collected by the microphone, so that the game application can timely communicate with other game players through the game voice. In a similar manner, the user C can communicate with the voice after switching back to the voice communication application quickly and timely.
Specifically, user B opens the game voice of a certain game application (e.g., game application A). As shown in list 1102, the user interface elements of the current sound recording application are displayed in the notification bar, and only game application a is currently in a state of capturing audio data collected by the microphone. A certain voice communication application (such as communication application B) is accessed in a voice call, and a user B is connected with the voice call of the communication application B through a notification bar popped up by the communication application B. The notification bar mode belongs to the background mode. As shown in list 1104, the notification bar displays that game application A and communication application B are in the recording application list. Game application a adds an attribute value: "Audio mode runner" or in the foreground, with higher priority, is in a state of capturing Audio data collected by the microphone; the communication application B is in a mute state and in a state where audio data collected by the microphone is not captured. The game application A and the communication application B both adopt VoIP to carry out voice call, are privacy sensitive applications, and add attribute values: an application of "Audio mode wner" or an application in the foreground (in the case where the attribute value of "Audio mode wner" is not added), who is controlled to capture Audio data collected by the microphone.
In the notification bar, the user clicks on a user interface element of the game application a, designates the game application a as a recording application that does not capture audio data captured by the microphone, and controls it not to capture audio data captured by the microphone. In response to the user's operation, as shown in list 1106, game application a is set to a silent recording application through a notification bar, and is controlled not to capture audio data collected by the microphone; currently, among the remaining recording applications except for the application (e.g., game application a) designated by the user that does not capture audio recording data, the communication application B has the highest system priority, and when the communication application B can capture audio data captured by the microphone, it is controlled to capture audio data captured by the microphone.
In the notification bar, the user clicks on a user interface element of communication application B. Then, click on the user interface element of game application A. In response to the user operation, as shown in the list 1108, the communication application B is set to be a silent recording application through the notification bar, and is controlled not to capture audio data collected by the microphone; the game application A is set as a recording application for capturing audio data collected by a microphone, and the recording application is controlled to capture the audio data collected by the microphone.
It should be understood that, although the steps in the flowcharts of fig. 2 and 5 are shown in order as indicated by the arrows, these steps are not necessarily performed in order as indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in fig. 2 and 5 may include multiple sub-steps or stages that are not necessarily performed at the same time, but may be performed at different times, nor does the order in which the sub-steps or stages are performed necessarily occur in sequence, but may be performed alternately or alternately with at least some of the other steps or sub-steps of other steps.
In some exemplary embodiments of the present disclosure, as shown in fig. 12, there is provided a multimedia data control apparatus including: an element providing module 1202 configured to provide at least one application with a user interface element for controlling capturing of multimedia recording data when the at least one application is in a multimedia recording state, wherein one user interface element corresponds to one application; a control module 1204 configured to control, in response to a user operation on the user interface element, the capturing or non-capturing of the multimedia recording data by the application to which the user interface element corresponds.
In certain exemplary embodiments of the present disclosure, the control module is configured to control, via the user interface element, a multimedia recording state of the application that does not capture the multimedia recording data without exiting the application that does not capture the multimedia recording data; and/or the control module is configured to support a plurality of applications to capture the multimedia recording data simultaneously when the application captures the multimedia recording data through the user interface element control.
In certain exemplary embodiments of the present disclosure, the user interface elements described above include user interface controls having identifications of corresponding applications.
In certain exemplary embodiments of the present disclosure, the above-described identification includes an iconic pattern of the corresponding application.
In certain exemplary embodiments of the present disclosure, the above-described user interface element is further configured to present state information of the corresponding application, the state information including information of whether the corresponding application is in a state of capturing or not capturing multimedia recording data and/or information of whether the captured or not captured state information of the application is set by a system or by a user operation.
In certain exemplary embodiments of the present disclosure, the user interface elements described above present different status information in different display modes.
In certain exemplary embodiments of the present disclosure, the different display modes described above include one or a combination of multiple modes of displaying in different sub-areas, displaying at different levels of darkness, displaying at different sizes, displaying at different colors, and adding different logos.
In certain exemplary embodiments of the present disclosure, the user interface elements described above are provided in a notification bar.
In certain exemplary embodiments of the present disclosure, an application that is controlled to capture multimedia recording data in response to a user operation does not preempt other applications to exit the capture state unless controlled again by the user operation to not capture multimedia recording data or to exit the multimedia recording state in response to an exit event.
In certain exemplary embodiments of the present disclosure, the control module described above is further configured to maintain a capture state of the multimedia recording data in response to the user operation of the application controlled to capture the multimedia recording data when the preset application captures the multimedia recording data.
In certain exemplary embodiments of the present disclosure, the predetermined application described above is an application having the highest system priority for capturing multimedia recording data.
In certain exemplary embodiments of the present disclosure, the multimedia recording data described above includes audio and/or video data collected by a multimedia component.
For specific limitations of the multimedia data control apparatus, reference may be made to the above limitations of the multimedia data control method, and no further description is given here. The respective modules in the above-described multimedia data control apparatus may be implemented in whole or in part by software, hardware, and a combination thereof. The above modules may be embedded in hardware or independent of a processor in the terminal, or may be stored in software in a memory in the terminal, so that the processor may call and execute operations corresponding to the above modules.
In certain exemplary embodiments of the present disclosure, a terminal is provided that includes a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the multimedia data control method of any one of the embodiments described above when the computer program is executed.
In certain exemplary embodiments of the present disclosure, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, implements the steps of the multimedia data control method of any one of the embodiments described above.
Those skilled in the art will appreciate that implementing all or part of the above-described methods in accordance with the embodiments may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed may comprise the steps of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in embodiments provided by the present disclosure may include non-volatile and/or volatile memory. The nonvolatile memory can include Read Only Memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), memory bus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), among others.
The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The foregoing examples merely represent several embodiments of the present disclosure, which are described in more detail and are not to be construed as limiting the scope of the invention. It should be noted that variations and modifications can be made by those skilled in the art without departing from the spirit of the disclosure, which are within the scope of the disclosure. Accordingly, the scope of protection of the present disclosure should be determined by the following claims.

Claims (26)

1. A method of multimedia data control, the method comprising:
providing at least one application with a user interface element for controlling capturing of multimedia recording data when the at least one application is in a multimedia recording state, wherein one of the user interface elements corresponds to one application;
and responding to the user operation of the user interface element, and controlling the application corresponding to the user interface element to capture or not capture the multimedia recording data.
2. The method of claim 1, wherein said controlling the application to which the user interface element corresponds to capture or not capture the multimedia recording data comprises:
controlling the application not to capture the multimedia recording data through the user interface element, and not exiting the multimedia recording state of the application not capturing the multimedia recording data;
and/or
And when the user interface element controls the application to capture the multimedia recording data, supporting a plurality of applications to capture the multimedia recording data simultaneously.
3. The method of claim 1 or 2, wherein the user interface element comprises a user interface control having an identification of a corresponding application.
4. A method according to claim 3, wherein the identification comprises an iconic pattern of the corresponding application.
5. The method according to claim 1 or 2, characterized in that:
the user interface element is further configured to present status information of the corresponding application, including information of whether the corresponding application is in a state of capturing or not capturing the multimedia recording data and/or information of whether the captured or not captured status information of the application is set by a system or by the user operation.
6. The method according to claim 5, wherein:
the user interface element presents different ones of the status information in different display modes.
7. The method of claim 5, wherein the different display modes include one or a combination of displaying in different sub-areas, displaying at different levels of darkness, displaying at different sizes, displaying at different colors, and adding different logos.
8. A method according to claim 1 or 2, wherein the user interface element is provided in a notification bar.
9. The method according to claim 1 or 2, characterized in that: an application controlled to capture the multimedia recording data in response to the user operation does not preempt other applications and exits the capture state unless controlled again by the user operation to not capture the multimedia recording data or exit the multimedia recording state in response to an exit event.
10. The method according to claim 1 or 2, characterized in that the method further comprises:
when a preset application captures the multimedia recording data, an application controlled to capture the multimedia recording data in response to the user operation maintains a capturing state of the multimedia recording data.
11. The method of claim 10, wherein the predetermined application is an application having a highest system priority for capturing the multimedia recording data.
12. The method according to claim 1 or 2, wherein the multimedia recording data comprises audio and/or video data collected by a multimedia component.
13. A multimedia data control apparatus, the apparatus comprising:
an element providing module configured to provide at least one application with a user interface element for controlling capturing of multimedia recording data when the at least one application is in a multimedia recording state, wherein one of the user interface elements corresponds to one application;
and the control module is configured to respond to the user operation of the user interface element and control the application corresponding to the user interface element to capture or not capture the multimedia recording data.
14. The apparatus according to claim 13, wherein:
the control module is configured to control the application not to capture the multimedia recording data through the user interface element, and not to exit the multimedia recording state of the application not capturing the multimedia recording data;
And/or
The control module is configured to support a plurality of the applications to simultaneously capture the multimedia recording data when the applications are controlled to capture the multimedia recording data through the user interface element.
15. The apparatus of claim 13 or 14, wherein the user interface element comprises a user interface control having an identification of a corresponding application.
16. The apparatus of claim 15, wherein the identification comprises an iconic pattern of the corresponding application.
17. The apparatus according to claim 13 or 14, wherein:
the user interface element is further configured to present status information of the corresponding application, including information of whether the corresponding application is in a state of capturing or not capturing the multimedia recording data and/or information of whether the captured or not captured status information of the application is set by a system or by the user operation.
18. The apparatus according to claim 17, wherein:
the user interface element presents different ones of the status information in different display modes.
19. The apparatus of claim 18, wherein the different display modes include one or a combination of displaying in different sub-areas, displaying at different levels of darkness, displaying at different sizes, displaying at different colors, and adding different logos.
20. The apparatus of claim 13 or 14, wherein the user interface element is provided in a notification bar.
21. The apparatus according to claim 13 or 14, wherein: an application controlled to capture the multimedia recording data in response to the user operation does not preempt other applications and exits the capture state unless controlled again by the user operation to not capture the multimedia recording data or exit the multimedia recording state in response to an exit event.
22. The apparatus according to claim 13 or 14, wherein:
the control module is further configured to maintain a capture state of the multimedia recording data in response to the user operation of an application controlled to capture the multimedia recording data when the multimedia recording data is captured by a preset application.
23. The apparatus of claim 22, wherein the predetermined application is an application having a highest system priority for capturing the multimedia recording data.
24. The apparatus of claim 13 or 14, wherein the multimedia recording data comprises audio and/or video data collected by a multimedia component.
25. A terminal comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the method according to any one of claims 1 to 12 when the computer program is executed.
26. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 12.
CN202210095172.6A 2022-01-26 2022-01-26 Multimedia data control method, device, terminal and storage medium Pending CN116546130A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210095172.6A CN116546130A (en) 2022-01-26 2022-01-26 Multimedia data control method, device, terminal and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210095172.6A CN116546130A (en) 2022-01-26 2022-01-26 Multimedia data control method, device, terminal and storage medium

Publications (1)

Publication Number Publication Date
CN116546130A true CN116546130A (en) 2023-08-04

Family

ID=87442293

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210095172.6A Pending CN116546130A (en) 2022-01-26 2022-01-26 Multimedia data control method, device, terminal and storage medium

Country Status (1)

Country Link
CN (1) CN116546130A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117082268A (en) * 2023-10-18 2023-11-17 成都有为财商教育科技有限公司 Video recording and broadcasting method and system for online live broadcast

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117082268A (en) * 2023-10-18 2023-11-17 成都有为财商教育科技有限公司 Video recording and broadcasting method and system for online live broadcast
CN117082268B (en) * 2023-10-18 2024-01-30 成都有为财商教育科技有限公司 Video recording and broadcasting method and system for online live broadcast

Similar Documents

Publication Publication Date Title
JP5959771B2 (en) Electronic device, method and program
CN111381739B (en) Application icon display method and device, electronic equipment and storage medium
CN112969097B (en) Content playing method and device, and content commenting method and device
JP6509516B2 (en) Electronic device, method and program
JP2009159507A (en) Electronic apparatus and image display control method
CN114095776B (en) Screen recording method and electronic equipment
CN112148163B (en) Screen recording method and device and electronic equipment
CN112764710A (en) Audio playing mode switching method and device, electronic equipment and storage medium
CN116546130A (en) Multimedia data control method, device, terminal and storage medium
CN110225182B (en) Control method for flexible screen intelligent terminal and intelligent terminal
CN113282362B (en) Application management method, device, storage medium and terminal
WO2022267433A1 (en) Video resource processing method and apparatus
CN114095611B (en) Processing method and device of caller identification interface, electronic equipment and storage medium
CN113923469A (en) Processing method, device, equipment and storage medium for continuous delivery of gifts in live broadcast
JP2024500481A (en) Video calling method and device
KR20230105345A (en) Video Recording Methods and Electronic Devices
WO2021249104A1 (en) System and method for determining position of a new interface element on user interface
CN114866844B (en) Video playing method and device
CN110913058B (en) Terminal, method for preventing mistaken touch control of terminal and device with storage function
CN115550505B (en) Incoming call processing method and device
WO2021249069A1 (en) System and method for combing applications running on a user device
CN115955455A (en) Voice message processing method and device and electronic equipment
WO2020107173A1 (en) Interface content adjustment method, electronic device and machine-readable storage medium
CN118151816A (en) Display method, display device, electronic equipment and storage medium
CN114554003A (en) Interface display method and device and electronic equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination