We once had a film crew in our school trying to get some shots of us at the computer. I overheard them having big problems getting the CRT flicker free on camera and trying to find out the refresh rate.
I was maybe 12 at the time and just told them point blank it‘s 60Hz. They asked me how I knew and I just told them I could see it from the feel of the flicker. Was a good guess as well since it was one of the standard VESA frame rates.
The cameraman came back to that kid 3 minutes later, showing me the shutter set to exactly 59.7 Hz with a still very surprised face.
I don't know what you mean by "muddy", but I did notice the speaker (perhaps mic too) has a crappy frequency response, and the bass notes are quiet and difficult to identify the pitch of.
When I got started I was awed by it in others I talked to on IRC, but it wasn't too long before I was familiar with it, too. It's also pretty easy for me—and I'd bet for nyanpasu64 as well—to identify the actual PSG or platform used and even to get a good idea of what sort of sequencing/programming is involved to get any particular sound I hear.
For me it's pretty specialized, though. I absolutely can't do that with traditional music production. I wouldn't be able to tell you too much about music I heard produced with modern tools.
If you're wearing headphones or have your speakers turned up, be careful!
EDIT: Upon reading the original code:
volume doesn't control the volume, but the duty cycle (timbre and harmonic content) of the waveform. And it looks like I guessed the 40% (audibly equivalent to 60%) duty cycle exactly!