Re: Feature request: id in .process
Mamadou DIOP
You can know, no need for additional param
The engine is a static variable, you cannot create instance of it. Even if you have 2 streams, only 1 engine will be used.
The images are delivered in FIFO mode (First In First Out). The two streams will put frames from different treads (A and B), let's say: A0, A1, B0, A3, B1... (A0 means threads A and frame number 0)
the callback will deliver the result in the exact same order: A0, A1, B0, A3, B1...
in short, you can maintain a queue (push,
pop) with information on the frames
We have one place where we have two streams which we would like to process with one ALPR computer.
When utilizing (C++) parallel ALPR process, we cannot know from what stream the result came from.
So, would it be possible to add one (optional) parameter to UltAlprSdkEngine::process -function, like one integer which acts as an id. This should come back in some way in result as well.
-t--
You received this message because you are subscribed to the Google Groups "doubango-ai" group.
To unsubscribe from this group and stop receiving emails from it, send an email to doubango-ai...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/doubango-ai/400a7a60-c99e-4f58-b218-ba4e4c6a22dcn%40googlegroups.com.
Mamadou DIOP
clarification:
in your app you know that you put (process): A0, A1, B0, A3, B1...
the callback will give you (result): R0, R1, R2, R3, R4...
you can easily map: (A0,R0), (A1,R1), (B0,R2), (A3,R3), (B1,R4)...
To view this discussion on the web visit https://groups.google.com/d/msgid/doubango-ai/8080a456-45a8-4574-bb15-8dfba19ae5fa%40doubango.org.
