Changelog
Auto-generated from the Vapourkit desktop repository. Do not hand-edit — update
Changelog.mdin the desktop repository instead.
Updating no longer costs you a re-setup
Section titled “Updating no longer costs you a re-setup”Until now, installing a new Vapourkit over an old one deleted the whole data folder: the Python/VapourSynth environment (several GB, ~20 minutes to rebuild), your settings, workflows, custom filters and built TensorRT engines. That is why copying a new portable build over an old one has been the faster way to update. From 2.1 the setup installer updates in place. data is kept, and the update takes seconds.
- Coming from 2.0 (setup install): just run the 2.1 installer. The uninstaller that runs during an update belongs to the version being replaced, and 2.0’s could not cope with the environment’s long file paths. It would have failed with “Vapourkit can’t be closed” (or “Failed to uninstall old application files”), and clicking Retry never helped. The 2.1 installer now moves
dataout of the way before 2.0’s uninstaller runs and puts it back afterwards, so the hop works and nothing is rebuilt- If you pick a different install folder on another drive, the installer can’t move
dataacross drives. It leaves it in a folder named<old install folder>.update-data, tells you where, and never deletes it. Move it into the new install folder asdataand start Vapourkit - If an update is interrupted,
datamay be left in that.update-datafolder. Running the installer again puts it back
- If you pick a different install folder on another drive, the installer can’t move
- Coming from 0.16 or older: unchanged from 2.0. The old environment isn’t compatible, so setup runs once. Export your workflows and filters first
- Portable users: extract 2.1 over your existing folder, keeping
data, as before - Uninstalling removes everything, including the long-path files the old uninstaller left behind, so the install folder no longer lingers after an uninstall
- What an update does to an existing install, and how it tells you: you don’t have to reinstall plugins to get a release’s fixes. On the first launch after an update, Vapourkit brings your install up to date and then shows a notice listing what it did. The notice stays in Settings → Last Update until every decision in it is made
- Filters you haven’t edited are updated to the new version, or removed if the release dropped them. This release updates 42 and removes 14
- Filters you have edited are never changed without asking. If the release changed a filter you edited, the notice offers Use new version or Keep mine. If it dropped one, the notice offers Remove or Keep, and names the replacement when the filter was only renamed. Your copy is saved to
data\config\template-backupsbefore anything replaces or removes it. An edit made to a filter the release didn’t change is left alone and not mentioned - Filters you deleted stay deleted. Updates used to put them back
- Python packages are checked against the list this version installs. Anything missing or below its minimum version is installed: this release,
vapoursynth-timecube(fast LUTs) andvs_undistort>=2.3.1. This needs an internet connection once. If it fails, the app still starts and tries again a day later - VapourSynth scripts (the Hybrid scripts and the bundled script pack) are versioned too. An update replaces the ones you haven’t edited when a release changes them, keeps any you edited and lists them in the notice, and downloads nothing when nothing changed. Reinstalling plugins restores every shipped script, saving your edited ones to
data\config\script-backupsfirst - Saved workflows are never touched: each step keeps its own copy of the filter’s code
- How it knows:
data\config\installed-components.jsonrecords the version of every filter, plugin and script Vapourkit put into your install, so later updates can tell its files from your changes
Installing is more reliable
Section titled “Installing is more reliable”- Downloads no longer hang. Every download now gives up on a stalled connection instead of sitting at “Downloading… N%” forever, retries, and only hands a file to 7-Zip once it’s completely written. That covers Python, pip, FFmpeg, video-compare, the model packs and the VapourSynth scripts. It also uses Windows’ proxy settings. Before this, the “7-zip exited with code 2 / 0 bytes / file in use” fix only covered the scripts download
- Errors say what went wrong. A failed install used to say only “exit code 1”. It now names the cause and what to do, with the relevant lines under Details and the log’s location. Recognised causes: disk full, antivirus or a locked file, Windows’ path-length limit, no connection, proxy or HTTPS interception, a damaged pip, and an interrupted earlier install
- Checked before starting: free space on the data drive and the temp folder (an NVIDIA plugin install needs 12 GB, and warns below 18 GB to leave room for pip’s downloads and the TensorRT engines you’ll build), whether Vapourkit’s folder is writable, and warnings for a portable copy under Program Files or a folder path too long for Windows. After a successful install, pip’s download cache is cleared, instead of growing to several GB
- No more tangled retries. Setup retries a failed plugin install once, as before, but no longer shows “Retry” while that retry is already running. Clicking it there used to start a second install into the same environment. Only one install or uninstall can run at a time
- Cancel works during downloads and extraction, not only while pip is running
- A failed setup no longer leaves “Start Setup” stuck on its spinner until you restart the app
- The VapourSynth scripts download no longer fails the whole install. If GitHub can’t be reached, the rest installs, and the next launch fetches the scripts
- Repairs itself where it can:
- At launch, a pip that no longer runs is reinstalled
- A half-extracted Python is re-extracted instead of being trusted because
python.exeexists - Plugin DLLs that vanish right after extraction are reported as antivirus quarantine, naming the folder to exclude, instead of failing later with a missing-plugin error
- On Linux, setup runs
vapoursynth config, which fixes “Failed to initialize VSScript” on first launch (not yet tested on a Linux machine) - The dependency check runs once per launch. It could run twice at once, and the two runs could spoil each other’s files; this was the cause of the occasional “Failed to write the trtexec shim” in logs
- Only one thing changes the Python environment at a time. The launch-time repairs, plugin installs, the vs-mlrt update and the vs-view install now take turns instead of running pip into the same environment at once. A plugin install that has to wait says Waiting for another Python package operation…
- The vs-mlrt update retries a dropped connection and reports a failure in a plain sentence, as plugin installs do, instead of pip’s raw output
- Plugins read as not installed when any package the install asks for is missing. Before, only 9 of them were checked
Colour grading
Section titled “Colour grading”- Colour grading is a step in the filter chain, so it can sit anywhere: before the model to fix the source, after it to finish the result, or both. Reorder or disable it like any other step
- Opening a grade docks a Resolve-style panel under the preview: lift/gamma/gain/offset trackballs, a tone grid, and scopes. On a wide enough window the scopes get their own column beside the picture
- Grading is live against the real chain at full resolution, shaded on the GPU. Closing the panel re-renders once with the values baked in
- The tone sliders follow the cursor and take typed values
- A Clip toggle stripes clipped pixels (red at the top, blue at the bottom) live while you drag
- A black point picker: click something that should be black, and lift is solved per channel for level and colour cast together
- The preview reports where the picture sits in 8-bit code values, and flags footage that looks like limited-range video being read as full range
- Lift and gain are now a single ramp, as in Resolve, so setting a black point no longer drags the highlights. Highlight headroom above 1.0 is kept through gamma and contrast. An unedited Color Grade template is upgraded automatically
- LUTs (experimental): export a grade as
.cubeor.3dl, or import one as an Apply LUT step. Create LUT / Load LUT is a pair of steps that captures the colour at one point in the chain and restores it at another, either exactly or by fitting when a model sits between them, and reports how well it fit - LUTs render through
timecube(installed automatically), which is about 4x faster and half the memory of the fallback. Fixed a.3dlround trip that could come back up to 16x too bright, and importing two LUTs with the same filename no longer repoints saved workflows at the wrong one
Inspect: preview the real chain in the app
Section titled “Inspect: preview the real chain in the app”- Inspect shows the actual output of each step at full resolution, one step at a time, instead of a 640px ffmpeg snapshot. Number keys switch steps, and Ctrl+R reloads after a chain change
- Playback: the chain plays in the app, each step at its own frame rate. Every frame is shown in order and none are dropped, so combing, cadence and ghosting are visible
- Timeline: position readout, drag to scrub, loop, Home/End, Shift+arrows for one-second steps. The picture follows a segment handle while you drag it, and the Segment button now toggles the mode directly
- The Before/After wipe works in Inspect
- Inspect can be cancelled while it’s opening, even mid engine build
- Removed: the “Preview selection” button, which rendered a segment to a temp file. Playback plus loop replaces it. Preview errors now show as a toast
- Fixed the timeline seeking to the wrong moment on steps that change the clip length (e.g. a bob deinterlacer), and being off by the segment’s in point
- Opening Inspect evaluates the chain once instead of twice, so it opens sooner after a chain change, and an engine build still shows its banner. An error opening it shows the Python exception instead of vspipe’s whole output
MIGraphX backend (AMD)
Section titled “MIGraphX backend (AMD)”- New inference backend for AMD GPUs, built on vs-mlrt’s MIGraphX plugin. Pick it from the backend menu, globally or per step. DirectML stays the default on AMD
- There’s no build step at import. The first render at a new resolution compiles the model for that size, with a build banner while it works (expect minutes), and later renders reuse the result
- Windows: needs an RX 6800-class (gfx1030) or RDNA3-or-newer GPU and a current AMD driver. The plugin and its HIP runtime aren’t on PyPI, so AMD installs download them from the vs-mlrt release (68 MB, 383 MB on disk); existing AMD installs fetch them in the background on the next launch. On a GPU or driver MIGraphX can’t use, a render stops with a message saying to switch to DirectML or NCNN
- Linux: needs ROCm with MIGraphX installed on the system (
migraphx-driveronPATH, or under$ROCM_PATH//opt/rocm) - Models whose input is 5-D (some multi-frame VSR architectures) aren’t supported by MIGraphX and say so; 4-D models, including frame-stacked VSR, work
- Not yet tested on AMD hardware
- Fixed: filters disappearing after a restart. Opening the queue sets the project’s chain aside and editing a queue item shows that item’s chain; the set-aside copy was only kept in memory, so restarting with the queue open and closing it left the item’s chain in place of the project’s. It is now kept across restarts
- Fixed: queue item settings reverting. Edits made just before closing the app are now saved as it closes (they were saved on a delay that closing cut short); selecting a completed item no longer drops the last edit to the item being edited; an item’s encoding settings (FFmpeg arguments, processing format, colorimetry) are loaded when it is selected instead of being overwritten by the current ones; and undo no longer reaches back into a different item’s chain
- Fixed: closing the queue while editing an item saved the project’s chain and settings into that item, and reset the project’s segment
- Fixed: adding several videos at once opened the queue without setting the project aside, so closing it kept a queue item’s chain as the project’s
- Restarting while editing a queue item picks the editing back up, instead of showing the item’s settings with nowhere for edits to go
- The queue is saved promptly while it runs: an item finishing, starting or failing is written at once, and progress at least every 10 s. A crash mid-batch no longer re-encodes finished items
- Items that are processing or done no longer take edits, so what is stored is what was rendered
- Fixed: Stop during the start of a run was ignored. Stopping while a run was still evaluating the chain (which includes building a TensorRT engine) let the encode start anyway, and it could no longer be stopped. It now stops. Quitting also stops an encode that is still shutting down, and any Align in progress
- Each queue item renders with its own FFmpeg arguments, processing format and colorimetry. Before, every item used whatever the main window showed when it started
- Fixed: running the queue changed the project. Starting an item loaded it into the main window, which reset the project’s segment and could point the finished-video preview at the wrong file. The queue now shows the running item in its own panel and progress bar, and the progress bar moves (it stayed at 0)
- Viewing a completed item no longer writes its settings into the project, and project edits made while the queue is open with nothing selected survive closing it
- Stopping the queue no longer loads the stopped item’s partial file or marks the item as failed
- Choosing an output file while editing a queue item saves it to that item
- Fixed: the settings and queue files could be corrupted, then replaced with defaults. Saves made in quick succession (selecting a queue item writes five) could interleave into invalid JSON, and the next start silently started over. Writes are now atomic and ordered, and a file that cannot be read is moved aside (
*.unreadable-<time>.json) rather than saved over
Workflows
Section titled “Workflows”- New: edit a filter in place. An Edit button on a step’s card (and the pencil in the filter picker) opens one dialog for the filter’s name, categories, description and code, and saves it as the same filter, no deleting and re-importing, no duplicate. Steps using it follow a rename, and get the new code unless their own code was changed
- A loaded workflow can still be cleared after a restart (its “before” state is kept), and clearing it puts the backend back too
- Workflow files now carry the default backend
- Align and Generate LUT apply their result to the chain as it is when they finish, keeping edits made meanwhile; if a different chain was loaded in between, they leave it alone and say so
- Code typed into a step and not yet committed is saved when the app closes
- Importing filters, saving or renaming a template, or importing a .vkfilter asks before replacing an existing template with the same name
- Encoding: Advanced mode no longer gets stuck on. Simple or Advanced is now saved with the settings (the project’s, each queue item’s and each workflow file’s), and only that choice decides what is encoded. Before, the mode was guessed from the FFmpeg arguments, so a fresh install opened in Advanced mode and encoded with those arguments, and switching modes could write old arguments over the current settings
- Both halves are kept: the simple settings and the typed arguments survive switching back and forth, so switching never asks to replace anything. Copy from simple settings fills the arguments from the simple controls
- Existing settings open in Simple mode when the simple controls can show their arguments, and otherwise in Advanced mode with the arguments unchanged and the simple controls set to their codec
- MP4 and MOV output gets
-movflags +faststartunless the arguments set movflags themselves - Quoted values in the FFmpeg and video-compare arguments (
-metadata "title=My Video") stay one argument - A render started right after changing a setting uses the new value
- Confirmations (delete, replace, overwrite, reinstall) use the app’s own dialog instead of the system one, veiled in privacy mode; Escape cancels, and destructive ones start on Cancel
- Escape closes only the topmost dialog. In the Edit Model dialog it closed the whole model picker
- Renaming a model keeps it in Favourites and Recent
- Ctrl+Shift+Z redoes, as well as Ctrl+Y
- Crop, Color Grade and Crop (Auto) with edited settings or description are no longer replaced or removed silently by an update: the update notice asks, as it does for other edited filters
Filters
Section titled “Filters”- New: Grain Synth. Adds film grain fitted to real sources, with two models:
mega_v1(stronger, harsher) andreal_v5(softer). Apply it after upscaling, at the final resolution. The grain is the same on every render of a frame, and it runs on CUDA with TensorRT or on the CPU otherwise - New: IVTC (AI Fallback). Inverse telecine for film on DVD that rebuilds the original 23.976 frames losslessly and runs Deep Deinterlace only on the frames field matching leaves combed (credits laid over film on video, edits that break the cadence). On a telecined Hokuto no Ken episode that is about 1 frame in 400, so it runs at IVTC speed. Use it instead of deinterlacing to 59.94 and dropping frames
- VIVTC keeps full bit depth and 4:2:0 instead of passing through 8-bit 4:2:2, and no longer replaces
original_clip, which made a later step reading “the source” get the un-IVTC’d 29.97 clip - sRestore restores NTSC film (23.976) by default; it restored 25 fps, which only suits PAL shows converted to NTSC
- New: side chains. Add a Load Video step to bring in a second video (another release, a reference) and drag steps into it to run on that video only; a step like Guided Color Fix can then read it. Align lines it up with the main source: timing (offset, speed, sections where the releases are cut differently) and framing (crop, scale and position, which can change partway). On Hokuto no Ken ep. 1 the reference sat 2% larger and up to 10 px off; aligned, it is within 1 px and colour stays on the lines. Aligning an episode takes about 30 s on the GPU
- New: Guided Color Fix. An AI colour correction (PACC V4) that matches an upscale’s or restoration’s colour to the source, or to any step you pick, while keeping its detail. Ships the
2x_bndl_aniccmodel (CC BY-NC-SA 4.0), and also takes your own PACC V4.onnx,.safetensorsor.pth. Runs on every inference backend: about 9 fps at 1080p and 2 fps at 4K with TensorRT fp16 on an RTX 5080 Laptop. Each frame is checked against its reference first, by outlines and by layout (where light and dark sit, so a glow, sky or flash with few lines still matches): it is corrected against the best-matching reference frame within 3 either side, picking by colour where outlines tie (flashes, fades). Whether to correct is decided per scene: a scene that mostly matches is corrected throughout, and one that mostly does not (credits one release lacks) is passed through whole, so nothing flickers between corrected and not. On Hokuto no Ken ep. 1, 99.9% of frames before the ending are corrected, against 91% before. Frames with no detail in either release (black, a flash) are only moved to the reference’s average colour, so faint captions and shapes in them are kept. Each reference frame is also warped onto its frame before correcting: a displacement field measured tile by tile, then refined per pixel, so pans, zooms, layers moving at different speeds and characters moving across a background no longer give doubled lines (misalignment median 2.1 px to 0.14 px; 99th percentile 6.5 to 1.5). Where the reference still disagrees after that (a drawing timed differently, a frame that release blended), its shapes are blurred there, so only its colour is taken. Matching and warping run on the GPU: about 50 fps at 480p, where the model alone runs at 140 - Every shipped filter is now checked against the real VapourSynth core, at both ends of the clip. All 151 build and render
- 37 filters that failed to build now work, most of them broken by upstream renames: Detail/Luma/Ridge/Difference/Normalize Mask, MC_Degrain, Binarize Mask, Maximum/Minimum and their combinations, Clense, Grain Stabilize, EEDI3, Warp Sharp, Temporal Median, SpotLess, the four descalers, Undistort, and more
- Also fixed: QTGMC (Old) on every preset, Guided Filter (refused every real source), Read Image, GradFun3, Add Duplicates, Replace Multiple Frames, LUTDeCrawl (now works at 10-bit instead of 8)
- Removed 13 filters that could not run, because their native plugins have no build available: Based AA, Fill Drops RIFE/SVP, Fine Dehalo2, Frame Rate Converter, Grain Factory, LGhost Deghost, Oyster, Rainbow Smooth, Remove Dirt, Remove Dirt MC, TFMBobN, TFMBobQ. Workflows that use them keep their copy of the step. Fine Dehalo2 will come back once an upstream bug is fixed
- Undistort works on 50-series GPUs again (needs
vs_undistort2.3.1, installed automatically) and gets itswindow_overlapcontrol back - Crop at all zeros removes the padding a Pad or Modulus step added, as it originally did, and passes straight through when nothing was padded. Crop (Auto) is merged into it. Crop also has a visual editor
- A step can take its picture from any step above it, not only from the original clip. Wavelet Color Fix from Step is the first filter to use this
- Start is disabled while a filter editor is open, with the reason on hover
Models and encoding
Section titled “Models and encoding”- New model: bndl animefilm v3 (2x, video). It uses 9 neighbouring frames and is CC BY-NC-SA 4.0
- The model licenses in About are up to date: AnimeJaNai V2 is listed, and AnimeJaNai HD V3 covers its Sharp1 variant
- BF16 TensorRT engines no longer produce corrupt output
- Model precision is read from the ONNX graph, so BF16 models import correctly. Auto-build now actually builds BF16 models as BF16
- Editing a model offers the same precisions as importing it, taken from the backend instead of assuming TensorRT
- Building a TensorRT engine no longer flashes a console window, and the import progress bar no longer jumps backwards
- A render probes the video once and evaluates the chain once before encoding, instead of three and two times, so it starts sooner (most noticeably with a model that takes a while to load)
- The quality slider now works on hardware encoders (NVENC, AMF, QSV). Before, it had no effect, and every quality setting produced the same few-Mbps output
- Variable frame rate videos keep their timing. Phone and screen recordings, and other videos whose frame rate changes, came out at one constant average rate, so the picture drifted away from the audio (by over 300 ms on a 60/30 fps test clip). Every frame now keeps its own timestamp, in MP4 and MKV, and the log says when a source has a variable frame rate
- RIFE keeps the timing too: each new frame gets its share of the frame it starts from. A step that sets a rate on purpose (Assume FPS, Change FPS, decimation) still gives a constant rate
- A segment’s audio is cut at the real time of its first frame instead of frame number ÷ frame rate, which was off by up to a few hundred ms on a variable rate source and drifted a little even at 23.976 fps
- A video that starts later than its audio (a common camera and capture quirk) no longer comes out with the audio early by that gap
- Temporal (multi-frame) models gave each frame the properties of the frame two before it, such as its duration and scene-change flags. Each frame keeps its own now
- Built-in filters no longer vanish. 2.1 took any missing built-in filter as one you deleted and never put it back, so a filter removed by anything else was gone for good. Vapourkit now records a delete when you make it in the app, and restores at launch any built-in filter that is missing without one
- The trash button on a filter step asks before deleting, and the filter picker offers Restore N deleted built-in filters for the ones you did delete
- A filter of your own that shares a name with one a new release ships is no longer shown as an edited built-in
- On Linux, leftover copies of Windows-only filters are cleaned up even when their line endings differ
- Reinstalling plugins has two options (Plugins window):
- Partial installs any package that is missing or out of date, and any missing built-in filter. Everything you changed stays: edited filters and scripts, and filters you deleted. Try this first
- Complete removes the plugin packages and installs them again from scratch, which fixes a damaged package a partial reinstall leaves in place. Every built-in filter and script goes back to how it ships, including ones you deleted; edited copies are saved to
dataconfig emplate-backupsandscript-backupsfirst. Filters you made yourself are never touched - Before, Reinstall overwrote every edited plugin filter with no backup
- Renaming a filter saves it under the new name before removing the old one, so a failed save no longer loses it. Deleting or editing DeHalo Alpha (Old) and Undistort (PyTorch) now works on the right file
- Plugins no longer read as “not installed” on NVIDIA laptops. When
nvidia-smitook more than 3 seconds to wake a sleeping GPU, or failed once, the app decided the machine had no NVIDIA GPU and checked for the wrong package set. It now waits longer and keeps a known NVIDIA GPU through one failed check - TensorRT no longer fails with “bits per sample mismatch” on models that take 32-bit input despite 16-bit weights, such as the bundled TSPAN models (#12)
- The video picker shows MTS, M2TS, TS, M4V, MPG and VOB files, and has an All Files option (#9)
- A duplicated queue item writes to its own file (
name-2.mp4), and an automatically named output follows edits to its item’s chain. Before, a duplicate overwrote the original’s output (#2)- This now also works with a default output folder set, which broke the renaming
- New app icon, in the same teal as the rest of the app and the website
- Descriptive output filenames now describe what actually ran
- Steps are named in the order they run: an AI model by its own name (
2xbndlanimefilmv3, not a scale guessed from the filename), and a filter by what it does (deint,denoise,color,crop…). Before, almost every filter was named by the first word of its title - The resolution and frame rate in the name (
2160p,59.94fps) come from the evaluated workflow, and only appear when they differ from the source. The old guess ignored every resize, crop and second model - A model that is selected but not in the chain no longer adds a scale (
-4x) to a run that never used it - Mask, utility and comparison steps are left out, each tag appears once, and a long name drops whole steps instead of cutting a word in half
- Steps are named in the order they run: an AI model by its own name (
- Discord Rich Presence, off by default (Settings)
- The VapourSynth core is pinned to R79, the version every plugin and filter is verified against, and a newer one is put back at launch
- An interrupted plugin install no longer makes every later install fail. Stranded package metadata and half-removed folders are cleaned up first
- Fixed “7-zip exited with code 2” when setup extracted the VapourSynth scripts download
- Compare opens its window again. Before, it ran hidden, holding up to ~1GB
- Filters that build TensorRT engines at runtime no longer look like a frozen app
- A banner names the engine being built, shows progress when the builder reports it, and explains that this is the first run at that resolution; it clears when the build ends, and on every cancel/crash path
- Engine builds are kill-safe: the engine is written to a temp file and renamed into place, so force-closing mid-build can no longer leave a truncated engine that gets reused as a cache hit and permanently breaks the filter
- Builds are recorded in the per-item queue log, and the vs-view launch now evaluates the script first so builds happen under Vapourkit’s UI instead of freezing vs-view’s window
- Covers
vs_temporalfix’s TemporalFix (AI) engine builds too — it builds engines its own way, so its existing build log lines are recognized directly (no progress percentage available, so the banner spins) - Third-party filters can opt into the same banner by printing
[vk-build] begin/progress/endlines to stderr — see the project documentation
- The RIFE and DPIR filter templates now use real TensorRT when the TensorRT backend is selected, instead of ONNX Runtime CUDA
- vs-mlrt builds those engines by shelling out to
trtexec, which the TensorRT pip wheels don’t ship; Vapourkit now installs atrtexecshim that routes the build through its own TensorRT Python API builder (the same one the model importer uses) - The first run at each resolution builds an engine (a few minutes, with the banner above); later runs at that resolution start instantly from the cached engine in
data/vsmlrt-models - The RIFE model packs now also install the
rife_v2model folder, so templates can select the v2 representation with_implementation=2; existing installs fetch it in the background at startup
- vs-mlrt builds those engines by shelling out to
- Python packages are now installed to match your GPU vendor, detected automatically at startup
- NVIDIA: unchanged — CUDA PyTorch,
vsjetpack[full,nvidia], and both vs-mlrt backends (TensorRT + ONNX Runtime) - AMD:
vsjetpack[full,amd](HIP/OpenCL/Vulkan plugins) with the DirectML backend, and no multi-GB TensorRT/CUDA stack - Intel and unrecognized GPUs:
vsjetpack[full,cl,vulkan]with the DirectML backend - PyTorch-based filters (vs_deepdeinterlace) get CPU PyTorch on non-NVIDIA GPUs instead of being broken — slower, but they run
- NVIDIA: unchanged — CUDA PyTorch,
- Installs now clean up packages left over from a different GPU configuration before installing (e.g. TensorRT/cuDNN and CUDA PyTorch when moving to an AMD GPU), including the duplicate ONNX Runtime plugin folder that could otherwise win the autoload race
- The Plugins modal reports “not installed” when the installed package set targets a different GPU than the one detected, so reinstalling repairs it
- Existing NVIDIA installs are recognized as-is and are not forced through a reinstall; AMD/Intel users who installed the old CUDA-only package set are prompted to reinstall to get the correct packages
- Set
VAPOURKIT_FORCE_GPU_VENDOR=nvidia|amd|intel|unknownto override GPU detection - Fix the RIFE and DPIR filter templates failing with
"...models\rife\rife_v4.10.onnx" not found- The old zip-based vs-mlrt shipped its model zoo next to the plugin DLLs; the PyPI wheels don’t, so the vsmlrt RIFE/DPIR wrappers had nothing to load
- The needed packs (RIFE v4.10, DPIR, ~75MB) now download to
data/vsmlrt-modelsduring plugin install, and existing installs fetch them automatically in the background at startup; generated scripts pointvsmlrt.models_paththere so pip reinstalls can’t remove them - Other RIFE model versions can be dropped into
data/vsmlrt-models/rifemanually
- Rework inference backends into self-contained provider modules (
electron/providers/)- Each backend (TensorRT, DirectML) owns its script codegen, model-file resolution, pip packages, plugin health checks, and engine building in one place; adding a backend (NCNN, OpenVINO) no longer touches the rest of the codebase
- The DML/TRT header toggle is now a backend dropdown driven by the provider registry, with the same selection available in Settings
- Backend choice is now per AI-model filter: every filter defaults to “Auto” (follows the app default) and can override it in the expanded filter card; overridden filters show a badge on the collapsed card
- Generated scripts now include a
vk_backend()helper so custom filters follow the app-selected backend; the bundled RIFE and DPIR templates use it (RIFE previously forced DirectML on every GPU, DPIR needed a hand-editednvidia_gpuflag). On the TensorRT selection, script filters get real TensorRT through thetrtexecshim described above - Settings, queue items, and workflow files store a backend id (
tensorrt/directml) instead of theuseDirectMLboolean; existing values migrate automatically on load
- Migrate the entire install path from manual zip downloads to PyPI
- VapourSynth (R79), vs-mlrt (16.1), BestSource, and all of pifroggi’s plugins (
vs_temporalfix,vs_undistort,vs_colorfix,vs_grain,vs_tiletools) now install via pip - Native VapourSynth plugins (akarin, vszip, zsmooth, bestsource, …) arrive automatically as dependencies of
vsjetpack[full,nvidia]and the pifroggi packages, using the NVIDIA and JET vs-wheels package indexes vspipe.exeand the core runtime now come from the VapourSynth wheel inLib\site-packages\vapoursynth; plugins autoload fromLib\site-packages\vapoursynth\plugins- vsjetpack is no longer pinned to 1.1.0 (the old
vapoursynth==72ABI pin is obsolete) vsview[full]is installed with the main plugin step instead of a separate pinned install
- VapourSynth (R79), vs-mlrt (16.1), BestSource, and all of pifroggi’s plugins (
- TensorRT engine building now uses the TensorRT Python API instead of
trtexec(the TensorRT pip wheels don’t ship trtexec)- The Import Model dialog still accepts trtexec-style parameters; unsupported flags are ignored with a warning
- Portable installs that reuse an existing
datafolder are migrated in place: the old portable runtime,vs-pluginsfolder, and bundled script modules that PyPI now provides are cleaned up during setup, and the Python environment is upgraded in place- Existing TensorRT engines were built with an older TensorRT and need rebuilding — the existing vs-mlrt version-change prompt handles clearing them
- NOTE: upgrading a setup install from 0.16.x or older starts fresh (the old installer’s upgrade flow removes the
datafolder) — export your workflows and filters before upgrading, then re-import them - Bundled
vs_deepdeinterlace(not yet on PyPI) and the Hybrid scripts continue to install as before - Groundwork for Linux support: all platform-specific filenames and the site-packages layout are centralized in
electron/constants.ts; the pip install phases are platform-neutral, leaving only the Python bootstrap (and FFmpeg/video-compare downloads) Windows-specific - Fix update checker falsely prompting nightly builds to “update” to the stable release they were cut from
- Nightly version suffixes (e.g.
0.16.1-nightly.2026-05-13) broke the version comparison; nightlies are now only offered stable releases with a strictly newer base version
- Nightly version suffixes (e.g.
- Fix vspipe crashing at startup with
v3bdg: unable to acquire api3 VSAPI, abort- The bundled
fft3dfilter.dllbuild contains its own API3-bridge guard that aborts the process under VapourSynth R79; it is now removed at install (fft3dfilter is unavailable until an API4 build is sourced) - Other API3 plugins load fine through VapourSynth’s compat bridge (with deprecation warnings)
- The bundled
- Replace API3-only bundled plugins with API4 wheels from PyPI: mvtools, CAS, adaptivegrain, WNNM, KNLMeansCL (nlm-cuda), SCXvid, DCTFilter
- Fix vs-mlrt ONNX Runtime CUDA support: both
vapoursynth-mlrt-ort(CPU/DirectML) andvapoursynth-mlrt-ort-cudaship avsort.dlland the CPU-only copy always won the autoload race; the redundant CPU-only folder is now removed post-install (the CUDA build bundles DirectML too) - Bundled plugins now extract with skip-existing semantics so they can never overwrite pip-managed plugin files (several share identical filenames)
- Fix fresh installs on NVIDIA GPUs silently starting in DirectML mode
- A race persisted
useDirectML=trueto localStorage before async CUDA detection resolved, permanently blocking the detection-based default
- A race persisted
- Fix DirectML failing with
open ..._fp16_fp16.onnx failedwhen a TensorRT engine model is selected- The engine→ONNX path mapping now understands the doubled precision suffix of custom-built engines and picks whichever ONNX candidate exists on disk
- Pre-included models now get the same ONNX auto-detection as custom imports when opening the build modal
- Temporal frame count, precision, and static shapes were previously hardcoded (15 channels for any VSR model, precision from filename only), and the frame count was missing from the form entirely
0.16.1
Section titled “0.16.1”- Fix
Cannot read properties of null (reading 'execute')crash when canceling or restarting an upscale during the frame count probe- Same fix applied to the preview-segment path
- Stream BestSource indexing progress during the frame count probe so cold-cache runs don’t look like a hang
- Indexing progress now shows in the same progress bar used on first video load, and is written to the queue item log
0.16.0
Section titled “0.16.0”- Auto-install plugins at the end of setup
- Removes the manual “reinstall your plugins” step required by 0.15.0
- Auto-retries once on transient failure; falls back to Retry / Continue-without-plugins on hard failure
- Add Privacy mode (lock icon in the header)
- Hides preview frames, input/output filenames, queue thumbnails, and queue item names behind clickable veils
- Notification toasts become generic so filenames don’t leak to screen
- Console auto-collapses when privacy is enabled
- Setting persists across launches
- Add descriptive output filenames (enabled by default) — thanks @fs10102020!
- See 0.15.1 entry below for details
- Add no-filters safety
- Persistent banner above the Upscale button when no filters are enabled
- Confirm dialog before upscaling with zero filters
- Removed the old “default-upscale” silent fallback that would secretly run whichever AI model was selected first
- Add BestSource indexing progress bar under the video drop zone on first video load
- Rename Temporal Fix filters
Temporal Fix V2→TemporalFix (AI)Temporal Fix→TemporalFix (Classic)
- Fix “Failed to initialize VSScript” on fresh installs
- Pinned
vapoursynth==72andvsjetpack==1.1.0so pip doesn’t silently upgrade to an ABI-incompatible Python binding
- Pinned
- Fix vsview failing to launch (switched from
python -m vsviewtovsview.exe) - Fix descriptive-naming regen ignoring the configured default output folder
- Fix duplicate
video-index-progressterminal event in theget-video-infohandler - Fix content-length parseInt type error under newer
@types/axios
0.15.1
Section titled “0.15.1”- Add descriptive output filenames (enabled by default)
- Output filenames now reflect your workflow instead of using a generic
_processedsuffix - Example:
EpisodeName-colorimetry_denoise_4x_resize2160.mkv - Includes applied filters, AI model scale, and output resolution
- Automatically truncates to 32 characters if too long
- Manually selecting an output path disables auto-generation for that file
- Toggle available in Settings under Processing
- Output filenames now reflect your workflow instead of using a generic
- Fix TypeScript compilation error in
electron/vsMlrtManager.ts
0.14.0
Section titled “0.14.0”This release in in dedication to my Mom. She passed away on 1/1/26 after a long battle with small cell lung cancer. Rest in peace
- Adds over 150 new filters, including many from Hybrid!
- Replaces the filter selection dropdown with a new modal
- This has a tag system to make finding filters easier
- It also has a search!
- Fixes the lag and focus issues present in previous versions of Vapourkit
- You can now have 20+ filters expanded in your workflow and it will not slow down!
- The bug that required alt tabbing to fix is no longer present
- Adds vse-previewer! This allows for realtime previewing of how your video will turn out without having to render the whole thing
- Replaced vse-previewer with vs-view, a much more modern solution that has more features and is more robust
- Adds ESC button support to all pop up modals
- Added vs_grain
- Replaces pop up dialogs with notifications within the GUI
- Change legacy “TSPAN” text to “VSR”. This change was made in conjunction with releasing TFDAT, which effectively replaces TSPAN + TSPANv2
- Lots of GUI tweaks and bug fixes to make it more cohesive and consistent
- Add option to Settings to set a permanent output path for all videos
- Add option to duplicate queued items, and overhaul the behavior of the queue button
0.12.2
Section titled “0.12.2”- Fix BF16 engine names (previously appended _fp16 when it’s _bf16)
- Remove unused code
- Hide Validate button during processing
- Rename Color Matrix to Colorimetry as it does more than the name implies
- Improve GUI responsiveness
- Change the way Developer Log works. It now polls main.log instead of printing directly to the UI
- This also has the added benefit of fixing formatting issues that were present previously
- Include 2x_bndl_animefilm_v1.5 FDAT
0.12.1
Section titled “0.12.1”- Overhaul validation method. It will no longer automatically run in the background, instead you must manually run it if desired
- Fix issue where “Same as Input” was the default for fresh installs of Vapourkit
- Fix broken AV1 presets
0.12.0
Section titled “0.12.0”- Remove simple mode to (ironically) simplify codebase
- Move encoding settings from Settings panel to the right pane, and add easy toggles for common settings
- Add RIFE filter for frame interpolation
- Overhaul vkfilter parsing to be more robust
- Fix GUI design inconsistencies
- Reverted to vs-mlrt 15.13 as 15.14 has noticeably lower performance
- Update vs_tiletools
- Update zsmooth to 0.15
0.11.0
Section titled “0.11.0”- Change the way file names are handled for models
- Overhaul the design of the header to save space
- Move the DirectML toggle from Settings to the header
- Change the default model type from
vsrtoimageto reduce chance of error for models without metadata - Fix audio clipping when using segments
- Allow users to customize video-compare settings in the Settings menu
- Force kill trtexec and vspipe processes when beginning workflow processing
- Add MC_Degrain filters
- Change to vs-mlrt version 15.14 from 15.13 RTX
- Add detection for vs-mlrt version changing (will not take effect in this release)
- Add BF16 toggle when building TensorRT models
- Add automatic static + shape detection when building TensorRT models
- Add update system for vs-mlrt plugin
- Update vs_undistort to version 2.0.0 (thanks tepete!)
- Update queue panel behavior and design to be more intuitive
0.10.2
Section titled “0.10.2”- Implement segment selection. Users can now select a small segment of a video to process and preview!
- When using this mode, the comparison buttons are disabled
- Fix issue where highlighted code wasn’t visible in the Filter panel
- Minor bug fixes
- Fix GUI lag
- Add search function to Manage Models menu
0.10.1
Section titled “0.10.1”- Redesign “Show Queue” button and change location
- Allow the user to change the color space the output video is saved in
- Rework the Settings menu to be easier to use
- Fix the way videos are displayed when processing is complete
0.10.0
Section titled “0.10.0”- Add batch video processing support
- Add ability to launch comparisons in from queue list
- Add experimental update checker
- Add force stop button for stuck processes
- Clean up About menu
- Improve changelog display
- Fix processing bug with batch processing
- Update zsmooth plugin to 0.14
- Overhaul internal code for start/stop processing button
- Overhaul Video Info Panel
- Add documentation for Batch Processing
- Shrink queue panel and clean up unused files
- Fix color scheme of syntax highlighting
- Clarify precision options in GUI
- Add syntax highlighting for filters
- Add section for license information of included models
- Add link to GitHub page in About window
- Fix Logo in header being misaligned in Simple Mode
- Fix program icon being missing
- Fix race condition with filters
- Fix “Start Processing” button not working when Advanced mode AND TensorRT mode are enabled without any built engines
- Expose previously forced ffmpeg arguments to be edited
- Remove automatic CUDA detection, turned out to be a driver based issue
- Add menu to manage models (modify metadata, change precision, rename, delete)
- Refactored `main.ts
- Change preview to PNG from mJPEG to improve compatibility and avoid YUV errors
- ACTUALLY fix —fp32 being added to trt build command
- Move ffmpeg settings to Settings menu, remove old config file
- Add automatic detection for CUDA versions, and install different Pytorch versions depending on that
- Update VapourSynth and filter templates (thanks tepete)
0.8.8:
Section titled “0.8.8:”- Add custom engine build command support for tensorrt
- Rework “Import Model” interface
- Hopefully fix scrolling bug on right pane when processing a video
0.8.7:
Section titled “0.8.7:”- Add labels on header buttons
- Relabel certain buttons to make their function clearer
- Prevent processing when ONNX model is selected in TensorRT mode
- Fix model auto select after building engine
0.8.6:
Section titled “0.8.6:”- Fix progress bar in setup screen, round ffmpeg download to nearest integer
- Fix plugins being missing
- Fix workflows not notifying the user of missing models
- Fix workflow names including the extension when loaded
0.8.5:
Section titled “0.8.5:”- Static engine support
- Adds version number to about menu and window title
- Fixes ffmpeg and vspipe handling when stopping processing, prevents corrupt files
- Added animations and progress bar text when ffmpeg is stopping
- Adds MOV as an output option
- Rolled back to version 0.12 of zsmooth to fix temporalfix
- Fixed visual bug with num_streams slider