1- Audience measurement


The Player once launched will send an http request to Quividi for each new media.

The purpose of this request is to log the new media and to stop the logging of the previous media.


Player installation

- Fill in the registry key : M4DHKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Telelogos\Media4DisplayClient\OnMediaStartCommand as follows :

C:\Media4Display\Quividi.cmd "%REF%"


Quividi.cmd will have to contain those 2 below commands :

curl -G http://localhost:9080/v1/stop (http://localhost:9080/v1/stop)

curl -G http://localhost:9080/v1/start (http://localhost:9080/v1/start)? --data-urlencode"content_id=%~1"


Note: Curl is native on Windows 10 if your machine doesn't have Curl don't hesitate to get it from another machine here :c:\windows\System32\curl.exe and copy the file to c:\windows\System32\curl.exe & c:\windows\Syswow64\curl.exe of the player


2- Facial Detection


When the session starts, a web page launched by mediacontact connects to Quividi's websocket, retrieves the events and launches the HTTP api by passing the criteria.


Note: The web page can call several players on the network and Vidireports can also be installed on another machine).

Installation


No installation required for face detection. Simply launching the web page is enough.

The Web page available here


By default, triggering.html is configured to use Vidireports and the local Web page results :


3- M4D Configuration 

Configure the rules base with the criteria provided by the api (gender / age_value / has_mask/ num_glances)