v1.0.42

Removed

• ComfyUI video templates: the two Seedance 2.x Comfy Cloud reference-to-video templates (2026-10-23). comfy/video-seedance2_5_r2v-cloud-only.json and comfy/video-seedance2_0_r2v-cloud-only.json, with their .md docs, no longer ship, so they are gone from the ComfyUI workflow list on the 生成模型 page. The handling for workflows built on ByteDance2ReferenceNode is unchanged, so a Comfy Cloud workflow you export yourself still works the same way. A setting that still points at one of the removed paths needs a workflow file of your own.

Changed

• 工作流预览: spent time and per-task time now come from the service's run records (2026-10-23, #134). A task's time used to come only from its runs/<task>/meta.json or the final result event of its run_id session log. So most tasks showed no time (many DAG nodes have no run_id), runs that ended in an error counted as 0, a re-run overwrote the earlier time, batch tasks sharing one run counted it once per group, and old meta.json files from an earlier version stood in for later re-runs. A task's time is now the sum of the run records (started → ended, kept in runtime.sqlite3) that belong to it. A run belongs to a task when the node lists it in run_id / prev_run_id / restyle_run_id, or when the first line of the dispatch message names the node ID. If the named node is a fanned-out parent and that line lists grpNNN or grpNNN–grpMMM, the run goes to those instances; a change-order suffix such as -B11R goes to the base node. A run that belongs to k tasks is split k ways. Producer sessions are not counted toward any task. meta.json and the session log are only used when no run is found. 已花费 is now the union of all the project's run periods (including the producer, re-runs and runs that ended in an error), so parallel runs count once. A fanned-out parent's own time counts toward its family, and the detail panel shows how many runs a task had. All 11 UI dictionaries are covered. On one real project, tasks with a recorded time went from 36 to 107 and 已花费 went from 9.3 h to 61.8 h.
• Volcengine and BytePlus model lists: retired models removed, Seedream 5.0 Flash added (2026-10-23). Checked against Ark's online model list. Seedance 1.5 Pro (doubao-seedance-1-5-pro-251215) was shut down on 2026-09-21 and now fails with ClosedEndpoint. Seedance 1.0 Pro / 1.0 Pro Fast and Seedream 5.0 / 5.0 Lite / 4.5 / 4.0 (-250828) are in Ark's tenth retirement batch: no new activations since 2026-09-24, shut down on 2026-11-24. All seven are gone from the Volcengine video and image lists on the 生成模型 page, the storyboard and canvas pickers, and the episode / group video-model choices. The Volcengine image list adds doubao-seedream-5-0-flash-260915 (same features as 5.0 Pro, faster and cheaper) and doubao-seedream-4-0-20260415 (Ark's replacement for Seedream 4.0). A setting that already uses a removed model keeps working: the page shows it under 自定义…, and accounts that activated the retiring ones before 2026-09-24 can call them until 2026-11-24. For 4.0 (20260415), the largest image size (4096×4096) was measured. For 5.0 Flash, the size range is taken from Ark's docs and is the same as 5.0 Pro; it has not been tried, because neither test account has Flash activated. On BytePlus, Seedance 1.5 Pro (seedance-1-5-pro-251215) is in the fourth retirement batch: no new endpoints since 2026-09-15, shut down at 17:00 on 2026-11-11 (UTC+8). It is gone from the BytePlus video list, and accounts that already use it can call it until then. The BytePlus image list adds dola-seedream-5-0-flash-260915. Every other BytePlus model in the lists still works, including Seedance 1.0 Pro / 1.0 Pro Fast, which Volcengine is retiring. seedream-4-0-20260415 is not added on BytePlus, because BytePlus is not retiring seedream-4-0-250828.

Fixed

• Engine CLIs: the fallback install paths for Kimi Code, OpenCode, Grok and Antigravity now work on Windows, and a failed launch shows the system's error (2026-10-23). When a CLI is not on the service's PATH, the service looks in the engine's default install location. For these four engines that location was written without .exe (e.g. ~/.kimi-code/bin/kimi), so on Windows it never matched, and the error only showed the bare command name. The fallbacks now come from the same default install locations that one-click install uses, with .exe on Windows and several candidates for some engines. When starting a CLI fails with "file not found", the "not installed" message now adds the error the system returned, so a transient failure (for example an antivirus scan holding a freshly downloaded runtime) can be told apart from a missing install. Paths on macOS and Linux are unchanged. Not exercised: the antivirus case itself.
• Image generation no longer gives up after 10 minutes (2026-10-23, #134). The shared wait limit for cloud image channels (Agentics, Volcengine Ark, OpenRouter, Fal, MiniMax and RunningHub standard models) rises from 600 s to 1800 s, the same as video and ComfyUI. An Agentics FLUX.2 image-to-image run with a 10-image reference chain took about 706 s and was cancelled before it finished. The four image subprocesses the service starts (sketch generation, storyboard sketches, grid sketches and hand-drawing AI refinement) now wait up to 2100 s instead of 900 / 1200 s. They used to kill genmedia while it was still waiting, which left the remote task running and saved nothing.
• Agentics TTS Voice Design now sends the voice description as instruction (2026-10-23, #134). On 2026-10-14 the Agentics service made instruction the official name of the TTS voice-description parameter. The client only recognised instruct / voice_instruction / voice_description / instructions. It treated a profile that declares instruction as having no description parameter, fell back to Voice Clone and could not produce the first voice sample. instruction is now checked first, and the old names still work for profiles imported earlier. This only takes effect once the Voice Design profile on the service is re-imported, or maps instruction.
• Agentics digital human: inputs now follow the service's digital-human contract (2026-10-23, #136). Digital-human profiles (media type 5) used to be checked against the video parameter and attachment list. The avatar image was sent as first_frame / reference_images and the speech as reference_audios. The avatar image now goes to avatar_image and the speech to driving_audios, checked against the digital-human contract's own parameters (e.g. audio_mode, audio_strength, audio_guidance_scale, fps, background_color) and attachments (avatar_video, dialogue_audio, speaker_masks, background_image / background_video, …). A profile with only attachment mappings is accepted and the prompt may be empty. When the profile requires duration, it is now the exact audio length in seconds, no longer rounded up. code/check_digitalhuman.py also accepts agentics as a clip ledger's provider, so finished Agentics lip-sync clips no longer fail the check as "渠道非法".
• Audio transcription now says which Python it ran on (2026-10-23, #136). When faster-whisper cannot be imported, modules/transcription.py and its doctor command now name the interpreter (sys.executable) and give the import error, instead of only asking for a reinstall. doctor also reports python_executable / python_prefix. The desktop app now lists the selected Python runtime's folder ahead of the login-shell and system paths in the web service's PATH, so python3 in commands finds the app's runtime. The desktop part takes effect after the desktop app is rebuilt.
• macOS desktop: Agentics runs no longer add an exec icon to the Dock for each running agent (2026-10-23). The built-in pi ran on the app's main executable in Node mode. pi sets its process title at start-up, and on macOS that registers the process with the system using the app's own settings, so every running agent showed up in the Dock as a separate app with a generic exec icon until it finished. The desktop app now runs pi on its Electron helper (VideoAgents Helper), which is marked as a background app, so agent runs stay out of the Dock. Windows and the source version are unchanged. Takes effect after the desktop app is rebuilt.
• Burned-in subtitles, whitebox reel subtitles and animatic captions now follow the requested font size on machines without a Chinese font (2026-10-23). When neither data/fonts/ nor the system has a Chinese font (typical on a Linux server), the subtitle renderer fell back to PIL's built-in font at a fixed 10 px, whatever the size the layout asked for. A 1920×1080 subtitle came out at about 1% of the frame height, and shrinking an over-long cue to fit two lines did nothing. The fallback now loads PIL's built-in font at the requested size. It has no Chinese glyphs, so Chinese text still needs a Chinese font installed, but English subtitles render at the right size. The subtitle burn ledger records PIL 默认字体 as the font in that case.