[Alitleis123]

Upflow2x 0.5.1: one-click setup, renders about three times faster, and renders saved out of your clip folders.

One-click install

• New installers: Upflow2xInstaller.exe on Windows, and Upflow2xInstaller-mac.zip on a Mac, which holds one app for Apple Silicon and Intel.
• Setup installs its own private Python. Nobody installs Python or opens a terminal.
• The plugin goes in DaVinci Resolve's own folder, %APPDATA%\Blackmagic Design\DaVinci Resolve\Support\Upflow2x on Windows or ~/Library/Application Support/Blackmagic Design/DaVinci Resolve/Upflow2x on a Mac. It sits beside Fusion, not in its Scripts folder, and the download can be deleted afterwards.
• Setup isn't signed yet. The install steps walk through Windows' More info → Run anyway and macOS's Open Anyway.
• The installer window and a new (i) at the top of the panel list what Upflow2x needs.
• The release workflow builds both installers on their own platforms and attaches them to the release.

Faster renders

• A 190-frame 4K render of a 1080p anime cut took 93 s and now takes 33 s on an RX 7900 XT.
• Real-ESRGAN upscales only the drawings, here 10 frames instead of 190. Each in-between is drawn at 4K from the upscaled drawings with RIFE's own motion and blend mask. That data is added to the model's outputs when it loads, by patching its protobuf in memory.
• Drawings come out identical, and the in-betweens measured 45 to 50 dB against the old ones.
• The 4K warps and the frame writes run in a pool while the GPU draws the next frame. There is less CPU work around each RIFE call, and OpenCV's threads are shared between the workers.

Where renders go

• Renders no longer go in an Upflow2x folder beside each clip. They go in an Upflow2x folder beside the project's Resolve cache folder, with a folder for each project.
• If the project has no cache folder, or it is unplugged, read only or in OneDrive, renders go in Upflow2x\Renders in Resolve's own folder.
• A new Save to row under Output chooses another folder through Fusion's folder dialog, still with a folder for each project. A chosen folder that can't be written stops the render with a message.
• A render that is stopped or fails is deleted. A finished render is never deleted, because the timeline uses it.
• Each render makes its own folder or file when it picks its name, and a video is drawn into a file of its own until it is done. Two renders at once can never overwrite or delete each other's files.
• Renders from 0.5.0 and earlier stay where they are.

Fixes

• A cache or output folder ending in a backslash escaped its closing quote on Windows, and the status file argument was lost, which broke progress and Stop.
• A project named like a Windows device, such as NUL or COM1, failed on its first frame.
• Choosing a drive root such as D:\ under Save to no longer turns into the drive-relative D:.

README and site

• README: new requirements, the setup install steps, a manual install section with the Python limits for source ZIPs, a "Where renders go" section, the new upscale and timing details, a "Rendering is slow" troubleshooting entry, and the new release steps for the installers.
• Home page: the specs now say Python installs automatically, and the download note says about 50 MB in all.
• Download page: the buttons point at the installers, with new steps.
• Help page: new Windows and Mac install steps with the security prompts, a Manual installation section, a "Where renders go" section, and updated Upscaling, Interpolate and troubleshooting text.

Testing

• Full test suite: 840+ tests pass on Windows, with 3 platform skips. Nothing needs Resolve.
• Real renders of a 1080p Demon Slayer cut on an RX 7900 XT, old against new: 93 s → 33 s, with frame-by-frame PSNR checks.
• Not yet tested inside Resolve: setup on Windows and Mac, the new panel row, Fusion's folder dialog, and Stop cleanup. That happens while recording the install tutorial, before the v0.5.1 tag.

Updating from 0.5.0: the panel updates itself. Restart Resolve, and renders go to the new folders after the restart.