Downloadable STV Updates for v6.6; Latest: STV v6.6.2.31, 2013010701

[waynedunham]

Just an FYI. I am running SageTv 6.6.2.218 on WHS and have 2 HD100 extenders running the stock STV with imports (based on the 200982102 STV and only the comskip for default STV import) as reported by system info. I received no system message about this new STV.

When does it look for that, when it does an EPG update? I forced an EPG update via Neilm's webserver this morning about 10am trying to see if the EPG would pick up some changes for the rained out Sox game. I'm not sure when the previous regular EPG update was done.

[hemicuda]

I don't think I got an invite to the party either, but I'm running a few plug-ins on the base.

[Opus4]

Originally Posted by waynedunham

I am running SageTv 6.6.2.218 ... stock STV ... the 200982102 STV ... I received no system message about this new STV.

Please read the change notes previously posted in this thread. If you aren't running STV set 2009090401 (or newer), you wouldn't get a system message about an STV update because the feature hadn't been added yet.

When does it look for that

This is covered in the change notes, above.

- Andy

[Opus4]

A downloadable STV update is available -- go to Detailed Setup -> Advanced -> Check for STV Update.

The v6.6.1/v6.6.2 STV file set 2009090901 will be updated to version 2009091601, updating the default STV with these changes:

6.6.2.11 -- 2009091601

1. Fixed issue finding Video ID for YouTube video.

Note: If you are using Vista, the STV update option may not be available. If you are unable to use the downloadable STV update within the SageTV v6.6.2 UI, you can manually install the update:

1. Download the update file:
   2009091601.zip
   
   
2. Make backup copies of this file: SageTV3.xml, found in <SageTV install path>\SageTV\STVs\SageTV3
   
   
3. Unzip the file to you SageTV install directory where SageTV.exe is located, making sure to preserve the zip file's directory structure. This will overwrite SageTV3.xml in <SageTV install path>\SageTV\STVs\SageTV3. Make sure the updated file does not end up in Vista's VirtualStore.
   
   
4. Restart SageTV or reload the default STV (SageTV3.xml) in the SageTV UI at Detailed Setup -> Advanced.

The STV version will be listed in System Information as v6.6.2.11.

- Andy

[reeven]

working ok, you're good.

[tmiranda]

Andy,

I am having trouble updating one of my HD100s. One updates fine but the other goes through the download and reload process and then tells me to look for another update and when I do I can see that the STV has not changed. (i.e. it says I still have the same version that I had before doing the update.) There are no error messages. NO matter how many times I try downloading the update it simply does not change.

Have you ever seen this before?

Tom

[Opus4]

Originally Posted by tmiranda

I am having trouble updating one of my HD100s. One updates fine but the other goes through the download and reload process and then tells me to look for another update and when I do I can see that the STV has not changed. (i.e. it says I still have the same version that I had before doing the update.) There are no error messages. NO matter how many times I try downloading the update it simply does not change.

Have you ever seen this before?

I haven't run into this before.

Are they both connected to the same server? If so, you should really only have to download the STV via one extender & then when you turn the other extenders on, they will use the already downloaded SageTV3.xml update. If the extender is already on when the STV file was updated via a different extender, its STV is already loaded so it needs to restart in order to use the updated file. Have you tried restarting the HD100?

Are you using a customized STV? If so, it shouldn't even complete the download.

What is the STV version info in System Information?

Post the debug log from the server so I can see if it has any info about what is going on.

- Andy

[tmiranda]

Both HD100's are connected to the same server. I installed the update on the "bad" HD100 doing what you described, I updated the other HD100 and rebooted the "bad" HD100 so it would pick up the update.

When I ran into problems I swithed back to the stock default STV and that did not make a difference.

In order to supply debug logs I'll have to "downgrade" the STV to an older version that I have saved and then re-run the upgrade. I'll try to do it this weekend but no promises. Lot's of "honey do's" on the list right now.

[tmiranda]

Andy,

I did get it to update but had to revert back to the default STV with no plugins.

Tom

[Opus4]

Originally Posted by tmiranda

I did get it to update but had to revert back to the default STV with no plugins.

That's expected -- it will not proceed with the update if SageTV3.xml is not the STV being used, though it will check for the update.

When a customized STV is in use, it should tell you that you need to revert back to the default STV before you can install the update. Is that not what it did?

- Andy

[tmiranda]

Nope. It downloaded , unzipped, and told me all was OK but I should check for another update. I was running an STV from July sometime (200907xxxx).

[Opus4]

OK, thanks. I'll add that to my list of things to check out.

You didn't keep the debug log from when this happened, did you?

- Andy

[Opus4]

Originally Posted by tmiranda

Nope. It downloaded , unzipped, and told me all was OK but I should check for another update. I was running an STV from July sometime (200907xxxx).

I just realized how old your STV was: are you sure it wasn't working correctly & updating the STV each time? There were several STV updates, so if you started the update process from that old of an STV version, there would a few times where you would see the message that another update is available. Once you reach the most recent update, it won't remind you to check again.

I don't see anything obvious in the code that would be a problem, so please keep debug logging on when the next STV update is released so I can see what is happening if you run into it again.

- Andy

[tmiranda]

Andy,

No logs, sorry.

I'm sure it was "stuck" on that old STV. At first I thought I also had multiple STVs to download to "catch up" but after 5 or 6 times I realized that the "current" version number was not changing.

Tom

[wayne5w]

I am having trouble updating the STV.

When I use the "Check for STV Update" option in Advanced it seems to work but "Current ver:" is listed as 2009072401

I have tried updating the STV manually and the correct version is displayed until I force a rebuild of the plugins. Then the Current ver is listed as 2009072401 again.

No matter what I try, when the plugins are rebuilt the version displayed is 2009072401.

Any help resolving this is much appreciated.

Regards,
---Wayne

[tmiranda]

That's exactly the same problem I was having. To fix it I had to revert back the the default STV and make sure the STVi manager did not automatically rebuild the STV. After that I could update. And there were several updates since the 2009072401 file is quite old.

[wayne5w]

I tried reverting to the default. I then was able to update and get to the current version. But as soon as I rebuilt the plugins the version displayed goes back to 2009072401.

Now when I select revert I am on the current STV version. But as soon as I load the plugins or rebuild I go back to 2009072401.

Are you able to load the plugins after reverting and keep the latest STV version?

Strange, can't figure this out.

[Opus4]

Did you see my request for a debug log, above? Do you have a log to post?

What are the imports being used? Does one happen to set the STV version back to what it should not be? Try loading them one by one to see what happens.

- Andy

[wayne5w]

I did some testing, removing all the plugins and then adding them back one at a time. It is the Phoenix Fan Art plugin (http://forums.sagetv.com/forums/down...do=file&id=330)
that is causing the STV to revert to the old version. If I remove this plugin the latest version of the STV is displayed. If I add the plugin the version reverts. I checked and I am using the latest Phoenix Fan Art STVi. I'll post a message on the support thread for that plugin.

Regards,
---Wayne.

[Opus4]

Thanks for doing the test and solving what is going on.

- Andy