![]() I do notice that this happens occasionally when a streaming session is started or stopped. I don't believe we load balance to other GPUs warning ] : DecodeMJPEGtoBGRA32(). BTW, this is the only messages that indicates GPU activity. ![]() You will see critical error messages in the viewer about firmware version, it is safe to ignore it. You will need to use 3 different log files names for the 3 different viewer instances so they don't conflict with each other. For future logs please log to a file instead of copy and pasting from the viewer, that will contain event timestamps to better understand timing. I do expect to see this warning occasionally when the PC is active and when a stream starts up. Its hard to tell from this version of the log if this is a 1 second session or several minutes. Depth image processing is too slow at 45ms (this may be transient). That firmware is good and expected to be officially released soon. Grab 79014 from the 1.4.1.Alpha package on Nuget. You need to upgrade your firmware, this version is fairly old. I also have libk4a1.3 and libk4a1.3-dev installed from Debian packages but k4aviewer is run from the built from source versionįirmware version: 1.6.102 (RGB) 1.6.75 (Depth) I expect that the GPUs are used as expected.ĬPU: AMD® Ryzen threadripper 2970wx 24-core processor × 48 After a few minutes one of the cameras should crash. Open three instances of k4aviewer and select BGRA format, 30fps, 2160p and the rest of values should be the default ones. It seems like when I check the activity of the GPU being used, there is a 64mb upper limit from the SDK per k4aviewer instance that might not be sufficient to keep up with the synchronization when having multiple cameras running. However my hardware consists on 2 GPUs GeForce RTX 2080 Ti/PCIe/SSE2, which I assume should do the job of keeping the processing under 33ms as mentioned in #1112 It seems like (from the log file) my GPU is not working hard enough. capturesync_drop, releasing capture early due to full queue TS: 326682755 type:Depth After running three instances of K4Viewer for a few minutes I get the following error (see log file below from the camera that stops working, the other two stay active)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |