Processing

This guide explains the Mimi Processing concepts and how to integrate it into your application.

Overview

For a detailed view, familiarize yourself with the Processing API Architecture.

Activation & Configuration

Activation

As the MimiProcessingController owns the MimiProcessingSession; it is the location where processing can be “activated” or “deactivated”.

The lifecycle of the MimiProcessingSession instance should align with the headphone connectivity lifecycle. The activation of the session should happen once a connection with the headphones has been established and the techLevel is obtained from the firmware, since it is required for the session activation. Similarly, the session should be deactivated once the headphones have been disconnected.

Note: Activation refers to the ability for parameters values to be transferred and not whether the physical processing effect is enabled or disabled.

During activation, a Processing Configuration must be provided and based on the firmware on the device, this will either be the Basic Processing Configuration or the Automatic Configuration.

Basic or Automatic Processing Configuration?

There are two Processing Configurations, MimiBasicProcessingConfiguration and MimiAutomaticProcessingConfiguration. A Mimi Processor device will only support one mode of configuration and MimiBasicProcessingConfiguration should be used with older devices without Automatic support.

Basic Automatic
Feature Availability Only Media Sound Personalization Varies - determined by Mimi Processor device
Applicators One per MimiProcessingParameter, included independent timeouts A single Applicator for all communication
Preset Data Source Configurable (Single, Fine Tuning or Group). Not configurable - only supports Fine Tuning)
Parameter Data Persistence Managed by MSDK Managed by Mimi Processor device

See Basic Processing Configuration Mode or Automatic Processing Configuration Mode for detailed documentation on the respective configuration modes.