Quote:
Originally Posted by stan li  So it sounds a little underhanded, but is anybody doing things in their PT sessions after a mix is completed to prevent this type of thing from going on? Such as doing a "save as" where everything is zeroed out and then hiding the final session file somewhere? |
We print out and export WAV files only. Partially, this is because we also use Radar and therefore I can only guarantee WAVs.
But also, the various methods used are not really a part of the mix, but based on macros and complex set-ups written by the engineer in his own time. In other words, they are software and as such, need to be protected, just like any other software.
Just because the software involved is a series of lines, settings, routings, assigned plug-ins and God-knows what else, and can be seen as a series of commands within a DAW that someone else may be able to copy, in no way means that anyone has a right to be able to copy them.
Most engineers have a series of set-ups that they take with them from gig to gig and DAW to DAW. It is rather difficult to tell a customer that you are going to 'hide' how you work, so the easy answer is to print the tracks as WAVs and just give them that.