- April 23, 2007
- 755
- 79
- Home Country
-
- Thread starter
- #21
Hi Cybrmage, placing the updated mpcontrolplugin.xml file in this directory also broke the plugin for me. I can't configure the plugin anymore. I'm really lost about what files are supposed to go where now, because there is all sorts of information in about 5 different threads. Sandcastle came up with the alternative of not using the abstract remote model, and those were the instructions to place the xml in this directory.
Anyway, bit lost now, and really don't know what to do. Back to using imon with no cybrdisplay for now.
Is it possible Aaron's main thread could be updated with where the files should be placed, as well as the updates you have been adding along the way? This is how you've been doing it with cybrdisplay, and that is pretty straight forward. The thing that threw it for me is that the MPControlplugin update had an extra .pdb file that I wasn't sure where it was supposed to go. My assumption was that these updates replaced existing files, so I tried to find where the various files were and replace them. I know now that they should have all gone in the plugins/process directory, but I think I've got myself in some sort of Gordian Knot now and need to start from scratch.
Update: OK, I've done a bit more troubleshooting on this and managed to untie the aforementioned gordian knot.
Firstly, there is a lot of confusion in these threads about where to copy the MPControlPlugin files that are included in the update on the main IR Server Suite thread. There are 3 files: mpcontrolplugin.dll mpcontrolplugin.xml and mpcontrolplugin.pdb that must be copied into the plugins\process directory. I used the theory that files should be copied to wherever you found the orginals. There was no pre-existing .pdb, but there was a pre-existing mpcontrolplugin.xml in the inputdevicemappings\default directory. If you copy over this xml file with the new one, you will be unable to configure MPControl plugin again. Clicking on configuration throws an exception that you can see in the main MP Config log.
So, if you have done this and copied these update files for MPControl plugin into any directory other than the process\plugins directory, resulting in being unable to configure MP Control plugin, my advice is to uninstall IR Server Suite and start again. Unfortuantely, the IR Server Suite uninstall leaves a few things behind at the moment, so you should delete mpcontrolplugin.* from the main mediaportal directory as well, and you should also delete the App data folder for IR Server Suite as well (c:\documents and settings\all users\application data\ir server suite)
Do NOT assume that you can use the update files in the main thread with the process that SandCastle described here. https://forum.team-mediaportal.com/...n-pad-ir-server-1-4-2-all-buttons-work-40004/
You must use the files that he has posted. They are different to the original updates. If you copy original update files to where this thread tells you, you will really hose things up.
So I am back to square one. I have copied the mpcontrolplugin updates into the process\plugins directory, and have copied the imon update files into their respective directories, including the recent dll's posted by cybrmage. IR Server Suite starts, and kills the original soundgraph imon process. The pad is locked in mouse mode (even though I configured the driver with "selectwithbutton"), the numeric keys and they keys around the pad work, but nothing else.
The IR Server Suite debug client shows no input from the remote (even though it is "half" working, and I can see the mouse moving while the debus client is running) and the input service and imonUSBreceiver logs also show no input from the remote. It is as though IR Server Suite somehow enabled some low level USB functions for the remote, but none of it is actually going through IR Server Suite.
Logs attached, showing no input, even though keys are pressed.
