autoEQ via Squig.link for supported earphones on HiBy R Android players

[Joe Bloggs]

1. Supported models
This is rolling out to all recent Android-based HiBy R branded devices through firmware updates now or in the near future. Check for the PEQ option in your Audio Settings after updating to the latest firmware.

2. How it works
Using the Equalizer tab and then the autoEQ option on squig.link, you can equalize earphones (that have been measured and uploaded to squig.link) to various "reviewer targets" or "reference targets" automatically using the autoEQ function. These EQ presets are supported on [supported models] using their new systemwide PEQ function.

3. How-to
a. go to squig.link and find the response curve for your earphones.
b. select the reference target or reviewer target to be overlaid in dotted lines. This will be the target autoEQ will attempt to convert to.
c. click Equalizer

d. Under "Parametric Equalizer open the "Choose EQ model" dropdown box to select your earphones on display.

e. Press "AutoEQ". AutoEQ will take a few seconds to run and calculate a set of parametric EQs for your earphones based on the target given.

f. Review the calculated EQ and make any changes to taste

g. Press the Export button (not the Export Graphic EQ button below) to export a text file containing the above settings.

h. Copy the resulting file to your HiBy R Android device. Or, if you did all of the above directly on a browser on your Hiby, you may skip this step --just note down the name of the text file generated.

i. On your HiBy R Android device, fire up PEQ inside Audio Settings. Press Import and select the file saved from the previous step using the file browser.

Enjoy

Notes:

1. HiBy Music makes no claims as to the merits of using autoEQ or indeed any parametric EQ vs not using them. That is for the user to explore and decide.
2. The curve displayed on the HiBy PEQ interface will be of the parametric EQs themselves, not the resulting FR curve which is the original FR curve modified by the PEQ. As such the curve may look unfamiliar, this is normal.
3. By default these generated presets will be such that the preamp setting puts the whole EQ curve under 0dB ("EQ-down-not-up" rule). For comparison purposes (between EQ on and off) you may consider moving the pre-amp up to a volume comparable with the direct output, however this might cause clipping in some situations.
4. If you don't see the Import button on the PEQ page, your font size may be set too large and the button may have gone offscreen you can rotate the screen or reduce the screen size for now. We are working on a fix for this.

 

[o0genesis0o]

1. Supported models
This is rolling out to all recent Android-based HiBy R branded devices through firmware updates now or in the near future. Check for the PEQ option in your Audio Settings after updating to the latest firmware.

2. How it works
Using the Equalizer tab and then the autoEQ option on squig.link, you can equalize earphones (that have been measured and uploaded to squig.link) to various "reviewer targets" or "reference targets" automatically using the autoEQ function. These EQ presets are supported on [supported models] using their new systemwide PEQ function.

3. How-to
a. go to squig.link and find the response curve for your earphones.
b. select the reference target or reviewer target to be overlaid in dotted lines. This will be the target autoEQ will attempt to convert to.
c. click Equalizer


d. Under "Parametric Equalizer open the "Choose EQ model" dropdown box to select your earphones on display.


e. Press "AutoEQ". AutoEQ will take a few seconds to run and calculate a set of parametric EQs for your earphones based on the target given.


f. Review the calculated EQ and make any changes to taste


g. Press the Export button (not the Export Graphic EQ button below) to export a text file containing the above settings.

h. Copy the resulting file to your HiBy R Android device. Or, if you did all of the above directly on a browser on your Hiby, you may skip this step --just note down the name of the text file generated.

i. On your HiBy R Android device, fire up PEQ inside Audio Settings. Press Import and select the file saved from the previous step using the file browser.

Enjoy

Notes:

1. HiBy Music makes no claims as to the merits of using autoEQ or indeed any parametric EQ vs not using them. That is for the user to explore and decide.
2. The curve displayed on the HiBy PEQ interface will be of the parametric EQs themselves, not the resulting FR curve which is the original FR curve modified by the PEQ. As such the curve may look unfamiliar, this is normal.
3. By default these generated presets will be such that the preamp setting puts the whole EQ curve under 0dB ("EQ-down-not-up" rule). For comparison purposes (between EQ on and off) you may consider moving the pre-amp up to a volume comparable with the direct output, however this might cause clipping in some situations.
4. If you don't see the Import button on the PEQ page, your font size may be set too large and the button may have gone offscreen you can rotate the screen or reduce the screen size for now. We are working on a fix for this.

Hey Joe, how many PEQ profiles can these DAPs keep at once? I'm thinking that these DAPs can be a useful tool to test some FR targets that I'm experimenting with the comfort of a DAP rather than being tied to my PC.

Fun thought: bringing PEQ to Hiby OS DAPs. I mean the MSEB is already on those devices.

 

[Joe Bloggs]

Hey Joe, how many PEQ profiles can these DAPs keep at once? I'm thinking that these DAPs can be a useful tool to test some FR targets that I'm experimenting with the comfort of a DAP rather than being tied to my PC.

It can save named presets and I'm not aware of any practical number limit

 

[gatecityradio]

Squig.link seems great and all, but their headphone library is maybe half the size of autoeq.app...As a result only a couple of my headphones/iem are available where all of them are available on autoeq.app, but unfortunately the .txt files autoeq.app use aren't compatible with the hiby PEQ. Since I'm stuck on a much older version of Android with the R5 Gen 2 other EQ apps like wavelet aren't available to me so I'm trying to use the built in PEQ. Are there any plans to update hiby PEQ where it can use .txt files like autoeq.app uses? If not is squig.link still adding headphones/iem to their library? Thanks.

 

[Blotto80]

The Roon OPRA project (LINK) may be something to look into integrating at an OS level. It should be pretty easy to use and is open source. Adding support from a hardware manufacturer like Hiby would go a long way to making it a central repo for EQ presets.

 

[XTF1]

The Roon OPRA project (LINK) may be something to look into integrating at an OS level. It should be pretty easy to use and is open source. Adding support from a hardware manufacturer like Hiby would go a long way to making it a central repo for EQ presets.

It appears to be open source, but with Roon involved, I just have some doubts: they must get something out of this…

As far as the EQ presets, my understanding is that they’ll be “curated”: somebody will review and decide, based on some unknown criteria, that a proposed preset is “acceptable”.

Open, yes… with some caveats.

 

[Joe Bloggs]

Squig.link seems great and all, but their headphone library is maybe half the size of autoeq.app...As a result only a couple of my headphones/iem are available where all of them are available on autoeq.app, but unfortunately the .txt files autoeq.app use aren't compatible with the hiby PEQ. Since I'm stuck on a much older version of Android with the R5 Gen 2 other EQ apps like wavelet aren't available to me so I'm trying to use the built in PEQ. Are there any plans to update hiby PEQ where it can use .txt files like autoeq.app uses? If not is squig.link still adding headphones/iem to their library? Thanks.

Only reason autoEQ .txts are incompatible is the extra decimal point on the frequency column. We only take whole numbers as squig.link files were our target when designing the importer. You may simply remove the decimal points and trailing numbers manually.

 

[gatecityradio]

Only reason autoEQ .txts are incompatible is the extra decimal point on the frequency column. We only take whole numbers as squig.link files were our target when designing the importer. You may simply remove the decimal points and trailing numbers manually.

Awesome, thanks for the reply!

 

[gatecityradio]

Just in case anyone else is curious, I tried editing the txt files from autoeq.app and they do work.

Here is an example of a txt file directly from autoeq.app for the Sony MDR-V6 corrected to the 2019 Harman curve.

Here is where I fixed it to work in the Hiby PEQ, all numbers directly following the Fc need to be whole numbers. If the decimal was below .5 I just took the decimal # out. If it was .5 or above I rounded to the next whole number.

I put a feature request in on autoeq.app's github to add an output option that is compatible with Hiby PEQ and shared what I had learned here. I know this is probably only an issue for a small group of people, but hopefully this helps someone in the future.

 

[XTF1]

I put a feature request in on autoeq.app's github to add an output option that is compatible with Hiby PEQ and shared what I had learned here. I know this is probably only an issue for a small group of people, but hopefully this helps someone in the future.

IMO, this should be on HiBY: they could for example improve their app to simply “ignore” the decimal—not perfect, but good enough “rounding” rule.

 

[AnamCeoil]

Just in case anyone else is curious, I tried editing the txt files from autoeq.app and they do work.

Here is an example of a txt file directly from autoeq.app for the Sony MDR-V6 corrected to the 2019 Harman curve.


Here is where I fixed it to work in the Hiby PEQ, all numbers directly following the Fc need to be whole numbers. If the decimal was below .5 I just took the decimal # out. If it was .5 or above I rounded to the next whole number.


I put a feature request in on autoeq.app's github to add an output option that is compatible with Hiby PEQ and shared what I had learned here. I know this is probably only an issue for a small group of people, but hopefully this helps someone in the future.

Thanks for taking the time to do this and show how it's done. Much appreciated!

 

[gatecityradio]

IMO, this should be on HiBY: they could for example improve their app to simply “ignore” the decimal—not perfect, but good enough “rounding” rule.

I agree, that's why I asked on here first if there was going to be an update to Hiby PEQ support autoeq.app txt files, but it looks like they targeted squig.link support instead. Autoeq.app does support multiple output types for different eq apps so I figured it was worth a shot to see if they could add Hiby PEQ support.

 

[Joe Bloggs]

I agree, that's why I asked on here first if there was going to be an update to Hiby PEQ support autoeq.app txt files, but it looks like they targeted squig.link support instead. Autoeq.app does support multiple output types for different eq apps so I figured it was worth a shot to see if they could add Hiby PEQ support.

I will see when things can be updated on our side. Every device would need to be firmware upgraded and those don't come every other week, that's all.

edit: in fact, new firmware is already supporting this. But this is not an update we'd push through to all devices without waiting for other issues to update. Which device are you using?

 

[gatecityradio]

I will see when things can be updated on our side. Every device would need to be firmware upgraded and those don't come every other week, that's all.

edit: in fact, new firmware is already supporting this. But this is not an update we'd push through to all devices without waiting for other issues to update. Which device are you using?

The R5 Gen 2. It wasn't working yesterday, but the ones I edited to not have the decimal were working.

 

[Joe Bloggs]

The R5 Gen 2. It wasn't working yesterday, but the ones I edited to not have the decimal were working.

Try updating to the latest firmware or wait for the next update if you're already on the latest.