Leonid Makarovsky wrote:
Scott Dorsey wrote:
: At the first shot on the reel, the audio is in synch. At the last shot on
: the reel, the audio is out of synch.

: If you run the tape, how far in do you first notice that it's out of synch?

It's proportional. So in 2 hours it's off by .155 of a sec. In 1 hour it's off
by .0775 of a sec.... Etc...

Right. But how far in do you NOTICE it? How far off can it be, before it is
a problem?

If it's two hours long, there should be PLENTY of places to cut a frame of
audio out here and there to match everything up.
--scott

--
"C'est un Nagra. C'est suisse, et tres, tres precis."

Scott Dorsey wrote:
: Right. But how far in do you NOTICE it? How far off can it be, before it is
: a problem?


I start notice things when it's off by 2 NTSC frames which is 0.06 of a second.


Would you recommend jumping to zero crossing and keep inserting silences?

--Leonid

Leonid Makarovsky wrote:
Scott Dorsey wrote:
: Right. But how far in do you NOTICE it? How far off can it be, before it is
: a problem?

I start notice things when it's off by 2 NTSC frames which is 0.06 of a second.

Would you recommend jumping to zero crossing and keep inserting silences?

No, if the sound is slipping back, I would recommend cutting out video
frames at transitions instead.
--scott
--
"C'est un Nagra. C'est suisse, et tres, tres precis."

Scott Dorsey wrote:
: No, if the sound is slipping back, I would recommend cutting out video
: frames at transitions instead.

That's a good idea. I haven't thought about it. I'll try it with my next
capture.

--Leonid

On or about 18 Oct 2004 18:56:07 -0400, Scott Dorsey allegedly wrote:

Leonid Makarovsky wrote:
Scott Dorsey wrote:
: Right. But how far in do you NOTICE it? How far off can it be, before it is
: a problem?

I start notice things when it's off by 2 NTSC frames which is 0.06 of a second.

Would you recommend jumping to zero crossing and keep inserting silences?

No, if the sound is slipping back, I would recommend cutting out video
frames at transitions instead.


With the error running at 0.0775 seconds per hour, that would mean only
2.3 frames (asssuming 30fps) in an hour. Find suitable places to remove 4
or 5 frames in the two hour program, and you're done.


Noel Bachelor noelbachelorAT(From:_domain)
Language Recordings Inc (Darwin Australia)