Cubase-MCP-GAJ3T.MusicGen.R.../docs/compatibility.md

20 KiB
Raw Permalink Blame History

Compatibility and evidence inventory

Inventory updated for release 0.2.0, Step 16 software acceptance on 2026-10-20. Target subset defaults generate real native Riffer/SD3 and mapped MIDI outputs. AME 4.0.1 / AMR 4.1.0 ProductVersions, XML 2.1 structure and limited mappings are verified; real .griff/.briff writers independently read saved originals. The AME-only PH extension and exact beat-range/triplet/hold grammar, visible text-only recovery and Em shorthand were added in Steps 11/12 and released in 0.1.1. This does not retroactively change earlier report evidence. Release 0.2.0 includes Step14/15 reusable exact voicings and public hybrid Counts/Events/Notes/Chords parsing, with visible rational interpretation. The corrected F#2/D3/Bb2 example passes real source and installed-wheel native tests; explicit D2 remains exact-MIDI fallback, never hidden transposition. The original E2 phrase remains byte-identical. These are software acceptance results, not application playback certification; see the release report and historical Step15 correction report. Slides (/ and backslash Events) are reserved, not implemented. Exact pitches are never key-retuned; explicit raw voicings can be physically unplayable and then require honest exact-MIDI fallback or an error with fallback disabled. Six production profiles exist; three standard maps remain explicit fallbacks. SD3 3.4.4 has a real template song writer/parser/validator and SL-DFH core three-voice profile. Native service integration is verified, including actual stdio and installed-wheel generation. All application acceptance remains unrun. Missing optional SD3 template permits drum-only fallback while preserving real lead/bass natives. Explicit template errors never become fallback.

Software acceptance covers the real service, stdio generation, actual saved MIDI/read-back and Windows no-overwrite publication (including real junction checks), plus the built-wheel server outside the checkout. The Riffer fix adds real native saved-file evidence but does not close application acceptance. Publication on non-Windows is explicitly unsupported until a no-replace primitive is supplied.

Tested software configuration (CURRENT release 0.2.0)

Current full-suite/package/static results, exact persisted distribution hashes, and retained original native read-back paths are in the Step 16 report. The unchanged Step 10 native report is historical baseline evidence, not acceptance of the later precise phrase or text-only recovery.

Only this configuration was executed, not every version permitted by metadata:

Component Actual tested version / outcome
OS / architecture Windows 11, build 10.0.26200, AMD64
Python CPython 3.13.13, MSC v.1944 64 bit; declared minimum 3.11 is not a test of 3.11/3.12/other runtimes
Runtime mcp 1.30.0; pydantic 2.14.1; mido 1.3.3
Tests / contracts pytest 9.1.1; anyio 4.15.1; MIDIUtil 1.2.1; jsonschema 4.26.0; types-jsonschema 4.26.0.20261006
Static checks Ruff 0.17.1 lint/format; mypy 2.4.0 strict
Build / install build 1.6.1; setuptools 84.2.0; wheel 0.48.0; packaging 26.3; pip 26.0.1
Package / MCP version 0.2.0, from one authoritative source; editable metadata refreshed offline without reinstalling dependencies
Complete automated suite Final counts in report_16.md; includes original E2 hybrid, canonical D3 and honest D2 fallback, slash/explicit voicings, exact phrase, text-only recovery, native/MIDI/CC and atomic/privacy checks; no application evidence is represented as a skip
Installed-wheel acceptance PASS: exact persisted final wheel installed offline/noneditably; isolated package/submodule/metadata and six resource paths, real stdio native/default/alias/actual-name/MIDI/CC generation with disk read-back outside checkout; existing dev-venv dependencies reused, not a fresh dependency certification
Final distributions Real 0.2.0 sdist and wheel (wheel built from sdist), under dist\hybrid-0.2.0-20261020; exact paths/hashes and final acceptance in report_16.md
Lint / format / strict types / dependency metadata PASS: Ruff lint/format, strict mypy, pip check
Applications / receivers UNRUN: Cubase MIDI import; Eclipse/Ray5/SD3 routing, native load/save/close/reload; installed AME/AMR versions are now verified, host/configuration acceptance remains unrun

Reproduce with the validation commands. The built-wheel workflow extends tests/integration/test_distribution.py; all six packaged JSON resources and all 18 package/submodule entry locations are asserted under the wheel target. The server's cwd is the checkout's existing parent, not the repository, and -I -B plus explicit install-target precedence prevents accidental editable imports. Normal tests use no network. Current exact commands, cleanup and separate results are in report_16.md. pip check certifies installed dependency metadata consistency, not all behavior of every transitive package. After this update restart the MCP, then start a fresh LM Studio chat to refresh schemas. The configured venv now resolves 0.2.0 without config edit/reinstall; the exact copy-ready original prompt is in README. Live model/playback is unrun.

Separate evidence gates

Target / product and version MIDI mappings Native layouts Automated checks Application import acceptance
Standard MIDI pitched lead/bass and GM Level 1 percussion; mapping policy standard-fallback-1 Production standard.lead.v1, standard.bass.v1, standard.gm-drums.v1; public mapping_kind=standard_midi, NOT vendor maps; explicit zero-based channels 0/1/9 No native availability; real .mid generation via service/MCP Strict profiles, independent numeric GM assertions, exact compiled events, real MIDI read-back, service/stdio publication, installed/ZIP wheel resources and actual built-wheel server generation outside checkout UNRUN in a receiver/plugin/Cubase; sound configuration external
Lead: Ample Metal Eclipse 4.0.1 (local VST3 ProductVersion) Default normal/palm-mute/PH subset; C0=24/D0=26/G0=31; normal 64–126, documented PM depth and PH range36–84; tuning/range and generator policy distinguished Real .griff, Riffer XML 2.1 / PPQ 480; agp request alias only; actual PM/PH labels and cross-bar PH hold Actual service/stdio/installed-wheel original XML and independent saved-file note/CC/timing validation, including exact nine-note phrase; strict profiles/contracts and corruption/physical-string/timing rejection UNRUN in plugin/Cubase; native software success is not application certification
Bass: Ample Metal Ray5 4.1.0 (local VST3 ProductVersion) Default normal/palm-mute subset; C0=24, sustain 64–126, PM 32–63 and native PMP; no accent/dead-note leakage Real .briff, Riffer XML 2.1 / PPQ 480; agp request alias only Actual service/stdio/installed-wheel native output; independent note/CC/timing/velocity/technique validation and partial-fallback regression UNRUN in plugin/Cubase; native software success is not application certification
Drums: Superior Drummer 3 standalone 3.4.4, local SL-DFH pad/alias evidence Default verified subset: kickR/36, snareR/38, hatsTP/42 only; channel/intensity policy separate; no full GM-map claim Real .sd3p template-based song replacement and bounded parser; sdp request alias only; operator-local matching template required Actual service/stdio/installed-wheel output, original minimal and genuine read-only local-template checks, exact note/tempo/meter/channel/velocity, full source-song replacement, byte-identical non-song state; malformed/version/IO/fault rejection UNRUN in SD3/Cubase; preserved host sync/mute/routing settings and acoustic behavior remain operator/application concerns
Cubase15 user project previously observed (PID 41836); exact edition/build and routing unconfirmed Imported tempo/meter, part alignment, routing and control preservation unverified No .cpr writer is in scope; plugin-native imports are separate operations Original generated SMF/native saved-byte checks only; no DAW tests UNRUN: no project manipulation, global input or competing audio host/driver

Native-file readability, correct mapping, automated structure checks, and actual application acceptance are distinct. No column can be inferred from another. Renaming a .mid to .agp or .sdp is not support. A file that stores only presets/settings might not carry the requested notes, rhythm, or song content.

Remaining application evidence to obtain

The executable codecs, local layout/map facts and original controlled fixtures are established. The following checklist concerns broader receiver/application certification and expansion beyond current verified subsets, not a current native implementation blocker.

  1. Record receiver configuration, SD3 installed library/preset/active MIDI map, Cubase version and routing. AME/AMR product identities/versions are now known.
  2. Record the exact application's native export/import menu actions, extension and file category. Establish whether notes/patterns/song tracks are actually stored, embedded, or merely referenced.
  3. Obtain lawful empty, one-note/hit, multi-note/hit exports, plus controlled single-variable changes to tempo, timing, velocity and articulation. See separate AGP and SDP checklists.
  4. Obtain authoritative mapping evidence for MIDI numbers (not ambiguous octave labels), channels, ranges, switches/CC timing/reset/latch rules and layers.
  5. Record real native load/save/reload acceptance and MIDI import in Cubase: notes, tempo/meter, aligned duration, dynamics, articulation and routing.
  6. Record evidence ID, product/version, workflow, source/date, observed facts, unknowns, expected/observed results, and redistribution permission. Keep private absolute paths and licensed content out of distributed metadata.

Do not upload private files, credentials, or code. Do not bypass authentication or copy licensed manuals. Check in native fixtures only with explicit redistribution rights. Otherwise keep files local in an operator-owned location, document local-only fixture IDs and an opt-in test procedure, and report missing private/application tests as unrun, not passed. New checked-in native fixtures contain exclusively original generated content, not factory or private exports. SD3's local-template generated evidence retains private kit state and stays ignored outside source/tests. See SD3 evidence/results.

Historical public checks through Step 10

The following records earlier discovery, superseded where the current native implementation above supplies local facts. It is not a current absent-evidence blocker for Riffer.

Checked 2026-10-19, using unauthenticated public pages only:

Source Observation What it establishes
Official Python MCP SDK, maintained v1.x metadata and test configuration SDK uses AnyIO; tests select its asyncio backend; Python floor allows 3.11 Dependency/test choice, not this project's transport or instrument support
AnyIO testing documentation pytest plugin ships with AnyIO; backend selection is explicit No separate pytest-asyncio plugin required
Ample public manual entry point Initial simplified text extraction missed links; raw official HTML exposes public main-panel, Riffer, Strummer and settings PDFs listed below Documentation is publicly accessible; exact installed mappings, octave labels and .agp native layout are not verified by link discovery
Toontrack SD3 manual entry point Page says to log in to view manuals; no login attempted No .sdp layout or song-content claim verified
MIDI Association GM Level 1 overview Describes the GM Level 1 standard and named sound portability, without defining acoustic timbre Standard identity only, not an SD3 preset/map
MIDI Association message summary Seven-bit note/velocity data and channel numbers 0–15 Legal MIDI values, not plugin playable ranges
Computer Music Resource / Vanderbilt Blair School of Music numerical table Explicit GM channel 10 and all 47 note-to-sound pairs 35–81, checked independently of the overview GM percussion numbers, not SD3 default-map or application acceptance

Package versions and Requires-Python were checked against public PyPI JSON metadata and resolved in .venv. Those checks are dependency evidence, not proprietary format documentation. The plan's references retain earlier MCP/Mido/MIDIUtil documentation; no earlier planning assertion is promoted into an application compatibility result.

Historical readiness before executable native fixes (superseded)

This section records the old unavailable-boundary state only. Current codecs and native service are implemented; see the matrix and report_9_fix above.

Foundation checks and their exact outcomes belong to report_1.md. Step 2 typed models are not blocked by unknown native layouts. Step 6 standard-only composition is implemented under the amended continuation decision. Step 7 implements the honest AGP capability boundary, not a native writer. Step 8 implements the corresponding SDP boundary; both are reused by Step 9's operational standard-MIDI service/fallback path. Step 10 independently verifies installed software/package behavior without claiming native acceptance. Verified instrument profiles and native writers remain gated. If a requested container cannot hold the requested musical data, record that contradiction and obtain a scope decision; do not substitute formats. The unresolved AGP fix handoff and SDP fix handoff stay BLOCKED: no actual native schema/codec, lawful controlled fixture corpus, version/content proof or real application round trip was supplied. No full native-project completion is claimed.

Corrected Ample documentation discovery

On 2026-10-19 the raw official manual-page HTML was checked directly and exposes:

The prior conclusion that the page contained only a domain label was an extraction error, not evidence that manuals were unavailable. These public links identify documentation candidates; this standard-only fix does not certify their numeric mappings against installed products. Octave labels must be resolved to MIDI numbers; installed versions, selected presets/maps, control semantics and native content/layout still require verification. No manual or factory MIDI song was downloaded into the repository or copied. Toontrack authentication was not bypassed. No private data was uploaded.

Historical standard-only registry (now explicit fallback resources)

The three resources below remain available by explicit ID. The current manifest also includes three target subset defaults; installed and ZIP-resource tests verify all six and distinguish target defaults from standard selections.

The explicit manifest lists standard-midi-lead-v1.json, standard-midi-bass-v1.json, and general-midi-percussion-v1.json. Standard provenance separates public facts (standard_public) from routing, normal/sustain-only behavior and linear velocity policy (generator_policy). See policy, source IDs and exact values. standard_midi is not verified instrument provenance. Reviewed instrument values are routing intent only. Public labels/limitations remain in profile listing and per-part STANDARD_MIDI_MAPPING warnings in Step 9 results.

Installed-wheel and ZIP-resource probes outside the checkout verify exactly these three production profiles, normal selection and absence of synthetic/ verified-vendor profiles. Synthetic maps remain in tests\fixtures\profiles, excluded from discovery. No test attestation or synthetic number is promoted.

The profile/compiler mechanics implement versioned validation, layer/action/state scheduling, common pre-roll and tails, and actual synthetic and standard three-part MIDI read-back. They do not verify Eclips/Ray/ SD3 behavior. Exact evidence needed is listed above and in report_5.md, with the continuation clarified in report_5_fix.md. Composition is standard fallback only. Vendor maps, native evidence and actual plugin/Cubase load/save acceptance are separately unresolved/unrun, not passed.

Historical Step 7 AGP boundary (superseded by executable fixes)

The following unavailable-boundary record is historical, not current codec status. The current matrix above and reports 7_fix/8_fix supersede it.

check_agp_capability returns a typed immutable unavailable result for valid lead/bass profiles. require_agp_capability raises NATIVE_FORMAT_UNAVAILABLE with format=agp, requested part, and fixed reason=agp_layout_not_established before output IO. Invalid requests, wrong-part selection and corrupt/mutated profiles remain distinct named failures. Metadata alone never enables a native codec. Standard .mid composition/writing remains independently usable, not native serialization.

The AGP evidence/API record records the supplied official main-panel/Riffer evidence and prior public-demo archive metadata inspection: range/articulation labels and MIDI/preset UI are not a native schema; the archive yielded no AGP fixture, not proof that the format does not exist. Those prior observations were not independently re-downloaded in Step 7. No licensed content/native fixtures were copied. Actual layout, lawful controlled fixtures, separate product/version encoding and real Eclips/Ray load/save/reload remain missing. Software capability tests may pass while native acceptance remains BLOCKED and application/round-trip tests UNRUN.

Historical Step 8 SDP boundary (superseded by executable Step 8 fix)

The following unavailable-boundary record is historical. Native SD3 parsing, song writing and saved-file validation are now implemented; only service and application acceptance remains open; native service integration is complete. See the current matrix and report_9_fix.

check_sdp_capability returns the shared immutable NativeCapability for valid drums profiles: part=drums, format=sdp, available=False, reason=sdp_layout_not_established. require_sdp_capability freshly checks and raises NATIVE_FORMAT_UNAVAILABLE with the same format/part/reason before any path is touched. Non-drums requests, valid wrong-part profiles and corrupted/ mutated/unchecked invalid models fail explicitly, not as native fallback.

The SDP evidence/API record distinguishes this passing software boundary from the still-blocked native writer. Prior official manual access required login; no new specification or genuine native fixture was obtained, no authentication bypass or licensed-content copy occurred. Content category, layout, supported versions, selected library/map semantics and actual generated drum events must still be established from lawful controlled exports and real SD3 import/save/close/reload. Preset-only settings do not meet drum-song scope.

Production General MIDI percussion remains explicitly NOT an SD3 map/native capability. Separate real drums-only/combined .mid tests validate the current standard pipeline, contain no SDP artifact and do not certify SD3 or Cubase. SDP serialization/native acceptance: BLOCKED; native round trips and actual SD3/Cubase acceptance: UNRUN. Step 9 implements the independent standard-MIDI service/fallback path under the amended continuation decision; its operational wiring and publication do not satisfy the SDP serialization/application gates.