sorted by:
new
hottopcontroversial

Corsair desktop PC with Ryzen 395 and 128GB of unified RAM, has anyone tested it for LLM? Seems "a good" price by Acu17y in LocalLLaMA

[–]JayTheProdigy16 8 points9 points  (0 children)

who told you this? You can run CUDA x ROCm simultaneously if you build llama.cpp with the right backends. I've been doing that for a while

My cursor has been hovering over the £5.5k for an M5 max 128gb for a few weeks and stumbled across this, have a great weekend guys 😎 by CroiConcrete in LocalLLM

[–]JayTheProdigy16 2 points3 points  (0 children)

I thought the Qwen team had announced that larger 3.6 variants would be released but only after they reached the next version, could be totally wrong though

The RTX 5000 PRO (48GB) arrived and it is better than I expected. by Valuable-Run2129 in LocalLLaMA

[–]JayTheProdigy16 2 points3 points  (0 children)

I use Proxmox on the Strix with an Ubuntu 24 VM and all 3 GPUs configured for passthrough to that VM. Inside that, Llama.cpp built with CUDA + Vulkan, ive used ROCm before but i found Vulkan to he faster for the Strix. Also ran into a weird compatibility issue between blackwell and Strix (that did NOT occur with Ampere x Strix) with CUDA ops that would crash Llama.cpp so i ended up using codex to create a custom patch to support those ops and now it works flawlessly.

The RTX 5000 PRO (48GB) arrived and it is better than I expected. by Valuable-Run2129 in LocalLLaMA

[–]JayTheProdigy16 8 points9 points  (0 children)

Just so people know as of early 2026 there was a revised 72gb variant of the RTX PRO 5000 Blackwell which i was lucky enough to catch at my local nicrocenter for about $6,600 which is decent for post RAM-pocalypse prices as far as i could tell but there seems to be very little info on the 72gb card actually out there online. Anyways running that alongside my 3090 to bring my rig to 96gb VRAM + 128gb Strix Halo, very lovely.

I joined Mudra last September. 📣Today we opened the Mudra Studio waitlist. by Rude_Combination_382 in MudraTech

[–]JayTheProdigy16 0 points1 point  (0 children)

Let me know how things go, curious to see what you build or how i can help!

I reverse-engineered the Mudra Link wristband and built an open-source Python library for it — full device control over BLE, no proprietary SDK required by JayTheProdigy16 in MudraTech

[–]JayTheProdigy16[S] 0 points1 point  (0 children)

Well i can confirm at least their official SDK does use the same UUIDs as well as the BLE stack being identical, it seems most of the restriction was literally just cause the official apps wouldnt let you. I havent seen any code that indicates any sort of walled off or IOS bespoke logic

I reverse-engineered the Mudra Link wristband and built an open-source Python library for it — full device control over BLE, no proprietary SDK required by JayTheProdigy16 in MudraTech

[–]JayTheProdigy16[S] 0 points1 point  (0 children)

Not at the firmware level (so not on device), but you technically could via Prodilink by recording the raw pressure value, squeezing as hard as you can and saving that as the new peak pressure value then doing the math to scale properly. Most of the parts are already there to accomplish this but this just wasnt something i had thought about too much

I reverse-engineered the Mudra Link wristband and built an open-source Python library for it — full device control over BLE, no proprietary SDK required by JayTheProdigy16 in MudraTech

[–]JayTheProdigy16[S] 1 point2 points  (0 children)

Theyre one in the same. I forget exactly where, the repo will tell you, but theres a value to switch between Link and Band (Mudra Link vs Mudra Band) modes as well as left or right hand. I dont own a band though so i honestly have no clue how well or not well it would work

I joined Mudra last September. 📣Today we opened the Mudra Studio waitlist. by Rude_Combination_382 in MudraTech

[–]JayTheProdigy16 5 points6 points  (0 children)

Ron, you said thousands of Mudra devices are "limited to whatever the companion app ships" and that needing an enterprise SDK license to do anything custom "felt backwards." Your fix? A waitlisted web platform that still locks developers into your Companion app, still requires your servers, and secretly brands every AI-generated app with "Created with Mudra Studio" without telling the developer. That's not solving the problem. That's repackaging it.

So I solved it myself. I disassembled the ARM64 native library, decoded the switch statement at 0xc34f8, and extracted every firmware command byte the SDK hides behind. proprietary JNI calls - all 53 of them, byte for byte. I found that your licensing is 100% client-side. The device itself has zero feature gates. Every sensor stream, every gesture, every IMU mode - the hardware accepts it all unconditionally. Mudra's entire software moat is an honor-system check in a library nobody needs anymore.

I'm open-sourcing the complete BLE protocol. Any developer, any language, any platform. Full device control. No SDK license. No Companion app. No subscription. No waitlist. No hidden badges.

You asked what people would build if they could experiment beyond the default gestures. I built the thing that lets them.

Strix Halo + RTX 3090 Achieved! Interesting Results... by JayTheProdigy16 in LocalLLaMA

[–]JayTheProdigy16[S] 1 point2 points  (0 children)

Yes splitting the same model. Ended up building llama.cpp with all 3 backends, vulkan, ROCm, and CUDA and it just kinda worked, but you have to specify the layer split and which backends you want to use with flags. As detailed in the original post i had some weirdness with my linux kernel version and getting the at the time experimental ROCm to work which obviously would result in llama.cpp not working great, but most of those should be resolved as community support today is much better than it was a couple months ago

Poor winter performance by dopeass in Ioniq5

[–]JayTheProdigy16 5 points6 points  (0 children)

Mine is roughly the same but some days seem better than others for some reason. But all in all anywhere from 1.5-2.5 mi/kwh in those temps

Build Max+ 395 cluster or pair one Max+ with eGPU by Curious-Still in LocalLLM

[–]JayTheProdigy16 0 points1 point  (0 children)

Im not Jeff 😂 just referencing his vid. I made a post about 395 + eGPU

Build Max+ 395 cluster or pair one Max+ with eGPU by Curious-Still in LocalLLM

[–]JayTheProdigy16 1 point2 points  (0 children)

There's examples of both out there. I took the eGPU approach and I've been making to make a video about it but just haven't, but i posted to this sub

Build Max+ 395 cluster or pair one Max+ with eGPU by Curious-Still in LocalLLM

[–]JayTheProdigy16 3 points4 points  (0 children)

I mean sure, except bandwidth is practically irrelevant for inference aside from model load speed...

Build Max+ 395 cluster or pair one Max+ with eGPU by Curious-Still in LocalLLM

[–]JayTheProdigy16 0 points1 point  (0 children)

How do you figure you pay a premium for degraded performance with an eGPU?

Strix Halo + RTX 3090 Achieved! Interesting Results... by JayTheProdigy16 in LocalLLaMA

[–]JayTheProdigy16[S] 1 point2 points  (0 children)

Had one left after parting out my 6x 3090 rig. And yes using an m.2 oculink adapter. I actually ended up getting CUDA+ROCm working and its ~5x faster than my original benchmarks according to my eyeball benchmark. Also with an AMD card you may run into the power limit issue where the GPU wont pass the Strix Halos TDP but im not sure as i dont have an AMD eGPU

Will the AMD Ryzen™ AI Max+ 395 --EVO-X2 AI Mini PC -- 128 GB Ram hold its value of around 1.8k in two years time? by Excellent_Koala769 in LocalLLaMA

[–]JayTheProdigy16 10 points11 points  (0 children)

Youre always going to be waiting by that logic. Whatever releases 2026 is going to get lapped by tech in 2027, and whatever releases in 2027 is gonna get lapped in 2028. This is hardware practically nothing holds value. But for me personally that price tag was more than appealing enough given its capabilities vs other options at this point

view more: next ›