AI Voice Engineering Services

From validation to product integration and production scale-up

mpWAV applies single- and multi-microphone enhancement, wake-word detection, sound source localization, multi-party processing, speaker diarization, on-device speech recognition, and a conversational LLM to your product.

From PoC on your real audio data through software integration, DSP·FPGA·AP porting, microphone array and multi-channel hardware design, model optimization, licensing, and dedicated SoC collaboration — engineering services matched to your development stage.

Core services

PoC · Software Integration · On-Device AI · Embedded Porting · HW Integration · Licensing · SoC Partnership

Image [S1]
Services hero — customer product & data → mpWAV services → integrated product

Customer Product + Real-World Audio + Target Platform

↓ mpWAV Engineering Services — Technology Selection · PoC · Software Integration

Model Optimization · DSP·FPGA·AP Porting · HW Integration · Licensing · SoC

↓ Integrated Voice Product (validate → integrate → field → production)

From Technology to Your Product

What do mpWAV's engineering services do?

Our engineering services validate and integrate our voice algorithms and AI models so they run on your real product data, your microphone and speaker structure, and your compute platform.

Rather than handing over algorithm or model files, we review the entire data flow — input capture, preprocessing, wake·location·speaker analysis, recognition, dialogue understanding, and product API execution.

We turn an algorithm's potential into your product's real performance.

Image [S2]
The engineering between technology and product

mpWAV Technology (10 technologies)

↓ Engineering — Audio I/O · Data Processing · Model Optimization

Platform Porting · API Integration · Field Validation

↓ Customer Product

Service Portfolio

Pick the service that matches your current challenge

PoC & performance validation

Confirm the effect on your real product data

We analyze single/multi-channel audio collected from your product and your current recognition results, comparing before and after mpWAV technology.

Covers

  • mpNC
  • mpAEC
  • mpBeamforming
  • mpAB
  • mpWWD
  • mpS
  • mpLocalization
  • mpDiarization
  • mpASR
  • mpLLM
Discuss a PoC

Software·SDK integration

Connect the voice technology you need to your product

Apply a single module, or integrate the full software stack from preprocessing to recognition and dialogue.

Typical structures

  • Preprocessing in front of your existing ASR
  • Wake-word based voice commands
  • Localization and speaker analysis
  • Kiosk voice ordering
  • Meeting records with speaker separation
  • Single-mic smart device processing
Discuss SDK integration

On-device AI optimization

Wake word, recognition, and dialogue inside the product

We review the feasibility of running mpWWD, mpASR, and mpLLM under your product's CPU·GPU·NPU and memory conditions.

Scope

  • Model size review
  • Inference latency
  • Memory footprint
  • Quantization & compression
  • Domain data application
  • Product API connection
Discuss on-device AI

DSP·FPGA·AP porting

Move validated technology to your target platform

We optimize technology proven on PC or reference environments to run in real time on your DSP, FPGA, or AP.

Scope

  • Multi-channel audio input
  • AEC reference connection
  • Real-time stream processing
  • Compute & memory optimization
  • Existing ASR & product API integration
See DSP·FPGA·AP porting

Mic array & HW integration

From voice input to the processing board

We connect the microphone array, speaker output, AEC reference, multi-channel audio I/O, and compute platform into one product structure.

Scope

  • Linear & multi-directional arrays
  • Multi-channel MEMS input
  • Speaker output
  • Reference loop-back
  • FPGA·DSP·AP boards
  • Product modules
Discuss mic array & HW

Licensing & co-development

Technology designed jointly around your product and data

When per-product optimization matters more than a standard module, we collaborate through algorithm licensing, AI model application, or co-development.

Scope

  • Speech preprocessing licenses
  • Interaction technology application
  • mpASR·mpLLM product optimization
  • Industrial acoustic analysis
  • Follow-on product expansion
Discuss licensing·co-development

Semiconductor IP·SoC partnership

Dedicated voice interface structures for volume production

Building on FPGA·DSP validation, we review semiconductor IP or dedicated SoC collaboration for products that need power, size, and cost optimization.

Collaboration type

  • Semiconductor IP collaboration
  • Dedicated SoC co-development
  • Volume production optimization

Official material presents voice interface chips and a dedicated SoC as business models and expansion directions. Today this proceeds as co-development and partnership, not a standard semiconductor product.

Discuss SoC·IP partnership
Image [S3]
Seven service cards (customer situation · technologies · deliverables · next step)

PoC | Software·SDK | On-Device AI | DSP·FPGA·AP Porting

Mic-Array·HW | Licensing·Co-development | Semiconductor IP·SoC

Proof of Concept

Confirm applicability with your real product data

Voice technology performance depends on microphone count and layout, user distance, noise, speaker output, number of talkers, your existing ASR, and the execution platform.

mpWAV evaluates before-and-after results against data collected from your actual product rather than generic demo audio.

Voice enhancement validation

mpNC · mpAEC · mpBeamforming · mpAB

  • Ambient noise impact
  • Echo reduction
  • Target voice preservation
  • Before/after audio quality
  • Change in existing ASR results

Wake-word & localization validation

mpWWD · mpLocalization

  • Wake-word detection results
  • Missed & false detections
  • Direction estimation
  • User position changes
  • Product mic array effects

Multi-party & speaker validation

mpS · mpDiarization

  • Multi-party & overlapping speech
  • Per-speaker segments
  • Speaker turns
  • Speaker tagging results
  • mpASR-connected results

Recognition & dialogue validation

mpASR · mpLLM

  • WER·CER
  • Command success rate
  • Domain terminology
  • Intent understanding
  • Menu·option·quantity extraction
  • Context retention
  • Product API execution

System performance validation

  • Processing latency
  • Memory
  • CPU·DSP·FPGA usage
  • Model size
  • Continuous streaming
  • Product stability

Example outputs

  • Before/after audio
  • Recognition & detection comparisons
  • Error-type analysis
  • Recommended technology stack
  • Target platform assessment
  • Follow-on porting & integration scope
Image [S4]
Full PoC dashboard (enhancement · interaction · recognition · dialogue · system)

Voice Enhancement: Noise·Echo·Distortion | Interaction: Wake Word·Localization·Speaker Segments

Recognition: WER·CER·Command Success | Dialogue: Intent·Slot·Context·API | System: Latency·Memory·Compute

Software and SDK Integration

Pick only what you need — or connect the full voice stack

Depending on your product's current structure and required features, apply a single module or integrate several technologies into one continuous pipeline.

Front end for your existing ASR

Microphone → mpNC / mpAEC / mpBeamforming / mpAB → Existing ASR

Improves input quality without replacing your recognition engine.

Robot voice interface

mpWWD → mpLocalization → mpAB → mpASR → mpLLM → Robot Command

Connects wake-up, speech direction, noise/echo preprocessing, recognition, and dialogue.

Kiosk voice ordering

Mic Array → mpAB → mpASR → mpLLM → Ordering API

Voice ordering and conversational option confirmation in store noise.

Single-mic smart device

Single Mic → mpNC → mpWWD → mpASR → mpLLM → Device Function

For earbuds and small devices that can't add microphones.

Meetings & voice chat

mpAEC / Beamforming → mpS → mpDiarization → mpASR → mpLLM → Transcript / Summary

Connects multi-party processing, speaker separation, records, and summaries.

Image [S5]
Five software pipeline cards

Existing ASR | Robot | Kiosk | Single-Mic Device | Meeting

On-Device AI Optimization

From wake word to recognition and dialogue — running inside your product

An on-device voice interface is not decided by model accuracy alone.

Wake-word detection, recognition, and the dialogue model must be reviewed as one execution structure against your product's memory, CPU·GPU·NPU, power, response time, and update method.

mpWWD optimization

Wake-word detection

  • Target wake words
  • Languages
  • Ambient noise
  • False/missed detections
  • Always-on compute
  • Product activation flow

mpASR optimization

On-device speech recognition

  • Supported languages
  • Model size
  • Domain vocabulary
  • WER·CER
  • Streaming
  • Latency
  • Server·PC·edge deployment

mpLLM optimization

Dialogue and intent understanding

  • Model scale
  • Memory & accelerators
  • Quantization level
  • Dialogue context
  • Menu & feature data
  • Product API connection
  • Response policy

mpLLM is being developed in the direction of a 1B-class on-device dialogue model; actual feasibility depends on model version, precision, memory, and the target accelerator.

Input preprocessing

Depending on your microphone conditions, the following applies as the front end:

  • Single microphone: mpNC
  • Multi-mic ambient noise: mpBeamforming
  • Speaker echo: mpAEC
  • Echo + noise together: mpAB

Key review metrics

  • Model size
  • Memory footprint
  • First response time
  • End-to-end latency
  • Token / command throughput
  • Power
  • Product API success rate
  • Network dependence
Image [S6]
On-device AI structure (preprocessing → wake word → recognition → dialogue + HW conditions)

Audio Input → mpNC/mpAB → mpWWD → mpASR → mpLLM → Local Product API

Conditions: CPU · GPU · NPU · Memory · Power · Latency

Embedded Porting

Validated technology, moved to your compute platform

Applying technology proven in a reference environment to a real product requires porting matched to the target processor's compute, memory, audio interfaces, and latency.

Official material presents FPGA implementation of the integrated mpAEC·mpBeamforming technology, MCU+DSP structures, AP·DSP porting, and multi-channel mic/echo input board design experience.

FPGA

Multi-channel real-time processing

  • Multi-channel mic input
  • AEC reference
  • mpAEC·Beamforming·mpAB
  • Real-time streaming
  • Resource usage
  • Pre-SoC architecture

DSP

In-product low-latency processing

  • Compute optimization
  • Memory
  • Fixed/floating point review
  • Audio frame processing
  • MCU coordination
  • Update structure

AP

OS and product service integration

  • Audio drivers
  • Multi-channel streams
  • Existing ASR
  • mpASR·mpLLM
  • Product APIs
  • Application deployment

Edge AI platform

AI models and preprocessing together

  • mpWWD
  • mpASR
  • mpLLM
  • CPU·GPU·NPU execution
  • Model compression
  • Full pipeline latency
Image [S7]
Porting platform structure (FPGA·DSP·AP·Edge AI → product)

mpWAV Reference Stack → Porting & Optimization

→ [ FPGA | DSP | AP | Edge AI ] → Audio Driver·ASR·API → Customer Product

Multi-Channel Hardware Integration

From voice input to the processing platform, in one product structure

Applying multi-microphone technology to a real product means designing mic count and layout, channel synchronization, speaker output, the AEC reference, and the compute board together.

mpWAV brings experience with linear and hexagonal arrays, USB multi-channel audio I/O, FPGA·DSP·AP connections, and integrated speech preprocessing.

Array design

  • User direction
  • User distance
  • Product form factor
  • Speaker placement
  • Dominant noise
  • mpLocalization requirements

Multi-channel audio I/O

  • MEMS mic input
  • Speaker output
  • AEC reference
  • Channel synchronization
  • Sampling conditions
  • USB or product interface

Processing boards

  • FPGA
  • MCU+DSP
  • AP
  • Edge processors
  • Existing product board connection

Algorithm integration

  • mpAEC
  • mpBeamforming
  • mpAB
  • mpLocalization
  • mpASR

Design cases from official material

  • Linear kiosk array — 4- or 6-channel MEMS microphone input
  • CES demo 6-channel hexagonal array — speaker output and AEC reference loop-back

These are design cases from official material and do not imply common specifications for all currently supplied modules.

Image [S8]
HW integration architecture (mics·speaker·reference → board → algorithms → API)

Mic Array + Speaker Output + AEC Reference → Multi-Channel Audio Board

→ FPGA·DSP·AP → mpAEC·Beamforming·Localization·mpAB → ASR·LLM·Product API

Licensing and Co-Development

Technology scope designed together around your product and data

Every product differs in microphones, users, noise, compute platform, and service goals — a standard package cannot solve everything.

mpWAV negotiates licensing, model optimization, or co-development scope based on your real data and product requirements.

Voice enhancement licensing

mpNC · mpAEC · mpBeamforming · mpAB

Applied to your product's single- or multi-microphone input.

Interaction technology

mpWWD · mpS · mpLocalization · mpDiarization

Connects wake word, user direction, multi-party voice, and speaker information to product functions.

Recognition & dialogue models

mpASR · mpLLM

Reviewed for your domain vocabulary, menus, command sets, and product APIs.

Industrial acoustic analysis

Co-develops analysis models using per-product acoustic data — such as factory equipment anomaly detection.

Full-product co-development

Microphone arrays, audio I/O, preprocessing, recognition, dialogue, and product APIs in one project.

Follow-on expansion

Technology proven in the first product extended to other mic configurations, platforms, product lines, and languages.

Image [S9]
Co-development process (requirements+data → review → stack design → PoC → optimization → integration → expansion)

Product Requirements + Real-World Data → Joint Technology Review → Technology Stack Design

→ PoC → Product Optimization → Platform Integration → License·Production·Expansion

Semiconductor IP and SoC Partnership

Validated voice technology, in dedicated structures for volume production

Vehicles, smart devices, and volume products must weigh size, power, and cost alongside algorithm performance.

Building on software algorithms, real-time FPGA processing, and multi-channel hardware implementation, mpWAV reviews IP·SoC collaboration with semiconductor companies and volume customers.

Technology blocks under review

  • mpNC
  • mpAEC
  • mpBeamforming
  • mpAB
  • mpWWD
  • Multi-channel Audio I/O
  • Lightweight mpASR
  • Per-product AI acceleration

Fields under review

  • Vehicles·mobility
  • Smart home·appliances
  • Robots·kiosks
  • Consumer smart devices
  • Defense·special environments

Collaboration phases

Algorithm Validation → FPGA Prototype → Architecture Review → Semiconductor IP → Dedicated SoC → Product Validation

Official material presents voice interface chips for vehicles, consumer devices, and defense, plus a dedicated SoC, as expansion directions. Public material does not include standard chip model names, datasheets, or production schedules.

Image [S10]
SoC expansion roadmap (SW → FPGA → module → IP → SoC → production)

Software → FPGA → Product Module → Semiconductor IP → Dedicated SoC → Mass Production

Targets: Performance · Latency · Power · Size · Cost

Service Packages by Application

Service combinations matched to your product environment

Robots

Recommended technology

mpWWD · mpLocalization · mpAEC · mpBeamforming · mpAB · mpASR · mpLLM

Recommended services

  • Multi-channel data PoC
  • Mic array design
  • AP·DSP·FPGA porting
  • Robot control API integration
  • Dialogue model optimization

Kiosks

Recommended technology

mpAB · mpASR · mpLLM · Mic-Array HW

Recommended services

  • Store audio validation
  • Linear mic array
  • Menu/domain ASR optimization
  • 1B-class dialogue model review
  • Ordering API integration

Vehicles & mobility

Recommended technology

mpWWD · mpLocalization · mpAEC · mpBeamforming · mpAB · mpASR · mpLLM

Recommended services

  • In-cabin multi-channel PoC
  • Audio reference integration
  • DSP·AP porting
  • Seat/direction validation
  • SoC·IP collaboration review

Smart devices & earbuds

Recommended technology

mpNC · mpWWD · mpASR · mpLLM

Recommended services

  • Single-mic data validation
  • Lightweight preprocessing
  • On-device model optimization
  • AP·edge integration
  • Low-power execution review

Meetings & voice chat

Recommended technology

mpS · mpDiarization · mpAEC · mpBeamforming · mpASR · mpLLM

Recommended services

  • Multi-party meeting data evaluation
  • Speaker separation validation
  • Meeting transcription ASR
  • Summary·Q&A integration
  • PC·server·edge deployment

Factory anomaly detection

Recommended technology

Noise-Robust Acoustic Processing · Anomaly Detection

Recommended services

  • Real production line PoC
  • Feature analysis
  • Normal/anomaly classification
  • Edge integration
  • Licensing·co-development
Image [S11]
Per-industry service cards (product · key technology · services · final features)

Robot | Kiosk | Vehicle | Smart Device | Meeting | Factory

Find the Right Service

Pick your project's current situation

Current situationRecommended service
We want to confirm the effect of mpWAV technology firstPoC & validation
We want to connect a technology module to an existing productSoftware·SDK integration
We want wake word, ASR, and LLM running inside the productOn-device AI optimization
Our target DSP·FPGA·AP is already fixedEmbedded porting
We need a microphone array and audio boardHW integration
We need per-product data and long-term collaborationLicensing·co-development
We need a dedicated chip for volume productionSoC·IP partnership
Image [S12]
Service selection flowchart

Confirm effect?→PoC | Connect to SW?→SDK Integration | On-device AI?→Model Optimization

Platform fixed?→Porting | Mic·board?→HW Integration | Long-term?→License/Co-dev | Volume?→SoC/IP

From Requirement to Deployment

From real-environment analysis to product deployment and expansion

The following is a typical example — the actual sequence and scope are adjusted per project.

  1. 1

    Define product & service goals

    Wake word, commands, dialogue, meeting records, listening improvement, or anomaly detection — we scope what you need.

  2. 2

    Analyze acoustic & system structure

    Microphone count, speakers, user distance, number of talkers, dominant noise, and the target platform.

  3. 3

    Evaluate data

    Single/multi-channel raw audio, the AEC reference, ground-truth text, and existing results.

  4. 4

    Design the technology stack

    Select the required technologies and processing order from the full mpWAV portfolio.

  5. 5

    Reference PoC

    Confirm before/after performance and product features on PC or an evaluation environment.

  6. 6

    Decide the implementation

    SDK, model optimization, mic array, DSP·FPGA·AP porting, or licensing.

  7. 7

    Integrate the product

    Connect audio input, mpWAV technology, your existing ASR, mpASR·mpLLM, and product APIs.

  8. 8

    Optimize the platform

    Tune latency, memory, compute, power, and model size.

  9. 9

    Field verification

    Confirm results and user experience on the real product, where it's used.

  10. 10

    Production & expansion

    Licensing, updates, follow-on products, international deployment, and SoC expansion.

Image [S13]
Full service timeline (goals→analysis→data→stack→PoC→implementation→integration→optimization→field→production)

Goals → System analysis → Data → Stack → PoC → Implementation → Integration → Optimization → Field → Production

Project Deliverables

Deliverable scope agreed per project

The following are typical examples — actual scope is agreed per project under the development and licensing terms.

PoC results

  • Before/after audio
  • Recognition & detection results
  • Error analysis
  • Performance comparison
  • Recommended stack

Software·SDK

  • Library or executable module
  • API
  • Configuration
  • Sample code
  • Integration guide

AI models

  • Target-platform models
  • Model configuration
  • Domain data applied
  • Performance report
  • Runnable examples

Embedded porting

  • FPGA·DSP·AP builds
  • Audio I/O interfaces
  • Resource & latency measurements
  • Regression results
  • Build & integration docs

Hardware

  • Evaluation boards
  • Microphone arrays
  • Audio I/O design
  • Reference connection
  • Product board design data

Licensing·co-development

  • Technology scope
  • Supported platforms
  • Update terms
  • Product line coverage
  • Follow-on development
Image [S14]
Deliverable package (reports · SW · models · ported builds · HW · docs)

PoC Report | Software Library | AI Model | API | Ported Build | Hardware Module | Integration Guide

Implementation Experience

Research technology, applied to real products and sites

Robot voice interfaces

ASR preprocessing validated for home, showroom, and care robots

Kiosk modules

Multi-channel array I/O and ASR preprocessing structures deployed

Mobility PoC

Vehicle and mobility voice interfaces reviewed in real noise

Factory acoustic analysis

Motor anomaly detection validated amid complex line noise

Hearing assistance

ClearSense Audio applied on smartphones and earphones, including welfare centers

Embedded implementation

Real-time FPGA, MCU+DSP structures, and AP·DSP porting

Image [S15]
Implementation evidence (robot·kiosk·vehicle·factory·ClearSense·boards)

Robot voice test | Kiosk mic array | In-vehicle data collection

Factory motor measurement | ClearSense in use | FPGA·DSP boards

Project Information

Share the following and we can scope the right service

Product

  • Product or service type
  • Primary users
  • Usage locations
  • Development stage
  • Launch schedule
  • Expected volume

Mic & speaker structure

  • Microphone count & positions
  • Single or multi-channel
  • Speaker output
  • AEC reference
  • User distance
  • Main speech directions
  • Multi-party speech

Required features

  • Single-mic noise reduction
  • Echo cancellation
  • Multi-mic noise reduction
  • Wake-word detection
  • Sound source localization
  • Multi-party processing
  • Speaker separation
  • Speech recognition
  • Natural-language dialogue
  • Anomaly detection

System environment

  • CPU·MCU
  • DSP
  • FPGA
  • AP
  • GPU·NPU
  • Operating system
  • Memory
  • Latency budget
  • Power budget

Data

  • Single/multi-channel raw audio
  • Speaker reference
  • Ground-truth text
  • Existing ASR results
  • Menus & commands
  • Meeting or speaker data
  • Failure cases
  • System block diagram

You don't need every item confirmed to start — share the voice problems your product hits most often and the features you're aiming for.

FAQ

Frequently asked questions about mpWAV engineering services

The full mpWAV portfolio can be reviewed.

That includes mpNC, mpAEC, mpBeamforming, mpAB, mpWWD, mpS, mpLocalization, mpDiarization, mpASR, and mpLLM.

Delivery status and contract form are agreed per project.

Yes.

Starting from your product structure and typical usage scenarios, we can design the required data channels, recording conditions, and ground-truth format first.

Yes.

mpNC, mpAEC, mpBeamforming, and mpAB apply in front of your existing ASR, improving the input audio.

mpNC covers single-microphone noise control feasibility.

Specific platforms and compute budgets are confirmed under real product conditions.

A microphone array, mpAB, mpASR, and mpLLM can be connected to interpret menu·options·quantity and hand off to the ordering API.

Real deployment also needs menu data, dialogue policy, and target hardware validation.

mpS and mpDiarization process multi-party audio and speaker segments, then connect to mpASR.

It is being developed in the direction of a 1B-class on-device dialogue model.

Feasibility depends on model version, quantization, memory, accelerators, and the target response time.

Official material presents real-time FPGA implementation, MCU+DSP structures, and AP·DSP porting experience.

Support for a specific chipset is reviewed against compute resources, the toolchain, and audio interfaces.

Multi-channel microphone arrays, speaker output, the AEC reference, USB audio, and processing board integration can be reviewed.

Whether it's a standard module or a custom design depends on the project.

There is no fixed standard duration or price.

They are agreed per project based on the technologies applied, data readiness, target platform, hardware scope, optimization level, and field validation scope.

The delivery form — source code, libraries, binaries, models, FPGA IP, or co-development — is decided by the contract terms.

Start Your AI Voice Project

Turn your product's voice problem into a concrete engineering project

Tell us your product type, mic·speaker structure, dominant noise, required features, and target platform — we will scope the right mpWAV technology and services.

From single-mic noise control to multi-channel echo and noise processing, wake·location·speaker analysis, on-device ASR and conversational LLM, DSP·FPGA·AP porting, and SoC expansion — start at whatever stage your product is in.

Image [S17]
Final CTA service stack (data → selection → PoC → integration → optimization → deployment)

Real-World Audio → Technology Selection → PoC → Software/AI/HW Integration

→ Platform Optimization → Product Deployment (Earbuds·Robot·Kiosk·Vehicle·Meeting·Factory)

mpWAV develops and licenses voice interface technology that makes speech clear in noisy, real-world environments, built on 25+ years of speech signal processing research.

(주)엠피웨이브·사업자등록번호 859-81-01905·대표 박형민

Teilhard Hall 405, 35 Baekbeom-ro, Mapo-gu, Seoul, Korea

02-705-8916·info@mpwav.com

© 2026 (주)엠피웨이브. All Rights Reserved.