Both options are fully supported. VidNo's AI voice cloning is a feature, not a requirement. You can choose whichever approach fits your workflow and preferences.
Option one: use the AI-cloned voice. This is the default workflow and what most users choose. VidNo generates a script from your coding session, synthesizes speech using your local voice model, and renders the video with AI narration. The advantage is speed — you never have to record a voiceover, and you can produce videos from coding sessions after the fact without being near a microphone.
Option two: record your own voiceover. If you prefer narrating yourself, VidNo supports a manual voiceover workflow. The process is: run VidNo in script-only mode (vidno process --script-only recording.mp4), review and edit the generated script, record yourself reading it, then run VidNo in render mode with your audio file (vidno render recording.mp4 --audio your-voiceover.wav). VidNo handles the editing, cuts, and compositing using your real voice instead of the AI clone.
Option three: hybrid. Some users let VidNo generate the AI voice for the initial render, review the output, and then re-record only the sections where they want a more personal touch. You can mix AI and human voiceover within the same video by providing timestamps for which sections use which audio source.
There is no quality penalty for choosing any option. The video editing, smart cuts, transitions, and compositing work identically regardless of the audio source.
One common use case for the own-voice option is developers who already have an established YouTube channel with a recognizable voice. Their audience knows how they sound, and switching to AI narration would be jarring. These users love VidNo for the script generation and editing pipeline while keeping their authentic voice. The AI voice is there for when speed matters more than that personal touch — batch-producing content, covering less important updates, or creating secondary channel content.