<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";
mso-fareast-language:NO-BOK;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="NO-BOK" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi Lin,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thank you for your response. If I understand you correct your suggestion is one mount for ads per listener? Or is it possible to move everyone
to a single mount with a scripted playlist that plays individual ads from a different CDN based on URL, IP and querystring parameters etc? Would love more detailed help to how/if something like that can be achieved.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">And how do I “from the outside” trigger the switch to a new mount and back? Can it be done via a specific ID3 tag, does Icecast have some sort
of API or other mechanisms for doing this?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Appreciate any insights on this,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">BR<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Rune<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Lin DasSarma [mailto:__@umbc.edu]
<br>
<b>Sent:</b> 11. april 2017 16:00<br>
<b>To:</b> Rune Hafskjær<br>
<b>Cc:</b> icecast-dev@xiph.org<br>
<b>Subject:</b> Re: [Icecast-dev] Server Side Spot Replacement?<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">It looks like you'd have to patch icecast to allow individual listener moves - do you control the live feed? Whatever triggers the ad could also move listeners to their own mounts. Also, keep in mind that could
be suddenly much more taxing on the server than usual.<o:p></o:p></p>
</div>
<p class="MsoNormal">Lin<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On 11 April 2017 at 09:03, Rune Hafskjær <<a href="mailto:Rune.Hafskjaer@p4.no" target="_blank">Rune.Hafskjaer@p4.no</a>> wrote:<o:p></o:p></p>
<p class="MsoNormal">Thank you Phillip, my first time here.<br>
<br>
What I want to achieve is to replace ads in a live ad break on live streamed radio with personal spots for each listener. I want to recognize the start of the break, split listeners into separate streamed spots and then back again to the live stream when the
spots has been played.<br>
<br>
The main goal is to offer programmatic data driven ads on streamed radio and bring radio into the modern advertising world.<br>
<br>
There are a number of companies that offers this in various cloud solutions in connection with Icecast servers, but there are pros and cons with the offerings and I want to understand how it's done and consider build it myself.<br>
<br>
<br>
Best regards,<br>
Rune<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><br>
-----Original Message-----<br>
From: Icecast-dev [mailto:<a href="mailto:icecast-dev-bounces@xiph.org">icecast-dev-bounces@xiph.org</a>] On Behalf Of Philipp Schafft<br>
Sent: 11. april 2017 14:48<br>
To: Rune Hafskjær<br>
Cc: <a href="mailto:icecast-dev@xiph.org">icecast-dev@xiph.org</a><br>
Subject: Re: [Icecast-dev] Server Side Spot Replacement?<br>
<br>
Good afternoon,<br>
<br>
On Tue, 2017-04-11 at 11:06 +0000, Rune Hafskjær wrote:<br>
> Hi guys,<br>
<br>
> Can anyone share some (deep technical) light on how «Server Side Spot<br>
> Replacement” on live radio streaming with Icecast can be done?<br>
<br>
I think it would be helpful if you could give some more context. Maybe by explaining your goal in a non-technical way (that often helps).<br>
<br>
Have a nice day,<br>
<br>
with best regards,<br>
<br>
<br>
--<br>
Philipp Schafft (CEO/Geschäftsführer)<br>
Telephon: <a href="tel:%2B49.3535%20490%2017%2092">+49.3535 490 17 92</a><br>
<br>
Löwenfelsen UG (haftungsbeschränkt) Registration number:<br>
Bickinger Straße 21 HRB 12308 CB<br>
04916 Herzberg (Elster) VATIN/USt-ID:<br>
Germany DE305133015<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal">_______________________________________________<br>
Icecast-dev mailing list<br>
<a href="mailto:Icecast-dev@xiph.org">Icecast-dev@xiph.org</a><br>
<a href="http://lists.xiph.org/mailman/listinfo/icecast-dev" target="_blank">http://lists.xiph.org/mailman/listinfo/icecast-dev</a><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>