current save state file? #15
Closed
DrewThomasson
started this conversation in
Ideas
Replies: 2 comments
|
I'm updating this tomorrow night (pull latest changes) I'll try to do that. For audiobooks you might want to use --prompt_file book.txt --prompt_file_separator (some special word or token that divides the book roughly in paragraphs) and then either --split_by_words or --split_by_chars to split within the paragraph. That way the voice will 'reset' every paragraph, and it also outputs separate wav files for each. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

Uh oh!
There was an error while loading. Please reload this page.
Thinking that we should add a save state function to it where if it crashes while in the middle of creating the audio file (for instance a Google Colab runtime times out) then you'll have a save file to be able to resume from or something like that idk. You could have it at least keep a current version of the wav file that it keeps adding on to with every bit and a txt file that holds the last sentence it held so if your are making a audiobook then it'll start generating back from that line onwards
All reactions