Public qualification is pending.
App platform is one part.
| Environment | Reported context | Public-package qualification |
|---|---|---|
| Windows | Internal native development build | Not qualified for public distribution |
| macOS | Internal native development build | Not qualified for public distribution |
| Other OS / architectures | No advertised support in this foundation | Not assessed / not offered |
This is a qualification-status table, not minimum hardware advice. No installer, architecture or operating-system-version support is inferred from compiling source.
Resolve edition, version and route matter.
| Combination | What needs qualification |
|---|---|
| Resolve Free | Actual supported transport/setup, destination target, rendered/editable output and persistence |
| Resolve Studio | Exact external/local route, output, persistence and recovery |
| Mac or Windows counterpart | Its own native execution, media handling and edition proof |
| Other Resolve versions | Revalidation when APIs, media behaviour or routes change |
An internal Free-compatible route and a Studio route can differ. Do not change scripting/security preferences based on this generic matrix. Use the instructions for the exact package and route.
A client must do useful editing.
Client qualification includes setup, state discovery, completion, inspection, revision after a human change and reconnect/recovery. A connection badge or generic MCP support is not sufficient. Named client/version/OS records are not assigned as publicly supported here.
Check the content you actually use.
- Font availability, style, wrapping and language shaping.
- Image dimensions, alpha and colour interpretation.
- Video/audio container, codec, rate, duration and alignment.
- Path/effect/animation support in editable destination output.
- Original-source and proxy dependencies.
A file extension does not establish admission or export support. Use representative content and inspect the actual result.
Every future supported row needs context.
Record app stage/version, exact candidate/package, OS/architecture and relevant hardware, Resolve edition/version/transport or client/version, scenario/date and observed limits. Recheck affected proof when the combination changes.