Buffering badly on certain OTA channels

Just set up a timed recording ... 5 minutes long.

ddint think of that. but i just started a record of a 30 min show, that only has 5 min left.

Come to think of it, I don't really know how to do this. Hmmmm.

So. aside from a red DELAYED! Tag
there is no % of recording had issues banner on the short recording i just did.
does it take a while to process/analyze?
and yes, it does pixelate alot when i play back the recording file.
when i do the open rec log, all that is there is
loc=188 pkt=2 pid=512 what="pat_and_pmt" offset=0 length=376 contiguous=true changed=true packets=2

ill have to wait a bit and see if any errors reported for the full length schedule rec went.

If you're within LOS (Line of sight) of the transmitter and in the green contour area of the map you should be good receiving 33.

Have you tried entering your location in RabbitEars Signal Search Map ?

There will be no delay on reporting the errors. It will show up as soon as the recording has completed if there are any issues.

You can see more detail by looking in the logs for the [SNR] message.

yup...well within the green. i zoomed in to my exact location.

i suspect it is a issue with the tower/stations now.

I connected up my spare antenna near to my main one, to my portable tv i have, even with the antennas amp, the same pixelzation is happening on all 33- channels.....

what logs? the recording log? like I said, that was the only line in the log.

there is this a crap ton of this in the sever log tab.

2020/03/14 17:39:15.823877 [HLS] ffmpeg: file102-ip192.168.0.7: Last message repeated 9 times
2020/03/14 17:39:15.823890 [HLS] ffmpeg: file102-ip192.168.0.7: [mpegts @ 0x2243700] Dropped corrupted packet (stream = 1)
2020/03/14 17:39:15.946320 [HLS] ffmpeg: file102-ip192.168.0.7: [mpegts @ 0x2243700] Dropped corrupted packet (stream = 0)
2020/03/14 17:39:16.316370 [ENC] Segment 163 has unexpected duration: inputs=472-473 expected=1.001 actual=1.2012 expected_pts=185.947200-186.948200 actual_pts=185.968533-187.136367
2020/03/14 17:39:17.715992 [ENC] Segment 180 has unexpected duration: inputs=507-508 expected=1.001 actual=1.1011 expected_pts=203.564800-204.565800 actual_pts=203.586133-204.653867
2020/03/14 17:39:18.003726 [HLS] ffmpeg: file102-ip192.168.0.7: Last message repeated 17 times
2020/03/14 17:39:18.003740 [HLS] ffmpeg: file102-ip192.168.0.7: [mpegts @ 0x2243700] Dropped corrupted packet (stream = 1)
2020/03/14 17:39:18.004907 [HLS] ffmpeg: file102-ip192.168.0.7: [mpegts @ 0x2243700] Dropped corrupted packet (stream = 0)
2020/03/14 17:39:18.546139 [HLS] ffmpeg: file102-ip192.168.0.7: Last message repeated 5 times
2020/03/14 17:39:18.546153 [HLS] ffmpeg: file102-ip192.168.0.7: [mpeg2video @ 0x224b180] slice below image (153 >= 30)
2020/03/14 17:39:18.546157 [HLS] ffmpeg: file102-ip192.168.0.7: Error while decoding stream #0:0: Invalid data found when processing input
2020/03/14 17:39:18.816072 [HLS] ffmpeg: file102-ip192.168.0.7: [mpegts @ 0x2243700] Dropped corrupted packet (stream = 0)
2020/03/14 17:39:19.517083 [ENC] Segment 202 has unexpected duration: inputs=555-556 expected=1.001 actual=1.1011 expected_pts=226.988200-227.989200 actual_pts=227.009533-228.077267
2020/03/14 17:39:20.017466 [ENC] Segment 208 has unexpected duration: inputs=564 expected=1.001 actual=1.5015 expected_pts=233.094300-234.095300 actual_pts=232.615133-234.083267
2020/03/14 17:39:20.320596 [ENC] Segment 211 has unexpected duration: inputs=567-569 expected=1.5015 actual=2.002 expected_pts=236.097300-237.598800 actual_pts=235.618133-237.586767
2020/03/14 17:39:21.666791 [HLS] ffmpeg: file102-ip192.168.0.7: Last message repeated 32 times
2020/03/14 17:39:21.666804 [HLS] ffmpeg: file102-ip192.168.0.7: [mpegts @ 0x2243700] Dropped corrupted packet (stream = 1)
2020/03/14 17:39:21.865428 [HLS] ffmpeg: file102-ip192.168.0.7: [mpegts @ 0x2243700] Dropped corrupted packet (stream = 0)
2020/03/14 17:39:23.317632 [ENC] Segment 248 has unexpected duration: inputs=682-683 expected=1.001 actual=1.1011 expected_pts=275.036200-276.037200 actual_pts=275.057533-276.125267
2020/03/14 17:39:23.616828 [ENC] Segment 252 has unexpected duration: inputs=687-688 expected=1.001 actual=1.1011 expected_pts=279.040200-280.041200 actual_pts=278.561033-279.628767
2020/03/14 17:39:23.819253 [ENC] Segment 253 has unexpected duration: inputs=689-691 expected=1.001 actual=1.4014 expected_pts=280.041200-281.042200 actual_pts=279.662133-281.030167
2020/03/14 17:39:23.918189 [ENC] Segment 255 has unexpected duration: inputs=693-694 expected=1.001 actual=1.1011 expected_pts=282.043200-283.044200 actual_pts=282.064533-283.132267
2020/03/14 17:39:24.616990 [ENC] Segment 262 has unexpected duration: inputs=706-708 expected=1.5015 actual=2.002 expected_pts=289.550700-291.052200 actual_pts=289.071533-291.040167
2020/03/14 17:39:24.920700 [ENC] Segment 265 has unexpected duration: inputs=713-714 expected=1.001 actual=1.1011 expected_pts=293.054200-294.055200 actual_pts=293.075533-294.143267
2020/03/14 17:39:25.297472 [HLS] ffmpeg: file102-ip192.168.0.7: Last message repeated 30 times
2020/03/14 17:39:25.297509 [HLS] ffmpeg: file102-ip192.168.0.7: [mpegts @ 0x2243700] Dropped corrupted packet (stream = 1)
2020/03/14 17:39:25.416705 [ENC] Segment 270 has unexpected duration: inputs=721-722 expected=1.001 actual=1.1011 expected_pts=298.059200-299.060200 actual_pts=298.080533-299.148267
2020/03/14 17:39:25.480855 [HLS] ffmpeg: file102-ip192.168.0.7: [mpegts @ 0x2243700] Dropped corrupted packet (stream = 0)
2020/03/14 17:39:25.816788 [ENC] Segment 274 has unexpected duration: inputs=727-729 expected=1.5015 actual=2.002 expected_pts=302.063200-303.564700 actual_pts=301.584033-303.552667
2020/03/14 17:39:26.219252 [ENC] Segment 279 has unexpected duration: inputs=736-737 expected=1.001 actual=1.5015 expected_pts=307.568700-308.569700 actual_pts=307.089533-308.557667
2020/03/14 17:39:26.916159 [ENC] Segment 287 has unexpected duration: inputs=748-749 expected=1.001 actual=1.5015 expected_pts=315.576700-316.577700 actual_pts=315.097533-316.565667
2020/03/14 17:39:27.301248 [HLS] ffmpeg: file102-ip192.168.0.7: Last message repeated 19 times
2020/03/14 17:39:27.301265 [HLS] ffmpeg: file102-ip192.168.0.7: [mpegts @ 0x2243700] Dropped corrupted packet (stream = 1)
2020/03/14 17:39:27.421244 [ENC] Segment 292 has unexpected duration: inputs=756-757 expected=1.001 actual=1.1011 expected_pts=320.581700-321.582700 actual_pts=320.603033-321.670767
2020/03/14 17:39:27.447461 [HLS] ffmpeg: file102-ip192.168.0.7: [mpegts @ 0x2243700] Dropped corrupted packet (stream = 0)
2020/03/14 17:39:27.712980 [HLS] ffmpeg: file102-ip192.168.0.7: Last message repeated 2 times
2020/03/14 17:39:27.712991 [HLS] ffmpeg: file102-ip192.168.0.7: [mpegts @ 0x2243700] Dropped corrupted packet (stream = 1)
2020/03/14 17:39:27.826414 [ENC] Segment 297 has unexpected duration: inputs=795-804 expected=1.4014 actual=1.5015 expected_pts=325.586700-326.988100 actual_pts=325.608033-327.076167
2020/03/14 17:39:27.985569 [HLS] ffmpeg: file102-ip192.168.0.7: Last message repeated 1 times
2020/03/14 17:39:27.985579 [HLS] ffmpeg: file102-ip192.168.0.7: [mpegts @ 0x2243700] Dropped corrupted packet (stream = 0)
2020/03/14 17:39:28.317929 [ENC] Segment 304 has unexpected duration: inputs=856-865 expected=1.001 actual=1.1011 expected_pts=333.094200-334.095200 actual_pts=333.015433-333.983067
2020/03/14 17:39:28.975829 [HLS] ffmpeg: file102-ip192.168.0.7: Last message repeated 7 times
2020/03/14 17:39:28.975847 [HLS] ffmpeg: file102-ip192.168.0.7: [mpegts @ 0x2243700] Dropped corrupted packet (stream = 1)
2020/03/14 17:39:28.977824 [HLS] ffmpeg: file102-ip192.168.0.7: [mpegts @ 0x2243700] Dropped corrupted packet (stream = 0)
2020/03/14 17:39:29.770146 [HLS] ffmpeg: file102-ip192.168.0.7: Last message repeated 4 times
2020/03/14 17:39:29.770163 [HLS] ffmpeg: file102-ip192.168.0.7: [mpegts @ 0x2243700] Dropped corrupted packet (stream = 1)
2020/03/14 17:39:29.907943 [HLS] ffmpeg: file102-ip192.168.0.7: [mpegts @ 0x2243700] Dropped corrupted packet (stream = 0)
2020/03/14 17:39:30.426758 [HLS] ffmpeg: file102-ip192.168.0.7: Last message repeated 2 times
2020/03/14 17:39:30.426773 [HLS] ffmpeg: file102-ip192.168.0.7: [mpegts @ 0x2243700] Dropped corrupted packet (stream = 1)
2020/03/14 17:39:30.427632 [HLS] ffmpeg: file102-ip192.168.0.7: [mpegts @ 0x2243700] Dropped corrupted packet (stream = 0)
2020/03/14 17:39:31.416645 [ENC] Segment 338 has unexpected duration: inputs=977-978 expected=1.001 actual=1.1011 expected_pts=368.529600-369.530600 actual_pts=368.550933-369.618667
2020/03/14 17:39:31.699725 [HLS] ffmpeg: file102-ip192.168.0.7: Last message repeated 12 times
2020/03/14 17:39:31.699735 [HLS] ffmpeg: file102-ip192.168.0.7: [mpegts @ 0x2243700] Dropped corrupted packet (stream = 1)
2020/03/14 17:39:31.724924 [HLS] ffmpeg: file102-ip192.168.0.7: [mpegts @ 0x2243700] Dropped corrupted packet (stream = 0)
2020/03/14 17:39:31.819874 [ENC] Segment 342 has unexpected duration: inputs=983-984 expected=1.001 actual=1.1011 expected_pts=372.533600-373.534600 actual_pts=372.054433-373.122167
2020/03/14 17:39:31.916619 [ENC] Segment 343 has unexpected duration: inputs=985-986 expected=1.001 actual=1.4014 expected_pts=373.534600-374.535600 actual_pts=373.155533-374.523567
2020/03/14 17:39:33.317376 [ENC] Segment 359 has unexpected duration: inputs=1015-1016 expected=1.001 actual=1.5015 expected_pts=390.151200-391.152200 actual_pts=389.672033-391.140167
2020/03/14 17:39:33.576490 [HLS] ffmpeg: file102-ip192.168.0.7: Last message repeated 15 times
2020/03/14 17:39:33.576502 [HLS] ffmpeg: file102-ip192.168.0.7: [mpegts @ 0x2243700] Dropped corrupted packet (stream = 1)
2020/03/14 17:39:33.605019 [HLS] ffmpeg: file102-ip192.168.0.7: Last message repeated 1 times
2020/03/14 17:39:33.605045 [HLS] ffmpeg: file102-ip192.168.0.7: [mpegts @ 0x2243700] Dropped corrupted packet (stream = 0)
2020/03/14 17:39:34.761091 [HLS] ffmpeg: file102-ip192.168.0.7: Last message repeated 9 times
2020/03/14 17:39:34.761116 [HLS] ffmpeg: file102-ip192.168.0.7: [mpegts @ 0x2243700] Dropped corrupted packet (stream = 1)
2020/03/14 17:39:34.934665 [HLS] ffmpeg: file102-ip192.168.0.7: [mpegts @ 0x2243700] Dropped corrupted packet (stream = 0)
2020/03/14 17:39:36.416679 [ENC] Segment 392 has unexpected duration: inputs=1085-1086 expected=1.001 actual=1.2012 expected_pts=426.988000-427.989000 actual_pts=427.009333-428.177167
2020/03/14 17:39:36.816814 [ENC] Segment 397 has unexpected duration: inputs=1095-1096 expected=1.001 actual=1.1011 expected_pts=431.993000-432.994000 actual_pts=432.014333-433.082067
2020/03/14 17:39:37.401403 [HLS] ffmpeg: file102-ip192.168.0.7: Last message repeated 21 times
2020/03/14 17:39:37.401431 [HLS] ffmpeg: file102-ip192.168.0.7: [mpegts @ 0x2243700] Dropped corrupted packet (stream = 1)
2020/03/14 17:39:37.550038 [HLS] ffmpeg: file102-ip192.168.0.7: [mpegts @ 0x2243700] Dropped corrupted packet (stream = 0)
2020/03/14 17:39:37.993621 [HLS] ffmpeg: file102-ip192.168.0.7: Last message repeated 5 times
2020/03/14 17:39:37.993634 [HLS] ffmpeg: file102-ip192.168.0.7: [mpegts @ 0x2243700] Dropped corrupted packet (stream = 1)
2020/03/14 17:39:38.110553 [HLS] ffmpeg: file102-ip192.168.0.7: [mpegts @ 0x2243700] Dropped corrupted packet (stream = 0)
2020/03/14 17:39:38.116481 [ENC] Segment 412 has unexpected duration: inputs=1124-1126 expected=1.3013 actual=1.5015 expected_pts=447.208200-448.509500 actual_pts=446.729033-448.197167
2020/03/14 17:39:38.195782 [ENC] Encoder stopped for Forensic Files S11E31 2007-02-14 Muffled Cries 2020-03-14-1725.mpg in /media/simba/DATA1/TV/Streaming/file102-ip192.168.0.7-540245243/encoder-0-747877918 after encoding 0 to 412
2020/03/14 17:42:30.572152 [HLS] Stopping inactive session file102-ip192.168.0.7

No banner for errors on the full 1hr rec. yet the show is ear unwatchable with breaks ups.
and only 2 lines in the Rec log.

the signal stats as reported by HDHR are the same, as i posted above 88/ 100 / 100 and dont really flucuate at all.

eric was saying to look at the line in the Channels DVR Server log for when the recording ended
You can see more detail by looking in the logs for the [SNR] message.
i.e.

2020/03/12 23:02:00.610626 [SNR] Statistics for "TV/Building Off the Grid/Building Off the Grid S08E11 Flathead Lake Pontoon 2020-03-12-2201.mpg": ss=98%-99% snq=100% seq=100% bps=3848553,1212224-5636992 pps=369,129-536

Like I said those same percentages that the HD are tuner itself reports for those three stats
From Channels log

[SNR] Statistics for "TV/Emergency!/Emergency! S03E05 1973-10-20 Heavyweight 2020-03-14-1659.mpg": ss=87%,86%-89% snq=100% seq=100% bps=2207544,323360-2750816 pps=211,31-261

from HDHR

Signal Strength 87%
Signal Quality 100%
Symbol Quality 100%

It also clear that ur "Recording has issues" trigger detection needs work, as it is not detecting the clearly bad recording with a very bad corrupt video and audio data streams, as the other dev said was happening.

It has to be something with the stations themselves.

As I removed the CM LTE filter, and the channels still are digitizing and breaking up/buffering badly....same as when i loaded them on my portable tv and other antenna.

Like I mentioned in last post, the " % of recording has signal issues" i guess it is just monitoring the signal stats, and in this case, those are strong and dont fluctuate much, vs the raw data stream quality of dropped frames etc??

Have you tried disabling Surround Sound?

Pretty sure that was mentioned previously in this thread I've never had surround sound enabled.

We are monitoring the HDHR stats for counters for if there were any MPEG-TS packets that did not decode properly. We had expected that it would detect all tuning issues, but it appears there's something special about the issues you're having that is corrupting the feed without causing the standard detection mechanisms to trip.

The reason why we asked for you to be on the latest build and for the [SNR] stats instead of just the signal stats you posted from the HDHR is that they can vary from moment to moment and our system is checking with the HDHR every 2 seconds and can detect momentary drops that would cause issues that otherwise would look fine. It also looks at some debug statistics that aren't presented in the HDHR UI.

All this to say: it's very odd that we aren't detecting this kind of error. Would you be willing to upload the file somewhere that we can download it to see if there are other artifacts in the file that we could use to identify corruption to present better errors in the UI? You can email [email protected] with the link.

1 Like

You could check over at the AVS Forum in the section for your local TV reception https://www.avsforum.com/forum/45-local-hdtv-info-reception/446660-minneapolis-mn-ota.html and see if anyone else is seeing the same thing with K33LN-D. Maybe it's being transmitted that way.

I did delete the recording from the dvr, but did save a copy of the file elsewhere.
I put it on MEGA so u can download the raw file
email sent with link

@eric Did u get the email with the link?

Just an FYI on parts of posts I saved from Siliconduct support forum, since they fall off the edge of the earth after 3 months.

Your 87% Signal Strength is equvilent to -7.8dBmV

Signal Strength
100% = 0dBmV and a change of 5% is a 3dBmV difference, so every 1% change is equivilent to 0.6dBmV

A signal strength of 90% or higher is recommended for QAM operation, 80% minimum.
US Cable specs are 0dBmV +/- 12dBmV

A signal strength of 80% or higher is recommended for OTA operation, 60% minimum.
OTA ATSC minimun -30dBmV
OTA ATSC maximum isn't something that can easily be expressed, because overload is a cumulative result of everything going in, including non-TV signals like FM radio and LTE.
Non-TV signals often end up being a bigger problem than TV,since most people live a lot closer to a cell phone tower than they do a broadcast station, and most antennas are still designed to have peak gain at the frequencies that are now used for LTE.

SNQ & SEQ
For ATSC, 100% SNQ is 30dB+ SNR, 50% is 16dB SNR.
SEQ is a logarithmic scale of packets with errors in the last second, 50%=9, 0%=99+

Aiming an OTA antenna using the numbers
Use the Signal Strength for a rough idea of direction, but align the antenna for the highest Signal Quality, ignoring Signal Strength. When aimed correctly, Symbol Quality will show 100%, indicating no errors in the output. Splitters and amplifiers can introduce noise which will lower the Signal Quality, even if the Signal Strength increases.

2 Likes