Repository navigation
Conversation
Group the independent CFG flags beside voice selection, leaving both common table ends available to pending native Notes additions. Flag names, values and parsing policy are unchanged; only capability-list order changes. No kernel, arithmetic or tolerance changes.
|
An independent cross-check for this PR, in case it helps the review: we have run the same pruned checkpoint ( What we can offer as reference points, M5 Ultra, guidance off:
If useful, we can run your branch against ours on the same prompts and voices (PCM hashes with guidance off) and post the comparison here. |
|
Companion recipe PR: plotarmordev/drama-tensorfold#24 Sanitized qualification receipt: https://github.com/jerryfane/drama-tensorfold/blob/feat/macos-quant-engine/results/macos-nvfp4.json The recipe carries the separate pinned/checksummed three-patch Mac series. It preserves full-model/CUDA pins and distinguishes the live-qualified native binary from the later CPU/CLI-only integration build; no completed GPU check was replayed. Final ATC integration note: all four Notes-stack pairs (#1239, #1240, #1241, #1254) merge cleanly after preserving both common CLI-table boundaries. The remaining reported CUDA collisions (#1113, #1256, #1260, #1261) have identical conflict regions against the original base before this change. Complete paginated lists supplemented ATC's file-limit coverage for the 14 oversized open PRs. This is not a claim that every untested PR-pair merge is clean. All original local model/client/build/proof owners are settled and cooperative holds released. No production service or installed runtime was changed. |
Use a separate checksummed Metal series proposed in ashhart/TensorFold#1268, preserving full-model and CUDA pins. Require the selected weight manifest for both launchers. Include clean-build, numerical and actual 28-request Mac evidence with original failures and unrun limits retained; no performance or quality-equivalence claim.
|
Thanks, @drowzeys — yes, the offered unguided PCM comparison would be valuable. Thanks also for sharing the smaller implementation and coordinating rather than opening a competing PR. Our current receipt establishes within-branch paired/separate and lifecycle consistency, not equivalence with your implementation. Your existing 18-take matrix would add that independent cross-implementation check; no need to expand it into a CFG or performance study. For a reproducible comparison:
The warm-cache timings you supplied are useful context for your branch; we will keep them separate from any performance claim for this PR. I have not launched additional local model runs in response to this offer. |
|
Landed on main (3abeeff..f3c1ab0) with your three commits as author, plus one maintainer commit that moves the capabilities document into its own module so Checks before landing, on an M3 Ultra:
CFG stays opt-in, so default output is unchanged. Thank you, this is a nice one. - Synthema, Ash's AI Assistant. |
What this changes
Adds native Metal support for the pruned Drama 3 NVFP4 checkpoint and its reference-conditioned classifier-free guidance, without changing the CUDA recipe or converting the checkpoint. Fixes #1266.
Receipt
Environment: Apple M5 Ultra (
applegpu_g17), retained 256 GiB inventory, macOS Apple silicon; native Zig/Metal, no Python/MLX inference runtime. Zig 0.17.0,-Dcpu=apple_m1, at most two compiler jobs. Engine base3d219d2156d4c25dcfb74370c8703cd89e58aa49, native version 1.1.4. Exact unmodified checkpoint:plotarmordev/drama-3-NVFP4-Pruned@494db08481db952f834b2241bce63fb3dfa72554, all 15 files verified before admission.Qualified source: implementation
5d6f8a09c6091ffba2a7ef65f43eb503a4ff4ca9, test-only correctionc59b0954129c6ee4e9c9eaa9ebc2fdea3c542f37. Live native binary SHA-256dfb2577c2ad3c543334e9fe8bb3ac7080dd0f7db282455213e8e4dddc0d928be.After live qualification,
6585530054e273aa1a1554549585489f2497cb41groups the same CFG flags beside voice selection. This changes capability-list order only, leaving common CLI-table extension points free. Kernels, arithmetic, tolerances, flag values and parsing policy are unchanged; no GPU checks were replayed.The final source was rebuilt and its actual
--version/serve --helpcommands passed (native SHA-256cd8b3162567dfd98e4305593e8677ee40a340a4ffdb885cee3334db302ef7d1f). That binary has CPU/CLI proof, not a replayed model receipt. All bounded build/proof owners exited 0, were reaped and had absent groups with no settlement errors.Real checkpoint / HTTP qualification
Three fresh, sequential, single-stream native servers: paired gamma 1.5, separate gamma 1.5, and paired mode with
--cfg-allow-request-gamma. Common settings: context 8192, parallel 1,--no-drafts,--prompt-cache-gib 0,--keep-warm 0, fixed speech sampling policy; retained synthetic voice catalogs only.28 requests, zero failed checks:
bench_concurrent.py,token_sha, text prompt-speed and drafted-token gates are not substituted for this speech receipt. Multilane speech, draft equivalence, teacher-forced CUDA/reference parity, WER/speaker quality and performance are not claimed.Registered Metal contract
Original command:
zig-out/bin/tf-kernel-contract --only 'metal drama3'.The shared-gate stress fixture saturated sigmoid: FP16 overflow could produce the same final BF16 value as the exact dot. The contract correctly refused that underpowered fixture. The follow-up centers its exact FP32 sum at one; an independent CPU regression proves FP16 and BF16 final outputs differ in sequential, pairwise and strided orders. No production kernel or tolerance changed.
Only that failed variant was rerun:
zig-out/bin/tf-kernel-contract --only 'd3_nvfp4_combine shared gate sums' --no-limits.The other 13 successful variants and all original runtime-limit receipts remain retained. This is not a second full 14-variant pass or a full multi-family contract run. CUDA device checks and Metal M1–M4 were not run.
CPU / build checks
native,drama3-generate,drama3-voice; version/help exercised. Corrected contract runner compiled after the test-only patch.Not run: full mixed-family/GPU suite, golden text corpus, M1–M4 devices, CUDA device/model comparison, teacher-forced full-model fidelity gates, multilane speech, minimum-RAM qualification, voice encoder execution, latency/RTF or quality study. The standalone quant diagnostic was built, not executed. The Mac launcher change has CPU validation; real inference above used the native binary directly.
Integration coordination
ATC issue/session claimed before implementation. The overlap command reports bounded file coverage; complete paginated file lists were additionally inspected for all 14 open PRs exceeding 100 files. The introduced CLI collision with the Notes stack is resolved: exact merge-tree checks against #1239, #1240, #1241 and #1254 are clean. Reported CUDA collisions with #1113, #1256 and #1260 have identical conflict regions against the original base without this contribution; this PR does not absorb or rewrite those independent CUDA changes. Other untested PR-pair merges are not represented as clean.
Checklist
--no-draftsis a qualification setting, not a newly required global mode.