Opened 6 years ago

Last modified 6 years ago

#11543 new Bug Report - General

Recordings Never Leave "Currently Recording" Status if Watched Live

Reported by: Knnniggett <knnniggett@…> Owned by:
Priority: minor Milestone: unknown
Component: MythTV - General Version: 0.26-fixes
Severity: medium Keywords:
Cc: Ticket locked: yes

Description

Description: If a show in the recording schedule is watched live, then the recoding will never leave the "Currently Recording" status as shown on MythWeb. The recording file exists on the hard drive and can be downloaded through MythWeb. However, it never appears in the list of recorded programs on the Frontend. If the Backend is restarted, the recording disappears altogether.

Reproducible: Always

Steps to Reproduce: Watch a show live that is also in the recording schedule

Additional information: I've noticed that, when watching a show live that is also being recorded, both tuners on the HDHomerun will be enabled and on the same channel. Perhaps this is confusing the system. I do not know if this issue is specific to HDHomerun's or just any system that has multiple tuners.

This issue has been occurring for several months, possible since the upgrade from 0.25 to 0.26. Since I have not found any relevant errors in any log file, I'm at a loss as to what I can provide to help troubleshoot this issue. Please advise.

System:
Mythbuntu 12.04 + latest updates
Mythtv 0.26 + latest fixes
HDHomerun with latest firmware

Attachments (5)

mythbackend.version.txt (875 bytes) - added by Knnniggett <knnniggett@…> 6 years ago.
mythfrontend.version.txt (909 bytes) - added by Knnniggett <knnniggett@…> 6 years ago.
mythfrontend.log (365.1 KB) - added by Knnniggett <knnniggett@…> 6 years ago.
mythfrontend.version.2.txt (909 bytes) - added by Knnniggett <knnniggett@…> 6 years ago.
mythbackend.log (861.8 KB) - added by Knnniggett <knnniggett@…> 6 years ago.

Download all attachments as: .zip

Change History (9)

Changed 6 years ago by Knnniggett <knnniggett@…>

Attachment: mythbackend.version.txt added

Changed 6 years ago by Knnniggett <knnniggett@…>

Attachment: mythfrontend.version.txt added

Changed 6 years ago by Knnniggett <knnniggett@…>

Attachment: mythfrontend.log added

Changed 6 years ago by Knnniggett <knnniggett@…>

Attachment: mythfrontend.version.2.txt added

comment:1 Changed 6 years ago by Knnniggett <knnniggett@…>

Forgot to mention. When looking at the log files, two examples of this occur on May 16's showing of the two episodes of the Big Bang Theory at 7pm and 7:30pm.

Changed 6 years ago by Knnniggett <knnniggett@…>

Attachment: mythbackend.log added

comment:2 Changed 6 years ago by matt@…

I would like to "second" this issue. It happens on my system and is very annoying.

comment:3 Changed 6 years ago by Raymond Wagner

Ticket locked: set

Please read the TicketHowTo. "Metoos" result in tickets becoming locked.

comment:4 Changed 6 years ago by stuartm

Note that 'Locked' is not the same thing as 'Closed', it just means that you can't comment on the ticket any longer. We ask that people only comment when they are providing solid information useful in finding or fixing the bug, and if in any doubt to discuss it on the mailings lists first.

Every comment without value, whether it's a 'me too' or wild conjecture, just adds to the clutter that developers have to wade through and makes it less, not more, likely that the problem will be addressed quickly.

Note: See TracTickets for help on using tickets.