joden
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) 

My post was meant for the OP as way to get around the mute issue he talks about in the OP. It is not about saving a cwp project. It clearly says to save the MIDI file. It does not say to save the cwp file.  
 
You may not know this but Sonar can save MIDI files directly as a file type choice. Use save as to do this. 

Yup. I reproduce the OPs issue (or non issue TBC) using 'save as'. What you have here is a valid work around John. Even if this is a bug it's extremely trivial and I'm tempted to take it off my bug list. I'll give it a few more days.

That work around (albeit worded differently) was already suggested (by me  )  in an earlier post Alex....
 
@ John, it was your comment "The notion that muted tracks in Sonar project would not be saved seems odd to me"  that I was referring to. The saving of the  mute status to CWP's was never in question ...an m8, I have been using Cakewalk since version 4 for all midi work, so I reckon I am pretty au faix with how it works  and I am sure even the OP knows pc 101 stuff like "save as".

joden
That work around (albeit worded differently) was already suggested (by me  )  in an earlier post Alex....
 
@ John, it was your comment "The notion that muted tracks in Sonar project would not be saved seems odd to me"  that I was referring to. The saving of the  mute status to CWP's was never in question ...an m8, I have been using Cakewalk since version 4 for all midi work, so I reckon I am pretty au faix with how it works  and I am sure even the OP knows pc 101 stuff like "save as".

Right but I wrote that, that way because there is no such thing as a muted track in an SMF.  There would be no purpose for such a thing. Therefore Sonar, unless told otherwise will save all the MIDI tracks without regard to mute status to a SMF. 
 
No I don't know what the OP knows.  I'm not a mind reader. 

John I am assuming that you didn't read the whole thread. Just responded to OP. Everything your suggesting and stated has already been discussed. That's what Joden pointing out.

I have X1 on my box. I tried to replicate what OP says X1 does, "ignore muted tracks" when "save as" is used to create a midi 1 file.

I created a new project.
16 midi tracks.
One instance CWSC
I renamed first five trks to "Mute 1-5"
Muted the first five trks
"Save As" midi one file.
Transferred to second box via USB key
Open that midi file in Reaper.
All18 trks were there.

I could not reproduce what he says happens.

Thanks Grem that is all what I was trying to say. That the points raised by John had already been discussed.
As I also wrote, even if one moves the non-required midi tracks to a folder, and then only selects the rest to be saved, the ones in the folder still get saved.
 
Cake have simply implemented the GM1/2 specs re this. Correctly too. Users are aware and simply temporarily remove tracks or save a separate file to maintain all original data in storage should it be required again.
 
In my case I save all my midi projects as a CWp, then open that remove the tracks I don't want then save that file to the "working" midi for use elsewhere, on a gigging keyboard for example.
 
This method is nothing new and I am sure many other Cake suers do the same thing.

I did read the thread.  The reason I posted is because I read no where what I suggested. But perhaps I mised a post. SO WHAT. If what I wrote is right which it is and it is helpful what find fault? 
 
What Joden was having a problem with as quoted in my reply to him above is I somehow did get the point of the OP's post. That is not the case. Now its about not reading the whole thread. 
 
Please show me where someone said delete the track and save the MIDI file? After all isn't that really what the OP want to do?

I mentioned it was quite easy to workaround in #11 but I never pointed to a solution myself, so I definitely should get minus points :).
 
Anyway I'm glad people have contributed workarounds here.
As has been pointed out by others, the current behaviour is documented so I'm going to take it off my bug list I think there are other more pressing issues. I'm sure Cakewalk will process the issue appropriately.

John
 
 
Please show me where someone said delete the track and save the MIDI file? After all isn't that really what the OP want to do?

post 21
 
Oh, and the one above it too.

CakeAlexS
I mentioned it was quite easy to workaround in #11 but I never pointed to a solution myself, so I definitely should get minus points :).
 
Anyway I'm glad people have contributed workarounds here.
As has been pointed out by others, the current behaviour is documented so I'm going to take it off my bug list I think there are other more pressing issues. I'm sure Cakewalk will process the issue appropriately.

 
fwiw Alex I think this is a good idea (remove from buglist) . Even as a feature request (the ability to leave mute tracks out of a smf save)  I would be surprised if Cake ever bothered to implement it.