Shoutcast Disconnection, Ls_script
  • Vote Up0Vote Down Tom MeatTom Meat
    Posts: 2Member
    I have recently upgraded from version 2.0.3 to 2.3.1 running ubuntu 10.04 32bit and Shoutcast Dnas v2.0.0.29.
    The ls_script was modified to play mp3s from a folder on silence using the following:

    #default = amplify(0.00001, noise())
    #default = rewrite_metadata([("artist","Airtime"), ("title", "offline")],default)
    default = playlist(mode='random', "/MusicPath/")
    s = fallback(track_sensitive=false, [queue, default])

    s = on_metadata(notify, s)
    s = crossfade(s)

    I have read some posts and have added the following to the new ls_script, which is not playing anything (not sure if the old code will work, or where to put it?):

    #default = playlist(mode='random',"Music/Path")
    default = amplify(id="silence_src", 0.00001, noise())
    ref_off_air_meta = ref off_air_meta
    if !ref_off_air_meta == "" then
        ref_off_air_meta := "Airtime - offline"
    end
    default = rewrite_metadata([("title", !ref_off_air_meta)], default)
    #default = playlist(mode='random', "/Music/Path")
    ignore(output.dummy(default, fallible=true))
    default = playlist(mode='random',"/Music/Path")

    service airtime-playout restart does not make a difference.

    If I do service airtime-liquidsoap restart it causes the connection to drop from shoutcast, even though Airtime thinks it is still connected. 
    Airtime seems to be fine:

    AIRTIME_SERVER_RESPONDING      = OK
    KERNEL_VERSION                 = 3.2.13-grsec-xxxx-grs-ipv6-32
    MACHINE_ARCHITECTURE           = i686
    TOTAL_MEMORY_MBYTES            = 2046900
    TOTAL_SWAP_MBYTES              = UNKNOWN
    AIRTIME_VERSION                = 2.3.1
    OS                             = Ubuntu 10.04.4 LTS i686
    CPU                            = Intel(R) Atom(TM) CPU D425   @ 1.80GHz
    WEB_SERVER                     = Apache/2.2.14 (Ubuntu)
    PLAYOUT_ENGINE_PROCESS_ID      = 23500
    PLAYOUT_ENGINE_RUNNING_SECONDS = 1122
    PLAYOUT_ENGINE_MEM_PERC        = 0.8%
    PLAYOUT_ENGINE_CPU_PERC        = 1.9%
    LIQUIDSOAP_PROCESS_ID          = 22497
    LIQUIDSOAP_RUNNING_SECONDS     = 1235
    LIQUIDSOAP_MEM_PERC            = 0.5%
    LIQUIDSOAP_CPU_PERC            = 25.4%
    MEDIA_MONITOR_PROCESS_ID       = 3237
    MEDIA_MONITOR_RUNNING_SECONDS  = 3234
    MEDIA_MONITOR_MEM_PERC         = 0.5%
    MEDIA_MONITOR_CPU_PERC         = 1.4%
    -- Your installation of Airtime looks OK!

    Hope someone can help.

    Thanks





  • 3 Comments sorted by
  • Vote Up0Vote Down Albert FRAlbert FR
    Posts: 1,978Member, Airtime Moderator
    comment this line and retry :

    default = amplify(id="silence_src", 0.00001, noise())

    ----
    Je peux le faire ;) [Pour vous] / I can do it [For You] Gnu/Linux & Media Architect
    Co-founder NessRadio.com
  • Vote Up0Vote Down Tom MeatTom Meat
    Posts: 2Member
    I added comment to this line
    default = amplify(id="silence_src", 0.00001, noise())

    and done service airtime-playout restart 

    Still the same. Do I need to restart anything else when making changes?
  • Vote Up0Vote Down hoerichhoerich
    Posts: 627Member, Airtime Moderator
    same for me! can not wait for fallback to be implemented in v2.4

    I've got the same problem.
    On my sandbox ubuntu 32bit it works, on automation server Ubuntu 64bit at the Radio Station it does not.
    airtme-check on my sandbox says Liquidsoap not working, but It relays to an Icecast-Stream when nothing is scheduled in Airtime.
    This is an extraction of my working ls_script.liq working on my sandbox.

    #default = amplify(id="silence_src", 0.00001, noise())
    ref_off_air_meta = ref off_air_meta
    if !ref_off_air_meta == "" then
        ref_off_air_meta := "Airtime - offline"
    end
    #default = rewrite_metadata([("title", !ref_off_air_meta)], default)
    default = input.http("http://icecast.ipax.at:8010/k001436-1.mp3")
    ignore(output.dummy(default, fallible=true))

    Official Airtime Forum Manager
    --------------------------
    Most of the time an issue is located between keyboard and chair.
Add a Comment