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


pack time TimeSpan Date
Credits: tmp robert@intolight.de


If you also think that using the Astronomy nodes to handle times and dates is a pain then this pack could make you happy.

Version history

Since v0.5.6

  • small bugfix in select nodes

Since v0.5.5

  • vvvv beta33.3 compatibility
  • added JSON serializing (important if you use time in your own plugin and want to de/serialize the object in JSON format)

Since v0.5.4

  • vvvv beta33 compatibility
  • fixed toString method in core dll (important if you use the nuget package VVVV.Packs.Time)

Since v0.5

  • vvvv beta32 compatibility
  • Fixed a bug in AsTime (Value Decimal)

Since v0.4

  • AsTime (Value Decimal Advanced)
  • AsTime (Value Decimal)
  • AsTime (Value Unix)
  • S+H (Time Timespan)

Since v0.3 (thanks to sebl):

  • AsValue (Time Decimal)
  • AsValue (Time Unix)
  • AsString (Time Unix)

Since v0.1

  • CurrentTime (Time)
  • LocalTimezone (Time)
  • ChangeTimezone (Time)
  • AsTime (String)
  • AsTime (Value)
  • AsString (Time)
  • AsString (TimeSpan)
  • Time(Time Split)
  • Time(Time Join)
  • Zip (Time)
  • Unzip (Time)
  • Sort (Time)
  • + (Time, TimeSpan)
  • - (Time, TimeSpan)
  • - (Time, Time)
  • + (TimeSpan, TimeSpan)
  • - (TimeSpan, TimeSpan)
  • TimeSpan (Time Join)
  • TimeSpan (Time Split)
  • Select (Time)
  • Select (Time Bin)
  • > (Time)
  • < (Time)
  • = (Time)
  • S+H (Time)
  • GetSlice (Time)
  • SetSlice (Time)
  • DeleteSlice (Time)

Install Guide

  • Download relevant version
  • Copy folder into vvvv directory, like you would do for addonpack

Source Code

You can find the source code here:https://github.com/letmp/vvvv-Time


You can use vvvv-time in your own project by adding VVVV.Packs.Time as nuget dependency to make your nodes compatible with this contribution.https://www.nuget.org/packages/VVVV.Packs.Time/

Comments and bugreports are highly appreciated!



07.11.17 [09:26 UTC] by tmp | 209 downloads


07.11.17 [09:26 UTC] by tmp | 36 downloads

tmp 20/12/2013 - 18:51

And here is a funny new years eve patch.
You can see when everyone steps into 2014 ;)

beyon 20/12/2013 - 20:06

Started on some time nodes before, will have a look later and see if I have something to complement this contribution.

tmp 23/12/2013 - 12:42

v0.2 contains 3 new nodes:

  • + (TimeSpan, TimeSpan)
  • - (TimeSpan, TimeSpan)
  • AsString (TimeSpan)

Gregorian (Time Split/Join) was renamed to Time (Time Split/Join).

The sourcecode in my github was also cleaned up and restructured. thanks to velcrome ;)

colorsound 26/12/2013 - 20:44

thanks for that

Gareth.Griffiths 16/02/2014 - 18:31

Thank you for this TMP! Real nice.

sansui 27/03/2014 - 19:49

Thanks! Was here another plugin like this?
this is very essential.

sansui 27/03/2014 - 23:25

tmp, can I ask a question?
why different 'day of week' order with Gregorian(Astronomy Split)?
today is friday, Greogorian has 6 in DayOfWeek output.
Time(time split) has 5 in DayOfWeek output.

tmp 28/03/2014 - 10:27

hey sansui, of course you can ask questions ;)

as stated on microsofts developer network ( http://msdn.microsoft.com/en-us/library/system.datetime.dayofweek(v=vs.90).aspx ) the constants in the DayOfWeek enums range from 0(=sunday) to 6(=saturday).

the standard gregorian (astronomy split) node uses the SysUtils.DayOfWeek function ( http://docs.embarcadero.com/products/rad_studio/delphiAndcpp2009/HelpUpdate2/EN/html/delphivclwin32/SysUtils_DayOfWeek.html ) and counts from 1 (=sunday) to 7 (=saturday).

it is a design decision but from a computer scientists view it makes more sense to count from 0 to 6 ;)

sansui 28/03/2014 - 11:32

thank you for answer!
I got it.

joreg 21/04/2014 - 16:52

have to admit i didn't have a look at this contribution at all but just stumbled about this nuget http://www.nodatime.org/ and thought it could be relevant..

tmp 23/04/2014 - 17:43

hey joreg!

i also stumbled about nodatime and decided not to use it, because i didn't want the time pack to be dependent of a foreign framework (that is not "finished" yet). but it indeed looks very interesting and offers many additional features that could be useful in vvvv.

regarding to the roadmap ( http://nodatime.org/developer/roadmap.html ) and current limitations ( http://nodatime.org/1.2.x/userguide/limitations.html ) it seems to be a good idea to revisit nodatime when version 2.0 gets released and rewrite the timepack with the help of it.

DiMiX 09/05/2014 - 21:38

thanks for contribution, but i cant run pack with fresh beta32_x86.
had no problem with b31.2

tmp 09/05/2014 - 22:22

ok thanks for the info.
i will fix it on monday!

if you are in a hurry you can already have a look at https://github.com/letmp/vvvv-Time and try to fix it yourself.

tmp 12/05/2014 - 17:45

the time-pack should be beta32 compatible now.

tmp 14/05/2014 - 17:09


the core of the time pack is available via nuget now (vvvv.packs.time).
you can access many functions to handle conversion/arithmetic easily and make your nodes compatible with the time pack.

anonymous user login


~1d ago

gregsn: we have a new release candidate of beta37! download RC5 here: beta37-release-candidate #vvvv

~2d ago

fjen: open call CCL Mainz: http://choreographiccoding.org/labs/mainz-between-us-september-2018 … patch with our markerless tracking system, meet great artists and hackers

~3d ago

joreg: @ryuzaki it is all listed here: node17-workshop-material

~4d ago

ryuzaki: it seems all node17 workshop files are down (?)

~4d ago

u7angel: @ggml videos will come

~5d ago

ggml: some nice instastories from link presentations ::: will there be videos ?