Tester requirements

What to prepare before testing.

ReelCool Studio is close enough to begin controlled workflow testing. These requirements explain who is useful now, what setup details matter, and what the tester form should not collect.

Operating system

  • Windows is the primary near-term testing target.
  • macOS and Linux interest is useful, but exact support may differ before launch.
  • Testers should report the OS version they use.

Local creative tools

  • Final editing can happen in VEGAS Pro, DaVinci Resolve, Premiere, or another editor.
  • External helper tools remain user-managed.
  • ReelCool Studio does not bundle ComfyUI, FFmpeg, models, or custom nodes.

Project readiness

  • A finished or nearly finished song is ideal.
  • A lyric sheet helps the app structure the project.
  • Existing visual references, mood notes, or shot ideas make feedback more useful.

Hardware notes

  • GPU capability matters for local AI workflows, but exact minimums are still being validated.
  • Testers should document workstation specs when possible.
  • Low-spec testers are still useful for setup and workflow feedback.

Best-fit testers

Real projects are more useful than curiosity clicks.

The most useful testers have a song, lyric sheet, editing workflow, AI-video workflow, or clear production problem. The first testing phase is about finding friction in the real process.

If someone only wants to see whether the app exists, that is less useful than someone trying to push a song through planning, prompts, renders, review, and editor handoff.

Do not collect

Keep the Tally intake form lightweight and safe. It should not ask for sensitive or legally complicated information.

  • Payment information
  • Account password sharing
  • Private API keys
  • Unreleased music rights documents
  • Commercial clearance guarantees
  • Uploading model weights or third-party binaries to ReelCool Studio

Current boundary

The website collects tester interest. The app testing process comes later by email.

Tester selection, build distribution, setup instructions, license behavior, and support flow should remain manual until the app is ready for a controlled release process.

View launch roadmap