|
|
|||||||
| SageMC Custom Interface This forum is for discussing the user-created SageMC custom interface for SageTV. |
 |
|
|
Thread Tools | Search this Thread | Display Modes |
|
#1
10-17-2008, 12:22 PM
|
||||
|
||||
|
Can't import stvi's
I am trying to import "infopopup_import.stvi" into SageMC and it will not show up in the list to import. Either will the IMDB import either.
I have tried importing into the default skin and it worked fine. The new manage imports seem to work alot better. But as ffar as SageMC goes I have never been able to get CID working with that skin. In any of the 6.x versions. So I believe it's me that is doing something wrong. I have created the import in the default skin and tested, and that works fine then I use the SageMC_169.xml and the CID will work until I restart the client and then nothing. This test is being done on the servers clint GUI. I am ultimetly going to use that skin on my hd100's (hopefully). Is this possable or am I doing something wrong? Thanks, Skybolt 
|
|
#2
10-17-2008, 12:25 PM
|
|||
|
|||
|
SageMC does not use .stvi imports, it uses .xml imports. So it won't find them to import.
Depending on the actual code in the import, you may be able to just rename the suffix to .xml and then be able to import it. Or, you may be to use a SageMC specific version of the import.
__________________
- Jack __________________________________________ Server: AMD Phenom 9750, 2GB RAM, 2 Hauppauge PVR500, 1 Firewired DCT6200, 1 HDHomerun tuning 2 QAM channels, Vizio 37" HDTV LCD, 1 USB-UIRT Clients: 1 MediaMVP, 1 Placeshifter Client, & 1 SageTV Client.
|
|
#5
10-20-2008, 07:42 AM
|
||||
|
||||
|
What else can you call it? To make sure you don't get STVi's that were designed for the default STV a design decision was made to make sure all STVIs designed for SageMC used the .xml extension. For the call ID plugin you can rename the extension to .xml, import it in and it generally will work. Not all of the default STVI's will work within SageMC and some will cause issues.
Gerry
__________________
Big Gerr _______ Server - WHS 2011: Sage 7.1.9 - 1 x HD Prime and 2 x HDHomeRun - Intel Atom D525 1.6 GHz, Acer Easystore, RAM 4 GB, 4 x 2TB hotswap drives, 1 x 2TB USB ext Clients: 2 x PC Clients, 1 x HD300, 2 x HD-200, 1 x HD-100 DEV Client: Win 7 Ultimate 64 bit - AMD 64 x2 6000+, Gigabyte GA-MA790GP-DS4H MB, RAM 4GB, HD OS:500GB, DATA:1 x 500GB, Pace RGN STB.
|
|
#7
10-20-2008, 10:32 AM
|
||||
|
||||
|
Imports/plugins are still called STVi's regardless of extension in same manner that SageTV Appplication Packages are called STV's even though they have all had .xml extensions for ages (they used to have .STV extensions). Maybe 'Import Plugin' would be Ok, but 'Import Import' is just plain silly.
 Aloha, Mike
__________________
"Everything doesn't exist. I'm thirsty." ...later... "No, it's real!!! I'm full." - Nikolaus (4yrs old)
|
|
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| STV Import: Read & Write Metadata files for Default STV 5/6 (v2.2.9 18/Feb./2010) | JREkiwi | SageTV Customizations | 251 | 10-09-2019 11:11 AM |
| Photo Import Directories not working on clean install | iolaus | SageTV Beta Test Software | 1 | 08-15-2008 11:53 PM |
| SageTV and import folders | bastafidli | SageTV Software | 0 | 01-27-2008 12:42 AM |
| Help Me With My Import | aperry | SageTV Studio | 5 | 07-19-2006 03:59 AM |
| Choppy Playback with Import STV's??? | RedCoat999 | SageTV Customizations | 3 | 12-09-2004 10:28 PM |
Linear Mode
