X2 & Faderport problems - possible Midi Device name related?

I apologize for the long post:

The FaderPort 'bug' where the Faderport's fader goes nuts and Sonar locks up seems to be worse with X2 (the actual chatter from the motorized fader made me jump - and I am used to it).  I had a project earlier in the day and the chatter noise was not nearly as bad.

I tried to open a project done in X1 as my first X2 test. The Faderport went nuts (the actual motorized fader grinds away).   This has been documented a few times on the forums here.  The 'fix' is to unplug the FaderPort, restart Sonar, remove the FaderPort as a controller, close Sonar, restat, and re-add the FaderPort as a controller after the offending song has been loaded.

It requires a Kill Process from the Task Manager when this happens.  I tried it today with X2 and it would not shut down or end.  I had to do a full system restart.

So FaderPort is still a hit or miss device in X2.

Theory:

I have seen various posts that point to it being a Presonus problem, but I think it is actually related to how Sonar renames Midi Ports when the USB physical port changes.  Other sequencers don't seem to renumber or rename Midi and Audio ports, where Sonar appears to rename the device.

For example, I have a lot of FireWire and USB devices: FireFace 800, FireFace UFX, AxeFX, Yamaha 01v96, M-Audio Axiom 49, M-Audio MidiSport 4.4 Anniversary, M-Audio Venom, Yamaha MOX6.  These all expose midi and audio ports via USB or FireWire.  I am usually swapping stuff in and out depending on my live needs and sequencing requirements.

If they are not plugged in to the same USB port they were originally, Sonar renames the inputs/outputs by adding a numeric to the end.  Any projects that that are opened after that no longer match up to the original device/port.  For example, a USB midi port will show up as "MidiPort" originally, then "MidiPort(2)" if I plug it in to a different port.  Depending on how many times I have used a different port the number can change (I have seen it as high as 6). 

I use a few other sequencing programs from other well known vendors.  They do not have this problem - every port seems to keep the correct naming and regardless of what USB port is used.  Sonar seems to be hit or miss if there are any midi/audio port changes.  This leads me to believe it could have something to with the way Sonar surfaces USB/FireWire ports.

The issue is not machine specific: I have a  few laptops that I use live that I have to label the USB ports to make sure the device names stay the same.  I use the Play List for live tracks several shows a week, and this HAS to work every time.  I made the mistake of plugging in something backwards and had the first few songs come up with 'changed' ports that need to be mapped.

This is starting to get more frustrating as more devices expose midi ports via USB.  There are only so many ports you can use without going to big hubs <g>.  Re-selecting ports on older projects also gets old when you have a lot of I/O ports.

I don't normally post here, but read the messages daily....