nginx - There is sound when playing h264 encoded mp4 locally, but there is no sound when playing through the web page.
过去多啦不再A梦2017-05-16 17:23:31
0
2
1412
I used nginx to build a simple flv and mp4 streaming media server. When playing a certain mp4, there is only image and no sound, but there is sound when playing it directly locally. What may be the reason?
How to troubleshoot:
1. Can the browser directly open the file you have online (such as visiting http://xxx.com/a.mp4)? Can I download or play it directly through the url? Chrome and Firefox will not judge cross-domain issues, but IE and Safari have access restrictions. You first need to visit the URL of the MP4 resource in each browser to see what the HTTP response is.
2. On the basis of 1, if (a) cannot be accessed, then it must be an nginx configuration error, and tail nginx log troubleshooting (usually there is no chmod permission). (b) If only some browsers have problems, it may be a cross-domain problem, and Google search will solve it. (c) If you can all access it, then there is a problem with the configuration of your media player. Troubleshoot. If it doesn't work, just change the player.
If there are no problems with the encoding and player, the problem may occur on the network. If the network speed is too slow, such a problem may occur, because streaming media is divided into video and audio parts, and the bit rate of audio is generally relatively low. When the network speed cannot be guaranteed, there will usually be a problem of sound but no image.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
How to troubleshoot:
1. Can the browser directly open the file you have online (such as visiting http://xxx.com/a.mp4)? Can I download or play it directly through the url? Chrome and Firefox will not judge cross-domain issues, but IE and Safari have access restrictions. You first need to visit the URL of the MP4 resource in each browser to see what the HTTP response is.
2. On the basis of 1, if (a) cannot be accessed, then it must be an nginx configuration error, and tail nginx log troubleshooting (usually there is no chmod permission). (b) If only some browsers have problems, it may be a cross-domain problem, and Google search will solve it. (c) If you can all access it, then there is a problem with the configuration of your media player. Troubleshoot. If it doesn't work, just change the player.
If there are no problems with the encoding and player, the problem may occur on the network. If the network speed is too slow, such a problem may occur, because streaming media is divided into video and audio parts, and the bit rate of audio is generally relatively low. When the network speed cannot be guaranteed, there will usually be a problem of sound but no image.