• TI degrading specs of existing parts without changing part numbers

    From Chris Jones@3:633/10 to All on Wednesday, June 03, 2026 23:10:06
    https://www.youtube.com/watch?v=22ZmmZ67SMY

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From John R Walliker@3:633/10 to All on Wednesday, June 03, 2026 15:00:47
    On 03/06/2026 14:10, Chris Jones wrote:
    https://www.youtube.com/watch?v=22ZmmZ67SMY

    This looks horrendous.
    How to destroy your reputation in one easy lesson.
    John


    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Chris Jones@3:633/10 to All on Thursday, June 04, 2026 00:12:34
    On 4/06/2026 12:00 am, John R Walliker wrote:
    On 03/06/2026 14:10, Chris Jones wrote:
    https://www.youtube.com/watch?v=22ZmmZ67SMY

    This looks horrendous.
    How to destroy your reputation in one easy lesson.
    John


    Supposedly they enshittified the TL072 as well.


    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Wednesday, June 03, 2026 07:39:04
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    They changed the process on a part that's 47 years old.

    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From John R Walliker@3:633/10 to All on Wednesday, June 03, 2026 16:12:27
    On 03/06/2026 15:39, john larkin wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    They changed the process on a part that's 47 years old.

    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    When you significantly degrade a couple of parameters
    that are important for many users of that part and
    don't provide a means of knowing whether you have
    the original part or the degraded imitation, then
    yes, it is scandalous. Especially when the ECN
    tells buyers that the changes will have no impact.
    John


    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Wednesday, June 03, 2026 08:37:22
    On Wed, 3 Jun 2026 16:12:27 +0100, John R Walliker
    <jrwalliker@gmail.com> wrote:

    On 03/06/2026 15:39, john larkin wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    They changed the process on a part that's 47 years old.

    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    When you significantly degrade a couple of parameters
    that are important for many users of that part and
    don't provide a means of knowing whether you have
    the original part or the degraded imitation, then
    yes, it is scandalous. Especially when the ECN
    tells buyers that the changes will have no impact.
    John

    It is impressive that TI keeps parts in production for decades, almost
    5 in this case.

    This part belongs in the 555 timer and uA741 and 2N3055 generation,
    getting creaky before most of my enginers were born. Or before their
    parents were born.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Martin Rid@3:633/10 to All on Wednesday, June 03, 2026 11:42:26
    Chris Jones <lugnut808@spam.yahoo.com> Wrote in message:r
    https://www.youtube.com/watch?v=22ZmmZ67SMY

    Well you could use the tlv9362.

    Cheers
    --


    ----Android NewsGroup Reader---- https://piaohong.s3-us-west-2.amazonaws.com/usenet/index.html

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Thursday, June 04, 2026 02:04:25
    On 3/06/2026 11:10 pm, Chris Jones wrote:

    <snipped U-tube link>

    I hate U-tube and didn't watch it, but I suspect Texas Instruments is
    still doing what it did back in 1974 - changing the numbers in the specification of an industry standard part.

    At George Kent back in 1974 we had our own part numbers, and the
    engineers had the job of setting up a specification sheet and filling in
    the numbers and identifying which manufacturers parts could be bought
    against that part number.

    I repeatedly found that the Texas Instruments "industry standard" parts weren't. Their data sheet for that part number would specify looser
    limits and poorer typical values than the rest of the industry.

    The U-tube link starts off on this this part

    https://www.onsemi.com/download/data-sheet/pdf/ne5532-d.pdf

    https://www.ti.com/lit/ds/symlink/ne5532.pdf?ts=1780440996215&ref_url=https%253A%252F%252Fwww.google.com%252F

    I couldn't see any obvious differences between the TI and the On-Semi
    data sheets, but I didn't look all that hard. I don't think that Texas Instruments is destroying their reputation - they are just confirming it.

    --
    Bill Sloman, Sydney


    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From John R Walliker@3:633/10 to All on Wednesday, June 03, 2026 18:16:51
    On 03/06/2026 17:04, Bill Sloman wrote:
    On 3/06/2026 11:10 pm, Chris Jones wrote:

    <snipped U-tube link>

    I hate U-tube and didn't watch it, but I suspect Texas Instruments is
    still doing what it did back in 1974 - changing the numbers in the specification of an industry standard part.

    At George Kent back in 1974 we had our own part numbers, and the
    engineers had the job of setting up a specification sheet and filling in
    the numbers and identifying which manufacturers parts could be bought against that part number.

    I repeatedly found that the Texas Instruments "industry standard" parts weren't. Their data sheet for that part number would specify looser
    limits and poorer typical values than the rest of the industry.

    The U-tube link starts off on this this part

    https://www.onsemi.com/download/data-sheet/pdf/ne5532-d.pdf

    https://www.ti.com/lit/ds/symlink/ne5532.pdf? ts=1780440996215&ref_url=https%253A%252F%252Fwww.google.com%252F

    I couldn't see any obvious differences between the TI and the On-Semi
    data sheets, but I didn't look all that hard. I don't think that Texas Instruments is destroying their reputation - they are just confirming it.

    The key differences are that the same TI part number has reduced its
    absolute max supply voltage from 22V to 18V and substantially
    reduced the output drive capability. They have removed the spec
    for driving into 600 ohm loads. The main use for these parts is in
    audio system where driving 600 ohm loads is often a requirement.
    I don't have a problem with them stopping the manufacture of an
    ancient part and recommending a replacement. They should not
    take a completely different design and try to pass it off as the
    original and keep the exact same part number they were using
    previously. The design really is completely different.
    The comparison is between different editions of the same TI
    data sheet.
    One advantage of using automotive parts is that such changes
    are very unlikely. Car manufacturers would not tolerate it.
    I was once sitting in on a meeting when a car manufacturer told
    a well known semiconductor manufacturer to spend another
    USD500k on requalifying a part that had been changed. The semi
    manufacturer immediately agreed to do it.


    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From piglet@3:633/10 to All on Wednesday, June 03, 2026 20:22:24
    On 03/06/2026 16:37, john larkin wrote:
    On Wed, 3 Jun 2026 16:12:27 +0100, John R Walliker
    <jrwalliker@gmail.com> wrote:

    On 03/06/2026 15:39, john larkin wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    They changed the process on a part that's 47 years old.

    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    When you significantly degrade a couple of parameters
    that are important for many users of that part and
    don't provide a means of knowing whether you have
    the original part or the degraded imitation, then
    yes, it is scandalous. Especially when the ECN
    tells buyers that the changes will have no impact.
    John

    It is impressive that TI keeps parts in production for decades, almost
    5 in this case.

    This part belongs in the 555 timer and uA741 and 2N3055 generation,
    getting creaky before most of my enginers were born. Or before their
    parents were born.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    All great parts - technically obsolete but will be available forever
    from thousands of sources - if your application can use them then why
    use anything else?

    piglet


    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Thursday, June 04, 2026 14:56:42
    On 4/06/2026 3:16 am, John R Walliker wrote:
    On 03/06/2026 17:04, Bill Sloman wrote:
    On 3/06/2026 11:10 pm, Chris Jones wrote:

    <snipped U-tube link>

    I hate U-tube and didn't watch it, but I suspect Texas Instruments is
    still doing what it did back in 1974 - changing the numbers in the
    specification of an industry standard part.

    At George Kent back in 1974 we had our own part numbers, and the
    engineers had the job of setting up a specification sheet and filling
    in the numbers and identifying which manufacturers parts could be
    bought against that part number.

    I repeatedly found that the Texas Instruments "industry standard"
    parts weren't. Their data sheet for that part number would specify
    looser limits and poorer typical values than the rest of the industry.

    The U-tube link starts off on this this part

    https://www.onsemi.com/download/data-sheet/pdf/ne5532-d.pdf

    https://www.ti.com/lit/ds/symlink/ne5532.pdf?
    ts=1780440996215&ref_url=https%253A%252F%252Fwww.google.com%252F

    I couldn't see any obvious differences between the TI and the On-Semi
    data sheets, but I didn't look all that hard. I don't think that Texas
    Instruments is destroying their reputation - they are just confirming it.

    The key differences are that the same TI part number has reduced its
    absolute max supply voltage from 22V to 18V and substantially
    reduced the output drive capability.˙ They have removed the spec
    for driving into 600 ohm loads.˙ The main use for these parts is in
    audio system where driving 600 ohm loads is often a requirement.
    I don't have a problem with them stopping the manufacture of an
    ancient part and recommending a replacement.˙ They should not
    take a completely different design and try to pass it off as the
    original and keep the exact same part number they were using
    previously.˙ The design really is completely different.
    The comparison is between different editions of the same TI
    data sheet.

    That's really bad. Purchasing departments aren't expected to read data
    sheets, and they really shouldn't have to cope with data sheet changes
    from one order to the next.

    Shrinking a part so that it is more likely to blow up if briefly
    over-loaded does create problems, but if the transient handling capacity
    isn't specified on the data sheet you don't have any right to sue.

    Changing the data sheet is criminal.

    One advantage of using automotive parts is that such changes
    are very unlikely.˙ Car manufacturers would not tolerate it.
    I was once sitting in on a meeting when a car manufacturer told
    a well known semiconductor manufacturer to spend another
    USD500k on requalifying a part that had been changed. The semi
    manufacturer immediately agreed to do it.

    People like us, and small scale manufacturers in general, exploit the
    mass market create by people who buy in bulk.

    If the people who buy in bulk change their ordering habits, we can be
    left high and dry.

    The disappearance of wide-band (5GHz or better) PNP transistors is a
    recent example.

    --
    Bill Sloman, Sydney

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Liz Tuddenham@3:633/10 to All on Thursday, June 04, 2026 10:25:02
    Bill Sloman <bill.sloman@ieee.org> wrote:

    [...]
    I repeatedly found that the Texas Instruments "industry standard" parts weren't. Their data sheet for that part number would specify looser
    limits and poorer typical values than the rest of the industry.

    Perhaps they were telling the truth and the others were stretching it a
    bit?

    A firm I worked for often quoted specs that were so far below the actual performance that one of our sets almost met spec. with one of the
    transistors soldered in backwards. This understatement meant that their
    sets had a reputation for always meeting the specification - even after
    the customer had tried to 'improve' them.

    It was only when the bean-counters began over-ruling the engineers that
    sets with better specs on paper but worse or unreliable performance
    began to out-sell them.

    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Thursday, June 04, 2026 20:21:49
    On 4/06/2026 7:25 pm, Liz Tuddenham wrote:
    Bill Sloman <bill.sloman@ieee.org> wrote:

    [...]
    I repeatedly found that the Texas Instruments "industry standard" parts
    weren't. Their data sheet for that part number would specify looser
    limits and poorer typical values than the rest of the industry.

    Perhaps they were telling the truth and the others were stretching it a
    bit?

    Seems unlikely.

    A firm I worked for often quoted specs that were so far below the actual performance that one of our sets almost met spec. with one of the
    transistors soldered in backwards. This understatement meant that their
    sets had a reputation for always meeting the specification - even after
    the customer had tried to 'improve' them.

    Specs tend to reflect what you can test quickly rather than actual performance.

    MOSFETs typically had picoamp leakage through the gate, but waiting for
    long enough for the leakage current to build up to a respectable voltage wasn't an option for production line testing.

    It was only when the bean-counters began over-ruling the engineers that
    sets with better specs on paper but worse or unreliable performance
    began to out-sell them.

    The bean-counters mostly don't know what they are doing. This is - in
    practice - where the problems usually come from.

    Educating managers is definitely part of an engineers job, and managers
    are remarkably resistant to the idea that they need education.

    --
    Bill Sloman, Sydney



    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Chris Jones@3:633/10 to All on Thursday, June 04, 2026 21:56:53
    Subject: Re: Re:TI degrading specs of existing parts without changing part numbers

    On 4/06/2026 1:42 am, Martin Rid wrote:
    Chris Jones <lugnut808@spam.yahoo.com> Wrote in message:r
    https://www.youtube.com/watch?v=22ZmmZ67SMY

    Well you could use the tlv9362.

    Cheers

    I'm not saying there isn't an alternative, I am saying that if they have
    to reduce the maximum supply voltage spec, or similar important ones,
    they should just say the old part is obsolete, and provide a new part
    number for whatever they can make.



    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From legg@3:633/10 to All on Thursday, June 04, 2026 10:38:04
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info
    on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick
    this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI
    never showed up, in the first place.

    RL

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Phil Hobbs@3:633/10 to All on Thursday, June 04, 2026 15:22:02
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info
    on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick
    this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI
    never showed up, in the first place.

    RL


    If I hadn?t stopped talking audio design seriously in about 1980, I
    certainly would have when crappy compressed MP3s took over the world.

    Golden ears, my left buttock.

    Cheers

    Phil Hobbs

    --
    Dr Philip C D Hobbs Principal Consultant ElectroOptical Innovations LLC / Hobbs ElectroOptics Optics, Electro-optics, Photonics, Analog Electronics

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From JM@3:633/10 to All on Thursday, June 04, 2026 16:54:29
    On Thu, 4 Jun 2026 15:22:02 -0000 (UTC), Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:

    Golden ears, my left buttock.

    Your buttocks have ears?

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Jan Panteltje@3:633/10 to All on Thursday, June 04, 2026 16:58:08
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net>wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info
    on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick
    this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI
    never showed up, in the first place.

    RL


    If I hadn?t stopped talking audio design seriously in about 1980, I
    certainly would have when crappy compressed MP3s took over the world.

    I was very impressed with mp3 compression first time I heard it
    So many audio files on a small memory.

    Same goes for MPEG compression for video.


    Golden ears, my left buttock.

    Have you ever heard a Quad electrostat?
    https://en.wikipedia.org/wiki/Quad_Electrostatic_Loudspeaker

    First time I heard that one was when attending some music group playing in a church
    and using it to amplify their stuff..
    Something I never forgot.
    In the studio audio rooms we had Quads too.
    I have considered many times to buy one, but my current speakers are OK too, can be very impressive.
    Lots depend on the acoustic, some churches have great acoustics.
    My living room is OK at high volume, else those YouAsh F35s crossing over my head almost every day
    need too much audio power, well I have plenty watts... would need earplugs..

    Have some old Sennheiser HD210 headphones too, good when practicing playing the keyboard.
    http://www.dancetech.com/item.cfm?threadid=879




    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Liz Tuddenham@3:633/10 to All on Thursday, June 04, 2026 18:42:35
    Jan Panteltje <alien@comet.invalid> wrote:

    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net>wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info
    on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick
    this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI
    never showed up, in the first place.

    RL


    If I hadn?t stopped talking audio design seriously in about 1980, I >certainly would have when crappy compressed MP3s took over the world.

    I was very impressed with mp3 compression first time I heard it

    ...but it doesn't sound so good by the second or third generation.

    The difference between the original AIFF file and a first generation mp3
    at a moderate compression rate is audible when both are electrically
    recorded to a wax cylinder. Sometimes, when a 78 is transferred to mp3,
    the results can be excruciating because the algorithm favours the
    scratch over the music.


    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Jan Panteltje@3:633/10 to All on Friday, June 05, 2026 07:33:37
    =?UTF-8?Q?Niocl=C3=A1s_P=C3=B3l_Caile=C3=A1n?= de Ghloucester <thanks-to@Taf.com>wrote:
    Jan Panteltje <alien@comet.invalid> schreef: >|----------------------------------------------------------------|
    |"I was very impressed with mp3 compression first time I heard it|
    |So many audio files on a small memory. |
    | |
    |Same goes for MPEG compression for video." | >|----------------------------------------------------------------|

    Commonly used resources for MPEG-4 audio are defective. Cf. e.g. >HTTP://Gloucester.Insomnia247.NL/FFMPEG_etc/Overcoming_MPEG-4_incompatibility.HTM
    (S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)

    Have you ever used 'sox' in Linux?
    From
    man sox
    NAME
    SoX - Sound eXchange, the Swiss Army knife of audio manipulation

    SYNOPSIS
    sox [global-options] [format-options] infile1
    [[format-options] infile2] ... [format-options] outfile
    [effect [effect-options]] ...

    play [global-options] [format-options] infile1
    [[format-options] infile2] ... [format-options]
    [effect [effect-options]] ...

    rec [global-options] [format-options] outfile
    [effect [effect-options]] ...

    DESCRIPTION
    Introduction
    SoX reads and writes audio files in most popular formats and can optionally apply effects to them.
    It can combine multiple input sources, synthesise audio, and, on many systems,
    act as a general purpose audio player or a multi-track audio recorder.
    It also has limited ability to split the input into multiple output files.

    All SoX functionality is available using just the sox command.
    To simplify playing and recording audio, if SoX is invoked as play, the output file is automatically set to be the default sound device,
    and if invoked as rec, the default sound device is used as an input source.
    Additionally, the soxi(1) command provides a convenient way to just query audio file header information.
    The heart of SoX is a library called libSoX.
    Those interested in extending SoX or using it in other programs should refer to the libSoX manual page: libsox(3).

    SoX is a command-line audio processing tool, particularly suited to making quick, simple edits and to batch processing.
    If you need an interactive, graphical audio editor, use audacity(1).
    I use it sometimes to make test signals, audio sweeps what not.

    ffmpeg is useful too, as is mpg123,
    Much more free audio stuff exists for Linux:
    raspberrypi: ~ # apropos audio
    alsa_in (1) - Jack clients that perform I/O with an alternate audio interface
    alsa_out (1) - Jack clients that perform I/O with an alternate audio interface
    axfer-list (1) - dump lists of available sound devices and nodes to transfer audio data frame.
    axfer-transfer (1) - transferrer of audio data frame for sound devices and nodes.
    default.pa (5) - PulseAudio Sound Server Startup Script jack_monitor_client (1) - The JACK Audio Connection Kit example client jack_showtime (1) - The JACK Audio Connection Kit example client jack_simple_client (1) - The JACK Audio Connection Kit example client jack_unload (1) - The JACK Audio Connection Kit example client
    jackd (1) - JACK Audio Connection Kit sound server
    jackrec (1) - JACK toolkit client for recording audio
    lame (1) - create mp3 audio files
    mediainfo (1) - command line utility to display information about audio/video files
    mp3-decoder (1) - play audio MPEG 1.0/2.0/2.5 stream (layers 1, 2 and 3) mpg123 (1) - play audio MPEG 1.0/2.0/2.5 stream (layers 1, 2 and 3) mpg123-alsa (1) - play audio MPEG 1.0/2.0/2.5 stream (layers 1, 2 and 3) mpg123-jack (1) - play audio MPEG 1.0/2.0/2.5 stream (layers 1, 2 and 3) mpg123-nas (1) - play audio MPEG 1.0/2.0/2.5 stream (layers 1, 2 and 3) mpg123-openal (1) - play audio MPEG 1.0/2.0/2.5 stream (layers 1, 2 and 3) mpg123-oss (1) - play audio MPEG 1.0/2.0/2.5 stream (layers 1, 2 and 3) mpg123-portaudio (1) - play audio MPEG 1.0/2.0/2.5 stream (layers 1, 2 and 3) mpg123-pulse (1) - play audio MPEG 1.0/2.0/2.5 stream (layers 1, 2 and 3) mpg123.bin (1) - play audio MPEG 1.0/2.0/2.5 stream (layers 1, 2 and 3) out123 (1) - send raw PCM audio or a waveform pattern to an output device
    pacat (1) - Play back or record raw or encoded audio streams on a PulseAudio sound server
    pacmd (1) - Reconfigure a PulseAudio sound server during runtime pactl (1) - Control a running PulseAudio sound server
    padsp (1) - PulseAudio OSS Wrapper
    pamon (1) - Play back or record raw or encoded audio streams on a PulseAudio sound server
    paplay (1) - Play back or record raw or encoded audio streams on a PulseAudio sound server
    parec (1) - Play back or record raw or encoded audio streams on a PulseAudio sound server
    parecord (1) - Play back or record raw or encoded audio streams on a PulseAudio sound server
    pasuspender (1) - Temporarily suspend PulseAudio
    pax11publish (1) - PulseAudio X11 Credential Utility
    play (1) - Sound eXchange, the Swiss Army knife of audio manipulation
    pulse-cli-syntax (5) - PulseAudio Command Line Interface Syntax pulse-client.conf (5) - PulseAudio client configuration file
    pulse-daemon.conf (5) - PulseAudio daemon configuration file
    pulseaudio (1) - The PulseAudio Sound System
    qjackctl (1) - User interface for controlling JACK (Jack Audio Connection Kit)
    rec (1) - Sound eXchange, the Swiss Army knife of audio manipulation
    scsynth (1) - SuperCollider audio synthesis server
    sox (1) - Sound eXchange, the Swiss Army knife of audio manipulation
    soxeffect (7) - Sound eXchange, the Swiss Army knife of audio manipulation
    soxformat (7) - Sound eXchange, the Swiss Army knife of audio manipulation
    start-pulseaudio-x11 (1) - PulseAudio Sound Server X11 Startup Script raspberrypi: ~ #

    And that is just the default install....

    raspberrypi: ~ # apropos sound
    and all the stuff I wrote myself of course
    https://panteltje.nl/panteltje/newsflex/download.html#freq_pi
    https://panteltje.nl/panteltje/newsflex/download.html#xpequ
    https://panteltje.nl/panteltje/newsflex/download.html#humfilter
    there is a lot more, if I need something I just write the code if it is not available
    Audio is just one thing, there is video too.



    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Jan Panteltje@3:633/10 to All on Friday, June 05, 2026 08:00:21
    liz@poppyrecords.invalid.invalid (Liz Tuddenham)wrote:
    Jan Panteltje <alien@comet.invalid> wrote:

    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net>wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info
    on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick
    this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI
    never showed up, in the first place.

    RL


    If I hadn?t stopped talking audio design seriously in about 1980, I
    certainly would have when crappy compressed MP3s took over the world.

    I was very impressed with mp3 compression first time I heard it

    ...but it doesn't sound so good by the second or third generation.

    The difference between the original AIFF file and a first generation mp3
    at a moderate compression rate is audible when both are electrically
    recorded to a wax cylinder. Sometimes, when a 78 is transferred to mp3,
    the results can be excruciating because the algorithm favours the
    scratch over the music.

    Sure, but I do not use wax cylinders, have never used those ..
    You can hear differences between a wav file and mp3 file made from it.
    But when listening to music for me it does not matter.
    I have an old Muvo mp3 player that I often let play
    through my Sennheiser HD210 headphones, next to the bed,
    all night long on a Eneloop AAA battery.
    It has lots of nice music pieces added together as one long file and is in repeat mode.
    makes me sleep better.
    Works on the road too.
    https://en.wikipedia.org/wiki/Creative_MuVo

    But then I am no 'audiophile' I just like [some] music
    Was playing 'Unchained melody' on my keyboard last night,
    needs some more work.
    https://www.youtube.com/watch?v=GjRLwYs-FXE
    https://www.letternoteplayer.com/unchained-melody---righteous-brothers--letternotes.php
    https://tomplay.com/singer-sheet-music/the-righteous-brothers/unchained-melody-singer-score

    As kid played trumpet and a little guitar.

    There is a lot more to it, but then ....

    Back to 'old' 'tronics:
    https://panteltje.nl/panteltje/amplifier/index.html
    that amp still runs 24/7, etched peeseebee
    Chip still available? Dunno.

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Liz Tuddenham@3:633/10 to All on Friday, June 05, 2026 09:58:03
    Jan Panteltje <alien@comet.invalid> wrote:

    liz@poppyrecords.invalid.invalid (Liz Tuddenham)wrote:
    Jan Panteltje <alien@comet.invalid> wrote:

    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net>wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info
    on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick
    this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI
    never showed up, in the first place.

    RL


    If I hadn?t stopped talking audio design seriously in about 1980, I
    certainly would have when crappy compressed MP3s took over the world.

    I was very impressed with mp3 compression first time I heard it

    ...but it doesn't sound so good by the second or third generation.

    The difference between the original AIFF file and a first generation mp3
    at a moderate compression rate is audible when both are electrically >recorded to a wax cylinder. Sometimes, when a 78 is transferred to mp3, >the results can be excruciating because the algorithm favours the
    scratch over the music.

    Sure, but I do not use wax cylinders, have never used those ..
    You can hear differences between a wav file and mp3 file made from it.

    My point, which I didn't make very clearly, is that even on 140-year-old recording technology it is possible to hear the degradation caused by
    the mp3 format.


    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From legg@3:633/10 to All on Friday, June 05, 2026 08:57:01
    On Thu, 4 Jun 2026 18:57:39 -0000 (UTC), Niocl?s P?l Caile?n de
    Ghloucester <thanks-to@Taf.com> wrote:

    Legg <legg@nospam.Magma.Ca> wrote: >|-----------------------------------------------|
    |"Audio mfrs are pretty paranoid about sources."| >|-----------------------------------------------|

    Dear RL,

    Why?

    With kind regards.
    (S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)

    The paranoia is created by the irrational market/clients.

    RL

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From legg@3:633/10 to All on Friday, June 05, 2026 09:10:08
    On Thu, 4 Jun 2026 15:22:02 -0000 (UTC), Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:

    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info
    on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick
    this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI
    never showed up, in the first place.

    RL


    If I hadn?t stopped talking audio design seriously in about 1980, I
    certainly would have when crappy compressed MP3s took over the world.

    Golden ears, my left buttock.

    Cheers

    Phil Hobbs

    It's the program material that matters and, often, the context or
    venue; not the hardware.

    Most distortion still from mikes, loudspeakers and other
    electromechanical transducers. The rest is probably in 'your' head.

    RL


    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Jan Panteltje@3:633/10 to All on Friday, June 05, 2026 13:31:26
    liz@poppyrecords.invalid.invalid (Liz Tuddenham)wrote:
    Jan Panteltje <alien@comet.invalid> wrote:

    liz@poppyrecords.invalid.invalid (Liz Tuddenham)wrote:
    Jan Panteltje <alien@comet.invalid> wrote:

    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net>wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info
    on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick
    this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI
    never showed up, in the first place.

    RL


    If I hadn?t stopped talking audio design seriously in about 1980, I
    certainly would have when crappy compressed MP3s took over the world.

    I was very impressed with mp3 compression first time I heard it

    ...but it doesn't sound so good by the second or third generation.

    The difference between the original AIFF file and a first generation mp3
    at a moderate compression rate is audible when both are electrically
    recorded to a wax cylinder. Sometimes, when a 78 is transferred to mp3,
    the results can be excruciating because the algorithm favours the
    scratch over the music.

    Sure, but I do not use wax cylinders, have never used those ..
    You can hear differences between a wav file and mp3 file made from it.

    My point, which I didn't make very clearly, is that even on 140-year-old >recording technology it is possible to hear the degradation caused by
    the mp3 format.

    Clear enough to me.
    But that is not a 'normal' situation
    Long ago when Sony came out with the Umatic video recorders
    those had a design problem, the FM frequency discriminator for the video (luminance not audio)
    would in case of a tape dropout not keep the last level but treat it as a 'low frequency'
    causing a huge spike in the images at that point that did overdrive the electronics
    As time passed by with many playbacks, dropouts increased, making the tapes unwatchable.
    So to fix the tapes I usd an old tricK, replace the spike (easy to detect) with the video from the previous picture line
    64 us delay line, or in software processing the recorded video was even simpler Somebody was very happy with that
    Later I fixed some more recorded stuff that way.
    Philips, in the LDL1000 video recorder I had, used the right FM discriminator and did not have that problem
    VHS was OK too.
    Same sort of work you are doing fixing old audio stuff.


    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Liz Tuddenham@3:633/10 to All on Friday, June 05, 2026 15:45:38
    Jan Panteltje <alien@comet.invalid> wrote:

    liz@poppyrecords.invalid.invalid (Liz Tuddenham)wrote:
    Jan Panteltje <alien@comet.invalid> wrote:

    liz@poppyrecords.invalid.invalid (Liz Tuddenham)wrote:
    Jan Panteltje <alien@comet.invalid> wrote:

    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net>wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info
    on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick
    this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI
    never showed up, in the first place.

    RL


    If I hadn?t stopped talking audio design seriously in about 1980, I
    certainly would have when crappy compressed MP3s took over the world. >> >>
    I was very impressed with mp3 compression first time I heard it

    ...but it doesn't sound so good by the second or third generation.

    The difference between the original AIFF file and a first generation mp3 >> >at a moderate compression rate is audible when both are electrically
    recorded to a wax cylinder. Sometimes, when a 78 is transferred to mp3, >> >the results can be excruciating because the algorithm favours the
    scratch over the music.

    Sure, but I do not use wax cylinders, have never used those ..
    You can hear differences between a wav file and mp3 file made from it.

    My point, which I didn't make very clearly, is that even on 140-year-old >recording technology it is possible to hear the degradation caused by
    the mp3 format.

    Clear enough to me.
    But that is not a 'normal' situation

    No - but it emphasises just how obvious the defects of mp3 can be.

    Long ago when Sony came out with the Umatic video recorders those had a design problem, the FM frequency discriminator for the video (luminance
    not audio) would in case of a tape dropout not keep the last level but
    treat it as a 'low frequency' causing a huge spike in the images at that point that did overdrive the electronics

    [...]
    Same sort of work you are doing fixing old audio stuff.

    Same problem: what to put in place of the waveform if corruption is
    detected. Return-to-zero works best at the higher audio frequencies but sample-and-hold works better at lower frequencies.

    I solved the problem by dividing the audio spectrum into 10 bands of an
    octave each, then following the blanking switch with a filter tuned to
    the centre of that octave. The missing waveform was replaced with an approximation which was already synchronised with the waveform and at
    about the right frequency. The substitution is almost inaudible unless
    the damge is a substantial proportion of the waveform.


    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Phil Hobbs@3:633/10 to All on Friday, June 05, 2026 13:44:12
    On 2026-06-05 09:10, legg wrote:
    On Thu, 4 Jun 2026 15:22:02 -0000 (UTC), Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:

    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info
    on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick
    this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI
    never showed up, in the first place.

    RL


    If I hadn?t stopped talking audio design seriously in about 1980, I
    certainly would have when crappy compressed MP3s took over the world.

    Golden ears, my left buttock.

    Cheers

    Phil Hobbs

    It's the program material that matters and, often, the context or
    venue; not the hardware.

    Most distortion still from mikes, loudspeakers and other
    electromechanical transducers. The rest is probably in 'your' head.

    RL


    Exactly. The idea of an "Audio Op Amp", as though the actual
    requirements were special, is pretty silly.

    (The idea that an 18-nV TL074 is a "low noise" amplifier is even
    sillier--it's a good 20 dB off the pace.)

    Cheers

    Phil Hobbs

    --
    Dr Philip C D Hobbs
    Principal Consultant
    ElectroOptical Innovations LLC / Hobbs ElectroOptics
    Optics, Electro-optics, Photonics, Analog Electronics
    Briarcliff Manor NY 10510

    http://electrooptical.net
    http://hobbs-eo.com


    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Friday, June 05, 2026 12:38:02
    On Fri, 5 Jun 2026 13:44:12 -0400, Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:

    On 2026-06-05 09:10, legg wrote:
    On Thu, 4 Jun 2026 15:22:02 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info
    on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick
    this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI
    never showed up, in the first place.

    RL


    If I hadn?t stopped talking audio design seriously in about 1980, I
    certainly would have when crappy compressed MP3s took over the world.

    Golden ears, my left buttock.

    Cheers

    Phil Hobbs

    It's the program material that matters and, often, the context or
    venue; not the hardware.

    Most distortion still from mikes, loudspeakers and other
    electromechanical transducers. The rest is probably in 'your' head.

    RL


    Exactly. The idea of an "Audio Op Amp", as though the actual
    requirements were special, is pretty silly.

    (The idea that an 18-nV TL074 is a "low noise" amplifier is even >sillier--it's a good 20 dB off the pace.)

    Cheers

    Phil Hobbs

    There should be a legally binding definition of "high speed" too.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Phil Hobbs@3:633/10 to All on Friday, June 05, 2026 21:49:12
    john larkin <jl@glen--canyon.com> wrote:
    On Fri, 5 Jun 2026 13:44:12 -0400, Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:

    On 2026-06-05 09:10, legg wrote:
    On Thu, 4 Jun 2026 15:22:02 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info
    on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick
    this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI
    never showed up, in the first place.

    RL


    If I hadn?t stopped talking audio design seriously in about 1980, I
    certainly would have when crappy compressed MP3s took over the world.

    Golden ears, my left buttock.

    Cheers

    Phil Hobbs

    It's the program material that matters and, often, the context or
    venue; not the hardware.

    Most distortion still from mikes, loudspeakers and other
    electromechanical transducers. The rest is probably in 'your' head.

    RL


    Exactly. The idea of an "Audio Op Amp", as though the actual
    requirements were special, is pretty silly.

    (The idea that an 18-nV TL074 is a "low noise" amplifier is even
    sillier--it's a good 20 dB off the pace.)

    Cheers

    Phil Hobbs

    There should be a legally binding definition of "high speed" too.

    To their dying day, National maintained that 1 mV was ?low offset? and 400
    ns was ?fast settling.?

    Cheers

    Phil Hobbs

    --
    Dr Philip C D Hobbs Principal Consultant ElectroOptical Innovations LLC / Hobbs ElectroOptics Optics, Electro-optics, Photonics, Analog Electronics

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Friday, June 05, 2026 15:00:27
    On Fri, 5 Jun 2026 19:42:43 -0000 (UTC), Niocl?s P?l Caile?n de
    Ghloucester <thanks-to@Taf.com> wrote:

    John Larkin <jl@Glen--Canyon.com> wrote: >|-------------------------------------------------------------------|
    |"There should be a legally binding definition of "high speed" too."| >|-------------------------------------------------------------------|

    The fastest integrated circuits are by no hardware description
    language, whereas VHDL stands for Very-High-Speed-Integrated-Circuit >Description Language.

    Does that mean you talk fast?


    (S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)

    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Joerg@3:633/10 to All on Friday, June 05, 2026 17:57:17
    On 6/3/26 8:37 AM, john larkin wrote:
    On Wed, 3 Jun 2026 16:12:27 +0100, John R Walliker
    <jrwalliker@gmail.com> wrote:

    On 03/06/2026 15:39, john larkin wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    They changed the process on a part that's 47 years old.

    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    When you significantly degrade a couple of parameters
    that are important for many users of that part and
    don't provide a means of knowing whether you have
    the original part or the degraded imitation, then
    yes, it is scandalous. ...


    Absolutamente. It falls under the category "Don't do this!".


    ... Especially when the ECN
    tells buyers that the changes will have no impact.
    John

    It is impressive that TI keeps parts in production for decades, almost
    5 in this case.


    Quite normal for market-successful components.


    This part belongs in the 555 timer and uA741 and 2N3055 generation,
    getting creaky before most of my enginers were born. Or before their
    parents were born.


    My longest-running design is from 1994 and still in production with all
    the same semiconductors. It might still be in production when I head
    home to Jesus.

    A former co-worker had a Chevy truck from the mid 50's. One day around
    the year 2000 it suffered minor indigestion, starter was bad. He asked
    me if I could give him a lift to an auto parts store. "Did you call them
    to see if they have a starter for such an old truck?" ... "Nah, don't
    need to, those are still made and they've always got them". Sure enough
    they did and he swapped it out during lunch break. Still had enough time
    for lunch.

    --
    Regards, Joerg

    http://www.analogconsultants.com/

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Joerg@3:633/10 to All on Friday, June 05, 2026 18:05:56
    On 6/3/26 6:10 AM, Chris Jones wrote:
    https://www.youtube.com/watch?v=22ZmmZ67SMY


    The worst I ever saw: A MOSFET that was used in a mixed supply
    situation. It switched a 3.3V rail but the gate control came from
    12V-driven logic. One day the manufacturer decided in their infinite
    wisdom to "improve" it. They added integrated gate protection zeners and
    from then on the abs max gate-source voltage became +/-8V instead of the
    prior +/-20V. The part number remained the same!

    *PHUT* ... *BANG* ... *POOF* ... the company lost hundreds of expensive
    boards and since this caused serious overvoltage on the 3.3V supply rail
    that fed processors and stuff the boards were not salvageable.

    --
    Regards, Joerg

    http://www.analogconsultants.com/

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Friday, June 05, 2026 20:10:10
    On Fri, 5 Jun 2026 18:05:56 -0700, Joerg <news@analogconsultants.com>
    wrote:

    On 6/3/26 6:10 AM, Chris Jones wrote:
    https://www.youtube.com/watch?v=22ZmmZ67SMY


    The worst I ever saw: A MOSFET that was used in a mixed supply
    situation. It switched a 3.3V rail but the gate control came from
    12V-driven logic. One day the manufacturer decided in their infinite
    wisdom to "improve" it. They added integrated gate protection zeners and >from then on the abs max gate-source voltage became +/-8V instead of the >prior +/-20V. The part number remained the same!

    *PHUT* ... *BANG* ... *POOF* ... the company lost hundreds of expensive >boards and since this caused serious overvoltage on the 3.3V supply rail >that fed processors and stuff the boards were not salvageable.

    Yikes. Protected gates usually zener at 20 volts or so.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Jan Panteltje@3:633/10 to All on Saturday, June 06, 2026 06:43:04
    =?UTF-8?Q?Niocl=C3=A1s_P=C3=B3l_Caile=C3=A1n?= de Ghloucester <thanks-to@Taf.com>wrote:
    Jan Panteltje <alien@comet.invalid> schreef: >|--------------------------------------------------------------------------------------------|
    |"mediainfo (1) - command line utility to display information about audio/video files"|
    |--------------------------------------------------------------------------------------------|

    So, Insomnia 24/7 installed mediainfo for me which is an interesting >alternative to ffprobe but the manpage for mediainfo does not explain
    a subset of its outputs which it showed me, so maybe I shall need to
    download its source instead of only using a packaged binary.

    I ran mediainfo and ffprobe on different types of MPEG-4 files in >HTTP://Gloucester.Insomnia247.NL/gardai/Where_are_you_from/

    mediainfo so far works great for me.
    I stick with mp3 or raw wavefiles for now.
    I have a lot of .ts files (satellite transponder streams) that hold sometimes many languages at once.
    On my security system I mave made .ts the default for video that has audio. Using mplayer to play those.
    For example mplayer -aid 1234 selects audio stream (language) 1234
    The .ts format can have several video streams too, subtitles, etc etc.

    raspberrypi: ~ # mplayer -h
    Usage: mplayer [options] [url|path/]filename

    Basic options: (complete list in the man page)
    -vo <drv> select video output driver ('-vo help' for a list)
    -ao <drv> select audio output driver ('-ao help' for a list)
    vcd://<trackno> play (S)VCD (Super Video CD) track (raw device, no mount)
    dvd://<titleno> play DVD title from device instead of plain file
    -alang/-slang select DVD audio/subtitle language (by 2-char country code)
    -ss <position> seek to given (seconds or hh:mm:ss) position
    -nosound do not play sound
    -fs fullscreen playback (or -vm, -zoom, details in the man page)
    -x <x> -y <y> set display resolution (for use with -vm or -zoom)
    -sub <file> specify subtitle file to use (also see -subfps, -subdelay)
    -playlist <file> specify playlist file
    -vid x -aid y select video (x) and audio (y) stream to play
    -fps x -srate y change video (x fps) and audio (y Hz) rate
    -pp <quality> enable postprocessing filter (details in the man page)
    -framedrop enable frame dropping (for slow machines)

    Basic keys: (complete list in the man page, also check input.conf)
    <- or -> seek backward/forward 10 seconds
    down or up seek backward/forward 1 minute
    pgdown or pgup seek backward/forward 10 minutes
    < or > step backward/forward in playlist
    p or SPACE pause movie (press any key to continue)
    q or ESC stop playing and quit program
    + or - adjust audio delay by +/- 0.1 second
    o cycle OSD mode: none / seekbar / seekbar + timer
    * or / increase or decrease PCM volume
    x or z adjust subtitle delay by +/- 0.1 second
    r or t adjust subtitle position up/down, also see -vf expand

    * * * SEE THE MAN PAGE FOR DETAILS, FURTHER (ADVANCED) OPTIONS AND KEYS * * *

    MPlayer 1.4 (Debian), built with gcc-10 (C) 2000-2019 MPlayer Team


    'man mplayer' has a lot more info
    mplayer uses ffmpeg AFAIK

    I like the + and - key when playing to adjust the audio video delay.


    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From piglet@3:633/10 to All on Saturday, June 06, 2026 11:29:35
    john larkin <jl@glen--canyon.com> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    They changed the process on a part that's 47 years old.

    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    More than a process change, it is a whole different product. Old was NPN
    input stage, new is PNP inputs. Unforgivable to not amend the part number
    in any way.

    --
    piglet

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Saturday, June 06, 2026 05:53:42
    On Sat, 6 Jun 2026 11:29:35 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    They changed the process on a part that's 47 years old.

    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    More than a process change, it is a whole different product. Old was NPN >input stage, new is PNP inputs. Unforgivable to not amend the part number
    in any way.

    You'd better not buy TI parts any more.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From piglet@3:633/10 to All on Saturday, June 06, 2026 13:27:05
    john larkin <jl@glen--canyon.com> wrote:
    On Sat, 6 Jun 2026 11:29:35 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    They changed the process on a part that's 47 years old.

    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    More than a process change, it is a whole different product. Old was NPN
    input stage, new is PNP inputs. Unforgivable to not amend the part number
    in any way.

    You'd better not buy TI parts any more.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    Exactly!

    --
    piglet

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Sunday, June 07, 2026 01:10:57
    On 6/06/2026 10:53 pm, john larkin wrote:
    On Sat, 6 Jun 2026 11:29:35 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    They changed the process on a part that's 47 years old.

    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    More than a process change, it is a whole different product. Old was NPN
    input stage, new is PNP inputs. Unforgivable to not amend the part number
    in any way.

    You'd better not buy TI parts any more.

    They were rarely anybody's first choice. Even when they came up with
    something neat they'd leave out a vital detail in the data sheet.
    They introduced a really nice MOSFET input op-amp and failed to mention
    in the data sheet that it had about 10pF input capacitance. For once I'd almost got a printed circuit layout that worked first time, but I had to
    bodge in 2.2pF capacitor in parallel with the feedback resistor to kill
    the oscillation the 10pF produced.

    --
    Bill Sloman, Sydney


    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Saturday, June 06, 2026 08:57:42
    On Sun, 7 Jun 2026 01:10:57 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 6/06/2026 10:53 pm, john larkin wrote:
    On Sat, 6 Jun 2026 11:29:35 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    They changed the process on a part that's 47 years old.

    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    More than a process change, it is a whole different product. Old was NPN >>> input stage, new is PNP inputs. Unforgivable to not amend the part number >>> in any way.

    You'd better not buy TI parts any more.

    They were rarely anybody's first choice. Even when they came up with >something neat they'd leave out a vital detail in the data sheet.
    They introduced a really nice MOSFET input op-amp and failed to mention
    in the data sheet that it had about 10pF input capacitance. For once I'd >almost got a printed circuit layout that worked first time, but I had to >bodge in 2.2pF capacitor in parallel with the feedback resistor to kill
    the oscillation the 10pF produced.

    Yeah, sometimes electronics gets complicated.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Sunday, June 07, 2026 02:19:03
    On 7/06/2026 1:57 am, john larkin wrote:
    On Sun, 7 Jun 2026 01:10:57 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 6/06/2026 10:53 pm, john larkin wrote:
    On Sat, 6 Jun 2026 11:29:35 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    They changed the process on a part that's 47 years old.

    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    More than a process change, it is a whole different product. Old was NPN >>>> input stage, new is PNP inputs. Unforgivable to not amend the part number >>>> in any way.

    You'd better not buy TI parts any more.

    They were rarely anybody's first choice. Even when they came up with
    something neat they'd leave out a vital detail in the data sheet.
    They introduced a really nice MOSFET input op-amp and failed to mention
    in the data sheet that it had about 10pF input capacitance. For once I'd
    almost got a printed circuit layout that worked first time, but I had to
    bodge in 2.2pF capacitor in parallel with the feedback resistor to kill
    the oscillation the 10pF produced.

    Yeah, sometimes electronics gets complicated.

    Regular opamps have about 1pF of input capacitance to ground. Dealing
    with that isn't complicated. Dealing with the 10pF when it messed me
    about wasn't complicated either.

    Having to do it after I'd laid out the board, and got it made and
    loaded, wasn't complicated either, but it was definitely irritating.

    --
    Bill Sloman, Sydney


    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Saturday, June 06, 2026 09:33:22
    On Sun, 7 Jun 2026 02:19:03 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 1:57 am, john larkin wrote:
    On Sun, 7 Jun 2026 01:10:57 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 6/06/2026 10:53 pm, john larkin wrote:
    On Sat, 6 Jun 2026 11:29:35 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    They changed the process on a part that's 47 years old.

    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    More than a process change, it is a whole different product. Old was NPN >>>>> input stage, new is PNP inputs. Unforgivable to not amend the part number >>>>> in any way.

    You'd better not buy TI parts any more.

    They were rarely anybody's first choice. Even when they came up with
    something neat they'd leave out a vital detail in the data sheet.
    They introduced a really nice MOSFET input op-amp and failed to mention
    in the data sheet that it had about 10pF input capacitance. For once I'd >>> almost got a printed circuit layout that worked first time, but I had to >>> bodge in 2.2pF capacitor in parallel with the feedback resistor to kill
    the oscillation the 10pF produced.

    Yeah, sometimes electronics gets complicated.

    Regular opamps have about 1pF of input capacitance to ground.

    Do you use opamps with a ground pin?

    My favorite gumdrop opamp, OPA197, has a typ "common mode" capacitance
    of 6.4 pF, whatever that means.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Sunday, June 07, 2026 03:06:10
    On 7/06/2026 2:33 am, john larkin wrote:
    On Sun, 7 Jun 2026 02:19:03 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 1:57 am, john larkin wrote:
    On Sun, 7 Jun 2026 01:10:57 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 6/06/2026 10:53 pm, john larkin wrote:
    On Sat, 6 Jun 2026 11:29:35 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    They changed the process on a part that's 47 years old.

    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    More than a process change, it is a whole different product. Old was NPN >>>>>> input stage, new is PNP inputs. Unforgivable to not amend the part number
    in any way.

    You'd better not buy TI parts any more.

    They were rarely anybody's first choice. Even when they came up with
    something neat they'd leave out a vital detail in the data sheet.
    They introduced a really nice MOSFET input op-amp and failed to mention >>>> in the data sheet that it had about 10pF input capacitance. For once I'd >>>> almost got a printed circuit layout that worked first time, but I had to >>>> bodge in 2.2pF capacitor in parallel with the feedback resistor to kill >>>> the oscillation the 10pF produced.

    Yeah, sometimes electronics gets complicated.

    Regular opamps have about 1pF of input capacitance to ground.

    Do you use opamps with a ground pin?

    Don't be silly. The ground reference is through the negative rail

    My favorite gumdrop opamp, OPA197, has a typ "common mode" capacitance
    of 6.4 pF, whatever that means.

    https://www.ti.com/lit/ds/symlink/opa197.pdf?ts=1780716494386

    It's on page 7 of the data sheet. I was more worried about the
    differential capacitance, which is 1.6pF for that part (and pretty
    typical). I could try to explain the difference between "differential"
    and "common mode" but if you haven't found out about that by now, you
    clearly aren't interested in finding out.

    --
    Bill Sloman, Sydney


    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Saturday, June 06, 2026 11:43:04
    On Sun, 7 Jun 2026 03:06:10 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 2:33 am, john larkin wrote:
    On Sun, 7 Jun 2026 02:19:03 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 1:57 am, john larkin wrote:
    On Sun, 7 Jun 2026 01:10:57 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 6/06/2026 10:53 pm, john larkin wrote:
    On Sat, 6 Jun 2026 11:29:35 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    They changed the process on a part that's 47 years old.

    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    More than a process change, it is a whole different product. Old was NPN
    input stage, new is PNP inputs. Unforgivable to not amend the part number
    in any way.

    You'd better not buy TI parts any more.

    They were rarely anybody's first choice. Even when they came up with >>>>> something neat they'd leave out a vital detail in the data sheet.
    They introduced a really nice MOSFET input op-amp and failed to mention >>>>> in the data sheet that it had about 10pF input capacitance. For once I'd >>>>> almost got a printed circuit layout that worked first time, but I had to >>>>> bodge in 2.2pF capacitor in parallel with the feedback resistor to kill >>>>> the oscillation the 10pF produced.

    Yeah, sometimes electronics gets complicated.

    Regular opamps have about 1pF of input capacitance to ground.

    Do you use opamps with a ground pin?

    Don't be silly. The ground reference is through the negative rail

    My favorite gumdrop opamp, OPA197, has a typ "common mode" capacitance
    of 6.4 pF, whatever that means.

    https://www.ti.com/lit/ds/symlink/opa197.pdf?ts=1780716494386

    It's on page 7 of the data sheet. I was more worried about the
    differential capacitance, which is 1.6pF for that part (and pretty
    typical). I could try to explain the difference between "differential"
    and "common mode" but if you haven't found out about that by now, you >clearly aren't interested in finding out.

    Explain it to me. I'm not sure what the commmon-mode capacitance of an
    opamp is.

    Any explaination why the peaking in your circuit could be blamed on differential capacitance and not care about common-mode capacitance?


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Phil Hobbs@3:633/10 to All on Saturday, June 06, 2026 20:41:07
    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 03:06:10 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 2:33 am, john larkin wrote:
    On Sun, 7 Jun 2026 02:19:03 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 1:57 am, john larkin wrote:
    On Sun, 7 Jun 2026 01:10:57 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>> wrote:

    On 6/06/2026 10:53 pm, john larkin wrote:
    On Sat, 6 Jun 2026 11:29:35 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    They changed the process on a part that's 47 years old.

    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    More than a process change, it is a whole different product. Old was NPN
    input stage, new is PNP inputs. Unforgivable to not amend the part number
    in any way.

    You'd better not buy TI parts any more.

    They were rarely anybody's first choice. Even when they came up with >>>>>> something neat they'd leave out a vital detail in the data sheet.
    They introduced a really nice MOSFET input op-amp and failed to mention >>>>>> in the data sheet that it had about 10pF input capacitance. For once I'd >>>>>> almost got a printed circuit layout that worked first time, but I had to >>>>>> bodge in 2.2pF capacitor in parallel with the feedback resistor to kill >>>>>> the oscillation the 10pF produced.

    Yeah, sometimes electronics gets complicated.

    Regular opamps have about 1pF of input capacitance to ground.

    Do you use opamps with a ground pin?

    Don't be silly. The ground reference is through the negative rail

    My favorite gumdrop opamp, OPA197, has a typ "common mode" capacitance
    of 6.4 pF, whatever that means.

    https://www.ti.com/lit/ds/symlink/opa197.pdf?ts=1780716494386

    It's on page 7 of the data sheet. I was more worried about the
    differential capacitance, which is 1.6pF for that part (and pretty
    typical). I could try to explain the difference between "differential"
    and "common mode" but if you haven't found out about that by now, you
    clearly aren't interested in finding out.

    Explain it to me. I'm not sure what the commmon-mode capacitance of an
    opamp is.

    Any explaination why the peaking in your circuit could be blamed on differential capacitance and not care about common-mode capacitance?


    As we?ve discussed before, the differential input capacitance of an op amp under bias is hard to measure, and the data sheet values are unreliable.

    The best way I know of is to put a very small pot directly in series with
    the inverting input and look at what happens to the phase margin.

    The CM capacitance you can get by doing the same on the noninverting input
    and looking at the bandwidth. Feedback bootstraps out the differential capacitance at low frequency.

    Cheers

    Phil Hobbs


    --
    Dr Philip C D Hobbs Principal Consultant ElectroOptical Innovations LLC / Hobbs ElectroOptics Optics, Electro-optics, Photonics, Analog Electronics

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Saturday, June 06, 2026 14:34:16
    On Sat, 6 Jun 2026 20:41:07 -0000 (UTC), Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 03:06:10 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 2:33 am, john larkin wrote:
    On Sun, 7 Jun 2026 02:19:03 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 1:57 am, john larkin wrote:
    On Sun, 7 Jun 2026 01:10:57 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>> wrote:

    On 6/06/2026 10:53 pm, john larkin wrote:
    On Sat, 6 Jun 2026 11:29:35 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    They changed the process on a part that's 47 years old.

    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    More than a process change, it is a whole different product. Old was NPN
    input stage, new is PNP inputs. Unforgivable to not amend the part number
    in any way.

    You'd better not buy TI parts any more.

    They were rarely anybody's first choice. Even when they came up with >>>>>>> something neat they'd leave out a vital detail in the data sheet. >>>>>>> They introduced a really nice MOSFET input op-amp and failed to mention >>>>>>> in the data sheet that it had about 10pF input capacitance. For once I'd
    almost got a printed circuit layout that worked first time, but I had to
    bodge in 2.2pF capacitor in parallel with the feedback resistor to kill >>>>>>> the oscillation the 10pF produced.

    Yeah, sometimes electronics gets complicated.

    Regular opamps have about 1pF of input capacitance to ground.

    Do you use opamps with a ground pin?

    Don't be silly. The ground reference is through the negative rail

    My favorite gumdrop opamp, OPA197, has a typ "common mode" capacitance >>>> of 6.4 pF, whatever that means.

    https://www.ti.com/lit/ds/symlink/opa197.pdf?ts=1780716494386

    It's on page 7 of the data sheet. I was more worried about the
    differential capacitance, which is 1.6pF for that part (and pretty
    typical). I could try to explain the difference between "differential"
    and "common mode" but if you haven't found out about that by now, you
    clearly aren't interested in finding out.

    Explain it to me. I'm not sure what the commmon-mode capacitance of an
    opamp is.

    Any explaination why the peaking in your circuit could be blamed on
    differential capacitance and not care about common-mode capacitance?


    As we?ve discussed before, the differential input capacitance of an op amp >under bias is hard to measure, and the data sheet values are unreliable.

    The best way I know of is to put a very small pot directly in series with
    the inverting input and look at what happens to the phase margin.

    The CM capacitance you can get by doing the same on the noninverting input >and looking at the bandwidth. Feedback bootstraps out the differential >capacitance at low frequency.

    Cheers

    Phil Hobbs

    I've seen the "common mode" capacitance defined as the C between one
    pin and the rails, and sometimes as the c of both pins in parellel to
    the world.

    A diagram of the several caps, with values, would help.

    One can Spice a standard inverting amp and see what it does, assumuing
    the Spice model is accurate.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Phil Hobbs@3:633/10 to All on Sunday, June 07, 2026 00:31:01
    john larkin <jl@glen--canyon.com> wrote:
    On Sat, 6 Jun 2026 20:41:07 -0000 (UTC), Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 03:06:10 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 2:33 am, john larkin wrote:
    On Sun, 7 Jun 2026 02:19:03 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>> wrote:

    On 7/06/2026 1:57 am, john larkin wrote:
    On Sun, 7 Jun 2026 01:10:57 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>> wrote:

    On 6/06/2026 10:53 pm, john larkin wrote:
    On Sat, 6 Jun 2026 11:29:35 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    They changed the process on a part that's 47 years old.

    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    More than a process change, it is a whole different product. Old was NPN
    input stage, new is PNP inputs. Unforgivable to not amend the part number
    in any way.

    You'd better not buy TI parts any more.

    They were rarely anybody's first choice. Even when they came up with >>>>>>>> something neat they'd leave out a vital detail in the data sheet. >>>>>>>> They introduced a really nice MOSFET input op-amp and failed to mention
    in the data sheet that it had about 10pF input capacitance. For once I'd
    almost got a printed circuit layout that worked first time, but I had to
    bodge in 2.2pF capacitor in parallel with the feedback resistor to kill
    the oscillation the 10pF produced.

    Yeah, sometimes electronics gets complicated.

    Regular opamps have about 1pF of input capacitance to ground.

    Do you use opamps with a ground pin?

    Don't be silly. The ground reference is through the negative rail

    My favorite gumdrop opamp, OPA197, has a typ "common mode" capacitance >>>>> of 6.4 pF, whatever that means.

    https://www.ti.com/lit/ds/symlink/opa197.pdf?ts=1780716494386

    It's on page 7 of the data sheet. I was more worried about the
    differential capacitance, which is 1.6pF for that part (and pretty
    typical). I could try to explain the difference between "differential" >>>> and "common mode" but if you haven't found out about that by now, you >>>> clearly aren't interested in finding out.

    Explain it to me. I'm not sure what the commmon-mode capacitance of an
    opamp is.

    Any explaination why the peaking in your circuit could be blamed on
    differential capacitance and not care about common-mode capacitance?


    As we?ve discussed before, the differential input capacitance of an op amp >> under bias is hard to measure, and the data sheet values are unreliable.

    The best way I know of is to put a very small pot directly in series with
    the inverting input and look at what happens to the phase margin.

    The CM capacitance you can get by doing the same on the noninverting input >> and looking at the bandwidth. Feedback bootstraps out the differential
    capacitance at low frequency.

    Cheers

    Phil Hobbs

    I've seen the "common mode" capacitance defined as the C between one
    pin and the rails, and sometimes as the c of both pins in parellel to
    the world.

    A diagram of the several caps, with values, would help.

    One can Spice a standard inverting amp and see what it does, assumuing
    the Spice model is accurate.

    It?s the measurement that?s difficult?if the amp is powered off, none of
    the junction capacitances will be right.

    Cheers

    Phil Hobbs

    --
    Dr Philip C D Hobbs Principal Consultant ElectroOptical Innovations LLC / Hobbs ElectroOptics Optics, Electro-optics, Photonics, Analog Electronics

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Saturday, June 06, 2026 18:44:28
    On Sun, 7 Jun 2026 00:31:01 -0000 (UTC), Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sat, 6 Jun 2026 20:41:07 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 03:06:10 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 2:33 am, john larkin wrote:
    On Sun, 7 Jun 2026 02:19:03 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>> wrote:

    On 7/06/2026 1:57 am, john larkin wrote:
    On Sun, 7 Jun 2026 01:10:57 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>>> wrote:

    On 6/06/2026 10:53 pm, john larkin wrote:
    On Sat, 6 Jun 2026 11:29:35 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    They changed the process on a part that's 47 years old. >>>>>>>>>>>>
    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    More than a process change, it is a whole different product. Old was NPN
    input stage, new is PNP inputs. Unforgivable to not amend the part number
    in any way.

    You'd better not buy TI parts any more.

    They were rarely anybody's first choice. Even when they came up with >>>>>>>>> something neat they'd leave out a vital detail in the data sheet. >>>>>>>>> They introduced a really nice MOSFET input op-amp and failed to mention
    in the data sheet that it had about 10pF input capacitance. For once I'd
    almost got a printed circuit layout that worked first time, but I had to
    bodge in 2.2pF capacitor in parallel with the feedback resistor to kill
    the oscillation the 10pF produced.

    Yeah, sometimes electronics gets complicated.

    Regular opamps have about 1pF of input capacitance to ground.

    Do you use opamps with a ground pin?

    Don't be silly. The ground reference is through the negative rail

    My favorite gumdrop opamp, OPA197, has a typ "common mode" capacitance >>>>>> of 6.4 pF, whatever that means.

    https://www.ti.com/lit/ds/symlink/opa197.pdf?ts=1780716494386

    It's on page 7 of the data sheet. I was more worried about the
    differential capacitance, which is 1.6pF for that part (and pretty
    typical). I could try to explain the difference between "differential" >>>>> and "common mode" but if you haven't found out about that by now, you >>>>> clearly aren't interested in finding out.

    Explain it to me. I'm not sure what the commmon-mode capacitance of an >>>> opamp is.

    Any explaination why the peaking in your circuit could be blamed on
    differential capacitance and not care about common-mode capacitance?


    As we?ve discussed before, the differential input capacitance of an op amp >>> under bias is hard to measure, and the data sheet values are unreliable. >>>
    The best way I know of is to put a very small pot directly in series with >>> the inverting input and look at what happens to the phase margin.

    The CM capacitance you can get by doing the same on the noninverting input >>> and looking at the bandwidth. Feedback bootstraps out the differential
    capacitance at low frequency.

    Cheers

    Phil Hobbs

    I've seen the "common mode" capacitance defined as the C between one
    pin and the rails, and sometimes as the c of both pins in parellel to
    the world.

    A diagram of the several caps, with values, would help.

    One can Spice a standard inverting amp and see what it does, assumuing
    the Spice model is accurate.

    It?s the measurement that?s difficult?if the amp is powered off, none of
    the junction capacitances will be right.

    Cheers

    Phil Hobbs

    I have a Spice model of the OPA197, basically TI's Pspice model
    converted for LT Spice.

    I made a unity-gain follower sim and drove that with a 1 volt step,
    through a 1M resistor. The output is a nice exponential with tau =
    6.45 usec, which means the c to ground is 6.45 pF.

    The TI data sheet says that cm capacitance is 6.4!

    The differential input c disappeared because it's bootstrapped in a
    follower.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Sunday, June 07, 2026 14:45:40
    On 7/06/2026 11:44 am, john larkin wrote:
    On Sun, 7 Jun 2026 00:31:01 -0000 (UTC), Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sat, 6 Jun 2026 20:41:07 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 03:06:10 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>> wrote:

    On 7/06/2026 2:33 am, john larkin wrote:
    On Sun, 7 Jun 2026 02:19:03 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>> wrote:

    On 7/06/2026 1:57 am, john larkin wrote:
    On Sun, 7 Jun 2026 01:10:57 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>>>> wrote:

    On 6/06/2026 10:53 pm, john larkin wrote:
    On Sat, 6 Jun 2026 11:29:35 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    They changed the process on a part that's 47 years old. >>>>>>>>>>>>>
    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    More than a process change, it is a whole different product. Old was NPN
    input stage, new is PNP inputs. Unforgivable to not amend the part number
    in any way.

    You'd better not buy TI parts any more.

    They were rarely anybody's first choice. Even when they came up with >>>>>>>>>> something neat they'd leave out a vital detail in the data sheet. >>>>>>>>>> They introduced a really nice MOSFET input op-amp and failed to mention
    in the data sheet that it had about 10pF input capacitance. For once I'd
    almost got a printed circuit layout that worked first time, but I had to
    bodge in 2.2pF capacitor in parallel with the feedback resistor to kill
    the oscillation the 10pF produced.

    Yeah, sometimes electronics gets complicated.

    Regular opamps have about 1pF of input capacitance to ground.

    Do you use opamps with a ground pin?

    Don't be silly. The ground reference is through the negative rail

    My favorite gumdrop opamp, OPA197, has a typ "common mode" capacitance >>>>>>> of 6.4 pF, whatever that means.

    https://www.ti.com/lit/ds/symlink/opa197.pdf?ts=1780716494386

    It's on page 7 of the data sheet. I was more worried about the
    differential capacitance, which is 1.6pF for that part (and pretty >>>>>> typical). I could try to explain the difference between "differential" >>>>>> and "common mode" but if you haven't found out about that by now, you >>>>>> clearly aren't interested in finding out.

    Explain it to me. I'm not sure what the commmon-mode capacitance of an >>>>> opamp is.

    Any explaination why the peaking in your circuit could be blamed on
    differential capacitance and not care about common-mode capacitance? >>>>>

    As we?ve discussed before, the differential input capacitance of an op amp >>>> under bias is hard to measure, and the data sheet values are unreliable. >>>>
    The best way I know of is to put a very small pot directly in series with >>>> the inverting input and look at what happens to the phase margin.

    The CM capacitance you can get by doing the same on the noninverting input >>>> and looking at the bandwidth. Feedback bootstraps out the differential >>>> capacitance at low frequency.

    Cheers

    Phil Hobbs

    I've seen the "common mode" capacitance defined as the C between one
    pin and the rails, and sometimes as the c of both pins in parellel to
    the world.

    A diagram of the several caps, with values, would help.

    One can Spice a standard inverting amp and see what it does, assumuing
    the Spice model is accurate.

    It?s the measurement that?s difficult?if the amp is powered off, none of
    the junction capacitances will be right.

    Cheers

    Phil Hobbs

    I have a Spice model of the OPA197, basically TI's Pspice model
    converted for LT Spice.

    I made a unity-gain follower sim and drove that with a 1 volt step,
    through a 1M resistor. The output is a nice exponential with tau =
    6.45 usec, which means the c to ground is 6.45 pF.

    The TI data sheet says that cm capacitance is 6.4!

    The differential input c disappeared because it's bootstrapped in a
    follower.

    It doesn't. There's a collector/base or gate/drain capacitance that has
    to be charged up if the input moves vis-a-vis local ground (in this case
    the local rail voltages inside the chip). There are heroic measures that
    can minimise this - essentially floating the power rails though they
    move too slowly to be of all that much help - but regular followers
    don't use them.

    --
    Bill Sloman, Sydney

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Sunday, June 07, 2026 06:19:34
    On Sun, 7 Jun 2026 14:45:40 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 11:44 am, john larkin wrote:
    On Sun, 7 Jun 2026 00:31:01 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sat, 6 Jun 2026 20:41:07 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 03:06:10 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>> wrote:

    On 7/06/2026 2:33 am, john larkin wrote:
    On Sun, 7 Jun 2026 02:19:03 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>>> wrote:

    On 7/06/2026 1:57 am, john larkin wrote:
    On Sun, 7 Jun 2026 01:10:57 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 6/06/2026 10:53 pm, john larkin wrote:
    On Sat, 6 Jun 2026 11:29:35 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    They changed the process on a part that's 47 years old. >>>>>>>>>>>>>>
    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    More than a process change, it is a whole different product. Old was NPN
    input stage, new is PNP inputs. Unforgivable to not amend the part number
    in any way.

    You'd better not buy TI parts any more.

    They were rarely anybody's first choice. Even when they came up with
    something neat they'd leave out a vital detail in the data sheet. >>>>>>>>>>> They introduced a really nice MOSFET input op-amp and failed to mention
    in the data sheet that it had about 10pF input capacitance. For once I'd
    almost got a printed circuit layout that worked first time, but I had to
    bodge in 2.2pF capacitor in parallel with the feedback resistor to kill
    the oscillation the 10pF produced.

    Yeah, sometimes electronics gets complicated.

    Regular opamps have about 1pF of input capacitance to ground. >>>>>>>>
    Do you use opamps with a ground pin?

    Don't be silly. The ground reference is through the negative rail >>>>>>>
    My favorite gumdrop opamp, OPA197, has a typ "common mode" capacitance >>>>>>>> of 6.4 pF, whatever that means.

    https://www.ti.com/lit/ds/symlink/opa197.pdf?ts=1780716494386

    It's on page 7 of the data sheet. I was more worried about the
    differential capacitance, which is 1.6pF for that part (and pretty >>>>>>> typical). I could try to explain the difference between "differential" >>>>>>> and "common mode" but if you haven't found out about that by now, you >>>>>>> clearly aren't interested in finding out.

    Explain it to me. I'm not sure what the commmon-mode capacitance of an >>>>>> opamp is.

    Any explaination why the peaking in your circuit could be blamed on >>>>>> differential capacitance and not care about common-mode capacitance? >>>>>>

    As we?ve discussed before, the differential input capacitance of an op amp
    under bias is hard to measure, and the data sheet values are unreliable. >>>>>
    The best way I know of is to put a very small pot directly in series with >>>>> the inverting input and look at what happens to the phase margin.

    The CM capacitance you can get by doing the same on the noninverting input
    and looking at the bandwidth. Feedback bootstraps out the differential >>>>> capacitance at low frequency.

    Cheers

    Phil Hobbs

    I've seen the "common mode" capacitance defined as the C between one
    pin and the rails, and sometimes as the c of both pins in parellel to
    the world.

    A diagram of the several caps, with values, would help.

    One can Spice a standard inverting amp and see what it does, assumuing >>>> the Spice model is accurate.

    It?s the measurement that?s difficult?if the amp is powered off, none of >>> the junction capacitances will be right.

    Cheers

    Phil Hobbs

    I have a Spice model of the OPA197, basically TI's Pspice model
    converted for LT Spice.

    I made a unity-gain follower sim and drove that with a 1 volt step,
    through a 1M resistor. The output is a nice exponential with tau =
    6.45 usec, which means the c to ground is 6.45 pF.

    The TI data sheet says that cm capacitance is 6.4!

    The differential input c disappeared because it's bootstrapped in a
    follower.

    It doesn't. There's a collector/base or gate/drain capacitance that has
    to be charged up if the input moves vis-a-vis local ground (in this case
    the local rail voltages inside the chip). There are heroic measures that
    can minimise this - essentially floating the power rails though they
    move too slowly to be of all that much help - but regular followers
    don't use them.

    Imagine three caps.

    C1 is inverting input to all the virtual grounds.

    C2 is n.i. input cap to ground

    C3 is between the two inputs.

    TI calls C1 the common-mode capacitance Zic

    They also call C2 the same thing.

    They call C3 the differential capacitance Zid.

    My sim measured only C2, because both C1 and C3 followed the input so
    were bootstrapped out of existence.

    C1 and C2 are each spec'd at 6.4 pF. I estmated 6.45 from my sim,
    eyeballing tau.

    OPA197 has a lots of protections and integral EMI filtering, which
    adds capacitance. Nice safe gumdrop. One can drive the inputs modestly
    past the rails and it doesn't go crazy. It makes a decent RRIO
    comparator too.

    Some people think the "common mode capacitance" is C1 + C2. TI
    doesn't.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Monday, June 08, 2026 00:10:54
    On 7/06/2026 11:19 pm, john larkin wrote:
    On Sun, 7 Jun 2026 14:45:40 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 11:44 am, john larkin wrote:
    On Sun, 7 Jun 2026 00:31:01 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sat, 6 Jun 2026 20:41:07 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 03:06:10 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>> wrote:

    On 7/06/2026 2:33 am, john larkin wrote:
    On Sun, 7 Jun 2026 02:19:03 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>>>> wrote:

    On 7/06/2026 1:57 am, john larkin wrote:
    On Sun, 7 Jun 2026 01:10:57 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 6/06/2026 10:53 pm, john larkin wrote:
    On Sat, 6 Jun 2026 11:29:35 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    They changed the process on a part that's 47 years old. >>>>>>>>>>>>>>>
    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    More than a process change, it is a whole different product. Old was NPN
    input stage, new is PNP inputs. Unforgivable to not amend the part number
    in any way.

    You'd better not buy TI parts any more.

    They were rarely anybody's first choice. Even when they came up with
    something neat they'd leave out a vital detail in the data sheet. >>>>>>>>>>>> They introduced a really nice MOSFET input op-amp and failed to mention
    in the data sheet that it had about 10pF input capacitance. For once I'd
    almost got a printed circuit layout that worked first time, but I had to
    bodge in 2.2pF capacitor in parallel with the feedback resistor to kill
    the oscillation the 10pF produced.

    Yeah, sometimes electronics gets complicated.

    Regular opamps have about 1pF of input capacitance to ground. >>>>>>>>>
    Do you use opamps with a ground pin?

    Don't be silly. The ground reference is through the negative rail >>>>>>>>
    My favorite gumdrop opamp, OPA197, has a typ "common mode" capacitance
    of 6.4 pF, whatever that means.

    https://www.ti.com/lit/ds/symlink/opa197.pdf?ts=1780716494386

    It's on page 7 of the data sheet. I was more worried about the >>>>>>>> differential capacitance, which is 1.6pF for that part (and pretty >>>>>>>> typical). I could try to explain the difference between "differential" >>>>>>>> and "common mode" but if you haven't found out about that by now, you >>>>>>>> clearly aren't interested in finding out.

    Explain it to me. I'm not sure what the commmon-mode capacitance of an >>>>>>> opamp is.

    Any explaination why the peaking in your circuit could be blamed on >>>>>>> differential capacitance and not care about common-mode capacitance? >>>>>>>

    As we?ve discussed before, the differential input capacitance of an op amp
    under bias is hard to measure, and the data sheet values are unreliable. >>>>>>
    The best way I know of is to put a very small pot directly in series with
    the inverting input and look at what happens to the phase margin.

    The CM capacitance you can get by doing the same on the noninverting input
    and looking at the bandwidth. Feedback bootstraps out the differential >>>>>> capacitance at low frequency.

    Cheers

    Phil Hobbs

    I've seen the "common mode" capacitance defined as the C between one >>>>> pin and the rails, and sometimes as the c of both pins in parellel to >>>>> the world.

    A diagram of the several caps, with values, would help.

    One can Spice a standard inverting amp and see what it does, assumuing >>>>> the Spice model is accurate.

    It?s the measurement that?s difficult?if the amp is powered off, none of >>>> the junction capacitances will be right.

    Cheers

    Phil Hobbs

    I have a Spice model of the OPA197, basically TI's Pspice model
    converted for LT Spice.

    I made a unity-gain follower sim and drove that with a 1 volt step,
    through a 1M resistor. The output is a nice exponential with tau =
    6.45 usec, which means the c to ground is 6.45 pF.

    The TI data sheet says that cm capacitance is 6.4!

    The differential input c disappeared because it's bootstrapped in a
    follower.

    It doesn't. There's a collector/base or gate/drain capacitance that has
    to be charged up if the input moves vis-a-vis local ground (in this case
    the local rail voltages inside the chip). There are heroic measures that
    can minimise this - essentially floating the power rails though they
    move too slowly to be of all that much help - but regular followers
    don't use them.

    Imagine three caps.

    Probably not a useful exercise, judging from the unhelpful observations
    that followed, which I've snipped.

    --
    Bill Sloman, Sydney




    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From piglet@3:633/10 to All on Sunday, June 07, 2026 14:40:04
    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 14:45:40 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 11:44 am, john larkin wrote:
    On Sun, 7 Jun 2026 00:31:01 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sat, 6 Jun 2026 20:41:07 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 03:06:10 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>> wrote:

    On 7/06/2026 2:33 am, john larkin wrote:
    On Sun, 7 Jun 2026 02:19:03 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>>>> wrote:

    On 7/06/2026 1:57 am, john larkin wrote:
    On Sun, 7 Jun 2026 01:10:57 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 6/06/2026 10:53 pm, john larkin wrote:
    On Sat, 6 Jun 2026 11:29:35 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    They changed the process on a part that's 47 years old. >>>>>>>>>>>>>>>
    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    More than a process change, it is a whole different product. Old was NPN
    input stage, new is PNP inputs. Unforgivable to not amend the part number
    in any way.

    You'd better not buy TI parts any more.

    They were rarely anybody's first choice. Even when they came up with
    something neat they'd leave out a vital detail in the data sheet. >>>>>>>>>>>> They introduced a really nice MOSFET input op-amp and failed to mention
    in the data sheet that it had about 10pF input capacitance. For once I'd
    almost got a printed circuit layout that worked first time, but I had to
    bodge in 2.2pF capacitor in parallel with the feedback resistor to kill
    the oscillation the 10pF produced.

    Yeah, sometimes electronics gets complicated.

    Regular opamps have about 1pF of input capacitance to ground. >>>>>>>>>
    Do you use opamps with a ground pin?

    Don't be silly. The ground reference is through the negative rail >>>>>>>>
    My favorite gumdrop opamp, OPA197, has a typ "common mode" capacitance
    of 6.4 pF, whatever that means.

    https://www.ti.com/lit/ds/symlink/opa197.pdf?ts=1780716494386

    It's on page 7 of the data sheet. I was more worried about the >>>>>>>> differential capacitance, which is 1.6pF for that part (and pretty >>>>>>>> typical). I could try to explain the difference between "differential" >>>>>>>> and "common mode" but if you haven't found out about that by now, you >>>>>>>> clearly aren't interested in finding out.

    Explain it to me. I'm not sure what the commmon-mode capacitance of an >>>>>>> opamp is.

    Any explaination why the peaking in your circuit could be blamed on >>>>>>> differential capacitance and not care about common-mode capacitance? >>>>>>>

    As we?ve discussed before, the differential input capacitance of an op amp
    under bias is hard to measure, and the data sheet values are unreliable. >>>>>>
    The best way I know of is to put a very small pot directly in series with
    the inverting input and look at what happens to the phase margin.

    The CM capacitance you can get by doing the same on the noninverting input
    and looking at the bandwidth. Feedback bootstraps out the differential >>>>>> capacitance at low frequency.

    Cheers

    Phil Hobbs

    I've seen the "common mode" capacitance defined as the C between one >>>>> pin and the rails, and sometimes as the c of both pins in parellel to >>>>> the world.

    A diagram of the several caps, with values, would help.

    One can Spice a standard inverting amp and see what it does, assumuing >>>>> the Spice model is accurate.

    It?s the measurement that?s difficult?if the amp is powered off, none of >>>> the junction capacitances will be right.

    Cheers

    Phil Hobbs

    I have a Spice model of the OPA197, basically TI's Pspice model
    converted for LT Spice.

    I made a unity-gain follower sim and drove that with a 1 volt step,
    through a 1M resistor. The output is a nice exponential with tau =
    6.45 usec, which means the c to ground is 6.45 pF.

    The TI data sheet says that cm capacitance is 6.4!

    The differential input c disappeared because it's bootstrapped in a
    follower.

    It doesn't. There's a collector/base or gate/drain capacitance that has
    to be charged up if the input moves vis-a-vis local ground (in this case
    the local rail voltages inside the chip). There are heroic measures that
    can minimise this - essentially floating the power rails though they
    move too slowly to be of all that much help - but regular followers
    don't use them.

    Imagine three caps.

    C1 is inverting input to all the virtual grounds.

    C2 is n.i. input cap to ground

    C3 is between the two inputs.

    TI calls C1 the common-mode capacitance Zic

    They also call C2 the same thing.

    They call C3 the differential capacitance Zid.

    My sim measured only C2, because both C1 and C3 followed the input so
    were bootstrapped out of existence.

    C1 and C2 are each spec'd at 6.4 pF. I estmated 6.45 from my sim,
    eyeballing tau.

    OPA197 has a lots of protections and integral EMI filtering, which
    adds capacitance. Nice safe gumdrop. One can drive the inputs modestly
    past the rails and it doesn't go crazy. It makes a decent RRIO
    comparator too.

    Some people think the "common mode capacitance" is C1 + C2. TI
    doesn't.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    Thanks, that makes sense, beforehand I too would have said it was C1+C2


    --
    piglet

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Sunday, June 07, 2026 09:01:24
    On Mon, 8 Jun 2026 00:10:54 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 11:19 pm, john larkin wrote:
    On Sun, 7 Jun 2026 14:45:40 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 11:44 am, john larkin wrote:
    On Sun, 7 Jun 2026 00:31:01 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sat, 6 Jun 2026 20:41:07 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 03:06:10 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>>> wrote:

    On 7/06/2026 2:33 am, john larkin wrote:
    On Sun, 7 Jun 2026 02:19:03 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 1:57 am, john larkin wrote:
    On Sun, 7 Jun 2026 01:10:57 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 6/06/2026 10:53 pm, john larkin wrote:
    On Sat, 6 Jun 2026 11:29:35 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones >>>>>>>>>>>>>>>> <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    They changed the process on a part that's 47 years old. >>>>>>>>>>>>>>>>
    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    More than a process change, it is a whole different product. Old was NPN
    input stage, new is PNP inputs. Unforgivable to not amend the part number
    in any way.

    You'd better not buy TI parts any more.

    They were rarely anybody's first choice. Even when they came up with
    something neat they'd leave out a vital detail in the data sheet. >>>>>>>>>>>>> They introduced a really nice MOSFET input op-amp and failed to mention
    in the data sheet that it had about 10pF input capacitance. For once I'd
    almost got a printed circuit layout that worked first time, but I had to
    bodge in 2.2pF capacitor in parallel with the feedback resistor to kill
    the oscillation the 10pF produced.

    Yeah, sometimes electronics gets complicated.

    Regular opamps have about 1pF of input capacitance to ground. >>>>>>>>>>
    Do you use opamps with a ground pin?

    Don't be silly. The ground reference is through the negative rail >>>>>>>>>
    My favorite gumdrop opamp, OPA197, has a typ "common mode" capacitance
    of 6.4 pF, whatever that means.

    https://www.ti.com/lit/ds/symlink/opa197.pdf?ts=1780716494386 >>>>>>>>>
    It's on page 7 of the data sheet. I was more worried about the >>>>>>>>> differential capacitance, which is 1.6pF for that part (and pretty >>>>>>>>> typical). I could try to explain the difference between "differential"
    and "common mode" but if you haven't found out about that by now, you >>>>>>>>> clearly aren't interested in finding out.

    Explain it to me. I'm not sure what the commmon-mode capacitance of an >>>>>>>> opamp is.

    Any explaination why the peaking in your circuit could be blamed on >>>>>>>> differential capacitance and not care about common-mode capacitance? >>>>>>>>

    As we?ve discussed before, the differential input capacitance of an op amp
    under bias is hard to measure, and the data sheet values are unreliable.

    The best way I know of is to put a very small pot directly in series with
    the inverting input and look at what happens to the phase margin. >>>>>>>
    The CM capacitance you can get by doing the same on the noninverting input
    and looking at the bandwidth. Feedback bootstraps out the differential >>>>>>> capacitance at low frequency.

    Cheers

    Phil Hobbs

    I've seen the "common mode" capacitance defined as the C between one >>>>>> pin and the rails, and sometimes as the c of both pins in parellel to >>>>>> the world.

    A diagram of the several caps, with values, would help.

    One can Spice a standard inverting amp and see what it does, assumuing >>>>>> the Spice model is accurate.

    It?s the measurement that?s difficult?if the amp is powered off, none of >>>>> the junction capacitances will be right.

    Cheers

    Phil Hobbs

    I have a Spice model of the OPA197, basically TI's Pspice model
    converted for LT Spice.

    I made a unity-gain follower sim and drove that with a 1 volt step,
    through a 1M resistor. The output is a nice exponential with tau =
    6.45 usec, which means the c to ground is 6.45 pF.

    The TI data sheet says that cm capacitance is 6.4!

    The differential input c disappeared because it's bootstrapped in a
    follower.

    It doesn't. There's a collector/base or gate/drain capacitance that has
    to be charged up if the input moves vis-a-vis local ground (in this case >>> the local rail voltages inside the chip). There are heroic measures that >>> can minimise this - essentially floating the power rails though they
    move too slowly to be of all that much help - but regular followers
    don't use them.

    Imagine three caps.

    Probably not a useful exercise, judging from the unhelpful observations
    that followed, which I've snipped.

    Of course observations like this are not helpful to you.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Sunday, June 07, 2026 09:04:28
    On Sun, 7 Jun 2026 14:40:04 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 14:45:40 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 11:44 am, john larkin wrote:
    On Sun, 7 Jun 2026 00:31:01 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sat, 6 Jun 2026 20:41:07 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 03:06:10 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>>> wrote:

    On 7/06/2026 2:33 am, john larkin wrote:
    On Sun, 7 Jun 2026 02:19:03 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 1:57 am, john larkin wrote:
    On Sun, 7 Jun 2026 01:10:57 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 6/06/2026 10:53 pm, john larkin wrote:
    On Sat, 6 Jun 2026 11:29:35 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones >>>>>>>>>>>>>>>> <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    They changed the process on a part that's 47 years old. >>>>>>>>>>>>>>>>
    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    More than a process change, it is a whole different product. Old was NPN
    input stage, new is PNP inputs. Unforgivable to not amend the part number
    in any way.

    You'd better not buy TI parts any more.

    They were rarely anybody's first choice. Even when they came up with
    something neat they'd leave out a vital detail in the data sheet. >>>>>>>>>>>>> They introduced a really nice MOSFET input op-amp and failed to mention
    in the data sheet that it had about 10pF input capacitance. For once I'd
    almost got a printed circuit layout that worked first time, but I had to
    bodge in 2.2pF capacitor in parallel with the feedback resistor to kill
    the oscillation the 10pF produced.

    Yeah, sometimes electronics gets complicated.

    Regular opamps have about 1pF of input capacitance to ground. >>>>>>>>>>
    Do you use opamps with a ground pin?

    Don't be silly. The ground reference is through the negative rail >>>>>>>>>
    My favorite gumdrop opamp, OPA197, has a typ "common mode" capacitance
    of 6.4 pF, whatever that means.

    https://www.ti.com/lit/ds/symlink/opa197.pdf?ts=1780716494386 >>>>>>>>>
    It's on page 7 of the data sheet. I was more worried about the >>>>>>>>> differential capacitance, which is 1.6pF for that part (and pretty >>>>>>>>> typical). I could try to explain the difference between "differential"
    and "common mode" but if you haven't found out about that by now, you >>>>>>>>> clearly aren't interested in finding out.

    Explain it to me. I'm not sure what the commmon-mode capacitance of an >>>>>>>> opamp is.

    Any explaination why the peaking in your circuit could be blamed on >>>>>>>> differential capacitance and not care about common-mode capacitance? >>>>>>>>

    As we?ve discussed before, the differential input capacitance of an op amp
    under bias is hard to measure, and the data sheet values are unreliable.

    The best way I know of is to put a very small pot directly in series with
    the inverting input and look at what happens to the phase margin. >>>>>>>
    The CM capacitance you can get by doing the same on the noninverting input
    and looking at the bandwidth. Feedback bootstraps out the differential >>>>>>> capacitance at low frequency.

    Cheers

    Phil Hobbs

    I've seen the "common mode" capacitance defined as the C between one >>>>>> pin and the rails, and sometimes as the c of both pins in parellel to >>>>>> the world.

    A diagram of the several caps, with values, would help.

    One can Spice a standard inverting amp and see what it does, assumuing >>>>>> the Spice model is accurate.

    It?s the measurement that?s difficult?if the amp is powered off, none of >>>>> the junction capacitances will be right.

    Cheers

    Phil Hobbs

    I have a Spice model of the OPA197, basically TI's Pspice model
    converted for LT Spice.

    I made a unity-gain follower sim and drove that with a 1 volt step,
    through a 1M resistor. The output is a nice exponential with tau =
    6.45 usec, which means the c to ground is 6.45 pF.

    The TI data sheet says that cm capacitance is 6.4!

    The differential input c disappeared because it's bootstrapped in a
    follower.

    It doesn't. There's a collector/base or gate/drain capacitance that has >>> to be charged up if the input moves vis-a-vis local ground (in this case >>> the local rail voltages inside the chip). There are heroic measures that >>> can minimise this - essentially floating the power rails though they
    move too slowly to be of all that much help - but regular followers
    don't use them.

    Imagine three caps.

    C1 is inverting input to all the virtual grounds.

    C2 is n.i. input cap to ground

    C3 is between the two inputs.

    TI calls C1 the common-mode capacitance Zic

    They also call C2 the same thing.

    They call C3 the differential capacitance Zid.

    My sim measured only C2, because both C1 and C3 followed the input so
    were bootstrapped out of existence.

    C1 and C2 are each spec'd at 6.4 pF. I estmated 6.45 from my sim,
    eyeballing tau.

    OPA197 has a lots of protections and integral EMI filtering, which
    adds capacitance. Nice safe gumdrop. One can drive the inputs modestly
    past the rails and it doesn't go crazy. It makes a decent RRIO
    comparator too.

    Some people think the "common mode capacitance" is C1 + C2. TI
    doesn't.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    Thanks, that makes sense, beforehand I too would have said it was C1+C2

    It's interesting, but one can just Spice actual circuits and see what
    happens. Understanding the capacitances helps make the initial opamp
    selections to sim.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From joegwinn@3:633/10 to All on Sunday, June 07, 2026 14:13:16
    On Sun, 07 Jun 2026 09:04:28 -0700, john larkin <jl@glen--canyon.com>
    wrote:

    On Sun, 7 Jun 2026 14:40:04 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 14:45:40 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 11:44 am, john larkin wrote:
    On Sun, 7 Jun 2026 00:31:01 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sat, 6 Jun 2026 20:41:07 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 03:06:10 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>>>> wrote:

    On 7/06/2026 2:33 am, john larkin wrote:
    On Sun, 7 Jun 2026 02:19:03 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 1:57 am, john larkin wrote:
    On Sun, 7 Jun 2026 01:10:57 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 6/06/2026 10:53 pm, john larkin wrote:
    On Sat, 6 Jun 2026 11:29:35 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones >>>>>>>>>>>>>>>>> <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY >>>>>>>>>>>>>>>>>
    They changed the process on a part that's 47 years old. >>>>>>>>>>>>>>>>>
    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    More than a process change, it is a whole different product. Old was NPN
    input stage, new is PNP inputs. Unforgivable to not amend the part number
    in any way.

    You'd better not buy TI parts any more.

    They were rarely anybody's first choice. Even when they came up with
    something neat they'd leave out a vital detail in the data sheet.
    They introduced a really nice MOSFET input op-amp and failed to mention
    in the data sheet that it had about 10pF input capacitance. For once I'd
    almost got a printed circuit layout that worked first time, but I had to
    bodge in 2.2pF capacitor in parallel with the feedback resistor to kill
    the oscillation the 10pF produced.

    Yeah, sometimes electronics gets complicated.

    Regular opamps have about 1pF of input capacitance to ground. >>>>>>>>>>>
    Do you use opamps with a ground pin?

    Don't be silly. The ground reference is through the negative rail >>>>>>>>>>
    My favorite gumdrop opamp, OPA197, has a typ "common mode" capacitance
    of 6.4 pF, whatever that means.

    https://www.ti.com/lit/ds/symlink/opa197.pdf?ts=1780716494386 >>>>>>>>>>
    It's on page 7 of the data sheet. I was more worried about the >>>>>>>>>> differential capacitance, which is 1.6pF for that part (and pretty >>>>>>>>>> typical). I could try to explain the difference between "differential"
    and "common mode" but if you haven't found out about that by now, you
    clearly aren't interested in finding out.

    Explain it to me. I'm not sure what the commmon-mode capacitance of an
    opamp is.

    Any explaination why the peaking in your circuit could be blamed on >>>>>>>>> differential capacitance and not care about common-mode capacitance? >>>>>>>>>

    As we?ve discussed before, the differential input capacitance of an op amp
    under bias is hard to measure, and the data sheet values are unreliable.

    The best way I know of is to put a very small pot directly in series with
    the inverting input and look at what happens to the phase margin. >>>>>>>>
    The CM capacitance you can get by doing the same on the noninverting input
    and looking at the bandwidth. Feedback bootstraps out the differential
    capacitance at low frequency.

    Cheers

    Phil Hobbs

    I've seen the "common mode" capacitance defined as the C between one >>>>>>> pin and the rails, and sometimes as the c of both pins in parellel to >>>>>>> the world.

    A diagram of the several caps, with values, would help.

    One can Spice a standard inverting amp and see what it does, assumuing >>>>>>> the Spice model is accurate.

    It?s the measurement that?s difficult?if the amp is powered off, none of >>>>>> the junction capacitances will be right.

    Cheers

    Phil Hobbs

    I have a Spice model of the OPA197, basically TI's Pspice model
    converted for LT Spice.

    I made a unity-gain follower sim and drove that with a 1 volt step,
    through a 1M resistor. The output is a nice exponential with tau =
    6.45 usec, which means the c to ground is 6.45 pF.

    The TI data sheet says that cm capacitance is 6.4!

    The differential input c disappeared because it's bootstrapped in a
    follower.

    It doesn't. There's a collector/base or gate/drain capacitance that has >>>> to be charged up if the input moves vis-a-vis local ground (in this case >>>> the local rail voltages inside the chip). There are heroic measures that >>>> can minimise this - essentially floating the power rails though they
    move too slowly to be of all that much help - but regular followers
    don't use them.

    Imagine three caps.

    C1 is inverting input to all the virtual grounds.

    C2 is n.i. input cap to ground

    C3 is between the two inputs.

    TI calls C1 the common-mode capacitance Zic

    They also call C2 the same thing.

    They call C3 the differential capacitance Zid.

    My sim measured only C2, because both C1 and C3 followed the input so
    were bootstrapped out of existence.

    C1 and C2 are each spec'd at 6.4 pF. I estmated 6.45 from my sim,
    eyeballing tau.

    OPA197 has a lots of protections and integral EMI filtering, which
    adds capacitance. Nice safe gumdrop. One can drive the inputs modestly
    past the rails and it doesn't go crazy. It makes a decent RRIO
    comparator too.

    Some people think the "common mode capacitance" is C1 + C2. TI
    doesn't.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    Thanks, that makes sense, beforehand I too would have said it was C1+C2

    It's interesting, but one can just Spice actual circuits and see what >happens. Understanding the capacitances helps make the initial opamp >selections to sim.

    I have a parallel story. The problem was to measure the Differential
    and Common-Mode current passing between a central power system and the
    power system within a major subsystem on some heavy conductors. There
    were debates as to just what it all meant.

    The solution was to use a current transformer. If both conductors
    passed in parallel through the current transformer's aperture, the
    common-mode current was measured. If those two conductors passed in
    opposite directions, twice the differential current was measured.

    Joe

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Phil Hobbs@3:633/10 to All on Sunday, June 07, 2026 18:49:05
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info
    on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick
    this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI
    never showed up, in the first place.

    RL


    If I hadn?t stopped talking audio design seriously in about 1980, I
    certainly would have when crappy compressed MP3s took over the world.

    Golden ears, my left buttock.

    Cheers

    Phil Hobbs


    TI managed it much better with the 324 and 339. They brought out the B
    versions with their own datasheets and kept making the old ones.

    I wonder if that process has gone away too. It must be a drag keeping
    creaky old litho tools and 5- inch wafer processes alive. Probably duct
    tape on top of JB Weld.

    Cheers

    Phil Hobbs

    --
    Dr Philip C D Hobbs Principal Consultant ElectroOptical Innovations LLC / Hobbs ElectroOptics Optics, Electro-optics, Photonics, Analog Electronics

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Sunday, June 07, 2026 13:10:13
    On Sun, 7 Jun 2026 18:49:05 -0000 (UTC), Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:

    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info
    on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick
    this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI
    never showed up, in the first place.

    RL


    If I hadn?t stopped talking audio design seriously in about 1980, I
    certainly would have when crappy compressed MP3s took over the world.

    Golden ears, my left buttock.

    Cheers

    Phil Hobbs


    TI managed it much better with the 324 and 339. They brought out the B >versions with their own datasheets and kept making the old ones.

    In the original National parts, all four channels would go bonkers if
    any input went slightly below ground.


    I wonder if that process has gone away too. It must be a drag keeping
    creaky old litho tools and 5- inch wafer processes alive. Probably duct
    tape on top of JB Weld.

    And the test sets.

    A support guy said "That's an old Burr-Brown part. We don't know much
    about those."

    Speaking of TI, this is incredible:

    https://www.ti.com/product/ADS131M02

    Under $2.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Phil Hobbs@3:633/10 to All on Sunday, June 07, 2026 20:52:26
    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 18:49:05 -0000 (UTC), Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:

    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info
    on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick
    this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI
    never showed up, in the first place.

    RL


    If I hadn?t stopped talking audio design seriously in about 1980, I
    certainly would have when crappy compressed MP3s took over the world.

    Golden ears, my left buttock.

    Cheers

    Phil Hobbs


    TI managed it much better with the 324 and 339. They brought out the B
    versions with their own datasheets and kept making the old ones.

    In the original National parts, all four channels would go bonkers if
    any input went slightly below ground.

    And saturated the tail source transistor, which then hogged all the base
    drive from the other sections.

    They fixed that in the 324A and the 358, iirc. Doesn?t seem to happen
    anymore, at least.


    I wonder if that process has gone away too. It must be a drag keeping
    creaky old litho tools and 5- inch wafer processes alive. Probably duct
    tape on top of JB Weld.

    And the test sets.

    A support guy said "That's an old Burr-Brown part. We don't know much
    about those."

    Speaking of TI, this is incredible:

    https://www.ti.com/product/ADS131M02

    Under $2.
    Nice. We?ll have to find a use for it.

    Cheers

    Phil Hobbs



    --
    Dr Philip C D Hobbs Principal Consultant ElectroOptical Innovations LLC / Hobbs ElectroOptics Optics, Electro-optics, Photonics, Analog Electronics

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Chris Jones@3:633/10 to All on Monday, June 08, 2026 12:12:27
    On 8/06/2026 2:04 am, john larkin wrote:
    On Sun, 7 Jun 2026 14:40:04 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 14:45:40 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 11:44 am, john larkin wrote:
    On Sun, 7 Jun 2026 00:31:01 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sat, 6 Jun 2026 20:41:07 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 03:06:10 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>>>> wrote:

    On 7/06/2026 2:33 am, john larkin wrote:
    On Sun, 7 Jun 2026 02:19:03 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 1:57 am, john larkin wrote:
    On Sun, 7 Jun 2026 01:10:57 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 6/06/2026 10:53 pm, john larkin wrote:
    On Sat, 6 Jun 2026 11:29:35 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones >>>>>>>>>>>>>>>>> <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY >>>>>>>>>>>>>>>>>
    They changed the process on a part that's 47 years old. >>>>>>>>>>>>>>>>>
    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    More than a process change, it is a whole different product. Old was NPN
    input stage, new is PNP inputs. Unforgivable to not amend the part number
    in any way.

    You'd better not buy TI parts any more.

    They were rarely anybody's first choice. Even when they came up with
    something neat they'd leave out a vital detail in the data sheet.
    They introduced a really nice MOSFET input op-amp and failed to mention
    in the data sheet that it had about 10pF input capacitance. For once I'd
    almost got a printed circuit layout that worked first time, but I had to
    bodge in 2.2pF capacitor in parallel with the feedback resistor to kill
    the oscillation the 10pF produced.

    Yeah, sometimes electronics gets complicated.

    Regular opamps have about 1pF of input capacitance to ground. >>>>>>>>>>>
    Do you use opamps with a ground pin?

    Don't be silly. The ground reference is through the negative rail >>>>>>>>>>
    My favorite gumdrop opamp, OPA197, has a typ "common mode" capacitance
    of 6.4 pF, whatever that means.

    https://www.ti.com/lit/ds/symlink/opa197.pdf?ts=1780716494386 >>>>>>>>>>
    It's on page 7 of the data sheet. I was more worried about the >>>>>>>>>> differential capacitance, which is 1.6pF for that part (and pretty >>>>>>>>>> typical). I could try to explain the difference between "differential"
    and "common mode" but if you haven't found out about that by now, you
    clearly aren't interested in finding out.

    Explain it to me. I'm not sure what the commmon-mode capacitance of an
    opamp is.

    Any explaination why the peaking in your circuit could be blamed on >>>>>>>>> differential capacitance and not care about common-mode capacitance? >>>>>>>>>

    As we?ve discussed before, the differential input capacitance of an op amp
    under bias is hard to measure, and the data sheet values are unreliable.

    The best way I know of is to put a very small pot directly in series with
    the inverting input and look at what happens to the phase margin. >>>>>>>>
    The CM capacitance you can get by doing the same on the noninverting input
    and looking at the bandwidth. Feedback bootstraps out the differential
    capacitance at low frequency.

    Cheers

    Phil Hobbs

    I've seen the "common mode" capacitance defined as the C between one >>>>>>> pin and the rails, and sometimes as the c of both pins in parellel to >>>>>>> the world.

    A diagram of the several caps, with values, would help.

    One can Spice a standard inverting amp and see what it does, assumuing >>>>>>> the Spice model is accurate.

    It?s the measurement that?s difficult?if the amp is powered off, none of >>>>>> the junction capacitances will be right.

    Cheers

    Phil Hobbs

    I have a Spice model of the OPA197, basically TI's Pspice model
    converted for LT Spice.

    I made a unity-gain follower sim and drove that with a 1 volt step,
    through a 1M resistor. The output is a nice exponential with tau =
    6.45 usec, which means the c to ground is 6.45 pF.

    The TI data sheet says that cm capacitance is 6.4!

    The differential input c disappeared because it's bootstrapped in a
    follower.

    It doesn't. There's a collector/base or gate/drain capacitance that has >>>> to be charged up if the input moves vis-a-vis local ground (in this case >>>> the local rail voltages inside the chip). There are heroic measures that >>>> can minimise this - essentially floating the power rails though they
    move too slowly to be of all that much help - but regular followers
    don't use them.

    Imagine three caps.

    C1 is inverting input to all the virtual grounds.

    C2 is n.i. input cap to ground

    C3 is between the two inputs.

    TI calls C1 the common-mode capacitance Zic

    They also call C2 the same thing.

    They call C3 the differential capacitance Zid.

    My sim measured only C2, because both C1 and C3 followed the input so
    were bootstrapped out of existence.

    C1 and C2 are each spec'd at 6.4 pF. I estmated 6.45 from my sim,
    eyeballing tau.

    OPA197 has a lots of protections and integral EMI filtering, which
    adds capacitance. Nice safe gumdrop. One can drive the inputs modestly
    past the rails and it doesn't go crazy. It makes a decent RRIO
    comparator too.

    Some people think the "common mode capacitance" is C1 + C2. TI
    doesn't.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    Thanks, that makes sense, beforehand I too would have said it was C1+C2

    It's interesting, but one can just Spice actual circuits and see what happens. Understanding the capacitances helps make the initial opamp selections to sim.


    A frustrating thing is that the opamp manufacturer has an exceedingly
    accurate spice model of the part that their designers created in order
    to optimise and verify the design, but the company won't give that one
    to the public. The schematic in the datasheet is often drawn by
    marketing people who have never discussed it with the design engineers,
    let alone seen the real schematic, and is sometimes a source of great amusement to the actual designers. The public spice model is quite
    possibly created in a similar manner, but possibly corrected based on
    some measurements by apps engineers or based on complaints from
    customers. Meanwhile the really accurate model sits on some internal
    server being ignored while the design engineers have moved on to some
    other product.





    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Monday, June 08, 2026 15:36:42
    On 8/06/2026 12:12 pm, Chris Jones wrote:
    On 8/06/2026 2:04 am, john larkin wrote:
    On Sun, 7 Jun 2026 14:40:04 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 14:45:40 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 11:44 am, john larkin wrote:
    On Sun, 7 Jun 2026 00:31:01 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sat, 6 Jun 2026 20:41:07 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 03:06:10 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 2:33 am, john larkin wrote:
    On Sun, 7 Jun 2026 02:19:03 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 1:57 am, john larkin wrote:
    On Sun, 7 Jun 2026 01:10:57 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:

    On 6/06/2026 10:53 pm, john larkin wrote:
    On Sat, 6 Jun 2026 11:29:35 -0000 (UTC), piglet >>>>>>>>>>>>>>>> <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones >>>>>>>>>>>>>>>>>> <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY >>>>>>>>>>>>>>>>>>
    They changed the process on a part that's 47 years old. >>>>>>>>>>>>>>>>>>
    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    More than a process change, it is a whole different >>>>>>>>>>>>>>>>> product. Old was NPN
    input stage, new is PNP inputs. Unforgivable to not >>>>>>>>>>>>>>>>> amend the part number
    in any way.

    You'd better not buy TI parts any more.

    They were rarely anybody's first choice. Even when they >>>>>>>>>>>>>>> came up with
    something neat they'd leave out a vital detail in the >>>>>>>>>>>>>>> data sheet.
    They introduced a really nice MOSFET input op-amp and >>>>>>>>>>>>>>> failed to mention
    in the data sheet that it had about 10pF input
    capacitance. For once I'd
    almost got a printed circuit layout that worked first >>>>>>>>>>>>>>> time, but I had to
    bodge in 2.2pF capacitor in parallel with the feedback >>>>>>>>>>>>>>> resistor to kill
    the oscillation the 10pF produced.

    Yeah, sometimes electronics gets complicated.

    Regular opamps have about 1pF of input capacitance to ground. >>>>>>>>>>>>
    Do you use opamps with a ground pin?

    Don't be silly. The ground reference is through the negative >>>>>>>>>>> rail

    My favorite gumdrop opamp, OPA197, has a typ "common mode" >>>>>>>>>>>> capacitance
    of 6.4 pF, whatever that means.

    https://www.ti.com/lit/ds/symlink/opa197.pdf?ts=1780716494386 >>>>>>>>>>>
    It's on page 7 of the data sheet. I was more worried about the >>>>>>>>>>> differential capacitance, which is 1.6pF for that part (and >>>>>>>>>>> pretty
    typical). I could try to explain the difference between >>>>>>>>>>> "differential"
    and "common mode" but if you haven't found out about that by >>>>>>>>>>> now, you
    clearly aren't interested in finding out.

    Explain it to me. I'm not sure what the commmon-mode
    capacitance of an
    opamp is.

    Any explaination why the peaking in your circuit could be >>>>>>>>>> blamed on
    differential capacitance and not care about common-mode
    capacitance?


    As we?ve discussed before, the differential input capacitance >>>>>>>>> of an op amp
    under bias is hard to measure, and the data sheet values are >>>>>>>>> unreliable.

    The best way I know of is to put a very small pot directly in >>>>>>>>> series with
    the inverting input and look at what happens to the phase margin. >>>>>>>>>
    The CM capacitance you can get by doing the same on the
    noninverting input
    and looking at the bandwidth.˙ Feedback bootstraps out the
    differential
    capacitance at low frequency.

    Cheers

    Phil Hobbs

    I've seen the "common mode" capacitance defined as the C between >>>>>>>> one
    pin and the rails, and sometimes as the c of both pins in
    parellel to
    the world.

    A diagram of the several caps, with values, would help.

    One can Spice a standard inverting amp and see what it does,
    assumuing
    the Spice model is accurate.

    It?s the measurement that?s difficult?if the amp is powered off, >>>>>>> none of
    the junction capacitances will be right.

    Cheers

    Phil Hobbs

    I have a Spice model of the OPA197, basically TI's Pspice model
    converted for LT Spice.

    I made a unity-gain follower sim and drove that with a 1 volt step, >>>>>> through a 1M resistor. The output is a nice exponential with tau = >>>>>> 6.45 usec, which means the c to ground is 6.45 pF.

    The TI data sheet says that cm capacitance is 6.4!

    The differential input c disappeared because it's bootstrapped in a >>>>>> follower.

    It doesn't. There's a collector/base or gate/drain capacitance that >>>>> has
    to be charged up if the input moves vis-a-vis local ground (in this >>>>> case
    the local rail voltages inside the chip). There are heroic measures >>>>> that
    can minimise this - essentially floating the power rails though they >>>>> move too slowly to be of all that much help - but regular followers
    don't use them.

    Imagine three caps.

    Don't bother.

    <snip>

    My sim measured only C2, because both C1 and C3 followed the input so
    were bootstrapped out of existence.

    Whatever that is supposed to mean.

    <snip>

    Thanks, that makes sense, beforehand I too would have said it was C1+C2

    It's interesting, but one can just Spice actual circuits and see what
    happens. Understanding the capacitances helps make the initial opamp
    selections to sim.

    If the simulation is any good. The published simulation models are
    mostly behavioral, and precise enough for the purpose the marketing
    people had in mind.

    A frustrating thing is that the opamp manufacturer has an exceedingly accurate spice model of the part that their designers created in order
    to optimise and verify the design, but the company won't give that one
    to the public.

    It's "commercial in confidence" because it exposes a lot of the detailed design of the chip being simulated.


    The schematic in the datasheet is often drawn by
    marketing people who have never discussed it with the design engineers,
    let alone seen the real schematic, and is sometimes a source of great amusement to the actual designers.

    Commercial secrecy pretty much demands that.

    The public spice model is quite
    possibly created in a similar manner, but possibly corrected based on
    some measurements by apps engineers or based on complaints from
    customers. Meanwhile the really accurate model sits on some internal
    server being ignored while the design engineers have moved on to some
    other product.

    It's not ignored - just too revealing to be made public.

    The late Jim Thompson used to claim that he could create behavioral
    models that were just as accurate as the transistor level models and a
    lot more compact. He was touting for business, but he had to be able to deliver something pretty good to make it worth his while to advertise at
    all.

    --
    Bill Sloman, Sydney


    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Monday, June 08, 2026 15:44:19
    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info
    on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick
    this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI
    never showed up, in the first place.

    If I hadn?t stopped talking audio design seriously in about 1980, I
    certainly would have when crappy compressed MP3s took over the world.

    Golden ears, my left buttock.

    The ears are close to the brain for a reason. Golden ears don't seem to
    be close to particularly good brains.

    TI managed it much better with the 324 and 339. They brought out the B versions with their own datasheets and kept making the old ones.

    I wonder if that process has gone away too. It must be a drag keeping
    creaky old litho tools and 5- inch wafer processes alive. Probably duct
    tape on top of JB Weld.

    Why would they bother? You can create the old patterns with much higher accuracy on 8 - inch wafers with modern tool, and many of the old
    designs worked fine if merely shrunk a bit (creating even more parts per wafer).

    --
    Bill Sloman, Sydney



    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Chris Jones@3:633/10 to All on Monday, June 08, 2026 21:38:21
    On 8/06/2026 3:36 pm, Bill Sloman wrote:
    On 8/06/2026 12:12 pm, Chris Jones wrote:
    On 8/06/2026 2:04 am, john larkin wrote:
    On Sun, 7 Jun 2026 14:40:04 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 14:45:40 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>> wrote:

    On 7/06/2026 11:44 am, john larkin wrote:
    On Sun, 7 Jun 2026 00:31:01 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sat, 6 Jun 2026 20:41:07 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 03:06:10 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 2:33 am, john larkin wrote:
    On Sun, 7 Jun 2026 02:19:03 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 1:57 am, john larkin wrote:
    On Sun, 7 Jun 2026 01:10:57 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:

    On 6/06/2026 10:53 pm, john larkin wrote:
    On Sat, 6 Jun 2026 11:29:35 -0000 (UTC), piglet >>>>>>>>>>>>>>>>> <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones >>>>>>>>>>>>>>>>>>> <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY >>>>>>>>>>>>>>>>>>>
    They changed the process on a part that's 47 years old. >>>>>>>>>>>>>>>>>>>
    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    More than a process change, it is a whole different >>>>>>>>>>>>>>>>>> product. Old was NPN
    input stage, new is PNP inputs. Unforgivable to not >>>>>>>>>>>>>>>>>> amend the part number
    in any way.

    You'd better not buy TI parts any more.

    They were rarely anybody's first choice. Even when they >>>>>>>>>>>>>>>> came up with
    something neat they'd leave out a vital detail in the >>>>>>>>>>>>>>>> data sheet.
    They introduced a really nice MOSFET input op-amp and >>>>>>>>>>>>>>>> failed to mention
    in the data sheet that it had about 10pF input >>>>>>>>>>>>>>>> capacitance. For once I'd
    almost got a printed circuit layout that worked first >>>>>>>>>>>>>>>> time, but I had to
    bodge in 2.2pF capacitor in parallel with the feedback >>>>>>>>>>>>>>>> resistor to kill
    the oscillation the 10pF produced.

    Yeah, sometimes electronics gets complicated.

    Regular opamps have about 1pF of input capacitance to ground. >>>>>>>>>>>>>
    Do you use opamps with a ground pin?

    Don't be silly. The ground reference is through the negative >>>>>>>>>>>> rail

    My favorite gumdrop opamp, OPA197, has a typ "common mode" >>>>>>>>>>>>> capacitance
    of 6.4 pF, whatever that means.

    https://www.ti.com/lit/ds/symlink/opa197.pdf?ts=1780716494386 >>>>>>>>>>>>
    It's on page 7 of the data sheet. I was more worried about the >>>>>>>>>>>> differential capacitance, which is 1.6pF for that part (and >>>>>>>>>>>> pretty
    typical). I could try to explain the difference between >>>>>>>>>>>> "differential"
    and "common mode" but if you haven't found out about that by >>>>>>>>>>>> now, you
    clearly aren't interested in finding out.

    Explain it to me. I'm not sure what the commmon-mode
    capacitance of an
    opamp is.

    Any explaination why the peaking in your circuit could be >>>>>>>>>>> blamed on
    differential capacitance and not care about common-mode >>>>>>>>>>> capacitance?


    As we?ve discussed before, the differential input capacitance >>>>>>>>>> of an op amp
    under bias is hard to measure, and the data sheet values are >>>>>>>>>> unreliable.

    The best way I know of is to put a very small pot directly in >>>>>>>>>> series with
    the inverting input and look at what happens to the phase margin. >>>>>>>>>>
    The CM capacitance you can get by doing the same on the
    noninverting input
    and looking at the bandwidth.˙ Feedback bootstraps out the >>>>>>>>>> differential
    capacitance at low frequency.

    Cheers

    Phil Hobbs

    I've seen the "common mode" capacitance defined as the C
    between one
    pin and the rails, and sometimes as the c of both pins in
    parellel to
    the world.

    A diagram of the several caps, with values, would help.

    One can Spice a standard inverting amp and see what it does, >>>>>>>>> assumuing
    the Spice model is accurate.

    It?s the measurement that?s difficult?if the amp is powered off, >>>>>>>> none of
    the junction capacitances will be right.

    Cheers

    Phil Hobbs

    I have a Spice model of the OPA197, basically TI's Pspice model
    converted for LT Spice.

    I made a unity-gain follower sim and drove that with a 1 volt step, >>>>>>> through a 1M resistor. The output is a nice exponential with tau = >>>>>>> 6.45 usec, which means the c to ground is 6.45 pF.

    The TI data sheet says that cm capacitance is 6.4!

    The differential input c disappeared because it's bootstrapped in a >>>>>>> follower.

    It doesn't. There's a collector/base or gate/drain capacitance
    that has
    to be charged up if the input moves vis-a-vis local ground (in
    this case
    the local rail voltages inside the chip). There are heroic
    measures that
    can minimise this - essentially floating the power rails though they >>>>>> move too slowly to be of all that much help - but regular followers >>>>>> don't use them.

    Imagine three caps.

    Don't bother.

    <snip>

    My sim measured only C2, because both C1 and C3 followed the input so >>>>> were bootstrapped out of existence.

    Whatever that is supposed to mean.

    <snip>

    Thanks, that makes sense, beforehand I too would have said it was C1+C2 >>>
    It's interesting, but one can just Spice actual circuits and see what
    happens. Understanding the capacitances helps make the initial opamp
    selections to sim.

    If the simulation is any good. The published simulation models are
    mostly behavioral, and precise enough for the purpose the marketing
    people had in mind.

    A frustrating thing is that the opamp manufacturer has an exceedingly
    accurate spice model of the part that their designers created in order
    to optimise and verify the design, but the company won't give that one
    to the public.

    It's "commercial in confidence" because it exposes a lot of the detailed design of the chip being simulated.


    The schematic in the datasheet is often drawn by marketing people who
    have never discussed it with the design engineers, let alone seen the
    real schematic, and is sometimes a source of great amusement to the
    actual designers.

    Commercial secrecy pretty much demands that.

    There are several commercial lab services that will take a competitor's
    chip that you obtained, (including mixed-signal designs much more
    complicated than an op-amp), and reverse engineer it for a smallish fee.
    They provide detailed schematics and layout. It is much cheaper than a
    mask set and well within the means of every competitor. It isn't usually
    that interesting except perhaps e.g. to see whether one's patent is
    being infringed.

    ˙The public spice model is quite
    possibly created in a similar manner, but possibly corrected based on
    some measurements by apps engineers or based on complaints from
    customers. Meanwhile the really accurate model sits on some internal
    server being ignored while the design engineers have moved on to some
    other product.

    It's not ignored - just too revealing to be made public.

    Keeping the best spice models secret from customers achieves little, as
    any competitor would already have full schematics if they wanted them.
    Perhaps the non-technical management and shareholders don't appreciate
    this, or don't appreciate the significant extra value to the customer of having a simulation model that is really accurate.



    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Monday, June 08, 2026 05:52:10
    On Mon, 8 Jun 2026 12:12:27 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    On 8/06/2026 2:04 am, john larkin wrote:
    On Sun, 7 Jun 2026 14:40:04 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 14:45:40 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 11:44 am, john larkin wrote:
    On Sun, 7 Jun 2026 00:31:01 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sat, 6 Jun 2026 20:41:07 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 03:06:10 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 2:33 am, john larkin wrote:
    On Sun, 7 Jun 2026 02:19:03 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 1:57 am, john larkin wrote:
    On Sun, 7 Jun 2026 01:10:57 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 6/06/2026 10:53 pm, john larkin wrote:
    On Sat, 6 Jun 2026 11:29:35 -0000 (UTC), piglet >>>>>>>>>>>>>>>> <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones >>>>>>>>>>>>>>>>>> <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY >>>>>>>>>>>>>>>>>>
    They changed the process on a part that's 47 years old. >>>>>>>>>>>>>>>>>>
    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    More than a process change, it is a whole different product. Old was NPN
    input stage, new is PNP inputs. Unforgivable to not amend the part number
    in any way.

    You'd better not buy TI parts any more.

    They were rarely anybody's first choice. Even when they came up with
    something neat they'd leave out a vital detail in the data sheet.
    They introduced a really nice MOSFET input op-amp and failed to mention
    in the data sheet that it had about 10pF input capacitance. For once I'd
    almost got a printed circuit layout that worked first time, but I had to
    bodge in 2.2pF capacitor in parallel with the feedback resistor to kill
    the oscillation the 10pF produced.

    Yeah, sometimes electronics gets complicated.

    Regular opamps have about 1pF of input capacitance to ground. >>>>>>>>>>>>
    Do you use opamps with a ground pin?

    Don't be silly. The ground reference is through the negative rail >>>>>>>>>>>
    My favorite gumdrop opamp, OPA197, has a typ "common mode" capacitance
    of 6.4 pF, whatever that means.

    https://www.ti.com/lit/ds/symlink/opa197.pdf?ts=1780716494386 >>>>>>>>>>>
    It's on page 7 of the data sheet. I was more worried about the >>>>>>>>>>> differential capacitance, which is 1.6pF for that part (and pretty >>>>>>>>>>> typical). I could try to explain the difference between "differential"
    and "common mode" but if you haven't found out about that by now, you
    clearly aren't interested in finding out.

    Explain it to me. I'm not sure what the commmon-mode capacitance of an
    opamp is.

    Any explaination why the peaking in your circuit could be blamed on >>>>>>>>>> differential capacitance and not care about common-mode capacitance? >>>>>>>>>>

    As we?ve discussed before, the differential input capacitance of an op amp
    under bias is hard to measure, and the data sheet values are unreliable.

    The best way I know of is to put a very small pot directly in series with
    the inverting input and look at what happens to the phase margin. >>>>>>>>>
    The CM capacitance you can get by doing the same on the noninverting input
    and looking at the bandwidth. Feedback bootstraps out the differential
    capacitance at low frequency.

    Cheers

    Phil Hobbs

    I've seen the "common mode" capacitance defined as the C between one >>>>>>>> pin and the rails, and sometimes as the c of both pins in parellel to >>>>>>>> the world.

    A diagram of the several caps, with values, would help.

    One can Spice a standard inverting amp and see what it does, assumuing >>>>>>>> the Spice model is accurate.

    It?s the measurement that?s difficult?if the amp is powered off, none of
    the junction capacitances will be right.

    Cheers

    Phil Hobbs

    I have a Spice model of the OPA197, basically TI's Pspice model
    converted for LT Spice.

    I made a unity-gain follower sim and drove that with a 1 volt step, >>>>>> through a 1M resistor. The output is a nice exponential with tau = >>>>>> 6.45 usec, which means the c to ground is 6.45 pF.

    The TI data sheet says that cm capacitance is 6.4!

    The differential input c disappeared because it's bootstrapped in a >>>>>> follower.

    It doesn't. There's a collector/base or gate/drain capacitance that has >>>>> to be charged up if the input moves vis-a-vis local ground (in this case >>>>> the local rail voltages inside the chip). There are heroic measures that >>>>> can minimise this - essentially floating the power rails though they >>>>> move too slowly to be of all that much help - but regular followers
    don't use them.

    Imagine three caps.

    C1 is inverting input to all the virtual grounds.

    C2 is n.i. input cap to ground

    C3 is between the two inputs.

    TI calls C1 the common-mode capacitance Zic

    They also call C2 the same thing.

    They call C3 the differential capacitance Zid.

    My sim measured only C2, because both C1 and C3 followed the input so
    were bootstrapped out of existence.

    C1 and C2 are each spec'd at 6.4 pF. I estmated 6.45 from my sim,
    eyeballing tau.

    OPA197 has a lots of protections and integral EMI filtering, which
    adds capacitance. Nice safe gumdrop. One can drive the inputs modestly >>>> past the rails and it doesn't go crazy. It makes a decent RRIO
    comparator too.

    Some people think the "common mode capacitance" is C1 + C2. TI
    doesn't.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    Thanks, that makes sense, beforehand I too would have said it was C1+C2

    It's interesting, but one can just Spice actual circuits and see what
    happens. Understanding the capacitances helps make the initial opamp
    selections to sim.


    A frustrating thing is that the opamp manufacturer has an exceedingly >accurate spice model of the part that their designers created in order
    to optimise and verify the design, but the company won't give that one
    to the public. The schematic in the datasheet is often drawn by
    marketing people who have never discussed it with the design engineers,
    let alone seen the real schematic, and is sometimes a source of great >amusement to the actual designers. The public spice model is quite
    possibly created in a similar manner, but possibly corrected based on
    some measurements by apps engineers or based on complaints from
    customers. Meanwhile the really accurate model sits on some internal
    server being ignored while the design engineers have moved on to some
    other product.




    The LT Spice library part models seem to be pretty good. They are
    behavioral models, and I assume that they have internal,
    semiconductor-level models, that run really slow.

    I found one LTC part that, with no power connected, would generate a
    teravolt on one of its pins. Free energy! Obviously they use ideal
    current sources in the public model.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Monday, June 08, 2026 23:31:47
    On 8/06/2026 9:38 pm, Chris Jones wrote:
    On 8/06/2026 3:36 pm, Bill Sloman wrote:
    On 8/06/2026 12:12 pm, Chris Jones wrote:
    On 8/06/2026 2:04 am, john larkin wrote:
    On Sun, 7 Jun 2026 14:40:04 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 14:45:40 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>> wrote:

    On 7/06/2026 11:44 am, john larkin wrote:
    On Sun, 7 Jun 2026 00:31:01 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sat, 6 Jun 2026 20:41:07 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 03:06:10 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 2:33 am, john larkin wrote:
    On Sun, 7 Jun 2026 02:19:03 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 1:57 am, john larkin wrote:
    On Sun, 7 Jun 2026 01:10:57 +1000, Bill Sloman >>>>>>>>>>>>>>>> <bill.sloman@ieee.org>
    wrote:

    On 6/06/2026 10:53 pm, john larkin wrote:
    On Sat, 6 Jun 2026 11:29:35 -0000 (UTC), piglet >>>>>>>>>>>>>>>>>> <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote: >>>>>>>>>>>>>>>>>>>> On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones >>>>>>>>>>>>>>>>>>>> <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY >>>>>>>>>>>>>>>>>>>>
    They changed the process on a part that's 47 years old. >>>>>>>>>>>>>>>>>>>>
    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center >>>>>>>>>>>>>>>>>>>> Lunatic Fringe Electronics


    More than a process change, it is a whole different >>>>>>>>>>>>>>>>>>> product. Old was NPN
    input stage, new is PNP inputs. Unforgivable to not >>>>>>>>>>>>>>>>>>> amend the part number
    in any way.

    You'd better not buy TI parts any more.

    They were rarely anybody's first choice. Even when they >>>>>>>>>>>>>>>>> came up with
    something neat they'd leave out a vital detail in the >>>>>>>>>>>>>>>>> data sheet.
    They introduced a really nice MOSFET input op-amp and >>>>>>>>>>>>>>>>> failed to mention
    in the data sheet that it had about 10pF input >>>>>>>>>>>>>>>>> capacitance. For once I'd
    almost got a printed circuit layout that worked first >>>>>>>>>>>>>>>>> time, but I had to
    bodge in 2.2pF capacitor in parallel with the feedback >>>>>>>>>>>>>>>>> resistor to kill
    the oscillation the 10pF produced.

    Yeah, sometimes electronics gets complicated.

    Regular opamps have about 1pF of input capacitance to >>>>>>>>>>>>>>> ground.

    Do you use opamps with a ground pin?

    Don't be silly. The ground reference is through the >>>>>>>>>>>>> negative rail

    My favorite gumdrop opamp, OPA197, has a typ "common mode" >>>>>>>>>>>>>> capacitance
    of 6.4 pF, whatever that means.

    https://www.ti.com/lit/ds/symlink/opa197.pdf?ts=1780716494386 >>>>>>>>>>>>>
    It's on page 7 of the data sheet. I was more worried about the >>>>>>>>>>>>> differential capacitance, which is 1.6pF for that part (and >>>>>>>>>>>>> pretty
    typical). I could try to explain the difference between >>>>>>>>>>>>> "differential"
    and "common mode" but if you haven't found out about that >>>>>>>>>>>>> by now, you
    clearly aren't interested in finding out.

    Explain it to me. I'm not sure what the commmon-mode
    capacitance of an
    opamp is.

    Any explaination why the peaking in your circuit could be >>>>>>>>>>>> blamed on
    differential capacitance and not care about common-mode >>>>>>>>>>>> capacitance?


    As we?ve discussed before, the differential input capacitance >>>>>>>>>>> of an op amp
    under bias is hard to measure, and the data sheet values are >>>>>>>>>>> unreliable.

    The best way I know of is to put a very small pot directly in >>>>>>>>>>> series with
    the inverting input and look at what happens to the phase >>>>>>>>>>> margin.

    The CM capacitance you can get by doing the same on the >>>>>>>>>>> noninverting input
    and looking at the bandwidth.˙ Feedback bootstraps out the >>>>>>>>>>> differential
    capacitance at low frequency.

    Cheers

    Phil Hobbs

    I've seen the "common mode" capacitance defined as the C
    between one
    pin and the rails, and sometimes as the c of both pins in >>>>>>>>>> parellel to
    the world.

    A diagram of the several caps, with values, would help.

    One can Spice a standard inverting amp and see what it does, >>>>>>>>>> assumuing
    the Spice model is accurate.

    It?s the measurement that?s difficult?if the amp is powered >>>>>>>>> off, none of
    the junction capacitances will be right.

    Cheers

    Phil Hobbs

    I have a Spice model of the OPA197, basically TI's Pspice model >>>>>>>> converted for LT Spice.

    I made a unity-gain follower sim and drove that with a 1 volt step, >>>>>>>> through a 1M resistor. The output is a nice exponential with tau = >>>>>>>> 6.45 usec, which means the c to ground is 6.45 pF.

    The TI data sheet says that cm capacitance is 6.4!

    The differential input c disappeared because it's bootstrapped in a >>>>>>>> follower.

    It doesn't. There's a collector/base or gate/drain capacitance
    that has
    to be charged up if the input moves vis-a-vis local ground (in
    this case
    the local rail voltages inside the chip). There are heroic
    measures that
    can minimise this - essentially floating the power rails though they >>>>>>> move too slowly to be of all that much help - but regular followers >>>>>>> don't use them.

    Imagine three caps.

    Don't bother.

    <snip>

    My sim measured only C2, because both C1 and C3 followed the input so >>>>>> were bootstrapped out of existence.

    Whatever that is supposed to mean.

    <snip>

    Thanks, that makes sense, beforehand I too would have said it was
    C1+C2

    It's interesting, but one can just Spice actual circuits and see what
    happens. Understanding the capacitances helps make the initial opamp
    selections to sim.

    If the simulation is any good. The published simulation models are
    mostly behavioral, and precise enough for the purpose the marketing
    people had in mind.

    A frustrating thing is that the opamp manufacturer has an exceedingly
    accurate spice model of the part that their designers created in
    order to optimise and verify the design, but the company won't give
    that one to the public.

    It's "commercial in confidence" because it exposes a lot of the
    detailed design of the chip being simulated.


    The schematic in the datasheet is often drawn by marketing people who
    have never discussed it with the design engineers, let alone seen the
    real schematic, and is sometimes a source of great amusement to the
    actual designers.

    Commercial secrecy pretty much demands that.

    There are several commercial lab services that will take a competitor's
    chip that you obtained, (including mixed-signal designs much more complicated than an op-amp), and reverse engineer it for a smallish fee. They provide detailed schematics and layout. It is much cheaper than a
    mask set and well within the means of every competitor. It isn't usually that interesting except perhaps e.g. to see whether one's patent is
    being infringed.

    A smallish fee isn't going to be all that small.

    ˙˙The public spice model is quite
    possibly created in a similar manner, but possibly corrected based on
    some measurements by apps engineers or based on complaints from
    customers. Meanwhile the really accurate model sits on some internal
    server being ignored while the design engineers have moved on to some
    other product.

    It's not ignored - just too revealing to be made public.

    Keeping the best spice models secret from customers achieves little, as
    any competitor would already have full schematics if they wanted them.

    If they wanted them badly enough. Reverse engineering may not be as
    expensive as a complete mask set, but it is quite expensive, and keeps
    fairly skilled people from your own firm busy for quite a while.

    I worked o voltage contrast for a bit, and the kind of electron
    microscope that can see what's going on on the exposed surface of an ude-encapsulated chip isn't cheap.

    Perhaps the non-technical management and shareholders don't appreciate
    this, or don't appreciate the significant extra value to the customer of having a simulation model that is really accurate.

    And really slow? Behavioral model are not only less revealing than
    transistor level models, but run a lot faster.

    --
    Bill Sloman, Sydney



    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Monday, June 08, 2026 23:41:24
    On 8/06/2026 10:52 pm, john larkin wrote:
    On Mon, 8 Jun 2026 12:12:27 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    On 8/06/2026 2:04 am, john larkin wrote:
    On Sun, 7 Jun 2026 14:40:04 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 14:45:40 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>> wrote:

    On 7/06/2026 11:44 am, john larkin wrote:
    On Sun, 7 Jun 2026 00:31:01 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sat, 6 Jun 2026 20:41:07 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 03:06:10 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 2:33 am, john larkin wrote:
    On Sun, 7 Jun 2026 02:19:03 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 1:57 am, john larkin wrote:
    On Sun, 7 Jun 2026 01:10:57 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 6/06/2026 10:53 pm, john larkin wrote:
    On Sat, 6 Jun 2026 11:29:35 -0000 (UTC), piglet >>>>>>>>>>>>>>>>> <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones >>>>>>>>>>>>>>>>>>> <lugnut808@spam.yahoo.com> wrote:


    <snip>

    Thanks, that makes sense, beforehand I too would have said it was C1+C2 >>>
    It's interesting, but one can just Spice actual circuits and see what
    happens. Understanding the capacitances helps make the initial opamp
    selections to sim.

    "Understanding" seems to be missing here.

    A frustrating thing is that the opamp manufacturer has an exceedingly
    accurate spice model of the part that their designers created in order
    to optimise and verify the design, but the company won't give that one
    to the public. The schematic in the datasheet is often drawn by
    marketing people who have never discussed it with the design engineers,
    let alone seen the real schematic, and is sometimes a source of great
    amusement to the actual designers. The public spice model is quite
    possibly created in a similar manner, but possibly corrected based on
    some measurements by apps engineers or based on complaints from
    customers. Meanwhile the really accurate model sits on some internal
    server being ignored while the design engineers have moved on to some
    other product.

    The LT Spice library part models seem to be pretty good. They are
    behavioral models, and I assume that they have internal,
    semiconductor-level models, that run really slow.

    Probably not true. I suspect that it is Laplace transforms all the way down.

    I found one LTC part that, with no power connected, would generate a
    teravolt on one of its pins. Free energy! Obviously they use ideal
    current sources in the public model.

    Crude mathematical models can generate large numbers if appropriately stimulated. Rationalising this as "ideal current sources" is imagining
    an unnecessary extra mechanism.

    --
    Bill Sloman, Sydney

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Monday, June 08, 2026 10:47:07
    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info
    on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick
    this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI
    never showed up, in the first place.

    If I hadn?t stopped talking audio design seriously in about 1980, I
    certainly would have when crappy compressed MP3s took over the world.

    Golden ears, my left buttock.

    The ears are close to the brain for a reason. Golden ears don't seem to
    be close to particularly good brains.

    I read a study that says that bats can correlate time between their
    ears with nanosecond resolution. Pretty good for wet stuff.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Phil Hobbs@3:633/10 to All on Monday, June 08, 2026 13:52:41
    On 2026-06-08 07:38, Chris Jones wrote:
    On 8/06/2026 3:36 pm, Bill Sloman wrote:
    On 8/06/2026 12:12 pm, Chris Jones wrote:
    On 8/06/2026 2:04 am, john larkin wrote:
    On Sun, 7 Jun 2026 14:40:04 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 14:45:40 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>> wrote:

    On 7/06/2026 11:44 am, john larkin wrote:
    On Sun, 7 Jun 2026 00:31:01 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sat, 6 Jun 2026 20:41:07 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 03:06:10 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 2:33 am, john larkin wrote:
    On Sun, 7 Jun 2026 02:19:03 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 1:57 am, john larkin wrote:
    On Sun, 7 Jun 2026 01:10:57 +1000, Bill Sloman >>>>>>>>>>>>>>>> <bill.sloman@ieee.org>
    wrote:

    On 6/06/2026 10:53 pm, john larkin wrote:
    On Sat, 6 Jun 2026 11:29:35 -0000 (UTC), piglet >>>>>>>>>>>>>>>>>> <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote: >>>>>>>>>>>>>>>>>>>> On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones >>>>>>>>>>>>>>>>>>>> <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY >>>>>>>>>>>>>>>>>>>>
    They changed the process on a part that's 47 years old. >>>>>>>>>>>>>>>>>>>>
    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center >>>>>>>>>>>>>>>>>>>> Lunatic Fringe Electronics


    More than a process change, it is a whole different >>>>>>>>>>>>>>>>>>> product. Old was NPN
    input stage, new is PNP inputs. Unforgivable to not >>>>>>>>>>>>>>>>>>> amend the part number
    in any way.

    You'd better not buy TI parts any more.

    They were rarely anybody's first choice. Even when they >>>>>>>>>>>>>>>>> came up with
    something neat they'd leave out a vital detail in the >>>>>>>>>>>>>>>>> data sheet.
    They introduced a really nice MOSFET input op-amp and >>>>>>>>>>>>>>>>> failed to mention
    in the data sheet that it had about 10pF input >>>>>>>>>>>>>>>>> capacitance. For once I'd
    almost got a printed circuit layout that worked first >>>>>>>>>>>>>>>>> time, but I had to
    bodge in 2.2pF capacitor in parallel with the feedback >>>>>>>>>>>>>>>>> resistor to kill
    the oscillation the 10pF produced.

    Yeah, sometimes electronics gets complicated.

    Regular opamps have about 1pF of input capacitance to >>>>>>>>>>>>>>> ground.

    Do you use opamps with a ground pin?

    Don't be silly. The ground reference is through the >>>>>>>>>>>>> negative rail

    My favorite gumdrop opamp, OPA197, has a typ "common mode" >>>>>>>>>>>>>> capacitance
    of 6.4 pF, whatever that means.

    https://www.ti.com/lit/ds/symlink/opa197.pdf?ts=1780716494386 >>>>>>>>>>>>>
    It's on page 7 of the data sheet. I was more worried about the >>>>>>>>>>>>> differential capacitance, which is 1.6pF for that part (and >>>>>>>>>>>>> pretty
    typical). I could try to explain the difference between >>>>>>>>>>>>> "differential"
    and "common mode" but if you haven't found out about that >>>>>>>>>>>>> by now, you
    clearly aren't interested in finding out.

    Explain it to me. I'm not sure what the commmon-mode
    capacitance of an
    opamp is.

    Any explaination why the peaking in your circuit could be >>>>>>>>>>>> blamed on
    differential capacitance and not care about common-mode >>>>>>>>>>>> capacitance?


    As we?ve discussed before, the differential input capacitance >>>>>>>>>>> of an op amp
    under bias is hard to measure, and the data sheet values are >>>>>>>>>>> unreliable.

    The best way I know of is to put a very small pot directly in >>>>>>>>>>> series with
    the inverting input and look at what happens to the phase >>>>>>>>>>> margin.

    The CM capacitance you can get by doing the same on the >>>>>>>>>>> noninverting input
    and looking at the bandwidth.˙ Feedback bootstraps out the >>>>>>>>>>> differential
    capacitance at low frequency.

    Cheers

    Phil Hobbs

    I've seen the "common mode" capacitance defined as the C
    between one
    pin and the rails, and sometimes as the c of both pins in >>>>>>>>>> parellel to
    the world.

    A diagram of the several caps, with values, would help.

    One can Spice a standard inverting amp and see what it does, >>>>>>>>>> assumuing
    the Spice model is accurate.

    It?s the measurement that?s difficult?if the amp is powered >>>>>>>>> off, none of
    the junction capacitances will be right.

    Cheers

    Phil Hobbs

    I have a Spice model of the OPA197, basically TI's Pspice model >>>>>>>> converted for LT Spice.

    I made a unity-gain follower sim and drove that with a 1 volt step, >>>>>>>> through a 1M resistor. The output is a nice exponential with tau = >>>>>>>> 6.45 usec, which means the c to ground is 6.45 pF.

    The TI data sheet says that cm capacitance is 6.4!

    The differential input c disappeared because it's bootstrapped in a >>>>>>>> follower.

    It doesn't. There's a collector/base or gate/drain capacitance
    that has
    to be charged up if the input moves vis-a-vis local ground (in
    this case
    the local rail voltages inside the chip). There are heroic
    measures that
    can minimise this - essentially floating the power rails though they >>>>>>> move too slowly to be of all that much help - but regular followers >>>>>>> don't use them.

    Imagine three caps.

    Don't bother.

    <snip>

    My sim measured only C2, because both C1 and C3 followed the input so >>>>>> were bootstrapped out of existence.

    Whatever that is supposed to mean.

    <snip>

    Thanks, that makes sense, beforehand I too would have said it was
    C1+C2

    It's interesting, but one can just Spice actual circuits and see what
    happens. Understanding the capacitances helps make the initial opamp
    selections to sim.

    If the simulation is any good. The published simulation models are
    mostly behavioral, and precise enough for the purpose the marketing
    people had in mind.

    A frustrating thing is that the opamp manufacturer has an exceedingly
    accurate spice model of the part that their designers created in
    order to optimise and verify the design, but the company won't give
    that one to the public.

    It's "commercial in confidence" because it exposes a lot of the
    detailed design of the chip being simulated.


    The schematic in the datasheet is often drawn by marketing people who
    have never discussed it with the design engineers, let alone seen the
    real schematic, and is sometimes a source of great amusement to the
    actual designers.

    Commercial secrecy pretty much demands that.

    There are several commercial lab services that will take a competitor's
    chip that you obtained, (including mixed-signal designs much more complicated than an op-amp), and reverse engineer it for a smallish fee. They provide detailed schematics and layout. It is much cheaper than a
    mask set and well within the means of every competitor. It isn't usually that interesting except perhaps e.g. to see whether one's patent is
    being infringed.

    ˙˙The public spice model is quite
    possibly created in a similar manner, but possibly corrected based on
    some measurements by apps engineers or based on complaints from
    customers. Meanwhile the really accurate model sits on some internal
    server being ignored while the design engineers have moved on to some
    other product.

    It's not ignored - just too revealing to be made public.

    Keeping the best spice models secret from customers achieves little, as
    any competitor would already have full schematics if they wanted them. Perhaps the non-technical management and shareholders don't appreciate
    this, or don't appreciate the significant extra value to the customer of having a simulation model that is really accurate.


    If they don't own the fab, there may well be NDA restrictions on the
    device models.

    Cheers

    Phil Hobbs

    --
    Dr Philip C D Hobbs
    Principal Consultant
    ElectroOptical Innovations LLC / Hobbs ElectroOptics
    Optics, Electro-optics, Photonics, Analog Electronics
    Briarcliff Manor NY 10510

    http://electrooptical.net
    http://hobbs-eo.com


    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Tuesday, June 09, 2026 12:39:22
    On 9/06/2026 3:47 am, john larkin wrote:
    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info
    on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick
    this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI
    never showed up, in the first place.

    If I hadn?t stopped talking audio design seriously in about 1980, I
    certainly would have when crappy compressed MP3s took over the world.

    Golden ears, my left buttock.

    The ears are close to the brain for a reason. Golden ears don't seem to
    be close to particularly good brains.

    I read a study that says that bats can correlate time between their
    ears with nanosecond resolution. Pretty good for wet stuff.

    Improbably good. I knew a psycho-acoustician who studied bats

    https://pubs.aip.org/asa/poma/article/19/1/050051/963723/Glenis-Long-s-contribution-to-animal

    and put together a bit of the electronics she used in her work in Germany. Nanosecond resolution isn't going to happen, even within a single nerve
    cell.

    --
    Bill Sloman, Sydney


    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Chris Jones@3:633/10 to All on Tuesday, June 09, 2026 23:39:35
    On 9/06/2026 3:52 am, Phil Hobbs wrote:
    On 2026-06-08 07:38, Chris Jones wrote:
    On 8/06/2026 3:36 pm, Bill Sloman wrote:
    On 8/06/2026 12:12 pm, Chris Jones wrote:
    On 8/06/2026 2:04 am, john larkin wrote:
    On Sun, 7 Jun 2026 14:40:04 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 14:45:40 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 11:44 am, john larkin wrote:
    On Sun, 7 Jun 2026 00:31:01 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sat, 6 Jun 2026 20:41:07 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 03:06:10 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 2:33 am, john larkin wrote:
    On Sun, 7 Jun 2026 02:19:03 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 1:57 am, john larkin wrote:
    On Sun, 7 Jun 2026 01:10:57 +1000, Bill Sloman >>>>>>>>>>>>>>>>> <bill.sloman@ieee.org>
    wrote:

    On 6/06/2026 10:53 pm, john larkin wrote: >>>>>>>>>>>>>>>>>>> On Sat, 6 Jun 2026 11:29:35 -0000 (UTC), piglet >>>>>>>>>>>>>>>>>>> <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote: >>>>>>>>>>>>>>>>>>>>> On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones >>>>>>>>>>>>>>>>>>>>> <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY >>>>>>>>>>>>>>>>>>>>>
    They changed the process on a part that's 47 years >>>>>>>>>>>>>>>>>>>>> old.

    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center >>>>>>>>>>>>>>>>>>>>> Lunatic Fringe Electronics


    More than a process change, it is a whole different >>>>>>>>>>>>>>>>>>>> product. Old was NPN
    input stage, new is PNP inputs. Unforgivable to not >>>>>>>>>>>>>>>>>>>> amend the part number
    in any way.

    You'd better not buy TI parts any more.

    They were rarely anybody's first choice. Even when >>>>>>>>>>>>>>>>>> they came up with
    something neat they'd leave out a vital detail in the >>>>>>>>>>>>>>>>>> data sheet.
    They introduced a really nice MOSFET input op-amp and >>>>>>>>>>>>>>>>>> failed to mention
    in the data sheet that it had about 10pF input >>>>>>>>>>>>>>>>>> capacitance. For once I'd
    almost got a printed circuit layout that worked first >>>>>>>>>>>>>>>>>> time, but I had to
    bodge in 2.2pF capacitor in parallel with the feedback >>>>>>>>>>>>>>>>>> resistor to kill
    the oscillation the 10pF produced.

    Yeah, sometimes electronics gets complicated. >>>>>>>>>>>>>>>>
    Regular opamps have about 1pF of input capacitance to >>>>>>>>>>>>>>>> ground.

    Do you use opamps with a ground pin?

    Don't be silly. The ground reference is through the >>>>>>>>>>>>>> negative rail

    My favorite gumdrop opamp, OPA197, has a typ "common >>>>>>>>>>>>>>> mode" capacitance
    of 6.4 pF, whatever that means.

    https://www.ti.com/lit/ds/symlink/opa197.pdf?ts=1780716494386 >>>>>>>>>>>>>>
    It's on page 7 of the data sheet. I was more worried about >>>>>>>>>>>>>> the
    differential capacitance, which is 1.6pF for that part >>>>>>>>>>>>>> (and pretty
    typical). I could try to explain the difference between >>>>>>>>>>>>>> "differential"
    and "common mode" but if you haven't found out about that >>>>>>>>>>>>>> by now, you
    clearly aren't interested in finding out.

    Explain it to me. I'm not sure what the commmon-mode >>>>>>>>>>>>> capacitance of an
    opamp is.

    Any explaination why the peaking in your circuit could be >>>>>>>>>>>>> blamed on
    differential capacitance and not care about common-mode >>>>>>>>>>>>> capacitance?


    As we?ve discussed before, the differential input
    capacitance of an op amp
    under bias is hard to measure, and the data sheet values are >>>>>>>>>>>> unreliable.

    The best way I know of is to put a very small pot directly >>>>>>>>>>>> in series with
    the inverting input and look at what happens to the phase >>>>>>>>>>>> margin.

    The CM capacitance you can get by doing the same on the >>>>>>>>>>>> noninverting input
    and looking at the bandwidth.˙ Feedback bootstraps out the >>>>>>>>>>>> differential
    capacitance at low frequency.

    Cheers

    Phil Hobbs

    I've seen the "common mode" capacitance defined as the C >>>>>>>>>>> between one
    pin and the rails, and sometimes as the c of both pins in >>>>>>>>>>> parellel to
    the world.

    A diagram of the several caps, with values, would help.

    One can Spice a standard inverting amp and see what it does, >>>>>>>>>>> assumuing
    the Spice model is accurate.

    It?s the measurement that?s difficult?if the amp is powered >>>>>>>>>> off, none of
    the junction capacitances will be right.

    Cheers

    Phil Hobbs

    I have a Spice model of the OPA197, basically TI's Pspice model >>>>>>>>> converted for LT Spice.

    I made a unity-gain follower sim and drove that with a 1 volt >>>>>>>>> step,
    through a 1M resistor. The output is a nice exponential with tau = >>>>>>>>> 6.45 usec, which means the c to ground is 6.45 pF.

    The TI data sheet says that cm capacitance is 6.4!

    The differential input c disappeared because it's bootstrapped >>>>>>>>> in a
    follower.

    It doesn't. There's a collector/base or gate/drain capacitance >>>>>>>> that has
    to be charged up if the input moves vis-a-vis local ground (in >>>>>>>> this case
    the local rail voltages inside the chip). There are heroic
    measures that
    can minimise this - essentially floating the power rails though >>>>>>>> they
    move too slowly to be of all that much help - but regular followers >>>>>>>> don't use them.

    Imagine three caps.

    Don't bother.

    <snip>

    My sim measured only C2, because both C1 and C3 followed the
    input so
    were bootstrapped out of existence.

    Whatever that is supposed to mean.

    <snip>

    Thanks, that makes sense, beforehand I too would have said it was >>>>>> C1+C2

    It's interesting, but one can just Spice actual circuits and see what >>>>> happens. Understanding the capacitances helps make the initial opamp >>>>> selections to sim.

    If the simulation is any good. The published simulation models are
    mostly behavioral, and precise enough for the purpose the marketing
    people had in mind.

    A frustrating thing is that the opamp manufacturer has an
    exceedingly accurate spice model of the part that their designers
    created in order to optimise and verify the design, but the company
    won't give that one to the public.

    It's "commercial in confidence" because it exposes a lot of the
    detailed design of the chip being simulated.


    The schematic in the datasheet is often drawn by marketing people
    who have never discussed it with the design engineers, let alone
    seen the real schematic, and is sometimes a source of great
    amusement to the actual designers.

    Commercial secrecy pretty much demands that.

    There are several commercial lab services that will take a
    competitor's chip that you obtained, (including mixed-signal designs
    much more complicated than an op-amp), and reverse engineer it for a
    smallish fee. They provide detailed schematics and layout. It is much
    cheaper than a mask set and well within the means of every competitor.
    It isn't usually that interesting except perhaps e.g. to see whether
    one's patent is being infringed.

    ˙˙The public spice model is quite
    possibly created in a similar manner, but possibly corrected based
    on some measurements by apps engineers or based on complaints from
    customers. Meanwhile the really accurate model sits on some internal
    server being ignored while the design engineers have moved on to
    some other product.

    It's not ignored - just too revealing to be made public.

    Keeping the best spice models secret from customers achieves little,
    as any competitor would already have full schematics if they wanted
    them. Perhaps the non-technical management and shareholders don't
    appreciate this, or don't appreciate the significant extra value to
    the customer of having a simulation model that is really accurate.


    If they don't own the fab, there may well be NDA restrictions on the
    device models.

    Good point. For most of the processes I used, we made the models,
    including some processes at external foundries. I expect this might no
    longer be so common, especially for foundry CMOS processes.




    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Chris Jones@3:633/10 to All on Wednesday, June 10, 2026 00:04:09
    On 8/06/2026 11:31 pm, Bill Sloman wrote:
    On 8/06/2026 9:38 pm, Chris Jones wrote:
    On 8/06/2026 3:36 pm, Bill Sloman wrote:
    On 8/06/2026 12:12 pm, Chris Jones wrote:
    On 8/06/2026 2:04 am, john larkin wrote:
    On Sun, 7 Jun 2026 14:40:04 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 14:45:40 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 11:44 am, john larkin wrote:
    On Sun, 7 Jun 2026 00:31:01 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sat, 6 Jun 2026 20:41:07 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 03:06:10 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 2:33 am, john larkin wrote:
    On Sun, 7 Jun 2026 02:19:03 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 1:57 am, john larkin wrote:
    On Sun, 7 Jun 2026 01:10:57 +1000, Bill Sloman >>>>>>>>>>>>>>>>> <bill.sloman@ieee.org>
    wrote:

    On 6/06/2026 10:53 pm, john larkin wrote: >>>>>>>>>>>>>>>>>>> On Sat, 6 Jun 2026 11:29:35 -0000 (UTC), piglet >>>>>>>>>>>>>>>>>>> <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote: >>>>>>>>>>>>>>>>>>>>> On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones >>>>>>>>>>>>>>>>>>>>> <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY >>>>>>>>>>>>>>>>>>>>>
    They changed the process on a part that's 47 years >>>>>>>>>>>>>>>>>>>>> old.

    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center >>>>>>>>>>>>>>>>>>>>> Lunatic Fringe Electronics


    More than a process change, it is a whole different >>>>>>>>>>>>>>>>>>>> product. Old was NPN
    input stage, new is PNP inputs. Unforgivable to not >>>>>>>>>>>>>>>>>>>> amend the part number
    in any way.

    You'd better not buy TI parts any more.

    They were rarely anybody's first choice. Even when >>>>>>>>>>>>>>>>>> they came up with
    something neat they'd leave out a vital detail in the >>>>>>>>>>>>>>>>>> data sheet.
    They introduced a really nice MOSFET input op-amp and >>>>>>>>>>>>>>>>>> failed to mention
    in the data sheet that it had about 10pF input >>>>>>>>>>>>>>>>>> capacitance. For once I'd
    almost got a printed circuit layout that worked first >>>>>>>>>>>>>>>>>> time, but I had to
    bodge in 2.2pF capacitor in parallel with the feedback >>>>>>>>>>>>>>>>>> resistor to kill
    the oscillation the 10pF produced.

    Yeah, sometimes electronics gets complicated. >>>>>>>>>>>>>>>>
    Regular opamps have about 1pF of input capacitance to >>>>>>>>>>>>>>>> ground.

    Do you use opamps with a ground pin?

    Don't be silly. The ground reference is through the >>>>>>>>>>>>>> negative rail

    My favorite gumdrop opamp, OPA197, has a typ "common >>>>>>>>>>>>>>> mode" capacitance
    of 6.4 pF, whatever that means.

    https://www.ti.com/lit/ds/symlink/opa197.pdf?ts=1780716494386 >>>>>>>>>>>>>>
    It's on page 7 of the data sheet. I was more worried about >>>>>>>>>>>>>> the
    differential capacitance, which is 1.6pF for that part >>>>>>>>>>>>>> (and pretty
    typical). I could try to explain the difference between >>>>>>>>>>>>>> "differential"
    and "common mode" but if you haven't found out about that >>>>>>>>>>>>>> by now, you
    clearly aren't interested in finding out.

    Explain it to me. I'm not sure what the commmon-mode >>>>>>>>>>>>> capacitance of an
    opamp is.

    Any explaination why the peaking in your circuit could be >>>>>>>>>>>>> blamed on
    differential capacitance and not care about common-mode >>>>>>>>>>>>> capacitance?


    As we?ve discussed before, the differential input
    capacitance of an op amp
    under bias is hard to measure, and the data sheet values are >>>>>>>>>>>> unreliable.

    The best way I know of is to put a very small pot directly >>>>>>>>>>>> in series with
    the inverting input and look at what happens to the phase >>>>>>>>>>>> margin.

    The CM capacitance you can get by doing the same on the >>>>>>>>>>>> noninverting input
    and looking at the bandwidth.˙ Feedback bootstraps out the >>>>>>>>>>>> differential
    capacitance at low frequency.

    Cheers

    Phil Hobbs

    I've seen the "common mode" capacitance defined as the C >>>>>>>>>>> between one
    pin and the rails, and sometimes as the c of both pins in >>>>>>>>>>> parellel to
    the world.

    A diagram of the several caps, with values, would help.

    One can Spice a standard inverting amp and see what it does, >>>>>>>>>>> assumuing
    the Spice model is accurate.

    It?s the measurement that?s difficult?if the amp is powered >>>>>>>>>> off, none of
    the junction capacitances will be right.

    Cheers

    Phil Hobbs

    I have a Spice model of the OPA197, basically TI's Pspice model >>>>>>>>> converted for LT Spice.

    I made a unity-gain follower sim and drove that with a 1 volt >>>>>>>>> step,
    through a 1M resistor. The output is a nice exponential with tau = >>>>>>>>> 6.45 usec, which means the c to ground is 6.45 pF.

    The TI data sheet says that cm capacitance is 6.4!

    The differential input c disappeared because it's bootstrapped >>>>>>>>> in a
    follower.

    It doesn't. There's a collector/base or gate/drain capacitance >>>>>>>> that has
    to be charged up if the input moves vis-a-vis local ground (in >>>>>>>> this case
    the local rail voltages inside the chip). There are heroic
    measures that
    can minimise this - essentially floating the power rails though >>>>>>>> they
    move too slowly to be of all that much help - but regular followers >>>>>>>> don't use them.

    Imagine three caps.

    Don't bother.

    <snip>

    My sim measured only C2, because both C1 and C3 followed the
    input so
    were bootstrapped out of existence.

    Whatever that is supposed to mean.

    <snip>

    Thanks, that makes sense, beforehand I too would have said it was >>>>>> C1+C2

    It's interesting, but one can just Spice actual circuits and see what >>>>> happens. Understanding the capacitances helps make the initial opamp >>>>> selections to sim.

    If the simulation is any good. The published simulation models are
    mostly behavioral, and precise enough for the purpose the marketing
    people had in mind.

    A frustrating thing is that the opamp manufacturer has an
    exceedingly accurate spice model of the part that their designers
    created in order to optimise and verify the design, but the company
    won't give that one to the public.

    It's "commercial in confidence" because it exposes a lot of the
    detailed design of the chip being simulated.


    The schematic in the datasheet is often drawn by marketing people
    who have never discussed it with the design engineers, let alone
    seen the real schematic, and is sometimes a source of great
    amusement to the actual designers.

    Commercial secrecy pretty much demands that.

    There are several commercial lab services that will take a
    competitor's chip that you obtained, (including mixed-signal designs
    much more complicated than an op-amp), and reverse engineer it for a
    smallish fee. They provide detailed schematics and layout. It is much
    cheaper than a mask set and well within the means of every competitor.
    It isn't usually that interesting except perhaps e.g. to see whether
    one's patent is being infringed.

    A smallish fee isn't going to be all that small.

    The person who arranged it said it was a few thousand. A mask set is
    maybe a hundred times that.

    ˙˙The public spice model is quite
    possibly created in a similar manner, but possibly corrected based
    on some measurements by apps engineers or based on complaints from
    customers. Meanwhile the really accurate model sits on some internal
    server being ignored while the design engineers have moved on to
    some other product.

    It's not ignored - just too revealing to be made public.

    Keeping the best spice models secret from customers achieves little,
    as any competitor would already have full schematics if they wanted them.

    If they wanted them badly enough. Reverse engineering may not be as expensive as a complete mask set, but it is quite expensive, and keeps fairly skilled people from your own firm busy for quite a while.

    No, just pay someone to do it. But, it's not all that useful if you
    intend to make something much better than what your competitors already
    make.


    I worked o voltage contrast for a bit, and the kind of electron
    microscope that can see what's going on on the exposed surface of an ude-encapsulated chip isn't cheap.

    I think at least some of those reverse engineering companies are run out
    of university labs. They already have the equipment and it's not always
    busy. The service I know of did not operate the chip, they just took
    images and made netlists / schematics, and measured the process parameters.

    Perhaps the non-technical management and shareholders don't appreciate
    this, or don't appreciate the significant extra value to the customer
    of having a simulation model that is really accurate.

    And really slow? Behavioral model are not only less revealing than transistor level models, but run a lot faster.

    It is good to have both. My block on one chip simulated 1e12 times
    slower than real time, but that had many thousands of transistors in it,
    and computers have got faster over the 20 years since then. I did have
    to simulate the whole real circuit for one beat period of a two-tone distortion test, and running all the process corners and temperatures
    did take many days, but I also made a fast behavioural model to make
    sure that the digital state machine could calibrate the analogue part
    properly etc.



    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Wednesday, June 10, 2026 00:35:16
    On 10/06/2026 12:04 am, Chris Jones wrote:
    On 8/06/2026 11:31 pm, Bill Sloman wrote:
    On 8/06/2026 9:38 pm, Chris Jones wrote:
    On 8/06/2026 3:36 pm, Bill Sloman wrote:
    On 8/06/2026 12:12 pm, Chris Jones wrote:
    On 8/06/2026 2:04 am, john larkin wrote:
    On Sun, 7 Jun 2026 14:40:04 -0000 (UTC), piglet
    <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 14:45:40 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 11:44 am, john larkin wrote:
    On Sun, 7 Jun 2026 00:31:01 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sat, 6 Jun 2026 20:41:07 -0000 (UTC), Phil Hobbs
    <pcdhSpamMeSenseless@electrooptical.net> wrote:

    john larkin <jl@glen--canyon.com> wrote:
    On Sun, 7 Jun 2026 03:06:10 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 2:33 am, john larkin wrote:
    On Sun, 7 Jun 2026 02:19:03 +1000, Bill Sloman >>>>>>>>>>>>>>>> <bill.sloman@ieee.org>
    wrote:

    On 7/06/2026 1:57 am, john larkin wrote:
    On Sun, 7 Jun 2026 01:10:57 +1000, Bill Sloman >>>>>>>>>>>>>>>>>> <bill.sloman@ieee.org>
    wrote:

    On 6/06/2026 10:53 pm, john larkin wrote: >>>>>>>>>>>>>>>>>>>> On Sat, 6 Jun 2026 11:29:35 -0000 (UTC), piglet >>>>>>>>>>>>>>>>>>>> <erichpwagner@hotmail.com> wrote:

    john larkin <jl@glen--canyon.com> wrote: >>>>>>>>>>>>>>>>>>>>>> On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones >>>>>>>>>>>>>>>>>>>>>> <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY >>>>>>>>>>>>>>>>>>>>>>
    They changed the process on a part that's 47 years >>>>>>>>>>>>>>>>>>>>>> old.

    Scandalous.


    John Larkin
    Highland Tech Glen Canyon Design Center >>>>>>>>>>>>>>>>>>>>>> Lunatic Fringe Electronics


    More than a process change, it is a whole different >>>>>>>>>>>>>>>>>>>>> product. Old was NPN
    input stage, new is PNP inputs. Unforgivable to not >>>>>>>>>>>>>>>>>>>>> amend the part number
    in any way.

    You'd better not buy TI parts any more. >>>>>>>>>>>>>>>>>>>
    They were rarely anybody's first choice. Even when >>>>>>>>>>>>>>>>>>> they came up with
    something neat they'd leave out a vital detail in the >>>>>>>>>>>>>>>>>>> data sheet.
    They introduced a really nice MOSFET input op-amp and >>>>>>>>>>>>>>>>>>> failed to mention
    in the data sheet that it had about 10pF input >>>>>>>>>>>>>>>>>>> capacitance. For once I'd
    almost got a printed circuit layout that worked first >>>>>>>>>>>>>>>>>>> time, but I had to
    bodge in 2.2pF capacitor in parallel with the >>>>>>>>>>>>>>>>>>> feedback resistor to kill
    the oscillation the 10pF produced.

    Yeah, sometimes electronics gets complicated. >>>>>>>>>>>>>>>>>
    Regular opamps have about 1pF of input capacitance to >>>>>>>>>>>>>>>>> ground.

    Do you use opamps with a ground pin?

    Don't be silly. The ground reference is through the >>>>>>>>>>>>>>> negative rail

    My favorite gumdrop opamp, OPA197, has a typ "common >>>>>>>>>>>>>>>> mode" capacitance
    of 6.4 pF, whatever that means.

    https://www.ti.com/lit/ds/symlink/opa197.pdf?ts=1780716494386 >>>>>>>>>>>>>>>
    It's on page 7 of the data sheet. I was more worried >>>>>>>>>>>>>>> about the
    differential capacitance, which is 1.6pF for that part >>>>>>>>>>>>>>> (and pretty
    typical). I could try to explain the difference between >>>>>>>>>>>>>>> "differential"
    and "common mode" but if you haven't found out about that >>>>>>>>>>>>>>> by now, you
    clearly aren't interested in finding out.

    Explain it to me. I'm not sure what the commmon-mode >>>>>>>>>>>>>> capacitance of an
    opamp is.

    Any explaination why the peaking in your circuit could be >>>>>>>>>>>>>> blamed on
    differential capacitance and not care about common-mode >>>>>>>>>>>>>> capacitance?


    As we?ve discussed before, the differential input
    capacitance of an op amp
    under bias is hard to measure, and the data sheet values >>>>>>>>>>>>> are unreliable.

    The best way I know of is to put a very small pot directly >>>>>>>>>>>>> in series with
    the inverting input and look at what happens to the phase >>>>>>>>>>>>> margin.

    The CM capacitance you can get by doing the same on the >>>>>>>>>>>>> noninverting input
    and looking at the bandwidth.˙ Feedback bootstraps out the >>>>>>>>>>>>> differential
    capacitance at low frequency.

    Cheers

    Phil Hobbs

    I've seen the "common mode" capacitance defined as the C >>>>>>>>>>>> between one
    pin and the rails, and sometimes as the c of both pins in >>>>>>>>>>>> parellel to
    the world.

    A diagram of the several caps, with values, would help. >>>>>>>>>>>>
    One can Spice a standard inverting amp and see what it does, >>>>>>>>>>>> assumuing
    the Spice model is accurate.

    It?s the measurement that?s difficult?if the amp is powered >>>>>>>>>>> off, none of
    the junction capacitances will be right.

    Cheers

    Phil Hobbs

    I have a Spice model of the OPA197, basically TI's Pspice model >>>>>>>>>> converted for LT Spice.

    I made a unity-gain follower sim and drove that with a 1 volt >>>>>>>>>> step,
    through a 1M resistor. The output is a nice exponential with >>>>>>>>>> tau =
    6.45 usec, which means the c to ground is 6.45 pF.

    The TI data sheet says that cm capacitance is 6.4!

    The differential input c disappeared because it's bootstrapped >>>>>>>>>> in a
    follower.

    It doesn't. There's a collector/base or gate/drain capacitance >>>>>>>>> that has
    to be charged up if the input moves vis-a-vis local ground (in >>>>>>>>> this case
    the local rail voltages inside the chip). There are heroic
    measures that
    can minimise this - essentially floating the power rails though >>>>>>>>> they
    move too slowly to be of all that much help - but regular
    followers
    don't use them.

    Imagine three caps.

    Don't bother.

    <snip>

    My sim measured only C2, because both C1 and C3 followed the
    input so
    were bootstrapped out of existence.

    Whatever that is supposed to mean.

    <snip>

    Thanks, that makes sense, beforehand I too would have said it was >>>>>>> C1+C2

    It's interesting, but one can just Spice actual circuits and see what >>>>>> happens. Understanding the capacitances helps make the initial opamp >>>>>> selections to sim.

    If the simulation is any good. The published simulation models are
    mostly behavioral, and precise enough for the purpose the marketing
    people had in mind.

    A frustrating thing is that the opamp manufacturer has an
    exceedingly accurate spice model of the part that their designers
    created in order to optimise and verify the design, but the company >>>>> won't give that one to the public.

    It's "commercial in confidence" because it exposes a lot of the
    detailed design of the chip being simulated.


    The schematic in the datasheet is often drawn by marketing people
    who have never discussed it with the design engineers, let alone
    seen the real schematic, and is sometimes a source of great
    amusement to the actual designers.

    Commercial secrecy pretty much demands that.

    There are several commercial lab services that will take a
    competitor's chip that you obtained, (including mixed-signal designs
    much more complicated than an op-amp), and reverse engineer it for a
    smallish fee. They provide detailed schematics and layout. It is much
    cheaper than a mask set and well within the means of every
    competitor. It isn't usually that interesting except perhaps e.g. to
    see whether one's patent is being infringed.

    A smallish fee isn't going to be all that small.

    The person who arranged it said it was a few thousand. A mask set is
    maybe a hundred times that.

    ˙˙The public spice model is quite
    possibly created in a similar manner, but possibly corrected based
    on some measurements by apps engineers or based on complaints from
    customers. Meanwhile the really accurate model sits on some
    internal server being ignored while the design engineers have moved >>>>> on to some other product.

    It's not ignored - just too revealing to be made public.

    Keeping the best spice models secret from customers achieves little,
    as any competitor would already have full schematics if they wanted
    them.

    If they wanted them badly enough. Reverse engineering may not be as
    expensive as a complete mask set, but it is quite expensive, and keeps
    fairly skilled people from your own firm busy for quite a while.

    No, just pay someone to do it. But, it's not all that useful if you
    intend to make something much better than what your competitors already make.

    It's never just "paying somebody to do it". You've got to spend time in
    house making sense of the results. And making something much better than
    your competitors already usually depends on knowing why they are as good
    as they are

    I worked o voltage contrast for a bit, and the kind of electron
    microscope that can see what's going on on the exposed surface of an
    de-encapsulated chip isn't cheap.

    I think at least some of those reverse engineering companies are run out
    of university labs. They already have the equipment and it's not always busy. The service I know of did not operate the chip, they just took
    images and made netlists / schematics, and measured the process parameters.

    Modern chips have several layers of metalisation. "Taking images" can
    involve taking off a layer or two of metalisation to expose what's
    underneath. University labs aren't always as well equipped or as
    well-informed as they like to think. They have just as many pretentious wankers as every other organisation - perhaps more since their stock in
    trade is presenting stuff at conferences.

    Perhaps the non-technical management and shareholders don't
    appreciate this, or don't appreciate the significant extra value to
    the customer of having a simulation model that is really accurate.

    And really slow? Behavioral model are not only less revealing than
    transistor level models, but run a lot faster.

    It is good to have both.

    Circuit designers don't really care what's going on inside the chip. A behavioral model is usually perfectly adequate.

    My block on one chip simulated 1e12 times
    slower than real time, but that had many thousands of transistors in it,
    and computers have got faster over the 20 years since then.

    Much of the progress has come from putting lots of processors in parallel.

    I did have
    to simulate the whole real circuit for one beat period of a two-tone distortion test, and running all the process corners and temperatures
    did take many days, but I also made a fast behavioural model to make
    sure that the digital state machine could calibrate the analogue part properly etc.

    That's process validation rather than circuit design.

    --
    Bill Sloman, Sydney



    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From joegwinn@3:633/10 to All on Tuesday, June 09, 2026 12:16:26
    On Mon, 08 Jun 2026 10:47:07 -0700, john larkin <jl@glen--canyon.com>
    wrote:

    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info
    on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick
    this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI
    never showed up, in the first place.

    If I hadn?t stopped talking audio design seriously in about 1980, I
    certainly would have when crappy compressed MP3s took over the world.

    Golden ears, my left buttock.

    The ears are close to the brain for a reason. Golden ears don't seem to
    be close to particularly good brains.

    I read a study that says that bats can correlate time between their
    ears with nanosecond resolution. Pretty good for wet stuff.

    Bats are pretty good, but that seems a bit too good. Can you find
    that study?

    Thanks,

    Joe

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Tuesday, June 09, 2026 09:44:55
    On Tue, 09 Jun 2026 12:16:26 -0400, joegwinn@comcast.net wrote:

    On Mon, 08 Jun 2026 10:47:07 -0700, john larkin <jl@glen--canyon.com>
    wrote:

    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org> >>wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info
    on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick
    this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI
    never showed up, in the first place.

    If I hadn?t stopped talking audio design seriously in about 1980, I
    certainly would have when crappy compressed MP3s took over the world. >>>>>
    Golden ears, my left buttock.

    The ears are close to the brain for a reason. Golden ears don't seem to >>>be close to particularly good brains.

    I read a study that says that bats can correlate time between their
    ears with nanosecond resolution. Pretty good for wet stuff.

    Bats are pretty good, but that seems a bit too good. Can you find
    that study?

    Thanks,

    Joe

    Good grief, just google

    bat echolocation nanosecond

    The history of science is rich with people saying "that's not
    possible" when it turns out to be.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From John R Walliker@3:633/10 to All on Tuesday, June 09, 2026 18:27:54
    On 09/06/2026 17:44, john larkin wrote:
    On Tue, 09 Jun 2026 12:16:26 -0400, joegwinn@comcast.net wrote:

    On Mon, 08 Jun 2026 10:47:07 -0700, john larkin <jl@glen--canyon.com>
    wrote:

    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info
    on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick
    this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI
    never showed up, in the first place.

    If I hadn?t stopped talking audio design seriously in about 1980, I >>>>>> certainly would have when crappy compressed MP3s took over the world. >>>>>>
    Golden ears, my left buttock.

    The ears are close to the brain for a reason. Golden ears don't seem to >>>> be close to particularly good brains.

    I read a study that says that bats can correlate time between their
    ears with nanosecond resolution. Pretty good for wet stuff.

    Bats are pretty good, but that seems a bit too good. Can you find
    that study?

    Thanks,

    Joe

    Good grief, just google

    bat echolocation nanosecond

    The history of science is rich with people saying "that's not
    possible" when it turns out to be.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    Google finds claims of as low as 10ns, but I have not yet
    found an original reference for such small time intervals.
    On the other hand, the abstract of this paper claims
    500ns which is a bit easier to believe.

    Perception of Echo Phase Information in Bat Sonar
    James A. Simmons
    Science 22 Jun 1979 Vol 204, Issue 4399 pp. 1336-1338
    Echolocating bats (Eptesicus fuscus) can detect changes
    as small as 500 nanoseconds in the arrival time of sonar
    echoes when these changes appear as jitter or alternations
    in arrival time from one echo to the next.

    John



    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From joegwinn@3:633/10 to All on Tuesday, June 09, 2026 16:22:55
    On Tue, 09 Jun 2026 09:44:55 -0700, john larkin <jl@glen--canyon.com>
    wrote:

    On Tue, 09 Jun 2026 12:16:26 -0400, joegwinn@comcast.net wrote:

    On Mon, 08 Jun 2026 10:47:07 -0700, john larkin <jl@glen--canyon.com> >>wrote:

    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org> >>>wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info
    on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick
    this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI
    never showed up, in the first place.

    If I hadn?t stopped talking audio design seriously in about 1980, I >>>>>> certainly would have when crappy compressed MP3s took over the world. >>>>>>
    Golden ears, my left buttock.

    The ears are close to the brain for a reason. Golden ears don't seem to >>>>be close to particularly good brains.

    I read a study that says that bats can correlate time between their
    ears with nanosecond resolution. Pretty good for wet stuff.

    Bats are pretty good, but that seems a bit too good. Can you find
    that study?

    Thanks,

    Joe

    Good grief, just google

    bat echolocation nanosecond

    And hear a lot of unsupported opinion. Like all that nonsense on
    circuit design.

    I studied bat sonar quite intently at least 20 years ago, and saw that
    bat sonar was very good at finding moths on the wing. Some bats used
    CW (good for detecting moths hiding in vegetation) and Chirp FM (good
    for moths out in the open), anticipating human designed radar and
    sonar by a hundred million years or so. But as others have said this
    did not require nanoseconds, and I don't recall such numbers.

    It did use correlation, but in a neural map that was spread out on a
    2D sheet, a tectum like those in the visual system.

    I have a thick folder on this somewhere.


    The history of science is rich with people saying "that's not
    possible" when it turns out to be.

    Oh absolutely. Biology will find a way to achieve dinner, at least on
    average.

    Joe


    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Jeff Liebermann@3:633/10 to All on Tuesday, June 09, 2026 16:15:44
    On Tue, 09 Jun 2026 12:16:26 -0400, joegwinn@comcast.net wrote:

    On Mon, 08 Jun 2026 10:47:07 -0700, john larkin <jl@glen--canyon.com>
    wrote:

    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org> >>wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info
    on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick
    this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI
    never showed up, in the first place.

    If I hadn?t stopped talking audio design seriously in about 1980, I
    certainly would have when crappy compressed MP3s took over the world. >>>>>
    Golden ears, my left buttock.

    The ears are close to the brain for a reason. Golden ears don't seem to >>>be close to particularly good brains.

    I read a study that says that bats can correlate time between their
    ears with nanosecond resolution. Pretty good for wet stuff.

    Bats are pretty good, but that seems a bit too good. Can you find
    that study?

    "The transfer function of a target limits the jitter detection
    threshold with signals of echolocating FM-bats" <https://pubmed.ncbi.nlm.nih.gov/16395614/>
    "Some investigators have obtained results indicating that bats are
    able to discriminate alternations in delay down to 10 ns, which
    appears incredible for purely physical reasons."

    "Bat sonar: an alternative interpretation of the 10-ns jitter result" <https://pubmed.ncbi.nlm.nih.gov/9528108/>
    "In 1990 Simmons et al. reported evidence of a time resolution
    hitherto unknown in any animal, namely a 10-ns jitter detection
    threshold in echolocating bats."

    Google Scholar produces additional papers on bat echolocation acuity: <https://scholar.google.com/scholar?q=bat%20echolocation%2010%20nsec>


    --
    Jeff Liebermann jeffl@cruzio.com
    PO Box 272 http://www.LearnByDestroying.com
    Ben Lomond CA 95005-0272 AE6KS 831-336-2558


    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Wednesday, June 10, 2026 12:29:23
    On 10/06/2026 2:44 am, john larkin wrote:
    On Tue, 09 Jun 2026 12:16:26 -0400, joegwinn@comcast.net wrote:

    On Mon, 08 Jun 2026 10:47:07 -0700, john larkin <jl@glen--canyon.com>
    wrote:

    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info
    on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick
    this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI
    never showed up, in the first place.

    If I hadn?t stopped talking audio design seriously in about 1980, I >>>>>> certainly would have when crappy compressed MP3s took over the world. >>>>>>
    Golden ears, my left buttock.

    The ears are close to the brain for a reason. Golden ears don't seem to >>>> be close to particularly good brains.

    I read a study that says that bats can correlate time between their
    ears with nanosecond resolution. Pretty good for wet stuff.

    Bats are pretty good, but that seems a bit too good. Can you find
    that study?

    Thanks,

    Joe

    Good grief, just google

    bat echolocation nanosecond

    You made the claim, you do the googling.

    The history of science is rich with people saying "that's not
    possible" when it turns out to be.

    It's even richer with people saying "that's not possible" and turning
    out to be right.

    Jeff Liebermann dug out the example.

    "Bat sonar: an alternative interpretation of the 10-ns jitter result" <https://pubmed.ncbi.nlm.nih.gov/9528108/>
    "In 1990 Simmons et al. reported evidence of a time resolution
    hitherto unknown in any animal, namely a 10-ns jitter detection
    threshold in echolocating bats."

    You do seem to be hell-bent on maintaining your reputation as a gullible
    twit.

    --
    Bill Sloman, Sydney



    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Jan Panteltje@3:633/10 to All on Wednesday, June 10, 2026 06:22:58
    john larkin <jl@glen--canyon.com>wrote:
    Good grief, just google

    bat echolocation nanosecond

    The history of science is rich with people saying "that's not
    possible" when it turns out to be.

    FYI:
    Speed of sound is 340.29 m / s

    In a nano-second sound moves:
    340.29 * 10^-9 = 3.4029e-07 meter
    or 3.4029e-07 * 1000 = 0.00034029 milimeter
    Even a 1 degree phase shift is 1/360 so about 0.000001 mm,
    distance between 2 neurons.. hairs in the ear?

    Not even counting <MAKING the sound.
    Beep!


    You can express Any Sing in nano seconds
    !!!

    BTW the signal from the nerves in the ear to the brain takes orders of magnitude more time

    Drop your nano nano obsession!!!

    Did you not got hit by crocodile sounds once?
    There is a survival series here on TV every sunday .. those guys catch alligators with a hook and same bait.
    I now know how to catch and kill an alligator!

    Done ANYTHING with sound ever?

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Wednesday, June 10, 2026 06:20:36
    On Wed, 10 Jun 2026 06:22:58 GMT, Jan Panteltje <alien@comet.invalid>
    wrote:

    john larkin <jl@glen--canyon.com>wrote:
    Good grief, just google

    bat echolocation nanosecond

    The history of science is rich with people saying "that's not
    possible" when it turns out to be.

    FYI:
    Speed of sound is 340.29 m / s

    In a nano-second sound moves:
    340.29 * 10^-9 = 3.4029e-07 meter
    or 3.4029e-07 * 1000 = 0.00034029 milimeter
    Even a 1 degree phase shift is 1/360 so about 0.000001 mm,
    distance between 2 neurons.. hairs in the ear?

    Not even counting <MAKING the sound.
    Beep!


    You can express Any Sing in nano seconds
    !!!

    I use nanoseconds (or pico of femto) to describe anything below a
    microsecond. I do have old books that use millimicrosecond units, or micromicrofarad, uuF.


    BTW the signal from the nerves in the ear to the brain takes orders of magnitude more time

    The prop delay between your wrist and your brain obviously makes it
    impossible to play tennis.

    My favorite expert-impossible was fathead boffins declaring that a
    biological rotating motor was impossible. I think there is one that
    runs something like 100K RPM. We would not have babies without a
    spinning molecular machine.


    Drop your nano nano obsession!!!

    Did you not got hit by crocodile sounds once?

    We helped discover some infrasonic croc calls, yes.

    There is a survival series here on TV every sunday .. those guys catch alligators with a hook and same bait.
    I now know how to catch and kill an alligator!

    Done ANYTHING with sound ever?

    I designed a guitar amp once, the Ryder 200 or 500 or something. Named
    after a buddy, Frank Ryder. He wised up and married a rich German
    girl and got out of audio.

    And of course I designed the things that found the alligator calls in Mississippi.

    Oh, and the paging system for the New York City subway. Not very
    hi-fi.

    I don't like music and audio is boring and low profit, so I prefer
    picosecond stuff.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Jan Panteltje@3:633/10 to All on Wednesday, June 10, 2026 14:21:31
    john larkin <jl@glen--canyon.com>wrote:
    On Wed, 10 Jun 2026 06:22:58 GMT, Jan Panteltje <alien@comet.invalid>
    wrote:

    john larkin <jl@glen--canyon.com>wrote:
    Good grief, just google

    bat echolocation nanosecond

    The history of science is rich with people saying "that's not
    possible" when it turns out to be.

    FYI:
    Speed of sound is 340.29 m / s

    In a nano-second sound moves:
    340.29 * 10^-9 = 3.4029e-07 meter
    or 3.4029e-07 * 1000 = 0.00034029 milimeter
    Even a 1 degree phase shift is 1/360 so about 0.000001 mm,
    distance between 2 neurons.. hairs in the ear?

    Not even counting <MAKING the sound.
    Beep!


    You can express Any Sing in nano seconds
    !!!

    I use nanoseconds (or pico of femto) to describe anything below a >microsecond. I do have old books that use millimicrosecond units, or >micromicrofarad, uuF.


    BTW the signal from the nerves in the ear to the brain takes orders of magnitude more time

    The prop delay between your wrist and your brain obviously makes it >impossible to play tennis.

    Why? those balls do not fly FTL or even faster then sound!
    I cannot play tennis anyways...
    Football: yes, been a long time though.
    Hockey in school days
    And Chess too.
    Won from a local champ once, that really pissed him off.




    My favorite expert-impossible was fathead boffins declaring that a
    biological rotating motor was impossible. I think there is one that
    runs something like 100K RPM. We would not have babies without a
    spinning molecular machine.

    Nature has a lot we still need to discover.
    Will the next generations come from a tube?
    Or just be computer chips and no more humans?
    Or use a 'Design you own kid' Walmart box?


    Drop your nano nano obsession!!!

    Did you not got hit by crocodile sounds once?

    We helped discover some infrasonic croc calls, yes.

    There is a survival series here on TV every sunday .. those guys catch alligators with a hook and same bait.
    I now know how to catch and kill an alligator!

    Done ANYTHING with sound ever?

    I designed a guitar amp once, the Ryder 200 or 500 or something. Named
    after a buddy, Frank Ryder. He wised up and married a rich German
    girl and got out of audio.


    I designed a (tube in those dayhs) guitar audio amp for the school band, they liked it.
    Later I got contacted by one of the players, he wanted special effect stuff too.

    Build nice 3055 amps too for at home, and then when in broadcasting designed some audio stuff.
    It is quite something to get audio right with all those bands and artists
    no errors allowed.
    We did film stuff too.
    Relayed Euro Vision songfestival, head control room.
    No errors allowed.
    Moonlandings the same
    politicians..
    what not.


    And of course I designed the things that found the alligator calls in >Mississippi.

    Oh, and the paging system for the New York City subway. Not very
    hi-fi.

    Impressive.


    I don't like music and audio is boring and low profit, so I prefer
    picosecond stuff.

    Well 'no profit' the Beatles were one of my favorite groups, they did get very rich I think?
    Bob Dylan music I still have (now in mp3 ;-)), he got a Nobel prize for his music.

    I like music, was just listening to 'I Will Always Love You' by Whitney Houston
    https://www.youtube.com/watch?v=OTJtq2DGGk8
    There are some satellite channels here that play old hits all day long, a channel for the seventies, one for the nineties, one for rock, there are more.
    Sometimes I press the 'record' button on the remote if I like it.

    As to sound and ultrasound:
    I have published lots of stuff in this newsgroup over the years.
    https://panteltje.nl/pub/wind_speed_by_differential_2_ebay_distance_meters_IMG_4891.JPG
    https://panteltje.nl/pub/ultrasonic_anti_fouling_test_board_IMG_5135.JPG

    From satellite:
    raspberrypi: ~ # mediainfo "/mnt/sda2/video/satellite_4/you're.so.vain.ts"

    General
    ID : 2112 (0x840)
    Complete name : /mnt/sda2/video/satellite_4/you're.so.vain.ts
    Format : MPEG-TS
    File size : 10.9 MiB
    Duration : 1 min 2 s
    Overall bit rate mode : Variable
    Overall bit rate : 1 456 kb/s

    Video
    ID : 2352 (0x930)
    Menu ID : 55207 (0xD7A7)
    Format : MPEG Video
    Format version : Version 2
    Format profile : Main@Main
    Format settings : CustomMatrix / BVOP
    Format settings, BVOP : Yes
    Format settings, Matrix : Custom
    Format settings, GOP : Variable
    Format settings, picture structure : Frame
    Codec ID : 2
    Duration : 1 min 2 s
    Bit rate mode : Variable
    Bit rate : 1 190 kb/s
    Maximum bit rate : 2 049 kb/s
    Width : 544 pixels
    Height : 576 pixels
    Display aspect ratio : 16:9
    Frame rate : 25.000 FPS
    Standard : Component
    Color space : YUV
    Chroma subsampling : 4:2:0
    Bit depth : 8 bits
    Scan type : Interlaced
    Scan order : Top Field First
    Compression mode : Lossy
    Bits/(Pixel*Frame) : 0.152
    Stream size : 8.82 MiB (81%)

    Audio
    ID : 2326 (0x916)
    Menu ID : 55207 (0xD7A7)
    Format : MPEG Audio
    Format version : Version 1
    Format profile : Layer 2
    Codec ID : 4
    Duration : 1 min 2 s
    Bit rate mode : Constant
    Bit rate : 192 kb/s
    Maximum bit rate : 39.0 Mb/s
    Channel(s) : 2 channels
    Sampling rate : 48.0 kHz
    Frame rate : 41.667 FPS (1152 SPF)
    Compression mode : Lossy
    Delay relative to video : -631 ms
    Stream size : 1.43 MiB (13%)
    Language : English

    Menu
    ID : 259 (0x103)
    Menu ID : 55207 (0xD7A7)
    Duration : 1 min 2 s
    List : 2352 (0x930) (MPEG Video) / 2326 (0x916) (MPEG Audio, English)
    Language : / English
    Service name : That's Oldies
    Service provider : BSkyB
    Service type : digital television

    If I press record too late I only get the end part of the song

    mp2 audio!!!

    Poor Mr Hobbs

    Probably have all of it or more of this on some harddisc

    Seems most is on youtube anyways these days, you can download that via some sites.

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Phil Hobbs@3:633/10 to All on Wednesday, June 10, 2026 11:04:37
    On 2026-06-09 19:15, Jeff Liebermann wrote:
    On Tue, 09 Jun 2026 12:16:26 -0400, joegwinn@comcast.net wrote:

    On Mon, 08 Jun 2026 10:47:07 -0700, john larkin <jl@glen--canyon.com>
    wrote:

    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info
    on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick
    this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI
    never showed up, in the first place.

    If I hadn?t stopped talking audio design seriously in about 1980, I >>>>>> certainly would have when crappy compressed MP3s took over the world. >>>>>>
    Golden ears, my left buttock.

    The ears are close to the brain for a reason. Golden ears don't seem to >>>> be close to particularly good brains.

    I read a study that says that bats can correlate time between their
    ears with nanosecond resolution. Pretty good for wet stuff.

    Bats are pretty good, but that seems a bit too good. Can you find
    that study?

    "The transfer function of a target limits the jitter detection
    threshold with signals of echolocating FM-bats" <https://pubmed.ncbi.nlm.nih.gov/16395614/>
    "Some investigators have obtained results indicating that bats are
    able to discriminate alternations in delay down to 10 ns, which
    appears incredible for purely physical reasons."

    "Bat sonar: an alternative interpretation of the 10-ns jitter result" <https://pubmed.ncbi.nlm.nih.gov/9528108/>
    "In 1990 Simmons et al. reported evidence of a time resolution
    hitherto unknown in any animal, namely a 10-ns jitter detection
    threshold in echolocating bats."

    Google Scholar produces additional papers on bat echolocation acuity: <https://scholar.google.com/scholar?q=bat%20echolocation%2010%20nsec>



    In my neck of the woods, when you rhetorically quote some spec in the
    100-999 nm range, you normally call it "submicron", whereas anything
    between 1 nm and 100 nm is "nanometer".

    Cheers

    Phil Hobbs

    --
    Dr Philip C D Hobbs
    Principal Consultant
    ElectroOptical Innovations LLC / Hobbs ElectroOptics
    Optics, Electro-optics, Photonics, Analog Electronics
    Briarcliff Manor NY 10510

    http://electrooptical.net
    http://hobbs-eo.com


    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Jeff Liebermann@3:633/10 to All on Wednesday, June 10, 2026 09:10:34
    On Wed, 10 Jun 2026 11:04:37 -0400, Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:

    On 2026-06-09 19:15, Jeff Liebermann wrote:
    On Tue, 09 Jun 2026 12:16:26 -0400, joegwinn@comcast.net wrote:

    On Mon, 08 Jun 2026 10:47:07 -0700, john larkin <jl@glen--canyon.com>
    wrote:

    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info
    on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick
    this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI
    never showed up, in the first place.

    If I hadn?t stopped talking audio design seriously in about 1980, I >>>>>>> certainly would have when crappy compressed MP3s took over the world. >>>>>>>
    Golden ears, my left buttock.

    The ears are close to the brain for a reason. Golden ears don't seem to >>>>> be close to particularly good brains.

    I read a study that says that bats can correlate time between their
    ears with nanosecond resolution. Pretty good for wet stuff.

    Bats are pretty good, but that seems a bit too good. Can you find
    that study?

    "The transfer function of a target limits the jitter detection
    threshold with signals of echolocating FM-bats"
    <https://pubmed.ncbi.nlm.nih.gov/16395614/>
    "Some investigators have obtained results indicating that bats are
    able to discriminate alternations in delay down to 10 ns, which
    appears incredible for purely physical reasons."

    "Bat sonar: an alternative interpretation of the 10-ns jitter result"
    <https://pubmed.ncbi.nlm.nih.gov/9528108/>
    "In 1990 Simmons et al. reported evidence of a time resolution
    hitherto unknown in any animal, namely a 10-ns jitter detection
    threshold in echolocating bats."

    Google Scholar produces additional papers on bat echolocation acuity:
    <https://scholar.google.com/scholar?q=bat%20echolocation%2010%20nsec>


    In my neck of the woods, when you rhetorically quote some spec in the >100-999 nm range, you normally call it "submicron", whereas anything
    between 1 nm and 100 nm is "nanometer".

    Cheers

    Phil Hobbs

    The numbers that were cited were all for timing in nanoseconds and NOT
    for distance as in nanometers.

    Incidentally, I've read through various papers that mention the 10
    nsec number. The majority refer to a 10 nsec jitter and NOT a 10 nsec resolution. Also, the 10 nsec number seems to be at the extreme edge
    when graphs were supplied. My guess(tm) is that there might be some
    confusion between 10 nsec jitter and nsec resolution in some of the
    various papers. For example:

    "Delay accuracy in bat sonar is related to the reciprocal of
    normalized echo bandwidth, or Q" <https://pmc.ncbi.nlm.nih.gov/articles/PMC373515/#sec2>
    See graphs in Fig 1, 2 and 3.
    "In jitter experiments, the bat's thresholds for detecting changes in
    delay were small fractions of a microsecond, which seemed impossible
    for the animal to achieve, so attention was then focused on what
    (presumably spectral) artifact other than change in delay itself must
    be the cue for the bat's performance (19, 20)."

    I couldn't determine what the author meant by a "small fraction of a microsecond".

    --
    Jeff Liebermann jeffl@cruzio.com
    PO Box 272 http://www.LearnByDestroying.com
    Ben Lomond CA 95005-0272 AE6KS 831-336-2558


    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From joegwinn@3:633/10 to All on Wednesday, June 10, 2026 17:28:51
    On Tue, 09 Jun 2026 16:15:44 -0700, Jeff Liebermann <jeffl@cruzio.com>
    wrote:

    On Tue, 09 Jun 2026 12:16:26 -0400, joegwinn@comcast.net wrote:

    On Mon, 08 Jun 2026 10:47:07 -0700, john larkin <jl@glen--canyon.com> >>wrote:

    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org> >>>wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info
    on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick
    this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI
    never showed up, in the first place.

    If I hadn?t stopped talking audio design seriously in about 1980, I >>>>>> certainly would have when crappy compressed MP3s took over the world. >>>>>>
    Golden ears, my left buttock.

    The ears are close to the brain for a reason. Golden ears don't seem to >>>>be close to particularly good brains.

    I read a study that says that bats can correlate time between their
    ears with nanosecond resolution. Pretty good for wet stuff.

    Bats are pretty good, but that seems a bit too good. Can you find
    that study?

    "The transfer function of a target limits the jitter detection
    threshold with signals of echolocating FM-bats" ><https://pubmed.ncbi.nlm.nih.gov/16395614/>
    "Some investigators have obtained results indicating that bats are
    able to discriminate alternations in delay down to 10 ns, which
    appears incredible for purely physical reasons."

    "Bat sonar: an alternative interpretation of the 10-ns jitter result" ><https://pubmed.ncbi.nlm.nih.gov/9528108/>
    "In 1990 Simmons et al. reported evidence of a time resolution
    hitherto unknown in any animal, namely a 10-ns jitter detection
    threshold in echolocating bats."

    Google Scholar produces additional papers on bat echolocation acuity: ><https://scholar.google.com/scholar?q=bat%20echolocation%2010%20nsec>

    So that's a source of the 10ns stuff. The theory is that there was an instrumentation error, which is certainly plausible as no biological
    system is that fast, so biological researchers are far out of their
    domain for sure.

    Joe

    PS: The 100,000 rpm spinner in biology is "ATP Synthase", the enzyme
    system that converts between ADP and ATP in the mitochondria (in
    animals) and chloroplasts (in plants).

    .<https://en.wikipedia.org/wiki/ATP_synthase>

    JMG

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Wednesday, June 10, 2026 18:02:22
    On Wed, 10 Jun 2026 17:28:51 -0400, joegwinn@comcast.net wrote:

    On Tue, 09 Jun 2026 16:15:44 -0700, Jeff Liebermann <jeffl@cruzio.com>
    wrote:

    On Tue, 09 Jun 2026 12:16:26 -0400, joegwinn@comcast.net wrote:

    On Mon, 08 Jun 2026 10:47:07 -0700, john larkin <jl@glen--canyon.com> >>>wrote:

    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info
    on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick
    this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI
    never showed up, in the first place.

    If I hadn?t stopped talking audio design seriously in about 1980, I >>>>>>> certainly would have when crappy compressed MP3s took over the world. >>>>>>>
    Golden ears, my left buttock.

    The ears are close to the brain for a reason. Golden ears don't seem to >>>>>be close to particularly good brains.

    I read a study that says that bats can correlate time between their >>>>ears with nanosecond resolution. Pretty good for wet stuff.

    Bats are pretty good, but that seems a bit too good. Can you find
    that study?

    "The transfer function of a target limits the jitter detection
    threshold with signals of echolocating FM-bats" >><https://pubmed.ncbi.nlm.nih.gov/16395614/>
    "Some investigators have obtained results indicating that bats are
    able to discriminate alternations in delay down to 10 ns, which
    appears incredible for purely physical reasons."

    "Bat sonar: an alternative interpretation of the 10-ns jitter result" >><https://pubmed.ncbi.nlm.nih.gov/9528108/>
    "In 1990 Simmons et al. reported evidence of a time resolution
    hitherto unknown in any animal, namely a 10-ns jitter detection
    threshold in echolocating bats."

    Google Scholar produces additional papers on bat echolocation acuity: >><https://scholar.google.com/scholar?q=bat%20echolocation%2010%20nsec>

    So that's a source of the 10ns stuff. The theory is that there was an >instrumentation error, which is certainly plausible as no biological
    system is that fast, so biological researchers are far out of their
    domain for sure.

    Why do you say that no biological system can be that fast?

    Anything less than a microsecond is astounding, inside the gooey head
    of a bat flapping its wings mid-air hunting a moth.



    Joe

    PS: The 100,000 rpm spinner in biology is "ATP Synthase", the enzyme
    system that converts between ADP and ATP in the mitochondria (in
    animals) and chloroplasts (in plants).

    .<https://en.wikipedia.org/wiki/ATP_synthase>

    JMG


    DNA helicase, the little gadget that splits our DNA when a cell
    divides, spins at about 10,000 RPM.

    <Rotating biological motors were declared to be impossible, and
    rotating flagellum were known to be optical illusions.> Once.

    Google the <> above.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Jeff Liebermann@3:633/10 to All on Wednesday, June 10, 2026 19:32:15
    On Wed, 10 Jun 2026 17:28:51 -0400, joegwinn@comcast.net wrote:

    On Tue, 09 Jun 2026 16:15:44 -0700, Jeff Liebermann <jeffl@cruzio.com>
    wrote:

    On Tue, 09 Jun 2026 12:16:26 -0400, joegwinn@comcast.net wrote:

    On Mon, 08 Jun 2026 10:47:07 -0700, john larkin <jl@glen--canyon.com> >>>wrote:

    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info
    on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick
    this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI
    never showed up, in the first place.

    If I hadn?t stopped talking audio design seriously in about 1980, I >>>>>>> certainly would have when crappy compressed MP3s took over the world. >>>>>>>
    Golden ears, my left buttock.

    The ears are close to the brain for a reason. Golden ears don't seem to >>>>>be close to particularly good brains.

    I read a study that says that bats can correlate time between their >>>>ears with nanosecond resolution. Pretty good for wet stuff.

    Bats are pretty good, but that seems a bit too good. Can you find
    that study?

    "The transfer function of a target limits the jitter detection
    threshold with signals of echolocating FM-bats" >><https://pubmed.ncbi.nlm.nih.gov/16395614/>
    "Some investigators have obtained results indicating that bats are
    able to discriminate alternations in delay down to 10 ns, which
    appears incredible for purely physical reasons."

    "Bat sonar: an alternative interpretation of the 10-ns jitter result" >><https://pubmed.ncbi.nlm.nih.gov/9528108/>
    "In 1990 Simmons et al. reported evidence of a time resolution
    hitherto unknown in any animal, namely a 10-ns jitter detection
    threshold in echolocating bats."

    Google Scholar produces additional papers on bat echolocation acuity: >><https://scholar.google.com/scholar?q=bat%20echolocation%2010%20nsec>

    So that's a source of the 10ns stuff. The theory is that there was an >instrumentation error, which is certainly plausible as no biological
    system is that fast, so biological researchers are far out of their
    domain for sure.

    It's only my best guess(tm). I didn't have much success at finding
    the oldest bat related citation that included a 10 nsec response time.
    Joe

    PS: The 100,000 rpm spinner in biology is "ATP Synthase", the enzyme
    system that converts between ADP and ATP in the mitochondria (in
    animals) and chloroplasts (in plants).

    .<https://en.wikipedia.org/wiki/ATP_synthase>

    JMG

    Sigh. I initially mentioned that there might have been some confusion
    between response time and jitter. Now, you add DNA replication to the confusion. Time for a sanity check.

    What got my attention was the radical difference between the alleged
    10 nsec nervous response time in bats, and the much slower nerve
    conduction times in humans. (I couldn't find specific numbers for
    bats).

    "Nerve conduction velocity" <https://en.wikipedia.org/wiki/Nerve_conduction_velocity>
    "The speed of nerve impulse transmission ranges from about 0.5 m/s to
    over 120 m/s".

    I once watched a "cloud" of fruit bats emerging from the trees at
    dusk:
    <https://en.wikipedia.org/wiki/Egyptian_fruit_bat>
    I don't know how many there were, but my guess(tm) is in the
    thousands. The bats were not using their sonar for locating moths.
    Instead, they were looking for fruit and using their sonar to prevent
    mid-air collisions. I watched carefully and didn't see any collisions
    or bats falling from the sky. In order to do that, the muscles that
    move the bats wings need to quickly respond to brain signals and the
    muscles need to move quite fast. 10 nsec response time isn't going to
    work when the signals move at 0.5 m/s to over 120 m/s. A nerve
    impulse moves at perhaps 1 meter/sec (or 10 nanometers in 10
    nanoseconds). A 10 nsec nerve impulse will have moved a microscopic
    distance.


    --
    Jeff Liebermann jeffl@cruzio.com
    PO Box 272 http://www.LearnByDestroying.com
    Ben Lomond CA 95005-0272 AE6KS 831-336-2558


    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Thursday, June 11, 2026 14:33:12
    On 11/06/2026 11:02 am, john larkin wrote:
    On Wed, 10 Jun 2026 17:28:51 -0400, joegwinn@comcast.net wrote:

    On Tue, 09 Jun 2026 16:15:44 -0700, Jeff Liebermann <jeffl@cruzio.com>
    wrote:

    On Tue, 09 Jun 2026 12:16:26 -0400, joegwinn@comcast.net wrote:

    On Mon, 08 Jun 2026 10:47:07 -0700, john larkin <jl@glen--canyon.com>
    wrote:

    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>> wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info >>>>>>>>> on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick >>>>>>>>> this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI >>>>>>>>> never showed up, in the first place.

    If I hadn?t stopped talking audio design seriously in about 1980, I >>>>>>>> certainly would have when crappy compressed MP3s took over the world. >>>>>>>>
    Golden ears, my left buttock.

    The ears are close to the brain for a reason. Golden ears don't seem to >>>>>> be close to particularly good brains.

    I read a study that says that bats can correlate time between their
    ears with nanosecond resolution. Pretty good for wet stuff.

    Bats are pretty good, but that seems a bit too good. Can you find
    that study?

    "The transfer function of a target limits the jitter detection
    threshold with signals of echolocating FM-bats"
    <https://pubmed.ncbi.nlm.nih.gov/16395614/>
    "Some investigators have obtained results indicating that bats are
    able to discriminate alternations in delay down to 10 ns, which
    appears incredible for purely physical reasons."

    "Bat sonar: an alternative interpretation of the 10-ns jitter result"
    <https://pubmed.ncbi.nlm.nih.gov/9528108/>
    "In 1990 Simmons et al. reported evidence of a time resolution
    hitherto unknown in any animal, namely a 10-ns jitter detection
    threshold in echolocating bats."

    Google Scholar produces additional papers on bat echolocation acuity:
    <https://scholar.google.com/scholar?q=bat%20echolocation%2010%20nsec>

    So that's a source of the 10ns stuff. The theory is that there was an
    instrumentation error, which is certainly plausible as no biological
    system is that fast, so biological researchers are far out of their
    domain for sure.

    Why do you say that no biological system can be that fast?

    He's got some idea of what be involved in that. You clearly don't.

    Anything less than a microsecond is astounding, inside the gooey head
    of a bat flapping its wings mid-air hunting a moth.

    The word is not "astounding" but "implausible".

    PS: The 100,000 rpm spinner in biology is "ATP Synthase", the enzyme
    system that converts between ADP and ATP in the mitochondria (in
    animals) and chloroplasts (in plants).

    .<https://en.wikipedia.org/wiki/ATP_synthase>

    DNA helicase, the little gadget that splits our DNA when a cell
    divides, spins at about 10,000 RPM.

    But it is a single molecule, and correspondingly small, and isolated
    within a cage of other molecules.

    <Rotating biological motors were declared to be impossible, and
    rotating flagellum were known to be optical illusions.> Once.

    Google the <> above.

    And get the responses of people as pig ignorant as John Larkin.

    --
    Bill Sloman, Sydhney


    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Wednesday, June 10, 2026 22:29:45
    On Wed, 10 Jun 2026 19:32:15 -0700, Jeff Liebermann <jeffl@cruzio.com>
    wrote:

    On Wed, 10 Jun 2026 17:28:51 -0400, joegwinn@comcast.net wrote:

    On Tue, 09 Jun 2026 16:15:44 -0700, Jeff Liebermann <jeffl@cruzio.com> >>wrote:

    On Tue, 09 Jun 2026 12:16:26 -0400, joegwinn@comcast.net wrote:

    On Mon, 08 Jun 2026 10:47:07 -0700, john larkin <jl@glen--canyon.com> >>>>wrote:

    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info >>>>>>>>> on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick >>>>>>>>> this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI >>>>>>>>> never showed up, in the first place.

    If I hadn?t stopped talking audio design seriously in about 1980, I >>>>>>>> certainly would have when crappy compressed MP3s took over the world. >>>>>>>>
    Golden ears, my left buttock.

    The ears are close to the brain for a reason. Golden ears don't seem to >>>>>>be close to particularly good brains.

    I read a study that says that bats can correlate time between their >>>>>ears with nanosecond resolution. Pretty good for wet stuff.

    Bats are pretty good, but that seems a bit too good. Can you find
    that study?

    "The transfer function of a target limits the jitter detection
    threshold with signals of echolocating FM-bats" >>><https://pubmed.ncbi.nlm.nih.gov/16395614/>
    "Some investigators have obtained results indicating that bats are
    able to discriminate alternations in delay down to 10 ns, which
    appears incredible for purely physical reasons."

    "Bat sonar: an alternative interpretation of the 10-ns jitter result" >>><https://pubmed.ncbi.nlm.nih.gov/9528108/>
    "In 1990 Simmons et al. reported evidence of a time resolution
    hitherto unknown in any animal, namely a 10-ns jitter detection
    threshold in echolocating bats."

    Google Scholar produces additional papers on bat echolocation acuity: >>><https://scholar.google.com/scholar?q=bat%20echolocation%2010%20nsec>

    So that's a source of the 10ns stuff. The theory is that there was an >>instrumentation error, which is certainly plausible as no biological
    system is that fast, so biological researchers are far out of their
    domain for sure.

    It's only my best guess(tm). I didn't have much success at finding
    the oldest bat related citation that included a 10 nsec response time.
    Joe

    PS: The 100,000 rpm spinner in biology is "ATP Synthase", the enzyme >>system that converts between ADP and ATP in the mitochondria (in
    animals) and chloroplasts (in plants).

    .<https://en.wikipedia.org/wiki/ATP_synthase>

    JMG

    Sigh. I initially mentioned that there might have been some confusion >between response time and jitter. Now, you add DNA replication to the >confusion. Time for a sanity check.

    What got my attention was the radical difference between the alleged
    10 nsec nervous response time in bats, and the much slower nerve
    conduction times in humans. (I couldn't find specific numbers for
    bats).

    "Nerve conduction velocity" ><https://en.wikipedia.org/wiki/Nerve_conduction_velocity>
    "The speed of nerve impulse transmission ranges from about 0.5 m/s to
    over 120 m/s".

    I once watched a "cloud" of fruit bats emerging from the trees at
    dusk:
    <https://en.wikipedia.org/wiki/Egyptian_fruit_bat>
    I don't know how many there were, but my guess(tm) is in the
    thousands. The bats were not using their sonar for locating moths.
    Instead, they were looking for fruit and using their sonar to prevent
    mid-air collisions. I watched carefully and didn't see any collisions
    or bats falling from the sky. In order to do that, the muscles that
    move the bats wings need to quickly respond to brain signals and the
    muscles need to move quite fast. 10 nsec response time isn't going to
    work when the signals move at 0.5 m/s to over 120 m/s. A nerve
    impulse moves at perhaps 1 meter/sec (or 10 nanometers in 10
    nanoseconds). A 10 nsec nerve impulse will have moved a microscopic >distance.

    For the record, I said "nanosecond resolution" not 10 nanoseconds.

    And yes, nerve impulses are assumed move about a meter per second, yet
    people play table tennis.

    One possible explanation is that nerve impulses don't move meters per
    second.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Thursday, June 11, 2026 17:13:17
    On 11/06/2026 3:29 pm, john larkin wrote:
    On Wed, 10 Jun 2026 19:32:15 -0700, Jeff Liebermann <jeffl@cruzio.com>
    wrote:

    On Wed, 10 Jun 2026 17:28:51 -0400, joegwinn@comcast.net wrote:

    On Tue, 09 Jun 2026 16:15:44 -0700, Jeff Liebermann <jeffl@cruzio.com>
    wrote:

    On Tue, 09 Jun 2026 12:16:26 -0400, joegwinn@comcast.net wrote:

    On Mon, 08 Jun 2026 10:47:07 -0700, john larkin <jl@glen--canyon.com> >>>>> wrote:

    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>> wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    <snip>

    Sigh. I initially mentioned that there might have been some confusion
    between response time and jitter. Now, you add DNA replication to the
    confusion. Time for a sanity check.

    What got my attention was the radical difference between the alleged
    10 nsec nervous response time in bats, and the much slower nerve
    conduction times in humans. (I couldn't find specific numbers for
    bats).

    "Nerve conduction velocity"
    <https://en.wikipedia.org/wiki/Nerve_conduction_velocity>
    "The speed of nerve impulse transmission ranges from about 0.5 m/s to
    over 120 m/s".

    I once watched a "cloud" of fruit bats emerging from the trees at
    dusk:
    <https://en.wikipedia.org/wiki/Egyptian_fruit_bat>
    I don't know how many there were, but my guess(tm) is in the
    thousands. The bats were not using their sonar for locating moths.
    Instead, they were looking for fruit and using their sonar to prevent
    mid-air collisions. I watched carefully and didn't see any collisions
    or bats falling from the sky. In order to do that, the muscles that
    move the bats wings need to quickly respond to brain signals and the
    muscles need to move quite fast. 10 nsec response time isn't going to
    work when the signals move at 0.5 m/s to over 120 m/s. A nerve
    impulse moves at perhaps 1 meter/sec (or 10 nanometers in 10
    nanoseconds). A 10 nsec nerve impulse will have moved a microscopic
    distance.

    For the record, I said "nanosecond resolution" not 10 nanoseconds.

    But it is still nonsense.

    And yes, nerve impulses are assumed move about a meter per second, yet
    people play table tennis.

    One possible explanation is that nerve impulses don't move meters per
    second.

    Possible, but not plausible. People have been measuring nerve impulse
    speed for quite a while now.

    https://en.wikipedia.org/wiki/Squid_giant_axon

    There was quite a lot of fuss about that measurement back in 1952 and it
    lead to a Nobel Prize - I remember it and I was only a kid at the time.

    https://en.wikipedia.org/wiki/Nerve_conduction_velocity

    cites work going as far back as 1972. Some of speeds cited get up to 120 meters per second. A lot faster than your "meter per second" but not
    fast enough for 10nsec resolution to be plausible.

    --
    Bill Sloman, Sydney


    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Jan Panteltje@3:633/10 to All on Thursday, June 11, 2026 08:42:10
    Bill Sloman <bill.sloman@ieee.org>wrote:
    On 11/06/2026 3:29 pm, john larkin wrote:
    On Wed, 10 Jun 2026 19:32:15 -0700, Jeff Liebermann <jeffl@cruzio.com>
    wrote:

    On Wed, 10 Jun 2026 17:28:51 -0400, joegwinn@comcast.net wrote:

    On Tue, 09 Jun 2026 16:15:44 -0700, Jeff Liebermann <jeffl@cruzio.com> >>>> wrote:

    On Tue, 09 Jun 2026 12:16:26 -0400, joegwinn@comcast.net wrote:

    On Mon, 08 Jun 2026 10:47:07 -0700, john larkin <jl@glen--canyon.com> >>>>>> wrote:

    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>> wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    <snip>

    Sigh. I initially mentioned that there might have been some confusion
    between response time and jitter. Now, you add DNA replication to the
    confusion. Time for a sanity check.

    What got my attention was the radical difference between the alleged
    10 nsec nervous response time in bats, and the much slower nerve
    conduction times in humans. (I couldn't find specific numbers for
    bats).

    "Nerve conduction velocity"
    <https://en.wikipedia.org/wiki/Nerve_conduction_velocity>
    "The speed of nerve impulse transmission ranges from about 0.5 m/s to
    over 120 m/s".

    I once watched a "cloud" of fruit bats emerging from the trees at
    dusk:
    <https://en.wikipedia.org/wiki/Egyptian_fruit_bat>
    I don't know how many there were, but my guess(tm) is in the
    thousands. The bats were not using their sonar for locating moths.
    Instead, they were looking for fruit and using their sonar to prevent
    mid-air collisions. I watched carefully and didn't see any collisions
    or bats falling from the sky. In order to do that, the muscles that
    move the bats wings need to quickly respond to brain signals and the
    muscles need to move quite fast. 10 nsec response time isn't going to
    work when the signals move at 0.5 m/s to over 120 m/s. A nerve
    impulse moves at perhaps 1 meter/sec (or 10 nanometers in 10
    nanoseconds). A 10 nsec nerve impulse will have moved a microscopic
    distance.

    For the record, I said "nanosecond resolution" not 10 nanoseconds.

    But it is still nonsense.

    And yes, nerve impulses are assumed move about a meter per second, yet
    people play table tennis.

    One possible explanation is that nerve impulses don't move meters per
    second.

    Possible, but not plausible. People have been measuring nerve impulse
    speed for quite a while now.

    https://en.wikipedia.org/wiki/Squid_giant_axon

    There was quite a lot of fuss about that measurement back in 1952 and it >lead to a Nobel Prize - I remember it and I was only a kid at the time.

    https://en.wikipedia.org/wiki/Nerve_conduction_velocity

    cites work going as far back as 1972. Some of speeds cited get up to 120 >meters per second. A lot faster than your "meter per second" but not
    fast enough for 10nsec resolution to be plausible.

    For a continuous 30 kHz beep transmitted by a bat the wavelength is
    1 / 340.29 = 0.00293867 meters, or about 3 mm.
    For a 1 degree difference in the reflected received signal 3 / 360 = 0.0083 mm Brain is close to ears in a bat, and signal path is the same from each ear to brain,
    so signal delays by length cancel.
    Periodic changes in arrival time in the brain could perhaps be perceived.

    In the simplest way by doing a digital XOR causing a changing pulse width,
    like do here:
    https://panteltje.nl/pub/wind_speed_by_differential_2_ebay_distance_meters_IMG_4891.JPG
    https://panteltje.nl/pub/xor_both_with_PC_fan_wind_IMG_4893.JPG

    10 dollar ebay stuff test.

    Pulse width in xor neural net... one neuron!

    Nature..

    mm underwater drones, submarines, war machines... I am sure they have it all figured out.

    Was thinking this morning about the minimum age for kids to read social networks in nano nano

    16 years x 365 days * 24 hours * 60 minutes * 60 seconds * 10^9
    raspberrypi: # wcalc
    Enter an expression to evaluate, q to quit, or ? for help:
    16 * 365 * 24 * 60 * 60 * 10^9 = 5.04576e+17 nano nanos

    Not counting leap-years of course...







    --- PyGate Linux v1.5.15
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Liz Tuddenham@3:633/10 to All on Thursday, June 11, 2026 14:28:44
    john larkin <jl@glen--canyon.com> wrote:


    Anything less than a microsecond is astounding, inside the gooey head
    of a bat flapping its wings mid-air hunting a moth.

    To put it in perspective, a microsecond at the velocity of sound in air corresponds to 0.25mm (or 0.125mm for echolocation distance
    measurement).


    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk

    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Liz Tuddenham@3:633/10 to All on Thursday, June 11, 2026 14:28:45
    Bill Sloman <bill.sloman@ieee.org> wrote:

    [...]
    Some [nerve impulse] speeds cited get up to 120
    meters per second. A lot faster than your "meter per second" but not
    fast enough for 10nsec resolution to be plausible.

    The resolution would be the time-difference between two pulses and could possibly be resolved to 10nSec if the delay times were equal (or
    equalised). Prediction, based on existing trajectories, is a more
    likely explanation.


    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk

    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Thursday, June 11, 2026 07:12:25
    On Thu, 11 Jun 2026 17:13:17 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 11/06/2026 3:29 pm, john larkin wrote:
    On Wed, 10 Jun 2026 19:32:15 -0700, Jeff Liebermann <jeffl@cruzio.com>
    wrote:

    On Wed, 10 Jun 2026 17:28:51 -0400, joegwinn@comcast.net wrote:

    On Tue, 09 Jun 2026 16:15:44 -0700, Jeff Liebermann <jeffl@cruzio.com> >>>> wrote:

    On Tue, 09 Jun 2026 12:16:26 -0400, joegwinn@comcast.net wrote:

    On Mon, 08 Jun 2026 10:47:07 -0700, john larkin <jl@glen--canyon.com> >>>>>> wrote:

    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>> wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    <snip>

    Sigh. I initially mentioned that there might have been some confusion
    between response time and jitter. Now, you add DNA replication to the
    confusion. Time for a sanity check.

    What got my attention was the radical difference between the alleged
    10 nsec nervous response time in bats, and the much slower nerve
    conduction times in humans. (I couldn't find specific numbers for
    bats).

    "Nerve conduction velocity"
    <https://en.wikipedia.org/wiki/Nerve_conduction_velocity>
    "The speed of nerve impulse transmission ranges from about 0.5 m/s to
    over 120 m/s".

    I once watched a "cloud" of fruit bats emerging from the trees at
    dusk:
    <https://en.wikipedia.org/wiki/Egyptian_fruit_bat>
    I don't know how many there were, but my guess(tm) is in the
    thousands. The bats were not using their sonar for locating moths.
    Instead, they were looking for fruit and using their sonar to prevent
    mid-air collisions. I watched carefully and didn't see any collisions
    or bats falling from the sky. In order to do that, the muscles that
    move the bats wings need to quickly respond to brain signals and the
    muscles need to move quite fast. 10 nsec response time isn't going to
    work when the signals move at 0.5 m/s to over 120 m/s. A nerve
    impulse moves at perhaps 1 meter/sec (or 10 nanometers in 10
    nanoseconds). A 10 nsec nerve impulse will have moved a microscopic
    distance.

    For the record, I said "nanosecond resolution" not 10 nanoseconds.

    But it is still nonsense.

    And yes, nerve impulses are assumed move about a meter per second, yet
    people play table tennis.

    One possible explanation is that nerve impulses don't move meters per
    second.

    Possible, but not plausible. People have been measuring nerve impulse
    speed for quite a while now.

    They measure what's easy to measure, an electrical impulse. Maybe
    that's not the information being sent.


    https://en.wikipedia.org/wiki/Squid_giant_axon

    There was quite a lot of fuss about that measurement back in 1952 and it >lead to a Nobel Prize - I remember it and I was only a kid at the time.

    https://en.wikipedia.org/wiki/Nerve_conduction_velocity

    cites work going as far back as 1972. Some of speeds cited get up to 120 >meters per second. A lot faster than your "meter per second" but not
    fast enough for 10nsec resolution to be plausible.

    Bats catch moths. Baseballs get hit.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Thursday, June 11, 2026 07:21:26
    On Thu, 11 Jun 2026 14:28:44 +0100, liz@poppyrecords.invalid.invalid
    (Liz Tuddenham) wrote:

    john larkin <jl@glen--canyon.com> wrote:


    Anything less than a microsecond is astounding, inside the gooey head
    of a bat flapping its wings mid-air hunting a moth.

    To put it in perspective, a microsecond at the velocity of sound in air >corresponds to 0.25mm (or 0.125mm for echolocation distance
    measurement).

    If nerve impulses travel 100 m/s and a bat's ears are 2 cm apart, the
    neural delay between ears is 200 us. And that's modulated by movement, heartbeats, things like that.

    Maybe nature doesn't care about our opinions of how it's allowed to
    work.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Friday, June 12, 2026 01:57:15
    On 12/06/2026 12:12 am, john larkin wrote:
    On Thu, 11 Jun 2026 17:13:17 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 11/06/2026 3:29 pm, john larkin wrote:
    On Wed, 10 Jun 2026 19:32:15 -0700, Jeff Liebermann <jeffl@cruzio.com>
    wrote:

    On Wed, 10 Jun 2026 17:28:51 -0400, joegwinn@comcast.net wrote:

    On Tue, 09 Jun 2026 16:15:44 -0700, Jeff Liebermann <jeffl@cruzio.com> >>>>> wrote:

    On Tue, 09 Jun 2026 12:16:26 -0400, joegwinn@comcast.net wrote:

    On Mon, 08 Jun 2026 10:47:07 -0700, john larkin <jl@glen--canyon.com> >>>>>>> wrote:

    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>>> wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote: >>>>>>>>>>> legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    <snip>

    Sigh. I initially mentioned that there might have been some confusion >>>> between response time and jitter. Now, you add DNA replication to the >>>> confusion. Time for a sanity check.

    What got my attention was the radical difference between the alleged
    10 nsec nervous response time in bats, and the much slower nerve
    conduction times in humans. (I couldn't find specific numbers for
    bats).

    "Nerve conduction velocity"
    <https://en.wikipedia.org/wiki/Nerve_conduction_velocity>
    "The speed of nerve impulse transmission ranges from about 0.5 m/s to
    over 120 m/s".

    I once watched a "cloud" of fruit bats emerging from the trees at
    dusk:
    <https://en.wikipedia.org/wiki/Egyptian_fruit_bat>
    I don't know how many there were, but my guess(tm) is in the
    thousands. The bats were not using their sonar for locating moths.
    Instead, they were looking for fruit and using their sonar to prevent
    mid-air collisions. I watched carefully and didn't see any collisions >>>> or bats falling from the sky. In order to do that, the muscles that
    move the bats wings need to quickly respond to brain signals and the
    muscles need to move quite fast. 10 nsec response time isn't going to >>>> work when the signals move at 0.5 m/s to over 120 m/s. A nerve
    impulse moves at perhaps 1 meter/sec (or 10 nanometers in 10
    nanoseconds). A 10 nsec nerve impulse will have moved a microscopic
    distance.

    For the record, I said "nanosecond resolution" not 10 nanoseconds.

    But it is still nonsense.

    And yes, nerve impulses are assumed move about a meter per second, yet
    people play table tennis.

    One possible explanation is that nerve impulses don't move meters per
    second.

    Possible, but not plausible. People have been measuring nerve impulse
    speed for quite a while now.

    They measure what's easy to measure, an electrical impulse. Maybe
    that's not the information being sent.

    The electrical impulse isn't all that easy to measure, but at least it
    is visible, if you measure carefully enough.

    You can hypothesise all sorts of magic connections, but until you spell
    out what one of them might be and how you'd measure it, you are just
    going in for hand-waving mysticism.

    It all looks very as if you got caught being even stupider than usual,
    and are now trying to back off.

    https://en.wikipedia.org/wiki/Squid_giant_axon

    There was quite a lot of fuss about that measurement back in 1952 and it
    lead to a Nobel Prize - I remember it and I was only a kid at the time.

    https://en.wikipedia.org/wiki/Nerve_conduction_velocity

    cites work going as far back as 1972. Some of speeds cited get up to 120
    meters per second. A lot faster than your "meter per second" but not
    fast enough for 10nsec resolution to be plausible.

    Bats catch moths. Baseballs get hit.

    And half-wits have very silly ideas about what that implies.

    --
    Bill Sloman, Sydney


    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Friday, June 12, 2026 02:00:02
    On 12/06/2026 12:21 am, john larkin wrote:
    On Thu, 11 Jun 2026 14:28:44 +0100, liz@poppyrecords.invalid.invalid
    (Liz Tuddenham) wrote:

    john larkin <jl@glen--canyon.com> wrote:


    Anything less than a microsecond is astounding, inside the gooey head
    of a bat flapping its wings mid-air hunting a moth.

    To put it in perspective, a microsecond at the velocity of sound in air
    corresponds to 0.25mm (or 0.125mm for echolocation distance
    measurement).

    If nerve impulses travel 100 m/s and a bat's ears are 2 cm apart, the
    neural delay between ears is 200 us. And that's modulated by movement, heartbeats, things like that.

    Maybe nature doesn't care about our opinions of how it's allowed to
    work.

    Obviously it doesn't. That doesn't excuse you from picking up
    particularly half-baked ideas about how well it might be performing and posting them here.

    --
    Bill Sloman, Sydney


    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Jeff Liebermann@3:633/10 to All on Thursday, June 11, 2026 09:16:05
    On Wed, 10 Jun 2026 22:29:45 -0700, john larkin <jl@glen--canyon.com>
    wrote:

    On Wed, 10 Jun 2026 19:32:15 -0700, Jeff Liebermann <jeffl@cruzio.com>
    wrote:

    On Wed, 10 Jun 2026 17:28:51 -0400, joegwinn@comcast.net wrote:

    On Tue, 09 Jun 2026 16:15:44 -0700, Jeff Liebermann <jeffl@cruzio.com> >>>wrote:

    On Tue, 09 Jun 2026 12:16:26 -0400, joegwinn@comcast.net wrote:

    On Mon, 08 Jun 2026 10:47:07 -0700, john larkin <jl@glen--canyon.com> >>>>>wrote:

    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info >>>>>>>>>> on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick >>>>>>>>>> this up in time to remove the TI part number from your list >>>>>>>>>> of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI >>>>>>>>>> never showed up, in the first place.

    If I hadn?t stopped talking audio design seriously in about 1980, I >>>>>>>>> certainly would have when crappy compressed MP3s took over the world. >>>>>>>>>
    Golden ears, my left buttock.

    The ears are close to the brain for a reason. Golden ears don't seem to >>>>>>>be close to particularly good brains.

    I read a study that says that bats can correlate time between their >>>>>>ears with nanosecond resolution. Pretty good for wet stuff.

    Bats are pretty good, but that seems a bit too good. Can you find >>>>>that study?

    "The transfer function of a target limits the jitter detection >>>>threshold with signals of echolocating FM-bats" >>>><https://pubmed.ncbi.nlm.nih.gov/16395614/>
    "Some investigators have obtained results indicating that bats are
    able to discriminate alternations in delay down to 10 ns, which
    appears incredible for purely physical reasons."

    "Bat sonar: an alternative interpretation of the 10-ns jitter result" >>>><https://pubmed.ncbi.nlm.nih.gov/9528108/>
    "In 1990 Simmons et al. reported evidence of a time resolution
    hitherto unknown in any animal, namely a 10-ns jitter detection >>>>threshold in echolocating bats."

    Google Scholar produces additional papers on bat echolocation acuity: >>>><https://scholar.google.com/scholar?q=bat%20echolocation%2010%20nsec>

    So that's a source of the 10ns stuff. The theory is that there was an >>>instrumentation error, which is certainly plausible as no biological >>>system is that fast, so biological researchers are far out of their >>>domain for sure.

    It's only my best guess(tm). I didn't have much success at finding
    the oldest bat related citation that included a 10 nsec response time.
    Joe

    PS: The 100,000 rpm spinner in biology is "ATP Synthase", the enzyme >>>system that converts between ADP and ATP in the mitochondria (in
    animals) and chloroplasts (in plants).

    .<https://en.wikipedia.org/wiki/ATP_synthase>

    JMG

    Sigh. I initially mentioned that there might have been some confusion >>between response time and jitter. Now, you add DNA replication to the >>confusion. Time for a sanity check.

    What got my attention was the radical difference between the alleged
    10 nsec nervous response time in bats, and the much slower nerve
    conduction times in humans. (I couldn't find specific numbers for
    bats).

    "Nerve conduction velocity" >><https://en.wikipedia.org/wiki/Nerve_conduction_velocity>
    "The speed of nerve impulse transmission ranges from about 0.5 m/s to
    over 120 m/s".

    I once watched a "cloud" of fruit bats emerging from the trees at
    dusk:
    <https://en.wikipedia.org/wiki/Egyptian_fruit_bat>
    I don't know how many there were, but my guess(tm) is in the
    thousands. The bats were not using their sonar for locating moths. >>Instead, they were looking for fruit and using their sonar to prevent >>mid-air collisions. I watched carefully and didn't see any collisions
    or bats falling from the sky. In order to do that, the muscles that
    move the bats wings need to quickly respond to brain signals and the >>muscles need to move quite fast. 10 nsec response time isn't going to
    work when the signals move at 0.5 m/s to over 120 m/s. A nerve
    impulse moves at perhaps 1 meter/sec (or 10 nanometers in 10
    nanoseconds). A 10 nsec nerve impulse will have moved a microscopic >>distance.

    For the record, I said "nanosecond resolution" not 10 nanoseconds.

    True. Please note that the URL's I provided were not in response to
    your posting. I was responding to a question by joegwinn@comcast.net: Message-ID: <bueg2l5gtditthqkhv407dcr924p5c07qd@4ax.com>
    "Bats are pretty good, but that seems a bit too good. Can you find
    that study?"

    And yes, nerve impulses are assumed move about a meter per second, yet
    people play table tennis.

    One possible explanation is that nerve impulses don't move meters per
    second.

    Methinks the mechanism might be similar to measuring the speed of
    electrons in wires. Energy transmission in a wire moves at near light
    speed. Electron drift velocity in wires (the movement of individual
    electrons) is about 1 mm/sec, which is much slower. I suspected that
    nerve impulse transmission in bats might be similar. However, my
    analogy breaks down because nerve impulse velocity can be 1 to 100
    meters/sec, which is still much slower than near light speed (3*10^8 meters/sec).

    "Nerve conduction velocity" <https://en.wikipedia.org/wiki/Nerve_conduction_velocity>
    "The speed of nerve impulse transmission ranges from about 0.5 m/s to
    over 120 m/s"

    "Bats are surprisingly fast decision makers" <https://www.sdu.dk/en/om-sdu/fakulteterne/naturvidenskab/nyheder-2015/2015_03_18_bat_decision>
    "Sometimes we also see reaction times of only 20 milliseconds in bats,
    for instance in response to loud sounds, but that is a simple reflex
    reaction that does not require brain work".

    20 msec response time isn't light speed it's a long way from 10 nsec.
    If the flying bat is on auto-pilot, then it's making 50 course
    corrections every second. Offhand, methinks that might be sufficient
    to avoid mid-air collisions with other bats. Even if 10 nsec
    resolution were possible, it would be overkill for a bat.



    --
    Jeff Liebermann jeffl@cruzio.com
    PO Box 272 http://www.LearnByDestroying.com
    Ben Lomond CA 95005-0272 AE6KS 831-336-2558


    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Friday, June 12, 2026 02:50:08
    On 12/06/2026 2:16 am, Jeff Liebermann wrote:
    On Wed, 10 Jun 2026 22:29:45 -0700, john larkin <jl@glen--canyon.com>
    wrote:

    On Wed, 10 Jun 2026 19:32:15 -0700, Jeff Liebermann <jeffl@cruzio.com>
    wrote:

    On Wed, 10 Jun 2026 17:28:51 -0400, joegwinn@comcast.net wrote:

    On Tue, 09 Jun 2026 16:15:44 -0700, Jeff Liebermann <jeffl@cruzio.com> >>>> wrote:

    On Tue, 09 Jun 2026 12:16:26 -0400, joegwinn@comcast.net wrote:

    On Mon, 08 Jun 2026 10:47:07 -0700, john larkin <jl@glen--canyon.com> >>>>>> wrote:

    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>> wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    <snip>

    And yes, nerve impulses are assumed move about a meter per second, yet
    people play table tennis.

    One possible explanation is that nerve impulses don't move meters per
    second.

    Methinks the mechanism might be similar to measuring the speed of
    electrons in wires. Energy transmission in a wire moves at near light
    speed. Electron drift velocity in wires (the movement of individual electrons) is about 1 mm/sec, which is much slower. I suspected that
    nerve impulse transmission in bats might be similar. However, my
    analogy breaks down because nerve impulse velocity can be 1 to 100 meters/sec, which is still much slower than near light speed (3*10^8 meters/sec).

    "Nerve conduction velocity" <https://en.wikipedia.org/wiki/Nerve_conduction_velocity>
    "The speed of nerve impulse transmission ranges from about 0.5 m/s to
    over 120 m/s"

    "Bats are surprisingly fast decision makers" <https://www.sdu.dk/en/om-sdu/fakulteterne/naturvidenskab/nyheder-2015/2015_03_18_bat_decision>
    "Sometimes we also see reaction times of only 20 milliseconds in bats,
    for instance in response to loud sounds, but that is a simple reflex
    reaction that does not require brain work".

    20 msec response time isn't light speed it's a long way from 10 nsec.
    If the flying bat is on auto-pilot, then it's making 50 course
    corrections every second. Offhand, methinks that might be sufficient
    to avoid mid-air collisions with other bats. Even if 10 nsec
    resolution were possible, it would be overkill for a bat.

    Caroline Palmer's Ph.D. thesis is on the timing in skilled piano
    playing. I've got a copy.

    https://www.mcgill.ca/psychology/caroline-palmer

    Essentially the piano key has to get the hammer to hit the string within
    10msec of the desired time to let the performer get the desired
    response from the listener. She's got a very well-instrumented piano
    that let her document that.

    We probably do as well as bats in our own areas of interest.

    --
    Bill Sloman, Sydney

    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Thursday, June 11, 2026 10:32:44
    On Wed, 10 Jun 2026 12:29:23 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 10/06/2026 2:44 am, john larkin wrote:
    On Tue, 09 Jun 2026 12:16:26 -0400, joegwinn@comcast.net wrote:

    On Mon, 08 Jun 2026 10:47:07 -0700, john larkin <jl@glen--canyon.com>
    wrote:

    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info
    on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick
    this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI
    never showed up, in the first place.

    If I hadn?t stopped talking audio design seriously in about 1980, I >>>>>>> certainly would have when crappy compressed MP3s took over the world. >>>>>>>
    Golden ears, my left buttock.

    The ears are close to the brain for a reason. Golden ears don't seem to >>>>> be close to particularly good brains.

    I read a study that says that bats can correlate time between their
    ears with nanosecond resolution. Pretty good for wet stuff.

    Bats are pretty good, but that seems a bit too good. Can you find
    that study?

    Thanks,

    Joe

    Good grief, just google

    bat echolocation nanosecond

    You made the claim, you do the googling.

    It's not hard to use an internet search engine. You could take a
    class.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Thursday, June 11, 2026 10:38:33
    On Fri, 12 Jun 2026 02:00:02 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 12/06/2026 12:21 am, john larkin wrote:
    On Thu, 11 Jun 2026 14:28:44 +0100, liz@poppyrecords.invalid.invalid
    (Liz Tuddenham) wrote:

    john larkin <jl@glen--canyon.com> wrote:


    Anything less than a microsecond is astounding, inside the gooey head
    of a bat flapping its wings mid-air hunting a moth.

    To put it in perspective, a microsecond at the velocity of sound in air >>> corresponds to 0.25mm (or 0.125mm for echolocation distance
    measurement).

    If nerve impulses travel 100 m/s and a bat's ears are 2 cm apart, the
    neural delay between ears is 200 us. And that's modulated by movement,
    heartbeats, things like that.

    Maybe nature doesn't care about our opinions of how it's allowed to
    work.

    Obviously it doesn't. That doesn't excuse you from picking up
    particularly half-baked ideas about how well it might be performing and >posting them here.

    Most ideas are half-baked at first. But hostility to ideas guarantees
    that you will have none.

    We need more goofy ideas; lots more. Then we need to sift out the few
    good ones, not club them all to death on first sight.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From joegwinn@3:633/10 to All on Thursday, June 11, 2026 13:41:15
    On Wed, 10 Jun 2026 18:02:22 -0700, john larkin <jl@glen--canyon.com>
    wrote:

    On Wed, 10 Jun 2026 17:28:51 -0400, joegwinn@comcast.net wrote:

    On Tue, 09 Jun 2026 16:15:44 -0700, Jeff Liebermann <jeffl@cruzio.com> >>wrote:

    On Tue, 09 Jun 2026 12:16:26 -0400, joegwinn@comcast.net wrote:

    On Mon, 08 Jun 2026 10:47:07 -0700, john larkin <jl@glen--canyon.com> >>>>wrote:

    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info >>>>>>>>> on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick >>>>>>>>> this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI >>>>>>>>> never showed up, in the first place.

    If I hadn?t stopped talking audio design seriously in about 1980, I >>>>>>>> certainly would have when crappy compressed MP3s took over the world. >>>>>>>>
    Golden ears, my left buttock.

    The ears are close to the brain for a reason. Golden ears don't seem to >>>>>>be close to particularly good brains.

    I read a study that says that bats can correlate time between their >>>>>ears with nanosecond resolution. Pretty good for wet stuff.

    Bats are pretty good, but that seems a bit too good. Can you find
    that study?

    "The transfer function of a target limits the jitter detection
    threshold with signals of echolocating FM-bats" >>><https://pubmed.ncbi.nlm.nih.gov/16395614/>
    "Some investigators have obtained results indicating that bats are
    able to discriminate alternations in delay down to 10 ns, which
    appears incredible for purely physical reasons."

    "Bat sonar: an alternative interpretation of the 10-ns jitter result" >>><https://pubmed.ncbi.nlm.nih.gov/9528108/>
    "In 1990 Simmons et al. reported evidence of a time resolution
    hitherto unknown in any animal, namely a 10-ns jitter detection
    threshold in echolocating bats."

    Google Scholar produces additional papers on bat echolocation acuity: >>><https://scholar.google.com/scholar?q=bat%20echolocation%2010%20nsec>

    So that's a source of the 10ns stuff. The theory is that there was an >>instrumentation error, which is certainly plausible as no biological
    system is that fast, so biological researchers are far out of their
    domain for sure.

    Why do you say that no biological system can be that fast?

    I did not say that, although it was widely believed in the past.


    Anything less than a microsecond is astounding, inside the gooey head
    of a bat flapping its wings mid-air hunting a moth.

    Yes.


    Joe

    PS: The 100,000 rpm spinner in biology is "ATP Synthase", the enzyme >>system that converts between ADP and ATP in the mitochondria (in
    animals) and chloroplasts (in plants).

    .<https://en.wikipedia.org/wiki/ATP_synthase>

    JMG


    DNA helicase, the little gadget that splits our DNA when a cell
    divides, spins at about 10,000 RPM.

    <Rotating biological motors were declared to be impossible, and
    rotating flagellum were known to be optical illusions.> Once.

    Google the <> above.


    Yes. It's true that this was believed back in the day when no
    microscope of the day could see these little motors.

    There were ways to determine the arrangement of atoms in crystals
    (X-ray diffraction), and it was possible to analyze such motors to the
    degree that they could be made to form good crystals. The motor
    assemblies are 10 to 15 nanometers across. Modern electron
    microscopes can see them directly as little blobs, but one cannot
    figure out the mechanism without using other kinds of data.

    Joe

    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Thursday, June 11, 2026 10:46:32
    On Fri, 12 Jun 2026 01:57:15 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 12/06/2026 12:12 am, john larkin wrote:
    On Thu, 11 Jun 2026 17:13:17 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 11/06/2026 3:29 pm, john larkin wrote:
    On Wed, 10 Jun 2026 19:32:15 -0700, Jeff Liebermann <jeffl@cruzio.com> >>>> wrote:

    On Wed, 10 Jun 2026 17:28:51 -0400, joegwinn@comcast.net wrote:

    On Tue, 09 Jun 2026 16:15:44 -0700, Jeff Liebermann <jeffl@cruzio.com> >>>>>> wrote:

    On Tue, 09 Jun 2026 12:16:26 -0400, joegwinn@comcast.net wrote:

    On Mon, 08 Jun 2026 10:47:07 -0700, john larkin <jl@glen--canyon.com> >>>>>>>> wrote:

    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>>>> wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote: >>>>>>>>>>>> legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    <snip>

    Sigh. I initially mentioned that there might have been some confusion >>>>> between response time and jitter. Now, you add DNA replication to the >>>>> confusion. Time for a sanity check.

    What got my attention was the radical difference between the alleged >>>>> 10 nsec nervous response time in bats, and the much slower nerve
    conduction times in humans. (I couldn't find specific numbers for
    bats).

    "Nerve conduction velocity"
    <https://en.wikipedia.org/wiki/Nerve_conduction_velocity>
    "The speed of nerve impulse transmission ranges from about 0.5 m/s to >>>>> over 120 m/s".

    I once watched a "cloud" of fruit bats emerging from the trees at
    dusk:
    <https://en.wikipedia.org/wiki/Egyptian_fruit_bat>
    I don't know how many there were, but my guess(tm) is in the
    thousands. The bats were not using their sonar for locating moths.
    Instead, they were looking for fruit and using their sonar to prevent >>>>> mid-air collisions. I watched carefully and didn't see any collisions >>>>> or bats falling from the sky. In order to do that, the muscles that >>>>> move the bats wings need to quickly respond to brain signals and the >>>>> muscles need to move quite fast. 10 nsec response time isn't going to >>>>> work when the signals move at 0.5 m/s to over 120 m/s. A nerve
    impulse moves at perhaps 1 meter/sec (or 10 nanometers in 10
    nanoseconds). A 10 nsec nerve impulse will have moved a microscopic >>>>> distance.

    For the record, I said "nanosecond resolution" not 10 nanoseconds.

    But it is still nonsense.

    And yes, nerve impulses are assumed move about a meter per second, yet >>>> people play table tennis.

    One possible explanation is that nerve impulses don't move meters per
    second.

    Possible, but not plausible. People have been measuring nerve impulse
    speed for quite a while now.

    They measure what's easy to measure, an electrical impulse. Maybe
    that's not the information being sent.

    The electrical impulse isn't all that easy to measure, but at least it
    is visible, if you measure carefully enough.

    You can hypothesise all sorts of magic connections, but until you spell
    out what one of them might be and how you'd measure it, you are just
    going in for hand-waving mysticism.

    It all looks very as if you got caught being even stupider than usual,
    and are now trying to back off.

    Not a bit. Maybe a complex chemical message travels very fast, and the electrical pulse is a system refresh that chases it.

    That would be harder to detect, especially if one wasn't looking for
    it.

    Have you read "Finding The Mother Tree"? It would be fun to instrument
    those fungi filaments in real time.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Thursday, June 11, 2026 10:58:33
    On Thu, 11 Jun 2026 09:16:05 -0700, Jeff Liebermann <jeffl@cruzio.com>
    wrote:

    On Wed, 10 Jun 2026 22:29:45 -0700, john larkin <jl@glen--canyon.com>
    wrote:

    On Wed, 10 Jun 2026 19:32:15 -0700, Jeff Liebermann <jeffl@cruzio.com> >>wrote:

    On Wed, 10 Jun 2026 17:28:51 -0400, joegwinn@comcast.net wrote:

    On Tue, 09 Jun 2026 16:15:44 -0700, Jeff Liebermann <jeffl@cruzio.com> >>>>wrote:

    On Tue, 09 Jun 2026 12:16:26 -0400, joegwinn@comcast.net wrote:

    On Mon, 08 Jun 2026 10:47:07 -0700, john larkin <jl@glen--canyon.com> >>>>>>wrote:

    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>>wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info >>>>>>>>>>> on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick >>>>>>>>>>> this up in time to remove the TI part number from your list >>>>>>>>>>> of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI >>>>>>>>>>> never showed up, in the first place.

    If I hadn?t stopped talking audio design seriously in about 1980, I >>>>>>>>>> certainly would have when crappy compressed MP3s took over the world.

    Golden ears, my left buttock.

    The ears are close to the brain for a reason. Golden ears don't seem to
    be close to particularly good brains.

    I read a study that says that bats can correlate time between their >>>>>>>ears with nanosecond resolution. Pretty good for wet stuff.

    Bats are pretty good, but that seems a bit too good. Can you find >>>>>>that study?

    "The transfer function of a target limits the jitter detection >>>>>threshold with signals of echolocating FM-bats" >>>>><https://pubmed.ncbi.nlm.nih.gov/16395614/>
    "Some investigators have obtained results indicating that bats are >>>>>able to discriminate alternations in delay down to 10 ns, which >>>>>appears incredible for purely physical reasons."

    "Bat sonar: an alternative interpretation of the 10-ns jitter result" >>>>><https://pubmed.ncbi.nlm.nih.gov/9528108/>
    "In 1990 Simmons et al. reported evidence of a time resolution >>>>>hitherto unknown in any animal, namely a 10-ns jitter detection >>>>>threshold in echolocating bats."

    Google Scholar produces additional papers on bat echolocation acuity: >>>>><https://scholar.google.com/scholar?q=bat%20echolocation%2010%20nsec>

    So that's a source of the 10ns stuff. The theory is that there was an >>>>instrumentation error, which is certainly plausible as no biological >>>>system is that fast, so biological researchers are far out of their >>>>domain for sure.

    It's only my best guess(tm). I didn't have much success at finding
    the oldest bat related citation that included a 10 nsec response time. >>>>Joe

    PS: The 100,000 rpm spinner in biology is "ATP Synthase", the enzyme >>>>system that converts between ADP and ATP in the mitochondria (in >>>>animals) and chloroplasts (in plants).

    .<https://en.wikipedia.org/wiki/ATP_synthase>

    JMG

    Sigh. I initially mentioned that there might have been some confusion >>>between response time and jitter. Now, you add DNA replication to the >>>confusion. Time for a sanity check.

    What got my attention was the radical difference between the alleged
    10 nsec nervous response time in bats, and the much slower nerve >>>conduction times in humans. (I couldn't find specific numbers for
    bats).

    "Nerve conduction velocity" >>><https://en.wikipedia.org/wiki/Nerve_conduction_velocity>
    "The speed of nerve impulse transmission ranges from about 0.5 m/s to >>>over 120 m/s".

    I once watched a "cloud" of fruit bats emerging from the trees at
    dusk:
    <https://en.wikipedia.org/wiki/Egyptian_fruit_bat>
    I don't know how many there were, but my guess(tm) is in the
    thousands. The bats were not using their sonar for locating moths. >>>Instead, they were looking for fruit and using their sonar to prevent >>>mid-air collisions. I watched carefully and didn't see any collisions
    or bats falling from the sky. In order to do that, the muscles that
    move the bats wings need to quickly respond to brain signals and the >>>muscles need to move quite fast. 10 nsec response time isn't going to >>>work when the signals move at 0.5 m/s to over 120 m/s. A nerve
    impulse moves at perhaps 1 meter/sec (or 10 nanometers in 10 >>>nanoseconds). A 10 nsec nerve impulse will have moved a microscopic >>>distance.

    For the record, I said "nanosecond resolution" not 10 nanoseconds.

    True. Please note that the URL's I provided were not in response to
    your posting. I was responding to a question by joegwinn@comcast.net: >Message-ID: <bueg2l5gtditthqkhv407dcr924p5c07qd@4ax.com>
    "Bats are pretty good, but that seems a bit too good. Can you find
    that study?"

    And yes, nerve impulses are assumed move about a meter per second, yet >>people play table tennis.

    One possible explanation is that nerve impulses don't move meters per >>second.

    Methinks the mechanism might be similar to measuring the speed of
    electrons in wires. Energy transmission in a wire moves at near light
    speed. Electron drift velocity in wires (the movement of individual >electrons) is about 1 mm/sec, which is much slower. I suspected that
    nerve impulse transmission in bats might be similar. However, my
    analogy breaks down because nerve impulse velocity can be 1 to 100 >meters/sec, which is still much slower than near light speed (3*10^8 >meters/sec).

    "Nerve conduction velocity" ><https://en.wikipedia.org/wiki/Nerve_conduction_velocity>
    "The speed of nerve impulse transmission ranges from about 0.5 m/s to
    over 120 m/s"

    "Bats are surprisingly fast decision makers" ><https://www.sdu.dk/en/om-sdu/fakulteterne/naturvidenskab/nyheder-2015/2015_03_18_bat_decision>
    "Sometimes we also see reaction times of only 20 milliseconds in bats,
    for instance in response to loud sounds, but that is a simple reflex
    reaction that does not require brain work".

    20 msec response time isn't light speed it's a long way from 10 nsec.
    If the flying bat is on auto-pilot, then it's making 50 course
    corrections every second. Offhand, methinks that might be sufficient
    to avoid mid-air collisions with other bats. Even if 10 nsec
    resolution were possible, it would be overkill for a bat.

    Some things happen locally, in the spinal cord or even closer to the
    action, without having to send messages to the head and back. The
    spinal cord is really just a part of the brain.

    But some things, like hitting a baseball, must use an eye-brain-muscle
    path fast.

    I surprise myself at how fast I can catch something that I drop. This
    morning I trapped an orange between the countertop and my belly, in a
    fraction of a second. Something decided that the belly would work
    better than a hand.

    I once caught a hot soldering iron in mid-air. Just once. Now
    something tells my muscles to grab oranges but not soldering irons.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From joegwinn@3:633/10 to All on Thursday, June 11, 2026 14:02:29
    On Wed, 10 Jun 2026 19:32:15 -0700, Jeff Liebermann <jeffl@cruzio.com>
    wrote:

    On Wed, 10 Jun 2026 17:28:51 -0400, joegwinn@comcast.net wrote:

    On Tue, 09 Jun 2026 16:15:44 -0700, Jeff Liebermann <jeffl@cruzio.com> >>wrote:

    On Tue, 09 Jun 2026 12:16:26 -0400, joegwinn@comcast.net wrote:

    On Mon, 08 Jun 2026 10:47:07 -0700, john larkin <jl@glen--canyon.com> >>>>wrote:

    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info >>>>>>>>> on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick >>>>>>>>> this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI >>>>>>>>> never showed up, in the first place.

    If I hadn?t stopped talking audio design seriously in about 1980, I >>>>>>>> certainly would have when crappy compressed MP3s took over the world. >>>>>>>>
    Golden ears, my left buttock.

    The ears are close to the brain for a reason. Golden ears don't seem to >>>>>>be close to particularly good brains.

    I read a study that says that bats can correlate time between their >>>>>ears with nanosecond resolution. Pretty good for wet stuff.

    Bats are pretty good, but that seems a bit too good. Can you find
    that study?

    "The transfer function of a target limits the jitter detection
    threshold with signals of echolocating FM-bats" >>><https://pubmed.ncbi.nlm.nih.gov/16395614/>
    "Some investigators have obtained results indicating that bats are
    able to discriminate alternations in delay down to 10 ns, which
    appears incredible for purely physical reasons."

    "Bat sonar: an alternative interpretation of the 10-ns jitter result" >>><https://pubmed.ncbi.nlm.nih.gov/9528108/>
    "In 1990 Simmons et al. reported evidence of a time resolution
    hitherto unknown in any animal, namely a 10-ns jitter detection
    threshold in echolocating bats."

    Google Scholar produces additional papers on bat echolocation acuity: >>><https://scholar.google.com/scholar?q=bat%20echolocation%2010%20nsec>

    So that's a source of the 10ns stuff. The theory is that there was an >>instrumentation error, which is certainly plausible as no biological
    system is that fast, so biological researchers are far out of their
    domain for sure.

    It's only my best guess(tm). I didn't have much success at finding
    the oldest bat related citation that included a 10 nsec response time.

    We did find it after all.


    Joe

    PS: The 100,000 rpm spinner in biology is "ATP Synthase", the enzyme >>system that converts between ADP and ATP in the mitochondria (in
    animals) and chloroplasts (in plants).

    .<https://en.wikipedia.org/wiki/ATP_synthase>

    JMG

    Sigh. I initially mentioned that there might have been some confusion >between response time and jitter. Now, you add DNA replication to the >confusion. Time for a sanity check.

    What got my attention was the radical difference between the alleged
    10 nsec nervous response time in bats, and the much slower nerve
    conduction times in humans. (I couldn't find specific numbers for
    bats).

    "Nerve conduction velocity" ><https://en.wikipedia.org/wiki/Nerve_conduction_velocity>
    "The speed of nerve impulse transmission ranges from about 0.5 m/s to
    over 120 m/s".

    These are directly measured values, taken in a wet lab.


    I once watched a "cloud" of fruit bats emerging from the trees at
    dusk:
    <https://en.wikipedia.org/wiki/Egyptian_fruit_bat>
    I don't know how many there were, but my guess(tm) is in the
    thousands. The bats were not using their sonar for locating moths.
    Instead, they were looking for fruit and using their sonar to prevent
    mid-air collisions. I watched carefully and didn't see any collisions
    or bats falling from the sky. In order to do that, the muscles that
    move the bats wings need to quickly respond to brain signals and the
    muscles need to move quite fast. 10 nsec response time isn't going to
    work when the signals move at 0.5 m/s to over 120 m/s. A nerve
    impulse moves at perhaps 1 meter/sec (or 10 nanometers in 10
    nanoseconds). A 10 nsec nerve impulse will have moved a microscopic >distance.

    Yes. There is a relevant visual example in birds, a murmuration of
    sparrows is famous. Starling murmuration creates incredible aerial
    display, Israel, from euronews:
    <https://www.youtube.com/watch?v=w6KmWzVe8n0>

    Hearing not required. I think the control law has been figured out
    for schooling fish, and it's quite simple.

    Joe

    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Thursday, June 11, 2026 11:03:52
    On Thu, 11 Jun 2026 13:41:15 -0400, joegwinn@comcast.net wrote:

    On Wed, 10 Jun 2026 18:02:22 -0700, john larkin <jl@glen--canyon.com>
    wrote:

    On Wed, 10 Jun 2026 17:28:51 -0400, joegwinn@comcast.net wrote:

    On Tue, 09 Jun 2026 16:15:44 -0700, Jeff Liebermann <jeffl@cruzio.com> >>>wrote:

    On Tue, 09 Jun 2026 12:16:26 -0400, joegwinn@comcast.net wrote:

    On Mon, 08 Jun 2026 10:47:07 -0700, john larkin <jl@glen--canyon.com> >>>>>wrote:

    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info >>>>>>>>>> on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick >>>>>>>>>> this up in time to remove the TI part number from your list >>>>>>>>>> of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI >>>>>>>>>> never showed up, in the first place.

    If I hadn?t stopped talking audio design seriously in about 1980, I >>>>>>>>> certainly would have when crappy compressed MP3s took over the world. >>>>>>>>>
    Golden ears, my left buttock.

    The ears are close to the brain for a reason. Golden ears don't seem to >>>>>>>be close to particularly good brains.

    I read a study that says that bats can correlate time between their >>>>>>ears with nanosecond resolution. Pretty good for wet stuff.

    Bats are pretty good, but that seems a bit too good. Can you find >>>>>that study?

    "The transfer function of a target limits the jitter detection >>>>threshold with signals of echolocating FM-bats" >>>><https://pubmed.ncbi.nlm.nih.gov/16395614/>
    "Some investigators have obtained results indicating that bats are
    able to discriminate alternations in delay down to 10 ns, which
    appears incredible for purely physical reasons."

    "Bat sonar: an alternative interpretation of the 10-ns jitter result" >>>><https://pubmed.ncbi.nlm.nih.gov/9528108/>
    "In 1990 Simmons et al. reported evidence of a time resolution
    hitherto unknown in any animal, namely a 10-ns jitter detection >>>>threshold in echolocating bats."

    Google Scholar produces additional papers on bat echolocation acuity: >>>><https://scholar.google.com/scholar?q=bat%20echolocation%2010%20nsec>

    So that's a source of the 10ns stuff. The theory is that there was an >>>instrumentation error, which is certainly plausible as no biological >>>system is that fast, so biological researchers are far out of their >>>domain for sure.

    Why do you say that no biological system can be that fast?

    I did not say that, although it was widely believed in the past.


    Anything less than a microsecond is astounding, inside the gooey head
    of a bat flapping its wings mid-air hunting a moth.

    Yes.


    Joe

    PS: The 100,000 rpm spinner in biology is "ATP Synthase", the enzyme >>>system that converts between ADP and ATP in the mitochondria (in
    animals) and chloroplasts (in plants).

    .<https://en.wikipedia.org/wiki/ATP_synthase>

    JMG


    DNA helicase, the little gadget that splits our DNA when a cell
    divides, spins at about 10,000 RPM.

    <Rotating biological motors were declared to be impossible, and
    rotating flagellum were known to be optical illusions.> Once.

    Google the <> above.


    Yes. It's true that this was believed back in the day when no
    microscope of the day could see these little motors.

    There were ways to determine the arrangement of atoms in crystals
    (X-ray diffraction), and it was possible to analyze such motors to the
    degree that they could be made to form good crystals. The motor
    assemblies are 10 to 15 nanometers across. Modern electron
    microscopes can see them directly as little blobs, but one cannot
    figure out the mechanism without using other kinds of data.

    Joe

    The breakthrough was that somebody glued a flagellum down and saw the
    bacteria rotate.

    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From John R Walliker@3:633/10 to All on Thursday, June 11, 2026 21:14:10
    On 11/06/2026 15:21, john larkin wrote:
    On Thu, 11 Jun 2026 14:28:44 +0100, liz@poppyrecords.invalid.invalid
    (Liz Tuddenham) wrote:

    john larkin <jl@glen--canyon.com> wrote:


    Anything less than a microsecond is astounding, inside the gooey head
    of a bat flapping its wings mid-air hunting a moth.

    To put it in perspective, a microsecond at the velocity of sound in air
    corresponds to 0.25mm (or 0.125mm for echolocation distance
    measurement).

    If nerve impulses travel 100 m/s and a bat's ears are 2 cm apart, the
    neural delay between ears is 200 us. And that's modulated by movement, heartbeats, things like that.

    Maybe nature doesn't care about our opinions of how it's allowed to
    work.

    The neurons from each ear merge together in the brainstem in
    humans and undoubtedly also in bats. Once signals from each
    ear are running alongside each other there is plenty of
    opportunity for cross correlation between the ears to take place.
    There is evidence that this takes place, but it is around 25
    to 30 years since I was involved in auditory research, so I
    can't immediately pull out the references.
    John


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics


    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From joegwinn@3:633/10 to All on Thursday, June 11, 2026 19:32:28
    On Thu, 11 Jun 2026 11:03:52 -0700, john larkin <jl@glen--canyon.com>
    wrote:

    On Thu, 11 Jun 2026 13:41:15 -0400, joegwinn@comcast.net wrote:

    On Wed, 10 Jun 2026 18:02:22 -0700, john larkin <jl@glen--canyon.com> >>wrote:

    On Wed, 10 Jun 2026 17:28:51 -0400, joegwinn@comcast.net wrote:

    On Tue, 09 Jun 2026 16:15:44 -0700, Jeff Liebermann <jeffl@cruzio.com> >>>>wrote:

    On Tue, 09 Jun 2026 12:16:26 -0400, joegwinn@comcast.net wrote:

    On Mon, 08 Jun 2026 10:47:07 -0700, john larkin <jl@glen--canyon.com> >>>>>>wrote:

    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>>wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info >>>>>>>>>>> on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick >>>>>>>>>>> this up in time to remove the TI part number from your list >>>>>>>>>>> of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI >>>>>>>>>>> never showed up, in the first place.

    If I hadn?t stopped talking audio design seriously in about 1980, I >>>>>>>>>> certainly would have when crappy compressed MP3s took over the world.

    Golden ears, my left buttock.

    The ears are close to the brain for a reason. Golden ears don't seem to
    be close to particularly good brains.

    I read a study that says that bats can correlate time between their >>>>>>>ears with nanosecond resolution. Pretty good for wet stuff.

    Bats are pretty good, but that seems a bit too good. Can you find >>>>>>that study?

    "The transfer function of a target limits the jitter detection >>>>>threshold with signals of echolocating FM-bats" >>>>><https://pubmed.ncbi.nlm.nih.gov/16395614/>
    "Some investigators have obtained results indicating that bats are >>>>>able to discriminate alternations in delay down to 10 ns, which >>>>>appears incredible for purely physical reasons."

    "Bat sonar: an alternative interpretation of the 10-ns jitter result" >>>>><https://pubmed.ncbi.nlm.nih.gov/9528108/>
    "In 1990 Simmons et al. reported evidence of a time resolution >>>>>hitherto unknown in any animal, namely a 10-ns jitter detection >>>>>threshold in echolocating bats."

    Google Scholar produces additional papers on bat echolocation acuity: >>>>><https://scholar.google.com/scholar?q=bat%20echolocation%2010%20nsec>

    So that's a source of the 10ns stuff. The theory is that there was an >>>>instrumentation error, which is certainly plausible as no biological >>>>system is that fast, so biological researchers are far out of their >>>>domain for sure.

    Why do you say that no biological system can be that fast?

    I did not say that, although it was widely believed in the past.


    Anything less than a microsecond is astounding, inside the gooey head
    of a bat flapping its wings mid-air hunting a moth.

    Yes.


    Joe

    PS: The 100,000 rpm spinner in biology is "ATP Synthase", the enzyme >>>>system that converts between ADP and ATP in the mitochondria (in >>>>animals) and chloroplasts (in plants).

    .<https://en.wikipedia.org/wiki/ATP_synthase>

    JMG


    DNA helicase, the little gadget that splits our DNA when a cell
    divides, spins at about 10,000 RPM.

    <Rotating biological motors were declared to be impossible, and
    rotating flagellum were known to be optical illusions.> Once.

    Google the <> above.


    Yes. It's true that this was believed back in the day when no
    microscope of the day could see these little motors.

    There were ways to determine the arrangement of atoms in crystals
    (X-ray diffraction), and it was possible to analyze such motors to the >>degree that they could be made to form good crystals. The motor
    assemblies are 10 to 15 nanometers across. Modern electron
    microscopes can see them directly as little blobs, but one cannot
    figure out the mechanism without using other kinds of data.

    Joe

    The breakthrough was that somebody glued a flagellum down and saw the >bacteria rotate.

    Yes, that was irrefutable. Even if they could not see what was going
    on.

    I do recall the initial announcement of the effect of tethering the
    flagellum to a surface - the bacteria rotated at a few Hz. Ended that
    debate.

    Joe

    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Friday, June 12, 2026 14:18:39
    On 12/06/2026 3:32 am, john larkin wrote:
    On Wed, 10 Jun 2026 12:29:23 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 10/06/2026 2:44 am, john larkin wrote:
    On Tue, 09 Jun 2026 12:16:26 -0400, joegwinn@comcast.net wrote:

    On Mon, 08 Jun 2026 10:47:07 -0700, john larkin <jl@glen--canyon.com>
    wrote:

    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>> wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote:
    legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info >>>>>>>>> on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick >>>>>>>>> this up in time to remove the TI part number from your list
    of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI >>>>>>>>> never showed up, in the first place.

    If I hadn?t stopped talking audio design seriously in about 1980, I >>>>>>>> certainly would have when crappy compressed MP3s took over the world. >>>>>>>>
    Golden ears, my left buttock.

    The ears are close to the brain for a reason. Golden ears don't seem to >>>>>> be close to particularly good brains.

    I read a study that says that bats can correlate time between their
    ears with nanosecond resolution. Pretty good for wet stuff.

    Bats are pretty good, but that seems a bit too good. Can you find
    that study?

    Thanks,

    Joe

    Good grief, just google

    bat echolocation nanosecond

    You made the claim, you do the googling.

    It's not hard to use an internet search engine. You could take a
    class.

    It certainly isn't hard, and I'm better at it than you are. The problem
    is the time it takes to filter out the irrelevant nonsense (and you
    don't spend enough time on that, perhaps because you lack the relevant skills). Its you who needs the class in critical thinking, but since you haven't got a clue what that might be, you aren't going to enroll any
    time soon.

    --
    Bill Sloman, Sydney


    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Friday, June 12, 2026 16:34:22
    On 12/06/2026 3:38 am, john larkin wrote:
    On Fri, 12 Jun 2026 02:00:02 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 12/06/2026 12:21 am, john larkin wrote:
    On Thu, 11 Jun 2026 14:28:44 +0100, liz@poppyrecords.invalid.invalid
    (Liz Tuddenham) wrote:

    john larkin <jl@glen--canyon.com> wrote:


    Anything less than a microsecond is astounding, inside the gooey head >>>>> of a bat flapping its wings mid-air hunting a moth.

    To put it in perspective, a microsecond at the velocity of sound in air >>>> corresponds to 0.25mm (or 0.125mm for echolocation distance
    measurement).

    If nerve impulses travel 100 m/s and a bat's ears are 2 cm apart, the
    neural delay between ears is 200 us. And that's modulated by movement,
    heartbeats, things like that.

    Maybe nature doesn't care about our opinions of how it's allowed to
    work.

    Obviously it doesn't. That doesn't excuse you from picking up
    particularly half-baked ideas about how well it might be performing and
    posting them here.

    Most ideas are half-baked at first. But hostility to ideas guarantees
    that you will have none.

    I've got three patents. You've got your name on one. I'm demonstrably
    not hostile to new ideas, if they are any good. This isn't any kind of brain-storming venue, and your attitude is more "gullible sucker" than "receptive to novel ideas".

    We need more goofy ideas; lots more. Then we need to sift out the few
    good ones, not club them all to death on first sight.

    You might. Talented people come up actual patentable ideas quite
    frequently. My father and two of my friends have all managed about 25
    each over their careers. People like that can afford to winnow out the nonsense early - probably because they are whole lot better at it than
    you seem to be.

    --
    Bill Sloman, Sydney


    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Friday, June 12, 2026 16:46:39
    On 12/06/2026 3:46 am, john larkin wrote:
    On Fri, 12 Jun 2026 01:57:15 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 12/06/2026 12:12 am, john larkin wrote:
    On Thu, 11 Jun 2026 17:13:17 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 11/06/2026 3:29 pm, john larkin wrote:
    On Wed, 10 Jun 2026 19:32:15 -0700, Jeff Liebermann <jeffl@cruzio.com> >>>>> wrote:

    On Wed, 10 Jun 2026 17:28:51 -0400, joegwinn@comcast.net wrote:

    On Tue, 09 Jun 2026 16:15:44 -0700, Jeff Liebermann <jeffl@cruzio.com> >>>>>>> wrote:

    On Tue, 09 Jun 2026 12:16:26 -0400, joegwinn@comcast.net wrote: >>>>>>>>
    On Mon, 08 Jun 2026 10:47:07 -0700, john larkin <jl@glen--canyon.com> >>>>>>>>> wrote:

    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote: >>>>>>>>>>>>> legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    <snip>

    Sigh. I initially mentioned that there might have been some confusion >>>>>> between response time and jitter. Now, you add DNA replication to the >>>>>> confusion. Time for a sanity check.

    What got my attention was the radical difference between the alleged >>>>>> 10 nsec nervous response time in bats, and the much slower nerve
    conduction times in humans. (I couldn't find specific numbers for >>>>>> bats).

    "Nerve conduction velocity"
    <https://en.wikipedia.org/wiki/Nerve_conduction_velocity>
    "The speed of nerve impulse transmission ranges from about 0.5 m/s to >>>>>> over 120 m/s".

    I once watched a "cloud" of fruit bats emerging from the trees at
    dusk:
    <https://en.wikipedia.org/wiki/Egyptian_fruit_bat>
    I don't know how many there were, but my guess(tm) is in the
    thousands. The bats were not using their sonar for locating moths. >>>>>> Instead, they were looking for fruit and using their sonar to prevent >>>>>> mid-air collisions. I watched carefully and didn't see any collisions >>>>>> or bats falling from the sky. In order to do that, the muscles that >>>>>> move the bats wings need to quickly respond to brain signals and the >>>>>> muscles need to move quite fast. 10 nsec response time isn't going to >>>>>> work when the signals move at 0.5 m/s to over 120 m/s. A nerve
    impulse moves at perhaps 1 meter/sec (or 10 nanometers in 10
    nanoseconds). A 10 nsec nerve impulse will have moved a microscopic >>>>>> distance.

    For the record, I said "nanosecond resolution" not 10 nanoseconds.

    But it is still nonsense.

    And yes, nerve impulses are assumed move about a meter per second, yet >>>>> people play table tennis.

    One possible explanation is that nerve impulses don't move meters per >>>>> second.

    Possible, but not plausible. People have been measuring nerve impulse
    speed for quite a while now.

    They measure what's easy to measure, an electrical impulse. Maybe
    that's not the information being sent.

    The electrical impulse isn't all that easy to measure, but at least it
    is visible, if you measure carefully enough.

    You can hypothesise all sorts of magic connections, but until you spell
    out what one of them might be and how you'd measure it, you are just
    going in for hand-waving mysticism.

    It all looks very as if you got caught being even stupider than usual,
    and are now trying to back off.

    Not a bit. Maybe a complex chemical message travels very fast, and the electrical pulse is a system refresh that chases it.

    And pigs might fly. The "electrical impulse" we can see is generated by changing sodium, and potassium concentrations. That is simple chemical messaging, with single ions moving about. More complex molecules aren't
    going to move any faster.

    That would be harder to detect, especially if one wasn't looking for
    it.

    Have you read "Finding The Mother Tree"? It would be fun to instrument
    those fungi filaments in real time.

    You have a strange idea of fun. They are all buried underground in an incoherent mess. and the signalling is all going to changes in the concentrations of chemicals.

    We can dream of finding a long chain molecule that isomerises rapdily
    from end to end in a series of tiny local bond shifts, but evolution has
    been looking for that for a couple pf billion years now and doesn't seem
    to have found it.

    --
    Bill Sloman, Sydney



    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Friday, June 12, 2026 17:08:08
    On 12/06/2026 3:58 am, john larkin wrote:
    On Thu, 11 Jun 2026 09:16:05 -0700, Jeff Liebermann <jeffl@cruzio.com>
    wrote:

    On Wed, 10 Jun 2026 22:29:45 -0700, john larkin <jl@glen--canyon.com>
    wrote:

    On Wed, 10 Jun 2026 19:32:15 -0700, Jeff Liebermann <jeffl@cruzio.com>
    wrote:

    On Wed, 10 Jun 2026 17:28:51 -0400, joegwinn@comcast.net wrote:

    On Tue, 09 Jun 2026 16:15:44 -0700, Jeff Liebermann <jeffl@cruzio.com> >>>>> wrote:

    On Tue, 09 Jun 2026 12:16:26 -0400, joegwinn@comcast.net wrote:

    On Mon, 08 Jun 2026 10:47:07 -0700, john larkin <jl@glen--canyon.com> >>>>>>> wrote:

    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>>> wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote: >>>>>>>>>>> legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    <snip>

    20 msec response time isn't light speed it's a long way from 10 nsec.
    If the flying bat is on auto-pilot, then it's making 50 course
    corrections every second. Offhand, methinks that might be sufficient
    to avoid mid-air collisions with other bats. Even if 10 nsec
    resolution were possible, it would be overkill for a bat.

    Some things happen locally, in the spinal cord or even closer to the
    action, without having to send messages to the head and back. The
    spinal cord is really just a part of the brain.

    But some things, like hitting a baseball, must use an eye-brain-muscle
    path fast.

    I surprise myself at how fast I can catch something that I drop. This
    morning I trapped an orange between the countertop and my belly, in a fraction of a second. Something decided that the belly would work
    better than a hand.

    There's a simple version of that.

    https://www.bbc.co.uk/bitesize/guides/zpkhcj6/revision/3

    Anything under 120msec is extraordinarily fast. About 180msec is typical.

    I once caught a hot soldering iron in mid-air. Just once. Now
    something tells my muscles to grab oranges but not soldering irons.

    One-trial learning happens.

    --
    Bill Sloman, Sydney


    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Liz Tuddenham@3:633/10 to All on Friday, June 12, 2026 13:45:07
    john larkin <jl@glen--canyon.com> wrote:


    I surprise myself at how fast I can catch something that I drop. This
    morning I trapped an orange between the countertop and my belly, in a fraction of a second. Something decided that the belly would work
    better than a hand.

    Whwn I started work in a radio factory I had to train myself NOT to
    catch things thrown at me - they were sometimes fully-charged 500v
    capacitors.

    When I later worked in a laboratory, the chief technician shouted
    "catch" as he threw a 1-litre round-bottomed flask at me; I stood still
    and watched it shatter on the floor. He was most upset.


    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk

    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Friday, June 12, 2026 07:36:31
    On Fri, 12 Jun 2026 16:34:22 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 12/06/2026 3:38 am, john larkin wrote:
    On Fri, 12 Jun 2026 02:00:02 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 12/06/2026 12:21 am, john larkin wrote:
    On Thu, 11 Jun 2026 14:28:44 +0100, liz@poppyrecords.invalid.invalid
    (Liz Tuddenham) wrote:

    john larkin <jl@glen--canyon.com> wrote:


    Anything less than a microsecond is astounding, inside the gooey head >>>>>> of a bat flapping its wings mid-air hunting a moth.

    To put it in perspective, a microsecond at the velocity of sound in air >>>>> corresponds to 0.25mm (or 0.125mm for echolocation distance
    measurement).

    If nerve impulses travel 100 m/s and a bat's ears are 2 cm apart, the
    neural delay between ears is 200 us. And that's modulated by movement, >>>> heartbeats, things like that.

    Maybe nature doesn't care about our opinions of how it's allowed to
    work.

    Obviously it doesn't. That doesn't excuse you from picking up
    particularly half-baked ideas about how well it might be performing and
    posting them here.

    Most ideas are half-baked at first. But hostility to ideas guarantees
    that you will have none.

    I've got three patents. You've got your name on one. I'm demonstrably
    not hostile to new ideas, if they are any good. This isn't any kind of >brain-storming venue, and your attitude is more "gullible sucker" than >"receptive to novel ideas".

    We need more goofy ideas; lots more. Then we need to sift out the few
    good ones, not club them all to death on first sight.

    You might. Talented people come up actual patentable ideas quite
    frequently. My father and two of my friends have all managed about 25
    each over their careers. People like that can afford to winnow out the >nonsense early - probably because they are whole lot better at it than
    you seem to be.

    Patents are mostly silly ego trips or VC hype. About half are
    abandoned. Only a couple per cent earn more than they cost.

    I'd rather design stuff and sell it. I know of only two cases where
    someone copied our designs, and both are out of business now.




    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Friday, June 12, 2026 07:42:06
    On Fri, 12 Jun 2026 13:45:07 +0100, liz@poppyrecords.invalid.invalid
    (Liz Tuddenham) wrote:

    john larkin <jl@glen--canyon.com> wrote:


    I surprise myself at how fast I can catch something that I drop. This
    morning I trapped an orange between the countertop and my belly, in a
    fraction of a second. Something decided that the belly would work
    better than a hand.

    Whwn I started work in a radio factory I had to train myself NOT to
    catch things thrown at me - they were sometimes fully-charged 500v >capacitors.

    When I later worked in a laboratory, the chief technician shouted
    "catch" as he threw a 1-litre round-bottomed flask at me; I stood still
    and watched it shatter on the floor. He was most upset.

    I knew a guy who chewed on most everything. Someone (not me) left a
    charged cap on his desk.

    That was good long-term, reduced his lead input.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Saturday, June 13, 2026 02:31:22
    On 13/06/2026 12:36 am, john larkin wrote:
    On Fri, 12 Jun 2026 16:34:22 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 12/06/2026 3:38 am, john larkin wrote:
    On Fri, 12 Jun 2026 02:00:02 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 12/06/2026 12:21 am, john larkin wrote:
    On Thu, 11 Jun 2026 14:28:44 +0100, liz@poppyrecords.invalid.invalid >>>>> (Liz Tuddenham) wrote:

    john larkin <jl@glen--canyon.com> wrote:


    Anything less than a microsecond is astounding, inside the gooey head >>>>>>> of a bat flapping its wings mid-air hunting a moth.

    To put it in perspective, a microsecond at the velocity of sound in air >>>>>> corresponds to 0.25mm (or 0.125mm for echolocation distance
    measurement).

    If nerve impulses travel 100 m/s and a bat's ears are 2 cm apart, the >>>>> neural delay between ears is 200 us. And that's modulated by movement, >>>>> heartbeats, things like that.

    Maybe nature doesn't care about our opinions of how it's allowed to
    work.

    Obviously it doesn't. That doesn't excuse you from picking up
    particularly half-baked ideas about how well it might be performing and >>>> posting them here.

    Most ideas are half-baked at first. But hostility to ideas guarantees
    that you will have none.

    I've got three patents. You've got your name on one. I'm demonstrably
    not hostile to new ideas, if they are any good. This isn't any kind of
    brain-storming venue, and your attitude is more "gullible sucker" than
    "receptive to novel ideas".

    We need more goofy ideas; lots more. Then we need to sift out the few
    good ones, not club them all to death on first sight.

    You might. Talented people come up actual patentable ideas quite
    frequently. My father and two of my friends have all managed about 25
    each over their careers. People like that can afford to winnow out the
    nonsense early - probably because they are whole lot better at it than
    you seem to be.

    Patents are mostly silly ego trips or VC hype. About half are
    abandoned. Only a couple per cent earn more than they cost.

    Patents are expensive. That winnows out a lot of the silly ego trips and
    the VC hype. I abandoned a provisional patent (which is very cheap) when
    I realised that it was based on a misconception. On the other hand
    Tektronix abandoned a patent on a better confocal microscope that made a friend of mine $A12 million.

    They are rather like venture capital investments, where nineteen out of
    twenty fail, but the one in twenty success pays out more than the
    nineteen failures cost.

    The point about patents is that they aren't obvious to those skilled in
    the art. They are an original solution to a problem - whether the
    problem is worth solving is a different question.

    I'd rather design stuff and sell it. I know of only two cases where
    someone copied our designs, and both are out of business now.

    You'd like to design stuff and sell it. You design skills aren't
    impressive, but you do seem to be able sell what you can cobble together.

    If your design skills were more impressive your stuff might be worth
    copying.

    --
    Bill Sloman, Sydney


    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From John R Walliker@3:633/10 to All on Friday, June 12, 2026 19:25:25
    On 12/06/2026 17:31, Bill Sloman wrote:
    On 13/06/2026 12:36 am, john larkin wrote:
    On Fri, 12 Jun 2026 16:34:22 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 12/06/2026 3:38 am, john larkin wrote:
    On Fri, 12 Jun 2026 02:00:02 +1000, Bill Sloman <bill.sloman@ieee.org> >>>> wrote:

    On 12/06/2026 12:21 am, john larkin wrote:
    On Thu, 11 Jun 2026 14:28:44 +0100, liz@poppyrecords.invalid.invalid >>>>>> (Liz Tuddenham) wrote:

    john larkin <jl@glen--canyon.com> wrote:


    Anything less than a microsecond is astounding, inside the gooey >>>>>>>> head
    of a bat flapping its wings mid-air hunting a moth.

    To put it in perspective, a microsecond˙ at the velocity of sound >>>>>>> in air
    corresponds to 0.25mm (or 0.125mm for echolocation distance
    measurement).

    If nerve impulses travel 100 m/s and a bat's ears are 2 cm apart, the >>>>>> neural delay between ears is 200 us. And that's modulated by
    movement,
    heartbeats, things like that.

    Maybe nature doesn't care about our opinions of how it's allowed to >>>>>> work.

    Obviously it doesn't. That doesn't excuse you from picking up
    particularly half-baked ideas about how well it might be performing >>>>> and
    posting them here.

    Most ideas are half-baked at first. But hostility to ideas guarantees
    that you will have none.

    I've got three patents. You've got your name on one. I'm demonstrably
    not hostile to new ideas, if they are any good. This isn't any kind of
    brain-storming venue, and your attitude is more "gullible sucker" than
    "receptive to novel ideas".

    We need more goofy ideas; lots more. Then we need to sift out the few
    good ones, not club them all to death on first sight.

    You might. Talented people come up actual patentable ideas quite
    frequently. My father and two of my friends have all managed about 25
    each over their careers. People like that can afford to winnow out the
    nonsense early - probably because they are whole lot better at it than
    you seem to be.

    Patents are mostly silly ego trips or VC hype. About half are
    abandoned. Only a couple per cent earn more than they cost.

    Patents are expensive. That winnows out a lot of the silly ego trips and
    the VC hype. I abandoned a provisional patent (which is very cheap) when
    I realised that it was based on a misconception. On the other hand
    Tektronix abandoned a patent on a better confocal microscope that made a friend of mine $A12 million.

    They are rather like venture capital investments, where nineteen out of twenty fail, but the one in twenty success pays out more than the
    nineteen failures cost.

    The point about patents is that they aren't obvious to those skilled in
    the art. They are an original solution to a problem - whether the
    problem is worth solving is a different question.

    Unfortunately, there are many patents that describe prior art. They
    should not have been approved. The problem is, that if the holder has
    deep pockets you can't afford to prove that you are right.
    (I do have some myself, but never made any money from them, unlike
    "knowhow" agreements that have worked very well on occasion.)


    I'd rather design stuff and sell it. I know of only two cases where
    someone copied our designs, and both are out of business now.

    You'd like to design stuff and sell it. You design skills aren't
    impressive, but you do seem to be able sell what you can cobble together.

    If your design skills were more impressive your stuff might be worth copying.



    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From joegwinn@3:633/10 to All on Friday, June 12, 2026 14:43:45
    On Thu, 11 Jun 2026 19:32:28 -0400, joegwinn@comcast.net wrote:

    On Thu, 11 Jun 2026 11:03:52 -0700, john larkin <jl@glen--canyon.com>
    wrote:

    On Thu, 11 Jun 2026 13:41:15 -0400, joegwinn@comcast.net wrote:

    On Wed, 10 Jun 2026 18:02:22 -0700, john larkin <jl@glen--canyon.com> >>>wrote:

    On Wed, 10 Jun 2026 17:28:51 -0400, joegwinn@comcast.net wrote:

    On Tue, 09 Jun 2026 16:15:44 -0700, Jeff Liebermann <jeffl@cruzio.com> >>>>>wrote:

    On Tue, 09 Jun 2026 12:16:26 -0400, joegwinn@comcast.net wrote:

    On Mon, 08 Jun 2026 10:47:07 -0700, john larkin <jl@glen--canyon.com> >>>>>>>wrote:

    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>>>wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote: >>>>>>>>>>> legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    https://www.youtube.com/watch?v=22ZmmZ67SMY

    NE5532

    . . . . just in case somebody is actually searching for info >>>>>>>>>>>> on an actual part number.

    If you're wired into the ON/TI/NXP PCN channels, you'll pick >>>>>>>>>>>> this up in time to remove the TI part number from your list >>>>>>>>>>>> of alternates.

    Audio mfrs are pretty paranoid about sources. Chances are TI >>>>>>>>>>>> never showed up, in the first place.

    If I hadn?t stopped talking audio design seriously in about 1980, I >>>>>>>>>>> certainly would have when crappy compressed MP3s took over the world.

    Golden ears, my left buttock.

    The ears are close to the brain for a reason. Golden ears don't seem to
    be close to particularly good brains.

    I read a study that says that bats can correlate time between their >>>>>>>>ears with nanosecond resolution. Pretty good for wet stuff.

    Bats are pretty good, but that seems a bit too good. Can you find >>>>>>>that study?

    "The transfer function of a target limits the jitter detection >>>>>>threshold with signals of echolocating FM-bats" >>>>>><https://pubmed.ncbi.nlm.nih.gov/16395614/>
    "Some investigators have obtained results indicating that bats are >>>>>>able to discriminate alternations in delay down to 10 ns, which >>>>>>appears incredible for purely physical reasons."

    "Bat sonar: an alternative interpretation of the 10-ns jitter result" >>>>>><https://pubmed.ncbi.nlm.nih.gov/9528108/>
    "In 1990 Simmons et al. reported evidence of a time resolution >>>>>>hitherto unknown in any animal, namely a 10-ns jitter detection >>>>>>threshold in echolocating bats."

    Google Scholar produces additional papers on bat echolocation acuity: >>>>>><https://scholar.google.com/scholar?q=bat%20echolocation%2010%20nsec> >>>>>
    So that's a source of the 10ns stuff. The theory is that there was an >>>>>instrumentation error, which is certainly plausible as no biological >>>>>system is that fast, so biological researchers are far out of their >>>>>domain for sure.

    Why do you say that no biological system can be that fast?

    I did not say that, although it was widely believed in the past.


    Anything less than a microsecond is astounding, inside the gooey head >>>>of a bat flapping its wings mid-air hunting a moth.

    Yes.


    Joe

    PS: The 100,000 rpm spinner in biology is "ATP Synthase", the enzyme >>>>>system that converts between ADP and ATP in the mitochondria (in >>>>>animals) and chloroplasts (in plants).

    .<https://en.wikipedia.org/wiki/ATP_synthase>

    JMG


    DNA helicase, the little gadget that splits our DNA when a cell >>>>divides, spins at about 10,000 RPM.

    <Rotating biological motors were declared to be impossible, and >>>>rotating flagellum were known to be optical illusions.> Once.

    Google the <> above.


    Yes. It's true that this was believed back in the day when no
    microscope of the day could see these little motors.

    There were ways to determine the arrangement of atoms in crystals
    (X-ray diffraction), and it was possible to analyze such motors to the >>>degree that they could be made to form good crystals. The motor >>>assemblies are 10 to 15 nanometers across. Modern electron
    microscopes can see them directly as little blobs, but one cannot
    figure out the mechanism without using other kinds of data.

    Joe

    The breakthrough was that somebody glued a flagellum down and saw the >>bacteria rotate.

    Yes, that was irrefutable. Even if they could not see what was going
    on.

    I do recall the initial announcement of the effect of tethering the
    flagellum to a surface - the bacteria rotated at a few Hz. Ended that >debate.

    I dug a little deeper. Turns out that the bit about the tethered
    flagella was the news-report version, and the actual science had been
    going on for some time before.

    The big name is Howard C. Berg, who published a review article "The
    Rotary Motion of Bacterial Flagella". .<https://www.annualreviews.org/content/journals/10.1146/annurev.biochem.72.121801.161737>

    or

    .<https://www.damtp.cam.ac.uk/user/gold/pdfs/teaching/ufk_papers/membrane_proteins/bergreview.pdf>

    Joe

    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Friday, June 12, 2026 12:37:30
    On Sat, 13 Jun 2026 02:31:22 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 13/06/2026 12:36 am, john larkin wrote:
    On Fri, 12 Jun 2026 16:34:22 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 12/06/2026 3:38 am, john larkin wrote:
    On Fri, 12 Jun 2026 02:00:02 +1000, Bill Sloman <bill.sloman@ieee.org> >>>> wrote:

    On 12/06/2026 12:21 am, john larkin wrote:
    On Thu, 11 Jun 2026 14:28:44 +0100, liz@poppyrecords.invalid.invalid >>>>>> (Liz Tuddenham) wrote:

    john larkin <jl@glen--canyon.com> wrote:


    Anything less than a microsecond is astounding, inside the gooey head >>>>>>>> of a bat flapping its wings mid-air hunting a moth.

    To put it in perspective, a microsecond at the velocity of sound in air
    corresponds to 0.25mm (or 0.125mm for echolocation distance
    measurement).

    If nerve impulses travel 100 m/s and a bat's ears are 2 cm apart, the >>>>>> neural delay between ears is 200 us. And that's modulated by movement, >>>>>> heartbeats, things like that.

    Maybe nature doesn't care about our opinions of how it's allowed to >>>>>> work.

    Obviously it doesn't. That doesn't excuse you from picking up
    particularly half-baked ideas about how well it might be performing and >>>>> posting them here.

    Most ideas are half-baked at first. But hostility to ideas guarantees
    that you will have none.

    I've got three patents. You've got your name on one. I'm demonstrably
    not hostile to new ideas, if they are any good. This isn't any kind of
    brain-storming venue, and your attitude is more "gullible sucker" than
    "receptive to novel ideas".

    We need more goofy ideas; lots more. Then we need to sift out the few
    good ones, not club them all to death on first sight.

    You might. Talented people come up actual patentable ideas quite
    frequently. My father and two of my friends have all managed about 25
    each over their careers. People like that can afford to winnow out the
    nonsense early - probably because they are whole lot better at it than
    you seem to be.

    Patents are mostly silly ego trips or VC hype. About half are
    abandoned. Only a couple per cent earn more than they cost.

    Patents are expensive. That winnows out a lot of the silly ego trips and
    the VC hype. I abandoned a provisional patent (which is very cheap) when
    I realised that it was based on a misconception. On the other hand
    Tektronix abandoned a patent on a better confocal microscope that made a >friend of mine $A12 million.

    They are rather like venture capital investments, where nineteen out of >twenty fail, but the one in twenty success pays out more than the
    nineteen failures cost.

    The point about patents is that they aren't obvious to those skilled in
    the art. They are an original solution to a problem - whether the
    problem is worth solving is a different question.

    I'd rather design stuff and sell it. I know of only two cases where
    someone copied our designs, and both are out of business now.

    You'd like to design stuff and sell it. You design skills aren't
    impressive, but you do seem to be able sell what you can cobble together.

    If your design skills were more impressive your stuff might be worth >copying.

    Sounds like our designs are perfectly calibrated: good enough to sell
    but not good enough to copy.

    I used to attend some physics conferences and hang out in the bar with competitors. We'd share what we were working on. In a small market, it
    doesn't make sense to have two vendors do the same stuff.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From bitrex@3:633/10 to All on Saturday, June 13, 2026 02:03:02
    On 6/11/2026 12:50 PM, Bill Sloman wrote:
    On 12/06/2026 2:16 am, Jeff Liebermann wrote:
    On Wed, 10 Jun 2026 22:29:45 -0700, john larkin <jl@glen--canyon.com>
    wrote:

    On Wed, 10 Jun 2026 19:32:15 -0700, Jeff Liebermann <jeffl@cruzio.com>
    wrote:

    On Wed, 10 Jun 2026 17:28:51 -0400, joegwinn@comcast.net wrote:

    On Tue, 09 Jun 2026 16:15:44 -0700, Jeff Liebermann <jeffl@cruzio.com> >>>>> wrote:

    On Tue, 09 Jun 2026 12:16:26 -0400, joegwinn@comcast.net wrote:

    On Mon, 08 Jun 2026 10:47:07 -0700, john larkin <jl@glen--
    canyon.com>
    wrote:

    On Mon, 8 Jun 2026 15:44:19 +1000, Bill Sloman
    <bill.sloman@ieee.org>
    wrote:

    On 8/06/2026 4:49 am, Phil Hobbs wrote:
    Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> wrote: >>>>>>>>>>> legg <legg@nospam.magma.ca> wrote:
    On Wed, 3 Jun 2026 23:10:06 +1000, Chris Jones
    <lugnut808@spam.yahoo.com> wrote:

    <snip>

    And yes, nerve impulses are assumed move about a meter per second, yet
    people play table tennis.

    One possible explanation is that nerve impulses don't move meters per
    second.

    Methinks the mechanism might be similar to measuring the speed of
    electrons in wires.˙ Energy transmission in a wire moves at near light
    speed.˙ Electron drift velocity in wires (the movement of individual
    electrons) is about 1 mm/sec, which is much slower.˙ I suspected that
    nerve impulse transmission in bats might be similar.˙ However, my
    analogy breaks down because nerve impulse velocity can be 1 to 100
    meters/sec, which is still much slower than near light speed (3*10^8
    meters/sec).

    "Nerve conduction velocity"
    <https://en.wikipedia.org/wiki/Nerve_conduction_velocity>
    "The speed of nerve impulse transmission ranges from about 0.5 m/s to
    over 120 m/s"

    "Bats are surprisingly fast decision makers"
    <https://www.sdu.dk/en/om-sdu/fakulteterne/naturvidenskab/
    nyheder-2015/2015_03_18_bat_decision>
    "Sometimes we also see reaction times of only 20 milliseconds in bats,
    for instance in response to loud sounds, but that is a simple reflex
    reaction that does not require brain work".

    20 msec response time isn't light speed it's a long way from 10 nsec.
    If the flying bat is on auto-pilot, then it's making 50 course
    corrections every second.˙ Offhand, methinks that might be sufficient
    to avoid mid-air collisions with other bats.˙ Even if 10 nsec
    resolution were possible, it would be overkill for a bat.

    Caroline Palmer's Ph.D. thesis is on the timing in skilled piano
    playing. I've got a copy.

    https://www.mcgill.ca/psychology/caroline-palmer

    Essentially the piano key has to get the hammer to hit the string within
    ˙10msec of the desired time to let the performer get the desired
    response from the listener. She's got a very well-instrumented piano
    that let her document that.

    We probably do as well as bats in our own areas of interest.


    Incidentally around 10ms of processing delay in e.g. guitar amplifier simulation is noticeable to an experienced player. 20, 30+ ms starts to
    go from just noticeable to an annoying lag.

    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Saturday, June 13, 2026 16:32:38
    On 13/06/2026 5:37 am, john larkin wrote:
    On Sat, 13 Jun 2026 02:31:22 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 13/06/2026 12:36 am, john larkin wrote:
    On Fri, 12 Jun 2026 16:34:22 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 12/06/2026 3:38 am, john larkin wrote:
    On Fri, 12 Jun 2026 02:00:02 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>> wrote:

    On 12/06/2026 12:21 am, john larkin wrote:
    On Thu, 11 Jun 2026 14:28:44 +0100, liz@poppyrecords.invalid.invalid >>>>>>> (Liz Tuddenham) wrote:

    john larkin <jl@glen--canyon.com> wrote:

    <snip>

    If your design skills were more impressive your stuff might be worth
    copying.

    Sounds like our designs are perfectly calibrated: good enough to sell
    but not good enough to copy.

    I used to attend some physics conferences and hang out in the bar with competitors. We'd share what we were working on. In a small market, it doesn't make sense to have two vendors do the same stuff.

    The aim, as a vendor, is to have stuff that blows the competition out of
    the water. You don't seem to have the design skills that might let you
    do that. I've had some good ideas, but none of them turned out to be all
    that good. Handy in the application, but not industry changing.

    --
    Bill Sloman, Sydney




    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Sunday, June 14, 2026 15:41:35
    On Sat, 13 Jun 2026 16:32:38 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 13/06/2026 5:37 am, john larkin wrote:
    On Sat, 13 Jun 2026 02:31:22 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 13/06/2026 12:36 am, john larkin wrote:
    On Fri, 12 Jun 2026 16:34:22 +1000, Bill Sloman <bill.sloman@ieee.org> >>>> wrote:

    On 12/06/2026 3:38 am, john larkin wrote:
    On Fri, 12 Jun 2026 02:00:02 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>> wrote:

    On 12/06/2026 12:21 am, john larkin wrote:
    On Thu, 11 Jun 2026 14:28:44 +0100, liz@poppyrecords.invalid.invalid >>>>>>>> (Liz Tuddenham) wrote:

    john larkin <jl@glen--canyon.com> wrote:

    <snip>

    If your design skills were more impressive your stuff might be worth
    copying.

    Sounds like our designs are perfectly calibrated: good enough to sell
    but not good enough to copy.

    I used to attend some physics conferences and hang out in the bar with
    competitors. We'd share what we were working on. In a small market, it
    doesn't make sense to have two vendors do the same stuff.

    The aim, as a vendor, is to have stuff that blows the competition out of
    the water.

    Not me. The aim is to sell.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Monday, June 15, 2026 15:38:20
    On 15/06/2026 8:41 am, john larkin wrote:
    On Sat, 13 Jun 2026 16:32:38 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 13/06/2026 5:37 am, john larkin wrote:
    On Sat, 13 Jun 2026 02:31:22 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 13/06/2026 12:36 am, john larkin wrote:
    On Fri, 12 Jun 2026 16:34:22 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>> wrote:

    On 12/06/2026 3:38 am, john larkin wrote:
    On Fri, 12 Jun 2026 02:00:02 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>> wrote:

    On 12/06/2026 12:21 am, john larkin wrote:
    On Thu, 11 Jun 2026 14:28:44 +0100, liz@poppyrecords.invalid.invalid >>>>>>>>> (Liz Tuddenham) wrote:

    john larkin <jl@glen--canyon.com> wrote:

    <snip>

    If your design skills were more impressive your stuff might be worth
    copying.

    Sounds like our designs are perfectly calibrated: good enough to sell
    but not good enough to copy.

    I used to attend some physics conferences and hang out in the bar with
    competitors. We'd share what we were working on. In a small market, it
    doesn't make sense to have two vendors do the same stuff.

    The aim, as a vendor, is to have stuff that blows the competition out of
    the water.

    Not me. The aim is to sell.

    Having a significantly better product than your competitors does make it easier to sell. You may never have been in a position to notice this. In
    a really small market, this may not be worth the trouble.

    --
    Bill Sloman, Sydney


    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From john larkin@3:633/10 to All on Monday, June 15, 2026 08:06:40
    On Mon, 15 Jun 2026 15:38:20 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 15/06/2026 8:41 am, john larkin wrote:
    On Sat, 13 Jun 2026 16:32:38 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 13/06/2026 5:37 am, john larkin wrote:
    On Sat, 13 Jun 2026 02:31:22 +1000, Bill Sloman <bill.sloman@ieee.org> >>>> wrote:

    On 13/06/2026 12:36 am, john larkin wrote:
    On Fri, 12 Jun 2026 16:34:22 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>> wrote:

    On 12/06/2026 3:38 am, john larkin wrote:
    On Fri, 12 Jun 2026 02:00:02 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>>> wrote:

    On 12/06/2026 12:21 am, john larkin wrote:
    On Thu, 11 Jun 2026 14:28:44 +0100, liz@poppyrecords.invalid.invalid >>>>>>>>>> (Liz Tuddenham) wrote:

    john larkin <jl@glen--canyon.com> wrote:

    <snip>

    If your design skills were more impressive your stuff might be worth >>>>> copying.

    Sounds like our designs are perfectly calibrated: good enough to sell
    but not good enough to copy.

    I used to attend some physics conferences and hang out in the bar with >>>> competitors. We'd share what we were working on. In a small market, it >>>> doesn't make sense to have two vendors do the same stuff.

    The aim, as a vendor, is to have stuff that blows the competition out of >>> the water.

    Not me. The aim is to sell.

    Having a significantly better product than your competitors does make it >easier to sell. You may never have been in a position to notice this. In
    a really small market, this may not be worth the trouble.

    Sure, blowaway products help sell.

    But many customers buy stuff because it's reliable, and well
    documented, and well supported, and long-term available. That is
    especially important in the aerospace and semiconductor industries.

    And another powerful reason people will buy from other people is
    because they like one another. You may never have been in a position
    to notice this.


    John Larkin
    Highland Tech Glen Canyon Design Center
    Lunatic Fringe Electronics

    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)
  • From Bill Sloman@3:633/10 to All on Tuesday, June 16, 2026 02:01:43
    On 16/06/2026 1:06 am, john larkin wrote:
    On Mon, 15 Jun 2026 15:38:20 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 15/06/2026 8:41 am, john larkin wrote:
    On Sat, 13 Jun 2026 16:32:38 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 13/06/2026 5:37 am, john larkin wrote:
    On Sat, 13 Jun 2026 02:31:22 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>> wrote:

    On 13/06/2026 12:36 am, john larkin wrote:
    On Fri, 12 Jun 2026 16:34:22 +1000, Bill Sloman <bill.sloman@ieee.org> >>>>>>> wrote:

    On 12/06/2026 3:38 am, john larkin wrote:
    On Fri, 12 Jun 2026 02:00:02 +1000, Bill Sloman <bill.sloman@ieee.org>
    wrote:

    On 12/06/2026 12:21 am, john larkin wrote:
    On Thu, 11 Jun 2026 14:28:44 +0100, liz@poppyrecords.invalid.invalid
    (Liz Tuddenham) wrote:

    john larkin <jl@glen--canyon.com> wrote:

    <snip>

    If your design skills were more impressive your stuff might be worth >>>>>> copying.

    Sounds like our designs are perfectly calibrated: good enough to sell >>>>> but not good enough to copy.

    I used to attend some physics conferences and hang out in the bar with >>>>> competitors. We'd share what we were working on. In a small market, it >>>>> doesn't make sense to have two vendors do the same stuff.

    The aim, as a vendor, is to have stuff that blows the competition out of >>>> the water.

    Not me. The aim is to sell.

    Having a significantly better product than your competitors does make it
    easier to sell. You may never have been in a position to notice this. In
    a really small market, this may not be worth the trouble.

    Sure, blowaway products help sell.

    But many customers buy stuff because it's reliable, and well
    documented, and well supported, and long-term available.

    Nobody ever got fired for buying IBM. Safe choices are popular, but even
    the safes choices were once new parts.

    That is especially important in the aerospace and semiconductor industries.

    Not so much popular there as a bias imposed by the capital intensive
    nature of those industries. Every last little bit has to work before the
    whole monster can start making money.

    And another powerful reason people will buy from other people is
    because they like one another. You may never have been in a position
    to notice this.

    There are all sorts of ways of getting popular. Ignoring those occasions
    when somebody has done something stupid may make you popular with them,
    but everybody else who has been stuck with cleaning up the mess will be
    less charmed.

    I was active enough where I worked that people did have opinions about
    me - I'd guess that I was mostly liked, and mainly by people that I
    though well of, but one's own opinions on the subject aren't worth much.

    --
    Bill Sloman, Sydney


    --- PyGate Linux v1.5.16
    * Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)