<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:12pt"><div><br></div><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><font size="2" face="Tahoma"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Steven Ellis <steven@openmedia.co.nz><br><b><span style="font-weight: bold;">To:</span></b> MythTV in NZ <mythtvnz@lists.linuxnut.co.nz><br><b><span style="font-weight: bold;">Sent:</span></b> Monday, 30 March, 2009 9:25:31 AM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [mythtvnz] DVB-T mux A errors<br></font><br><br><div><div>On 30/03/2009, at 8:55 AM, Steve V wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate;
color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;"><div><div style="margin: 0px; font-family: 'times new roman','new york',times,serif; font-size: 12pt;"><div style="margin: 0px;">I think it happened because the first time I scanned for channels I hadn't turned on the LNA (Low Noise Amplifier?) for the NOVA-T 500. Without the LNA active the other 2 muxes tune in fine but Mux A does not. I am guessing that this put corrupt info into the database and subsequent retries will not overwrite the old info - just a guess.</div><div style="margin: 0px;"> </div><div style="margin: 0px;">It will be interesting to see if manually changing the data in the database will fix the problem - I really don't want to rebuild it
again. <br></div><div style="margin: 0px; font-size: 12pt; font-family: 'times new roman','new york',times,serif;"><br><div style="margin: 0px; font-size: 12pt; font-family: 'times new roman','new york',times,serif;"><font size="2" face="Tahoma"><hr size="1"><b><span style="font-weight: bold;">From:</span></b><span class="Apple-converted-space"> </span>Guy Gibson <<a rel="nofollow" ymailto="mailto:ggibson@orcon.net..nz" target="_blank" href="mailto:ggibson@orcon.net.nz">ggibson@orcon.net.nz</a>><br><b><span style="font-weight: bold;">To:</span></b><span class="Apple-converted-space"> </span>MythTV in NZ <<a rel="nofollow" ymailto="mailto:mythtvnz@lists.linuxnut.co.nz" target="_blank" href="mailto:mythtvnz@lists.linuxnut.co.nz">mythtvnz@lists.linuxnut.co.nz</a>><br><b><span style="font-weight: bold;">Sent:</span></b><span class="Apple-converted-space"> </span>Monday, 30 March, 2009 8:05:24 AM<br><b><span style="font-weight:
bold;">Subject:</span></b><span class="Apple-converted-space"> </span>Re: [mythtvnz] DVB-T mux A errors<br></font><br>Only to say steve I've had exactly the same issue before, about 4 weeks ago. I thought it might have been lower signal strength, on the A mux, but boosting the signal made no difference. I tried lots of things and rescans etc but to no avail. In the end I rebuilt the box again and it disappeared.<div style="margin: 0px;"><br></div><div style="margin: 0px;">Guy</div><div style="margin: 0px;"> </div></div></div></div></div></span></blockquote><br></div><div>I recommend deleting all of your DVB multiplexes from the Transport Editor, and then searching channels on each one manually. As you perform each search re-enter the Transport Editor screen screen to make sure that the correct values have been loaded for each multiplec.</div><div><br></div><div>This is a reference for DVB-S but should apply for
DVB-T</div><div><br></div><div><a rel="nofollow" target="_blank" href="http://support.mypvr.co.nz/mypvr/?page_id=24">http://support.mypvr.co..nz/mypvr/?page_id=24</a></div><div><br></div><div>I've found in auckland that MythTV sometimes puts the wrong information in the database.</div><div><br></div><div>Steve</div><div><br></div><br><div> <span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;"><div style=""><div>Steven Ellis - Technical Director<br>OpenMedia Limited<br>email - <a rel="nofollow" ymailto="mailto:steven@openmedia.co.nz" target="_blank" href="mailto:steven@openmedia.co.nz">steven@openmedia.co.nz</a><br>website - <a rel="nofollow"
target="_blank" href="http://www.openmedia.co.nz/">http://www.openmedia.co.nz</a><br></div></div></span> </div><br>Thanks Steven,<br>
<br>
your advice was right on track, I only had to delete the corrupt multiplex using the transport editor then a rescan of channels and it was fixed.<br><br><br>Cheers<br><br>Steve <br></div></div></div><br>
<a href=http://au.rd.yahoo.com/nz/mail/tagline/2009/healthtest/*http://nz..lifestyle.yahoo.com/health/>Get fit, feel better!</a> All the help you need at Yahoo!Xtra Health</body></html>