Live data from Hacker News

Show HN: Kitten TTS – 25MB CPU-Only, Open-Source TTS Model

github.com

371–380 of 383 posts

Re: Show HN: Kitten TTS – 25MB CPU-Only, Open-Source TTS Model

#372

say is only 193K on MacOS ls -lah /usr/bin/say -rwxr-xr-x 1 root wheel 193K 15 Nov 2024 /usr/bin/say Usage: M1-Mac-mini ~ % say "hello world this is the kitten TTS model speaking"

If you make a shell script that calls say, that script will be even smaller!

Re: Show HN: Kitten TTS – 25MB CPU-Only, Open-Source TTS Model

#374
post #189

Microsoft's and some of Google's TTS models make the simplest mistakes. For instance, they sometimes read "i.e." as "for example." This is a problem if you have low vision and use TTS for, say, proofreading your emails. Why does it happen? I'm genuinely curious.

You probably mean "e.g." as "for example", not "i.e."? This might be on purpose and part of the training data because "for example" just sounds much better than "e.g.". Presumably for most purposes, linguistic naturalness is more important than fidelity.

I did mean "i.e." That's why it is a problem : - \

Re: Show HN: Kitten TTS – 25MB CPU-Only, Open-Source TTS Model

#380

Earlier quoted context omitted.

There are still people who use machine wide python installs instead of environments? Python dependency hell was already bad years ago, but today it's completely impractical to do it this way. Even on raspberries.

Using venv won't save you from having the wrong version of the actual Python interpreter installed.

venvs can be attached to arbitrary interpreters.
Post reply on HN