From winnjohnston at gmail.com  Fri Jun  3 16:41:50 2011
From: winnjohnston at gmail.com (Winn Johnston)
Date: Fri, 3 Jun 2011 12:41:50 -0400
Subject: [Icecast] Question about setting up a mixing board Icecast2 Ices
	Winamp
Message-ID: <BANLkTinM=viTe2Luzn_BUFOmhce6Bt9u7A@mail.gmail.com>

Hello,

(first post)
I have been running icecast2 with ices on my Debian server for some
time. I use the winamp plugin too.  I have now decided to do live
mobile broadcasts, but it is a little clunky. I am looking to purchase
a small mixing board, i have a 58 Mic i will use with it. So here is
what my proposed setup,

1. Setup with a wireless mic system on channel 1
2. streaming music on channel 2 & 3
3. phone on channel 4
4. Icecast2 (Debian)
5. Ices (Debian)
6. winamp plugin (MS Windows 7 64 bit)
7. stream type .ogg

all running into my laptop's line in or mic in.

I could really use some suggestions or critiques on this before i jump in.

Thanks All, and happy Friday!

-winn


From martin at thelightingshed.co.uk  Fri Jun  3 18:14:55 2011
From: martin at thelightingshed.co.uk (Martin Harrison)
Date: Fri, 3 Jun 2011 19:14:55 +0100
Subject: [Icecast] Icecast authentication cant resolve address on Debian
Message-ID: <61552040caac9673ddc92391a354fd85.squirrel@webmail.plus.net>

Hi,

I am trying to use the url authentication method but am having trouble
getting icecast to work on a Debian installation on a VPS platform.

I have logged in my VPS as root and installed icecast using

apt-get install icecast2
setup the config file and then set ENABLE=true in /etc/init.d/icecast2

This initialy didn't work as it couldn't access log files and then had
trouble with the graphics on the admin pages.
I fixed this by copying the graphics from /usr/share/icecast2/web into
/etc/icecast/web and by changing the log/web/admin paths
from /var/log/icecast to /log and /usr/share/icecast2/web to /web.
I also had to change the base dir fromto /usr/share/icecast2 to
/etc/icecast as none of the linked xmls files could be read.

At this point icecast will run, display the admin pages correctly, allow a
source to conenct and users can listen.

However when I enable the authentication it fails to resolve the address
for the authentication script. The log files contain just two warnings
that I don't understand the implications of/can't resolve.

[2011-06-03  16:47:46] WARN stats/stats_event_conv No charset found for
"ISO8859-1"
[2011-06-03  16:55:11] WARN auth_url/url_add_listener auth to server
http://www.***.co.uk/online/auth.php failed with Couldn't resolve host
'www.***.co.uk'

running curl from the icecast2 account created during the installation
works just fine returning

* About to connect() to www.***.co.uk port 80 (#0)
*   Trying 178.250.***.***... connected
* Connected to www.***.co.uk (178.250.***.***) port 80 (#0)
> GET /online/auth.php HTTP/1.1
> User-Agent: curl/7.18.2 (x86_64-pc-linux-gnu) libcurl/7.18.2
OpenSSL/0.9.8g zlib/1.2.3.3 libidn/1.8 libssh2/0.18
> Host: www.***.co.uk
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Fri, 03 Jun 2011 17:22:35 GMT
< Server: Apache
< icecast-auth-user: 0
< icecast-auth-message: Invalid Stream Requested
< Content-Length: 0
< Connection: close
< Content-Type: text/html
<
* Closing connection #0


I am assuing that this is something to do with access rights but am no
unix expert (I developed my authentication system with icecast on a
windows box trouble free).

The relevant sections of the config file are below. any help is really
appreciated.

     <mount>
        <mount-name>/****.mp3</mount-name>
        <password>******</password>
        <intro>/intro.mp3</intro>
        <charset>ISO8859-1</charset>
        <public>0</public>
        <max-listeners>500</max-listeners>
        <stream-name>My Station</stream-name>
        <stream-description>Noise on my station</stream-description>
        <stream-url>http://www.***.co.uk</stream-url>
        <genre>Speech</genre>
        <bitrate>64</bitrate>
        <hidden>0</hidden>
        <burst-size>65536</burst-size>
        <authentication type="url">
            <option name="listener_add"
value="http://www.***.co.uk/online/auth.php"/>
            <option name="listener_remove"
value="http://www.***.co.uk/online/auth.php"/>
            <option name="auth_header" value="icecast-auth-user: 1"/>
            <option name="timelimit_header" value="icecast-auth-timelimit:"/>
        </authentication>
    </mount>
    <fileserve>1</fileserve>

    <paths>
        <basedir>/etc/icecast2</basedir>

        <logdir>/log</logdir>
        <webroot>/web</webroot>
        <adminroot>/admin</adminroot>
        <alias source="/" dest="/status.xsl"/>
    </paths>

    <logging>
        <accesslog>access.log</accesslog>
        <errorlog>error.log</errorlog>
      	<loglevel>3</loglevel> <!-- 4 Debug, 3 Info, 2 Warn, 1 Error -->
      	<logsize>10000</logsize> <!-- Max size of a logfile -->
    </logging>

    <security>
        <chroot>1</chroot>
        <changeowner>
            <user>icecast2</user>
            <group>icecast</group>
        </changeowner>
    </security>





From karl at xiph.org  Fri Jun  3 18:44:31 2011
From: karl at xiph.org (Karl Heyes)
Date: Fri, 03 Jun 2011 19:44:31 +0100
Subject: [Icecast] Icecast authentication cant resolve address on Debian
In-Reply-To: <61552040caac9673ddc92391a354fd85.squirrel@webmail.plus.net>
References: <61552040caac9673ddc92391a354fd85.squirrel@webmail.plus.net>
Message-ID: <4DE92B8F.5080108@xiph.org>

On 03/06/11 19:14, Martin Harrison wrote:
> Hi,
>
> I am trying to use the url authentication method but am having trouble
> getting icecast to work on a Debian installation on a VPS platform.
>
> I have logged in my VPS as root and installed icecast using
>
> apt-get install icecast2
> setup the config file and then set ENABLE=true in /etc/init.d/icecast2
>
> This initialy didn't work as it couldn't access log files and then had
> trouble with the graphics on the admin pages.
> I fixed this by copying the graphics from /usr/share/icecast2/web into
> /etc/icecast/web and by changing the log/web/admin paths
> from /var/log/icecast to /log and /usr/share/icecast2/web to /web.
> I also had to change the base dir fromto /usr/share/icecast2 to
> /etc/icecast as none of the linked xmls files could be read.
>
> At this point icecast will run, display the admin pages correctly, allow a
> source to conenct and users can listen.
>
> However when I enable the authentication it fails to resolve the address
> for the authentication script. The log files contain just two warnings
> that I don't understand the implications of/can't resolve.
>
> [2011-06-03  16:47:46] WARN stats/stats_event_conv No charset found for
> "ISO8859-1"
> [2011-06-03  16:55:11] WARN auth_url/url_add_listener auth to server
> http://www.***.co.uk/online/auth.php failed with Couldn't resolve host
> 'www.***.co.uk'


> I am assuing that this is something to do with access rights but am no
> unix expert (I developed my authentication system with icecast on a
> windows box trouble free).
>
> The relevant sections of the config file are below. any help is really
> appreciated.

>      <paths>
>          <basedir>/etc/icecast2</basedir>

>      </paths>

>      <security>
>          <chroot>1</chroot>

The distribution package makers should take more care in such cases. If 
you want to use DNS names then the mechanism for name lookups needs to 
be complete if you want to use a chroot jail.  This means that the 
configuration files or libraries need to exist within the jail.  The 
simplest change would be to use the IP address as that won't require the 
lookup or avoid the chroot to avoid the restricted directories (use full 
paths) but if you want the DNS lookup in a jail then the mechanism is 
basically

/etc/nsswitch.conf
   read hosts: entry
   lib load of /lib/libnss_... (file, dns etc depending on the protocol)

/lib/libnss_dns... reads /etc/resolv.conf


karl.


From winnjohnston at gmail.com  Sat Jun  4 11:27:38 2011
From: winnjohnston at gmail.com (Winn Johnston)
Date: Sat, 4 Jun 2011 07:27:38 -0400
Subject: [Icecast] .ogg stream player
Message-ID: <BANLkTi=yP7uD97MWOLKt2aQ4-aLPJQEugQ@mail.gmail.com>

Hello all :)

I am looking to upgrade to a online, embedded player that will read
and display some of the meta data or maybe just the file name of my
.ogg files, like track and artist name. Currently i am using the
JOrbis Player. What is everyone else using? What suggestions does
everyone have? I am running icecast2 and ices on a debian server.

Thanks Again
-winn


From Thomas.Rucker at tieto.com  Sun Jun  5 14:11:25 2011
From: Thomas.Rucker at tieto.com (Thomas.Rucker at tieto.com)
Date: Sun, 5 Jun 2011 17:11:25 +0300
Subject: [Icecast] .ogg stream player
In-Reply-To: <BANLkTi=yP7uD97MWOLKt2aQ4-aLPJQEugQ@mail.gmail.com>
References: <BANLkTi=yP7uD97MWOLKt2aQ4-aLPJQEugQ@mail.gmail.com>
Message-ID: <5E49EEF5B3B23549BAF01B43D0C2BB3016E1ED5CEC@EXMB03.eu.tieto.com>

Hi,

>-----Original Message-----
>Sent: Saturday, 04 June, 2011 14:28
>Subject: [Icecast] .ogg stream player

>I am looking to upgrade to a online, embedded player that will read
>and display some of the meta data or maybe just the file name of my
>.ogg files, like track and artist name. Currently i am using the
>JOrbis Player. What is everyone else using? What suggestions does
>everyone have? I am running icecast2 and ices on a debian server.

I'd recommend to have a look at direct browser support html5-<audio> 
element and FFMP3 as a possible flash based fallback.

Notice that Mozilla has still not fixed their ogg demuxer in their
core, so all their Products expect a non-chained stream.
If you run an encoder in the first place and don't send metadata
you're safe. Otherwise you need to strip the metadata e.g. using
liquidsoap to provide a (second) stream that will work in Firefox.

For Metadata you might want to look at alternative options like
polling a xslt file that contains current metadata.
For an example check here:
http://www.ruecker-itk.de/foss/icecast/xslt/rds.xsl
(just change stream name and put it into your icecast webroot)

HTH

Thomas

From geoff at QuiteLikely.com  Mon Jun  6 13:50:52 2011
From: geoff at QuiteLikely.com (Geoff Shang)
Date: Mon, 6 Jun 2011 16:50:52 +0300 (IDT)
Subject: [Icecast] Using Icecast over IPv6
Message-ID: <alpine.DEB.2.00.1106061637200.4931@data.home>

Hi,


I realise this might be a Debian-specific question.

I've got access to two hosts which have IPv6 connectivity, both of which 
are running Icecast 2.3.2.  One is still running Debian Lenny and can be 
reached via IPv6 just fine, but the other is running Debian Squeeze and 
cannot.  In addition, my local server which does not have IPv6 conectivity 
to the Internet but which can be reached at localhost via ::1 and which 
also runs Debian Squeeze cannot either.

To test, I used:
telnet <IPv6address> 8000

The Squeeze boxes returned a "Connection Refused" error but the Lenny 
machine answered the call.

As far as I can see, there's no difference in the way these servers are 
configured.  I configured all three based on the shipped config file. 
There's nothing in the Debian-specific changelog which indicates a change 
in this regard.  And the Icecast2 documentation says that IPv6 should just 
work if no bind atributes are specified.

Any thoughts?

Geoff.



From Thomas.Rucker at tieto.com  Mon Jun  6 14:00:52 2011
From: Thomas.Rucker at tieto.com (Thomas.Rucker at tieto.com)
Date: Mon, 6 Jun 2011 17:00:52 +0300
Subject: [Icecast] Using Icecast over IPv6
In-Reply-To: <alpine.DEB.2.00.1106061637200.4931@data.home>
References: <alpine.DEB.2.00.1106061637200.4931@data.home>
Message-ID: <5E49EEF5B3B23549BAF01B43D0C2BB3016E1FDF5B0@EXMB03.eu.tieto.com>

Hi,

>-----Original Message-----
>From: icecast-bounces at xiph.org [mailto:icecast-bounces at xiph.org] On
>Behalf Of Geoff Shang
>Subject: [Icecast] Using Icecast over IPv6

>I realise this might be a Debian-specific question.

Bit yes, bit no. See below.

>I've got access to two hosts which have IPv6 connectivity, both of which
>are running Icecast 2.3.2.  One is still running Debian Lenny and can be
>reached via IPv6 just fine, but the other is running Debian Squeeze and
>cannot.

To your problem there are two approaches:
- bind explicitly to :: and to 0.0.0.0 (so an ipv4 and a separate ipv6 bind)
- change your sysctl.conf to contain: "net.ipv6.bindv6only = 0"

If you opt for the latter don't forget to reload sysctl settings or change that option using the 'sysctl' command. No reboot necessary!

This is because the latter setting changed in debian squeeze a while ago. It now defaults to a setting that prevents listening for ipv6 and ipv4 on the same bind. (This also used to break java)

Cheers

Thomas

From geoff at QuiteLikely.com  Mon Jun  6 14:39:09 2011
From: geoff at QuiteLikely.com (Geoff Shang)
Date: Mon, 6 Jun 2011 17:39:09 +0300 (IDT)
Subject: [Icecast] Using Icecast over IPv6
In-Reply-To: <5E49EEF5B3B23549BAF01B43D0C2BB3016E1FDF5B0@EXMB03.eu.tieto.com>
References: <alpine.DEB.2.00.1106061637200.4931@data.home>
	<5E49EEF5B3B23549BAF01B43D0C2BB3016E1FDF5B0@EXMB03.eu.tieto.com>
Message-ID: <alpine.DEB.2.00.1106061736120.4931@data.home>

Hi,

Thanks for the quick answer!

On Mon, 6 Jun 2011, Thomas.Rucker at tieto.com wrote:

> To your problem there are two approaches:
> - bind explicitly to :: and to 0.0.0.0 (so an ipv4 and a separate ipv6 bind)
> - change your sysctl.conf to contain: "net.ipv6.bindv6only = 0"

hmmm.  OK but this implies (does it not) that 
/proc/sys/net/ipv6/bindv6only should now contain something other than 0. 
It doesn't (i.e. it does contain 0).

> If you opt for the latter don't forget to reload sysctl settings or 
> change that option using the 'sysctl' command. No reboot necessary!


If I opt for the latter, will it break when I upgrade to the next Debian 
release?

> This is because the latter setting changed in debian squeeze a while 
> ago. It now defaults to a setting that prevents listening for ipv6 and 
> ipv4 on the same bind. (This also used to break java)

Is there a good reason to disable this?

Geoff.



From Thomas.Rucker at tieto.com  Mon Jun  6 14:59:29 2011
From: Thomas.Rucker at tieto.com (Thomas.Rucker at tieto.com)
Date: Mon, 6 Jun 2011 17:59:29 +0300
Subject: [Icecast] Using Icecast over IPv6
In-Reply-To: <alpine.DEB.2.00.1106061736120.4931@data.home>
References: <alpine.DEB.2.00.1106061637200.4931@data.home>
	<5E49EEF5B3B23549BAF01B43D0C2BB3016E1FDF5B0@EXMB03.eu.tieto.com>
	<alpine.DEB.2.00.1106061736120.4931@data.home>
Message-ID: <5E49EEF5B3B23549BAF01B43D0C2BB3016E1FDF5D3@EXMB03.eu.tieto.com>

Hi,

>-----Original Message-----
>From: icecast-bounces at xiph.org [mailto:icecast-bounces at xiph.org] On
>Behalf Of Geoff Shang
>Sent: Monday, 06 June, 2011 17:39
>Subject: Re: [Icecast] Using Icecast over IPv6

>On Mon, 6 Jun 2011, Thomas.Rucker at tieto.com wrote:
>
>> To your problem there are two approaches:
>> - bind explicitly to :: and to 0.0.0.0 (so an ipv4 and a separate ipv6
>bind)
>> - change your sysctl.conf to contain: "net.ipv6.bindv6only = 0"
>
>hmmm.  OK but this implies (does it not) that
>/proc/sys/net/ipv6/bindv6only should now contain something other than 0.
>It doesn't (i.e. it does contain 0).

Huh? Then we might be onto something different.
It's been ages since we sat down and fixed icecast to bind to ipv6 properly.
So my recollection is a bit fuzzy and distribution/kernel changes might
have changed our behaviour in an undesirable way.

What certainly works is adding this:
<bind-address>::</bind-address>
to your <listen-socket>. It will make icecast listen to ipv4 AND ipv6 IF
bindv6only is set to '0'.


>> If you opt for the latter don't forget to reload sysctl settings or
>> change that option using the 'sysctl' command. No reboot necessary!
>
>
>If I opt for the latter, will it break when I upgrade to the next Debian
>release?
>
>> This is because the latter setting changed in debian squeeze a while
>> ago. It now defaults to a setting that prevents listening for ipv6 and
>> ipv4 on the same bind. (This also used to break java)
>
>Is there a good reason to disable this?

I'd recommend to read (at least part) of the related debian issue:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560044

But if it's already '0' then this is likely not the culprit.

Cheers

Thomas

From petr.pisar at atlas.cz  Mon Jun  6 15:20:50 2011
From: petr.pisar at atlas.cz (Petr Pisar)
Date: Mon, 6 Jun 2011 17:20:50 +0200
Subject: [Icecast] Using Icecast over IPv6
In-Reply-To: <alpine.DEB.2.00.1106061637200.4931@data.home>
References: <alpine.DEB.2.00.1106061637200.4931@data.home>
Message-ID: <20110606152050.GD2464@dhcp-0-146.brq.redhat.com>

On Mon, Jun 06, 2011 at 04:50:52PM +0300, Geoff Shang wrote:
> 
> I realise this might be a Debian-specific question.
> 
> I've got access to two hosts which have IPv6 connectivity, both of which 
> are running Icecast 2.3.2.  One is still running Debian Lenny and can be 
> reached via IPv6 just fine, but the other is running Debian Squeeze and 
> cannot.  In addition, my local server which does not have IPv6 conectivity 
> to the Internet but which can be reached at localhost via ::1 and which 
> also runs Debian Squeeze cannot either.
> 
I have icecast 2.3.2 on Gentoo and on Fedora and I can connect it using IPv6.

However I have privoxy on Debian/testing and it stopped to accept IPv4
connections. I suspect something has changed in Debian libc because listening
on [::] does not create multi-family socket anymore. You can get listening
socket on IPv4, or IPv6, but not both. Other servers I have in Debian creates
separate socket of IPv4 and for IPv6 to serve both protocols.

I had not enough time/interrest to investigate it more deeply, so I would be
happy if you found some reason.

-- Petr
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 230 bytes
Desc: not available
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20110606/631019a0/attachment.sig>

From geoff at QuiteLikely.com  Mon Jun  6 16:05:45 2011
From: geoff at QuiteLikely.com (Geoff Shang)
Date: Mon, 6 Jun 2011 19:05:45 +0300 (IDT)
Subject: [Icecast] Using Icecast over IPv6
In-Reply-To: <5E49EEF5B3B23549BAF01B43D0C2BB3016E1FDF5D3@EXMB03.eu.tieto.com>
References: <alpine.DEB.2.00.1106061637200.4931@data.home>
	<5E49EEF5B3B23549BAF01B43D0C2BB3016E1FDF5B0@EXMB03.eu.tieto.com>
	<alpine.DEB.2.00.1106061736120.4931@data.home>
	<5E49EEF5B3B23549BAF01B43D0C2BB3016E1FDF5D3@EXMB03.eu.tieto.com>
Message-ID: <alpine.DEB.2.00.1106061835520.4931@data.home>

On Mon, 6 Jun 2011, Thomas.Rucker at tieto.com wrote:

> What certainly works is adding this:
> <bind-address>::</bind-address>
> to your <listen-socket>. It will make icecast listen to ipv4 AND ipv6 IF
> bindv6only is set to '0'.

OK, so I only need the one listen socket with this bind, I don't need two 
sockets with different binds.  Or doI?

> I'd recommend to read (at least part) of the related debian issue:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560044
>
> But if it's already '0' then this is likely not the culprit.

Seems this is no longer the case.  From the Debian changelog:

netbase (4.42) unstable; urgency=low

   * Stop setting net.ipv6.bindv6only=1 by default. (Closes: #560238)

Guess it *is* something else then.

Geoff.



From winnjohnston at gmail.com  Tue Jun  7 15:29:07 2011
From: winnjohnston at gmail.com (Winn Johnston)
Date: Tue, 7 Jun 2011 11:29:07 -0400
Subject: [Icecast] fogg Player
Message-ID: <BANLkTinfQNKyv3chBUqqG-Yrmu50QpXTcQ@mail.gmail.com>

Anyone using this for their streams?

http://barelyfocused.net/blog/2008/10/03/flash-vorbis-player/

Thanks
-winn


From winnjohnston at gmail.com  Tue Jun  7 17:36:07 2011
From: winnjohnston at gmail.com (Winn Johnston)
Date: Tue, 7 Jun 2011 13:36:07 -0400
Subject: [Icecast] fogg Player HIGHJACKED libreFM
Message-ID: <BANLkTi=QoYiVOh1+Ccmt8k2uhJDJG9FWtA@mail.gmail.com>

lol, your right john, i was also looking at

http://savannah.gnu.org/bzr/?group=librefm

better?

-winn

On Tue, Jun 7, 2011 at 1:10 PM, Jonathan Nalley <jnalley at jnalley.com> wrote:
> Flash? ? ewww.... That's not very freedom-loving.
>
> On Tue, Jun 7, 2011 at 11:29 AM, Winn Johnston <winnjohnston at gmail.com> wrote:
>> Anyone using this for their streams?
>>
>> http://barelyfocused.net/blog/2008/10/03/flash-vorbis-player/
>>
>> Thanks
>> -winn
>> _______________________________________________
>> Icecast mailing list
>> Icecast at xiph.org
>> http://lists.xiph.org/mailman/listinfo/icecast
>>
>


From Thomas.Rucker at tieto.com  Tue Jun  7 20:08:44 2011
From: Thomas.Rucker at tieto.com (Thomas.Rucker at tieto.com)
Date: Tue, 7 Jun 2011 23:08:44 +0300
Subject: [Icecast] fogg Player
In-Reply-To: <BANLkTinfQNKyv3chBUqqG-Yrmu50QpXTcQ@mail.gmail.com>
References: <BANLkTinfQNKyv3chBUqqG-Yrmu50QpXTcQ@mail.gmail.com>
Message-ID: <5E49EEF5B3B23549BAF01B43D0C2BB3016E1FDFBFE@EXMB03.eu.tieto.com>

Hi,

>-----Original Message-----
>From: icecast-bounces at xiph.org [mailto:icecast-bounces at xiph.org] On
>Behalf Of Winn Johnston
>Sent: Tuesday, 07 June, 2011 18:29
>
>Anyone using this for their streams?
>
>http://barelyfocused.net/blog/2008/10/03/flash-vorbis-player/

I'd recommend to go for HTML5 and only as a fallback jorbis or FFMP3 (the latter being a Flash based ogg/vorbis player).

I believe I outlined recently how to prep a stream so that it will work with e.g. Firefox.

Cheers

Thomas

From thedarkener at logicalnetworking.net  Wed Jun  8 00:23:38 2011
From: thedarkener at logicalnetworking.net (TheDarkener)
Date: Tue, 07 Jun 2011 17:23:38 -0700
Subject: [Icecast] Fwd: TASCAM Pre-Sales Support Request has been received -
 Reference: 4B130AY5
Message-ID: <4DEEC10A.5040700@logicalnetworking.net>

I'm forwarding this to the Icecast list in hopes that others can gain
some perspective on how the Tascam company operates currently as far as
supporting the Linux platform...Kind of dissapointing since it is known
that at least the US-100 product works very well with newer Linux
distributions. Maybe we can gently push them in the right direction and
gain an audio product company that supports our software..


Sincerely,
Jordan


-------- Original Message --------
Subject: 	TASCAM Pre-Sales Support Request has been received -
Reference: 4B130AY5
Date: 	Wed, 08 Jun 2011 00:19:25 +0000
From: 	TASCAM Pre-Sales Support <custser at tascam.com>
To: 	Jordan Erickson <jerickson at logicalnetworking.net>



2011-06-07 17:19:25
Hello Jordan Erickson,
Thank you for contacting TASCAM.
This message has been automatically generated in response to the request
you submitted to our support system with Support Reference Code: 4B130AY5

Below is a copy of the message that you submitted:

Support Reference Code: 4B130AY5
Support Request Type: Pre-Sales Information
Product: General question
Your Question:
Hello,

I hope you can forward this to your support department supervisor.

I received the following message below regarding Linux compatibility with one of your products. I feel the response I got was completely sub-par, as it is well known that the US-100 device is well supported in Linux 2.6 kernels. I understand that the response I got was most likely because Linux is not officially supported by your company. My reason for sending you this message is to ask that you invest more resources in supporting those who use the Linux platform, as it represents a large portion of the audio processing market. I feel that if companies such as Tascam embraces the Linux and wider open source software communities, it will result in many more sales and a wider support community. Please consider this, and let me know if you have any questions. I consider myself a part of the open source community, and I'm taking the time to write this to you because I want to show you that the people involved with Linux are eager to be able to use quality products such as what Ta
 scam has to offer.. but if your company simply does not care to support these advanced users, these users will simply turn toward other products.

Sincerely,
Jordan Erickson

---
2011-06-07 17:00:27
Hello Jordan Erickson,
Thank you for contacting TASCAM.
Our customer support representative, NFaison, has written
the following response to your message:


Jordan,

Our interfaces are only compatible with the Windows or Macintosh operating systems.

Thank you for your interest in TASCAM products.


Below is a copy of the message that you submitted:

Support Reference Code: BLKQQY0R
Support Request Type: Pre-Sales Information
Product: US-100
Your Question:
Is the US-100 compatible with Linux 2.4 series kernels? I would like to use this with "Damn Small Linux" which is based on the 2.4 series kernel
for an embedded device in streaming audio. Thank you for your input - Sincerely, Jordan Erickson



Please allow up to 2 working days for a response.
We will contact you again at this email address.
If you have any additional questions, please reply to this message with a
copy of the Support Reference Code in the subject line.
=========================================================================

Follow us on Facebook:
http://www.facebook.com/pages/Tascam/156388484378789

And on Twitter:
http://twitter.com/TASCAMpro

=========================================================================
Your privacy is important to us.
This message and any other communications we share with you are bound by
the terms of our Privacy Policy, which can be located at:
http://tascam.com/company/privacy/
=========================================================================
Copyright (C) 2010 TEAC Corporation. All rights reserved.





From getpaid00 at gmail.com  Tue Jun 14 01:06:11 2011
From: getpaid00 at gmail.com (Luis Barrett)
Date: Mon, 13 Jun 2011 18:06:11 -0700
Subject: [Icecast] Need Assistant
Message-ID: <BANLkTinX2vm7ZjsBS79mVpps=pDbWWByqg@mail.gmail.com>

Hi,

I have a few questions I hope you someone can answer:

1.) We need the info to access the cpanel and configure icecast2...? I don't
believe we
ever received the info when it was installed.

http://174.141.228.168:8000/admin/

2.)  Where can we find the html code to an mp3 or wav player that will
broadcast the
signal sent to icecast2 from our source? (to place on our existing website
pages)


Thank you,

Luis Barrett
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20110613/69ae30b8/attachment.htm>

From msmith at xiph.org  Tue Jun 14 01:16:23 2011
From: msmith at xiph.org (Michael Smith)
Date: Mon, 13 Jun 2011 18:16:23 -0700
Subject: [Icecast] Need Assistant
In-Reply-To: <BANLkTinX2vm7ZjsBS79mVpps=pDbWWByqg@mail.gmail.com>
References: <BANLkTinX2vm7ZjsBS79mVpps=pDbWWByqg@mail.gmail.com>
Message-ID: <BANLkTim_eVP9GEpjeSdeGG=FtPEG3eOdTQ@mail.gmail.com>

It sounds like some hosting provider is running an icecast server for you.

That's not us - we developer the software. You should contact your
hosting provider.

Miker


On Mon, Jun 13, 2011 at 6:06 PM, Luis Barrett <getpaid00 at gmail.com> wrote:
> Hi,
>
> I have a few questions I hope you someone can answer:
>
> 1.) We need the info to access the cpanel and configure icecast2...? I don't
> believe we
> ever received the info when it was installed.
>
> http://174.141.228.168:8000/admin/
> 2.)? Where can we find the html code to an mp3 or wav player that will
> broadcast the
> signal sent to icecast2 from our source? (to place on our existing website
> pages)
>
>
> Thank you,
>
> Luis Barrett
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
>


From timothyclark113 at gmail.com  Tue Jun 14 02:08:30 2011
From: timothyclark113 at gmail.com (Timothy Clark)
Date: Mon, 13 Jun 2011 22:08:30 -0400
Subject: [Icecast] Need Assistant
In-Reply-To: <BANLkTinX2vm7ZjsBS79mVpps=pDbWWByqg@mail.gmail.com>
References: <BANLkTinX2vm7ZjsBS79mVpps=pDbWWByqg@mail.gmail.com>
Message-ID: <BANLkTimLtaSnf5HQWaWAEuY9XupW3gKqvw@mail.gmail.com>

i have no idea if this will help but when i want to find things like that i
first consalt the icecast set up file. hope this helps.
 Timothy
 http://www.timothyclarkmusic.webs.com

On Mon, Jun 13, 2011 at 9:06 PM, Luis Barrett <getpaid00 at gmail.com> wrote:

> Hi,
>
> I have a few questions I hope you someone can answer:
>
> 1.) We need the info to access the cpanel and configure icecast2...? I
> don't believe we
> ever received the info when it was installed.
>
> http://174.141.228.168:8000/admin/
>
> 2.)  Where can we find the html code to an mp3 or wav player that will
> broadcast the
> signal sent to icecast2 from our source? (to place on our existing website
> pages)
>
>
> Thank you,
>
> Luis Barrett
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
>


-- 
Timothy

      unsigned independent singer songwriter.


http://www.timothyclarkmusic.webs.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20110613/c9a56db8/attachment.htm>

From getpaid00 at gmail.com  Wed Jun 15 01:17:58 2011
From: getpaid00 at gmail.com (Luis Barrett)
Date: Tue, 14 Jun 2011 18:17:58 -0700
Subject: [Icecast] How to stream audio
Message-ID: <BANLkTinCugSo3g2VpqDRdLNRss6-B1TwqA@mail.gmail.com>

Hi and thank you for your time. We have installed icecast2 on our server and
would like your guidance on how to effectively stream audio to our visitors.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20110614/380e8665/attachment.htm>

From Thomas.Rucker at tieto.com  Wed Jun 15 06:55:06 2011
From: Thomas.Rucker at tieto.com (Thomas.Rucker at tieto.com)
Date: Wed, 15 Jun 2011 09:55:06 +0300
Subject: [Icecast] How to stream audio
In-Reply-To: <BANLkTinCugSo3g2VpqDRdLNRss6-B1TwqA@mail.gmail.com>
References: <BANLkTinCugSo3g2VpqDRdLNRss6-B1TwqA@mail.gmail.com>
Message-ID: <5E49EEF5B3B23549BAF01B43D0C2BB3016E3548982@EXMB03.eu.tieto.com>

Hi,

Thank you for reading this:
http://liveice.sourceforge.net/understanding.html

and then this:
http://www.icecast.org/3rdparty.php

and if you need to configure your icecast server to your needs this:
http://www.icecast.org/docs/icecast-2.3.2/

Cheers

Thomas


From suarez.jf at gmail.com  Wed Jun 15 09:36:57 2011
From: suarez.jf at gmail.com (=?ISO-8859-1?Q?Facundo_Su=E1rez?=)
Date: Wed, 15 Jun 2011 06:36:57 -0300
Subject: [Icecast] metadata update
Message-ID: <BANLkTi=B80_wmm7fN8QSPZx+P5WfvAaHJQ@mail.gmail.com>

hi

i need to ask you how to do configuring icecast about updating
metadata. I know well streamer source is sending ok its metadata
stream. I proved it with another well working icecast server. But when
connecting with my server for "hearing radio", i just receive the
metadata info of the first theme streamed, no updates are displayed,
even when i know the source sends its info.

Any help?

Thanks.

-- 
Facundo Suarez
Neuquen - Capital
suarezjf -> twitter

()? ascii ribbon campaign - contra el coreo html
/\? www.asciiribbon.org?? - contra adjuntos propietarios


From getpaid00 at gmail.com  Thu Jun 16 00:25:39 2011
From: getpaid00 at gmail.com (Luis Barrett)
Date: Wed, 15 Jun 2011 17:25:39 -0700
Subject: [Icecast] Need help with config file
Message-ID: <BANLkTim42MZTMYRq5b-kLN73q7Fg45wFhw@mail.gmail.com>

Thank you for your time...we made some changes to our config file and the
server doesn't want to start with the command icecast -c
/path/to/icecast.xml giving the error:


'Could not create listener socket on port 8000 Server startup failed.
Exiting'

can you look at the config file bellow and let us know of any changes that
might help.  we need to be able to have 10,000 clients listening to the
server at once. 1,000 to start and we want our mount point to be
/stream1.mp3
Thank you in advance

Luis



<icecast>
<limits>
<clients>1000</clients>
<sources>2</sources>
<threadpool>5</threadpool>
<queue-size>524288</queue-size>
<client-timeout>30</client-timeout>
<header-timeout>15</header-timeout>
<source-timeout>10</source-timeout>

<burst-size>65535</burst-size>
</limits>

<authentication>

<source-password>anveo23</source-password>

<relay-password>hackme</relay-password>


<admin-user>admin</admin-user>
<admin-password>mami</admin-password>
</authentication>



<yp-url-timeout>15</yp-url-timeout>
<yp-url>http://dir.xiph.org/cgi-bin/yp-cgi</yp-url&gt;
</directory>
<directory>
<yp-url-timeout>15</yp-url-timeout>
<yp-url>http://www.oddsock.org/cgi-bin/yp-cgi</yp-url&gt;
</directory>
-->


<hostname>localhost</hostname>


8000</port> -->
127.0.0.1</bind-address>-->

elements -->
<listen-socket>
<port>8000</port>
127.0.0.1</bind-address> -->
</listen-socket>

<port>8001</port>
</listen-socket>
-->

127.0.0.1</master-server>-->
8001</master-server-port>-->
120</master-update-interval>-->
hackme</master-password>-->
1</master-relay-auth>-->

definitions here.
The default is 0 -->
1</relays-on-demand>-->


and this port to master server for redirecting
clients to this slave -->
8000</master-redirect-port>-->



<server>127.0.0.1</server>
<port>8001</port>
<mount>example.ogg</mount>
<local-mount>example.ogg</local-mount>
<on-demand>1</on-demand>

<relay-shoutcast-metadata>0</relay-shoutcast-metadata>
</relay>
-->

section if you want to use advanced options,
like alternative usernames or passwords
<mount>
<mount-name>example.ogg</mount-name>

<username>source</username>
<password>memore</password>

<max-listeners>1</max-listeners>
<dump-file>/tmp/dump-example1.ogg</dump-file>
<burst-size>65536</burst-size>
<fallback-mount>/example2.ogg</fallback-mount>
<fallback-override>1</fallback-override>
<fallback-when-full>1</fallback-when-full>
<intro>/path/to/stream-intro.ogg</intro>
<hidden>1</hidden>
<authentication type="htpasswd">
<option name="filename" value="myauth"/>
<option name="allow_duplicate_users" value="0"/>
</authentication>
<on-connect>/home/icecast/bin/stream-start</on-connect>
<on-disconnect>/home/icecast/bin/stream-stop</on-disconnect>
</mount>
-->

....
<authentication type="command">
<option name="filename" value="auth_verify"/>
</authentication>

or

for url auth, the add url needs to return a "icecast-auth-user: 1" http
header for a user to authenicate. Both urls are sent params via POST,
add is sent id, mount, user, pass, ip, useragent
remove is passed id, mount, user, pass, duration

<authentication type="url">

state username/password if url requires it

<option name="username" value="admin"/>
<option name="password" value="hackme"/>
<option name="add" value="http://myauthserver.com/scripts/add_listener.php"/
>
<option name="remove" value="
http://myauthserver.com/scripts/del_listener.php"/>
</authentication>
</mount -->


<fileserve>1</fileserve>

/stream1.mp3</shoutcast-mount&gt;
-->

<paths>

<basedir>/usr/share/icecast</basedir>

is turned on below, these paths must both
be relative to the new root, not the original root -->
<logdir>/var/log/icecast</logdir>
<webroot>/usr/share/icecast/web</webroot>
<adminroot>/usr/share/icecast/admin</adminroot>
<pidfile>/var/run/icecast/icecast.pid</pidfile>



-->

<alias source="/" dest="/status.xsl"/>
</paths>

<logging>
<accesslog>access.log</accesslog>
<errorlog>error.log</errorlog>
<playlistlog>playlist.log</playlistlog>
<loglevel>4</loglevel>
</logging>

<security>
<chroot>0</chroot>
<changeowner>
<user>icecast</user>
<group>icecast</group>
</changeowner>
</security>
</icecast>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20110615/41af96b8/attachment.htm>

From bigwavedave at gmail.com  Thu Jun 16 02:39:46 2011
From: bigwavedave at gmail.com (Big Wave Dave)
Date: Wed, 15 Jun 2011 19:39:46 -0700
Subject: [Icecast] Need help with config file
In-Reply-To: <BANLkTim42MZTMYRq5b-kLN73q7Fg45wFhw@mail.gmail.com>
References: <BANLkTim42MZTMYRq5b-kLN73q7Fg45wFhw@mail.gmail.com>
Message-ID: <BANLkTikeZoeV6yXRDyLgfoPW+7FReP0nTg@mail.gmail.com>

On Wed, Jun 15, 2011 at 5:25 PM, Luis Barrett <getpaid00 at gmail.com> wrote:
> Thank you for your time...we made some changes to our config file and the
> server doesn't want to start with the command icecast -c
> /path/to/icecast.xml giving the error:
>
> 'Could not create listener socket on port 8000 Server startup failed.
> Exiting'
>
> can you look at the config file bellow and let us know of any changes that
> might help.? we need to be able to have 10,000 clients listening to the
> server at once. 1,000 to start and we want our mount point to be
> /stream1.mp3
> Thank you in advance
> Luis
>
>
>
> <icecast>
> <limits>
> <clients>1000</clients>
> <sources>2</sources>
> <threadpool>5</threadpool>
> <queue-size>524288</queue-size>
> <client-timeout>30</client-timeout>
> <header-timeout>15</header-timeout>
> <source-timeout>10</source-timeout>
>
> <burst-size>65535</burst-size>
> </limits>
>
> <authentication>
>
> <source-password>anveo23</source-password>
>
> <relay-password>hackme</relay-password>
>
> <admin-user>admin</admin-user>
> <admin-password>mami</admin-password>
> </authentication>
>
>
>
> <yp-url-timeout>15</yp-url-timeout>
> <yp-url>http://dir.xiph.org/cgi-bin/yp-cgi</yp-url&gt;
> </directory>
> <directory>
> <yp-url-timeout>15</yp-url-timeout>
> <yp-url>http://www.oddsock.org/cgi-bin/yp-cgi</yp-url&gt;
> </directory>
> -->
>
> <hostname>localhost</hostname>
>
> 8000</port> -->
> 127.0.0.1</bind-address>-->
>
> elements -->
> <listen-socket>
> <port>8000</port>
> 127.0.0.1</bind-address> -->
> </listen-socket>
>
> <port>8001</port>
> </listen-socket>
> -->
>
> 127.0.0.1</master-server>-->
> 8001</master-server-port>-->
> 120</master-update-interval>-->
> hackme</master-password>-->
> 1</master-relay-auth>-->
>
> definitions here.
> The default is 0 -->
> 1</relays-on-demand>-->
>
> and this port to master server for redirecting
> clients to this slave -->
> 8000</master-redirect-port>-->
>
>
>
> <server>127.0.0.1</server>
> <port>8001</port>
> <mount>example.ogg</mount>
> <local-mount>example.ogg</local-mount>
> <on-demand>1</on-demand>
>
> <relay-shoutcast-metadata>0</relay-shoutcast-metadata>
> </relay>
> -->
>
> section if you want to use advanced options,
> like alternative usernames or passwords
> <mount>
> <mount-name>example.ogg</mount-name>
>
> <username>source</username>
> <password>memore</password>
>
> <max-listeners>1</max-listeners>
> <dump-file>/tmp/dump-example1.ogg</dump-file>
> <burst-size>65536</burst-size>
> <fallback-mount>/example2.ogg</fallback-mount>
> <fallback-override>1</fallback-override>
> <fallback-when-full>1</fallback-when-full>
> <intro>/path/to/stream-intro.ogg</intro>
> <hidden>1</hidden>
> <authentication type="htpasswd">
> <option name="filename" value="myauth"/>
> <option name="allow_duplicate_users" value="0"/>
> </authentication>
> <on-connect>/home/icecast/bin/stream-start</on-connect>
> <on-disconnect>/home/icecast/bin/stream-stop</on-disconnect>
> </mount>
> -->
>
> ....
> <authentication type="command">
> <option name="filename" value="auth_verify"/>
> </authentication>
>
> or
>
> for url auth, the add url needs to return a "icecast-auth-user: 1" http
> header for a user to authenicate. Both urls are sent params via POST,
> add is sent id, mount, user, pass, ip, useragent
> remove is passed id, mount, user, pass, duration
>
> <authentication type="url">
>
> state username/password if url requires it
>
> <option name="username" value="admin"/>
> <option name="password" value="hackme"/>
> <option name="add"
> value="http://myauthserver.com/scripts/add_listener.php"/>
> <option name="remove"
> value="http://myauthserver.com/scripts/del_listener.php"/>
> </authentication>
> </mount -->
>
> <fileserve>1</fileserve>
>
> /stream1.mp3</shoutcast-mount&gt;
> -->
>
> <paths>
>
> <basedir>/usr/share/icecast</basedir>
>
> is turned on below, these paths must both
> be relative to the new root, not the original root -->
> <logdir>/var/log/icecast</logdir>
> <webroot>/usr/share/icecast/web</webroot>
> <adminroot>/usr/share/icecast/admin</adminroot>
> <pidfile>/var/run/icecast/icecast.pid</pidfile>
>
>
>
> -->
>
> <alias source="/" dest="/status.xsl"/>
> </paths>
>
> <logging>
> <accesslog>access.log</accesslog>
> <errorlog>error.log</errorlog>
> <playlistlog>playlist.log</playlistlog>
> <loglevel>4</loglevel>
> </logging>
>
> <security>
> <chroot>0</chroot>
> <changeowner>
> <user>icecast</user>
> <group>icecast</group>
> </changeowner>
> </security>
> </icecast>
>

Perhaps a silly question, but have you tried starting it when logged
in as "root"?   Is it possible some other application is already
running on port 8000?

Dave


From winnjohnston at gmail.com  Thu Jun 16 15:39:20 2011
From: winnjohnston at gmail.com (Winn Johnston)
Date: Thu, 16 Jun 2011 11:39:20 -0400
Subject: [Icecast] 16bit vs. 24bit
Message-ID: <BANLkTimPbhF9SqAxDBVaM3SZTNx81Mn+Rw@mail.gmail.com>

I bought this recently

http://www.amazon.com/Tascam-US-100-USB-Audio-Interface/dp/B002QQC1ZI

But i have been thinking maybe it would have been better to get a 24bit
version

http://tascam.com/product/us-600/images/

I guess i am streaming at a lower quality, but if i were recording the 24
bit would be better no?

Thoughts?

-winn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20110616/d1956d2c/attachment.htm>

From xiphmont at xiph.org  Thu Jun 16 16:05:04 2011
From: xiphmont at xiph.org (xiphmont at xiph.org)
Date: Thu, 16 Jun 2011 12:05:04 -0400
Subject: [Icecast] 16bit vs. 24bit
In-Reply-To: <BANLkTimPbhF9SqAxDBVaM3SZTNx81Mn+Rw@mail.gmail.com>
References: <BANLkTimPbhF9SqAxDBVaM3SZTNx81Mn+Rw@mail.gmail.com>
Message-ID: <BANLkTi=LAA-gi+H0bVW1zwqUqxKdJpOPEA@mail.gmail.com>

On Thu, Jun 16, 2011 at 11:39 AM, Winn Johnston <winnjohnston at gmail.com> wrote:
> I bought this recently
> http://www.amazon.com/Tascam-US-100-USB-Audio-Interface/dp/B002QQC1ZI
> But i have been thinking maybe it would have been better to get a 24bit
> version
> http://tascam.com/product/us-600/images/
> I guess i am streaming at a lower quality, but if i were recording the 24
> bit would be better no?
> Thoughts?

24 bit does not improve audio quality (and on consumer equipment, the
24 bit mode is usually only ~ 18 bits deep at best before noise swamps
things).  Unless you're using microphones that cost more than cars,
the mic isn't much more than 16 bits deep either.  (Well, OK, used
cars).

What 24 bits gives you is a little more headroom in a recording
environment.  You can hedge more against transients clipping without
giving away S/N.  If that's what you're looking for-- then 24 bits
makes sense.

Monty


From xiphmont at gmail.com  Sun Jun 26 15:28:18 2011
From: xiphmont at gmail.com (Monty Montgomery)
Date: Sun, 26 Jun 2011 11:28:18 -0400
Subject: [Icecast] [Video@Xiph] OGG Theora streaming
In-Reply-To: <341CCC01FD5E46F5A6AABE0AFDE67156@WCRBACKUPPC>
References: <341CCC01FD5E46F5A6AABE0AFDE67156@WCRBACKUPPC>
Message-ID: <BANLkTikSRmp0b-Uh6NN3+DuujoXjKjKnBA@mail.gmail.com>

>
> We are a online media company and are developing a new product that uses
> theora for video streaming. We used your free Visonair OGG streamer to test
> and it worked perfect.

Visionair isn't ours (xiph's) directly. but it does use our libraries
somewhere to do the actual encoding stuff.  Layers upon layers :-)  I
know about it and have seen it used, but never worked directly with it
myself.  I'm not sure what others on the list have-- there's a good
chance (it looks nice).  You may need to contact the Visionair folks
for setup help.

That said, we do know Icecast and the actual Ogg streaming formats
very well.  We can help debug from that side.

(BTW, Ogg isn't an acronym, it's just "Ogg")

> We would like to find out if your experts can help
> us complete our OGG streamer software. We are able to connect to icecast but
> the stream is unstable and buffers 90% of the time. We just need to get the
> streaming to the point where it is streaming smoothly with very little
> buffering.

I don't know Visionair setup, but Icecast itself doesn't do much
buffering; it's just a 1->many server that passes whatever the source
hands it onto whatever client connects.  The exception is when
'burst-on-connect' is enabled, in which case it keeps around a small
buffer so that when a client connects, it can fill the client-side
buffer rapidly.  There's also a little bit of in-band fanciness to
start an Ogg stream properly in the middle.

Are you doing broadcast streaming, or low-latency conferencing, or...?

(BTW, I've trimmed the response list down to just icecast at xiph.org
since that's the most appropriate place for it to go).

Monty
Xiph.Org


From raylutz at cognisys.com  Mon Jun 27 21:33:52 2011
From: raylutz at cognisys.com (Raymond Lutz)
Date: Mon, 27 Jun 2011 14:33:52 -0700
Subject: [Icecast] Multiple mount points without dynamic reencoding
Message-ID: <4E08F740.1020008@cognisys.com>

Hello:

I am running the icecast2.3.2 server and ices0.4 with a perl script 
which provides the filename of the next track to play. I am reencoding 
in advance using ffmpeg, which has been very reliable. My main stream is 
mp3, 64kbps / 44.1 kHz (mono) and I have pre-reencoded the tracks to 
32kbps / 22.05 kHz (mono), for a lower data rate stream. At this time, I 
have not figured out how to get a second mount point to work for the 32k 
stream.

The stream is at http://www.AirProgressive.org.

My content is "News/Talk" and tend to be very long, usually at least 1/2 
hour or 1 hour (or more). Fidelity is not as important as compatibility, 
so we are using mp3 format, and therefore, ices 0.4 version. (plus most 
of the files we get to play are mp3 and it is not under our control.)

It is pretty clear that icecast can deal with multiple mount points. 
Ices says it can too, but apparently to do so, it will require that I 
deal with dynamic reencoding, which thus far I have not been able to 
successfully run as it encounters a runtime error. (See the end of this 
email for the dump of the error.) So I have worked around this 
difficulty by pre-reencoding the audio using ffmpeg, which is very 
robust, but can take significant time to reencode a track of 30 to 60 
minutes (taking a number of minutes to do so). But this can be easily 
done in advance and cached as separate files. Doing this has eliminated 
glitches that will occur at track boundaries when going from track to 
track (although mp3 describes the bitrate and freq on a frame-by-frame 
basis, the assumption is that each track will be uniform, and thus, the 
entire stream will be uniform).

1. Is it possible to serve two file formats using ices, destined to two 
different mount points?
     a. Will I need to run two instances of ices to do it?
     b. Is there a way to specify which mount point a given file should 
be sent to, when ices_get_next() perl function is called? (i.e. if I 
return a list of filenames, will each filename be sent to the list of 
streams if reencoding is not enabled, for example??)

2. You say in your documentation that there is no interest in mp3 format 
files, which I find to be astonishing, since most audio files available 
are mp3 and almost none are Ogg/Vorbis or anything else. You can add me 
to the list of people who are interested, so you will no longer say 
there is no interest (or is this some sort of a joke that I don't 
understand?) Since most of the files we get access to are mp3, 
reencoding into Ogg/Vorbis will only decrease fidelity, and so it sounds 
silly to do that.

3. If you happen to know, is there any benefit to changing the sample 
rate to a lower value when reencoding, or is it just as good to use 
32K/44.1K as 32K/22.05K.

4. Currently, what is the best approach to get into the Shoutcast 
directory. Can I treat shoutcast as a slave and relay content to it? 
That mean I need to install shoutcast on my (linux) server, right? What 
are the configuration details?

Thank you for your kind assistance.

--Ray Lutz

==============================================
ERROR DUMP

*** glibc detected *** ices: free(): invalid pointer: 0xb7ddd008 ***
======= Backtrace: =========
/lib/libc.so.6[0xa965a5]
/lib/libc.so.6(cfree+0x59)[0xa969e9]
ices[0x804fcbb]
ices(ices_stream_loop+0x6d1)[0x804d431]
ices(main+0x33)[0x804b793]
/lib/libc.so.6(__libc_start_main+0xdc)[0xa42e9c]
ices[0x804b6a1]
======= Memory map: ========
00110000-00228000 r-xp 00000000 00:26 157335553  /usr/local/lib/libxml2.so.2.7.8
00228000-0022e000 rw-p 00117000 00:26 157335553  /usr/local/lib/libxml2.so.2.7.8
0022e000-00236000 r-xp 00000000 00:26 157335612  /usr/local/lib/libvorbisfile.so.3.3.4
00236000-00237000 rw-p 00007000 00:26 157335612  /usr/local/lib/libvorbisfile.so.3.3.4
00237000-0023c000 r-xp 00000000 00:26 157335602  /usr/local/lib/libogg.so.0.7.1
0023c000-0023d000 rw-p 00004000 00:26 157335602  /usr/local/lib/libogg.so.0.7.1
0040d000-00428000 r-xp 00000000 00:26 26871825   /lib/ld-2.5.so
00428000-00429000 r--p 0001a000 00:26 26871825   /lib/ld-2.5.so
00429000-0042a000 rw-p 0001b000 00:26 26871825   /lib/ld-2.5.so
00543000-0056a000 r-xp 00000000 00:26 26871781   /lib/libm-2.5.so
0056a000-0056b000 r--p 00026000 00:26 26871781   /lib/libm-2.5.so
0056b000-0056c000 rw-p 00027000 00:26 26871781   /lib/libm-2.5.so
005a1000-005e8000 r-xp 00000000 00:26 157335629  /usr/local/lib/libmp3lame.so.0.0.0
005e8000-005e9000 rw-p 00046000 00:26 157335629  /usr/local/lib/libmp3lame.so.0.0.0
005e9000-0061c000 rw-p 005e9000 00:00 0
0068a000-0069f000 r-xp 00000000 00:26 26871789   /lib/libnsl-2.5.so
0069f000-006a0000 r--p 00014000 00:26 26871789   /lib/libnsl-2.5.so
006a0000-006a1000 rw-p 00015000 00:26 26871789   /lib/libnsl-2.5.so
006a1000-006a3000 rw-p 006a1000 00:00 0
0072e000-00737000 r-xp 00000000 00:26 26871796   /lib/libcrypt-2.5.so
00737000-00738000 r--p 00008000 00:26 26871796   /lib/libcrypt-2.5.so
00738000-00739000 rw-p 00009000 00:26 26871796   /lib/libcrypt-2.5.so
00739000-00760000 rw-p 00739000 00:00 0
00799000-007a4000 r-xp 00000000 00:26 26871882   /lib/libgcc_s-4.1.2-20080825.so.1
007a4000-007a5000 rw-p 0000a000 00:26 26871882   /lib/libgcc_s-4.1.2-20080825.so.1
007e0000-007f0000 r-xp 00000000 00:26 26871874   /lib/libresolv-2.5.so
007f0000-007f1000 r--p 0000f000 00:26 26871874   /lib/libresolv-2.5.so
007f1000-007f2000 rw-p 00010000 00:26 26871874   /lib/libresolv-2.5.so
007f2000-007f4000 rw-p 007f2000 00:00 0
0084f000-00876000 r-xp 00000000 00:26 157335607  /usr/local/lib/libvorbis.so.0.4.5
00876000-00877000 rw-p 00027000 00:26 157335607  /usr/local/lib/libvorbis.so.0.4.5
008ee000-008f8000 r-xp 00000000 00:26 26871832   /lib/libnss_files-2.5.so
008f8000-008f9000 r--p 00009000 00:26 26871832   /lib/libnss_files-2.5.so
008f9000-008fa000 rw-p 0000a000 00:26 26871832   /lib/libnss_files-2.5.so
00a2d000-00b7f000 r-xp 00000000 00:26 26871861   /lib/libc-2.5.so
00b7f000-00b81000 r--p 00152000 00:26 26871861   /lib/libc-2.5.so
00b81000-00b82000 rw-p 00154000 00:26 26871861   /lib/libc-2.5.so
00b82000-00b85000 rw-p 00b82000 00:00 0
00c76000-00c77000 r-xp 00c76000 00:00 0          [vdso]
00d7f000-00d8c000 r-xp 00000000 00:26 157335622  /usr/local/lib/libshout.so.3.2.0
00d8c000-00d8d000 rw-p 0000c000 00:26 157335622  /usr/local/lib/libshout.so.3.2.0
00e2d000-00e30000 r-xp 00000000 00:26 26871871   /lib/libdl-2.5.so
00e30000-00e31000 r--p 00002000 00:26 26871871   /lib/libdl-2.5.so
00e31000-00e32000 rw-p 00003000 00:26 26871871   /lib/libdl-2.5.so
00e6d000-00e6f000 r-xp 00000000 00:26 26871795   /lib/libutil-2.5.so
00e6f000-00e70000 r--p 00001000 00:26 26871795   /lib/libutil-2.5.so
00e70000-00e71000 rw-p 00002000 00:26 26871795   /lib/libutil-2.5.so
00e7f000-00e94000 r-xp 00000000 00:26 26871820   /lib/libpthread-2.5.so
00e94000-00e95000 r--p 00015000 00:26 26871820   /lib/libpthread-2.5.so
00e95000-00e96000 rw-p 00016000 00:26 26871820   /lib/libpthread-2.5.so
00e96000-00e98000 rw-p 00e96000 00:00 0
00ebf000-00fea000 r-xp 00000000 00:26 174100243  /usr/lib/perl5/5.8.8/i386-linux-thread-multi/CORE/libperl.so
00fea000-00fef000 rw-p 0012a000 00:26 174100243  /usr/lib/perl5/5.8.8/i386-linux-thread-multi/CORE/libperl.so
00fef000-00ff1000 rw-p 00fef000 00:00 0
08048000-08055000 r-xp 00000000 00:26 157302894  /usr/local/bin/ices
08055000-08056000 rw-p 0000d000 00:26 157302894  /usr/local/bin/ices
08056000-0810c000 rw-p 08056000 00:00 0
09893000-09b0b000 rw-p 09893000 00:00 0          [heap]
b7d1a000-b7e1e000 rw-p b7d1a000 00:00 0
b7ea0000-b7ec1000 rw-p b7ea0000 00:00 0
b7ec1000-b7efc000 r--p 00000000 00:26 36622587   /usr/lib/locale/en_US.utf8/LC_CTYPE
b7efc000-b7efd000 r--p 00000000 00:26 36622639   /usr/lib/locale/en_US.utf8/LC_NUMERIC
b7efd000-b7efe000 r--p 00000000 00:26 36623942   /usr/lib/locale/en_US.utf8/LC_TIME
b7efe000-b7fd5000 r--p 00000000 00:26 36622592   /usr/lib/locale/en_US.utf8/LC_COLLATE
b7fd5000-b7fd6000 r--p 00000000 00:26 36623941   /usr/lib/locale/en_US.utf8/LC_MONETARY
b7fd6000-b7fd7000 r--p 00000000 00:26 36622735   /usr/lib/locale/en_US.utf8/LC_MESSAGES/SYS_LC_MESSAGES
b7fd7000-b7fd8000 r--p 00000000 00:26 36623713   /usr/lib/locale/en_US.utf8/LC_PAPER
b7fd8000-b7fd9000 r--p 00000000 00:26 36623399   /usr/lib/locale/en_US.utf8/LC_NAME
b7fd9000-b7fe0000 r--s 00000000 00:26 139657355  /usr/lib/gconv/gconv-modules.cache
b7fe0000-b7fe5000 rw-p b7fe0000 00:00 0
b7fe5000-b7fe6000 r--p 00000000 00:26 36623939   /usr/lib/locale/en_US.utf8/LC_ADDRESS
b7fe6000-b7fe7000 r--p 00000000 00:26 36624033   /usr/lib/locale/en_US.utf8/LC_TELEPHONE
b7fe7000-b7fe8000 r--p 00000000 00:26 36624044   /usr/lib/locale/en_US.utf8/LC_MEASUREMENT
b7fe8000-b7fe9000 r--p 00000000 00:26 36623940   /usr/lib/locale/en_US.utf8/LC_IDENTIFICATION
b7fe9000-b7feb000 rw-p b7fe9000 00:00 0
bfa27000-bfa3c000 rw-p bffe9000 00:00 0          [stack]

Aborted



-- 
---------------------------------------
Raymond Lutz
Cognisys, Inc.
1010 Old Chase Ave., Bldg B
El Cajon (San Diego Cty), CA 92020 USA
Voice 619-447-3246
http//www.cognisys.com



From Thomas.Rucker at tieto.com  Tue Jun 28 06:01:18 2011
From: Thomas.Rucker at tieto.com (Thomas.Rucker at tieto.com)
Date: Tue, 28 Jun 2011 09:01:18 +0300
Subject: [Icecast] Multiple mount points without dynamic reencoding
In-Reply-To: <4E08F740.1020008@cognisys.com>
References: <4E08F740.1020008@cognisys.com>
Message-ID: <5E49EEF5B3B23549BAF01B43D0C2BB30170088D199@EXMB03.eu.tieto.com>

Hi,

I'll skip the ices0 part of the email as I don't know that software.
I only dealt with ices2 in that respect. So that is question
is left to be answered by someone else (though I'm not sure if it
will still apply).

And here we arrive also at the most likely source of an underlying
misconception:
You do not have to have the same codec for the files as for
the resulting stream! There are plenty source clients that will
happily take almost any file format and codec in and encode it into
a nice ogg/vorbis stream. (Random examples: mpd, rpld, liquidsoap,...)
Also today's CPUs will happily do that without consuming too many 
of their cycles.

It just happens to be a limitation of a few source clients that
do not allow for this (e.g. ices2) that is fuelling this misconception.

Also note that icecast and the shoutcast directory do not mix due
to the terms of service of the latter.

As to your question 32kbit at 44kHz vs 32kbit at 22kHz
Think of two pictures: 44100x16px and 22050x16px (which is 
only one half of the former) both run through a JPEG encoder at the 
same setting. Which one will look better?
It depends what you're after. Quality or spectral bandwith?
When in doubt, try it.

Cheers

Thomas

From raylutz at cognisys.com  Tue Jun 28 20:00:09 2011
From: raylutz at cognisys.com (Raymond Lutz)
Date: Tue, 28 Jun 2011 13:00:09 -0700
Subject: [Icecast] Multiple mount points without dynamic reencoding
In-Reply-To: <5E49EEF5B3B23549BAF01B43D0C2BB30170088D199@EXMB03.eu.tieto.com>
References: <4E08F740.1020008@cognisys.com>
	<5E49EEF5B3B23549BAF01B43D0C2BB30170088D199@EXMB03.eu.tieto.com>
Message-ID: <4E0A32C9.9060005@cognisys.com>

Thomas:

Thank you for your response. (I hope someone else will comment on how to 
deal with multiple source files without dynamic encoding, but the 
question may be moot if I can get dynamic encoding to work properly). It 
was some usefulness to write the response below, so I apologize for the 
length.

Perhaps you can correct/ my thinking here.

Reencoding from mp3 to ogg/vorbis will result in reduced fidelity, 
because both are lossy encoders and are both assuming they are starting 
with the original audio content, and it is well documented that 
reencoding mp3 to ogg-vorbis only reduces the ultimate fidelity. In my 
situation, we have mp3s coming from various sources, and their original 
encoding varies across the map,
but the most common is 64k/44.1.  So, we are re-encoding to that as our 
standard so that in some cases, no reencoding will be necessary and the 
original fidelity will be preserved.

(I find it is essential to have a continuous stream with the same format 
and changes from format to format will break the connection with some 
players, and some try to play the new  data at the old rate, etc. So the 
stream MUST be one encoding and data rate.)

It would be great if ices2 would be able to accept mp3 as input and 
perhaps reencode it to ogg/vorbis (although in my mind, that is a stupid 
thing to do, per the above argument). So my "interest" in mp3 continues, 
and the statement that no one is interested in mp3 is ridiculous.

With ices2, the documentation says about the configuration parameter 
"resample":

     <resample>
         <in-rate>44100</in-rate>
         <out-rate>22050</out-rate>
     </resample>

> When encoding or re-encoding, there is a point where you take PCM 
> audio and encode to Ogg Vorbis. In some situations a particular 
> encoded stream may require a lower samplerate to achieve a lower 
> bitrate. The resample will modifiy the audio data before it enters the 
> encoder, but does not affect other instances.
>
> The most common values used are 48000, 44100, 22050 and 11025, and is 
> really only used to resample to a lower samplerate, going to a higher 
> rate serves no purpose within IceS.
>

This implies that we have a PCM input stream of fixed format, and we can 
set this just once and be happy. This is not the case in my situation, 
because the mp3s are coming from various sources, with differing sample 
rates, and obviously are not PCM. Therefore, it appears that ices2 is 
not sufficient solution.

On your "source client" comment, I looked these over,
1. mpd is oriented to playing music and is not suitable for what I need 
to do. My application pulls in mp3 "podcasts" from various websites and 
queues these up for specific time slots during the day. mpd requires a 
playlist which I cannot provide since the content may change minutes 
before the timeslot arrives.

2. rpld (RoarAudio) -- looks interesting, but is a layer I'm not sure I 
need unless I need to interface with other sound input devices. I will 
have to research this more since it looks like a good building block, 
and may be a good solution for dynamic reencoding. (Of course, some of 
these may encounter the same runtime error as ices0.4).

3. liquidsoap -- looks very interesting, but also looks very new and 
unstable, and also looks like it is trying to do a lot more than I need 
right now, with a complete programming language to learn to boot. The 
good news is it looks like there is something going on here, unlike many 
audio projects that are largely defunct and abandoned. I see many 
outstanding issues before they get to version 1.0, with a stream of 
messages and difficulties implying that this might be a bottomless pit 
of time if I get started using it.
I'm not ready to take on the big project of adopting liquidsoap just to 
deal with this encoding issue.

As I see it, I still have the following options:

1. debug the runtime error that occurs when trying to use liblame to 
reencode mp3 using ices0.4. Not sure how long this will take or if I 
will be successful at determining what is wrong. This would be a nice 
solution but it still relies on the old version of ices.

2. Use a non-ices2 and non-ices0.4 source client that does support 
dynamic reencoding, so I can start from an arbitrary source format and 
produce a desired result format. From the list you suggested above, the 
choice is not clear. I looked over liquidsoap for about an hour and I 
still don't know how to use it to fill that need, and even if I worked 
on it for a week, I may not understand what is needed.

3. Figure out how to use ices2 or 0.4 to access multiple files at the 
same time, so that dynamic reencoding is not necessary.

3a. I am using mp3 now because but it is possible to produce ogg-vorbis 
using asynchronous reencoding (using ffmpeg), and then the question is 
the same -- if I have multiple sources, can ices2, for example, with 
ogg-vorbis input, run two sources simultaneously?

3b. If I continue to use ices0.4 because it supports mp3, then it may be 
possible to solve the problem by running multiple instances of ices and 
providing a different format mp3 to each, and connecting them to 
separate mount points on icecast.

BTW, I went through several versions of re-encoding packages before I 
was able to get ffmpeg to work correctly for my needs. I think it is too 
bad that ices dropped the ball and decided mp3 was irrelevant just 
because they have a vested interest in ogg/vorbis.

--Ray




On 6/27/2011 11:01 PM, Thomas.Rucker at tieto.com wrote:
> Hi,
>
> I'll skip the ices0 part of the email as I don't know that software.
> I only dealt with ices2 in that respect. So that is question
> is left to be answered by someone else (though I'm not sure if it
> will still apply).
>
> And here we arrive also at the most likely source of an underlying
> misconception:
> You do not have to have the same codec for the files as for
> the resulting stream! There are plenty source clients that will
> happily take almost any file format and codec in and encode it into
> a nice ogg/vorbis stream. (Random examples: mpd, rpld, liquidsoap,...)
> Also today's CPUs will happily do that without consuming too many
> of their cycles.
>
> It just happens to be a limitation of a few source clients that
> do not allow for this (e.g. ices2) that is fuelling this misconception.
>
> Also note that icecast and the shoutcast directory do not mix due
> to the terms of service of the latter.
>
> As to your question 32kbit at 44kHz vs 32kbit at 22kHz
> Think of two pictures: 44100x16px and 22050x16px (which is
> only one half of the former) both run through a JPEG encoder at the
> same setting. Which one will look better?
> It depends what you're after. Quality or spectral bandwith?
> When in doubt, try it.
>
> Cheers
>
> Thomas
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>

-- 
---------------------------------------
Raymond Lutz
Cognisys, Inc.
1010 Old Chase Ave., Bldg B
El Cajon (San Diego Cty), CA 92020 USA
Voice 619-447-3246
http//www.cognisys.com



From peter.lewis at worldcastinc.com  Sun Jun 26 13:51:19 2011
From: peter.lewis at worldcastinc.com (WCI Peter Lewis)
Date: Sun, 26 Jun 2011 13:51:19 -0000
Subject: [Icecast] OGG Theora streaming
Message-ID: <341CCC01FD5E46F5A6AABE0AFDE67156@WCRBACKUPPC>

Hi,

We are a online media company and are developing a new product that uses theora for video streaming. We used your free Visonair OGG streamer to test and it worked perfect . We would like to find out if your experts can help us complete our OGG streamer software. We are able to connect to icecast but the stream is unstable and buffers 90% of the time. We just need to get the streaming to the point where it is streaming smoothly with very little buffering .

Regards
Peter Lewis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20110626/6eedc6b6/attachment.htm>

From peter.lewis at worldcastinc.com  Sun Jun 26 17:22:51 2011
From: peter.lewis at worldcastinc.com (WCI Peter Lewis)
Date: Sun, 26 Jun 2011 17:22:51 -0000
Subject: [Icecast] [Video@Xiph] OGG Theora streaming
In-Reply-To: <BANLkTikSRmp0b-Uh6NN3+DuujoXjKjKnBA@mail.gmail.com>
References: <341CCC01FD5E46F5A6AABE0AFDE67156@WCRBACKUPPC>
	<BANLkTikSRmp0b-Uh6NN3+DuujoXjKjKnBA@mail.gmail.com>
Message-ID: <63286D47843F4DF38DDA0B66895B5499@WCRBACKUPPC>

Hi,

We are building our own custom streamer using your theora libraries. If we 
can get help to debug the solution and figure out why its not streaming 
smoothly that would be great. The end gold is to have a custom streamer for 
Windows and Mac that streams to icecast and can be viewed using HTML5. If 
you have any questions or need further details I would be happy to provide 
more details and thank you for the quick response .

Regards
Peter Lewis

-----Original Message----- 
From: Monty Montgomery
Sent: Sunday, June 26, 2011 11:28 AM
To: WCI Peter Lewis
Cc: icecast at xiph.org
Subject: Re: [Video at Xiph] OGG Theora streaming

>
> We are a online media company and are developing a new product that uses
> theora for video streaming. We used your free Visonair OGG streamer to 
> test
> and it worked perfect.

Visionair isn't ours (xiph's) directly. but it does use our libraries
somewhere to do the actual encoding stuff.  Layers upon layers :-)  I
know about it and have seen it used, but never worked directly with it
myself.  I'm not sure what others on the list have-- there's a good
chance (it looks nice).  You may need to contact the Visionair folks
for setup help.

That said, we do know Icecast and the actual Ogg streaming formats
very well.  We can help debug from that side.

(BTW, Ogg isn't an acronym, it's just "Ogg")

> We would like to find out if your experts can help
> us complete our OGG streamer software. We are able to connect to icecast 
> but
> the stream is unstable and buffers 90% of the time. We just need to get 
> the
> streaming to the point where it is streaming smoothly with very little
> buffering.

I don't know Visionair setup, but Icecast itself doesn't do much
buffering; it's just a 1->many server that passes whatever the source
hands it onto whatever client connects.  The exception is when
'burst-on-connect' is enabled, in which case it keeps around a small
buffer so that when a client connects, it can fill the client-side
buffer rapidly.  There's also a little bit of in-band fanciness to
start an Ogg stream properly in the middle.

Are you doing broadcast streaming, or low-latency conferencing, or...?

(BTW, I've trimmed the response list down to just icecast at xiph.org
since that's the most appropriate place for it to go).

Monty
Xiph.Org