<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 6 Jun 2023, at 22:16, Klaas de Waal <<a href="mailto:klaas.de.waal@gmail.com" class="">klaas.de.waal@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><br class=""></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, 6 Jun 2023 at 01:28, Douglas Peale <<a href="mailto:Douglas_Peale@comcast.net" class="">Douglas_Peale@comcast.net</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Why do both mythweb and MythTV Webfrontend both report "idle" for tuners that are running an EPG guide scan?<br class=""></blockquote><div class=""><br class=""></div><div class="">This is because these tuners are idle, in the sense that they can be used at any moment for a recording or for live TV.</div><div class="">The EIT scanning is done kind of "under de hood" with tuners that are, yes, idle…</div></div></div></div></blockquote><div><br class=""></div>There is an option to only scan for EIT while recording. That will avoid the issue altogether.</div><br class=""><div class="">Downside is that if your recordings are few and far between, then the guide data won’t be collected often. Also, and I don’t know if this is actually a problem anywhere, it won’t work very well if the data isn’t transmitted on all muxes - e.g. if only guide data for channels on that mux are transmitted. You’d have to record a program off each mux to collect all guide data if that was the case.</div><div class=""><br class=""></div><div class="">Simon</div><div class=""><br class=""></div></body></html>