Open beta

Test WAVScribe before it's released

WAVScribe is a Windows desktop application for reading, editing, and batch-processing the metadata inside WAV files. It isn't released yet, and a limited group of testers gets in first.

The WAVScribe main window with a real WAV library loaded, showing the metadata editor, chunk view, and waveform

WAVScribe reads, edits, and batch-processes the metadata inside WAV files: the broadcast, production, and library fields that sound tools rely on. This is the open beta, and a chance to put it through real work on your own files before it launches.

Seats are limited, and the testing window is a fixed two weeks. You get the build, use it on the files you actually work with, and tell us how it held up.

You don't need to be a working professional. Enthusiasts and hobbyists are just as welcome. The only thing that matters is that you regularly work with audio metadata and can give feedback we can actually use.

What you get, and what we ask

Testers who put in real testing and feedback get a free WAVScribe V1 license when the beta ends. Here is what that means in practice, so nobody is surprised later.

What counts as real feedback

  • Bug reports, with enough detail that we can find the problem: what you did, what happened, and what you expected.
  • Compatibility notes: how WAVScribe handled files from your recorder, editor, or library tools.
  • Workflow feedback: where it fit the way you work, where it fought you, and what was confusing the first time.
  • A genuine "I spent a few hours trying to break it and couldn't" report, telling us what you threw at it.

You do not need to find a bug. A thorough report that everything worked is just as valuable, as long as it shows you actually used the program on real files.

What doesn't count

  • Installing it and going quiet.
  • A single line like "works great" or "cool app" at the end of the window.
  • Feedback sent after the beta has closed.

The shape we are hoping for is a couple of messages during the two weeks, sent whenever something is fresh. Two short emails beat one polished report on the last day. This isn't homework and there is no required format, but silence isn't feedback, and the license is a thank-you for feedback.

We will also send a handful of questions along with the build that we would like answered by the end of the window. Answering them is part of this.

Whether feedback meets this bar is our call to make, and we make it when the beta closes. If you are partway through the window and not sure you have done enough, just ask.

Apply for a seat

If that sounds like you, tell us a little about your setup. We read every application.

Read the beta terms

Beta terms

  1. Confidential until launch. The build and anything shared with you during the beta stays between us until WAVScribe is publicly released. Please don't post public reviews, videos, or walkthroughs of the beta build - rough edges in pre-release software read as the finished product once they're online. After launch you're free to talk about it as you like.
  2. Testing use only. The pre-release build is licensed to you personally for testing. Don't share the installer, the download link, the password, or your license key. Not for production deliverables you'd hand to a client - your own library work is fine.
  3. It's pre-release software. It's been through heavy QA, but treat it accordingly: back up any files before batch operations, and expect the occasional rough edge. Finding those is rather the point. WAVScribe is provided as-is for the beta, and we can't take responsibility for data loss.
  4. Your feedback helps build the program. Anything you report or suggest may be used to improve WAVScribe, with no obligation or claim on either side.
  5. Either of us can stop anytime. If life intervenes or it's not for you, no hard feelings - just let us know.
  6. What you get, and what earns it. Your beta license key expires on its own at the end of the beta. Testers who put in real testing and feedback get a free WAVScribe V1 license when the beta ends. What counts: bug reports with enough detail to find the problem (what you did, what happened, what you expected); compatibility notes on how WAVScribe handled files from your recorder, editor, or library tools; workflow feedback on where it fit how you work and where it fought you; or a genuine "I spent a few hours trying to break it and couldn't" report telling us what you threw at it. We'll also send a handful of questions with the build that we'd like answered by the end. You do not need to find a bug - a thorough report that everything worked counts, as long as it shows you actually used the program on real files. What doesn't: installing it and going quiet; a single line like "works great" at the end of the window; feedback sent after the beta has closed. Whether feedback meets this bar is our call, made when the beta closes. If you're partway through and unsure whether you've done enough, just ask.

Seats are limited. We'll email you if you're selected - we can't reply to every application individually.

Something went wrong submitting the form. Please try again, or email the answers you entered above to contact@wavscribe.com and we'll add your application directly.

Thanks - your application is in.

Seats are limited, and we're placing testers as applications come in. If you're selected, you'll hear from us by email with the build and everything you need to get started.

We won't be able to reply to everyone individually. If you haven't heard from us within a few days of the beta starting, the seats were filled - no reflection on you, and we appreciate you putting your name forward.

WAVScribe launches later this year.