I am unsure what have downloaded but I think it may be the CVS version. CVS is the current "work in progress at the minute" so you'd need to get a 'released' version installed first.
These are available on the the upper right of the Mediaportal homepage:
ie. https://www.team-mediaportal.com/
Install either "Release 0.1.3.0 or "Test Release 0.2 RC2" first. These have a setup.exe in them!
Try either of these first and if all is good (runs well, etc), then you can try a CVS version.
Note: You will need "Test Release 0.2 RC2" to try the CVS version. You simply extract the CVS version over the top of your "Test Release 0.2 RC2" install. Make sure you back up your working install as the CVS may not work for you. It doesn't for me but that's OK as I (read: my wife) wants stablility over "bleeding edge" technology. :wink:
It is present, but not with that name. It is called Scheduler, viz:
Interesting. I had never noticed that when the "command" is "ACTION", the "cmdproperty" is the actual window id, but it makes sense that it is.
Try this for yourself. First backup your working profile for the remote, then in the "Mapping" panel make a change to...
It is present, but not with that name. It is called Scheduler, viz:
Interesting. I had never noticed that when the "command" is...
I would like to be able to go directly to the Scheduled recordings window without having to first go to the home menu.
I saw this...
Actually, you just reminded me of how I have handled this in the past: I merged the contents of an old export.xml with a new one to make a complete file containing the old values I needed and the new values I didn't want to change. Why should it matter if the export file is missing some values? I would expect the import process to...
Actually, you just reminded me of how I have handled this in the past: I merged the contents of an old export.xml with a new one to...
My "fresh install" is missing some settings (in particular genre maps) that I would like to import from a previous export. There...
100% my bad - as expected :)
So, I had disabled the Windows Update service. Not a wise move, until MP all installed and working nicely. The reason it failed is because DotNetFrameworkChecker.cs looks in Registry HKLM SOFTWARE\\Microsoft\\NET Framework Setup\\NDP for v4/v4.0 AND v3.5. W10 has V4.0 but not 3.5. MP installer...
100% my bad - as expected :)
So, I had disabled the Windows Update service. Not a wise move, until MP all installed and working...
Just tried a new Client-only install on a clean Win10 Pro box. Installer doesnt realise .NET 4 Framework already 'installed' (part...