This may only affect a few here, but nevertheless.
 
After applying X3d I found that saving a project as a MIDI file with one or more muted tracks the tracks were not muted, i.e. the save ignored this.  I prepare MIDI backing tracks for my band and for years I've used this function when I want to keep certain tracks, e.g. for later possible use, but not have them in the MIDI file I replay live on my Roland Fantom X6.  I reported it  last December as CWBRN 22566 and as of today it has not moved from 'under investigation'.  It's quite simple to replicate and it's definitely a bug introduced in X3d.  So why no correction???  I now have to delete the tracks before saving to a SMF, in other words save two versions of the project in future.  Small but annoying, especially as the fix would have been relatively trivial to carry out.
  

Rather than start a new thread may I suggest posting on your existing thread an update (will avoid confusion):
http://forum.cakewalk.com/After-X3d-saving-a-project-as-a-MIDI-file-type-1-ignores-muted-tracks-m2952255.aspx
 
I'm sorry your bug wasn't fixed this time, there are however lots of other bugs fixed that were older than this (at least when it comes to reporting them), and there hasn't been much noise from the community about fixing this.
 
Thanks.

If you archive the track rather than mute it, does it still save the track?
 
Regards,
Dan

Sounds like a prioritization issue. It's a relatively small problem, with a simple workaround, that doesn't appear to effect a lot of users. While the fix may even be easy to develop, it still takes time and resources, and requires a lot of testing. The X3e list looks like it tried to address more high value fixes frankly. Maybe X4.

Since I posted this there seems to have been quite a flurry of threads similar to mine, i.e. other CWBRNs that were ignored/parked for whatever reason.

Yup I just updated a whole load of threads. I can't understand why you think your issue is ignored (you've posted this several times now). If you wanted all the bugs fixed right now then X3E would have had to come out in 6 months time.
 
These were the bugs outstanding (well what we could identify) in X3D, a lot have been fixed in X3E, see #1.
http://forum.cakewalk.com/Outstanding-Issues-as-of-X3D-and-general-comments-m2952585.aspx#2952585
 
You can't fix all these issues are at once. Maybe you will get your issue fixed in X3F.