Mount Question

Steamcast is a stand alone server that combines the features of SHOUTcast and Icecast2 and more to make one mega awesome server.
Post Reply
User avatar
themixturemedia
Posts: 137
Joined: Fri Dec 10, 2004 2:42 pm
Location: Canada
Contact:

Mount Question

Post by themixturemedia »

Hey there Jay I am have been trying for days to get two mounts on Steamcast to get rid of the Icecast server and I keep getting a Source Login Invalid when I try to get the 2nd mount to work. Also I have try what you said in the last post and if I try to get the details to work the whats playing does not work and vice vursa and thoughts?

Thanks
Clash

; Source Configuration
; ====================
; Each source that you wish to allow on the server needs to be configured
; here first. The parser will read strait down the file so if you have
; multiple source mounts and you declare a new mount before finishing
; configuration of another, then those configurations after the new
; declaration will go to the new mount.

; SourceMount: This is the mount you would like to create, if you set
; this to /ghey.mp3 then you would be able to access this mount by
; going to http://localhost:8000/ghey.mp3 It is critical that you
; make sure to include the slash at the beginning.
SourceMount=/live.ogg
SourceMount=/live.mp3

; SourceBackup: This is the mount you would like listeners directed to in the
; event that this source becomes unavailable. These two mounts must be completely
; identical bitstreams in order for this feature to work properly. This includes
; MetaData in the event that you relay from multiple servers!
; SourceBackup=/live_back.mp3

; SourceUser: The last SourceMount declared will require this Username
; in order to become a source for this mount. Note: if you are running
; this mount in shoutcast compatibility mode, this is not required. However
; it's best to set this anyhow as it allows your encoder users to administrate
; their mounts from a CNTRL app or web panel.
SourceUser=
SourceUser=

; SourcePass: This is the last Source Mount's password, this is required
; for all connecting encoders. Mounts without passwords are invalid.
SourcePass=
SourcePass=

; SourceUserMax [*5]: This particular mount's UserMax, if all of your source
; UserMaxes combined exceed the global UserMax then the UserMax takes presedence.
SourceUserMax=30
SourceUserMax=30

; SourceRelay: This particular mount will pull data from the location specified below.
; If you publish both servers on yp.shoutcast.com and wish that they cluster at that
; yp server then enter your relay url without http:// or trailing path or slashes
; like the example below.
; SourceRelay=audio.str3am.com:4080

; SourceBitrateLimit: Set this to have Steamcast kick sources that exceed a
; certain average data rate. This value is based on actual data transfer and not any particular
; format headers. This is a great way to control users in community or hosting
; environments. Default is no limits. Be careful with this, sometimes there can be
; transfer spikes that can set this off.
; SourceAvgBitrateLimit=128

; SourceIsSC [*Yes|No]: Setting this to Yes will allow source applications
; which do not have a username capability to use the last source
; declared anyway.
SourceIsSC=Yes

; SourceIsDefault [*Yes|No]: Setting this to Yes will make this particular
; mount available globally. There can be only one global mount. This
; is also the only mount that will be able to list at shoutcast.com
SourceIsDefault=Yes

; SourceIP: Setting this to a dotted IP address will make this particular
; mount available at the root of steamcast (much like SHOUTcast) for the IP
; specified here. Note: You must own the IP you place here. Inaccurate
; settings will have no effect. This setting essentially will allow you to
; list multiple source points in the SHOUTcast directory. It is not neccessary
; to set this setting if you only own one IP. Setting this for any Source will
; disable the SourceIsDefault flag on any mount.
; SourceIP=192.168.0.1


; SourceAuth: [Yes|*No]: Allows you to setup HTTP Basic Authorization on this
; mount point. All Authentication is currently file based. Please see steamauth.txt
; SourceAuth overrides the public bit and will force all SourceAuth'd streams to be
; private.
; SourceAuth=No

; SourceAuthMax: [*0]: Allows you to set the maximum amount of connections per authenticated
; user. A setting of 0 is interpreted as unlimited.
; SourceAuthMax=0

; SourceBuffUtil [*100]: This value allows you to control the start position
; of connecting clients within the buffer. 0 would effectively set a new connecting
; client to the write point of the buffer giving a more real-time like experience
; although due to the way the internet really works it can never be truely real-time.
; Setting this to 100 would start them all the way at the back of the buffer which
; gives most clients no buffer wait times. It is highly recommended that you not mess
; with this parameter except in instances where the bitrate of the stream is extremely
; low and you require an interactive experience from the users connected to the server.
; (i.e. A talk show or other low bitrate interactive live program) Most other broadcasts
; SHOULD NOT CHANGE THIS SETTING!!! Doing so will make the connecting users feel like
; they are on dialup in 1996 listening to Real Player. :)
; SourceBuffUtil=100
The Mixture Media Radio: :twisted:
The best on-line music from the 60's,70's,80's,90's and today. Streaming at 64kbps/48khz (MP3) and 32kbps/44khz (Ogg) 24 hours a day 7 days a week. With great sound and even better music.
User avatar
Jay
Will work for food (Administrator)
Posts: 3020
Joined: Mon Jan 14, 2002 12:48 am
Location: Next Door
Contact:

Post by Jay »

you configured it wrong, don't double up entries in the configuration file like that, steamcast reads the configuration file from top to bottom and with your config as you have it you are basically setting up 2 sources with the first one not having any configuration.

Read the docs on how to properly setup multiple mount points:
http://www.radiotoolbox.com/docs/index. ... 4&doc_id=4

They are configured in blocks with the SourceMount denoting the beginning of a block.
- Jay
Lane
Posts: 154
Joined: Mon May 09, 2005 4:16 pm

Post by Lane »

I know other people that did the same thing. I wonder if there's a way to make it more obvious that the source mounts should be grouped in blocks? Maybe include another block right after, but commented out with a statement again that extra mounts must be group starting with SourceMount etc. Just a thought.
User avatar
Jay
Will work for food (Administrator)
Posts: 3020
Joined: Mon Jan 14, 2002 12:48 am
Location: Next Door
Contact:

Post by Jay »

yes I may include an example of a second mount in the included configuration file.
- Jay
User avatar
themixturemedia
Posts: 137
Joined: Fri Dec 10, 2004 2:42 pm
Location: Canada
Contact:

hmmm....

Post by themixturemedia »

Hey there is there anyway at all for anyone at all to give a detailed description of what it is spose to look like please?
The Mixture Media Radio: :twisted:
The best on-line music from the 60's,70's,80's,90's and today. Streaming at 64kbps/48khz (MP3) and 32kbps/44khz (Ogg) 24 hours a day 7 days a week. With great sound and even better music.
Lane
Posts: 154
Joined: Mon May 09, 2005 4:16 pm

Post by Lane »

the configuration file?

All the items that start with Source should be grouped together, starting with SourceMount=. Every time it sees SourceMount, it starts a new mount, and everything after it starting with Source will apply to it (right up until it sees another SourceMount). There is a simple example in the documentation if you want to refer to it on this page > http://www.radiotoolbox.com/docs/index. ... 4&doc_id=4 Scroll down to "Multiple Source Configuration Examples:"
User avatar
themixturemedia
Posts: 137
Joined: Fri Dec 10, 2004 2:42 pm
Location: Canada
Contact:

:-(

Post by themixturemedia »

Can you please give an example using this it is alot easier to see what you are spose to do via the config file.

; Source Configuration
; ====================
; Each source that you wish to allow on the server needs to be configured
; here first. The parser will read strait down the file so if you have
; multiple source mounts and you declare a new mount before finishing
; configuration of another, then those configurations after the new
; declaration will go to the new mount.

; SourceMount: This is the mount you would like to create, if you set
; this to /ghey.mp3 then you would be able to access this mount by
; going to http://localhost:8000/ghey.mp3 It is critical that you
; make sure to include the slash at the beginning.
SourceMount=/live.ogg
SourceMount=/live.mp3

; SourceBackup: This is the mount you would like listeners directed to in the
; event that this source becomes unavailable. These two mounts must be completely
; identical bitstreams in order for this feature to work properly. This includes
; MetaData in the event that you relay from multiple servers!
; SourceBackup=/live_back.mp3

; SourceUser: The last SourceMount declared will require this Username
; in order to become a source for this mount. Note: if you are running
; this mount in shoutcast compatibility mode, this is not required. However
; it's best to set this anyhow as it allows your encoder users to administrate
; their mounts from a CNTRL app or web panel.
SourceUser=
SourceUser=

; SourcePass: This is the last Source Mount's password, this is required
; for all connecting encoders. Mounts without passwords are invalid.
SourcePass=
SourcePass=

; SourceUserMax [*5]: This particular mount's UserMax, if all of your source
; UserMaxes combined exceed the global UserMax then the UserMax takes presedence.
SourceUserMax=30
SourceUserMax=30

; SourceRelay: This particular mount will pull data from the location specified below.
; If you publish both servers on yp.shoutcast.com and wish that they cluster at that
; yp server then enter your relay url without http:// or trailing path or slashes
; like the example below.
; SourceRelay=audio.str3am.com:4080

; SourceBitrateLimit: Set this to have Steamcast kick sources that exceed a
; certain average data rate. This value is based on actual data transfer and not any particular
; format headers. This is a great way to control users in community or hosting
; environments. Default is no limits. Be careful with this, sometimes there can be
; transfer spikes that can set this off.
; SourceAvgBitrateLimit=128

; SourceIsSC [*Yes|No]: Setting this to Yes will allow source applications
; which do not have a username capability to use the last source
; declared anyway.
SourceIsSC=Yes

; SourceIsDefault [*Yes|No]: Setting this to Yes will make this particular
; mount available globally. There can be only one global mount. This
; is also the only mount that will be able to list at shoutcast.com
SourceIsDefault=Yes

; SourceIP: Setting this to a dotted IP address will make this particular
; mount available at the root of steamcast (much like SHOUTcast) for the IP
; specified here. Note: You must own the IP you place here. Inaccurate
; settings will have no effect. This setting essentially will allow you to
; list multiple source points in the SHOUTcast directory. It is not neccessary
; to set this setting if you only own one IP. Setting this for any Source will
; disable the SourceIsDefault flag on any mount.
; SourceIP=192.168.0.1


; SourceAuth: [Yes|*No]: Allows you to setup HTTP Basic Authorization on this
; mount point. All Authentication is currently file based. Please see steamauth.txt
; SourceAuth overrides the public bit and will force all SourceAuth'd streams to be
; private.
; SourceAuth=No

; SourceAuthMax: [*0]: Allows you to set the maximum amount of connections per authenticated
; user. A setting of 0 is interpreted as unlimited.
; SourceAuthMax=0

; SourceBuffUtil [*100]: This value allows you to control the start position
; of connecting clients within the buffer. 0 would effectively set a new connecting
; client to the write point of the buffer giving a more real-time like experience
; although due to the way the internet really works it can never be truely real-time.
; Setting this to 100 would start them all the way at the back of the buffer which
; gives most clients no buffer wait times. It is highly recommended that you not mess
; with this parameter except in instances where the bitrate of the stream is extremely
; low and you require an interactive experience from the users connected to the server.
; (i.e. A talk show or other low bitrate interactive live program) Most other broadcasts
; SHOULD NOT CHANGE THIS SETTING!!! Doing so will make the connecting users feel like
; they are on dialup in 1996 listening to Real Player. Smile
; SourceBuffUtil=100
The Mixture Media Radio: :twisted:
The best on-line music from the 60's,70's,80's,90's and today. Streaming at 64kbps/48khz (MP3) and 32kbps/44khz (Ogg) 24 hours a day 7 days a week. With great sound and even better music.
User avatar
Jay
Will work for food (Administrator)
Posts: 3020
Joined: Mon Jan 14, 2002 12:48 am
Location: Next Door
Contact:

Post by Jay »

as has been said there is an example on the doc page.

The config you posted above is wrong.
- Jay
Post Reply