Hello Sam,
I would like to replace the metadata at scheduled times for the live
program name:
Example:
- Monday 20:00-22:00 programname 1
- thurseday 19:00-20:00 news
- thurseday 20:00-22:00 programme 2
- Sunday 08:00-10:30 Classcal musik
etc etc
Outside these hours i want to use the metadata from the source stream
plus if possible inserted a programmename like - daily 22:00-01:00
easylistening
- daily 01:00-08:00 musicmix
etc etc
The source stream is also the stream providing the LIVE programm,
streamed by Edcast source client, the metadata is provided by a text
file from Zararadio.
Below my liq file:
set("log.file",true)
set("log.stdout",true)
set("log.level",4)
# Input the stream,
# from an Icecast server or any other source
url = "http://127.0.0.1:8000/studio.flac";
input = mksafe(input.http(url))
# First transcoder: MP3 80 kbps
output.icecast(%mp3(stereo=true, stereo_mode="joint_stereo", bitrate=80,
internal_quality=0), host = "127.0.0.1", port = 8000, password =
"xxxxxxx", mount =
"studio.mp3",genre="various",url="http://www.flevoziekenomroep.net",description="FlevoZiekenOmroep";,
id="FZO_MP3",name="FZO MP3 stream",icy_metadata="true",public=false,input)
# Second transcoder: AACPLUS 56 kbps
output.icecast(%aacplus(bitrate=56), host = "127.0.0.1", port = 8000,
password = "xxxxxxx", mount = "studio.aac", genre= "various",url=
"http://www.flevoziekenomroep.net",description= "Flevoziekenomroep",
id="FZO_AACPLUS",name="FZO AACPLUS
stream",icy_metadata="true",public=false,input)
# Thirth transcoder: Vorbis 64 Kbps
output.icecast(%vorbis(samplerate=44100, channels=2, quality=0), host =
"127.0.0.1", port = 8000, password = "xxxxxxx", mount = "studio.ogg",
genre= "various",url= "http://www.flevoziekenomroep.net",description=
"Flevoziekenomroep", id="FZO_OGG",name="FZO OGG stream",public=false,input)
# Fourth transcoder: Opus 64 kbps
output.icecast(%opus(vbr="constrained", application="audio",
complexity=5, max_bandwidth="super_wide_band", samplerate=48000,
bitrate=64, frame_size=20., channels=2, signal="music"), host =
"127.0.0.1", port = 8000, password = "xxxxxxx", mount = "studio.opus",
genre= "various",url= "http://www.flevoziekenomroep.net",description=
"Flevoziekenomroep", id="FZO_OPUS",name="FZO OPUS
stream",icy_metadata="true",public=false,input)
I liked the code, but that is only inserted data and daily the same....
source = ...
# Create a function "meta" to update metadata
meta_source = insert_metadata(source)
# function to insert metadata
meta = fst(meta_source)
# the source
source = snd(meta_source)
# Create a function which insert the title in the metadata
def update_meta() =
# Compute the title
title = if 12h-14h then "Lunchtime"
elsif 6h30-9h then "Breakfast"
elsif 14h-18h then "Afternoon"
else "Anytime"
end
# The metadata to insert
m = [("title",title)]
# Insert metadata
meta(m)
# Schedule again in 10 min
600.
end
# Call the function every 10 min
add_timeout(0.,update_meta())
output.icecast(source)
Kind regards,
Dennis
Op 12-3-2013 18:25, Samuel Mimram schreef:
> Hi,
>
> What do you mean exactly by day by day schedule? Please provide more
> information about you setup and what you are trying to achieve!
>
> ++
>
> Sam.
>
> On Tue, Mar 12, 2013 at 10:17 AM, Dennis Heerema <[email protected]> wrote:
>> Hi There,
>>
>> Is it possible to do this also with a day by day schedule?
>>
>> Thanks for your help!
>>
>> Dennis
>>
>> -----Original Message-----
>> From: Samuel Mimram <[email protected]>
>> To: savonet-users <[email protected]>
>> Cc: savonet-users <[email protected]>
>> Date: Mon, 11 Mar 2013 19:13:56 +0100
>> Subject: Re: [Savonet-users] setting and getting stream metadata?
>>
>> Hi,
>>
>> The icy.update_metadata directly sends some metadata to the icecast
>> encoder, but the metadata is not passed through the usual Liquidsoap
>> mechanism, so Liquidsoap does not know about it. The proper way to
>> have everything in sync is to use insert_metadata (I have given a few
>> example of uses of this functions recently on the list, for instance
>> http://www.mail-archive.com/[email protected]/msg07761.html
>> )
>>
>> ++
>>
>> Sam.
>>
>> On Sun, Mar 10, 2013 at 6:06 AM, Tony Miller <[email protected]> wrote:
>>> I'm a little confused about the methods to set metadata. Right now I'm
>>> setting metadata with icy.update_metadata when an input.harbor
>>> connects successfully. That seems to work, and I can see the 'current
>>> song' changed when i visit the icecast server's web interface at port
>>> 8000. However, when I try to use the icecast.metadata command from
>>> telnet, I don't get this metadata. I seem to get a list of the songs
>>> in my playlist. (My fallback scheme is input.harbor,playlist,single).
>>>
>>> So now I am wondering what is the difference between whatever the
>>> icecast web interface is doing to get 'current_song', and what the
>>> icecast.metadata command does? Do I have a conceptual problem? :)
>>>
>>> I guess I could always just parse the xml the icecast loves to give
>>> you by visiting localhost:8000/admin/stats instead of calling
>>> icecast.metadata from telnet or socket...
>>>
>>> --
>>> -Tony Miller
>>> github.com/mcfiredrill
>>> @freedrull
>>> freedrool.us
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
>>> Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
>>> endpoint security space. For insight on selecting the right partner to
>>> tackle endpoint security challenges, access the full report.
>>> http://p.sf.net/sfu/symantec-dev2dev
>>> _______________________________________________
>>> Savonet-users mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/savonet-users
>> ------------------------------------------------------------------------------
>> Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
>> Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
>> endpoint security space. For insight on selecting the right partner to
>> tackle endpoint security challenges, access the full report.
>> http://p.sf.net/sfu/symantec-dev2dev
>> _______________________________________________
>> Savonet-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/savonet-users
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
>> Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
>> endpoint security space. For insight on selecting the right partner to
>> tackle endpoint security challenges, access the full report.
>> http://p.sf.net/sfu/symantec-dev2dev
>> _______________________________________________
>> Savonet-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/savonet-users
>>
------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
endpoint security space. For insight on selecting the right partner to
tackle endpoint security challenges, access the full report.
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users
