PrismCore / Project

Support and contact

Where to ask questions, report bugs and get integration help for PrismCore, and what to include so a report can be reproduced.

GitHub Issues

Questions, integration help and bug reports go to GitHub Issues on the PrismCore repository. Shipping something on PrismCore? Open an issue and it can be listed among the apps that use it.

Email

For anything that does not belong in a public issue, write to support@aetherplayer.com.

What to include in a bug report

Half of what the engine decides depends on the FFmpeg build and the exact source, so a report with these attached can usually be reproduced without a round of questions:

  1. The diagnostic report — try await session.diagnosticReport().jsonData(), or PrismCoreEngine.diagnosticReport(for:decision:) for a source that never got a session. It is redacted for public issues (no header values, query strings, tokens or local paths); if your URLs carry a token in the path, remove it first. See Diagnostics.
  2. FFmpegBuild.summary from the build your app ships.
  3. The PrismCore version — PrismCoreVersion.current — and the platform and device.
  4. A reproduction from a terminal, if you can: swift run prismcore-cli probe --json <url-or-path>, or serve --report report.json for a playback that fails.
Swift
let report = try await session.diagnosticReport().jsonData()
let summary = FFmpegBuild.summary
print(PrismCoreVersion.current, summary, String(decoding: report, as: UTF8.self))

Using Aether?

If you are a viewer using the Aether app rather than a developer integrating the engine, see Aether troubleshooting or the support page.