General • Re: Xbox One Kinect - 360 degrees
Technically, it can. It depends on how clearly the device can see the performer's limbs so it can interpolate what it can't see. Expect to do a lot of corrections during tracking though.

Way back when a single Kinect was the only depth sensor option in iPi Mocap Studio (known as iPi Desktop Motion Capture at the time,) I did a trick where I performed facing camera and the rotated the rig in my animation program to fake the 360 turn. It can be convincing from waist but not so effective for a full body render.

Naturally, the quality for 360 turnarounds improves considerably even if add only one additional sensor. Most of the turnaround stuff I did for my personal short films and the vfx footage I created for Asylum/SyFy movies were done using two Xbox Kinects. (A few were done using 3 sensors.)

IMO, single Kinect is a good introductory system for characters that will mostly stay 'in-place'. For anything more ambitious, you'll want to move up to using at least two sensors.

These days, I'm using multiple Kinect 2 sensors, which records cleaner data than the old Xbox Kinects. I haven't posted anything new for a while though. Lately, I've been very busy recording training videos for 2D animation software but planning to record similar videos for iPi Mocap Studio and 3D animation. Maybe I can prioritize that soon.

Statistics: Posted by Greenlaw — Wed Aug 14, 2019 5:23 pm


General • Re: Xbox One Kinect - 360 degrees
I think he use a lot of time to pose correctly until the key where can be refit and then track again and smooth it (the method is cost too much time and worth less ,so buy the ipi studio pro which can
support 4 Kinect2 and dont need to pose to pose ,so the show from truebones with nothing secret ,believe my experience ,there is nothing or dont exist super tracking setting)

Statistics: Posted by bluebox — Tue Aug 13, 2019 4:26 pm


General • Xbox One Kinect - 360 degrees
Hello. I want to ask if an Xbox One Kinect can record 360 degrees.
I ask because I came across this video that claims to be made with an Xbox One Kinect.


https://www.youtube.com/watch?v=3l7QvLSbvLw

Statistics: Posted by nikorusenov — Tue Aug 13, 2019 6:56 am


General • Xbox One Kinect - 360 degrees
Hello. I want to ask if an Xbox One Kinect can record 360 degrees.
I ask because I came across this video that claims to be made with an Xbox One Kinect.


https://www.youtube.com/watch?v=3l7QvLSbvLw

Statistics: Posted by nikorusenov — Tue Aug 13, 2019 6:56 am


Issues • Re: PS move dont work
New version worked perfectly!!!

Statistics: Posted by LordBlackwood — Sun Aug 04, 2019 11:01 pm


Issues • Re: Crash on launch of ipi Recorder 4
OK, Good news.
A reinstall of windows solved the issue.
Thank you so much.

If anyone else experiences issues with ntdll.dll just note that if you google what to do, there is a lot of bad info out there. If it tells you to use the command prompt to reinstall the dll, that is false and impossible for windows to do. It was bad advice that was given by a windows tech support rep that has been echoed multiple times in other locations.

Reinstalling windows is the only way I could find on how to repair a corrupt ntdll.dll.

Statistics: Posted by Midnight_blu3 — Sun Aug 04, 2019 1:06 pm


Issues • Re: Crash on launch of ipi Recorder 4
[EDIT]
I am currently getting the same ntdll error with other programs now. It is likely a problem on my end, and iPi was just the first one to show the symptom.
I am going to reinstall windows, I will update afterwards.
[/EDIT]

Thanks for the reply vmaslov,

I do not get a crash report for the program when it closes, so I checked the event viewer like you suggested.

The log shows an application error for iPiRecorder.exe, here is the message.

Quote:

Faulting application name: iPiRecorder.exe, version: 4.3.2.75, time stamp: 0x5d45a7c4
Faulting module name: ntdll.dll, version: 10.0.17134.799, time stamp: 0x7f828745
Exception code: 0xc0000374
Fault offset: 0x00000000000f479b
Faulting process id: 0x1dec
Faulting application start time: 0x01d54ae8014088ca
Faulting application path: C:\Program Files (x86)\iPiSoft\iPi Recorder 4\iPiRecorder.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: d132662d-68fe-4c84-b96b-11224a2fa869
Faulting package full name:
Faulting package-relative application ID:


There is also an information event that says this:

Quote:

Fault bucket 1684233284074855292, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: iPiRecorder.exe
P2: 4.3.2.75
P3: 5d45a7c4
P4: StackHash_cdc7
P5: 10.0.17134.799
P6: 7f828745
P7: c0000374
P8: PCH_A2_FROM_ntdll+0x000000000009B4F4
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDFA7.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE12F.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE15E.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE15C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE16D.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_iPiRecorder.exe_a9b058f969f2d1189386f9129a4f32bf32f8a6_de8dfae1_0e97e3ed

Analysis symbol:
Rechecking for solution: 0
Report Id: d132662d-68fe-4c84-b96b-11224a2fa869
Report Status: 268435456
Hashed bucket: f4c986a8a5e607ff175f993f982bdb7c
Cab Guid: 0


and the attached file it refers to is this:

Quote:

Version=1
EventType=APPCRASH
EventTime=132094124436701917
ReportType=2
Consent=1
UploadTime=132094124441409325
ReportStatus=268435456
ReportIdentifier=c5ac02b7-b89a-4eef-9ad0-32688e636c0c
IntegratorReportIdentifier=d132662d-68fe-4c84-b96b-11224a2fa869
Wow64Host=34404
NsAppName=iPiRecorder.exe
OriginalFilename=iPiRecorder.exe
AppSessionGuid=00001dec-0001-0073-ca88-4001e84ad501
TargetAppId=W:00061238e5ae48745e7e54171473949e848900000000!00005b420698f4167c2d52d796e9edb558539fa53579!iPiRecorder.exe
TargetAppVer=2019//08//03:15:27:00!2a98df!iPiRecorder.exe
BootId=4294967295
TargetAsId=901
UserImpactVector=3146544
IsFatal=1
Response.BucketId=f4c986a8a5e607ff175f993f982bdb7c
Response.BucketTable=4
Response.LegacyBucketId=1684233284074855292
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=iPiRecorder.exe
Sig[1].Name=Application Version
Sig[1].Value=4.3.2.75
Sig[2].Name=Application Timestamp
Sig[2].Value=5d45a7c4
Sig[3].Name=Fault Module Name
Sig[3].Value=StackHash_cdc7
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.17134.799
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=7f828745
Sig[6].Name=Exception Code
Sig[6].Value=c0000374
Sig[7].Name=Exception Offset
Sig[7].Value=PCH_A2_FROM_ntdll+0x000000000009B4F4
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.17134.2.0.0.768.101
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=cdc7
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=cdc7d02036fec46ba95d4792d264f40e
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=7c5b
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=7c5bc3485217bc75890ce12e8b73303e
UI[2]=C:\Program Files (x86)\iPiSoft\iPi Recorder 4\iPiRecorder.exe
LoadedModule[0]=C:\Program Files (x86)\iPiSoft\iPi Recorder 4\iPiRecorder.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\SYSTEM32\MSCOREE.DLL
LoadedModule[3]=C:\Windows\System32\KERNEL32.dll
LoadedModule[4]=C:\Windows\System32\KERNELBASE.dll
LoadedModule[5]=C:\Windows\SYSTEM32\apphelp.dll
LoadedModule[6]=C:\Windows\SYSTEM32\AcLayers.DLL
LoadedModule[7]=C:\Windows\System32\msvcrt.dll
LoadedModule[8]=C:\Windows\System32\USER32.dll
LoadedModule[9]=C:\Windows\System32\win32u.dll
LoadedModule[10]=C:\Windows\System32\GDI32.dll
LoadedModule[11]=C:\Windows\System32\gdi32full.dll
LoadedModule[12]=C:\Windows\System32\msvcp_win.dll
LoadedModule[13]=C:\Windows\System32\ucrtbase.dll
LoadedModule[14]=C:\Windows\System32\SHLWAPI.dll
LoadedModule[15]=C:\Windows\System32\combase.dll
LoadedModule[16]=C:\Windows\System32\RPCRT4.dll
LoadedModule[17]=C:\Windows\System32\bcryptPrimitives.dll
LoadedModule[18]=C:\Windows\SYSTEM32\WINSPOOL.DRV
LoadedModule[19]=C:\Windows\System32\kernel.appcore.dll
LoadedModule[20]=C:\Windows\SYSTEM32\PROPSYS.dll
LoadedModule[21]=C:\Windows\System32\OLEAUT32.dll
LoadedModule[22]=C:\Windows\System32\shcore.dll
LoadedModule[23]=C:\Windows\System32\sechost.dll
LoadedModule[24]=C:\Windows\SYSTEM32\IPHLPAPI.DLL
LoadedModule[25]=C:\Windows\SYSTEM32\bcrypt.dll
LoadedModule[26]=C:\Windows\SYSTEM32\sfc.dll
LoadedModule[27]=C:\Windows\SYSTEM32\sfc_os.DLL
LoadedModule[28]=C:\Windows\SYSTEM32\SortWindows61.dll
LoadedModule[29]=C:\Windows\System32\IMM32.DLL
LoadedModule[30]=C:\Windows\System32\ADVAPI32.dll
LoadedModule[31]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll
LoadedModule[32]=C:\Windows\SYSTEM32\VERSION.dll
LoadedModule[33]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
LoadedModule[34]=C:\Windows\SYSTEM32\MSVCR120_CLR0400.dll
LoadedModule[35]=C:\Windows\assembly\NativeImages_v4.0.30319_64\mscorlib\bef0a43af1bb9a52ee47a6f60bec2961\mscorlib.ni.dll
LoadedModule[36]=C:\Windows\System32\ole32.dll
LoadedModule[37]=C:\Windows\system32\uxtheme.dll
LoadedModule[38]=C:\Program Files (x86)\RivaTuner Statistics Server\RTSSHooks64.dll
LoadedModule[39]=C:\Windows\SYSTEM32\WINMM.dll
LoadedModule[40]=C:\Windows\SYSTEM32\winmmbase.dll
LoadedModule[41]=C:\Windows\System32\cfgmgr32.dll
LoadedModule[42]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clrjit.dll
LoadedModule[43]=C:\Windows\SYSTEM32\CRYPTSP.dll
LoadedModule[44]=C:\Windows\system32\rsaenh.dll
LoadedModule[45]=C:\Windows\SYSTEM32\CRYPTBASE.dll
LoadedModule[46]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System\2ef4bd82ccd0a1d27eaefb60228f9a48\System.ni.dll
LoadedModule[47]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Core\0083d13f6d5d7574379e1849bff4cbdd\System.Core.ni.dll
LoadedModule[48]=C:\Windows\assembly\NativeImages_v4.0.30319_64\WindowsBase\fed50aed9176810a50a13cd5266b0e43\WindowsBase.ni.dll
LoadedModule[49]=C:\Windows\assembly\NativeImages_v4.0.30319_64\PresentationCore\f9b4a881e33dca1bd3d5a3f6f388e19c\PresentationCore.ni.dll
LoadedModule[50]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Presentatio5ae0f00f#\aead21d9cf95c27c59c7afb0505097df\PresentationFramework.ni.dll
LoadedModule[51]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xaml\53623560e0b9660f9d8df8dcafc33310\System.Xaml.ni.dll
LoadedModule[52]=C:\Windows\SYSTEM32\dwrite.dll
LoadedModule[53]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\wpfgfx_v0400.dll
LoadedModule[54]=C:\Windows\SYSTEM32\MSVCP120_CLR0400.dll
LoadedModule[55]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\PresentationNative_v0400.dll
LoadedModule[56]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Configuration\c78d879be4e9a8d9e8d8b0613dd1ab63\System.Configuration.ni.dll
LoadedModule[57]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Xml\55f8a8308df67bd3d5d7441a99c6da88\System.Xml.ni.dll
LoadedModule[58]=C:\Windows\System32\shell32.dll
LoadedModule[59]=C:\Windows\System32\windows.storage.dll
LoadedModule[60]=C:\Windows\System32\profapi.dll
LoadedModule[61]=C:\Windows\System32\powrprof.dll
LoadedModule[62]=C:\Windows\System32\FLTLIB.DLL
LoadedModule[63]=C:\Windows\system32\dwmapi.dll
LoadedModule[64]=C:\Program Files (x86)\iPiSoft\iPi Recorder 4\OpenNI\amd64\OpenNI64.dll
LoadedModule[65]=C:\Windows\System32\WS2_32.dll
LoadedModule[66]=C:\Windows\System32\SETUPAPI.dll
LoadedModule[67]=C:\Program Files (x86)\iPiSoft\iPi Recorder 4\OpenNI\amd64\MSVCR100.dll
LoadedModule[68]=C:\Windows\System32\MSCTF.dll
LoadedModule[69]=C:\Windows\SYSTEM32\dxgi.dll
LoadedModule[70]=C:\Windows\SYSTEM32\d3d11.dll
LoadedModule[71]=C:\Windows\System32\crypt32.dll
LoadedModule[72]=C:\Windows\System32\MSASN1.dll
LoadedModule[73]=C:\Windows\System32\WINTRUST.DLL
LoadedModule[74]=C:\Windows\System32\imagehlp.dll
LoadedModule[75]=C:\Windows\system32\nvspcap64.dll
LoadedModule[76]=C:\Windows\SYSTEM32\ntmarta.dll
LoadedModule[77]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Drawing\1f4391ce1a8e125ee0ed1f97adce114a\System.Drawing.ni.dll
LoadedModule[78]=C:\Windows\SYSTEM32\urlmon.dll
LoadedModule[79]=C:\Windows\SYSTEM32\iertutil.dll
LoadedModule[80]=C:\Windows\SYSTEM32\SspiCli.dll
LoadedModule[81]=C:\Program Files (x86)\iPiSoft\iPi Recorder 4\iPiSolver\amd64\iPiSolverNet.dll
LoadedModule[82]=C:\Program Files (x86)\iPiSoft\iPi Recorder 4\iPiSolver\amd64\iPiSolverDll.dll
LoadedModule[83]=C:\Program Files (x86)\iPiSoft\iPi Recorder 4\iPiSolver\amd64\MSVCP120.dll
LoadedModule[84]=C:\Program Files (x86)\iPiSoft\iPi Recorder 4\iPiSolver\amd64\MSVCR120.dll
LoadedModule[85]=C:\Program Files (x86)\iPiSoft\iPi Recorder 4\iPiSolver\amd64\libblas.dll
LoadedModule[86]=C:\Program Files (x86)\iPiSoft\iPi Recorder 4\iPiSolver\amd64\liblapack.dll
LoadedModule[87]=C:\Program Files (x86)\iPiSoft\iPi Recorder 4\iPiSolver\amd64\VCOMP120.DLL
LoadedModule[88]=C:\Program Files (x86)\iPiSoft\iPi Recorder 4\iPiSolver\amd64\libgfortran-3.dll
LoadedModule[89]=C:\Program Files (x86)\iPiSoft\iPi Recorder 4\iPiSolver\amd64\libgcc_s_sjlj-1.dll
LoadedModule[90]=C:\Program Files (x86)\iPiSoft\iPi Recorder 4\iPiSolver\amd64\libquadmath-0.dll
LoadedModule[91]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System.Management\bf172689373674de4b867ad6225af2b6\System.Management.ni.dll
LoadedModule[92]=C:\Windows\System32\clbcatq.dll
LoadedModule[93]=C:\Windows\system32\wbem\wmiutils.dll
LoadedModule[94]=C:\Windows\SYSTEM32\wbemcomn.dll
LoadedModule[95]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[96]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\wminet_utils.dll
LoadedModule[97]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[98]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[99]=C:\Windows\SYSTEM32\msvfw32.dll
LoadedModule[100]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.17134.885_none_fb42a3473065565f\COMCTL32.dll
LoadedModule[101]=C:\Windows\System32\psapi.dll
LoadedModule[102]=C:\Windows\SYSTEM32\gpapi.dll
LoadedModule[103]=C:\Windows\System32\cryptnet.dll
LoadedModule[104]=C:\Windows\SYSTEM32\WINNSI.DLL
LoadedModule[105]=C:\Windows\System32\NSI.dll
LoadedModule[106]=C:\Windows\SYSTEM32\wldp.dll
LoadedModule[107]=C:\Windows\assembly\NativeImages_v4.0.30319_64\Presentatioaec034ca#\d7a06e0ff5c51b1bc834542b780bbde9\PresentationFramework.Aero2.ni.dll
LoadedModule[108]=C:\Windows\SYSTEM32\WindowsCodecs.dll
LoadedModule[109]=C:\Windows\SYSTEM32\d3d9.dll
LoadedModule[110]=C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_547eeefb57db4499\nvldumdx.dll
LoadedModule[111]=C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_547eeefb57db4499\nvd3dumx.dll
LoadedModule[112]=C:\Windows\assembly\NativeImages_v4.0.30319_64\WindowsForm0b574481#\c9fdf61ff6bda1e5ccb15ba54b40230f\WindowsFormsIntegration.ni.dll
LoadedModule[113]=C:\Windows\SYSTEM32\wtsapi32.dll
LoadedModule[114]=C:\Windows\SYSTEM32\WINSTA.dll
LoadedModule[115]=C:\Windows\system32\dataexchange.dll
LoadedModule[116]=C:\Windows\system32\dcomp.dll
LoadedModule[117]=C:\Windows\system32\twinapi.appcore.dll
LoadedModule[118]=C:\Windows\system32\RMCLIENT.dll
LoadedModule[119]=C:\Windows\SYSTEM32\mscms.dll
LoadedModule[120]=C:\Windows\SYSTEM32\USERENV.dll
LoadedModule[121]=C:\Windows\SYSTEM32\ColorAdapterClient.dll
LoadedModule[122]=C:\Windows\SYSTEM32\WindowsCodecsExt.dll
LoadedModule[123]=C:\Windows\assembly\NativeImages_v4.0.30319_64\UIAutomationTypes\9942aaba5329db0ca202765fccc649d8\UIAutomationTypes.ni.dll
LoadedModule[124]=C:\Windows\SYSTEM32\UIAutomationCore.dll
LoadedModule[125]=C:\Windows\System32\TextInputFramework.dll
LoadedModule[126]=C:\Windows\System32\CoreUIComponents.dll
LoadedModule[127]=C:\Windows\System32\CoreMessaging.dll
LoadedModule[128]=C:\Windows\SYSTEM32\wintypes.dll
LoadedModule[129]=C:\Windows\system32\msctfui.dll
LoadedModule[130]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscorsecimpl.dll
LoadedModule[131]=C:\Windows\SYSTEM32\D3DCOMPILER_47.dll
LoadedModule[132]=C:\Windows\System32\devenum.dll
LoadedModule[133]=C:\Windows\System32\DEVOBJ.dll
LoadedModule[134]=C:\Windows\System32\ksproxy.ax
LoadedModule[135]=C:\Windows\System32\ksuser.dll
LoadedModule[136]=C:\Windows\SYSTEM32\policymanager.dll
LoadedModule[137]=C:\Windows\System32\msvcp110_win.dll
LoadedModule[138]=C:\Windows\SYSTEM32\msdmo.dll
LoadedModule[139]=C:\Windows\SYSTEM32\Kinect10.dll
LoadedModule[140]=C:\Windows\SYSTEM32\WINUSB.DLL
LoadedModule[141]=C:\Windows\SYSTEM32\MSVCP100.dll
LoadedModule[142]=C:\Program Files (x86)\iPiSoft\iPi Recorder 4\Libfreenect2\amd64\libfreenect2.Net.dll
LoadedModule[143]=C:\Program Files (x86)\iPiSoft\iPi Recorder 4\Libfreenect2\amd64\VCRUNTIME140.dll
LoadedModule[144]=C:\Program Files (x86)\iPiSoft\iPi Recorder 4\Libfreenect2\amd64\freenect2.dll
LoadedModule[145]=C:\Program Files (x86)\iPiSoft\iPi Recorder 4\Libfreenect2\amd64\MSVCP140.dll
LoadedModule[146]=C:\Program Files (x86)\iPiSoft\iPi Recorder 4\Libfreenect2\amd64\libusb-1.0.dll
LoadedModule[147]=C:\Program Files (x86)\iPiSoft\iPi Recorder 4\Libfreenect2\amd64\turbojpeg.dll
LoadedModule[148]=C:\Program Files (x86)\iPiSoft\iPi Recorder 4\Libfreenect2\amd64\glfw3.dll
LoadedModule[149]=C:\Windows\SYSTEM32\OPENGL32.dll
LoadedModule[150]=C:\Windows\SYSTEM32\OpenCL.dll
LoadedModule[151]=C:\Windows\SYSTEM32\GLU32.dll
LoadedModule[152]=C:\Windows\SYSTEM32\hid.DLL
LoadedModule[153]=C:\Windows\SYSTEM32\UsbDkHelper.DLL
State[0].Key=Transport.DoneStage1
State[0].Value=1
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=17134
OsInfo[3].Key=ubr
OsInfo[3].Value=885
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1033
OsInfo[7].Key=geoid
OsInfo[7].Value=244
OsInfo[8].Key=sku
OsInfo[8].Value=101
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=768
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=530032
OsInfo[15].Key=osinsty
OsInfo[15].Value=2
OsInfo[16].Key=iever
OsInfo[16].Value=11.885.17134.0-11.0.135
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=32641
OsInfo[19].Key=svolsz
OsInfo[19].Value=222
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=180410
OsInfo[22].Key=bldtm
OsInfo[22].Value=1804
OsInfo[23].Key=bldbrch
OsInfo[23].Value=rs4_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.17134.885.amd64fre.rs4_release.180410-1804
OsInfo[30].Key=buildflightid
OsInfo[31].Key=edition
OsInfo[31].Value=Core
OsInfo[32].Key=ring
OsInfo[32].Value=Retail
OsInfo[33].Key=expid
OsInfo[34].Key=containerid
OsInfo[35].Key=containertype
OsInfo[36].Key=edu
OsInfo[36].Value=0
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=iPi Recorder 4
AppPath=C:\Program Files (x86)\iPiSoft\iPi Recorder 4\iPiRecorder.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=69608DAFF839CBE2A08F0AB0D02CC123
MetadataHash=1019713049


Sorry for the novel, I could not figure out how to make the logs collapsible.

Statistics: Posted by Midnight_blu3 — Sun Aug 04, 2019 10:33 am


Issues • Re: A few question for those who are getting good results
...

Yes, PS Eyes require a bit more room size, though if you have to use a more rectangle shaped room, use the long side as the front/rear camera side, if possible, even if not using a rear camera, it is better to face the front on the longest side of the room.

Very large area aren't really necessary, PS Eyes can only see well within 20 x 20 ft., outside of that it would require special camera placement, or more cameras than 6 to work effectively, but really it is better to keep your maximum floor capture volume from 12 x 12 ft. to 15 x 15 ft. where all the cameras can view the entire performer with arms extended upward while standing in the exact center floor mark of the room, wall to wall measurement.

Best to always use a dead center room floor mark (X), This is the ONLY spot that should be used to set the scale of the iPi Actor to the performer, after the scale is set correctly, it is then possible to start your tracking at any point in the space available, it isn't required to refit your Actor from the T Pose @ center, nor end in a T pose, but that is personal choice, as iPi can export a 1st frame T pose for characterization in any 3D editing package.

PS Eyes are a little more tricky to set up and use, especially if it is required to break the set up down after each session, so if possible try to set them up in a more stable environment where the system can remain untouched after set up.

I have went into some very specific detail explaining aspects of the system that always worked well for me, you are free to check them out in the forum posts.

It's all trial and error based on your preferences, and you will work through issues until you get a better idea of how and why things have to be as suggested for best results, but if you stick with things, it should start to fall in place rather quickly, the camera set up is fairly forgiving, but the room size, calibration, lighting and clothing fit isn't so forgiving, so heed any suggestions pertaining to those aspects.

Good Luck!

...

Statistics: Posted by Snapz — Sun Aug 04, 2019 7:27 am


Issues • Re: Crash on launch of ipi Recorder 4
Does the program show a crash report? If yes, please post its contents here. Otherwise, try to find info about the crash in Windows Event Viewer program, under application logs.

Statistics: Posted by vmaslov — Sun Aug 04, 2019 12:45 am


Issues • Re: A few question for those who are getting good results
When getting an USB card pay attention to USB chip it is based on not to get into other issues. NEC/Renesas USB 3.0 chips have good compatibility with most cameras including PS Eye.

Statistics: Posted by vmaslov — Sun Aug 04, 2019 12:41 am


General • Re: just want ipisoft to know that
Comparing the Quality of Point Cloud Between Azure Kinect, Kinect V2 and Real Sensehttps://youtu.be/NrIgjK_PeQU
1.png2.png3.png

Statistics: Posted by bluebox — Sat Aug 03, 2019 11:47 pm


Issues • Crash on launch of ipi Recorder 4
Hi. I've been testing out the software and so far It's been performing much better than I expected it would with a single kinect. I just bought a second kinect and I noticed the frame rate would drop while recording. I did some reading and saw that I needed to have each Kinect on a seperate USB 3.0 controller, so I went and bought a PCI-E expansion card.

This is where the problem begins.
Now ipi Recorder 4 crashes as soon as I launch it. The toolbar appears at the top, my previously recorded videos appear on the right, but before any devices populate on the screen the program crashes to desktop. I can run the kinect through the microsoft SDK and it runs fine so I don't think that's the problem.

Just to be safe though I uninstalled my second USB controller and ipi Recorder 4 still crashes.

I uninstalled everything labeled kinect or ipi in my control panel, then restarted my PC and (still with the new controller removed) it immediately crashes to desktop before any devices populate.

Any ideas?
Thanks.

Statistics: Posted by Midnight_blu3 — Sat Aug 03, 2019 8:55 pm


Issues • Re: A few question for those who are getting good results
Great info guys. Sounds like my first priority is to get additional USB controllers, and might as well upgrade to 6 PS3 Eyes since they're so cheap.
Initially I did move my entire setup to a much bigger room, but got no better results, so moved back to my office, which is likely too small. I will go back to the big room and try it with new USB controllers and no red statistic pop ups. There are so many variables I wasn't sure where to trouble shoot, so I'll fix these obvious problems first. Thanks.

Statistics: Posted by kyleb2112 — Sat Aug 03, 2019 8:49 pm


Issues • Re: PS move dont work
Please check iPi Recorder v4.3.2, it should fix the issue.

Statistics: Posted by vmaslov — Sat Aug 03, 2019 8:59 am


News and Announcements • iPi Recorder updated to 4.3.2
See release notes

Statistics: Posted by vmaslov — Sat Aug 03, 2019 8:58 am


Issues • Re: A few question for those who are getting good results
...

Best to just share your calibration and action videos with iPi Support, there are many causes that new users can quite easily overlook, or not be able to determine the cause, when many are easier to see by experienced users, or iPi Support, this is assuming your computer(s) used are compatible for the PS Eyes system use you are performing.

Once you get the PS cameras and PS controllers set correctly and detected properly, as well as correct room lighting and clothing, the system will track very accurately at 90% or better, even during fast motions and extreme motions, but there is always caveats during tracking when using RGB cameras, with any mocap system that may cause interference with the tracking, that just comes with usage experience and can usually be rectified with iPi by simply re-tracking the area, or some basic clean up in iPi Studio, or ultimately in post.

Be aware that PS Eye cams do not like really bright light and definitely not where it shines into their lenses, better to have more less wattage lighting around the area, this will also lessen the shadows on the floor. (Really bright room lighting can and most likely will cause frame drops randomly).

Good saturated clothing colors and tighter fitting is very important too, as well closely matching the iPi Actor dimensions to the video performer before tracking, using the Overall Body Mass set lower first, then individually adjusting the rest of the sliders will help, as well as the correct lengths of the Actor skeleton.
(See the Pose Tab to set hip height accordingly, it usually comes in to high for most performers, which means you need to shorten the legs length and usually the arms length after to better match the performer).

If your Actor height isn't within approx 1-2 cm of the performers actual height, when you refit the Actor from the center point floor mark, something is off, as this should occur without much issue when done properly.

Depending on the amount of cameras you are using, though 6 should be a minimum for better results, the positioning can be just about anywhere above 3 ft, can be lower in some circumstances, but to learn they should be set higher than 3 to 4 ft off the floor and the correct measurement used for camera 1 when calibration asks for it, as calibration is the most important part of RGB tracking quality, then lighting, then clothing, then background colors, as iPi does a pretty good job of removing background inconsistencies.

You are on the right track by choosing PS Eyes, though a bit slower in tracking depending on your graphics card, but much more accurate, with less loss of tracking and lessened post clean up, that is once you get things working properly, and the system does work properly with 6 cams, or more, with proper computer running the system, but would be best to let iPi see your videos and give some better recommendations.

One note many don't understand, the Scene light is there for a reason, and should be placed in the Studio scene to match the brightest light source, so setting your lights should conform to give a directional lighting appearance on the performer, this doesn't mean a one sided lighting source, it means higher wattage lighting on some lamps and this works better if set from the side of the front facing actor, this helps split the shadows on the iPi Actors skin and can aid in tracking quality, but the main thing is that the scene light should be placed and used, just not forgotten about, it will make subtle, noticeably better differences in your tracking quality.

...

Statistics: Posted by Snapz — Sat Aug 03, 2019 6:14 am


Issues • Re: A few question for those who are getting good results
dont worry guys ,I have got all of the issues what you have mention about ,so I guess the first problem is your space may be too small ,in my experience ,at least need 70 m x m to capture motion and then calibration and tracking the motion in ipi studio mocap ,because if the space too small and the actor can be not suit the background character and can not track the motion ,all the issue is the basic knowledge you need to learn ,some example (bandwide the usb or how to use ps move controlor and if the distance too far from the pc which you link to the ps move controlor then the data will lose ,or you need The tripod
is the best choice to fix the camera postion and you need usb 3.or usb 2 cable to extend to connect to your pc if the camera too far from ,or too high)and so on

Statistics: Posted by bluebox — Sat Aug 03, 2019 5:01 am


Issues • Re: A few question for those who are getting good results
Hi

First, you didn't mention which cameras you use. I guess it's PS Eye and below comment is under this assumption.

If you see "red" statistics during recording this is usually a sign of some performance issues which need to be addressed. Acceptable number of frame drops or slightly lower frame rate do not cause red.
Probably you need to connect cameras to other USB ports so that not too many cameras are connected to a single USB controller, or add an additional USB controller to your PC. If your issues are with USB bandwidth, you can also try lower frame rate instead of lower resolution. Also, USB extension cables of poor quality (or passive cables of more than 3m length) may cause frame drops and other issues.

Motion Controllers tab appears automatically for action projects containing data from motion controllers. For this data to be recorded, motion controllers should be selected in device list of iPi Recorder before hitting the Record button.

Cameras shouldn't be distributed evenly. The main point when placing cameras is to provide different points of view on a capture space for the tracking algorithm. Hence we recommend placing several cameras at increased heights (for color). Being close to a wall means you cannot place cameras in a full circle around the capture area thus limiting POVs and making harder to track certain motions. But the main thing for color tracking is even lighting and good contrast between actor clothes and background.

Size of calibration marker only matters for its detection (distinction from other light sources in the scene). Calibration algorithm takes center point of detected marker spot for its calculations. If you see low percentage of marker misdetection then you should be good to go.

You may share you calibration and action videos so that I can give you more specific recommendations.

Statistics: Posted by vmaslov — Fri Aug 02, 2019 11:48 pm


Issues • A few question for those who are getting good results
I'm desperately trying to get this to work, as the alternative is to tell my boss we need a $20,000 mocap suit (as the cheaper suits don't look good enough). I have a high tech level, but so far I can't get decent results after a solid week of research and testing.

1). If you see any red pop up on the recording windows (dropped frames or whatever), is that a total deal killer? Do you stop recording and troubleshoot/upgrade system? Or continue on? I'm seeing a low percentage of dropped frames at 640 resolution. I don't know if upgrading my system would fix all my problems or not. At a lower resolution, I don't get dropped frames, but I still have the same tracking problems, so I've been assuming it's not the main source of my problems.

2). How do I get the Motion Controller tab on iPi Mocap Studio to appear? The wiki instructions possibly suggest you need a separate computer for each PS Move. But all three of my Moves (connected to 2 computers) show up and calibrate in Ipi Recorder. BUT, then there is no Motion Controller tab added to iPi Mocap Studio. I don't know if I'm not recording Move data, or if I need to set an option somewhere to record the Move data, or if the trial version of iPi Mocap Studio doesn't support this feature.

3). How important is spacing of cameras? Are you putting them at exact intervals around the shot area?

4). I've been close to a wall, but not with particularly dark shadows. Do I need to use an open space before this will work?

5.) The calibration shows "Perfect" only when I switch "Marker Spot On Video" to Large. Am I sacrificing accuracy by doing this? Should I get a smaller calibration light?

I'd appreciate any responses. It'd be a real heart-breaker if I can't get this system to work just for overlooking something simple.

Statistics: Posted by kyleb2112 — Fri Aug 02, 2019 1:23 pm


Issues • Re: PS move dont work
I couldn't get mine connected until I went into the Windows Device manager, selected the controller from the list, and updated the driver from the internet. I have the recommended Asus USB-BT400 dongles. I was surprised the driver they included with them couldn't recognize really old PS3 moves that I got off eBay, but it couldn't. They connect great now.

Statistics: Posted by kyleb2112 — Fri Aug 02, 2019 12:33 pm