similar to: Source Drops, metadata, and source limits in setup

Good morning, On Sat, 2017-07-15 at 20:51 +0000, ScanCaster wrote: > On Fri, 14 Jul 2017 09:16:34 +0000, Philipp Schafft wrote: > > > This posting confirms me in that I should write a separate e-mail to the > > list on how metadata updates work and how they should be implemented on > > the source side. > > And what is different in the way this is updated??? The

I use Let's Encrypt for SSL with icecast. Here is my rudimentary script on GitHub... It does NOT require Apache or nginx. https://github.com/amavarick/letsencrypt_certbot_standalone_icecast On Jul 10, 2017, at 9:39 AM, ScanCaster <scancaster at scancaster.net<mailto:scancaster at scancaster.net>> wrote: On Mon, 10 Jul 2017 09:31:06 +0000, Philipp Schafft wrote: Good morning,

Hello ! El lun, 10-07-2017 a las 09:31 +0000, Philipp Schafft escribi?: > Good morning, > > > On Mon, 2017-07-10 at 01:25 +0000, ScanCaster wrote: > > IceCast is one of the last services I have that doesn't connect > > securely,? > > and I am looking to close that hole.... > > [...] > > OK... add a port for SSL for IceCast in icecast.xml...path for

El vie, 21-07-2017 a las 19:07 +0200, Marvin Scholz escribi?: > > On 21 Jul 2017, at 18:41, Jos? Luis Artuch wrote: > > > Hello ! > > > > El lun, 10-07-2017 a las 09:31 +0000, Philipp Schafft escribi?: > > > Good morning, > > > > > > > > > On Mon, 2017-07-10 at 01:25 +0000, ScanCaster wrote: > > > > IceCast is one of

Thanks bubba, but I am referring to the meaning of the line: "... INFO connection/get_ssl_certificate No SSL capability" El vie, 11-08-2017 a las 13:37 -0500, bubba watson escribi?: > It is a server message indicator. It is used to distinguish server > messages. > > Sent from my iPhone > > > On Aug 11, 2017, at 13:28, Jos? Luis Artuch <artuch at

update string? In-Reply-To: <02b501c4788b$e1df6dc0$a601a8c0@recorder> References: <02b501c4788b$e1df6dc0$a601a8c0@recorder> Message-ID: <1091461406.2970.15.camel@bogus.hackers.club> On Mon, 2004-08-02 at 13:25, Nagy Gergely - K?k Duna R?di? wrote: > Hello everybody, hello Karl! hi > Sorry for my horrible English. I'm a newbie in icecast2. > I would like to use the

Hi ! Still fighting here :) /var/log/icecast2/error.log ... [2017-08-08??03:05:34] INFO main/main Icecast 2.4.2 server started [2017-08-08??03:05:34] INFO connection/get_ssl_certificate No SSL capability *** [2017-08-08??03:05:34] INFO yp/yp_update_thread YP update thread started ... What exactly does *** mean ?. Thanks ! Jos? Luis El vie, 21-07-2017 a las 19:44 +0200, Marvin Scholz escribi?:

update string? Message-ID: <02b501c4788b$e1df6dc0$a601a8c0@recorder> Hello everybody, hello Karl! Sorry for my horrible English. I'm a newbie in icecast2. I would like to use the /admin/metadata?mount=/mymount.ogg&mode=updinfo&song=New%20Title string to update metadata with -kh48 (to update metadata with ogg stream :) ) but I couldn't find how to insert admin username and

Good morning, On Mon, 2017-07-10 at 01:25 +0000, ScanCaster wrote: > IceCast is one of the last services I have that doesn't connect securely, > and I am looking to close that hole.... > [...] > OK... add a port for SSL for IceCast in icecast.xml...path for cert file > in same.... no biggie The <ssl-certificate> belongs in the <paths> section of the config

On 06/06/2014 01:08 PM, uno wrote: > ... to answer myself: > > i had a fallback-mount specified, after removing it > things work as expected. sorry for the noise. In case of fallbacks you have to check properly through querying a custom XSL, JSON or the admin backend. > btw: what's the prefered way to get server and/or listener info?

just parse status-json.xsl with php's curl/json_parse... ScanCaster: > On Mon, 12 Mar 2018 22:07:34 +0100, Jeroen van Oosten wrote: > > > Well, you can create your own XSL with less data. I use this (as > > web/simple.xsl): > > Well since I don't know XSL, BASH etc. was my go to choice... > > BUT... > > Doing this gets > 404's from a

Monday, July 12, 2004, 4:49:57 Michael Smith wrote: MS> You should be able to get this information from the access logs. There's no MS> software I know of to do that automatically for you, though - you might have MS> to write your own. As I understand, access logs do not contain any informatin about the time a listener has been connected for. But I found such an internal variable in

Good evening, On Wed, 2018-07-18 at 14:21 +0000, ScanCaster wrote: > On Thu, 12 Jul 2018 15:12:05 +0000, Philipp Schafft wrote: > > > You already guessed it: Using relays. > > > > Try something like: > > <relay> > > <server>localhost</server> > > <port>8000</port> > >

On Tuesday, 07 August 2001 at 12:56, Richard Fromm wrote: > i've been trying to get title streaming of metadata to work with icecast > 1.3.10. i've found what i believe to be a bug -- is this the right place to > file a bug report? I think so. > it appears that this information should be periodically inserted into the data > stream. the behavior that i was seeing was

Good afternoon, On Tue, 2018-07-31 at 10:36 -0400, Jordan Verner wrote: > Hi, > I am writing a source client (from scratch). Mind to share a link with the community? > I’ve got the actual audio streaming part worked out just fine, but the > metadata has me scratching my head a little bit. > According to the docs, to update metadata for an mp3 stream Yes. And only for MP3 and

Nevermind, that stats.xml page is worthless anyways. got a updated version of icecast2 status http://www.casterclub.com/icecast_status.php parses the status2.xsl page <p><p>Dave St John (C.E.O.) Xstream1.com Mediacast1.com Casterclub.com (720-641-7586) ----- Original Message ----- From: "Dave St John" <dstjohn@mediacast1.com> To: <icecast-dev@xiph.org> Sent:

Hi, I am writing a source client (from scratch). I’ve got the actual audio streaming part worked out just fine, but the metadata has me scratching my head a little bit. According to the docs, to update metadata for an mp3 stream you’re supposed to issue an http request like this: http://hostname:port/admin/metadata?mode=updinfo&mount=/station&song=test

On 19 Sep 2019, at 16:46, ScanCaster wrote: > So ffmpeg can pull the metadata out of a stream and if its updated can > parse it out, at least according to the documentation... > > I am just not finding any info on what I am supposed to "poll" and read > to get this data????? > > ffmpeg -icy 1 -hide_banner -reconnect 1 -reconnect_at_eof 1 - > reconnect_streamed 1

Hi there Relay is the answer! Have not tried this but makes logically sense. Best regards On Thu, Jul 12, 2018 at 3:59 PM, ScanCaster <scancaster at scancaster.net> wrote: > I have a situation where it would be desirable to provide a mount/stream, > but in a rather unique fashion. > > We will call the feed Radio. > > My source would encode via DarkIce/EZStream etc. and

Hi there, Icecast 2.4 introduced the « PUT » HTTP method for sources, which is not supported by Icecast 2.3 (that uses the legacy « SOURCE » method). This may explain why your piece of software works with Icecast 2.4 but not with 2.3. You should find relevant lines regarding this issue in your Icecast 2.3 logfiles. > Le 25 juil. 2018 à 18:00, ScanCaster <scancaster at scancaster.net>