INKLINGUGC PERFORMANCE LAB

PUBLIC BUILD / 2026

05 / Comparison

Text comparison ready / listening pending

Base Inkling versus the trained adapter

The public question is simple—did the adapter make expressive direction better? The answer requires matched prompts, preserved words, and ears, not just two impressive-looking text boxes.

Two comparison modes and the listening test that still needs to happen.

01 / Two modes

One playful test and one clean diagnostic

A local comparison dashboard can load Base Inkling and the final trained adapter under the same generation settings. It supports two modes because the project is interested in both creative usefulness and the narrower behavior represented in training.

Mode 01 / Exploratory

Generate Ads

Enter a product, audience, verified facts, offer, duration, and creative direction. Both models write a complete ad. Differences may come from copywriting, structure, or expressive markup.

Mode 02 / Controlled

Compare Markup

Paste one approved script. Both models may add performance direction, but every spoken word must remain unchanged. This is the closer test of the supervised task.

Matched conditions

Model identity is the intended difference. Prompt, temperature, token limit, and renderer settings remain paired so a comparison is interpretable.

02 / Text stage

Inspect the extraction before listening

Each arm records the raw model response and the extracted performance-ready text. That separation catches a common failure: a model may write commentary around the requested script or return a field name different from the expected one.

CheckWhy it mattersFailure state
Response extractedThe dashboard found one usable script field without guessing.Preserve raw response and stop that arm.
Spoken words preservedControlled mode changes direction, not claims or copy.Mark the arm invalid for the diagnostic.
Expressive cues visibleReviewers can inspect density, specificity, and placement.Record an unmarked or malformed response honestly.
Both arms completeOnly paired outputs move to the same-voice renderer.Keep the successful arm; do not fabricate a pair.

Adding more tags is not automatically better. Useful direction should clarify an audible or intended performance without turning every phrase into competing stage instructions.

03 / Audio stage

Same voice. Blind A/B. One irreversible reveal.

Fish Audio S2-Pro is the planned downstream renderer. The same voice reference and synthesis settings will render both texts. The interface randomizes their identity as A and B, withholds the mapping, and asks for A, B, tie, or neither.

LockOne experiment

Freeze the prompt, scripts, configurations, and model identities.

RenderSame Fish voice

Only the expressive text changes between audio arms.

JudgeBlind A/B

Listen before knowing which model produced either script.

RevealAfter preference

Lock the decision, reveal identity once, and freeze the record.

Current state

Fish Audio has not yet been called for this comparison. No public page presents a synthetic listening winner.

04 / Verdict

What changed after fine-tuning? Not enough is established yet.

The available text outputs can suggest that the adapter uses different or richer performance language. A small training set can also produce superficial changes, unstable cue placement, or behavior that already existed in the base model.

Established

Operational difference

Base and trained identities can be loaded separately; the trained adapter completed the intended supervised run.

Not established

Quality improvement

There is not yet a completed, sufficiently sized blind listening evaluation showing the trained arm wins.

The next claim should follow the evidence: either the trained output wins on untouched scripts, it ties the base model, or it loses. Every outcome teaches us something useful about the data design.