Scratchpole's picture

@Scratchpole

Scratchpole's picture

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

Scratchpole's picture

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/.

Scratchpole's picture
@Scratchpole commented on @Scratchpole's Discussion, “Have you seen OpenPose?

I had some further correspondence with Ginés: 'So far OpenPose only outputs 2D keypoint locations. With 3-D cameras yes, it would be able to output 3-D keypoints (there is a 3-D demo inside OpenPose), but we still don't provide joint angles (not sure if it's a requirement for you).

About the output, I understand it should be easy to modify the output to write OSC files rather than JSON files if your developers have knowledge on how to write those kind of files in C++ (I am not familiar how hard this OSC format is). If they add that functionality for their own OpenPose version for Vuo, they can definitely contact me again and I can try to officially join it to OpenPose so you would be able to use always the most updated version of OpenPose (not your custom version).

About licensing I am just an engineer (so not an expert at all), so not sure what your idea of its use is, but if it's released for free I think it should be fine (but check the license and previous answer from David to be sure).'

Scratchpole's picture
@Scratchpole commented on @Scratchpole's Discussion, “Have you seen OpenPose?

I received a reply within minutes which was a nice surprise, but I'm still not 100% clear on the answer or that they were totally clear on what I was asking:

'A point set generated from OpenPose software wouldn't be considered a derivative. (A derivative would be modifications to the code itself, not products of the code). So, that point set could be distributed. In order to generate that code set for commercial purposes though, a commercial license would be required.'

I suggested that they comment here if they would care to do so.

Scratchpole's picture
@Scratchpole commented on @Scratchpole's Discussion, “Have you seen OpenPose?

Well I guess this line from the 'license' says what we don't want to read: 'DERIVATIVES: You may create derivatives of or make modifications to the Software, however, You agree that all and any such derivatives and modifications will be owned by Licensor and become a part of the Software licensed to You under this Agreement. You may only use such derivatives and modifications for your own noncommercial internal research purposes, and you may not otherwise use, distribute or copy such derivatives and modifications in violation of this Agreement.'

But I'm contacting one of the dev's to clarify anyhoo: https://www.gineshidalgo.com/

Pages