Stem rendering: -leaves multiple (and confusing) render files in your media directory; for example, ever try going back to an old mix and asking yourself "Is it 05_Bass_Stem_blahblahblah.wav or 06_Bass_Stem_blahblahblah.wav or maybe 11_Bass_Stem_blahblahblah.wav... Not really a good use of time. -Doubles your track size. Even if you're only using 10 tracks (really, I doubt it's the majority working with such small projects but let's say) going up to 20 has just radically changed the whole workflow of your project. Do you push the originals to the end of the project (leaving only your "freezes" at the front end)? Do you go every other (and risk muting/not muting the correct variant)? Doubling your project track count, while quite doable, is in no way a small deal workflow-wise. If you search old Freeze feature requests you'll even find me, Ngarjuna, saying "Yeah, but isn't stem render a suitable workaround?" What I have discovered is that no, in fact it really isn't. It is the only workaround (so people are using it I'm sure) but it's failing to take into account some of the key features of what Freeze achieves. I don't mind people pointing out that you can go the long way and use stem renders, but several people put a fair amount of time and effort into Freeze macro systems, which is what I'd like to know more about. Are Bevosss or Mercado_Negro maintaining these macros? Is anybody using them (or some variation thereof) with success?