Skip to content

Controlling output to the console #76

@djipco

Description

@djipco

Is it possible to control how the library outputs messages to the console? When calling open(), if no Kinect is detected, we get a bunch of error messages in the console. I'd rather output my own messages through a centralized logging system. I see the SDK provides some control via environment variables, but they don't seem to work in the context of this library. Would it be possible to expose some form of control over logging and console output?

Alternatively, if there was a way to get a list of available devices and associated serial number, I could open only when I know the device to be there.

By the way, thanks for your work on this great library.

P.S. These are the types of messages I'd like to get rid of:

[2024-06-28 15:30:21.142] [critical] [t=26780] D:\a\1\s\extern\Azure-Kinect-Sensor-SDK\src\usbcommand\usbcommand.c (366): find_libusb_device(). libusb device(s) are all unavalable. Is the device being used by another application?
[2024-06-28 15:30:21.142] [error] [t=26780] D:\a\1\s\extern\Azure-Kinect-Sensor-SDK\src\depth_mcu\depth_mcu.c (68): usb_cmd_create(USB_DEVICE_DEPTH_PROCESSOR, device_index, NULL, &depthmcu->usb_cmd) returned failure in depthmcu_create()
[2024-06-28 15:30:21.142] [error] [t=26780] D:\a\1\s\extern\Azure-Kinect-Sensor-SDK\src\sdk\k4a.c (133): depthmcu_create(index, &device->depthmcu) returned failure in k4a_device_open()

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions