Listen, everything that they are doing by scorching the planet and turning the tap water brown, could be achieved on CPU or much smaller GPUs on local machines - it’s a question of focused, tight training. What they’re doing instead is literally attempting to build gigantic models that take in absolutely everything (burning real books in the process because fuck history we got money to make) and attempting to sell the idea that this brute force, one-thing-does-it-all approach, which requires us to give up everything else that is good in the world, is the only way forward, and yes, we must build the roko basilisk now.
It’s a big, big grift.
A_norny_mousse@piefed.zip
irmadlad@lemmy.world
robottoaster@mander.xyz@mander.xyz
curbstickle_lw@lemmy.world 4 hours ago
Audio processing by ai can absolutely happen on a pi.
As an example, whisper.cpp is a high performance speech recognition model, and it does a great job. The biggest version of it as a model requires less than 5GB to live fully in memory, the large model at about 1.5billion parameters, and it works great even CPU only.
The one used most often is small, which has about 244million parameters, and needs about a gig of ram and nothing more.
For a pi 5, usually the base or tiny model are used. Small could be used in most scenarios, but tiny and base are able to run real-time.
So it depends for how local - sometimes its all self contained and can do just fine on a pi, sometimes its local in that it needs an LLM endpoint to hit, but that can be running on another system entirely.
It would really depend on the project for how/where/why for a definition of local.