An AI agent skill that turns any subject into a 3D film or app
Split, join and check 67js films longer than one render job; release 0.6.1
Nguyen Xuan An083bf1f65c07
diff --git a/plugins/visualize-in-3d/.claude-plugin/plugin.json b/plugins/visualize-in-3d/.claude-plugin/plugin.jsonindex 60a3099..64cf7db 100644--- a/plugins/visualize-in-3d/.claude-plugin/plugin.json+++ b/plugins/visualize-in-3d/.claude-plugin/plugin.json@@ -1,6 +1,6 @@{"name": "visualize-in-3d",- "version": "0.6.0",+ "version": "0.6.1","description": "Turn hard-to-picture places, systems, objects and events into a 3D world you can watch, learn from or click through: a live three.js app with a dashboard, a lesson app, a documentary film, or an illustrated cutaway book, built from real layouts and models made from real references.","author": {"name": "CodePawl",diff --git a/plugins/visualize-in-3d/skills/visualize-in-3d/references/67js.md b/plugins/visualize-in-3d/skills/visualize-in-3d/references/67js.mdindex 9687752..da127f8 100644--- a/plugins/visualize-in-3d/skills/visualize-in-3d/references/67js.md+++ b/plugins/visualize-in-3d/skills/visualize-in-3d/references/67js.md@@ -47,10 +47,17 @@ Ask once at the start whether 67js may be installed when a film or a still is ththe user the grid, and keep the winner with `scene_restore`. Check every `scene_apply` result for`renderSucceeded`.5. **Preview, then final.** Submit a fast render job of the whole cut at low size first, with the soundtrack- (`settings.audio`), and show it to the user. Render full quality only after they sign off. A video job takes up to- 60 s and 900 frames at 1 to 30 fps. Render a longer film as jobs that start where the last one ended- (`settings.timeline.start`) and join them with the ffmpeg concat demuxer: frames keep no state, so the joins are- seamless. Each job checks audio sync and fails on a drift over 50 ms.+ (`settings.audio`), and show it to the user. Render full quality only after they sign off. Two limits shape a long+ film: a timeline holds at most 60 s, and a video job at most 900 frames (30 s at 30 fps, 37.5 s at 24 fps).+ - Within one timeline, render it as jobs that start where the last one ended (`settings.timeline.start` plus+ `duration`). Frames keep no state, so the picture joins without a jump.+ - Past 60 s, render the next part after `scene_apply` with `set-timeline` (its shots carry on the motion clock with+ `motionStart`), then submit with the new revision.+ - Join the parts with the ffmpeg concat demuxer, copying the video, and lay the whole soundtrack once over the+ result: `ffmpeg -f concat -safe 0 -i parts.txt -i score.wav -map 0:v -map 1:a -c:v copy -c:a aac -shortest film.mp4`.+ Each job still gets `settings.audio` with its `offset`, so it checks its own sync (fails over 50 ms).+ Measured on an RTX 3060, a 70 s film at 640x360 and 24 fps as three jobs: about 12 to 14 s of render per job, picture+ joins with no jump, the decoded sound 4 to 20 ms from each cut.6. **Keep the recipe.** `scene_export_recipe` into the project, so a fix starts from the same scene. Releasefinished jobs with `scene_render_release` and the scene with `scene_dispose`.@@ -63,5 +70,8 @@ checks in `self-review.md` on the rendered MP4, because a grid of stills cannot- A job that runs out of memory on a textured 1080p scene: `--memory` left at the default.- A model that keeps its old look after a Blender fix: the server still holds the old asset ID. Restart it.- A long film rendered as one job: the job is refused past 60 s or 900 frames. Split it on the timeline.+- A click or drop-out at every join: the parts were joined with their own AAC tracks, and each one adds a few+ milliseconds of encoder padding (the tone fell to near silence for 5 ms at each join). Copy the video only and lay the+ soundtrack once over the joined film.File an engine bug at https://github.com/codepawl/67.js/issues with the recipe, the steps and one still.