How-To Geek recently ran down seven of them: the 1/4-inch jack, the 3.5 mm jack, RCA, XLR, TOSLINK optical, five-pin DIN MIDI and VGA. This piece walks through each one. It also tightens a few claims that were looser than the evidence allows, because "old" doesn't automatically mean "better."
The 1/4-inch jack: the switchboard survivor
The lineage here is telephony. The first commercial telephone exchange opened in New Haven in 1878 is the historical anchor, per the National Park Service, though that dates the switchboard era rather than today's exact audio plug design. A 1927 Bell Laboratories account suggests the plug-and-jack arrangement resembling later hardware arrived around 1882. So "1870s" is fair as a loose origin story, but not as a standards date.
Today it lives on guitars, amplifiers, studio headphone outputs and other professional gear. Focusrite notes that its audio interfaces carry 1/4-inch (6.35 mm) headphone outputs, and that 3.5 mm headphones connect through a simple adapter.
The real-world gotcha is that the same physical plug can carry different signals. Focusrite warns that gaming headsets with a built-in microphone use a four-conductor TRRS plug. Studio headphone outputs expect a three-conductor TRS plug, and the mismatch can make audio sound filtered or lopsided. A connector that fits doesn't guarantee a signal that matches.
The 3.5 mm jack: still the PC's workhorse
Phones dropped it, but desktops, laptops, consoles and countless peripherals kept it. The appeal is plain: plug in, hear sound. There's no pairing step, no battery and no wireless link to drop.
A few caveats the original glossed over:
- "Zero latency" is too strong. A passive analog path avoids Bluetooth's encode-and-decode steps, but the rest of the chain, such as drivers and buffers, still adds delay.
- "High fidelity" describes the transport, not the result. Quality still depends on the source, converter, amplifier and headphones.
- Headset wiring varies. Google's ChromeOS headset specification, for example, calls for a four-conductor plug, recommends CTIA pin order and lists OMTP as optional. Mixed wiring standards are why a headset can work on one device and lose its mic on another.
For Windows users, the practical advice is to check whether your port is a combo headset jack or separate headphone and mic sockets before blaming drivers.
RCA: yellow, red and white, still on duty
RCA left the TV's back panel in many homes, replaced by HDMI. It remains common on analog line-level gear such as receivers, mixers, turntable preamps and powered subwoofers. If you're adding a sub or feeding a vintage amp, RCA is often the connector you'll meet.
Treat sockets as labeled, not interchangeable. An RCA-shaped jack might be an input, an output or a phono-level connection, and plugging into the wrong one gives you hum, distortion or silence. "Practically indestructible" is marketing-speak; "simple and widely understood" is the safer claim.
XLR: balanced audio with a latch
XLR's three pins enable balanced audio, which helps reject interference over long cable runs. That's why it dominates microphones, stage gear and studio interfaces. The latch keeps the cable seated.
It also carries phantom power. Shure describes phantom power as DC supplied through the mic cable, typically 12 to 48 V, which powers condenser-microphone electronics without a separate battery. The caveats matter:
- Not every XLR input supplies phantom power.
- Not every microphone needs it.
- Balanced benefits only appear when the equipment at both ends is balanced.
The original piece also warns against mixing audio XLR cables with DMX lighting cables. That's sensible advice, because a similar plug doesn't prove the cable or signal is compatible. I couldn't verify the specific cable differences it cites, so check the cable's labeling and specifications.
TOSLINK optical (S/PDIF): light instead of copper
TOSLINK sends digital audio as pulses of light, which gives it electrical isolation. Vendor documentation notes that it's immune to electrical interference because it carries light rather than current. That can help in setups where ground loops or noise are a problem, for example a PC feeding a soundbar or DAC. It doesn't automatically make audio sound better.
The bigger question is format support. The underlying S/PDIF interface is described by IEC 60958-1 as a serial, unidirectional, self-clocking digital audio interface. In practice, TOSLINK is comfortable with two-channel PCM and compressed 5.1 such as Dolby Digital or DTS. XDA-Developers' format table shows stereo PCM and Dolby Digital 5.1 working over optical and Dolby TrueHD not working. It lists Dolby Digital Plus as "usually no / limited." Another explainer says S/PDIF does not have enough bandwidth for TrueHD or for more than two channels of PCM.
Sources disagree on Atmos. Most say optical can't carry it, and one claims it can via Dolby Digital Plus. The more careful position is that TrueHD-based Atmos can't travel over optical, and anything else depends on what both devices support. Check both manuals. If you have a PC or TV with a surround setup, HDMI eARC is the path for lossless and object-based formats. Also, if optical output goes silent, a mismatched format setting is the usual suspect, so try setting the output to PCM.
Five-pin DIN MIDI: control data, not sound
MIDI isn't audio. The MIDI Association describes it as a specification for exchanging notes, program changes and expression data between instruments and other devices. Its 1.0 specification includes the original five-pin DIN serial transport, and the electrical specification was later updated for 3.3 V circuitry.
The "no drivers, no computer" claim is true in a narrow sense. Keyboard-to-synth hardware chains work without a PC. But once a computer is involved, you need an interface and often drivers or configuration. MIDI is also direction-sensitive. Ports are labeled In, Out and Thru, so routing means connecting the right pairs.
VGA: the presentation-room cockroach
VGA is analog, carries no audio, and has mostly vanished from new PCs. It lingers on projectors and older monitors. It doesn't implement HDCP, so it avoids handshake failures in that department. That is a legacy-compatibility quirk, not a way around protected-content rules, and software and source behavior still apply.
The claim that VGA tops out at 1440p at 75 Hz is also better framed as a device-specific limit. Some CRT monitors have listed higher analog modes, so the ceiling depends on the graphics output, cable, adapter and display. If you need to connect a modern laptop to a VGA projector, plan on a converter rather than assuming a cable will do it.
What to take away
The shared lesson isn't that old beats new. It's that each port survives because it solves a narrow problem cheaply:
| Port | Why it persists | Watch out for |
|---|---|---|
| 1/4-inch jack | Instruments, studio headphones | TS, TRS and TRRS mismatches |
| 3.5 mm | Simple wired audio | Headset wiring and combo jacks |
| RCA | Analog line-level gear | Input, output and phono labeling |
| XLR | Balanced mics, phantom power | Not every input supplies power |
| TOSLINK | Electrical isolation | PCM and Dolby Digital limits |
| 5-pin DIN MIDI | Instrument control | In, Out and Thru direction |
| VGA | Legacy projectors | Needs an active converter |
Before buying a cable or adapter, identify the signal type and the modes both devices actually support. That habit saves more money than any "gold-plated" upgrade ever will.
References
- 7 ancient audio and video ports that are still useful today How-To Geek · 2026-10-24T22:00:16+00:00
- ChromeOS Compatible - 3.5mm Headset Specification v2.0 | Google for Developers developers.google.com
- Why does audio from my headset sound unusual? – Focusrite support.focusrite.com