Very interesting to see how people are putting it to use.
My process would be fairly basic ( and I think close to the sweet spot for how MR was intended):
End phase, multiple versions such as Minus Vocal, LV +1dB, down 2db, etc, No Drums, etc
Most people doing TV pitching want multiple vocal levels and I would like to have all those stored in the project file instead of multiple "Save As----" versions. 
I'm going back to prior client projects and doing testing, and so far it looks like MR is pretty reliable. Haven't heard any trainwrecks like the first time I used it...so that's promising :) 
Thanks for all the replies...really helps.

pilutiful
To be honest, personally, I dare not to use it... It seems there can be alot of things that can go wrong. But that could just be me...

On what do you base that statement on? If you don't use it how would know if things go wrong?

Kev999
But what can it do that Save As can't do? I must be missing something obvious.

Good Day,
 
I guess my biggest issues are my own, "Dohhhhhh! moments", after forgetting not to save initial mix scene, and/or one somewhere in between tweaks, one way or another you could have long list of mix scenes, or save as files, or both, if you want to wear a belt and suspenders, and not get caught with your pants down. LOL. (and not to mention saving individual FX settings as presets).  
(Luckily and thankfully, Craig has accumulated and shares a lot these presets and tips from over the years).
I probably also still tend more toward "save as" for more global or drastic changes, and as necessary for clip editing changes or for what I consider a session, (e.g. Lead Mix 1, Mix 2, etc.), and perhaps I haven't yet fully appreciated mix scenes function for within or between sessions and/or projects, or more so to remember to create and give a meaning full name to a mix scene after spontaneous fader, FX or pan tweaks, its usually like, crap, I should have saved that last 10 minutes of mixing, 5 minutes ago, at least there's some undue history if you haven't closed session. I guess with mix scenes it allows for some undue history recall between sessions and even different projects, history dependant on how often you remember to save them, and with a meaningful name, and how common and interchangeable the mix scenes details may be between projects.
 
What would be a nice addition to Sonar is to have more extensive or comprehensive tracking of undo history, such as Izotope uses, i.e., every tweak to anything is exactly identified and shown in current history, but in addition to be able to save and recall undo history files between sessions (also not possible with Izotope). So somewhat like automatically saving a string of mix scene changes made to anything over the given period of time, i.e., from a starting point, to a saving point, say after completing the tweaking a drum mix, all changes are listed and selectable in a mix scene history file rather than a number of distinct mix scene files, (and automatically saving an accumulating undue history file, along with saving project file). Even a text file listing of undue histories could be a useful reference.
 
I guess in getting older I want to use less brain/memory resources into remembering what I did yesterday, and more thought into what I want to do today. LOL.
 
Cheers
    
 

Actually the Mix Recall Settings Dialog documentation is very specific about what Mix Recall does indeed recall: controls (track and bus), track and bus automation envelopes, and FX. Furthermore, there's a complete listing of all recalled controls under the Advanced heading of the documentation.
 
If the Mix Recall documentation doesn't mention being able to recall something, then it doesn't recall it. For example one could hope that editing clips is not considered an editing process but a mixing process, or that Mix Recall should recall the console view configuration because one could consider that part of mixing. But if something isn't on the list of what gets recalled, it's not going to get recalled. 

Reading about is a very good way to get started with any feature.  Working with it and learning it by using it is going to yield a greater understanding. In the post I referenced on the first page it was my testing and using it that got my attention on what it could do.
 
   

As John mentioned above, just experimenting with it teaches you a few things.
 
My two tips:
If you mute clips in one mix and not in another, don't expect that to be represented.
Also, when I mute a track, I habitually hit Archive as well. Mix recall won't un-archive for a prior mix.
Don't do that with MR :)
 
Stxx-I used to be a big UAD user; no longer..but that would've been a deal breaker. Have other UAD users commented on this issue as well?