Can you post the error? There’s nothing quite like offering detailed technical advice blind…or deaf in this case.
Drag-select a portion before and then going into the edit. A portion that illustrates the quality shift, say three to five seconds before and three to five seconds after. Export as a 192 quality, constant MP3 and post it here. You will note 192 quality is the ACX/Audible submission quality.
Scroll down from a forum text window > Attachments > Add Files.
If you’re recording in Windows 11, there is a festival of problems you can have by Windows trying to “help you.” You can also have sound problems by Zoom, Skype, Meetings, and other programs trying to “help you.”
And finally, the microphone itself can have driver and software packages trying to “help you.”
You picked the worst possible repair condition. Come back next week and try to patch it.
If you know you’re making a fluff or mistake, the prevailing advice is stop reading, go back at least one full sentence and read it all again. Do Not try to patch one word or other short phrase and Do Not stop the recording. Later in editing, you go in and slice off the mistake and the new and old sentences should fit together. You get the swing of how to do this as you go. This technique closely matches the mistake and the voice quality, presentation, and emphasis of the patch because they’re seconds apart.
Do you listen to your live voice as you go? It should be possible to plug your headphones into the Yeti and listen in real time. That goes a very long way to making your chapters match because you can hear in real time when your presentation, emphasis, and rhythm start drifting off.
That also gives you the ability, absent all the other computer problems, to do a patch by using Music Overdubbing techniques. Play the work up until the patch and then start announcing and match the voice quality in your headphones in real time. That’s not easy, but it’s a lot easier than trying to announce a patch cold.
Koz
