MartinusMagneson's picture

Magneson (@MartinusMagneson)

MartinusMagneson's picture
Magneson commented on keithlang's Discussion, “🕶 Design patterns for filtering

You could try something like this:

Looks a bit excessive, but should scale up pretty easily to 2d and 3d grids as well. The general idea is to select forwards, not backwards. That way you check the points and create and modify any layers/images/objects on those points based on an arbitrary input (mouse position in this case).

MartinusMagneson's picture
Magneson posted a new Feature Request, “Camera tracking

Camera tracking

For virtual studios, camera tracking is starting to become the go-to effect for tying in the AR. Looking at some different approaches I stumbled across this paper http://rpg.ifi.uzh.ch/docs/ICRA14_Forster.pdf which promises single camera tracking in realtime. As this is also a component of the ROS that I've seen mentioned for blob-tracking, could this be a possible implementation for Vuo?

Notes from Team Vuo

Vuo Pro: 

Yes — requires a Vuo Pro license

Complexity: 

●●○○ — A few weeks of work

Potential: 

●●○ — Could expand community
MartinusMagneson's picture
Magneson commented on video piglet's Bug Report, “Vuo crashes on launch

If you launch the macos console before starting Vuo and filter with "vuo" in the top right corner, it should display why it crashes and the offending node as well iirc.

MartinusMagneson's picture

And I assume "Select Latest" isn't working in this scenario?

MartinusMagneson's picture

Not on a mac right now, but I assume a workaround could be to feed the select node to a "Hold Value" node. Then for the output of each node going to the select node, add an "Allow Changes" node and send the output of those to the trigger/update port of the hold node. A caveat would be that if you change the value of the input that is not selected, the hold node would change to the current value of the selected input.

To maintain concurrency in the graph you might have to send the allow changes output to the select node, and then use a "Spin Off Event" node to fire the events for the hold node (but I'm not sure about this).

Alternatively you could delay the switching of the port until you changed the value in the same manner, not sure about what would be more tidy and/or efficient.

Pages