Alexa Play......
"Tony Harding" <[email protected]> Sat, 4 Oct 2025 00:41:59 +0800
| Newsgroups | gmane.comp.audio.icecast.general |
|---|---|
| Organization | radiocompany.net |
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============7826045068379208255==
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0000_01DC34C7.B2AB9DC0"
This is a multi-part message in MIME format.
------=_NextPart_000_0000_01DC34C7.B2AB9DC0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
This may be a bit off topic, but I would welcome a Knowledge Base suggestion
As I now have two stations I service that have Smart Speaker skills and both
suffer from the same problem, I would like to know if other have the same
problem and how you remedy it.
Both stream to Icecast 2.4.4 Windows. Both are MP3 128K to AWS.
After an indeterminate period, but something like 10 days or more, the smart
speakers connect and play for 20 seconds and stop. If you reconnect they do
the same thing.
I have found that dropping the stream to the Icecast (NOT restarting the
icecast) and then reconnecting fixes the problem. As both have fallback set
up and have a sustaining stream to fallback too, this does not drop
listeners. Normal listeners do not have the 20 second problem.
I have taken to picking a low traffic period and dropping the main feed
every week or so as a preventative measure.
The speakers are not connected for 10 days solid, but the mounting point is
up for that time, but as I say the other listeners do not suffer the
problem. So I do not think this is a encoder problem, but likewise it does
not seem to be an icecast problem. Is it an AWS interface problem? AWS is
not connected until you say the magic words "Alexa play .."
Does anyone have this problem with their smart speaker listeners?
Regards
Tony
------=_NextPart_000_0000_01DC34C7.B2AB9DC0
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=3DEN-US link=3Dblue vlink=3Dblue>
<div class=3DSection1>
<div>
<blockquote style=3D'border:none;border-left:solid #CCCCCC =
1.0pt;padding:0cm 0cm 0cm 6.0pt;
margin-left:4.8pt;margin-right:0cm'>
<p class=3DMsoNormal><font size=3D3 face=3DArial><span =
style=3D'font-size:12.0pt;
font-family:Arial'>This may be a bit off topic, but I would welcome a =
Knowledge
Base suggestion<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D3 face=3DArial><span =
style=3D'font-size:12.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D3 face=3DArial><span =
style=3D'font-size:12.0pt;
font-family:Arial'>As I now have two stations I service that have Smart =
Speaker
skills and both suffer from the same problem, I would like to know if =
other
have the same problem and how you remedy =
it.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D3 face=3DArial><span =
style=3D'font-size:12.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D3 face=3DArial><span =
style=3D'font-size:12.0pt;
font-family:Arial'>Both stream to Icecast 2.4.4 Windows. Both are MP3 =
128K to
AWS.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D3 face=3DArial><span =
style=3D'font-size:12.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D3 face=3DArial><span =
style=3D'font-size:12.0pt;
font-family:Arial'>After an indeterminate period, but something like 10 =
days or
more, the smart speakers connect and play for 20 seconds and stop. If =
you
reconnect they do the same thing.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D3 face=3DArial><span =
style=3D'font-size:12.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D3 face=3DArial><span =
style=3D'font-size:12.0pt;
font-family:Arial'>I have found that dropping the stream to the Icecast =
(NOT
restarting the icecast) and then reconnecting fixes the problem. As both =
have
fallback set up and have a sustaining stream to fallback too, this does =
not
drop listeners. Normal listeners do not have the 20 second problem. =
<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D3 face=3DArial><span =
style=3D'font-size:12.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D3 face=3DArial><span =
style=3D'font-size:12.0pt;
font-family:Arial'>I have taken to picking a low traffic period and =
dropping
the main feed every week or so as a preventative =
measure.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D3 face=3DArial><span =
style=3D'font-size:12.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D3 face=3DArial><span =
style=3D'font-size:12.0pt;
font-family:Arial'>The speakers are not connected for 10 days solid, but =
the
mounting point is up for that time, but as I say the other listeners do =
not
suffer the problem. So I do not think this is a encoder problem, but =
likewise
it does not seem to be an icecast problem. Is it an AWS interface =
problem? AWS
is not connected until you say the magic words “Alexa play =
….”<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D3 face=3DArial><span =
style=3D'font-size:12.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D3 face=3DArial><span =
style=3D'font-size:12.0pt;
font-family:Arial'>Does anyone have this problem with their smart =
speaker
listeners?<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D3 face=3DArial><span =
style=3D'font-size:12.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D3 face=3DArial><span =
style=3D'font-size:12.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D3 face=3DArial><span =
style=3D'font-size:12.0pt;
font-family:Arial'>Regards<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D3 face=3DArial><span =
style=3D'font-size:12.0pt;
font-family:Arial'>Tony<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
</blockquote>
</div>
</div>
</body>
</html>
------=_NextPart_000_0000_01DC34C7.B2AB9DC0--
--===============7826045068379208255==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Icecast mailing list -- [email protected]
To unsubscribe send an email to [email protected]
--===============7826045068379208255==--