I understand sync issues, but I would think that the latency of the
output device would have more influence than not having the playback
device's clock synced to the input. I've never heard of a clock
drifting so badly that, for example, it took 3:05 to play back a 3:00
song. I can't imagine anyone's playing to be of such exactness that the
lack of sample-accurate playback sync would possibly be noticed??? If
you are overdubbing over drum tracks, can you truthfully say that your
note start times are within 1/48,000th of a second??
On 11/18/2013 11:06 AM, jmancine wrote:
The idea is that you would be playing along with a track that wasnt
"in time" with what you are recording. In reality, minor drift is
probably not audibly noticeable but it precludes work that needs to be
On Nov 18, 2013 10:56 AM, "Al Thompson-3 [via Linux Audio]" <[hidden
email] </user/SendEmail.jtp?type=node&node=87953&i=0>> wrote:
I can see this being a problem if the multiple devices were all
input devices, such as the "multiple Soundblasters" mentioned in a
previous post, but if there is a single device used for input, and
another device that is used strictly for listening, what problems
can be caused? I fail to see how it could cause a problem, even if
the clock on the monitor audio chain drifts.
michael noble <[hidden email]
On Mon, Nov 18, 2013 at 9:42 PM, jmancine <[hidden email]
The sync is fine, one clock becomes master.
I should clarify. You didn't specify any kind of sync solution, and
not only recommended using two devices, but stated that it is the
normal way of doing things. Doing so without a sync solution will
result in unsynchronized clocks, which as far as I know, is very much
not the normal way of doing things.
My bands, CD projects, music, news, and pictures:
Staat heißt das kälteste aller kalten Ungeheuer. Kalt lügt es auch;
und diese Lüge kriecht aus seinem Munde: 'Ich, der Staat, bin das Volk.'
- [Friedrich Nietzsche]