[mythtv] conflict resolution

Bruce Markey bjm at lvcm.com
Thu Nov 6 17:17:19 EST 2003


David Engel wrote:
> On Thu, Nov 06, 2003 at 10:35:57AM -0800, Bruce Markey wrote:
> 
>>I've been trying some other cases that could potentially
>>cause problems and it seems to give reasonable results in
>>most cases. Not always what I'd expect but reasonable =).
> 
> 
> Could you elaborate, please.  I'm sure some idiosyncrasies will be
> found once this gets wider use.

Well I was deliberately vague because I didn't see anything
else as being a "bug" that needed fixing. I was trying to do
bad things like setting the max episodes to 4 then marking 6
of them to "record anyway". Somewhere in this test it picked
different episodes than I would have guessed but it didn't
break so what happens when you do the wrong thing is moot.

I was trying to trick it by switching something between record
and don't record while changing other things around it. I
noticed that the item would simply change the type in the
recordoverride table and do the right thing. However, I
there isn't a way to clear something from the override table
(other than removing the recurring title). Once you set an
override you can only switch between override do and override
don't. This is not a problem that would need a fix. It won't
be a problem in practice and I believe any interface change
to address this would be more confusing than helpful.

>>PrintList and the conflicts page still show extra showings
>>of the episodes as not recording.  I verified that recorddups
>>does mark all showings to be recorded with the same database
>>but unpatched CVS.
> 
> 
> Interesting, I don't see how the old scheduler would do that unless
> conflicts were involved.  Regardless, once a showing was recorded and
> kept in the recorded table, the old scheduler would then suppress
> future showings so the end result should be the same as with the new
> scheduler.

Hum, I must not have been clear about where the bug is and
didn't convinced you to try the test case. Let me try again =).

In the record table there is a field called "recorddups". The
value is changed via a checkbox on the Advanced Options page
marked "Allow recording even if duplicate episode". The purpose
of this is for situations where the user believes all showings
should be recorded without checking for duplicate descriptions.
This feature has worked correctly for the past few months but
doesn't work with the override patch.

1) compile unpatched CVS in one directory and compile CVS
CVS plus the override patch in another directory.

2) "make install" the unpatched version.

3) run "mythbackend -v schedule" and "mythfrontend"

4) From mythfrontend, go to TV->Schedule Recordings->Program
Finder. Find "Nova". In the right column press "I". For 
"Schedule:" choose "Record this program whenever it's shown
anywhere". Press Enter.

5) Look at the console output of mythbackend. One of each
episode is marked for record (if not, find another show that
has multiple showings of an episode in your listings).

6) Return to the "Nova" Advanced Options page. Check the
box marked "Allow recording even if duplicate episode".
Press Enter.

7) Look at the console output of mythbackend. Every showing
should be marked for record.

9) Exit mythfrontend and kill mythbackend.

10) "make install" the patched version.

11) run "mythbackend -v schedule" and "mythfrontend".

12) Look at the console output of mythbackend. One of each
"Nova" episode is marked for record. All other showings are
marked as N=4 (however, they should all be marked to record
because the "recorddups" flag should be set at this point).

13) Return to the "Nova" Advanced Options page. Toggle the
box marked "Allow recording even if duplicate episode".
Press Enter.

14) Look at the console output of mythbackend. One of each
episode is marked for record. All other showings are marked
as N=4 regardless of the state of "recorddups".

--  bjm



More information about the mythtv-dev mailing list