A standalone tool is ideal for a one-off operation. A pipeline becomes useful when the same sequence of transformations must be repeated.
Bethemesh Audio tools and Workspace modules rely on shared processing engines, so the operations can be composed without inventing a separate workflow.
Example: prepare a voice recording
Import → Trim → Normalize → Compress → Download
Trim first so normalization measures the material you will actually keep. Perform lossy compression near the end to avoid unnecessary repeated encoding.
Example: prepare audio for video
Import → Trim → Resample to 48 kHz → Normalize → Convert → Download
This makes the project requirement explicit and keeps the order reproducible.
Example: two microphones in a stereo file
Import stereo → Split channels → Process voice A / voice B separately
If left and right contain independent microphones, separating them is more appropriate than immediately converting the source to mono.
Why order matters
Audio operations are not always interchangeable. A fade-in that is reversed becomes a fade-out. A lossy encode repeated after every stage can accumulate degradation.
Write the objective first, then translate it into steps: input, selection, transformation, technical normalization, loudness, output format and download.
Test before processing a batch
Run the pipeline on one representative file. Listen to the result and check duration, channels, sample rate, loudness, format and file size before applying the same workflow repeatedly.
Local processing
The Audio architecture is designed for processing in the browser. Required WebAssembly engines may be loaded by the page, while the media itself can remain on the device instead of being uploaded to Bethemesh.
Open the Workspace when you want to compose and reuse transformations. For a single operation, an individual tool such as Trim audio remains faster.
Start with the main Audio guide if you want an overview of all available operations.
