Support
Email danilson.daveigaramos.pro@gmail.com for beta access, installation help or a problem with a check.
Support policy
During the private beta, support is provided by the developer by email, on a best-effort basis, without a guaranteed response time and without live support. When sales open, Studio licenses include priority email support with a reply within one business day; other plans get email support.
Installation
System requirements, installation steps and what to do if macOS won’t open a beta build are on the download page. Windows isn’t available yet.
What the statuses mean
| Status | Meaning | Example |
|---|---|---|
| PASS | The check ran to completion and found no problem. | Every file listed in the manifest is present and byte-identical. |
| FAIL | A confirmed problem. | Media the Premiere project uses is missing from the folder; a received file differs from the manifest. |
| REVIEW | Something needs your judgement before you send or accept. | A file name Windows won’t accept; extra files in a received folder; a Premiere project saved by an unverified version. |
| UNSUPPORTED | Bundvera can’t perform this check for this format or configuration. | Fonts and plugins; dependencies inside After Effects or DaVinci Resolve projects. |
| INCOMPLETE | The check could not finish. | A drive was disconnected or the scan was cancelled. Nothing is reported as missing until a scan completes. |
Supported formats
| Project type | Folder and manifest verification | Project dependency analysis |
|---|---|---|
| Any folder of files | Supported | Not applicable |
Adobe Premiere Pro (.prproj) | Supported | Experimental: media file references |
Adobe After Effects (.aep, .aepx) | Supported | Planned, not supported |
DaVinci Resolve (.drp, project archives) | Supported | Planned, not supported |
Final Cut Pro libraries (.fcpbundle) | Supported | Planned, not supported. Files inside the library are verified as files. |
Fonts, effects, third-party plugins and whether a project opens are never checked, for any format.
Large projects
- Start with Quick Preflight: it doesn’t read file contents, so it’s fast even on very large projects.
- Deep Verification reads every byte. Expect it to take roughly as long as reading the whole project from its drive. You can keep using Bundvera while it runs, and cancel at any time. A cancelled check never produces a manifest.
- Keep external drives connected and stop your Mac from sleeping during long checks. If a drive disconnects, the result is marked INCOMPLETE, never “missing”.
- For spinning disks and network shares, lower the number of parallel file reads in Settings.
- Download cloud files fully before checking; online-only placeholders aren’t the real files.
Common messages
The manifest was created by a newer version of Bundvera
Update Bundvera, then open the manifest again.
The manifest was modified or damaged after it was created
The manifest no longer matches its own integrity digest. Ask the sender to send the original again through a channel you trust.
An external drive was disconnected
Reconnect the drive and check again. Results from before the disconnection are kept but marked INCOMPLETE.
A file changed while it was being checked
Another app was writing to the file. Close it, then check again.
Unverified Premiere Pro project version
The project was saved by a Premiere version Bundvera hasn’t been validated against. The media references were still read; review the result and open the project to confirm.
Names that Windows doesn’t allow
Bundvera flags names such as CON.mov, names ending in a dot or a space, and characters such as : or ?. Rename those files before sending to someone on Windows.
Reporting a problem without sharing footage
You never need to send client media to get help. In Bundvera, open Settings and export a diagnostic file. It contains the app version, your system, your settings and recent error codes, and no file names, folder paths, manifests or fingerprints. You can open it and read it before sending it.
- Tell us what you expected, what happened, and the exact message Bundvera showed.
- Attach the diagnostic file if you can.
- If a sample helps, send a synthetic example rather than a client project.
License recovery
First check Settings, then License, in Bundvera, and any license file you downloaded. If a payment went through but you’ve lost the key, use the license recovery page or return to your payment confirmation link. Don’t pay again to recover a key.
Refunds
Bundvera doesn’t sell licenses yet. The draft refund policy offers a full refund within 14 days of purchase. If you believe you were charged for Bundvera, email us with the payment date and receipt reference. Never send card details, passwords or a full license key.
Privacy
Bundvera processes your project files only on your computer. The privacy policy explains what data exists and where it goes, and the security page explains how untrusted files are handled.