Populāri: Dati atjaunināti: 2026. gada 17. novembris

Kategorijas

Internets1416
Saziņa328
Audio un video938
Grafika un dizains562
Birojs un produktivitāte1180
Izstrādes rīki3283
MI rīki607
Drošība un privātums407
Sistēmas rīki3188
Spēles543
Izglītība un zinātne242
Tīkls un IT292

Multiplane: vecākas versijas un visa vēsture

Local headless HTML-to-video renderer for AI agents. Shots are plain web pages driven by render(t); includes determinism checks, cut-aware motion blur, and a 3D layer with accumulated depth of field.

Šeit uzskaitītas programmas Multiplane versijas (3): no pirmās, kas izlaista 2026. gada 19. oktobrī, līdz pašreizējai versijai 0.3.16. Katra ved uz izdevēja paša instalēšanas failiem.

2026: 3 3 26
VersijaDatumsLielumsFaili
0.3.16Jaunākā 2026. gada 15. novembris — 64 bitu EXE (NSIS)
Izmaiņu saraksts
A fix for jobs that looked stuck forever after their process had exited.
Desktop app
- Exited renders no longer look stuck. The app decides whether a running job's process is still there by its process ID, then checks the process's start time. When the render's process had exited and Windows (or another system) later gave the same ID to an unrelated program, that check could only say "unknown", so the job showed "possibly stuck" forever, its elapsed time kept growing, and a hosted job held the queue. A process that started after the job began cannot be its executor, so such a job is now shown as lost and the queue moves on. A failed check is still treated as unknown, and Stop still never kills a process it cannot verify.
Renderer
- multiplane wait no longer hangs on a reused process ID. In the same situation, wait (and the hosted handoff that follows a job) kept waiting; it now ends with internal_error ("Job process exited without a result"). The process start time is checked at most every 10 seconds while waiting.
0.3.15 2026. gada 15. novembris — 64 bitu EXE (NSIS)
Izmaiņu saraksts
Faster motion blur on moving frames, a frame time for shots, a hosted queue that survives a deleted job, and three fixes contributed by @liuyinchu. 0.3.14 was prepared on 2026-10-21 but not announced; its two fixes are included here. Both the renderer and the desktop app changed; an npm release follows.
Renderer
- Moving frames take fewer captures. With fast, standard and high, each frame used to capture the middle and one end of the shutter window before capturing its sample grid, so a moving frame with 4 samples took 6 captures. The still check now uses points of the starting grid itself: the two outermost times first, then the one nearest the frame time. A moving frame takes as many captures as samples, and a still frame still takes 3. On a 20-second 1080p clip from a real promo, render time dropped from 432 s to 343 s with identical sample counts. Frames whose only change happens in the outer eighth of the shutter window are now treated as still.
- SHOT.sampleContext.frameTime. The time of the output frame a sample belongs to: the same for every motion-blur sample of that frame, probes included, and unchanged when a cut shortens the window. Grain offsets, flicker and glitch patterns that change in discrete steps should take their time from SHOT.sampleContext?.frameTime ?? t: they then stay constant within the shutter, so two states are not blended into one frame and the sample count is not raised. Reading it does not trigger the full-grid recapture that reading motionBlur does.
- Settings locks are recovered safely. A process that exited while writing settings used to leave config.json.lock behind, and every later settings write timed out. The lock now records its owner and is recovered once that process is confirmed gone; a live or unverifiable owner is never evicted, and contention ends with the new config_locked code (exit code 3) (#6, thanks @liuyinchu).
- Resume notices a retargeted symlink. Checkpoints record the requested path as well as the resolved file, so an asset directory or project root that is a symlink and was pointed at different content after an interrupted render is refused with inputs_changed (#7, thanks @liuyinchu).
Desktop app
- A deleted job no longer stalls the hosted queue. If the directory of a running hosted job was removed (for example a job in a cleaned-up temporary folder), the app counted the job as busy forever and never started the next one. Such a job is now marked abandoned and the queue moves on. Records of finished hosted jobs are archived automatically, so the app no longer rereads hundreds of them twice a second.
- A hosted render that cannot start no longer blocks the queue. If its executor fails to start, the job ends as failed with internal_error (details.reason is hosted_launch_failed), multiplane wait receives the result, and the queue moves on (#8, thanks @liuyinchu).
Skill
- Instant changes inside a scene (a pressed button, a panel that collapses, an effect that starts at full strength, a caption swap) should be declared in cuts like any other hard cut; undeclared, the frame at that instant blends both states and is rendered with the maximum number of samples.
- When to use frameTime instead of t.
0.3.13 2026. gada 19. oktobris — 64 bitu EXE (NSIS)
Izmaiņu saraksts
Two fixes contributed by @fisHarly0: copied job commands keep their encoder and raster settings, and a relative --root no longer splits one project into several on the Jobs page. Both the renderer and the desktop app changed; an npm release follows.
Renderer
- A relative --root no longer splits a project. Jobs started with a relative --root (for example --root .) stored that relative value in their events. The desktop app resolved it against each shot's own directory, so shots in shots/ and other/ showed up as two different projects. The root is now resolved against the working directory when the command starts and stored as an absolute path. Jobs recorded by earlier versions keep their current grouping, because the original working directory was not recorded. Fixes #3 (#5, thanks @fisHarly0).
Desktop app
- Copied commands keep encoder and raster settings. "Copy command" left out --encoder x264 and --raster gpu because they match the built-in defaults. If your saved preferences named a different encoder or raster mode, running the copied command used those instead. Copied commands now always include the raster mode, and the encoder for MP4 renders. Fixes #2 (#4, thanks @fisHarly0).

Populārākā kategorijā „MI asistenti un LLM”

Skatīt visu
  1. Claude CodeMI asistenti un LLM · Anthropic PBC
  2. Codex CLIMI asistenti un LLM · OpenAI, Inc.
  3. ChatGPT by lencxMI asistenti un LLM · lencx
  4. GPT4AllMI asistenti un LLM · Nomic
  5. JanMI asistenti un LLM · Jan
  6. oh-my-piMI asistenti un LLM · Can Bölük
  7. T3 CodeMI asistenti un LLM · T3 Tools
  8. CC SwitchMI asistenti un LLM · farion1231
  9. WSL ManagerMI asistenti un LLM · Bostrot
  10. LobeHubMI asistenti un LLM · LobeHub

Birkas

Kopīgot