From inetken at gmail.com Mon Apr 2 16:52:09 2018 From: inetken at gmail.com (Inetken) Date: Mon, 2 Apr 2018 09:52:09 -0700 Subject: [Icecast] NAT and Playlist Question Message-ID: Brief backstory, previous admin is gone and the previous server died. What I could gather was it may have been running Icecast. I setup Icecast on a new CentOS 7 server and the server sits behind a firewall. The links from the users web site points to and internal address for internal users and an link to an external address. I created a listen.pls playlist with the following: [playlist] NumberOfEntries=1 File1=http://:8000/ The website points to this playlist file and it works fine. However, when I use the external link offsite I get an error that it cannot download the listen.pls file and won't play the stream. Should this work as I have it configured? How should I configure Icecast to work behind a NAT firewall for internal and external users? Thanks, Ken -------------- next part -------------- An HTML attachment was scrubbed... URL: From larry at acbradio.org Mon Apr 2 17:18:46 2018 From: larry at acbradio.org (Larry Turnbull) Date: Mon, 02 Apr 2018 17:18:46 +0000 Subject: [Icecast] NAT and Playlist Question In-Reply-To: References: Message-ID: <00c901d3caa6$a7957c50$f6c074f0$@acbradio.org> Do you have access to the firewall settings? If you are going to use port 8000 it needs to be opened for incoming and outgoing traffic. When most firewalls are activated they have port 8000 closed by default. Larry From: Icecast On Behalf Of Inetken Sent: Monday, April 2, 2018 11:52 AM To: icecast at xiph.org Subject: [Icecast] NAT and Playlist Question Brief backstory, previous admin is gone and the previous server died. What I could gather was it may have been running Icecast. I setup Icecast on a new CentOS 7 server and the server sits behind a firewall. The links from the users web site points to and internal address for internal users and an link to an external address. I created a listen.pls playlist with the following: [playlist] NumberOfEntries=1 File1=http://:8000/ The website points to this playlist file and it works fine. However, when I use the external link offsite I get an error that it cannot download the listen.pls file and won't play the stream. Should this work as I have it configured? How should I configure Icecast to work behind a NAT firewall for internal and external users? Thanks, Ken -------------- next part -------------- An HTML attachment was scrubbed... URL: From awi3 at live.com Mon Apr 2 17:00:23 2018 From: awi3 at live.com (Alan Bowness) Date: Mon, 2 Apr 2018 17:00:23 +0000 Subject: [Icecast] NAT and Playlist Question Message-ID: Look at port forwarding 8000 to the local IP address of the server behind your router. But check the port number in icecast.xml. That?s my guess, but I?m not an expert. From: Inetken Sent: Monday, April 02, 2018 5:52 PM To: icecast at xiph.org Subject: [Icecast] NAT and Playlist Question However, when I use the external link offsite I get an error that it cannot download the listen.pls file and won't play the stream. Should this work as I have it configured? How should I configure Icecast to work behind a NAT firewall for internal and external users? Thanks, Ken -------------- next part -------------- An HTML attachment was scrubbed... URL: From inetken at gmail.com Mon Apr 2 17:41:10 2018 From: inetken at gmail.com (Inetken) Date: Mon, 2 Apr 2018 10:41:10 -0700 Subject: [Icecast] NAT and Playlist Question In-Reply-To: <00c901d3caa6$a7957c50$f6c074f0$@acbradio.org> References: <00c901d3caa6$a7957c50$f6c074f0$@acbradio.org> Message-ID: The port should be opened, as it was working before, but that was a while ago. I'll have the network group double check. Ken On Mon, Apr 2, 2018 at 10:18 AM, Larry Turnbull wrote: > Do you have access to the firewall settings? > > > > If you are going to use port 8000 it needs to be opened for incoming and > outgoing traffic. > > > > When most firewalls are activated they have port 8000 closed by default. > > > > Larry > > > > > > *From:* Icecast *On Behalf Of *Inetken > *Sent:* Monday, April 2, 2018 11:52 AM > *To:* icecast at xiph.org > *Subject:* [Icecast] NAT and Playlist Question > > > > Brief backstory, previous admin is gone and the previous server died. > What I could gather was it may have been running Icecast. I setup Icecast > on a new CentOS 7 server and the server sits behind a firewall. The links > from the users web site points to and internal address for internal users > and an link to an external address. > > > > I created a listen.pls playlist with the following: > > > > [playlist] > > NumberOfEntries=1 > > File1=http://:8000/ > > > > The website points to this playlist file and it works fine. However, when > I use the external link offsite I get an error that it cannot download the > listen.pls file and won't play the stream. Should this work as I have it > configured? How should I configure Icecast to work behind a NAT firewall > for internal and external users? > > > > Thanks, > > Ken > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jake at jakebriggs.com Mon Apr 2 20:06:45 2018 From: jake at jakebriggs.com (Jake) Date: Tue, 03 Apr 2018 08:06:45 +1200 Subject: [Icecast] NAT and Playlist Question In-Reply-To: References: Message-ID: <2E65DEF9-B3AA-4DA6-B4FF-591B3D971308@jakebriggs.com> You may need to set up a reverse proxy depending on your setup. What is the external URL? Is it something like http://example.com ? Or http://example.com/playlist.pls ? Or perhaps http://example.com:8000/playlist.pls ? I guess I am asking if you are natting from 80 to 8000, or something like that. There could be firewall rules on the outgoing connection that stop getting at port 8000. Also, what error do you get when attempting to get the URL with curl or wget? If your URL is not private, I'd be happy to have a poke at it. I can't guarantee a solution though haha Jake On 3 April 2018 4:52:09 AM NZST, Inetken wrote: >Brief backstory, previous admin is gone and the previous server died. >What >I could gather was it may have been running Icecast. I setup Icecast >on a >new CentOS 7 server and the server sits behind a firewall. The links >from >the users web site points to and internal address for internal users >and an >link to an external address. > >I created a listen.pls playlist with the following: > >[playlist] >NumberOfEntries=1 >File1=http://:8000/ > >The website points to this playlist file and it works fine. However, >when >I use the external link offsite I get an error that it cannot download >the >listen.pls file and won't play the stream. Should this work as I have >it >configured? How should I configure Icecast to work behind a NAT >firewall >for internal and external users? > >Thanks, >Ken -------------- next part -------------- An HTML attachment was scrubbed... URL: From phschafft at de.loewenfelsen.net Tue Apr 3 10:58:47 2018 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Tue, 03 Apr 2018 10:58:47 +0000 Subject: [Icecast] NAT and Playlist Question In-Reply-To: References: Message-ID: <1522753127.2776.27.camel@de.loewenfelsen.net> Good afternoon Ken, On Mon, 2018-04-02 at 09:52 -0700, Inetken wrote: > Brief backstory, previous admin is gone and the previous server died. What > I could gather was it may have been running Icecast. Things like this sadly happen. > I setup Icecast on a > new CentOS 7 server and the server sits behind a firewall. The links from > the users web site points to and internal address for internal users and an > link to an external address. > > I created a listen.pls playlist with the following: > > [playlist] > NumberOfEntries=1 > File1=http://:8000/ Generally I suggest against using IP addresses. But see below. > The website points to this playlist file and it works fine. However, when > I use the external link offsite I get an error that it cannot download the > listen.pls file and won't play the stream. Should this work as I have it > configured? How should I configure Icecast to work behind a NAT firewall > for internal and external users? There are several possible optimal setups. All of them have Icecast with the same configuration in common. For most stations the default Icecast configuration works fine (with only passwords changed). Most people break Icecast by setting too many options. The default configuration uses port 8000. I suggest to keep this. Next with NAT you need to ensure the port is forwarded. I generally suggest not use NAT but routed connections. However this requires a public IP for your server. But it also solves the problem with internal/external-split. I strongly recommend against using a reverse proxy. This works but there are several pitfalls. This should only be done with a professional around. The next step is to decide where to split internal and external users. There are three possibilities: A. You can give internal and external users different URLs to your stream. This is the most simple solution but does not work if people use the same URL from inside and outside your network. B. You can have a server that is reachable from both networks and knows the client location (within your network or public internet) and generate a playlist based on this. This works nicely if such infrastructure already exists. Also it gives you a stable playlist URL. However if players cache the Playlist they still can't move between networks. C. You make Icecast accessible from both networks with the same URL. This is the preferred method. This can be done by using a static and public IP address for your server. Or by using a Hostname that resolves differently from your internal network. E.g. bind(DNS server) supports "view"s to allow such setups. Which solution is best depends a bit on the ecosystem your Icecast runs within. E.g. if there is any of the other systems already and how much your clients move around. As you want to run Icecast behind a NATed connection I guess that it's also bandwidth limited. I suggest to consider this as well. The bandwidth needed is about: 2*bitrate*listeners. E.g. with 112kbit/s and 32 listeners the required "upload" bandwidth is about 7.2MBit/s. I hope that this is of help to you. If you need professional business support feel free to reply to me off-list. With best regards, -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephon: +49.3535 490 17 92 L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 490 bytes Desc: This is a digitally signed message part URL: From jake at jakebriggs.com Tue Apr 3 19:28:31 2018 From: jake at jakebriggs.com (Jake) Date: Wed, 04 Apr 2018 07:28:31 +1200 Subject: [Icecast] NAT and Playlist Question In-Reply-To: References: Message-ID: Oh one thing I over looked, you say you are populating the pls file with the internal IP of the machine streaming? Well that's not going to work outside your network. Is the error perhaps not that you can't download the pls file, but that it can't download the contents? On 3 April 2018 4:52:09 AM NZST, Inetken wrote: >Brief backstory, previous admin is gone and the previous server died. >What >I could gather was it may have been running Icecast. I setup Icecast >on a >new CentOS 7 server and the server sits behind a firewall. The links >from >the users web site points to and internal address for internal users >and an >link to an external address. > >I created a listen.pls playlist with the following: > >[playlist] >NumberOfEntries=1 >File1=http://:8000/ > >The website points to this playlist file and it works fine. However, >when >I use the external link offsite I get an error that it cannot download >the >listen.pls file and won't play the stream. Should this work as I have >it >configured? How should I configure Icecast to work behind a NAT >firewall >for internal and external users? > >Thanks, >Ken -------------- next part -------------- An HTML attachment was scrubbed... URL: From stowe.jim at gmail.com Wed Apr 11 12:30:01 2018 From: stowe.jim at gmail.com (Jim Stowe) Date: Wed, 11 Apr 2018 08:30:01 -0400 Subject: [Icecast] Need to install orginal Icecast 1.3 (not Icecast2) Message-ID: I have an urgent need to install the original Icecast (1.3.12). I have a piece of broadcasting software that can only receive a stream from the "old" version of Icecast. I've tried building it under Debian 9, but failed. Can anyone provide any assistance? I'd prefer to stick with Debian, but I'm willing to use a different distro if necessary. I've worked in IT for almost three decades, but I'm still a relative newbie with Linux. Any help would be greatly appreciated. Thank you! Jim -------------- next part -------------- An HTML attachment was scrubbed... URL: From yahav.shasha at gmail.com Wed Apr 11 12:32:17 2018 From: yahav.shasha at gmail.com (Yahav Shasha) Date: Wed, 11 Apr 2018 15:32:17 +0300 Subject: [Icecast] Need to install orginal Icecast 1.3 (not Icecast2) In-Reply-To: References: Message-ID: I know its probably not the answer you want to hear but if this broadcast software require Icecast 1.x, you should be really looking into alternative broadcast software. -------------- next part -------------- An HTML attachment was scrubbed... URL: From oskar.vilkevuori at ovt.fi Wed Apr 18 08:13:22 2018 From: oskar.vilkevuori at ovt.fi (Oskar Vilkevuori) Date: Wed, 18 Apr 2018 11:13:22 +0300 Subject: [Icecast] Intro & Chrome v. 65.0.33.25.181 Message-ID: Hi there, I ran to dead end when Google released a new version for Chrome. I have tried to search with google and I haven?t found anything. There seems to be a problem when a stream has an intro element. It only plays the the intro and does not allow the stream to be played. http://185.139.186.34:8000/yleisohjelma And if there is no intro then it will play like: http://185.139.186.34:8000/vara Is it something wrong on my config? Is this somehow related with http headers? Or Access Control Allow Origin? Looking forward, Yours, Oskar Vilkevuori Radio Dei From leif at scriba-bb.de Wed Apr 18 09:26:34 2018 From: leif at scriba-bb.de (Leif Scriba) Date: Wed, 18 Apr 2018 11:26:34 +0200 Subject: [Icecast] Intro & Chrome v. 65.0.33.25.181 In-Reply-To: References: Message-ID: <6963562C-112C-4C09-A9C7-4A0A01C8FB17@scriba-bb.de> Hello Oskar, I had a similar problem. The fix was to produce an intro file with same Bitrate, sampling rate (khz), channels and so on as the stream. Most players get confused when one of this parameters changes in between. Cheers Leif > Am 18.04.2018 um 10:13 schrieb Oskar Vilkevuori : > > Hi there, > > I ran to dead end when Google released a new version for Chrome. I have tried to search with google and I haven?t found anything. > > There seems to be a problem when a stream has an intro element. It only plays the the intro and does not allow the stream to be played. > http://185.139.186.34:8000/yleisohjelma > > And if there is no intro then it will play like: > > http://185.139.186.34:8000/vara > > Is it something wrong on my config? Is this somehow related with http headers? Or Access Control Allow Origin? > > Looking forward, > > Yours, > > Oskar Vilkevuori > Radio Dei > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast -------------- next part -------------- An HTML attachment was scrubbed... URL: From oskar.vilkevuori at ovt.fi Wed Apr 18 11:53:02 2018 From: oskar.vilkevuori at ovt.fi (Oskar Vilkevuori) Date: Wed, 18 Apr 2018 14:53:02 +0300 Subject: [Icecast] Intro & Chrome v. 65.0.33.25.181 In-Reply-To: <6963562C-112C-4C09-A9C7-4A0A01C8FB17@scriba-bb.de> References: <6963562C-112C-4C09-A9C7-4A0A01C8FB17@scriba-bb.de> Message-ID: <1D69F2A1-8F37-4E34-A212-094DCDF3AEF1@ovt.fi> Hi Leif, Did You faced that with the exact same Chrome version? Since this version is the only one having this issue. I have had this kind of arrangement (intro + live stream) for decades. Technology changes but the idea is the same. I have tested a lot of hardware and combinations. I do have a fail over stream (with different specs) and that hasn?t been an issue at all. I do not know but I assume my problem is related with headers on the stream but I don?t have more right now. Thats why I?m writing here? Yours, Oskar > On 18 Apr 2018, at 12.26, Leif Scriba wrote: > > Hello Oskar, > > I had a similar problem. The fix was to produce an intro file with same Bitrate, sampling rate (khz), channels and so on as the stream. > Most players get confused when one of this parameters changes in between. > > Cheers > Leif > > > > Am 18.04.2018 um 10:13 schrieb Oskar Vilkevuori >: > >> Hi there, >> >> I ran to dead end when Google released a new version for Chrome. I have tried to search with google and I haven?t found anything. >> >> There seems to be a problem when a stream has an intro element. It only plays the the intro and does not allow the stream to be played. >> http://185.139.186.34:8000 /yleisohjelma >> >> And if there is no intro then it will play like: >> >> http://185.139.186.34:8000/vara >> >> Is it something wrong on my config? Is this somehow related with http headers? Or Access Control Allow Origin? >> >> Looking forward, >> >> Yours, >> >> Oskar Vilkevuori >> Radio Dei >> _______________________________________________ >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast -------------- next part -------------- An HTML attachment was scrubbed... URL: From leif at scriba-bb.de Wed Apr 18 14:38:45 2018 From: leif at scriba-bb.de (Leif Scriba) Date: Wed, 18 Apr 2018 16:38:45 +0200 Subject: [Icecast] Intro & Chrome v. 65.0.33.25.181 In-Reply-To: <1D69F2A1-8F37-4E34-A212-094DCDF3AEF1@ovt.fi> References: <6963562C-112C-4C09-A9C7-4A0A01C8FB17@scriba-bb.de> <1D69F2A1-8F37-4E34-A212-094DCDF3AEF1@ovt.fi> Message-ID: <4ACA0187-B9F3-43A0-9504-C39E046CD38D@scriba-bb.de> Hello Oskar, No i didn?t face it with this exact version of Chrome but with different versions and other players/ Webbrowsers. IMHO you should first try to set encoding of intro and stream identical. And try different players. Regards Leif > Am 18.04.2018 um 13:53 schrieb Oskar Vilkevuori : > > Hi Leif, > > Did You faced that with the exact same Chrome version? Since this version is the only one having this issue. I have had this kind of arrangement (intro + live stream) for decades. Technology changes but the idea is the same. I have tested a lot of hardware and combinations. > > I do have a fail over stream (with different specs) and that hasn?t been an issue at all. > > I do not know but I assume my problem is related with headers on the stream but I don?t have more right now. Thats why I?m writing here? > > Yours, > > Oskar > >> On 18 Apr 2018, at 12.26, Leif Scriba wrote: >> >> Hello Oskar, >> >> I had a similar problem. The fix was to produce an intro file with same Bitrate, sampling rate (khz), channels and so on as the stream. >> Most players get confused when one of this parameters changes in between. >> >> Cheers >> Leif >> >> >> >>> Am 18.04.2018 um 10:13 schrieb Oskar Vilkevuori : >>> >>> Hi there, >>> >>> I ran to dead end when Google released a new version for Chrome. I have tried to search with google and I haven?t found anything. >>> >>> There seems to be a problem when a stream has an intro element. It only plays the the intro and does not allow the stream to be played. >>> http://185.139.186.34:8000/yleisohjelma >>> >>> And if there is no intro then it will play like: >>> >>> http://185.139.186.34:8000/vara >>> >>> Is it something wrong on my config? Is this somehow related with http headers? Or Access Control Allow Origin? >>> >>> Looking forward, >>> >>> Yours, >>> >>> Oskar Vilkevuori >>> Radio Dei >>> _______________________________________________ >>> Icecast mailing list >>> Icecast at xiph.org >>> http://lists.xiph.org/mailman/listinfo/icecast >> _______________________________________________ >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast -------------- next part -------------- An HTML attachment was scrubbed... URL: From oskar.vilkevuori at ovt.fi Wed Apr 18 15:06:09 2018 From: oskar.vilkevuori at ovt.fi (Oskar Vilkevuori) Date: Wed, 18 Apr 2018 18:06:09 +0300 Subject: [Icecast] Intro & Chrome v. 65.0.33.25.181 In-Reply-To: <4ACA0187-B9F3-43A0-9504-C39E046CD38D@scriba-bb.de> References: <6963562C-112C-4C09-A9C7-4A0A01C8FB17@scriba-bb.de> <1D69F2A1-8F37-4E34-A212-094DCDF3AEF1@ovt.fi> <4ACA0187-B9F3-43A0-9504-C39E046CD38D@scriba-bb.de> Message-ID: <403B42AE-C6FF-429B-889F-09CF5E7AC18D@ovt.fi> Hi there, Any other versions of Google Chrome and all version of other browsers are working. I have done my best to set up the intro to match the live stream. http://185.139.168.34:8000/yleisohjelma - intro is 256 kbits/s 48 kHz ISO-MPEG2 L3 - live is 256 kbits/s 48 kHz ISO-MPEG2 L3 http://185.139.168.34:8000/vara - live is 128 kBits/s 48 kHz, possible ISO-MPEG2 L3 - there is no intro Of cause there is a certain difference between a file and a stream. Yours, Oskar > On 18 Apr 2018, at 17.38, Leif Scriba wrote: > > > Hello Oskar, > > No i didn?t face it with this exact version of Chrome but with different versions and other players/ Webbrowsers. > IMHO you should first try to set encoding of intro and stream identical. And try different players. > > Regards > Leif > > > Am 18.04.2018 um 13:53 schrieb Oskar Vilkevuori >: > >> Hi Leif, >> >> Did You faced that with the exact same Chrome version? Since this version is the only one having this issue. I have had this kind of arrangement (intro + live stream) for decades. Technology changes but the idea is the same. I have tested a lot of hardware and combinations. >> >> I do have a fail over stream (with different specs) and that hasn?t been an issue at all. >> >> I do not know but I assume my problem is related with headers on the stream but I don?t have more right now. Thats why I?m writing here? >> >> Yours, >> >> Oskar >> >>> On 18 Apr 2018, at 12.26, Leif Scriba > wrote: >>> >>> Hello Oskar, >>> >>> I had a similar problem. The fix was to produce an intro file with same Bitrate, sampling rate (khz), channels and so on as the stream. >>> Most players get confused when one of this parameters changes in between. >>> >>> Cheers >>> Leif >>> >>> >>> >>> Am 18.04.2018 um 10:13 schrieb Oskar Vilkevuori >: >>> >>>> Hi there, >>>> >>>> I ran to dead end when Google released a new version for Chrome. I have tried to search with google and I haven?t found anything. >>>> >>>> There seems to be a problem when a stream has an intro element. It only plays the the intro and does not allow the stream to be played. >>>> http://185.139.186.34:8000 /yleisohjelma >>>> >>>> And if there is no intro then it will play like: >>>> >>>> http://185.139.186.34:8000/vara >>>> >>>> Is it something wrong on my config? Is this somehow related with http headers? Or Access Control Allow Origin? >>>> >>>> Looking forward, >>>> >>>> Yours, >>>> >>>> Oskar Vilkevuori >>>> Radio Dei >>>> _______________________________________________ >>>> Icecast mailing list >>>> Icecast at xiph.org >>>> http://lists.xiph.org/mailman/listinfo/icecast >>> _______________________________________________ >>> Icecast mailing list >>> Icecast at xiph.org >>> http://lists.xiph.org/mailman/listinfo/icecast >> >> _______________________________________________ >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast -------------- next part -------------- An HTML attachment was scrubbed... URL: From brad at musatcha.com Thu Apr 19 05:17:27 2018 From: brad at musatcha.com (Brad Isbell) Date: Wed, 18 Apr 2018 22:17:27 -0700 Subject: [Icecast] Intro & Chrome v. 65.0.33.25.181 In-Reply-To: <403B42AE-C6FF-429B-889F-09CF5E7AC18D@ovt.fi> References: <6963562C-112C-4C09-A9C7-4A0A01C8FB17@scriba-bb.de> <1D69F2A1-8F37-4E34-A212-094DCDF3AEF1@ovt.fi> <4ACA0187-B9F3-43A0-9504-C39E046CD38D@scriba-bb.de> <403B42AE-C6FF-429B-889F-09CF5E7AC18D@ovt.fi> Message-ID: There should be no issue with the varying bit rate. For an MP3 stream, you can change bit rates mid-stream all you want as long as you keep the sample rate and channel counts the same. If you check chrome://media-internals, you'll see that you're getting a PIPELINE_ERROR_DECODE. Since Chrome v64, it has been a lot more picky about the streams it accepts. I suspect that Icecast is simply dumping the buffer for the file out to the client, and then needle-dropping into the middle of the live MP3 stream without re-syncing to a frame boundary first. (Someone more familiar with the Icecast internals could probably answer that in detail.) I suspect that Chrome isn't happy about this, doesn't bother to re-sync to the stream itself, and throws this error. I would recommend dropping your intro. In-stream intros tend to have bad side effects anyway, when clients get disconnected and have to reconnect. This re-connection often happens seamlessly, but cannot be so seamless if your intro gets sent for every GET request. Brad Isbell brad at musatcha.com http://www.musatcha.com On Wed, Apr 18, 2018 at 8:06 AM, Oskar Vilkevuori wrote: > Hi there, > > Any other versions of Google Chrome and all version of other browsers are > working. > > I have done my best to set up the intro to match the live stream. > > http://185.139.168.34:8000/yleisohjelma > - intro is 256 kbits/s 48 kHz ISO-MPEG2 L3 > - live is 256 kbits/s 48 kHz ISO-MPEG2 L3 > > http://185.139.168.34:8000/vara > - live is 128 kBits/s 48 kHz, possible ISO-MPEG2 L3 > - there is no intro > > Of cause there is a certain difference between a file and a stream. > > Yours, > > Oskar > > > On 18 Apr 2018, at 17.38, Leif Scriba wrote: > > > Hello Oskar, > > No i didn?t face it with this exact version of Chrome but with different > versions and other players/ Webbrowsers. > IMHO you should first try to set encoding of intro and stream identical. > And try different players. > > Regards > Leif > > > Am 18.04.2018 um 13:53 schrieb Oskar Vilkevuori : > > Hi Leif, > > Did You faced that with the exact same Chrome version? Since this version > is the only one having this issue. I have had this kind of arrangement > (intro + live stream) for decades. Technology changes but the idea is the > same. I have tested a lot of hardware and combinations. > > I do have a fail over stream (with different specs) and that hasn?t been > an issue at all. > > I do not know but I assume my problem is related with headers on the > stream but I don?t have more right now. Thats why I?m writing here? > > Yours, > > Oskar > > On 18 Apr 2018, at 12.26, Leif Scriba wrote: > > Hello Oskar, > > I had a similar problem. The fix was to produce an intro file with same > Bitrate, sampling rate (khz), channels and so on as the stream. > Most players get confused when one of this parameters changes in between. > > Cheers > Leif > > > > Am 18.04.2018 um 10:13 schrieb Oskar Vilkevuori : > > Hi there, > > I ran to dead end when Google released a new version for Chrome. I have > tried to search with google and I haven?t found anything. > > There seems to be a problem when a stream has an intro element. It only > plays the the intro and does not allow the stream to be played. > > http://185.139.186.34:8000/yleisohjelma > > And if there is no intro then it will play like: > > http://185.139.186.34:8000/vara > > Is it something wrong on my config? Is this somehow related with http > headers? Or Access Control Allow Origin? > > Looking forward, > > Yours, > > Oskar Vilkevuori > Radio Dei > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > > > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From phschafft at de.loewenfelsen.net Thu Apr 19 05:44:33 2018 From: phschafft at de.loewenfelsen.net (Philipp Schafft) Date: Thu, 19 Apr 2018 05:44:33 +0000 Subject: [Icecast] Intro & Chrome v. 65.0.33.25.181 In-Reply-To: References: <6963562C-112C-4C09-A9C7-4A0A01C8FB17@scriba-bb.de> <1D69F2A1-8F37-4E34-A212-094DCDF3AEF1@ovt.fi> <4ACA0187-B9F3-43A0-9504-C39E046CD38D@scriba-bb.de> <403B42AE-C6FF-429B-889F-09CF5E7AC18D@ovt.fi> Message-ID: <1524116673.2197.10.camel@de.loewenfelsen.net> Good morning, On Wed, 2018-04-18 at 22:17 -0700, Brad Isbell wrote: > There should be no issue with the varying bit rate. For an MP3 > stream, you > can change bit rates mid-stream all you want as long as you keep the > sample > rate and channel counts the same. This is true for many codecs. However we have seen some really bad implementations for MP3 that required all encoder parameters to be time-invariant. I don't want to say that it's the problem. Just want to say it's worth to have a look at this as well. > If you check chrome://media-internals, you'll see that you're getting > a PIPELINE_ERROR_DECODE. Since Chrome v64, it has been a lot more > picky > about the streams it accepts. > I suspect that Icecast is simply dumping the buffer for the file out > to the > client, and then needle-dropping into the middle of the live MP3 > stream > without re-syncing to a frame boundary first. (Someone more familiar > with > the Icecast internals could probably answer that in detail.) For all supported codecs Icecast2 does proper re-syncing and all other necessary steps for a correct transition. However as MP3 is not a supported codec Icecast2 uses the 'generic' handler. Which basically does what you said above. > I suspect that Chrome isn't happy about this, doesn't bother to > re-sync to the stream itself, and throws this error. Then it would be Chrome's bug. The syncwords exist for a reason: to make broken streams recoverable. Bit flipping errors aren't uncommon. And MP3 can handle them. There is no real excuse why not to handle them. More true if it worked in older versions of the same software. But this is just a guess at this point. Generally speaking: Players improved over the last decade. Even MP3 players. > > On Wed, Apr 18, 2018 at 8:06 AM, Oskar Vilkevuori > > wrote: > > > I have done my best to set up the intro to match the live stream. > > > > http://185.139.168.34:8000/yleisohjelma > > - intro is 256 kbits/s 48 kHz ISO-MPEG2 L3 > > - live is 256 kbits/s 48 kHz ISO-MPEG2 L3 > > > > http://185.139.168.34:8000/vara > > - live is 128 kBits/s 48 kHz, possible ISO-MPEG2 L3 > > - there is no intro With best regards, -- Philipp Schafft (CEO/Gesch?ftsf?hrer) Telephon: +49.3535 490 17 92 L?wenfelsen UG (haftungsbeschr?nkt) Registration number: Bickinger Stra?e 21 HRB 12308 CB 04916 Herzberg (Elster) VATIN/USt-ID: Germany DE305133015 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 490 bytes Desc: This is a digitally signed message part URL: From antonixfelinski at gmail.com Tue Apr 24 13:51:47 2018 From: antonixfelinski at gmail.com (=?UTF-8?Q?F=C3=A9lix=2DAntoine_Morin?=) Date: Tue, 24 Apr 2018 09:51:47 -0400 Subject: [Icecast] Server renew... Message-ID: Hi there, (sorry for my bad english speaking) I was broadcasting my Iphones audio feed to the Icecast server : http://104.236.126.104:8000/ or http://104.236.126.104/ (port 8000) But now it seams like that server is dead... An other developper set it up for me, so I don't know if we just need to re-activate it by paying or else... It was working in December 2017. I use the application KoalaSan on my iphone4. Please give me an indication on how to re-activate the server! My friend who set it up had an accident and can't help me now... ?Regards , F?lix-Antoine Morin 769 Villeray Montr?al, Qc. Canada H2R 1J2 (514) 690.36.89 felixantoinemorin.com Facebook -------------- next part -------------- An HTML attachment was scrubbed... URL: From epirat07 at gmail.com Tue Apr 24 13:54:47 2018 From: epirat07 at gmail.com (Marvin Scholz) Date: Tue, 24 Apr 2018 15:54:47 +0200 Subject: [Icecast] Server renew... In-Reply-To: References: Message-ID: <4B0B8390-DE0E-43B4-870B-5FE1E0719C88@gmail.com> On 24 Apr 2018, at 15:51, F?lix-Antoine Morin wrote: > Hi there, (sorry for my bad english speaking) > > I was broadcasting my Iphones audio feed to the Icecast server : > http://104.236.126.104:8000/ > or > http://104.236.126.104/ (port 8000) > > But now it seams like that server is dead... An other developper set it up > for me, so I don't know if we just need to re-activate it by paying or > else... It was working in December 2017. > > I use the application KoalaSan on my iphone4. > > Please give me an indication on how to re-activate the server! > My friend who set it up had an accident and can't help me now... Icecast is the software running on the server, not a hosting provider for such servers, so there is nothing we can do about that. You have to contact the person that set up the server for you. > > ?Regards > , > F?lix-Antoine Morin > > 769 Villeray > Montr?al, Qc. > Canada > H2R 1J2 > > (514) 690.36.89 > > felixantoinemorin.com > Facebook > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast From jmcharry at gmx.net Tue Apr 24 14:27:04 2018 From: jmcharry at gmx.net (John McHarry) Date: Tue, 24 Apr 2018 10:27:04 -0400 Subject: [Icecast] Server renew... In-Reply-To: <4B0B8390-DE0E-43B4-870B-5FE1E0719C88@gmail.com> References: <4B0B8390-DE0E-43B4-870B-5FE1E0719C88@gmail.com> Message-ID: <1524580024.3479.1.camel@gmx.net> It looks like the server is provided by this company:? http://www.digitalocean.com?I would try contacting them. On Tue, 2018-04-24 at 15:54 +0200, Marvin Scholz wrote: > > On 24 Apr 2018, at 15:51, F?lix-Antoine Morin wrote: > > > > > Hi there, (sorry for my bad english speaking) > > > > I was broadcasting my Iphones audio feed to the Icecast server : > > http://104.236.126.104:8000/ > > or > > http://104.236.126.104/ (port 8000) > > > > But now it seams like that server is dead... An other developper > > set it up > > for me, so I don't know if we just need to re-activate it by paying > > or > > else... It was working in December 2017. > > > > I use the application KoalaSan on my iphone4. > > > > Please give me an indication on how to re-activate the server! > > My friend who set it up had an accident and can't help me now... > Icecast is the software running on the server, not a hosting provider > for such servers, so there is nothing we can do about that. > > You have to contact the person that set up the server for you. > > > > > > > Regards > > , > > F?lix-Antoine Morin > > > > 769 Villeray > > Montr?al, Qc. > > Canada > > H2R 1J2 > > > > (514) 690.36.89 > > > > felixantoinemorin.com > > Facebook > > _______________________________________________ > > Icecast mailing list > > Icecast at xiph.org > > http://lists.xiph.org/mailman/listinfo/icecast > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast From vpayne1 at unl.edu Tue Apr 24 14:46:42 2018 From: vpayne1 at unl.edu (Vance Payne) Date: Tue, 24 Apr 2018 14:46:42 +0000 Subject: [Icecast] Server renew... In-Reply-To: <4B0B8390-DE0E-43B4-870B-5FE1E0719C88@gmail.com> References: <4B0B8390-DE0E-43B4-870B-5FE1E0719C88@gmail.com> Message-ID: Oops! This exchange was erroneously forwarded or copied to me. Please correct. Thanks. -----Original Message----- From: Icecast On Behalf Of Marvin Scholz Sent: Tuesday, April 24, 2018 8:55 AM To: Icecast streaming server user discussions Subject: Re: [Icecast] Server renew... On 24 Apr 2018, at 15:51, F?lix-Antoine Morin wrote: > Hi there, (sorry for my bad english speaking) > > I was broadcasting my Iphones audio feed to the Icecast server : > https://urldefense.proofpoint.com/v2/url?u=http-3A__104.236.126.104-3A > 8000_&d=DwIGaQ&c=Cu5g146wZdoqVuKpTNsYHeFX_rg6kWhlkLF8Eft-wwo&r=rWOyw61 > wUu7C5473U986LQ&m=YkvVV310rZCVZkd3M5RLygOe9fh0IJ-iuIqPhWY54Cg&s=fuMkaF > yH16iOqO2nzFljwAZmsZtsY8Z751vPfv84oCU&e= > or > https://urldefense.proofpoint.com/v2/url?u=http-3A__104.236.126.104_&d > =DwIGaQ&c=Cu5g146wZdoqVuKpTNsYHeFX_rg6kWhlkLF8Eft-wwo&r=rWOyw61wUu7C54 > 73U986LQ&m=YkvVV310rZCVZkd3M5RLygOe9fh0IJ-iuIqPhWY54Cg&s=G2dyIgYl7k-3q > GHdF-kIoYIyZlE1qgOF63_fRiKGSKg&e= (port 8000) > > But now it seams like that server is dead... An other developper set > it up for me, so I don't know if we just need to re-activate it by > paying or else... It was working in December 2017. > > I use the application KoalaSan on my iphone4. > > Please give me an indication on how to re-activate the server! > My friend who set it up had an accident and can't help me now... Icecast is the software running on the server, not a hosting provider for such servers, so there is nothing we can do about that. You have to contact the person that set up the server for you. > > ?Regards > , > F?lix-Antoine Morin > > 769 Villeray > Montr?al, Qc. > Canada > H2R 1J2 > > (514) 690.36.89 > > felixantoinemorin.com > Facebook > _felixantoine.morin&d=DwIGaQ&c=Cu5g146wZdoqVuKpTNsYHeFX_rg6kWhlkLF8Eft > -wwo&r=rWOyw61wUu7C5473U986LQ&m=YkvVV310rZCVZkd3M5RLygOe9fh0IJ-iuIqPhW > Y54Cg&s=Q5_arSUsjjN6lErFk94ebQurxiOzhAeBwGgh7E-3khI&e=> > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.xiph.org_mai > lman_listinfo_icecast&d=DwIGaQ&c=Cu5g146wZdoqVuKpTNsYHeFX_rg6kWhlkLF8E > ft-wwo&r=rWOyw61wUu7C5473U986LQ&m=YkvVV310rZCVZkd3M5RLygOe9fh0IJ-iuIqP > hWY54Cg&s=X0viyfzYFbq9wIIEXjZFO5xqF0gWZHxiYBwvDL1EdlM&e= _______________________________________________ Icecast mailing list Icecast at xiph.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.xiph.org_mailman_listinfo_icecast&d=DwIGaQ&c=Cu5g146wZdoqVuKpTNsYHeFX_rg6kWhlkLF8Eft-wwo&r=rWOyw61wUu7C5473U986LQ&m=YkvVV310rZCVZkd3M5RLygOe9fh0IJ-iuIqPhWY54Cg&s=X0viyfzYFbq9wIIEXjZFO5xqF0gWZHxiYBwvDL1EdlM&e= From rominfo at i.ua Wed Apr 25 06:17:41 2018 From: rominfo at i.ua (=?utf-8?B?0JDQu9C10LrRgQ==?=) Date: Wed, 25 Apr 2018 09:17:41 +0300 Subject: [Icecast] =?utf-8?q?Icecast_+_Google_Analytics?= Message-ID: Good afternoon! Can you please tell me how to connect the Icecast server to the Google Analytics system to see the statistics of the connections to the icecast server. In advance thanks for the answer. Very much I wait. Regards, Aleks -- ??????? ----------------------------------------------------------- ???? ???????? ??????? ?? ????? ??????????! ??????? ???? ???! https://goo.gl/iptNm5 From antonixfelinski at gmail.com Wed Apr 25 11:33:16 2018 From: antonixfelinski at gmail.com (=?UTF-8?Q?F=C3=A9lix=2DAntoine_Morin?=) Date: Wed, 25 Apr 2018 07:33:16 -0400 Subject: [Icecast] Icecast + Google Analytics In-Reply-To: References: Message-ID: Its okay now, it is working... ;) Au plaisir, F?lix-Antoine Morin 769 Villeray Montr?al, Qc. Canada H2R 1J2 (514) 690.36.89 felixantoinemorin.com Facebook 2018-04-25 2:17 GMT-04:00 ????? : > Good afternoon! Can you please tell me how to connect the Icecast server > to the Google Analytics system to see the statistics of the connections to > the icecast server. > In advance thanks for the answer. Very much I wait. Regards, Aleks > > -- ??????? ----------------------------------------------------------- > ???? ???????? ??????? ?? ????? ??????????! > ??????? ???? ???! https://goo.gl/iptNm5 > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rominfo at i.ua Wed Apr 25 20:14:30 2018 From: rominfo at i.ua (=?utf-8?B?0JDQu9C10LrRgQ==?=) Date: Wed, 25 Apr 2018 23:14:30 +0300 Subject: [Icecast] =?utf-8?q?Icecast_+_Google_Analytics?= In-Reply-To: References: Message-ID: How to do it? 25.04.2018 14:33, Felix-Antoine Morin >Its okay now, it is working... ;) > > > Au plaisir, > F?lix-Antoine Morin > > > 769 Villeray > Montr?al, Qc. > Canada > H2R 1J2 > > (514) 690.36.89 > > felixantoinemorin.com > Facebook > > 2018-04-25 2:17 GMT-04:00 ????? : > > > Good afternoon! Can you please tell me how to connect the Icecast server > > to the Google Analytics system to see the statistics of the connections to > > the icecast server. > > In advance thanks for the answer. Very much I wait. Regards, Aleks > > > > -- ??????? ----------------------------------------------------------- > > ???? ???????? ??????? ?? ????? ??????????! > > ??????? ???? ???! https://goo.gl/iptNm5 > > _______________________________________________ > > Icecast mailing list > > Icecast at xiph.org > > http://lists.xiph.org/mailman/listinfo/icecast > > -- ??????? ----------------------------------------------------------- ???? ???????? ??????? ?? ????? ??????????! ??????? ???? ???! https://goo.gl/iptNm5 From antonixfelinski at gmail.com Wed Apr 25 22:44:46 2018 From: antonixfelinski at gmail.com (=?UTF-8?Q?F=C3=A9lix=2DAntoine_Morin?=) Date: Wed, 25 Apr 2018 18:44:46 -0400 Subject: [Icecast] Icecast + Google Analytics In-Reply-To: References: Message-ID: I"m not sure, I just re-initiate the password and it is working now.. Au plaisir, F?lix-Antoine Morin 769 Villeray Montr?al, Qc. Canada H2R 1J2 (514) 690.36.89 felixantoinemorin.com Facebook 2018-04-25 16:14 GMT-04:00 ????? : > How to do it? > > 25.04.2018 14:33, Felix-Antoine Morin > >Its okay now, it is working... ;) > > > > > > Au plaisir, > > F?lix-Antoine Morin > > > > > > 769 Villeray > > Montr?al, Qc. > > Canada > > H2R 1J2 > > > > (514) 690.36.89 > > > > felixantoinemorin.com > > Facebook > > > > 2018-04-25 2:17 GMT-04:00 ????? : > > > > > Good afternoon! Can you please tell me how to connect the Icecast > server > > > to the Google Analytics system to see the statistics of the > connections to > > > the icecast server. > > > In advance thanks for the answer. Very much I wait. Regards, Aleks > > > > > > -- ??????? ----------------------------------------------------------- > > > ???? ???????? ??????? ?? ????? ??????????! > > > ??????? ???? ???! https://goo.gl/iptNm5 > > > _______________________________________________ > > > Icecast mailing list > > > Icecast at xiph.org > > > http://lists.xiph.org/mailman/listinfo/icecast > > > > > > -- ??????? ----------------------------------------------------------- > ???? ???????? ??????? ?? ????? ??????????! > ??????? ???? ???! https://goo.gl/iptNm5 > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > -------------- next part -------------- An HTML attachment was scrubbed... URL: From epirat07 at gmail.com Wed Apr 25 23:00:05 2018 From: epirat07 at gmail.com (Marvin Scholz) Date: Thu, 26 Apr 2018 01:00:05 +0200 Subject: [Icecast] Icecast + Google Analytics In-Reply-To: References: Message-ID: It seems you are replying to the wrong email, unrelated to your initial question. Avoid that please, it just confuses everyone... On 26 Apr 2018, at 0:44, F?lix-Antoine Morin wrote: > I"m not sure, I just re-initiate the password and it is working now.. > > > Au plaisir, > F?lix-Antoine Morin > > > 769 Villeray > Montr?al, Qc. > Canada > H2R 1J2 > > (514) 690.36.89 > > felixantoinemorin.com > Facebook > > 2018-04-25 16:14 GMT-04:00 ????? : > >> How to do it? >> >> 25.04.2018 14:33, Felix-Antoine Morin >>> Its okay now, it is working... ;) >>> >>> >>> Au plaisir, >>> F?lix-Antoine Morin >>> >>> >>> 769 Villeray >>> Montr?al, Qc. >>> Canada >>> H2R 1J2 >>> >>> (514) 690.36.89 >>> >>> felixantoinemorin.com >>> Facebook >>> >>> 2018-04-25 2:17 GMT-04:00 ????? : >>> >>>> Good afternoon! Can you please tell me how to connect the Icecast >> server >>>> to the Google Analytics system to see the statistics of the >> connections to >>>> the icecast server. >>>> In advance thanks for the answer. Very much I wait. Regards, Aleks >>>> >>>> -- ??????? >>>> ----------------------------------------------------------- >>>> ???? ???????? ??????? ?? ????? >>>> ??????????! >>>> ??????? ???? ???! https://goo.gl/iptNm5 >>>> _______________________________________________ >>>> Icecast mailing list >>>> Icecast at xiph.org >>>> http://lists.xiph.org/mailman/listinfo/icecast >>>> >> >> >> -- ??????? >> ----------------------------------------------------------- >> ???? ???????? ??????? ?? ????? >> ??????????! >> ??????? ???? ???! https://goo.gl/iptNm5 >> _______________________________________________ >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast >> > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast From oskar.vilkevuori at ovt.fi Sat Apr 28 19:46:43 2018 From: oskar.vilkevuori at ovt.fi (Oskar Vilkevuori) Date: Sat, 28 Apr 2018 22:46:43 +0300 Subject: [Icecast] mp3 stream and Chrome v.65.0.33.25.181 Message-ID: <50D2BA25-172E-4F8C-A320-69D8246D29BF@ovt.fi> Hi there, I have used VLC 0.9.9 on Windows platform for streaming audio to icecast2 for years. Had no problems. Since Google Chrome v.65.0.33.25.181 I ran into problems. Stream will play couple of minutes and then stop. Is there something fundamentally wrong with my configuration in vlm configuration: output #transcode{acodec=mp3,ab=128,channels=2}:duplicate{dst=std{access=shout{mp3=1,bitrate=128},mux=mpeg1,dst=source:hacme at 185.139.168.34:8000/vara},dst=std{access=shout{mp3=1,bitrate=128},mux=mpeg1,dst=source:hacme at 185.139.168.36:8000/vara}} http://185.139.168.34:8000/vara http://185.139.168.36:8000/vara Yours,, Oskar Vilkevuori From epirat07 at gmail.com Sat Apr 28 20:07:29 2018 From: epirat07 at gmail.com (Marvin Scholz) Date: Sat, 28 Apr 2018 22:07:29 +0200 Subject: [Icecast] mp3 stream and Chrome v.65.0.33.25.181 In-Reply-To: <50D2BA25-172E-4F8C-A320-69D8246D29BF@ovt.fi> References: <50D2BA25-172E-4F8C-A320-69D8246D29BF@ovt.fi> Message-ID: <8CABBA43-95F9-43C4-9BC3-EF94470B858E@gmail.com> On 28 Apr 2018, at 21:46, Oskar Vilkevuori wrote: > Hi there, > > I have used VLC 0.9.9 on Windows platform for streaming audio to > icecast2 for years. Had no problems. Since Google Chrome > v.65.0.33.25.181 I ran into problems. Stream will play couple of > minutes and then stop. > > Is there something fundamentally wrong with my configuration in vlm > configuration: > > output > #transcode{acodec=mp3,ab=128,channels=2}:duplicate{dst=std{access=shout{mp3=1,bitrate=128},mux=mpeg1,dst=source:hacme at 185.139.168.34:8000/vara},dst=std{access=shout{mp3=1,bitrate=128},mux=mpeg1,dst=source:hacme at 185.139.168.36:8000/vara}} > > http://185.139.168.34:8000/vara > > http://185.139.168.36:8000/vara > > Yours,, > > Oskar Vilkevuori Hi, Wow, VLC 0.9.9 is nearly a decade old, you really should update to a newer version. In your MRL, instead of mux=mpeg1 you should use mux=raw, afaik. Do you have a intro configured in Icecast? If yes, you need to ensure that all parameters of the file match your stream. > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast From oskar.vilkevuori at ovt.fi Sat Apr 28 20:38:28 2018 From: oskar.vilkevuori at ovt.fi (Oskar Vilkevuori) Date: Sat, 28 Apr 2018 23:38:28 +0300 Subject: [Icecast] mp3 stream and Chrome v.65.0.33.25.181 In-Reply-To: <8CABBA43-95F9-43C4-9BC3-EF94470B858E@gmail.com> References: <50D2BA25-172E-4F8C-A320-69D8246D29BF@ovt.fi> <8CABBA43-95F9-43C4-9BC3-EF94470B858E@gmail.com> Message-ID: <1B5D70C2-EF9D-4B84-B917-52D2F35BE580@ovt.fi> Hi there, mux=raw made the change. Thanks! Moimoi, Oskar Vilkevuori > On 28 Apr 2018, at 23.07, Marvin Scholz wrote: > > > > On 28 Apr 2018, at 21:46, Oskar Vilkevuori wrote: > >> Hi there, >> >> I have used VLC 0.9.9 on Windows platform for streaming audio to icecast2 for years. Had no problems. Since Google Chrome v.65.0.33.25.181 I ran into problems. Stream will play couple of minutes and then stop. >> >> Is there something fundamentally wrong with my configuration in vlm configuration: >> >> output #transcode{acodec=mp3,ab=128,channels=2}:duplicate{dst=std{access=shout{mp3=1,bitrate=128},mux=mpeg1,dst=source:hacme at 185.139.168.34:8000/vara},dst=std{access=shout{mp3=1,bitrate=128},mux=mpeg1,dst=source:hacme at 185.139.168.36:8000/vara}} >> >> http://185.139.168.34:8000/vara >> >> http://185.139.168.36:8000/vara >> >> Yours,, >> >> Oskar Vilkevuori > Hi, > > Wow, VLC 0.9.9 is nearly a decade old, you really should update to a newer > version. > > In your MRL, instead of mux=mpeg1 you should use mux=raw, afaik. Do you have a intro > configured in Icecast? If yes, you need to ensure that all parameters of the file match > your stream. > >> _______________________________________________ >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast -------------- next part -------------- An HTML attachment was scrubbed... URL: