icecast

问题 So i'm using the Webcaster Browser Client and I also got the Webcast NodeJS example server working locally as well. I'm receiving the data from the client in the server e.g Mon Jul 16 2018 14:31:11 GMT+0300 (FLE Daylight Time) -- Got 1252 bytes of binary data But I've been googling for a couple of days and can't seem to find information on how to actually pass those chunks of data to my Icecast server. Additional Info that might be relevant: Icecast server : 2.4.3; Platform: Windows; Server

问题 I have Icecast 2.4.4 running on a Windows box at sub.domain.org. My website is on a different server at domain.org. When I SSH into my Linux host shell and run curl to the mount point I get a response of 400, but if I do wget I get a response of 200. How can this be? # wget https://sub.domain.org/live.mp3 --2018-12-19 17:52:58-- https://sub.domain.org/live.mp3 Resolving sub.domain.org... 111.111.111.111 Connecting to sub.domain.org|111.111.111.111|:443... connected. HTTP request sent,

问题 Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 5 months ago . Improve this question I am having an issue with trying to get icecast to work on port 80. It works on it's default but when i try to set it to port 80 everything breaks. I have made sure that the firewall is allowing connections on port 8000 as well as port 80 and 443. I have also

问题 Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 5 months ago . Improve this question I am having an issue with trying to get icecast to work on port 80. It works on it's default but when i try to set it to port 80 everything breaks. I have made sure that the firewall is allowing connections on port 8000 as well as port 80 and 443. I have also

来源： https://stackoverflow.com/questions/53748382/icecast-stream-repeats-after-interruptions-on-mobile-devices

来源： https://stackoverflow.com/questions/53748382/icecast-stream-repeats-after-interruptions-on-mobile-devices

来源： https://stackoverflow.com/questions/53748382/icecast-stream-repeats-after-interruptions-on-mobile-devices

问题 I am getting icecast metadata using jquery XMLHttpRequest. There is status.xsl and status-json.xsl url. How do I know when do I use each one, if I only have icecast radio url? For example this radio works with both of them: http://149.56.195.94:8416/status.xsl http://149.56.195.94:8416/status-json.xsl This radio throws an error using status-json.xsl http://stream.radios-arra.fr:8000/status.xsl http://stream.radios-arra.fr:8000/status-json.xsl - ERROR: Could not parse XSLT file 回答1: If you are

问题 When I start receiving the live audio (radio) stream (e.g. MP3 or AAC) I think the received data are not kind of raw bitstream (i.e. raw encoder output), but they are always wrapped into some container format. If this assumption is correct, then I guess I cannot start streaming from arbitrary place of the stream, but I have to wait to some sync byte. Is that right? Is it usual to have some sync bytes? Is there any header following the sync byte, from which I can guess the used codec, number

问题 When I start receiving the live audio (radio) stream (e.g. MP3 or AAC) I think the received data are not kind of raw bitstream (i.e. raw encoder output), but they are always wrapped into some container format. If this assumption is correct, then I guess I cannot start streaming from arbitrary place of the stream, but I have to wait to some sync byte. Is that right? Is it usual to have some sync bytes? Is there any header following the sync byte, from which I can guess the used codec, number