Same as copying the midi track/s deleting them saving the midi and then pasting them back in from clipboard, any method would work.
 
I do agree, as I wrote, that giving a user the "option" in the SMF save dialogue to include/exclude muted tracks would be nice..non-essential but nice!

To clarify. There is a change in behaviour. 
I have an older version of Sonar on another PC and fired it up to confirm the issue before filing the CWBRN. And no, I don't want to keep digging it out, swapping my screen, keyboard and mouse to do this routine editing and saving - why should I when CW introduced the issue in X3d?
 
Also, over the last six years I have edited and prepared hundreds of  MIDI files using this facility of muting tracks before saving as a .MID to use on my Fantom X6 (mostly guitar tracks because I play the guitar parts live but it's handy to keep the tracks in case I want to check a riff or something at a future date). So, I'm not hallucinating. I haven't changed something else in my setup and inadvertently introduced the issue.  The  CWBRN moved a few weeks ago to 'Under investigation' so I'm still waiting for at least an update of that status from Cakewalk. I'll repost if and when I see an update.
 
As for MIDI standards compliance, a muted status on a track may well not exist, but I assume the original (laudable) intention of CW was to allow you to simply not save the track by muting it. Perhaps a programmer thought that wasn't 100% MIDI compliant so 'corrected' it.

Skyline_UK
 
Perhaps a programmer thought that wasn't 100% MIDI compliant so 'corrected' it.

Best explanation yet!!

Well do let us know when and IF Cakewalk get back to you on this...as far as I can see there has been no response at all from them to the OP (well none he has shared) , and clearly no comment on this thread.
 
As I said, I have prepared many hundreds of SMF files, format 0 and format 1, going all the way back to Cakewalk 4 (pre audio days) and never has it saved a SMF ignoring muted tracks in the save process.  Maybe it was an option I missed all those years as I simply assumed it ran according to the MMA specs??
 
So it would be very interesting to get a Cakewalk response to this...

Skyline_UK
#1 "Since applying X3d yesterday this seems broken as muted tracks still get saved".

Skyline_UK
"I have an older version of Sonar on another PC and fired it up to confirm the issue before filing the CWBRN."

Exactly what version of Sonar did you update from, or are you comparing this to?
Thanks...

For example, I found this from a search and the page relates to X2 - I will continue to try and find more references ...although even searches through old forums posts indicate saving the status of a muted track was never possible..
 
The quote:
While playback is in progress, you can mute and unmute tracks in any combination, which means you can hear only the tracks that you want. You can change the status of a track in the Track view, the Console view, the Track Inspector, or the Mix module in the Control Bar. If a track is both muted and soloed, it does not play. Mute has precedence.
The track status is saved with the SONAR project file. If you save a SONAR project as a standard MIDI File, however, all tracks are saved without mute, solo, or archive indicators.
 
Link is http://www.cakewalk.com/D...p;Req=Playback.11.html

Yes, and the documentation remains the same in X3 http://www.cakewalk.com/Documentation/default.aspx?Doc=SONAR%20X3&Lang=EN&Req=Playback.11.html
 
FWIW, the behavior is consistent (and documented) at least since X1.

Thanks Scook

It seems a simple thing to delete the muted track/s and save the MIDI file under a new name,. If you wish later on to open the original MIDI file with all the tracks in place just open the old MIDI file.   
 
The notion that muted tracks in Sonar project would not be saved seems odd to me. 

John, sorry m8, but you really need to read the thread - it is about the mute status of a track in regard to saving as a standard midi file, NOT a project file (or CWP)