<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 2/25/15 11:26 AM, Karl Newman wrote:<br>
</div>
<blockquote
cite="mid:CAOOwNtK5LbeRDoLRooxisZ=yPis_Jk7xhrZTOOy5zenaFK-cAA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Wed, Feb 25, 2015 at 6:54 AM, Dan
Wilga <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:mythtv-users2@dwilga-linux1.amherst.edu"
target="_blank">mythtv-users2@dwilga-linux1.amherst.edu</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Ideally,
there would be some way for the channel change script to
tell Myth, "I can't tune that" and have the recording
marked as "failed". Looking at the Myth source code, I
don't think it does anything with the script return value,
so I guess there's nothing to be done in this regard.<br>
<br>
</blockquote>
<div>It must do something with the channel change script
return value, because I just had some recordings fail
because my channel change script returned an error. They
showed up in Myth as grayed out with 0 bytes, so it was
obvious they had failed. It tripped me up, actually,
because the channel change script failure was only logged
as an info status under the channel logging group, so I
didn't see the error in the log. I submitted a patch to
change a failure to be logged as an error under general
(so it will be seen with the default logging options) and
it's been incorporated into master.<br>
<br>
</div>
<div>So, in your case, if the channel change script can
detect the failure and propagate that as a nonzero script
exit code, it should be picked up by Myth.<br>
</div>
</div>
</div>
</div>
</blockquote>
You're right, Karl. And, not only that, there's a way to leverage
this in Jon's script.<br>
<br>
I'm sending him a modified version privately that he can consider
for inclusion. When using it, a failure to tune is easily detected
by the script, and a non-zero status is returned. When this happens,
Myth creates a zero-byte recording and holds the tuner "active" for
a while (seems to be about 30 minutes.)<br>
<br>
But the zero-byte recording isn't considered complete, so the
recording gets rescheduled. This will happen over and over until the
channel is finally available which, counter-intuitive though it may
seem, is pretty much what I want. The only minor wish is that Myth
would not even create the zero-byte Recordings entry, but I can live
with it the way it is.<br>
</body>
</html>