So... benn playing with the beta... here's my notes so far.

BUG - If you pause tracking, then hit track forward again, the timeline in point jumps to current frame, and the track goes bonkers.

BUG - Scaling seems out. Loading the same video (converted ofc) in v2 requires setting the character height to 1.95m... in v1 it would be 1.8 (which is what my actual height is).

POSSIBLE BUG - Tracking is much slower. In v1 I was kicking about 0.4 sec/frame, in 2 its 1.5 secs. not a BIG deal, and if its related to better tracking overall, tolerable.

POSSIBLE BUG - It appears (and this ofc is objective) to be much more jittery than v1. Or more to the point... the jitteryness appears to be of a higher frquency... more noisy, less wobbly if you get me.

FEATURE - The new actor settings are ok... however I don't like that the ability to set the thickness of limbs/torso has been removed. The new BMI and fatten portions is OK... but less helpful I find, harder to get a match to the live actor. Also, the ability to set the "waistline" (cut off between shirt and pants) is gone, want that back. MORE OPTIONS HERE PLEASE.

FEATURE - Whilst the male/female presets are a nice addition, I would MUCH prefer it if there could be someway to manually adjust ALL proportions, shoulder/hip width, limb/torso lengths, etc. Proportions of the human body vary a LOT between individuals. One size does not fit all Im afraid.

Ok, cheers all.

_________________
My Site

Hello RebelHill!

Thank you for your valuable feedback.

Could you please provide us with the following additional information:

1. To what kind of video described bugs concern? Single Kinect? Dual Kinect? Multiple PS Eye?

2. Model of your video card

Thanks in advance!

We cannot reproduce this problem. Can you please give more details.

Please note that tracking logic is changed a bit in new version. In old version, tracking always started from beginning of the Region of Interest. In new version, tracking starts from current frame and trims Region of Interest to exclude preceding unprocessed frames (that is, it sets the beginning of Region of Interest to the nearest processed frame).



Yes, seems like it is a bit off for RGB (PS3Eye) videos. It is something that is hard to fix quickly. We'll look at this later next week.

There is a simple workaround: set actor height to a larger value.



Yes, for high resolution. But it should be much faster in low resolution. In new version, low resolution can be almost as accurate as high.

It will take some time for us to optimize new version for speed. You can expect improvement in v.2.1.



So far we cannot reproduce this problem. We need more time to look at it.



We will add more shape controls in future versions. The new version is much more extensible than the old one. It may take 4-6 weeks.

Ok... so the vids Im testing with is a 6 PSeye setup, so there's that.

Also, videocard is an Asus engtx460Top (OC'd).

Regarding bug 1... Im not sure what more details I can give. Using v1... if I tracked, paused track (say to correct something, refit pose, or to just go back take a look at what I had so far), and I hit track forward again, then tracking would proceed from the last tracked frame. Now in v2 beta, if I do the same, the region of interest in point jumps to the current frame, and all previous tracking is lost. I'll knock up a screen cap later for you.

I'll see if I can show an example of the jitteryness too.

Cheers guys.

_________________
My Site

OK...

www.rebelhill.net/bits/ipi2.mov

cheers.

_________________
My Site

I haven't gotten as far as RH yet (so far I've only had time to convert some files from 1.0 to 2.0), but seeing his video, I have to agree on one point: having iPi DMC reset the region of interest could be very annoying--in my opinion, ROI should be defined by the user and not altererable by the software.

@RH, if you set a Take to the range of your desired ROI, double-clicking the Take will reset the ROI to that range. That's not a replacement for how it used to work but it might serve as a workaround for the time being.

Also, when I start tracking a project, I first set my desired range and let the tracker run completely through on its own. This will create a keyframe at every frame in the ROI, and maybe it will keep the tracker from jumping around and resetting the ROI? Just a thought--I have yet to really use 2.0 yet so I'm not sure how this affects my own workflow yet.

I'm a bit busy at work this weekend but I still hope to do some real testing tonight. Will post my thoughts then.

G.

_________________
Greenlaw
Artist/Partner - Little Green Dog | My Demo Reels (2013,) (2015,) (2017,) and (2019)

Watch a one minute excerpt on Vimeo now!

This is by design. The idea is to always track from current frame and to adjust region of interest to include only adjacent tracked frames.

We'll think about it and will see what we can do about it. It may take us several days.



Not actually. Previously tracked frames remain unchanged, only region of interest changes.



We'll have a look at this problem. It may take us some time.

For your information, in our tests we observe less jitter with new version, especially for large capture volumes (for PSEye videos). However, it is possible that there is a problem in some configurations.

I guess some of its a matter of taste really then.

Personally I find it more intuitive in v1 to just hit track forward and have it commence tracking from the last tracked frame, rather than the current frame, saves scrubbing back to see where you were. I also find altering the region of interest odd... as ofc when you eventually come to export, that's what gets exported, no? So you'll have to go back, reset it, etc.

I dont know, spose I just find the old way quicker and less hassle.

As for the difference in jitter... you're right, it def is more accurate now in 2, ust a different result, so you can really ignore that I guess.

Cheers.

_________________
My Site

In new version, we only trim the beginning of the Region of Interest to exclude empty frames (frames where tracking never happened). There would be no sense in exporting empty frames anyway.

Ah but it doesnt... If you see my video, region of interest trims to the current frame you hit track forward on, irrespective of if there is track data on previous frames. Tracking from previous frames is kept, yes, but those areas are trimmed outside the roi.

_________________
My Site