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

26 KiB
Raw Blame History

Format compatibility and evidence inventory

Inventory updated: 2026-10-20. Baseline: Step 1; current infrastructure: Step 9 supported-slice win-x64 publication and Step 8 MCP MIDI/fallback slice plus Step 4 correction iteration 4 capabilities and Step 5 MIDI.

This is the historical compatibility baseline. Step 2 has since implemented and tested stdio MCP transport/lifecycle; see the current protocol contract. The two production tools do not change any native format or installed/application verification status below.

Step 3 added validated instrument-neutral composition planning. Step 4 now adds generic profile validation, an embedded mapping catalog and typed keyswitch/velocity/CC event-intention planning, verified with synthetic test-only profiles. See the mapping contract. The production mapping catalog now contains five Documented profiles: AGLP/AGM/AGT/AME Lead Sustain/PM and ABJ Bass Sustain only, anchored by official manuals and vendor demo MIDI. See the current source review for exact URLs, sections, revision hashes, numeric facts and remaining gaps. Documented-default subset readiness is separate from full Step 4/application readiness, which remains false / BLOCKED. Step 5 now adds the actual in-process Standard MIDI builder/writer with DryWetMIDI 8.0.3 file write/read-back tests using synthetic mappings and all five admitted documented default profiles. Step 8 exposes profile discovery and actual MIDI generation/fallback through MCP. No native writers or actual application imports exist. MIDI format and RPC-to-file behavior are verified, not installed plugin acceptance. The historical tables below retain their original evidence scope; “future gate” does not mean the generic infrastructure itself is absent.

Supported-slice publication evidence (Step 9)

The local deployment guide records the actual Release win-x64 self-contained, single-file, untrimmed/non-AOT payload, commands and copyable stdio client configuration. Twenty-eight focused checks launch isolated copies of the published payload from an unrelated cwd, discover exactly two tools/seven identities/five Documented profiles and generate/reopen actual MIDI. They cover all four Lead profiles and real combined Lead+Bass, native/default fallback, disabled fallback, unavailable selected roles, collisions, errors, protocol-only stdout, ping, cancellation and active/empty EOF with owned cleanup.

An executable-only copy also generated MIDI without source DLL/catalogs or optional symbol/macOS sidecars. Host tracing identifies self-contained/internal hostpolicy; the two extracted DLLs match the pinned DryWetMIDI 8.0.3 Windows native assets. The guide records extraction/cache requirements; no device/ playback API was used. The locally retained, actual published-RPC-generated artifacts\examples\ame-lead-example.mid is a 371-byte type-1/960-PPQ AME Lead example with 32 musical notes, switch26 on0/off30, lead-in120/end15480, verified using DryWetMIDI. It is not a copied vendor fixture or application acceptance.

This verifies supported-slice packaging on an SDK-equipped Windows x64 host. Runtime-free Windows launch remains pending, as do all licensed Cubase/ Ample/SD3 import/audible checks, AMR/SD3 mappings, ABJ PM and native Steps 6/7. Full requested-product readiness remains false/blocked.

Current instrument metadata scope

Correction iteration 2 adds a separate embedded declarative instrument catalog:

ID Code Product Existing role
ample-abj ABJ Ample Bass J Bass
ample-aglp AGLP Ample Guitar LP Lead
ample-agm AGM Ample Guitar M Lead
ample-agt AGT Ample Guitar T Lead
ample-ame AME Ample Metal Eclipse Lead
ample-amr AMR Ample Metal Ray5 Bass
toontrack-sd3 SD3 Superior Drummer 3 Drums

The mapping contract records vendor/manual URLs, strict validation and the data-only admission steps. There are seven declared identities, five Documented profiles and zero application-Verified profiles. ABJ/AGLP/AGM/AGT/AME report profile_available; AMR and SD3 remain mapping_unavailable. profile_available means an admitted mapping, not native-format compatibility or installed/application acceptance. Definitions have no fabricated versions, switches or capabilities. Profiles bind required instrumentId plus matching role/product identity. Additional existing-mechanism instruments require JSON definitions and authorized profiles, followed by rebuild/publish, not engine subclasses or product switches. No runtime profile/VST discovery/loading is added. MCP discovery exposes this embedded catalog without scanning installations.

The folder screenshot is not version, path or map evidence. Each product's articulations/settings need independent verification; acoustic/electric guitars share the Lead slot without new patterns/roles. Missing mappings block full Step 4 production readiness, not this metadata/catalog extension.

No owner-created native fixture, exact installed-version confirmation, or native template permission record has been supplied in this repository. The owner's screenshots identify Ample Metal Eclipse and expose articulation labels and velocity behavior. Public vendor manuals have now been consulted; they are sources for documented defaults, not proof of installed custom settings. No vendor products were installed, personal directories searched, or licensed sample content copied. No proprietary schema is implemented. Only the five bounded documented-default capabilities are admitted; installed configurations remain unknown.

Documentation-backed mapping scope (correction iteration 4)

  • Documented is a distinct source-backed stage, not Verified application acceptance. Both stages are admissible; Unverified/Synthetic are rejected. Existing serialized profiles can omit optional compatibility notes, but Documented profiles require nonempty validated immutable version scope, configuration requirements, routing policy and timing policy. Source/mapping revision is explicitly separate from unknown installed product version.
  • AGLP: Sustain 24, PM 26, range 40-86; Sustain musical velocities 1-126. AME: Sustain 24, PM 26, range 36-84; Sustain 64-126. AGM/AGT: Sustain 24, PM 26, range 40-84, Sustain 1-126. All guitar PM preserves 1-127. ABJ: Sustain only, switch 24/range 35-76/velocities 1-125. AGM uses direct demo switches; AGT's official named A6 tab-play control plus note 105 in the explicitly AGT/AGM-shared tab demo supplies its numeric anchor, not a direct Sustain/PM performance. ABJ uses the explicitly vendor-listed ABJ/ABP shared demo; its track is named ABP, not a separate ABJ performance. No anchor is based on assumed C0 octave naming.
  • Default tuning/mapping/thresholds, instrument mode, MIDI Guitar mode off, idle isolated receiver, Lead channel 0 and ABJ Bass channel 1 routing are explicit requirements. Initial articulation is unknown; first requested state is selected alone. Switch velocity 100 occurs in vendor examples; advance 120/pulse 30 ticks at 960 PPQ is our deterministic policy, not a vendor timing guarantee. Pairing/order/transitions/boundaries are verified through actual MIDI file write/read-back; no real plugin, VST host, audible articulation or Cubase import test was run. Native-format readiness is unaffected.
  • ABJ's missing dedicated PM/Dead Note threshold blocks PM, NOT its supported Sustain-only profile. PM requests explicitly fail without a file or silent Sustain replacement. AMR still lacks its own absolute anchor; ABJ/ABP applicability is not extended to AMR. SD3's manual requires login through both fetch/rendered retrieval; the accessible Hansa - Marble Room example shows 36/38/42 but is not evidence of a universal/core default library map or its velocity/hi-hat control scope. AMR and SD3 stay unavailable. The source review records exact facts/limits.

Status meanings: VERIFIED (planning/toolchain) means the cited public documentation or local inspection supports only that statement. MISSING means evidence was not supplied. NOT PERFORMED means no actual application/deployment check was carried out. Neither missing evidence nor successful compilation is proof of native compatibility.

Step numbers below refer to prompts\plan.md: 2 protocol; 4 production profiles/articulations; 5 generic MIDI (accepted infrastructure plus synthetic format tests, not completed production mapping admission); 6 Ample native writer; 7 SD3 native writer; 9 deployment/application acceptance. Outstanding production gates are not Step 1 scaffold failures.

Standard MIDI format evidence (Step 5)

Actual generated .mid files are reopened with the pinned library and checked for type 1, 960 PPQ, tick-zero tempo/meter, conductor plus selected named role tracks, exact channels/pitches/velocities/CCs/note-offs and stable order/pairing. The complete synthetic example has 175 channel events, 32/4/48 musical notes, two switch pairs, and four end markers at tick 15600 (15360 plus shared 240). Additional file tests cover role subsets, 3/8, 1,000 repeated 7/8 bars, rests, momentary releases and final reset tails, unrelated cwd and safe no-overwrite.

Local XML/reflection plus serialization/read-back establish these pinned facts:

  • TimeSignatureEvent(byte, byte) takes the denominator itself; /128 round-trips. The byte API cannot represent Core-valid /256: the writer fails explicitly.
  • Tempo is integer microseconds/quarter, nearest-integer with midpoint away from zero (120 -> 500000; 123 -> 487805; 512 -> 117188). Core's unrounded range 1..16777215 remains unchanged.
  • Library event deltas are Int64 and serialization itself accepts >0x0FFFFFFF. The builder instead checks four-byte SMF VLQs and rejects larger gaps, including the conductor's global end gap, without filler events.
  • End-of-Track has no public constructor; the library writes it automatically. The builder retains one from a library-generated empty-track read using EndOfTrackStoringPolicy.Store, inserts events before it and sets its delta. Tests confirm exactly one end marker per track at the full planned end.

See the MIDI API guide for stream ownership, single-file staging, cleanup and cancellation boundaries. The multi-track arrangement is not a Riffer single-track export or AGP/SDP serialization. Format-writer readiness does not close any production/native/ Cubase gate below; AMR/SD3 remain unavailable and all five admitted Documented mappings still lack installed/application acceptance.

MCP generation/fallback evidence (Step 8)

Production advertises exactly list_instrument_profiles and generate_project. Real subprocess tests initialize/discover/call the tools from an unrelated cwd, select explicit AGLP/AGM/AGT/AME and ABJ Documented profiles, obtain actual MIDI paths/byte counts, and reopen files with DryWetMIDI. The default four-bar PM eighth-note Lead case is type 1/960 PPQ with Conductor/Lead, 120 BPM/4-4 metadata, 32 pitch-64 velocity-96 notes, one PM26/100 switch pair at ticks 0/30, shared lead-in 120 and end 15480. Every target and source-only compatibility warning survives the RPC wrapper. Lead+Bass cases add Bass channel 1, four pitch-40 velocity-96 sustained notes, Sustain24/100 on0/off30 and a third track/end marker; Lead stays on channel 0 with the same shared 120-tick lead-in and 15480 end. Complete and native-fallback cases retain both roles in exactly one artifact. ABJ PM is explicitly rejected.

AGP-only, AGP+MIDI and omitted Lead formats produce one real combined .mid with status:"fallback", not a native placeholder; MIDI-only is complete, including fallback disabled. Native requests with fallback disabled fail before output. Missing explicit Bass selection (no_default_profile), unmapped Drums (mapping_unavailable), unsupported ABJ PM, wrong/unselected profiles, inapplicable formats, unsupported text/MIDI limits, unsafe paths, collisions, I/O and cancellation do not become successful fallback. Synchronous work is off the reader; ping/cancellation responsiveness is tested with deterministic blocking. Read-back validates file semantics only. No application acceptance, native codec, new mapping, native extension substitution, publishing or deployment readiness is established by Step 8.

Public planning facts versus native compatibility

Item Status Evidence/source Required evidence or limitation Future gate
MCP stdio framing VERIFIED (planning) MCP 2025-11-25 transport specification, rechecked during Step 1: UTF-8 JSON-RPC, newline-delimited (not LSP Content-Length framing), no non-protocol stdout Implement and test framing/lifecycle later; the scaffold only discards stdin and emits nothing Step 2
DryWetMIDI package availability VERIFIED (package metadata) Official 8.0.3 package page, version index and 8.0.3 manifest; manifest includes .NET Standard 2.0 Exact central dependency is 8.0.3; a restore/build/smoke check does not verify proprietary formats or application import Steps 5–7 use only verified capabilities
Stable test dependency availability VERIFIED (package metadata) Official NuGet indexes and manifests: xunit 2.9.3, xunit.runner.visualstudio 4.0.1, Microsoft.NET.Test.Sdk 18.11.0; adapter/test SDK include net8.0 groups compatible with net10.0 Resolve and execute actual tests; versions pinned centrally, no independent coverage package Step 1 validation, not a native gate
Installed .NET toolchain VERIFIED (local inspection) C:\Program Files\dotnet\dotnet.exe --list-sdks / --info: SDK 10.0.400, runtime 10.0.11, win-x64 global.json pins SDK with patch roll-forward; this is development-machine evidence only Step 1 validation
Self-contained, single-file deployment capability VERIFIED (supported-slice packaging on SDK host) Actual win-x64 profile/payload, isolated and executable-only RPC generation, read-back and extraction/host-trace tests; deployment guide Matching runtime-free host still pending; no application/native acceptance implied Step 9 full-scope gate remains open
AGP/SDP support inferred from MIDI library or .NET NOT ESTABLISHED No such evidence supplied; Standard MIDI and deployment docs are not proprietary format specifications Independent authorized native evidence and real product acceptance are mandatory Steps 6, 7, 9

Exact product identity and environment

The names above are requested targets, not verified installed identities. ABJ, AGLP, AGM and AGT installed versions/settings and mappings are also unresolved; the historical Eclipse/Ray rows below do not narrow the expanded requested scope.

Item Status Evidence/source Required evidence Future gate blocked
Lead: owner's exact Ample “Eclips” product name, edition, version/build PARTIAL; product identified as Ample Metal Eclipse, version/build unknown Owner-provided plugin screenshots, 2026-10-20; official Eclipse manual Installed version/settings, including host/plugin format if relevant Steps 4, 6, 9
Bass: owner's exact Ample “Ray” product name, edition, version/build MISSING; unknown Not supplied Same identity/version evidence for the bass product independently Steps 4, 6, 9
Superior Drummer 3 exact version/build MISSING; unknown Not supplied Exact installed version, relevant plugin settings and chosen content library Steps 4, 7, 9
Cubase exact product/edition/version/build MISSING; unknown Not supplied Acceptance host version, project/import settings and instrument routing Step 9
SD3 installed library, MIDI map/preset and mapping overrides MISSING; unknown Not supplied; do not assume GM mapping Exact library/version, selected map, custom overrides and reproducible settings Steps 4, 5, 7, 9

Native containers, supported workflows and rights

No native format is assumed to be MIDI, XML, JSON, ZIP, or any other container. An extension is a requested output name, not proof of product support.

Item Status Evidence/source Required evidence Future gate blocked
Lead AGP container/schema/version metadata MISSING; unknown Not supplied; Ample manual entry point did not yield a usable format schema during planning Lawfully usable specification or owner-created one-variable fixtures identifying container, musical fields, metadata and version behavior Step 6 (lead)
Bass AGP container/schema/version metadata MISSING; unknown Not supplied Independent bass fixtures/specification; establish whether lead/bass actually share a codec rather than assuming Step 6 (bass)
Lead supported import/load path and extension MISSING; .agp requested, support unverified Not supplied Exact product/version workflow and confirmation whether .agp represents a riff, preset, project or other entity Steps 6, 9
Bass supported import/load path and extension MISSING; .agp requested, support unverified Not supplied Equivalent independent bass workflow/extension confirmation Steps 6, 9
SD3 SDP container/schema/version metadata MISSING; unknown Not supplied; SD3 manual entry point required login during planning Authorized versioned schema or minimal owner-created fixtures with musical-data semantics Step 7
Whether SD3 supports the requested .sdp extension and musical content MISSING; unknown, not asserted Not supplied Actual supported extension/entity type and documented load/import steps for the installed version Steps 7, 9; mismatch requires owner decision, not silent substitution
Authorized lead/bass/SD3 fixture availability and provenance MISSING; none supplied No fixture files in the initial repository Minimal empty/one-note files, separate changes to pitch, duration, velocity, tempo and each articulation/control; record creating product/version and ownership Steps 4, 6, 7
Fixture redistribution and template reuse permissions MISSING; unknown, no permission assumed Not supplied Explicit authorization/license scope for analysis, test redistribution and any generated/template-derived output; exclude sample/audio libraries and unrelated projects Steps 6, 7; no template-based route without rights
Native fields express required timing, notes and articulation mechanisms MISSING; unknown Not supplied Evidence-backed capability/limitation table from controlled fixtures and reopening tests; use DryWetMIDI for any actual embedded MIDI payload Steps 6, 7, 9

Absolute articulation and MIDI mapping evidence

All six Ample main-panel manuals and Settings/CPC were read. Vendor demo MIDI now anchors the admitted AGLP/AME/AGM/AGT/ABJ numeric maps. AMR's anchor and the selected SD3 default mapping remain unresolved. The following historical inventory records the broader requested-product gate; the current subset and explicit policies are described above. There are no synthetic production maps, guessed octave conversions or claims of application-tested timing.

Item Status Evidence/source Required evidence Future gate blocked
Absolute playable MIDI notes, lead/bass ranges and SD3 voices PARTIAL; Ample range labels documented, numeric anchor and SD3 voices unresolved Official Eclipse/Ray5 manuals, section 2.2.1 Exact numeric notes/ranges per product/library/map, including control/playable collisions and the octave-label convention Steps 4, 5, 6, 7
Keyswitch notes, switch velocity and mechanisms PARTIAL; Ample Sustain C0 and Palm Mute D0 documented; numeric values/complete semantics unresolved Official manuals, sections 2.2.1-2.2.4; owner Eclipse tooltips Absolute switch numbers, switch velocities and remaining semantics; consult documentation before requesting local checks Steps 4, 5, 6, 7
CC numbers, values and combinations (including hi-hat state) MISSING; unknown Not supplied Verified controller numbers/ranges and combined keyswitch/CC behavior, not product-name inference Steps 4, 5, 6, 7
Velocity layers, legal ranges and transitions PARTIAL; Ample Sustain layers documented, not all articulation thresholds Official Eclipse/Ray5 manuals and owner Eclipse Sustain tooltip; see mapping source review Remaining articulation boundaries, settings-dependent behavior and representability Steps 4, 5, 6, 7
Channels, routing and simultaneous-state constraints MISSING; unknown Not supplied Numeric channel allocations, plugin multi-channel behavior and conflict rules; planned conventions are not verified plugin mappings Steps 4, 5, 9
Initial state, persistence/latching, release and reset behavior MISSING; unknown Not supplied Initial state, momentary/latched controls, required releases/resets and supported simultaneous articulations Steps 4, 5, 6, 7
Control advance, switch duration and musical timing MISSING; unknown Not supplied Required lead-in/advance, event ordering, durations and native timing limitations from controlled tests Steps 4, 5, 6, 7
SD3 library/map-dependent articulations and velocity interpretation MISSING; unknown Not supplied Mapping/settings evidence for the actual installed SD3 content, including custom overrides and stateful controls Steps 4, 5, 7, 9

Actual acceptance checks

Native investigation update (2026-10-20)

Public discovery through the vendor material, web search and GitHub did not establish an authorized AGP or SDP serialization schema/fixture. Search absence does not prove a format unsupported. Riffer's documented single-track SMF import is not a native encoding specification.

The SD3 manual still requires login in the shared browser session. The vendor-hosted SD3P topic also requires login to read its body; public indexed snippets discuss SD3P project files. This raises an extension/entity question, not authority to substitute .sd3p for the requested .sdp, nor a codec for either.

Until actual native evidence is available, tool capabilities must report no AGP/SDP writer. Explicit fallback may produce a genuinely generated MIDI file with per-target warnings; disabled fallback must fail preflight without output. Never fabricate a container or change its filename extension to claim support.

Item Status Evidence/source Required evidence Future gate blocked
Generated lead AGP reopened in the owner's Eclips target NOT PERFORMED Not supplied; no writer or authorized fixtures Record exact version, input identifier, load procedure, pitches/timing/velocity/articulation results Steps 6, 9
Generated bass AGP reopened in the owner's Ray target NOT PERFORMED Not supplied; no writer or authorized fixtures Equivalent independent bass acceptance record Steps 6, 9
Generated SDP reopened in SD3 NOT PERFORMED Not supplied; extension semantics remain unknown Verified extension/workflow, library/map and drum timing/voice/velocity/articulation results Steps 7, 9
Standard MIDI imported and routed in Cubase NOT PERFORMED Step 5 verifies synthetic MIDI file read-back, not Cubase import Exact host/version, track separation, timing, tempo/meter and instrument/channel routing evidence Step 9
Intended articulations verified in actual plugins through Cubase NOT PERFORMED Not supplied Reproducible acceptance session/settings and observed articulation behavior Step 9
Published executable launched without a separately installed runtime NOT PERFORMED / pending Step 9 self-contained publish and unrelated-cwd isolated/executable-only RPC checks pass on SDK machine; bundle inspection/host trace are not a runtime-free host Matching runtime-free Windows x64 test environment still required Step 9

Gate decision

Missing proprietary evidence does not prevent accepting the Step 1 scaffold. It does prevent declaring native writers or actual plugin/Cubase compatibility verified. It does not prohibit honest Documented default profiles supported by sources and disclosed policies. Step 4 still needs the remaining target mappings; Steps 6 and 7 additionally need schemas/fixtures/rights and successful native imports. A native extension mismatch requires an owner decision. Do not fabricate files, relabel MIDI as native output, or treat MIDI fallback as native acceptance. Automated scaffold results belong in prompts\report_1.md and do not close any of these application-level gates.

Step 4's generic validator/planner/catalog and synthetic pipeline tests are automated infrastructure evidence only (see prompts\report_4.md). Production mapping catalog count is five Documented/zero Verified; identity catalog count is seven. Documented Ample facts above are PARTIAL requested-product evidence, not missing merely because no owner-run test was supplied. Complete exact-version profiles and native/application acceptance remain unresolved. Consult available official documentation first; request owner assistance only for remaining local settings, inaccessible documentation or real-application acceptance. Synthetic numbers, compilation and passing tests cannot close those gaps.