Re-ran a video from start and here is what is happening for me:

After actor is set up and refit and I start tracking-forward, (some, not all videos) start tracking at comparative speed to V2...

If I change any tracking option after I start tracking, (as I always can to do in V2, without issue), in V3 degrades the tracking speed to .50 f/s or below.

Some videos (not all) have started at .75-.80 f/s, but if I touch anything, except pause/stop, when it restarts tracking it is what previous videos show.

In V2, I can switch spine options to my choice in different areas during tracking and it works fine, with V3 there is some conflict happening.

Seems any option I do in V3, even if just adding a hand gesture, (which I commonly do a fist a few frames in after tracking settles better for Moves when holding in palms without issue), I do this in V3 and re-starts tracking at degraded speed.

If I turn off head tracking, speeds jump measurably to .85+, but I don't want to track without the head tracking on.

I don't know if this is helpful info. for you, but it seems to be what is going on and no issue with that in V2.

Also, I have no other programs open, not even the recorder, in these tests.

Some videos of V3 captures with V3 recorder and exported to different applications:

iPi V3 capture tracked forward only once and full JR options used (except torso left on default) as well as full 5 steps of smoothing. Character added, but I can't find how to remove the iPi rig skin now.

Link: http://youtu.be/ZQx06NyZjWM


Exported to 3DS Max biped, no cleanup.

Link: http://youtu.be/vdEQk9aEvXM


Exported to Motion Builder rig, no cleanup.

Link: http://youtu.be/GSKlixsW-uw

You can compare to previous posted videos done in V2.

I think the difference may be caused by the following:
1. Tracking speed often fluctuates and may differ up to 10-15% in different frames of the same project with the same tracking options.
2. Tracking speed substantially differs for different tracking options
3. In v3 tracking speed is measured as an average for all tracked frames. In v2 you see tracking speed for the latest frame.

I think speed drops you see may be explained by above factors.

To make correct tracking speed comparison, you need
1. Run tracking for the same project, same ROI, same tracking options
2. You need at least 100 frames in a ROI
3. In v2 you need to measure total tracking time, and divide by number of tracked frames.
4. It is better to have only iPi Studio opened.

We'll further increase v3 tracking speed, so having the same (or slightly higher) tracking speed compared to v2 is only the beginning.

_________________
iPi Soft

Ok..

Will discuss more with tech support, but all that doesn't matter when it is visually and by the clock slower, that can't be mistaken by a program.

Yes, all were run with same ROI and same tracking settings shown in previous posts.

Please check an updated Mocap Studio 3.0.1.169. It should fix the issue with processing speed.

Yes, I downloaded update last night and on first test, did increase the processing speed correctly and measurably faster than V2, visually and by timing it on the clock.

Processing performance readings are now more stable and accurate to actual times, not as erratically shown as in V2.

By this fix, it also seemed to help with other issues in tracking, I am doing more and will discuss finding with Tech Support.

Thanks for correcting this issue.

Video of a female dance demo. with flexible spine option exported to biped, after update of V3.

You will now see noticeable improvement and quality of tracking.

No editing done outside of iPi Studio, just JR and smoothing.

Link: http://youtu.be/NESxbwoDiDw

This was recorded in V3 recorder with JPG compression setting @ 75%

I was able to track that issue down to being part of the progress bar or something with the small performance data window and reported it to a tech, I see the progress

bar was changed.

I don't know if the update included other bug fixes associated with it or not, other than disabling tabs while tracking, but glad you could isolate and correct it.

Any word on the update for the Moves yet?

Update to Recorder is awaited in a few hours.

Ok, thanks for advanced notification.