CN111158802B - Audio playing method, equipment, client device and electronic equipment - Google Patents
Audio playing method, equipment, client device and electronic equipment Download PDFInfo
- Publication number
- CN111158802B CN111158802B CN201811326466.5A CN201811326466A CN111158802B CN 111158802 B CN111158802 B CN 111158802B CN 201811326466 A CN201811326466 A CN 201811326466A CN 111158802 B CN111158802 B CN 111158802B
- Authority
- CN
- China
- Prior art keywords
- weex
- interface
- audio
- playing
- layer
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
Abstract
A method, an apparatus, a client device and an electronic device for playing audio are disclosed. The method comprises the following steps: the Weex layer acquires a first operation input for a Weex audio playing interface; the Weex layer obtains corresponding play data information from the Native layer through an active call class interface corresponding to the first operation in a preset communication protocol; the Weex layer updates the Weex audio playing interface according to the playing data information; the active call class interface is used for the Weex layer to actively call the corresponding audio playing function in the Native layer. According to the method and the device, the application developed through the Weex framework can call the Native component to realize the audio playing function, and the playing experience of the Native application is achieved.
Description
Technical Field
The disclosure relates to the field of computer technology, and more particularly, to a method, a device, a client device and an electronic device for audio playing based on a hybrid implementation of Weex and Native.
Background
In the current application development process, the page application is developed by using an H5 technology with release, update and one URL adaptable end, and although the method is simple and efficient, the interactive performance experience of a Native application is very difficult to obtain. Thus, an application development framework, such as the Weex framework, that can compromise development efficiency and performance experience has evolved.
Applications developed through application frameworks such as Weex generally only provide basic application function development, for example, only basic audio playing functions, and cannot realize functions of native audio playing applications such as background audio playing and song switching.
Accordingly, the inventors have recognized that there is a need for an improvement over the above-described deficiencies in the prior art.
Disclosure of Invention
It is an object of the present disclosure to provide a new solution for audio playback.
According to a first aspect of the present disclosure, there is provided a method of audio playback, wherein the method comprises:
the Weex layer acquires a first operation input for a Weex audio playing interface;
the Weex layer obtains corresponding play data information from the Native layer through an active call class interface corresponding to the first operation in a preset communication protocol;
the Weex layer updates the Weex audio playing interface according to the playing data information;
the active call class interface is used for the Weex layer to actively call the corresponding audio playing function in the Native layer.
Optionally, the method further includes:
the Weex layer acquires a second operation input for the Weex audio playing interface;
the Weex layer displays a Native play control according to the second operation, and closes the Weex audio play interface;
and the Weex layer receives the playing data information sent by the Native layer in real time through a monitoring interface in a preset communication protocol.
Optionally, the active call class interface includes at least: the audio player initializes the interface, acquires the current audio player data interface, the current play data interface, the pause audio play interface and the current play seconds interface.
Optionally, the listening interface includes at least: the method comprises the steps of obtaining a current playing audio data interface, obtaining a current player playing second interface, obtaining a current player playing state interface and obtaining a current player playing index interface.
Optionally, the Weex audio playing interface at least includes: a trailable progress bar, audio time, play control buttons, a pop-up playlist directory, a player cover map, and play information.
Optionally, the Native play control is displayed in a form of a widget;
and displaying the current playing information in the Native playing control.
Optionally, the method further comprises:
and responding to clicking operation for the Native play control, and displaying the Weex audio play interface.
According to a second aspect of the present disclosure, there is provided an apparatus for audio playback, comprising:
means for causing the Weex layer to obtain a first operation input for the Weex audio playback interface;
means for enabling the Weex layer to obtain corresponding play data information from the Native layer through an active call class interface corresponding to the first operation in a preset communication protocol; the method comprises the steps of,
means for causing the Weex layer to update the Weex audio playback interface based on the playback data information;
the active call class interface is used for the Weex layer to actively call the corresponding audio playing function in the Native layer.
According to a third aspect of the present disclosure there is provided a client device comprising an apparatus for audio playback according to the second aspect of the present disclosure, or designed for performing operations in a method of audio playback according to any one of the first aspects of the present disclosure.
According to a fourth aspect of the present disclosure, there is provided an electronic apparatus, comprising a client device according to the third aspect of the present disclosure; alternatively, the electronic device includes a memory for storing instructions and a processor; the instructions are for controlling the processor to operate to perform operations in the method of audio playback as described in any one of the first aspects of the present disclosure.
According to the embodiment of the disclosure, the application developed through the Weex framework can call the Native component to realize the audio playing function, so that the playing experience of the Native application is achieved.
Other features of the present invention and its advantages will become apparent from the following detailed description of exemplary embodiments of the invention, which proceeds with reference to the accompanying drawings.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description, serve to explain the principles of the invention.
Fig. 1 shows a schematic flow chart of a method of audio playback according to an embodiment of the present disclosure.
Fig. 2 shows a schematic flow chart of a method of yet another audio playback according to an embodiment of the present disclosure.
Fig. 3 shows a schematic block diagram of a client device according to an embodiment of the present disclosure.
Fig. 4 shows a schematic block diagram of an electronic device according to an embodiment of the disclosure.
Detailed Description
Various exemplary embodiments of the present invention will now be described in detail with reference to the accompanying drawings. It should be noted that: the relative arrangement of the components and steps, numerical expressions and numerical values set forth in these embodiments do not limit the scope of the present invention unless it is specifically stated otherwise.
The following description of at least one exemplary embodiment is merely exemplary in nature and is in no way intended to limit the invention, its application, or uses.
Techniques, methods, and apparatus known to one of ordinary skill in the relevant art may not be discussed in detail, but are intended to be part of the specification where appropriate.
In all examples shown and discussed herein, any specific values should be construed as merely illustrative, and not a limitation. Thus, other examples of exemplary embodiments may have different values.
It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further discussion thereof is necessary in subsequent figures.
Various embodiments and examples according to the present disclosure are described below with reference to the accompanying drawings.
< method example >
Fig. 1 shows a schematic flow chart of a method of audio playback according to an embodiment of the present disclosure.
As shown in fig. 1, in which, in step 1100, the Weex layer obtains a first operation input for a Weex audio playing interface.
It should be noted that, the Weex audio playing interface is constructed by placing audio playing interface controls on a Weex page in a way of integrating independent components on the page, and the Weex audio playing interface is an independent visual interface.
The audio playing interface control is compiled by adopting a Weex technology, and the Weex audio playing interface at least comprises: a trailable progress bar, audio time, play control buttons, a pop-up playlist directory, a player cover map, and play information.
The first operation is an operation for triggering an audio play function, which is input for the Weex audio play interface. For example, the first operation may include: initialization operation, play operation, pause operation, forward/backward operation, audio switching operation, drag progress bar operation, and the like.
The initialization operation may trigger an initialization function of the Weex audio playing interface. The play operation may trigger an audio play function. The pause operation may trigger a pause audio play function. The forward/reverse operation may trigger a fast forward/reverse play audio function. The audio switching operation may trigger a function of playing the previous audio/next audio. Dragging the progress bar may trigger a function where audio starts playing from a particular description.
After the first operation is obtained, step 1200 is entered, where the Weex layer obtains corresponding play data information from the Native layer through an active call class interface corresponding to the first operation in a preset communication protocol.
The active call class interface is used for the Weex layer to actively call the corresponding audio playing function in the Native layer. The Weex layer can actively communicate with the Native layer through the active call type interface, and the Weex layer obtains or transmits parameters to the Native layer through single call, and the Native layer returns corresponding play data information and responds to corresponding function operation, and the call is ended.
Specifically, the active call class interface at least includes: an audio player initializes an interface (initAudio), acquires a current audio player data interface (getExtraInfo), a current play data interface (play), a pause audio play interface (pause), and a current play seconds interface (seekTo).
It should be noted that, in setting the current playing data interface, the method may optionally include: and playing the data parameters and the playing index parameters to specify the played audio data, and playing the current audio data if the parameters are not included. In setting the current playback second interface, a second parameter must be included to specify the start seconds of audio playback.
In one example, when the webx audio playing interface implements the initialization function, an audio player initialization interface (initAudio) is called to notify the Native layer of initialization, and then the current audio playing data is obtained by obtaining the current audio player data interface (getExtraInfo).
When the Weex audio playing interface realizes the playing/pausing function, a current playing data interface (play) and a pause audio playing interface (pause) are called to play/pause the current audio.
When the Weex audio playing interface realizes the forward/backward function, the current playing second interface (seekTo) is called, the seconds needing forward/backward are transferred, and the function of continuing playing from the transferred seconds is realized.
When the Weex audio playing interface realizes the audio switching function, the current playing data interface (play) is called, and the data and index value of the audio needing to be played are transmitted, so that the piece of audio data can be played.
When the function of dragging the progress bar and playing the progress bar to a specific position is achieved through the Weex audio playing interface, the Weex layer does not depend on the Native layer, a progress bar component capable of being dragged in real time is achieved on the Weex layer, the dragged progress is returned in real time, a current playing seconds interface (seekTo) is called, the seconds after dragging are transferred to the Native layer, and the function of playing the progress bar after the Weex dragging is achieved.
In step 1300, the Weex layer updates the Weex audio playing interface according to the playing data information.
For example, current audio playing data is obtained, information in the Weex audio playing interface is updated according to the current audio playing data, and an audio player interface which can be operated is displayed. And acquiring the number of seconds of forward/backward, and updating the audio time in the Weex audio playing interface to the corresponding number of seconds. And when the play/pause information is acquired, updating the play control button in the Weex audio play interface to a corresponding play/pause state. When the data and index value of the audio are obtained, the cover map and the playing information of the player in the Weex audio playing interface are updated to corresponding audio data.
Further, in the actual use process, the background switching play of the Weex audio play interface and the Native play component can be performed.
Specifically, as shown in fig. 2, in step 2100, the Weex layer obtains a second operation input for the Weex audio playing interface.
The second operation is to switch the Weex audio playing interface to a Native playing component. For example, the second operation may be an operation of clicking a close button of the Weex audio playing interface. For another example, the second operation may be an operation of clicking on a background to run the Weex audio playing interface.
In step 2200, the Weex layer displays a Native play control according to the second operation, and closes the Weex audio play interface.
Specifically, the Native play control is displayed in a widget form; and displaying the current playing information in the Native playing control.
It should be noted that, the closing the Weex audio playing interface means that the Weex audio playing interface is not displayed any more in the current display interface, and the Weex audio playing interface is operated in the background.
When the Weex audio playing interface needs to be switched to perform the finer audio operation, the Weex audio playing interface can be quickly opened by clicking the Native playing control. Specifically, in response to clicking operation for the Native play control, the Weex audio play interface is displayed.
In step 2300, the Weex layer receives, in real time, the play data information sent by the Native layer through a listening interface in a preset communication protocol.
The monitoring interface is used for passive communication of the Weex layer and the Native layer, and receives playing data information returned by the Native layer in real time. As long as the Native layer returns data, the Weex layer receives the data and responds without invoking the end.
Specifically, the listening interface at least includes: the method comprises the steps of obtaining a current playing audio data interface (getcurrentState), obtaining a current player playing second interface (onaudioProgressChange), obtaining a current player playing state interface (onaudioStateChange), and obtaining a current player playing index interface (onaudioItemChange).
When the Weex audio playing interface is played, playing data information is transferred to the Native layer through a preset communication protocol, a Native background playing function is still realized under the condition that the Weex audio playing interface of the Weex layer is turned off, and when the background is played, the Weex audio playing interface of the Weex layer can be seamlessly switched back at any time, the current audio playing state is displayed, and audio playing is continued.
In a possible implementation, with the preset communication protocol, further expandable functions, such as multiple play, audio manuscripts, audio comments, etc., may be implemented, which are not listed here.
In another possible implementation, the preset communication protocol between the Weex and Native may also be that the audio data information is stored in a public area, and the Weex layer and the Native layer implement communication through respective real-time reading and copying.
According to the audio playing method, through constructing a communication protocol between the Weex and Native and related to audio, the application developed through the Weex can call the Native component to realize the audio playing function, and can realize more expandable functions such as multiple playing, audio manuscripts, audio comments and the like, so that the diversity of audio playing on the Weex is greatly enriched, the application developed through the Weex framework can call the Native component to realize the audio playing function, and the playing experience of the Native application is achieved.
< apparatus >
It will be appreciated by those skilled in the art that in the field of electronic technology, the above method may be embodied in a product in a form of software, hardware, and a combination of software and hardware, and that a person skilled in the art will readily produce an apparatus for audio playback comprising means for performing the respective operations of the method for audio playback according to the above embodiments based on the method disclosed above. For example, the apparatus comprises: means for causing the Weex layer to obtain a first operation input for the Weex audio playback interface; means for enabling the Weex layer to obtain corresponding play data information from the Native layer through an active call class interface corresponding to the first operation in a preset communication protocol; means for causing the Weex layer to update the Weex audio playback interface based on the playback data information; the active call class interface is used for the Weex layer to actively call the corresponding audio playing function in the Native layer.
It will be appreciated by those skilled in the art that the apparatus for audio playback may be implemented in a variety of ways. For example, the processor may be configured by instructions to implement a device for audio playback. For example, instructions may be stored in a ROM and, when the device is booted, read from the ROM into a programmable device to implement the device for audio playback. For example, the device for audio playback may be solidified into a dedicated device (e.g., ASIC). The devices for audio playback may be separated into separate units or they may be combined together. The device for audio playback may be implemented by one of the above-described various implementations, or may be implemented by a combination of two or more of the above-described various implementations.
< client device >
At least one embodiment in accordance with the present disclosure may be implemented in a client device (or client application) such as a cell phone, tablet, or the like.
Fig. 3 shows a schematic block diagram of a client device according to an embodiment of the present disclosure. As shown in fig. 3, the client apparatus 3000 includes an audio playback device 3010. The device 3010 for audio playback may be a device for audio playback according to the above-described embodiments.
Furthermore, as previously mentioned, a client device can also be produced based on the method described above, which can be designed to perform the steps in the solution of the embodiment described with reference to fig. 1.
It is well known to those skilled in the art that with the trend of electronic information technology such as large scale integrated circuit technology and software hardware, it has become difficult to clearly divide the software and hardware boundaries of a computer system. Because any operations may be implemented in software or hardware. Execution of any instructions may be accomplished by hardware as well as software. Whether a hardware implementation or a software implementation is employed for a certain machine function depends on non-technical factors such as price, speed, reliability, storage capacity, change period, etc. The software implementation and the hardware implementation are equivalent to the skilled person. The skilled person may choose software or hardware to implement the above scheme as required. Thus, specific software or hardware is not limited herein.
< electronic device >
Any of the above embodiments may be implemented in an electronic device such as a cell phone, tablet computer, or the like. For example, the electronic apparatus may include the client device in the above-described embodiment.
Further, fig. 4 shows a schematic block diagram of an electronic device according to an embodiment of the disclosure. As shown in fig. 4, the electronic apparatus 4000 may include a processor 4010, a memory 4020, an interface device 4030, a communication device 4040, a display device 4050, an input device 4060, a speaker 4070, a microphone 4080, and the like.
The processor 4010 may be, for example, a Central Processing Unit (CPU), a Microprocessor (MCU), or the like. The memory 4020 includes, for example, ROM (read only memory), RAM (random access memory), nonvolatile memory such as a hard disk, and the like. The interface device 4030 includes, for example, a USB interface, a headphone interface, or the like.
The communication device 4040 can perform wired or wireless communication, for example.
The display device 4050 is, for example, a liquid crystal display, a touch display, or the like. The input device 4060 may include, for example, a touch screen, a keyboard, or the like. A user may input/output voice information through the speaker 4070 and the microphone 4080.
The electronic device shown in fig. 4 is merely illustrative and is in no way intended to limit the invention, its application or uses.
In this embodiment, the memory 4020 is configured to store instructions that, when executed by the electronic device 4000, control the processor 4010 to perform operations in the method of audio playback described above with reference to fig. 1. Those skilled in the art will appreciate that although a plurality of devices are shown in fig. 4, the present invention may relate to only some of the devices therein, such as the processor 4010 and the memory 4020, etc. The skilled person can design instructions according to the disclosed solution. How the instructions control the processor to operate is well known in the art and will not be described in detail here.
It is well known to those skilled in the art that with the trend of electronic information technology such as large scale integrated circuit technology and software hardware, it has become difficult to clearly divide the software and hardware boundaries of a computer system. Because any operations may be implemented in software or hardware. Execution of any instructions may be accomplished by hardware as well as software. Whether a hardware implementation or a software implementation is employed for a certain machine function depends on non-technical factors such as price, speed, reliability, storage capacity, change period, etc. The software implementation and the hardware implementation are equivalent to the skilled person. The skilled person may choose software or hardware to implement the above scheme as required. Thus, specific software or hardware is not limited herein.
The present invention may be an apparatus, method and/or computer program product. The computer program product may include a computer readable storage medium having computer readable program instructions embodied thereon for causing a processor to implement aspects of the present invention.
The computer readable storage medium may be a tangible device that can hold and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium would include the following: portable computer disks, hard disks, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static Random Access Memory (SRAM), portable compact disk read-only memory (CD-ROM), digital Versatile Disks (DVD), memory sticks, floppy disks, mechanical coding devices, punch cards or in-groove structures such as punch cards or grooves having instructions stored thereon, and any suitable combination of the foregoing. Computer-readable storage media, as used herein, are not to be construed as transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., optical pulses through fiber optic cables), or electrical signals transmitted through wires.
The computer readable program instructions described herein may be downloaded from a computer readable storage medium to a respective computing/processing device or to an external computer or external storage device over a network, such as the internet, a local area network, a wide area network, and/or a wireless network. The network may include copper transmission cables, fiber optic transmissions, wireless transmissions, routers, firewalls, switches, gateway computers and/or edge servers. The network interface card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium in the respective computing/processing device.
Computer program instructions for carrying out operations of the present invention may be assembly instructions, instruction Set Architecture (ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, c++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The computer readable program instructions may be executed entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider). In some embodiments, aspects of the present invention are implemented by personalizing electronic circuitry, such as programmable logic circuitry, field Programmable Gate Arrays (FPGAs), or Programmable Logic Arrays (PLAs), with state information for computer readable program instructions, which can execute the computer readable program instructions.
Various aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.
These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable medium having the instructions stored therein includes an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer, other programmable apparatus or other devices implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions. It is well known to those skilled in the art that implementation by hardware, implementation by software, and implementation by a combination of software and hardware are all equivalent.
The foregoing description of embodiments of the invention has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the various embodiments described. The terminology used herein was chosen in order to best explain the principles of the embodiments, the practical application, or the technical improvements in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein. The scope of the invention is defined by the appended claims.
Claims (10)
1. A method of audio playback, wherein the method comprises:
the method comprises the steps that a Weex layer obtains a first operation input for a Weex audio playing interface, wherein the first operation is an operation for triggering an audio playing function;
the Weex layer obtains corresponding play data information from the Native layer through an active call class interface corresponding to the first operation in a preset communication protocol;
the Weex layer updates the Weex audio playing interface according to the playing data information;
the active call class interface is used for the Weex layer to actively call the corresponding audio playing function in the Native layer.
2. The method of claim 1, wherein the method further comprises:
the Weex layer acquires a second operation input for the Weex audio playing interface, wherein the second operation is an operation of switching the Weex audio playing interface into a Native playing component;
the Weex layer displays a Native play control according to the second operation, and closes the Weex audio play interface;
and the Weex layer receives the playing data information sent by the Native layer in real time through a monitoring interface in a preset communication protocol.
3. The method of claim 1, wherein the active invocation class interface comprises at least: the audio player initializes the interface, acquires the current audio player data interface, the current play data interface, the pause audio play interface and the current play seconds interface.
4. The method of claim 2, wherein the listening class interface comprises at least: the method comprises the steps of obtaining a current playing audio data interface, obtaining a current player playing second interface, obtaining a current player playing state interface and obtaining a current player playing index interface.
5. The method of claim 1, wherein the Weex audio playing interface comprises at least: a trailable progress bar, audio time, play control buttons, a pop-up playlist directory, a player cover map, and play information.
6. The method of claim 2, wherein the Native play control is displayed in a widget form;
and displaying the current playing information in the Native playing control.
7. The method of claim 2, wherein the method further comprises:
and responding to clicking operation for the Native play control, and displaying the Weex audio play interface.
8. An apparatus for audio playback, comprising:
means for causing a Weex layer to obtain a first operation input for a Weex audio playback interface, wherein the first operation is an operation for triggering an audio playback function;
means for enabling the Weex layer to obtain corresponding play data information from the Native layer through an active call class interface corresponding to the first operation in a preset communication protocol; the method comprises the steps of,
means for causing the Weex layer to update the Weex audio playback interface based on the playback data information;
the active call class interface is used for the Weex layer to actively call the corresponding audio playing function in the Native layer.
9. A client device comprising the apparatus for audio playback according to claim 8 or being designed for performing operations in the method of audio playback according to any one of claims 1-7.
10. An electronic device comprising the client apparatus of claim 9; alternatively, the electronic device includes a memory for storing instructions and a processor; the instructions are for controlling the processor to operate to perform operations in the method of audio playback as claimed in any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811326466.5A CN111158802B (en) | 2018-11-08 | 2018-11-08 | Audio playing method, equipment, client device and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811326466.5A CN111158802B (en) | 2018-11-08 | 2018-11-08 | Audio playing method, equipment, client device and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111158802A CN111158802A (en) | 2020-05-15 |
| CN111158802B true CN111158802B (en) | 2023-06-09 |
Family
ID=70554983
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811326466.5A Active CN111158802B (en) | 2018-11-08 | 2018-11-08 | Audio playing method, equipment, client device and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111158802B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113626130A (en) * | 2021-10-14 | 2021-11-09 | 中航信移动科技有限公司 | Video application program processing method and device, computer equipment and storage medium |
| CN114339277A (en) * | 2021-12-22 | 2022-04-12 | 武汉斗鱼鱼乐网络科技有限公司 | Live broadcast room sound shielding method and related equipment |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017206626A1 (en) * | 2016-06-01 | 2017-12-07 | 广州市动景计算机科技有限公司 | Network resource access apparatus, mixed apparatus, and method |
| CN107509092A (en) * | 2017-09-07 | 2017-12-22 | 深圳创维数字技术有限公司 | Set top box plays method, set top box, terminal and the storage medium of audio in real time |
| CN107679113A (en) * | 2017-09-15 | 2018-02-09 | 广州神马移动信息科技有限公司 | Acquisition methods, equipment and the electronic equipment gently applied |
| CN107968841A (en) * | 2017-12-20 | 2018-04-27 | 深圳乐信软件技术有限公司 | Dynamic routing method, device, storage medium and the client of Webpage |
| CN108173833A (en) * | 2017-12-25 | 2018-06-15 | 北京摩拜科技有限公司 | A kind of audio frequency playing method, system, server and playback equipment |
| CN108509243A (en) * | 2018-03-15 | 2018-09-07 | 广州虎牙信息科技有限公司 | The method, apparatus and electronic equipment of a kind of page load in application |
| CN108595234A (en) * | 2018-03-13 | 2018-09-28 | 阿里巴巴集团控股有限公司 | Five application page switching method, device and equipment |
-
2018
- 2018-11-08 CN CN201811326466.5A patent/CN111158802B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017206626A1 (en) * | 2016-06-01 | 2017-12-07 | 广州市动景计算机科技有限公司 | Network resource access apparatus, mixed apparatus, and method |
| CN107509092A (en) * | 2017-09-07 | 2017-12-22 | 深圳创维数字技术有限公司 | Set top box plays method, set top box, terminal and the storage medium of audio in real time |
| CN107679113A (en) * | 2017-09-15 | 2018-02-09 | 广州神马移动信息科技有限公司 | Acquisition methods, equipment and the electronic equipment gently applied |
| CN107968841A (en) * | 2017-12-20 | 2018-04-27 | 深圳乐信软件技术有限公司 | Dynamic routing method, device, storage medium and the client of Webpage |
| CN108173833A (en) * | 2017-12-25 | 2018-06-15 | 北京摩拜科技有限公司 | A kind of audio frequency playing method, system, server and playback equipment |
| CN108595234A (en) * | 2018-03-13 | 2018-09-28 | 阿里巴巴集团控股有限公司 | Five application page switching method, device and equipment |
| CN108509243A (en) * | 2018-03-15 | 2018-09-07 | 广州虎牙信息科技有限公司 | The method, apparatus and electronic equipment of a kind of page load in application |
Non-Patent Citations (1)
| Title |
|---|
| 呙森林 ; 张玺 ; .Weex跨平台开发方案研究与应用.信息通信.2017,(第04期),全文. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111158802A (en) | 2020-05-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP6571106B2 (en) | Method, system, computer program, and storage medium for language model customization | |
| WO2019184348A1 (en) | Split-screen display and operation method and apparatus, terminal device, and storage medium | |
| CN107168780B (en) | Virtual reality scene loading method and equipment and virtual reality equipment | |
| TW201243716A (en) | Customized launching of applications | |
| TW201919406A (en) | Bullet screen display method and device | |
| CN107203425B (en) | Switching method and device of light application and electronic device | |
| CN111708557B (en) | Method, device and storage medium for updating configuration file | |
| TW201902232A (en) | Method and apparatus for previewing video search results, and computer readable storage medium | |
| CN105518604A (en) | Feedback for lasso selection | |
| CN110781349A (en) | Method, equipment, client device and electronic equipment for generating short video | |
| CN108449255B (en) | Comment interaction method and equipment, client device and electronic equipment | |
| CN111158802B (en) | Audio playing method, equipment, client device and electronic equipment | |
| CN111970571A (en) | Video production method, device, equipment and storage medium | |
| US10698744B2 (en) | Enabling third parties to add effects to an application | |
| CN110753251A (en) | Video switching method and device and electronic equipment | |
| CN103207726B (en) | The apparatus and method of clipper service are provided in portable terminal | |
| WO2015171228A1 (en) | Methods for facilitating a remote interface and devices thereof | |
| CN111125480A (en) | Background music playing method and equipment, client device and electronic equipment | |
| WO2018010317A1 (en) | Desktop style switching method and device | |
| JP2021056989A (en) | Voice skill recommendation method, apparatus, device, and storage medium | |
| CN111158678B (en) | Video playing method and device, client device and electronic device | |
| CN110764849A (en) | Rendering method and device for user interface, client device and electronic device | |
| CN110780952A (en) | Application interface interaction method and device and electronic equipment | |
| CN116762055A (en) | Synchronizing virtual reality notifications | |
| CN110704141A (en) | Page switching 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |