Repository navigation
Windows Build
Previous Page Installation | Home
Next Page MacOS Build | Linux Build
TBC Tools (
ld-analyse) — the GUI analysis & export hub of the tbc-tools suite.
These instructions cover installing and building tbc-tools only — the post-decode TBC processing toolchain. It consumes .tbc files produced by the RF decode projects; the decoders themselves are separate repositories and are not covered here.
- VHS Decode (Python)
- Tape Decode (Real-Time Rust Version)
tbc-tools ships self-contained portable zip releases for Windows, in both x86_64 and ARM64:
Each release zip bundles the full GUI + CLI tool suite, the Qt6 runtime, MSVC 2022 (VC143) CRT DLLs, FFmpeg + FFprobe, FLAC, ONNX Runtime, the self-contained tbc-video-export, and (x86_64 only) the CUDA 11.8 + cuDNN 8.9 runtime DLLs for ONNX GPU acceleration. A qt.conf and the Qt platform plugin are included so the GUI starts on a clean machine.
-
Microsoft Visual C++ 2022 Redistributable — usually already installed by other apps. The VC143 CRT DLLs (
vcruntime140.dll,vcruntime140_1.dll,msvcp140.dll) are also bundled in the release.
No other system dependencies are required for the portable release.
-
Download the
tbc-tools_windows_x86_64(orarm64).zippackage and extract all files into a folder (e.g.tbc-tools). -
Place it on your desktop or a drive you are working from. All tools and scripts inside are self-contained, so they can be run from any location as long as they stay together in one folder.
-
Use
CMD, PowerShell, or Windows Terminal. For AI/LLM assistance, Warp Terminal works too. -
With a terminal open inside the
tbc-toolsfolder, run the GUI:ld-analyse.exeThe CLI tools are invoked the same way, for example:
ld-chroma-decoder.exe --help tbc-video-export.exe input.tbc output
Tip
To make ld-analyse the default app for .tbc files: right-click a .tbc → Open with → Look for another app on this PC → browse to ld-analyse.exe → Always use this app to open .tbc files.
Tip
Dark mode for ld-analyse can be enabled with ld-analyse.exe -style fusion via CMD, or by editing a shortcut to add that flag.
From inside ld-analyse, use the Export page to chroma-decode and encode to a video file via FFmpeg. You can also drive the same export from the command line with the bundled tbc-video-export.exe:
tbc-video-export.exe input.tbc output
See the Analyse & Export page for full usage on export profiles, framing options, codecs and audio muxing.
This is the workflow to manually build the tbc-tools suite from source on Windows. It mirrors the official Windows CI (.github/workflows/build_windows_tools.yml).
- Git
- Microsoft Visual Studio 2022 with the C++ workload (the build uses the MSVC VC143 toolchain)
-
CMake 3.31.x — pin to CMake 3.x;
fftw3does not yet support CMake 4.x -
vcpkg — the build uses a pinned vcpkg commit and the
vcpkg.jsonmanifest -
Python 3.11 — only needed to build the self-contained
tbc-video-exportvia PyInstaller
git clone https://github.com/harrypm/tbc-tools.git
cd tbc-tools
git submodule update --init --recursive
Clone vcpkg and check out the pinned commit, then bootstrap it:
git clone https://github.com/microsoft/vcpkg.git vcpkg
cd vcpkg
git checkout d30fdf55cfca16e12bc3ad99cbc615997014b61b
.\bootstrap-vcpkg.bat -disableMetrics
cd ..
$env:VCPKG_ROOT = "$PWD\vcpkg"
The manifest (vcpkg.json) pulls: qtbase (with concurrent), qtsvg, fftw3, libflac, ffmpeg, sqlite3.
Open the x64 Native Tools Command Prompt for VS 2022 (or a PowerShell with the MSVC environment loaded) and run:
cmake --preset vcpkg `
-DCMAKE_BUILD_TYPE=Release `
-DUSE_QT_VERSION=6 `
-DBUILD_PYTHON=false `
-DVCPKG_TARGET_TRIPLET=x64-windows `
-DVCPKG_APPLOCAL_DEPS=ON `
-DBUILD_TESTING=OFF
cmake --build --preset vcpkg --config Release
For ARM64, use the vcpkg-arm64 preset and the arm64-windows triplet (from an ARM64 VS prompt on Windows 11 ARM):
cmake --preset vcpkg-arm64 `
-DCMAKE_BUILD_TYPE=Release `
-DUSE_QT_VERSION=6 `
-DBUILD_PYTHON=false `
-DVCPKG_TARGET_TRIPLET=arm64-windows `
-DVCPKG_APPLOCAL_DEPS=ON `
-DBUILD_TESTING=OFF
cmake --build --preset vcpkg-arm64 --config Release
The built binaries land in build\bin\.
Note
The first vcpkg build downloads and compiles Qt6 and FFmpeg from source, which takes a long time (many hours on a slow machine). Subsequent builds reuse the vcpkg binary cache.
Note
Out-of-source builds are enforced by CMakeLists.txt — always build in build\ (or another separate directory), never in the source tree.
The nnTransform3DCUDA chroma model uses ONNX Runtime. For x64, download ONNX Runtime 1.18.1 (onnxruntime-win-x64-gpu-1.18.1.zip), extract it, and point CMake at it:
$env:ONNXRUNTIME_ROOT = "C:\path\to\onnxruntime-win-x64-gpu-1.18.1"
For ARM64 use the CPU-only onnxruntime-win-arm64-1.18.1.zip package (no CUDA on ARM64).
Note
On x64, onnxruntime_providers_cuda.dll imports the CUDA 11.8 + cuDNN 8.9 runtime DLLs (cudart64_110.dll, cublas64_11.dll, cublasLt64_11.dll, cufft64_10.dll, cudnn64_8.dll and the cudnn_*_infer64_8.dll sub-libraries). Without these next to the exe, ONNX Runtime silently falls back to the CPU EP — no GPU acceleration. The official release bundles them; a manual build must stage them into the output directory by hand.
To assemble a portable folder equivalent to the official release, copy from build\bin\ and the vcpkg install tree:
- all
*.exeand*.dllfrombuild\bin\ - the
vendor\tree (Auto Audio Align + vhs-teletext) frombuild\bin\vendor\ - Qt6 plugins from
build\vcpkg_installed\<triplet>\Qt6\plugins\ - a
qt.confwithPrefix = .andPlugins = . - the MSVC VC143 runtime DLLs (
vcruntime140.dll,vcruntime140_1.dll,msvcp140.dll) -
sqlite3.dllfrombuild\vcpkg_installed\<triplet>\bin\ - FFmpeg + FLAC binaries
- the PyInstaller-built
tbc-video-export.exe(built fromsrc\tbc-video-exportviapyinstaller\build_windows.py)
Previous Page Installation | Home
TBC Tools Wiki - © 2026 Harry Munday