Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Chatterbox TTS

github.com

Post reply on HN
Print view View original

181–190 of 197 posts

Re: Chatterbox TTS

#181

Post by travisvn »

mistersquid wrote: post #172
travisvn wrote: post #171

Earlier quoted context omitted.

Ok, here's a command that works. I'm new to actually commenting on HN as opposed to just lurking, so I hope this formatting works.. cat your_file.txt | python3 -c 'import sys, json; print(json.dumps({"input": sys.stdin.read()}))' | curl -X POST http://localhost:5123/v1/audio/speech \ -H "Content-Type: application/json" \ -d @- \ --output speech.wav Just replace the `your_file.txt` with.. well, you get it. This'll hop…

> Just replace the `your_file.txt` with.. well, you get it. > This'll hopefully handle any potential issues you'd have with quotes or other symbols breaking the JSON input. > Let me know how it goes! Wow. I'm humbled and grateful. I'll update once I'm done with work and back in front of my hone nachine.

Hey — just pushed a big update that adds an (opt-in) frontend to test the API

For now, there's just a textarea for input (so you'll have to copy the `.txt` contents) — but it's a lot easier than trying to finagle into a `curl` request

Let me know if you have any issues!

Re: Chatterbox TTS

#182

Post by chii »

IshKebab wrote: post #173
Ylpertnodi wrote: post #160

Earlier quoted context omitted.

Works for me and the family. No code-word, no transfer of funds.

Have your parents been targeted by convincing fraudsters? It doesn't work for you; you hope it will work.

It is better than not having it as a backup method. It might even trip the scammer up as they may not expect it.

Not to mention that it is your responsibility as the technically minded to hammer it into your family members.

Re: Chatterbox TTS

#183

Post by mistersquid »

travisvn wrote: post #181
mistersquid wrote: post #172

Earlier quoted context omitted.

> Just replace the `your_file.txt` with.. well, you get it. > This'll hopefully handle any potential issues you'd have with quotes or other symbols breaking the JSON input. > Let me know how it goes! Wow. I'm humbled and grateful. I'll update once I'm done with work and back in front of my hone nachine.

Hey — just pushed a big update that adds an (opt-in) frontend to test the API For now, there's just a textarea for input (so you'll have to copy the `.txt` contents) — but it's a lot easier than trying to finagle into a `curl` request Let me know if you have any issues!

(Didn't carefully read your reply. What follows are the results of cat-ing a text file in the CLI. Will give the new textbox a whirl in the morning PDT. A truly heartfelt thanks for helping me work with Chatterbox TTS!)

Absolutely blown away.

I fed it the first page of Gibson's "Neuromancer" and your incantation worked like a charm. Thanks for the shell script pipe mojo.

Some other details:

  - 3:01 (3 mins, 1 sec) of generated .wav took 4:28 to process
  - running on M4 Max with 128GB RAM
  - Chatterbox TTS inserted a few strange artifacts which sounded like air venting, machine whirring, and vehicles passing. Very odd and, oddly, apropos for cyberpunk.
  - Chatterbox TTS managed to enunciate the dialog _as_ dialog, even going so far as to mimick an Australian accent where the speaker was identified as such. (This might be the effect of wishful listening.)
I am astounded.

Re: Chatterbox TTS

#186

Post by DHolzer »

I love chatterbox, it's my favourite. While the generation speed is quick, i wonder what performance optimization i could try on my 3090 to improve throughput. It's not quite enough for realtime.

Re: Chatterbox TTS

#188

Post by dragonwriter »

echelon wrote: post #107
fastball wrote: post #101

Earlier 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…

> This will never be built by anyone, and they know that. If it could be, they'd provide it themselves.

Community fine-tuning code has been developed in the past for open-weights models without public first-party training code.

Re: Chatterbox TTS

#189

Post by dragonwriter »

SV_BubbleTime wrote: post #178
andyferris wrote: post #103

It took me ages to understand what TTS means!

I don't like how for text to image/video it's T2V I2V, and reference video to video is V2V... Then when we get to text 2 it T all of a sudden.

TTS has been around as an initialism long before the current AI wave, the x2y pattern is newer. (You do see it around TTS, even though TTS itself hasn't become T2S; e.g., TTS toolchains often include a g2p—grapheme-to-phoneme—component.)
Post reply on HN