# Second KiCad video: the 24-net crossover

This was a constructed fixture, not an arbitrary-board autorouter. For i=0..23, j=(7*i) mod 24 selects an output column. Rows are y=52+2.54*i mm; columns x=65+2.54*j mm. Front copper carries horizontal runs and back copper vertical runs. Each net branches to a third pad and uses two layer-changing vias. Width 0.30 mm, via diameter 0.60 mm, drill 0.30 mm.

Measured final board: 24 nets, 72 pads, 120 segments, 48 vias. KiCad reported zero DRC errors and zero unconnected items, plus three synthetic-library warnings. These are this fixture's results, not promises about another board.

## Original scripts and evidence in the shared development container

All paths below are in /home/adom/project/work/routing/team-demo/:

- make_crossbar.py and crossbar-plan.json: fixture and routing plans.
- record_crossbar.py: live recording, per-net preview, individual segment/via commits, revision checks, final validation, save, stop and pull.
- crossbar-report.json: timestamped verb calls and responses.
- before.json, after.json, validated.json: measured evidence.
- find_action.py, action-ranges.json: finding and retaining action intervals.
- render.py: common FFmpeg/ASS layout and editing pipeline.
- render_complex.py: second video's caption sequence, retained intervals and 5-second final hold.
- 02-astra-crossbar-24-3x.ass and .edit.json: exact captions and edit provenance.
- video-verification.json: video checks.
- 02-astra-crossbar-24-3x.mp4: delivered clip, about 30.83 seconds.

These are historical, machine-specific examples. Read and adapt them; do not run their hardcoded HWNDs, board paths or routing mutations on another editor. They are not installed as executable package commands.

## Recording and editing details

The native recorder used desktop_record_window_start at 30 fps, audio false, maxDurationMs 600000. kicad_routing_state verified the empty board and dev bridge. Each kicad_route_net dryRun checked a whole planned net; its exact segments/vias were then committed individually using expectedRevision and validate:false, with roughly 0.3 seconds between visible commits. After each net, state was refreshed. kicad_routing_validate checked the completed board, and Ctrl+S saved it through the background KiCad command path. Finally the recording was stopped by recordingId and pulled into the container.

The raw video contained about 166 seconds of frames. The edit retained verified action intervals, accelerated their concatenation 3x, and held the last frame 5 seconds. For the original constant-30-fps source, the select expression was followed by setpts=N/(30*TB) to eliminate gaps, then setpts=(PTS-STARTPTS)/3 and fps=30. For a variable-frame-rate source, use timestamp-aware trim/concat instead of assuming 30-fps frame spacing.

The composition fitted CAD into a 1440x900 region, preserved aspect ratio, and padded to 1920x1080 with a heading, side explanations and bottom ASS captions. FFmpeg came from imageio_ffmpeg installed in /home/adom/project/work/routing/video-deps. Check that dependency before reusing the scripts.

One gotcha: the final clone hold came AFTER burning ASS captions. The final-result caption therefore starts 0.2 seconds before the action ends so the cloned frame contains the result text. Inspect the end to avoid freezing an outgoing caption over the final result.

The user asked for trimming idle opening footage, 3x routing, explanatory captions and a team-shareable video. No narrated audio was used. The completed files were transferred to C:/Users/john/Documents/Adom Routing Demos/ and opened through the Windows file association via Adom Bridge.

For Fusion, substitute its proven native routing/read-back verbs and report its own validation evidence. Do not borrow KiCad's DRC claims or call the video an independent autorouting demonstration unless the geometry was actually independently planned.