<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Nov 11, 2018, at 5:40 PM, James Abernathy <<a href="mailto:jfabernathy@gmail.com" class="">jfabernathy@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><blockquote type="cite" class=""><div class=""><br class="Apple-interchange-newline">On Nov 11, 2018, at 3:08 PM, John P Poet <<a href="mailto:jppoet@gmail.com" class="">jppoet@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">On Sun, Nov 11, 2018 at 11:24 AM James Abernathy <<a href="mailto:jfabernathy@gmail.com" class="">jfabernathy@gmail.com</a>> wrote:<br class=""><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;"><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Nov 11, 2018, at 1:03 PM, John P Poet <<a href="mailto:jppoet@gmail.com" target="_blank" class="">jppoet@gmail.com</a>> wrote:</div><br class="m_-4932032940744177468Apple-interchange-newline"><div class=""><div dir="ltr" class="">On Sun, Nov 11, 2018 at 9:40 AM Jim Abernathy <<a href="mailto:jfabernathy@gmail.com" target="_blank" class="">jfabernathy@gmail.com</a>> wrote:<br class=""><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-style: solid; border-left-color: rgb(204, 204, 204); padding-left: 1ex;">I have a new situation where channel 11-1 has huge issues with my new<span class="Apple-converted-space"> </span><br class="">HDHR Quatro. Signal Strength is 100% but Quality and Symbols go to 0<span class="Apple-converted-space"> </span><br class="">very 4-5 seconds. However on my HDHR Duo none of this happens. So<span class="Apple-converted-space"> </span><br class="">until I can get Silicondust to help resolve this, I need to set all<span class="Apple-converted-space"> </span><br class="">recording on Channel 11-1 to only use the Duo.<br class=""><br class="">I see the record scheduling option of preferred input. Is that the<span class="Apple-converted-space"> </span><br class="">correct way?<br class=""><br class="">Jim A<br class=""></blockquote><div class=""><br class=""></div><div class="">The easiest way is to set a "Custom Priority" for the desired combination:</div><div class=""><br class=""></div><div class="">Setup -> Video -> Recording Priorities -> Custom Priority</div><div class="">Rule Name: "11-1"</div><div class="">Priority Change: +50</div><div class="">Use the "Avoid poor signal quality" sample rule and modify as appropriate.</div><div class=""><br class=""></div><div class="">Alternatively, If you happened to set the display name of your capture cards to indicate which HDHR they are, for example:</div><div class="">Quatro1, Quatro2, Quatro3, Quatro4, Duo1, Duo2</div><div class=""><br class=""></div><div class="">Then you could use a rule like:</div><div class="">capturecard.displayname LIKE 'Duo%' and channel.channum="11-1"</div><div class=""><br class=""></div></div></div></div></blockquote><div class=""><br class=""></div>I named the tuners HDHR-0 thru HDHR-5. I could always change it to Quatro and Duo to make it simpler. Not sure I understand the rules. If I set this up in one Frontend, will it affect live and recorded TV on other Frontends and on Kodi frontends?</div><div class=""><br class=""></div><div class="">Jim A</div></div></blockquote><div class=""><br class=""></div><div class="">Yes, that configuration affects the mythbackend scheduler. It really belongs in the backend settings, but is put in the frontend to make it more convenient for the user to change.</div><div class=""><br class=""></div><div class="">When Myth is decided how to record a show, part of the decision process involves setting priorities for different situations. A "Custom Priority" rule can be used to adjust those priorities. In the example above, If it saw that it was able to record channel "11-1" and a capture card with a display name like "Duo", then it would give extra "weight" to that combination, making it more likely that it would choose it. A positive "Priority Change" means it is more likely to choose than scenario, and a negative value means that it is less likely.</div><div class=""><br class=""></div><div class="">John<br class=""></div><div class=""><br class=""></div></div></div></div></blockquote></div><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">Thanks, I changed my tuner display names to match your example. I put in the custom priority and found the channel is 11_1 and not 11-11. Once I install the custom priority I can see on Mythweb that the 11_1 programs are now set for Duo1.</span><div class="" style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><br class=""></div><div class="" style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;">The whole logic behind using priorities to make tuner choices still escapes me. But thanks again for explaining it.</div><div class="" style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><br class=""></div><div class="" style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;">Jim A</div></div></blockquote></div><br class=""><div class=""><br class=""></div><div class="">SO, now that I have my scheduling problem solved for channel 11_1 recordings. What about Live TV? is there a mechanism to force channel 11_1 to Duo% for Live TV?</div><div class=""><br class=""></div><div class="">Jim A</div><div class=""><br class=""></div></body></html>