Checking for time code deviations
|
Checking for time code deviations |
|
When you have a useable recording with video and audio in sync you must check the third factor: time code. It is being generated by the computer with a certain number of frames per second (default: 25) in compliance with an ideal demand that not a single frame is dropped in the process.
Sometimes that really happens, but usually there are small deviations that have to be corrected before you can start working. If the number of dropped frames is unusually high, please check the troubleshooting guide.
Below are some examples of how many frames are dropped when using the PicVideo MJPEG codec V2 (or how few, if you choose to look at it that way) .
70's Show 22, 16 minutes Compression: 100% 0 frames dropped
|
70's show 22, 22 minutes Compression: 90% 8 frames dropped |
Fawlty Towers 11, 29 minutes Compression: 90% 5 frames dropped
|
Fawlty Towers 11, 29 minutes Compression: 75% 2 frames dropped |
Atlantis High 18, 26 minutes Compression: 75% 5 frames dropped
|
Atlantis High 18, 26 minutes Compression: 100% (3,6 gb!) 5 frames dropped |
The Practice 15, 40 minutes Compression: 75% 1 frame dropped
|
Screamers, 104 minutes Compression: 75% 9 frames dropped |
Screamers, 104 minutes Compression: 95% (3,6 gb!) 10 frames dropped |
Revenge, 54 minutes Compression: 95% 1 frame dropped
|
Okay, so some frames are missing (and sometimes extra frames are added). What do we do about it?
We calibrate the time code, a process similar to something most of us already know: recutting.