You are here

Home › Forums › mrpt-users

[kinect-3d-view]rebuliding kinect-3d-view.cpp but working badly

Wed, 04/11/2012 - 19:16 — goldkeytom

 

Hello all,
 
I'm able to run the kinect-3d-view app and it works fine.However when i tried to rebuild the program from 
 
the cpp source under Windows 7,vs 2010,mrpt 0.95, and run the program.I could figure out that RGB image(viewport) is taking some time to update. 
 
Something around 5-10 sec. I dont see error message but only the stream messages below. And in kinect-3d-view app,
 
it has no this messages.Maybe something with performance?Or my compiling environment has some problem?Could
anyone tell me why and how to fix it?
Any suggestion would be appreciate!
 
Thanks!
 
 
Waiting for sensor initialization...
Calling CKinect::initialize()...libusb-win32: dll version 1.2.2.0 | driver (libu
sb0.sys) version 1.2.2.0
Thread execution started.
Write Reg 0x0105 <= 0x00
Write Reg 0x0006 <= 0x00
Write Reg 0x0012 <= 0x02
Write Reg 0x0013 <= 0x01
Write Reg 0x0014 <= 0x1e
Write Reg 0x0006 <= 0x02
ReapThreadProc(): no pending transfers, sleeping until delivery...
Write Reg 0x0017 <= 0x00
Thread execution started.
Write Reg 0x000c <= 0x00
Write Reg 0x000d <= 0x01
Write Reg 0x000e <= 0x1e
Write Reg 0x0005 <= 0x01
ReapThreadProc(): no pending transfers, sleeping until delivery...
Write Reg 0x0047 <= 0x00
OK
1760 remaining out of 45760
1920 remaining out of 42240
1308 remaining out of 16692
1760 remaining out of 24640
112 remaining out of 18912
1760 remaining out of 33440
[Stream 70] Lost 1 packets
[Stream 70] Lost 4 packets
[Stream 70] Inconsistent flag 72 with 219 packets in buf (220 total), resyncing.
..
[Stream 70] Expected 1748 data bytes, but got 1236
1760 remaining out of 29920
[Stream 70] Lost 1 packets
[Stream 70] Lost 5 packets
[Stream 70] Inconsistent flag 72 with 219 packets in buf (220 total), resyncing.
..
[Stream 70] Expected 1748 data bytes, but got 1532
1760 remaining out of 12320
[1S9t2r0e arme m7a0i]n iLnogs to u1t  poafc k1e7t2s8
0
[Stream 70] Lost 3 packets
[Stream 80] Lost 1 packets
[Stream 80] Lost 5 packets
[3S5t2r0e arme m8a0i]n iInngc oonusti sotfe n4t7 5f2l0a
 82 with 161 packets in buf (162 total), resyncing...
[Stream 705]7 6L orsetm a7i npiancgk eotust
of[ S3t3r2e4a0m
70] Lost too many packets, resyncing...
1760 remaining out of 5280
[Stream 70] Lost 1 packets
[Stream 70] Lost 3 packets
[Stream 70] Inconsistent flag 71 with 213 packets in buf (220 total), resyncing.
..
1068 remaining out of 9308
[Stream 70] Lost 1 packets
[Stream 70] Lost 3 packets
[Stream 70] Inconsistent flag 75 with 204 packets in buf (220 total), resyncing.
..
1760 remaining out of 3520
1[9S2t0r eraemm a7i0n]i nLg ooustt  o1f  p5a76c0k
ts
[Stream 70] Lost 3 packets
[Stream 70] Inconsistent flag 75 with 194 packets in buf (220 total), resyncing.
..
[Stream 80] Lost 1 packets
[Stream 70] Expected 1748 data bytes, but got 1708
[Stream 80] Lost 3 packets
[Stream 80] Inconsistent flag 81 with 157 packets in buf (162 total), resyncing.
..
1920 remaining out of 30720
[Stream 80] Lost 1 packets
[Stream 80] Lost 3 packets
984 remaining out of 2928
[Stream 80] Inconsistent flag 85 with 143 packets in buf (162 total), resyncing.
..
1760 remaining out of 22880
[Stream 70] Lost 1 packets
[Stream 70] Lost 3 packets
[Stream 70] Inconsistent flag 71 with 200 packets in buf (220 total), resyncing.
..
ect.
Forums: 
mrpt-users
Fri, 04/27/2012 - 10:09 — jlblanco
jlblanco's picture

It looks like you have executed the program in Debug, which may render it too slow as for capturing Kinect data in real-time. 

Try running in Release mode or, in you really need to debug the program I would recommend using something like this to switch between live data and a grabbed dataset for debugging.