[mythtv-users] Colors in Mythbuntu theme

[Stephen Worthington]

On Sat, 11 May 2019 09:47:21 -0700, you wrote:

>I recently added a HDHomerun to my setup (in addition to an HDPVR).  Now
>some of the recordings in the episodes list appear in yellow.  Does anyone
>know what this means?  The recordings play.  I was thinking it might
>indicate the input used for the recording, but it seems it does not.

A yellow recording in the Mythbuntu theme, as in MythCentre Wide,
indicates a damaged recording.  In the database, this is a 'DAMAGED'
flag in the recordedprogram.videoprop field.  It indicates that when
the recording finished, mythbackend calculated the level of damage was
over a certain limit.  Not being in yellow does not guarantee that a
recording is undamaged - it only means that any damage is less than
the limit, so is small.  Mythbackend can log information about the
damage to a recording if it is started with the "-v record" flag. Then
you get messages like this in mythbackend.log at the end of each
recording:

May  2 00:09:00 mypvr mythbackend: mythbackend[2691]: I TVRecEvent
tv_rec.cpp:863 (FinishedRecording) TVRec[2]:
FinishedRecording(1013_2019-05-01T09:30:00Z) good
recq:<RecordingQuality overall_score="0.992903"
key="1013_2019-05-01T09:30:00Z" countinuity_error_count="0"
packet_count="44745673">#012    <Gap start="2019-05-01T09:30:00Z"
end="2019-05-01T09:30:22Z" duration="22" />#012</RecordingQuality>

That message shows a 22 second gap in the recording at the start of
the recording - for some reason, the tuner did not start up
immediately.  The calculated level of damage is low, so it is not
marked as DAMAGED.

This one has too much damage and is marked as DAMAGED:

Apr 15 00:25:32 mypvr mythbackend: mythbackend[2627]: I TVRecEvent
tv_rec.cpp:863 (FinishedRecording) TVRec[90]:
FinishedRecording(10007_2019-04-14T12:24:00Z) damaged
recq:<RecordingQuality overall_score="0.7"
key="10007_2019-04-14T12:24:00Z" countinuity_error_count="0"
packet_count="155517">#012    <Gap start="2019-04-14T12:24:00Z"
end="2019-04-14T12:24:18Z" duration="18" />#012</RecordingQuality>

This is what happens when you use Live TV, but stop before the end
time for the programme:

Mar 14 09:49:01 mypvr mythbackend: mythbackend[2640]: I TVRecEvent
tv_rec.cpp:863 (FinishedRecording) TVRec[92]:
FinishedRecording(10005_2019-03-13T20:19:00Z) damaged
recq:<RecordingQuality overall_score="0"
key="10005_2019-03-13T20:19:00Z" countinuity_error_count="0"
packet_count="5421">#012    <Gap start="2019-03-13T20:19:05Z"
end="2019-03-13T20:45:00Z" duration="1554" />#012</RecordingQuality>

Mythbackend thinks that the recording is massively damaged as it stops
1554 seconds before the scheduled end of that programme, so it gives
it an overall quality score of 0.  But since you stopped it manually,
it really should not do that.

When using -v record, to find the messages about damaged recordings in
the log, you can use this command:

grep -a "overall_score=\"0" /var/log/mythtv/mythbackend.log