Sony ships Eclipsa-certified phone microphone, opening spatial-audio capture to USB-C smartphones

Spatial capture moves to the smartphone with the ECM-AX10

The day's clearest workflow shift is Sony's launch of the ECM-AX10, a compact USB-C microphone that brings spatial-audio capture to compatible smartphones. According to multiple reports, the unit weighs approximately 24g and uses four built-in omnidirectional microphone capsules to record ambisonics and binaural material directly to a phone. Sony positions the device as the first Eclipsa Audio-certified microphone for smartphones, meaning creators can capture and publish spatial audio on a handset without a separate field recorder.

A 3.5-mm jack provides real-time monitoring, and the package ships with a windscreen. For podcasters and field recordists who already work in ambisonics, the bar to publishing a spatial mix drops from a dedicated recorder to a phone, a USB-C cable, and an app that speaks Eclipsa.

Why a phone-friendly spatial mic changes the recording chain

A pocketable, Eclipsa-certified microphone reframes which steps of a spatial-audio session actually need a studio. Capture, monitoring, and first-stage encoding can now happen on the handset itself, so the post-production work that used to require a DAW session becomes a file-import and metadata-check pass. That in turn puts pressure on editing and publishing tools to recognise Eclipsa Audio metadata and to preserve ambisonic channel layouts through export.

Creators who have been holding off on spatial projects because the capture path was a separate recorder can now trial the format on the device they already carry, and the recording session can fit inside an Online Metronome rehearsal block rather than a dedicated studio day.

What mobile creators should check before adopting Eclipsa capture

The evidence points to a few practical gates that decide whether the ECM-AX10 is usable in a given setup. The microphone requires a compatible smartphone that supports both USB-C audio input and the Eclipsa Audio publishing path; without the host-side software, the four-capsule ambisonics array is just hardware. Monitoring depends on the 3.5-mm output, so engineers who monitor through the phone's own speakers or a Bluetooth headset should plan for wired monitoring.

Wind handling is addressed by the bundled windscreen, but indoor use in treated rooms will still need a stand or mount — the 24g body is light enough to clip or rest, and any handling noise will sit inside the spatial bed. Treat the first sessions as format-validation work, not as a finished pipeline.

What to watch as Eclipsa moves onto phones

The single development to track is whether editing and podcast-hosting tools start advertising native Eclipsa Audio support, because the capture side is now solved. Until DAWs and hosting platforms confirm they will pass through ambisonic channel data without downmix, the practical ceiling on the workflow sits in post, not in the field. Creators who already maintain lyric or SRT timed-text deliverables can prepare by adding a metadata check pass; any spatial mix that ships without channel-layout notes is harder for collaborators to audition correctly.

A short, structured workflow is to capture with the ECM-AX10, audition through the 3.5-mm monitor path, then verify that the host app and editor preserve the ambisonic bed through export before publishing. The Cut Audio in Your Browser: A First-Time Walkthrough guide becomes more useful as soon as the export step keeps spatial metadata intact, and Create a Lyrics SRT File for Music with Exact Timestamps covers the timed-text side that any spatial release should ship alongside.

Follow-up coverage should focus on Eclipsa compatibility lists from phone makers and from the major DAWs, since those lists decide whether today's announcement becomes a real production path.