Transcribe the original or a cleaned derivative?
Use the original when speech is already usable. Compare cleanup only for a diagnosed problem; reject processing that removes consonants, quiet replies or overlap, even if a quality score improves.
Elysia Tools
Navigation
Workflow Playbook
Preserve an interview recording, assess transcription risks, compare an optional cleaned copy, review an AI draft against the original and deliver traceable text with unresolved passages.
Hubs
This workflow serves journalists, research interviewers and editors handing off one recorded conversation. Agree whether the result is verbatim, lightly edited or a reading copy. Do not silently remove hesitations, qualifiers or negation from material intended for quotation. Identify who can approve names and who owns final review. Automatic speaker identification, translation, authenticity assessment and legal admissibility are outside this page.
Keep the original locally, record its SHA-256 digest and inspect its duration and channels. A hash identifies a file version; it does not establish who recorded it or whether its contents are true. Separate microphone channels can contain different speakers, so a multichannel warning is not an instruction to collapse them blindly. If extraction or channel selection is needed, perform it in an approved media process and record the relationship to the original.
Use the waveform to locate suspicious levels and the spectrogram to inspect persistent noise, then listen at those times. Neither image reveals the words. The dictation checker estimates readiness from format, activity, clipping and noise separation. Without a suitable non-speech reference, noise separation can be unavailable; never rewrite that missing measurement as a clean pass.
Create a cleanup preview only for a real obstacle. Save the assistant's suggested filter chain and chosen output settings. Its diagnostic analysis uses mono PCM, so reports are not separate speaker-channel assessments. Compare source and derivative at comparable playback level, especially quiet replies, consonants and simultaneous speech. More pleasant sound or a higher score is not proof of better transcription. Keep an unprocessed input when cleanup loses information; substantial restoration belongs in the related repair workflow.
The transcriber sends audio to an external AI provider. Confirm this is authorized before use; an authorized local copy is not automatically permission for external processing. Check the applicable duration limit instead of assuming all long interviews fit. For separately prepared excerpts, keep a table of original start offsets and restore global time references manually; this Hub does not perform automatic long-interview assembly.
Choose text for reading, or SRT, VTT or JSON for review with time references. Save the returned timing provenance. Provider timestamps may be replaced by silence-aligned approximate timing when unavailable. Replay the entire draft against the original, paying particular attention to chunk joins, repeated or missing words, names, dates, amounts and negation. Assign speaker labels from verified context, not vocal guesses. Mark uncertain speech with an original-time range and an explicit uncertainty label rather than inventing a completion.
For SRT or VTT, the sync checker compares cue timing with likely speech activity. It does not check wording, identify speakers or automatically repair drift. A cue can overlap speech while containing the wrong words. Review opening, middle and closing anchors and every flagged interval by playback; plain text and JSON references require manual checks. Caption readability and publication delivery belong in the accessibility workflow.
Open the exact final text or timed file in the receiving application, check encoding and line breaks, and verify that its transcript policy and time origin are stated. Deliver the approved draft revision, source identifier, derivative identifiers where used, processing settings, reports and uncertainty list with reviewer approval. Hash the final files for version tracking, but do not expect them to match the source hash. Store the package outside temporary processing links. A traceable handoff makes limits visible rather than hiding them behind an AI success message.
Workflow playbook
Calculate a SHA-256 source digest, inspect duration and audio channels, and assign a source revision; do not mistake a matching hash for proof of recording authenticity or consent.
Run the dictation preflight and inspect waveform and spectrogram alongside listening; record noisy, clipped, quiet and overlapping passages, treating missing noise references and heuristic warnings as review prompts.
Generate a separate preview only when justified, save the suggested chain and compare difficult passages with the original; recheck metadata and preflight without treating a higher score as approval.
Transcribe the selected version with a deliberate language and output format, save timestamp-source metadata, and review the entire draft against the original; check excerpt offsets and chunk joins and assign speakers manually.
Use the original when speech is already usable. Compare cleanup only for a diagnosed problem; reject processing that removes consonants, quiet replies or overlap, even if a quality score improves.
Use text for reading and quotation review, or SRT, VTT or JSON when time references are needed. Inspect timestamp provenance; approximate timing and activity overlap are not word-level verification.
Replay the original and consult approved references. Mark inaudible words, tentative names and uncertain speakers with time ranges rather than filling gaps from context or accepting a plausible AI sentence.
For SRT or VTT, use the sync checker to flag activity mismatches and then verify actual words by playback; for text or JSON, check references manually. Hash approved files and retain metadata, reviewer sign-off and unresolved notes.