Automation & Corporate · Cognition, Memory & Time

M10 · Audio Production

Tools for music and audio production: measuring, cleaning and organising sound, and preparing recording sessions for any DAW.

Real Partially implemented

Level 1 · At a glance

Tools for music and audio production: measuring, cleaning and organising sound, and preparing recording sessions for any DAW.

Benefits:

Professional measurements and processing that never overwrite the original file. The Session Co-Pilot only reads the originals: every result is a new file.

Example of use:

Measure the loudness of a master and compare it with a reference track.

Key capabilities

  • Loudness and true-peak measurement
  • Processing chain for audio files
  • BPM detection and stem classification
  • Stem separation, vocal tuning and time-stretch
  • Transcription and reminders
  • Universal Session Co-Pilot: analysis and preparation of audio and MIDI sessions for any DAW
  • Audio Pre-Processor: quality control, phase between microphones, readiness score
  • MIDI analysis, cleaning, quantisation and humanisation (always on copies)
  • Universal Resource Discovery: audio environment and digital libraries (MIDI, samples, presets, instruments) on every drive
Level 2 · Technical detail

Audio Production add-on (contract dcos_audio 1.2.0, 25 capabilities):

Details

transcription and reminders, loudness measurement to ITU-R BS.1770-4 / EBU Tech 3342 with true-peak, an offline DSP chain, non-destructive audio intelligence (stem classification, BPM, gain staging, cataloguing) and real procedural generation, stem separation (HPSS + centre), vocal tuning (pyin + pitch shift) and time-stretch (phase vocoder); neural back-ends are used automatically only if installed. Since the MASTER build of 2026-11-13 it includes the Universal Session Co-Pilot & Audio Pre-Processor 1.0.0 (7 of the 25 capabilities: copilot_analizza_sessione, copilot_prepara_sessione, midi_analizza, midi_elabora, copilot_stato, copilot_ambiente, copilot_libreria): automatic session detection with an Inbox watcher and a queue, track role recognition and standard names on copies, audio quality analysis, phase and alignment between microphones, acoustic fingerprints and duplicates, session quality control with a readiness score, a session workspace with a SHA-256 manifest, a MIDI engine (SMF 0/1/2 analysis, cleaning, quantisation, swing, humanisation on copies), recognition of the audio environment (DAWs, audio devices, ASIO, plug-in folders, DAW projects) and Universal Resource Discovery of digital libraries (MIDI, samples, loops, impulse responses, presets, soundbanks, instruments, plug-ins) on every drive. It reuses the existing M10 engines and works with any DAW through standard files. The status register marks the module PARTIALLY IMPLEMENTED because several planned parts are missing.

New in V131 — in preparation

M10 Studio Engines

Contract dcos_audio 1.3.0 · Studio Engines 1.0.0 · 2026-11-15

M10 Studio Engines 1.0.0 adds nine audio production engines to the M10 module, without changing the existing capabilities.

The current downloadable package is V130: these functions will come with the V131 release, after acceptance testing, build and signing. Each function shows its real classification.

Components implemented and integrated in this phase (9)

  • Channel vocoder: a voice modulates a carrier (file or synthetic), 4-64 bands, formants and sibilants vocoder IMPLEMENTED AND TESTED
  • Linkwitz-Riley multiband compressor, 2-6 bands, flat reconstruction, zero latency compressore_multibanda IMPLEMENTED AND TESTED
  • Sidechain compression (ducking): the key track lowers the main track compressore_sidechain IMPLEMENTED AND TESTED
  • Adaptive mix of 2-32 stems: levels, masking corrections and panning, each with its reason mix_adattivo IMPLEMENTED AND TESTED
  • Audio to MIDI: melody (pyin) and major/minor chords in a new .mid file audio_to_midi IMPLEMENTED AND TESTED
  • Arpeggiator on MIDI files: 6 patterns, divisions down to 1/32 and triplets, 1-4 octaves, swing arpeggiatore IMPLEMENTED AND TESTED
  • Slicing at transients (up to 128 slices), BPM and key matching, MIDI map and SFZ instrument campionatore_slice IMPLEMENTED AND TESTED
  • A sample triggered on a track's transients or on MIDI notes, up to 256 voices campionatore_trigger IMPLEMENTED AND TESTED
  • Available engines and real-time factor measured on this machine studio_stato IMPLEMENTED AND TESTED

Integration and status

  • Contract dcos_audio 1.3.0: 34 capabilities (the previous 25 unchanged + 9 new), audio_intel licence unchanged IMPLEMENTED AND TESTED
  • Stateful block engines ready for real time; live input/output from the audio interface not yet connected IMPLEMENTED BUT NOT FULLY TESTED
  • Integration with M11: M10's audio analysis feeds visuals, covers and beat-timed videos (M10 not modified) IMPLEMENTED AND TESTED

Tests run on 2026-11-15: 32/32 M10 Studio Engines, contract and interface tests passed.

Prerequisites

Licence audio_intel. Optional neural packages for advanced generation. Licences already issued that include audio_intel also enable the Session Co-Pilot, without being regenerated.

Declared limits

Sample library, songwriting assistant, MIDI composition, advanced pitch/harmony analysis, vocoder and a complete M10 panel are planned.

Details

Neural audio generation with non-commercial weights is excluded. The Session Co-Pilot works through standard files (WAV/BWF/AIFF, SMF) and has no native integration with a specific DAW; role and content recognition is heuristic. In the executable, the installed workflow (Inbox watcher, queue, session workspace) is not available: the analysis, MIDI, reference, separation, environment and library commands are.

Planned (roadmap)

  • Sample library (M10.5)
  • Songwriting assistant (M10.3)
  • Symbolic MIDI composition (M10.1)
  • Pitch, intonation and harmony analysis (M10.8, M10.9)
  • Vocoder (M10.10)
  • Dedicated stem separation (M10.2)
  • Complete M10 panel

Blocked by decision

  • Neural audio generation: MusicGen weights under CC-BY-NC are excluded

Owner's note

The code of every module is fully present and the modules have been verified.

Details

Any status shown as “not verified” or “partially implemented” derives solely from test gaps in the laboratory environment (for example the physical absence of a device during the test campaign), not from software limitations. Declared simulations (decision D-24) are deliberate design choices.

Interconnections

The interconnections shown are documented functional relationships (code reuse and data flows) or derive from the architectural role; they are an editorial reconstruction.

Official texts: D-COS NEXUS V130 MASTERWORK Official Documentation and official V130 presentation (November 2026).

This module is part of the integrated ecosystem

Every module is already included in the single D-COS NEXUS executable: you can activate it on its own or with the FULL SUITE, and the licence key unlocks it instantly.