Minimum
- Windows 10 x64
- 8 GB RAM
- 2 GB free disk space
- Intel Core i5 / AMD Ryzen 5
- SSD recommended
Guide • Censor Script
Install and use Censor Script
A practical guide to automatic profanity detection. Censor Script can prepare a beep-censored file or help mark questionable moments for review in a DaVinci Resolve workflow.
Platform
Windows 10/11 x64
Workflow
DaVinci Resolve Studio 18–21
Before installation
System requirements
DaVinci Resolve Studio is required when you want to use the timeline integration workflow.
Recommended
- Windows 11 x64
- 16 GB RAM
- SSD storage
- Intel Core i7 / AMD Ryzen 7 or better
- DaVinci Resolve Studio 18–21 for timeline integration
Installation
Set up Censor Script
01
Download the installer
Save CensorScriptSetup.exe to your computer.
02
Run it as administrator
If Windows shows SmartScreen, verify that you downloaded the installer from this website before confirming the launch.
03
Install the components
Keep the recommended installation settings unless you specifically need a custom location.
04
Run a short test
Launch Censor Script and test it on a short piece of spoken audio or video before processing a full episode.
First run
Two practical workflows
Choose the output that matches the job: a quick beep-censored file or editorial control through DaVinci Resolve timeline markers.
01
Add audio or video
Select spoken content that needs to be checked for profanity.
02
Run analysis
The tool transcribes speech and finds sections that match the censoring vocabulary.
03
Choose the output mode
Create a beep-censored result or use the DaVinci Resolve workflow for timeline review.
04
Review questionable hits
Check the detected sections because noise, slang and unclear speech can produce false positives or misses.
Workflow
Automatic censoring pipeline
The script accelerates detection and rough marking, while the final decision about ambiguous language remains with the user.
01
Audio / video
02
Speech recognition
03
Term detection
04
Output mode
05
Beep pass
06
Review / markers
Result
What gets automated
Manual workflow
- •listen through the entire episode
- •search for profanity manually
- •place markers one by one
- •build beep replacements manually
→
With Censor Script
- •automatic speech analysis
- •a prepared list of detected sections
- •beep output or DaVinci Resolve review markers
- •manual review focused on ambiguous moments
Important
Automatic censoring is not infallible. Review the result before publishing: context, background sound and speech characteristics can affect detection accuracy.
FAQ
Common questions
Yes. In the standalone workflow you can process audio or video and generate a beep-censored result without opening a Resolve project.
It is useful when you continue editing manually and want to jump through detected sections on the timeline for review and correction.
Internet access may be needed for downloads, activation, license checks and updates. Core processing can run locally once the environment is prepared.
Speech recognition can be affected by music, noise, overlapping speakers, accents and unusual pronunciation.
The finished file is better for speed. Timeline markers are better for a professional editing workflow where every detected section should remain under editorial control.
No. Its purpose is to reduce the amount of manual searching; final quality control before publishing is still required.
Support
What to include in a support request
Include your Windows version, DaVinci Resolve version when timeline integration is used, Censor Script version, an error screenshot and a short sample file that reproduces the problem.