Comments (7)
I removed the calibration argument because it was not really very usable and was altogether confusing. The functionality is now replaced with --sound_signature
parameter. See here for usage examples: https://github.com/jaakkopasanen/AutoEq#Using-Sound-Signatures
from autoeq.
I actually working on a script file that able to run AutoEq fast and easy.
https://github.com/mhtvsSFrpHdE/autoeq-batch-generator/blob/master/autoeq-batch-generator.ps1
At line 172~178, the "Write" function will generate AutoEq command for later use.
I read the introduction about the introduction "Using-Sound-Signatures".
There are still some specified issue that I'm not sure.
We know that now I'm going to update my script to match the latest change in AutoEq.
In the "The running command", for example,
I use ATH-M50X as my hardware,
and try to equalize this headphone to Razer Kraken(Just for demo & fun).
I set inputDir
, and set compensation file,
in such case the compensation is not from innerfidelity
but the inputDir
is.
So a calibration file is being used for innerfidelity
to rtings
.
This is the logic behind the old version.
By reading the introduction I'm not sure how to do same thing in the new version.
Do you have some suggestion?
from autoeq.
Something like this:
python frequency_response.py --input_dir="innerfidelity/data/onear/Audio Technica ATH-M50x" --output_dir="my_results\m50x Kraken" --compensation="innerfidelity\resources\innerfidelity_compensation_sbaf-serious.csv" --sound_signature="results\rtings\avg\Razer Kraken USB\Razer Kraken USB.csv" --equalize --parametric_eq --max_filters=5+5 --ten_band_eq --bass_boost=4
Parameters here are:
--input_dir
points to the headphones you are using--output_dir
to whatever path you want to save your results in--compensation
must be the path to compensation file for measurement systems used for measuring the headphones you are using which is Innerfidelity in this case--sound_signature
points to a pre-existing equalization result of the target headphone which is Kraken in this case--bass_boost=4
is here because the pre-existing result for Kraken has been made with bass boost of 4dB. Not using bass boost here would result in having less bass than what Kraken has naturally.- The rest are the usual stuff
--sound_signature
will use the error curve of the pre-existing result. Sound signature of a headphone is really the deviation from neutral. We assume that the compensation curve represents neutral so deviation (or error) from the compensation curve is the sound signature. This means that the pre-existing result for the target headphone must be made with a neutral compensation curve. Compensation curves used in pre-computed results of AutoEQ are neutral ones (with the exception of bass boost) so the pre-computed results can always be used.
from autoeq.
@jaakkopasanen So this time we do not compare the difference between the two raw data, instead, but the Razer Kraken "result" is being used.
By my understanding, the new approach that we equalize "M50X" to "sbaf-serious" first, then use "Kraken's result" for sound signature.
Another potential problem is, did the "sbaf-serious" is the same as "avg"?
Do we need to further calibrate the two?
from autoeq.
@jaakkopasanen Can you drag a release tag for which commit that removed "--calibration" argument?
So I can drag a release for the API change too.
In this case, is easy to find which version of "AutoEq" can work with "AutoEq batch generator".
There indeed a release in my project, that shows it can work with AutoEq that published around 12/30/2018, but the detailed version is unsure.
https://github.com/mhtvsSFrpHdE/autoeq-batch-generator/releases
from autoeq.
Yes, M50x is first equalized to SBAF-Serious and then to Kraken's sound signature (which is the error curve). Raw data's are not compared directly anymore. SBAF-Serious is not the same as Rting's avg but the whole thing works on the assumption that both of the compensation curves represent neutral for their respective measurement systems. There is no need to calibrate the two systems because having a neutral target for each system works as the calibration mechanism, in a way.
Calibration was removed in this commit: e79b06b
from autoeq.
@jaakkopasanen Thank you, I then keep coding.
from autoeq.
Related Issues (20)
- Pulse Explore measurements missing (404 error) HOT 1
- Some more Equalizer options HOT 1
- __
- Adjust eq profile to 8-band equalizer from soundcore app HOT 5
- Broken URLs HOT 4
- Broken Links!! HOT 1
- How to Control or See Impulse Response Headroom HOT 3
- Question about copyright notice
- Monarch MK2
- Adding Fiio as a new data source
- Export to HibyMusic (.peq) file
- Python no longer provides distutils since 3.12
- Input parameter checks in PEQFilter -class
- https://developer.android.com/studio/debug/dev-options.html#enable
- KZ EDX
- 1More SonoFlow
- Add capraaudio headphones
- Headphone request - HEDDPhone Two (available from oratory1990)
- Generate average/median of measurements for a given headphone
- FIIO JT1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from autoeq.