Zoner,
A couple of things could help troubleshoot this:
1) With the Girder window open, press your remote buton for a command that is exhibiting this behavior. Girder will highlight which command it executed in the tree on the left. Let us know which command it is.
2) If you are not using the MC9 group I created to run with the mjextman commands, you should then look in the "Action" pane of Girder (that's the area in the lower right, with all the tabs). Let us know what Action & all the parameters are for that command.
Assuming it's my GML, it will be something like: Action-"O.S." (the tab); Dropdown box="Execute"; File="mjextman.exe"; Step Size="/MCC 10000,0"; StartupOptions="Default"
3) Finally, start simply--Manually add some files to "Playing Now" and try the play/pause command to see if you can start & pause playback.
I haven't seen the problems you're having. I suppose it's possible that there are problems with build 127--I haven't moved up to it.
I know that when I started with Girder I had lots of problems with unexpected behavior. One of my main problems was that I had accidentally assigned the same eventstring (IR command) to several actions. Girder matches the first eventstring it finds in its tree, so if you have the same IR code assigned to "Play" and "Next", and you want to go to the Next track, but "Play" is ahead of "Next" in the tree, you will never be able to access the "Next" command. Knowing which command Girder is trying to execute (#1 above) will help.
Troubleshooting Girder & multi-program interactions is always a complex chore. Keep at it--we'll get it!
Brad