v1.3.0: script import/export, progress bars, and an embarrassing cloning bug

Shipped another update today. Two things people asked for, one thing I should have caught earlier, and one quiet fix.

The embarrassing one first:

Voice cloning could silently fail. If you hadn't downloaded the Expressive engine model yet, the cloning process would run, appear to finish successfully, even show engine badges on the card. But the cloned voice wouldn't actually work. It looked fine. It wasn't.

The problem was three things stacked on top of each other: the preview generation was routing to a model that wasn't there, the success check wasn't actually checking for success, and the UI was painting badges based on assumption rather than reality. Classic "it works on my machine" situation where my machine had every model downloaded.

Fixed properly now. If something fails during cloning, you'll know about it.

Script import and export:

This one kept coming up. People wanted to move scripts between projects, back them up, or bring in text they'd written elsewhere.

You can now export scripts as Markdown files. One file per script. Speaker voice assignments get saved in the file header, so when you import back (even into a different project), each speaker reconnects to their voice automatically.

Three options in the editor's menu:

• Export the current script

• Export all scripts in a project (picks a folder, saves one file each)

• Import files (select one or more .md or .txt files)

Plain text files without the header work too. They just come in without voice assignments.

Generation progress:

The Generate button now doubles as a progress bar. It fills up as chunks complete, so you can see where things are instead of wondering if the app froze. Small thing, but it makes longer generations less stressful.

Autosave after import:

Imported scripts weren't triggering autosave. So you could import, close the project, and lose the content. Nobody reported this one, I caught it while testing import/export. Fixed now.

Full disclosure: I built Vois.

New Blog post: The Complete Guide to Vois Script Formatting to help users using AI for scriptwriting and importing it into Vois.

If you've been using Vois, what workflow stuff like this would save you the most time?

I'm trying to figure out what to prioritize next.