Thank you the idea. However, the very first step would be to provide a version that supports all the Kinect correctly (including the 1473 model). Then we could study your idea.
In the meantime, you could use Synapse : there are some tutorials on their website, especially how to share the Kinect result via Syphon (for this, yes you will need Quartz Composer).
As written in the first message : "Only Kinect 1414 is currently supported. Kinect for Windows and Kinect 1473 are not." That's why you got a black screen.
Best. Philippe
PS : I deleted your same message that you post on this thread, because it wasn't the right topic
Hi there Thanks for sharing this app. I was so excited, it may sound crazy, but I had no idea the Kinect could be tilted remotely. I nearly fell off my chair when I heard it buzzing and tilting behind me! The depth image is brilliant compared to the one I'm getting via Synapse, but I can't get it to appear in Syphon. Kinectmask2Syphon appears in the dropdown, but I just get a black screen. I'm using a 1414 on Mac OS X 10.10 Any ideas?
None of the ports used in your QTZ files are used by Millumin (unless you changed the default values : 5000 and 5001 in OSC settings). For info, Millumin uses the same libraries as Quartz Composer (Quartz.framework), so the rendering is the same. I tested the node "qcOSC", and everythign is fine. Be sure Quartz Composer isn't running while you execute your QTZ file in Millumin.
- of course, even without Quartz Composer running while executing the composition in Millumin.
- only the qcOSC Patch in the composition with no other patches inside.
- with other ports in the qcOSC Patch. It does not matter which port I set in the qcOSC patch. It always appear the error message in Millumin. If no port is set, the error message does not appear.
I tested again a simple patch with qcOSC, moving a circle when receiving an OSC message : everything is fine, and behaving as expected. Did you contact qcOSC support to know more about the meaning of this error (it's generated by qcOSC itself) ? Maybe a sandboxing issue.
Comments
As written in the first message : "Only Kinect 1414 is currently supported. Kinect for Windows and Kinect 1473 are not."
Best. Philippe
Thank you the idea.
However, the very first step would be to provide a version that supports all the Kinect correctly (including the 1473 model). Then we could study your idea.
In the meantime, you could use Synapse : there are some tutorials on their website, especially how to share the Kinect result via Syphon (for this, yes you will need Quartz Composer).
Best. Philippe
As written in the first message : "Only Kinect 1414 is currently supported. Kinect for Windows and Kinect 1473 are not."
That's why you got a black screen.
Best. Philippe
PS : I deleted your same message that you post on this thread, because it wasn't the right topic
Thanks for sharing this app. I was so excited, it may sound crazy, but I had no idea the Kinect could be tilted remotely. I nearly fell off my chair when I heard it buzzing and tilting behind me!
The depth image is brilliant compared to the one I'm getting via Synapse, but I can't get it to appear in Syphon. Kinectmask2Syphon appears in the dropdown, but I just get a black screen.
I'm using a 1414 on Mac OS X 10.10
Any ideas?
The image sent via Syphon has black and transparent areas.
Please follow the tutorial in the first message for more information.
Best. Philippe
None of the ports used in your QTZ files are used by Millumin (unless you changed the default values : 5000 and 5001 in OSC settings).
For info, Millumin uses the same libraries as Quartz Composer (Quartz.framework), so the rendering is the same. I tested the node "qcOSC", and everythign is fine.
Be sure Quartz Composer isn't running while you execute your QTZ file in Millumin.
Best. Philippe
Hi Philippe,
i testet it several times with different options.
- on different computers.
- of course, even without Quartz Composer running while executing the composition in Millumin.
- only the qcOSC Patch in the composition with no other patches inside.
- with other ports in the qcOSC Patch. It does not matter which port I set in the qcOSC patch. It always appear the error message in Millumin. If no port is set, the error message does not appear.
kind regards
I tested again a simple patch with qcOSC, moving a circle when receiving an OSC message : everything is fine, and behaving as expected.
Did you contact qcOSC support to know more about the meaning of this error (it's generated by qcOSC itself) ? Maybe a sandboxing issue.
Best. Philippe