CN110545488A - Audio and video zero-fault playing method and system in web player publishing - Google Patents
Audio and video zero-fault playing method and system in web player publishing Download PDFInfo
- Publication number
- CN110545488A CN110545488A CN201910893633.2A CN201910893633A CN110545488A CN 110545488 A CN110545488 A CN 110545488A CN 201910893633 A CN201910893633 A CN 201910893633A CN 110545488 A CN110545488 A CN 110545488A
- Authority
- CN
- China
- Prior art keywords
- player
- version
- audio
- video
- file
- 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
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/45—Management operations performed by the client for facilitating the reception of or the interaction with the content or administrating data related to the end-user or to the client device itself, e.g. learning user preferences for recommending movies, resolving scheduling conflicts
- H04N21/458—Scheduling content for creating a personalised stream, e.g. by combining a locally stored advertisement with an incoming stream; Updating operations, e.g. for OS modules ; time-related management operations
- H04N21/4586—Content update operation triggered locally, e.g. by comparing the version of software modules in a DVB carousel to the version stored locally
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
- H04N21/81—Monomedia components thereof
- H04N21/8166—Monomedia components thereof involving executable data, e.g. software
- H04N21/8173—End-user applications, e.g. Web browser, game
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
- H04N21/81—Monomedia components thereof
- H04N21/8166—Monomedia components thereof involving executable data, e.g. software
- H04N21/8193—Monomedia components thereof involving executable data, e.g. software dedicated tools, e.g. video decoder software or IPMP tool
Landscapes
- Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Signal Processing (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Databases & Information Systems (AREA)
- Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
Abstract
The invention provides an audio and video zero fault playing method and system in web player publishing, wherein the method comprises the following steps: embedding a player.js file into an audio and video page, wherein the player.js file has addresses of a first version player and a second version player; when an audio and video playing request is received, downloading and calling a first version player to play audio and video through a player. Judging whether the first version player successfully plays the audio and video; if so, playing the audio and video through the first version player; and if not, the first version player feeds error information back to the player.js file, and the player.js downloads and calls the second version player to play the audio and video. The method has a defensive mechanism, prepares counter measures in advance for possible abnormal conditions in the future, can obviously improve the publishing stability of the web player, avoids unexpected audio and video playing faults, provides powerful support for rapid testing publishing of the player, and greatly lightens the pressure and workload of testers.
Description
Technical Field
The invention relates to the technical field of multimedia, in particular to an audio and video zero-fault playing method and system in web player publishing.
Background
The existing web player is generally integrated to pages of different clients in an external embedding mode, the use modes are various, and particularly, some irregular use modes exist, so that the condition that individual clients often play the files in the player version, and the player has to go back is caused. Especially for the online education industry, students who watch videos are numerous (including students at school), and version failure has a great influence. The instability of player publishing is always a difficult problem in the industry, and the traditional publishing mode at present replaces an old player file with a new player file, so that only one formal player version exists on line, and the publishing mode has no defensive mechanism, namely, no corresponding measures are prepared in advance for possible future abnormal conditions, no support force is provided for the abnormal conditions, and the rollback phenomenon is easy to occur. In addition, the mode of directly replacing the old version player with the new version player file has the advantages of low test efficiency, high test coverage requirement, incapability of realizing accurate test, high pressure of testers and long version sending period.
disclosure of Invention
aiming at the defects of the prior art, the invention provides an audio and video zero-fault playing method and system in web player publishing, which greatly improve the stability of player publishing, avoid the occurrence of unexpected audio and video playing faults, provide powerful support for rapid player testing publishing and greatly reduce the pressure and workload of testers.
the technical scheme of the invention is realized as follows:
A zero-fault audio and video playing method in web player publishing comprises the following steps:
Embedding a player.js file on an audio and video page, wherein the player.js file has two player addresses: a first version player, a second version player;
When an audio and video playing request is received, downloading and calling a first version player to play audio and video through a player.
Judging whether the first version player successfully plays the audio and video; if so, continuing to play the audio and video through the first version player; if not, the first version player feeds error information back to the player.
The player.js file downloads and calls a second version player to play the audio and video after receiving the error information;
When the first version player is updated, the file name of the first version player before updating is changed into the file name of the second version player, namely the first version player before updating is changed into the second version player.
optionally, the step of downloading and calling the first version player to play the audio and video through the player.js file when the audio and video playing request is received includes:
When receiving an audio and video playing request, player.js tries to download and call a first version player;
Initializing a first version player and generating a corresponding player DOM element; and if the initialization is successful, loading the audio and video resources through the first version player for playing.
Optionally, the step of downloading and calling a second version player to play the audio and video after the player.js file receives the error information includes:
after receiving error information of playing failure of the first-version player, the player DOM element is removed by using a removecold function so as to destroy the first-version player;
Js file download and call a second version player;
and initializing the second version player, plugging the second version player into the original player DOM element, and loading the audio and video resources to play by using the second version player.
Optionally, the method further comprises the following steps:
When the play.js file has the behavior of downloading the second version player, the play.js file sends an error log to the server, a tester checks a related user page according to the received error log and issues a repair version of the first version player, and the second version player is unchanged at the moment, so that the usability of the second version player is ensured.
A zero-fault audio-video playing system in web player publishing comprises
an embedding module, configured to embed a player.js file on an audio/video page, where the player.js file has two player addresses: a first version player, a second version player;
The first calling module is used for downloading and calling a first version player to play the audio and video through a player.
the judging module is used for judging whether the first version player successfully plays the audio and video; if so, continuing to play the audio and video through the first version player; if not, the first version player feeds error information back to the player.
the second calling module is used for downloading the player.js file after receiving the error information and calling a second version player to play the audio and video;
in the embedded module, the first version player is a new version player, and when the first version player is updated, the file name of the first version player before updating is changed into the file name of the second version player, that is, the first version player before updating is changed into the second version player.
Optionally, the first calling module includes
A first player calling unit, configured to try to download and call a first version player when receiving an audio/video playing request;
The first playing unit is used for initializing the first version player and generating a corresponding player DOM element; and when the initialization is successful, loading the audio and video resources for playing through the first version player.
Optionally, the second calling module includes
A removing unit, configured to remove a DOM element of the player by using a removecield function to destroy the first version player after the player.js file receives error information that the first version player fails to play;
a second player calling unit, configured to download the player.js file and call a second version player;
And the second playing unit is used for initializing the second version player, plugging the second version player into the original player DOM element, and loading the audio and video resources by using the second version player for playing.
Optionally, also include
And the repair module is used for sending an error log to the server when the play.js file has a behavior of downloading the second version player, and a tester checks a related user page according to the received error log and issues a repair version of the first version player, wherein the second version player is unchanged at the moment, so that the usability of the second version player is ensured.
compared with the prior art, the invention also has the following advantages: the invention calls a web player through a player.js file embedded in an audio and video page, wherein the player.js file has two player addresses: the first version player is a new version player, when the player receives an audio and video playing request, the first version player is preferentially downloaded and called to play the audio and video, and if the playing fails, the second version player is automatically downloaded and called to play the audio and video, so that the occurrence of unexpected audio and video playing faults is avoided. The invention not only can ensure the usability of the web player during version issuing, but also provides powerful support for the rapid testing version issuing of the player, thereby greatly reducing the pressure and the workload of testers, and the service conditions of the new version player in different client pages can be known in time by checking the error log received by the server.
drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a flowchart of an embodiment of a method for zero-fault playback of audio and video in web player publishing according to the present invention;
FIG. 2 is a block diagram of an embodiment of an audio/video zero-fault playing system in a web player release according to the present invention;
FIG. 3 is a block diagram of a first call unit;
Fig. 4 is a block diagram of the second call module.
Detailed Description
the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that the terms "first," "second," "third," "fourth," and the like (if any) in the description and claims of this application and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are, for example, capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Referring to fig. 1, an audio and video zero fault playing method in web player publishing disclosed by one embodiment of the present invention includes the following steps:
S101, embedding a player.js file on an audio/video page, where the player.js file has two player addresses: a first version player (e.g., player.swf), a second version player (e.g., old _ player.swf);
In the embodiment of the present invention, the player uses dual versions, that is, a first version player (e.g., player.swf) and a second version player (e.g., old _ player.swf), and the first version player is a new version player and the second version player is an old version player; when an audio and video playing request is received, the first version player is downloaded and called preferentially to play audio and video, and if the playing fails, the second version player is downloaded and called automatically to play audio and video, so that the occurrence of unexpected audio and video playing faults is avoided.
Furthermore, when the first version player is updated, the file name of the first version player before updating is changed to the file name of the second version player (for example, player.swf is changed to old _ player.swf), that is, the first version player before updating is changed to the second version player, so that the last stable player version is taken as the alternative player every time the new version player is released, thereby avoiding the occurrence of unexpected audio/video playing failure.
s102, when an audio and video playing request is received, downloading and calling a first version player to play audio and video through a player.
In the embodiment of the invention, the first version player (namely, the new version player) is preferentially called to play the audio and video through player.
S103, judging whether the first version player successfully plays the audio and video; if so, continuing to play the audio and video through the first version player; if not, the first version player feeds error information back to the player.
in the embodiment of the invention, when the first version player (namely, the new version player) fails to play, the error information is transmitted to player.
and S104, downloading and calling a second version player to play the audio and video after the player.js file receives the error information.
in the embodiment of the invention, after receiving the error information, the player js downloads and calls a second version player (namely an old version player) to play the audio and video, wherein the second version player is a stable old version player which is verified on line, thereby avoiding the occurrence of unexpected audio and video playing faults.
further, step S102 includes the following sub-steps:
S1021, when receiving an audio/video play request, player.js attempts to download and invoke a first version player;
S1022, initializing the first version player, and generating a corresponding player DOM element; and if the initialization is successful, loading the audio and video resources through the first version player for playing.
In the embodiment of the present invention, the web player initialization refers to a process of generating a player according to specified attributes (width, height, etc.).
Further, step S104 includes the following sub-steps:
step S1041, after receiving the error information of the playing failure of the first version player, the player js removes a player DOM element by using a removecold function so as to achieve the purpose of destroying the first version player;
step S1042, the player.js file downloads and calls a second version player;
and step S1043, initializing the second version player, plugging the second version player into the original player DOM element, and loading the audio and video resources to play by using the second version player.
In the embodiment of the invention, when the first version player fails to play, the first version player needs to be replaced by the second version player, and the position of the player on the page is unchanged. Therefore, the DOM element of the first version player needs to be removed first to destroy the first version player; and then downloading and calling the second version player, initializing the second version player, and plugging the second version player into the DOM element of the original player so as to realize replacement of the player.
Further, the audio and video zero fault playing method in web player publishing further comprises the following steps:
And S105, when the play.js file has the behavior of downloading the second version player, the play.js file sends an error log to the server, a tester checks a related user page according to the received error log and issues a repair version of the first version player, and the second version player is unchanged at the moment so as to ensure the usability of the second version player.
after the new version of player is released, if a client uses a second version of player, it is indicated that the first version of player is likely to have problems, the player.js file sends an error log to the server, and a tester receives the error log and then checks a related client page. If the first version player is determined to have a problem, a repair version is sent, the last version is called a problem version, the problem version cannot be changed into a second version player, and the second version player should be kept unchanged, so as to ensure that the second version player is always available.
In the embodiment of the invention, when the first version player fails to play, the second version player is automatically called to play, so that unexpected play faults can not occur, and the pressure of testing personnel is greatly reduced. When the testing time is urgent, the updating point of the new version player can be tested only (if the automatic regression testing can be matched, the effect is better), and the method is particularly suitable for the conditions that the customer needs to be responded preferentially and the version is sent out emergently.
In summary, the present invention calls the web player through the player.js file embedded in the audio/video page, where there are two player addresses: the first version player is a new version player, when an audio and video playing request is received, the first version player is preferentially downloaded and called to play audio and video, and if the playing fails, the second version player is automatically downloaded and called to play audio and video, so that the occurrence of unexpected audio and video playing faults is avoided. The invention has a defensive mechanism, can not only ensure the usability of the web player during version sending, but also provide powerful support for the rapid testing version sending of the player, greatly reduce the pressure and workload of testers, and can know the use conditions of the new version player in different client pages in time by checking the error logs received by the server.
Referring to fig. 2, an embodiment of the present invention further provides an audio/video zero-fault playing system in web player publishing, including
An embedding module 10, configured to embed a player.js file on an audio/video page, where the player.js file has two player addresses: a first version player (e.g., player.swf), a second version player (e.g., old _ player.swf);
In the embodiment of the invention, dual-version players, namely a first-version player and a second-version player, are embedded in a page through an embedding module 10, wherein the first-version player is a new-version player, and the second-version player is an old-version player; when an audio and video playing request is received, the first version player is downloaded and called preferentially to play audio and video, and if the playing fails, the second version player is downloaded and called automatically to play audio and video, so that the occurrence of unexpected audio and video playing faults is avoided.
further, when the first version player is updated, the file name of the first version player before updating is changed to the file name of the second version player (for example, player.swf is changed to old _ player.swf), that is, the first version player before updating becomes the second version player. Therefore, when a new player is released each time, the last stable player version is taken as an alternative player, so that unexpected audio and video playing faults are avoided.
The first calling module 20 is configured to download and call a first version player to play the audio and video through a player.
in the embodiment of the present invention, the first calling module 20 makes the player.js preferentially call the first version player (new version player) to play the audio and video, so that the user can experience the new function of the new version player.
the judging module 30 is configured to judge whether the first version player successfully plays the audio/video; if so, continuing to play the audio and video through the first version player; if not, the first version player feeds error information back to the player.
In the embodiment of the present invention, the judgment module 30 judges whether the audio/video playing fails, and after the playing of the first version player (i.e. the new version player) fails, the error information is transmitted to player.
And the second calling module 40 is used for downloading the player.js file after receiving the error information and calling a second version player to play the audio and video.
In the embodiment of the invention, after the player.js receives the error information, the second calling module 40 downloads and calls the second version player to play the audio and video, wherein the second version player is a stable old version player which is verified on line, so that the occurrence of unexpected audio and video playing faults is avoided.
Further, the first calling module 20 comprises
A first player calling unit 201, configured to try to download and call a first version player when receiving an audio/video playing request;
a first playing unit 202, configured to initialize a first version player and generate a corresponding player DOM element; and when the initialization is successful, loading the audio and video resources for playing through the first version player.
Therein, web player initialization refers to a process of generating a player according to specified attributes (wide, high, etc.).
further, the second calling module 40 comprises
A removing unit 401, configured to remove a DOM element of the player by using a removecold function after the player.js file receives error information that the playing of the first-version player fails, so as to destroy the first-version player;
A second player calling unit 402, configured to download the player.js file and call a second version player;
The second playing unit 403 initializes the second version player, plugs the second version player into the original DOM element, and loads the audio/video resource for playing by using the second version player.
When the first version player fails to play, the first version player needs to be replaced by a second version player, and the position of the player on the page is unchanged. Therefore, the DOM element of the first version player needs to be removed first to destroy the first version player; and then downloading and calling the second version player, initializing the second version player, and plugging the second version player into the original DOM element so as to realize the replacement of the player.
furthermore, the audio and video zero-fault playing system in web player publishing also comprises
And the repair module 50 is configured to send an error log to the server when the player.js file has a behavior of downloading the second version player, and a tester checks a relevant user page according to the received error log and issues a repair version of the first version player, where the second version player is unchanged at this time, so as to ensure the usability of the second version player.
After the new version of player is released, if a client uses a second version of player, it is indicated that the first version of player is likely to have problems, the player.js file sends an error log to the server, and a tester receives the error log and then checks a related client page. If the first version player is determined to have a problem, a repair version is sent, the last version is called a problem version, the problem version cannot be changed into a second version player, and the second version player should be kept unchanged, so as to ensure that the second version player is always available.
In the embodiment of the invention, when the first version player fails to play, the second version player is automatically called to play, so that unexpected play faults can not occur, and the pressure of testing personnel is greatly reduced. When the testing time is urgent, the updating point of the new version player can be tested only (if the automatic regression testing can be matched, the effect is better), and the method is particularly suitable for the conditions that the customer needs to be responded preferentially and the version is sent out emergently.
in summary, the present invention calls the web player through the player.js file embedded in the audio/video page, where there are two player addresses: the first version player is a new version player, when an audio and video playing request is received, the first version player is preferentially downloaded and called to play audio and video, and if the playing fails, the second version player is automatically downloaded and called to play audio and video, so that the occurrence of unexpected audio and video playing faults is avoided. The invention has a defensive mechanism, can not only ensure the usability of the web player during version sending, but also provide powerful support for the rapid testing version sending of the player, greatly reduce the pressure and workload of testers, and can know the use conditions of the new version player in different client pages in time by checking the error logs received by the server.
The above disclosure provides many different embodiments or examples for implementing different configurations of embodiments of the invention. In order to simplify the disclosure of embodiments of the invention, the components and arrangements of specific examples are described below. Of course, they are merely examples and are not intended to limit the present invention. Furthermore, embodiments of the invention may repeat reference numerals and/or reference letters in the various examples, which have been repeated for purposes of simplicity and clarity and do not in themselves dictate a relationship between the various embodiments and/or arrangements discussed. In addition, embodiments of the present invention provide examples of various specific processes and materials, but one of ordinary skill in the art may recognize applications of other processes and/or use of other materials.
in the description herein, references to the description of the terms "an embodiment," "some embodiments," "an illustrative embodiment," "an example," "a specific example" or "some examples" or the like mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and alternate implementations are included within the scope of the preferred embodiment of the present invention in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present invention.
The logic and/or steps represented in the flowcharts or otherwise described herein, such as an ordered listing of executable instructions that can be considered to implement logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processing module-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
It should be understood that portions of embodiments of the present invention may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), a Graphic Processor (GPU), a Tensor Processing Unit (TPU), and the like.
it will be understood by those skilled in the art that all or part of the steps carried by the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, which may be stored in a computer readable storage medium, and when the program is executed, the program includes one or a combination of the steps of the method embodiments.
In addition, functional units in the embodiments of the present invention may be integrated into one processing module, or each unit may exist alone physically, or two or more units are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may also be stored in a computer readable storage medium.
The storage medium mentioned above may be a read-only memory, a magnetic or optical disk, etc.
although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention, and that variations, modifications, substitutions and alterations can be made to the above embodiments by those of ordinary skill in the art within the scope of the present invention.
Claims (8)
1. A zero-fault audio and video playing method in web player publishing is characterized by comprising the following steps:
Embedding a player.js file on an audio and video page, wherein the player.js file has two player addresses: a first version player, a second version player;
When an audio and video playing request is received, downloading and calling a first version player to play audio and video through a player.
judging whether the first version player successfully plays the audio and video; if so, continuing to play the audio and video through the first version player; if not, the first version player feeds error information back to the player.
The player.js file downloads and calls a second version player to play the audio and video after receiving the error information;
when the first version player is updated, the file name of the first version player before updating is changed into the file name of the second version player, namely the first version player before updating is changed into the second version player.
2. The method for playing audio/video zero fault in web player release according to claim 1, wherein the step of downloading and calling the first version player to play audio/video through player.
When receiving an audio and video playing request, player.js tries to download and call a first version player;
Initializing a first version player and generating a corresponding player DOM element; and if the initialization is successful, loading the audio and video resources through the first version player for playing.
3. the method for playing audio/video zero fault in web player publishing according to claim 2, wherein the step of downloading and calling a second version player to play the audio/video after the player.js file receives the error message comprises:
After receiving error information of playing failure of the first-version player, the player DOM element is removed by using a removecold function so as to destroy the first-version player;
Js file download and call a second version player;
And initializing the second version player, plugging the second version player into the original player DOM element, and loading the audio and video resources to play by using the second version player.
4. The audio-video zero-fault playing method in web player release as claimed in claim 1, further comprising the steps of:
When the play.js file has the behavior of downloading the second version player, the play.js file sends an error log to the server, a tester checks a related user page according to the received error log, and issues a repair version of the first version player, and the second version player is not changed at this time.
5. A zero-fault audio and video playing system in web player version release is characterized by comprising
An embedding module, configured to embed a player.js file on an audio/video page, where the player.js file has two player addresses: a first version player, a second version player;
the first calling module is used for downloading and calling a first version player to play the audio and video through a player.
The judging module is used for judging whether the first version player successfully plays the audio and video; if so, continuing to play the audio and video through the first version player; if not, the first version player feeds error information back to the player.
The second calling module is used for downloading the player.js file after receiving the error information and calling a second version player to play the audio and video;
In the embedded module, the first version player is a new version player, and when the first version player is updated, the file name of the first version player before updating is changed into the file name of the second version player, that is, the first version player before updating is changed into the second version player.
6. The system as set forth in claim 6, wherein the first calling module comprises
a first player calling unit, configured to try to download and call a first version player when receiving an audio/video playing request;
The first playing unit is used for initializing the first version player and generating a corresponding player DOM element; and when the initialization is successful, loading the audio and video resources for playing through the first version player.
7. The system of claim 7, wherein the second calling module comprises
A removing unit, configured to remove a DOM element of the player by using a removecield function to destroy the first version player after the player.js file receives error information that the first version player fails to play;
A second player calling unit, configured to download the player.js file and call a second version player;
and the second playing unit is used for initializing the second version player, plugging the second version player into the original player DOM element, and loading the audio and video resources by using the second version player for playing.
8. the audio-visual zero-fault playback system in web player release of claim 6, further comprising
And the repair module is used for sending an error log to the server when the play.js file has a behavior of downloading the second version player, and the tester checks the related user page according to the received error log and issues the repair version of the first version player, wherein the second version player is unchanged.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910893633.2A CN110545488A (en) | 2019-09-20 | 2019-09-20 | Audio and video zero-fault playing method and system in web player publishing |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910893633.2A CN110545488A (en) | 2019-09-20 | 2019-09-20 | Audio and video zero-fault playing method and system in web player publishing |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110545488A true CN110545488A (en) | 2019-12-06 |
Family
ID=68714131
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910893633.2A Pending CN110545488A (en) | 2019-09-20 | 2019-09-20 | Audio and video zero-fault playing method and system in web player publishing |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110545488A (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1889041A (en) * | 2006-08-02 | 2007-01-03 | 华为技术有限公司 | Software staging and back spacing method |
| CN101207800A (en) * | 2007-12-04 | 2008-06-25 | 深圳市同洲电子股份有限公司 | Method and system for updating set-top box VOD player |
| CN104778038A (en) * | 2015-03-20 | 2015-07-15 | 四川长虹电器股份有限公司 | Method for realizing universal HTML5 (hypertext markup language 5) player for embedded browser |
| US20150229987A1 (en) * | 2013-12-24 | 2015-08-13 | Lg Electronics Inc. | Digital device and method for controlling the same |
| CN106028142A (en) * | 2016-05-25 | 2016-10-12 | 广东欧珀移动通信有限公司 | Upgrading control method and upgrading control apparatus for playing devices |
| CN207182261U (en) * | 2017-04-13 | 2018-04-03 | 重庆科创职业学院 | A kind of software upgrading download system |
| CN108509291A (en) * | 2018-02-27 | 2018-09-07 | 广东欧珀移动通信有限公司 | Application program operation exception restorative procedure and system and mobile terminal |
-
2019
- 2019-09-20 CN CN201910893633.2A patent/CN110545488A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1889041A (en) * | 2006-08-02 | 2007-01-03 | 华为技术有限公司 | Software staging and back spacing method |
| CN101207800A (en) * | 2007-12-04 | 2008-06-25 | 深圳市同洲电子股份有限公司 | Method and system for updating set-top box VOD player |
| US20150229987A1 (en) * | 2013-12-24 | 2015-08-13 | Lg Electronics Inc. | Digital device and method for controlling the same |
| CN104778038A (en) * | 2015-03-20 | 2015-07-15 | 四川长虹电器股份有限公司 | Method for realizing universal HTML5 (hypertext markup language 5) player for embedded browser |
| CN106028142A (en) * | 2016-05-25 | 2016-10-12 | 广东欧珀移动通信有限公司 | Upgrading control method and upgrading control apparatus for playing devices |
| CN207182261U (en) * | 2017-04-13 | 2018-04-03 | 重庆科创职业学院 | A kind of software upgrading download system |
| CN108509291A (en) * | 2018-02-27 | 2018-09-07 | 广东欧珀移动通信有限公司 | Application program operation exception restorative procedure and system and mobile terminal |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10958548B2 (en) | Generating production server load activity for a test server | |
| US9417865B2 (en) | Determining when to update a package manager software | |
| US9158577B2 (en) | Immediately launching applications | |
| US20160371134A1 (en) | Resilience as a Service | |
| CN108255708B (en) | Method, device, storage medium and equipment for accessing production file in test environment | |
| US11726800B2 (en) | Remote component loader | |
| KR20130077846A (en) | Exception handling test device and method thereof | |
| CN111813495A (en) | Node testing method and device, storage medium and electronic device | |
| JP5147216B2 (en) | Method, system and computer program for measuring autonomic capability of a computing system | |
| CN109471799B (en) | Method, device, storage medium and terminal for deploying demand environment | |
| CN106512397A (en) | Data loading method for game server and game server | |
| CN111147331A (en) | Server network card interaction test method, system, terminal and storage medium | |
| CN113721957B (en) | Automatic test method, device and system for firmware deployment upgrade of embedded equipment | |
| US9043440B2 (en) | Automatic WSDL download of client emulation for a testing tool | |
| CN110545488A (en) | Audio and video zero-fault playing method and system in web player publishing | |
| CN109922101A (en) | A kind of method, apparatus and server for realizing specific transactions in the terminal | |
| CN115276844B (en) | Communication module testing method and device, storage medium and electronic equipment | |
| CN110716730A (en) | Gray scale distribution method, device, equipment and computer readable storage medium | |
| CN115190293A (en) | Dial testing method and device, electronic equipment and computer storage medium | |
| CN111143347A (en) | Object storage data consistency test method, system, terminal and storage medium | |
| CN102487459A (en) | Monitoring method for web television system and device thereof | |
| CN112905415B (en) | Serial port log file acquisition method and device and related components | |
| US20220066917A1 (en) | Candidate program release evaluation | |
| CN111400117B (en) | Method for automatically testing Ceph cluster | |
| CN113010187A (en) | Application installation 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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20191206 |