I'm having some strange (some of it being repeatable) behavior happening when I've been padding recording time. I have the following scenario occur for the past 2 weeks. I have a season pass for New Amsterdam on FoxHD (scheduled at 9:00-10:00), a season pass for Medium on NBCHD (10:00-11:00) as well as a higher-priority wish list for Hockey/Penguins, which is currently scheduled as a recording from 7:00-9:30 on VS-HD. My first problem occurs when I go to edit the Pens game to pad to record an extra 30 minutes (to record from 7:00-10:00). There are no other overlapping recordings going on at 9:00-10:00, and in fact, New Amsterdam is in my ToDo list. After updating the record time, ComcastTivo incorrectly insists that it needs to cancel the New Amsterdam recording, even though the tuner is free. I let it do so, and it disappears from my ToDo list. I then have gone back in and manually scheduled a recording for New Amsterdam, which shows up, without conflict, in my todo list, with the Pens game still scheduled for 3 hours. New Amsterdam stays in the todo list for a day, then disappears (I changed the recording last Friday night). I go back in and rescheduled New Amsterdam again, and it stayed for a day, then disappeared. I have not yet checked ComcastTivo to see if its disappeared again (I have a feeling it has something to do with getting new guide data). The same occurred last week as well when the Pens were on VS-HD as well.
Has anyone seen editing recording padding time cancel other recordings on an idle tuner?
One other thing that I have noticed, but is not completely reproducible, with padded recordings is that sometimes the padded portion isn't recorded. The recording shows up as being padded, but just ends (previous weeks Pens games on NBC, scheduled for 2.5 hours, extended to 3 hours, have had a 3 hour progress bar, but only recorded 2.5 hours). I forget whether they state partial recordings in the Tivo recordings screen. I know that it has something to do with watching the game in-progress but delayed, but have not figured out the exact scenario that led to this issue.