I've been using the app called TRNIO to generate a 3d model (.ply) and texture and I'm having trouble assigning the texture to it. Actually I can assign the texture to it but it's not acting as it should here
I think port socket shape variations could add to readability. I'm certain line-types by cable object-type would (event-only, single object data+event, lists, one day lambdas!). They've been standard in complex engineering, maps and architecture drawings for a very long time because they work.
I was never a fan of the protruding ports, even though I understand the reasoning behind the decision (making cable-port connections more obvious than in QC) I think it's debatable if the logic holds water. To me it can still be hard to see if the angle is close to perpendicular and that could be rectified by making the cable arcs enter ports at a horizontal angle.
Various shapes that ports could take if they were rather than outside nodes but inside ports but open and on the edge would be triangular (normal), square (data), circular (lists and lists of lists), hexagonal (four sides of the hexagon) (events). Or any other permutation. (I don't like the aesthetic of it though so far).
Colouring wires (either randomly or by type) on selected nodes could improve readability as well as dots for events and dash-dot for lists. Although if screen notes or expanded sub-graphs (window-in-window that doesn't exist yet) had coloured backgrounds that could make random colours problematic for readability.
Hi, I've started playing with Kinect v2 and have some questions on how it can operate with Vuo.
Let's start with the data I'm able to read from NiMate. One the left side is "Depth" image encoded with grayscale (0-255) color, on the right is "Encoded Depth" using REP118 protocol with RG channels for econding depth (0-65025).
I'm able to receive the simpler "Depth" image via Syphon and then displace an object with it, it works fine, but amount of details is really low.