Greetings people of the Internet and good afternoon. Select measured loudspeaker responses have become something of a casual, standardized yardstick in places, and assumptions about them are being transferred onto real sound. I've had some thoughts about speaker response measurements versus sound rattling around for awhile and thought I'd post them.
Just tossing a few graphs out there (like we did recently) may imply that they actually do translate, more or less, into our aural impressions of the loudspeakers that made them. I've never found the measurement / speaker connection all that evident and automatic, however.
The challenges tied up in measurements are real. They're not insignificant.
There's too much to speaker behavior for us to leap from data to sound. We can develop a reasonable, qualifying view of speaker data, just not as a rigorous interpretation of sound.
Using data carries with it two seemingly contradictory truths: The first is that there can never be enough. More quality data simply means more reference points for a more nuanced view. The second is that the more of it there is the more variability creeps into the casual assumptions sometimes freighted with it.
Yet depending on preference, data is anything from a one-stop bible on speaker performance to an irrelevant accessory barely related to listening at all. In my opinion it's neither, but there are complexities to data - some practical, some theoretical, and some logical – to explore if we expect relevance.
Data type, condition, and acquisition are neither standardized or static. The context I'm addressing is the retail, casual, street use of data and not the bleeding edge in a closed laboratory where context and meaning are vastly different. There is a gulf between the two just as there is a logical contradiction between the complexity of data and drawing a simple conclusion from it. In my experience it's very reluctant to be that convenient.
I'll try and break questions out into specific areas of its tech, its collection, assumptions about its use, and the fallacies that arise around it. In no specific order, here we go.
UPDATE July 29, 2020
Since these posts were written three years ago aspects of the measurement-centric mindset have naturally evolved. A look at the conventional wisdom in places where speaker theory is discussed shows similar reliance on expanding data sets. Many times these circles have come to see what they call "the measurements" as a comprehensive, even complete snapshot of sound.
But are measured data complete? In some cases "the measurements" refer to just one amplitude response. In others they refer to a cluster of amplitude responses, which is more useful. But just as there's no way to summarize all available data into a predictive tool on real sound, there's still a general parsing to data down to just the amplitude response(s).
Are they universal and do they speak to every behavior of a fairly complex loudspeaker? They are not complete and as abstracts, they cannot condense reproduced sound down to a handful of graphical records of some speaker behaviors.
What are the other characteristics of complex loudspeaker behavior, in rough order of importance, not reflected intuitively in available data if they appear there at all?
Acoustical size. The importance of acoustical size cannot be overstated. Conversely, if data does not first call out the difference between, for example, a large multiway floor speaker's amplitude response and a single 4" driver equalized to copy that response, then the data is virtually meaningless. This applies across all speaker size classes.
Damping, transient response, stored energy, self-noise, etc. Cumulative Spectral Decay (CSD) is one way to display "hidden" resonant stored energy as a function of time. Just as a bell rings over time, any undamped speaker behaviors, whether mechanical, acoustical, or electrical may also store energy and release it over time.
Fundamental transfer function, damping, and power behaviors. Multiway speaker crossovers split the audio band into segments and route it to specialized drivers in the speaker. How these functions affect an enormous range of audible behaviors, while obliquely visible in some data, is almost completely unknown to the consumer and casual speaker data fan.
Distortion, type, and distribution, including by loudness level. No speaker reproduces a signal without distorting to some degree. Amount, type, and location of this distortion is naturally an important consideration.
Harmonic distribution. Harmonics generated by distortion appear in relationship to a fundamental tone. How they're distributed and to what relationship can be a component of perceived reproduced sound.
All pass, minimum phase, linear phase, and transient relationships; time offset, group delay, step response, etc. The complexities of the transfers mentioned above are compounded almost infinitely across all speaker design types and examples. How they work is virtually never expanded upon, but how they all inherently affect both sound and data is fundamental.
Bandwidth. Arguably as important as acoustical size, the bandwidth of the speaker is a strong precursor of listener reaction. However without acoustical size being established, it becomes a fairly ignored aspect of real sound.
There are many other elements to loudspeaker-reproduced sound.
Virtually all discussions of speaker data fail to include all data. At the same time no discussion of loudspeaker data can predict the sound of a loudspeaker, which is to say that data is very arguably a design check and is not a post-design predictor of sound, at least to the degree that it will speak to the reaction of a reasonably perceptive listener as s/he is or is not gratified by an original musical performance reproduced by a loudspeaker.
References to :"the measurements" as if there were a global, comprehensive, and complete data snapshot to predict sound are simple biases.
Over the time since the first comment above, some speakers regarded for their measured linearity on one measurement system have been shown to be much less attractive in the data from another. This calls a comment posted below about deviations in the data from a single speaker into play. Even the objective data is apparently not absolute. In other cases an over-reliance on very limited amplitude data has created a small class of listeners who have conditioned themselves to hear virtually nothing else in the complex reproduced sound.
The point of speaker data is to isolate a speaker's behavior and scale its relative degree. It seems much, much less able to thoroughly capture the actual sound of a whole, complex device. It's perfectly acceptable to deviate from one of more classical data expectations in order to fulfill aspects of real sound elsewhere - Chane has done this in places, both consciously and to pursue a more truthful sound.
Without a thorough facsimile of total sound visible in the data, the data fails to display enough of a comprehensive, even total picture of that sound. The data is a profound and essential component of the loudspeaker design looking outward. It is however nearly as profoundly incapable of proving sound unheard as a predictive tool looking inward on the speaker and its measurable, complex personality from the outside. There is a fundamental difference between primary design data and an after-the-fact attempt to show sound through data.
What's the solution? As always, it's hearing the speaker, in the space in which it'll be used, over a long enough period of time to allow it to inform the subtleties of perception, and to not bias the experience - which is what this is ultimately all about - with limited preconceptions of what the sound should be according to a limited interpretation of data.
Just tossing a few graphs out there (like we did recently) may imply that they actually do translate, more or less, into our aural impressions of the loudspeakers that made them. I've never found the measurement / speaker connection all that evident and automatic, however.
The challenges tied up in measurements are real. They're not insignificant.
There's too much to speaker behavior for us to leap from data to sound. We can develop a reasonable, qualifying view of speaker data, just not as a rigorous interpretation of sound.
Using data carries with it two seemingly contradictory truths: The first is that there can never be enough. More quality data simply means more reference points for a more nuanced view. The second is that the more of it there is the more variability creeps into the casual assumptions sometimes freighted with it.
Yet depending on preference, data is anything from a one-stop bible on speaker performance to an irrelevant accessory barely related to listening at all. In my opinion it's neither, but there are complexities to data - some practical, some theoretical, and some logical – to explore if we expect relevance.
Data type, condition, and acquisition are neither standardized or static. The context I'm addressing is the retail, casual, street use of data and not the bleeding edge in a closed laboratory where context and meaning are vastly different. There is a gulf between the two just as there is a logical contradiction between the complexity of data and drawing a simple conclusion from it. In my experience it's very reluctant to be that convenient.
I'll try and break questions out into specific areas of its tech, its collection, assumptions about its use, and the fallacies that arise around it. In no specific order, here we go.
UPDATE July 29, 2020
Since these posts were written three years ago aspects of the measurement-centric mindset have naturally evolved. A look at the conventional wisdom in places where speaker theory is discussed shows similar reliance on expanding data sets. Many times these circles have come to see what they call "the measurements" as a comprehensive, even complete snapshot of sound.
But are measured data complete? In some cases "the measurements" refer to just one amplitude response. In others they refer to a cluster of amplitude responses, which is more useful. But just as there's no way to summarize all available data into a predictive tool on real sound, there's still a general parsing to data down to just the amplitude response(s).
Are they universal and do they speak to every behavior of a fairly complex loudspeaker? They are not complete and as abstracts, they cannot condense reproduced sound down to a handful of graphical records of some speaker behaviors.
What are the other characteristics of complex loudspeaker behavior, in rough order of importance, not reflected intuitively in available data if they appear there at all?
Acoustical size. The importance of acoustical size cannot be overstated. Conversely, if data does not first call out the difference between, for example, a large multiway floor speaker's amplitude response and a single 4" driver equalized to copy that response, then the data is virtually meaningless. This applies across all speaker size classes.
Damping, transient response, stored energy, self-noise, etc. Cumulative Spectral Decay (CSD) is one way to display "hidden" resonant stored energy as a function of time. Just as a bell rings over time, any undamped speaker behaviors, whether mechanical, acoustical, or electrical may also store energy and release it over time.
Fundamental transfer function, damping, and power behaviors. Multiway speaker crossovers split the audio band into segments and route it to specialized drivers in the speaker. How these functions affect an enormous range of audible behaviors, while obliquely visible in some data, is almost completely unknown to the consumer and casual speaker data fan.
Distortion, type, and distribution, including by loudness level. No speaker reproduces a signal without distorting to some degree. Amount, type, and location of this distortion is naturally an important consideration.
Harmonic distribution. Harmonics generated by distortion appear in relationship to a fundamental tone. How they're distributed and to what relationship can be a component of perceived reproduced sound.
All pass, minimum phase, linear phase, and transient relationships; time offset, group delay, step response, etc. The complexities of the transfers mentioned above are compounded almost infinitely across all speaker design types and examples. How they work is virtually never expanded upon, but how they all inherently affect both sound and data is fundamental.
Bandwidth. Arguably as important as acoustical size, the bandwidth of the speaker is a strong precursor of listener reaction. However without acoustical size being established, it becomes a fairly ignored aspect of real sound.
There are many other elements to loudspeaker-reproduced sound.
Virtually all discussions of speaker data fail to include all data. At the same time no discussion of loudspeaker data can predict the sound of a loudspeaker, which is to say that data is very arguably a design check and is not a post-design predictor of sound, at least to the degree that it will speak to the reaction of a reasonably perceptive listener as s/he is or is not gratified by an original musical performance reproduced by a loudspeaker.
References to :"the measurements" as if there were a global, comprehensive, and complete data snapshot to predict sound are simple biases.
Over the time since the first comment above, some speakers regarded for their measured linearity on one measurement system have been shown to be much less attractive in the data from another. This calls a comment posted below about deviations in the data from a single speaker into play. Even the objective data is apparently not absolute. In other cases an over-reliance on very limited amplitude data has created a small class of listeners who have conditioned themselves to hear virtually nothing else in the complex reproduced sound.
The point of speaker data is to isolate a speaker's behavior and scale its relative degree. It seems much, much less able to thoroughly capture the actual sound of a whole, complex device. It's perfectly acceptable to deviate from one of more classical data expectations in order to fulfill aspects of real sound elsewhere - Chane has done this in places, both consciously and to pursue a more truthful sound.
Without a thorough facsimile of total sound visible in the data, the data fails to display enough of a comprehensive, even total picture of that sound. The data is a profound and essential component of the loudspeaker design looking outward. It is however nearly as profoundly incapable of proving sound unheard as a predictive tool looking inward on the speaker and its measurable, complex personality from the outside. There is a fundamental difference between primary design data and an after-the-fact attempt to show sound through data.
What's the solution? As always, it's hearing the speaker, in the space in which it'll be used, over a long enough period of time to allow it to inform the subtleties of perception, and to not bias the experience - which is what this is ultimately all about - with limited preconceptions of what the sound should be according to a limited interpretation of data.
Comment