similar to: Client development

reflum, On Mon, 2015-02-09 at 22:36 +0100, Marvin Scholz wrote: > If you do not want to do all work yourself, you can use the libshout > library: > Git: https://git.xiph.org/?p=icecast-libshout.git;a=summary > Download: http://icecast.org/download I would support this. libshout takes care of many problems and will always match Icecast development. And it's even easy to use! :)

On Tue, 07 Aug 2018 21:20:07 +0200 "Marvin Scholz" <epirat07 at gmail.com> wrote: > On 7 Aug 2018, at 20:55, Dave Serls wrote: > > > Is it possible to register ones icecast streams at dir.xiph.org if > > they require > > URL authentication? > > Why would it be useful to have streams in the directory that users can > not listen > to

On Mon, Oct 5, 2020 at 9:59 PM Marvin Scholz <epirat07 at gmail.com> wrote: > > Hi, CC'd the mailing list. > > It seems you are not up to date, git master already has a > --without-openssl option. Without this patch, I get /bin/bash ../libtool --tag=CC --mode=link mips-openwrt-linux-musl-gcc -Wall -ffast-math -fsigned-char

On Wed, Oct 7, 2020 at 3:43 AM Marvin Scholz <epirat07 at gmail.com> wrote: > > Hi, please provide the contents of the config.log > > I can not reproduce your issue on my machine, --without-openssl > works fine here. > > Oh and next time please mention that its about libshout right > away :) https://gist.github.com/neheb/a26714035978d07a822985477524cd45 > > On 7

The default ices.conf.dist file from the source distribution contains: <!-- Header protocol to use when communicating with the server. Shoutcast servers need "icy", icecast 1.x needs "xaudiocast", and icecast 2.x needs "http". --> <Protocol>http</Protocol> I haven't checked the code to see if this is used for

El mié, 23-08-2017 a las 14:13 +0200, Marvin Scholz escribió: > > On 23 Aug 2017, at 14:08, José Luis Artuch wrote: > > > Hello, good morning ! > > Running Icecast2 and Ices2 with live audio from Line IN, what is > > the > > correct way to change the bitrate ?. > > In the Icecast2 configuration file I set: > > > > <mount

On 24 Jun 2015, at 15:33, Martin Jangowski wrote: > I regularly broadcast with 48kBit streaming rate (mp3, mono, 44kHz). > My fallback-file is a 244kBit, stereo, 44kHz, mp3 file. Works like a > charme.... That depends on the player, if it works you are lucky. It might not work for other formats or with some players.

Can you please unsubscribe me from your emails. John Dohnt support at psrfm.org.au -----Original Message----- From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of icecast-request at xiph.org Sent: Monday, 20 March 2017 10:42 AM To: icecast at xiph.org Subject: Icecast Digest, Vol 153, Issue 3 Send Icecast mailing list submissions to icecast at xiph.org To subscribe or unsubscribe

Yes, it is the first thing I have tried, but I have encountered this problem. If I enable option <option name="allow_duplicate_users" value="1"/>, it works fine. But if set to 0, to limit one connection per user, it does not work properly and forces you to manually enter the data again. It seems that there are players who make 2 requests, and being limited to 1, makes the

Same situation with the smartphone, connection timed out. 2017-02-01 1:40 GMT+01:00 Marvin Scholz <epirat07 at gmail.com>: > It is possible that you are not able to connect to your external IP > address and reach Icecast. > Please try doing so from a connection that has not the external IP that > Icecast has, like with > your mobile phone over cellular network. > > The

I would like to have a private signal, which can only be tuned by whoever has the username and password, and know who is connected. But I wish the URL could be delivered with the username and password, to open it directly on a player or receiving device... Thanks. El sáb., 14 sept. 2019 a las 21:33, Marvin Scholz (<epirat07 at gmail.com>) escribió: > > > On 14 Sep 2019, at 21:09,

Marvin, Ah, thank you for clarifying where "webroot" is. The application here will be a non-public stream with one listener client. Icecast is hosted on a computer at our radio station. It will receive a stream from a stream client at a remote live music event. There will be one listener: a media player running on another computer on the network at the station which will send the

On 08/04/2018 07:00 PM, Marvin Scholz wrote: > > On 4 Aug 2018, at 16:12, Ross Levis wrote: > >> I've been told that Icecast streams could be listed on the popular >> Shoutcast.com directory if it supported the new DNAS v2 protocol for YP >> updates. Any thoughts of adding support for that? > There are no plans to add that. And personally I would oppose such an

On 14 Feb 2020, at 21:46, Chip wrote: > > […] > > The second version above works because Icecast is configured > differently to > the first example - indeed, they're different versions: > > This doesn't work: > > [chip at machine]# icecast -v > Icecast 2.3.3-kh11-20150225150031 Hi, you are using Icecast-kh, this is quite different from the „normal“

El mié, 23-08-2017 a las 14:42 +0200, Marvin Scholz escribió: > > On 23 Aug 2017, at 14:40, José Luis Artuch wrote: > > > El mié, 23-08-2017 a las 14:13 +0200, Marvin Scholz escribió: > > > > > > On 23 Aug 2017, at 14:08, José Luis Artuch wrote: > > > > > > > Hello, good morning ! > > > > Running Icecast2 and Ices2 with live

On 18 Jan 2023, at 22:56, Damian wrote: > Another question: I see in the icecast config it states that "If a bind-address is not specified for a particular listen-socket, then the socket will be bound to all interfaces (including IPv6 if available). ? > > Are there any checks / tests that I could do at my end show if it is configured for IPV6 connections? The one below doesn?t seem

On 16 Jun 2017, at 5:41, Rick Keniuk wrote: > Is this the HTTP call for injecting the “song” metadata? > This is a capture (using RawCap in conjunction with Wireshark) of my > AAC+ stream metadata input to IceCast that works fine. > > GET > /admin/metadata?mode=updinfo&mount=%2FFVHradio_AAC&song=Fox%20Valley%20Hit%20radio%20-%20Hits%20from%20the%20Valley > HTTP/1.0

So why does the ices.conf file have <Protocol>http</Protocol> ic it is going to use icy anyways? On Fri, Feb 26, 2016 at 2:00 AM, Marvin Scholz <epirat07 at gmail.com> wrote: > On 26 Feb 2016, at 7:03, A. Craig West wrote: > > > I have been trying to access the "artist" and "title" metadata in the > > xml > > files as separate

On 16/06/17 18:47, Marvin Scholz wrote: > This concatenation are valid streams, it's called chaining, afaik. So > players not supporting them are broken and the authors should be > notified about it, I think. And my question is... Is THAT the way an OPUS source communicates new metadata to the icecast server?. That is the question I would like to know :-). -- Jesús Cea Avión

2020-01-08 09:59, Marvin Scholz wrote: > >> On Mon, 2020-01-06 at 10:24 +0000, user wrote: > > > > I'm consider to put icecast behind reverse proxy. It is not so easy as I > > think before. Does anyone have experience with it? > > In general putting Icecast behind a reverse proxy is not the best idea as > some webservers are not really made out of the box