One thing that has been giving me heartburn is the way Tracktion/Waveform handles track freezing and traditional busses. I always work with a reference track to compare against my current mix. Of course, you don't want the reference mix track running through your master effects, so I create a track called 'Master' where I place the master effects, and run everything through it except the reference track.
(I'm sure there are other methods involving outputing the reference track directly to a different set of channels, but my current interface only supports the stereo out).
Unfortunately, if your track in Tracktion/Waveform is pointed at anything other than the built-in master bus, you can't freeze the track individually, or use the super handy freeze point plugin... you can only freeze the track it feeds into. So my SOP when I needed to save some CPU cycles on a track was to do a full render of the track, do some renaming, then disable and hide the original track. It isn't a big deal, but it's obviously much more time-consuming than simply dropping a freeze point on the track!
I was hoping this freezing behavior would change in Waveform, but alas it's still the same. But while testing things out I discovered my glaringly obvious work-around: When it's time to freeze, all you need to do is temporarily set the track to output to the built-in master out, then you're free to freeze to your heart's content before resetting the track output back to the home-made master bus track for further editing, which will accept the already frozen track just fine.
Yes, simple and obvious, but opaque to me. I hope this helps anyone else in the same predicament.
Happy Waveforming... and it makes me wonder, are we now to be called Waveformers instead of Tracktioneers?
