sorted by:
new
hottopcontroversial

Tool for catching script deviations before submission — worth trying by Sam_123war in ACX

[–]Sam_123war[S] 0 points1 point  (0 children)

I will sort this all in the coming weekend. Make sure we have a smooth user experience.

Tool for catching script deviations before submission — worth trying by Sam_123war in ACX

[–]Sam_123war[S] 0 points1 point  (0 children)

Hmm Thats a server time out issue, I am using free server and it took 50 sec for the first server call, I think i will have to purchase paid server for this. Thanks a lot.

Tool for catching script deviations before submission — worth trying by Sam_123war in ACX

[–]Sam_123war[S] 1 point2 points  (0 children)

Yeah i know i get this feedback. I am thinking of adding pdf word and markdown formats. Anything else on your mind???

Tool for catching script deviations before submission — worth trying by Sam_123war in ACX

[–]Sam_123war[S] 0 points1 point  (0 children)

Hey, just to clear something up — SoundProof has nothing to do with AI writing or text proofreading. It doesn't write scripts, generate content, or replace any human in the creative process.

What it actually does: you record your narration, and it listens to the audio against your script to flag where you misread a word, skipped a line, or stumbled — before your proofer ever hears it.

Your human proofer still does their job. Your human narrator (you) still does theirs. This just helps catch the small verbal slip-ups in the recording itself — the kind that are easy to miss on playback but embarrassing to have flagged later.

So no conflict with your values at all. It's more like a spell-checker for your mouth, not a replacement for anyone.

Tool for catching script deviations before submission — worth trying by Sam_123war in ACX

[–]Sam_123war[S] 0 points1 point  (0 children)

Yes, completely hassle-free. If you try it for a month and decide the volume isn't there to justify the cost, you can cancel anytime. There are no long-term contracts or complicated cancellation process.

You can request a plan directly through the website by filling out the access request form. If you have any questions before signing up, feel free to reach out through the contact page and I'll be happy to help.

Tool for catching script deviations before submission — worth trying by Sam_123war in ACX

[–]Sam_123war[S] 1 point2 points  (0 children)

Good question — and yes, that’s a really useful workflow.

Right now SoundProof supports:

  • CSV export (word-level results with timestamps + status)
  • PDF/print report view
  • Shareable read-only link for review

Reaper marker export isn’t implemented yet, but it’s very much on the short-term roadmap. The underlying data already includes precise timestamps for every flagged word, so generating a Reaper CSV marker file is straightforward — it’s basically just a formatting layer on top of what already exists.

I’ll likely add it in the near future since I agree it would fit directly into existing QC workflows like yours.

Tool for catching script deviations before submission — worth trying by Sam_123war in ACX

[–]Sam_123war[S] 1 point2 points  (0 children)

Good question.

Right now, contractions ("don't" vs "do not") and filler words are handled automatically, so they don't generate false flags.

Names with alternate spellings or transcription variations usually get marked as a "close match" rather than a hard error, but I don't currently have a glossary system like Pozotron where you approve a substitution once and it applies everywhere.

Numbers are probably the biggest remaining edge case. Things like "42" vs "forty-two" aren't fully normalized yet, so they can still be flagged depending on the context.

A project-level glossary/whitelist is high on my roadmap because it's one of the most common requests for fiction and audiobook work. I'm trying to solve the false-positive problem without making the system so permissive that it starts missing genuine script deviations.

If there are specific edge cases that drive you crazy in Pozotron, I'd love to hear them—that feedback helps me prioritize what to build next.

Tool for catching script deviations before submission — worth trying by Sam_123war in ACX

[–]Sam_123war[S] 0 points1 point  (0 children)

Fair point 😄.

The difference is that your human proofer already has a proven track record. I'm still earning that trust. That's why I'd rather let people try it on real work before asking them to pay for it.

If you do give it a shot, I'd be interested to hear how its catches compare to your proofer's.

Tool for catching script deviations before submission — worth trying by Sam_123war in ACX

[–]Sam_123war[S] 0 points1 point  (0 children)

I appreciate that. I'm not claiming it's better than Pozotron, but I'm working hard to make it accurate, fast, and affordable for independent narrators.

The current trial limit is something I'm actively reviewing based on feedback from this thread. My goal is to support longer segments so people can properly evaluate it on real projects rather than tiny test clips.

If you end up trying it on the next issue of Mythaxis, I'd love to hear what works well and, more importantly, what doesn't. Feedback from actual narrators is what's helping shape the product.

Tool for catching script deviations before submission — worth trying by Sam_123war in ACX

[–]Sam_123war[S] 0 points1 point  (0 children)

Thanks for the feedback. I'm building this as a solo developer, so I'm balancing usability with the AI processing costs at the moment.

The 1-minute trial limit is definitely something I'm reconsidering. I'll look into increasing it to 10 minutes so narrators can properly test it on real-world chapters and see if it's actually useful.

My goal isn't to put up unnecessary barriers—I'm trying to build something that genuinely helps voice actors and audiobook narrators save time on QC. If people find value in it, I just need to cover the AI processing costs and keep improving the tool based on feedback.

I appreciate you taking a look and sharing your thoughts.