CN111158802A

CN111158802A - Audio playing method and equipment, client device and electronic equipment

Info

Publication number: CN111158802A
Application number: CN201811326466.5A
Authority: CN
Inventors: 关基荣; 庞锦贵; 李金�; 肖遥航
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Group Holding Ltd
Priority date: 2018-11-08
Filing date: 2018-11-08
Publication date: 2020-05-15
Anticipated expiration: 2038-11-08
Also published as: CN111158802B

Abstract

Disclosed are an audio playing method, audio playing equipment, a client device and electronic equipment. The method comprises the following steps: the Weex layer acquires a first operation input aiming at a Weex audio playing interface; the Weex layer acquires corresponding playing data information from the Native layer through an active calling 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 calling type 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

Audio playing method and equipment, client device and electronic equipment

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a method, a device, a client device, and an electronic device for audio playback based on Weex and Native mixture.

Background

In the current application development process, the H5 technology with "release, i.e. update", and "one URL adaptable to multiple ends" is used to develop the page application, which is simple and efficient, but it is very difficult to obtain the rich interactive performance experience of Native (Native) applications. Therefore, an application development framework, such as the Weex framework, which can achieve both development efficiency and performance experience, has been produced.

Applications developed through an application framework such as Weex can only provide basic application function development, for example, can only provide basic audio playing function, and cannot realize the functions of native audio playing applications such as background playing of audio, song switching and the like.

Therefore, the inventors have considered that there is a need to improve upon the above-mentioned drawbacks of the prior art.

Disclosure of Invention

An object of the present disclosure is to provide a new technical 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 aiming at a Weex audio playing interface;

the Weex layer acquires corresponding playing data information from the Native layer through an active calling 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 calling type interface is used for the Weex layer to actively call the corresponding audio playing function in the Native layer.

Optionally, wherein the method further comprises:

the Weex layer acquires a second operation input aiming at the Weex audio playing interface;

the Weex layer displays a Native playing control according to the second operation, and closes the Weex audio playing 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 at least includes: the audio player initializes the interface, obtains the current audio player data interface, the current playing data interface, the pause audio playing interface and the current playing second interface.

Optionally, the listening class interface at least includes: 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 playback interface at least includes: draggable progress bars, audio times, play control buttons, pop-up playlist directories, player cover drawings, and play information.

Optionally, wherein the Native play control is displayed in a small window;

and the Native playing control displays current playing information.

Optionally, the method further comprises:

and responding to the clicking operation aiming at the Native playing control, and displaying the Weex audio playing interface.

According to a second aspect of the present disclosure, there is provided an apparatus for audio playback, comprising:

the device comprises a Weex layer, a first operation module and a second operation module, wherein the first operation module is used for enabling the Weex layer to obtain a first operation input aiming at a Weex audio playing interface;

the device is used for enabling the Weex layer to obtain corresponding playing data information from a Native layer through an active calling interface corresponding to the first operation in a preset communication protocol; and the number of the first and second groups,

means for enabling the Weex layer to update the Weex audio playing interface according to the playing data information;

According to a third aspect of the present disclosure, there is provided a client device, wherein the apparatus for audio playback according to the second aspect of the present disclosure is included or is designed to perform operations in the method for 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 device, comprising the client apparatus according to the third aspect of the present disclosure; alternatively, the electronic device comprises a memory for storing instructions and a processor; the instructions are for controlling the processor to operate so as to carry out operations in a method of audio playback as claimed in any one of the first aspects of the disclosure.

According to one embodiment of the disclosure, 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.

Other features of the present invention and advantages thereof will become apparent from the following detailed description of exemplary embodiments thereof, 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 diagram of a method of audio playback according to an embodiment of the present disclosure.

Fig. 2 shows a schematic flow diagram of yet another method of 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 present 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, the numerical expressions and numerical values set forth in these embodiments do not limit the scope of the present invention unless specifically stated otherwise.

The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the invention, its application, or uses.

Techniques, methods, and apparatus known to those 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 particular value should be construed as merely illustrative, and not limiting. Thus, other examples of the exemplary embodiments may have different values.

It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, further discussion thereof is not required in subsequent figures.

Various embodiments and examples according to the present disclosure are described below with reference to the drawings.

< method examples >

As shown in fig. 1, wherein the Weex layer obtains a first operation input for the Weex audio playback interface in step 1100.

It should be noted that the Weex audio playing interface is constructed by placing an audio playing interface control on a Weex page in a manner of page integration independent components, 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 the following components: draggable progress bars, audio times, play control buttons, pop-up playlist directories, player cover drawings, 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: an initialization operation, a play operation, a pause operation, a forward/backward operation, an audio switching operation, a drag progress bar operation, and the like.

The initialization operation can trigger the 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/fast reverse audio play function. The audio switch operation may trigger the function of playing the previous/next audio. Dragging the progress bar operation may trigger a function where audio is played from a specific description.

After the first operation is obtained, step 1200 is performed, and the Weex layer obtains corresponding play data information from the Native layer through an active call interface corresponding to the first operation in a preset communication protocol.

The active calling type 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 calling interface, the Weex layer can obtain or transmit parameters to the Native layer through single calling, the Native layer returns corresponding playing data information, and the calling is finished in response to corresponding function operation.

Specifically, the active call class interface at least includes: the method comprises the steps of initializing an audio player interface (initAudio), acquiring a current audio player data interface (getExtraInfo), a current playing data interface (play), a pause audio playing interface (pause) and a current playing seconds interface (seekTo).

It should be noted that, in setting the current playing data interface, optionally, the following may be included: and playing the data parameters and the playing index parameters to specify the played audio data, and if the parameters are not included, playing the current audio data. In setting the currently playing seconds interface, a seconds parameter must be included to specify the starting seconds for audio playback.

In an example, when the Weex audio playing interface implements an initialization function, an audio player initialization interface (initAudio) is called first to notify a Native layer of initialization, and then current audio playing data is obtained by obtaining a current audio player data interface (getExtraInfo).

When the Weex audio playing interface realizes the playing/pausing function, the current playing data interface (play) and the paused audio playing interface (pause) are called to play/pause the current audio.

When the Weex audio playing interface realizes the forward/backward function, the currently played second interface (seekTo) is called to transfer the seconds needing forward/backward, 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 to transfer the data and the index value of the audio required to be played, and the audio data can be played.

When the Weex audio playing interface realizes the function of dragging the progress bar to play to a specific position, the Weex layer does not depend on the Native layer, a progress bar assembly capable of being dragged in real time is realized on the Weex layer, the dragged progress is returned in real time, the current playing second interface (seekTo) is called, the dragged second is transferred to the Native layer, and the function of Weex dragging the progress bar to play is realized.

In step 1300, the Weex layer updates the Weex audio playing interface according to the playing data information.

For example, the current audio playing data is acquired, the 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 forward/backward seconds, and updating the audio time in the Weex audio playing interface to the corresponding seconds. And when the playing/pausing information is acquired, updating the playing control button in the Weex audio playing interface to be in a corresponding playing/pausing state. And when the data and the index value of the audio are acquired, updating the cover page map and the playing information of the player in the Weex audio playing interface into corresponding audio data.

Further, in the actual use process, the Weex audio playing interface and the Native playing component can be switched and played in the background.

Specifically, as shown in fig. 2, in step 2100, the Weex layer obtains a second operation for the Weex audio playback interface input.

The second operation is the operation of switching 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 playback interface. For another example, the second operation may be an operation of clicking the Weex audio playback interface to run in the background.

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 playing control is displayed in a small window form; and the Native playing control displays current playing information.

It should be noted that, the closing of the Weex audio playing interface means that the Weex audio playing interface is no longer displayed in the current display interface, and the Weex audio playing interface is executed in the background.

When the Weex audio playing interface needs to be switched to for detailed audio operation, the Weex audio playing interface can be quickly opened by clicking the Native playing control. Specifically, the Weex audio playing interface is displayed in response to the clicking operation of the Native playing control.

In step 2300, the Weex layer receives the broadcast data information sent by the Native layer in real time through a monitoring interface in a preset communication protocol.

The monitoring interface is used for the Weex layer to passively communicate with the Native layer and receive the playing data information returned by the Native layer in real time. As long as the Native layer returns data, the Weex layer always receives data and responds, and the call is not ended.

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 plays, playing data information is transmitted to the Native layer through a preset communication protocol, the Native background playing function is still realized under the condition that the Weex audio playing interface of the Weex layer is turned off, and during background playing, 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 manner, by using the preset communication protocol, more extensible functions, such as multiple playing, audio manuscript, audio comment, etc., can be implemented.

In another possible implementation manner, the preset communication protocol between the Weex layer and the Native layer can also be that the audio data information is stored in a common area, and the Weex layer and the Native layer realize communication by reading and copying in real time respectively.

According to the audio playing method, a communication protocol related to audio between the Weex and the Native is established, the fact that the Native component can be called by the application developed through the Weex to achieve an audio playing function is achieved, more extensible functions can be achieved, for example, multiple playing, audio manuscripts, audio comments and other functions are achieved, the diversity of audio playing on the Weex is greatly enriched, the fact that the Native component can be called by the application developed through the Weex framework to achieve an audio playing function can be achieved, and playing experience of Native application is achieved.

< apparatus >

It will be understood by those skilled in the art that in the electronic technology field, the above method can be embodied in products by software, hardware and a combination of software and hardware, and those skilled in the art can easily generate a device for audio playing based on the above disclosed method, the device for audio playing comprises a means for executing each operation in the method for audio playing according to the above embodiment. For example, the apparatus comprises: the device comprises a Weex layer, a first operation module and a second operation module, wherein the first operation module is used for enabling the Weex layer to obtain a first operation input aiming at a Weex audio playing interface; the device is used for enabling the Weex layer to obtain corresponding playing data information from a Native layer through an active calling interface corresponding to the first operation in a preset communication protocol; and a device for enabling the Weex layer to update the Weex audio playing interface according to the playing data information; the active calling type interface is used for the Weex layer to actively call the corresponding audio playing function in the Native layer.

It will be apparent to those skilled in the art that the apparatus for audio playback may be implemented in various ways. For example, a device for audio playback may be implemented by instructing a configuration processor. For example, the instructions may be stored in ROM and read from ROM into a programmable device to implement a device for audio playback when the device is started. For example, the apparatus for audio playback may be solidified into a dedicated device (e.g., ASIC). The devices for audio playback may be divided into separate units or they may be combined together. The apparatus for audio playback may be implemented by one of the various implementations described above, or may be implemented by a combination of two or more of the various implementations described above.

< client terminal device >

At least one embodiment according to the present disclosure may be implemented in a client device (or client application) such as a cell phone, tablet, etc.

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 apparatus 3010 for audio playback. The apparatus 3010 for audio playback may be an apparatus for audio playback according to the above-described embodiments.

Furthermore, as mentioned above, a client device may also be generated based on the method described above, which may be designed to perform the steps of the solution of the embodiment described with reference to fig. 1.

It is well known to those skilled in the art that with the development of electronic information technology such as large scale integrated circuit technology and the trend of software hardware, it has been difficult to clearly divide the software and hardware boundaries of a computer system. As any of the operations may be implemented in software or hardware. Execution of any of the instructions may be performed by hardware, as well as by 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, and the like. A software implementation and a hardware implementation are equivalent for the skilled person. The skilled person can choose software or hardware to implement the above described scheme as desired. Therefore, specific software or hardware is not limited herein.

< electronic apparatus >

Any of the above embodiments may be implemented in an electronic device such as a cell phone, tablet, computer, etc. For example, the electronic device may include the client apparatus in the above embodiments.

Furthermore, fig. 4 shows a schematic block diagram of an electronic device according to an embodiment of the present 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, a ROM (read only memory), a RAM (random access memory), a nonvolatile memory such as a hard disk, and the like. The interface 4030 includes, for example, a USB interface, a headphone interface, and 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 panel, a touch panel, or the like. The input device 4060 may include, for example, a touch screen, a keyboard, and the like. A user can 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 present invention, its application, or uses.

In this embodiment, the memory 4020 is configured to store instructions that, when the electronic device 4000 is running, control the processor 4010 to perform the operations of the method for audio playback described above with reference to fig. 1. It should be understood by those skilled in the art that although a plurality of devices are shown in fig. 4, the present invention may only relate to some of the devices, for example, the processor 4010 and the memory 4020, etc. The skilled person can design the instructions according to the disclosed solution. How the instructions control the operation of the processor is well known in the art and will not be described in detail 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 therewith for causing a processor to implement various aspects of the present invention.

The computer readable storage medium may be a tangible device that can hold and store the instructions for use by the instruction execution device. The computer readable storage medium may be, for example, but not limited to, an electronic memory device, a magnetic memory device, an optical memory device, an electromagnetic memory device, a semiconductor memory 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: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a Static Random Access Memory (SRAM), a portable compact disc read-only memory (CD-ROM), a Digital Versatile Disc (DVD), a memory stick, a floppy disk, a mechanical coding device, such as punch cards or in-groove projection structures having instructions stored thereon, and any suitable combination of the foregoing. Computer-readable storage media as used herein is not to be construed as transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission medium (e.g., optical pulses through a fiber optic cable), or electrical signals transmitted through electrical 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 via 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 transmission, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. The network adapter 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.

The computer program instructions for carrying out operations of the present invention may be assembler 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 execute 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 type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made 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 an electronic circuit, such as a programmable logic circuit, a Field Programmable Gate Array (FPGA), or a Programmable Logic Array (PLA), with state information of computer-readable program instructions, which can execute the computer-readable program instructions.

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 storing the instructions comprises 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 flowchart 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, by software, and by a combination of software and hardware are equivalent.

Having described embodiments of the present invention, the foregoing description is intended to be exemplary, not exhaustive, and not 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 described embodiments. The terminology used herein is chosen in order to best explain the principles of the embodiments, the practical application, or improvements made to the technology 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

1. A method of audio playback, wherein the method comprises:

2. The method of claim 1, wherein the method further comprises:

3. The method of claim 1, wherein the unsolicited call class interface comprises at least: the audio player initializes the interface, obtains the current audio player data interface, the current playing data interface, the pause audio playing interface and the current playing second 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 playback interface includes at least: draggable progress bars, audio times, play control buttons, pop-up playlist directories, player cover drawings, and play information.

6. The method of claim 2, wherein the Native play control is displayed in a small window;

and the Native playing control displays current playing information.

7. The method of claim 2, wherein the method further comprises:

8. An apparatus for audio playback, comprising:

9. A client device comprising an apparatus for audio playback according to claim 8 or being designed for performing operations in a method of audio playback according to any of claims 1-7.

10. An electronic device comprising the client apparatus of claim 9; alternatively, the electronic device comprises a memory for storing instructions and a processor; the instructions are for controlling the processor to operate so as to carry out operations in the method of audio playback according to any one of claims 1 to 7.