Detect audio sensitive words
- Category: Middleware
What it is
Matches sensitive words on word-level subtitles and produces a beep audio and marker ranges. To place the beep on the timeline, you must connect it to "Import audio".
This node grew out of the related Lab tools: wires in a blueprint replace the step-by-step clicks in the Lab, which makes it easy to reuse and to hand to an agent.
Related Lab tools
Inputs
| Name | Description |
|---|---|
| Word-level subtitles | Word-level subtitles with timestamps |
| Timeline summary | Timeline position and related info |
| Custom beep | Optional. Replaces the default beep with your own sound |
Outputs
| Name | Description |
|---|---|
| Marker ranges | Markers to place on the timeline |
| Beep ranges | Time ranges that need a beep |
| Audio | Audio asset |
How to connect
After word-level subtitles go into this node, connect both the generated audio and the beep ranges to "Import audio". The marker ranges can also go to "Create timeline markers".
Settings
| Name | Description |
|---|---|
| Custom blocked words | Extra words to block, added to the default list |
| Beep placement | How the beep covers a sensitive-word range |
| Beep padding (ms) | Extra time covered before and after the word |
Typical downstream
Import audio, Create timeline markers
Notes
- Before writing back to the editing app, make sure LmBox is connected to the matching app (DaVinci Resolve / Premiere / After Effects and so on).
- To hear the beep, connect both the generated audio and the beep ranges to "Import audio".
Related recipes
- Sensitive-word beep write-back: see the recipes in the Blueprint lab overview
Agents / MCP
For agents or developers (optional)
- Once LmBox's open MCP is connected, the full ports and settings can be read from the catalog. This page is written for people, not around machine fields.
- Node type:
audio-censor-detect
← Back to the Blueprint lab overview · Lab features overview · Blueprint lab guide