On 05/08/2012 04:25 AM, J. Forster wrote:
The SMPTE Time Code was on one line in first 20 odd of the Verticle
Blanking Interval (VBI), along with the Color Bars, Multiburst, Closed
Captrion data and some other things.
It was not accurate to microseconds. It had a format of HH:MM:SS:FR
(Hours,
One area where accuracy is important is not because of pitch (nobody can
hear 1ppm differences), but because of the need to synchronize sound
from different sources, particularly with video or motion picture frames.
1000 seconds (20 minutes, give or take) with the sampler off by 1ppm
will be
A movie may be 7000 seconds, and you may need a fairly stable timebase,
but every movie I've watched is made up of short (300 second) scenes that
are placed sequentially on the framework.
You are not meshing together a pair or multiplicity of 7000 second event
sequences. E#very time you edit in
On Mon, May 07, 2012 at 06:13:56PM -0700, J. Forster wrote:
A movie may be 7000 seconds, and you may need a fairly stable timebase,
but every movie I've watched is made up of short (300 second) scenes that
are placed sequentially on the framework.
5-10 seconds a cut is quite common,
We had time code to sync a number of separate A/V recorders so that
during editing you can cut from one to another seamlessly. I didn't
calculate or look at how tight the sync had to be. The mobile cams
could be out there for a while, maybe an hour or more, starting and
stopping
When I was doing some video production, we would first Black Burst the
tape. This was done from end-to-end as the lattice.
Then we assembled the segments onto the that tape. The inserted segments
were always an integral number of frames.
The source deck for the playback was slaved to the
Yes, the nice thing about that is it is so easy (if you prepare ahead
of time). Here is what we used:
http://en.wikipedia.org/wiki/SMPTE_timecode
Both have their uses.
On 05/07/12, J. Forsterj...@quikus.com wrote:
When I was doing some video production, we would first Black
The SMPTE Time Code was on one line in first 20 odd of the Verticle
Blanking Interval (VBI), along with the Color Bars, Multiburst, Closed
Captrion data and some other things.
It was not accurate to microseconds. It had a format of HH:MM:SS:FR
(Hours, Minutes, Seconds, Frame) ... the frame was
On 5/7/12 6:13 PM, J. Forster wrote:
A movie may be 7000 seconds, and you may need a fairly stable timebase,
but every movie I've watched is made up of short (300 second) scenes that
are placed sequentially on the framework.
You are not meshing together a pair or multiplicity of 7000 second
