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

Track (Vector3D)

module blob contour id spread tracking

about

This contribution helps to restore a certain spread order from a unordered list of coordinates. This is necessary if you do touch detection or even 3D blob tracking yourself or if you use a Tracker, that handles IDs badly.

Instead of doing it in a plugin, I tried to do as much as possible with good oldschool patching. It would not have worked without the advanced spread nodes, so thanks to woei.

The upload includes generic plugin NearestPair, which can be used similarily to ConnectAll or NearestNeigbour.

Edit:
This contribution is part of the PointCloud toolkit and its most current version can be found at github.

download

Track (Vector3D).7z
27.06.14 [18:26 UTC] by velcrome | 861 downloads
Version 1.1
Show 1 older revisions

Older Revisions

Track (Vector3D).7z
22.06.14 [02:14 UTC] by velcrome | 278 downloads
Version 1.0 incl. Help Patches

tekcor 22/06/2014 - 21:29

Hey velcrome nice one this is very usefull. Will try to use it next time the dynamic spread + Unique ID problem comes up again. So far I worked in this case with a fixed spread size in this case and dynamically isert at certain slices the elements of the dynamic spread.

Noir 23/06/2014 - 02:05

Tnx for sharing

velcrome 27/06/2014 - 18:29

Found some inconsistencies when reactivating ghost IDs and fixed them. also I am now caching Ghost IDs in a special (generically implemented) Cache (Vector3D), that automatically removes IDs depending on their age.

circuitb 04/07/2014 - 03:41

brillant

Gareth.Griffiths 09/07/2014 - 10:12

Very nice. This has potential uses for sensors other than just touch too!

velcrome 16/02/2015 - 00:51

This contribution is part of the PointCloud toolkit and its most current version can be found at github.

mediadog 19/05/2015 - 20:05

This is very useful, and would be even more so if there was a "Previous Slice" output so other associated data could be easily re-ordered. I could not see how to easily modify this patch, so I am using another NearestPairs node after it to get the previous slice positions. Or is it here somewhere and I'm missing it? Thanks!

velcrome 20/05/2015 - 21:04

you are correct, and if you download the most current version here you will see your dream come true ;)

anonymous user login

Shoutbox

~2d ago

joreg: Two #vvvv workshops this week in #berlin: Friday: Physical Computing, Saturday: Computer Vision. Tickets: upcoming-full-day-vvvv-gamma-workshops-in-berlin

~3d ago

joreg: @cznickesz also feel free to join our chat for such questions: chat

~3d ago

cznickesz: @joreg: Yeah, I´ll give it a try! Thx

~3d ago

joreg: @cznickesz: we're hoping this week. but depends on feedback. please test your project and let us know if it works.

~3d ago

cznickesz: @joreg: I should stop asking my questions so cryptic ;-) So right away: is final Beta39 hours, days or weeks away?

~3d ago

joreg: @cznickesz: the idea of an RC is exactly to make sure your projects will work with it. your last chance to report problems with b39.

~3d ago

cznickesz: So how "RC" is the "RC3"? I have to update an old project soon and I´m wondering if I should wait and directly update to Beta39

~3d ago

joreg: @takuma, the "one frame" issue was fixed in RC3 for beta39, see: beta39-release-candidate

~3d ago

Takuma: @joreg thank!! Ill try this. Are there a way to send video texture from vvvv to vl? fromimage node in vl somehow only sends 1 frame

~3d ago

cznickesz: @ravasquez thx, so I need to stop avoiding nuget in the end ;-)