Future shows appearing in Recorded TV?

[leadfoot]

I have a V6.6.2.218 SageTV server. I have 2 HD-200 extenders and a HD-300 extender. I am running SageMC version 6.3.9b.

Recently something strange has been happening. A week or so ago a show (Santa Claus Is Comin' To Town) appeared in the Recorded TV list that isn't supposed to be broadcast until sometime in the future! It is supposed to air on 12/12/2011. When I went into program info and looked at the extra info that shows which file contains the show, the filename was an old "Terminator: The Sarah Connor Chronicles" show that was archived on a unraid server where I store old recordings! If I played it, I got the "Terminator: The Sarah Connor Chronicles" episode. I went into Recorded TV and looked for that particular episode of "Terminator: The Sarah Connor Chronicles"...it was no longer listed in Recorded TV. It looks like this upcoming show (Santa Claus Is Comin' To Town) somehow usurped the "Terminator: The Sarah Connor Chronicles" episode. I didn't really care about the "Terminator: The Sarah Connor Chronicles" episode, so I deleted the "Santa Claus Is Comin' To Town" usurper (I had to go to the stock V6 STV to do it) and chalked it up to some weird showid glitch.

Yesterday a couple more shows appeared in the Recorded TV list with the same symptoms. Now I'm a little worried that my wiz.bin might be corrupted somehow. Has anyone ever seen/heard of anything like this? Any suggestions on what to do?

Thanks for listening
Ron

[BobPhoenix]

Originally Posted by leadfoot

I have a V6.6.2.218 SageTV server. I have 2 HD-200 extenders and a HD-300 extender. I am running SageMC version 6.3.9b.

Recently something strange has been happening. A week or so ago a show (Santa Claus Is Comin' To Town) appeared in the Recorded TV list that isn't supposed to be broadcast until sometime in the future! It is supposed to air on 12/12/2011. When I went into program info and looked at the extra info that shows which file contains the show, the filename was an old "Terminator: The Sarah Connor Chronicles" show that was archived on a unraid server where I store old recordings! If I played it, I got the "Terminator: The Sarah Connor Chronicles" episode. I went into Recorded TV and looked for that particular episode of "Terminator: The Sarah Connor Chronicles"...it was no longer listed in Recorded TV. It looks like this upcoming show (Santa Claus Is Comin' To Town) somehow usurped the "Terminator: The Sarah Connor Chronicles" episode. I didn't really care about the "Terminator: The Sarah Connor Chronicles" episode, so I deleted the "Santa Claus Is Comin' To Town" usurper (I had to go to the stock V6 STV to do it) and chalked it up to some weird showid glitch.

Yesterday a couple more shows appeared in the Recorded TV list with the same symptoms. Now I'm a little worried that my wiz.bin might be corrupted somehow. Has anyone ever seen/heard of anything like this? Any suggestions on what to do?

Thanks for listening
Ron

It is probably NOT corrupted. The ID number in the database (Wiz.Bin) has been reused by SageTV. I believe the upper ID limit was increased in V7 compared with V6. I got that allot on earlier versions of SageTV. What I would suggest is that you look in the WEB app for the now disconnected "Terminator: The Sarah Connor Chronicles" airing and lookup the airing ID. I will bet that the number is different from the one in the file name of the media file. If that is true than you might be able to reconnect them by just renaming the media file with the airing ID that the WEB app displays. Note you need to shut SageTV down before renaming the file and I would keep a copy of the file somewhere else with the old name too. Then if SageTV thinks it is a corrupt recording or a partial and deletes it you will still have a backup. Sage will likely reconnect the renamed file with the correct episode after restarting SageTV. If you use Service mode that is what need to be stopped for the rename.

[razrsharpe]

Sounds like it could be the bug talked about in this post. Basically Sage assigns a unique ID to each mediafile and prior to one of the early betas of V7 sage reset the counter at some lowish value that you could hit with normal use. So what could be happening is sage sees that old ID and it is associating that OLD ID with the new information.... NO idea if that is really what is happening or not but if it is the only way to fix it is to upgrade to v7.

EDIT: Looks like bob beat me to it...

[WellThen]

Originally Posted by razrsharpe

Sounds like it could be the bug talked about in this post. Basically Sage assigns a unique ID to each mediafile and prior to one of the early betas of V7 sage reset the counter at some lowish value that you could hit with normal use. So what could be happening is sage sees that old ID and it is associating that OLD ID with the new information.... NO idea if that is really what is happening or not but if it is the only way to fix it is to upgrade to v7.

EDIT: Looks like bob beat me to it...

Not sure if the fix Bob suggests will work, but I don't agree that this is resolved by going to Sage 7. I've previously reported this issue here and something related here. And I was using Sage 7 for both of these occurrences.

[razrsharpe]

Originally Posted by WellThen

Not sure if the fix Bob suggests will work, but I don't agree that this is resolved by going to Sage 7. I've previously reported this issue here and something related here. And I was using Sage 7 for both of these occurrences.

If the problem is the wiz.bin reseting the unique ID count and the software getting confused then upgrading to win7 will fix the problem for the future. Bobs suggestion is probably the only way to potentially fix the problem on existing recordings.

[BobPhoenix]

Originally Posted by WellThen

Not sure if the fix Bob suggests will work, but I don't agree that this is resolved by going to Sage 7. I've previously reported this issue here and something related here. And I was using Sage 7 for both of these occurrences.

It does work much of the time if the problem actually IS that SageTV recycled the airing ID numbers. There are problems using this method occasionally. Sometimes SageTV thinks the renamed airing is a partial recording and will delete it. Another problem is that you can occasional get the renamed file listed as an imported video and as a recording at the same time. You usually DON'T see either of these problems when performing the rename manually. When writing my VideoEdit plugin I was trying to do this automatically in a Java app and I had to put delays in the procedure at the correct points or they would show up frequently. Even with delays it wasn't 100% successful so I never finished the update to the VideoEdit plugin that would have allowed you to re-associate a disconnected airing and a media file from within the SageTV GUI.

[willieb]

I have had this exact issue numerous times in Sage7 over the past few months. WellThen did you try the fix Andy suggested in the other thread? Did it work? I am going to try it.

[ke6guj]

this happened to me last year and this was the solution:

Try this. Close SageTV and the service then set this in your Sage.properties file that is located in the SageTV directory:

repair_mismatched_media_filenames=true

Then startup SageTV and let it run for at least a day (it needs to write out a new Wiz.bin/bak file; and when it does that it'll do this repair operation). Then after that you can set this property back to false again and the problem shouldn't occur anymore.

You will see the names of your recordings before the rollover changed to match their current IDs in the database when this happens. It won't fix files that have already been linked to new EPG data; there's no way to do that unfortunately.

George

this occured when I was on 7.0.11. I can not say if it will work with V6.

[leadfoot]

Originally Posted by BobPhoenix

It is probably NOT corrupted. The ID number in the database (Wiz.Bin) has been reused by SageTV. I believe the upper ID limit was increased in V7 compared with V6. I got that allot on earlier versions of SageTV. What I would suggest is that you look in the WEB app for the now disconnected "Terminator: The Sarah Connor Chronicles" airing and lookup the airing ID. I will bet that the number is different from the one in the file name of the media file. If that is true than you might be able to reconnect them by just renaming the media file with the airing ID that the WEB app displays. Note you need to shut SageTV down before renaming the file and I would keep a copy of the file somewhere else with the old name too. Then if SageTV thinks it is a corrupt recording or a partial and deletes it you will still have a backup. Sage will likely reconnect the renamed file with the correct episode after restarting SageTV. If you use Service mode that is what need to be stopped for the rename.

I just had a bunch of these future recordings show up again and Bob's method for fixing it worked! Thanks!

[VCRUser]

I get these routinely, since I have shows on hand from 2009 - it seems to attack the shows that have been around for a while. What I've done is to create XML files for all older shows. Then when future shows turn up, I use the web interface to find out the filenames associated with the future shows. For insurance, I also make a copy of the affected show. I make a note of those, and then after the future airing occurs, I use the web interface's "edit airing info" option to put the metadata back in based on the xml file. (The option to simply import the xml file has never worked for me, so I do the task manually). It's a pain, but it works.