» Clock Sources
This site relies heavily on Javascript. You should enable it if you want the full experience. Learn more.

Clock Sources


Recent computers have different clocks running on their hardware. This would not be a problem if the clocks would run in the same speed. Well, theoretically they do, but in reality they typically have a drift of a few milliseconds per hour from each other.

If you work with animations, video, audio and external time sources it is important to know which clock is used by which node. The three main clock sources are:

CPU clock

Aka high resolution performance counter. This clock is used by vvvv's MainLoop (VVVV) (see its help patch) and all timebased/animation nodes of vvvv, like LFO, MonoFlop, Timing, Stopwatch...

System clock

The date/time of your PC. Used by the nodes in the category Astronomy and under some circumstances by FileStream (DShow9).

Soundcard clock

Driving the digital to analog converter of the audio output. Used by all Audio related nodes, also FileStream if the video contains audio.

The good news is, that most animation nodes use the high resolution CPU counter. The bad news is, that the FileStream node usually uses the Soundcard time source. It might also depend on whether your video has an audio track or not. However, the FileStream node has a Reference Clock configuration pin (via Inspektor) to choose a clock source. For more information see Reference Clocks.

In order to find out about the drift between the 3 clocks on your PC run:

 \girlpower\Animation\Compare Clock Sources\_root_CompareClockSources.v4p

CPU Clock vs. Speed Step technology

The CPU clock is only a relative timekeeper, it does not represent any meaningful value like time of day or date. vvvv captures the value at startup, divides it by the CPU frequency and calculates the time values for the animation nodes with this reference value.
It is important to know that speed step technology which alters the CPU frequency for power saving can lead to false readings of the CPU clock, because the CPU frequency is captured only sometimes, like on startup or creation of a node. So if the frequency changes the divisor will be wrong and a false time interval will be calculated. So make sure you turn off any speed step technology (set your system to a high performance power plan) or restart vvvv after the CPU frequency has changed. You can keep an eye on your CPU with tools like CPU-Z.

anonymous user login


~3d ago

domj: Midweek Patch Therapy later today at 17:30 ⌚ Come discuss sequencers, the VL language and your patches. https://discourse.vvvv.org/t/come-join-midweek-patch-therapy/18430/17?u=domj

~4d ago

joreg: Looking for support for your #AI project? Try this: https://www.link-niedersachsen.de/link-masters

~11d ago

blausand: Ill be in #Warszawa next weekend. Any #vvvv people around to meet?

~12d ago

sebescudie: Last call, c'est ce soir : webinaire en français pour débutants sur #vvvv gamma! https://thenodeinstitute.org/event/introduction-au-creative-coding-avec-vvvv-gamma-francais/

~13d ago

domj: Ultra high definition volumetric visualization using GPUDirect storage https://youtu.be/GAZP1NcdWMo

~16d ago

CeeYaa: thx for V4-Meetup - some days ago 40th_RetuneStudioVisit from old friends RefikAnadol and Quadrature https://vimeo.com/429510091

~18d ago

david: 4. worldwide vvvv meetup will be here...https://www.youtube.com/watch?v=i0zd68tDUVE

~21d ago

mediadog: @metrowave Magnetic repulsion has always been pure magic to me, proof we only sense a small part of the universe - thanks!