Problem with the trajectorize

[sito]

Hi,

I tried 9 captures today. The only one pt2 file cannot be change to the pt3 file.
That pt2 file has 151002080 frames, but recording time was 1 or 2 minutes.
The playback in pt2 is not work correctly.


23 cameras, 1 skelton, 2 rigidbodies, Arena version is 1.7.3000.

Looking forward to hear your recommendations.

sito

[NaturalPoint - Mike]

Hello -

Could you send the corrupted PT2 file to support@naturalpoint.com?

[Ghost_Train]

I've been running into the same problem. I just recorded about 20 seconds of motion and when I tried to trajectorize it showed 7294165 frames. I end up having to start all over. So far this has happened to me 4 times today.
I'll email you the files

[Ghost_Train]

I just sent an email with a zipped pt2 file.

[NaturalPoint - Mike]

Hello -

While it is not yet known how this is occurring, we have integrated a check and correct procedure for this in an upcoming release. The software will detect the incorrect start time and pop up a box offering you the opportunity to correct it. A release date for this has not been officially settled yet, though.

[Ghost_Train]

Awesome. I'm looking forward to it. It seems to be happening more frequently these days.

[Ghost_Train]

Actually today is the most frustrating session yet. Only about 10% of my takes arae actually able to trajectorize. I tried to downgrade back to 1.7 since this issues rarely happened before but sadly the camera results from 1.8.1 are not backward comparable. I reinstalled the latest version and I still cannot get it to work. I have not made any changes to the computer as far as I know. So feel free to let me beta test the update.

[Ghost_Train]

Actually, I think I'm onto something.

I realize I'm the only one out of the 2 other people mocap'ing who experiences this problem. I am also the only one who turn off the default 5 second count down. I like to get right into capturing. But for some reason in the latest versions this is causing trajectory problems. Or causing Arena to get confused and add a ridiculously high number of extra frames rendering the capture data useless.

Time will tell. But so far I have not had the issue since leaving the 5 second count down turned on.

[NaturalPoint - Mike]

Hmm, that's an interesting lead. I'll take a look more into this and get some test results back to our development team.

[Ghost_Train]

This theory is still rolling strong on my end. I still have not run into the problem since leaving the default 5 second count down turned on.