Not really because headphones can be measured to some average ear but every room is wildly different.
This would be, however, not at all similar to how OPRA works. OPRA doesnāt measure when you wear the headphones, someone else creates measurements and uploads them - and this is precisely what canāt be done for speakers because nobody has your room to measure it.
Itās already possible to measure rooms with various apps (from super simple like HouseCurve to complex like REW and several other options), then create convolution filters and load them into Roon. Maybe it would be useful to have such a tool built into Roon (but, to repeat, this would not at all be similar to how OPRA works).
When I first tried it, with my Sennheiser 660S, I also initially preferred the default sound, and found the oratory1990 OPRA sound too bright.
But after a while, for some music, I began to get used to the OPRA sound, and prefer it, and the default then sounded muddy. So, for me at least, thereās a strong element of āwhat youāre used toā, and that changes, obviously. So now I donāt know what I like
Also, note that for a fairer comparison, you may need to add a headroom reduction to the default, non-OPRA sound, to match the inbuilt OPRA headroom reduction, so you can compare at similar volume. I have to reduce the default by 6.3dB, to match OPRA. Without doing that, the default may well sound better, simply because itās louder.
Many newer headphones and IEMs are not showing up in the OPRA database even a full year after released. The OPRA database needs to be updated and updated frequently.
This is us. We are all-too-aware and I just happened to see these questions about update parity so figured itās a good time to respond. We are trying to schedule work that does a better job of keeping profiles updated. Just a matter of getting it done. Very much appreciate your patience but it is coming.
