FastKoko has stopped talking #434
Replies: 5 comments 1 reply
-
|
kokoro-tts-1 | INFO: Uvicorn running on http://0.0.0.0:8880 (Press CTRL+C to quit) |
Beta Was this translation helpful? Give feedback.
-
|
Good news, bad news. FastKoko is speaking again, and showing times, etc. The bad news is I have no idea why FastKoko's speaking again. I tried running "Openreader", a PDF reader, and it worked as it should. I tried OpenWebUI and had it read back a chat with an LLM-it worked, too. I tried FastKoko again and it works. FastKoko has returned to working with no significant changes save for running two other containers. |
Beta Was this translation helpful? Give feedback.
-
|
Weirder and weirder... FastKoko has shut up again, while Openreader continues to speak. Once FastKoko started running to the point of posting my previous post, I played back roughly 15-17K of text in 5K to 7K chunks, all without a problem. But FastKoko's shut up again, although it continues to write audio files correctly (file name glitch excepted). That Openreader works, but FastKoko doesn't suggests the problem is somewhere in Fast-KokoAPI's web UI implementation. |
Beta Was this translation helpful? Give feedback.
-
|
Regarding question 1, I ran FastKoko in airplane mode (no WiFi or Bluetooth, Ethernet isn't available at this location), and both Openreader and (when it behaves) FastKoko speak as expected. Or, yes, I'm successfully using Kokoro locally. |
Beta Was this translation helpful? Give feedback.
-
|
As of this post, launching FastKoko and attempting to get speech while creating an audio file fails - no speech while the file's being generated, no run time display, and clicking Play produces nothing. However, launch OpenReader (in Docker) and OpenReader WebUI (with Vivaldi), then launch FastKoko (in Vivaldi), and FastKoko behaves as expected, and experienced over several months. It is not enough to only launch OpenReader, the web UI must be opened, too. However, FastKoko continues to run correctly after closing the web UI. Stop OpenReader in Docker, and FastKoko stops working correctly. Naturally, kokoro-tts-gpu is launched in Docker before starting anything else. The machine is an i9 with RTX-4090 running Win 11 and Docker, with Vivaldi browser, a setup that's been stable for several months. |
Beta Was this translation helpful? Give feedback.
-
|
OK, what happens with another browser? Firefox craters as expected - there are enough comments about trying to use Firefox. Endit. Edge? NFW will I willingly run Edge. Endit. Bravo? Surprise, surprise, surprise..., FastKoko behaves exactly as it does under Vivaldi. I suppose I could try Chrome directly, but Vivaldi and Bravo are AFAIK Chrome-based, so there's little reason to think Chrome and FastKoko together would behave differently. It also explains why Vivaldi and Bravo interact with FastKoko in the same way. So, at the moment, the only way to get FastKoko speaking is to launch OpenReader and its webUI first. My guess is doing that somehow sets up kokoro in a way FastKoko no longer does (but used to). That FastKoko "magically" stopped working in spite of not doing intentionally, or accidentally, any updates or changes is more than a little troubling. Something changed, but darned if I know what, how, or why. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Within the last day or two, FastKoko has stopped playing, in real time, text in the FastKoko web interface. The desired audio can be saved as a file (MP3, WAV, etc.) and played back with VLC, etc. The "speak while generating" capability has stopped for no apparent reason. The display of current run time/total run time remains 0:00/0:00 regardless of the size of the text (from "Hello, world." to 5K+ of text), and toggling "Play/Pause" and "Auto-Play" makes no difference.
Version numbers are, sadly, meaningless but suffice it the Docker container was over a month old, and worked within two days of this post. There's been no OS update (Win 11), and Docker wasn't updated at the time of failure. I've since moved to Docker 4.55.0 with no change. I've scrapped the previously functioning container (which had the initial failure), and replaced it with a new build. No change in behavior.
Unfortunately, I'm away from home and stuck with a horrendous DSL connection, making a fresh Git literally an hours long process.
Question 1: I've assumed that I've been running Kokoro and FastKoko strictly locally, and any changes to Kokoro-Fast, FastKoko, etc. in the repo would have no influence on my installation. Is this assumption correct?
Question 2: has anything changed in the Kokoro world since 23 Dec 2025?
Once again I'll be a PITA about version numbering here being about as useful as a screen door on a submarine. V0.2.4 has existed since at least June 2025, so saying I'm running a new build of V0.2.4 is effin' meaningless.
Beta Was this translation helpful? Give feedback.
All reactions