It’s <= a Radeon 7600 GPU (28 CUs RDNA3 vs 32), so I’m not sure I’d have advertised it as a 4k60 machine. Then again I’m not a marketer so what do I know. 4k60 is a flexible target with FSR I suppose.
What coordinate in the space is furthest from any named color? It looks like there are some relatively large voids in the blue/purple boundary area but it’s hard to say.
perceptual distance is quite different from Euclidean distance in this RGB space. Like if put two swaths of color side by side and said “how similar are these?” to samples of people, the groupings would not much resemble this cube.
They’ve done this! It’s shown on a “chromaticity diagram”, and is useful for comparing what colors different screens/printers/etc can reproduce. (It’s 2D not 3D cause it’s normalized for luminance or brightness.) Color science is weirdly fascinating:
For Euclidean distance it seems to be in the neighborhood of (59, 250, 60) which is a bright green, although of course Euclidean distance is not perceptual distance. The blue at (57, 42, 214) also is up there.
Pick points at random, then use a general-purpose optimization method (the optim function in R) to find local maxima. I don’t claim this is a good way to do it.
I think I’d buy something with Strix Halo or Strix Point if there was official ROCm support. As of 6.4.1 from earlier this month there’s still not, as I understand it. I’d be delighted to be corrected on this matter.
There is (unofficial) ROCm support for Strix Halo with ROCm 6.4.1. But like Llama.cpp and such were seg faulting but ROCR-based OpenCL was working and other workloads.
I haven't gotten around to trying it but it's on my TODO list if having the time before needing to send the review unit back (likely next week or so I'd expect)
What’s AMD's strategy in not having consumer chip support for ROCm? It's puzzling. No way to get critical mass of development interest if the bar to entry is high.
I think that part of the issue is the split between CDNA for data centers [1] and RDNA for consumer products [2] with AMD only having the money to focus on the bigger data center market. There are rumors that both architectures will be merged into UDNA in the future, which will hopefully improve ROCm support, but for now it's lacking
The strategy (seems to be) targeting data centres and focusing support efforts on the cards most likely to be used in one. There is an expectation that ROCm will work on pretty much everything but their drivers aren't good so in practice it is dicey whether it actually does.
You can run theoretically run ollama on it, as with the earlier APUs (I did it on an M780 by allocating 16 of the machine's 32GB to the iGPU). I am _very_ interested in getting my hands on one because I see it as a decent compromise between power, RAM capacity (with soldered-on RAM, it's got pretty good latency) and performance.
The article goes on to say what the author thinks is bad about this:
> We’re not raising emotionally intelligent kids. We’re raising kids to navigate human unpredictability as if it’s a design flaw. Because when you grow up with a machine that always gets you, messy human behavior feels broken. We’re not preparing kids to handle people.
I don’t think there’s anything wrong with escaping into fantasy in the right time and place, but young kids (and even well-adjusted adults) can have problems self-moderating and letting fantasy substitute for engaging with reality.
I compiled it for Ampere and counted 6834 actual F32 operations in the SASS after optimizations. I only counted FFMA, FADD, FMUL, FMNMX, and MUFU.RSQ after eyeballing the SASS code, so there might even be more. It's possible the FMNMX doesn't actually take a FLOP since you can do f32 max as an integer operation, and perhaps MUFU.RSQ doesn't either, but even if you only count FFMA, FADD, and FMUL there are still 3685 ops.
I basically have an even simpler version of something like this for my own personal use too. I found it pretty easy to write in Go and my area of expertise is decidedly not web frontend/backend. I’d recommend it as a fun little project if you’re looking for something to do.
For mine, I paste in a video or playlist URL and it downloads the video and creates a lower resolution transcoded version suitable for streaming to my phone. It also extracts an audio-only version in case that’s more appropriate.
I have one too, it's honestly a very fun area to program around, and I'm not going to be surprised if this thread is full of me-toos.
Mine is specifically meant to help get videos onto plex in exactly the way we want - with particular emphasis on playlists, taking the numbering and putting it in plex format, and transcoding any codecs (detected via ffprobe) i know certain shitty players (smart TVs) will have issues with. Along with putting it in the right spot on the filesystem with the right permissions and user+group set so it serves correctly over samba too (for management from windows / via GUI).
Plex is the destination for my setup, too. I have a bookmarklet I can click when I'm on any Youtube (or other video) page that sends the URL to a local Flask app that's just a wrapper for calling yt-dlp with the right args and post-processing.
I have something similar as a simple PHP script on a shared hosting service. I can't PHP well anymore so it's probably the worst and most insecure code I've produced by a big margin. Does it do the job? Yes.
No unfortunately, not only is it too tangled (not irredeemably, but I've never made an effort t try to make it cleanly ploppable) with the rest of my home-rails-server monolith, but the code is all also ridiculously bad, written in 2000 separate 5 minute scraps of time, all while standing up and holding at least one baby.
My reading of OP is that it’s less about whether zopfli is technically the best way to achieve a 5% reduction in package size, and more about how that relatively simple proposal interacted with the NPM committee. Do you think something like this would fare better or differently for some reason?
> Starting from version 6.6 of the Linux kernel, [CFS] was replaced by the EEVDF scheduler.[citation needed]