Sage won't stop recording

[Tiki]

I had a very strange problem with Sage today. When I opened Sage this morning, I noticed that it was reporting about 150GB less free space than it had before I went to bed last night. I spent a bunch of time trying to figure out what could have used so much space. I eventually found that I had one recording from last night that Sage was reporting as 75GB.

I tried to play the file, and it played OK, but I noticed there was a red line in the middle of the recording time line, indicating a gap in the recording. I went back to the recording details screen and saw that it reported two file segments.

I looked in the folder on my hard drive and found that the two file segments - the one labeled -0 was 75GB and growing (the Windows date stamp for this one was 3/23/2017 09:55pm). The one labeled -1 was 6GB (the Windows date stamp for this one was 3/23/2017 10:03pm).

It looks like Sage thought the recording failed, even though it had not, so it started a new recording on a different tuner.

I checked the info screen in Sage and it shows that no recordings are in progress. However, one of the lights on my HDHR-Prime is lit, indicating a tuner is active. I'm still using SageDCT to control the Prime, by the way.

I went through the Sage Logs and looked for anything unusual around 10:03pm on 3/23. I found a bunch of entries starting at 22:03:05.110 that said: Seeker removing dead encoder, for all my Primes. These were followed at 22:03:20.649 with a bunch of entries like: Seeker adding new encoder, for all of my Primes.

Has anyone seen anything like this before? Anything I should be looking at? I guess I will probably have to unplug my Prime to get it to stop recording.

I'm running Sage v9.0.12.506 on Windows 7, by the way.

[graywolf]

I've had it happen a couple times over the years on v6
Could not kill the recording
Had to stop sagetv service then restart it.
No idea why it happened

[BobPhoenix]

I have had something similar happen as well in v7. Had a 250GB recording file. Did not have a split file and it was on an HDPVR file.

[Tiki]

So, I'm wondering the best way to recover from this.

Right now Sage thinks it has 2 segments for this show: Segment 0 is 3 minutes plus padding, Segment 1 is 57 minutes plus padding.

Sage is correct about Segment 1, but in reality, Segment 0 is 12 hours long.

What I would like to do is delete Segment 1 (since it is incomplete and missing the beginning of the recording), the edit Segment 0 to trim off the extra 11 hours. However, I'm afraid that if I do this, Sage will think it is missing the second segment and either won't play the recording or will have a screwed-up timeline and transport controls (skip, etc.) may not work correctly.

How can I do this so that Sage still recognizes the show and plays it back correctly?

[alfi33]

Originally Posted by Tiki

So, I'm wondering the best way to recover from this.

Right now Sage thinks it has 2 segments for this show: Segment 0 is 3 minutes plus padding, Segment 1 is 57 minutes plus padding.

Sage is correct about Segment 1, but in reality, Segment 0 is 12 hours long.

What I would like to do is delete Segment 1 (since it is incomplete and missing the beginning of the recording), the edit Segment 0 to trim off the extra 11 hours. However, I'm afraid that if I do this, Sage will think it is missing the second segment and either won't play the recording or will have a screwed-up timeline and transport controls (skip, etc.) may not work correctly.

How can I do this so that Sage still recognizes the show and plays it back correctly?

This has never happened to me but I would think the easiest thing to do would be to (sort of) start over. Assuming you can't just record another airing, backup Segment 0 then have Sage delete both segments. Trim your backup of Segment 0 appropriately then import the file back into Sage. Mark the import as a recording if desired.

[KryptoNyte]

You could probably also test it by stopping the SageTV service and then moving the problem files out of Sage's recognized directories, do the fix, alter the filename if necessary, and move the repaired file back into the recording directory to see how Sage picks it up.

[wnjj]

I'm not sure but I think Sage automatically handles segments, outside its DB. You can probably make one file with the '0' name and be fine. Keep the originals before you try.

EDIT: Scratch that. I see that number of segments is stored with the airing in the DB. Sage may still correct it if the files don't match the DB. It doesn't hurt to try.

[waynedunham]

I have seen it on rare occasions in SageTV as well. I just moved to SageTV V9 so I haven't seen it yet, but did run into it a few times on V7.

The other posters are correct in that you can stop the service (may take longer than normal since SageTV Service "thinks" it is recording something) and then restart the service.
Usually when it happened to me I would just stop the service and take that opportunity to reboot the computer as well as power cycle all my external tuners so that everything started fresh.

Then you can go into your recordings, or even possibly the import directory where it may be instead, and view and/or delete them there. Don't forget to reschedule a later airing if you didn't get all of that recording.