Scratchpole's picture
Shared by on 2017.12.14 11:47

Hello all this is my first share. I hope you can help me improve upon this composition. It is sometimes/unexpectedly/itermitently grinding to a halt and I can't determine what is wrong. (I realise I should probably make some sub comps but not sure which bits yet).

I have included the NImate project file if you have a licence, for those without a license it's set to: Track Single user, basic skeleton, no hands, Origin= sensor coordinates. The camera is set to adjust for the Kinect positioned on the floor.

I tried export as an app but the audio didn't play...

Crystal man

+5
Interesting
+1
Helpful
+3
Unique

Download composition

Other categories

Tested with

Vuo version:
OS version:

Comments

It is sometimes/unexpectedly

jstrecker's picture
Submitted by

It is sometimes/unexpectedly/itermitently grinding to a halt and I can't determine what is wrong.

Oddly it looks like NI mate is sending a lot more OSC messages than it says (instead of 30 fps, about 120 fps, which is around 1,200 OSC messages per second). That's a bit much for Vuo to digest. Adding a Hold List node, as in the attached composition, should help.

Unless I'm missing something, you could skip the Get Mesh Values and Make Mesh with Values, and maybe improve performance a bit.

I tried export as an app but the audio didn't play...

The problem is that your audio file didn't get copied into the app. Vuo can automatically copy audio files in some cases, but if it misses your file, you can copy it into the app manually. See the manual section Exporting an application.

Well, the Hold Value can't go

jstrecker's picture
Submitted by

Well, the Hold Value can't go between Receive OSC Messages and Filter Skeleton, because Filter Skeleton can't skip any of the messages. (NI mate sends a series of messages for each frame. When Filter Skeleton gets the whole frame, it emits an event.)

The earliest point where you could insert a Hold Value is after Filter Skeleton. The reason I didn't suggest putting it there is because you'd have to put a whole bunch of Hold Value nodes, one for each output of Filter Skeleton. Anyway, it's probably just fine to put the Hold Value a bit later in the chain. The math and list stuff just after Filter Skeleton probably isn't as performance-intensive as the graphics stuff at the bottom.

I'm glad you like the look of

Scratchpole's picture
Submitted by

I'm glad you like the look of it. You don't need to compile them, just download them and put them in the correct folder. ( Please read my comment below and download the fresher version). Here's the important bit of text from the Parabox nodes Read Me: Place the co.parabox.nodes.vuonode & all .vuo files (found in the bin folder) in your User Modules folder: ~/Library/Application\ Support/Vuo/Modules/.

Now I remembered that I

Scratchpole's picture
Submitted by

Now I remembered that I removed those nodes in a later revision after Jaymie pointed out above that they were not being used (I had put them in when playing around trying other things). Jaymie also added the Hold List which fixed the issues with too many OSC messages being sent from NImate.

So I have now replaced the compostition again with the correctly working version. Hope you get it running @marioepsley, please do let me know if you are successful. Cheers

Add comment

Log in or register to post comments