Load STVI on Hd100?

[heffneil]

I am trying to load the fanart stvi on my HD Extender but when I go to the option and browse it only shows XML. I am still getting to know this system but am I missing something obvious here?

Thanks!

Neil

[gplasky]

If it only shows xml then you're running the SageMC UI interface. Any plugin that ends in .stvi is for the default SageTV UI only. SageMC UI already has fanart built into it. You need to enable it in the SageMC options.

Gerry

[freedml]

Chalk up another one for SageMC confusion!

[gplasky]

One BIG rule of thumb. Any plugin the ends in .STVI is ONLY for the default SageTV STV. Plugins for SageMC UI will end in .xml and can ONLY be used for SageMC UI. These are strictly for the plugins or what is know as an STVI.

All plugin authors spell out in the download area, either in the title, description or readmes what Sage UI the plugin is designed for and to be used with. It will usually reference either the Default STV or the SageMC STV. As per a suggestion I have started calling it SageMC UI as to not to confuse it with people calling the product SageTV Media Center. The name goes back to when mlbdude first came up with the alternate interface and called it SageMC because it was similar at the time to the first Windows Media Center 2004 product interface. The full name of the STV is SageMC16x9. It was also one of the first STV designed for the 16 x 9 screen format.


Gerry

[heffneil]

Thanks for the help. So I downloaded the latest SageMC and selected the sagemc_169.xml but fanart of fart if you read it real fast doesn't appear there. Any ideas? Do I have to enable it somewhere. Be gentle.

Thanks!

Neil

[gplasky]

If you did a full install of it then grab the latest: SageMC_6_3_8b_12.zip

Also this forum: SageMC Custom Interface forum is where to be for all things SageMC UI.

Gerry

[heffneil]

You are right we should move this over there. I guess I was confused because this seemed HD100 Extender specific. I downloaded what I thought was the latest version but it was sagemc_6_3_8a_full.zip.

Neil

[heffneil]

That link was just to an XML file nothing else. Am I missing yet another thing?
Thanks!

Neil

[gplasky]

Originally Posted by heffneil

You are right we should move this over there. I guess I was confused because this seemed HD100 Extender specific. I downloaded what I thought was the latest version but it was sagemc_6_3_8a_full.zip.

Neil

And you do need that if you have never installed it before. The link I provided is the latest test release that has fanart and some fixes. You'll just copy that in and load that STV.

Gerry

[heffneil]

Should that download just be an XML file and nothing else?

Thanks,

Neil

[gplasky]

Originally Posted by heffneil

Should that download just be an XML file and nothing else?

Thanks,

Neil

Yes.

Gerry

[freedml]

Gerry, "SageMC UI" won't help avoid confusion since Sage Media Center has a UI (User Interface) also. The relative newbies are the ones who get confused and they won't get the distinction.

[gplasky]

Originally Posted by freedml

Gerry, "SageMC UI" won't help avoid confusion since Sage Media Center has a UI (User Interface) also. The relative newbies are the ones who get confused and they won't get the distinction.

It should be referred to as the Default UI or the SageTV3 UI. When adding "UI" it is an attempt to differentiate the STV's. SageTV3.xml is the Default UI (STV). (The UI (STV) is how it looks AND acts.) SageMC UI would be the SageMC_169.xml (STV). (Again-how it looks AND acts) Themes are just the changing of graphic elements (How it looks). Themes are used with the UI (STV).

For the actual Sage product the abbreviation should be SageTVMC (not SageMC) because on the website the product is called SageTV Media Center.

So my suggestion is:

Product Name and abbreviation: SageTV Media Center (used on the website) or SageTVMC. (When running the product refer to either Service Mode or App Mode (single machine) or App/Server mode (if clients attach to it).

STVs: SageTV3 UI or Default UI. Others: SageMC UI, Meekel UI, Phoenix UI (upcoming) (All of the latest STVs files end in .XML. Previous versions used to end in STV.)


STVIs: Plugins for Default UI. (files ends in .STVI) Plugins for SageMC UI (files end in .XML and can ONLY be used in SageMC UI) Upcoming Phoenix UI (my guess is plugins will be specific to the UI)

These are suggestions and hopefully goes toward reducing the confusion while still maintaining compatability with established and previous description conventions.

Gerry

[freedml]

I know all that now, too. But it took several months to figure it out. There were clues such as the ones you're suggesting, but it can take a long time to 'connect the dots.' And some of the clues (like the "16x9" reference) can create even more confusion.

Changing how we refer to the software won't help. We need to have a distinctive way to refer to 'SageMC' (it used to be '16x9', now 'SageMC', why not change it again to avoid future confusion?). I've suggested SageMC+. or how about SageUI+, People would not confuse "+" with SageTV Media Center and would look for how to get the "+" on their system.

[gplasky]

Unfortunately changing the name may not be enough. Examle: If the product is SageMC (which you are saying is the default) then why are you loading an STV called SageTV3.xml when there is an STV called SageMC_169.xml? For the SageMC UI there is references to SageMC in the STV file names, .properties files and within the program (widgets and other objects.) You need to refer somehow to the STV name to keep the two seperate.

Some of the developers are working on the Phoenix api's which is also going to result in the creation of another STV. (UI) I'n guessing it will use the best of both and will not have the confusion of naming that we currently have to endure.
Just mky 2 cents.

Gerry

[heffneil]

Guys not to be a downer here but I downloaded that XML file do I then select the file as my application on the HD100?

Thanks,

Neil