Quote:
Originally Posted by WinTaper
Okay one more try - here is an analogy...
Let's say I have really bad headphones that introduce a 1 second delay (48000 samples @ 48K). For sake of example, assume zero input latency. I'm overdubbing a track, so I'm playing along with something coming from Pro-Tools. Obviously, with my bad headphones, by the time I hear something, the transport is already 1 second ahead (48000 samples). I play along with the music as I hear it.
If I look at the tracks in edit view and zoom in, I can see/hear that the overdubbed part is 48000 samples late - the amount of delay introduced by the bad headphones.
What should happen if everythign were correctly aligned, is the recorded track would get 48000 samples discarded at the head and the start point moved up by the same amount, thus compensating for the headphone delay. The track would then be aligned with the existing track and the physical wave files on the disk would also align.
Alt+H doesn't change the physical files - I'd never be able to export the session and there's no way to tell from the files themselves which ones need what offset. Back to the example...
Since I use the same headphones for everything I do, I'd like to be able to enter this offset as a fixed value somewhere. Its not an insert. Its not about low/no latency monitoring. Its about sample-accurate alignment of overdub tracks.
Now, in my case, the additional delay isn't from bad headphones, but rather from my mic pre-amp A/D converter connected via ADAT to the RME 9652. Its basically a fixed offset on all hardware inputs but its not being reported by the RME card back to Pro Tools.
This offset is in samples - not milliseconds. So anything recorded through this interface would need this offset applied. Exception: as someone else pointed out ... theoretically, if I'm recording all new and not overdubbing I wouldn't need this compensation. It wouldn't hurt anything tho.
Somehow I'm getting the feeling PT doesn't do this.
|
Unless I'm missing something, the point that was being made before is that you can adjust for this in milliseconds.
Just convert samples to milliseconds.