<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, 14 Mar 2020 at 18:28, John Pilkington <<a href="mailto:johnpilk222@gmail.com">johnpilk222@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 14/03/2020 15:18, John Pilkington wrote:<br>
> On 14/03/2020 13:14, John Pilkington wrote:<br>
>> On 14/03/2020 12:25, Klaas de Waal wrote:<br>
>>><br>
>>><br>
>>> On Sat, 14 Mar 2020 at 12:04, John Pilkington <<a href="mailto:johnpilk222@gmail.com" target="_blank">johnpilk222@gmail.com</a> <br>
>>> <mailto:<a href="mailto:johnpilk222@gmail.com" target="_blank">johnpilk222@gmail.com</a>>> wrote:<br>
>>><br>
>>> On 04/03/2020 14:48, John Pilkington wrote:<br>
>>><br>
>>> ><br>
>>> > The DVB-T/T2 scans did not find the new QAM-256 transports<br>
>>> > automatically, and a full scan looked as if it would take a long<br>
>>> time.<br>
>>> > I'm afraid I let the TV tell me the new frequencies.<br>
>>> ><br>
>>> > "700 Mhz clearance" -> DVB-T2 now on 586, 746 and 754 MHz<br>
>>> ><br>
>>><br>
>>> I have a new problem with DVB-T2 and last night's master, <br>
>>> 2e9f884. I'm<br>
>>> not sure when it started.<br>
>>><br>
>>> After last week's retune I had 3 DVB-T2 transports, with channels.<br>
>>> Their frequencies are quoted above. In current scans only two are<br>
>>> populated. 746 MHz gives no channels. VLC, also using the MyGica <br>
>>> 230<br>
>>> tuner, has the same problem with just that mux.<br>
>>><br>
>>> My TV finds and plays these channels. One is BBC NEWS HD.<br>
>>><br>
>>> There's a new commit, 405e049, that may affect this. I'll start a<br>
>>> build.<br>
>>><br>
>>> When VLC also has problems there might have been something changed in <br>
>>> the multiplex.<br>
>>> You could try with the "Complete scan data required" option unchecked <br>
>>> (by default it is checked).<br>
>>> A complete log of the scan, capturing the terminal output of <br>
>>> mythtv-setup like this:<br>
>>><br>
>>> mythtv-setup -v chanscan,channel,record --loglevel=debug 2>&1 | tee <br>
>>> ms-20200314-1321.log<br>
>>><br>
>>> is what I need to figure out what is happening. This will be too big <br>
>>> for the mailing list but it can be sent to me directly.<br>
>>><br>
>>> BTW the latest commit changes the numbering scheme for duplicate <br>
>>> channels. It will not influence the scanning itself.<br>
>>><br>
>>> Klaas.<br>
>><br>
>> I have the new build and will experiment soon. I forgot to say that <br>
>> the scans reported No Lock, with all the options I tried.<br>
>><br>
>> There are political moves to stop open access in the future. May be <br>
>> ominous.<br>
>><br>
> Hope this helps<br>
> <br>
> <a href="https://drive.google.com/open?id=1SW5c-KbgpghSSvqhs5walkD6-MLJ13Zs" rel="noreferrer" target="_blank">https://drive.google.com/open?id=1SW5c-KbgpghSSvqhs5walkD6-MLJ13Zs</a><br>
<br>
It probably won't, because it didn't get lock on the transport giving <br>
the problem.<br>
<br>
So I tried a frequency offset. and got lock with 746.1 MHz. It saw <br>
channels but apparently didn't update the DB (probably because I had <br>
cheated by editing another transport with the wrong transportid).<br>
<br>
Deleted and created a new transport at 746166000 Hz, and one more 'all <br>
transports' scan looks OK.<br>
<br>
I suppose a full scan might have been quicker. I haven't dared to look <br>
at the chanids :-)<br>
> <br><br></blockquote><div>Yes, a full scan in the UK does try also the offset frequencies..... so the frequency was the problem. Glad that it is solved.</div><div><br></div><div>While at the subject of doing a full scan, would it be possible for you to do a full scan with again the full debug?</div><div>Goal of this is to figure out if and how to automatically remove duplicate transports received "on the back of the antenna" from other transmitters.</div><div>To prevent messing up your working system, you could do the following:</div><div>- create a new video source</div><div>- connect your MyGIca to the new video source</div><div>- do a full scan (-v chanscan,channel,record --loglevel=debug) for the new video source and capture the output</div><div>- then just delete the video source, this also deletes all the new transports and channels</div><div>- reconnect your MyGica to the videos source it was connected to previously so your system works again.</div><div><br></div><div>No hurry on my side, but while we are at it....</div><div><br></div><div>Thanks!</div><div>Klaas.</div><div><br></div><div><br></div><div><br></div><div><br></div><div> </div></div></div>