RenditionProof

YOUR FIRST LOCAL CHECK

From download
to your first report.

Use the synthetic example first. It deliberately contains a duration difference, so you can learn how to read a finding without using customer media.

1. Download and open

On Windows 11 x64, download the EXE from the download section. It is a self-extracting package containing the desktop app and its runtime files. Read and accept the included license, then choose Extract and open. It stores the complete package under your local app folder, without administrator rights.

Alternatively, extract the portable ZIP into its own writable folder, then open RenditionProof.exe. Keep the files and subfolders together. Your media and reports are separate from this program folder.

This is an unsigned preview. Windows may warn about or block it. Verify the checksum and follow your device or organization policy. A checksum verifies matching bytes; it does not replace a trusted publisher signature.

Verify a download

Download the matching .sha256 file. In PowerShell, calculate the hash and compare it with that file:

Get-FileHash "$env:USERPROFILE\Downloads\RenditionProof-0.37.25-win-x64.exe" -Algorithm SHA256

2. Configure external media tools

Media inspection uses FFprobe. Decoded audio checks also use FFmpeg. They are not bundled with RenditionProof.

Obtain a Windows x64 build through the official FFmpeg download page, review its license and extract it into a separate local folder. Follow your organization’s codec and tool policies.

  1. Open RenditionProof and click Get started.
  2. Browse to your installed ffprobe.exe and ffmpeg.exe, usually in the tool’s bin folder.
  3. Click Check tools. Correct any missing or invalid paths before continuing.

3. Create the example

  1. In Get started, click Create example. This creates a separate local synthetic example.
  2. Click Continue to load its project inputs.
  3. Click Check setup, then Run scan.
  4. In Findings, select the duration Warning. The master is three seconds and the rendition is four seconds: this warning is intentional.
  5. Read What to do next, then click Open report to view the local HTML report.

4. Check your own delivery

Choose Project → New project. Select one approved master file or folder. Add each rendition with its locale, such as fr-FR, and explicitly confirm the mapping after checking it. Use Scan settings to review the expectations; tighter thresholds require your own workflow calibration.

Choose an independent report output folder with Save to…, save the project to its own JSON or YAML file, then run Check setup and Run scan. Use filters, asset details and the Unknown summary to review the recorded evidence. You can reopen a saved JSON report with History….

Understand the result

Pass

The recorded evidence meets this check’s expectations.

Warning

A condition needs manual review and may be legitimate.

Fail

A check found evidence that does not meet its expectations.

Unknown

Evidence is missing, ambiguous or otherwise insufficient.

None of these statuses is a translation-quality verdict or a final delivery approval.

Troubleshooting and removal

If tools are missing, reopen Get started and check their complete executable paths. If a mapping is Unknown, verify and confirm it. If a report destination is rejected, choose a separate writable local folder outside the source input directories.

Use Advanced options → Export diagnostics for a redacted local diagnostic ZIP. Inspect it before sharing. Runtime logs can contain full paths and should be reviewed separately.

The EXE is a portable extractor, not a system-wide installer. To remove the program, close it and delete its extracted version folder or your portable ZIP folder. Saved source media, reports and local preferences are separate and are not automatically deleted.

Back to downloads