| View previous topic :: View next topic |
| Author |
Message |
Anonymous
Guest
|
 Posted: Wed Jul 26, 2006 2:28 pm Post subject: Icy-metaint |
 |
|
Hi everyone.
The default data length between metadata (icy-metaint) is 16000, but I need to set this value to 8192. Anyone know where I can change it? I've looked everywhere, but I can't find it. |
|
| Back to top |
|
 |
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Wed Jul 26, 2006 4:16 pm Post subject: |
|
|
in the appropriate <mount> define
<mp3-metadata-interval>8192</mp3-metadata-interval>
karl. |
|
| Back to top |
|
|
Anonymous
Guest
|
| Posted: Thu Jul 27, 2006 8:40 am Post subject: |
|
|
| Thanks a lot |
|
| Back to top |
|
|
Anonymous
Guest
|
| Posted: Wed Aug 09, 2006 3:24 pm Post subject: metadata icy |
|
|
I've tried to insert the following tag in the config file:
<mp3-metadata-interval>8192</mp3-metadata-interval>
but it doesn't do anything, it still sends the metadata when the program wants. Any ideas?
Thanks in advance |
|
| Back to top |
|
|
Anonymous
Guest
|
| Posted: Thu Aug 10, 2006 9:31 am Post subject: |
|
|
| Sorry about my previus post, I've rewritten it in english |
|
| Back to top |
|
|
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Thu Aug 10, 2006 3:07 pm Post subject: |
|
|
you'll have to expand on what you are experiencing, for all we know, you've added it in a commented out section or maybe you have restarted the server/stream/listener etc you also haven't said what the log says about the metadata setting.
karl. |
|
| Back to top |
|
|
Anonymous
Guest
|
| Posted: Fri Aug 11, 2006 8:57 am Post subject: |
|
|
This is my config file:
| Code: |
<icecast>
<limits>
<clients>100</clients>
<sources>2</sources>
<threadpool>5</threadpool>
<queue-size>102400</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>testpass</source-password>
<!-- Relays log in username 'relay' -->
<relay-password>hackme</relay-password>
<!-- Admin logs in with the username given below -->
<admin-user>testuser</admin-user>
<admin-password>testpass</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>192.168.0.119</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>8000</port>
<shoutcast-compat>1</shoutcast-compat>
<shoutcast-mount>/test</shoutcast-mount>
<!-- <bind-address>127.0.0.1</bind-address> -->
</listen-socket>
<!--<master-server>127.0.0.1</master-server>-->
<!--<master-server-port>8001</master-server-port>-->
<!--<master-update-interval>120</master-update-interval>-->
<!--<master-password>hackme</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>-->
<!-- Only define a <mount> section if you want to use advanced options,
like alternative usernames or passwords-->
<mount>
<mount-name>/test</mount-name>
<password>testpass</password>
<bitrate>64</bitrate>
<type>application/mp3</type>
<subtype>mp3</subtype>
<hidden>1</hidden>
<burst-size>65536</burst-size>
<mp3-metadata-interval>8192</mp3-metadata-interval>
</mount>
<relay>
<server>192.168.0.119</server>
<port>8000</port>
<mount>/test</mount>
<on-demand>1</on-demand>
<relay-shoutcast-metadata>1</relay-shoutcast-metadata>
</relay>
<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>./</basedir>
<!-- Note that if <chroot> is turned on below, these paths must both
be relative to the new root, not the original root -->
<logdir>./logs</logdir>
<webroot>./web</webroot>
<adminroot>./admin</adminroot>
<!-- <pidfile>./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>
<!--
<changeowner>
<user>nobody</user>
<group>nogroup</group>
</changeowner>
-->
</security>
</icecast>
|
As you can see everithing seems fine, I don't get why it doesn't do as I wish. About the log, can you tell me where can I find the metadata things inside it? I don't understand what you are talking about. |
|
| 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
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
