Julian Rubisch

To render waveforms, peaks.js and wavesurfer both want precomputed data. Usually you need to run audiowaveform on your data (or a custom analyzer) and procure the data on request.

Here's the post, with a Rails helper for ActiveStorage at the end: audioproxy.dev/blog/wavefor...

To render waveforms, peaks.js and wavesurfer both want precomputed data. Usually you need to run audiowaveform on your data (or a custom analyzer) and procure the data on request.

Find out what works, they say, and do more of that. Well, something that always „worked“ for me is my passion for music, audio, and sound art. So I‘m doubling down on that 🧵👇

And finally, I‘m also doing audio product work: soundlogo.co

Find out what works, they say, and do more of that. Well, something that always „worked“ for me is my passion for music, audio, and sound art. So I‘m doubling down on that 🧵👇

More recently, and an indirect outcome of that, I’ve published audioproxy.dev, an open source, drop in solution to transcode, edit, trim, normalize audio on the fly.

Find out what works, they say, and do more of that. Well, something that always „worked“ for me is my passion for music, audio, and sound art. So I‘m doubling down on that 🧵👇

After I published The Vibe Coder's Sound Check, I was approached by a founder building on Softr. The setup was clear: A no-code solution with vibe coded parts that needed human judgment.

The TLDR is that the deploy step that's been removed was doing an actual job. It was making sure that the natural anxiety that goes with publishing your software had a natural crystallization point, where it was felt and dissolved, not blocked out.

After I published The Vibe Coder's Sound Check, I was approached by a founder building on Softr. The setup was clear: A no-code solution with vibe coded parts that needed human judgment.

Calling all podcast hosters, social networks, CMSes - everybody who hosts audio content and needs to transcode, edit, distribute it in large quantities. I’ve created something that might be genuinely useful for you: docs.audioproxy.dev

Capabilities, in short: - apply transforms as URL parameters - signed URLs - fully cacheable by CDNs and/or a configured variant store - S3 and local file sources - built on Elixir/BEAM for maximum stability - built-in backpressure and queue contention management

To make ImPulsar4 more widely available and playable I've decided to mold it into an interactive web art piece that follows precisely the same mechanics as the installation, but allows you to interact with it. impulsar4.julianrubisch.at #SoundArt #ExperimentalMusic #SpatialAudio #GenerativeArt

To make ImPulsar4 more widely available and playable I've decided to mold it into an interactive web art piece that follows precisely the same mechanics as the installation, but allows you to interact with it. impulsar4.julianrubisch.at #SoundArt #ExperimentalMusic #SpatialAudio #GenerativeArt

New Hotwire Club challenge! I learned this technique from @domchristie.bsky.social , and it's a really slick one: Turn a controller into an asynchronously callable API via Promise Returning Outlets: hotwire.club/blog/2026-07...

A while back I asked my Patreon subscribers to vote for what set of tools I should extract from the > 50 challenges we've been solving over the last years. Today I can proudly ship the first one: an Optimistic Form Builder, check it out: github.com/TheHotwireCl...