[mythtv-users] Suddenly only recording in SD, not HD

[Karl Buckland]

On Fri, 28 Apr 2023 at 19:49, Klaas de Waal <klaas.de.waal at gmail.com> wrote:
>
>
>
> On Fri, 28 Apr 2023 at 18:30, Karl Buckland <buckland.karl at gmail.com> wrote:
>>
>> Hi,
>>
>> I have a MythTV setup that has been working very well for a few years.
>> Highlights:
>> - Proxmox, container with Ubuntu 20.04.
>> - Hauppauge dualHD USB stick (passed through), DVB/DVB-T2
>>
>> Suddenly in the last few days it has stopped being able to tune into
>> HD channels, but it can still tune to SD. When trying to tune to any
>> HD channel, I get a timeout error:
>> TuningSignalCheck: taking more than 5000 ms to get a lock. marking
>> this recording as 'Failing'.
>>
>> The timeout was 3000ms, and I tried increasing it to 5000 but it has not helped.
>>
>> When tuning in MythTV Frontend, it shows:
>> Signal 73%
>> S/N 4.7dB
>> (TLMs) Partial Lock
>>
>> Clearly, my hardware is still working. I appear to have decent signal
>> quality. I have completely restarted all hardware to eliminate any odd
>> issues there.
>>
>> I am not sure on where my line of enquiry should be to investigate
>> further? Does anyone have any suggestions?
>>
>> Thanks!
>>
>> Karl
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>> http://wiki.mythtv.org/Mailing_List_etiquette
>> MythTV Forums: https://forum.mythtv.org
>
>
> It could be that your provider has changed the signal. I suggest doing a new channel scan.
>
> Klaas.
>
>


I've done a full rescan - which definitely worked because it's renamed
some of the channels and changed their IDs. The console output shows
that it detected plenty of channels, including the HD channels I would
expect.

Unfortunately I still can't view the HD channels - but I can still
view the SD channels.

I've stopped mythtv-backend, and used dvbv5-scan and dvbv5-zap to
successfully record a few seconds of an HD channel that I can't view
through MythTV. So this would suggest that my hardware, drivers, etc
are all working fine. Signal must be fine?

Why would this have suddenly stopped working only a few days ago?

Here's the relevant log lines from my mythbackend.log:

Apr 29 15:42:51 bender mythbackend: mythbackend[534]: I TVRecEvent
tv_rec.cpp:1057 (HandleStateChange) TVRec[1]: Changing from None to
WatchingLiveTV
Apr 29 15:42:51 bender mythbackend: mythbackend[534]: I TVRecEvent
tv_rec.cpp:3662 (TuningFrequency) TVRec[1]: TuningFrequency
Apr 29 15:42:52 bender mythbackend: mythbackend[534]: I TVRecEvent
cardutil.cpp:1173 (SetDeliverySystem) CardUtil[1]: Set delivery
system: DVB-T2
Apr 29 15:42:52 bender mythbackend: mythbackend[534]: N CoreContext
autoexpire.cpp:242 (CalcParams) AutoExpire: CalcParams(): Max required
Free Space: 3.0 GB w/freq: 14 min
Apr 29 15:42:52 bender mythbackend: mythbackend[534]: N TVRecEvent
recordinginfo.cpp:678 (ApplyRecordRecGroupChange)
ApplyRecordRecGroupChange: LiveTV to LiveTV (2)
Apr 29 15:42:59 bender mythbackend: mythbackend[534]: E TVRecEvent
tv_rec.cpp:3967 (TuningSignalCheck) TVRec[1]: TuningSignalCheck: Hit
pre-fail timeout
Apr 29 15:43:02 bender mythbackend: mythbackend[534]: W TVRecEvent
tv_rec.cpp:3995 (TuningSignalCheck) TVRec[1]: TuningSignalCheck:
taking more than 10000 ms to get a lock. marking this recording as
'Failing'.
Apr 29 15:43:02 bender mythbackend: mythbackend[534]: W TVRecEvent
tv_rec.cpp:4000 (TuningSignalCheck) TVRec[1]: See 'Tuning timeout' in
mythtv-setup for this input
Apr 29 15:43:04 bender mythbackend: mythbackend[534]: I TVRecEvent
tv_rec.cpp:1057 (HandleStateChange) TVRec[1]: Changing from
WatchingLiveTV to None
Apr 29 15:43:04 bender mythbackend: mythbackend[534]: I
MythSocketThread(84) mainserver.cpp:7858 (connectionClosed) Playback
sock(56445bd4f1a0) 'bender' disconnected

Any further suggestions or areas to investigate please?