+1 kinect v2 and future for v4 for azure openpose photoshop in

directx in and out leap motion real sense zed

+ 1 See sensors and suggestions above . Also cv. jit would be nice

Thanks in advance!

+1 Kinect, Zed, Leap Motion, Wacom

+1 Kinect, LeapMotion, Wacom - also keep publishing sources and let users choose older driver versions if need be (don't force udpate please, those things are expensive and programmed obsolescence is around us everywhere already)

+1 Kinect v1 and v2 (and other RGBD devices like Intel RealSense)

+1 Kinect, LeapMotion, Zed

I think they would of given it to us by now, if this was their intent.

Phiol, sadly yes. I think we'll have to figure some way to relay messages from the sensors. For now, I'm gonna stick with Leap motion v2.3 and previous externals. Downgrading and building from source is the only thing we can do now I guess. Raja, ofcourse it's a request but much needed one. Max is supposed to be the platform to experiment and develop. I think what we are really frustrated about is all the previous work/projects done with these sensors. nothing against cycling74. Also, I'm not sure if these companies would consider such a request. Leap Motion just discontinued a bunch of legacy APIs in Javascript, Python and C++, just like that.

Raja , TouchDesigner include vanilla objects for interactive hardware. I believe they are around 12-15 employees. They manage to put out a new build increment on average , every 2 weeks. sometime a week , sometimes a month. Cycling 74 , will post newsletters celebrating the virtues and how cool max is as an interactive software with interactive hardware. When this is only true based on the generous efforts of 3rd parties. The are a small team of circa 25 I believe and what they come up with is amazing and far beyond many. But it's a real time data manager / visuals and yes music software. they should be researching and putting openpose and densepose externals . not hoolyhook and not diablodale for kinect 1 and 2 and all the aka and etc... ambisonics are all done by 3rd parties like ircam and the hoa and spat and icst and a good build in hrtf system that is straight forward like in Unity.

Of course you could read this and there are contradictions here in what I wrote, but I think you know what I mean. making it vanilla assures stability and support when integrated by the developers of the software. They master the backend.

phiol

nice one

Hi All, Spa is not Phiol but Phiol explains very well, the surprisingly non subject for cycling74, for including vanilla objects for interactive hardware. What I do consider offensive, is that, after years of multiple threads of experienced max users asking for c74 vanilla objects or explaining that no official objects were a problem for them in term of stability and making a living with max, c74 never, ever responded. You will find that many of those users from old threads are not anymore on the forum. I suppose they dont use max anymore. I suppose that 3rd party external is one of the problem they found. It seems sometimes that c74 switched 10 years ago to a clearly commercial license world, but maintain an academic mentality respect to demands of their users. Required is there for: required to make a living selling permanent instalation with max and external sensor hardware. Raja, dont try to hack the thread, but consider what is the subject. And it's an important one. Still no comments by c74 team by the way...

haha yeah I can't speak for the rest of the team, but the tone of the OP pretty much turned me off from formulating any reply... REQUIRED... lol.

but I hear what's being requested here. of course there will always be some fundamental differences in opinion regarding what our software should focus on providing to our customers. 3rd party externals have always been a feature rather than a bug IMO, and that's not going to change anytime soon. additionally, tools like syphon, spout, and OSC fill in holes not filled by 3rd party externs. Max is simply one tool in the toolbox of the professional real time media designer.

I'd encourage anyone who's interested to check out our min-devkit project, which modernizes our sdk and greatly lowers the barrier to entry into external development. it is still a work in progress, and will probably remain so for some time, but we are excited about the potential in this area. there are some plans in place to look at the realsense sdk in the context of min.

For the newbieshere, what does min-devkit do exactly? Is is an SDK? What is the difference between this and the normal SDK?