This is probably one of those requests that sounds simpler to implement than they are, but it would be nice to have the option to use a scale of 0 to 1 to move through these. 0 = linear, 1 = exponential. 0 = easing in, 1 = easing out.
This would mean that the in + out option would not be available in this scenario, but that would be possible to math around in implementations. It would also bring about the option to animate the easings which would be fun!
The main purpose of this would be to neat up some nodes with separate curve modes and easings for 2d/3d/4d points which can look a bit excessive at the moment.
Hello Jaymie, thank you for your answer.I understand Vuo's choice. Of course working with the beta 2.0 is an option but I don't know how to get it and I'm probably not the good user for reporting some bugs (I'm new with this type of app.) I'm a sound engineer and musician and I'm mainly focused for now on what I call the interfaces (the outside world ,midi, audio, controllers, osc, ...) creating visuals will come later. Thank you
Thanks for the tip. We looked into OpenPose in OpenCV to see if it would be compatible with Vuo. Although the OpenPose model dataset is still noncommercial, there's an alternative dataset with a license that should work for us. They say that macOS support is coming sometime in 2019. With macOS support, we could consider OpenCV for the built-in skeletal tracking feature request.
better tracking than the other two, based on our brief testing
uses regular camera, not depth camera
requires macOS 10.13+, not Windows/Linux-compatible
The other 24 libraries we considered wouldn't currently work with Vuo for one reason or another: Windows only, proprietary or non-commercial license, incompatible programming language, etc.
So we will likely choose one of the above libraries, unless something better comes along by the time we implement this feature request.
All of the above libraries input an image rather than interfacing directly with a Kinect or other camera. PoseEstimation-CoreML uses a regular video camera. Skeltrack requires a depth camera. BodySkeletonTracker says that the depth camera is optional, but we weren't able to get it to track without one.
Now that we have a better idea of the libraries we might use, I've bumped this feature request's complexity rating down a notch, meaning we will be more likely to choose it compared to a more complex feature with a similar number of votes.
Chris, I discussed your suggestion with the team. While I totally understand not wanting to spend money on something that's going to be free soon, it would take us some time and possibly even a new release to unlock the trial version. We think it would be better to focus on getting the 2.0 beta release out instead.
●●●○ — It prevents me from completing a specific task with Vuo.
Steps causing the bug to occur:
Make Grid Points Object
Make Make Grid Lines Object
Input image as shader
Image displays stretched vertically on the point grid, it's correct on the line grid.
Have you found a workaround?:
But if I use image resize and feed it a 1:1 ratio image it displays at the correct proportions. Sadly this does not resolve the issue. I want to feed the same image to both a point and line grid and have the image the same on both.