depthai-python: [ImageManip(7)] [error] Invalid configuration or input image - skipping frame
Hi, on my Blazepose repository, I am investigating the following issue: geaxgx/depthai_blazepose#29
In summary, we get the message [ImageManip(7)] [error] Invalid configuration or input image - skipping frame under certain conditions that are still not perfectly clear. It happens from time to time when the script node sends an ImageManip config to the ImageManip node (7) (the blue arrow in the graph below):
The ImageManip configuration is a dynamically calculated setCropRotatedRect operation. The RotatedRect is defined with normalized values (normalizedCoords=True). My first hypothesis was that the config sent was invalid, but if I try to apply the same exact RotatedRect in a very basic example (a pipeline with a ColorCamera and a ImageManip), I don’t get any error.
Actually, I wonder if there are possible invalid values in a setCropRotatedRect operation. I have tried with even absurd values without getting any error. I am aware that the output images may be too big, but in that case the error message is different ([error] Output image is bigger than maximum frame size specified in properties).
Knowing the exact conditions under which the message [error] Invalid configuration or input image happens would help me to investigate. Can you help me on this ?
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 19 (1 by maintainers)
I’m glad it helped @geaxgx. This is more of a temporary fix, as we would ideally use allocate all remaining memory after other nodes allocate their needs, to the ImageManip node, but there is no ETA on that yet.
Thanks @geaxgx for the MRE and sorry for the delay.
@moratom do you mind checking this one out?
Hi @Erol444 , I am currently using depthai 2.17.3 It is true that some of the values that defines the ROI are weird in the context of blazepose (they are generated from the output of the pose detection model and I have to investigated on this side too). But these same “weird” values works well in a simpler context (pipeline with a ColorCamera and a ImageManip), so I am wondering if the problem does not come from something else. A more precise message than
[error] Invalid configuration or input imagewould help. I agree with you, checking the values of the ROI with thresholds make sense to avoid edge cases but determining these thresholds is not straightforward (for instance for blazepose, a ROI center outside of the image is possible).