From: Vesa <di...@nb...> - 2014-01-17 16:34:30
|
On 01/17/2014 06:28 PM, Tres Finocchiaro wrote: > @Tobiasz, > > No, I don't think anyone is suggesting "export tracks" uses settings > from "export track". > > Regardless though, "export tracks" is reserved for the mastering > process, so in my opinion, settings not being remembered from the > "export tracks" are not as much of a burden as the setttings on the > often used "export track". > The "export tracks" option as it currently works is pretty useless for mastering (or much of anything). All it does is it basically soloes every track in sequence and exports. This means that any sidechaining with peak controllers gets lost, so if you use sidechaining in your project, it's no use at all. And I'm not sure if even automations work with it... I think this feature needs to be rewritten so that peak controllers etc. can still "hear" the output of the other tracks, but their output just doesn't go to the output. Then it could be a really powerful feature (export tracks, open in audacity, do final mixing/mastering...) |