<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">For something as basic and fundamental as an op-amp, it's very likely that such a translation layer would be impossible.<div class=""><br class=""></div><div class="">if it were possible to design a translation layer, it would surely be an order of magnitude more complex than simply designing another op-amp that has the desired characteristics natively.</div><div class=""><br class=""></div><div class="">In contrast, if there is a subsystem like a power supply, then it's more plausible to translate one power supply design to another.</div><div class=""><br class=""></div><div class="">Using the software analogy, I'd say that an op-amp is like the programming language itself, rather than a collection of thousands of lines of code that can be translated. Sure, you can translate programming languages, but it takes an order of magnitude more resources than simply rewriting the code in the new language.</div><div class=""><br class=""><div><br class=""><div class="">On May 7, 2026, at 8:27 AM, Eric Honour wrote:</div><blockquote type="cite" class=""><div class=""><div dir="ltr" class="">I'm actually curious if it would be plausible to add an additional translation layer that allows a new part to behave like an old one.<div class=""><br class=""></div><div class="">In software development, there's a pattern called an "anti-corruption layer" where you basically segregate legacy code apart from cleaner, more modern code. I'm basically envisioning a hardware version of this, but inverted - a "re-corruption layer".</div></div><br class=""><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Thu, May 7, 2026 at 11:06 AM Matthew Skala via Synth-diy <<a href="mailto:synth-diy@synth-diy.org" class="">synth-diy@synth-diy.org</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Thu, 7 May 2026, Sean Ellis via Synth-diy wrote:<br class="">
<br class="">
> Just saw this thread, not sure if it was shared here.<a href="https://groupdiy.com/threads/the-new-ti-5532-chips-are-not-5532s-weve-used-" rel="noreferrer" target="_blank" class="">https://groupdiy.com/threads/the-new-ti-5532-chips-are-not-5532s-weve-used-</a><br class="">
> for-decades.93707/<br class="">
<br class="">
Sounds like the TL074H story over again.<br class="">
<br class="">
It is a genuine problem that obsolete processes can't be kept running<br class="">
indefinitely. They can't necessarily keep making a chip that they've been<br class="">
making for decades, and keep making it exactly the same way, especially<br class="">
not with the commercial reality of dwindling demand for old analog parts.<br class="">
<br class="">
If only one tech knows how to run the machine, and the output of that<br class="">
machine already doesn't sell enough to pay his salary, then when that guy<br class="">
retires it's not reasonable to expect them to have another one trained,<br class="">
and keep doing so forever. And there can be plenty of little gotchas like<br class="">
"Oh, that old analog process involved washing the die in X solvent, which<br class="">
we're no longer allowed to use for environmental reasons." At some point<br class="">
they may really have to pull the plug.<br class="">
<br class="">
But I don't understand why they can't admit that they're outright ending<br class="">
production of a given part, and assign a new part number (not just a<br class="">
suffix!) for the "better" replacement. Make it clear that it's a new part<br class="">
and not just the evolution of the old one. The supply of few-digit part<br class="">
numbers isn't infinite, but it's big enough; and keeping the reputation<br class="">
for dealing with customers honestly instead of jerking us around breaking<br class="">
our designs, ought to be worth something.<br class="">
<br class="">
-- <br class="">
Matthew Skala<br class="">
North Coast Synthesis Ltd.<br class=""></blockquote></div></div></blockquote></div><br class=""></div></body></html>