A multi-detector is used to combine multiple detectors, so that multiple detectors can be used together on a frame or frames received from a source within a pipeline. Each detector is run separately on each associated frame.
For example, the code below creates and starts a pipeline that continuously receives preview frames from a camera source, runs two different detectors on each frame, and delivers results to associated processors.
fooDetector.setProcessor(new MyFooProcessor());
barDetector.setProcessor(new MyBarProcessor());
MultiDetector multiDetector = new MultiDetector.Builder()
.add(fooDetector)
.add(barDetector)
.build();
CameraSource cameraSource = new CameraSource.Builder(context, multiDetector)
.build()
.start();
Where "fooDetector" is a Detector implementation for detecting "foos" and
"MyFooProcessor" is a Detector.Processor implementation for receiving the "foos" that are detected.
| class | MultiDetector.Builder | Builder for creating MultiDetector instances. | |
| SparseArray<Object> | |
| boolean |
isOperational()
Indicates whether the detector has all of the required dependencies available
locally in order to do detection.
|
| void |
release()
Releases the underlying resources associated with the multi-detector and its
underlying detectors.
|
| void |
Runs detection on the supplied frame with each underlying detector, returning the combined detection results from all detectors.
| IllegalStateException | This indicates that the results from the underlying detectors could not be combined, because the same ID was associated with different detected items. This likely means that there is a bug with one of the detectors, in that it did not translate its detected item IDs to the global ID space. |
|---|
Indicates whether the detector has all of the required dependencies available locally in order to do detection.
When an app is first installed, it may be necessary to download required files. If this returns false, those files are not yet available. Usually this download is taken care of at application install time, but this is not guaranteed. In some cases the download may have been delayed.
If your code has added a processor, an indication of the detector operational state
is also indicated with the
Detector.Detections.detectorIsOperational() method. You can check this in
your app as it processes detection results, and can convey this state to the user if
appropriate.
Releases the underlying resources associated with the multi-detector and its underlying detectors.