Yes, thatās correct.
The measuring of headphones and IEMs seems to be by headphone community volunteers in their spare time.
I find most headphones donāt need EQ actually, I have only 2 pairs that do, my others are fine without it and sound worse with EQ to the Harman curve, IMO.
Do you feel your IEMs need it?
Thanks Grasshopper and SukieInTheGraveyard. I think it was more a curiosity to try out. That said I did note the Oriveti OH500 preset is available (measured by crinacle) and it is a similar 4 BA design as mine, but the OH500 has an additional 8mm dynamic driver. Iām listening to that preset as we speak and am quite impressed.
I anticipate the dynamic driver in the OH500 may impart a bit more bottom end than the 4BA design of my O400 IEMs. But thatās not to say the preset is sounding lacking really.
Perhaps Iāll reach out to others further, as was suggested, at a latter point.
I completely agree, but as i have also come to the conclusion that not all headphones suit everyone, maybe this is a good way of subjecting more people to good music and sound quality?
Yes I agree, I think OPRA is a great initiative.
It seems to have been adopted enthusiastically by people who could have maybe entered the numbers into the Muse PEQ anyway, pre OPRA, but for some reason didnāt. This gives a measure of convenience and ease.
I used muse before but got a bit tired of messing around with it . Loading a convolution filter is simple as well but recently I failed to find filters for my headphones that I liked before and didnāt bother with it anymore.
But opra is a gamechanger⦠Iām not that crazy anymore about getting 100% best performances out of everything⦠95% is fine as well.
Just curious, but whoās vetting these presets in OPRA? Whatās to stop some malicious person from entering bogus presets in AutoEq? Iām asking out of ignorance. Just want to know what the procedure is.
We love seeing the OPRA conversation. Want to make sure to clarify RE: āMeasurements only transfer over to OPRA if theyāre added to AutoEqā:
Measurements transfer into Roon (or any other application that is designed to access OPRA) if theyāre added to the github repository (which resides here).
We invite measurement folks to upload profiles directly into the OPRA GitHub repository.
Itās been designed for consistency, stability, and clean software interaction so that Roon or any other software can call/present profile data.
f youāre in a position to have someone measure a product for which a profile doesnāt already exist (i.e. as someone mentioned asking oratory or ToneDeafMonk or others to measure for you), assuming the repo specs are followed as displayed in OPRA, you can upload.
We can then review the submission, and, assuming all good, merge right into the DB for you. The new profile would appear in Roon (or any other application that access OPRA) for use in the headphone EQ.
Roon has set up the repository, defined the git-based database format, built the documentation and tooling, and created a system that makes this data available to software that might make use of it. We have also contributed significant amounts of vendor and product artwork to ensure that products based on OPRA look great.
We will be approving PRs as the community builds out the repository, and as leaders emerge in the community, we will share this responsibility with others to ensure that this project is resilient in the long term.
Going forward, we will work to keep the data set clean and consistent so that when it is utilized within a product, the experience is great. We will use our graphic design team to maintain high quality product and manufacturer artwork, as we recognize that many people interested in contributing data may not be in a position to produce high quality graphics assets."
Just back home, after an extend trip (using ARC of course ) and although the line art for the Zone does change when an OPRA filter is used, BUT only if the default icon for the endpoint is used.
Unfortunately my main endpoint is a Naim NDS Network player, where I use with the SonoreUPnP Bridge to provide Roon based playback. This uses the Squeezelite support in Roon, for which there is no specific line art icon. I did make a feature request to have something done here, that was about 10 years ago, butā¦.
So I urge for the inclusion of a feature to duplicate a endpoint into a āspeakerā and āheadphoneā zone, so I can benefit from the correct zoneās line art.
But OPRA does draw its data from the same root source as AutoEq. What Iām asking is the whether new submissions are added to the source data that is then used by OPRA and AutoEq (and others) or whether the new submissions would then be specific to OPRA.
Hi there - thatās not actually how it works. OPRA is its own independent source and, based on increasing community participation and submissions, can house profiles that are available under CC BY-SA 4 licensing (and of course meet OPRAās content requirements).
New submissions would be specific to OPRA as the originating content repository but, under the same CC licensing, attributed, unmodified, and available for other platforms to pull (i.e. other repositories, Roonās headphone EQ, other playback software applications).
Hope this helps but let me know if still unclear.
J
Hi @mike I have a compromise request, when a OPRA Headphonre profile is active, could the line art be configured to over write any select zone icon, and itās display be forced within Roon Remote.
Which would provide the indication that a headphone filter had been selected, which is I believe your intention for the OPRA feature, and be very useful to remind the user that one was selected for headphone use over speakers.