I just tested it out locally, really excellent quality, the server was easy to set up and well documented.
I'd love to get to real-time generation if that's in the pipeline? Would like to use it along with Home Assistant.
Chatterbox TTS
111–120 of 197 posts
Re: Chatterbox TTS
#112How do you set the voice? On the Huggingface demo, there seems to be no option for it. It has a female voice. Any way to set it to a male voice?
It's voice cloning. Maybe not available in the demo, but you just provide a different input.
Re: Chatterbox TTS
#113Here's an open-source serving implementation: https://lightning.ai/bhimrajyadav/studios/build-a-production... Also, a deployable model: https://lightning.ai/bhimrajyadav/ai-hub/temp_01jwr0adpqf055...
You failed to mention that this is an ad for the company you work at. Also, the links don't even work without signing up for some shitty service.
Re: Chatterbox TTS
#114Just a regular reminder to tell your friends and family to be extra skeptical about phone conversations. It’s becoming much more likely that the friend who desperately needs a gift card to Walmart isn’t the friend at all. :(
the easiest way to defeat phone fraud is to ahead of time decide on a verbal password between family (and close friends, if they're close enough that you'd lend them money).
In a real scenario, they'd know the verbal password and you can authenticate them. Drum it into them that this password will prevent other people from impersonating you in this brave new world of ai voices and even video.
Re: Chatterbox TTS
#115The voice cloning is okay, not as good as Eleven Labs. There's a Rick (from Rick and Morty) voice example, and the generated audio sounds muffled and low quality. I appreciate that its open source though.
Re: Chatterbox TTS
#116> Every audio file generated by Chatterbox includes Resemble AI's Perth (Perceptual Threshold) Watermarker - imperceptible neural watermarks that survive MP3 compression, audio editing, and common manipulations while maintaining nearly 100% detection accuracy. Am I misunderstanding, or can you trivially disable the watermark by simply commenting out the call to the apply_watermark function in tts.py? https://github.c…
Possibly a sort of CYA gesture, kinda like how original Stable Diffusion had a content filter IIRC. Could also just be to prevent people from accidentally getting peanut butter in the toothpaste WRT training data, too.
Stable Diffusion or rather Automatic1111 which was initially the UI of choice for SD models had a joke/fake "watermark" setting too which was deliberately doing nothing besides poking fun at people who were thinking that open source projects would really waste time on developing something that could easily be stripped/reverted by the virtue of being open source anyways.
Re: Chatterbox TTS
#117What is the current state of the art for open source multilingual TTS? I have found Kokoro to be great as English as well, but am still searching for a good solution for French, Japanese, German...
Re: Chatterbox TTS
#118What is the latency?
Re: Chatterbox TTS
#119Earlier quoted context omitted.
The weights are indeed open (both accessible and licensing-wise): you don't need to put that in square quotes. Training code is not. You can fine-tune the weights yourself with your own training code. Saying that isn't open is like saying ffmpeg isn't open because it doesn't do everything I need it to do and I have to wrap it with own code to achieve my goals.
Machine learning assets are not binary "open" or "closed". There is a continuum of openness. To make a really poor analogy, this repo is like a version of Linux that you can't cross-compile or port. To make another really poor (but fitting) analogy, this is like an "open core" SaaS platform that you know you'll never be able to run the features that matter on your own. This repo scores really low on the "openness" co…
Why can't you improve it or fit it to your data?
This can be cross-compiled/ported in the Linux analogy. The Linux analogy would be more like: a kernel dev wrote code for some part of the Linux kernel using JetBrains' CLion. He used features of CLion that made this process much easer than if he had written the code using `nano`. By your logic, the resulting kernel code is not "open" because the tooling used to create it is not open. This is, of course, nonsense.
I agree that the project as a whole is less open than it could be, but the weights are indeed as open as they can be, no scare quotes required.
Re: Chatterbox TTS
#120Watermarking is easily disabled in the code. I a wondering when they will release model weights with embedded watermarking.