I dont think so. This one doesn’t have any code or implementation details. The one I saw was fully installable but a PITA.

That’s an excellent setup! I’ll try to replicate it when I get home!

What’s your workflow on your phone?

That looks amazing! Will check it out. Love Kokoro and love how good Apple Silicon is!

Kokoro is your best bet right now. It works wonderfully even in a docker container with no GPU. There are others but I don’t have the list right now. Will throw another update on here when I do.

The rhasspy guy was very invested in Coqui. He built a lot of his own stuff, for his home automation and such. But Coqui was superior, so he started spending time on that.

Unfortunately, the coqui team (based out of Mozilla) was very distracted and didn’t ship a lot of stuff on time or at all. It doesn’t even have basic stuff like SSML support right now, if I recall correctly. So the rhasspy guy also lost steam.

Of course, with the OpenAI model of audio generation, you’re expected to not use SSML at all and just use the black box API to get “good enough” results. That really sucks.

Oh, I just remembered which other one I wanted to mention - someone has built an open source version of NotebookLLM, complete with multi voice support. But it requires GPU, I believe. Do what you will with that. I’ll add a link if I find it.

I prefer kokoro because it’s really solid and works really well on CPU.

I was just trying to open my transmission dashboard! 😄

I hope so too! I’m not running a lot on this box. Just a few containers and avahi.

temp

I installed a thing called lm-sensors on debian and it shows me this during a time when the box is struggling -

Every 1.0s: sensors

coretemp-isa-0000 Adapter: ISA adapter Package id 0: +44.0°C (high = +105.0°C, crit = +105.0°C) Core 0: +38.0°C (high = +105.0°C, crit = +105.0°C) Core 1: +39.0°C (high = +105.0°C, crit = +105.0°C) Core 2: +39.0°C (high = +105.0°C, crit = +105.0°C) Core 3: +39.0°C (high = +105.0°C, crit = +105.0°C)

acpitz-acpi-0 Adapter: ACPI interface temp1: +0.0°C (crit = +119.0°C)

Seems to be working fine.

Unless the thermal throttling limits are set by the BIOS and I’ll have to go looking into that by rebooting?

Resources also seemed ok - RAM was 2 GB used out of 16 and all the cores were at 10-15% usage, according to htop.

The problem with the tobacco analogy is that you can buy a pack of cigarettes and walk away, then study it at peace. You cannot run any kind of testing on the shithole systems of Meta without their permission and involvement. That’s how you know every such independent study will be tainted by Zuck’s dirty hands.

I set it up last night. Network share would be too easy to corrupt apparently, so I hustled copied over the files and started fresh. Once in a while, I’ll move files back to my “original” install.

Scrapes from Netflix?

Why were you watching it? It’s a shit… show!

No but seriously… sail, people!

I don’t use calibre web yet. I only use calibre’s inbuilt web service thing. Does theme park work with that too?

Also, I have calibre running on windows and I don’t run docker on that (for reasons). So can I use calibre web on a separate system on the network and have it connect to the calibre db somehow over the wire?

Theme park add on? Tell me more!

Could you tell me more about the non standard implementation? Coz I just use composerize to convert docker run commands to compose (or if I find compose files then hooray!) and pop those into portainer. Seems to work fine. I don’t like that a lot of features seem to be hidden behind a costly subscription, but thems the brakes.

As for proxmox… is it lighter weight than Debian?

It’s fanless! How can I check for thermal throttling? Is that a bios setting?

Oh that’s awesome to know!!

deleted by creator

The server kinda stops completely responding when it’s doing a heavy download… so I can’t get to those stats. But the other commenter has recommended I use https://github.com/henrygd/beszel so I’ll check it out and see what the data reveals. I believe, based on how the system freezes up, that it must be the CPU hitting the roof.

Thanks for that link! I’ll run that service, collect some data and get back to you. I think it hits CPU limits though…