Good shoutcast setup for Ubuntu 12.04 LTS 64bit?

[JohnnyBeGood]

Hi all,

 

 

I was asked by a friend to start a online radio station using shoutcast that will be fed by SAM Broadcaster.

This is for a really small community.

Right now I have a dedicated server with these specs:

Ubuntu 12.04 LTS 64bit

Intel i3

8GB Ram

2x1TB HDs

100/100 internet link

5TB Bandwith

Its not running anything other then couple of my personal websites.

I've tried to look for tutorial and the closest I've came across is this

Before I start, I was wondering is this the most up-to-date or there's something else?

 

 

TIA

[shoutcaststreaming]

That looks like a great tutorial. What's wrong with it ?

[Brutish Sailor]

for a server? Unless your running virtual desktop, Ubuntu remote frees up ALOT of resources. But you should know how to putty well before messing with that.

[Brutish Sailor]

OH WAIT!? your operating the server locally?

[JohnnyBeGood]

That looks like a great tutorial. What's wrong with it ?

Thanks for the reply!

 

I've tried to follow it but ran into issues and after searching the net i was able to start it without errors and start a test stream using SAM Broadcaster!

 

Couple of questions:

 

1. I added portbase=7777 to sc_serv_simple.conf

Once I start ./sc_serv

after that I choose 0

2013-09-06 07:19:00     I       msg:[CONFIG]  [0]  :  sc_serv_simple.conf

 

Why does it opens connection on port 7777 and 7778? what is 7778 for?

 

2013-09-06 07:19:02     I       msg:[MICROSERVER] Listening for connection on port 7777
2013-09-06 07:19:02     I       msg:[MICROSERVER] Listening for connection on port 7778

 

2. What are mount points?

[JohnnyBeGood]

for a server? Unless your running virtual desktop, Ubuntu remote frees up ALOT of resources. But you should know how to putty well before messing with that.

Yes, this is a remote server.

[djsoft]

Why does it opens connection on port 7777 and 7778? what is 7778 for?

This is for DJ access, so one DJ can kick in while another is broadcasting. If you're the only one who connects you don't need to use it...

[JohnnyBeGood]

This is for DJ access, so one DJ can kick in while another is broadcasting. If you're the only one who connects you don't need to use it...

Wait, that sounds interesting.

So one is sending stream to say 7777 and other can do what with 7778? merge those two? Can you please explain?

[djsoft]

I was wrong - the DJ feature exists in the sc_trans, not in sc_serv (but neither of them mix streams together IIRC).

[JohnnyBeGood]

I was wrong - the DJ feature exists in the sc_trans, not in sc_serv (but neither of them mix streams together IIRC).

Ok, so what's the purpose of other port?

[djsoft]

Ok, so what's the purpose of other port?

This is for legacy purposes - for Shoutcast v1 sources.

http://forums.winamp.com/showpost.php?p=2895826&postcount=2

[JohnnyBeGood]

This is for legacy purposes - for Shoutcast v1 sources.

http://forums.winamp.com/showpost.php?p=2895826&postcount=2

 

Thanks! makes sense.

 

Do you know anything about mount points?

[djsoft]

Do you know anything about mount points?

You can broadcast multiple streams using one Shoutcast v2 server instance.

 

In the Shoutcast config configure mount points:

streamid_1=1

streampath_1=/test.mp3

 

streamid_2=2

streampath_2=/test.aac

 

Then set up multiple encoders in your broadcasting app for each of the stream IDs you spedcified (1, 2, ...)

 

You'll be able to listen to your streams like this: http://your-ip:port/test.mp3

[JohnnyBeGood]

You can broadcast multiple streams using one Shoutcast v2 server instance.

 

In the Shoutcast config configure mount points:

streamid_1=1

streampath_1=/test.mp3

 

streamid_2=2

streampath_2=/test.aac

 

Then set up multiple encoders in your broadcasting app for each of the stream IDs you spedcified (1, 2, ...)

 

You'll be able to listen to your streams like this: http://your-ip:port/test.mp3

 

In SAM i can have multiple transcodes. So you're saying in other words I can mask them.

ie. http://your-ip:port/test.mp3 is 64 bit

http://your-ip:port/test.aac 96 bit

But in my transcoder I don't see where I can specify that.

 

2. Why does it ask me for user/pass in VLC as soon as I stop sending stream to shoutcast?

I feel like its not configured correctly.

 

 

 

 

Below is my sc_serv_simple.conf

 

; NOTE: for any relative paths specified are relative to
; sc_serv and not to where the conf file is being stored


; here we will setup where the log and other related files
; will be stored. make sure that these folders exist else
; sc_serv will throw an error and will close itself down.
; we will make the logs save to the sc_serv2 directory
logfile=logs/sc_serv.log
w3clog=logs/sc_w3c.log
banfile=control/sc_serv.ban
ripfile=control/sc_serv.rip




; the following will force any sources to be public which
; allows us to then connect and be listed on the YP
publicserver=never




; password used by sc_trans or the Winamp DSP plug-in
; NOTE: remember to change this to something else
password=MYPASS




; password used for accessing the administation pages
; NOTE: remember to change this to something else
adminpassword=MYOTHERPASS




; as we are going to connect to the YP then we need to fill
; in the required options so we can authenticate to the YP2
; see sc_serv.txt - section 3.0 for details on getting this
;
; make sure that you completely replace the string
;  with the authorisation key you
; obtained when registering the stream for the SHOUTcast YP
; e.g. if you auth hash key is 12345 then the line would be
;      streamauthhash=12345
streamauthhash_1=xxxxxxxxxxxxxxxxxx


portbase=7777


; now we will specify the details of the stream we're going
; to serve which can be done as follows
streamid=1
streampath=/radio


; or


; it can be done like this which is how it needs to be done
; if you are going to provide multiple streams from sc_serv
;streamid_1=1
;streampath_1=/radio.mp3
;streamid_2=2
;streampath_2=/radio.aac

[djsoft]

You'll need to remove

 

streamid=1

streampath=/radio

 

from the config and add

 

streamid_1=1

streampath_1=/test.mp3

streamid_2=2

streampath_2=/test.aac

 

instead. Change paths according to your broadcast and format.

 

Then add 2 encoders and configure them to use those stream IDs. Software has to support Shoutcast 2 for this to work.

[JohnnyBeGood]

You'll need to remove

 

streamid=1

streampath=/radio

 

from the config and add

 

streamid_1=1

streampath_1=/test.mp3

streamid_2=2

streampath_2=/test.aac

 

instead. Change paths according to your broadcast and format.

 

Then add 2 encoders and configure them to use those stream IDs. Software has to support Shoutcast 2 for this to work.

Ok, I will make that change.

So what would be proper way to send direct links to friends to check it out or post online?

http://your-ip:port/test.mp3 ?

[djsoft]

Ok, I will make that change.

So what would be proper way to send direct links to friends to check it out or post online?

http://your-ip:port/test.mp3 ?

Yes. Also http://your-ip:port/test.aac will work if you use the config lines I've posted.

In general, the link is built like this: http://your-ip:port/path - where path is the streampath (or streampath_N) setting in your config.

[JohnnyBeGood]

Yes. Also http://your-ip:port/test.aac will work if you use the config lines I've posted.

In general, the link is built like this: http://your-ip:port/path - where path is the streampath (or streampath_N) setting in your config.

I've switched to shoutcast v1 and kicking user works.

As far as I know there's no streampath's in v1?

What would be proper link in v1?

[djsoft]

Yes, there's no streampath. For v1 the link is simple:

http://your-ip:port