[mythtv-users] [Solved] Debugging hdhomerun - can I record the same show from multiple tuners in duplicate?

[James]

> On 4 Mar 2023, at 10:39 am, Ram Ramesh <rramesh2400 at gmail.com> wrote:
> 
> On 2/26/23 22:17, Ram Ramesh wrote:
>> On 2/26/23 21:29, Stephen Worthington wrote:
>>> Recording rules do have an option to set the "Preferred Input". If
>>> you edit a recording rule, go to Schedule Options and change the
>>> second selection box from "Use Any Available Input" to the input you
>>> want it to use.  If the preferred input is not available due to using
>>> it causing a scheduling clash, I believe the scheduler will then use a
>>> different input, but I have never actually had that happen as I have
>>> too many tuners to get many clashes.
>>> 
>>> It is difficult to create two normal recording rules to record the
>>> same programme.  The only way I can think of is to use one of the API
>>> interfaces, such as the Services API, to create the second rule.  If
>>> you try from the GUI, you only get offered the option of editing the
>>> current rule, and it may be that the Services API will reject creating
>>> a second rule for the same showing.  The only way to find out would be
>>> to try.
>>> 
>>> However, you can create two manual recording rules for the same time
>>> period on the same channel.  Mythfrontend > Schedule Recordings >
>>> Manual Schedule, then create two manual recording rules with the same
>>> settings, but give them different titles.  On the second page of the
>>> settings there, use the Schedule Options to set them to use different
>>> inputs.
>>> 
>>> To see which tuner was used for any recording, in mythfrontend go to
>>> the recording and press the I (Info) key twice.  Then scroll down if
>>> necessary until you see the "Recording Input" field.  This is the
>>> capturecard.displayname field from the database.  I have manually set
>>> all of mine so that the different virtual tuners can be distinguished,
>>> but the defaults should show which physical tuner was used.
>>> 
>>> In the mythbackend.log file you can find a report line for each
>>> recording that is written at the end of the recording which will tell
>>> you the recording's status and the virtual tuner number
>>> (cardinput.cardid):
>>> 
>>> cd /var/log/mythtv
>>> grep "overall_score=" mythbackend.log
>>> 
>>> A good recording should look like this:
>>> 
>>> Feb 27 16:04:00 mypvr mythbackend: mythbackend[1446471]: I TVRecEvent
>>> tv_rec.cpp:856 (FinishedRecording) TVRec[11]:
>>> FinishedRecording(1003_2023-02-27T01:58:00Z) good
>>> recq:#012<RecordingQuality overall_score="1"
>>> key="1003_2023-02-27T01:58:00Z" continuity_error_count="0"
>>> packet_count="17913081" />
>>> 
>>> That is all one long line in the log - my email client wraps long
>>> lines.  The virtual tuner number is the [11] after "TVRec".
>>> 
>>> And this is what I got for a bad recording recently:
>>> 
>>> Feb  1 22:34:00 mypvr mythbackend: mythbackend[105007]: I TVRecEvent
>>> tv_rec.cpp:841 (FinishedRecording) TVRec[94]:
>>> FinishedRecording(10070_2023-02-01T07:29:00Z) damaged
>>> recq:#012<RecordingQuality overall_score="0.8"
>>> key="10070_2023-02-01T07:29:00Z" continuity_error_count="45265"
>>> packet_count="25817462" />
>>> 
>>> I think I had rain fade on my satellite dish that day.
>>> _______________________________________________
>>> mythtv-users mailing list
>>> mythtv-users at mythtv.org <mailto:mythtv-users at mythtv.org>
>>> http://lists.mythtv.org/mailman/listinfo/mythtv-users <http://lists.mythtv.org/mailman/listinfo/mythtv-users>
>>> http://wiki.mythtv.org/Mailing_List_etiquette <http://wiki.mythtv.org/Mailing_List_etiquette>
>>> MythTV Forums: https://forum.mythtv.org <https://forum.mythtv.org/>
>> 
>> Stephen,
>> 
>>   Thanks for the detail. I have one other question regarding this. What happens if my backend is always on and the tuner gets a new IP on DHCP? Will backend not find the tuner and give up on recording? What happens if the same happens during a recording is in progress?
>> 
>> I noticed that my broken recordings are really missing files meaning no recording was made at all. I am wondering if this has       to do with missing tuner
>> 
>> Regards
>> Ramesh
> 
> After a bit more experimentation, I realized that my second hdhomerun was on DHCP getting dynamic IPs.  My backend being on all the time had a hit and miss on the IP address resulting in missing recording completely. I remember putting my hdhomerun under static IP assignments, but it appears in some accidental editing, I made a typo in ethernet address of hdhomerun, and this made my server switch to dynamic IP. Once I fixed the issue, and rebooted relevant machines, static assignment happened and since then my backend has been consistently recording fine from this unit. So, no longer I have this issue. 
> 
> Thanks for everyone's help in guiding me to check for relevant configurations/scripts/resources in debugging this issue.

Hmmm using fixes/32. I had a single very bad recording so I went hunting to see if THAT tuner is bad:

[seagull] /var/log/mythtv [1998]% grep 'overall_score' mythbackend.*
mythbackend.20230219020210.2421.log-20230302:<RecordingQuality overall_score="0.5" key="10032_2023-03-01T13:32:00Z" continuity_error_count="224286" packet_count="15540838" />

The *only* entry is for that recording and it does not identify the tuner.
I've not gone spelunking but are there debug flags to set?

James

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20230304/e66c73fb/attachment.htm>