The sound of the dialup, pictured
windytan.blogspot.com
windytan.blogspot.com
I remember the evolution in tones but never knew what they were till I took a signaling class in college. One of the projects in that class was to build visual transmitters. We'd stand outside a few hundred yards apart and see how fast we could transmit a message to a partner. The trick to being fast was encoding multiple bits in each symbol, but not so many you'd fumble around grabbing the next symbol. I think my transmitter encoded 2 bits at a time (so four symbols).
Aside, the Apple Cat II was a fascinating modem - http://www.jammed.com/~jwa/Machines/cat/
Ah! V.23.
The 75 baud backward channel of 1200/75 was good enough to keep up with typing so it was my preferred speed when accessing various things remotely where I never needed to send large amounts of text/data but had lots of data coming back the other way.
That feels like the obvious explanation to me ... Not sure if that means it must be wrong. :)
Keep in mind that the very high rate of change in signaling standards (9.6 -> 14.4 -> 19.2 -> 28.8 -> 33.6 -> 56 in roughly ten years) seemed to essentially leave little energy for non-core engineering changes.
In other words, having the modem duplicate the lines' "tones"/sounds over a speaker was a nice hack on the natural human ability to distinguish between different sets of complex patterns.
A similar hack: there is a blind programmer named Karl Dahlke who pipes the character stream being sent to his Linux console through his PC speaker. Even though it probably sounds like radio static or a cacophony to the untutored ear, he has been able to learn to distinguish certain patterns quickly without having to wait for his text-to-speech software to read him any of what is on the console.
ADDED. The "blinking lights" on the front panels of early computers and mini-computers is another example. I understand that computer operators learned to extract a lot of relevant information from the row of lights on the front of the computer that formed a binary representation of the contents of the program counter.
Parenthetically, these "out of band" debugging cues still work. Try holding an AM radio next to your PC's motherboard. :)
This was occasionally useful for debugging before CPU clock frequencies started to look less like AM radio and more like microwave ovens...
Useful for anyone else who wants to be able to match the sounds and pictures, I hope!
Reading someone else's post about the Apple Cat II just reminded me of the sheer joy of experimentation at the time. While what we have now was what we were ultimately striving for and would have switched to in a heartbeat, I'm glad for the experience I gained at the time. And I didn't know better so I still loved it :)
I just want to know how I got my first BBS numbers - I was visiting NZ when I got my first modem, and somehow got hold of some local numbers and then found other BBSes from there... but how did I get the first one?
Afaik not-so-ancient ADSL does the same thing.
IOW, each digit plays a two-note chord indicating the row and column on the keypad.
So primitive...
You've probably seen one before in relation to music. However, since we're dealing with computer-generated tones here, the spectrogram looks very very sparse (few overtones). You can see patterns in music as well, just not as clearly (because there's a lot more going on).
If you'd like to make your own, consider looking into GNU Octave (http://www.gnu.org/software/octave/) or possibly Scilab, both of which are free.
EDIT: I might add that Audacity can easily view the spectogram of a sound file, but if you want to manipulate the signal programatically (filters and so on; signal processing is a great subject), try the above.
Or with sox.
Why does dial-up always sound the same? That clip is exactly how I remember my modems sounding!
Edit: Hah, Scroll down Kiall, scroll down.