Why the capture point matters
A file can pass through recording software, editing tools, exports and messaging services before a collaborator sees it. Capture hardware raises an earlier question: what evidence can be associated with the recording when it is first made? The research aim is to reduce uncertainty about that first step while preserving a useful connection to later versions. The full chain still needs to account for what happens after capture.
Define what the device would attest to
A credible device record needs a specific meaning. It might identify the device, a capture event and the bytes produced by that event. It must also describe how the record is bound to those bytes and how a verifier checks it. Avoid treating a device's presence as an explanation of authorship, consent or every later edit. Those questions require additional records and a workflow that connects them.
Design the failure cases before the demonstration
An evaluation plan should examine an interrupted recording, a changed export, unavailable connectivity, an incorrect device clock and a lost or replaced device. For each case, state what evidence is retained and how an incomplete result is presented. A useful prototype demonstration includes at least one of these exceptions so reviewers can see the recovery behavior instead of only a successful recording.
Make the evidence useful to a musician
The recording process should leave a file and a record that can travel with the project. A musician needs to know which export the record describes, what information will be shared and how to preserve the original. The handoff should remain intelligible to a collaborator who does not own the same device. These usability questions belong alongside capture quality, reliability and verification in an evaluation.
Current public status
The hardware direction is in development, with specifications held pending the filing process. This page sets out the problem and evaluation questions; it is not a product specification or a shipping announcement. The VoicePrint page covers the related identity research, and the provenance page explains how an exact file and its subsequent versions can be documented. The public registry documentation describes the workflow available for preparing a work today.
Sources and current documentation
Continue