Text capacity with Fast Koko?

[RBEmerson970]

Using Fast Koko to read back a short story, I found it seems to max out at about 15 minutes of text. After that I get fragments of the text.

What's the upper bound on what Fast Koko will accept?

[remsky]

I've run it on a few hours worth without issue, and listened through. What route are you using? Through the WebUI, or API?

[RBEmerson970]

I'm using the web access.

Updated to 0.2.2 and the problem persists I've attached the full log, from installation to starting to speak, along with a grab of the UI.. Note the play time is given as 13:55 which is much too short fo 50k characters. At somewhere around 13:15-:20 the playback skips through the remaining text, reading some chunks, but skipping others.

The text, in PDF form, can be collected here: https://drive.google.com/file/d/1j8ktSuWqgm8w3tWPB1csP8Dvf_qmHAM-/view?usp=drive_link
When using Fast Koko I do CTRL-A, CTRL-C, paste into the Fast Koko text window. I don't use formatting (which compresses the text into a block (makes problems when following in the manuscript).

Install+Run.txt

[RBEmerson970]

BUMP. Any progress?

[remsky]

Sent a request to access the text, will check it out

[remsky]

I'll add in a fix for the 'format' compressing it to block as well.

[RBEmerson970]

[/2 thumbs up]
Link sent.

[RBEmerson970]

BUMP
I'm still hitting a point where the speech goes from linear "word for word" to the beginning of subsequent chunks. This happens +/- 13 minutes into a text.
In my particular case, I read text that I'm writing for a novel, and listening for tense errors, missing or duplicated words, etc.. Using small clips to wade through 50K+ words... not a winner.

[RBEmerson970]

BUMP
This problem persists - any text beyond 10:12 is not spoken by FastKoko. All text does, however, show up correctly in saved audio files (MP3|WAV)..

While I've built Docker containers recently, only the Odd Gods of the Universe know what version I'm really running. I sure as heck don't! >:-(

[RBEmerson970]

Still present after shredding all prior Korkoro-FastAPI containers and directories, and building a fresh V0.2.4.

[BronnEdward]

Maybe helpful... I am running Kokoro-FastAPI container. I was experiencing a same/similar problem where when I would feed it a very long text I would get a maximum of about 10-11 minutes of audio which would have artifacts and skip a lot of text. I found that if I enabled 'Auto-play' in the GUI it would bork the container. Once I tried to generate audio with 'Auto-play' enabled, all subsequent operations would have this truncated audio with artifacts. If I rebuild the container from image and disable 'Auto-play' first, then all text to audio is generated full length without artifacts.

[RBEmerson970]

@BronnEdward
What you're reporting is my experience as well: audio output {MP3|WAV} plays back cleanly regardless of length. FastKoko AutoPlay fails at around 10 minutes 12 seconds , although output to a file works as expected. FWIW, I generated a 3 hours 45 minutes file that played back as expected - outside of FastKoko.

Watching log files as long passages are processed, there's no obvious seam around 10:12. Things just stop working as they should.

Under V0.2.4, once AutoPlay is is disabled, playback through FastKoko (clicking on Play) no longers works, period. Considering prior to 0.2.4 this was not always the case, it's another regression.

This is Koko-FastAPI V0.2.4, under Docker, under Win 11, on an i9 (64 Gb) w/ RTX4090 (16 Gb).