[mythtv-users] Frontend/backend status shows pgm recording but it's not

Mon Feb 3 22:01:05 UTC 2025

On Mon, 3 Feb 2025 at 22:15, Ian Evans <dheianevans at gmail.com> wrote:

> On Mon, Feb 3, 2025, 4:02 p.m. Peter Bennett <pb.mythtv at gmail.com> wrote:
>
>>
>> On 2/3/25 14:14, Ian Evans wrote:
>>
>> On Mon, Feb 3, 2025 at 12:22 AM Ian Evans <dheianevans at gmail.com> wrote:
>>
>>> MythTV 34. Had an issue with the Grammys tonight that also happened with
>>> one of the NFL playoff games a couple of weeks ago.
>>>
>>> Was recording the Grammys. Had extra time on the end. When I got back to
>>> the MythTV just before midnight, both Leanfront and the web app status page
>>> said the show was still recording as I had added extra time and it would
>>> end at 1230am. I hit stop recording. I went to check the recording and it
>>> was only 81 minutes long, far short of the 3+ hours it said it had been
>>> recording. The recording drive had over 120 gigs of free space. It wasn't
>>> showing up as damaged. Why would the backend status be saying it was still
>>> recording if it had stopped 2 hours earlier?
>>>
>>> Heading to bed soon, so I can check logs in the morning, but anything
>>> jump to mind?
>>>
>>> Thanks.
>>>
>>
>> Had some time to look at the logs. To reiterate/clarify: Recording was
>> set from 19:59 to 00:30. As stated, when I went to hit "Stop Recording" in
>> the PC frontend, the recording was showing as green and still recording.
>> Web app and Leanfront both showed it was still recording at that point. I
>> hit Stop Recording. The PC frontend now showed the show as Yellow (damaged).
>>
>> Instead of 3+ hours It had recorded only 1 hr and 21 minutes. Looking at
>> the logs for around that time (21:15 to 21:30), the mythbackend log only
>> shows the every 14 minute free space tester:
>>
>> 2025-02-02T21:15:18.784347-05:00 bhmf mythbackend: mythbackend[2571]: N
>> Expire autoexpire.cpp:247 (CalcParams) AutoExpire: CalcParams(): Max
>> required Free Spa
>> ce: 3.0 GB w/freq: 14 min
>> 2025-02-02T21:29:18.763079-05:00 bhmf mythbackend: mythbackend[2571]: N
>> Expire autoexpire.cpp:247 (CalcParams) AutoExpire: CalcParams(): Max
>> required Free Spa
>> ce: 3.0 GB w/freq: 14 min
>> 2025-02-02T21:43:18.792261-05:00 bhmf mythbackend: mythbackend[2571]: N
>> Expire autoexpire.cpp:247 (CalcParams) AutoExpire: CalcParams(): Max
>> required Free Spa
>> ce: 3.0 GB w/freq: 14 min
>>
>> The recording drive has 160GB free. The logs didn't show (is it supposed
>> to show?) any info that the tuner had failed.
>>
>> This is the log after I hit Stop Recording:
>>
>> 2025-02-02T23:53:12.968495-05:00 bhmf mythbackend: mythbackend[2571]: N
>> RecThread recorderbase.cpp:492 (FinishRecording) Finished Recording:
>> Containe
>>        │ r: MPEG2-TS Video Codec: mpeg2video (1920x1080 A/R: 3 29.97fps)
>> Audio Codec: ac3
>> 3236   │ 2025-02-02T23:53:12.968608-05:00 bhmf mythbackend:
>> mythbackend[2571]: I TVRecEvent tv_rec.cpp:867 (FinishedRecording)
>> TVRec[17]: FinishedRecording(20
>>        │ 401_2025-02-03T00:59:00Z) damaged recq:#012<RecordingQuality
>> overall_score="0" key="20401_2025-02-03T00:59:00Z"
>> continuity_error_count="241" packet_c
>>        │ ount="28706117">#012    <Gap start="2025-02-03T02:20:01Z"
>> end="2025-02-03T04:30:00Z" duration="7798" />#012</RecordingQuality>
>> 3237   │ 2025-02-02T23:53:12.968727-05:00 bhmf mythbackend:
>> mythbackend[2571]: I CoreContext scheduler.cpp:674 (UpdateRecStatus)
>> Updating status for "The 67th
>>        │  Annual Grammy Awards" on cardid [17] (Recording => Recorded)
>> 3238   │ 2025-02-02T23:53:12.968832-05:00 bhmf mythbackend:
>> mythbackend[2571]: I Scheduler scheduler.cpp:2353 (HandleReschedule)
>> Reschedule requested for CHEC
>>        │ K -3 1200 0 UpdateRecStatus1 | The 67th Annual Grammy Awards |
>>  | Trevor Noah hosts festivities at the Crypto.com arena in Los Angeles
>> honoring excel
>>        │ lence in the recording industry as voted on by the Recording
>> Academy's membership body of music makers, who represent all genres and
>> creative discipl
>>        │ ines, including recording artists, songwriters, producers,
>> mixers and engineers. Beyoncé leads the pack with 11 nominations --
>> including album of the
>>        │  year -- bringing her up to a record career total of 99
>> nominations, followed by Kendrick Lamar, Charli XCX and Billie Eilish with
>> seven nods each. |
>>        │  SH051450660000
>>
>> Hope that gives some additional info.
>>
>> _______________________________________________
>>
>> You can see there are two hours missing from the recording, a gap from
>> 02:20 to 04:30, 7798 seconds. The tuner lost the signal or failed in some
>> way. If you has not stopped the recording before the end it should have
>> shown as damaged. I suspect that stopping the recording removes the damaged
>> indicator.
>>
>
> On my system, it did show as damaged after it was stopped.
>
>

> I guess I've been lucky with most recordings, but I was a little surprised
> that there was no indication in the logs. I thought they'd show errors
> about lost tuner or something.
>

Purely from memory, the recording process works a bit like this. The tuner
spits out a chunk of bytes to the recording subsystem; the bytes are
written to disk and the recording subsystem waits for the next chunk of
bytes. The next chunk usually comes a short time later. Think of 50
milliseconds or so. While waiting for the next chunk nothing happens, but
the system is still in the state "recording".
In your case it seems that there has been no data coming from the tuner for
two hours, but the system stays in state "recording" until the scheduled
end time is reached or until the recording is manually stopped. For the
system it does not make a difference if the time interval is 50
milliseconds or one hour or so.
The way MythTV works is that the signal strength is only observed on the
initial tuning; once the recording has started the signal strength is not
measured or monitored anymore.
So it is possible that you might have a bad signal which halfway the
recording gets a lot worse. It is also possible that some of your hardware
is slowly dying.
I would suggest first checking your cabling and signals and then make lots
of long recordings, just for testing.

Klaas.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20250203/5c4d5304/attachment-0001.htm>