Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "synthesizer"
-
Client: "we need a piece of software to have our son be able to talk again"
Me: "what can your son do physically?"
Client: "He can only grip something"
Me: "well, I suppose that is possible by using Intel ACAT, some synthesizer and some switches"
Client: "Never heard of ACAT, probably some small program that nobody else heard of"
Me: "It was used by a great man called Stephen Hawking. If it worked for him, it should work for your son"
Client: "Who is Stephen Hawking?"
Me: *urge to put client in wheelchair intensifies*14 -
I didn't knew it was this expensive....
(cries in the corner)
Price: $1,302.94
https://amazon.com/gp/product/...13 -
AAARGH ELECTRON IS SO FUCKING...decently pleasant to use?
So I've been working on a FPGA based synthesizer on a Xilinx Arty A7 board (that little Artix 35T chip is surprisingly capable), and since I hate typing commands into a serial stream for anything even decently complex just like any sane person should, I needed something to build a UI for controlling it and other synth projects while I make the Eurorack compatible enclosure and knobs and stuff. I chose Electron because they said it was simple and easy to make cool looking stuff, fast.
And they were right. In like two hours, with Electron and p5.js, starting from zero since I don't know jack about frontend, I had a pretty nice UI driving the hardware synth and effects modules. Not bad. I should use this more often.11 -
Years ago when I was a kid I was into making things to solve problems. Earlier in my life I remember as a kid seeing a neighbor shove 120VAC into the ground to get worms to come up to the surface. I also remember taking a worm and slapping it on one of the posts and shocking the shit out of myself. Apparently that lesson did not stick.
As a teenager I wanted a device similar to this. So I wired a 120VAC plug and cord to a 1/4" audio connector. I threw this in a box and forgot about it. Years later my sister went through my things looking for a power plug for a synthesizer we had. It had an audio 1/4" plug for headphones. She told me she plugged this cord she found of mine into the synth and it started smoking. She went to pull the plug out and shocked the shit out of her. I don't think that the synth ever worked correctly after that.
Well, today I was thinking fondly about that story. I mean, who wouldn't think fondly about shocking the shit out of your sister (she didn't die, so its okay). However, it was dangerous. Really really dangerous.
The lesson I can take from this memory is this: if you know a software interface (or electrical) is not safe then don't build it. Someone will try and use that shit years later and really fuck some stuff up. I have to wonder. What kind of software traps have I built in the past that are yet to be discovered?3 -
Hmm... My first experience with computers was in 1991 or so, when my then best friend had C64. And I was 7. My first PC arrived in 1993. Prince of Persia is the first game I remember from that time. I started programming in 1995 or '96, writing useless things in Pascal. Using PHP since 2000. Still that’s my main programming language. And sadly, my kids have different hobbies than me, so they aren’t even trying to program.
I remember the sound of modem connecting thru phone line to some BBS systems and later to the first public and free internet service in Poland. I remember simple, really „computer-like” voice of my dad’s speech synthesizer (he’s blind person). I remember, when our time to „play on PC” was limited to max 1hr a day... What will our kids remember? -
I don't know docker. Could it possibly make sense, at least for development, to containerize a digital synthesizer so people don't have to mess with Portaudio?