[prev in list] [next in list] [prev in thread] [next in thread]
List: icecast
Subject: Re: [Icecast] Shoutcast directory listing?
From: Raymond Lutz <raylutz () cognisys ! com>
Date: 2012-03-01 18:25:22
Message-ID: 4F4FBF12.3090908 () cognisys ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
I don't think -- from what I've been able to discern -- that your
scenario below will work, starting with "once you've done that".
My own attempts to get something going in this regard stopped even
earlier, as I as attempting not to use a winamp source but a
server-based playlist. Shoutcast folks were apparently moving to Y2
support and their side was seriously broken at the time.
It took a lot of trial and error to get the shoutcast machine set up.
Finally, this configuration worked.
portbase srcip destip serverport_1 serverip_1
8080 (no spec) (no spec) 8080 localhost
My strategy was as follows:
1. Try to get listed on shoutcast with a fixed playlist on the server. I
haven't solved this yet, but should probably try again.
2. See if your theory that it is possible to relay an icecast stream
through shoutcast and be correctly listed. I have a humch this may not work.
3. If not, then run the icecast server and shoutcast servers in
parallel. Since my station at http://www.AirProgressive.org uses an
extensive perl script to "get_next" track to play, this will likely need
to be recoded slightly to become a wrapper around a call to a program
that can be called by Shoutcast and will generate the same track.
I wonder if anyone has actually tried relaying a stream through
shoutcast AND getting it listed. It would save me a lot of time if we
can settle whether this actually works or not.
--Ray
On 3/1/2012 7:48 AM, Leo Currie wrote:
> I think the message is pretty clear: The Shoutcast directory only
> lists Shoutcast servers.
>
> However, it would seem logical that if a Shoutcast server was setup to
> relay an Icecast server (i.e. the Shoutcast source is an Icecast
> server) then it would still be listed in the Shoutcast directory as
> normal.
> I would assume that the goal of this kind of setup would be to gain a
> wider audience.
> However, it should be understood that any listeners arriving from the
> Shoutcast directory would connect to the Shoutcast server, not the
> Icecast server.
>
> I've never tried this, but assuming you have a working Icecast server,
> I imagine the steps to getting the Shoutcast relay working would be:
> 1) Setup a Shoutcast server
> 2) Setup the default Shoutcast source client (Winamp?)
> 3) Test that the server works with a Shoutcast listener client (Winamp
> again!)
> 4) Test that the server is then being listed in the public Shoutcast
> directory
>
> Once you've done that, then you could switch over and use Icecast as a
> source:
> 5) Configure Icecast to provide the correct content when Shoutcast
> requests a stream (that's the <alias> directive stuff)
> 6) Reconfigure Shoutcast to relay Icecast
> 7) Repeat step 3 & 4.
>
> I'm not sure if others agree, but 'on-topic' for this list would just
> be step (5) above.
> The rest of the steps would probably be better answered on the
> Shoutcast forums, but you might find others on this list with more
> experience who can add something.
>
> Leo
>
>
> On 29 February 2012 16:48, Romain Beauxis <toots@rastageeks.org
> <mailto:toots@rastageeks.org>> wrote:
>
> Hi all,
>
> 2012/2/29 Tom Swirly <tom@swirly.com <mailto:tom@swirly.com>>:
> > On Wed, Feb 29, 2012 at 11:29 AM, Raymond Lutz
> <raylutz@cognisys.com <mailto:raylutz@cognisys.com>> wrote:
> >>
> >> This is absolutely not "off-topic" and if this list will not
> support this
> >> VERY IMPORTANT discussion, then I will be happy to host the
> discussion on a
> >> different list for those who are interested. I have been trying
> to solve
> >> this for some time. Much of the problem so far has been
> Shoutcast internal
> >> problems (on their site) which I assume are cleared up now. My
> current
> >> assumption is it will be necessary to establish a second
> shoutcast server
> >> just to get in their directory.
> >
> >
> > Generally this list has been extremely accepting of sincere
> questions
> > relating to internet radio!
> >
> > My theory is simply that no one knows the answer, not that
> people are
> > believing the question is off-topic.
>
> I do not believe that this is off-topic at all. However, I personally
> do not wish to support shoutcast YP technology, even though I
> understand the importance of being listed there.
>
> Romain
> _______________________________________________
> Icecast mailing list
> Icecast@xiph.org <mailto:Icecast@xiph.org>
> http://lists.xiph.org/mailman/listinfo/icecast
>
>
>
>
> _______________________________________________
> Icecast mailing list
> Icecast@xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
[Attachment #5 (text/html)]
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I don't think -- from what I've been able to discern -- that your
scenario below will work, starting with "once you've done that".<br>
My own attempts to get something going in this regard stopped even
earlier, as I as attempting not to use a winamp source but a
server-based playlist. Shoutcast folks were apparently moving to Y2
support and their side was seriously broken at the time.<br>
<br>
It took a lot of trial and error to get the shoutcast machine set
up.<br>
<br>
Finally, this configuration worked.<br>
portbase srcip destip \
serverport_1 serverip_1<br> 8080 (no spec) \
(no spec) 8080 localhost \
<br> <br>
My strategy was as follows:<br>
1. Try to get listed on shoutcast with a fixed playlist on the
server. I haven't solved this yet, but should probably try again.<br>
2. See if your theory that it is possible to relay an icecast stream
through shoutcast and be correctly listed. I have a humch this may
not work.<br>
3. If not, then run the icecast server and shoutcast servers in
parallel. Since my station at <a class="moz-txt-link-freetext" \
href="http://www.AirProgressive.org">http://www.AirProgressive.org</a> uses an \
extensive perl script to "get_next" track to play, this will likely need to be \
recoded slightly to become a wrapper around a call to a program that can be called \
by Shoutcast and will generate the same track.<br>
<br>
I wonder if anyone has actually tried relaying a stream through
shoutcast AND getting it listed. It would save me a lot of time if
we can settle whether this actually works or not.<br>
<br>
--Ray<br>
<br>
On 3/1/2012 7:48 AM, Leo Currie wrote:
<blockquote
cite="mid:CANBFD3pBnMd_ZHRu5uYx=HfpPRd6n83b-YQaUu2Vo0fKvgVBgA@mail.gmail.com"
type="cite">I think the message is pretty clear: The Shoutcast
directory only lists Shoutcast servers.
<div><br>
</div>
<div>However, it would seem logical that if a Shoutcast server was
setup to relay an Icecast server (i.e. the Shoutcast source is
an Icecast server) then it would still be listed in the
Shoutcast directory as normal. </div>
<div>
<div>I would assume that the goal of this kind of setup would be
to gain a wider audience. </div>
<div>However, it should be understood that any listeners
arriving from the Shoutcast directory would connect to the
Shoutcast server, not the Icecast server.<br>
</div>
</div>
<div><br>
</div>
<div>I've never tried this, but assuming you have a working
Icecast server, I imagine the steps to getting the Shoutcast
relay working would be:</div>
<div>1) Setup a Shoutcast server<br>
2) Setup the default Shoutcast source client (Winamp?)</div>
<div>3) Test that the server works with a Shoutcast listener
client (Winamp again!)<br>
4) Test that the server is then being listed in the public
Shoutcast directory<br>
<br>
Once you've done that, then you could switch over and use
Icecast as a source:<br>
5) Configure Icecast to provide the correct content when
Shoutcast requests a stream (that's the <alias> directive
stuff)<br>
6) Reconfigure Shoutcast to relay Icecast</div>
<div>7) Repeat step 3 & 4.<br>
<br>
</div>
<div>I'm not sure if others agree, but 'on-topic' for this list
would just be step (5) above. </div>
<div>The rest of the steps would probably be better answered on
the Shoutcast forums, but you might find others on this list
with more experience who can add something.</div>
<div><br>
</div>
<div>Leo<br>
<br>
<br>
<div class="gmail_quote">On 29 February 2012 16:48, Romain
Beauxis <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:toots@rastageeks.org" \
target="_blank">toots@rastageeks.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all,<br>
<br>
2012/2/29 Tom Swirly <<a moz-do-not-send="true"
href="mailto:tom@swirly.com" \
target="_blank">tom@swirly.com</a>>:<br> <div>
<div>> On Wed, Feb 29, 2012 at 11:29 AM, Raymond Lutz
<<a moz-do-not-send="true"
href="mailto:raylutz@cognisys.com" \
target="_blank">raylutz@cognisys.com</a>> wrote:<br>
>><br>
>> This is absolutely not "off-topic" and if this
list will not support this<br>
>> VERY IMPORTANT discussion, then I will be happy
to host the discussion on a<br>
>> different list for those who are interested. I
have been trying to solve<br>
>> this for some time. Much of the problem so far
has been Shoutcast internal<br>
>> problems (on their site) which I assume are
cleared up now. My current<br>
>> assumption is it will be necessary to establish
a second shoutcast server<br>
>> just to get in their directory.<br>
><br>
><br>
> Generally this list has been extremely accepting of
sincere questions<br>
> relating to internet radio!<br>
><br>
> My theory is simply that no one knows the answer,
not that people are<br>
> believing the question is off-topic.<br>
<br>
</div>
</div>
I do not believe that this is off-topic at all. However, I
personally<br>
do not wish to support shoutcast YP technology, even though
I<br>
understand the importance of being listed there.<br>
<span><font color="#888888"><br>
Romain<br>
</font></span>
<div>
<div>_______________________________________________<br>
Icecast mailing list<br>
<a moz-do-not-send="true" href="mailto:Icecast@xiph.org"
target="_blank">Icecast@xiph.org</a><br>
<a moz-do-not-send="true"
href="http://lists.xiph.org/mailman/listinfo/icecast"
target="_blank">http://lists.xiph.org/mailman/listinfo/icecast</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Icecast mailing list
<a class="moz-txt-link-abbreviated" \
href="mailto:Icecast@xiph.org">Icecast@xiph.org</a> <a class="moz-txt-link-freetext" \
href="http://lists.xiph.org/mailman/listinfo/icecast">http://lists.xiph.org/mailman/listinfo/icecast</a>
</pre>
</blockquote>
</body>
</html>
_______________________________________________
Icecast mailing list
Icecast@xiph.org
http://lists.xiph.org/mailman/listinfo/icecast
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic