From leo.currie at gmail.com  Thu Mar  1 15:48:00 2012
From: leo.currie at gmail.com (Leo Currie)
Date: Thu, 1 Mar 2012 15:48:00 +0000
Subject: [Icecast] Shoutcast directory listing?
In-Reply-To: <CABWZ6ORGWzDc_=9QMQUQ16Mvv6yFC=iXwBiinWHN1Jv2ZXNJeQ@mail.gmail.com>
References: <4E4019BE.2000405@cognisys.com> <4E4023BD.8040403@xiph.org>
	<CAJbJ1Bsagp53YnK=iTgACM4wVnKTk2at9C-xad46GuAAzUXDqw@mail.gmail.com>
	<CAJbJ1BvEe13tUHzG356_5j99xa5uda57xN=HY2JG45e6db-cpA@mail.gmail.com>
	<4F4E525C.6010909@cognisys.com>
	<CAOuQWfVH6muSgseYuCqR3KXdPNSFCCeBjirNVvyNei7LmX2ShQ@mail.gmail.com>
	<CABWZ6ORGWzDc_=9QMQUQ16Mvv6yFC=iXwBiinWHN1Jv2ZXNJeQ@mail.gmail.com>
Message-ID: <CANBFD3pBnMd_ZHRu5uYx=HfpPRd6n83b-YQaUu2Vo0fKvgVBgA@mail.gmail.com>

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 at rastageeks.org> wrote:

> Hi all,
>
> 2012/2/29 Tom Swirly <tom at swirly.com>:
> > On Wed, Feb 29, 2012 at 11:29 AM, Raymond Lutz <raylutz at 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 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/20120301/f87c4c0c/attachment.htm>

From raylutz at cognisys.com  Thu Mar  1 18:25:22 2012
From: raylutz at cognisys.com (Raymond Lutz)
Date: Thu, 01 Mar 2012 10:25:22 -0800
Subject: [Icecast] Shoutcast directory listing?
In-Reply-To: <CANBFD3pBnMd_ZHRu5uYx=HfpPRd6n83b-YQaUu2Vo0fKvgVBgA@mail.gmail.com>
References: <4E4019BE.2000405@cognisys.com> <4E4023BD.8040403@xiph.org>
	<CAJbJ1Bsagp53YnK=iTgACM4wVnKTk2at9C-xad46GuAAzUXDqw@mail.gmail.com>
	<CAJbJ1BvEe13tUHzG356_5j99xa5uda57xN=HY2JG45e6db-cpA@mail.gmail.com>
	<4F4E525C.6010909@cognisys.com>
	<CAOuQWfVH6muSgseYuCqR3KXdPNSFCCeBjirNVvyNei7LmX2ShQ@mail.gmail.com>
	<CABWZ6ORGWzDc_=9QMQUQ16Mvv6yFC=iXwBiinWHN1Jv2ZXNJeQ@mail.gmail.com>
	<CANBFD3pBnMd_ZHRu5uYx=HfpPRd6n83b-YQaUu2Vo0fKvgVBgA@mail.gmail.com>
Message-ID: <4F4FBF12.3090908@cognisys.com>

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 at rastageeks.org 
> <mailto:toots at rastageeks.org>> wrote:
>
>     Hi all,
>
>     2012/2/29 Tom Swirly <tom at swirly.com <mailto:tom at swirly.com>>:
>     > On Wed, Feb 29, 2012 at 11:29 AM, Raymond Lutz
>     <raylutz at cognisys.com <mailto:raylutz at 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 at xiph.org <mailto: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: <http://lists.xiph.org/pipermail/icecast/attachments/20120301/079ab2c2/attachment.htm>

From thedarkener at logicalnetworking.net  Sat Mar  3 21:16:38 2012
From: thedarkener at logicalnetworking.net (TheDarkener)
Date: Sat, 03 Mar 2012 13:16:38 -0800
Subject: [Icecast] Hardware-based Icecast source client
Message-ID: <4F528A36.8060000@logicalnetworking.net>

Hi all,

I'm in the midst of creating a turnkey Icecast source client embedded in
a plug computer, using Ices2.

I've hacked together some scripts to automate the starting and stopping
of a live stream (launched by pressing buttons on the device). It's dead
easy once the network/server is configured - you just plug it in, push a
button and you're live.

It accepts any Debian compatible USB audio device - I've verified my
nice stereo microphone (made by Blue) and a USB direct-audio device
works great. It can hook into your existing network via wired or
wireless. I've used it already to broadcast live concerts to my station
and even with the microphone, provided it's placed well, provides
exceptional sound quality over 64kb/sec. Would be even better if it was
128 or more, obviously, but bars/venues rarely have decent Internet
connections available.

I have my own Icecast server which I provide stream mounts for but there
are other Icecast server vendors out there too that this would be
compatible with.

ATM network configuration is done manually, but it's vanilla Debian (on
ARM platform) so it's not too difficult. If I'm able to generate
interest and get some sales, I will be recruiting someone to make a nice
web configuration UI for everything. In the interim I'm thinking of
putting together some simple shell scripts to automate network
configuration. If it's wired (DHCP), no network configuration is necessary.

Would anyone here be interested? I'm just starting out so I would want
to have a couple of 'guinea pigs' to help me test it out (I would
provide the hardware/streaming service at a discounted rate). I think
"IceBox" would be a cool name for it, too ;) I have an existing business
and reseller's permit so I am a legit hardware/service vendor.

Any feedback is appreciated - here's a link to what I've put together as
a marketing blurb for music venues: http://socorock.com/?page_id=4345


Cheers,
Jordan

-- 
Jordan (PGP: 0xDA470FF8)



From kloschi at subsignal.org  Sat Mar  3 23:17:26 2012
From: kloschi at subsignal.org (kloschi)
Date: Sun, 04 Mar 2012 00:17:26 +0100
Subject: [Icecast] Hardware-based Icecast source client
In-Reply-To: <4F528A36.8060000@logicalnetworking.net>
References: <4F528A36.8060000@logicalnetworking.net>
Message-ID: <1330816646.19025.5.camel@enigma.local.subsignal.org>

hi,

On Sat, 2012-03-03 at 13:16 -0800, TheDarkener wrote:
> I'm in the midst of creating a turnkey Icecast source client embedded in
> a plug computer, using Ices2.

Just out of curiosity: what kind of plug computer do you intend to use?
as the marvell based stuff never worked for me with proper ogg
encoding ..

kind regards,
kloschi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 665 bytes
Desc: This is a digitally signed message part
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20120304/961b4656/attachment.sig>

From small.net.nz at gmail.com  Sun Mar  4 02:47:21 2012
From: small.net.nz at gmail.com (Gavin Stephens)
Date: Sun, 04 Mar 2012 14:47:21 +1200
Subject: [Icecast] Hardware-based Icecast source client
In-Reply-To: <4F528A36.8060000@logicalnetworking.net>
References: <4F528A36.8060000@logicalnetworking.net>
Message-ID: <4F52D7B9.8000006@gmail.com>

What's a plug computer?

Does anyone know if Barix extreamers work with IceCast?

On 2012-03-04 09:16, TheDarkener wrote:
> Hi all,
>
> I'm in the midst of creating a turnkey Icecast source client embedded in
> a plug computer, using Ices2.
>
> I've hacked together some scripts to automate the starting and stopping
> of a live stream (launched by pressing buttons on the device). It's dead
> easy once the network/server is configured - you just plug it in, push a
> button and you're live.
>
> It accepts any Debian compatible USB audio device - I've verified my
> nice stereo microphone (made by Blue) and a USB direct-audio device
> works great. It can hook into your existing network via wired or
> wireless. I've used it already to broadcast live concerts to my station
> and even with the microphone, provided it's placed well, provides
> exceptional sound quality over 64kb/sec. Would be even better if it was
> 128 or more, obviously, but bars/venues rarely have decent Internet
> connections available.
>
> I have my own Icecast server which I provide stream mounts for but there
> are other Icecast server vendors out there too that this would be
> compatible with.
>
> ATM network configuration is done manually, but it's vanilla Debian (on
> ARM platform) so it's not too difficult. If I'm able to generate
> interest and get some sales, I will be recruiting someone to make a nice
> web configuration UI for everything. In the interim I'm thinking of
> putting together some simple shell scripts to automate network
> configuration. If it's wired (DHCP), no network configuration is necessary.
>
> Would anyone here be interested? I'm just starting out so I would want
> to have a couple of 'guinea pigs' to help me test it out (I would
> provide the hardware/streaming service at a discounted rate). I think
> "IceBox" would be a cool name for it, too ;) I have an existing business
> and reseller's permit so I am a legit hardware/service vendor.
>
> Any feedback is appreciated - here's a link to what I've put together as
> a marketing blurb for music venues: http://socorock.com/?page_id=4345
>
>
> Cheers,
> Jordan
>


From paul at dabdig.com  Sun Mar  4 01:57:08 2012
From: paul at dabdig.com (Paul Webster)
Date: Sat, 3 Mar 2012 20:57:08 -0500
Subject: [Icecast] Hardware-based Icecast source client
In-Reply-To: <4F52D7B9.8000006@gmail.com>
References: <4F528A36.8060000@logicalnetworking.net>
	<4F52D7B9.8000006@gmail.com>
Message-ID: <D36F2CD4-A5E4-43EB-BB90-2F71315B223F@dabdig.com>

On 3 Mar 2012, at 21:47, Gavin Stephens <small.net.nz at gmail.com> wrote:

> What's a plug computer?

Something like this:
http://pogoplug.com/

or the latest kid on the block (my order is in)
http://www.raspberrypi.org

Paul


From thedarkener at logicalnetworking.net  Sun Mar  4 02:05:25 2012
From: thedarkener at logicalnetworking.net (TheDarkener)
Date: Sat, 03 Mar 2012 18:05:25 -0800
Subject: [Icecast] Hardware-based Icecast source client
In-Reply-To: <4F52D7B9.8000006@gmail.com>
References: <4F528A36.8060000@logicalnetworking.net>
	<4F52D7B9.8000006@gmail.com>
Message-ID: <4F52CDE5.8040803@logicalnetworking.net>

I would assume only Ices1, if any - their product page says MP3/PCM support.


On 03/03/2012 06:47 PM, Gavin Stephens wrote:
> What's a plug computer?
>
> Does anyone know if Barix extreamers work with IceCast?
>
> On 2012-03-04 09:16, TheDarkener wrote:
>> Hi all,
>>
>> I'm in the midst of creating a turnkey Icecast source client embedded in
>> a plug computer, using Ices2.
>>
>> I've hacked together some scripts to automate the starting and stopping
>> of a live stream (launched by pressing buttons on the device). It's dead
>> easy once the network/server is configured - you just plug it in, push a
>> button and you're live.
>>
>> It accepts any Debian compatible USB audio device - I've verified my
>> nice stereo microphone (made by Blue) and a USB direct-audio device
>> works great. It can hook into your existing network via wired or
>> wireless. I've used it already to broadcast live concerts to my station
>> and even with the microphone, provided it's placed well, provides
>> exceptional sound quality over 64kb/sec. Would be even better if it was
>> 128 or more, obviously, but bars/venues rarely have decent Internet
>> connections available.
>>
>> I have my own Icecast server which I provide stream mounts for but there
>> are other Icecast server vendors out there too that this would be
>> compatible with.
>>
>> ATM network configuration is done manually, but it's vanilla Debian (on
>> ARM platform) so it's not too difficult. If I'm able to generate
>> interest and get some sales, I will be recruiting someone to make a nice
>> web configuration UI for everything. In the interim I'm thinking of
>> putting together some simple shell scripts to automate network
>> configuration. If it's wired (DHCP), no network configuration is necessary.
>>
>> Would anyone here be interested? I'm just starting out so I would want
>> to have a couple of 'guinea pigs' to help me test it out (I would
>> provide the hardware/streaming service at a discounted rate). I think
>> "IceBox" would be a cool name for it, too ;) I have an existing business
>> and reseller's permit so I am a legit hardware/service vendor.
>>
>> Any feedback is appreciated - here's a link to what I've put together as
>> a marketing blurb for music venues: http://socorock.com/?page_id=4345
>>
>>
>> Cheers,
>> Jordan
>>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


-- 
Jordan (PGP: 0xDA470FF8)



From thedarkener at logicalnetworking.net  Sun Mar  4 02:09:43 2012
From: thedarkener at logicalnetworking.net (TheDarkener)
Date: Sat, 03 Mar 2012 18:09:43 -0800
Subject: [Icecast] Hardware-based Icecast source client
In-Reply-To: <4F52CDE5.8040803@logicalnetworking.net>
References: <4F528A36.8060000@logicalnetworking.net>	<4F52D7B9.8000006@gmail.com>
	<4F52CDE5.8040803@logicalnetworking.net>
Message-ID: <4F52CEE7.8000508@logicalnetworking.net>

Ices1 meaning they don't seem to do ogg/vorbis encoding, of course.. the
opposite being the product I mentioned I'm making, which I would only
support using ogg/vorbis. :)



On 03/03/2012 06:05 PM, TheDarkener wrote:
> I would assume only Ices1, if any - their product page says MP3/PCM support.
>
>
> On 03/03/2012 06:47 PM, Gavin Stephens wrote:
>> What's a plug computer?
>>
>> Does anyone know if Barix extreamers work with IceCast?
>>
>> On 2012-03-04 09:16, TheDarkener wrote:
>>> Hi all,
>>>
>>> I'm in the midst of creating a turnkey Icecast source client embedded in
>>> a plug computer, using Ices2.
>>>
>>> I've hacked together some scripts to automate the starting and stopping
>>> of a live stream (launched by pressing buttons on the device). It's dead
>>> easy once the network/server is configured - you just plug it in, push a
>>> button and you're live.
>>>
>>> It accepts any Debian compatible USB audio device - I've verified my
>>> nice stereo microphone (made by Blue) and a USB direct-audio device
>>> works great. It can hook into your existing network via wired or
>>> wireless. I've used it already to broadcast live concerts to my station
>>> and even with the microphone, provided it's placed well, provides
>>> exceptional sound quality over 64kb/sec. Would be even better if it was
>>> 128 or more, obviously, but bars/venues rarely have decent Internet
>>> connections available.
>>>
>>> I have my own Icecast server which I provide stream mounts for but there
>>> are other Icecast server vendors out there too that this would be
>>> compatible with.
>>>
>>> ATM network configuration is done manually, but it's vanilla Debian (on
>>> ARM platform) so it's not too difficult. If I'm able to generate
>>> interest and get some sales, I will be recruiting someone to make a nice
>>> web configuration UI for everything. In the interim I'm thinking of
>>> putting together some simple shell scripts to automate network
>>> configuration. If it's wired (DHCP), no network configuration is necessary.
>>>
>>> Would anyone here be interested? I'm just starting out so I would want
>>> to have a couple of 'guinea pigs' to help me test it out (I would
>>> provide the hardware/streaming service at a discounted rate). I think
>>> "IceBox" would be a cool name for it, too ;) I have an existing business
>>> and reseller's permit so I am a legit hardware/service vendor.
>>>
>>> Any feedback is appreciated - here's a link to what I've put together as
>>> a marketing blurb for music venues: http://socorock.com/?page_id=4345
>>>
>>>
>>> Cheers,
>>> Jordan
>>>
>> _______________________________________________
>> Icecast mailing list
>> Icecast at xiph.org
>> http://lists.xiph.org/mailman/listinfo/icecast
>


-- 
Jordan (PGP: 0xDA470FF8)



From martin at thelightingshed.co.uk  Sun Mar  4 18:50:35 2012
From: martin at thelightingshed.co.uk (=?utf-8?B?TWFydGluIEhhcnJpc29u?=)
Date: Sun, 04 Mar 2012 18:50:35 +0000
Subject: [Icecast] =?utf-8?q?Hardware-based_Icecast_source_client?=
Message-ID: <133088703779028274@ukmrpl004>

Yes the barix extreamers work fine with icecast. I used to use them as studio to transmitter links for a radio station.

Martin

----- Reply message -----
From: "Gavin Stephens" <small.net.nz at gmail.com>
Date: Sun, Mar 4, 2012 02:47
Subject: [Icecast] Hardware-based Icecast source client
To: <icecast at xiph.org>

What's a plug computer?

Does anyone know if Barix extreamers work with IceCast?

On 2012-03-04 09:16, TheDarkener wrote:
> Hi all,
>
> I'm in the midst of creating a turnkey Icecast source client embedded in
> a plug computer, using Ices2.
>
> I've hacked together some scripts to automate the starting and stopping
> of a live stream (launched by pressing buttons on the device). It's dead
> easy once the network/server is configured - you just plug it in, push a
> button and you're live.
>
> It accepts any Debian compatible USB audio device - I've verified my
> nice stereo microphone (made by Blue) and a USB direct-audio device
> works great. It can hook into your existing network via wired or
> wireless. I've used it already to broadcast live concerts to my station
> and even with the microphone, provided it's placed well, provides
> exceptional sound quality over 64kb/sec. Would be even better if it was
> 128 or more, obviously, but bars/venues rarely have decent Internet
> connections available.
>
> I have my own Icecast server which I provide stream mounts for but there
> are other Icecast server vendors out there too that this would be
> compatible with.
>
> ATM network configuration is done manually, but it's vanilla Debian (on
> ARM platform) so it's not too difficult. If I'm able to generate
> interest and get some sales, I will be recruiting someone to make a nice
> web configuration UI for everything. In the interim I'm thinking of
> putting together some simple shell scripts to automate network
> configuration. If it's wired (DHCP), no network configuration is necessary.
>
> Would anyone here be interested? I'm just starting out so I would want
> to have a couple of 'guinea pigs' to help me test it out (I would
> provide the hardware/streaming service at a discounted rate). I think
> "IceBox" would be a cool name for it, too ;) I have an existing business
> and reseller's permit so I am a legit hardware/service vendor.
>
> Any feedback is appreciated - here's a link to what I've put together as
> a marketing blurb for music venues: http://socorock.com/?page_id=4345
>
>
> Cheers,
> Jordan
>
_______________________________________________
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/20120304/8049ac76/attachment.htm>

From contact at junglised.co.uk  Sun Mar  4 20:35:24 2012
From: contact at junglised.co.uk (Junglised)
Date: Sun, 04 Mar 2012 20:35:24 +0000
Subject: [Icecast] Dump file title still %d_%m_%Y-%H%M_%S.mp3 on centos rpm
	build
In-Reply-To: <133088703779028274@ukmrpl004>
References: <133088703779028274@ukmrpl004>
Message-ID: <4F53D20C.60906@junglised.co.uk>

Hi all.

Digging up an old topic I know, but one that might have hopefully 
changed since I last asked over a year ago.

I've had to rebuild our stations server, so used the Centos RPM build 
for Icecast. Everything is working great, but I'd completely forgotten 
that the dump file doesnt work as it should unless I compile from source 
rather than use the RPM.

Is there a way around this, or will I have to rebuild from source? I'd 
rather not, as last time the web admin part of icecast never every worked.

Thanks
Huw


From Alistair.Young at uhi.ac.uk  Fri Mar 16 12:18:28 2012
From: Alistair.Young at uhi.ac.uk (Alistair Young)
Date: Fri, 16 Mar 2012 12:18:28 +0000
Subject: [Icecast] uri authentication
Message-ID: <12C672DE-C1C4-4D96-870A-08CC9AE1997E@uhi.ac.uk>

Hi folks,

http://www.icecast.org/docs/icecast-2.3.1/icecast2_listenerauth.html

is uri authentication an extension of http authentication? i.e. if you use uri authentication the user is also asked for their username and password, which are sent to the script via the username and password options?

thanks,

Alistair

--------------
mov eax,1
mov ebx,0
int 80



From leo.currie at gmail.com  Fri Mar 16 22:58:17 2012
From: leo.currie at gmail.com (Leo Currie)
Date: Fri, 16 Mar 2012 22:58:17 +0000
Subject: [Icecast] uri authentication
In-Reply-To: <12C672DE-C1C4-4D96-870A-08CC9AE1997E@uhi.ac.uk>
References: <12C672DE-C1C4-4D96-870A-08CC9AE1997E@uhi.ac.uk>
Message-ID: <CANBFD3qD9=RDcZZKwBFXGG6vx0ZPrAUCah4ADROXevyhtoR7vA@mail.gmail.com>

Alistair -

That's pretty much correct.

It might be worth pointing out that the client will probably only prompt
you to enter a username and password if it receives a 401 from the server.
Icecast will respond to the client with a 401 if the call to the
authentication script doesn't return the auth header ("icecast-auth-user:
1" by default).
This is another way of saying that the client normally won't know that it
needs to ask you for a username/password without first attempting to
connect without a username/password. And so your authentication script will
normally be called twice for each connection.

It's perfectly feasible to write an authentication script that uses
something other than the basic HTTP username/password. For example, you
could use the IP address to authenticate clients. Any additional parameters
tagged on to the mountpoint will be passed on to your authentication script
too, so if you had a mountpoint called /stream.ogg and you tried to connect
to /stream.ogg?myParam=123 then the value 123 would also be passed in the
parameter myParam to your script (url encoded).

So if you've already setup a website with user authentication, you might be
able to allow already-logged-in users to open a stream without any
additional login steps by using a session id parameter on the listen link.

Or you can use the URL authentication mechanism for simply tracking
listener start/stop events for usage stats (e.g. Google analytics to track
listener events).

Leo

On 16 March 2012 12:18, Alistair Young <Alistair.Young at uhi.ac.uk> wrote:

> Hi folks,
>
> http://www.icecast.org/docs/icecast-2.3.1/icecast2_listenerauth.html
>
> is uri authentication an extension of http authentication? i.e. if you use
> uri authentication the user is also asked for their username and password,
> which are sent to the script via the username and password options?
>
> thanks,
>
> Alistair
>
> --------------
> mov eax,1
> mov ebx,0
> int 80
>
> _______________________________________________
> 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/20120316/d21e3cae/attachment.htm>

From alistair.young at uhi.ac.uk  Sat Mar 17 09:21:07 2012
From: alistair.young at uhi.ac.uk (Alistair Young)
Date: Sat, 17 Mar 2012 09:21:07 +0000
Subject: [Icecast] uri authentication
In-Reply-To: <CANBFD3qD9=RDcZZKwBFXGG6vx0ZPrAUCah4ADROXevyhtoR7vA@mail.gmail.com>
References: <12C672DE-C1C4-4D96-870A-08CC9AE1997E@uhi.ac.uk>
	<CANBFD3qD9=RDcZZKwBFXGG6vx0ZPrAUCah4ADROXevyhtoR7vA@mail.gmail.com>
Message-ID: <C9D96B27-D6F7-44C4-B923-AD5FFFF40A4D@uhi.ac.uk>

thanks for such a detailed answer Leo, just what I needed. The script will authenticate/authorize via LDAP and thanks for the pointers on stats/usage.

cheers,

Alistair

--------------
mov eax,1
mov ebx,0
int 80

On 16 Mar 2012, at 22:58, Leo Currie wrote:

> Alistair -
> 
> That's pretty much correct.
> 
> It might be worth pointing out that the client will probably only prompt you to enter a username and password if it receives a 401 from the server.
> Icecast will respond to the client with a 401 if the call to the authentication script doesn't return the auth header ("icecast-auth-user: 1" by default).
> This is another way of saying that the client normally won't know that it needs to ask you for a username/password without first attempting to connect without a username/password. And so your authentication script will normally be called twice for each connection.
> 
> It's perfectly feasible to write an authentication script that uses something other than the basic HTTP username/password. For example, you could use the IP address to authenticate clients. Any additional parameters tagged on to the mountpoint will be passed on to your authentication script too, so if you had a mountpoint called /stream.ogg and you tried to connect to /stream.ogg?myParam=123 then the value 123 would also be passed in the parameter myParam to your script (url encoded).
> 
> So if you've already setup a website with user authentication, you might be able to allow already-logged-in users to open a stream without any additional login steps by using a session id parameter on the listen link.
> 
> Or you can use the URL authentication mechanism for simply tracking listener start/stop events for usage stats (e.g. Google analytics to track listener events).
> 
> Leo
> 
> On 16 March 2012 12:18, Alistair Young <Alistair.Young at uhi.ac.uk> wrote:
> Hi folks,
> 
> http://www.icecast.org/docs/icecast-2.3.1/icecast2_listenerauth.html
> 
> is uri authentication an extension of http authentication? i.e. if you use uri authentication the user is also asked for their username and password, which are sent to the script via the username and password options?
> 
> thanks,
> 
> Alistair
> 
> --------------
> mov eax,1
> mov ebx,0
> int 80
> 
> _______________________________________________
> 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: <http://lists.xiph.org/pipermail/icecast/attachments/20120317/96f5f34a/attachment.htm>

From paul at dabdig.com  Sat Mar 17 09:41:25 2012
From: paul at dabdig.com (Paul Webster)
Date: Sat, 17 Mar 2012 09:41:25 +0000
Subject: [Icecast] Including station directory list in 3rd-party services
In-Reply-To: <q2bqj7df2pfdupttntj5o8igvs7duau62m@4ax.com>
References: <q2bqj7df2pfdupttntj5o8igvs7duau62m@4ax.com>
Message-ID: <16704493-EF1F-492E-AD84-84C904803B06@dabdig.com>

Any thoughts on this one that I asked about a month ago?

Paul

On 16 Feb 2012, at 20:58, Paul Webster <paul at dabdig.com> wrote:

> Hello,
> 
> I am interested to know what the rules are about including the station directory in 3rd-party services.
> Apologies in advance if I am dragging up an old and well known topic. I browsed the wiki and searched the archives for
> reference to "Directory" and also to a couple of the big station directory services and found only references to interop
> with SHOUTcast YP.
> 
> If it is allowed to include station details (name, description, genre, stream URL) - can someone give a pointer to
> documentation on how to get the list and, efficiently, get updates - or is it a matter of going through the source and
> working it out?
> 
> I ask because I help (as a volunteer) with the updates to a couple of the station directories that are used by internet
> radio devices.
> 
> Paul Webster
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


From keith at karsites.net  Sat Mar 17 12:54:42 2012
From: keith at karsites.net (Keith Roberts)
Date: Sat, 17 Mar 2012 12:54:42 +0000 (GMT)
Subject: [Icecast] Multpiple sound cards with ices client?
Message-ID: <alpine.LRH.2.02.1203171252020.9580@karsites.localdomain>

I was wondering is it possible to use the ices client with 
more that one soundcard under Centos Linux?

I only want to stream one mono audio feed to icecast, but am 
already using the Line input of my sound card for something 
else, and the mic input might be far to sensitive.

TIA

Keith

-----------------------------------------------------------
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  Sat Mar 17 17:55:34 2012
From: thedarkener at logicalnetworking.net (The Darkener)
Date: Sat, 17 Mar 2012 10:55:34 -0700
Subject: [Icecast] Multpiple sound cards with ices client?
In-Reply-To: <alpine.LRH.2.02.1203171252020.9580@karsites.localdomain>
References: <alpine.LRH.2.02.1203171252020.9580@karsites.localdomain>
Message-ID: <4F64D016.3080703@logicalnetworking.net>

Hi Keith,

I would assume this would be pretty straightforward - you just have to
define which audio device you're using in ices configuration. I know I
do this as my laptop has an Internal audio chipset, but I use a USB
audio device for streaming.

- Jordan



On 03/17/2012 05:54 AM, Keith Roberts wrote:
> I was wondering is it possible to use the ices client with 
> more that one soundcard under Centos Linux?
>
> I only want to stream one mono audio feed to icecast, but am 
> already using the Line input of my sound card for something 
> else, and the mic input might be far to sensitive.
>
> TIA
>
> Keith
>
> -----------------------------------------------------------
> 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 keith at karsites.net  Sat Mar 17 19:18:50 2012
From: keith at karsites.net (Keith Roberts)
Date: Sat, 17 Mar 2012 19:18:50 +0000 (GMT)
Subject: [Icecast] Multpiple sound cards with ices client?
In-Reply-To: <4F64D016.3080703@logicalnetworking.net>
References: <alpine.LRH.2.02.1203171252020.9580@karsites.localdomain>
	<4F64D016.3080703@logicalnetworking.net>
Message-ID: <alpine.LRH.2.02.1203171917500.18260@karsites.localdomain>

OK, thanks for that Jordan.

Nice to know it's possible to set which sound input to use.

I'll post back when I get round to actually doing this.

Keith

On Sat, 17 Mar 2012, The Darkener wrote:

> To: icecast at xiph.org
> From: The Darkener <thedarkener at logicalnetworking.net>
> Subject: Re: [Icecast] Multpiple sound cards with ices client?
> 
> Hi Keith,
>
> I would assume this would be pretty straightforward - you just have to
> define which audio device you're using in ices configuration. I know I
> do this as my laptop has an Internal audio chipset, but I use a USB
> audio device for streaming.
>
> - Jordan
>
>
>
> On 03/17/2012 05:54 AM, Keith Roberts wrote:
>> I was wondering is it possible to use the ices client with
>> more that one soundcard under Centos Linux?
>>
>> I only want to stream one mono audio feed to icecast, but am
>> already using the Line input of my sound card for something
>> else, and the mic input might be far to sensitive.
>>
>> TIA
>>
>> Keith
>>
>> -----------------------------------------------------------
>> 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
>>
>
>
>

-- 
-----------------------------------------------------------
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 stig at stigc.dk  Sat Mar 24 12:28:01 2012
From: stig at stigc.dk (Stig Christensen)
Date: Sat, 24 Mar 2012 13:28:01 +0100
Subject: [Icecast] icy-metaint in header and in stream data
Message-ID: <4F6DBDD1.3060505@stigc.dk>

Normally icy-metaint is a line in the http header, but some stream only 
sends it in the response data is self.

Where can I find such a stream?
Is that compliant to the standard?

Implementation that also parses the response data
http://stackoverflow.com/questions/8621353/textview-not-updating-shoutcast-stream-metadata-in-android-2-2

Thank

Stig

-- 

Best Regards / Mvh

Stig Christensen

stig at stigc.dk
www.stigc.dk



From msmith at xiph.org  Mon Mar 26 15:56:52 2012
From: msmith at xiph.org (Michael Smith)
Date: Mon, 26 Mar 2012 08:56:52 -0700
Subject: [Icecast] icy-metaint in header and in stream data
In-Reply-To: <4F6DBDD1.3060505@stigc.dk>
References: <4F6DBDD1.3060505@stigc.dk>
Message-ID: <CAB=BY8unAc8B7hCF8i7nipdr_O8b3DqR2Dw+V5t=O8CCvOo6iA@mail.gmail.com>

I've never seen such a stream. I've never seen a client or server
implementation that could handle that being done. To the extent that
there's any sort of 'standard' this would clearly violate it.

I'm pretty sure nobody ever sends it in the response data.

Mike


On Sat, Mar 24, 2012 at 5:28 AM, Stig Christensen <stig at stigc.dk> wrote:
> Normally icy-metaint is a line in the http header, but some stream only
> sends it in the response data is self.
>
> Where can I find such a stream?
> Is that compliant to the standard?
>
> Implementation that also parses the response data
> http://stackoverflow.com/questions/8621353/textview-not-updating-shoutcast-stream-metadata-in-android-2-2
>
> Thank
>
> Stig
>
> --
>
> Best Regards / Mvh
>
> Stig Christensen
>
> stig at stigc.dk
> www.stigc.dk
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


From edhoeven at gmail.com  Sun Mar  4 21:32:51 2012
From: edhoeven at gmail.com (edu hoeven, van der)
Date: Sun, 04 Mar 2012 21:32:51 -0000
Subject: [Icecast] Icecast Digest, Vol 94, Issue 2
In-Reply-To: <mailman.11535.1330887448.748.icecast@xiph.org>
References: <mailman.11535.1330887448.748.icecast@xiph.org>
Message-ID: <CAF76TuW_RDQw3aJWUzdYFeqKuj9cwT-9uQ3Y_7+Uv-RJr61JBw@mail.gmail.com>

Hi,

My name is Edu, living in the Netherlands

I good be a great thing, to get a list of ogg radiostations for my website
www.fm88-108.nl/radio/

I have update this for html5 player so can now play also ogg

I want make an ogg radio list on wwr frequency's to get the visitors
favorite stations in memory mind how know the frequency

This will make find back easy and looking for others stations will be also
fun to do.

I hope you will help me with an OGG radio stations list

Kind regards,

Edu van der Hoeven.



2012/3/4 <icecast-request at xiph.org>

> 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. Hardware-based Icecast source client (TheDarkener)
>   2. Re: Hardware-based Icecast source client (kloschi)
>   3. Re: Hardware-based Icecast source client (Gavin Stephens)
>   4. Re: Hardware-based Icecast source client (Paul Webster)
>   5. Re: Hardware-based Icecast source client (TheDarkener)
>   6. Re: Hardware-based Icecast source client (TheDarkener)
>   7. Re: Hardware-based Icecast source client ( Martin Harrison )
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 03 Mar 2012 13:16:38 -0800
> From: TheDarkener <thedarkener at logicalnetworking.net>
> Subject: [Icecast] Hardware-based Icecast source client
> To: icecast at xiph.org
> Message-ID: <4F528A36.8060000 at logicalnetworking.net>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi all,
>
> I'm in the midst of creating a turnkey Icecast source client embedded in
> a plug computer, using Ices2.
>
> I've hacked together some scripts to automate the starting and stopping
> of a live stream (launched by pressing buttons on the device). It's dead
> easy once the network/server is configured - you just plug it in, push a
> button and you're live.
>
> It accepts any Debian compatible USB audio device - I've verified my
> nice stereo microphone (made by Blue) and a USB direct-audio device
> works great. It can hook into your existing network via wired or
> wireless. I've used it already to broadcast live concerts to my station
> and even with the microphone, provided it's placed well, provides
> exceptional sound quality over 64kb/sec. Would be even better if it was
> 128 or more, obviously, but bars/venues rarely have decent Internet
> connections available.
>
> I have my own Icecast server which I provide stream mounts for but there
> are other Icecast server vendors out there too that this would be
> compatible with.
>
> ATM network configuration is done manually, but it's vanilla Debian (on
> ARM platform) so it's not too difficult. If I'm able to generate
> interest and get some sales, I will be recruiting someone to make a nice
> web configuration UI for everything. In the interim I'm thinking of
> putting together some simple shell scripts to automate network
> configuration. If it's wired (DHCP), no network configuration is necessary.
>
> Would anyone here be interested? I'm just starting out so I would want
> to have a couple of 'guinea pigs' to help me test it out (I would
> provide the hardware/streaming service at a discounted rate). I think
> "IceBox" would be a cool name for it, too ;) I have an existing business
> and reseller's permit so I am a legit hardware/service vendor.
>
> Any feedback is appreciated - here's a link to what I've put together as
> a marketing blurb for music venues: http://socorock.com/?page_id=4345
>
>
> Cheers,
> Jordan
>
> --
> Jordan (PGP: 0xDA470FF8)
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sun, 04 Mar 2012 00:17:26 +0100
> From: kloschi <kloschi at subsignal.org>
> Subject: Re: [Icecast] Hardware-based Icecast source client
> To: TheDarkener <thedarkener at logicalnetworking.net>
> Cc: icecast at xiph.org
> Message-ID: <1330816646.19025.5.camel at enigma.local.subsignal.org>
> Content-Type: text/plain; charset="utf-8"
>
> hi,
>
> On Sat, 2012-03-03 at 13:16 -0800, TheDarkener wrote:
> > I'm in the midst of creating a turnkey Icecast source client embedded in
> > a plug computer, using Ices2.
>
> Just out of curiosity: what kind of plug computer do you intend to use?
> as the marvell based stuff never worked for me with proper ogg
> encoding ..
>
> kind regards,
> kloschi
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 665 bytes
> Desc: This is a digitally signed message part
> Url :
> http://lists.xiph.org/pipermail/icecast/attachments/20120304/961b4656/attachment-0001.pgp
>
> ------------------------------
>
> Message: 3
> Date: Sun, 04 Mar 2012 14:47:21 +1200
> From: Gavin Stephens <small.net.nz at gmail.com>
> Subject: Re: [Icecast] Hardware-based Icecast source client
> To: icecast at xiph.org
> Message-ID: <4F52D7B9.8000006 at gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> What's a plug computer?
>
> Does anyone know if Barix extreamers work with IceCast?
>
> On 2012-03-04 09:16, TheDarkener wrote:
> > Hi all,
> >
> > I'm in the midst of creating a turnkey Icecast source client embedded in
> > a plug computer, using Ices2.
> >
> > I've hacked together some scripts to automate the starting and stopping
> > of a live stream (launched by pressing buttons on the device). It's dead
> > easy once the network/server is configured - you just plug it in, push a
> > button and you're live.
> >
> > It accepts any Debian compatible USB audio device - I've verified my
> > nice stereo microphone (made by Blue) and a USB direct-audio device
> > works great. It can hook into your existing network via wired or
> > wireless. I've used it already to broadcast live concerts to my station
> > and even with the microphone, provided it's placed well, provides
> > exceptional sound quality over 64kb/sec. Would be even better if it was
> > 128 or more, obviously, but bars/venues rarely have decent Internet
> > connections available.
> >
> > I have my own Icecast server which I provide stream mounts for but there
> > are other Icecast server vendors out there too that this would be
> > compatible with.
> >
> > ATM network configuration is done manually, but it's vanilla Debian (on
> > ARM platform) so it's not too difficult. If I'm able to generate
> > interest and get some sales, I will be recruiting someone to make a nice
> > web configuration UI for everything. In the interim I'm thinking of
> > putting together some simple shell scripts to automate network
> > configuration. If it's wired (DHCP), no network configuration is
> necessary.
> >
> > Would anyone here be interested? I'm just starting out so I would want
> > to have a couple of 'guinea pigs' to help me test it out (I would
> > provide the hardware/streaming service at a discounted rate). I think
> > "IceBox" would be a cool name for it, too ;) I have an existing business
> > and reseller's permit so I am a legit hardware/service vendor.
> >
> > Any feedback is appreciated - here's a link to what I've put together as
> > a marketing blurb for music venues: http://socorock.com/?page_id=4345
> >
> >
> > Cheers,
> > Jordan
> >
>
>
> ------------------------------
>
> Message: 4
> Date: Sat, 3 Mar 2012 20:57:08 -0500
> From: Paul Webster <paul at dabdig.com>
> Subject: Re: [Icecast] Hardware-based Icecast source client
> To: "icecast at xiph.org" <icecast at xiph.org>
> Message-ID: <D36F2CD4-A5E4-43EB-BB90-2F71315B223F at dabdig.com>
> Content-Type: text/plain;       charset=us-ascii
>
> On 3 Mar 2012, at 21:47, Gavin Stephens <small.net.nz at gmail.com> wrote:
>
> > What's a plug computer?
>
> Something like this:
> http://pogoplug.com/
>
> or the latest kid on the block (my order is in)
> http://www.raspberrypi.org
>
> Paul
>
>
> ------------------------------
>
> Message: 5
> Date: Sat, 03 Mar 2012 18:05:25 -0800
> From: TheDarkener <thedarkener at logicalnetworking.net>
> Subject: Re: [Icecast] Hardware-based Icecast source client
> To: Gavin Stephens <small.net.nz at gmail.com>
> Cc: icecast at xiph.org
> Message-ID: <4F52CDE5.8040803 at logicalnetworking.net>
> Content-Type: text/plain; charset=ISO-8859-1
>
> I would assume only Ices1, if any - their product page says MP3/PCM
> support.
>
>
> On 03/03/2012 06:47 PM, Gavin Stephens wrote:
> > What's a plug computer?
> >
> > Does anyone know if Barix extreamers work with IceCast?
> >
> > On 2012-03-04 09:16, TheDarkener wrote:
> >> Hi all,
> >>
> >> I'm in the midst of creating a turnkey Icecast source client embedded in
> >> a plug computer, using Ices2.
> >>
> >> I've hacked together some scripts to automate the starting and stopping
> >> of a live stream (launched by pressing buttons on the device). It's dead
> >> easy once the network/server is configured - you just plug it in, push a
> >> button and you're live.
> >>
> >> It accepts any Debian compatible USB audio device - I've verified my
> >> nice stereo microphone (made by Blue) and a USB direct-audio device
> >> works great. It can hook into your existing network via wired or
> >> wireless. I've used it already to broadcast live concerts to my station
> >> and even with the microphone, provided it's placed well, provides
> >> exceptional sound quality over 64kb/sec. Would be even better if it was
> >> 128 or more, obviously, but bars/venues rarely have decent Internet
> >> connections available.
> >>
> >> I have my own Icecast server which I provide stream mounts for but there
> >> are other Icecast server vendors out there too that this would be
> >> compatible with.
> >>
> >> ATM network configuration is done manually, but it's vanilla Debian (on
> >> ARM platform) so it's not too difficult. If I'm able to generate
> >> interest and get some sales, I will be recruiting someone to make a nice
> >> web configuration UI for everything. In the interim I'm thinking of
> >> putting together some simple shell scripts to automate network
> >> configuration. If it's wired (DHCP), no network configuration is
> necessary.
> >>
> >> Would anyone here be interested? I'm just starting out so I would want
> >> to have a couple of 'guinea pigs' to help me test it out (I would
> >> provide the hardware/streaming service at a discounted rate). I think
> >> "IceBox" would be a cool name for it, too ;) I have an existing business
> >> and reseller's permit so I am a legit hardware/service vendor.
> >>
> >> Any feedback is appreciated - here's a link to what I've put together as
> >> a marketing blurb for music venues: http://socorock.com/?page_id=4345
> >>
> >>
> >> Cheers,
> >> Jordan
> >>
> > _______________________________________________
> > Icecast mailing list
> > Icecast at xiph.org
> > http://lists.xiph.org/mailman/listinfo/icecast
>
>
> --
> Jordan (PGP: 0xDA470FF8)
>
>
>
> ------------------------------
>
> Message: 6
> Date: Sat, 03 Mar 2012 18:09:43 -0800
> From: TheDarkener <thedarkener at logicalnetworking.net>
> Subject: Re: [Icecast] Hardware-based Icecast source client
> To: Gavin Stephens <small.net.nz at gmail.com>
> Cc: icecast at xiph.org
> Message-ID: <4F52CEE7.8000508 at logicalnetworking.net>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Ices1 meaning they don't seem to do ogg/vorbis encoding, of course.. the
> opposite being the product I mentioned I'm making, which I would only
> support using ogg/vorbis. :)
>
>
>
> On 03/03/2012 06:05 PM, TheDarkener wrote:
> > I would assume only Ices1, if any - their product page says MP3/PCM
> support.
> >
> >
> > On 03/03/2012 06:47 PM, Gavin Stephens wrote:
> >> What's a plug computer?
> >>
> >> Does anyone know if Barix extreamers work with IceCast?
> >>
> >> On 2012-03-04 09:16, TheDarkener wrote:
> >>> Hi all,
> >>>
> >>> I'm in the midst of creating a turnkey Icecast source client embedded
> in
> >>> a plug computer, using Ices2.
> >>>
> >>> I've hacked together some scripts to automate the starting and stopping
> >>> of a live stream (launched by pressing buttons on the device). It's
> dead
> >>> easy once the network/server is configured - you just plug it in, push
> a
> >>> button and you're live.
> >>>
> >>> It accepts any Debian compatible USB audio device - I've verified my
> >>> nice stereo microphone (made by Blue) and a USB direct-audio device
> >>> works great. It can hook into your existing network via wired or
> >>> wireless. I've used it already to broadcast live concerts to my station
> >>> and even with the microphone, provided it's placed well, provides
> >>> exceptional sound quality over 64kb/sec. Would be even better if it was
> >>> 128 or more, obviously, but bars/venues rarely have decent Internet
> >>> connections available.
> >>>
> >>> I have my own Icecast server which I provide stream mounts for but
> there
> >>> are other Icecast server vendors out there too that this would be
> >>> compatible with.
> >>>
> >>> ATM network configuration is done manually, but it's vanilla Debian (on
> >>> ARM platform) so it's not too difficult. If I'm able to generate
> >>> interest and get some sales, I will be recruiting someone to make a
> nice
> >>> web configuration UI for everything. In the interim I'm thinking of
> >>> putting together some simple shell scripts to automate network
> >>> configuration. If it's wired (DHCP), no network configuration is
> necessary.
> >>>
> >>> Would anyone here be interested? I'm just starting out so I would want
> >>> to have a couple of 'guinea pigs' to help me test it out (I would
> >>> provide the hardware/streaming service at a discounted rate). I think
> >>> "IceBox" would be a cool name for it, too ;) I have an existing
> business
> >>> and reseller's permit so I am a legit hardware/service vendor.
> >>>
> >>> Any feedback is appreciated - here's a link to what I've put together
> as
> >>> a marketing blurb for music venues: http://socorock.com/?page_id=4345
> >>>
> >>>
> >>> Cheers,
> >>> Jordan
> >>>
> >> _______________________________________________
> >> Icecast mailing list
> >> Icecast at xiph.org
> >> http://lists.xiph.org/mailman/listinfo/icecast
> >
>
>
> --
> Jordan (PGP: 0xDA470FF8)
>
>
>
> ------------------------------
>
> Message: 7
> Date: Sun, 04 Mar 2012 18:50:35 +0000
> From: " Martin Harrison " <martin at thelightingshed.co.uk>
> Subject: Re: [Icecast] Hardware-based Icecast source client
> To: " Gavin Stephens " <small.net.nz at gmail.com>,        icecast at xiph.org
> Message-ID: <133088703779028274 at ukmrpl004>
> Content-Type: text/plain; charset="utf-8"
>
> Yes the barix extreamers work fine with icecast. I used to use them as
> studio to transmitter links for a radio station.
>
> Martin
>
> ----- Reply message -----
> From: "Gavin Stephens" <small.net.nz at gmail.com>
> Date: Sun, Mar 4, 2012 02:47
> Subject: [Icecast] Hardware-based Icecast source client
> To: <icecast at xiph.org>
>
> What's a plug computer?
>
> Does anyone know if Barix extreamers work with IceCast?
>
> On 2012-03-04 09:16, TheDarkener wrote:
> > Hi all,
> >
> > I'm in the midst of creating a turnkey Icecast source client embedded in
> > a plug computer, using Ices2.
> >
> > I've hacked together some scripts to automate the starting and stopping
> > of a live stream (launched by pressing buttons on the device). It's dead
> > easy once the network/server is configured - you just plug it in, push a
> > button and you're live.
> >
> > It accepts any Debian compatible USB audio device - I've verified my
> > nice stereo microphone (made by Blue) and a USB direct-audio device
> > works great. It can hook into your existing network via wired or
> > wireless. I've used it already to broadcast live concerts to my station
> > and even with the microphone, provided it's placed well, provides
> > exceptional sound quality over 64kb/sec. Would be even better if it was
> > 128 or more, obviously, but bars/venues rarely have decent Internet
> > connections available.
> >
> > I have my own Icecast server which I provide stream mounts for but there
> > are other Icecast server vendors out there too that this would be
> > compatible with.
> >
> > ATM network configuration is done manually, but it's vanilla Debian (on
> > ARM platform) so it's not too difficult. If I'm able to generate
> > interest and get some sales, I will be recruiting someone to make a nice
> > web configuration UI for everything. In the interim I'm thinking of
> > putting together some simple shell scripts to automate network
> > configuration. If it's wired (DHCP), no network configuration is
> necessary.
> >
> > Would anyone here be interested? I'm just starting out so I would want
> > to have a couple of 'guinea pigs' to help me test it out (I would
> > provide the hardware/streaming service at a discounted rate). I think
> > "IceBox" would be a cool name for it, too ;) I have an existing business
> > and reseller's permit so I am a legit hardware/service vendor.
> >
> > Any feedback is appreciated - here's a link to what I've put together as
> > a marketing blurb for music venues: http://socorock.com/?page_id=4345
> >
> >
> > Cheers,
> > Jordan
> >
> _______________________________________________
> 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/20120304/8049ac76/attachment.htm
>
> ------------------------------
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
>
> End of Icecast Digest, Vol 94, Issue 2
> **************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20120304/421dae50/attachment.htm>