[PR #195] [MERGED] fix(docs): correct the Crystal Video Upscale limits wording #191

New issue

Closed

opened 2026-10-26 22:10:29 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-26 22:10:29 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/Comfy-Org/embedded-docs/pull/195
Author: @lin-bot23
Created: 10/21/2026
Status: ✅ Merged
Merged: 10/24/2026
Merged by: @comfyui-wiki

Base: main ← Head: docs/clarity-video-upscale-limits

📝 Commits (2)

7c73dc7 fix(docs): correct the Crystal Video Upscale limits wording
a3980c8 fix(docs): name the input limits and the 30-fps cost multiplier for Crystal Video Upscale

📊 Changes

6 files changed (+14 additions, -14 deletions)

View changed files

📝 comfyui_embedded_docs/docs/ClarityCrystalVideoUpscaleNode/en.md (+3 -3)
📝 comfyui_embedded_docs/docs/ClarityCrystalVideoUpscaleNode/ja.md (+3 -3)
📝 comfyui_embedded_docs/docs/ClarityCrystalVideoUpscaleNode/ko.md (+3 -3)
📝 comfyui_embedded_docs/docs/ClarityCrystalVideoUpscaleNode/zh.md (+3 -3)
📝 comfyui_embedded_docs/docs/Flux3VideoContinuationNode/ja.md (+1 -1)
📝 comfyui_embedded_docs/docs/Flux3VideoContinuationNode/ko.md (+1 -1)

📄 Description

The Crystal Video Upscale page told readers that frames over 9 megapixels or clips over 360 megapixel-seconds "come back at a lower resolution". They do not: ClarityCrystalVideoUpscaleNode.execute raises ValueError for both, and the only automatic reduction is the 5120 px output-side cap (min(scale_factor, floor(5120 / max(width, height) * 100) / 100)).

This pull request:

says the over-limit cases are rejected with an error and names the 5120 px cap as the only automatic reduction (intro and scale_factor row, four languages)
states the clip-length divisor as ceil(fps / 30) instead of "the frame rate rounded up to a multiple of 30 fps", which reads as dividing by 30 and makes the 1080p at 30 fps example look wrong
says the 3840x2160 threshold in Flux3VideoContinuationNode applies to pixel area (ja, ko), matching the English text and the node tooltip

Facts taken from comfy_api_nodes/nodes_clarityai.py (MAX_VIDEO_FRAME_PIXELS = 9_000_000, MAX_VIDEO_PIXEL_SECONDS = 360_000_000, MAX_VIDEO_SIDE = 5120, max_duration = 360e6 / (w * h * ceil(fps / 30))) and comfy_api_nodes/nodes_bfl.py ("Clips over 3840x2160 pixels in area are downscaled to fit").

Found while reviewing the docs sync that copies these pages into Comfy-Org/docs (Comfy-Org/docs#2018).

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/Comfy-Org/embedded-docs/pull/195 **Author:** [@lin-bot23](https://github.com/lin-bot23) **Created:** 10/21/2026 **Status:** ✅ Merged **Merged:** 10/24/2026 **Merged by:** [@comfyui-wiki](https://github.com/comfyui-wiki) **Base:** `main` ← **Head:** `docs/clarity-video-upscale-limits` --- ### 📝 Commits (2) - [`7c73dc7`](https://github.com/Comfy-Org/embedded-docs/commit/7c73dc729ad15d9fd7a737db8900f67ec9954d6e) fix(docs): correct the Crystal Video Upscale limits wording - [`a3980c8`](https://github.com/Comfy-Org/embedded-docs/commit/a3980c81faf3b2c70b45724b8a914668217b34d8) fix(docs): name the input limits and the 30-fps cost multiplier for Crystal Video Upscale ### 📊 Changes **6 files changed** (+14 additions, -14 deletions) <details> <summary>View changed files</summary> 📝 `comfyui_embedded_docs/docs/ClarityCrystalVideoUpscaleNode/en.md` (+3 -3) 📝 `comfyui_embedded_docs/docs/ClarityCrystalVideoUpscaleNode/ja.md` (+3 -3) 📝 `comfyui_embedded_docs/docs/ClarityCrystalVideoUpscaleNode/ko.md` (+3 -3) 📝 `comfyui_embedded_docs/docs/ClarityCrystalVideoUpscaleNode/zh.md` (+3 -3) 📝 `comfyui_embedded_docs/docs/Flux3VideoContinuationNode/ja.md` (+1 -1) 📝 `comfyui_embedded_docs/docs/Flux3VideoContinuationNode/ko.md` (+1 -1) </details> ### 📄 Description The Crystal Video Upscale page told readers that frames over 9 megapixels or clips over 360 megapixel-seconds "come back at a lower resolution". They do not: `ClarityCrystalVideoUpscaleNode.execute` raises `ValueError` for both, and the only automatic reduction is the 5120 px output-side cap (`min(scale_factor, floor(5120 / max(width, height) * 100) / 100)`). This pull request: - says the over-limit cases are rejected with an error and names the 5120 px cap as the only automatic reduction (intro and `scale_factor` row, four languages) - states the clip-length divisor as `ceil(fps / 30)` instead of "the frame rate rounded up to a multiple of 30 fps", which reads as dividing by 30 and makes the 1080p at 30 fps example look wrong - says the 3840x2160 threshold in `Flux3VideoContinuationNode` applies to pixel area (ja, ko), matching the English text and the node tooltip Facts taken from `comfy_api_nodes/nodes_clarityai.py` (`MAX_VIDEO_FRAME_PIXELS = 9_000_000`, `MAX_VIDEO_PIXEL_SECONDS = 360_000_000`, `MAX_VIDEO_SIDE = 5120`, `max_duration = 360e6 / (w * h * ceil(fps / 30))`) and `comfy_api_nodes/nodes_bfl.py` ("Clips over 3840x2160 pixels in area are downscaled to fit"). Found while reviewing the docs sync that copies these pages into Comfy-Org/docs (Comfy-Org/docs#2018). --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-26 22:10:29 +00:00