I looked at the example you suggested with clipping/NMS, but I’m looking for a way for the parser to actually deal with the frame data itself in the context of feature extraction. Any ideas?
It seems that the custom-bbox-parser-function doesn’t interact with the frame pixel data itself, since it relies on either detect or classify output. However, the pixel data itself would be needed for extracting facial features for a given model. I suppose I could maybe add another parameter to the parser function itself (that being the raw data), but I was wondering if there is an existing pipeline for doing this type of detect-and-process-on-a-bbox task.
There is no update from you for a period, assuming this is not an issue any more.
Hence we are closing this topic. If need further support, please open a new one.
Thanks
Hi @patrick.g.tinsley
Sorry for long delay! Not sure if you have found out the solution. for your question, if you can acceess the corresponding frame, can it meet your requirement?
Do you actually have a solution to this? The .cpp file you suggested doesn’t look to do the same thing. Even so, it would be nice to keep consistency with the rest of the deepstream-python-apps. If I find anything, I’ll let you know. Thank you!
@ahsanmuhammadakram1996 You can submit a new topic with your enviornment and issues in details to start the discussion, it’s difficult to trace back the discussion happened more than one year ago, thanks.