|
SageMC Custom Interface This forum is for discussing the user-created SageMC custom interface for SageTV. |
|
Thread Tools | Search this Thread | Display Modes |
#1
|
|||
|
|||
Clarification on proper way to import new version of STVi
I am just slightly confused on what to do when a new plugin version comes out and I want to try it. It usually comes with a statement like (this one from Ben):
"As usual make sure you BACKUP first and install as you normally would but not over a previous install of the import." Does this simply mean that I go back and "Load STV" and pick sageMC_6_3_8b_11 and then import all the STVi's again that I want, including the new version of some plugin? Or, do I have to roll back to a copy of my sage folder where I never even installed the old version of the plugin? For example, I want to roll from Movie_Info_Screen_V.1.0d to Advanced_Movie_Info_Screen_V.2.0a_01. ( Also, my import STVi file is now filled up with obsolete things like sageMC_169-#.xml (where # varies from 1 to 15). This can get a bit confusing on which one to pick for all of my extenders. How do I remove all these old obsolete (either STVs or STVi's) that I no longer want around. -R
__________________
QTY 2 dual-core AMD 3.0GHz Opteron processors, Windows 7 Pro, 4G RAM, 500GByte system drive, 3TByte recording drives, ATI video Radeon 5500, on-board audio, 3 HD100 Extenders, Gigabyte Switch, 2 Haup. PV150 tuners |
#2
|
|||
|
|||
Quote:
Quote:
__________________
Server 2003 r2 32bit, SageTV9 (finally!) 2x Dual HDHR (OTA), 1x HD-PVR (Comcast), 1x HDHR-3CC via SageDCT (Comcast) 2x HD300, 1x SageClient (Win10 Test/Development) Check out TVExplorer |
#3
|
|||
|
|||
Quote:
SageMC_6_3_8b_12-1.xml SageMC_6_3_8b_12-2.xml SageMC_6_3_8b_12-3.xml and so on. The clever part is that if the new import doesn't work or you don't like it you can load the previous number (via default SageTV settings and not SageMC). When you do import a new file it will also remember all your old settings. As long as you goto the default SageTV options first and import the base xml file before you install a new version of an import you shouldn't have a problem (SageMC_6_3_8b_12.xml is base). This creates a clean install which you can then re-import all your plugins into. When I say backup I usually close the client down and just copy all the files and folders to a backup folder, not a very efficient way to do a backup but it does make sure you have a backup of every single file. Quote:
__________________
Server - Win7 64bit, 2.4Ghz Intel Core 2 Duo, TBS 6284 PCI-E Quad DVB-T2 Tuner, 3 x HD200 & 1 x HD300 extenders |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
STV Import: iMovies for SageMC | jvl711 | SageMC Custom Interface | 112 | 11-16-2009 08:04 AM |
STV Import: STVi importer | dflachbart | SageTV Customizations | 47 | 07-31-2008 05:30 PM |
Is there a custom weather stvi for the default UI of version 6? | scat | SageTV Customizations | 2 | 01-20-2008 05:18 AM |
Can't Import STVi | tmiranda | SageTV Software | 4 | 09-02-2006 09:23 AM |
Import module names .STV vs .STVi | Doubletop | SageTV Customizations | 1 | 11-04-2005 01:26 PM |