| View previous topic :: View next topic |
| Author |
Message |
dards
Joined: 01 Mar 2011
Posts: 23
Location: Dubai
|
 Posted: Mon Jul 16, 2012 10:03 pm Post subject: Icecast KH33 - Metadata not working on shoutcast-mount |
 |
|
Dear all,
I have some weird issue on song metadata which is not showing if I customize the default /stream mount point for shoutcast-mount.
base on the documentation the default mount point of a shoutcast client icecast is /stream but this can be change by specifying any value on shoutcast-mount, please note that when i leave to default then metadata is showing without any problem, now i want it to change to other name instead of /stream, here is my setup
| Code: |
<port>8000</port>
<bind-address>localhost</bind-address>
<listen-socket>
<port>8000</port>
</listen-socket>
<listen-socket>
<port>8000</port>
<shoutcast-compat>1</shoutcast-compat>
<shoutcast-mount>/scmount</shoutcast-mount>
</listen-socket> |
so my defined mount point is /scmount
Did someone has this issue? and found any solution?
Thanks
dards |
|
| Back to top |
|
 |
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Tue Jul 17, 2012 12:19 am Post subject: |
|
|
incorrectly defined. In the 2.3.x style 2 port definition then you use shoutcast-compat but not shoutcast-mount within the listen-socket.
In the kh build, you can use shoutcast-mount within listen-socket but only on the first and it implicitly defines the subsequent port, so all you actually need is
| Code: |
<listen-socket>
<port>8000</port>
<shoutcast-mount>/scmount</shoutcast-mount>
</listen-socket>
|
BTW, there is very little use for setting bind-address to localhost.
karl. |
|
| Back to top |
|
|
dards
Joined: 01 Mar 2011
Posts: 23
Location: Dubai
|
| Posted: Tue Jul 17, 2012 5:00 am Post subject: Meta-data not working |
|
|
Thanks for the quick reply KarlH,
Sorry I put the wrong port number on the code, the second listen socket should be original port + 1 so it should be 8001 as required for shoutcast client encoder
| Code: |
<port>8000</port>
<bind-address>localhost</bind-address>
<listen-socket>
<port>8000</port>
</listen-socket>
<listen-socket>
<port>8001</port>
<shoutcast-compat>1</shoutcast-compat>
<shoutcast-mount>/scmount</shoutcast-mount>
</listen-socket> |
so on your suggestion is the shoutcast mount shout be define on the first port 8000 or on the second port 8001?
| Code: |
<listen-socket>
<port>8001</port>
<shoutcast-mount>/scmount</shoutcast-mount>
</listen-socket> |
and no need of shoutcast-compat tag
Thanks and regards,
dards |
|
| Back to top |
|
|
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Tue Jul 17, 2012 2:44 pm Post subject: |
|
|
On the first (so 8000), the second is implicitly defined. It allows for specifying multiple groups of 2 ports for different mountpoints fed by more than 1 source client at the same time.
karl. |
|
| Back to top |
|
|
dards
Joined: 01 Mar 2011
Posts: 23
Location: Dubai
|
| Posted: Wed Jul 18, 2012 2:18 pm Post subject: |
|
|
Hi KarlH,
Thanks, I also did that and when I run the icecast which that settings takes time and when started I cannot browse the icecast page.
here is my setup:
| Code: |
<port>8000</port>
<bind-address>localhost</bind-address>
<listen-socket>
<port>8000</port>
<shoutcast-mount>/scmount</shoutcast-mount>
</listen-socket>
|
I am using Icecast KH 2.3.2 KH33 linux version |
|
| Back to top |
|
|
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Fri Jul 20, 2012 11:49 pm Post subject: |
|
|
If you are trying to access the port from the LAN address then that behaviour would be expected as you have told icecast to only listen on localhost
karl. |
|
| Back to top |
|
|
dards
Joined: 01 Mar 2011
Posts: 23
Location: Dubai
|
| Posted: Sat Jul 21, 2012 5:42 am Post subject: mount point for shoutcast |
|
|
| karlH wrote: |
If you are trying to access the port from the LAN address then that behaviour would be expected as you have told icecast to only listen on localhost
karl. |
Hi KarlH,
Sorry to confused you, I just only use localhost as an example any way here is the actual address; http://184.107.191.197:8051/ its icecast kh 2.3.2 kh 33, and here is the configuration file, right now its working but there is not metadata or the song title is not showing
| Code: |
<icecast>
<limits>
<clients>250</clients>
<sources>3</sources>
<threadpool>5</threadpool>
<queue-size>102400</queue-size>
<client-timeout>30</client-timeout>
<header-timeout>15</header-timeout>
<source-timeout>10</source-timeout>
<burst-on-connect>1</burst-on-connect>
<burst-size>65535</burst-size>
</limits>
<authentication>
<source-password>password</source-password>
<relay-password>password</relay-password>
<admin-user>admin</admin-user>
<admin-password>password</admin-password>
</authentication>
<hostname>184.107.191.197</hostname>
<port>8051</port>
<bind-address>184.107.191.197</bind-address>
<listen-socket>
<port>8051</port>
</listen-socket>
<listen-socket>
<port>8052</port>
<shoutcast-compat>1</shoutcast-compat>
<shoutcast-mount>/autodj</shoutcast-mount>
</listen-socket>
<mount cc="main">
<mount-name>/stream</mount-name>
<intro></intro>
<fallback-mount>/live</fallback-mount>
<fallback-override>1</fallback-override>
<fallback-when-full>0</fallback-when-full>
<no-yp>1</no-yp>
</mount>
<mount cc="live">
<mount-name>/live</mount-name>
<intro></intro>
<fallback-mount>/autodj</fallback-mount>
<fallback-override>1</fallback-override>
<fallback-when-full>0</fallback-when-full>
<no-yp>1</no-yp>
</mount>
<mount cc="autodj">
<mount-name>/autodj</mount-name>
<bitrate>64</bitrate>
<intro></intro>
<fallback-mount></fallback-mount>
<fallback-override>1</fallback-override>
<fallback-when-full>0</fallback-when-full>
<no-yp>1</no-yp>
<charset>UTF-8</charset>
</mount>
<fileserve>1</fileserve>
<paths>
<basedir>/home/centovacast/vhosts/autodjstream/</basedir>
<logdir>var/log/</logdir>
<webroot>web/</webroot>
<adminroot>admin/</adminroot>
<pidfile>var/run/server.pid</pidfile>
<!--
<alias source="/foo" dest="/bar"/>
-->
<alias source="/" dest="/status.xsl"/>
</paths>
<logging>
<accesslog>access.log</accesslog>
<errorlog>error.log</errorlog>
<playlistlog>playlist.log</playlistlog>
<loglevel>1</loglevel>
</logging>
<security>
<chroot>0</chroot>
<!--
<changeowner>
<user>nobody</user>
<group>nogroup</group>
</changeowner>
-->
</security>
</icecast>
|
If I follow what you suggest to put the <shoutcast-compat>1</shoutcast-compat> on the first listen socket then the stream does not start
if I remove the <shoutcast-mount>/autodj</shoutcast-mount> then the mount point will become /stream and the metadata is working as normal
I also try different mount point name instead of /autodj thinking that maybe it does get conflict on the declared mount point but the same thing happened the mount point updated to the specified one but no metadata or song title is not showing.
thanks, |
|
| Back to top |
|
|
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Sat Jul 21, 2012 1:43 pm Post subject: |
|
|
no, delete the lines
| Quote: |
<port>8051</port>
<bind-address>184.107.191.197</bind-address>
<listen-socket>
<port>8051</port>
</listen-socket>
<listen-socket>
<port>8052</port>
<shoutcast-compat>1</shoutcast-compat>
<shoutcast-mount>/autodj</shoutcast-mount>
</listen-socket> |
and add
| Quote: |
<listen-socket>
<port>8051</port>
<shoutcast-mount>/autodj</shoutcast-mount>
</listen-socket
|
You can add bind-address in there if you wish, but unless you know that you need it then don't.
The shoutcast-compat is _only_ needed if you define the 2 ports separately
karl. |
|
| Back to top |
|
|
dards
Joined: 01 Mar 2011
Posts: 23
Location: Dubai
|
| Posted: Sat Jul 21, 2012 3:15 pm Post subject: shoutcast metadata issue |
|
|
Oh my Goodness!, just only that? and everything work just fine! it even solve my two year problem in centovacast, you know that whenever I have autoDJ stream SC_transV2 + Icecast KH I just write protect the configuration file because when I save the configuration from centovacast the port+1 settings on configuration file has been overwritten by centovacast and the stream will not work.
So this is my settings
| Code: |
<port>8051</port>
<bind-address>184.107.191.197</bind-address>
<listen-socket>
<port>8051</port>
</listen-socket>
<listen-socket>
<port>8052</port>
<shoutcast-compat>1</shoutcast-compat>
<shoutcast-mount>/autodj</shoutcast-mount>
</listen-socket> |
And when I save or update from centovacast control panel it will become like this, the port 8052 become all 8051 and the stream does not work
| Code: |
<port>8051</port>
<bind-address>184.107.191.197</bind-address>
<listen-socket>
<port>8051</port>
</listen-socket>
<listen-socket>
<port>8051</port>
<shoutcast-compat>1</shoutcast-compat>
<shoutcast-mount>/autodj</shoutcast-mount>
</listen-socket> |
So mostly I disabled and write protect the configuration file so that my manual configuration will not get overwritten by centovacast,
But because of your solution to eliminate those extra port settings this problem of mine in centovacast (Even the developer of centovacast cannot solve this issue) has been also solve including the auto DJ mount point.
You are life saver KarlH, please do you have any donation link for paypal, as I will repay you of what you did, or that paypal donation link on the Icecast KH download site is still working?
THANK YOU VERY MUCH!! |
|
| Back to top |
|
|
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Mon Jul 23, 2012 1:56 pm Post subject: |
|
|
I've never been quite sure how the centovacast system builds the xml files, I suspect they apply xsl translations to it which often breaks things like adding authentication. If you can disable the overwriting aspect and just use the portal for starting/stopping then great.
Beside simplifying the options used, it also allows for multiple blocks of 2 ports making it possible to use multiple shoutcast style source clients to be used at the same time. The traditional 2.3.2 style 2 listen-socket way can be used as well.
Just look on my www link for making any donations.
karl. |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
