I hope this is the future. Offline, small ML models, running inference on ubiquitous, inexpensive hardware. Models that are easy to integrate into other things, into devices and apps, and even to drive from other models maybe.
Dedicated single-purpose hardware with models would be even less energy-intensive. It's theoretically possible to design chips which run neural networks and alike using just resistors (rather than transistors). Such hardware is not general-purpose, and upgrading the model would not be possible, but there's plenty of use-cases where this is reasonable.
Show HN: Kitten TTS – 25MB CPU-Only, Open-Source TTS Model
221–230 of 383 posts
Re: Show HN: Kitten TTS – 25MB CPU-Only, Open-Source TTS Model
#222Earlier quoted context omitted.
> IANAL, but AFAICS this leaves 2 options, switching the license or removing that dependency. There is a third option: asking the project for an exception. Though that is unlikely to be granted¹ leaving you back with just the other two options. And of course a forth choice: just ignore the license. This is the option taken by companies like Onyx, whose products I might otherwise be interested in… ---- [1] Those of us…
A fourth option would be a kind of dual-licensing: the project as-is is available under GPL-3.0, but the source code in this repository excluding any dependencies is also available under Apache 2.0 Any user would still effectively be bound by the GPL-3.0, but if someone can remove the GPL dependencies they could use the project under Apache
Re: Show HN: Kitten TTS – 25MB CPU-Only, Open-Source TTS Model
#223Re: Show HN: Kitten TTS – 25MB CPU-Only, Open-Source TTS Model
#224Re: Show HN: Kitten TTS – 25MB CPU-Only, Open-Source TTS Model
#225Earlier quoted context omitted.
> It’s that KittenTTS is Apache-2.0 Have you seen the code[1] in the repo? It uses phonemizer[2] which is GPL-3.0 licensed. In its current state, it's effectively GPL licensed. [1]: https://github.com/KittenML/KittenTTS/blob/main/kittentts/on... [2]: https://github.com/bootphon/phonemizer Edit: It looks like I replied to an LLM generated comment.
This would only apply if they were distributing the GPL licensed code alongside their own code. If my MIT-licensed one-line Python library has this line of code… run([“bash”, “-c”, “echo hello”]) …I’m not suddenly subject to bash’s licensing. For anyone wanting to run my stuff though, they’re going to need to make sure they themselves have bash installed. (But, to argue against my own point, if an OS vendor ships my…
Sillyness
Re: Show HN: Kitten TTS – 25MB CPU-Only, Open-Source TTS Model
#226System Requirements Works literally everywhere Haha, on one of my machines my python version is too old, and the package/dependencies don't want to install. On another machie the python version is too new, and the package/dependencies don't want to install.
https://github.com/KittenML/KittenTTS/pull/21 https://github.com/KittenML/KittenTTS/pull/24 https://github.com/KittenML/KittenTTS/pull/25
If you have `uv` installed, you can try my merged ref that has all of these PRs (and #22, a fix for short generation being trimmed unnecessarily) with
uvx --from git+https://github.com/akx/KittenTTS.git@pr-21-22-24-25 kittentts --output output.wav --text "This high quality TTS model works without a GPU"Re: Show HN: Kitten TTS – 25MB CPU-Only, Open-Source TTS Model
#227Earlier quoted context omitted.
A fourth option would be a kind of dual-licensing: the project as-is is available under GPL-3.0, but the source code in this repository excluding any dependencies is also available under Apache 2.0 Any user would still effectively be bound by the GPL-3.0, but if someone can remove the GPL dependencies they could use the project under Apache
That is an option for the publisher of the library, not the consumer of it. If it isn't already done then asking for it to be done is the same as asking for an exception otherwise (option three).
Obviously you can't run them (with the original library) without complying with the GPL. But I don't see why I couldn't independently of that also give you this text file under Apache 2.0 to do with as you want (which for the record still doesn't allow you to run them with the original library without complying with the GPL, but that'd be phoneme forcing you to do that, not this project)
You would have to be very specific about the dual-licensing to avoid confusion about what you are allowed to do under Apache conditions though. You can't just say "it's dual-licensed"
Re: Show HN: Kitten TTS – 25MB CPU-Only, Open-Source TTS Model
#228I'm curious, but right now I don't want to install the package and run some code.
Re: Show HN: Kitten TTS – 25MB CPU-Only, Open-Source TTS Model
#229Earlier quoted context omitted.
This one is at least an interesting idea: https://genderlessvoice.com/
Interesting concept, but why is that site filled with Top X blogspam?
Other than the video, the only relevant content is on the about page [2]. It says the voice is a collaboration between 5 different entities, including advocacy groups, marketing firms and a music producer.
The video is the only example of the voice in use. There is no API, weights, SDK, etc.
I suspect this was a one-off marketing stunt sponsored by Copenhagen pride before the pandemic. The initial reaction was strong enough that a couple years they were still getting a small but steady flow of traffic. One of the involved marketing firms decided to monetize the asset and defaced it with blog spam.
Re: Show HN: Kitten TTS – 25MB CPU-Only, Open-Source TTS Model
#230Earlier quoted context omitted.
> It’s that KittenTTS is Apache-2.0 Have you seen the code[1] in the repo? It uses phonemizer[2] which is GPL-3.0 licensed. In its current state, it's effectively GPL licensed. [1]: https://github.com/KittenML/KittenTTS/blob/main/kittentts/on... [2]: https://github.com/bootphon/phonemizer Edit: It looks like I replied to an LLM generated comment.
This would only apply if they were distributing the GPL licensed code alongside their own code. If my MIT-licensed one-line Python library has this line of code… run([“bash”, “-c”, “echo hello”]) …I’m not suddenly subject to bash’s licensing. For anyone wanting to run my stuff though, they’re going to need to make sure they themselves have bash installed. (But, to argue against my own point, if an OS vendor ships my…
As far as I understand the FSF's interpretation of their license, that's not true. Even if you only dynamically link to GPL-licensed code, you create a combined work which has to be licensed, as a whole, under the GPL.
I don't believe that this extends to calling an external program via its CLI, but that's not what the code in question seems to be doing.
(This is not an endorsement, but merely my understanding on how the GPL is supposed to work.)