|
SageTV Customizations This forums is for discussing and sharing user-created modifications for the SageTV application created by using the SageTV Studio or through the use of external plugins. Use this forum to discuss customizations for SageTV version 6 and earlier, or for the SageTV3 UI. |
|
Thread Tools | Search this Thread | Display Modes |
#1
|
|||
|
|||
Miniguide and Dynamic Custom Menus Issue
I apologize for not putting this in a STVi-specific thread but it sorta laps over two different ones, so hopefully I can find help here... (see my specs in signature)...
I installed the Miniguide plug-in last night and it works fine on my server and on one of my two HD Extenders... but I'm having problems on the other Extender. I posted a few days ago about some problems I had when I installed Dynamic Custom Menus because my wife had one Extender running when I did it - and that Extender, for some reason, did not pick up the menu changes that I made on the server. So I had to manually point that Extender to the "menu.xml" file (though all of the other customizations that I had installed afterwards all came through and the Extender indicated that it was on SageTV3-8.xml as it should have). Last night when I installed the miniguide (moving me to SageTV3-9.xml), that same extender is not seeing it. The setup screen does show it at 3-9 (so it recognizes that I'm on a revised xml file), but it doesn't work nor does it have the options line in detailed setup. I think somehow that Extender (because of what I described above with getting Dynamic Custom Menus to work) is ignoring the miniguide plug-in, or else operating from a completely different STV file or xml file or something. Can someone with a better handle of "what looks at what" explain what I need to do? I still don't have a handle on how the "SageTV3-{x}.xml", and the "menu.xml" created through Dynamic Custom Menus, work together.
__________________
Server: AMD Athlon II x4 635 2.9GHz, 8 Gb RAM, Win 10 x64, Java 8, Gigabit network Drives: Several TB of internal SATA and external USB drives, no NAS or RAID or such... Software: SageTV v9x64, stock STV with ADM. Tuners: 4 tuners via (2) HDHomeruns (100% OTA, DIY antennas in the attic). Clients: Several HD300s, HD200s, even an old HD100, all on wired LAN. Latest firmware for each. |
#2
|
|||
|
|||
It is possible that you may have to install the mini-guide before you install any other plugins. I haven't used it for quite a while so I could be wrong but as I remember it if you are using the comskip plugin the mini guide plugin has to be installed first. It may be that way for other plugins like my FCL plugin for example. Just guessing here. So you might try switching back to SageTV3.xml then import the mini guide and make sure it is working then import the dynamic menu plugin. The "menu.xml" will still be present and you will get your menus back after reinstalling without having to do anything else.
|
#3
|
|||
|
|||
FWIW - I install the mini guide first before any other plugin.
B
__________________
Running SageTV on unRAID via Docker Tuning handled by HDHR3-6CC-3X2 using OpenDCT |
#4
|
||||
|
||||
The menu.xml is in use exclusively by Dynamic Menus. This is what gives Dynamic menu its look and feel, what menus show up in what order, what icons get used for which items, etc. When you save your Dynamic menu changes this is where that is stored. If you had a client where you wanted to remove access to say the Videos then you would want to go to that client, remove the Videos menu but do a save as with a different name like menunov.xml because you only want that on that particular client. Your server and other extender would continue to load menu.xml for Dynamic menus.
The SageTV3-(x).xml is a Sage STV with imports. So let's say I start with SageTV3.xml and I import Dynamic menus and get SageTV3-1.xml and then I import the mini-guide and get SageTV3-2.xml. Now if an upgrade comes out you'll get a new SageTV3.xml that will overwrite the existing one. Because this may have new features in it you want to go back and do your imports to take advantage of these. If you do it now you will go back and load SageTV3.xml to begin with. Now let's import Dynamic menus. When you do you will now have SageTV3-3.xml. And when you import the mini-guide you will be at SageTV3-4.xml. If you were to go back and load SageTV3-2.xml it would probably look just like SageTV3-4.xml. Except it would be using the previous version of SageTV3.xml and not have the features or fixes of the one you received with the update. As a cleanup I usually go back and delete all my SageTV3-(x).xml so I can keep track of the number of imports I have. Maybe that extender was in use again when you did the update. The fix should just be to do it on that extender itself. I probably made it more confusing but honest, I am trying to help. 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. |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
STV: SageMC 16x9 Version 6.x (latest dev build) | dflachbart | SageMC Custom Interface | 6112 | 04-04-2008 11:16 PM |