I recently released my article on Headphones.com discussing the mechanics of Harman's 2018 research into headphone listener preference, and how certain constraints from that research have made the way this work is commonly used fraught with oversimplification and overconfidence.
Afterwards, there was some discussion that led to me resolving to make a few updates. The first, which has been pushed to GraphWorks, is that the preference boundaries can now be split between 5128 and GRAS so that people only looking at data for one headphone measurement set only have to see the boundary space for the fixture that is actually being used.
This change has been integrated into an automatic function on GraphWorks, so users will not have to manually select boundary spaces; it should all work with no need to think about it.
The second change I'm currently working on is an additional upper-bound for the bass region in particular that automatically activates when closed-back headphones are brought into the visualizer. As we've seen from multiple sources (eg. Sean Olive, @oratory1990, and our own measurements), the magnitude of bass in closed-back headphones tends to be overemphasized on most of the fixtures we use relative to what humans receive on average, whereas open-back headphones tend not to experience this disconnect. This is important, because an open-back headphone was used as the replicator headphone in Harman's study that led to these bounds being created.
So as of now, I'm in the middle of doing some investigation as to what sort of additional range of overestimated bass is worth accommodating in our boundary space, given obviously this is going to be both headphone-specific and rig-specific behavior that will likely differ substantially across acoustic designs. Interested to hear what everyone here thinks of this premise or how to attack such a thing to make it maximally useful.
Currently, I'm working with a dataset of a few (5) closed headphones measured on a variety of fixtures, while each is compensated to the same headphone's measurement at the ear-canal entrance point of whomever actually owns the headphones, results below. It's clear that there's some level of overestimation, but the amount and shape of elevation (as expected) shifts between rigs and between headphones.
Interested to hear what people think is a good approach for this, or if they have any reasons why the above wouldn't be a defensible thing to give people.
Afterwards, there was some discussion that led to me resolving to make a few updates. The first, which has been pushed to GraphWorks, is that the preference boundaries can now be split between 5128 and GRAS so that people only looking at data for one headphone measurement set only have to see the boundary space for the fixture that is actually being used.
This change has been integrated into an automatic function on GraphWorks, so users will not have to manually select boundary spaces; it should all work with no need to think about it.
The second change I'm currently working on is an additional upper-bound for the bass region in particular that automatically activates when closed-back headphones are brought into the visualizer. As we've seen from multiple sources (eg. Sean Olive, @oratory1990, and our own measurements), the magnitude of bass in closed-back headphones tends to be overemphasized on most of the fixtures we use relative to what humans receive on average, whereas open-back headphones tend not to experience this disconnect. This is important, because an open-back headphone was used as the replicator headphone in Harman's study that led to these bounds being created.
So as of now, I'm in the middle of doing some investigation as to what sort of additional range of overestimated bass is worth accommodating in our boundary space, given obviously this is going to be both headphone-specific and rig-specific behavior that will likely differ substantially across acoustic designs. Interested to hear what everyone here thinks of this premise or how to attack such a thing to make it maximally useful.
Currently, I'm working with a dataset of a few (5) closed headphones measured on a variety of fixtures, while each is compensated to the same headphone's measurement at the ear-canal entrance point of whomever actually owns the headphones, results below. It's clear that there's some level of overestimation, but the amount and shape of elevation (as expected) shifts between rigs and between headphones.
Interested to hear what people think is a good approach for this, or if they have any reasons why the above wouldn't be a defensible thing to give people.