161–170 of 197 posts
Earlier quoted context omitted.
So in my experience smaller models tend to produce worse results BUT I actually got really good transcription cleanup with CoT (Chain of Thought models) like Qwen even quantized down to 8b.
I think the 8B+ question was about parameter count (8 billion+ parameters), not quantization level (8 bits per weight).
Earlier quoted context omitted.
Nevermind, this is just ~3/10 open, or not really open at all [1]: https://github.com/resemble-ai/chatterbox/issues/45#issuecom... > For now, that means we’re not releasing the training code, and fine-tuning will be something we support through our paid API ( https://app.resemble.ai ). This helps us pay the bills and keep pushing out models that (hopefully) benefit everyone. Big bummer here, Resemble. This is not at…
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.
Has anyone developed a way to annotate the input to provide emotional context? In the past I've used different samples from the same speaker for this.
Chatterbox is fantastic. I created an API wrapper that also makes installation easier (Dockerized as well) https://github.com/travisvn/chatterbox-tts-api/ Best voice cloning option available locally by far, in my experience.
Would this be usable on a PC without a GPU?
To be honest, it uses a decently large amount of resources. If you had a GPU, you could expect about 4-5 gb memory usage. And given the optimizations for tensors on GPUs, I'm not sure how well things would work "CPU only".
If you try it, let me know. There are some "CPU" Docker builds in the repo you could look at for guidance.
If you want free TTS without using local resources, you could try edge-tts https://github.com/travisvn/openai-edge-tts
I always have issues with TTS models that do not allow you to send large chunks of text. Seems this one does not resolve this either. Always has a limit of like 2-3 sentences.
If you want to run it without size limits, here's an open-source API wrapper that fixes some of the main headaches with the main repo https://github.com/travisvn/chatterbox-tts-api/
Chatterbox is fantastic. I created an API wrapper that also makes installation easier (Dockerized as well) https://github.com/travisvn/chatterbox-tts-api/ Best voice cloning option available locally by far, in my experience.
> I created an API wrapper that also makes installation easier (Dockerized as well) https://github.com/travisvn/chatterbox-tts-ap
Gave your wrapper a try and, wow, I'm blown away by both Chatterbox TTS and your API wrapper.
Excuse the rudimentary level of what follows.
Was looking for a quick and dirty CLI incantation to specify a local text file instead of the inline `input` object, but couldn't figure it.
Pointers much appreciated.
Chatterbox is fantastic. I created an API wrapper that also makes installation easier (Dockerized as well) https://github.com/travisvn/chatterbox-tts-api/ Best voice cloning option available locally by far, in my experience.
> Chatterbox is fantastic. > I created an API wrapper that also makes installation easier (Dockerized as well) https://github.com/travisvn/chatterbox-tts-ap Gave your wrapper a try and, wow, I'm blown away by both Chatterbox TTS and your API wrapper. Excuse the rudimentary level of what follows. Was looking for a quick and dirty CLI incantation to specify a local text file instead of the inline `input` object, but co…
A lot of these frontends have an option for using OpenAI's TTS API, and some of them allow you to specify the URL for that endpoint, allowing for "drop-in replacements" like this project.
So the speech generation endpoint in the API is designed to fill that niche. However, its usage is pretty basic and there are curl statements in the README for testing your setup.
Anyway, to get to your actual question, let me see if I can whip something up. I'll edit this comment with the command if I can swing it.
In the meantime, can I assume your local text files are actual `.txt` files?
Earlier quoted context omitted.
> Chatterbox is fantastic. > I created an API wrapper that also makes installation easier (Dockerized as well) https://github.com/travisvn/chatterbox-tts-ap Gave your wrapper a try and, wow, I'm blown away by both Chatterbox TTS and your API wrapper. Excuse the rudimentary level of what follows. Was looking for a quick and dirty CLI incantation to specify a local text file instead of the inline `input` object, but co…
This API wrapper was initially made to support a particular use case where someone's running, say, Open WebUI or AnythingLLM or some other local LLM frontend. A lot of these frontends have an option for using OpenAI's TTS API, and some of them allow you to specify the URL for that endpoint, allowing for "drop-in replacements" like this project. So the speech generation endpoint in the API is designed to fill that nic…
To answer your question, yes, my local text files are .txt files.