There are several problems associated with XGworks.

1. The biggest market is Japan, followed by Europe. North America is a distant third. XGworks for western countries is handled by the UK. There's no expertise in North America.

2. There's some politics involved. There's a sharp line between the Home and Pro divisions of Yamaha. I don't know which one is reponsible for XGworks but I suspect the Pro division because XGworks is definitely slanted toward stand alone synths like the MU series. Adding stuff for PSRs was an afterthought. Most of the PSR tables actually point to MU synths or CVP tables so you don't get the proper definitions.

3. The PSRs have extended the effects mapping beyond the original XG spec. The effects map in XGworks is only 8 bits wide whereas later PSRs have extended this to 24 bits. This means that the effects menus can't be displayed properly and odd anomalies appear in dialog boxes if you add the extended effects. Also some internal tables limit the number of basic effects so even if you add them the parameters won't display. This requires a major change to the XG Editor to fix these problems. Then you run into backwards compatibility problems. Not only do you have to write the code but also update every table for every synth.

4. At least it's possible to add new instrument definitions if you know what you are doing. Takes a bit of effort though.

5. XGworks was very much on a par with Cakewalk but Sonar is a long way ahead so a complete update of XGworks would be required with no guarantee that it would sell enough to recoup development costs. Much cheaper to write plugins for Sonar which is what they seem to be doing. It's probably the best way to go. Leave XGworks for the older instruments and go with SOnar. Now that Logic is out of the picture for PCs there's only Cubase left so Sonar can only go up.

Bryan