hopefully its right this time!
I'm afraid, not so much.
When you bind a socket to an address, the networking stack will only let you see connections the bound address can talk to. If you bind it to 127.*, you'll never see connections from 192.168.* because the subnets do not match. The "state of the art" solution I learned is to just have multiple listen sockets - one for each port and interface.
Anyway, it's really a good thing that the socket is bound to 127.0.0.1; everything else would be way too dangerous and you'd just have to worry about security - and that's a whole different bag of saber-tooth tigers. Just bind to loopback by default, and when a user selects to let MB listen on any other address (via a simple checkbox), they should be told that that's an experimental feature, in no way safe and only meant for people who know what they're doing. Your other option is to basically blow this thing out of proportion and make it safe enough that nothing bad is going to happen even if MusicBee's control port is exposed to the internet (read: chinese hackers)...