Subject: Re: [linux-audio-dev] Random thought on HDR latency compensation
From: Tom Pincince (stillone_AT_snowcrest.net)
Date: Thu Apr 20 2000 - 06:52:13 EEST
I think this is important. In fact, the first thing I do when I use a
new recording environment is to record a single sharp transient to track
1. Then I route the analog output from track 1 to the analog input of
track 2, and record on track 2 while playing back track 1. Then I zoom
in to single sample resolution and drag track 1 until the waveforms are
alligned. The full duplex latency is equal to the number of samples
that track 1 has been dragged.
This issue will probably become more important as the hdr, mixing, and
plug-in activities merge. Before the pre-existing track can be heard,
it must first move through the mixer and any plug-ins applied to that
track. Often more than one track of pre-existing material will be
played back simultaniously, and each track may have different plug-ins,
or a different number of plug-ins. This means that each track will play
back with a different amount of latency. It would be nice if the
plug-in architecture could communicate the latency, in number of
samples, to the host mixer so that the mixer could allign all playback
tracks and communicate the total latency to the hdr for determining
start time for new tracks. This becomes even more complicated if the
mixer allows the musician to monitor himself with plug-ins on the
recording tracks and the playback tracks simultaniously. Creamware
claims this capability, but I have never used it.
Musicians don't monitor from the playback head but recording engineers
do. This is called confidence monitoring, because the recording
engineer can be confident that what he hears is exactly what has been
recorded, and is a feature that differentiates true pro gear from
semi-pro or consumer gear. I would want this feature in my next
recording environment.
Tom
This archive was generated by hypermail 2b28 : Thu Apr 20 2000 - 07:24:55 EEST