I’m testing out the new RealSense CHOP in build 50500. After I got all my drivers up to date (a re-registration and 4 separate downloads from Intel) I was getting data! I was easily able to instance geometry on my hands/face. instagram.com/p/35v53fD_sn/
Then I tried to grab the video stream from the RealSense to overlay geometry on video. Adding a Video Device In TOP caused a pop-up error dialog “CoInitialization Error” and then selecting the RealSense RGB feed in the TOP’s device dropdown crashed Touch… I started a new project with Video Device In first, then tried adding RealSense CHOP. No crash, but no data in CHOP. Closed. Un/Re-plugged device. New Project. Start with CHOP, still no data. Restart computer (Retina MacBook Pro) Open Touch, no data. Un/Re-plug, re-open touch, now there’s data again… I think the device hadn’t fully enumerated yet after the reboot, before Touch opened. Is there a reason that the RealSense device needs to be plugged in before starting Touch or is that a bug? Same for using RealSense CHOP and Video Device In TOP concurrently?
Is anybody else getting a really slow frame rate whilst using the RealSense CHOP or TOP? I have an Intel 4770K with an Nvidia 970 and it’s slowing my system down to 17 FPS. Should it be doing this?
Seems I spoke too soon.
I now get 60FPS on the RealSense TOP which is great! But when using the RealSense CHOP I still get a low 17FPS. Is this just teething problems with the CHOP Beta for now?
It takes a few tries for the camera to get recognized by Windows, but once it is recognized the SDK tools and samples work fine.
The RealSense TOP is black. I do get an image from VideoInTOP using the WDM or Media Foundation libraries. RGB camera is fine in these modes (640x480 only), and the depth and IR images are visible (320x962, 8-bit only) though the image is left-half/right-half interlaced.
The RealSense CHOP does not show any data.
The VideoIN modes seem to be limitations of Intel’s drivers. I’m wondering if the RealSense TOP issues have to do with using the r200 camera instead of the f200? Are there certain driver versions that work better?
There seems to be a conflict with the R200 and the Video Device In TOP that can cause the CoInitialize error. Working on fixing that right now actually.