From thedarkener at logicalnetworking.net  Mon Jan  2 21:21:27 2012
From: thedarkener at logicalnetworking.net (The Darkener)
Date: Mon, 02 Jan 2012 13:21:27 -0800
Subject: [Icecast] *Bump* ices2 memory leak on Debian/ARM
In-Reply-To: <4EEA9F41.5030506@logicalnetworking.net>
References: <4EEA9F41.5030506@logicalnetworking.net>
Message-ID: <4F021FD7.8040002@logicalnetworking.net>

Hi all,

I was really hoping to get a bit of help from this. I've since gone to
ezstream to try and accomplish the same goal, but ices2 is so simple to
use I would really like to stay with that instead.

Can anyone help me debug this memory leak? I can't use valgrind to try
and debug because it throws an "Illegal Instruction" whenever I try to
run it. :(


Happy New Year!
Jordan


On 12/15/2011 05:30 PM, TheDarkener wrote:
> Hi all.. I'm having a memory leak issue with Ices2 (using package
> 2.0.1-8 from Debian stable on arm platform)..
>
> I've tried turning off metadata, modifying samplerate, and some other
> misc. things that haven't helped. Eventually, during a stream, ices2
> will invoke oom-killer and bring the whole system down. It eats about
> 0.05MB/Sec of memory, so it takes a while, but this plug has 512mb, so
> about 2 hours into a stream, it will die.
>
> Any ideas? I can't seem to find anything online, especially regarding my
> arch. Nothing really shows up in the logs, even though I have ices set
> to 4 (debug) log output. I have a small portion of the strace output
> when running ices2... it keeps going, incrementing at the 'brk' calls...
> here: http://pastebin.com/5UHpM49s
>
> I have a system with identical configuration, only i386-based (an ASUS
> laptop). This system, with the same packages (but different arch)
> doesn't experience the memory leak.
>
> Any help or questions for me would be greatly appreciated :)
>
>
> Cheers,
> Jordan
>
>   


-- 
Jordan (PGP: 0xDA470FF8)



From doc at krushradio.com  Mon Jan  9 07:34:12 2012
From: doc at krushradio.com (Doc Nasty)
Date: Mon, 9 Jan 2012 01:34:12 -0600
Subject: [Icecast] EZSTREAM: Playlist Automation Script for Windows
Message-ID: <000901cccea1$15d1a8a0$4174f9e0$@krushradio.com>

Hey All,

Happy New Year!  I have a question regarding EZStream for Windows.  I saw in
one of the examples, I could use a script, such as a playlist.pl.  Is it
possible to use a custom .exe file, or a vbs/wsh script instead?  

Thanks,
Doc

-----Original Message-----
From: icecast-bounces at xiph.org [mailto:icecast-bounces at xiph.org] On Behalf
Of icecast-request at xiph.org
Sent: Tuesday, January 03, 2012 2:00 PM
To: icecast at xiph.org
Subject: Icecast Digest, Vol 92, Issue 1

Send Icecast mailing list submissions to
	icecast at xiph.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.xiph.org/mailman/listinfo/icecast
or, via email, send a message with subject or body 'help' to
	icecast-request at xiph.org

You can reach the person managing the list at
	icecast-owner at xiph.org

When replying, please edit your Subject line so it is more specific than
"Re: Contents of Icecast digest..."


Today's Topics:

   1. *Bump* ices2 memory leak on Debian/ARM (The Darkener)


----------------------------------------------------------------------

Message: 1
Date: Mon, 02 Jan 2012 13:21:27 -0800
From: The Darkener <thedarkener at logicalnetworking.net>
Subject: [Icecast] *Bump* ices2 memory leak on Debian/ARM
To: icecast at xiph.org
Message-ID: <4F021FD7.8040002 at logicalnetworking.net>
Content-Type: text/plain; charset=ISO-8859-1

Hi all,

I was really hoping to get a bit of help from this. I've since gone to
ezstream to try and accomplish the same goal, but ices2 is so simple to use
I would really like to stay with that instead.

Can anyone help me debug this memory leak? I can't use valgrind to try and
debug because it throws an "Illegal Instruction" whenever I try to run it.
:(


Happy New Year!
Jordan


On 12/15/2011 05:30 PM, TheDarkener wrote:
> Hi all.. I'm having a memory leak issue with Ices2 (using package
> 2.0.1-8 from Debian stable on arm platform)..
>
> I've tried turning off metadata, modifying samplerate, and some other 
> misc. things that haven't helped. Eventually, during a stream, ices2 
> will invoke oom-killer and bring the whole system down. It eats about 
> 0.05MB/Sec of memory, so it takes a while, but this plug has 512mb, so 
> about 2 hours into a stream, it will die.
>
> Any ideas? I can't seem to find anything online, especially regarding 
> my arch. Nothing really shows up in the logs, even though I have ices 
> set to 4 (debug) log output. I have a small portion of the strace 
> output when running ices2... it keeps going, incrementing at the 'brk'
calls...
> here: http://pastebin.com/5UHpM49s
>
> I have a system with identical configuration, only i386-based (an ASUS 
> laptop). This system, with the same packages (but different arch) 
> doesn't experience the memory leak.
>
> Any help or questions for me would be greatly appreciated :)
>
>
> Cheers,
> Jordan
>
>   


--
Jordan (PGP: 0xDA470FF8)



------------------------------

_______________________________________________
Icecast mailing list
Icecast at xiph.org
http://lists.xiph.org/mailman/listinfo/icecast


End of Icecast Digest, Vol 92, Issue 1
**************************************




From doc at krushradio.com  Tue Jan 10 02:04:51 2012
From: doc at krushradio.com (Doc Nasty)
Date: Mon, 9 Jan 2012 20:04:51 -0600
Subject: [Icecast] ices2 memory leak on Debian/ARM (The Darkener)
Message-ID: <004e01cccf3c$3dbcc2f0$b93648d0$@krushradio.com>

Justin,

I'm not a linux guy, or a that well versed on ICES, but, I went thru the
code (stream.c) and just kinda nosed around the broadcast part.  When we
look at distros that this uses, it may be the correct version of the
package, but it might actually be a supporting package, like curl or
something like that.  If you look at the code attached below, it shows there
might be some kind of memory leak that needs to be taken care of.  This is
in the sdsc stream description, which if I'm right, uses shout.  (#include
<shout/shout.h>)  

Maybe the error you're finding is because you have special chars, or bad
chars, and the version of shout you're using isn't right.  When I look at
the code below (sorry, can't read machine language to guess what you put
into pastebin).  Have you taken a chance to set your logging to a high level
to see what the error log says?  That may shed some light as to what the
error could be.  

But if you go thru the log and check out the errors, and then go back and
look at the stream.c file that's included in the source, you could search on
the error code, find where it's blowing up, and then try to figure out what
library it's using when it does.  There may be a different version of that
library for each different processor. 

    if(encoding)
    {
        if(inmod->metadata_update)
            inmod->metadata_update(inmod->internal, &sdsc->vc);
        sdsc->enc = encode_initialise(stream->channels, stream->samplerate,
                stream->managed, stream->min_br, stream->nom_br,
stream->max_br,
                stream->quality, &sdsc->vc);
        if(!sdsc->enc) {
            LOG_ERROR0("Failed to configure encoder");
            stream->died = 1;
            shout_free (sdsc->shout);
            sdsc->shout = NULL;
            return NULL; /* FIXME: probably leaking some memory here */
        }
        sdsc->enc->max_samples_ppage = sdsc->stream->max_samples_ppage;
    }

-----Original Message-----
From: icecast-bounces at xiph.org [mailto:icecast-bounces at xiph.org] On Behalf
Of icecast-request at xiph.org
Sent: Monday, January 09, 2012 2:00 PM
To: icecast at xiph.org
Subject: Icecast Digest, Vol 92, Issue 2

Send Icecast mailing list submissions to
	icecast at xiph.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.xiph.org/mailman/listinfo/icecast
or, via email, send a message with subject or body 'help' to
	icecast-request at xiph.org

You can reach the person managing the list at
	icecast-owner at xiph.org

When replying, please edit your Subject line so it is more specific than
"Re: Contents of Icecast digest..."


Today's Topics:

   1. EZSTREAM: Playlist Automation Script for Windows (Doc Nasty)


----------------------------------------------------------------------

Message: 1
Date: Mon, 9 Jan 2012 01:34:12 -0600
From: "Doc Nasty" <doc at krushradio.com>
Subject: [Icecast] EZSTREAM: Playlist Automation Script for Windows
To: <icecast at xiph.org>
Message-ID: <000901cccea1$15d1a8a0$4174f9e0$@krushradio.com>
Content-Type: text/plain;	charset="us-ascii"

Hey All,

Happy New Year!  I have a question regarding EZStream for Windows.  I saw in
one of the examples, I could use a script, such as a playlist.pl.  Is it
possible to use a custom .exe file, or a vbs/wsh script instead?  

Thanks,
Doc

-----Original Message-----
From: icecast-bounces at xiph.org [mailto:icecast-bounces at xiph.org] On Behalf
Of icecast-request at xiph.org
Sent: Tuesday, January 03, 2012 2:00 PM
To: icecast at xiph.org
Subject: Icecast Digest, Vol 92, Issue 1

Send Icecast mailing list submissions to
	icecast at xiph.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.xiph.org/mailman/listinfo/icecast
or, via email, send a message with subject or body 'help' to
	icecast-request at xiph.org

You can reach the person managing the list at
	icecast-owner at xiph.org

When replying, please edit your Subject line so it is more specific than
"Re: Contents of Icecast digest..."


Today's Topics:

   1. *Bump* ices2 memory leak on Debian/ARM (The Darkener)


----------------------------------------------------------------------

Message: 1
Date: Mon, 02 Jan 2012 13:21:27 -0800
From: The Darkener <thedarkener at logicalnetworking.net>
Subject: [Icecast] *Bump* ices2 memory leak on Debian/ARM
To: icecast at xiph.org
Message-ID: <4F021FD7.8040002 at logicalnetworking.net>
Content-Type: text/plain; charset=ISO-8859-1

Hi all,

I was really hoping to get a bit of help from this. I've since gone to
ezstream to try and accomplish the same goal, but ices2 is so simple to use
I would really like to stay with that instead.

Can anyone help me debug this memory leak? I can't use valgrind to try and
debug because it throws an "Illegal Instruction" whenever I try to run it.
:(


Happy New Year!
Jordan


On 12/15/2011 05:30 PM, TheDarkener wrote:
> Hi all.. I'm having a memory leak issue with Ices2 (using package
> 2.0.1-8 from Debian stable on arm platform)..
>
> I've tried turning off metadata, modifying samplerate, and some other 
> misc. things that haven't helped. Eventually, during a stream, ices2 
> will invoke oom-killer and bring the whole system down. It eats about 
> 0.05MB/Sec of memory, so it takes a while, but this plug has 512mb, so 
> about 2 hours into a stream, it will die.
>
> Any ideas? I can't seem to find anything online, especially regarding 
> my arch. Nothing really shows up in the logs, even though I have ices 
> set to 4 (debug) log output. I have a small portion of the strace 
> output when running ices2... it keeps going, incrementing at the 'brk'
calls...
> here: http://pastebin.com/5UHpM49s
>
> I have a system with identical configuration, only i386-based (an ASUS 
> laptop). This system, with the same packages (but different arch) 
> doesn't experience the memory leak.
>
> Any help or questions for me would be greatly appreciated :)
>
>
> Cheers,
> Jordan
>
>   


--
Jordan (PGP: 0xDA470FF8)



------------------------------

_______________________________________________
Icecast mailing list
Icecast at xiph.org
http://lists.xiph.org/mailman/listinfo/icecast


End of Icecast Digest, Vol 92, Issue 1
**************************************




------------------------------

_______________________________________________
Icecast mailing list
Icecast at xiph.org
http://lists.xiph.org/mailman/listinfo/icecast


End of Icecast Digest, Vol 92, Issue 2
**************************************




From keith at karsites.net  Tue Jan 10 15:43:31 2012
From: keith at karsites.net (Keith Roberts)
Date: Tue, 10 Jan 2012 15:43:31 +0000 (GMT)
Subject: [Icecast] ices2 memory leak on Debian/ARM (The Darkener)
In-Reply-To: <004e01cccf3c$3dbcc2f0$b93648d0$@krushradio.com>
References: <004e01cccf3c$3dbcc2f0$b93648d0$@krushradio.com>
Message-ID: <alpine.LRH.2.02.1201101536350.18479@karsites.localdomain>

On Mon, 9 Jan 2012, Doc Nasty wrote:

> To: icecast at xiph.org
> From: Doc Nasty <doc at krushradio.com>
> Subject: Re: [Icecast] ices2 memory leak on Debian/ARM (The Darkener)
> 
> Justin,
>
> I'm not a linux guy, or a that well versed on ICES, but, I went thru the
> code (stream.c) and just kinda nosed around the broadcast part.  When we
> look at distros that this uses, it may be the correct version of the
> package, but it might actually be a supporting package, like curl or
> something like that.  If you look at the code attached below, it shows there
> might be some kind of memory leak that needs to be taken care of.  This is
> in the sdsc stream description, which if I'm right, uses shout.  (#include
> <shout/shout.h>)

There's a Linux memory profiler called:

"Valgrind" is a multipurpose code profiling and memory 
debugging tool for Linux when on the x86 and, as of version 
3, AMD64, architectures. It allows you to run your program 
in Valgrind's own environment that monitors memory usage 
such as calls to malloc and free (or new and delete in C++). 
If you use uninitialized memory, write off the end of an 
array, or forget to free a pointer, Valgrind can detect it. 
Since these are particularly common problems, this tutorial 
will focus mainly on using Valgrind to find these types of 
simple memory problems, though Valgrind is a tool that can 
do a lot more.

that might help you out. I've used it to find programs 
running under Linux with bad memory management.

For other memory leakage tools, just Google for something 
like: memory leak detection tools

Kind Regards,

Keith Roberts

-----------------------------------------------------------
Websites:
http://www.karsites.net
http://www.php-debuggers.net
http://www.raised-from-the-dead.org.uk

All email addresses are challenge-response protected with
TMDA [http://tmda.net]
-----------------------------------------------------------


From thedarkener at logicalnetworking.net  Tue Jan 10 23:02:01 2012
From: thedarkener at logicalnetworking.net (TheDarkener)
Date: Tue, 10 Jan 2012 15:02:01 -0800
Subject: [Icecast] ices2 memory leak on Debian/ARM (The Darkener)
In-Reply-To: <alpine.LRH.2.02.1201101536350.18479@karsites.localdomain>
References: <004e01cccf3c$3dbcc2f0$b93648d0$@krushradio.com>
	<alpine.LRH.2.02.1201101536350.18479@karsites.localdomain>
Message-ID: <4F0CC369.40600@logicalnetworking.net>

Hi Keith,

As I explained before, Valgrind won't run in my arch. I'll Google for
some other memory leak detection tools, however. Thank you for your
input...I look forward to helping fix this bug!

- Jordan

On 01/10/2012 07:43 AM, Keith Roberts wrote:
> *snip*
> There's a Linux memory profiler called:
>
> "Valgrind" is a multipurpose code profiling and memory 
> debugging tool for Linux when on the x86 and, as of version 
> 3, AMD64, architectures. It allows you to run your program 
> in Valgrind's own environment that monitors memory usage 
> such as calls to malloc and free (or new and delete in C++). 
> If you use uninitialized memory, write off the end of an 
> array, or forget to free a pointer, Valgrind can detect it. 
> Since these are particularly common problems, this tutorial 
> will focus mainly on using Valgrind to find these types of 
> simple memory problems, though Valgrind is a tool that can 
> do a lot more.
>
> that might help you out. I've used it to find programs 
> running under Linux with bad memory management.
>
> For other memory leakage tools, just Google for something 
> like: memory leak detection tools
>
> Kind Regards,
>
> Keith Roberts
>
> -----------------------------------------------------------
> Websites:
> http://www.karsites.net
> http://www.php-debuggers.net
> http://www.raised-from-the-dead.org.uk
>
> All email addresses are challenge-response protected with
> TMDA [http://tmda.net]
> -----------------------------------------------------------
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


-- 
Jordan (PGP: 0xDA470FF8)



From thedarkener at logicalnetworking.net  Wed Jan 11 01:31:05 2012
From: thedarkener at logicalnetworking.net (TheDarkener)
Date: Tue, 10 Jan 2012 17:31:05 -0800
Subject: [Icecast] ices2 memory leak on Debian/ARM (The Darkener)
In-Reply-To: <ef32c94c-063b-431a-97f0-b5b6a422679c@email.android.com>
References: <004e01cccf3c$3dbcc2f0$b93648d0$@krushradio.com>
	<alpine.LRH.2.02.1201101536350.18479@karsites.localdomain>
	<4F0CC369.40600@logicalnetworking.net>
	<ef32c94c-063b-431a-97f0-b5b6a422679c@email.android.com>
Message-ID: <4F0CE659.3050200@logicalnetworking.net>

ARM, default install on an Ionics Stratus plug computer -
http://www.ionicsplug.com/stratus.html ) - running Current Debian Stable.

- Jordan


On 01/10/2012 03:13 PM, Christian Eichert [K9] wrote:
> Can you describe your architecture?
> -- 
> Christian Eichert
>
> ------------------------------------------------------------------------
> *Von:* TheDarkener <thedarkener at logicalnetworking.net>
> *Gesendet:* Wed Jan 11 00:02:01 MEZ 2012
> *An:* icecast at xiph.org
> *Betreff:* Re: [Icecast] ices2 memory leak on Debian/ARM (The Darkener)
>
> Hi Keith,
>
> As I explained before, Valgrind won't run in my arch. I'll Google for
> some other memory leak detection tools, however. Thank you for your
> input...I look forward to helping fix this bug!
>
> - Jordan
>
> On 01/10/2012 07:43 AM, Keith Roberts wrote:
> > *snip*
> > There's a Linux memory profiler called:
> >
> > "Valgrind" is a multipurpose code profiling and memory 
> > debugging tool for Linux when on the x86 and, as of version 
> > 3, AMD64, architectures. It allows you to run your program 
> > in Valgrind's own environment that monitors memory usage 
> > such as calls to malloc and free (or new and delete in C++). 
> > If you use uninitialized memory, write off the end of an 
> > array, or forget to free a pointer, Valgrind can detect it. 
> > Since these are particularly common proble
>  ms,
> this tutorial 
> > will focus mainly on using Valgrind to find these types of 
> > simple memory problems, though Valgrind is a tool that can 
> > do a lot more.
> >
> > that might help you out. I've used it to find programs 
> > running under Linux with bad memory management.
> >
> > For other memory leakage tools, just Google for something 
> > like: memory leak detection tools
> >
> > Kind Regards,
> >
> > Keith Roberts
> >
> >
> ------------------------------------------------------------------------
>
> > Websites:
> > http://www.karsites.net
> > http://www.php-debuggers.net
> > http://www.raised-from-the-dead.org.uk
> >
> > All email addresses are challenge-response protected with
> > TMDA [http://tmda.net]
> >
> ------------------------------------------------------------------------
>
> >
> ------------------------------------------------------------------------
>
> > 
>  Icecast
> mailing list
> > Icecast at xiph.org
> > http://lists.xiph.org/mailman/listinfo/icecast
>
>
> -- 
> Jordan (PGP: 0xDA470FF8)
>
> ------------------------------------------------------------------------
>
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>


-- 
Jordan (PGP: 0xDA470FF8)



From eichertc at googlemail.com  Wed Jan 11 11:50:28 2012
From: eichertc at googlemail.com (Christian Eichert [Gmail])
Date: Wed, 11 Jan 2012 12:50:28 +0100
Subject: [Icecast] ices2 memory leak on Debian/ARM (The Darkener)
In-Reply-To: <4F0CE659.3050200@logicalnetworking.net>
References: <004e01cccf3c$3dbcc2f0$b93648d0$@krushradio.com>
	<alpine.LRH.2.02.1201101536350.18479@karsites.localdomain>
	<4F0CC369.40600@logicalnetworking.net>
	<ef32c94c-063b-431a-97f0-b5b6a422679c@email.android.com>
	<4F0CE659.3050200@logicalnetworking.net>
Message-ID: <4F0D7784.7040808@googlemail.com>

Sorry to interrupt

but for such devices you should use Optware. - It is created for this 
kind of hardware.

http://www.nslu2-linux.org/wiki/Optware/HomePage

Here is the Bootstrap for ARM
http://ipkg.nslu2-linux.org/feeds/optware/syno-x07/cross/unstable/syno-x07-bootstrap_1.2-7_arm.xsh

and in this repository you find a Ices

Package: ices0
Version: 0.4-2
Depends: libshout, libxml2, perl
Status: install user installed
Section: multimedia
Architecture: powerpc
maintainer: NSLU2 Linux <nslu2-linux at yahoogroups.com>
MD5Sum: b272e8d4e7d5c579f9fc1ffd4ec5dbc0
Size: 38618
Filename: ices0_0.4-2_powerpc.ipk
Source: http://downloads.us.xiph.org/releases/ices/ices-0.4.tar.gz
Description: source client for broadcasting in MP3 format to an icecast2 
server


regards.
Christian

Am 11.01.2012 02:31, schrieb TheDarkener:
> ARM, default install on an Ionics Stratus plug computer -
> http://www.ionicsplug.com/stratus.html ) - running Current Debian Stable.
>
> - Jordan
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4391 bytes
Desc: S/MIME Kryptografische Unterschrift
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20120111/1f7eb116/attachment.bin>

From thedarkener at logicalnetworking.net  Thu Jan 12 07:23:14 2012
From: thedarkener at logicalnetworking.net (TheDarkener)
Date: Wed, 11 Jan 2012 23:23:14 -0800
Subject: [Icecast] ices2 memory leak on Debian/ARM (The Darkener)
In-Reply-To: <4F0D7784.7040808@googlemail.com>
References: <004e01cccf3c$3dbcc2f0$b93648d0$@krushradio.com>	<alpine.LRH.2.02.1201101536350.18479@karsites.localdomain>	<4F0CC369.40600@logicalnetworking.net>	<ef32c94c-063b-431a-97f0-b5b6a422679c@email.android.com>	<4F0CE659.3050200@logicalnetworking.net>
	<4F0D7784.7040808@googlemail.com>
Message-ID: <4F0E8A62.8030903@logicalnetworking.net>

I think I might have inadvertently worked around the problem by setting
my sample rate to 22050 from 44100... as to why that would stop a memory
leak, I don't know, but my stream has been going strong for 3+ hours
now, with only 33MB used RAM total =D I'm following up tomorrow with
someone to see if it might be an underlying problem somewhere that can
be remedied. But for now, it looks like my immediate crisis has been
averted! =)


- Jordan


-- 
Jordan (PGP: 0xDA470FF8)



From mcbicecast at robuust.nl  Thu Jan 12 22:56:12 2012
From: mcbicecast at robuust.nl (Maarten Bezemer)
Date: Thu, 12 Jan 2012 23:56:12 +0100 (CET)
Subject: [Icecast] ices2 memory leak on Debian/ARM (The Darkener)
In-Reply-To: <4F0CC369.40600@logicalnetworking.net>
References: <004e01cccf3c$3dbcc2f0$b93648d0$@krushradio.com>
	<alpine.LRH.2.02.1201101536350.18479@karsites.localdomain>
	<4F0CC369.40600@logicalnetworking.net>
Message-ID: <Pine.LNX.4.64.1201122350530.15588@wormhole.robuust.nl>


On Tue, 10 Jan 2012, TheDarkener wrote:

> As I explained before, Valgrind won't run in my arch. I'll Google for
> some other memory leak detection tools, however. Thank you for your
> input...I look forward to helping fix this bug!

If it is a memory leak because of some bug in the source code, using 
Valgrind on one of its supported platforms would probably be a smart thing 
to do. Fix the source code and recompile on any other platform, and the 
bug should be gone ;-)

Admittedly, x86 and amd64 may not have the exact same issues, e.g. 
data-alignment may be different, but memory leaks should still be memory 
leaks.

Just my 2 cents..

-- 
Maarten



From tom at swirly.com  Thu Jan 19 20:28:58 2012
From: tom at swirly.com (Tom Swirly)
Date: Thu, 19 Jan 2012 15:28:58 -0500
Subject: [Icecast] artist and song for mp3 streams?;
 and, canonical list of legal value-ofs that can be used in XSLT!
Message-ID: <CAOuQWfVBkXOCnNCqNHyBQ0xS8Ks1VzQEpuHFR9imf=e3zarhZg@mail.gmail.com>

Hello, Iceys!

Two related questions here.  First, I've just finished a little icecast ->
twitter script that's working nicely, and I've also discovered quite a bit
about icecast (the main thing is that it's dead easy to set up on Ubuntu -
I got a working radio station the first time with almost no debugging!
 Good job, guys.)

Now, on mp3 streams I only get a value for  <xsl:value-of select="title" />
and not for "artist" or "song".  Looking at the code, it appears as if the
artist value is only filled in for Ogg streams.


   1. Is there some hope of getting the artist or song from mp3 streams?
    If the developers would take a patch, I could fairly likely make the
   change myself, it doesn't seem that hard (after looking at it for all of 30
   seconds, that is...)
   2. Is there a canonical list of all the legal values you can get from an
   icecast server in a template by using <xsl:value-of select="..."> ?


This isn't critical - I'm getting good results already - but I'm always
interested in improving.  Thanks in advance!

-- 
     /t

http://radio.swirly.com - art music radio 24/7 366/1000
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20120119/06ac2ac2/attachment.htm>

From michel.memeteau at gmail.com  Sat Jan 21 21:15:35 2012
From: michel.memeteau at gmail.com (michel memeteau)
Date: Sat, 21 Jan 2012 22:15:35 +0100
Subject: [Icecast] Shoutcast directory listing?
In-Reply-To: <4E4023BD.8040403@xiph.org>
References: <4E4019BE.2000405@cognisys.com> <4E4023BD.8040403@xiph.org>
Message-ID: <CAJbJ1Bsagp53YnK=iTgACM4wVnKTk2at9C-xad46GuAAzUXDqw@mail.gmail.com>

HI , Sorry as I did not read all the thread , but I answer from here :

2011/8/8 Karl Heyes <karl at xiph.org>:
> On 08/08/11 18:15, Raymond Lutz wrote:
>> I've been reading posts on the difficulty in getting an icecast stream
>> listed in the shoutcast directory.
> you should be able to allow shoutcast to relay icecast by adding an
> alias of / to /stream <alias source="/" dest="/stream" />

I know this is off-topic , but if it works people would use icecast as
main server and shoutcast as a relay , as it should be.

I've been doing this for few weeks and just discover that the soutcast
server did not appear  in the Shoutcast yellow pages.

I fixed some stuff :

- in the shoutcast config , the "default" setting for the public state
if the server has to be set to 'always' in order to have the server
trying to publish to SYP.
- But then , the shoucast will say

[yp_add] yp.shoutcast.com gave error (nak)
[yp_add] yp.shoutcast.com gave extended error (Bitrate too small.)


I then specify the bitrate in the mount config that is relayed but it
didn't change anything, still failing at registering to SYP.


Do you have an idea about how icecast could be relayed correctly by shoutcast ?


Thanks









-- 
<------------------------------------------------------->
web perso : http://memeteau.com
Boutique Ordinateurs GNU/Linux : http://shop.ekimia.fr
Fixe :? 0974763294 Mobile : 0624808051


From geoff at QuiteLikely.com  Sun Jan 29 20:21:47 2012
From: geoff at QuiteLikely.com (Geoff Shang)
Date: Sun, 29 Jan 2012 22:21:47 +0200 (IST)
Subject: [Icecast] HTPasswd format and protecting XSL pages
Message-ID: <alpine.DEB.2.00.1201292126120.3284@data.home>

Hi,

I had a need to look at icecast.org yesterday.  Despite the fact that it 
had been there for over 3 years (since the last release), I only just 
noticed that XSL pages can be password-protected using the same auth 
mechanism available to other items.  I was very interested in this as I 
wanted to be able to protect our stats info without giving those with a 
right to access it the admin password of the server.

Unfortunately, the Icecast documentation didn't give an example of how to 
do this.  It did talk about authentication in general and how to apply it 
to mounts 
(http://icecast.org/docs/icecast-2.3.2/icecast2_listenerauth.html) so I 
took that as a starting point.

I added a <mount> section and used "/status.xsl" as the mount-name and 
used the auth example found in one of the config files.  All well and good 
- instead of the page coming up straight away, I got an authentication 
prompt.  But this is about as far as I got.

Since I want to use the same credentials as an area of the website, I 
thought that maybe I could use the .htpasswd file I use for that.  It 
didn't work.

So I did a bit of searching and turned up 
http://www.barnyardbbs.com/Projects/Streaming/ where it is asserted that 
Icecast2 htpasswd files use MD5 hashes (the Icecast2 documentation doesn't 
say what is used).  So I reran htpasswd(1) with the -m switch and 
recreated the entry in the .htpasswd file in use for the website, in order 
to encode it with MD5 instead of CRYPT.  But this didn't make any 
difference either - I still couldn't authenticate.

So I gave up doing this and decided to try doing what the manual says to 
do - use the admin interface to create the entries in the HTPasswd file. 
But I hit a problem - a rather obvious problem in that /status.xsl is not 
an active source which can be clicked on.  So I tried going to 
/admin/manageauth.xsl but nothing showed up there either.  And I tried 
/admin/manageauth.xsl?mount=/status.xsl but I got a 400 Bad Request error 
with the message "Source does not exist".

So I'm somewhat stuck.  The Icecast release announcement for 2.3.2 says 
this can be done, and the config file part of it seems to work.  But I 
can't see how I'm meant to either generate the htpasswd file externally in 
such a way that Icecast2 can understand it, or persuade Icecast2 itself to 
do it when it's not a traditional source as such.

Any advice anyone could give would help.

Thanks,
Geoff.



From tom at swirly.com  Tue Jan 31 01:58:20 2012
From: tom at swirly.com (Tom Swirly)
Date: Mon, 30 Jan 2012 20:58:20 -0500
Subject: [Icecast] Making a smooth transition between sources?
Message-ID: <CAOuQWfWTd3QcgAAXb+yFjiqaKnakxMCGFRJ=xOwRErW93h1kyw@mail.gmail.com>

Hello!

I'm setting up an icecast radio station.  I'll usually be broadcasting from
this machine, but want to be able to make a smooth transition to an
ezstream instance that I can run on the same server as the radio station.

Unfortunately, my experiments haven't found a way I can make a transition
without knocking off all my clients.  :-(

Any idea about best practices on this?

-- 
     /t

http://radio.swirly.com - art music radio 24/7 366/1000
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20120130/8538e456/attachment.htm>

From brandon at loudcity.net  Tue Jan 31 02:00:57 2012
From: brandon at loudcity.net (Brandon Casci)
Date: Mon, 30 Jan 2012 21:00:57 -0500
Subject: [Icecast] Making a smooth transition between sources?
In-Reply-To: <CAOuQWfWTd3QcgAAXb+yFjiqaKnakxMCGFRJ=xOwRErW93h1kyw@mail.gmail.com>
References: <CAOuQWfWTd3QcgAAXb+yFjiqaKnakxMCGFRJ=xOwRErW93h1kyw@mail.gmail.com>
Message-ID: <CACRQB3LQeVfQ7NTPgsBUgQ4X3RvhJJatGC2mpS=R29D4FG1aeA@mail.gmail.com>

What are you listening with? I've noticed that some clients drop
connections, like Flash, when mounts fallback while other, like iTunes,
TuneIn, QuickTime mobile, don't.

On Mon, Jan 30, 2012 at 8:58 PM, Tom Swirly <tom at swirly.com> wrote:

> Hello!
>
> I'm setting up an icecast radio station.  I'll usually be broadcasting
> from this machine, but want to be able to make a smooth transition to an
> ezstream instance that I can run on the same server as the radio station.
>
> Unfortunately, my experiments haven't found a way I can make a transition
> without knocking off all my clients.  :-(
>
> Any idea about best practices on this?
>
> --
>      /t
>
> http://radio.swirly.com - art music radio 24/7 366/1000
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
>


-- 
=========================================
Brandon Casci
Loudcaster
http://loudcaster.com
=========================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20120130/44338dc0/attachment.htm>

From email at christianeichert.de  Tue Jan 10 23:20:32 2012
From: email at christianeichert.de (Christian Eichert [K9])
Date: Tue, 10 Jan 2012 23:20:32 -0000
Subject: [Icecast] ices2 memory leak on Debian/ARM (The Darkener)
In-Reply-To: <4F0CC369.40600@logicalnetworking.net>
References: <004e01cccf3c$3dbcc2f0$b93648d0$@krushradio.com>
	<alpine.LRH.2.02.1201101536350.18479@karsites.localdomain>
	<4F0CC369.40600@logicalnetworking.net>
Message-ID: <ef32c94c-063b-431a-97f0-b5b6a422679c@email.android.com>

Can you describe your architecture?
-- 
Christian Eichert

_____________________________________________
Von: TheDarkener <thedarkener at logicalnetworking.net>
Gesendet: Wed Jan 11 00:02:01 MEZ 2012
An: icecast at xiph.org
Betreff: Re: [Icecast] ices2 memory leak on Debian/ARM (The Darkener)


Hi Keith,

As I explained before, Valgrind won't run in my arch. I'll Google for
some other memory leak detection tools, however. Thank you for your
input...I look forward to helping fix this bug!

- Jordan

On 01/10/2012 07:43 AM, Keith Roberts wrote:
> *snip*
> There's a Linux memory profiler called:
>
> "Valgrind" is a multipurpose code profiling and memory 
> debugging tool for Linux when on the x86 and, as of version 
> 3, AMD64, architectures. It allows you to run your program 
> in Valgrind's own environment that monitors memory usage 
> such as calls to malloc and free (or new and delete in C++). 
> If you use uninitialized memory, write off the end of an 
> array, or forget to free a pointer, Valgrind can detect it. 
> Since these are particularly common problems, this tutorial 
> will focus mainly on using Valgrind to find these types of 
> simple memory problems, though Valgrind is a tool that can 
> do a lot more.
>
> that might help you out. I've used it to find programs 
> running under Linux with bad memory management.
>
> For other memory leakage tools, just Google for something 
> like: memory leak detection tools
>
> Kind Regards,
>
> Keith Roberts
>
>_____________________________________________

> Websites:
> http://www.karsites.net
> http://www.php-debuggers.net
> http://www.raised-from-the-dead.org.uk
>
> All email addresses are challenge-response protected with
> TMDA [http://tmda.net]
>_____________________________________________

>_____________________________________________

> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


-- 
Jordan (PGP: 0xDA470FF8)

_____________________________________________

Icecast mailing list
Icecast at xiph.org
http://lists.xiph.org/mailman/listinfo/icecast

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20120110/587e1f68/attachment.htm>