Thanks @neumann and @nate for #clojuredesign-podcast! Both the new episodes and the old ones. They are playing in my ears a lot this week because I am preparing for holding an introductory course to Clojure. Never designed or held a course before so I am pretty nervous. You two calm me down, because you are so friendly and obviously are having really fun while you fill in my many blanks. Itβs so worth re-listening because a lot of things click this time, that I let fly over my head the first time(s) I listened. Still not quite getting juxt, even though I sometimes just can use it (weird!). Your take on it is fantastic in helping me to a more conscious understanding of juxt and more. Itβs so generous of you to take of your time to share all that with us! gratitude β€οΈ π
@pez Thank you so much! I'm so happy to hear that! You've made my week! And yes, juxt is full of deep mysteries. @nate and I have had fun reading through the https://porkostomus.gitlab.io/tags-output/juxt/. (Thanks @porkostomus!) I'd be happy to take a look any of your materials for your course. Just DM me about it. And, of course, I must thank you for #calva and how you've helped so many people in the Clojure community!
@neumann Getting slightly off topic here, but what do you recommend for simple audio processing like that?
On the subject of "calm me down", I don't know if there's some intentional sound leveling in your process or if it's just the way you guys talk, but whatever you're doing makes your podcast a great one to fall asleep to because I can listen at a low volume and not strain to hear certain quiet parts or get startled by louder parts. I'll often listen to the same episode several nights in a row and let the ideas soak while I sleep. So.. thanks for putting me to sleep with the podcast (but in a good way) π
@neumann I will probably take you up on input for the material. Super generous offer! π
@jason.bullers @pez I take your meaning in the pest possible way! You guys are so kind and encouraging. Thank you! On the technical side, I do process the audio. I have separate tracks for @nate and myself. I "normalize" -> "compress" -> "normalize". 1. Normalize: gets the overall volume of each track to a roughly equal "normal" listening level 2. Compress: pushes down the louder parts to be more similar to the quieter parts. My goal is to keep the dynamic range fairly low. This isn't a movie, after all! 3. Normalize: brings the overall volume of each track back to a "normal" listening level since compressing makes everything quieter I've done a fair amount of audio work in the past, so I geek out over this stuff!
Ah, cool! Nice insight in to the process. My ears thank you for the effort π