iPi DMC 2.0

RebelHill · **Joined:** Tue May 24, 2011 9:05 am **Posts:** 53

yeah... NEVER plan a production on unreleased or "expected" software, that's rule #1.

Just sayin'.

kristian · **Joined:** Wed May 02, 2012 1:33 am **Posts:** 12

for shure ... in this stage it's R&D, and for that 2.0 should be part of it. if it's possible, i think it's better to wait a few weeks and save a lot of work. actually the question grows up how many weeks we have to wait anymore.

if we got an info that the release is re-scheduled for October, isn't that a problem. Just know how to work with it.

A little bit more info about the status would be nice.

Greenlaw · **Posted:** Tue May 29, 2012 11:01 am

IMO, you shouldn't hold up production waiting for unreleased software. I would count on using the current release and then take advantage of the 2.0 features as they become available.

This was essentially how we approached out little movie--at the time, we knew twin Kinect support was 'coming soon' but our deadline had been so tight we went ahead and shot everything with a single Kinect since that's what was immediately available. We were very grateful when the twin Kinect beta arrived in mid-production because it did help us enormously but even if it had not we were still prepared to finish our film using the tools we already had.

G.

AaronC · **Joined:** Tue Dec 13, 2011 10:52 pm **Posts:** 73

I guess its a lesson in making promises, and listening to said promises, but I too have put off big jobs hoping for the overdue update.

I'd be keen to hear how things are going at iPiSoft. Not to put pressure on developers but to know where we stand.
Thanks
AaronC

nestergal · **Posted:** Wed May 30, 2012 12:25 am

I'd like to hear how things are going with version 2.0 too!!!

kristian · **Joined:** Wed May 02, 2012 1:33 am **Posts:** 12

yes, Aaron. that was just my intention.

just keen to hear how things are going. I worked in a former live as an software developer. so i absolutly understand the abyss of technical issues. And know also the gap between the omnipresent wish and the impossibility of binding timings. Just interessted in the actuall status.

kristian · **Joined:** Wed May 02, 2012 1:33 am **Posts:** 12

YIIIEEEEHHHHAAAA!!!!

Greenlaw · **Posted:** Fri Jun 01, 2012 7:57 am

Congratulations on the official release of 2.0 guys! This is very exciting and we're looking forward to using it soon!

Greenlaw and Alisa

Michael Nikonov · **Joined:** Tue Mar 31, 2009 9:13 pm **Posts:** 805

InfoCentral wrote:

I think the new features just released in the Kinect SDK 1.5 maybe a source of delay. This should greatly speed up the head and hand tracking implementation. The facial mocap and other features would probably take more time.

Currently we are not using Kinect SDK skeletal tracking. We only use Microsoft drivers to get depth data from Kinect. Kinect SDK skeletal tracking is very limited compared to our software. There are simple poses (like sitting or bending a knee) that cannot be tracked with Kinect SDK. So there is little sense in using it for animation. Of course, Kinect SDK tracking is very fast (realtime), but in animation accuracy is more important.

Hand tracking and head tracking in Kinect SDK is rudimentary and is hardly useful for full-body animation. Of course, Microsoft has pretty good head tracking at close range (1.0-1.5 meters), but this is not what we need for full-body mocap. At 3.0-3.5 meters Kinect SDK's head tracking works very unreliably.

InfoCentral wrote:

The facial mocap and other features would probably take more time.

We are not working on facial mocap as of yet. Part of the reason for this is the fact that other companies like Image Metrics (and now their spin-off Faceware) are doing a very good job with markerless facial mocap. We feel we should concentrate on full-body markerless mocap for now, because that is where the challenge is.

iPi DMC 2.0

Who is online