Ok, looks like multiple newseq entries under a port was throwing things off.
I've fixed things up and will do some testing, then post the new build here in a bit.
First off, want to say that I finally got around to using this utility, and it works great. I have a modular CP with several USB joysticks, and it works great for me. I'm also assuming this could work for MESS on my cab too. I also have a number of console to USB converters as well.
I am having one issue with newseq entries, but I don't believe it is the fault of ControllerRemap. ControllerRemap appears to be correctly creating them in the "live" input section. However, MAME appears to be ignoring anything other than what is passed in the "standard" entry. I'm posting in this thread, hoping that this user base would be most likely run into this issue, since it depends on the use of ctrlr files.
For example, I am trying to map the "P1_POSITIONAL" port for my rotary controller in Ikari Warriors. It is hooked up to my GP-Wiz40 which translates the rotation into one of two button presses. Here is the code generated in the input section.
<port type="P1_POSITIONAL" mask="240" defvalue="0" keydelta="0" sensitivity="100">
When I fire up MAME, it does acknowledge that I set the actual dial setting to "NONE". I have manually changed this to MOUSECODE_1_ZAXIS to test, and MAME does in fact pick up the change from none to mouse z. But it continues to ignore the fact the dial increase and dial decrease should be mapped to buttons 19 and 18. It shows them with the default of Z and X (I believe off the top of my head).
It also appears to be ignoring any of the analog settings that are passed on the port line, like the sensitivity. It keeps defaulting to like 15 (or something) when I'm passing 100 in the string. Having the same issue when I set up a profile for Arkanoid to set the sensitivity to 40. It keeps defaulting to 30. If I manually change them in MAME, it then creates a cfg file in the cfg directory for that particular game. And if I load the game again, MAME honors those settings. So it appears to only be ignoring these settings when they are passed via the -ctrlr option. I even took the corrected cfg file for Ikari and moved it from the cfg folder into the ctrlr folder, and ran MAME using -ctrlr ikari, and it then defaulted back to the original settings.
Has anyone else using this utility notice the same thing? I'd feel better if at least one other person noticed it besides me before opening a bug with the MAME team.