mmprompt/easy-media-track-gate/examples
2026-11-03 01:58:03 +00:00
..
outline_sam_park.json track-gate: plain text IS the deliverable - the skill told the agent to write JSON (goal line said 'PRIMARY deliverable is prompt_override.json'; smoke test, file lists, Step 4 and Step 5A all JSON-centric), so it kept writing the old format; now the paste is plain text end to end: verify_track_rules gains validate_prompt_override_text (mirror of the pack's parse_override_segments: split on |, strip, drop empties, trailing [s-e(,type)] marker lifted, @imageN/@audioN/@videoN refs vs inventory, <Picture N> and stray @ rejected, marker frames/types pinned to the approved rows, markerless form requires equal row lengths, markers all-or-nothing) + build_plain_text_override (fragment text VERBATIM - newlines survive, six-section structure intact - not the JSON's collapsed prompts; bare-| join, byte-identical to the user's proven node186 paste) and the override command takes .txt or .json; build_track_plan writes prompt_override.txt for EVERY zero-media story (markers auto-added for uneven lengths / non-t2v types), media stories keep JSON-only with an explicit note; SKILL.md/README/schema/wiring docs flipped: plain text default, JSON demoted to the <Picture N>/continuity/locks option; suite 46/46; merge output proven byte-identical to prompt_override_r2v_refmod.txt 2026-11-02 22:26:53 +00:00
outline.json easy-media-track-gate: the h3-plan-gate methodology adapted to ComfyUI-Easy-Media multitrack nodes 2026-11-01 01:09:26 +00:00
plan.json easy-media-track-gate: the h3-plan-gate methodology adapted to ComfyUI-Easy-Media multitrack nodes 2026-11-01 01:09:26 +00:00
prompt_override_r2v_refmod.txt track-gate: worked r2v+refmod plain-text example - examples/prompt_override_r2v_refmod.txt is the Sam park story as one prompt_override paste: three six-section r2v scene prompts, Sam refmod verbatim in every subject_definitions, pipes between, [0-240,r2v]/[240-480,r2v]/[480-720,r2v] markers at segment ends; proven through parse_override_segments + build_multitrack_data_from_prompt_override: 3 tasks TYPE r2v, frames [0-240]/[240-480]/[480-720], task-duration sum 720 (that sum, not the builder's 721 metadata, drives the MiniMax total), text byte-identical to plan shots, marker stripped clean; schema doc: marker end-placement, newline survival, pointer to the example 2026-11-01 22:32:31 +00:00
prompt_override.json track-gate: prompt_override minimized to the parser's real contract - parse_minimax_prompt_override requires ONLY type+prompts; version is read by nothing (validator no longer demands it); duration/generation_type/continuity_mode/locks emitted only when non-default (code defaults: '10' SECONDS, r2v, shot, 0); proven with the pack's own code: minimal 3-key Sam payload builds byte-identical TRACKS_INFO vs the old 9-key one; schema doc rewritten around the minimal form, no frame fields 2026-11-01 20:52:57 +00:00
segment_01.txt track-gate: the txt IS the pipeline - segment fragments are now plain text (segment_NN.txt = the scene prompt verbatim + one '# handoff:' line; the approved outline row supplies id, frames, modes and images, so nothing is retyped and the old verbatim-copy failures cannot happen by construction) and the merge writes ONE file by default: prompt_override.txt for zero-media stories, prompt_override.json for stories with media (tokens are JSON-only); plan.json + track_data.json only behind --plan (the 5B patch path), prompt_override.json behind --json for zero-media continuity modes/locks. verify_track_rules gains fragment_from_text/load_text_fragment/load_fragment_any (reusing validate_fragment + prompt_rules + _check_override_refs stray-token logic on the synthesized fragment; rejects |, hand-written [start-end] markers, @, and zero-media <Picture N>) and the segment command takes .txt or .json in every position incl. --prev; 11 new suite cases, 57/57. SKILL.md/README flipped: outline.json is the only JSON the default flow ever writes; the full JSON fragment is demoted to the variant-b / custom-system-prompt escape hatch; examples/ swaps the three JSON segments + track_data.json for the Sam story's segment_01-03.txt. Proven end to end: outline_sam_park.json + the three txt fragments merge to ONE file byte-identical to the proven prompt_override_r2v_refmod.txt paste 2026-11-03 01:58:03 +00:00
segment_02.txt track-gate: the txt IS the pipeline - segment fragments are now plain text (segment_NN.txt = the scene prompt verbatim + one '# handoff:' line; the approved outline row supplies id, frames, modes and images, so nothing is retyped and the old verbatim-copy failures cannot happen by construction) and the merge writes ONE file by default: prompt_override.txt for zero-media stories, prompt_override.json for stories with media (tokens are JSON-only); plan.json + track_data.json only behind --plan (the 5B patch path), prompt_override.json behind --json for zero-media continuity modes/locks. verify_track_rules gains fragment_from_text/load_text_fragment/load_fragment_any (reusing validate_fragment + prompt_rules + _check_override_refs stray-token logic on the synthesized fragment; rejects |, hand-written [start-end] markers, @, and zero-media <Picture N>) and the segment command takes .txt or .json in every position incl. --prev; 11 new suite cases, 57/57. SKILL.md/README flipped: outline.json is the only JSON the default flow ever writes; the full JSON fragment is demoted to the variant-b / custom-system-prompt escape hatch; examples/ swaps the three JSON segments + track_data.json for the Sam story's segment_01-03.txt. Proven end to end: outline_sam_park.json + the three txt fragments merge to ONE file byte-identical to the proven prompt_override_r2v_refmod.txt paste 2026-11-03 01:58:03 +00:00
segment_03.txt track-gate: the txt IS the pipeline - segment fragments are now plain text (segment_NN.txt = the scene prompt verbatim + one '# handoff:' line; the approved outline row supplies id, frames, modes and images, so nothing is retyped and the old verbatim-copy failures cannot happen by construction) and the merge writes ONE file by default: prompt_override.txt for zero-media stories, prompt_override.json for stories with media (tokens are JSON-only); plan.json + track_data.json only behind --plan (the 5B patch path), prompt_override.json behind --json for zero-media continuity modes/locks. verify_track_rules gains fragment_from_text/load_text_fragment/load_fragment_any (reusing validate_fragment + prompt_rules + _check_override_refs stray-token logic on the synthesized fragment; rejects |, hand-written [start-end] markers, @, and zero-media <Picture N>) and the segment command takes .txt or .json in every position incl. --prev; 11 new suite cases, 57/57. SKILL.md/README flipped: outline.json is the only JSON the default flow ever writes; the full JSON fragment is demoted to the variant-b / custom-system-prompt escape hatch; examples/ swaps the three JSON segments + track_data.json for the Sam story's segment_01-03.txt. Proven end to end: outline_sam_park.json + the three txt fragments merge to ONE file byte-identical to the proven prompt_override_r2v_refmod.txt paste 2026-11-03 01:58:03 +00:00