Easyplayer consumes traffic but does not play video and reports an error libdecoder Wasm404 troubleshooting

EasyPlayer The player series provides a very easy to use SDK And API Interface , User pass API Call can be very fast to develop their own applications , Second development . New version of the EasyPlayer Because of support 265 Web play , So many users are integrating .

Some users use EasyPlayer The player will get the stream address and put it in it , It shows that there is traffic consumption , But there is no picture playing , And it appears libDecoder.wasm404- Error report not found .

Generally speaking, this kind of problem is H265 Problems caused by video streaming , And the customer is close to success , The reason for this problem is libDecoder.wasm The file is in the wrong place , We check it remotely , See that the customer really easyplayer The file is placed under the root directory of the service ：

however libDecoder.wasm This file is also placed in EasyPlayer It's in the document , This will lead to missing wasm Error reporting of documents .

libDecoder.wasm The correct position of is and EasyPlayer File flush , The two are in place localhost below , Belong to the same level of relationship , So you can play it normally H265 Video streaming .

EasyPlayer The player series project uses high performance EasyRTSPClient Components , Its low delay control is in the leading position in the industry , Have Windows、Android、iOS Stable running versions of the three platforms ,EasyPlayer.js And support Linux platform , It's the best choice for multiple platforms in the player field .EasyPlayer The player has been integrated TSINGSEE In Qingxi video platform , Support video playback in multiple encoding formats , We welcome you to understand and test .