Post
by Mark Alan Miller » Wed Aug 06, 2008 10:08 am
The issue I tested for was simply to see if a bounce-to-disk or a re-record internally to a track yielded the same data. They did.
I don't know about this 'hold down the mouse over the plugin' thing, never heard of it before, and I imagine that if it's true that a plugin somehow changes its math when being moused on that it would yield a different sound. But that's not what I was debating. As I have not tested for plug-in "wobble", to coin a phrase, I cannot comment on it. But I want to try it. I'm on PT 7.4, so I don't know if there's any relationship to any version 5 shenanigans...
And to play back even two copies of the exact same file, the exact same data, using different clocks would unlikely yield a null if one was inverted, even through an analog board. They have to be sample-locked for the test to even be relevant. Also, the likelihood of getting 100% nulling on an analog desk is low as no two channels are going to sound 100% the same due to tolerances in components in the circuits.
I have not tried the third option - running a multitrack mix out of PT onto another digital recorder and comparing that in a 'null test' to either or both a bounce-to-disc or a record-back-to-a-track mix. Could be intersting.
I never bothered, because the debate was always how bad 'bounce to disc' sounded vs. recording back to a track.
I surmise, though, that the difference between recording a multitrack mix out to another recorder, and recording it back to another track would be negligible as far as anything goes, unless the system was running so taxed that putting another track in record strains it to the point of - but not quite getting there - putting up a 'PT cannot get data/CPU taxed, etc...' error.
In this case, too, though, the clocking would all have to be the same, as, again, two different clocks will almost never run at exactly the same speed, nor is the likelihood of lining the two files being compared up at exactly the same starting sample very good at all. Without the exact same start time and clock, a null test won't tell one anything.