Aus dem KVR Forum - Sehr Interessante Infos von Entwickler:
"Hi everyone, John from Temecula DSP here. I saw the discussion and wanted to jump in and say hello! First off, thanks for the excitement around DEEP/4. The original hardware is a beast, and recreating it was a massive passion project.
I wanted to hop in to address some of the comments regarding my development process and my use of AI, as I've always aimed to be 100% transparent about how I work.
I saw the comment asking "painstaking for who, exactly?"—which is a completely fair question! To clarify: the painstaking part is the human element. I have 25 years of experience in reverse engineering, circuit analysis, and programming. A.I. has given me the leverage to combine my talents and scale out my ideas without needing a team to do it with. Prior to starting my own independent company, I worked for an Audio/Visual company developing media supply chain software.
For DEEP/4, I manually analyzed the original 24-bit fixed-point architecture and the ES5510 DSP engines to ensure a mathematically accurate 1:1 match. That architecture design and analysis was entirely manual labor. For the Stargate (one of my other plugins), I actually created a model in Logisim of the DSP schematic and had Claude write a Python model to prove it out. I traced every single wire myself on that schematic and verified all the Python. You can read a blog post about my findings here:
https://www.temeculadsp.com/journal/ana ... argate-626
Regarding the AI side (and the "vibe coding" comments): Once that rigorous human engineering is done, I use Claude essentially as a highly advanced compiler. It translates my architectural design into code syntax. It condenses what would be a year of typing into months, which allows me to focus purely on the audio fidelity and exact behavior of the emulation. It still requires an expert architect to direct it, verify it, line-by-line, and refine it. It's a modern workflow that allows a solo dev to bring a massive 43-algorithm project like the DP/4 to life at an accessible price.
Finally, as with any complex 1.0 software release, edge cases and bugs in different DAWs can happen—whether the syntax was typed by a human or generated by an AI assistant. I am actively supporting this release, so if you run into any weird behaviors or feedback loops, please drop a note here or contact me directly so I can get them squashed!
Thanks again for the interest, and I’m happy to answer any questions you guys have about the plugin or the development process.
Cheers,
John"