app
AI Flow
Public Made by Adomby adom
Adom's AI Flow: a tool to help the AI follow all of the steps it takes to build a board.
compose: final video is soft (built from 720p 10x cuts at about 265 kbit/s) and the Fields viewer narration is not captured
We kept a list of tool issues as we worked on a project, the 772 power module (LM251772), a 4-layer board built with AI Flow on the Fusion lane, and set them aside so they wouldn't slow the build down. Now that the project is finished, we're filing them together. Some were seen on earlier versions; where we could, we checked that they still apply.
Versions: adom-aiflow 0.2.44, Fusion lane.
What happens (772 power module, LM251772 run):
- The raw window recordings are 3840x2160 at about 42 Mbit/s. The 10x cuts compose uses are 1280x720, and the final 1920x1080 video came out at about 265 kbit/s video bitrate, so on-screen text (Fusion, the Fields viewer) is visibly soft.
- The Fields viewer speaks an explanation for each view, but the window recorder records video only, so none of it is in the final video. Compose adds its own TTS, which doesn't describe what the viewer was showing.
Expected:
- Compose from the raw recordings (or cuts at the output resolution) with a bitrate that keeps UI text sharp.
- Capture the app's audio for the Fields tour (a desktop recording with system audio, or splicing the viewer's cached narration clips into the timeline).
No design files attached; happy to describe more on request.
2 Replies
Colby Knox marked this in progress ·
Colby Knox mentioned this in pull request #68 ·
Colby Knox removed the in progress marker ·
Colby Knox marked this in progress ·
Colby Knox linked pull request #88, which closes this when it merges ·
Colby Knox closed this in pull request #88 ·
Log in to reply.