You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you need to apply text processing to your ASR transcriptions, you will need to implement custom stages. The `AudioToDocumentStage` provides the foundation for this by converting to the standard`DocumentBatch`format.
149
+
While `AudioToDocumentStage` converts audio data to `DocumentBatch`format, NeMo Curator's built-in text processing stages (filters, classifiers, etc.) are designed for text documents, not audio transcriptions. For audio-specific text processing, implement custom stages that operate on the converted `DocumentBatch` data.
98
150
99
151
### Example: Custom Text Processing
100
152
153
+
101
154
```python
102
155
from nemo_curator.stages.function_decorators import processing_stage
103
156
from nemo_curator.tasks import DocumentBatch
@@ -141,12 +194,19 @@ document_batch.data # pandas DataFrame with columns:
141
194
142
195
## Limitations
143
196
144
-
:::{note}
145
-
**Text Processing Integration**: NeMo Curator's text processing stages are designed for `DocumentBatch` inputs, but they may not be optimized for audio-derived transcriptions. You may need to implement custom processing for audio-specific workflows.
197
+
:::{important}
198
+
**Text Processing Integration**: NeMo Curator's text processing stages are designed for `DocumentBatch` inputs (text documents such as articles, web pages), but they are not designed for audio-derived transcriptions. You should implement custom processing stages for audio-specific workflows.
199
+
200
+
**Reasons for incompatibility:**
201
+
- Text filters assume document-level content (e.g., paragraph structure, word count thresholds designed for articles)
202
+
-ASR transcriptions have different characteristics (shorter, may contain recognition errors, conversational language)
0 commit comments