Asking as a novice, how come this is such a big deal compared to just vibe coding something for an stm32 and hooking up a midi keyboard? Is it the professional enclosure + screen + hackability combo or something extra?
I spent a number of hours building a minidexed from a RPi Zero 2 and parts I already had on hand, and it still doesn't have a proper case. Add 40 buttons, 8 pots and a screen, that's an easy $20-40 worth of parts. Then there's lithium battery and charging curcuits.
Or just buy an FM-1 for $60, most musicians are not hardware hackers.
For the hardware hackers there are hundreds if not thousands of open-source projects. Infinite Digits Zeptocore immediately comes to my mind.
I grabbed one of these since I didn't have a hardware FM synth. While playing around with a web-based patch editor and seeing how well synths can run in a web, I started using AI to build out my own synths, and it's been a lot of fun. I've done FM, granular, samplers, 303 and 808 clones, and a bunch of others. So yeah, if you don't care about the experience of having a bespoke device, you could probably one-shot something much more sophisticated than this.
Yes, musical instruments represent the refinement of technology towards a very specific purpose: the creation of music.
The nature and form of the instrument directs the talents of the musician towards their desired aesthetic. In many ways, the interface informs and sculpts the final product - so instruments which are malleable (software-upgradeable) while providing a canonical haptic experience (hardware control surface) are very appealing to the modern artist.
There is a lot of innovation in the music technology world, vis a vis turning technology into an instrument of sound - but there is also a lot of stagnation, too. Whether its the ancient art of menu-diving as a performance method, or indeed if its the sudden appearance of cocktail devices with whimsy and creativity encoded in the interface, music technology offers a big, wide and often very woolly world in which to apply creative juices.
The M-VAVE is fantastics because it's cheap, it has a somewhat decent user interface layout, haptically, and now .. it is getting serious hacker attention as a boutique/unique thing to play with. Musicians - especially of the technology-aligned variety - absolutely love to one-up each other and excel in distinguishing themselves from standards - of course, musicians also love standards too - the field offers a very broad spectrum of tastes.
Vibe-coding something for the STM32 is indeed a fun thing to do from a music technology perspective - but having it in a fancy case with a battery management PMU, a decent screen with whimsy (and as little menu-diving as possible), and .. interesting sound .. is very, very appealing.
The issue is, music-technology manufacturers often take the shortest possible route to getting their interfaces implemented. Menu-diving is the scourge of music technology - at least until, that is, someone finds a way to incorporate the washing-machine method into a really kickass performance. Think Kraftwerks' reference to the Operator With Their Pocket Calculator, the mundane yet fashionable laptop-on-stage DaDa faction, and compare it to the real rock and roll of guitar and 'tradititional' instruments. The M-VAVE is an expression of the desire of music technology to not only be great (cheap!) but also full of unexplored potential. It is that unexplored potential which motivates the musician, after all ..
(EDIT: there are plenty of examples of music-hacker toys which fulfill your STM32 postulate: the monome, the Zynthian, the insanely great and fertile field of Eurorack modules, many of which did indeed first start off as some hacky STM32 project .. but there are plenty of STM32's which have found their way into a fancy, somewhat expensive case, too .. so seeing M-VAVE pitch into that world is exciting. I literally cannot wait to see what the M-VAVE will have to offer next week ..)
Were you reading through the code it was generating to make sure the flow was intuitive and comprehensible for each PR? Projects only turn in to maintainable messes if you blindly merge in unmaintainable messy code.
The law is only meant to apply to citizens of Utah though. Blocking all exit relays would mean that absolutely anyone accessing that website would not be able to do so from a VPN which burdens people outside of Utah too.
This is what I was missing. Demanding that porn sites block VPN traffic (or only accept residential traffic) would mean that everyone everywhere using a VPN gets blocked not just in Utah.
I still suspect there's some kind of solution. Like Utah could tell VPN providers that if they service a customer in Utah then the VPN provider can't route traffic to adult sites. Or put the burden on the VPN provider to do age verification if porn is gonna be available through the VPN.
Come to think of it, I'm still a bit confused as to why VPNs are even relevant because it would seem to me that age verification would be done through some kind of having-credit-card type scheme which VPNs are entirely irrelevant to. I even read the article and I'm still confused. Oh well.
I think they just meant its weird as in if you met a software dev at a dinner party who was still writing all their code by hand it would raise an eyebrow and you’d want to enquire further why that is.
I think understand the purpose of this comment. I think you're sensing friction and you'd like to reduce that by explaining for the other guy. Which is a common social script, but one that is being exploited here I'd say.
But, regardless, what is interesting I think is the scenario chosen there. Because a "dinner party" is not where engineering happens; and that's kinda the point I was getting at.
That's pulled from the pool of "social consensus" and not "math" or "physics" or whatever.
It's interesting, isn't it?
Just like how specific tokens in the context window of LLMs pull probabilities towards specific clusters of ideas (and tokens); with humans, you see similar things happen.
(This comment is more coherent than it might look at at first sight.)
___
Anyway, point (and to the point) is: Don't get hacked by the current thing fraudsters/grifters.
They don't respect you or me or really anyone the slightest. They're just in it to get rich quick (or simply just inflict psychological damage for sadistic reasons), and they will use any means necessary to do so.
This comment chain only exists because some hype guy is trying to induce FOMO into people for not doing more AI.
Why is unclear, but it's clearly malicious. Whether they consciously know that they are doing that doesn't matter for that assessment.
I think LLMs just allow you to get to where you want to get to quicker. So in a productivity oriented world it seems weird to not be making use of them where those gains can be had.
Let me try another analogy:
AI-related comment sections are like a watering hole for both get-rich-quick grifters, but also bad people wanting to hurt others.
The technology is so disruptive that there are all sorts of opportunities while stuff is still developing, things aren't regulated, and people themselves have not yet learned how to self-regulate.
So if you're looking to make money or to just inflict pain onto others, you're pulled towards this stuff.
This is what I am seeing in this specific comment sub-tree. A troll.
But in current year, you cannot just call people trolls, so instead you get these elaborate meta comments that bypass the anti-anti-troll defenses, but get so abstract, people just go "what".
My advice would be to view any of these comment sections through a zero-trust lens.
Godspeed. We will all eventually get through this.
But the screens should look different, right? That's the point of building separate iOS vs. Android versions is to make each version "native" to its platform. The feature-set should be the same, but the interfaces can diverge.
I guess theyre talking about all the electronics being used to populate the various data centre's popping up about the place. The GPUs, RAM and what not
reply