<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><br><br><div><br>> > <br>> > I tried it yet again and what you're saying is true for 0.27 but not true in trunk as of Feb 27.<br>> > <br>> > In all cases I did "record this showing" for shows broadcast at the same day/time on two different channels (as defined by callsign) and having specific program ids (eg, ending in non-zero digits). In 0.27 the rule affected only the channel I selected while in trunk it scheduled the channel I selected and the other channel showed "single recording - other channel". That "other showing" thing prevents me from creating a second "record this showing" rule as a backup which is my complaint.<br><br>I've scheduled a pair of recordings on fixes/0.27. Both have the same non generic programid. As George says using a 'record only this showing' rule with default options on the first showing did not appear on the second recording and I was therefore able to schedule a second 'record only this showing' rule on the second recording. I will report back this evening as to whether the second showing does actually record or not. (I am on Australian DVB-T).<br><br>At this stage it is reporting that the second showing will record.<br><br>mysql> select recordid, type, title, subtitle, chanid, starttime, programid, dupmethod from record where title="Thomas and Friends";<br>+----------+------+--------------------+-------------------+--------+-----------+----------------+-----------+<br>| recordid | type | title | subtitle | chanid | starttime | programid | dupmethod |<br>+----------+------+--------------------+-------------------+--------+-----------+----------------+-----------+<br>| 1296 | 1 | Thomas And Friends | Thomas' Crazy Day | 1022 | 21:30:00 | EP22482981114e | 6 |<br>| 1297 | 1 | Thomas And Friends | Thomas' Crazy Day | 1022 | 03:00:00 | EP22482981114e | 6 |<br>+----------+------+--------------------+-------------------+--------+-----------+----------------+-----------+<br>2 rows in set (0.00 sec)<br><br><br>> Anyway, I seriously doubt it's a change in the scheduler proper. I'm<br>> more inclined to believe it's a bad reporting problem dealing with the<br>> "other channel" reporting logic, which was changed by another<br>> developer recently.<br>> <br>> David<br>> <br><br>That was my understanding of the earlier comment in this thread from Mike, that the display was reporting that it would work when in fact it wouldn't work. Will see later this evening.<br></div> </div></body>
</html>