I've been using Murf for a few months now, primarily for generating voiceovers for internal training videos and system alerts. While the voice quality is excellent, I've hit a consistent pain point in my workflow: the iterative editing process.
My typical flow is to generate a script, render a draft, listen, then make tweaks to pacing or pronunciation. With Murf, every minor edit—like adjusting a single word's emphasis—feels like a full page reload. The UI is visually polished but seems to carry a heavy frontend framework overhead. Compared to simpler, almost text-editor-like interfaces such as Lovo's, the latency adds up.
Here's a concrete example from my last session:
* I needed to change "reboot the *database* cluster" to "reboot the *main* database cluster."
* In Murf, clicking the word, editing, and having the audio re-process and the entire sentence re-render in the timeline took ~4-5 seconds.
* In Lovo, a similar edit in my previous project felt near-instantaneous, with the audio chunk updating in-place without a full UI refresh.
It feels like the difference between editing a YAML file directly in `vim` versus using a heavy GUI config manager. For bulk, set-and-forget generation, Murf is superb. But for rapid, iterative tweaks—which is most of my work—the UI friction is real. I've started drafting scripts elsewhere and pasting the final version into Murf, which defeats the purpose of its integrated editor.
Has anyone else run into this, or developed a workaround? I'm curious if it's a perception issue or if others have measured similar slowdowns.