search

rebhichaouki / sagetv-addons

Automatically exported from code.google.com/p/sagetv-addons
0 stars 0 forks source link

Recording Conflits (Unresolved) Event #295

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
A while ago I had requested that a separate "Recording Conflicts (Unresolved)" 
event to be added and it was. The problem is that I don't think it has ever 
worked. I've had unresolved recording conflicts for a long time, including 
right now, and I've never received an alert from this new event.

If you would like me to provide any logs, let me know. I will subscribe to this 
issue.

Original issue reported on code.google.com by s%mkenny...@gtempaccount.com on 16 May 2011 at 1:44

GoogleCodeExporter commented 9 years ago 
I should add that I am running the latest version of SageAlert available on the 
SageTV plugin repo.

Original comment by s%mkenny...@gtempaccount.com on 16 May 2011 at 1:45

GoogleCodeExporter commented 9 years ago 
I need to see the sagealert.log file.  I need the time frame for when the 
unresolved conflict first occurred.  Seems to me I've had this event triggered 
in my installation, but your logs should answer that question rather easily.

Please either prune the log file before posting or be sure to tell me what 
timestamp I should be looking for in the file.

Original comment by de...@battams.ca on 16 May 2011 at 3:27

GoogleCodeExporter commented 9 years ago 
Unfortunately I won't be able to pinpoint the exact time the conflict started 
to appear... But I can give you a rough time frame.

1) Yesterday between 6 pm and 8:30 pm CST I made some changes to my tuners and 
channel setup which caused the conflict. I would have also restarted Sage a few 
times during the process. I've attached the portion of the log between that 
time (see sagealert.log). The conflict that I had in Sage was for "The Voice" 
and "Hoarders". I've since resolved them so the wife doesn't miss her shows!

2) This morning while I was at work my wife scheduled some manual recordings 
between 10 am and 11:30 am CST, which caused more conflicts. See sagealert2.log 
for these.

In both instances I can see the event ConflictStatusChanged keeps on firing 
about when the conflicts happen, but I do not have anything associated with 
"Recording Conflicts" in the GUI, only "Recording Conflicts (Unresolved)". A 
quick look I don't see an event for unresolved conflicts.

Original comment by s%mkenny...@gtempaccount.com on 17 May 2011 at 12:06

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by s%mkenny...@gtempaccount.com on 17 May 2011 at 12:07

Attachments:

GoogleCodeExporter commented 9 years ago 
I see the problem.  The fix is rather trivial, I just need to find an hour or 
two one evening to fix it.  I'll get a fix into the plugin repository by week's 
end.

Original comment by de...@battams.ca on 17 May 2011 at 12:31

GoogleCodeExporter commented 9 years ago 
That's good that it was easy to find. Don't stress yourself out to fix it, I 
just wanted to mention it before I forgot again.

Original comment by s%mkenny...@gtempaccount.com on 17 May 2011 at 1:13

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision r1530.

Original comment by de...@battams.ca on 17 May 2011 at 6:10

GoogleCodeExporter commented 9 years ago

Original comment by de...@battams.ca on 9 Apr 2013 at 2:11