Bug #5012
Services on 195.028MHz stutering big time
0%
Description
Here is Portland, OR-USA, OPB is serviced on 195.028MHz. It works great with my MythTV installation on the same system. No issues at all. TVHeadend stutters 100% of the time. It stutters both on HTSP and HTTP. Below are the errors
2018-03-19 20:45:10.356 mpegts: 195.028MHz in DualHaup - tuning on LG Electronics LGDT3306A VSB/QAM Frontend #0 : ATSC-T #0
2018-03-19 20:45:10.690 subscription: 000D: "HTTP" subscribing to service "DualHaup/195.028MHz/OPB-HD Channel", weight: 100, adapter: "LG Electronics LGDT3306A VSB/QAM Frontend #0 : ATSC-T #0", network: "DualHaup", mux: "195.028MHz", profile="pass", hostname="192.168.1.14", client="VLC/2.2.8 LibVLC/2.2.8"
2018-03-19 20:45:14.364 TS: DualHaup/195.028MHz/OPB-HD Channel: AC3 #52 Continuity counter error (total 1)
#49 Continuity counter error (total 1)
2018-03-19 20:45:26.185 TS: DualHaup/195.028MHz/OPB-HD Channel: MPEG2VIDEO
2018-03-19 20:45:26.186 TS: DualHaup/195.028MHz/OPB-HD Channel: AC3 #52 Continuity counter error (total 2)
#53 Continuity counter error (total 1)
2018-03-19 20:45:26.186 TS: DualHaup/195.028MHz/OPB-HD Channel: AC3
2018-03-19 20:45:48.969 subscription: 000D: "HTTP" unsubscribing, hostname="192.168.1.14", client="VLC/2.2.8 LibVLC/2.2.8"
History
Updated by Jaroslav Kysela over 6 years ago
Those errors usually mean that the input stream has some data lost. You may try to increase the receive buffer (in the adapter tree / tuner settings).
Updated by NW User over 6 years ago
Hi. I had played with that value. I had it set to 1504000. I just increased it to max value of 1880000. Yet no use. I swear that this was the only channel with zero issues on MythTV. I switched to TVH to get the rest of the channels fixed (plus the authentication system). I am 100% confident that the reception is perfect with no issues in input stream. Would you have a, say, ffmpeg command to record the input stream for 1 minute. Maybe that will give us some info into why TVH is having issues.
Updated by Jaroslav Kysela over 6 years ago
Upload here (or somewhere on net) one minute for the complete .ts stream - use 'play' URL in the mux grid and wget or curl tools to save the stream to a file.
Updated by NW User over 6 years ago
Hi Jaroslav,
I think what I am saying now might sound like Voodoo magic. I was trying to collect the ts using wget yesterday night. After recording a minute of the stream using wget I noticed that I no longer had issues playing OPB or any channel on my Kodi/PiZero. I went to bed and tried the same thing this morning and bingo!, I could recreate the same issue twice. Basically after bootup, OPB will stutter but when I record the stream using wget for, say, a minute, it no longer has any issues. I tried it once again this evening and I could recreate it once more. I am now running 4.2.5-50~g1997b348a~xenial and have this dirty fix on reboot in crontab. Would you know what is going on?
#!/bin/sh
sleep 20
wget http://192.168.1.175:9981/play/stream/mux/b53ac0caffda711efcca0686b828e596$
WGETPID=$!
sleep 20
kill $WGETPID
rm -f b53ac0caffda711efcca0686b828e596?title=195.028MHz%20%2F%20DualHaup
Updated by NW User over 6 years ago
Here is a stream from OPB Mux. There are 4 services on this mux. I dont know if all 4 have been recorded in this stream.
Updated by Jaroslav Kysela over 6 years ago
Nothing is attached. But it does seem that it may be a driver issue if wget of the full mux fixes the issue for you.
Updated by NW User over 6 years ago
I tried different browsers but I am having issues attaching the file. Do you think I can put a post-run script into TVH to run wget rather than crontab? I tried updating my driver for my DualHaup and still it doesnt seem to help. With the cron script however, I dont have any issues with viewing OPB.
Updated by Jaroslav Kysela over 6 years ago
- Status changed from New to Invalid
You can try anything. I would also check the kernel module parameters for the driver (full mux reception) and maybe, the issue might have something related to the USB stack settings (kernel) - I assume that your hardware is an USB device. I believe that this bug is not tvh related.