Changing recording quality causes sagetv to record for 10+ hours

[jrhessey]

I've been noticing 18gb - 40 gb recordings from sagetv lately and decided to sit down and try to figure out what was causing them. I checked the padding as I orginally thought that might have something to do with it. I also thought I had SRE installed, which I didn't. I changed the record quality from 2.0 (default) to 3.2 and wala, The ND -SDSU game, ND - Mich game, OSU - USC game, are now 10 + hour recordings and 6 + hour recordings (OSU game). None of them stopped recording at the scheduled stop time. I'm using an sd source. They are manual recordings. Any ideas?

[paulbeers]

Originally Posted by jrhessey

I've been noticing 18gb - 40 gb recordings from sagetv lately and decided to sit down and try to figure out what was causing them. I checked the padding as I orginally thought that might have something to do with it. I also thought I had SRE installed, which I didn't. I changed the record quality from 2.0 (default) to 3.2 and wala, The ND -SDSU game, ND - Mich game, OSU - USC game, are now 10 + hour recordings and 6 + hour recordings (OSU game). None of them stopped recording at the scheduled stop time. I'm using an sd source. They are manual recordings. Any ideas?

Did you happen to start watching the recordings while it was recording? And then not hit stop? In this case, Sage will treat the recording as live tv and continue to record.

[jrhessey]

no, I almost always let the recording go, then watch it later.

[matt91]

And to confirm, since Andy might ask, you're seeing this behavior with the stock STV? No addins at all?

[jrhessey]

no, I forgot about having the comskip integrated into sagetv. That is the comskip_payback.stvi I have in the sagetv3 folder if I remember correctly. I'm away from the box, but can get in remotely, so I'm trying to see everything that's installed by directory plus remember what I've done (over a year ago). Thanks for your help guys!!