View previous topic :: View next topic |
Author |
Message |
Anonymous Guest
|
Posted: Mon Mar 24, 2008 6:32 pm Post subject: I get a conntection, but no sound on my client |
|
|
Hi,
At first my aim:
I want the alsa audio stream from the server distributed oder my local network.
i ve installed the icecast server and ices and when i go on the page of the server i can download the ogg file an the timecounter goes on but i can't hear anything.
can somebody show how to configure the icecast and ices ?
thx
Code: |
<?xml version="1.0"?>
<ices>
<background>1</background> <!-- run in background? (unimplemented) -->
<logpath>/home/lordf/stream</logpath> <!-- where logs, etc go. -->
<logfile>ices.log</logfile>
<loglevel>3</loglevel> <!-- 1=error,2=warn,3=info,4=debug -->
<consolelog>1</consolelog>
<pidfile>/home/lordf/stream/ices.pid</pidfile>
<stream>
<metadata>
<name>ChoasWG_Radio</name>
<genre>ChaosMusik</genre>
<description>Bis der erste reiert</description>
</metadata>
<input>
<module>alsa</module>
<param name="rate">44100</param>
<param name="channels">2</param>
<param name="device">hw:0,0</param>
<param name="buffer-time">500</param>
<param name="metadata">1</param>
<param name="metadatafilename">/home/lordf/stream/trackinfo.txt</param>
</input>
<instance>
<hostname>t-laster</hostname>
<port>8010</port>
<password>passwort!</password>
<mount>/ChaosWGradio.ogg</mount> <!--[Hier wird der Mountpoint angegeben, auf den die Zuhörer später zugreifen]-->
<reconnectdelay>2</reconnectdelay>
<reconnectattempts>5</reconnectattempts>
<maxqueuelength>80</maxqueuelength>
<encode>
<nominal-bitrate>96000</nominal-bitrate>
<samplerate>44100</samplerate>
<channels>2</channels>
</encode>
</instance>
</stream>
</ices>
|
Code: |
<icecast>
<limits>
<clients>100</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>
<!-- If enabled, this will provide a burst of data when a client
first connects, thereby significantly reducing the startup
time for listeners that do substantial buffering. However,
it also significantly increases latency between the source
client and listening client. For low-latency setups, you
might want to disable this. -->
<burst-on-connect>1</burst-on-connect>
<!-- same as burst-on-connect, but this allows for being more
specific on how much to burst. Most people won't need to
change from the default 64k. Applies to all mountpoints -->
<burst-size>65535</burst-size>
</limits>
<authentication>
<!-- Sources log in with username 'source' -->
<source-password>passwort!</source-password>
<!-- Relays log in username 'relay' -->
<relay-password>passwort!</relay-password>
<!-- Admin logs in with the username given below -->
<admin-user>admin</admin-user>
<admin-password>passwort!</admin-password>
</authentication>
<!-- Uncomment this if you want directory listings -->
<!--
<directory>
<yp-url-timeout>15</yp-url-timeout>
<yp-url>http://dir.xiph.org/cgi-bin/yp-cgi</yp-url>
</directory>
<directory>
<yp-url-timeout>15</yp-url-timeout>
<yp-url>http://www.oddsock.org/cgi-bin/yp-cgi</yp-url>
</directory>
-->
<!-- This is the hostname other people will use to connect to your server.
It affects mainly the urls generated by Icecast for playlists and yp
listings. -->
<hostname>t-laster</hostname>
<!-- You can use these two if you only want a single listener -->
<!--<port>8000</port> -->
<!--<bind-address>127.0.0.1</bind-address>-->
<!-- You may have multiple <listener> elements -->
<listen-socket>
<port>8010</port>
<!-- <bind-address>127.0.0.1</bind-address> -->
</listen-socket>
<listen-socket>
<port>8009</port>
</listen-socket>
<!--
<listen-socket>
<port>8001</port>
</listen-socket>
-->
<master-server>127.0.0.1</master-server>
<master-server-port>8008</master-server-port>
<master-update-interval>120</master-update-interval>
<master-password>passwort!</master-password>
<!-- setting this makes all relays on-demand unless overridden, this is
useful for master relays which do not have <relay> definitions here.
The default is 0 -->
<!--<relays-on-demand>1</relays-on-demand>-->
<!--
<relay>
<server>127.0.0.1</server>
<port>8001</port>
<mount>/example.ogg</mount>
<local-mount>/different.ogg</local-mount>
<on-demand>0</on-demand>
<relay-shoutcast-metadata>0</relay-shoutcast-metadata>
</relay>
-->
<!-- Only define a <mount> section if you want to use advanced options,
like alternative usernames or passwords
<mount>
<mount-name>/example-complex.ogg</mount-name>
<username>othersource</username>
<password>hackmemore</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>/example_intro.ogg</intro>
<hidden>1</hidden>
<no-yp>1</no-yp>
<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>
<mount>
<mount-name>/auth_example.ogg</mount-name>
<authentication type="url">
<option name="mount_add" value="http://myauthserver.net/notify_mount.php"/>
<option name="mount_remove" value="http://myauthserver.net/notify_mount.php"/>
<option name="listener_add" value="http://myauthserver.net/notify_listener.php"/>
<option name="listener_remove" value="http://myauthserver.net/notify_listener.php"/>
</authentication>
</mount>
-->
<fileserve>1</fileserve>
<!-- set the mountpoint for a shoutcast source to use, the default if not
specified is /stream but you can change it here if an alternative is
wanted or an extension is required
<shoutcast-mount>/live.nsv</shoutcast-mount>
-->
<paths>
<!-- basedir is only used if chroot is enabled -->
<basedir>/usr/share/icecast</basedir>
<!-- Note that if <chroot> 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>/usr/share/icecast/icecast.pid</pidfile> -->
<!-- Aliases: treat requests for 'source' path as being for 'dest' path
May be made specific to a port or bound address using the "port"
and "bind-address" attributes.
-->
<!--
<alias source="/foo" dest="/bar"/>
-->
<!-- Aliases: can also be used for simple redirections as well,
this example will redirect all requests for http://server:port/ to
the status page
-->
<alias source="/" dest="/status.xsl"/>
</paths>
<logging>
<accesslog>access.log</accesslog>
<errorlog>error.log</errorlog>
<!-- <playlistlog>playlist.log</playlistlog> -->
<loglevel>4</loglevel> <!-- 4 Debug, 3 Info, 2 Warn, 1 Error -->
<logsize>10000</logsize> <!-- Max size of a logfile -->
<!-- If logarchive is enabled (1), then when logsize is reached
the logfile will be moved to [error|access|playlist].log.DATESTAMP,
otherwise it will be moved to [error|access|playlist].log.old.
Default is non-archive mode (i.e. overwrite)
-->
<!-- <logarchive>1</logarchive> -->
</logging>
<security>
<chroot>0</chroot>
<!--
Note from the packager:
For security reasons you should not run the icecast server as root.
SUSE adds a icecast user and group for this purpose.
If you change the user/group here you need to change the ownership
of the /var/log/icecast aswell
-->
<changeowner>
<user>lordf</user>
<group>users</group>
</changeowner>
</security>
</icecast>
|
|
|
Back to top |
|
|
karlH Code Warrior
Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Mon Mar 24, 2008 9:13 pm Post subject: |
|
|
Typically when a source client is taking input from dsp and the player is not playing any sound (although it's getting data) then that would tend to indicate the settings in the mixer. eg capturing Mic input when really you want mix or Line-in for instance.
karl. |
|
Back to top |
|
|
Anonymous Guest
|
Posted: Tue Mar 25, 2008 9:23 am Post subject: |
|
|
it is not the problem. I found out that the mic in signal is used for streaming signal.
Can somebody help me to change this into normal lineout signal.
thx |
|
Back to top |
|
|
karlH Code Warrior
Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Tue Mar 25, 2008 2:06 pm Post subject: |
|
|
The actual mixer setting will depend on the card/driver but from the list of possibilities you will see something like wave or mix which will have a capture option
karl. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2002 phpBB Group subRebel style by ktauber
|