Interesting. So if I'm reading this correctly, this is distinctly different than the artifacts that Claude creates? If that's the case, why create it inline as opposed to an artifact? Any time I get a visual, I tend to find them so useful that I _want_ them to be an artifact that I can export and share.
Anyone have any experience using this? I've been managing most of my homelab infrastructure with a combination of saltstack and docker compose files and I'm curious how this would stack up.
You know, I've never really thought about it. Yeah, I guess I do just remember the feeling and know that it's a step that I've completed. And when I recall the steps that need to be done, it's not really a cohesive spoken thought. It's like impulses of sensations? My brain is just like "Order's important. Red red, black black." without the words.
For really difficult mental tasks, I'll actually talk to myself or write things down so that they are less chaotic since the feelings/impulses in my brain may not line up. Kind of like a buffer filling up.
Now what really bothers my wife is when we talk about how we have conversations with others. I don't necessarily think about what I'm going to say verbatim when I'm talking to someone. It's impulses like I mention above where things kind of "flash" into my brain the moment before I say it. The best way that I can think of it is that it's similar to playing a sport where you have moments to change your trajectory and movement to accomplish what you want. I know thematically what I want to say, but I don't actually build the sentence in my brain.
I'll answer from my own experience (with no inner voice):
1) I have to be very explicit when reading with an inner voice (which goes to your second point). Generally, it is a kind of recognition that a word has a meaning and I "feel" that meaning, if that makes sense?
I'm a huge fan of Squarofumi. I've bought two Watchy kits and have absolutely loved coding all kinds of interesting things for them. Given that it's powered by ESP32, it makes development super easy.
Part of me wonders if it's similar to the "never carry an umbrella" dynamic? Maybe it's just a "well, this is just how it is, carry on"?
Anyway, it's probably different in our minds because in the southeast, the heat + the humidity can literally kill you. Not having AC isn't just an inconvenience there; it's an emergency.
I've had a very similar experience (both in terms of coming from the southeast and the "you don't need air conditioning here" lines). I don't know why people still say that AC isn't needed. Year over year, it seems to get worse. Add in the smoke from the fires that seems to settle in every other year, it just doesn't make sense _not_ to have AC.
A couple of summers ago, when the heat was so bad in the Seattle area, I called a local HVAC installation and repair company to talk about getting AC installed at my home (built sometime in the 80's). There was a wait list of _hundreds_ ahead of me and unit shortages. It was a nightmare. Luckily, folks seemed to reconsider installation over the winter and I was able to work our way up to the top of the line to get things installed during the winter. Best decision I've made.
Trying to figure out what's unique here, but it seems like Proxmox is being used to create VMs that then run docker. Then docker on these VMs is used to spin up a bunch of containers. So really, it's just Proxmox -> VM -> Docker -> Containers. So it's dedicated docker VMs to coordinate containers...
I was expecting Proxmox's LXC capabilities to be used to scale up to 13000, but this is just VMs + docker allowing that. Seems like the same thing could be done with any LVM hypervisor and VMs? Can someone correct me if I'm missing something?
As others have mentioned, I think the interesting thing here would be understanding the latency for processing the signal. Anything in the single digit milliseconds would be fantastic! I know at one point I was looking into Raspberry Pi and ended up on Pedal Pi[0], though I couldn't get the parts I needed to make it work.
I ended up using Teensy[1] and related audio shields[2] to get things working from a sound/acceptable delay perspective. But being able to get things going on a Pi would probably make more of the advanced input controls much simpler to implement simply from a OS support perspective (like in this project with the WebUI). The UI I'm seeing in this project looks great and it would be cool to potentially see something like kits/preinstalled images roll out for this!
You've done a fantastic job of describing what I couldn't put my finger on! One of the issues I had when developing this code was what I referred to as a "jarring" noise when distortion gain was turned up. It's like you describe: almost "metallic." I alluded to the "jarring" sound in the article, and it's great to know the culprit! There weren't a lot of repos, articles, or forum posts that had examples of solid, straightforward distortion implementations, and now I can see why.
Hopefully, we'll see someone get some code out there that helps clean this up!
OP here! I'm admittedly new to the world of digital signal processing and don't have a math background. But what I _do_ have is a background in programming and guitar effect pedal building.
My hope with this site and series is to get people like me exposed to the possibilities a little bit of code and a Teensy can unlock for them. The lower the barrier of entry, the more cool things people can create. :)
That being said, I'd love to get feedback on good sources to learn more about signal processing/theory or any resources folks would suggest for covering the topic even better!
I appreciate your feedback and sharing your knowledge! I'll definitely be digging more into some of the things your mentioned to get a better understanding. The topic is a super deep one–though my goal (at least at this point) is to stay high level enough so that anyone could get started in making their own sounds/effects.
The lower the barrier of entry, the more cool things that people can come up with! I'm hoping that more without a math/EE/audio background like myself can get started and explore some more of these deeper topics :)
Interesting, I was under the impression that aliasing was something on the presentation layer (e.g. plotting on an oscilloscope). Have some breadcrumbs/links to share that would be a good resource on understanding aliasing in your context? Would be excited to learn more!
Hey there, no aliasing in this case. As for the clipping, this is effectively just hard clipping like you'd see from two alternating diodes in series on an analog gain circuit.
Admittedly, I'm early into moving from analog circuits to digital signal processing, so I could be off the mark on my answer. :) Hope it helps, though.
This is exactly what I've been looking for, but unable to find in such an approachable format! I recently picked up guitar after almost a decade without, and I've realized that guitar tutorials online follow a similar structure as cooking recipes: full of fluff at the top and you have to scroll a while before you get to the content. Well done!
I personally find that seeing the points by comments allows me to see interesting comments while I am skimming over a thread. I wouldn't mind having points hidden if there was some way that the most commented on threads or most popular threads appeared closer to the top of the story.