As we all know, easyplayer player series is a very stable and comprehensive video player, covering the playing versions of various systems such as PC, mobile phone and web page. Moreover, easyplayer player has been integrated into many streaming media platforms such as easygbs, easynvr and easycvr to experience the video playing effect of h265 coding.
Some customers will encounter some calling problems when using easyplayer player. For example, it can be played on easygbs, but it can not be played with easyplayer player after calling the over-current address, and an error is reported on the console:
This is a common error of easyplayer player. There are two main reasons. Let’s analyze and explain it one by one.
This video stream is h265, so we need to play it with our version of h265 player. The reason for this error is that the libdecoder.wasm file is not found. It is likely that the player version used by the user is a demo above and below GitHub, not 265, but H5 player.
In this case, the libdecoder.wasm file should be added to the demo of h265.
The customer does not start the player with the service, but directly starts it with the demo file, which will also lead to an error. Our player is service-based. We should put the demo file in the root directory of the service instead of another directory.
- Windows / Android / IOS / Linux platform h265 streaming media player easyplayer.js deployment error
- What is the reason why the easygbs client calls token and reports an error “refer to set unsafe header” cookie “
- Easygbs runs with an error of too many open files and cannot play the video stream. How to adjust?
- the media could not be loaded, either because the server or network failed o
- Failed to execute ‘toDataURL’ on ‘HTMLCanvasElement’: Tainted canvases may not be exported [Solved]
- Google service framework and installation method and Google play error resolution!!
- MediaPlayer error (1, -2147483648) [How to Solve]
- error loading stream: ID not found on server
- Git Error: The requested URL returned error: 403 Forbidden while accessing