I am using the latest build of Shoutcast DNAS 2 and am trying to get the sc_serv_basic.conf & sc_trans_basic.conf sc_trans_playlist.conf to work as they are suggested they will.
I have everything working and sounding great except that the jingles do not play at all, and I cannot login with SAM to broadcast live. By default the jingles are supposed to fire at 20 and 40 minutes past the hour yet they never play. I want to increase the frequency of the jingles playing to brand my stream more effectively, but need to get it working first before tackling that job. I'm hoping with your help I can get this working.
I was wondering if it will not play the jingles because I added xfade to the sc_trans_basic.conf file? Will the jingles play with xfade active? There is no errors that I can find so I am at a loss for an explanation.
Below are my files with the sensitive info redacted.
SC_SERV_BASIC.CONF
code:
; 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
; for testing we will make the server only work locally
; (i.e. localhost / 127.0.0.1) though if this is left out
; or set to publicserver=always then we attempt to make a
; connection to the YP for listing - do not forget to add
; in a 'streamauthhash' value for any public streams made
publicserver=always
; if you're wanting to use a different port to use for any
; connections then you can use this option e.g. to use 80
; otherwise port 8000 is used as the default to listen on.
;portbase=8000
; password used by sc_trans or the Winamp dsp plug-in
; NOTE: remember to change this to something else
password=********
; password used for accessing the administration pages
; NOTE: remember to change this to something else
adminpassword=********
; now we will specify the details of the stream we're going
; to serve which can be done as follows
;streamid=1
;streampath=/test.aac
; 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=/test.aac
;streamid_2=2
;streampath_2=/test2.aac
maxuser=100
autodumpusers=1
streamid_1=1
streampath_1=/NitrofishRadio.mp3
streamid_2=2
streampath_2=/NitrofishRadio2.mp3
SC_TRANS_BASIC.CONF
code:
; NOTE: for any relative paths specified are relative to
; sc_trans 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_trans will throw an error and will close itself down.
logfile=logs/sc_trans.log
; for the purpose of this test then we will not take into
; account the use of a calendar.xml file and so disable it
calendarrewrite=0
; for testing we will only setup a single encoder though it
; is easy to add in additional encoder configurations and
; we are using an aac plus encoder as the default due to
; the licensing requirements for mp3 encoding as detailed
; in sc_trans.txt - section 2.5).
encoder_1=mp3
bitrate_1=56000
; this is where we define the details required for sc_trans
; to connect to the sc_serv instance being used where the
; details must match those specified in sc_serv_basic.conf
outprotocol_1=3
serverip_1=***.***.***.**
; default is 8000, if not change to sc_serv's 'portbase'
serverport_1=8000
unlockkeyname=H**** B******
unlockkeycode=*****-*****-*****-*****
; this is the same as 'password' in sc_serv_basic.conf
password_1=********
; this is the same as 'streamid' in sc_serv_basic.conf for
; the stream we are acting as the source for
streamid_1=1
; this is a name for the source we're creating and is used
; with the AJAX control api or can be left blank to get a
; generic name created in the form of 'endpointX' where 'X'
; is the index of the created source from sc_trans lists.
endpointname_1=/Bob
; here you would provide any information to fill in details
; provided to clients about the stream. it us upto you what
; is entered though do not do anything which will annoy, etc
streamtitle=N******** Radio
streamurl=http://www.N********Radio.com
genre=Rock
; here we specify a playlist to use as the master list from
; which to play files from.
playlistfile=playlists/main.lst
; these options will allow you access the admin interfaces
; of sc_trans though also allows the 'testui' example to be
; accessed. remember to change the password, etc as needed
adminport=7999
adminuser=admin
adminpassword=*********
xfade=7
xfadethreshold=45
; if we want to have an intro file for when the client gets
; the stream or a backup file incase of our connection to
; the server failing then we can set these. this is needed
; as we are using 'outprotocol=3' which supports this (and
; is needed in place of the sc_serv defined values to work)
serverintrofile=jingles/Ident-1.mp3
;serverbackupfile=<specify_backup_filepath>
SC_TRANS_PLAYLIST.CONF
code:
; NOTE: for any relative paths specified are relative to
; sc_trans and not to where the conf file is being stored
; we use the sc_trans_basic.conf configuration file as the
; base configuration to work from for enabling DJ support
include=sc_trans_basic.conf
; this is needed otherwise sc_trans will not allow DJ joins
; to be allowed to connect to the sc_trans instance.
calendarfile=calendar/pl_calendar.xml
; here we setup sc_trans to know about the playlists we are
; going to be using as declared in the pl_calendar.xml file
; with two example playlists loaded to show different parts
;
; note: remember that the calendar file will use what has
; been set with the 'playlistfilename' entries - see
; sc_trans.txt - section 3.0.12 for more information
playlistfilename_1=jingles
playlistfilepath_1=playlists/jingles.lst
playlistfilename_2=main
playlistfilepath_2=playlists/main.lst
PL_CALENDAR.XML
code:
<?xml version="1.0" encoding="UTF-8" ?>
<eventlist>
<!-- if more playlists are required in the system then we just add in
more event blocks making sure to have entered a 'playlistfilename'
and 'playlistfilepath' entry into the sc_trans configuration file -->
<!-- this should activate the specified playlist at 18:00:00 (based on
the time of the machine sc_trans is running on) and keep playing
until 06:00:00 (as specified by the duration field from 18:00:00
and is applied only to weekdays
remember: playlist events are queued up so the transition is not
likely to happen until the currently playing file ends -->
<event type="playlist">
<playlist loopatend="1" shuffle="1" priority="1" >main</playlist>
<calendar starttime="18:00:00" duration="12:00:00" repeat="62" />
</event>
<!-- this should activate the specified playlist at 06:00:00 (based on
the time of the machine sc_trans is running on) and keep playing
it over the weekend until 06:00:00 on monday morning instead of the
main playlist as specified by 'playlistfile' in sc_trans_basic.conf
remember: playlist events are queued up so the transition is not
likely to happen until the currently playing file ends -->
<event type="playlist">
<playlist loopatend="1" shuffle="1" priority="1" >main</playlist>
<calendar starttime="06:00:00" duration="48:00:00" repeat="65" />
</event>
<!-- here we setup time periodic events which allow us to queue a jingle
type event to play approximately at 20 and 40 minutes past the hour
remember: playlist events are queued up so the transition is not
likely to happen until the currently playing file ends -->
<event type="playlist">
<playlist loopatend="0" shuffle="1" priority="2" >jingles</playlist>
<calendar starttime="00:00:00" timeoffset="00:20:00" repeat="128" />
</event>
<event type="playlist">
<playlist loopatend="0" shuffle="1" priority="2" >jingles</playlist>
<calendar starttime="00:00:00" timeoffset="00:40:00" repeat="128" />
</event>
</eventlist>
DJ_CALENDAR.XML
code:
<?xml version="1.0" encoding="UTF-8" ?>
<eventlist>
<!-- if more DJ's are required in the system
then we just add in more event blocks -->
<event type="dj">
<dj archive="1">dj</dj>
<!-- for this example we will allow the DJ
to connect to sc_trans at any time -->
<calendar />
</event>
</eventlist>
JINGLES.LST
code:
# This example playlist is used as the main playlist sc_trans will use to pick
# out the files it will use to create its output for the source we generate.
#
# Also remember to use the correct path format for the OS you are using and to
# ensure that the files you want to play are present in the location you choose
# e.g.
../jingles/ident-1.mp3
../jingles/indent_cutpower.mp3
../jingles/rtaw24-7.mp3
../jingles/you're listening to NFR.mp3
#
# In this example we will just assume that all of the files associated to the
# playlist are in one folder and all have an mp3 extension though there is no
# reason why you cannot explicitly specify files to use or to reference a tool.
# See sc_trans.txt - section 7.1 for more information on how playlists work.
# Remember to change this to reference the file you want to use for a jingle if
# using the sc_trans_playlist.conf example to setup a timed jingle system
Can anyone help me get these jingles going and maybe sort out the DJ issues please? I will submit logs if you need them just let me know which.
3rd May 2012, 18:34
Linear Mode
