Rondo & Soopchik | Character dialogue

Soopchik

Hey Rondo, I just pulled a dead PS4 controller out of a trash bin, and I'm thinking of turning it into a MIDI controller for a retro synth project. Thoughts on blending that glitchy hardware with your classic yet experimental compositions?

Rondo

That’s an intriguing hack—glitchy hardware can add a raw, almost analog texture to a retro synth. Just make sure the controller’s timing is tight; any latency will taste like a deliberate delay in the mix. Use the sticks for subtle modulation, maybe map them to filter cutoff or LFO depth, so the old tech becomes part of the new voice rather than a distraction. Keep the overall structure tight—perfection is a good guide, but let the glitch breathe enough to keep it fresh.

Soopchik

Thanks, that’s solid advice. I’ll try mapping the sticks to LFO depth, but honestly, I’m still two patches away from finishing the game that I started three years ago. Also, I’m still debating whether to eat a sandwich before I lose the whole project to a power surge. Any thoughts on how to keep the latency low with a dead PS4 controller?

Rondo

If the controller’s firmware is still in its original state, the USB side is the most reliable. Plug it straight into a PC and use something like DS4Windows or OpenEmu to map the sticks to MIDI. The USB serial is usually low‑latency—under 10 ms if the PC isn’t overloaded. If you need to push it into an Arduino or Teensy, flash a simple HID‑to‑MIDI sketch; that keeps the round‑trip short. Keep the driver on a fresh Windows build or a clean Linux install—any background services will bite into the timing. For the sandwich, eat it. A proper lunch keeps the brain sharp, and you’ll be less likely to hit the power surge when you’re chasing that two‑patch finish. Keep the power strip grounded, use a UPS for the key gear, and you’ll have the stability to finish without sacrificing the groove.

Soopchik

I’ll fire up the PC, plug that dead controller straight into the USB, and fire up DS4Windows. If the timing still feels off, I’ll dump the HID‑to‑MIDI sketch on a Teensy, because those little boards are almost like having a mini‑CPU in a sock drawer. I’ll keep the system lean—no unnecessary services, one clean Windows build, and a decent UPS on the outlet. As for the sandwich, I’ll probably just grab a peanut‑butter one because it’s fast and the carbs are a good steady fuel. I’ll also set a timer so I don’t end up in a loop of tweaking the same patch until midnight. I’ve got that “two patches away” thing, so I need to keep the rhythm of the game project too. Maybe I’ll map the sticks to LFO depth first and see if the raw glitch adds that edge we want. Let’s see if the latency is under 10 ms, because if it’s 20 ms I’ll start feeling like the controller is in a time zone of its own. Sound good?

Rondo

Nice plan. Keep an eye on that 10 ms target—if it slips to 20 ms the groove starts to feel out of phase, but a Teensy will shave a few miliseconds off the round‑trip. Peanut butter gives a steady carb base, but add a splash of protein or a banana to keep the energy even. Stick to the timer and you’ll finish those two patches without the midnight tweak loop. Good luck—let the glitch be the edge, not the distraction.

Soopchik

Thanks, I’ll toss the banana in, keep an eye on the 10 ms, and make sure the power strip is grounded. I’ll also mute any background services so the controller doesn’t start a glitch rebellion. Let’s get those patches done before the midnight tweak loop starts.

Rondo

Sounds solid. Keep the timer ticking and stay disciplined—those last patches can turn into endless tweaks if you let them. Once they’re wrapped up, give yourself a moment to breathe before diving back in. Good luck.