If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
==
"In Japan, I was in a relationship for seven years and my boyfriend never once heard me pee." --Miho Ogawa, 29, a Japanese waitress living in New York / Giant Robot 24
1. dropped frames. If there are too many then the audio drifts according to how many have been dropped. AVI_IO helps this by filling in the drops with the previous frame. This keeps the frame count right.
2. incorrect frame rate. IF you set 30 fps instead of 29.970 for NTSC video this can cause things to get out of whack. Also many bundled capture programs (Matrox's PC-VCR for example) do not lock the frame rate to the proper value. AVI_IO can also help this.
3. the typical filesystem optimizations for editing have not performed. Check here for what needs to be done;
This is a Matrox page but the tips apply for any editing system.
4. IF this is a DV project the problem could also be the cam. Most consumer DV cams (and some rather expensive ones) use unlocked audio. This means the audio sample rate doesn't exactly match the video rate due to a lack of precision in the audio sampling rate. This small error can accumulate to an error of up to a couple of seconds per hour. The only fix is to force a render of the audio stream in your editor or, in the case of MSPro6, to use its built-in DVAudio codec.
taping from TV tuner
never had problems in 9x
0 dropped frames @ 30 fps (ATA100 ibm deskstar 7200rpm hd)
celery 600a, 192mb ram
tried 29.970 and it dropped 1 frane a sec
with the same problem with the audio about 1-2 seconds ahead of the video
hmm?
==
"In Japan, I was in a relationship for seven years and my boyfriend never once heard me pee." --Miho Ogawa, 29, a Japanese waitress living in New York / Giant Robot 24
Comment