When a transcript is wrong or missing
Why a Rhazes transcript comes out inaccurate, in the wrong language or spelling, or does not appear at all, and how to fix each.
Updated
Fix the transcript before you generate anything
The most important habit in this collection. A note is written from the transcript as it stands, so an error in the transcript becomes an error in the note, and it is much easier to correct one line now than a paragraph later.
See Reading and editing a transcript.
It is inaccurate throughout
Almost always the audio rather than the transcription. Things that help:
- Get the microphone closer. A laptop microphone across a desk picks up the room as much as the person.
- Reduce background noise. Corridors, fans and open doors cost more accuracy than accents do.
- Check the microphone in use is the one you think. See Microphone and recording problems in Rhazes.
It is in the wrong language
Set the spoken language explicitly rather than relying on detection, particularly if you switch languages during consultations. See Choosing the spoken language.
The spelling convention is wrong
Set US, UK or Australian spelling once and it applies to transcripts and documents. See Choosing US, UK or Australian spelling.
It is full of ums and pauses
Turn on filler word removal. See Removing filler words.
There is no transcript at all
- Was the recording ever finished? An unfinished recording sits on the device that made it and produces nothing until you resume and complete it. See Managing saved recordings.
- Are you on the same device and browser? Unfinished recordings do not follow you between machines.
- Did the microphone capture anything? If Rhazes said no sound was recorded, there is nothing to transcribe.
The note is wrong but the transcript is right
Then the problem is the template, not the transcription. See When the output is not what you expected.