» PathVectors (3d)
This site relies heavily on Javascript. You should enable it if you want the full experience. Learn more.

PathVectors (3d)

plugin
Credits: by herbst, idea from ArcLength (john, frank, gregsn, joreg), funding from Uberact

about

Some of you might know the ArcLength module. It's very nice because it's able to place points at specified distances along a spline.

Unfortunately, it's not spreadable (some of the nodes needed for this don't have general purpose, use- and meaningful spreadable implementations).

Thus here I present to you PathVectors (3d), rewritten as plugin, spreadable, binsizeable and fast.

You basically input a spread of splines and a spread of percentages at which to place new points. See the help patch for different usecases.

download

PathVectors.zip
02.09.13 [01:50 UTC] by herbst | 1555 downloads

sunep 02/09/2013 - 10:46

High Like

please put this in the addon pack

u7angel 02/09/2013 - 12:27

awesome!

hierro 02/09/2013 - 18:14

good job :D

m4d 02/09/2013 - 18:38

neat!
(also what sune said)

lasal 04/09/2013 - 00:03

finally!
thanks

Desaxismundi 04/09/2013 - 15:17

woop woop!

graphicuserinterface 04/09/2013 - 23:02

exquisite

u7angel 09/12/2013 - 12:14

add to addonpack ?

readme 11/03/2014 - 15:02

Found a bug, which only seems to appear if Helper Points AND Inputs are being bin sized.
The sorting is off, see attached screenshot.

Luper 26/01/2016 - 20:00

yep that wrong sorting bug happened to me also! was going totally nut XD

eno 10/02/2016 - 10:45

chapeau. long needed thing! Finally something to design envelopes.

u7angel 21/12/2016 - 14:35

tagging thisobsolete is maybe a bit overhasty since it still works well and is production-proven. not everyone wants to apply VL to production right now.

tonfilm 21/12/2016 - 16:15

@u7angel i've just downloaded it and checked the plugin and it's code.

you're right. but not because you shouldn't use nodes written in VL for production, but because the plugin is written in a very efficient way that makes it 5-10 times faster for high spread counts and this clearly took more development time and brain power than the new ArcLength node.

readme 21/12/2016 - 16:21

It does however still have the issues I reported above

tonfilm 21/12/2016 - 18:10

@readme thanks for pointing that out. so the decision making goes as follows:

  • always use the vvvv built-in ArcLength at first.
  • if that affects performance because you use very high spread counts use PathVectors
  • if you need to bin size helper points and inputs then go fix the bug

anonymous user login

Shoutbox

~12h ago

joreg: We're live now! Please join or watch the #vvvv meetup by following this link: 15.-vvvv-worldwide-meetup

~11d ago

andresc4: gamma+stride+fuse+standaloneapp+soputoutput+oscinput = lovvvvvveeeeeee!!!!

~14d ago

joreg: @pechart thanks for the flowers!

~14d ago

pechart: Just a big shoutout to the whole vvvv devteam and the friendly community! It's fantastic to export patches to standalone apps. THX!

~23d ago

daviddenker: We are looking asap for 3x Azure Kinect to rent or buy. Any kind of help appreciated! :-)

~26d ago

mediadog: Hmmm md.ecosystem link on staff pics page is not found

~28d ago

schlonzo: physics constraints and forces plz?

~30d ago

karistouf: thank you @gml but im thinking about and old version of vvvvv. There was a redraw with HSL of each pixels

~30d ago

schlonzo: no more previews? is there a 4.0 stable?