| View previous topic :: View next topic |
| Author |
Message |
Anonymous
Guest
|
 Posted: Wed Apr 09, 2008 12:47 pm Post subject: intro not working |
 |
|
Hi,
I'm trying to set up multiple DJ's and have an intro on listeners connecting, I seem to have managed to get the fallback working although there are still some issues with it but I've not managed to get an intro.mp3 to play at all.
This is what I've got set in the mount point section -
<mount>
<mount-name>/dj1.mp3</mount-name>
<max-listeners>1999</max-listeners>
<burst-size>65536</burst-size>
<fallback-mount>/dj2.mp3</fallback-mount>
<fallback-override>1</fallback-override>
<fallback-when-full>1</fallback-when-full>
<intro>/etc/icecast2/web/intro.mp3</intro>
<hidden>1</hidden>
<no-yp>1</no-yp>
</mount>
<mount>
<mount-name>/dj2.mp3</mount-name>
<max-listeners>1999</max-listeners>
<burst-size>65536</burst-size>
<fallback-mount>/etc/icecast2/web/premade.mp3</fallback-mount>
<fallback-override>1</fallback-override>
<fallback-when-full>1</fallback-when-full>
<intro>/etc/icecast2/web/intro.mp3</intro>
<hidden>1</hidden>
<no-yp>1</no-yp>
</mount>
I've checked permissions on the intro.mp3 and it seems to be ok and chown'ed to the same as everything else but I figure I'm doing something wrong and can't work out what it is. Any suggestions greatly appreciated
Thanks |
|
| Back to top |
|
 |
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Wed Apr 09, 2008 12:54 pm Post subject: |
|
|
If the intro file is not accessible by icecast then iceast will log it as an error in the error log, are you saying no error exists? Are you sure that the setting you have specified exists within the webroot directory?
karl. |
|
| Back to top |
|
|
DjQuick
Joined: 15 Aug 2008
Posts: 4
|
| Posted: Fri Aug 15, 2008 4:46 am Post subject: How would I.... |
|
|
karl,
You posted to another message mine on another forum, and thought I would browse these to see if I could find the information you were speaking of.
BEHOLD - PAYDIRT!
Now, for the MILLION dollar question  - How can I manage this config in CentovaCast (IceCast) Cpanel? Any thoughts/clues... If necessary, I can profide some screenshots.
Dj Quick
_________________
Dj Quick - CFXRNetRadio.com |
|
| Back to top |
|
|
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Fri Aug 15, 2008 11:16 am Post subject: |
|
|
I don't know about cpanel personally. If it's configurable then intro files are just a text entry (a path) which is appended to webroot. You would want any intro on the mount that listeners connect to, even if that is a local relay.
karl. |
|
| Back to top |
|
|
DjQuick
Joined: 15 Aug 2008
Posts: 4
|
| Posted: Fri Aug 15, 2008 3:19 pm Post subject: |
|
|
| karlH wrote: |
I don't know about cpanel personally. If it's configurable then intro files are just a text entry (a path) which is appended to webroot. You would want any intro on the mount that listeners connect to, even if that is a local relay.
karl. |
Karl,
Please see the server conf below... We are using CentovaCAST as the control panel, and there has to be a way to make this work the way we want it to. I tried messing around with this file on a test server, but it eneded up barfing.
Unfortunately, I am not as well versed as some when it comes to making "AD-HOC" changes to the conf file. We have always just dealt with what we have. But, since we own/maintain the server(s), why not make them work to our advantage, correct?
---- server conf ----
<icecast>
<limits>
<clients>60</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>dim164k</source-password>
<!-- Relays log in username 'relay' -->
<relay-password></relay-password>
<!-- Admin logs in with the username given below -->
<admin-user>admin</admin-user>
<admin-password>Atch8925</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>
-->
<!-- {%comment-open-if:icecast.directory.yp-url==""%} --> <!--
<directory>
<yp-url-timeout>15</yp-url-timeout>
<yp-url>http://www.oddsock.org/cgi-bin/yp-cgi</yp-url>
</directory>
--> <!-- {%comment-close-if:icecast.directory.yp-url==""%} -->
<!-- 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>eclipsenightclub.net</hostname>
<!-- You can use these two if you only want a single listener -->
<port>9100</port>
<bind-address>74.52.8.138</bind-address>
<!-- You may have multiple <listener> elements -->
<!--
<listen-socket>
<port>8050</port>
<bind-address>192.168.0.10</bind-address>
</listen-socket>
-->
<!--
<listen-socket>
<port>8001</port>
</listen-socket>
-->
<!-- {%comment-open-if:icecast.masterserver==""%} --> <!--
<master-server>127.0.0.1</master-server>
<master-server-port>8001</master-server-port>
<master-update-interval>120</master-update-interval>
<master-password>password</master-password>
--> <!-- {%comment-close-if:icecast.masterserver==""%} -->
<!-- {%comment-open-if:icecast.relay.server==""%} --> <!--
<relay>
<server>127.0.0.1</server>
<port>8001</port>
<mount>/example.ogg</mount>
<local-mount>/different.ogg</local-mount>
<relay-shoutcast-metadata>0</relay-shoutcast-metadata>
</relay>
--> <!-- {%comment-close-if:icecast.relay.server==""%} -->
<!-- Only define a <mount> section if you want to use advanced options,
like alternative usernames or passwords -->
<mount>
<mount-name>/stream</mount-name>
<intro>/home/eatchiso/centovacast/vhosts/dim1/var/spool/sounds/introfile.mp3</intro>
<fallback-mount>/home/eatchiso/centovacast/vhosts/dim1/var/spool/sounds/fallbackfile.mp3</fallback-mount>
<fallback-override>1</fallback-override>
<fallback-when-full>0</fallback-when-full>
<no-yp>1</no-yp>
</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>/home/eatchiso/centovacast/vhosts/dim1/</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/</logdir>
<webroot>web/</webroot>
<adminroot>admin/</adminroot>
<pidfile>var/run/server.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 -->
</logging>
<security>
<chroot>0</chroot>
<!--
<changeowner>
<user>nobody</user>
<group>nogroup</group>
</changeowner>
-->
</security>
</icecast>
---- END ----
If you could provide any pointers of an easy way we could utilize a similar config to the one above, it would greatly be appreciated. I am sure some of this garbage could be cleaned up, but not sure what we can do without, or what is safe to delete.
As an FYI, I can't seem to get the INTRO or FALLBACK file to work (AT ALL). Both files are encoded the at the same rate as the streams would be (64k, 22.1kHz).
Any thoughts or guidance you may be able to provide would be greatly appreciated.
_________________
Dj Quick - CFXRNetRadio.com |
|
| Back to top |
|
|
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Fri Aug 15, 2008 3:51 pm Post subject: |
|
|
I'm assuming you are streaming on /stream and the intro and fallback are not working. From what I can see it looks like you are assuming absolute paths from the root of the filesystem which is incorrect. webroot and fallback-mount (when used as a file) are appended to webroot so I'm guessing the error log is reporting that the intro file cannot be found at
web/home/eatchiso/centovacast/vhosts/dim1/var/spool/sounds/fallbackfile.mp3
maybe you actually want to set logdir and webroot to /home/..... ?
karl. |
|
| Back to top |
|
|
DjQuick
Joined: 15 Aug 2008
Posts: 4
|
| Posted: Fri Aug 15, 2008 3:58 pm Post subject: |
|
|
I can try that...
Any suggestions on the rest of the config?
_________________
Dj Quick - CFXRNetRadio.com |
|
| Back to top |
|
|
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Fri Aug 15, 2008 6:03 pm Post subject: |
|
|
well a lot of it is comments ie <-- ignored --> but you should increase the queue-size from 100k, we ship with 512k
karl. |
|
| Back to top |
|
|
DjQuick
Joined: 15 Aug 2008
Posts: 4
|
| Posted: Fri Aug 15, 2008 8:24 pm Post subject: |
|
|
Well, I am not sure how helpful that answer actually was, but I appreciate your time either way. I suppose I am back to the drawing board of trying to figure this mess out. 
Thanks again...
_________________
Dj Quick - CFXRNetRadio.com |
|
| Back to top |
|
|
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Fri Aug 15, 2008 9:50 pm Post subject: |
|
|
It means, if you take out all the stuff from <!-- to --> then you won't have much on an xml left. The <queue-size> of 100k is probably a leftover from an earlier release as the last few releases have had 500k in the xml files we ship. As a general rule, don't specify things unless you know what they are, even the bind-address is probably not what you want.
karl. |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
