Capturesync careers12/2/2023 ![]() Both support Power-over-Ethernet, making them easy to install when using a PoE-enabled switch. ![]() The main difference between the two models is the low-light performance: the LD2222 is rated down to 0.6 lux while the IPD2220 is specified to produce useful images at down to 0.2 lux, due to what LILIN calls “Sense UP+” low-light technology. This potentially makes the IPD2220 particularly useful for installation in locations with poor lighting. Same error happens when trying to get a capture in the SDK from C# using the NuGet package.Here we are testing the LD2222E4, which has a 4mm lens (there is also a LD2222E2 model available with a 2.8mm lens), and the IPD2220ES2, which has a 2.8mm lens (there is also a IPD2220ES4.3 model available with a 4mm lens). OS with Version: Windows 10 Build 18363.The error I get in the Windows Camera appĭesktop (please complete the following information): Failed to request flush for stop: 0x800700c1 D:\x\color\mfcamerareader.cpp (538): Stop(). D:\x\color\color.cpp (123): color_capture_available(). Queue "Queue_color" stopped, shutting down and notifying consumers. Queue "Queue_depth" stopped, shutting down and notifying consumers. D:\x\sdk\k4a.c (269): capturesync_get_capture(device->capturesync, capture_handle, timeout_in_ms) returned failure in k4a_device_get_capture() Queue "Queue_capture" waiting for blocking call to complete. ![]() ![]() Queue "Queue_capture" stopped, shutting down and notifying consumers. D:\x\capturesync\capturesync.c (200): capturesync_add_capture(). Pipeline propagate error to callback: 0x800700c1 D:\x\color\mfcamerareader.cpp (1126): OnReadSample(). D:\x\deloader\deloader.cpp (51): verify_plugin(). Depth Engine loaded C:\Program Files\Azure Kinect SDK v1.4.0\tools\depthengine_2_0.DLL D:\x\dynlib\dynlib_windows.c (131): dynlib_create(). Starting camera's with the following config. D:\x\depth\depth.c (253): Signature type: MSFT D:\x\depth\depth.c (248): Build type: Release D:\x\usbcommand\usbcommand.c (224): populate_serialnumber(). D:\x\usbcommand\usbcommand.c (343): find_libusb_device(). Else, maybe some sort of dependency issue? I'd think uninstalling and reinstalling or repairing would handle that. No warnings or fishy looking USB items though. I'm wondering if it's a USB controller issue as I once got a "not enough USB controller resources" error when I had a few too many things plugged in. I've been hitting my head against this for a while, so hoping someone has seen this before. Nothing of note in the system Event Viewer either. Tried updating the firmware of the camera (it was on the version that shipped w/ 1.3), reset the camera w/ the paperclip trick, uninstalled/reinstalled and repaired the SDK too. I tried different USB ports (it's currently on a dedicated 3.1 port with external power), checked device manager for weirdness with no changes. If I only select microphone in the Azure Kinect Viewer, the sound shows up. The camera also no longer works in the Windows Camera application. I've been working with the SDK for a couple months and with the 1.4 release for a few weeks, but recently started getting this error when running either my code OR the Azure Kinect Viewer.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |