I'm coming up on a month with my 2x GB10 cluster. I was at 1x for a week before I pulled the trigger for the second.
Initial setup was a tad annoying because I had to update their firmwares and then power cycle them to get the 200GbE link working at full speed. After setting that up, it has been pretty smooth. I don't directly deal with the cluster, usually I just have the LLM itself handle updates/stopping to load different models.
Generation speed and TTFT is decent with Qwen3.8-flash, and it does a good job for my fiddling around with enough concurrency for multiple sessions/subagents. GLM 5.3-flash was also nice, but not too much better for how much slower it is.
I should also add that I already maintain a homelab with a couple of computers, VMs etc, so I am probably somewhat more tolerant of the occasional issue and fine with manually managing stuff over SSH. I think this is just a tradeoff of self-hosting relatively recent tech though.
I have a triple 3090 rig, but it mostly stays powered off because of the massive power draw and cooling requirements. The Sparks are slower but at peak they consume as much power as my 3090 machine at idle.
The recent talk of regulation has me wanting to pick up 2 more Sparks, but that's mostly to have the capacity to play with multiple models, local model tuning and to be ahead in case they force some limits/registration requirements for buying new hardware (kind of like the attempts to regulate 3d printers).
Hmm? I'm running the models locally... 2x Sparks consume ~150W at peak, and they usually spend more time waiting on results from whatever task they're working on, so I imagine that the contribution to my electricity bill is maybe a dollar/mo or less. Though, of course, each Spark was $4000, so the total I've spent is equivalent to several years of the maximum tier for most cloud model susbcriptions.
What I get out of it is the ability to hand login credentials to my other computers to manage their updates, bug fixes etc. Eg. After updating my proxmox server, the nvme drive kept dying. Was able to let my local AI in to figure out and fix what was wrong (known issue). A cloud-based AI could've done it too, but I don't want to be sending internal passwords out of my network like that.
Plus, the ability to freely delegate tasks or exploration of things cloud models generally avoid. For example, I draw as a hobby, and when I'm struggling with a pose but can't quite figure out what I'm missing, I pass it into a VLM for advice, but Claude etc get unnecessarily cautious because they interpret an anatomical sketch as a naked person.
It also blocks my ability to talk about Emily Dickinson in other languages/scripts. Apparently,the poem: "Because I could not stop for Death" is too dangerous.
That's theoretically arguable. Still, for the many reCaptcha users in the world, Google dropped it on them and they are at least temporarily stuck with it. Not everyone has the time or energy to implement another solution, and what solution is better? Cloudflare's infinite turnstile?
In my experience, yes, the irredeemable bigot is rare. For everyone else, regardless of whether their political views are unknown to you or they are threatening your personal way of life, the world will be a better place for you being good neighbors with them. Not to mention that it will improve your own living situation as well.
Most bigotry doesn't come from an inherent maliciousness or evil. It's often just limited experience and never having had reason to reflect on one's views. If you instinctively go "fuck off bigot", you're not only not helping, you're their mirror image.
To be clear, there's a point at which you have to be intolerant of intolerance, but starting off with that is not only counterproductive by reinforcing echo chambers and increasing division, it also makes you not unlike the thing you're opposed to.
Madame Tracy poked her head around the door. "Coo-ee, Mr. Shadwell," she said, giving Newt a friendly little wave. "A gentleman on the telephone for you. Hallo, Mr. Newton."
"Awa' wi' ye, harlot," said Shadwell, automatically.
"He sounds ever so refined," said Madame Tracy, taking no notice. "And I'll be getting us a nice bit of liver for Sunday."
"I'd sooner sup wi' the De'el, wumman."
"So if you'd let me have the plates back from last week it'd be a help, there's a love," said Madame Tracy, and tottered unsteadily back on three-inch heels to her flat and whatever it was that had been interrupted.
Earlier this year, i turned some of Emily Dickinson’s poems into Shavian script. When i asked Claude to make sure i was doing the transcriptions correctly, it stopped responding. Her work is plainly in the pd, I’m not sure what would cause Claude to stop working with it.
Hey Claude - The information in this essay is fine, but you have got to stop leaning on correctio as a rhetorical device. The whole essay is built on it. We've talked about this before and it's grating because you use it in every piece of writing you produce. It's just not how people write.
>> The following Audacity 3 features are not available in Audacity 4.0, but we're working on adding them in future releases.
Time Tracks
Note/MIDI tracks
Mixer
Macro Manager and the scripting pipe
VAMP and LADSPA plugin hosting
Play-at-speed
Sync-Lock and the old tool modes were replaced by the workflows described above.
>>Additionally, Audacity 4 ships with some missing exporting and rendering features, analyzers, and effects.
it might be ancient, but it's also very simple. it's relatively easy to import a single header and write a working plug-in, which makes it attractive for enthusiasts.
the release date is decided before the work even starts. Whatever's done gets released, and marketing gets to claim a new major version. When it's still a work in progress. All software works like this nowadays (I'm sure it doesn't really.... but it sure looks that way). A lot of software I use have missing features in their latest major version
Should watch the pre release video https://www.youtube.com/watch?v=QYM3TWf_G38
If what they're saying is true, this project is very much a pile of tech debt. They need to migrate whatever they can early before continuing work on the audio engine.
Thanks for the essay Claude. It’s good info, just something feels off. It doesn’t feel like a person wrote this article… what are 10 options to fix this?
Look pretty. Can we load alternative stem separators like Spleeter, MDX-Net, and RoFormer implementations? I'd like to be able to AB them for different stems types.
Not yet. StemDeck currently ships with htdemucs_6s, and there is no general model-loading interface today.
This is something I’m actively exploring. MDX-Net and RoFormer are especially interesting because different models can perform better on different instruments and mixes.
I agree that running the same track through multiple models and A/B comparing individual stems would be far more useful than presenting one model as universally “best.”
The difficult parts are model licensing, package size, hardware requirements, and providing a consistent output format across models.
I also want to avoid making every user download several gigabytes of weights they may never use. The likely approach would be optional, on-demand model downloads with cached results and a model selector.
So the short answer is no today, but alternative models and proper A/B comparison are absolutely on the roadmap. Contributions and model recommendations are very welcome thoyugh :)
I'd love to hear more about your setup. I have a single GB10 and am thinking about adding an additional one.
reply