<div dir="ltr"><div dir="ltr"><div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Mon, Oct 15, 2018 at 7:12 PM Stephen Worthington <<a href="mailto:stephen_agent@jsw.gen.nz">stephen_agent@jsw.gen.nz</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 Mon, 15 Oct 2018 17:58:14 -0700, you wrote:<br>
<br>
>On Mon, Oct 15, 2018 at 12:41 PM Peter Bennett <<a href="mailto:pb.mythtv@gmail.com" target="_blank">pb.mythtv@gmail.com</a>> wrote:<br>
><br>
>><br>
>><br>
>> On 10/15/2018 01:13 PM, Jay Harbeston (ISeePeople) wrote:<br>
>><br>
>><br>
>><br>
>> On Oct 15, 2018, at 11:50 AM, Allen Edwards <<a href="mailto:allen.p.edwards@gmail.com" target="_blank">allen.p.edwards@gmail.com</a>><br>
>> wrote:<br>
>><br>
>> I changed the name of my thread because the video card update problems are<br>
>> gone (thanks to the help from all of you) and I am only left with glitches<br>
>> in the recordings. I have done a lot of experimentation to try and isolate<br>
>> the problem but am at a loss as to what is going on.<br>
>><br>
>> Here is an example of a bad glitch <a href="http://l-36.com/mythtv.jpg" rel="noreferrer" target="_blank">http://l-36.com/mythtv.jpg</a><br>
>> Here is an example of a small one blown up to show it<br>
>> <a href="http://l-36.com/mythtv4.jpg" rel="noreferrer" target="_blank">http://l-36.com/mythtv4.jpg</a><br>
>><br>
>><br>
>><br>
>> You can use the hdhomerun_config and hdhomerun_config_gui utilities to see<br>
>> the status of the stream using the following example:<br>
>><br>
>> You will want to use the gui to set the channel to be verified and then do<br>
>> the following:<br>
>><br>
>> hdhomerun_config FFFFFFFF save /tuner0 capture.ts<br>
>><br>
>> This will capture the video to the file capture.ts, and also echo information while recording.<br>
>><br>
>> Quoting from the hdhomerun development pdf document:<br>
>><br>
>> ............n...............................n..........ts..........<br>
>> -- Video statistics --<br>
>> 23323 packets recieved, 2 network errors, 1 transport errors, 1 sequence errors<br>
>><br>
>> Advanced: A filename of “null” indicates no file should be created,<br>
>> allowing the use of the save command as a diagnostic tool.<br>
>><br>
>> Advanced: “-” may be used as a filename to indicate standard output,<br>
>> allowing the save command to be used as a pipe on supported platforms.<br>
>><br>
>> eg: hdhomerun_aptureconfig FFFFFFFF save /tuner0 - | vlc -<br>
>><br>
>> The dev document can be downloaded from SiliconDust, and has much more<br>
>> information that can be had using the utility.<br>
>> Something you can also check using the hdhomerun_config_gui is the signal<br>
>> strength and quality live.<br>
>> I have found these tools very handy.<br>
>><br>
>> I had the same problem with HD Homerun Prme, and the above test showed<br>
>> dropped packets. It was my router that was dropping UDP packets. I changed<br>
>> to a switch instead of the router between the HDHomerun Prime and the<br>
>> backend and the problem was solved.<br>
>><br>
>> Peter<br>
>><br>
><br>
>Thanks for the suggestions.<br>
><br>
>I have tried a few things.<br>
>1) sudo sysctl -w net.core.rmem_max=1048576 increased some buffer sizes --<br>
>no change<br>
>2) Ran hdhomerun_config FFFFFFFF save /tuner0 - | vlc - --where FFFFFFFF<br>
>was the address of one of the tuners. By the way, the tuners show 100%<br>
>signal strength and 80 - 100% signal quality. I got a series of dots<br>
>across the screen and no indication of a problem.<br>
>3) I switched the number of backend jobs to 1 from 2. It was 2 in the<br>
>Mythbuntu 8 system so I think that should be OK. We will watch the show<br>
>tomorrow morning to verify but I did not see any artifacts in about 5<br>
>minutes of watching.<br>
><br>
><br>
>dad@NewMyth:~$ hdhomerun_config 10126134 save /tuner0 null<br>
>......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................<br>
>...................................................^C<br>
>-- Video statistics --<br>
>15743 packets received, 0 overflow errors, 0 network errors, 0 transport<br>
>errors, 0 sequence errors<br>
><br>
>Note, I could not play anything using VLC either on the myth box or my<br>
>computer. The file was capture.ts but I was mainly interested in the<br>
>statistics, which did not show a problem.<br>
><br>
>Doesn't seem like it is a HDHomerun problem.<br>
><br>
>My guess is it is a myth problem either because the software no longer<br>
>supports such a slow computer, or some configuration changed between my<br>
>install of Mythbuntu 8 and 16.<br>
><br>
>Allen<br>
<br>
What sort of partition(s) are you recording to? Please post the fstab<br>
line you are using for it, so we can see what options are being used.<br>
If it is on the same drive as the system partition, please post the<br>
fstab line for that too.<br><br></blockquote><div><br></div><div>It is straight default Mythbuntu 16.041 on a single 750G drive. When I run out of ideas, I plan on buying a new 1T drive. </div><div><br></div><div>dad@NewMyth:~$ more /etc/fstab</div><div># /etc/fstab: static file system information.</div><div>#</div><div># Use 'blkid' to print the universally unique identifier for a</div><div># device; this may be used with UUID= as a more robust way to name devices</div><div># that works even if disks are added and removed. See fstab(5).</div><div>#</div><div># <file system> <mount point> <type> <options> <dump> <pass></div><div># / was on /dev/sda1 during installation</div><div>UUID=863a7857-d97e-432f-be2a-aa6d00f4e75d / ext4 errors=remount-ro 0 1</div><div># swap was on /dev/sda5 during installation</div><div>UUID=e4227cca-c0b0-4da9-80ee-f6fd2d73abb9 none swap sw 0 0</div><div>/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0</div><div><br></div><div><br></div><div>dad@NewMyth:/$ df</div><div>Filesystem 1K-blocks Used Available Use% Mounted on</div><div>udev 1008340 0 1008340 0% /dev</div><div>tmpfs 206196 6700 199496 4% /run</div><div>/dev/sda1 718883112 269065760 413277092 40% /</div><div>tmpfs 1030972 10196 1020776 1% /dev/shm</div><div>tmpfs 5120 4 5116 1% /run/lock</div><div>tmpfs 1030972 0 1030972 0% /sys/fs/cgroup</div><div>tmpfs 206196 8 206188 1% /run/user/1000</div><div> </div></div></div></div></div>