Webfilmland QC User Guide

Webfilmland QC is a desktop quality-control application for video, audio, caption, and delivery preflight checks. It creates audit-ready HTML, PDF, and JSON reports for technical review and customer delivery evidence.

This guide describes the customer release build distributed as an Apple Developer ID signed, notarized, and stapled macOS .pkg installer. Windows customer releases are distributed as a compiled .exe artifact, not as a source-code archive.

Current Release Evidence

The current macOS customer package is published at:

Release checks completed for this build:

Product Positioning

Webfilmland QC is a professional preflight QC assistant for indie films, web masters, marketplace delivery, archive review and post-production teams. It is designed to catch common technical problems before upload, client delivery, archive handoff or external certified QC.

It is not marketed as a legal replacement for Baton, Vidchecker, Harding or a broadcaster-certified final QC workflow. Internal detectors and FFmpeg-based checks provide advisory evidence, while certified results must come from certified external engines where required by the delivery contract.

What Webfilmland QC Can Do

Webfilmland QC can help a professional team find common technical problems before a master is uploaded, delivered to a client, archived, or sent for external certified QC.

Core capabilities:

Good uses:

Limits:

Downloads

Stable customer download links are served from the Webfilmland license server:

The macOS link points to the latest published signed, notarized, stapled PKG installer. The Windows link points to the latest published compiled .exe after a Windows build has been created and published.

System Requirements

The signed app includes its required runtime dependencies, including OpenCV (cv2), FFmpeg/FFprobe, PySide6, NumPy, audio/caption libraries, report generation libraries, and the bundled AI/QC runtime.

Installation

Because the customer build is Apple Developer ID signed and notarized, macOS Gatekeeper should allow normal launch without unsafe bypass steps.

Windows Release

Windows customers receive a compiled Webfilmland_QC-<version>-build-<build>-windows.exe. Do not distribute the repository, Python files, virtual environment, build folder, or source tree to customers. The executable is built with PyInstaller in one-file/windowed mode so the release artifact is an application executable rather than a folder of source files.

Python desktop apps cannot be made impossible to reverse engineer, but customer builds should avoid shipping readable source files. For stronger source-code protection later, use a native compiler/obfuscation build such as Nuitka commercial mode or a compiled extension boundary for sensitive detector logic.

First Launch

At startup, Webfilmland QC checks that the packaged runtime is complete. If a required component is missing or damaged, the app shows the exact problem before starting QC.

During development or source-based use, the checker can ask before installing missing Python packages. In the signed customer PKG, required dependencies are expected to be bundled already.

Basic Workflow

Scan Modes

Fast Mode

Use Fast mode for quick triage during editing, conform, or early delivery prep.

Best use: early checks, quick customer screeners, obvious technical mistakes.

Deep ML Mode

Use Deep ML mode when you want sampled deterministic QC plus advisory AI review.

Best use: stronger preflight before final export or before human QC review.

Final Full Precision Mode

Use Final Full Precision before delivery sign-off.

Best use: final delivery preflight, long-form masters, customer-facing QC evidence.

Long-Form Runtime Expectations

QC speed depends on codec, resolution, disk speed, enabled checks, CPU, and whether the media is HD, UHD, HDR, IMF, ProRes, H.264, HEVC, or MXF.

General expectations:

For a 90-minute film, use Fast or Deep ML during development and Final Full Precision only for final sign-off or selected problem ranges.

Live QC Progress

The Live QC panel prints what the app is doing:

If the app is running a long Final Full Precision job, Live QC should continue showing progress so the operator can see that analysis is active.

Delivery Presets

The app includes source-linked delivery presets for:

Reports include the selected preset, thresholds used, and official/public or partner-official spec-source references where available.

Platform requirements can change. For contractual delivery, always confirm the active client or platform specification before final acceptance.

PSE Certification Policy

PSE findings are deliberately separated into advisory and certified evidence:

The app only shows Certified PSE: PASS when an imported external PSE report from a recognized professional engine, such as Harding, Baton, Vidchecker, Telestream or Aurora, confirms PASS. PEAT or unknown/free tools can be imported as review evidence, but they do not create a certified PASS claim.

Trial and Data-Sharing Option

Paid licenses are issued after order review and payment confirmation. A 90-day research trial may be issued when the user explicitly consents to share selected QC data for detector training and product improvement.

Data sharing must be opt-in. Shared material may include QC reports, measured values, snapshots, review decisions and selected media samples only when the user has the legal right to share that material. Trial users can be asked to remove or anonymize confidential client data before sharing.

IMF Package Preflight

For IMF package checks, select an IMF preset and load the package folder.

The app checks:

This is an IMF preflight, not a replacement for a formal studio/platform certification process.

Reports

After QC, the app saves:

Reports include:

Reviewing Findings

Use FAIL findings for delivery-blocking issues unless a qualified reviewer marks them as accepted. WARN findings usually require review but may be acceptable depending on the content and delivery spec.

During development and pilot use, keep notes on:

This evidence improves future presets and helps build trust with buyers.

Support Bundle

If a customer reports a crash, wrong result, or unexpected behavior, create a support bundle from the application support tools or by running the included support-bundle command in the development environment.

The support bundle is designed to include:

It does not include source media by default.

Troubleshooting

App Does Not Open

Confirm you are using the signed/notarized customer PKG. If macOS still blocks launch, download the PKG again and make sure it was not modified after signing.

QC Seems Slow

Check Live QC. Long Final Full Precision runs can be slow because every decoded frame is inspected. For early review, use Fast or Deep ML mode.

Missing Dependency Message

In a signed customer build this usually means the app package is damaged or an incomplete build was distributed. Reinstall from the latest signed PKG.

Report Does Not Open

The report is still saved on disk even if automatic opening fails. Use the path shown in Live QC or the report preview.

Best Practice