17.1.5 模块教程 4 - Plate Detector Filter
This web application consists on a WebRTC video communication in mirror (loopback) with a plate detector filter element.
Java Module Tutorial 4 - Plate Detector Filter
This web application consists on a WebRTC video communication in mirror (loopback) with a plate detector filter element.
For the impatient: running this example
First of all, you should install Kurento Media Server to run this demo. Please visit the installation guide for further information.
In addition, the built-in module kms-platedetector-6.0 should be also installed:
sudo apt-get install kms-platedetector-6.0
To launch the application you need to clone the GitHub project where this demo is hosted and then run the main class, as follows:
git clone />
cd kurento-tutorial-java/kurento-platedetector
mvn compile exec:java
The web application starts on port 8080 in the localhost by default. Therefore,
open the URL in a WebRTC compliant browser (Chrome, Firefox).
Note: These instructions work only if Kurento Media Server is up and running in the same machine than the tutorial.
However, it is possible to locate the KMS in other machine simple adding the argument kms.ws.uri to the Maven execution command,
as follows:
mvn compile exec:java -Dkms.ws.uri=ws://kms_host:kms_port/kurento
Understanding this example
This application uses computer vision and augmented reality techniques to detect a plate in a WebRTC stream on optical character recognition (OCR).
The interface of the application (an HTML web page) is composed by two HTML5 video tags: one for the video camera stream (the local client-side stream) and other for the mirror (the remote stream). The video camera stream is sent to Kurento Media Server, which processes and sends it back to the client as a remote stream. To implement this, we need to create a Media Pipeline composed by the following Media Element s:
Figure 17.27: WebRTC with plateDetector filter Media Pipeline
The complete source code of this demo can be found in GitHub.
This example is a modified version of the Magic Mirror tutorial. In this case,
this demo uses a PlateDetector instead of FaceOverlay filter.
An screenshot of the running example is shown in the following picture:
Figure 17.28: Plate detector demo in action
The following snippet shows how the media pipeline is implemented in the Java server-side code of the
demo. An important issue in this code is that a listener is added to the PlateDetectorFilter object
(addPlateDetectedListener). This way, each time a plate is detected in the stream, a message is sent to
the client side. As shown in the screenshot below, this event is printed in the console of the GUI.
private void start(final WebSocketSession session, JsonObject jsonMessage) {
try {
// Media Logic (Media Pipeline and Elements)
UserSession user = new UserSession();
MediaPipeline pipeline = kurento.createMediaPipeline();
user.setMediaPipeline(pipeline);
WebRtcEndpoint webRtcEndpoint = new WebRtcEndpoint.Builder(pipeline).build();
user.setWebRtcEndpoint(webRtcEndpoint);
users.put(session.getId(), user);
webRtcEndpoint.addOnIceCandidateListener(new EventListener<OnIceCandidateEvent>() {
@Override
public void onEvent(OnIceCandidateEvent event) {
JsonObject response = new JsonObject();
response.addProperty("id", "iceCandidate");
response.add("candidate", JsonUtils.toJsonObject(event.getCandidate()));
try {
synchronized (session) {
session.sendMessage(new TextMessage(response.toString()));
}
} catch (IOException e) {
log.debug(e.getMessage());
}
}
});
PlateDetectorFilter plateDetectorFilter = new PlateDetectorFilter.Builder(pipeline).build();
webRtcEndpoint.connect(plateDetectorFilter);
plateDetectorFilter.connect(webRtcEndpoint);
plateDetectorFilter.addPlateDetectedListener(new EventListener<PlateDetectedEvent>() {
@Override
public void onEvent(PlateDetectedEvent event) {
JsonObject response = new JsonObject();
response.addProperty("id", "plateDetected");
response.addProperty("plate", event.getPlate());
try {
session.sendMessage(new TextMessage(response.toString()));
} catch (Throwable t) {
sendError(session, t.getMessage());
}
}
});
// SDP negotiation (offer and answer)
String sdpOffer = jsonMessage.get("sdpOffer").getAsString();
String sdpAnswer = webRtcEndpoint.processOffer(sdpOffer);
// Sending response back to client
JsonObject response = new JsonObject();
response.addProperty("id", "startResponse");
response.addProperty("sdpAnswer", sdpAnswer);
synchronized (session) {
session.sendMessage(new TextMessage(response.toString()));
}
webRtcEndpoint.gatherCandidates();
} catch (Throwable t) {
sendError(session, t.getMessage());
}
}
Dependencies
This Java Spring application is implemented using Maven.
The relevant part of the pom.xml is where Kurento dependencies are declared. As the following snippet shows,
we need three dependencies:
the Kurento Client Java dependency (kurento-client),
the JavaScript Kurento utility library (kurento-utils) for the client-side,
and the plate detector module (platedetector):
<parent>
<groupId>org.kurento</groupId>
<artifactId>kurento-parent-pom</artifactId>
<version>|CLIENT_JAVA_VERSION|</version>
</parent>
<dependencies>
<dependency>
<groupId>org.kurento</groupId>
<artifactId>kurento-client</artifactId>
</dependency>
<dependency>
<groupId>org.kurento</groupId>
<artifactId>kurento-utils-js</artifactId>
</dependency>
<dependency>
<groupId>org.kurento.module</groupId>
<artifactId>platedetector</artifactId>
</dependency>
</dependencies>
Note: We are in active development. You can find the latest versions at Maven Central.
