Hello

Me am Frank, living in Cologne. I ordered my page in functional topics rather than technical. Trying to put some of my stuff onto it now and hope some of you will find it useful.
Feedback is welcome as modules are working for me and hopefully for you either ;)

Table of contents

coming soon...

Multidimensional arrays

Spreads in VVVV stay always in linear order, which is sometimes quite limitating in cases you have different amounts of data (bin sizes).
I did some sort of MultidimensionalSpreads for this Actually modules Set and Get right now, giving you access to specific parts of a spread. In detail you can arrange a spread like this MultiArr=(0.1,0.2,0.1),(1,1,1,1,1,1,1),(0.75,0.81) . More to come.

Streaming video

I tried FugStream(1.11) and its not working at Udp, sadly. Only, MEM and TCP is working - but later has an remarkable delay. A suggestion of Joreg gave the starting point for building it up by VVVV-own Udp node. UdpStreaming is working stable now and __streams video to your other computer by Udp, video size is limited to 220x220px maximum, though.
A deeper look at FugStream has shown, that Udp sender IS working, but not properly. There is a limit at 64x32 px, because of not working image splitting across several Udp-packets. 64x32px is not massive, but FugStream is still faster to compute than transmission by choice above.

Working flow

I was always confused by sudden disconnection of subpatches after moving or copying parent-patch. Its because of absolute and relative paths of subpatches.
At working progress sometimes lower versions of patches can't run properly, because some subpatches were edited and overwritten by newer versions. Keeping lower versions consistent barely possible.

For this cases I've written two modules solving this issue:
SetModuleRoot is reading all subpatches in patch and changing absolute and/or relative paths to V4-root path related paths (":MODULES:"). Your subpatches will stay connected after moving your patch.
CreateSaveVersion (is dependent of former module and) copies all modules, plugins and shaders you use in current patch to a specified save folder. In there will be created a subfolder with timestamp, where its being stored as well as all needed VVVV-related binaray files. This subfolder will keep a consistent and running version of your current working state. And nothing more or less.
Sorry, its still Beta-state and somehow buggy. Im on it....