This week, I thought it would be useful to consider the topic of "silence". Music grows out of silence. Without silence - or to more accurately put it; a low noise floor in the listening room - it would be difficult to detect very slight "microdynamic" changes. Even if one were to pump up the volume, nuances can be missed. In part, this is why the "dreaded" dynamic range compression (volume compression) is used. It reduces the dynamic range such that even very "soft" detail is pushed up in volume allowing detection of these details on the subway and in cars (remember back in the day when we had "loudness" buttons on car music players?), as well as qualitative psychoacoustic preference to some extent. There is a limit to how far volume can be pushed in that at some point, we experience the sound to be intolerably loud or the hardware starts distorting - remember to always protect your hearing. Important characteristics of accuracy in reproduction - tonal neutrality (uncolored), and precise conveyance of detail (combination of good dynamic range & timing accuracy) - demand that the room be isolated from external noise as much as possible. It'd be a shame to listen to high quality audio at reference 75-80dB level but 50dB of that is affected by noise! Even worse than consistent background hissing, humming, or rumbling is random or episodic noise like frequent cars passing by or people talking outside distracting the virtual "concert".
Refer to the "Sound Pressure" Wiki page with the relevant levels at the bottom. For convenience, I've reproduced it here:
Not on the list: AT&T-Bell "Quiet Room" = 10dB(A). Orfield Labs "quietest place on earth" as per Guinness = -9.4 dB(A)! |
In my home, as I mentioned last month regarding the HTPC in my sound room, I could still hear the hard drives spinning in that computer. A bit annoying, and this just won't do :-). So I decided to rectify the situation doing what I suggested in that post - separating the music/movie/data server component to another room and putting together a relatively low cost, less powerful computer which could act as a streamer. I extracted the fanless power supply from that computer and reinstalled the SSD with Windows Server; moving it into an adjacent room. Here are the pieces then for the new build:
Case: Bitfenix Prodigy M microATX
Power supply: transplanted the fanless SeaSonic SS-400FL2 400W
Motherboard: ASUS B85M-E/CSM - has HDMI with 4K capability
CPU: Intel Pentium G3220 (dual core, 3GHz, 54W TDP only, Haswell graphics features but slow 3D)
CPU Cooler: CoolerMaster Hyper 212 Plus (total overkill but lets me run almost fanless!)
SSD: Corsair FORCE 240GB (got a good deal on a refurb)
RAM: 8GB Kingston DDR3 1600 (note the G3220 will underclock this to 1333)
I installed Windows 8.1 Pro x64 on the system. Due to the oversized CPU cooler, I'm able to run the 120mm fan essentially silent between 20-30% speed and this is the only fan in the whole unit. No problem running 50 iterations of IntelBurnTest without any errors at "Very High" stress level while staying cool (I like using this program for stability testing more than Prime95; generates lots of heat within minutes).
So far, I've streamed a couple of MKV 1080P movies in excellent quality 20Mbps H.264 plus DTS soundtrack - no problem at all. I also installed JRiver 19 and foobar as I described in that last HTPC article and have no problem streaming DSD64/128 to the TEAC UD-501 using USB2 and 5.1 multichannel FLAC to the Onkyo receiver through HDMI. The Squeezebox system (Transporter, Touch, Boom, Radio) connects directly to the Windows Server machine and has nothing to do with this HTPC.
All this is running silently with a reasonably fast machine for media playback purposes. I should be able to play 4K as well using the built-in Intel graphics off the ASUS motherboard's HDMI 1.4. I tried streaming some YouTube 4K videos and they looked great on the 1080P screen - they're decoding reasonably well without much framerate issue at least so it'll be interesting to see how smoothly (or not) they play on a native 4K panel one day assuming I'm still running this rig...
Out of interest, I decided to try measuring the background noise in my sound room using a calibrated Behringer ECM8000. Realize that this inexpensive measurement microphone is not meant for low noise purposes with a self-noise in the low 20dB range (according to this link) mainly related to the small microphone diaphragm. I'm certainly not about to spend something like $2000 to buy the AcoPacific PS9200KIT for this purpose (this can measure down to ~8dB(A)). I figure if I can get a rough estimate, it'd be good enough. So, using a Radio Shack digital SPL meter (which only goes down to 50dB) for quck'n'dirty calibration for the Behringer with REW, then letting the Behringer measure the "silence" at the optimal listening position, I'm seeing this:
Quiet room, 10:30PM: HTPC/pre-amp/monoblocks/subwoofer/TEAC DAC/Transporter/room EQ DSP all turned on. |
Even though the ambient noise level is low, my room still has not been treated with acoustic panels so the room reverberation time remains a bit high. EQ'ing has provided a reasonably flat response described previously (+/-5dB around the target Brüel and Kjær "house curve" with recent digital EQ tweaks). Absorptive acoustic panels remain on my radar screen - I'm still contemplating aesthetics.
Happy listening everyone. Make sure to take a minute and consider the "sound of silence" in your audio room...
-----
I want to end this post on a more serious note (as much as I enjoy the topic of audio, it's only a hobby after all!)... I want to send my regards to Matt Ashland, the CTO of JRiver, the principle developer of Monkey's Audio (APE format - probably the most space-efficient free lossless compression system), and contributor to the DoP protocol (DSD over PCM). As some of you know, he had a fall in January and required surgical evacuation of intracranial bleeding; still recovering in hospital. I had the pleasure of exchanging E-mails with Matt last year around the time of the beta JRiver 19 release regarding the PCM to DSD transcoding algorithm, DST decoding, some bug fixes to JRiver, and his summer vacation with his kids. A truly genuine, generous gentleman and one of the unsung heroes of the computer audio hobby... My thoughts and prayers are with you and the family, Matt. Get well soon.
Matt has a CaringBridge page.
ADDENDUM: (March 7, 2014)
For those wondering, even with the Pentium G3220 underclocked to 2.5GHz, undervolted by -0.1V to consume <30W under full load with IntelBurnTest (~36C after 30 minutes), there is no problem upsampling 24/192 PCM to DSD128 in realtime with JRiver 9. CPU utilization <30%. I had to increase the TEAC DAC's ASIO buffer to 250ms to prevent some buffer issues though. Sounds great...
Given the price and performance of this CPU, I can't imagine any reason to build anything less powerful these days. I think it would be no problem running this fanless with a good sized heatsink if I underclocked it even further; 2GHz dual core with lower voltage fanless probably would be totally fine!
The ambient noise part may have to be nuanced a bit.
ReplyDeleteWhile it is true that when looking at oscilloscope pictures or SPL meter readings one would fear that listening at 80dBA peak levels would give only 50dB dynamic range and lower signals will be masked by the 30dBA background noise as the small signals are 'buried' in the noise (as the signals add)
However, a car passing by may indeed distract from the music (should be louder than 30dBA to be offensive IMO) is simply interpreted by the brain as a car passing by + the music playing.
It may be true that the sound the car makes (in certain frequency bands) will mask some of the music frequencies present in that car-sound.
But we will still simply hear a car + music, which the brain derives from the other music signals/cues that are not masked by the car-sound.
Another example, I have no problems listening to music when the wind is hauling around the house as I know it is just the wind and maybe distracts a bit.
But... when a 'noise' source inside the house is present, that can be eliminated, I won't rest till that is sorted as that does seem to take away enjoyment of the music.
A psychological thing I reckon.
Indeed. Type of noise itself can have significant impact on the psychological mechanism - maybe has to do with our perception of threat if we think about it from an adaptive/evolutionary basis. I agree it'd be more difficult to enjoy music if the sound could be that of an intruder in the home vs. the wind howling outside :-).
DeleteOf course as an obsessive, I wouldn't rest if I can get rid of the noise!
Although 70-80dB might be the average volume, for very dynamic pieces, it's not unusual to hit >100dB at reference volume...
I guess I'm just screwed LOL
ReplyDeleteWith no electronics, A/C, etc., on at all (i.e., best possible conditions from my listening position), ambient noise in the room is ~50dB. Given I'm uncomfortable listening to music at more than about 65-70dB (just sounds "too loud" to me), I should presumably just listen to 128k MP3s ;)
Seriously, I live close to downtown Dallas, only a couple hundred yards from Central Expressway, and the same from a busy shopping district, so there is always ambient traffic noise, etc. Headphones are really my only option for analytic listening.