<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 29/01/2019 14:30, Tim Pletcher
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CABBGYbEatMvgiOcUdBDZp3bLgyp0vNmd4tPzEqvi=pGkFWyTxw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">Since updating
to 2:30.0+fixes-autobuild.201901261750.f11c5ab~ubuntu18.04.1
via Mythbuntu PPA early yesterday morning, I have had
several intermittent recurrences of the error 'Could
not open decoder' appear on a remote mythtv frontend
while attempting to watch LiveTV. Unfortunately, I am
away on travel and can't do much detailed
troubleshooting right now. However, I was made aware
of this new issue after receiving an angry text from
my wife last evening. </div>
<div dir="ltr"><br>
</div>
<div dir="ltr">Looking through mythtv frontend log that
goes back about 5 months, I don't see any occurrences
of this until yesterday after installing the mentioned
update.</div>
<div dir="ltr"><br>
</div>
<div>Linked are log files with sections that cover the
sequences bookending an occurrence on the frontend and
backend.</div>
<div dir="ltr">
<div><a
href="https://gist.github.com/pletch/b7136765971df50c1c6b9990d18fb059"
moz-do-not-send="true">Frontend Log</a>
<--Line 28 is where error occurred.<br>
</div>
<div><a
href="https://gist.github.com/pletch/2ea3c5e2dc102e03b92b543ce8b9f0b3"
moz-do-not-send="true">Backend Log</a><br>
</div>
<div dir="ltr"><br>
</div>
<div>If attempting to re-tune again, it eventually
seems to work.</div>
<div><br>
</div>
<div>It appears that two updates were rolled into the
fixes version installed yesterday. Is it possible
this error is associated with this update: [ <a
href="https://github.com/MythTV/mythtv/commit/b06510032478ec887fd2491b5f9a5dad415c30f0"
moz-do-not-send="true">Ringbuffer change commit</a> ]?
Anyone else experienced anything similar?</div>
<div><br>
</div>
<div>Once I return home later this week, I'll do some
experiments to see if the error primarily associates
with channel changes, program transitions etc.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Tim</div>
<div><br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
mythtv-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a>
<a class="moz-txt-link-freetext" href="http://lists.mythtv.org/mailman/listinfo/mythtv-users">http://lists.mythtv.org/mailman/listinfo/mythtv-users</a>
<a class="moz-txt-link-freetext" href="http://wiki.mythtv.org/Mailing_List_etiquette">http://wiki.mythtv.org/Mailing_List_etiquette</a>
MythTV Forums: <a class="moz-txt-link-freetext" href="https://forum.mythtv.org">https://forum.mythtv.org</a>
</pre>
</blockquote>
<p>I also get this error on a remote frontend with version 30. Some
timeout must need a tweak. Note the issue has been there for
several weeks it is not due to a very recent change. I don't use
live tv enough to make it a major issue for me.<br>
</p>
</body>
</html>